From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [RFC] [PATCH] Changes to Tag groups - allow nesting and regexps Date: Sat, 31 Jan 2015 09:41:25 +0100 Message-ID: <874mr7pcju.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41474) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHTbK-0002fp-J9 for emacs-orgmode@gnu.org; Sat, 31 Jan 2015 03:40:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YHTbH-0002rL-E2 for emacs-orgmode@gnu.org; Sat, 31 Jan 2015 03:40:22 -0500 Received: from relay6-d.mail.gandi.net ([2001:4b98:c:538::198]:43842) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHTbH-0002rH-7b for emacs-orgmode@gnu.org; Sat, 31 Jan 2015 03:40:19 -0500 In-Reply-To: ("Gustav \=\?utf-8\?Q\?Wikstr\=C3\=B6m\=22's\?\= message of "Sun, 25 Jan 2015 12:07:16 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Gustav =?utf-8?Q?Wikstr=C3=B6m?= Cc: Org Mode List Hello, Gustav Wikstr=C3=B6m 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.=20 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, --=20 Nicolas Goaziou