You are not logged in.
Hello everyone!
So the problem is that i've accidentally selected vi as my configuration files editor and now i don't see a way to select nano again. How can i use nano again?
Offline
What wm or de are you using? Hard to help without more info.
Time is a great teacher, but unfortunately it kills all its pupils ... - Louis Hector Berlioz
Offline
Oh damn, forgot!
Have no idea what you just said (ya, me be n00b), but here's something: the release is 2009.02 and it's Core. I'm installing it on VirtualBox.
Offline
During the install selecting an editor only is for the install, you can probably go back to the original choice and choose it again.
Setting Up a Scripting Environment | Proud donor to wikipedia - link
Offline
It should be in your .bashrc file. EDITOR=nano should do it.
Offline
In the installer, as far as I can remember you should finish editting all your files and then repeat that stage of the install again, but then select nano as your editor.
edit: The command to save and exit in vi is ":wq" and then press [enter].
Last edited by dyscoria (2009-03-27 19:34:02)
flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)
Offline
Yeah, i did that, but when i repeat the step, it doesn't give me the menu to choose the editor
EDIT: Oh, well, never mind, i'll go restart the installation.
Last edited by HappyD (2009-03-27 19:46:51)
Offline
...or you could just use Vi
Learning it 'for reals' takes a while, but all you need to know to use it like a less awesome editor is arrow keys to move cursor, 'i' to go to insert mode to type stuff, 'esc' to go back to command mode, and ':x' in command mode to save and quit -- ':q!' in command mode to quit without saving.
Offline
Once $EDITOR is set, it will keep using it and not ask again.
You could background the installer, export EDITOR=nano and forground it again. Or just restart it.
I'm pretty sure we don't put it in a .bash*
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
Dieter@be
Once $EDITOR is set, it will keep using it and not ask again.
You could background the installer, export EDITOR=nano and forground it again. Or just restart it.
I'm pretty sure we don't put it in a .bash*
I'm probably doing something wrong again but if I don't have export EDITOR=nano in my .bashrc, mc always uses vi for the editor--I turned off the internal edIt option. Works for me.
Time is a great teacher, but unfortunately it kills all its pupils ... - Louis Hector Berlioz
Offline
Thanks people, but i've already restarted the installation and finished it, right now i'm configuring my system. I'm at the X installation.
Offline