Fast question abount EDITOR

2012-04-05 Thread Andrea Venturoli
Hello. This might be a stupid question... however... %setenv EDITOR emacs -nw setenv: Too many arguments. %setenv EDITOR emacs -nw %crontab -e crontab: emacs -nw: No such file or directory crontab: emacs -nw exited with status 1 Is there a way I can easily achieve the above? Do I really

Re: Fast question abount EDITOR

2012-04-05 Thread Polytropon
On Thu, 05 Apr 2012 08:57:55 +0200, Andrea Venturoli wrote: Hello. This might be a stupid question... however... %setenv EDITOR emacs -nw setenv: Too many arguments. %setenv EDITOR emacs -nw %crontab -e crontab: emacs -nw: No such file or directory crontab: emacs -nw exited with

Re: Fast question abount EDITOR

2012-04-05 Thread Robert Bonomi
Andrea Venturoli wrote: Hello. This might be a stupid question... however... %setenv EDITOR emacs -nw setenv: Too many arguments. %setenv EDITOR emacs -nw %crontab -e crontab: emacs -nw: No such file or directory crontab: emacs -nw exited with status 1 Is there a way I can easily

Re: Fast question abount EDITOR

2012-04-05 Thread John Levine
Do I really need a script which in turns call emacs -nw? Authoritative answer: 'maybe'. grin There may be an alternative to the obvious one line shell script, but that's what one line shell scripts are for. One of the strengths of Unix is that its design encourages people to solve problems by