From: Bruno BARBIER <brubar.cs@gmail.com>
To: Lawrence Bottorff <borgauf@gmail.com>,
emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Parens matching off in babel code block
Date: Thu, 02 May 2019 22:11:51 +0200 [thread overview]
Message-ID: <5ccb4155.1c69fb81.e3d19.0601@mx.google.com> (raw)
In-Reply-To: <CAFAhFSWC-8VjBbt26ZrE0VHrejxe=GQr-NF5AroK8Q9ftdyVjw@mail.gmail.com>
Hi Lawrence,
Lawrence Bottorff <borgauf@gmail.com> 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 <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
>> 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
>>
next prev parent reply other threads:[~2019-05-02 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 2:56 Parens matching off in babel code block Lawrence Bottorff
2019-05-02 15:35 ` Berry, Charles
2019-05-02 16:01 ` Lawrence Bottorff
2019-05-02 20:11 ` Bruno BARBIER [this message]
2019-05-02 20:28 ` Marco Wahl
2019-05-02 21:38 ` Nicolas Goaziou
2019-05-03 2:11 ` Lawrence Bottorff
2019-05-03 9:23 ` Fraga, Eric
2019-05-04 12:54 ` John Kitchin
2019-05-05 15:02 ` Marco Wahl
2019-05-03 8:20 ` Marco Wahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ccb4155.1c69fb81.e3d19.0601@mx.google.com \
--to=brubar.cs@gmail.com \
--cc=borgauf@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).