Some features:
* Create/rename/move/delete files by editing the current directory listing's textbuffer
* Filter using glob pattern
* Trash and undo support
* Works even in remote-ssh workspaces
* Works across multiple vscode windows
Some features:
* Create/rename/move/delete files by editing the current directory listing's textbuffer
* Filter using glob pattern
* Trash and undo support
* Works even in remote-ssh workspaces
* Works across multiple vscode windows
Also voil asks you to confirm destructive actions. And even if you do, by default voil moves deleted files to a trash location and has undo functionality so you can easily undo your mistakes.
just like fvwm, there is nothing better than :o) !
> Do you trust the publisher "Ali Mostafavi"?
> The extension voil is published by Ali Mostafavi. This is the first extension > you're installing from this publisher.
> Ali Mostafavi is not verified.
> Visual Studio Code has no control over the behavior of third-party extensions, including how they manage your personal data. Proceed only if you trust the publisher.
It is not easy to get verified in vscode marketplace, even major publishers like Qt organization are not verified much less so a solo open source developer like myself.
The problem is that nobody will do that. Even if it were 500 LOC.
And this is why supply chain attacks are on the rise.
> nobody will do that
"nobody" is a strong word. Yes, most people don't do that, but if a single person reads the source code and finds something nefarious they can report it or leave a review disclosing that and my reputation would be ruined.
1. There is no way that `touch newfile` is faster. Using voil, you press a keybind, enter `newfile`, save and you are done. Using touch you have to first, use some keybinding to switch to terminal, then type `touch ` (6 letter overhead) then type the name of the file and then switch back to vscode. I am not saying voil is meaningfully faster, but you saying that `touch newfile` is faster is wild to me.
2. If I am editing a comlpex file name I like having access to all the text editing features that I have in vscode as opposed to the barebones text editing features in the terminal.
3. There is also all the other moving/copying/renaming with visual feedback that you decided to completely ignore.
4. If touch was faster then oil.nvim would not have been such a popular extension. I am sure most vim users know how to use `touch`.
turboponyy•6h ago
heltale•6h ago
hexomancer•6h ago
- It can work across multiple vscode windows
- The top line (that shows the current directory) can be used to filter files. For example, if you add "*.{txt,md}" to the end of that line, it will only show the txt and markdown files.
- The ability to defined custom shell commands and bind keybindings to them. For example, I can create a command that zips selected files and run it with a single keybinding in voil.
- Undo functionality
hexomancer•6h ago
The major difference being that you still need to learn some new keybinds for dired, for example, you can't just create a file by editing the text buffer whereas in oil.nvim (and by extension, voil) your text editing skills immediately apply.
globular-toast•6h ago
hexomancer•6h ago
I kind of disagree? Most files were once created as an empty file! (at least that's the case in my workflow).
ckolkey•5h ago
globular-toast•2h ago
In Emacs I can even open a file in a non-existent directory and it will create all the containing directories when I try to save. So I rarely even use mkdir.
whalesalad•1h ago