From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#24172: 25.1; Doc of parse-sexp-ignore-comments: what does a value of nil mean? Date: Sat, 27 Jul 2019 17:21:42 +0200 Message-ID: <874l37fqpl.fsf@mouse.gnus.org> References: <874m6xqxy9.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="183844"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: 24172@debbugs.gnu.org To: Michael Heerdegen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Jul 27 17:22:11 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hrOWQ-000ldu-Ci for geb-bug-gnu-emacs@m.gmane.org; Sat, 27 Jul 2019 17:22:10 +0200 Original-Received: from localhost ([::1]:46168 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hrOWO-0003JE-Vb for geb-bug-gnu-emacs@m.gmane.org; Sat, 27 Jul 2019 11:22:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55762) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hrOWL-0003HK-TX for bug-gnu-emacs@gnu.org; Sat, 27 Jul 2019 11:22:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hrOWK-0000jz-B3 for bug-gnu-emacs@gnu.org; Sat, 27 Jul 2019 11:22:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36381) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hrOWI-0000in-ML for bug-gnu-emacs@gnu.org; Sat, 27 Jul 2019 11:22:04 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hrOWI-0006Ia-Hg for bug-gnu-emacs@gnu.org; Sat, 27 Jul 2019 11:22:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 27 Jul 2019 15:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 24172 X-GNU-PR-Package: emacs Original-Received: via spool by 24172-submit@debbugs.gnu.org id=B24172.156424091024182 (code B ref 24172); Sat, 27 Jul 2019 15:22:02 +0000 Original-Received: (at 24172) by debbugs.gnu.org; 27 Jul 2019 15:21:50 +0000 Original-Received: from localhost ([127.0.0.1]:45202 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hrOW5-0006Hy-R0 for submit@debbugs.gnu.org; Sat, 27 Jul 2019 11:21:50 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:40494) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hrOW4-0006Hp-4w for 24172@debbugs.gnu.org; Sat, 27 Jul 2019 11:21:48 -0400 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=marnie) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hrOVy-000246-Ph; Sat, 27 Jul 2019 17:21:45 +0200 In-Reply-To: <874m6xqxy9.fsf@web.de> (Michael Heerdegen's message of "Sun, 07 Aug 2016 01:28:30 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:163885 Archived-At: Michael Heerdegen 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. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no