emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Gustav Wikström" <gustav.erik@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] [PATCH] Changes to Tag groups - allow nesting and regexps
Date: Sat, 31 Jan 2015 09:41:25 +0100	[thread overview]
Message-ID: <874mr7pcju.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CA+SyOP-Hk+8Yv+T3tHmsCimwCX6ewVog0hqzNt_nDeV_QXMncg@mail.gmail.com> ("Gustav \=\?utf-8\?Q\?Wikstr\=C3\=B6m\=22's\?\= message of "Sun, 25 Jan 2015 12:07:16 +0100")

Hello,

Gustav Wikström <gustav.erik@gmail.com> writes:

> This time I've made some changes in the code. More specifically in how
> tag groups function and would like them to be included in Orgmode.

Thank you.
>
> I suppose an FSF-assignment signature is needed before it can be
> included.

Indeed.

> I'll start with that process if this is something the
> community can agree to include. But until then; please take it for a
> ride.

OK. Some comments follow.

> The changes are listed below:
>
> - Grouptags don't have to be unique on a headline if added with [ ]
>   instead of with { }:
>   ,----
>   | #+TAGS: [ group : include1 included2 ]
>   `----

I'd rather not introduce yet another syntax for group tags. IIUC, the
current one (with curly braces) can be extended. 

Also, I don't get the "have to be unique on a headline" part.

> - Grouptags can have regular expressions as "sub-tags". The regular
>   expressions in the group must be marked up within { }. Example use:
>
>   ,----
>   | #+TAGS: [ Project : {^P@.+} ]
>   `----
>
>   Searching for the tag Project will now list all tags also including
>   regular expression matches for ^P@.+. it is good, for example, if tags
>   for a certain project are tagged with a common project-identifier, i.e.
>   P@2014_OrgTags.

This seems an interesting addition.

> - Nesting grouptags. Allowing subtags to be defined as groups
>   themselves.
>
>   ,----
>   | #+TAGS: [ Group : SubOne(1) SubTwo ]
>   | #+TAGS: [ SubOne : SubOne1 SubOne2 ]
>   | #+TAGS: [ SubTwo : SubTwo1 SubTwo2 ]
>   `----
>
>   Should be seen as a tree of tags:
>   - Group
>     - SubOne
>       - SubOne1
>       - SubOne2
>     - SubTwo
>       - SubTwo1
>       - SubTwo2
>   Searching for "Group" should return all tags defined above.

OK.

>   A new variable is defined `ORG-GROUP-TAGS-MAX-DEPTH' that is used to
>   limit the depth of recursion when expanding tags. It defaults to 2.

I don't think this variable is necessary. However, a check for circular
inclusions would be necessary.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2015-01-31  8:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-25 11:07 [RFC] [PATCH] Changes to Tag groups - allow nesting and regexps Gustav Wikström
2015-01-31  8:41 ` Nicolas Goaziou [this message]
2015-02-19 20:00   ` Gustav Wikström
2015-02-24 16:43     ` Nicolas Goaziou
2015-03-05  1:08       ` Gustav Wikström
2015-03-07 21:51         ` Nicolas Goaziou
2015-03-15 10:17           ` Gustav Wikström
2015-03-16 20:38           ` Gustav Wikström
2015-03-16 21:30             ` Nicolas Goaziou
2015-03-19 21:07               ` Gustav Wikström
2015-03-19 22:43                 ` Nicolas Goaziou
  -- strict thread matches above, loose matches on Subject: below --
2015-11-25  7:50 sgeorgii .
2015-11-25 10:26 ` Gustav Wikström
2015-11-25 11:05   ` sgeorgii .
2015-11-25 12:20     ` Gustav Wikström
2015-11-25 12:58       ` Nicolas Goaziou
2015-11-25 14:44         ` Gustav Wikström
2015-11-25 14:52           ` Nicolas Goaziou
2015-11-25 15:39             ` Gustav Wikström
2015-11-26  7:30               ` sgeorgii .
2015-11-26  8:21               ` Nicolas Goaziou
2015-11-26 10:01                 ` Gustav Wikström
2015-11-26 10:21                   ` Nicolas Goaziou

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=874mr7pcju.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=gustav.erik@gmail.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).