From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 24172@debbugs.gnu.org
Subject: bug#24172: 25.1; Doc of parse-sexp-ignore-comments: what does a value of nil mean?
Date: Sat, 23 Oct 2021 10:32:38 -0700 [thread overview]
Message-ID: <CADwFkmkMEWEOcfT5oPsEah9KunNnV331PoLNiwT_KAtf93Gp1g@mail.gmail.com> (raw)
In-Reply-To: <874l37fqpl.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Sat, 27 Jul 2019 17:21:42 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
>> in the docstring of `parse-sexp-ignore-comments' (or at least in the
>> manual), I miss a description about what a value of nil exactly means:
>> How are comments treated then? Are they treated as separate units that
>> can then be parsed as well, but separately from code, or are they treated
>> as indistinguishable from code?
>>
>> For example, if parsing starts from within a comment, and parsing finds
>> the end of the comment and is not yet finished, is parsing just
>> continued inside the following code, or does it fail?
>
> After doing some testing, it seems that if it's nil, the commands
> affected by the setting just treat the commented-out text as if it
> wasn't commented out.
>
> So the answer to your last question seems to be "yes".
>
> ;; (foo
>
> (bar zot))
>
> However, pretty much the same thing happens with a non-nil value, too --
> with point before (foo C-M-f will advance past zot)).
>
> So it doesn't treat comments as whitespace, really -- it only does that
> if point is outside (before, at the end of a line, etc) the comment to
> begin with. Seems like you could write an essay about it, but perhaps
> it's not worth listing the eccentricities here which I guess could change.
So is there anything more to do here, or could this be closed? I can't
see anything actionable from reading this thread.
next prev parent reply other threads:[~2021-10-23 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 23:28 bug#24172: 25.1; Doc of parse-sexp-ignore-comments: what does a value of nil mean? Michael Heerdegen
2019-07-27 15:21 ` Lars Ingebrigtsen
2021-10-23 17:32 ` Stefan Kangas [this message]
2021-10-24 13:11 ` Lars Ingebrigtsen
2019-07-28 9:20 ` Alan McKenzie
2019-07-29 2:18 ` Michael Heerdegen
[not found] <20190728082012.19960.qmail@mail.muc.de>
2019-07-28 10:11 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmkMEWEOcfT5oPsEah9KunNnV331PoLNiwT_KAtf93Gp1g@mail.gmail.com \
--to=stefan@marxist.se \
--cc=24172@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.