From: amscopub-mail@yahoo.com
To: emacs-orgmode@gnu.org
Subject: Re: Automatic global tag list?
Date: Tue, 23 Nov 2010 09:59:56 -0800 (PST) [thread overview]
Message-ID: <754893.88649.qm@web120711.mail.ne1.yahoo.com> (raw)
In-Reply-To: <A704FE45-1022-42F0-8B02-9B71C88A4B4A@gmail.com>
I just want to keep tag names consistent across files and I want to know what tags are in use in all files as I add a tag. However, it's too tedious to manually maintain org-tag-alist because I use a large and arbitrary number of tags at any given time.
It would also be great if there was a way to list all tags in global use. (I'm thinking something like a tag cloud here.)
BTW, where is the documentation? I'm using orgmode 7.03, perhaps it's not documented there?
U Avalos
--- On Tue, 11/23/10, Carsten Dominik <carsten.dominik@gmail.com> wrote:
> From: Carsten Dominik <carsten.dominik@gmail.com>
> Subject: Re: [Orgmode] Automatic global tag list?
> To: "Uriel Avalos" <amscopub-mail@yahoo.com>
> Cc: emacs-orgmode@gnu.org
> Date: Tuesday, November 23, 2010, 11:50 AM
>
> On Nov 23, 2010, at 4:45 PM, Uriel Avalos wrote:
>
> > On Tue, 23 Nov 2010 06:52:34 +0100
> > Carsten Dominik <carsten.dominik@gmail.com>
> wrote:
> >
> >>
> >> On Nov 23, 2010, at 1:30 AM, Uriel Avalos wrote:
> >>
> >>> Is there a way to auto-magically construct the
> global tag list (org-
> >>> tag-alist)?
> >>> That is, tags would get added to the global
> list as you add them.
> >>>
> >>> Alternatively, is there a way to construct the
> global list of all tags
> >>> in use (in the agenda files or given set of
> files)?
> >>
> >> There is the function
> `org-global-tags-completion-table' which will
> >> construct this list for the agenda files or for
> any other list of
> >> files you are giving it. For each of these
> files it will at the tags
> >> defined in #+TAGS: lines as well as any other tags
> being used in that
> >> file.
> >>
> >> HTH
> >>
> >> - Carsten
> >>
> >
> > Thanks for the reply. However, I'm afraid that I'm not
> (yet) a lisp
> > programmer. What would the definition of such a
> function look like?
> > This function seems to be undocumented.
>
> The function is there, and it is documented. But I
> think they key question is: what you you want to do
> with the list of tags. If you tell us, maybe you can
> get an answer!
>
> - Carsten
>
>
next prev parent reply other threads:[~2010-11-23 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101122193057.6e59460camscopub-mail@yahoo.com@dove.localdomain>
2010-11-23 5:52 ` Automatic global tag list? Carsten Dominik
2010-11-23 15:45 ` Uriel Avalos
[not found] ` <20101123104500.6275e344amscopub-mail@yahoo.com@dove.localdomain>
2010-11-23 16:50 ` Carsten Dominik
2010-11-23 17:59 ` amscopub-mail [this message]
2010-11-24 5:01 ` Matt Lundin
2010-11-24 8:38 ` Sébastien Vauban
2010-11-25 1:35 ` Uriel Avalos
2010-11-23 0:30 Uriel Avalos
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=754893.88649.qm@web120711.mail.ne1.yahoo.com \
--to=amscopub-mail@yahoo.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).