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: Tue, 16 Oct 2007 11:38:31 -0400	[thread overview]
Message-ID: <871wbvm5mw.fsf@stupidchicken.com> (raw)
In-Reply-To: <m2tzr8ldoq.fsf@newartisans.com> (John Wiegley's message of "Thu\, 09 Aug 2007 13\:18\:13 -0600")

John Wiegley <johnw@newartisans.com> writes:

> Chong Yidong <cyd@stupidchicken.com> writes:
>
>> This code would need to prevent the eshell prompt from being emitted until
>> the external process is complete, like how the 'eshell-defer mechanism works
>> in eshell-resume-eval for "normal" external commands.  However, I don't know
>> eshell well enough to make this work.  I tried adding the return value of
>> eshell-external-command to eshell-last-async-proc but that doesn't work for
>> some reason.  Do you know what needs to be done to make it work?
>
> Ok, I have to give this some serious thought, which I cannot do just now
> because I'm about to move to Grenada.  After a week or so has gone by and I've
> settled in, then I can focus enough to find the right answer.

Hi John,

Any further thoughts on this problem?

  reply	other threads:[~2007-10-16 15:38 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
2007-08-09 19:03         ` Chong Yidong
2007-08-09 19:18           ` John Wiegley
2007-10-16 15:38             ` Chong Yidong [this message]
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=871wbvm5mw.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.