* bug#21385: 24.5; Emacs Lisp Manual, section 17.3 "Debugging Invalid Lisp Syntax": wording can be improved
@ 2015-08-31 12:52 phs
2019-08-01 19:40 ` Lars Ingebrigtsen
0 siblings, 1 reply; 2+ messages in thread
From: phs @ 2015-08-31 12:52 UTC (permalink / raw)
To: 21385
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
I needed help with finding the location of a spurious closing
parenthesis and the manual was very helpful.
Here I'm talking about sections 17.3.* of the Emacs Lisp Manual at
http://www.gnu.org/software/emacs/manual/
However, I think these sections would be better/clearer if (at some
place) they explicitly mentioned by name the command `backward-up-list'
invoked via C-M-u rather than just give cryptic key sequences. Also,
this could perhaps support a link to the appropriate section (curr.
26.4.2) of the Emacs manual for more details on the function.
-phs
[-- Attachment #2: Type: text/html, Size: 973 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* bug#21385: 24.5; Emacs Lisp Manual, section 17.3 "Debugging Invalid Lisp Syntax": wording can be improved
2015-08-31 12:52 bug#21385: 24.5; Emacs Lisp Manual, section 17.3 "Debugging Invalid Lisp Syntax": wording can be improved phs
@ 2019-08-01 19:40 ` Lars Ingebrigtsen
0 siblings, 0 replies; 2+ messages in thread
From: Lars Ingebrigtsen @ 2019-08-01 19:40 UTC (permalink / raw)
To: phs; +Cc: 21385
phs <phs@lsv.ens-cachan.fr> writes:
> I needed help with finding the location of a spurious closing parenthesis and
> the manual was very helpful.
>
> Here I'm talking about sections 17.3.* of the Emacs Lisp Manual at
> http://www.gnu.org/software/emacs/manual/
>
> However, I think these sections would be better/clearer if (at some place)
> they explicitly mentioned by name the command `backward-up-list' invoked
> via C-M-u rather than just give cryptic key sequences. Also, this could
> perhaps support a link to the appropriate section (curr. 26.4.2) of the Emacs
> manual for more details on the function.
(I'm going through old bug reports that have unfortunately not gotten
any responses.)
Hm... Well, reading that section and the following nodes ("Excess
Open"), it seems like it's written in a tutorial-ish fashion. I think
perhaps that dropping in that level of low-level details would make it
less readable. So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-08-01 19:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-08-31 12:52 bug#21385: 24.5; Emacs Lisp Manual, section 17.3 "Debugging Invalid Lisp Syntax": wording can be improved phs
2019-08-01 19:40 ` Lars Ingebrigtsen
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.