From: Kyle Meyer <firstname.lastname@example.org>
To: Marcin Borkowski <email@example.com>
Cc: Org-Mode mailing list <firstname.lastname@example.org>
Subject: Re: How to enhance the agenda output if soome info is only in the parent entry?
Date: Sun, 07 Dec 2014 17:45:55 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Marcin Borkowski's message of "Sun, 07 Dec 2014 23:09:44 +0100")
Marcin Borkowski <email@example.com> wrote:
> On 2014-12-07, at 22:37, Kyle Meyer wrote:
>> What about assigning categories?
> Thanks a lot! I found it in the manual right after sending my email:-(.
> It still violates DRY, but I guess it's the best I can come up with; I
> think I'll use it
True. For a handful of cases, this seems like an ok approach to
distinguish tasks from different subtrees, but it would get tedious if
that pattern occurs frequently across your agenda.
> (even though I don't really like it - I prefer my
> categories to be /very/ broad, corresponding to /files/ - think
> "research", "personal", "teaching" etc. It's just a habit of mine,
> though, and I allow myself to change these from time to time;-).
Yes, I prefer broad categories too, so that makes sense to me.
next prev parent reply other threads:[~2014-12-07 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 21:22 How to enhance the agenda output if soome info is only in the parent entry? Marcin Borkowski
2014-12-07 21:37 ` Kyle Meyer
2014-12-07 22:09 ` Marcin Borkowski
2014-12-07 22:45 ` Kyle Meyer [this message]
2014-12-08 3:39 ` Eric Abrahamsen
2014-12-08 9:05 ` Marcin Borkowski
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).