From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lawrence Bottorff Subject: Re: Parens matching off in babel code block Date: Thu, 2 May 2019 11:01:22 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000008293cb0587e9bf0e" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:40322) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hME9R-0006fn-Og for emacs-orgmode@gnu.org; Thu, 02 May 2019 12:01:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hME9Q-0005RE-0a for emacs-orgmode@gnu.org; Thu, 02 May 2019 12:01:37 -0400 Received: from mail-lj1-x232.google.com ([2a00:1450:4864:20::232]:44884) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hME9P-0005Ni-PO for emacs-orgmode@gnu.org; Thu, 02 May 2019 12:01:35 -0400 Received: by mail-lj1-x232.google.com with SMTP id c6so2653094lji.11 for ; Thu, 02 May 2019 09:01:35 -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: emacs-orgmode Mailinglist --0000000000008293cb0587e9bf0e Content-Type: text/plain; charset="UTF-8" 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. 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 > --0000000000008293cb0587e9bf0e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Not sure what you mean. This is the probl= em, i.e., just this code

#+begin_src emacs-lisp
=C2=A0 (> 1 2)
#+end_src

in an org file produces a parens mismatch, which, BTW, check-parens also f= lags. Anywhere else (e.g., *scratch*) in Emacs this code produces no mismat= ch.

On Thu, May 2, 2019 at 10:35 AM Berry, Charles <ccberry@ucsd.edu> wrote:


> On May 1, 2019, at 7:56 PM, Lawrence Bottorff <borgauf@gmail.com> wrote:
>
> Wondering if you have seen this over at emacs.stackexchange. Very puzz= ling 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
=C2=A0 (> 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
--0000000000008293cb0587e9bf0e--