From: David Masterson <dsmasterson@outlook.com>
To: Colin Baxter <m43cap@yandex.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Tracking Tags ??
Date: Thu, 24 Jan 2019 01:12:02 +0000 [thread overview]
Message-ID: <DM6PR07MB553290BB4C426126FC7D852AA59A0@DM6PR07MB5532.namprd07.prod.outlook.com> (raw)
In-Reply-To: <87zhrrteo8.fsf@yandex.com> (Colin Baxter's message of "Wed, 23 Jan 2019 18:24:55 +0000")
Colin Baxter <m43cap@yandex.com> writes:
> Hello David,
>>>>>> David Masterson <dsmasterson@outlook.com> writes:
>
> > Anyone have a good method of tracking the Tags that you've use
> > across all of your Org files? Some sort of Tag Index to help you
> > keep track of the tags you've used and where you've used them so
> > that you don't start creating new tags that differ from old ones
> > by (say) capitalization? Or to help you find everything tagged a
> > certain when you're moving to a new tagging style? Perhaps an
> > index where you could keep a note on why and when you created the
> > tag?
>
> > Is there any tools for this? -- David
>
> Maybe I'm old-fashioned, but what's wrong with just using grep?
Hmm. Little old-fashioned myself, but I was thinking of something a
little more integrated with Org. Perhaps something that could populate
an Org table with the Tag information for reference. Just a thought...
--
David
next prev parent reply other threads:[~2019-01-24 1:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 0:53 Tracking Tags ?? David Masterson
2019-01-23 18:24 ` Colin Baxter
2019-01-23 18:46 ` John Kitchin
2019-01-23 19:48 ` Colin Baxter
2019-01-23 20:22 ` John Kitchin
2019-01-23 21:57 ` Ken Mankoff
2019-01-24 1:12 ` David Masterson [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-23 15:17 Anders Johansson
2019-01-24 1:07 ` David Masterson
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=DM6PR07MB553290BB4C426126FC7D852AA59A0@DM6PR07MB5532.namprd07.prod.outlook.com \
--to=dsmasterson@outlook.com \
--cc=emacs-orgmode@gnu.org \
--cc=m43cap@yandex.com \
/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).