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

The UI for a previously ran InputHandler command is shown when running a different InputHandler command from a keyboard shortcut #2926

Open
frou opened this issue Aug 11, 2019 · 2 comments

Comments

@frou
Copy link

commented Aug 11, 2019

Description

There is a bug when using a keyboard shortcut to run a command that uses a ListInputHandler.

Video here

Source for the two commands shown in the video, and the corresponding .sublime-commands and sublime-keymap files are here

cc @OdatNurd

Steps to reproduce

  1. Use the Command Palette to find and run a command that uses a ListInputHandler.
  2. Use a keyboard shortcut to run a different command that uses a ListInputHandler.

Expected behavior

The ListInputHandler for command (2) is presented.

Actual behavior

The ListInputHandler for command (1) is presented again.

Environment

  • Build: 3208
  • Operating system and version: macOS 10.14.6
@frou

This comment has been minimized.

Copy link
Author

commented Aug 11, 2019

A few times, a different malfunction happened. Instead of the ListInputHandler for command (1) being presented again, the view syntax highlighting would inconspicuously get changed to LaTeX Log. So presumably those times, the Set Syntax: LaTeX Log command in the palette was somehow being ran.

@OdatNurd

This comment has been minimized.

Copy link

commented Aug 11, 2019

I've only personally witnessed the second variant of this happening (The key binding executes the wrong command) but it happens for any input handler type.

If you happen to have command logging turned on when you press the key binding, you can see that it logs the correct command even when it executes the incorrect one.

Most often the incorrect command being executed is one of the syntax commands, but this isn't always the case. I'm guessing that that happens most often because they are predominant in the command palette.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.