From: Christopher Suckling <firstname.lastname@example.org>
To: Carsten Dominik <email@example.com>
Cc: org-mode mailing list <firstname.lastname@example.org>,
Christopher Suckling <email@example.com>
Subject: Re: [PATCH] fast tag selection interface
Date: Wed, 18 Feb 2009 22:50:08 +0000 [thread overview]
Message-ID: <43D95BBE-1B97-4194-BA31-5FFBC7362E13@gmail.com> (raw)
On 17 Feb 2009, at 21:00, Carsten Dominik wrote:
> On Feb 16, 2009, at 1:15 AM, Christopher Suckling wrote:
>> As a result of the 40 variables thread and assorted worg tutorials,
>> I'm getting a little carried away with customising my workflow.
>> Consequently, my tag list have grown to the extent that the fast
>> tags selection interface is looking rather messy.
>> The small patch below adds the capability to create arbitrary new
>> lines, either by adding "\n" (backslash n, not a newline!) to your #
>> +TAGS: or by adding "(:newline . nil)" to org-tag-alist.
>> So I can have something like:
>> [a] @assorted [g] @gtd [c] @contexts
>> [o] other [r] relevant [t] tags
>> [m] more [f] for [d] different [p] projects
> I am not convinced that this helps a lot. Do ou really think
> it is much better?
It's a tiny thing; my tags setup had got messy so I added it! I don't
think it's much better, but it works for my situation (perhaps I
should change my workflow than the tool...)
> The patch looks good and complete! Do you have a copyright
> assignment with the FSF? Not absolutely necessary for
> this small a patch, but still...
Assignment form requested...
next prev parent reply other threads:[~2009-02-18 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 0:15 Christopher Suckling
2009-02-17 21:00 ` Carsten Dominik
2009-02-18 22:50 ` Christopher Suckling [this message]
[not found] ` <B2AEFB22-36E9-4FF0-A8F8-F360718FF11E@uva.nl>
2009-02-27 18:40 ` Christopher Suckling
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).