eshell - editing files

eshell - editing files

[Gary]

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? It kind of popped up because
if you do something with svn that requires editing something, I got
,----
| $ svn pe svn:ignore .
| emacs: Terminal type "dumb" is not powerful enough to run Emacs.
| It lacks the ability to position the cursor.
| If that is not the actual type of terminal you have,
| use the Bourne shell command `TERM=... export TERM' (C-shell:
| `setenv TERM ...') to specify the correct type.  It may be necessary
| to do `unset TERMINFO' (C-shell: `unsetenv TERMINFO') as well.
| svn: system('emacs svn-prop.tmp') returned 256
`----

Re: eshell - editing files

[Richard Riley]

Gary <help-gnu-emacs@garydjones.name> 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? It kind of popped up because
> if you do something with svn that requires editing something, I got
> ,----
> | $ svn pe svn:ignore .
> | emacs: Terminal type "dumb" is not powerful enough to run Emacs.
> | It lacks the ability to position the cursor.
> | If that is not the actual type of terminal you have,
> | use the Bourne shell command `TERM=... export TERM' (C-shell:
> | `setenv TERM ...') to specify the correct type.  It may be necessary
> | to do `unset TERMINFO' (C-shell: `unsetenv TERMINFO') as well.
> | svn: system('emacs svn-prop.tmp') returned 256
> `----
>

Set your EDITOR to use emacsclient.

The emacs wiki has more details.

http://www.emacswiki.org/emacs/EmacsClient#toc2

Re: eshell - editing files

[Pascal J. Bourguignon]

Gary <help-gnu-emacs@garydjones.name> 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? It kind of popped up because
> if you do something with svn that requires editing something, I got
> ,----
> | $ svn pe svn:ignore .
> | emacs: Terminal type "dumb" is not powerful enough to run Emacs.
> | It lacks the ability to position the cursor.
> | If that is not the actual type of terminal you have,
> | use the Bourne shell command `TERM=... export TERM' (C-shell:
> | `setenv TERM ...') to specify the correct type.  It may be necessary
> | to do `unset TERMINFO' (C-shell: `unsetenv TERMINFO') as well.
> | svn: system('emacs svn-prop.tmp') returned 256
> `----

Use emacsclient instead.

In your ~/.bashrc put:

export EDITOR=emacsclient
export VISUAL=$EDITOR


In your ~/.emacs put:

(server-start)


For eshell, I don't know how it takes its environment.  Perhaps it
just uses that of emacs, so you could also put in your ~/.emacs:

(require 'cl)
(setf (getenv "EDITOR") "emacsclient"
      (getenv "VISUAL") "emacsclient")


Then instead of typing:

    emacs foo
type:
    emacsclient foo

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/

Re: eshell - editing files

[Tim X]

Gary <help-gnu-emacs@garydjones.name> 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? It kind of popped up because
> if you do something with svn that requires editing something, I got
> ,----
> | $ svn pe svn:ignore .
> | emacs: Terminal type "dumb" is not powerful enough to run Emacs.
> | It lacks the ability to position the cursor.
> | If that is not the actual type of terminal you have,
> | use the Bourne shell command `TERM=... export TERM' (C-shell:
> | `setenv TERM ...') to specify the correct type.  It may be necessary
> | to do `unset TERMINFO' (C-shell: `unsetenv TERMINFO') as well.
> | svn: system('emacs svn-prop.tmp') returned 256
> `----
>
>

What you want to do is setup svn to use emacs as the editor via
emacscleint. You can either do this in svn config files or you can set
your shell EDITOR variable to emacsclient. 

tim

-- 
tcross (at) rapttech dot com dot au

Re: eshell - editing files

[Gary]

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? It kind of popped up because
>> if you do something with svn that requires editing something, I got
>> ,----
>> | $ svn pe svn:ignore .
>> | emacs: Terminal type "dumb" is not powerful enough to run Emacs.
..
> Set your EDITOR to use emacsclient.

It is, actually. Although I suspect it wasn't working correctly before
because of my confusion between EDITOR and my aliases. Now, however,
having set it explicitly to emacsclient:

,----
| /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 '.'
`----

Re: eshell - editing files

[Thierry Volpiatto]

Gary <help-gnu-emacs@garydjones.name> 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? It kind of popped up because
>>> if you do something with svn that requires editing something, I got
>>> ,----
>>> | $ svn pe svn:ignore .
>>> | emacs: Terminal type "dumb" is not powerful enough to run Emacs.
> ..
>> Set your EDITOR to use emacsclient.
>
> It is, actually. Although I suspect it wasn't working correctly before
> because of my confusion between EDITOR and my aliases. Now, however,
> having set it explicitly to emacsclient:
>
> ,----
> | /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?

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.

If so, use as EDITOR:(make a script maybe)

emacsclient -a "" "$@"
or
emacsclient -a "emacs -Q" "$@"

Be sure also you have an emacs server running.

-- 
Thierry Volpiatto
Gpg key: http://pgp.mit.edu/

Re: eshell - editing files

[Richard Riley]

Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:

> Gary <help-gnu-emacs@garydjones.name> 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? It kind of popped up because
>>>> if you do something with svn that requires editing something, I got
>>>> ,----
>>>> | $ svn pe svn:ignore .
>>>> | emacs: Terminal type "dumb" is not powerful enough to run Emacs.
>> ..
>>> Set your EDITOR to use emacsclient.
>>
>> It is, actually. Although I suspect it wasn't working correctly before
>> because of my confusion between EDITOR and my aliases. Now, however,
>> having set it explicitly to emacsclient:
>>
>> ,----
>> | /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?
>
> 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.
>
> If so, use as EDITOR:(make a script maybe)
>
> emacsclient -a "" "$@"
> or
> emacsclient -a "emacs -Q" "$@"
>
> Be sure also you have an emacs server running.

To simplify things, the whole point of the alternate-editor="" is that it starts the emacs
server for you.

I find it a lot easier to compartmentalise it all inside a script (edit
in the link above and simply set EDITOR to that script)

But yes, using -t would be wrong and isn't suggested in the linked
info. 

My edit command is currently set as 

,----
| #!/bin/bash
| # edit
| export GDK_NATIVE_WINDOWS=1
| exec emacsclient --alternate-editor="" "$@"
`----

Re: eshell - editing files

[Matt Lundin]

Gary <help-gnu-emacs@garydjones.name> 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? It kind of popped up because
> if you do something with svn that requires editing something, I got

I have the following line in my eshell-aliases-file:

alias emacs find-file $1

Best,
Matt

Re: eshell - editing files

[Gary]

Matt Lundin 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? It kind of popped up because
>> if you do something with svn that requires editing something, I got
>
> I have the following line in my eshell-aliases-file:
>
> alias emacs find-file $1

That's the kind of thing I was hoping to be able to do, because it
doesn't involve disturbing the ecosystem. Unfortunately, although I can
then happily do 'emacs foo', and get the file in a new buffer, svn, or
the environment variable, or something, doesn't play fair and still
tries to open a new emacs instance (or emacsclient, or whatever).

Re: eshell - editing files

[Gary]

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.

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.