Re: [O] Parens matching off in babel code block

"Fraga, Eric" writes: > On Thursday, 2 May 2019 at 21:11, Lawrence Bottorff wrote: >> Well, at least there is a sane explanation. Ironically, I was also about to >> complain about all my loose ">"s getting flagged. So they are related! >> Would there be a way to make an exception for < and > ins

Re: [O] Parens matching off in babel code block

This issue also pops up in python blocks for me alot. For example, here is a place where it does not work as it should. [image: image.png] John --- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh,

Re: [O] Parens matching off in babel code block

On Thursday, 2 May 2019 at 21:11, Lawrence Bottorff wrote: > Well, at least there is a sane explanation. Ironically, I was also about to > complain about all my loose ">"s getting flagged. So they are related! > Would there be a way to make an exception for < and > inside of actual code > forms? L

Re: [O] Parens matching off in babel code block

Hi, >> Using < and > as parenthesis in Org is questionable, I think. > > In Org syntax, < and > often come in pair (timestamps, some links, > targets, radio targets). There is at least some interest in the current > behaviour. Yes, okay. >> Also this behavior is not documented AFAICT. > > I do

Re: [O] Parens matching off in babel code block

Well, at least there is a sane explanation. Ironically, I was also about to complain about all my loose ">"s getting flagged. So they are related! Would there be a way to make an exception for < and > inside of actual code forms? Languages need them for "greater than" and "less than". On Thu, May

Re: [O] Parens matching off in babel code block

Hello, Marco Wahl writes: > Using < and > as parenthesis in Org is questionable, I think. In Org syntax, < and > often come in pair (timestamps, some links, targets, radio targets). There is at least some interest in the current behaviour. > Also this behavior is not documented AFAICT. I do

Re: [O] Parens matching off in babel code block

>> 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 o

Re: [O] Parens matching off in babel code block

Hi Lawrence, Lawrence Bottorff 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

Re: [O] Parens matching off in babel code block

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 Be

Re: [O] Parens matching off in babel code block

> 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

[O] Parens matching off in babel code block

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