mjcrouch
Saving a file often fails
I don't want to p4edit modified files, because I often undo my edits, I want to check out only when I save them. However this can be slow if the server doesn't respond immediately, and the file remains write-protected, and vscode shows a popup asking whether I want to overwrite it. Editing many files at once, this slows down the save all process very much, because only 3 popups are shown at once by vscode. Can you find a way to wait for the edit operation and its subsequent OS writeprotection flag removal?
Hi - yes, there is a way to do this. VS code sets a limit on how long we can delay saving a file before it asks about overwriting - however we can get around it by using a different command instead of the save command.
Specifically you can rebind your save keyboard shortcut so that if we know the file is in a perforce client and not already open then it will try to open it - this is described in the faq here - (you could also just bind a different keyboard shortcut and use that instead)
Editing many files at once, this slows down the save all process very much, because only 3 popups are shown at once by vscode.
What's the scenario where you save many files at once? i.e. do you go through all your edited files and save them each one at a time or is there some way you're saving them all in one operation (I can't think of one atm :))?
see #72 for more context on the implementation
Ah yes, it might be possible to make a similar command for 'edit and save all open files' which might help. It seems that find and replace generally automatically saves files when it replaces so we wouldn't be able to change the way that behaves as far as I know