146900a07 broke VSCode commit editing for me. Does anyone have a workaround?

[aconradi]

I use remote ssh in VSCode and use its code -w as my editor. This used to work great with jujutsu, but with commit 146900a it broke.

The -w flag is supposed to tell VSCode to wait, but that doesn't work when the file to edit is outside the workspace of the VSCode window which causes VSCode to open a new window. In this case the code -w command returns immediately and then VSCode opens the new window editing the commit message.

When jj put the commit message files in the .jj directory VSCode did not open a new window, so code -w worked.

Does anyone have a way to get using VSCode as the editor to work to edit jj commit messages?

[PhilipMetzger]

This issue is related, see #6540

[martinvonz]

FWIW, I'm fine with reverting that commit if necessary. We can instead do something like automatically cleaning up description files that are older than a week or something. (Or we can do nothing. Maybe these files only bother me.)

[aconradi]

I'd like that, but I'm just a happy user. Now I sort of regret updating jj as it broke my workflow. I know this is not jj's fault, but rather a bug in VSCode. I'm considering a downgrade of jj to a version without that change right now.