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 minor mode enabled, these are syntax highlighted, and when I export a document they come out as todo notes in latex. I can run a command to see a list of all of these in a document, and for a big document like a proposal or report, there would be none at the end when it is done. It is a work in progress, and probably the 3rd such annotation solution I have tried. It is the best so far though, and I feel is pretty close to what I want. Fraga, Eric <e.fr...@ucl.ac.uk> writes: > On Saturday, 2 Nov 2019 at 14:01, alain.coch...@unistra.fr wrote: >> You also said that you had "already moved to using drawers for a large >> number of [your] inline task use cases, the ones that weren't really >> tasks!". Is this consistent with your "almost completely" above? >> This leads me to the question of what precisely _defines_ a "task"; > > Good question! I guess, for me, a task is one that will appear in my > agenda so has a TODO state (possibly) and/or scheduling/deadline > information. But the distinction is rather blurry. > > So, in fact, when I am working on a long document, I have tasks of the > "must improve this section" type which are not tasks for scheduling (the > whole document is itself a task) or "notes" for processing later (by > myself or by others involved in the same document). I use drawers for > these types of activities. I then use the export formatting options to > make the pseudo-tasks and notes appear differently in the exported > output, whether for sharing or for printing/display. So, for instance, > I look for ":todo:" and ":note:" drawers. > > If the document I am working on is a coursework or test, I use drawers > for storing the solutions, e.g. a drawer called ":solution:"! For this, > for instance, I have the following elisp in the document that is invoked > when I open the document: > > #+begin_src emacs-lisp > (setq-local org-latex-format-drawer-function > (lambda (name contents) > (cond ((string= name "solution") > (format "\\begin{mdframed}\\paragraph{Solution.} > %s\\end{mdframed}" contents)) > (t (format "\\textbf{%s}: %s" name contents)) > ))) > #+end_src > > together with > > #+latex_header: \usepackage[backgroundcolor=yellow!10!white]{mdframed} > > to make the solution stand out clearly. > > The nice thing about drawers is I can turn them on or off for exporting > via the "d:" document option: > > HTH, > eric -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu