From: Martin Leduc <ldcmrtn@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Tags management strategies
Date: Tue, 31 May 2016 15:20:41 -0400 [thread overview]
Message-ID: <niko6a$7hc$1@ger.gmane.org> (raw)
In-Reply-To: <2016-05-17T13-59-11@devnull.Karl-Voit.at>
On 05/17/2016 08:23 AM, Karl Voit wrote:
> David Weinberger
Hi Karl,
Thank you so much for these interesting resources. I've read your
technique for tagging files and folders and must admit that it's quite
impressing. I would love to implement such kind of a system one day
along with my GTD set-up, but I'm unfortunately lacking time for such a
project at the moment.
I found your suggestion of using file-specific tags very interesting
because it simplifies a lot of things. For example, rather than using
grouptags in a global list, I can use file-specific tags. That way each
file can represent a specific context, with a group of tags associated
with it. Used along with capture templates, this can become powerful, as
I can press C-q and then TAB to display an ordered list of all tags
related to that context.
Using file-specific tags allowed me to simplify my org-tag-alist to 5
tags (HOME,WORK,MAIL,CALL,READ), which can be added to any file-specific
list without any problems since, as you said, context-related lists of
tags overlap rather vaguely.
David Weinberger's book seems interesting. This is in agreement with
Samuel Wales suggestion (see the other response to my first post) to
make an extensive use of regexp searches (I need to invest some time for
this).
At first I thought I was asking a simple and naive question about tags.
Thanks for opening this interesting Pandora's box.
Martin
prev parent reply other threads:[~2016-05-31 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 2:48 Tags management strategies Martin Leduc
2016-05-16 19:59 ` Samuel Wales
2016-05-19 19:59 ` Martin Leduc
2016-05-19 20:03 ` Samuel Wales
2016-05-17 12:23 ` Karl Voit
2016-05-31 19:20 ` Martin Leduc [this message]
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='niko6a$7hc$1@ger.gmane.org' \
--to=ldcmrtn@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).