I almost feel like this a somewhat pointless feature. It’s almost easier to just learn the default ones as opposed to adding “-modernbindings” or creating an “enano” variant/copy.
That’s your opinion.
I like updating it to modern conventions. One day they become default and on another day you get rid of the old ones. The people of the future don’t have to learn two sets of keybindings.
It’s definitely just my opinion. Honestly did not mean to imply otherwise.
I would almost prefer them to just switch to the new keybindings by default in version 8.0.
It’s definitely just my opinion. Honestly did not mean to imply otherwise.
For my opinion I usually create a comment below my post to seperate my opinion and the post itself.
On-topic: I do believe it’s useful to have this switch and there’s nothing stopping distros to change their default. Completely replacing the default keybindings might be surprising to long time users, but I also believe it should be done at some point. For the meantime this switch can be simply added as an alias.
Fair point. I guess this was more of a casual post, so I didn’t think too much about it.
I would have preferred if they switched to new keyboard model in version 8.x by default.
I am a relatively light Linux user. Raspberry Pi headless via DietPi/Debian for NAS/Media server/torrents/PiHole and some experiments with self hosted services on major cloud services. I prefer to stick to defaults whenever possible.
I prefer to stick to defaults whenever possible.
Same goes for me.
E.g. changing vim keybindings on my local system to better suit my non-QWERTY keyboard would be annoying since they don’t transfer to remote systems. That’s a reason I like fish, because it’s defaults are modern and useable, compared to zsh/bash which benefits strongly from plugins.
creating an “enano” variant/copy
What’s wrong with that?
Providing optional alternative keybindings for people who know a set of bindings from other tools makes lot of sense. I always appreciate that some tools provide these. This shows that the devs think about newcomers who are used to other set of bindings. It’s optional.
BTW the blog post you posted has only 4 sentences (excluding the quote). I often dislike articles that short, but on the other hand, at least its not blown up with crap. So there is that.
My issue is that the only time I use vim or nano it’s because I’m logged into some server where you’re going to be stuck with the defaults anyway. I guess it’s nice on your home machine, but customising a bunch of servers with your personal preferences isn’t really something you can do in most work situations.
Yes, that’s why I still need to learn how vi and vim in their default config work (in fact I started like that, so I know already). I wanted to get into finding as solution to this problem. Years ago I read in Reddit someone setup a keyboard macro (outside of Vim) to execute bunch of commands to setup the environment in the live session, while in Vim. At least some of the configuration can be used like that.
Otherwise, yeah this really sucks. That is not a unique problem to editors, but any software that you run with a customized local setup and with bare naked server version. If you often switch back and forth, it makes sense to just use one set of keybindings. That also is the point: For people using other tools, it makes sense to provide these alternative keybindings, so they don’t need to relearn the nano specific setup.
Edit: Too many Buts reduced.
I’m pretty sure enano means dwarf in Spanish. Not that it’s an issue.