Re: Multiple noweb-ref

2023-03-03 Thread Ihor Radchenko
t > about "|" ? I do not feel like being creative with characters here is a good idea. I think that using multiple :noweb-ref+ will be more reliable and surely will not break any existing configs. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <

Re: Multiple noweb-ref

2023-02-26 Thread Théo Maxime Tyburn
Hi Ihor, >> Anyway I tried to hack my way trough it. It seems there are two things >> to do : >> 1) Enable noweb-ref to contain multiple references. >> 2) Accumulate references when using header-args+ or use tags to set the >> value of noweb-ref >> >> I came up with a quick patch for 1): >>

Re: Multiple noweb-ref

2023-02-20 Thread Ihor Radchenko
Théo Maxime Tyburn writes: > What I would like to have, when I expand `<>` is to get all the blocks > under A, and when I expand `<>` I get all the blocks under B. For > now when I expand `<>` I only get the blocks under A that are not under > B. > > Is there a way to do this with the current

Multiple noweb-ref

2023-02-10 Thread Théo Maxime Tyburn
Hi, I have several code blocks that I label using `:noweb-ref label`. I set them for all blocks under a subtree by setting the org property `header-args+` of the root of the subtree to `:noweb-ref label`. Now with this approach, I can't accumulate `noweb-ref` like I could do for tags. I would