GNU bug report logs - #76611
30.1; Elisp manual: Say what it means for a char to be printable

Previous Next

Full log

Message #16 received at 76611-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 76611-done <at> debbugs.gnu.org
Subject: Re: [External] : Re: bug#76611: 30.1; Elisp manual: Say what it means
 for a char to be printable
Date: Fri, 28 Feb 2025 20:56:02 +0200

> From: Drew Adams <drew.adams <at> oracle.com>
> CC: "76611 <at> debbugs.gnu.org" <76611 <at> debbugs.gnu.org>
> Date: Fri, 28 Feb 2025 17:56:03 +0000
> 
> > I don't understand what you are trying to say here.  Is something
> > missing from the "Character Type" node of the ELisp manual and its
> > sub-nodes, wrt the read syntax of characters?
> 
> I had in mind just mentioning in the context of the
> doc about printable chars that what's printed can
> be read by the Lisp reader.
> 
> This is different from the read syntax of character
> objects: ?<CHAR>.  It's not about reading character
> objects as such.  It's about the reader's handling
> of printable chars.
> 
> (aref printable-chars ?^L) => nil (pretend it's ^L)
> 
> A Ctrl-L char isn't read by the reader, e.g. as part
> of a symbol name.
> 
> But now that I think about it, it would probably be
> more confusing than helpful, because to explain it
> would dig a new rabbit hole, to no good.
> 
> Feel free to close, if you haven't already.

Done now.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.