unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#32742: 27.0.50; text-char-description examples fail
@ 2018-09-15 22:44 Juri Linkov
  2018-09-16  2:36 ` Eli Zaretskii
  0 siblings, 1 reply; 3+ messages in thread
From: Juri Linkov @ 2018-09-15 22:44 UTC (permalink / raw)
  To: 32742

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.





^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#32742: 27.0.50; text-char-description examples fail
  2018-09-15 22:44 bug#32742: 27.0.50; text-char-description examples fail Juri Linkov
@ 2018-09-16  2:36 ` Eli Zaretskii
  2018-09-20  6:43   ` Eli Zaretskii
  0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2018-09-16  2:36 UTC (permalink / raw)
  To: Juri Linkov; +Cc: 32742

> 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.





^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#32742: 27.0.50; text-char-description examples fail
  2018-09-16  2:36 ` Eli Zaretskii
@ 2018-09-20  6:43   ` Eli Zaretskii
  0 siblings, 0 replies; 3+ messages in thread
From: Eli Zaretskii @ 2018-09-20  6:43 UTC (permalink / raw)
  To: juri; +Cc: 32742-done

> Date: Sun, 16 Sep 2018 05:36:04 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 32742@debbugs.gnu.org
> 
> > 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.

Now fixed on the release branch.

Thanks.





^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2018-09-20  6:43 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-09-15 22:44 bug#32742: 27.0.50; text-char-description examples fail Juri Linkov
2018-09-16  2:36 ` Eli Zaretskii
2018-09-20  6:43   ` Eli Zaretskii

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).