Re: eshell - editing files

[Richard Riley]

Gary <help-gnu-emacs@garydjones.name> writes:

> Thierry Volpiatto writes:
>> Gary writes:
>>> Richard Riley writes:
>>>> Gary writes:
>>>>> This may sound like a weird question. Is there any way to configure
>>>>> eshell so that when I want to edit a file, e.g. by typing "emacs foo", I
>>>>> instead get a new buffer with the file in?
> ...
>>> ,----
>>> | /home/jg/work/drivers/lib/Src $ env | grep "EDITOR"
>>> | EDITOR=emacsclient -t --alternate-editor=""
>>> |
>>> | /home/jg/work/drivers/lib/Src $ svn pe svn:ignore .
>>> | *ERROR*: Terminal type "dumb" is not powerful enough to run Emacs
>>> | No changes to property 'svn:ignore' on '.'
>>> `----
>>
>> Are you running these commands from inside emacs? eshell? where?
>
> Yes, inside eshell, which is inside an emacsclient/server pair.
>
>> If yes, because your EDITOR is bind to emacsclient -t, it try to open an
>> emacsclient inside the emacs terminal (eshell or something else) and it
>> fail because terminal is not powerful enough to run emacs.
>
> Aha! Yes. Adding
>
> (eshell/export "EDITOR=emacsclient")
>
> to ~/.eshell/login makes everything work :) Yippee!
>
> Thanks, all.
>

If you follow the advice elsewhere in the thread and bind it to an edit
script and use the --alternate-editor="" in the script you wont have to
worry about starting the daemon yourself - emacsclient will do it for
you. 

The benefit is then that other apps can use EDITOR too without knowing
anything about emacs.