From: Michael Heerdegen <michael_heerdegen@web.de>
To: 38736@debbugs.gnu.org
Subject: bug#38736: 26.3; ellipsis in `*Messages*', doc of `format' etc.
Date: Thu, 26 Dec 2019 04:24:07 +0100 [thread overview]
Message-ID: <877e2j22i0.fsf@web.de> (raw)
In-Reply-To: <83d0ccuxoe.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 25 Dec 2019 19:23:13 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Like I said: eval's doc string documents this feature
I don't understand that comment either, did you mean `prin1'?
> you just looked for the documentation in the wrong place (and still
> found it, albeit through a long path). So I see nothing to be done
> here, and I'm closing this bug report.
I can agree that what we have is acceptable.
But in this sentence in the docstring of `message':
"The first argument is a format control string [...]"
"format" could get quoted so that it gets transformed into a link to the
`format' help page - right?
Michael.
next prev parent reply other threads:[~2019-12-26 3:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<006e6244-dd0a-46a8-8c61-36744b3216de@default>
[not found] ` <<83pngcv5ha.fsf@gnu.org>
2019-12-25 16:44 ` bug#38736: 26.3; ellipsis in `*Messages*', doc of `format' etc Drew Adams
2019-12-25 17:23 ` Eli Zaretskii
2019-12-26 3:24 ` Michael Heerdegen [this message]
2019-12-26 16:23 ` Eli Zaretskii
[not found] <<<<006e6244-dd0a-46a8-8c61-36744b3216de@default>
[not found] ` <<<<83pngcv5ha.fsf@gnu.org>
[not found] ` <<<32378b4e-d158-48d5-a48c-7afde59f5d32@default>
[not found] ` <<<83d0ccuxoe.fsf@gnu.org>
[not found] ` <<4a9b955a-ac97-41d9-a373-fc37b37581a4@default>
[not found] ` <<838smzvk86.fsf@gnu.org>
2019-12-26 17:49 ` Drew Adams
[not found] <<<006e6244-dd0a-46a8-8c61-36744b3216de@default>
[not found] ` <<<83pngcv5ha.fsf@gnu.org>
[not found] ` <<32378b4e-d158-48d5-a48c-7afde59f5d32@default>
[not found] ` <<83d0ccuxoe.fsf@gnu.org>
2019-12-25 20:54 ` Drew Adams
2019-12-26 3:28 ` Eli Zaretskii
2019-12-24 21:02 Drew Adams
2019-12-25 14:34 ` Eli Zaretskii
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=877e2j22i0.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=38736@debbugs.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.