From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: A P documentation could be enhanced
Date: Sun, 04 Jan 2004 01:21:42 +0100 [thread overview]
Message-ID: <m3k7484l7t.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <878ykoy89l.fsf@emptyhost.emptydomain.de>
Kai Grossjohann <kai@emptydomain.de> writes:
> In that case, I think the docstring is confusingly worded. (At least
> it confused this lowly poster.) It talks at length about the N arg,
> and only mentions the FILENAME arg in passing. Even though it was not
> stated explicitly, I thought that N was the prefix arg.
Uhm... looking at the code, I think that N always is nil when called
interactively. So it's not a docstring confusion; it's just a bug.
:-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2004-01-04 0:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 17:23 Kai Grossjohann
2004-01-03 18:57 ` Lars Magne Ingebrigtsen
2004-01-03 22:31 ` Kai Grossjohann
2004-01-04 0:21 ` Lars Magne Ingebrigtsen [this message]
2004-01-04 18:01 ` Kai Grossjohann
2004-01-04 18:04 ` Kai Grossjohann
2004-01-04 18:12 ` Kai Grossjohann
2004-01-04 20:48 ` Lars Magne Ingebrigtsen
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=m3k7484l7t.fsf@quimbies.gnus.org \
--to=larsi@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).