unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 32742@debbugs.gnu.org
Subject: bug#32742: 27.0.50; text-char-description examples fail
Date: Sun, 16 Sep 2018 05:36:04 +0300	[thread overview]
Message-ID: <83d0tei2y3.fsf@gnu.org> (raw)
In-Reply-To: <87h8iq1iuj.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 16 Sep 2018 01:44:36 +0300)

> From: Juri Linkov <juri@linkov.net>
> Date: Sun, 16 Sep 2018 01:44:36 +0300
> 
> The second and third example in (info "(elisp) Describing Characters")
> fail when evaluated:
> 
>           (text-char-description ?\M-m)
> 
> Debugger entered--Lisp error: (wrong-type-argument characterp 134217837)
>   text-char-description(134217837)
>   eval((text-char-description 134217837) nil)
>   elisp--eval-last-sexp(nil)
>   eval-last-sexp(nil)
>   funcall-interactively(eval-last-sexp nil)
>   call-interactively(eval-last-sexp nil nil)
>   command-execute(eval-last-sexp)
> 
>           (text-char-description ?\C-\M-m)
> 
> Debugger entered--Lisp error: (wrong-type-argument characterp 134217741)
>   text-char-description(134217741)
>   eval((text-char-description 134217741) nil)
>   elisp--eval-last-sexp(nil)
>   eval-last-sexp(nil)
>   funcall-interactively(eval-last-sexp nil)
>   call-interactively(eval-last-sexp nil nil)
>   command-execute(eval-last-sexp)
> 
> Not sure if there is a bug in the implementation of text-char-description,
> or its documentation was not updated after some implementation changes.

It's a documentation bug, see bug#32562.





  reply	other threads:[~2018-09-16  2:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-15 22:44 bug#32742: 27.0.50; text-char-description examples fail Juri Linkov
2018-09-16  2:36 ` Eli Zaretskii [this message]
2018-09-20  6:43   ` 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

  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=83d0tei2y3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=32742@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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).