From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruno BARBIER Subject: Re: Parens matching off in babel code block Date: Thu, 02 May 2019 22:11:51 +0200 Message-ID: <5ccb4155.1c69fb81.e3d19.0601@mx.google.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:40152) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hMH98-0005nS-GX for emacs-orgmode@gnu.org; Thu, 02 May 2019 15:13:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hMH97-0008I0-K0 for emacs-orgmode@gnu.org; Thu, 02 May 2019 15:13:30 -0400 Received: from mail-wr1-x430.google.com ([2a00:1450:4864:20::430]:43523) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hMH97-0008G8-Dt for emacs-orgmode@gnu.org; Thu, 02 May 2019 15:13:29 -0400 Received: by mail-wr1-x430.google.com with SMTP id a12so4865708wrq.10 for ; Thu, 02 May 2019 12:13:28 -0700 (PDT) In-Reply-To: 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: Lawrence Bottorff , emacs-orgmode Mailinglist Hi Lawrence, Lawrence Bottorff writes: > 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 '). Bruno > On Thu, May 2, 2019 at 10:35 AM Berry, Charles wrote: > >> >> >> > On May 1, 2019, at 7:56 PM, Lawrence Bottorff wrote: >> > >> > Wondering if you have seen this over at emacs.stackexchange. Very >> puzzling why the parens mismatch in a babel emacs-lisp block, but not >> anywhere else in Emacs. >> >> I don't know the details but this ECM might help: >> >> #+begin_src emacs-lisp >> (> 1 2) >> #+end_src >> >> The right broken bracket matches the left parenthesis in org-mode, but not >> in a Lisp Interaction Mode buffer. >> >> HTH >> >> Chuck >>