i use comments, sometimes with self-highlighted /emphasis/ or
self-highlighted fixme, or demote to a standard "x" task and use tasks
one level above.
if it is exportable, then i use non-task entries as the thing to
export and do not export any tasks. this works pertty well.
on rare occasions i
"Fraga, Eric" writes:
> Mind you, an alternative could be #+CALL-ing a src block
> that generates the text as output?
On these lines: I've been thinking recently that it would be great to be
able to tangle/export other kinds of blocks (quotes, examples, etc.) via
the same kind of mechanism that
I have been exploring the use of something I call editmarks for this
(https://github.com/jkitchin/scimax/blob/master/scimax-editmarks.org).
They are light-weight markups I usually use for commenting org
documents, and they look like this.
{>~ @jk this is a comment~<}
{>*This is a task*<}
with
the include route seems brittle to me, as you have to name the file
you are in. this would be interesting:
#+include: {{{input-file}}}::#yada-quote
(i have a bug in org more recent than a pretty old version so idk if
this is already possible.)
On 11/4/19, Richard Lawrence wrote:
> "Fraga,
Along the lines of what Eric suggested, you can put inline calls to
src-blocks in the text. Here are some ways you could get something like
what you describe I think.
* text to be included
:noexport:
#+name: block-1
#+BEGIN_SRC python :results value :var a="a" b="b"
return f"<<{a} {b} c>>"
On Sunday, 3 Nov 2019 at 12:37, Samuel Wales wrote:
> ah, or do you mean you refer the reader to the text by a regular link
> instaed of including? that's not what i am lokoing for here as these
> are separate posts.
Yes, this is what I meant, in case the adjusted use case were of some
use.
