Is it possible to make an extension like that for Zed?
AFAIK not with their current extremely limited API, but it’s on their roadmap to have a more extendable editor.
Show HN: VS Code extension to edit the filesystem like a text buffer
41–50 of 50 posts
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#42Awesome work! I’ll definitely try this out.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#43Falling to see why `touch newfile` doesn't accomplish this as fast if not faster and without yet another extension.
I doubt this comment was in good faith (you decided to ignore literally all the features I mentioned and focused on just creating files) but I am going to reply anyway: 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…
If you need complex file manipulation, all of that can be achieved by writing a shell script. That's what I've been doing. You also automatically get access to flow control statements and tools like sed/awk/find.
> all the text editing features that I have in vscode as opposed to the barebones text editing features in the terminal.
VSCode is a very primitive text editor compared to vim, emacs or helix. You don't need to edit the command line right there in the shell prompt, nor do you need to create any files — press Ctrl+X + Ctrl+E and hack away. Save and close the file (ZZ in vim, for example), and it gets executed by the shell.
> then oil.nvim would not have been such a popular extension
Popularity is a bad metric, most people don't bother to learn the tools they're using.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#44This looks cool, but I'm a bit wary of publishers that aren't verified. > 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 t…
You can view the source code and package the extension yourself if you are worried about that. It is only ~2000 LOC. 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.
I’m Iranian too and our names get people a lot more concerned.
If your name sounded English the implicit bias would make you sound more trust worthy.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#45Earlier quoted context omitted.
You can view the source code and package the extension yourself if you are worried about that. It is only ~2000 LOC. 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.
> view the source code and package the extension yourself 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.
>The problem is that nobody will do that. Even if it were 500 LOC.
I do it with the code I download to extend Emacs.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#46Earlier quoted context omitted.
I doubt this comment was in good faith (you decided to ignore literally all the features I mentioned and focused on just creating files) but I am going to reply anyway: 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…
If you need complex file manipulation, all of that can be achieved by writing a shell script. That's what I've been doing. You also automatically get access to flow control statements and tools like sed/awk/find. > all the text editing features that I have in vscode as opposed to the barebones text editing features in the terminal. VSCode is a very primitive text editor compared to vim, emacs or helix. You don't need…
> If you need complex file manipulation, all of that can be achieved by writing a shell script. That's what I've been doing. You also automatically get access to flow control statements and tools like sed/awk/find.
Well yes, of course they all "can" be done by writing a shell script, the same way any text editing with vim "can" also be done using ed.
> VSCode is a very primitive text editor compared to vim, emacs or helix. You don't need to edit the command line right there in the shell prompt, nor do you need to create any files — press Ctrl+X + Ctrl+E and hack away. Save and close the file (ZZ in vim, for example), and it gets executed by the shell.
I actually use vscode with the vim extension. You seem to be assuming I am unfamiliar with vim and emacs, I can assure you I know them well enough (at least vim, I also am familiar with the overall features of emacs, though I lack the muscle memory to use it efficiently).
Here is an example: Let's say you have a file named `feature_experimental.cpp` now you want to remove the `_experimental.cpp` from all the files in the current directory which have `_experimental`. I assure you that I can do it faster using voil than you can with vanilla vscode.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#47Earlier quoted context omitted.
What are you proposing? Should I not be allowed to develop and publish an extension that I think is useful? > 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.
IMO you should avoid installing editor extensions generally. It's better to try to get them merged into the editor itself. I don't think it's good to constrain people in some way from doing that, you should just have a personal policy of avoiding extensions you're not involved in the development of.
I thought the entire point of vscode was to be an extensible "lightweight" barebones code editor, as opposed to eg jetbrains stuff; what about vim/emacs then?
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#48Falling to see why `touch newfile` doesn't accomplish this as fast if not faster and without yet another extension.
I doubt this comment was in good faith (you decided to ignore literally all the features I mentioned and focused on just creating files) but I am going to reply anyway: 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…
1. There is an inbuilt terminal in VS code. Its almost always active for me and even if it isnt focusing it/bringing it up is the same distance as firing up voil. The benefit here is that it doesnt occupy your editor
2. What complex file names do you need text editing features for?
3. fzf and zoxide covers most of it
I dont want to return the favor of speculate on intent of comment as yours would be petulant and stubborn without focusing on meaningful rebuttal. Im placing this in my comment as based on your other responses there does seem to be a pattern.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#49This looks cool, but I'm a bit wary of publishers that aren't verified. > 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 t…
You can view the source code and package the extension yourself if you are worried about that. It is only ~2000 LOC. 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.
I have high 2 digits of extensions in my VS Code, and yours is the only one that wouldn't have a verified publisher. And I certainly have more than one from solo developers.
Qt organization (because you mentioned it) also has verification. It displays a different message (because I haven't installed anything from them):
> The extension Qt Core is published by Qt Group. This is the first extension you're installing from this publisher.
> Qt Group has verified ownership of qt.io.
> 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.
EDIT: I'm sure there are other extensions that are also by unverified publishers. It was the first time I was hit with that message though.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#50Earlier quoted context omitted.
I did not by any means want to discourage you from developing things and sharing them, if anything I thank you for that. My intention was to highlight that the SW supply chain nowadays is an insecure mess. Regarding your last point, for the vast majority of open source SW releases, we can never be sure if the release we get is produced from the same code we see. I do not know if that is the case with VScode addons, b…
> Regarding your last point, for the vast majority of open source SW releases, we can never be sure if the release we get is produced from the same code we see. I do not know if that is the case with VScode addons, but you get my point You actually can depackage vscode's .vsix files (it is just a zip file) and compare the package contents to the repository.
Yes but realistically, who is going to do that ?
Again, I am not questioning your integrity or your plugin.