Nano has already supplanted the great EMacs and Vim as the most popular text editor of all linux distros, for though it has many omissions in functionality it scores over the older, more complete programs in two important respects. First, it is slightly simpler; and secondly it has the text "^ Exit" inscribed in highlighted text on its footer

EDIT : This sees to be going over some people's heads. It's a hitchiker's guide to the galaxy reference.

The Hitchhiker's Guide has already supplanted the great Encyclopaedia Galactica as the standard repository of all knowledge and wisdom, for though it has many omissions . . . it scores over the older, more pedestrian work in two important respects. First, it is slightly cheaper; and secondly it has the words DON'T PANIC inscribed in large friendly letters on its cover.

you are viewing a single comment's thread
view the rest of the comments

[–] edinbruh@feddit.it 22 points 2 weeks ago* (last edited 2 weeks ago) (12 children)

It's there and it's easy. Most people don't use terminal text editors unless they are SSHing in a server, and they would only do that sporadically, so it makes no sense to become proficient in a complex text editor like vim or Emacs for that little use case.

Sidenote: personally, I learned vim once, and used it extensively every day for two years. I stopped using it for one year and was back to square one. Now I use vscode for everything... Even when I'm using SSH, because vscode supports SSH

[–] scrion@lemmy.world 4 points 2 weeks ago (1 children)

Every editor "supports" SSH, you can mount files on a remote SSH server via SSHFS.

[–] edinbruh@feddit.it 7 points 1 week ago (1 children)

And instead vscode supports SSH (without quotes), you can connect to an SSH host, and it will open files and folders on the host like it does locally. And if you open the integrated terminal it will run on the remote host. And it will forward the git login agent so you can commit or push with the credentials of your local machine. And it can forward ports from the remote.

[–] scrion@lemmy.world 2 points 1 week ago* (last edited 1 week ago) (1 children)

Sure, but none of that is special in any way. That's just what SSH does already. If you like that to happen in your editor GUI, by all means, you do you.

What I'm saying is not a single of those features is an accomplishment of vscode and you can do that with every editor you like, or even without any. I didn't want people to believe they'd need to switch to vscode to achieve any of that. That was my angle.

I can't and I'm not going to comment on the integration or the workflow, if you're the audience for those kinda things, it's probably great, give vscode a try. It's probably obvious that I am not but hey, different strokes and all.

[–] Kazumara@discuss.tchncs.de 2 points 1 week ago* (last edited 1 week ago)

By the way, regarding integration, I just learned from a colleague last week that he uses emacs for editing remote files too. You can just open a file as:

/method:user@host:filename, with method being ssh or ftp for example

https://www.gnu.org/software/emacs/manual/html_node/emacs/Remote-Files.html

load more comments (10 replies)