From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: "Johan Lindström" <johanl@DarSerMan.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Async shell-command-to-string?
Date: Mon, 02 Jun 2008 01:11:03 +0200 [thread overview]
Message-ID: <48432C87.30906@gmail.com> (raw)
In-Reply-To: <E1K2wQC-0003ay-DH@lists.gnu.org>
Johan Lindström wrote:
> Hi all!
>
> I'd like to run something similar to shell-command-to-string, but that
> runs "asynchronously" in a "subprocess" in the "background". I've
> searched for all those things without finding anything suitable.
>
> async-shell-command-to-string or whatever it would be called would take
> a callback for the string output when the subprocess is done.
>
> Is there anything like that already?
>
> If not, any hints on how to implement it? The async part of
> shell-command looks promising to nick.
Look in the Emacs manual:
(info "(elisp) Processes")
next prev parent reply other threads:[~2008-06-01 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 22:53 Async shell-command-to-string? Johan Lindström
2008-06-01 23:11 ` Lennart Borgman (gmail) [this message]
2008-06-03 0:47 ` Johan Lindström
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=48432C87.30906@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=johanl@DarSerMan.com \
/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).