[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Parens matching off in babel code block
From: |
Marco Wahl |
Subject: |
Re: [O] Parens matching off in babel code block |
Date: |
Thu, 02 May 2019 22:28:16 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
>> 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 ').
Using < and > as parenthesis in Org is questionable, I think. Also this
behavior is not documented AFAICT.
What about removing this special? Or does anyone enjoy this behavior?
- [O] Parens matching off in babel code block, Lawrence Bottorff, 2019/05/01
- Re: [O] Parens matching off in babel code block, Berry, Charles, 2019/05/02
- Re: [O] Parens matching off in babel code block, Lawrence Bottorff, 2019/05/02
- Re: [O] Parens matching off in babel code block, Bruno BARBIER, 2019/05/02
- Re: [O] Parens matching off in babel code block,
Marco Wahl <=
- Re: [O] Parens matching off in babel code block, Nicolas Goaziou, 2019/05/02
- Re: [O] Parens matching off in babel code block, Lawrence Bottorff, 2019/05/02
- Re: [O] Parens matching off in babel code block, Fraga, Eric, 2019/05/03
- Re: [O] Parens matching off in babel code block, John Kitchin, 2019/05/04
- Re: [O] Parens matching off in babel code block, Marco Wahl, 2019/05/05
- Re: [O] Parens matching off in babel code block, Marco Wahl, 2019/05/03