Is it possible to make an extension like that for Zed?
Show HN: VS Code extension to edit the filesystem like a text buffer
21–30 of 50 posts
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#22This 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.
> 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.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#23"Look what they need to mimic a fraction of our power" - some Emacs user, probably
[deleted]
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#24When I was a student about 10 years ago there was a custom shell that works like this and even had an extension for sublime, but for the life of me I cannot remember its name.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#25Earlier 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.
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.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#26This 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…
For the current extension model, I would not trust anyone besides any known org. Even installing themes are potentially dangerous, because of the attack vector.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#27Is it possible to make an extension like that for Zed?
At this point I opted to just install extension from known ORGs only, like Microsoft, Github, etc and the official extensions from the languages I use. All other extensions, even themes are no more for me.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#28Falling to see why `touch newfile` doesn't accomplish this as fast if not faster and without yet another extension.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#29See vimv ( https://github.com/thameera/vimv ) for a minimal version of this in the CLI, using Vim as the editor.
Also vidir, which is in the moreutils package in popular distros.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#30Falling 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 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`.