From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Wales Subject: Re: How to move from inline tasks to drawers? [was: How to change the width of a latex exported inlinetask?] Date: Mon, 4 Nov 2019 13:30:07 -0700 Message-ID: References: <23997.32316.900106.897373@frac.u-strasbg.fr> <871rupax29.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:44588) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iRj6Q-00042M-Ow for emacs-orgmode@gnu.org; Mon, 04 Nov 2019 15:37:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iRj6P-0005Zx-5m for emacs-orgmode@gnu.org; Mon, 04 Nov 2019 15:37:30 -0500 Received: from mail-lj1-x242.google.com ([2a00:1450:4864:20::242]:41213) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iRj6O-0005ZP-Tt for emacs-orgmode@gnu.org; Mon, 04 Nov 2019 15:37:29 -0500 Received: by mail-lj1-x242.google.com with SMTP id m9so19144667ljh.8 for ; Mon, 04 Nov 2019 12:37:28 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: John Kitchin Cc: emacs-orgmode@gnu.org, "Alain.Cochard@unistra.fr" 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 use inline tasks, but i have not gotten used tot hem. a long time ago, i catalogued a bunch ofthings needing fixing in inline tasks tomaket hem more complete as an org feture, but couldn't fix them so didn't post. i guess i sort of didn't develop the habit becuase i didnt' remember which features can be relied on. maybe they have all been fixed by now. idk. On 11/4/19, John Kitchin wrote: > 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 writes: > >> On Saturday, 2 Nov 2019 at 14:01, Alain.Cochard@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 > > -- The Kafka Pandemic What is misopathy? https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html The disease DOES progress. MANY people have died from it. And ANYBODY can get it at any time.