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.

  • @grue
    link
    English
    -37 months ago

    So “some other bastard system” it is, then.

    That’s a shame; a GNU project should be consistently GNU-like (i.e. adopt Emacs key bindings).

      • @lemming741
        link
        English
        147 months ago

        There are now 15 standards

      • @grue
        link
        English
        07 months ago

        If Emacs keybindings are good enough to be the system default for Mac users, they should be good enough for anybody.

          • Drew
            link
            fedilink
            47 months ago

            Every text field in MacOs supports Emacs keybindings, like Ctrl-a to go to beginning, ctrl-k to delete to end of line, etc

        • @RavuAlHemio
          link
          0
          edit-2
          7 months ago

          Given that Mac keybindings for “common special functions” (Open/Save/Cut/Copy/Paste/Find/etc.) use Command instead of Ctrl, leaving Ctrl effectively unused unless in combination with Command, this argument doesn’t hold much water.

          Sure, some Emacs fan at Apple decided to add Emacs shortcuts to Cocoa controls, but that was a pretty arbitrary decision since people coming from Mac OS 9 didn’t use the Ctrl key, well, ever.

          • @[email protected]
            link
            fedilink
            17 months ago

            Books, periodicals, internet searches, practicing everything at home on a personal equipment until you’ve got it all mastered. If one can’t learn that way, take courses. The way the rest of us did it. Once you’ve got that, you have the ability to learn anything new coming… and can hit internet forums with well formed questions, complete with context. Staying on nano/pico, there is just no excuse if you’ve already been heavily using linux for 3 years or more. It’s an editor for those who are still in the beginning of the SELF learning phase. It should never be included in any distro’s default install except for school classroom centered distros. Just because something is easy to use doesn’t mean it’s installed as a standard everywhere. Folks learning this as their craft need to learn how to sit in front of any Linux or Unix and use standard tools to achieve what they need to do. That means learn your Vi. Learn your Posix shells like Ksh, Bash, Zsh, Dash, not the nano of shells, fish! Learn your Python, your Perl. Learn your SysV ‘isms in addition to your SystemD. Learn your csh (tcsh will do). Learn your terminal control codes. Learn your SysRq funtions. Learn your tmux, your gnu screen. Learn with and keep handy your books for awk, sed, patterns, perl. Learn your mkfs’, the different filesystems and their benefits, their options and tools, how to resize. Learn your MD raid. Learn your LVM. Learn various encrypt at rest options. Learn containers. Study and remember the differences between gnu, bsd, and sysv tools like tar, cpio, find, and even ps. Books books books! Practice practice practice! Study study study!

            And when you got that done, look up and see what you’ve missed while you were doing all that, and start in on all that new stuff. Wash, Rinse, Repeat. Never stop reading, studying, practicing, learning.

            That’s how. Oh, and delete nano!!!

            • ElectricMachman
              link
              fedilink
              English
              17 months ago

              My point was that you can’t be an advanced user without first being a non-advanced user

              (and side note, I’ve been using Linux for over 20 years on and off… still use Nano)

    • Chewy
      link
      fedilink
      17 months ago

      I like all editors to have as many diverse sets of keybindings as possible. Sadly most apps don’t, which is a main reason why I never bothered to properly learn emacs bindings, as I wouldn’t be able to use them anywhere else.