From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: advice: how to export a list without exporting all entries
Date: Thu, 24 Mar 2011 19:12:55 +0000 [thread overview]
Message-ID: <87fwqc5o3s.fsf@ucl.ac.uk> (raw)
In-Reply-To: <5E6F4851-F46B-42DB-9260-320244D45A77@gmail.com> (Carsten Dominik's message of "Thu, 24 Mar 2011 16:19:23 +0100")
Carsten Dominik <carsten.dominik@gmail.com> writes:
[...]
>
> Hi Eric,
>
> I guess you could use one of the export hooks to clean up your
> exported file when you are done. However, the problem will always
> be that if you take a list environment, the numbering of the list
> items will change when you take out items. An I am sure you know
> from experience how nice it is to be able to talk about the number
> of an action item, in order to get everyone on the same page
> quickly. I am afraid it will be hard to achieve this with the
> path you are thinking about.
Yes, I am coming to that conclusion as well!
> Defining and tracking action items through a series of meetings where
> I have to do the notes is a frequent tasks for me. Here is my workflow
> for this - maybe you can pick and choose some stuff for yourself.
> In particular, I use outline nodes for tasks, in order to keep access
> to the machinery Org gives me for tracking stuff.
Thanks for the *very* detailed workflow. Fantastic and I think it would
work well with my mode of operation. I guess I was too stuck in the
/list/ mode and didn't even think of using outline nodes. I don't mind
numbering them manually as we're talking about tens of actions over
several years (typically <10 per meeting with 3 meetings per year for
each individual "committee"). But, in any case, your code looks like
even this bit is easily automated.
What will work particularly well in my workflow will be the
todo-state-tag trigger part which I had not even realised could be done
(silly of me, of course ;-). Tying the =closed= tag to the export
exclusion is so obvious in hindsight.
Again, many thanks for this and for your code as well. I'll be
implementing it like right now!
eric
PS - your whole workflow description might be very useful on Worg...
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.113.g9010a.dirty)
next prev parent reply other threads:[~2011-03-24 19:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 9:16 advice: how to export a list without exporting all entries Eric S Fraga
2011-03-23 17:29 ` Nicolas
2011-03-24 8:55 ` Eric S Fraga
2011-04-01 16:26 ` Nicolas
2011-04-01 16:52 ` Eric S Fraga
2011-04-01 20:20 ` Nicolas
2011-03-24 15:19 ` Carsten Dominik
2011-03-24 19:12 ` Eric S Fraga [this message]
2011-03-24 20:45 ` Eric S Fraga
2011-03-24 21:00 ` Carsten Dominik
2011-03-28 18:46 ` Carsten Dominik
2011-03-29 6:39 ` Eric S Fraga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fwqc5o3s.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).