From: Harry Putnam <reader@newsguy.com>
Subject: How to make gnus read something besides .gnus in batch mode
Date: Sun, 29 Jun 2003 10:24:31 -0700 [thread overview]
Message-ID: <m3fzlsvltc.fsf@newsguy.com> (raw)
I want to run batch commands but not read my standard .emacs .gnus
site-start.el. I've learned from the past that things in any init
files that write to standard out like (message) can cause I/O errors.
But I like having some of those in there... so:
I compile an init file on the fly for gnus (or emacs) to read. But
how can I aim gnus at only that file?
I've tinkered with the batch command shown in gnus manual:
From manual version:
emacs -batch -l ~/.emacs -f -l ~/.gnus.el gnus-agent-batch >/dev/null 2>&1
To my version:
emacs -q -no-site-file -batch -l ~/.my_gnus.el -f gnus-agent-batch
It still tries to load ~/.gnus:
emacs -q -no-site-file -batch -l ~/.my_gnus.el -f gnus-agent-batch
hello world -- ~/.gnus
Reading /home/reader/.newsrc-enews.newsguy.com.eld...
[...]
The formulation in the manual has a `-f -l ~/.gnus.el' before
agent-fetch but when I try that it give me this error:
emacs -q -no-site-file -batch -l ~/.my_gnus.el -f -l \
~/.my_gnus.el gnus-agent-batch
Symbol's function definition is void: -l
So how can I tell the function `gnus-agent-batch' which code to load
and prevent it from automatically reading ~/.gnus.
I know about the behavior where if both ~/.gnus and ~/.gnus.el are
present then ~/.gnus.el is read, but that seems likely to lead to a
running gnus reading from ~/.gnus.el too.
Even if I create it for the batch run, then destroy it. Still seems
sooner or later it would get inadvertantly read by a possible running
gnus process during the batch fetch.
next reply other threads:[~2003-06-29 17:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-29 17:24 Harry Putnam [this message]
2003-06-29 20:47 ` Harry Putnam
2003-06-30 4:32 ` John Paul Wallington
2003-06-30 6:25 ` Harry Putnam
2003-06-30 7:01 ` John Paul Wallington
2003-06-30 15:07 ` Harry Putnam
2003-06-30 17:06 ` John Paul Wallington
2003-06-29 21:22 ` lawrence mitchell
2003-07-01 0:15 ` Harry Putnam
2003-07-01 14:17 ` Harry Putnam
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=m3fzlsvltc.fsf@newsguy.com \
--to=reader@newsguy.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 NNTP newsgroup(s).