From: Sebastian Tennant <sebyte@smolny.plus.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Asynchronous commands with eshell-command
Date: Tue, 27 Jan 2009 16:09:02 +0000 [thread overview]
Message-ID: <hc3k91ep.fsf@vps203.linuxvps.org> (raw)
In-Reply-To: vs7ocxtzwkl.fsf@pax07e3.mipool.uni-jena.de
Quoth Michael Heerdegen <michaelh@minet.uni-jena.de>:
> Does anybody know how to start external commands asynchronously with
> `eshell-command'? I tried `xterm &' for example, which works but also
> raises an error.
>
> The source code seems to support the asynchronous case, but I don't
> know what to type.
Where's Thierry Volpiatto when you need him :)
Sebastian
--
Emacs' AlsaPlayer - Music Without Jolts
Lightweight, full-featured and mindful of your idyllic happiness.
http://home.gna.org/eap
next prev parent reply other threads:[~2009-01-27 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 19:39 Asynchronous commands with eshell-command Michael Heerdegen
2009-01-27 16:09 ` Sebastian Tennant [this message]
2009-01-27 16:40 ` Thierry Volpiatto
2009-01-27 18:55 ` Sebastian Tennant
2009-01-27 19:51 ` Thierry Volpiatto
-- strict thread matches above, loose matches on Subject: below --
2009-01-27 11:49 Nurullah Akkaya
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=hc3k91ep.fsf@vps203.linuxvps.org \
--to=sebyte@smolny.plus.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).