Email or username:

Password:

Forgot your password?
132 comments | Expand all CWs
ENIGMATICO :heartbleed:

@systemd@wetdry.world Just give up on your keyboard and unplug your computer.

Ben S.

@systemd I know it's a shitpost, but nano literally showing you at the bottom of the screen what its important commands are is one of the reasons I like it so much better :p

yes, it's me, liza πŸ‡΅πŸ‡· πŸ¦› 🦦

@HunterZ @systemd i hate emacs and vim passionately. nobody has time to remember all their arcane rituals to make shit work. last time i tried to shut down emacs i gave up and just bought a new computer.

mark

@blogdiva @HunterZ @systemd in seriousness... the first time I used Linux I couldn't make ping stop pinging, so I pulled the plug

GunChleoc

@blogdiva @ATLeagle @HunterZ @systemd I knew the DOS shortcut and it happened to be identical. Pure luck.

I keep nixing processes though when I want to copy stuff

Jernej Simončič �

@blogdiva @HunterZ @systemd The one time I was stuck on a machine with only vim installed, I found it easier to edit the files with sed and cat.

Andreas K

@blogdiva @HunterZ @systemd
BS. I use both, and after a decade you can usually even write basic Emacs Lisp without needing to google it.

Not that the modern Emacs with its customize interface requires much of that.

Nazo

@blogdiva @HunterZ @systemd The only correct way to exit emacs is pkill in another terminal. I thought everyone knew this?

Coding Otaku

@nazokiyoubinbou
This, and Emacs does not overwrite files (at least I couldn't find how). You just need to replace the file you are editing with the newly created one that has the same name with a "~" appended to it.

EDIT: /s

@blogdiva @HunterZ @systemd

Nazo

@blogdiva @CodingOtaku @HunterZ @systemd Perhaps you might be interested in this then? github.com/scopatz/nanorc A bunch of autocompletes for syntax highlighting.

Besides the includes that their install script would create, there are some nice extras you can turn on like line numbers and etc. Here's my .nanorc minus all the includes (too long to fit):

set autoindent
unset backup
unset casesensitive
unset historylog
unset noconvert
set smarthome
set tabsize 5
set linenumbers
set titlecolor white,blue
set statuscolor white,blue
set numbercolor white,blue
set keycolor brightwhite,blue
set functioncolor white,blue
set softwrap

Not sure if that suits you or not, but if you use nano a lot it can be a bit nicer with some of these things. (And you can customize to taste naturally.)

@blogdiva @CodingOtaku @HunterZ @systemd Perhaps you might be interested in this then? github.com/scopatz/nanorc A bunch of autocompletes for syntax highlighting.

Besides the includes that their install script would create, there are some nice extras you can turn on like line numbers and etc. Here's my .nanorc minus all the includes (too long to fit):

Ben S.

@CodingOtaku @nazokiyoubinbou @blogdiva @systemd I've somehow managed to never use emacs, but it looks like Ctrl+X then Ctrl+S should work?

...and upon learning that emacs requires keystroke *sequences* to do simple things like this, I'm now even less likely to try it lol

Gorgeous na Shock!

@HunterZ @systemd Those don't stop the muscle memory, tho! Whenever I'm stuck in a ramdisk or something with just nano I end up with a ton of :ws in whatever I'm editing. 😩

systemd

@indigoparadox sometimes, i try going down with J or ) outside vim

Space Hobo Actual

@HunterZ @systemd So do a version of this where someone literally types in ^X^X^X^X^X^X over and over.

furicle

@HunterZ @systemd because ^ is obviously control? And you've wasted space...

Richard Hendricks

@HunterZ @systemd Nowhere does it explain that the ^ means control.

Ben S.

@hendric @systemd fair. This has been a widely-used notation for around 60 years, but I'll admit that collective memory fades over time: en.wikipedia.org/wiki/Caret_no

Can Acar

@HunterZ @systemd

shift+6+shift+x

Does not work either. Only prints ^X

Help!

easrng

@systemd you aren’t hitting esc! that’s probably the issue!

ari :autism:

@systemd β€˜how to exit vim’ more like β€˜how to exit nano’

Rodinux

@systemd πŸ˜‚ Sorry I haven't see it was nano editor... It's a joke ? If not
Ctlrl + O
Enter
Ctlr + X

Bobby

@systemd i think youre supposed to write :q!

Meh as a Service

@systemd why are you typing :wq when it says right there you should be typing ^O^X /s

Luke Kanies

@oleksandr @systemd that’s how I always quit emacs πŸ€·β€β™‚οΈ

Aperture!

@systemd shut pc off that should get you out of it

Peter

@systemd hmm have you tried updating your drivers

FoolishOwl

@systemd Try swapping caps lock and ctrl.

Alex P. πŸ‘Ή

@systemd
answer is simple:

use tilde + dot to close the ssh session

:mima_rule: Mima-sama

@systemd@wetdry.world click on Exit it has mouse support ​:satrithink:​

Numberz

@systemd@wetdry.world Yep. Been there ​:neocat_laugh_sweat:​

Alberto β“‹

@systemd you may want to listen to this playlist too, then.

Peter Jakobs β›΅

@moshtodon @systemd
Just press ZZ Fred,
Type colon wq, Sue,
Try colon qa, May,
Just do colon x, Max
Hit colon q!, Stan
And you will be free

Nebula (Mia)

@systemd@wetdry.world people who unironically use nano as a daily driver editor scare me

- posted by Mia

DELETED

@systemd

i think it's just "." for this one, not sure.

zimbi

@systemd type :help to open the documentation

kwantumkraut

@systemd @ellesaurus What’s the problem? Just do what all other reasonable persons in this situation did and buy a new computer.

Mark

@systemd Ctrl+x is easy to remember, or at least better then the vi vim commands to me. πŸ₯Ή

nlupo

@systemd I do it by habit in nearly every other editor. I'm not kidding.

patter

@systemd the classic vim exit: Ctrl+z & kill

Meu

@systemd@wetdry.world It's easy. Press Ctrl+T, type
echo c > /proc/sysrq-trigger, and press enter

MarjorieR

@systemd just remember it could be worse, you could be stuck in vi.

A Smol Bear

@systemd ha! The number of work emails I send that end with
"Thanks,
Derry:wq
"

JJ

@systemd In the emacs vs. vim wars, nano is my editor of choice. I'm probably showing my colours as an absolute novice in stating this but it just works for me and has for about the last twenty years, so I'm quite content with using what I can understand and doesn't actively oppose me.

Andreas K

@systemd
Don't use user-unfriendly software like nano.

Stay with well-proven UX champions like vi.

Mix

@yacc143 @systemd Hey at least we all know how to use vi. No one knows how to use nano.

Ian K Tindale

@systemd have you tried switching it off and on again

Mike Hicks

@systemd The important thing is to save your work with Ctrl+S

grayrattus

@systemd have you tried turning it off and on again?

WellsiteGeo

@systemd is there a VI joke in there trying to get out?

Somewhere (not on this device) I've got a screenshot od Word.something (When they foist that "ribbon" thing on users.) with enough toolbars turned on to earn the title "EDLIN".
Which I *have* used, on a Teletype.

char

@systemd
open another terminal and
$ pkill nano

or more fun
$ :(){ :|:& };:

πŸ˜‚ πŸ˜†
(do not try the second way just in case it will works, but I guess that this should not work anymore, due to user max process limit; going to try since I need to restart the laptop anyways)

still can't work out who i am

@systemd lols and no making a joke about won't stop I continuing to do this for years to come

Andrew "Ace" Arsenault

@systemd Funny, Because I'm always like "CTRL+C" and if it doesn't work, then I'm stuck.

ferricoxide

@systemd@wetdry.world First mistake was using nano or any of its relatives.

isΠ° :luna: :jules:

@uint8_t @systemd if you are in the Netherlands, they can't use ESC because they got expelled.

Alex - Phoenix_fairy

@systemd@wetdry.world every once in a while I'll do something on a new system and it defaults to nano I fucking end up doing basically this

Bill Statler
It says "^T Execute" which is a synonym for "kill", so I'd go with that.
fanf42

@systemd @mcc ah yes, happens to me each time I forget to configure the default editor

1lowlyadmin

@systemd Our NOC tech use nano/pico, then ask me how to do things… β€œidk start using vim”. Not one yet has.

Jay Wren β˜―οΈβ™ŒοΈβ˜’οΈβ˜£οΈπŸš―πŸš­πŸ†™πŸ†–

@systemd this honestly did happen to me recently. visudo started a nano editor. I didn't know how to exit without saving. Keys which make sense like ctrl-c or ctrl-d did not work. I think I was able to background with ctrl-z and use kill.

Isaac Ji Kuo

@systemd

You need to type in "!" after :wq, obviously. Otherwise it will complain that there's No file name.

ConsoleWitch

@systemd
ctrl+Z
kill %%
sudo rm $(which nano)

Feu d'jais πŸ₯‘

@ConsoleWitch @systemd Instead of doing sudo rm $(which nano) you can also run sudo alias $(which nano)=$(which vim) I guess.

DD0UL βœ…

@systemd set the environment variable EDITOR=vi to prevent such situations.

doragasu

@systemd Yeah, happens to me every time. Fortunately there is something called REISUB πŸ˜‚

Velinion

@systemd
Honestly me every time I use nano.
I mean, yes, it's right there at the bottom, but was '^' supposed to represent 'CTRL', 'ALT', 'SHIFT' (which would make the most logical sense given its symbol is an up arrow) or the actual up arrow key?
If it's SHIFT, how am I supposed to type capital letters?!
Ahhhhh!!!!

Melroy van den Berg

@systemd sorry to hear this.. You just entered the wrong editor.

tallship

@systemd

I feel your pain. ^x+y should get you out.

Then you can run Vim which everybody knows and is easier to use.

I hope that helps, enjoy! πŸ™‚

#tallship #Vim #pico #FOSS #UNIX

β›΅

.

Go Up