Default Command Line Editor?
 

So I was installing a version of cron on my n800 (os2007), and it suggested to run crontab -e to setup after cron was installed. But then I didn't recognise the editor that opened up and couldn't figure out how to use it (most of the old-style CLI editors require ESC key, which I don't see on osso-xterm...). I fell back on putting cron jobs into a temp file and "installing" that using crontab, but I'm still curious about which editor opens as the os2007 default. Anyone know?

Re: Default Command Line Editor?
 

You can control this behaviour by setting the EDITOR shell variable. Setting it to something like (for ash)
export EDITOR=vi

should set you up for vi (if that is what you wanted).

I hope this helps,

Craig...

Re: Default Command Line Editor?
 

OK, but even vi requires the use of the Esc key, right? I don't use the command line editor enough to remember the commands, so I tend to stick to nano, which doesn't need me to remember anything! (And yes I know that real geeks only use vi or emacs...)

Of course, if I'd thought of it I could have used the 'export EDITOR' approach to set nano as the default (yes, I had it on there).

Ultimately, I'm just curious as to what editor the n800 does default to... and can you generate 'Esc' from osso-xterm?

Re: Default Command Line Editor?
 

Esc is the "back" hardware key on the N800, probably the same for N810.

I don't like vi, and I don't like emacs. I consider myself a real geek, and I use JOE. Wordstar-based key-binds FTW!

Re: Default Command Line Editor?
 

Have you tried using the hardware Escape button, above the Menu button on the N800?

Re: Default Command Line Editor?
 

There is also "leafpad", a simple editor with GUI, startable from the command line.

Re: Default Command Line Editor?
 

i like PyGtkEditor on OS2008.

Re: Default Command Line Editor?
 

Leafpad isn't very helpful IMHO; it only accesses files within MyDocs from the file selector. You could use it from command line, but why endure such hassle? Install a real text-editor, use it with the flying-keyboard xterm, and be happy.

Re: Default Command Line Editor?
 

Unfortunately I was in clueless n00b mode and didn't think of that! :D

Oh well... <smacks forehead>

Re: Default Command Line Editor?
 

I'm with you on this. I had already stuck nano on there as my favorite 'real' editor, since I don't need to use a command line editor often enough to remember the command keystrokes for vi or joe. I hadn't noticed the 'flying keyboard' xterm though; looks like it might be easier to use, so I'll check it out. Thanks!

Re: Default Command Line Editor?
 

I use JOE on my desktop for practically all editing, so for me keystrokes are no trouble, but I'm not sure why nano's would be easier to remember? I understand vi being harder, but JOE is also modeless, and has online help (displays in top ~7 lines without disruption to editing).
Oh, well, not to start editor flamewars, and any of them will edit text, so go with what ya know!

Re: Default Command Line Editor?
 

nano has its most common commands listed on the bottom two lines in a ncurses type interface. So for simple editing you don't have to remember ANY keystrokes at all. That makes it easier (for me anyway) :D But, as you said, everyone has their favorite, and if it gets the job done then that's the best for you!