emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Victor A. Stoichita" <victor@svictor.net>
To: chris <inkbottle007@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-tag-persistent-alist AND per-file dynamic tags
Date: Thu, 09 Dec 2021 20:35:05 +0100	[thread overview]
Message-ID: <87mtl9ft1f.fsf@svictor.net> (raw)
In-Reply-To: <5046398.lFmPd3n6S9@pluto>

Hi Chris,

Le 29 Nov 2021, chris <inkbottle007@gmail.com> a écrit :

> I use footnote 53 from https://orgmode.org/manual/Setting-Tags.html[1].
> I put my tags in `tags-file.org`, using `#+TAGS:`.
> I've put the next two lines in `init.el`.
> (setq org-agenda-files (list "~/path-to/tags-file.org")
>          org-complete-tags-always-offer-all-agenda-tags t)
> And I have completion on both the tags in `tags-file.org` and tags in
> the current buffer. I don't use `org-tag-alist`, so the comments made
> in https://emacs.stackexchange.com/q/ 69369#comment111307_69369[2],
> would not apply.

That’s great! It’s exactly what I needed. I’ll just switch my persistent
tags from org-tag-alist to an agenda file. This is also neater as it
will get them out of my init files, where I didn’t feel that they
really belonged.

> I use a script to collect the tags, based on Kitchin's https://stackoverflow.com/a/27527252[3], and help from `#emacs`.
> […]
> The tags are sorted by frequency, which is not necessary
> here, but it's really nice.
> […]

Thanks for this as well! It’s nice to have it. For the moment, I curate
manually these "persistent" tags, because i want to have them grouped
hierarchically. But knowing how to collect them automatically might be
useful for me as well in the future!


      reply	other threads:[~2021-12-09 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-06  9:10 org-tag-persistent-alist AND per-file dynamic tags Victor A. Stoichita
2021-11-29  3:49 ` chris
2021-12-09 19:35   ` Victor A. Stoichita [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:

  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=87mtl9ft1f.fsf@svictor.net \
    --to=victor@svictor.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=inkbottle007@gmail.com \


* 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).