From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-pretest-bug@gnu.org, ding@gnus.org
Subject: Re: doc strings that are too long
Date: Tue, 29 Nov 2005 16:47:32 -0500 [thread overview]
Message-ID: <E1EhDK0-0007Rr-CH@fencepost.gnu.org> (raw)
In-Reply-To: <v9br03heo3.fsf@marauder.physik.uni-ulm.de> (message from Reiner Steib on Tue, 29 Nov 2005 12:33:16 +0100)
| gnus-msg-mail is an interactive compiled Lisp function in `gnus-msg.el'.
| (gnus-msg-mail &optional TO SUBJECT OTHER-HEADERS CONTINUE SWITCH-ACTION YANK-ACTION SEND-ACTIONS)
|
The doc string isn't too long. Maybe you meant the arguments? What
can we do about this?
The only thing we could do to solve this is to change
describe-function-1 to fill the argument list.
next prev parent reply other threads:[~2005-11-29 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MEEKKIABFKKDFJMPIOEBKEJDCNAA.drew.adams@oracle.com>
2005-11-29 11:33 ` Reiner Steib
2005-11-29 21:47 ` Richard M. Stallman [this message]
2005-11-30 0:59 ` John Paul Wallington
2005-12-01 6:05 ` Richard M. Stallman
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=E1EhDK0-0007Rr-CH@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.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).