GNU bug report logs - #24172
25.1; Doc of parse-sexp-ignore-comments: what does a value of nil mean?

Previous Next

Full log

Message #17 received at 24172 <at> debbugs.gnu.org (full text, mbox):

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Alan McKenzie <MAILER-DAEMON <at> mail.muc.de>
Cc: 24172 <at> debbugs.gnu.org
Subject: Re: bug#24172: 25.1; Doc of parse-sexp-ignore-comments: what does a
 value of nil mean?
Date: Mon, 29 Jul 2019 04:18:56 +0200

Alan McKenzie <MAILER-DAEMON <at> mail.muc.de> writes:

> All in all, this variable seems not to be a good idea.  It is not
> tested consistently by the syntax routines (see above), must be set
> explicitly to t by any major mode with comments, the nil value is
> rarely used, and it is not clear whether this nil value is actually
> ever useful.

My question mainly arised from pondering whether this variable could be
useful for el-search, a package for searching Elisp code (with
patterns).  It could be of minor use if it allowed to search commented
code.  But I can also implement this in other ways.  Apart from that, I
have no use cases, so I wrote the bug report only because of the unclear
documentation.

But the variable seems to be used.  I have 75 matches in my load-path.

Michael.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.