4 ms·

> Opinionated, or just old and consistent? That old hotkeys didn't survive the evolution so it doesn't make sense to support them anymore.

tivert 3y ago
> That old hotkeys didn't survive the evolution so it doesn't make sense to support them anymore. No. It makes sense to support them if the userbase is familiar with them. Nothing is more annoying than having changes like that forced on you. Then there's the fact that the "GUI standards" conflict with other command-line standards in a pretty serious way. Every command shell on Windows I've ever used uses a different convention than the "GUI standard" for copy-paste for exactly that reason (e.g. Windows Command Prompt's "mark" stuff, PuTTY's select/middle-click behavior).
- GoblinSlayer 3y ago
  Won't such hardcore oldtimers use vi anyway? I thought the point of nano was to be like notepad.
  - cesarb 3y ago
    > I thought the point of nano was to be like notepad. No, the point of nano was to be like pico.
- codedokode 3y ago
  > userbase is familiar I think that every user who can use terminal, knows combinations like Ctrl + S (Save) or Ctrl + C (Copy). So they are familiar to them as well and should cause no problems. For me, for example, those combinations from vi, nano or emacs are simply weird and non-standard. And I assume that they are "non-standard" for everyone who was born after 1980 and have never seen a PDP or something from that era. Therefore it doen't make sense to support those key combinations only because 40 years ago they were used in PDP and other archaic systems.
  - tivert 3y ago
    > Therefore it doen't make sense to support those key combinations only because 40 years ago they were used in PDP and other archaic systems. OK, you write the memo about replacing Ctrl-C for SIGINT.
- MagicMoonlight 3y ago
  Lmao what userbase, you're talking about software from 40 years ago
  - Shared404 3y ago
    For nano? Every single Linux user who edits text on a cli amd hasn't bothered to learn vim.
  - nurettin 3y ago
    Every person who deployed code or edited configuration files without a graphical user interface knows about nano.
    - Kwpolska 3y ago
      How many of those people are attached to nano's key combos?
      - dotnet00 3y ago
        Probably a decent chunk of them, due to having them committed to muscle memory.
        lostmsu 3y ago
        As one of them I would guess less than 10% of users
stonetrw 3y ago
Yes, it's time inferior gui apps start freezing when you press C-z.
oso2k 3y ago
Correct. I’ve used pico & nano as my primary editors for 25+ years. A fun one to work around with nano in shellinabox browser tab is ctl+w (Where is/“Find” function in nano/pico, Close tab in Chrome/Firefox). nano let’s you remap it to ctl+f in nanorc at least.

tivert 3y ago

> That old hotkeys didn't survive the evolution so it doesn't make sense to support them anymore. No. It makes sense to support them if the userbase is familiar with them. Nothing is more annoying than having changes like that forced on you. Then there's the fact that the "GUI standards" conflict with other command-line standards in a pretty serious way. Every command shell on Windows I've ever used uses a different convention than the "GUI standard" for copy-paste for exactly that reason (e.g. Windows Command Prompt's "mark" stuff, PuTTY's select/middle-click behavior).

GoblinSlayer 3y ago
Won't such hardcore oldtimers use vi anyway? I thought the point of nano was to be like notepad.
- cesarb 3y ago
  > I thought the point of nano was to be like notepad. No, the point of nano was to be like pico.
codedokode 3y ago
> userbase is familiar I think that every user who can use terminal, knows combinations like Ctrl + S (Save) or Ctrl + C (Copy). So they are familiar to them as well and should cause no problems. For me, for example, those combinations from vi, nano or emacs are simply weird and non-standard. And I assume that they are "non-standard" for everyone who was born after 1980 and have never seen a PDP or something from that era. Therefore it doen't make sense to support those key combinations only because 40 years ago they were used in PDP and other archaic systems.
- tivert 3y ago
  > Therefore it doen't make sense to support those key combinations only because 40 years ago they were used in PDP and other archaic systems. OK, you write the memo about replacing Ctrl-C for SIGINT.
MagicMoonlight 3y ago
Lmao what userbase, you're talking about software from 40 years ago
- Shared404 3y ago
  For nano? Every single Linux user who edits text on a cli amd hasn't bothered to learn vim.
- nurettin 3y ago
  Every person who deployed code or edited configuration files without a graphical user interface knows about nano.
  - Kwpolska 3y ago
    How many of those people are attached to nano's key combos?
    - dotnet00 3y ago
      Probably a decent chunk of them, due to having them committed to muscle memory.
      - lostmsu 3y ago
        As one of them I would guess less than 10% of users

stonetrw 3y ago

Yes, it's time inferior gui apps start freezing when you press C-z.

oso2k 3y ago

Correct. I’ve used pico & nano as my primary editors for 25+ years. A fun one to work around with nano in shellinabox browser tab is ctl+w (Where is/“Find” function in nano/pico, Close tab in Chrome/Firefox). nano let’s you remap it to ctl+f in nanorc at least.