From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Porter Subject: Re: Discrepancy between documentation and implementation regarding comments Date: Sun, 27 Oct 2019 15:09:49 -0500 Message-ID: <877e4qq7aq.fsf@alphapapa.net> References: <87eeyyy013.fsf@thb.lt> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:51403) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iOorV-0000gq-EC for emacs-orgmode@gnu.org; Sun, 27 Oct 2019 16:10:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iOorU-0008Ra-G0 for emacs-orgmode@gnu.org; Sun, 27 Oct 2019 16:10:05 -0400 Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:48384 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iOorU-0008QR-9P for emacs-orgmode@gnu.org; Sun, 27 Oct 2019 16:10:04 -0400 Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1iOorQ-0014HO-2y for emacs-orgmode@gnu.org; Sun, 27 Oct 2019 21:10:00 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org I agree with Robert that "whitespace" includes newlines in "Emacsland." For example, with this document (the second "#" has a newline immediately after, no spaces or tabs): #+BEGIN_SRC org foo # comment bar # buzz #+END_SRC This code matches both lines that begin with "#": (re-search-forward (rx bol "#" (1+ space))) But this code only matches the first one, because "blank" only matches "horizontal whitespace": (re-search-forward (rx bol "#" (1+ blank))) So I think Pandoc is technically at fault here. However, outside of Emacs's own context, I can see how the the documentation could be misinterpreted in this case, so it's hard to fault them too much. :)