all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Wiegley <johnw@newartisans.com>
To: Chong Yidong <cyd@stupidchicken.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 12:44:56 -0600	[thread overview]
Message-ID: <m23aysmtsn.fsf@newartisans.com> (raw)
In-Reply-To: <873aysr987.fsf@stupidchicken.com> (Chong Yidong's message of "Thu\, 09 Aug 2007 11\:58\:00 -0400")

Chong Yidong <cyd@stupidchicken.com> writes:

> 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.

This is likely due to the speed of your machine.  When I was using my old
Pentium III laptop, the slowdown was so exaggerated that I finally sought the
cause -- which resulted in this fix.

> 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?

You know, something you could do is to traverse the Lisp tree at the point of
decision looking for the symbol `eshell-external-command'.  If it's found, use
eshell-eval-command rather than eval.  That way, the slowdown is only suffered
for external commands, which are going to be slow anyway because of the
necessary invocation of an external process.

John

  reply	other threads:[~2007-08-09 18:44 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
2007-08-09 18:44       ` John Wiegley [this message]
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=m23aysmtsn.fsf@newartisans.com \
    --to=johnw@newartisans.com \
    --cc=ams@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --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.