Clock becomes a paragraph by prefixing with not-really-affiliated-keyword

2023-10-12 Thread Tom Alexander
This test document correctly parses as a clock: ``` CLOCK: [2023-04-21 Fri 19:43] ``` This test document incorrectly parses as a paragraph: ``` #+NAME: foo CLOCK: [2023-04-21 Fri 19:43] ``` -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Re: Keyword becoming a paragraph based on optval

2023-10-12 Thread Tom Alexander
> Note that _affiliated keyword_ has an optional form of Ah, that was what I was missing, thanks! -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Re: Keyword becoming a paragraph based on optval

2023-10-12 Thread Ihor Radchenko
"Tom Alexander" writes: > Emacs version: 29.1 > Org-mode version: f3de4c3e041e0ea825b5b512dc0db37c78b7909e (latest in git) > > This test document parses as a keyword: > ``` > #+CAPTION[*foo*]: baz > ``` > > but this test document parses as a paragraph: > ``` > #+CAPTION[*foo* bar]: baz > ```

Keyword becoming a paragraph based on optval

2023-10-12 Thread Tom Alexander
Emacs version: 29.1 Org-mode version: f3de4c3e041e0ea825b5b512dc0db37c78b7909e (latest in git) This test document parses as a keyword: ``` #+CAPTION[*foo*]: baz ``` but this test document parses as a paragraph: ``` #+CAPTION[*foo* bar]: baz ``` -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Re: [BUG] org-babel-tangle may fail due to (org-babel-tangle-collect-blocks lang-re tangle-file) [9.6.9 ( @ /home/andrea/.emacs.d/elpa/org-9.6.9/)]

2023-10-12 Thread Andrea
On Thu 12 Oct 2023 at 15:29, Ihor Radchenko wrote: > > I recommend trying to shrink the problematic file to the smallest possible. > Then, try with emacs -Q. If cannot reproduce, you can use > https://github.com/Malabarba/elisp-bug-hunter to bisect the config > quickly. Thanks Ihor! I found

Re: [BUG] org-babel-tangle may fail due to (org-babel-tangle-collect-blocks lang-re tangle-file) [9.6.9 ( @ /home/andrea/.emacs.d/elpa/org-9.6.9/)]

2023-10-12 Thread Ihor Radchenko
Andrea writes: > Mmm... I run org-lint (and fix unrelated issues, thanks!) and the problem > remains. > It is strange though, this is the block on which the function > stops working (it is the first actually) > > ... > Must be something wrong with my configuration then. > I will update this

Re: [BUG] org-babel-tangle may fail due to (org-babel-tangle-collect-blocks lang-re tangle-file) [9.6.9 ( @ /home/andrea/.emacs.d/elpa/org-9.6.9/)]

2023-10-12 Thread Andrea
On Thu 12 Oct 2023 at 14:40, Ihor Radchenko wrote: > Andrea writes: > >> This is the full trace I get running "emacs --debug-init" (sorry I should >> have added it in my bug report): >> >>Debugger entered--Lisp error: (wrong-type-argument stringp nil) >>

Re: [the cryptic @@#$7]

2023-10-12 Thread Uwe Brauer
>>> "BB" == Bruno Barbier writes: > Hi Uwe, > Uwe Brauer writes: >> Here is an example where the org-lookup-first method seems to fail >> #+TBLFM: $3='(org-lookup-first $2 '(remote(Table1A, @I$1..@II$1)) >> '(remote(Table1A, @I$7..@II$7)))::$4='(org-lookup-first $2 >> '(remote(Table2A,

Re: [BUG] org-babel-tangle may fail due to (org-babel-tangle-collect-blocks lang-re tangle-file) [9.6.9 ( @ /home/andrea/.emacs.d/elpa/org-9.6.9/)]

2023-10-12 Thread Ihor Radchenko
Andrea writes: > This is the full trace I get running "emacs --debug-init" (sorry I should > have added it in my bug report): > >Debugger entered--Lisp error: (wrong-type-argument stringp nil) > string-match("\\`\\(?:e\\(?:\\(?:macs-\\)?lisp\\)\\)\\'" nil nil) >

Re: [BUG] org sub tree sort broken [9.7-pre (release_9.6.10-827-ge15699 @ /home/d/src/git-org-mode/lisp/)]

2023-10-12 Thread Daniel Ortmann
Fix confirmed. Thank you! On 10/12/23 03:21, Ihor Radchenko wrote: Daniel Ortmann writes: org-element--generate-copy-script: Symbol\u2019s function definition is void: org-export--list-bound-variables Sorry. Silly mistake in a recent commit. Fixed, on main.

Re: [BUG] org-babel-tangle may fail due to (org-babel-tangle-collect-blocks lang-re tangle-file) [9.6.9 ( @ /home/andrea/.emacs.d/elpa/org-9.6.9/)]

2023-10-12 Thread Andrea
Thanks Ihor for the super quick response! On Thu 12 Oct 2023 at 13:04, Ihor Radchenko wrote: > Andrea writes: > >> >> Sometimes I get an error on org-babel-load-file saying that >> org-babel-tangle-collect-blocks was called with target-file set to nil. > > May it be possible to provide

Re: [the cryptic @@#$7]

2023-10-12 Thread Bruno Barbier
Hi Uwe, Uwe Brauer writes: > Here is an example where the org-lookup-first method seems to fail > #+TBLFM: $3='(org-lookup-first $2 '(remote(Table1A, @I$1..@II$1)) > '(remote(Table1A, @I$7..@II$7)))::$4='(org-lookup-first $2 '(remote(Table2A, > @I$1..@II$1)) '(remote(Table2A,

Re: [BUG] org-babel-tangle may fail due to (org-babel-tangle-collect-blocks lang-re tangle-file) [9.6.9 ( @ /home/andrea/.emacs.d/elpa/org-9.6.9/)]

2023-10-12 Thread Ihor Radchenko
Andrea writes: > > Sometimes I get an error on org-babel-load-file saying that > org-babel-tangle-collect-blocks was called with target-file set to nil. May it be possible to provide more details about the error you are seeing? You can set `debug-on-error' to t and post the backtrace,

Re: Event management

2023-10-12 Thread Ihor Radchenko
Rainer Hansen writes: > > The event is managed via LinkedIn: > https://www.linkedin.com/events/communicatesuccessfullyininterv7115081313199509504/ > > but it is difficult to keep track of who has recently signed-up in > LinkedIn. I can only see the complete list of people having >

Re: Inconsistent text markup handling when double-nesting markers

2023-10-12 Thread Ihor Radchenko
Max Nikulin writes: > By the way, is it explicitly specified that within an element namely > top-down strategy must be used to recognize objects? https://orgmode.org/worg/org-syntax.html has it, I think. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: Add new word before an org-agenda entry (like "MODIFIED")

2023-10-12 Thread Ihor Radchenko
Cletip Cletip writes: > Here's an example for clarification: > Consider this line in org-agenda: > > 14:08-14:10 Clocked: (0:02) name-of-the-heading > > I want exactly the same thing, but not with the "Clocked" word ! This is not easy. The supported log types are hard-coded in

Re: Exporting elisp: and shell: links

2023-10-12 Thread Ihor Radchenko
Max Nikulin writes: >> I like more how ox-ascii (without the >> proposed diff) handles the situation via footnote-like link. > > That is why I believe that extracting fragments of code into helper > functions is important. If ox-ascii.el had a function that adds an item > to link list then

[BUG] org-babel-tangle may fail due to (org-babel-tangle-collect-blocks lang-re tangle-file) [9.6.9 ( @ /home/andrea/.emacs.d/elpa/org-9.6.9/)]

2023-10-12 Thread Andrea
Hello, thanks for maintaining the great Org Mode! I have been keeping a literate Org Mode configuration for my init file. This means that I have tons of src blocks looking like #+begin_src emacs-lisp :tangle yes ... #+end_src Sometimes I get an error on org-babel-load-file saying that

Re: Comments following not-really-affiliated keywords are becoming paragraphs

2023-10-12 Thread Ihor Radchenko
"Tom Alexander" writes: > Test document: > ``` > #+CAPTION: foo > # bar > ``` > > This parses as a paragraph with the caption of foo and the body of "# bar" > when it should parse as a regular keyword followed by a comment. Thanks for reporting! Fixed, on main.

Re: Document-level properties incorrect and/or missing based on preceding blank lines and/or comments

2023-10-12 Thread Ihor Radchenko
"Tom Alexander" writes: > ### Issue 1 > > Putting a comment before it makes the value for the foo property incorrect > (seems to be grabbing an earlier string slice): > > ### Issue 2 > > Putting any blank lines before it makes the foo property not appear in > org-data at all > ``` > >

Re: Inconsistent text markup handling when double-nesting markers

2023-10-12 Thread Max Nikulin
On 11/10/2023 19:26, Ihor Radchenko wrote: Max Nikulin writes: P.S. Juan Manuel at certain moment discovered that pandoc allows nesting for *b1 *b2* b3*. Which is a bug in pandoc. I think we discussed this topic a number of times in the past - our markup is a compromise between simplicity

Re: [BUG] org sub tree sort broken [9.7-pre (release_9.6.10-827-ge15699 @ /home/d/src/git-org-mode/lisp/)]

2023-10-12 Thread Ihor Radchenko
Daniel Ortmann writes: > org-element--generate-copy-script: Symbol\u2019s function definition is > void: org-export--list-bound-variables Sorry. Silly mistake in a recent commit. Fixed, on main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f660afc50 -- Ihor Radchenko //

Re: Org-mode starting with 37d6bde27 errors out parsing org-mode/testing/examples/pub/a.org

2023-10-12 Thread Ihor Radchenko
"Tom Alexander" writes: > I've attached a Dockerfile that reproduces the issue. Just throw that in a > directory and run `docker build -t temp .` to see it fail. Change the `ARG > ORG_VERSION=` line to `ac108a3ac1b332bf27ff2984a9cf26af3744185d` to see it > succeed. > > Error message: > ``` >