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
Broken workflow: return to the old incremental numbering behaviour when pasting files #76752
Comments
I really need a digital incremental copy |
This is a fair request. We will not do it in the current milestone but will consider it in the future. |
@isidorn Thanks! |
Yeah, I strongly prefer the previous number-based naming too, for all the same reason as @axefrog - and also because it ensured the new file would appear right next to the original file. With the new naming, the copy easily gets lost among the other files:
I'd encourage you to roll this change back asap, or alternatively introduce an option :-) |
I also prefer the old method of copy. Perhaps an option could be add where the user can choose how the file is copied? |
More details on the motivation why we did it #55128 |
@isidorn Actually, I thought it would only increment the number postfix added at the end of the file name. I can certainly see how magically incrementing numbers in the middle of the file name could be surprising and confusing to users, and possibly even a source of bugs. Personally, I'd prefer that if you copy a file, it simply adds the |
@thomas-darling It wouldn't work for the workflow I described in #55128 (comment) 😕 |
We have introduced a new setting The default value is You can try it out in vscode insiders in a couple of days. |
To verify: make sure this setting behaves as described in my last comment and provide potential feedback on the naming of the setting. |
I do a lot of rapid iteration on prototype code and like to frequently copy deprecated code files into archive subdirectories so they are still readily available for me to refer to immediately, without the friction of having to do so via Git branch/commit/diff operations. I also write a lot of markdown notes in sequentially-numbered files, each of which I create by copying and pasting its predecessor which I then use as a base template that is conveniently already named correctly as soon as it is created.
Until now, the incremental numbering behaviour has been nice as it let me copy a file into a folder and it would simply increment the number at the end of the file without polluting the rest of the filename. After the latest release, it's now polluting the filename with "copy", which forces me to manually rename the file. This is one of those cases where a change to help a few users has had the opposite effect for others. Usually a change in behaviour in a new release is accompanied by a setting in recognition that different people have different workflow preferences. There is no setting in this case, so I have no choice but to accept the added friction in my workflow.
Would it be possible to include a setting to retain the old behaviour?
The text was updated successfully, but these errors were encountered: