On 2025-03-27 17:13, pinmacs wrote:
Maybe we can use similar idea and allow users to list the affiliated
keywords (or regexps matching the keyword names) to keep. Then, after
updating the dynamic block, if some affiliated keywords have been
removed, they are re-added. WDYT?
3/5 I think that's bet
5 inline replies
On 2025-03-16 13:18, Ihor Radchenko wrote:
pinmacs writes:
Maybe we can arrange Org to leave manually added affiliated keywords as
is when updating the dblock, similar to what colview does.
Another idea is https://list.orgmode.org/orgmode/871qaer7bo.fsf@localhost/
2/4
Regre
pinmacs writes:
>> Maybe we can arrange Org to leave manually added affiliated keywords as
>> is when updating the dblock, similar to what colview does.
>>
>> Another idea is https://list.orgmode.org/orgmode/871qaer7bo.fsf@localhost/
>
> 2/4
> Regretably I could not try the patch, is it because I
4 inline replies:
On 2025-03-15 19:39, Ihor Radchenko wrote:
pinmacs writes:
There is a special case that might need a clarification in the orgmode
implementation and/or the org-syntax [0]
The affiliated keyword, when it's before a dynamic block [1] it does not
work.
Example:
#+NAME: test
pinmacs writes:
> There is a special case that might need a clarification in the orgmode
> implementation and/or the org-syntax [0]
>
> The affiliated keyword, when it's before a dynamic block [1] it does not
> work.
>
> Example:
>
> #+NAME: test
> #+BEGIN: something-that-generates-a-table
> |
Hi orgmode folks,
There is a special case that might need a clarification in the orgmode
implementation and/or the org-syntax [0]
The affiliated keyword, when it's before a dynamic block [1] it does not
work.
Example:
#+NAME: test
#+BEGIN: something-that-generates-a-table
| State | ID | Ta
