Skip to content

Fix return Promises so each step runs in sequence#11

Open
xoob wants to merge 1 commit into
geddski:masterfrom
xoob:patch-1
Open

Fix return Promises so each step runs in sequence#11
xoob wants to merge 1 commit into
geddski:masterfrom
xoob:patch-1

Conversation

@xoob

@xoob xoob commented May 3, 2017

Copy link
Copy Markdown

Return the Promise of each executeCommand() call to PromiseSeries, so that commands are executed in sequence, not in parallel.

Return the Promise of each executeCommand() call to PromiseSeries, so that commands are executed in sequence, not in parallel.
@josenicomaia

Copy link
Copy Markdown

+1

@Spongman

Spongman commented Aug 8, 2017

Copy link
Copy Markdown

please merge this. this extension is pretty much broken without this.

@josenicomaia

Copy link
Copy Markdown

@Spongman Indeed

@Spongman

Spongman commented Aug 9, 2017

Copy link
Copy Markdown

also, the 'custom delay' patch is unnecessary with this patch.

@mizagog

mizagog commented Sep 4, 2017

Copy link
Copy Markdown

why is it not in...?

@therealpeterhua

Copy link
Copy Markdown

Is this extension abandoned? This fix is pretty core, why no merge?

@clayms

clayms commented Jan 2, 2019

Copy link
Copy Markdown

This worked well for me and is easy to understand. Simply add return to the beginning of lines 34 and 38.

Current:

vscode.commands.executeCommand(action.command, action.args);

vscode.commands.executeCommand(action);

Fixed:

return vscode.commands.executeCommand(action.command, action.args);

return vscode.commands.executeCommand(action);

@jpotterm

jpotterm commented Apr 2, 2020

Copy link
Copy Markdown

Since it's been three years with no merge I found this fork that fixes this: https://github.com/ctf0/macros

@tobiashochguertel

tobiashochguertel commented Apr 22, 2022

Copy link
Copy Markdown

@geddski how is it about this Pull Request? Can we may work on this this weekend and merge and release a version 1.3?

@Ashark

Ashark commented May 10, 2022

Copy link
Copy Markdown

This worked well for me and is easy to understand. Simply add return to the beginning of lines 34 and 38.

Current:

vscode.commands.executeCommand(action.command, action.args);

vscode.commands.executeCommand(action);

Fixed:

return vscode.commands.executeCommand(action.command, action.args);

return vscode.commands.executeCommand(action);

I also am affected by the issue. See https://stackoverflow.com/questions/72153504/prevent-asynchronous-order-of-command-sequence-execution-in-vs-codium

I added these two return in the ~/.vscode/extensions/geddski.macros-1.2.1/extension.js, but it did not work for me. It still always execute commands in parallel. Any advise?

@Ashark

Ashark commented May 10, 2022

Copy link
Copy Markdown

Since it's been three years with no merge I found this fork that fixes this: https://github.com/ctf0/macros

@jpotterm How to install that? It seems it has not been published in marketplace?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants