From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: sending messages from script/command line
Date: Mon, 01 Jul 2013 08:40:50 -0400 [thread overview]
Message-ID: <87obamjvvx.fsf@lifelogs.com> (raw)
In-Reply-To: <87zjua8edq.fsf@yun.yagibdah.de>
On Fri, 28 Jun 2013 17:40:25 +0200 lee <lee@yun.yagibdah.de> wrote:
l> is there a way to send messages from a script using the posting style of
l> a particular group? Like
l> emacsclient -e "(gnus-group-mail 1)"
l> works fine, only it doesn't let me specify which group to use and emacs
l> asks me.
...
l> This might not be as it should be, but it seems to work:
l> emacsclient -e '(my-gnus-group-mail "particular.group.name")'
l> Maybe there's a better (already built-in) way to do this?
There's no built-in way to do what you describe, so your function is
probably the best solution.
l> Since I am at this: This only works when gnus has already been started.
l> What would I do to make sure that it's started if it isn't? Is there a
l> way to check whether gnus is running from the command line/script, or
l> could/should I write a wrapper around 'my-gnus-group-mail that starts
l> gnus in case it's not started already?
Since Gnus is not a daemon, it's hard to do what you describe. Gnus is
more like a set of functions that agree upon the same buffer formats :)
So the simplest way, probably, is to give some advice to the `gnus'
function and to the `q' keybinding in the Group buffer. You can also
look at the `gnus-slave' stuff but that's opportunistic and not stateful.
Ted
next prev parent reply other threads:[~2013-07-01 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 15:40 lee
2013-07-01 12:40 ` Ted Zlatanov [this message]
2013-07-02 9:48 ` lee
2013-07-02 15:35 ` Ted Zlatanov
2013-07-05 22:00 ` lee
2013-07-06 3:22 ` Eric Abrahamsen
2013-07-08 12:23 ` Ted Zlatanov
2013-07-08 14:08 ` Eric Abrahamsen
2013-07-08 12:32 ` Ted Zlatanov
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=87obamjvvx.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).