emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Brett Witty <brettwitty@brettwitty.net>
Cc: Org mailing list <emacs-orgmode@gnu.org>
Subject: Re: Normalizing tags
Date: Wed, 03 Sep 2014 09:06:50 +0200	[thread overview]
Message-ID: <m2lhq141yt.fsf@christianmoe.com> (raw)
In-Reply-To: <CANK_Tn8u70RyuavaPvoreqZ94T6a28LESN4QewHn3PJirwJxww@mail.gmail.com>


Brett Witty writes:

> Hi,
>
> Has anyone made a module to normalize tags across your entire setup?

Not that I know of.

> That is if you have "Blog" and "blog" as tags, then you fix it as one
> or the other, or "hint" and "tip" tags being collapsed.
>
> If not, would people be interested in that?

There may not be a lot of demand for it since tags are bounded by colons
and can be easily search-replaced. Of course, a function that flags up
all the possible duplicates and queries you for the preferred form could
be a time-saver.

If you're planning to write one: 

In addition to capitalization ("Blog"/"blog"), it would be useful to
look for English singular/plural ("blog"/"blogs") -- but let the user
beware ("aid" and "aids" may not be the same tag).

People tagging their documents in other languages might find some kind
of pattern-matching option helpful.

What I would find *really* nice, now that Org supports tag groups, is a
function to normalize old documents where entries are tagged with both a
group tag and its members. That is, given

  #+TAGS: { music : classical rock folk }

and a heading like 

  * Woody Guthrie  :music:American:folk:

the function would remove the redundant group tag to yield

  * Woody Guthrie  :American:folk:

Yours,
Christian

      reply	other threads:[~2014-09-03  7:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 22:11 Normalizing tags Brett Witty
2014-09-03  7:06 ` Christian Moe [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=m2lhq141yt.fsf@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=brettwitty@brettwitty.net \
    --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).