Re: How to make gnus read something besides .gnus in batch mode

[Harry Putnam <reader@newsguy.com>]

John Paul Wallington <jpw@gnu.org> writes:

>>> Many arguments are deleted from `command-line-args' as they are
>>> processed.  How about checking the `noninteractive' variable ?

[...]

> I don't think it makes sense to heed `noninteractive' in a form that
> is passed to emacs -batch -eval because that would be redundant.
>
> [Nevertheless, emacs -batch -eval 'noninteractive' is syntactically
> correct at least, and to "make it do something" you could say emacs
> -batch -eval '(print noninteractive)' or emacs -batch -eval '(if
> noninteractive (print "foo"))'.]
>
> It makes more sense to heed `noninteractive' in your .gnus file.

Yes,  I was looking for the correct syntax to access it.  You've
supplied it.  Test for boolean value.

> emacs -q -no-site-file -batch -l ~/.my_gnus.el -f gnus-agent-batch
>
> Maybe it helps to frob the variable `gnus-init-file' to avoid loading
> ~/.gnus ?  For example, you could put (setq gnus-init-file
> (expand-file-name "~/.my_gnus.el")) at the start of ~/.my_gnus.el
> (untested).

L. Mitchell posted something that does that same thing I think:
emacs -batch --eval '(setq gnus-init-file "~/.not-dot-gnus")' \
 -f gnus-agent-batch

After being shown the proper stuff to look at and some experimentation.
It looks like one cannot slurp the contents of command-line-args even
by sticking it in a variable first thing:

 $ emacs -eval '(defvar myargs command-line-args)' \ 
   -q -no-site-file -batch  -eval '(print myargs)'

("emacs" "-eval" "(defvar myargs command-line-args)" "-eval" "(print
myargs)")

Still doesn't know about `-q', `-no-stite-file', or `-batch'

But noninteractive knows its a -batch command.

cat new.el
(message "Hello World from new.el")
(if noninteractive (print "Running noninteractive"))

=========

     $ emacs -q -no-site-file -batch -l ./new.el
   Hello World from new.el

   "Running noninteractive"

I have enough to solve my problme but still wondered if there just is
no way to grab all of command-line-args before processing begins?
Oh, and where is the extra newline coming from in the above output?