From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: monkey@sandpframing.com, schwab@linux-m68k.org, 6576@debbugs.gnu.org
Subject: bug#6576: documentation `string-to-char' is incorrect
Date: Thu, 14 Jul 2011 15:02:53 +0200 [thread overview]
Message-ID: <m3oc0x9fr6.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87ipr5pq35.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 13 Jul 2011 22:13:02 -0400")
Chong Yidong <cyd@stupidchicken.com> writes:
> How bout linking to the `String and Character Basics' node in the Elisp
> manual instead?
I can do that if you want, but wouldn't it be better just to leave it as
--
Return the first character in STRING.
A multibyte character is handled correctly.
--
If somebody then wonders (and they shouldn't) "hm, what's a character,
then?", they probably already know that a manual exists.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-14 13:02 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
2011-07-14 13:02 ` Lars Magne Ingebrigtsen [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3oc0x9fr6.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=6576@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).