Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Splitting terminal breaks navigation #8493

Closed
musjj opened this issue Oct 8, 2023 · 4 comments
Closed

Splitting terminal breaks navigation #8493

musjj opened this issue Oct 8, 2023 · 4 comments
Labels
C-bug Category: This is a bug

Comments

@musjj
Copy link

musjj commented Oct 8, 2023

Summary

In a kitty terminal, if you try to open a new window split, buffer navigation will no longer work. You can also see the line numbers being a little bugged out. For some reason, pressing <Esc> will make everything work again.

Reproduction Steps

asciicast

I tried this:

  1. hx <file>
  2. :sh kitty @ launch (alternatively, :sh kitty @ launch --location hsplit)
  3. Close the new window (<C-d>, etc.)

I expected this to happen: Everything works fine

Instead, this happened: Buffer navigation stops working

Helix log

My log file is empty.

Platform

Linux

Terminal Emulator

kitty 0.30.0

Helix Version

23.05-466-gbdf7937a

@musjj musjj added the C-bug Category: This is a bug label Oct 8, 2023
@CptPotato
Copy link
Contributor

CptPotato commented Oct 9, 2023

This is actually the command's stdout output (try :sh echo hi). After a quick search I didn't find a "silent" variant of :sh.

To elaborate, ctrl-u/ctrl-d doesn't work because it's used to scroll the popup window.

@musjj
Copy link
Author

musjj commented Oct 9, 2023

Oh wow you're right. The "weird line number" was actually the output of the command (a window ID). The solution for my particular case is to use kitty @ launch --no-response. But a silent version of :sh would definitely be helpful.

I'm going to open a new issue, but what's the right place for a feature request? There's an issue template for a feature request, but it seems that feature requests tend to be moved to discussions. A clearer policy would be helpful.

@CptPotato
Copy link
Contributor

I'm going to open a new issue, but what's the right place for a feature request? There's an issue template for a feature request, but it seems that feature requests tend to be moved to discussions. A clearer policy would be helpful.

Feature requests in this repo are fine, though it's best to search before (silent :sh version PR is here #3247). I guess requests are sometimes converted to discussions when they don't quite align with the repo owner's vision (requiring further discussion about the feature or possible workarounds) or are already implemented.

@musjj
Copy link
Author

musjj commented Oct 9, 2023

Alright, thanks for the info, closing this issue for now.

@musjj musjj closed this as completed Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug
Projects
None yet
Development

No branches or pull requests

2 participants