You're viewing a single thread.
I always get annoyed when I'm on some system and nano pops up and I need to figure out how to kill that thing.
Nano literally tells you all the shortcuts to your face.
It shows a message which wastes valuable screen estate, especially on low resolution terminals, containing a message I have to read every single time because the keys are not in muscle memory, and never will because the bindings are stupid.
On systems I have control over the reaction to nano popping up is exiting, removing it, making sure the package system blocks reinstallation attempts, and go back to what I was initially doing in a sane editor.
My man, most of us aren't connecting to our mainframes on VT20s these days. Even on my phone screen the three extra lines nano takes over vi aren't a problem.
Also if you have the time to go through all that you have the time to learn ctrl+x.
Sometimes I'm on call and all I have is my 3DS! Stop assuming by maximum screen resolution :'(
I know you kid but even the 3ds fits a decent number of lines on screen.
You have so much pent up emotion over a text editor. Life can be so much more my friend!
First day on linux?
You know the bell curve meme? I'm just beyond this.
Same. As a vim user I now can't quit nano.
Very intuitive - Ctrl + X... unlike vim.
Why is Ctrl-X intuitive? Shouldn't it be Ctrl-Q (for "quit")?
CTRL+eXit
In most apps, Ctrl-X means "cut", not "quit". Especially when it's a freakin' text editor!
I will grant you that it's more intuitive than vi, but that is a very, very low bar.
Ctrl-X in Nano is arguably more nonsensical, considering that vi was made in an era long (decades) before many of the conventions we know today came about. They were figuring it out in real time. And the criterium here is much simpler: it must be available on all keyboards so no fancy keys. That's all.
On the other hand, when nano decided to use Ctrl+X for eXit, Apples Ctrl+X/C/V had already been brought over to Windows and Apple, and was also the de facto way for most Linux apps to handle these inputs although I do think it came before any "official" efforts to standardize these shortcuts in desktop environments.
It doesn't have to be X, just the fact that it uses modifier keys is enough. It could be Q or anything else, just please, for the love of god, we live in the 21st century now, all keyboards have modifier keys, please, add modifier keys shortcuts as well.
And it's also an X, like any GUI app in any OS.
I know I always try GUI methods in console
That's normal for people that didn't grow up in the 70s and 80s and GUI wasn't the first thing they knew. I was a teen in the late 90s and early 00s, so yeah, we had GUIs for almost everything.
We're basically trying to do catchup with the cool kids, but let's face it, they live somewhat in the past regarding modifier keys and vi/vim.
Because it also sends the kill signal in every terminal I've witnessed yet... And you have it right on screen the second you start Nano.
I'm over here using Ctrl c all over the place to kill stuff...
Yeah, you could use that as well.
Can you please elaborate on the first part? It is not standard Linux terminal behavior to send the KILL signal on Ctrl+X.
Actually, you are right. I will stand by my point that Nano tells you what to press, but I wonder where I got the stuff about Ctrl+X... I am very positive that I have used it at some point (outside of Nano), but maybe my brain is playing tricks on me 🤔
Because nano just shows how to exit, as well as some other basic functions at bottom
gg/un2x?-d/like
FTFY
I'm not planning on googling that 😒.
result: Very intuitive like vim.
gg- top of the file/un- find “un” place cursor at u2x- remove 2 characters?-- search backwards for the character-d/like- delete everything up until the characterslike
See, intuitive!
I don't do that much search and replace in any terminal based text editor to actually use that on a regular basis. If I need edits like that, I use a GUI text editor.
Sure, I just hate moving from mouse to keyboard every few seconds as I code.
Why not just using Micro? Ctrl + Q. Intuitive af
Yeah, sure, that works as well.
As long as I get to use modifier keys, almost anything is fine with me. We don't live in the 70s, that was 50 years ago. If backwards compatibility is what they're after, I'm sorry but I think they overdid it. Plus, you can just add them, the defaults don't need to be changed.