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

Eliminate leading "escape"? #17

Open
gitcabezon opened this issue Jun 15, 2020 · 2 comments
Open

Eliminate leading "escape"? #17

gitcabezon opened this issue Jun 15, 2020 · 2 comments

Comments

@gitcabezon
Copy link

Is it possible to eliminate having to press escape to type a new shell command?

At first invocation, it goes into a "search the command history" mode, but I'd rather it go straight into editing-the-command mode, where up/down arrows would switch between previous commands, and right-left arrows would let you modify the current command, and enter would run it immediately.

Even better would be to have "/" switch into "search the history" mode.

@ryu1kn
Copy link
Owner

ryu1kn commented Jul 7, 2020

Hi @gitcabezon , thanks for the great suggestion. Let me re-think this once we have the following feature implemented in the editor.

microsoft/vscode#35785

I'd like to start typing a command (without dismissing the history panel first), but looking at past commands at the same time 😃

@pallxk
Copy link

pallxk commented May 29, 2024

For now, I'm using the following key binding to work around this:

    {
        "key": "cmd+k cmd+e",
        "command": "runCommands",
        "args": {
            "commands": [
                "editWithShell.runCommand",
                "editWithShell.runCommand"
            ]
        },
        "when": "!inKeybindings"
    },

This works regardless of whether command history is empty or not, and will go directly to the Enter a command prompt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants