3 ms·
Right after the nano maintainer got bullied out by the FSF, I noticed two bindings got their defaults changed. They never change. I almost feel like it was gr
by positron26 11mo ago
Right after the nano maintainer got bullied out by the FSF, I noticed two bindings got their defaults changed. They never change. I almost feel like it was graffiti, a flex against the old maintainer, a retribution for not doing whatever the FSF wanted.
Since forever, GNU readline programs and nano had identical bindings. I'm fast moving around the CLI because I'm fast at nano. Emacs has the same defaults. What sane organization only abandons their own defaults and prioritizes that work after pushing the existing maintainer out (or irritating them enough to accomplish this)?
- kstrauser 11mo agoWhich bindings changed?
- positron26 11mo agobind ^F forward main bind ^B back main bind M-f nextword main bind M-b prevword main
- kstrauser 11mo agoWhat did the maintainer change them to instead? (Because tone doesn't always come across, I'm asking out of curiosity, not to like challenge you about it.)
- forgotpwd16 11mo agoSeems GP got somewhere confused as well. From `man nano`: Since version 8.0, to be newcomer friendly, ^F starts a forward search, ^B starts a backward search, M-F searches the next occurrence forward, and M-B searches the next occurrence backward. If you want those keystrokes to do what they did before version 8.0, add the fol‐ lowing lines at the end of your nanorc file: bind ^F forward main bind ^B back main bind M-F formatter main bind M-B linter main M-F/B have not defaulted to nextword/prevword, or at least haven't within the last 10y since have those binds in the earliest version of nanorc in my .config git repo.
- positron26 11mo agoYour 10y estimate must be wrong since my nanorc only acquired these things after the nano maintainer was bullied out.