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@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    12
    ·
    7 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).

    • Chewy@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      ·
      7 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.

      • grue@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        4
        ·
        7 months ago

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

        • RavuAlHemio@lemmy.world
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          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.

          • Drew@sopuli.xyz
            link
            fedilink
            arrow-up
            4
            ·
            7 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