Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: backend stuff for the manual
Date: Tue, 04 Sep 2001 00:22:11 +0200	[thread overview]
Message-ID: <vaf3d63rk30.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3wv3nk4fn.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Tue, 28 Aug 2001 22:03:34 -0400")

prj@po.cwru.edu (Paul Jarc) writes:

> For nnchoke-request-create-group, the third argument is not
> documented.  How is it supposed to be used?

I think it isn't used at all?!?

I looked at nnmbox-, nnfolder-, nnml-, and
nnimap-request-create-group.  These functions don't use the ARGS
argument.

I looked at gnus-request-create-group which presumably calls these
functions.  It just passes on its own ARGS parameter.

I then looked for callers of gnus-request-create-group.  None passed
ARGS, except for gnus-group-make-group, which passes on its own ARGS
parameter.

I then looked for callers of gnus-group-make-group.  The ARGS
parameter was not used.

[time passes]

OK, now I searched for all occurrences of -request-create-group, and
the ARGS parameter was not used in calls, except for functions which
just passed on their own ARGS parameter.

I think that this means that ARGS is not used.

Is anybody adventurous enough to try deleting it?  If it works, submit
a patch, then it will be deleted from the Gnus sources.  (This job can
be done by anybody, I think, no Lisp experience required.  Just a good
backup of your mail  :-)

kai
-- 
Symbol's function definition is void: signature


      parent reply	other threads:[~2001-09-03 22:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-29  2:03 Paul Jarc
2001-09-03 22:08 ` Kai Großjohann
2001-09-03 22:59   ` Paul Jarc
2001-09-04 13:38     ` Kai Großjohann
2001-09-03 22:22 ` Kai Großjohann [this message]

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=vaf3d63rk30.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).