Bastien writes:
> I'll work on integrating small bug fixes and feature improvements
> listed on https://updates.orgmode.org during this week, aiming at
> releasing Org 9.5 over the next week-end.
>
> If your patch does not appear on updates.orgmode.org and didn't
> receive an answer on the
[Java Source Code Blocks in Org
Mode](https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-java.html)
says the following:
"It is not necessary to include the class statement or define a main method.
ob-java will wrap a source code block in boilerplate class and main method
definitions
Bumping this patch for 9.5.
On Fri, Jul 30, 2021 at 8:59 PM Tom Gillespie wrote:
>
> Hi,
>This patch restores the addition of class="org-svg" to svg images
> during html export. Best!
> Tom
> Should we allow syntax like #+KEYWORD:value to be correct or do we
> require a whitespace/space after colon all the time?
The spec as written is ambiguous/silent on this issue. In my work on
laundry tokenizer and grammar I have found keyword syntax to be a
thorny issue, and I strongly suggest
Hi Maxim,
Max Nikulin writes:
> [...]
> Possible options:
> - Add the note directly to the .el file. I am afraid, as inline
> comment it could be considered too long.
> - To a file in the "doc" directory dedicated to such decisions (there
> is no such file yet however) with a reference from
Hi Ihor,
Thanks for checking.
I could narrow down on the issue. It happens after (require
'org-inlinetask) is executed.
So to reproduce:
1. emacs -Q
2. paste the following snipped (right into the scratch buffer)
3. execute the two commands at the end C-x C-e for each
4. collapse all (TAB TAB)
I’m suspect it too short notice for such a large change to make its way into Org
9.5, but Bastien’s release email is certainly a good prompt to bump this.
Bastien writes:
> Thank you *very much* for this work and sorry for the slow reply.
>
> I urge everyone to test this change, as I’d like to
Dominik Schrempf writes:
> Running =org-lint= on an Org file containing
>
> #+NAME:Hello
> #+BEGIN_SRC emacs-lisp :exports code
> #+END_SRC
>
> I get the following error:
> #+begin_quote
> Debugger entered--Lisp error: (search-failed "^[ \11]*#\\+[A-Za-z]+: +Hello
> *$")
> #+end_quote
Dominik Schrempf writes:
> Thank you, org-lint works just fine after applying your patch!
The patch is applied to master as c9dc6603a.
Best,
Ihor
Thank you for the Haskell fix! I found another issue (not a bug but could be
handled better):
Running =org-lint= on an Org file containing
#+NAME:Hello
#+BEGIN_SRC emacs-lisp :exports code
#+END_SRC
I get the following error:
#+begin_quote
Debugger entered--Lisp error: (search-failed "^[
Thank you, org-lint works just fine after applying your patch!
Ihor Radchenko writes:
> Dominik Schrempf writes:
>
>> whenever I have a Haskell source code block in my Org mode file, and I
>> execute
>> =org-lint=, I get the following error:
>
> Confirmed.
>
> Can you try with the attached
Dominik Schrempf writes:
> whenever I have a Haskell source code block in my Org mode file, and I execute
> =org-lint=, I get the following error:
Confirmed.
Can you try with the attached patch?
Best,
Ihor
>From f640249d08a14bfde417c38274634b88c789d1c7 Mon Sep 17 00:00:00 2001
Message-Id:
Hi,
whenever I have a Haskell source code block in my Org mode file, and I execute
=org-lint=, I get the following error:
#+begin_quote
Debugger entered--Lisp error: (wrong-type-argument listp :any)
#+end_quote
(This was obtained with a minimal file just having:
#+BEGIN_SRC haskell
inc n = n+1
13 matches
Mail list logo
