From: Chong Yidong <cyd@stupidchicken.com>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: monkey@sandpframing.com, schwab@linux-m68k.org, 6576@debbugs.gnu.org
Subject: bug#6576: documentation `string-to-char' is incorrect
Date: Wed, 13 Jul 2011 22:13:02 -0400 [thread overview]
Message-ID: <87ipr5pq35.fsf@stupidchicken.com> (raw)
In-Reply-To: <m3sjq9ivto.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 14 Jul 2011 01:50:59 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I've now installed a slight variation on this in Emacs 24.
>
> But after checking it in, I started wondering whether this doc string
> really makes sense. The function returns an Emacs character, and it
> would be rather weird if all functions that take or return an Emacs
> character goes through that entire explanation.
>
> Is there a specific reason this particular function deserves this
> detailed explanation?
How bout linking to the `String and Character Basics' node in the Elisp
manual instead?
next prev parent reply other threads:[~2011-07-14 2:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 21:34 bug#6576: documentation `string-to-char' is incorrect MON KEY
2010-07-07 7:12 ` Eli Zaretskii
2010-07-07 8:40 ` Andreas Schwab
2010-07-07 10:31 ` Eli Zaretskii
2010-07-07 12:16 ` Andreas Schwab
2010-07-07 14:23 ` Eli Zaretskii
2010-07-07 15:46 ` Eli Zaretskii
2011-07-13 23:50 ` Lars Magne Ingebrigtsen
2011-07-14 2:13 ` Chong Yidong [this message]
2011-07-14 13:02 ` Lars Magne Ingebrigtsen
2011-07-14 3:06 ` Eli Zaretskii
2011-07-14 13:00 ` Lars Magne Ingebrigtsen
2011-07-14 13:34 ` Eli Zaretskii
2011-07-14 14:06 ` Lars Magne Ingebrigtsen
2011-07-14 15:59 ` Eli Zaretskii
2011-07-14 16:12 ` Lars Magne Ingebrigtsen
2011-07-14 19:37 ` Eli Zaretskii
2011-07-14 19:39 ` Lars Magne Ingebrigtsen
2011-07-15 19:06 ` MON KEY
2011-07-21 18:38 ` Chong Yidong
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=87ipr5pq35.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=6576@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monkey@sandpframing.com \
--cc=schwab@linux-m68k.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.