all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: 24172@debbugs.gnu.org
Subject: bug#24172: 25.1; Doc of parse-sexp-ignore-comments: what does a value of nil mean?
Date: Sun, 07 Aug 2016 01:28:30 +0200	[thread overview]
Message-ID: <874m6xqxy9.fsf@web.de> (raw)


Hello,

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?


Thanks in advance,

Michael.



In GNU Emacs 25.1.1 (x86_64-pc-linux-gnu, GTK+ Version 3.20.6)
 of 2016-08-04 built on drachen
Repository revision: 72221f51439d666d54f5d147f00ecdbb3778ab1b
Windowing system distributor 'The X.Org Foundation', version 11.0.11804000
System Description:	Debian GNU/Linux testing (stretch)

Configured features:
XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND DBUS GSETTINGS NOTIFY
LIBXML2 FREETYPE XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11





             reply	other threads:[~2016-08-06 23:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-06 23:28 Michael Heerdegen [this message]
2019-07-27 15:21 ` bug#24172: 25.1; Doc of parse-sexp-ignore-comments: what does a value of nil mean? Lars Ingebrigtsen
2021-10-23 17:32   ` Stefan Kangas
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=874m6xqxy9.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=24172@debbugs.gnu.org \
    /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.