From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Pankaj Jangid <pankaj@codeisgreat.org>
Cc: "Adam Sjøgren" <asjo@koldfront.dk>, ding@gnus.org
Subject: Re: Does Gnus automatically run 'notmuch new' if configured?
Date: Fri, 25 Sep 2020 09:31:40 -0700 [thread overview]
Message-ID: <873635akcz.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m2r1qpc3vc.fsf@codeisgreat.org> (Pankaj Jangid's message of "Fri, 25 Sep 2020 20:14:55 +0530")
Pankaj Jangid <pankaj@codeisgreat.org> writes:
[...]
> Now that I have put a lambda function to invoke `async-shell-command`,
> it opens up *Async Shell Command* buffer in another window whenever I
> press `g`. I want the messages in *Async Shell Command* buffer. But I
> don't want it to open up on every call to `gnus-group-get-new-news`.
Ahem, I may have led you astray with `async-shell-command', which is
mostly meant to be called interactively -- in which case you usually
want to see the output. In lisp code that runs in the background, you're
better off using `start-process', where you can tell it not to keep the
output:
(start-process "unnecessary label" nil "/path/to/notmuch" '("new"))
This returns a process object that you're supposed to continue
interacting with, but in your case you can just disregard it.
Sorry about that! Wasn't thinking clearly.
Eric
next prev parent reply other threads:[~2020-09-25 16:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 8:32 Pankaj Jangid
2020-09-24 16:42 ` Eric Abrahamsen
2020-09-24 17:55 ` Adam Sjøgren
2020-09-25 4:00 ` Pankaj Jangid
2020-09-25 6:05 ` Eric Abrahamsen
2020-09-25 7:51 ` Pankaj Jangid
2020-09-25 8:09 ` Eric S Fraga
2020-09-25 9:31 ` Adam Sjøgren
2020-09-25 14:44 ` Pankaj Jangid
2020-09-25 16:31 ` Eric Abrahamsen [this message]
2020-09-25 17:47 ` Pankaj Jangid
2020-09-25 18:16 ` Adam Sjøgren
2020-09-25 18:45 ` Eric Abrahamsen
2020-09-25 18:52 ` Adam Sjøgren
2020-09-26 1:29 ` Pankaj Jangid
2020-09-26 11:48 ` Adam Sjøgren
2020-09-26 17:08 ` Pankaj Jangid
2020-09-25 18:25 ` Adam Sjøgren
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=873635akcz.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=asjo@koldfront.dk \
--cc=ding@gnus.org \
--cc=pankaj@codeisgreat.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 NNTP newsgroup(s).