From: Martin Leduc <ldcmrtn@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Tags management strategies
Date: Sat, 14 May 2016 22:48:32 -0400 [thread overview]
Message-ID: <nh8o20$cr6$1@ger.gmane.org> (raw)
Hi !
Tags are a very useful feature to filter information in org-mode. After
few years of developing a system to organize my life with org-mode, I
realize that tags can become rather difficult to deal with as we tend to
define a lot of tags spread out over several org files.
One general issue is to track all the tags that you have defined in all
your org files. Rather than requesting an org-mode feature that would
make a dynamical list of all the defined tags, I personally prefer the
approach of making a static list of all preferred tags in one place and
to try to keep this list as small as I can. I can achieve this by
defining a global list of tags through the variable "org-tag-alist",
which allows to access all the tags from any of my org files, and also
because it allows to make "grouptags" which are very convenient to
organize tags by themes.
The latter approach seems however limited to the use of a rather small
number of tags since in the fast-tag-selection interface, tags entries
beyond the 33th are marked with extended ASCCI characters such as ^?,
\200, \201,... So my first question is how can I access these tags, and
if it is possible, what is the physical limit in terms of the number of
tags I can define and access ?
My second question is a bit more general, but I would like to know what
peoples are currently doing to manage, track and make an efficient use
of their numerous tags.
Many thanks,
Martin
next reply other threads:[~2016-05-16 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 2:48 Martin Leduc [this message]
2016-05-16 19:59 ` Tags management strategies 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='nh8o20$cr6$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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.