unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
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 18:12:24 +0200	[thread overview]
Message-ID: <m3pqlcvo2f.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <83mxggetu6.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 14 Jul 2011 18:59:45 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> If you delete it, how would users know what does this function do with
> unibyte strings?  What numerical value will it return when passed a
> unibyte string?

Isn't the same the case with `char-after' in a unibyte buffer, for
instance? 

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/





  reply	other threads:[~2011-07-14 16:12 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
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 [this message]
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=m3pqlcvo2f.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --cc=6576@debbugs.gnu.org \
    --cc=eliz@gnu.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 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).