all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: John Wiegley <johnw@newartisans.com>
Cc: "Alfred M. Szmidt" <ams@gnu.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: amd@gnu.org: eshell and external commands
Date: Thu, 09 Aug 2007 11:58:00 -0400	[thread overview]
Message-ID: <873aysr987.fsf@stupidchicken.com> (raw)
In-Reply-To: <m2ejidmdk4.fsf@newartisans.com> (John Wiegley's message of "Thu\, 09 Aug 2007 00\:23\:23 -0600")

John Wiegley <johnw@newartisans.com> writes:

> Chong Yidong <cyd@stupidchicken.com> writes:
>
>> The following patch fixes this.  However, maybe it is too drastic
>> because it imposes the use of eshell-eval-command on *every* build-in
>> command.
>
> This is how Eshell used to behave.  It's is a bit drastic, because
> eshell-eval-command is much, much slower than plain eval.

I thought so at first, but after trying out, I don't notice any
observable slowdown for using eshell-eval-command for the eshell/*
lisp commands.

> I'm prefer to find a fix which preservers the faster behavior for all cases
> except those which break.

Another simple possibility is to make the code that falls back on
external commands perform eshell/wait on the external process, but
this has obvious drawbacks too.

I don't know how to hack the code to implement the deferment behavior
for "fallback to external programs" commands.  Do you have an idea how
to do it?

  reply	other threads:[~2007-08-09 15:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05  3:05 amd@gnu.org: eshell and external commands Richard Stallman
2007-08-08 22:55 ` Chong Yidong
2007-08-09  6:23   ` John Wiegley
2007-08-09 15:58     ` Chong Yidong [this message]
2007-08-09 18:44       ` John Wiegley
2007-08-09 19:03         ` Chong Yidong
2007-08-09 19:18           ` John Wiegley
2007-10-16 15:38             ` Chong Yidong
2007-10-17  1:09               ` John Wiegley
2007-10-17  2:08                 ` Chong Yidong

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=873aysr987.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=ams@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@newartisans.com \
    --cc=rms@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.