I open nano more often than any other editor, and by a lot. I spend more TIME in vscode and maybe Kate, but lately I’ve been tweaking setups on a couple of machines.
It is an old joke that I thought was very well known, at least for people that know about emacs, my mistake, but hey, Luck 10.000 of you, so here it goes:
“Emacs is a great operating system, lacking only a decent text editor”
The only differencedownside really is the occasional extension that needs a manual install.
I’ve been trying out VSIX Manager for my extensions so that I can keep track of which ones I want to install on each machine. This can make it easier to install the weird extensions that you can’t install otherwise
I tried open vss I think it’s called on arch and I have trouble using it to remotely access configs on my home server via the SSH extension. I got fed up with it and installed the MS version from yay. I resent it but it works.
I think the open version might not have the ms extension store configured. There should be a separate AUR package for that. At least there is for VSCodium. Alternately you can just grab the VSIX for the extensions you want from the MS version and install them on the open one. Personally I don’t know what open vss is so I use codium.
Friendly reminder that VSCodium exists, and nobody should be using Microslop’s spyware version anyway.
Friendly reminder, that Emacs exists.
Hostile reminder that vi exists.
Helix crew, where we at
#nano4life
I open nano more often than any other editor, and by a lot. I spend more TIME in vscode and maybe Kate, but lately I’ve been tweaking setups on a couple of machines.
sudo nano /that/cfg/file/u/thinking/.aboutUse
sudoedit(orsudo -e) to make sure you don’t mess up permissions and alsoexport EDITOR=vimin your shell to use a superior editor.JED checking in from out wherever Voyager is at the moment (sorry about the lag)
And vim/nvim.
*And vim~~/nvim~~.
deleted by creator
I am sorry? Are you suggesting that somehow an text editor has more functionality than a fucking OS?
deleted by creator
It is an old joke that I thought was very well known, at least for people that know about emacs, my mistake, but hey, Luck 10.000 of you, so here it goes:
VSCodium would have the same Electron caching issues though, wouldn’t it?
That’d be relevant if it were the issue and not specifically snap related.
Been using zed lately. Pretty similar ui, wildly different performance.
I’ve been using sed recently to edit my lines. Quite cumbersome but it gets the work done.
Friendly reminder that Kate has nothing to do with Microsoft at all.
The only
differencedownside really is the occasional extension that needs a manual install.I’ve been trying out VSIX Manager for my extensions so that I can keep track of which ones I want to install on each machine. This can make it easier to install the weird extensions that you can’t install otherwise
https://open-vsx.org/extension/zokugun/vsix-manager
Not the only downside - some MS developed extensions, e.g. their Python integration, have to be patched to work with VSCodium: https://github.com/VSCodium/vscodium/discussions/1641
Yeah, they really added DRM.
Well, that and the lack of telemetry and “phoning home” to Redmond. And that’s a big one.
Whoops, I meant to say “only downside”. Edited it
There are lots of positive differences
Arent a lot of extensions incompatible by design? Some closed part of vscode needed for full functionality.
Oh nice, I didn’t know, thank you!
I tried open vss I think it’s called on arch and I have trouble using it to remotely access configs on my home server via the SSH extension. I got fed up with it and installed the MS version from yay. I resent it but it works.
I think the open version might not have the ms extension store configured. There should be a separate AUR package for that. At least there is for VSCodium. Alternately you can just grab the VSIX for the extensions you want from the MS version and install them on the open one. Personally I don’t know what open vss is so I use codium.
I got it working on vscodium, i’ll try using that. thanks!
Awesome, great to hear that!
Team Jetbrains!