From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: eshell - editing files
Date: Tue, 22 Jun 2010 13:15:08 +0200 [thread overview]
Message-ID: <8739wfz5c3.fsf@tux.homenetwork> (raw)
In-Reply-To: hvq4op$vnt$1@dough.gmane.org
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/
next prev parent reply other threads:[~2010-06-22 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 8:52 eshell - editing files Gary
2010-06-22 9:17 ` Richard Riley
2010-06-22 10:54 ` Gary
2010-06-22 11:15 ` Thierry Volpiatto [this message]
2010-06-22 11:31 ` Richard Riley
2010-06-22 15:44 ` Gary
2010-06-22 15:54 ` Richard Riley
2010-06-22 13:03 ` Matt Lundin
2010-06-22 15:21 ` Gary
[not found] <mailman.6.1277197523.11696.help-gnu-emacs@gnu.org>
2010-06-22 9:21 ` Pascal J. Bourguignon
2010-06-22 10:10 ` Tim X
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8739wfz5c3.fsf@tux.homenetwork \
--to=thierry.volpiatto@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).