emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eddie Drury <eddie.drury@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Parens matching errors in org-babel code blocks
Date: Tue, 21 Dec 2021 20:51:39 +0800	[thread overview]
Message-ID: <CABa5=g5z0C9Vd0JPOczUHukHXXCGb2oMGShuXPDLK4uYayRTrQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 589 bytes --]

Inside org-babel code blocks, emacs matches parens incorrectly whenever
different bracket types (eg <> {} []) are used.

For example the following in an .org file will cause check-parens to throw
an error:

#+BEGIN_SRC emacs-lisp

  (> 1 0)


Where in an .el it will interpret the parens correctly. This error also
occurs with show-paren-mode and evil-jump-item.

Thanks very much.

Emacs  : GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.27, cairo version 1.17.4)
 of 2021-03-27
Package: Org mode version 9.4.4 (release_9.4.4 @

[-- Attachment #2: Type: text/html, Size: 779 bytes --]

             reply	other threads:[~2021-12-21 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 12:51 Eddie Drury [this message]
2021-12-21 18:20 ` Tim Cross
2021-12-21 20:58   ` Tom Gillespie

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:

  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='CABa5=g5z0C9Vd0JPOczUHukHXXCGb2oMGShuXPDLK4uYayRTrQ@mail.gmail.com' \
    --to=eddie.drury@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: Parens matching errors in org-babel code blocks' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).