From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Wahl Subject: Re: Parens matching off in babel code block Date: Thu, 02 May 2019 22:28:16 +0200 Message-ID: <847eb88uu7.fsf@gmail.com> References: <5ccb4155.1c69fb81.e3d19.0601@mx.google.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:53128) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hMIJe-0004d8-IJ for emacs-orgmode@gnu.org; Thu, 02 May 2019 16:28:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hMIJd-0007eB-Lx for emacs-orgmode@gnu.org; Thu, 02 May 2019 16:28:26 -0400 Received: from [195.159.176.226] (port=60040 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hMIJd-0007de-FO for emacs-orgmode@gnu.org; Thu, 02 May 2019 16:28:25 -0400 Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1hMIJb-000jae-2t for emacs-orgmode@gnu.org; Thu, 02 May 2019 22:28:23 +0200 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 >> Not sure what you mean. This is the problem, i.e., just this code >> >> #+begin_src emacs-lisp >> (> 1 2) >> #+end_src >> >> in an org file produces a parens mismatch, which, BTW, check-parens also >> flags. Anywhere else (e.g., *scratch*) in Emacs this code produces no >> mismatch. > In an org buffer, '>' is a closing delimiter. In an elisp buffer (like > the *scratch* one), '>' is just a symbol (you can use the command > 'describe-char' to have a description of the character at point). > In short, if I understand correctly, it's not supposed to work like you > expect; you need to edit the source block to do things that really > depend on the code source syntax (C-c '). Using < and > as parenthesis in Org is questionable, I think. Also this behavior is not documented AFAICT. What about removing this special? Or does anyone enjoy this behavior?