bug#52841: show-paren paring error in org-mode source blocks

bug#52841: show-paren paring error in org-mode source blocks

[Yilkal Argaw]

show-paren-mode works fairly well in lisp source codes but the pairing
does not work in emacs source blocks. For example it pairs ) with <.

An example source code is in the following source code

#+begin_src emacs-lisp

  (if (not (version< emacs-version "27.0"))
      (progn
    (if (fboundp 'native-comp-available-p) (setq comp-deferred-compilation t))
    (setq warning-suppress-types '((flycheck syntax-checker) (comp))))
    )

#+end_src

bug#52841: show-paren paring error in org-mode source blocks

[Eli Zaretskii]

> From: Yilkal Argaw <yilkalargawworkneh@gmail.com>
> Date: Tue, 28 Dec 2021 07:01:37 +0300
> 
> show-paren-mode works fairly well in lisp source codes but the pairing
> does not work in emacs source blocks. For example it pairs ) with <.
> 
> An example source code is in the following source code
> 
> #+begin_src emacs-lisp
> 
>   (if (not (version< emacs-version "27.0"))
>       (progn
>     (if (fboundp 'native-comp-available-p) (setq comp-deferred-compilation t))
>     (setq warning-suppress-types '((flycheck syntax-checker) (comp))))
>     )
> 
> #+end_src

Isn't this a problem specific to Org?  If so, please report it to the
Org bug address first.

Thanks.

bug#52841: show-paren paring error in org-mode source blocks

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

>> #+begin_src emacs-lisp
>> 
>>   (if (not (version< emacs-version "27.0"))
>>       (progn
>>     (if (fboundp 'native-comp-available-p) (setq comp-deferred-compilation t))
>>     (setq warning-suppress-types '((flycheck syntax-checker) (comp))))
>>     )
>> 
>> #+end_src
>
> Isn't this a problem specific to Org?  If so, please report it to the
> Org bug address first.

Well, you see it in any mode that displays code blocks, like in Gnus.
Doesn't rmail fontify that block of code for you?

I can reproduce the problem in Gnus, too, but I'm not that familiar with
how show-paren works -- does it just use the syntax properties in the
buffer?  In which case I don't know how to fix this, because in Gnus
article buffers, <> have parenthesis syntax.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#52841: show-paren paring error in org-mode source blocks

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Yilkal Argaw <yilkalargawworkneh@gmail.com>,  52841@debbugs.gnu.org
> Date: Wed, 29 Dec 2021 16:41:09 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> #+begin_src emacs-lisp
> >> 
> >>   (if (not (version< emacs-version "27.0"))
> >>       (progn
> >>     (if (fboundp 'native-comp-available-p) (setq comp-deferred-compilation t))
> >>     (setq warning-suppress-types '((flycheck syntax-checker) (comp))))
> >>     )
> >> 
> >> #+end_src
> >
> > Isn't this a problem specific to Org?  If so, please report it to the
> > Org bug address first.
> 
> Well, you see it in any mode that displays code blocks, like in Gnus.
> Doesn't rmail fontify that block of code for you?

No, and I'm infinitely grateful that it doesn't.

> I can reproduce the problem in Gnus, too, but I'm not that familiar with
> how show-paren works -- does it just use the syntax properties in the
> buffer?

Yes, it does.

bug#52841: show-paren paring error in org-mode source blocks

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

>> I can reproduce the problem in Gnus, too, but I'm not that familiar with
>> how show-paren works -- does it just use the syntax properties in the
>> buffer?
>
> Yes, it does.

Hm...  but the parentheses machines has the concept of matching pairs,
right?  Let's see...

    (modify-syntax-entry ?> ")<" table)
    (modify-syntax-entry ?< "(>" table)

Right.  So why does it think that < is the opening char for )?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#52841: show-paren paring error in org-mode source blocks

[Stefan Kangas]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Well, you see it in any mode that displays code blocks, like in Gnus.

If it helps, I can confirm that I see this bug with notmuch as well.

bug#52841: show-paren paring error in org-mode source blocks

[Stefan Kangas]

[Please use "Reply to all" so the discussion is in the bug tracker.]

Yilkal Argaw <yilkalargawworkneh@gmail.com> writes:

> You can also see a similar situation in org-tables and example table
> is the following
>
> |-----------------------------------+---------|
> | Logical Expression                | Meaning |
> |-----------------------------------+---------|
> | if ["$variable1" \< "$variable2"] |         |
> |-----------------------------------+---------|
> | if ["$variable1" \> "$variable2"] |         |
> |-----------------------------------+---------|

Thanks.

(This reply is only so that this ends up in the bug tracker.)

bug#52841: show-paren paring error in org-mode source blocks

[Yilkal Argaw]

Will do, thanks!

On Sun, Jan 2, 2022 at 4:34 AM Stefan Kangas <stefan@marxist.se> wrote:
>
> [Please use "Reply to all" so the discussion is in the bug tracker.]
>
> Yilkal Argaw <yilkalargawworkneh@gmail.com> writes:
>
> > You can also see a similar situation in org-tables and example table
> > is the following
> >
> > |-----------------------------------+---------|
> > | Logical Expression                | Meaning |
> > |-----------------------------------+---------|
> > | if ["$variable1" \< "$variable2"] |         |
> > |-----------------------------------+---------|
> > | if ["$variable1" \> "$variable2"] |         |
> > |-----------------------------------+---------|
>
> Thanks.
>
> (This reply is only so that this ends up in the bug tracker.)