GNU nano is my editor of choice (2021) • Hacker News Board

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

#301

Post by palata » Fri, Dec 30, 2022, 1:38 PM UTC

torstenvl wrote: post #165

palata wrote: post #153

Earlier quoted context omitted.

Sorry for the communication style, that's noted. I meant to communicate a point though. My point is that I don't want vim to copy with "Cmd + V" (I want the vim bindings there), and maybe I want to reuse "Cmd + V" in Blender for something more important than "paste" (assuming that "pasting" is not really a concept in Blender, I don't know). But still I want "Cmd + V" in Word and in my e-mail client. How do you set th…

They're not enforced by technical means, usually, but Apple HIG are fairly highly regarded by developers and users alike. I only do UI programming in wxWidgets so I can't speak for other developer workflows. When I create a menu system, if I don't include accelerators manually, the system-appropriate ones are automatically added for certain things. Additionally, wxWidgets automatically moves Windows/Linux "standard"…

Yeah for UI it makes a lot of sense. Especially if those are "standalone" (for lack of a better word) elements. For instance, changing the accelerators (I guess that's related to the animation when opening a menu, right?) cannot really conflict with anything else. So it's perfect to use system-wide configurations like that.

But I wonder about key bindings. I think it makes sense to have guidelines, and to use "Cmd + Q" to quit whenever it makes sense. But defining this as a high-level action "quit", and letting the user define the binding (e.g. "I want Cmd + S to quit") seems rather complicated to me. If "Cmd + S" is already set system-wide for the "save" action, then the system could tell you "that will disable the 'save' action, are you sure?". But if you go for "Quit with Cmd + J", and "Cmd + J" is not a system-wide binding but instead is used by... say... Blender. Then the system will happily change "Ctrl + Q" with "Ctrl + J", and now what happens if you hit "Ctrl + J" in Blender? Should it quit, or should it do what Blender does for "Ctrl + J"?

I am not sure everything can be configurable. My Firefox toolbar is at the top, on mobile I can have it at the bottom (not sure I can do that on Desktop). But I can't have it in the middle of the page, or vertically on a side. That's a decision that was made by the Firefox devs, not by the system settings. That does not mean we should not expect sane defaults, but I would argue that ":q" is a sane default in vim.

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

#302

Post by themodelplumber » Fri, Dec 30, 2022, 4:08 PM UTC

cesarb wrote: post #164

There's a reason I've always removed nano on every system I administer, and have done so for decades: when I first learned of nano, I also learned that it can corrupt configuration files where line breaks are significant by hard-wrapping long lines, unless you're very careful to always use "nano -w" instead of just "nano". I believe that this default has changed in a recent version of nano, and even before that some…

I accidentally turned this on once, IIRC, and discovered the issue after some shell scripting went off the rails. It was pretty irritating.

Still, it led me to a deeper read of the configuration and I ended up enjoying nano more after that. It's come a long way in recent years too.

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

#303

Post by giancarlostoro » Sun, Jan 01, 2023, 7:18 PM UTC

pjmlp wrote: post #228

giancarlostoro wrote: post #137

Earlier quoted context omitted.

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.

If Emacs ever does the headless UI thing I will crawl back to it, in all honesty. I like the idea of consistent editor key bindings across editors and consistently being able to reuse a powerful editor with any IDE.