So emacs-dired ?
Show HN: VS Code extension to edit the filesystem like a text buffer
31–40 of 50 posts
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#32hey that's just dired ! https://www.gnu.org/software/emacs/manual/html_node/emacs/Di...
There was some discussion about dired here: https://news.ycombinator.com/item?id=44568404
yup ! thanks i read it all. have been using Emacs for longer than i care to admit.
just like fvwm, there is nothing better than :o) !
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#33Earlier quoted context omitted.
> 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.
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.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#34This 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.
The burden isn't just when I install it, I need to validate every time it's updated as well. But let's be realistic, the fact that I intrinsically trust extensions published by Microsoft isn't any better.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#35Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#36There's a long history of "directory editor" programs going back to (at least) 1974, which predates emacs. It's not surprising that there are many examples of convergent evolution.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#37There's a long history of "directory editor" programs going back to (at least) 1974, which predates emacs. It's not surprising that there are many examples of convergent evolution. https://invisible-island.net/ded/dating-dired.html
That's so cool, I was actually curious about history of such programs. Thanks for posting this :)
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#38Earlier quoted context omitted.
> 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.
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, but you get my point
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#39Earlier 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.
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.
Re: Show HN: VS Code extension to edit the filesystem like a text buffer
#40This 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…
[deleted]