Wait until previous command is "done" before executing next command in sequence?

[macintacos]

It'd be really nice if there was an option for multi-command to "wait" until whatever palette the previous command brought up is "dismissed" before moving on with the next command in the sequence (unless the previous command was "escaped", like if they hit the "ESC" key or clicked out of the prompt).

As an example, take the following command:

    {
      "command": "multiCommand.test",
      "sequence": [
        "workbench.action.quickOpen",
        "workbench.action.moveEditorToBelowGroup"
      ]
    },

I set this up because I want to search for a file, and then after I hit "enter" I'd like that file to be moved to the editor in the below group. However right now that's not how it works; the quick open panel opens, but then it immediately executes workbench.action.moveEditorToBelowGroup without waiting for me to actually search for a file.

It'd be nice if multi-command "knew" that it needed to wait for the quick open panel to be closed before moving on to the next command in the sequence. There isn't a way that I'm glossing over, is there?

[aterenin]

As a workaround, you can set the interval property to some positive number, so that the package waits a bit before executing the rest of the command.

I'm using this extension to work around very poor default behavior of the "Run Selected Text" command described in https://github.com/Microsoft/vscode/issues/43242 by running cursorDown after workbench.action.terminal.runSelectedText.

Waiting for previous command to complete rather than setting a specific fixed timeout interval would be ideal.

[ryuta46]

This extension waits until the previous command has finished. But "workbench.action.quickOpen" command itself is finished when the small picker window is opened.

I checked the source code of quickOpen command in VSCode GitHub but I couldn't find a way to wait for the user to select a file, or get what that user select from an extension.

As another workaround, you can use workbench.action.acceptSelectedQuickOpenItem command when you select a file in quick open window.

For example, in settings.json

        {
            "command": "multiCommand.test",
            "sequence": [
              "workbench.action.acceptSelectedQuickOpenItem",
              "workbench.action.moveEditorToBelowGroup"
            ]
        }        

and bind it in keybindings.json

    {
        "key": "alt+t",
        "command": "multiCommand.test",
        "when": "inQuickOpen"
    },

and type alt+t instead of enter for selecting a file. I wanted to bind this command to just enter key but it didn't work...

[ArturoDent]

Actually,

{
   "key": "enter",
   "command": "multiCommand.test",
   "when": "inQuickOpen"
},

works fine. But workbench.action.moveEditorToBelowGroup is a problem if you don't already have a split editor down. So if there is split editor, vscode will not create another group with that command.

For me if there is already a group down, the enter version works just fine.

[mjs271]

To throw my hat in the ring, I would also love a feature that waits for a command to finish before moving on to the next one; e.g., like a bash script. My use case is with the LaTeX Workshop extension. I attempted chain together build and View LaTeX PDF file as:

{
    "key": "cmd+b",
    "command": "extension.multiCommand.execute",
    "args": { 
        "sequence": [
            "latex-workshop.build",
            "latex-workshop.view"
        ]
    }
}

However, it is typically the case that the pdf takes a moment to build, so the view executes before the build finishes. It is even worse if it's a first-time build, as an error is thrown because the pdf does not exist yet. Also, @ArturoDent, I dig the handle. Arthur Dent is my go-to placeholder name for most cases 🙂.