Option to disable Undo/Redo for File Operations

[tsiege]

Multiple times since the "Undo File Operations" feature has been released, I've experienced accidentally undoing file renames/deletions. This has caused me a lot more trouble than it's worth. I've lost time undoing unknowingly altering my file system and even automatic name changes in other files related to auto renaming. A prompt isn't enough for me. I simply find the feature harmful to my workflows and would like to have the ability to turn it off. I know others have also found it difficult as well

[isidorn]

This is a fair feature request, however we do not have it on our immediate plan. Thus assigning to backlog and we might add this in the future. Thanks

[tsiege]

Thanks @isidorn!

[elis]

When navigating between files, and often selecting a file that you just recently did some change to (in the code), and at the same time having some changes made to the files themselves (e.g. copying, renaming, moving files via the file navigator), I often click Undo/Redo EXPECTING my code to update, but sometimes it will have catastrophic consequences, such as deleting an entire codebase with no ability to "Redo/Undo" to retrieve any of the lost code.

Didn't commit? well, have fun trying to reconstruct your last three hours of your coding session - because it's gone and you have no way to get it back!

Please - allow some way to disable this demonic "feature".

When I click on a file in the file navigator, I expect the code editor to be the active element that any and all actions will be performed on. Having the focus stay on the file manager is utterly unintuitive and requires high attention to details to not mess up a work in progress.

[avshyz]

This is highly frustrating.
@isidorn Jet brains products has the same feature, but in their case there's a prompt, warning about the operation that's about to happen ("are you sure you want to undo file deletion / move of x files?")

[elis]

From the Stackoverflow thread mentioned by the OP, here's a quick fix that you can use by modifying the keybindings json to the following:

    {
        "key": "cmd+z",
        "command": "undo",
        "when": "editorFocus"
    },
    {
        "key": "cmd+z",
        "command": "-undo"
    },
    {
        "key": "shift+cmd+z",
        "command": "redo",
        "when": "editorFocus"
    },
    {
        "key": "shift+cmd+z",
        "command": "-redo"
    }

[slikk66]

I would like to disable all keyboard operations for the file explorer, period. I just had to reconstruct missing files/folders that were appearing/disappearing, I have no idea how these things even were happening. I'd prefer no files get deleted, undeleted/redeleted etc unless I use the mouse and menu actions to perform file operations.

[watsonian]

I would like to reiterate that this needs to be addressed. I'm not sure why this feature was implemented, but it's caused me much grief. The behavior is unexpected and I find that I end up accidentally undoing file explorer operations when I had no intention of doing so several times per day. I've not once ever wanted to undo anything done in the explorer. So, this feature has introduced daily frustration to solve something that was never a problem. Behavior like this should be toggle-able and defaulted to disabled.

[gravity-addiction]

Why is this still an issue??? The issue wouldn't be so bad if the REDO command actually worked. The feature is broken and should never have made it to production. It's been an issue for 6 month, I spent a month on sublime due to this issue. been pretty good and just had a folder complete get erased, not in the garbage can, not anywhere. just f'in gone, and redo gave me an empty folder..

[h-archer]

This is an absolute joke!! The guy who thought of this "feature" needs to be put into prison for life!!! What are you thinking vscode team??? You have shown a lack of user commitment.

GET RID OF THIS NOW!!!!

[fedalvez]

I think is a cool feature, however it needs to be confirmed by the user before doing it.