Live data from Hacker News

GNU nano is my editor of choice (2021)

ariadne.space

221–230 of 303 posts

Re: GNU nano is my editor of choice (2021)

#222
post #177

Earlier quoted context omitted.

Nano default key bindings are not standard either. They are less different than vi from a typical GUI input controls and having a menu at the bottom of the screen help, but they force the user to get used to yet another convention. I was considering at some point to create a patch to nano to have a simple option to switch to more common bindings or even ask the user on the first run about it. But then I discovered th…

They're standard for beginning of line, end of line, cut line when using bash/zsh; that's already most of the way there. I use vim day to day but I do miss pico's ctrl-k/ctrl-u behavior for doing quick block cut/paste.

most shells support both emacs shortcuts and vi style commands so there are at least 2 "standards" fwiw.

Re: GNU nano is my editor of choice (2021)

#223
post #39

There is a very simple, end-of-discussion type argument why shipping Vim as the default editor is a terrible idea: Because its user interface differs significantly from how every other program on the system works. You can have all kinds of fruitful or fruitless debates about whether there is some deeper sense in which Vim is a "superior" editor, but there is no sensible reason for it to be the default, ever. Conventi…

> Replacing Vi(m) with Nano in the standard install was one of the most important UX decisions made by the major distros in recent years It sounds like you want a unix with the UI/UX of a different OS. If a user is coming from a world where editors have all coped MS-DOS edit and its notepad progeny then nano makes sense. I am sure this goes for whatever default editor comes with Mac. If a user is coming from a Unix w…

Back in the day you'd write your own driver where need be, and compiled almost everything. I'm quite happy to not be back in the day and will take nano for editing a config file over writing C in Vim.

Re: GNU nano is my editor of choice (2021)

#224
post #39

There is a very simple, end-of-discussion type argument why shipping Vim as the default editor is a terrible idea: Because its user interface differs significantly from how every other program on the system works. You can have all kinds of fruitful or fruitless debates about whether there is some deeper sense in which Vim is a "superior" editor, but there is no sensible reason for it to be the default, ever. Conventi…

ed is the only editor which works like every other console program on the system. Nano does not work like every other program on the system. Neither vi nor nano should be shipped in the base system.

This is the reason why ed was originally "the standard editor".

Of course, moving from teletypes to terminals made it quite irrelevant as we moved to ex/nvi, but ed still has its advantages. It only requires a kernel and a libc, forget even needing ncurses or termcap. It was running perfectly fine on an 11/40 running V6 on 250kB of memory, so it has stayed insanely resource efficient by today standards.

It's not even that bad once the verbose errors are activated (H), and it's still better than using sed or cat > << to recover a partition.

Re: GNU nano is my editor of choice (2021)

#225
post #99

Earlier quoted context omitted.

I have used VI in and out since introduced to it on Xenix in 1993. Definitely not missing out.

I know I'm not going to convince everyone, and I know that there are other advanced options that compete (people tell me I'm missing out because I don't use an IDE with all the auto complete stuff). But I see a lot of people using a text editor that's basically notepad, possibly with syntax highlighting. For an occasional edit that's fine, but if you regularly spend more than an hour editing a file, you would benefit…

IDEs of course, and if stuck on UNIX without an IDE, either Emacs (muscle memory goes back to XEmacs glory days) or VSCode.

Pure text editor, Notepad++.

Re: GNU nano is my editor of choice (2021)

#226
post #67

Earlier quoted context omitted.

How can you even use cat to write? I understand dd or echo, but cat by itself? Cat /dev/whatever and a steady hand?

$ cat test > this is a test text file > written with cat > EOF $ cat > test > this is an extra line at the end > EOF $ cat test this is a test text file written with cat this is an extra line at the end But not sure how you modify them. An option will be using other tools but that makes cat incapable of being a text editor .

[deleted]

Re: GNU nano is my editor of choice (2021)

#227

Earlier quoted context omitted.

> Does any such academic study exist for any editor comparison? I don't know, you tell me. You're making the claim that one is superior. The burden of proof is on you.

The burden of proof is not infinite. Asking specifically to a level of proof that does not exist either way on a subject that does not pertains to such a level of proof is merely stifling discussion, not to mention that the claim that the editors are equal in capability are not immediately obvious and proof absolving.

Expecting a single scientific study is not infinite burden of proof, in response to someone making a claim. It's the least to expect.

Though it's convenient for you that you consider anything higher than your own standards "infinite".

Re: GNU nano is my editor of choice (2021)

#228
post #99

Earlier quoted context omitted.

I have used VI in and out since introduced to it on Xenix in 1993. Definitely not missing out.

Neovim is a different beast than vi or vim, definitely suggest looking into it. It's insanely capable, and if major IDE's invested time into supporting it, you wouldn't need to ever choose between Neovim or an IDE, you could just use both together. I think currently VS Code is the only editor that supports Neovim properly, there might be others though. The neat benefit is you get all the editors own plugins + all of…

If stuck with classical UNIX editors, I rather spend my time on Emacs.

I know VI well enough to save me when nothing else is available, specially helpful when dealing with servers without root account access, and noexec $HOME, and that is good enough for me.

Re: GNU nano is my editor of choice (2021)

#229
post #102
post #58

For people picking up linux for the first time that initial impression is crucial. Dropping people like that into an editor that requires you to somehow know ":q!" is the answer is utterly insane. Same with beginner tutorials using vi. It's straight up bad for linux adoption even if technically superior. Anyone that is a vi fan likely has the skillset to install it themselves - the reverse is not always true.

> It's straight up bad for linux adoption even if technically superior. I think the idea that Vim is "technically superior" should be challenged as well. I've watched, and participated in, dozens of discussions on text editors, and have never been shown a concrete piece of scientific evidence demonstrating Vim's claimed superiority according to any real-world metric. All we have are artificial comparisons where it ta…

Yeah. I think it's silly to make the claim, by and large. For me, using vim is like a hobby. It helps me get into flow state because I have fun writing and editing code using an editor I know well, have configured, and can zip around in fast without touching the mouse. I never try to convince anyone else to use it, though if a coworker shows interest I'm more than happy to oblige. It's the right tool for me. VS Code and IntelliJ products are the right tools for others, and that's cool too.
Post reply on HN