* bug#18957: 25.0.50; document #: in Elisp manual
@ 2014-11-05 16:43 Drew Adams
2016-04-30 15:02 ` Lars Ingebrigtsen
2019-10-12 18:58 ` Lars Ingebrigtsen
0 siblings, 2 replies; 7+ messages in thread
From: Drew Adams @ 2014-11-05 16:43 UTC (permalink / raw)
To: 18957
`#:' 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#', `#@COUNT', `#$', `#.', 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 rgm@gnu.org-20141020195941-icp42t8ttcnud09g
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking=yes,glyphs CPPFLAGS=-DGLYPH_DEBUG=1'
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#18957: 25.0.50; document #: in Elisp manual
2014-11-05 16:43 bug#18957: 25.0.50; document #: in Elisp manual Drew Adams
@ 2016-04-30 15:02 ` Lars Ingebrigtsen
2019-10-12 18:58 ` Lars Ingebrigtsen
1 sibling, 0 replies; 7+ messages in thread
From: Lars Ingebrigtsen @ 2016-04-30 15:02 UTC (permalink / raw)
To: Drew Adams; +Cc: 18957
Drew Adams <drew.adams@oracle.com> writes:
> `#:' 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#', `#@COUNT', `#$', `#.', comments,
> number syntax (including non-10 radix), \-escaped newlines and spaces,
> hash tables.
I think most of these are explained in the sections where the objects
they describe appears, but it would be nice to have a section that just
describes them all, yes.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#18957: 25.0.50; document #: in Elisp manual
2014-11-05 16:43 bug#18957: 25.0.50; document #: in Elisp manual Drew Adams
2016-04-30 15:02 ` Lars Ingebrigtsen
@ 2019-10-12 18:58 ` Lars Ingebrigtsen
2019-10-12 19:04 ` Noam Postavsky
2019-10-12 19:25 ` Eli Zaretskii
1 sibling, 2 replies; 7+ messages in thread
From: Lars Ingebrigtsen @ 2019-10-12 18:58 UTC (permalink / raw)
To: Drew Adams; +Cc: 18957
Drew Adams <drew.adams@oracle.com> writes:
> `#:' 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#', `#@COUNT', `#$', `#.', comments,
> number syntax (including non-10 radix), \-escaped newlines and spaces,
> hash tables.
#$ and #. doesn't seem to be things Emacs understands? But I've now
added a new node that lists all the rest, which I think is a useful
overview.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#18957: 25.0.50; document #: in Elisp manual
2019-10-12 18:58 ` Lars Ingebrigtsen
@ 2019-10-12 19:04 ` Noam Postavsky
2019-10-12 19:15 ` Lars Ingebrigtsen
2019-10-12 19:25 ` Eli Zaretskii
1 sibling, 1 reply; 7+ messages in thread
From: Noam Postavsky @ 2019-10-12 19:04 UTC (permalink / raw)
To: Lars Ingebrigtsen; +Cc: 18957
Lars Ingebrigtsen <larsi@gnus.org> writes:
> #$ and #. doesn't seem to be things Emacs understands?
#$ translates to current file, and is documented at the end of (info
"(elisp) Docs and Compilation"). #. is indeed a Common Lisp thing only
(though it's mentioned in (info "(elisp) Eval During Compile")).
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#18957: 25.0.50; document #: in Elisp manual
2019-10-12 19:04 ` Noam Postavsky
@ 2019-10-12 19:15 ` Lars Ingebrigtsen
0 siblings, 0 replies; 7+ messages in thread
From: Lars Ingebrigtsen @ 2019-10-12 19:15 UTC (permalink / raw)
To: Noam Postavsky; +Cc: 18957
Noam Postavsky <npostavs@gmail.com> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> #$ and #. doesn't seem to be things Emacs understands?
>
> #$ translates to current file, and is documented at the end of (info
> "(elisp) Docs and Compilation").
Thanks; I thought I had grepped for it, but I must have gotten the
escaping wrong.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#18957: 25.0.50; document #: in Elisp manual
2019-10-12 18:58 ` Lars Ingebrigtsen
2019-10-12 19:04 ` Noam Postavsky
@ 2019-10-12 19:25 ` Eli Zaretskii
2019-10-12 19:37 ` Lars Ingebrigtsen
1 sibling, 1 reply; 7+ messages in thread
From: Eli Zaretskii @ 2019-10-12 19:25 UTC (permalink / raw)
To: Lars Ingebrigtsen; +Cc: 18957
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sat, 12 Oct 2019 20:58:54 +0200
> Cc: 18957@debbugs.gnu.org
>
> I've now added a new node that lists all the rest, which I think is
> a useful overview.
When you add a new node, you need to update the @detailmenu in
elisp.texi, and sometimes also the @menu there.
Thanks.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2019-10-12 19:37 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-05 16:43 bug#18957: 25.0.50; document #: in Elisp manual Drew Adams
2016-04-30 15:02 ` Lars Ingebrigtsen
2019-10-12 18:58 ` Lars Ingebrigtsen
2019-10-12 19:04 ` Noam Postavsky
2019-10-12 19:15 ` Lars Ingebrigtsen
2019-10-12 19:25 ` Eli Zaretskii
2019-10-12 19:37 ` Lars Ingebrigtsen
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).