Re: Exporting multiple #+AUTHOR keywords

ypuntot writes: > Is it related with AUTHOR property? > I am starting to add these properties to every book, and chapter of > the book, that I study. I hope this doesn't lead to a suboptimal > workflow. > > Doesn't this work? > > :PROPERTIES: > :AUTHOR: García-Ael, Cristina and Pérez-Gar

Re: Table of contents position in HTML export

Ihor Radchenko writes: > Kodi Arfer writes: > >> the table of contents appears before "text before headline", although the >> manual says "Org normally inserts the table of contents directly before the >> first headline of the file". So shouldn't it be after "text before >> headline"? Or is i

[DISCUSSION] What should we do with undocumented x^(superscript inside /round/ braces) syntax? (was: Subscript with parenthesis)

Ihor Radchenko writes: > "Tom Alexander" writes: > >> Some additional things I'm noticing: >> >> - when using parenthesis, :use-brackets-p is nil, so they're not equivalent >> to curly braces. > > `org-element-subscript-parser' uses `org-match-substring-regexp', which > indeed allows foo_(...).

Re: [BUG] Warning: The error was: (error "Invalid search bound (wrong side of point)") [9.6.15 (release_9.6.15 @ z:/emacs-i686/share/emacs/29.2/lisp/org/)]

Hi, Ihor Nope, I don't usually see that error. On 14/02/2024 15:22, Ihor Radchenko wrote: Ypo writes: I got a warning, which asked to be reported. Not sure why it happened, I think it was when I refreshed calfw calendar: Thanks for reporting! Do you see the same warning if you switch to Org

Re: [BUG] Warning: The error was: (error "Invalid search bound (wrong side of point)") [9.6.15 (release_9.6.15 @ z:/emacs-i686/share/emacs/29.2/lisp/org/)]

Ypo writes: > Nope, I don't usually see that error. Thanks for checking! I did some non-trivial fixes to org-element-cache code on main that cannot go onto the stable branch. So, I will assume that this error will be gone in the next Org mode release. Canceled. -- Ihor Radchenko // yantar92,

Re: [POLL] Change calling convention for when `org-link-file-path-type' is set to custom function (was: Enhancement Proposal for 'org-link-file-path-type' Behavior)

Ihor Radchenko writes: >> I'd like to suggest a small enhancement to the >> 'org-link-file-path-type' option. When set to 'function', it currently >> passes an absolute path to the user's custom function. This limits >> flexibility as the original path input is not available to the >> function. >

Re: nested blocks in org

mahmood sheikh writes: > can you point me in the right direction of getting org mode to recognize > nested blocks, like code highlighting for src blocks that are within > another special block? May you please give an example of what you have in mind? -- Ihor Radchenko // yantar92, Org mode con

Re: detangling with babel :var header entries

"Fraga, Eric" writes: > Can anybody suggest a workaround that allows me to incorporate a :var > data field in a src block but still allow to tangling/detangling to work > as it should? I cannot think of any way and can obviously live with it > (I just have to remember to delete the spurious vers

Re: #6 [[bbb:OrgMeetup]] on Wed, Feb 14, 19:00 UTC+3

Ihor Radchenko writes: > Another OrgMeetup will be scheduled on the second Wednesday of > February, in two weeks. Wait, ... the date of your message is "the second Wednesday of February" (Feb 14). Did you mean "the *fourth* Wednesday of February" (Feb 28), which is "in two weeks" from Feb 14, o

Re: #6 [[bbb:OrgMeetup]] on Wed, Feb 14, 19:00 UTC+3

Rudolf Adamkovič writes: > Ihor Radchenko writes: > >> Another OrgMeetup will be scheduled on the second Wednesday of >> February, in two weeks. > > Wait, ... the date of your message is "the second Wednesday of February" > (Feb 14). Did you mean "the *fourth* Wednesday of February" (Feb 28), >

Re: nested blocks in org

[ Adding Org list back to CC; please use Reply All or wide reply to keep the discussion public ] mahmood sheikh writes: > consider the following block > ``` > #+begin_solution > #+begin_src sql > SELECT > CONCAT(c.first_name, ' ', c.family_name) AS name, c.customer_id, > ... > #+end_solu

Re: [DISCUSSION] What should we do with undocumented x^(superscript inside /round/ braces) syntax? (was: Subscript with parenthesis)

On Saturday, February 17th, 2024 at 07:07, Ihor Radchenko wrote: > I tentatively propose to remove the x^(2-i) example from the docstring > and mark the ^(...) syntax deprecated. > > WDYT? I think it's very sensible. It's surprising ^(...) works like this, and if anyone was using it (perhaps

Re: [DISCUSSION] What should we do with undocumented x^(superscript inside /round/ braces) syntax? (was: Subscript with parenthesis)

+1 Tom > On Feb 17, 2024, at 9:38 AM, William Denton wrote: > > On Saturday, February 17th, 2024 at 07:07, Ihor Radchenko > wrote: > >> I tentatively propose to remove the x^(2-i) example from the docstring >> and mark the ^(...) syntax deprecated. >> >> WDYT? > > I think it's very sensib

Re: [DISCUSSION] What should we do with undocumented x^(superscript inside /round/ braces) syntax? (was: Subscript with parenthesis)

> On Feb 17, 2024, at 5:33 AM, Ihor Radchenko wrote: > > WDYT? +1 I use the curly braces since I often use underscores for other reasons. There would be no impact to me and this is the first I ever heard that parentheses would work.

Extraneous blank lines in when attempting to export org tables

Hello, I'm currently working on an exporter that will allow org-mode to export to PMWiki markdown (https://github.com/quanticle/ox-pmwiki/), and I'm running into a problem when writing the export code to handle tables. When exporting table rows, I'm getting extraneous blank lines between table row