emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#18957: closed (25.0.50; document #: in Elisp manua


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#18957: closed (25.0.50; document #: in Elisp manual)
Date: Fri, 16 Feb 2018 09:26:02 +0000

Your message dated Fri, 16 Feb 2018 11:25:06 +0200
with message-id <address@hidden>
and subject line Re: bug#30478: 26.0.91; Add index entries to Elisp manual 
for#: syntax
has caused the debbugs.gnu.org bug report #30478,
regarding 25.0.50; document #: in Elisp manual
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
30478: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30478
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 25.0.50; document #: in Elisp manual Date: Wed, 5 Nov 2014 08:43:50 -0800 (PST)
`#:' should be documented properly in the Elisp manual.  There are just
a few in-passing references to it, which do not explain it.

The Lisp reader should be documented well, from a user point of view,
with everything affecting it explained - preferably in one place.

That includes `#<', `#:', `#N=', `#N#', address@hidden', `#$', `#.', comments,
number syntax (including non-10 radix), \-escaped newlines and spaces,
hash tables.

In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2014-10-20 on LEG570
Bzr revision: 118168 address@hidden
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --enable-checking=yes,glyphs CPPFLAGS=-DGLYPH_DEBUG=1'



--- End Message ---
--- Begin Message --- Subject: Re: bug#30478: 26.0.91; Add index entries to Elisp manual for#: syntax Date: Fri, 16 Feb 2018 11:25:06 +0200
> Date: Thu, 15 Feb 2018 16:55:50 -0800 (PST)
> From: Drew Adams <address@hidden>
> 
> Subject line says it all.  Targets would be nodes `Symbol Type'
> and `Output Variables'.

The index entry is already there, but it cannot be #: because Info
cannot cope with a colon in a menu, and index in Info is just a large
menu.  So in Info we use "#COLON instead (we do use #: in the printed
manual).


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]