Suggestion: User-contributed use-cases on orgmode.org ?

Just a suggestion (or maybe this is already handled?). Was thinking I'd like to see an archive of tagged use-cases for Org that could be searched via tags or regexp. The use-cases should include a description of the problem, a general description of the answer, blocks of elisp (general code) to s

Re: [TASK] Allow customizeable ditaa executable in ob-ditaa.el

On Sat, Nov 11 2023, Ihor Radchenko wrote: > Leo Butler writes: > >>> And even if we do want to add certain features in future (like >>> supporting ditaa executable herein), it does not mean that we have to >>> rush them by any cost. >> >> Ihor, I don't understand that sentence. >> >> The *docum

Re: org-src-font-lock-fontify-block is unaware of org-edit-src-content-indentation, leading to fontification issues

JD Smith writes: >> Duplicate of >> https://list.orgmode.org/orgmode/CAOn=hbevUMGS0-qMTy8kB4-db65s1Tmn0cQJcw8b++PZZ=v...@mail.gmail.com/ >> Handled. > > Great. In Org 9.7? No. It is not fixed yet. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: org-src-font-lock-fontify-block is unaware of org-edit-src-content-indentation, leading to fontification issues

> On Nov 13, 2023, at 3:37 AM, Ihor Radchenko wrote: > > JD Smith writes: > >> When `org-edit-src-content-indentation’ is non-nil (default: 2), editing SRC >> blocks preserves this amount of extra indentation space at the beginning of >> each line of the block, removing and then re-adding

Re: org-src-font-lock-fontify-block is unaware of org-edit-src-content-indentation, leading to fontification issues

JD Smith writes: > When `org-edit-src-content-indentation’ is non-nil (default: 2), editing SRC > blocks preserves this amount of extra indentation space at the beginning of > each line of the block, removing and then re-adding it on round trips through > `org-edit-src-code’. > > But `org-src-