From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Spiers Subject: proposal: defconst/defcustom org-tags-regexp Date: Mon, 16 Jul 2007 14:21:18 +0100 Message-ID: <20070716132118.GA28297@atlantic.linksys.moosehall> Reply-To: Adam Spiers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IAQVt-00019k-J3 for emacs-orgmode@gnu.org; Mon, 16 Jul 2007 09:21:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IAQVt-00019U-1N for emacs-orgmode@gnu.org; Mon, 16 Jul 2007 09:21:21 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IAQVs-00019Q-W0 for emacs-orgmode@gnu.org; Mon, 16 Jul 2007 09:21:21 -0400 Received: from mail.beimborn.com ([70.84.38.100]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IAQVs-00012s-LY for emacs-orgmode@gnu.org; Mon, 16 Jul 2007 09:21:20 -0400 Received: from mail.beimborn.com (localhost.localdomain [127.0.0.1]) by mail.beimborn.com (8.12.11.20060308/8.12.8) with ESMTP id l6GDLJqf002191 for ; Mon, 16 Jul 2007 08:21:19 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by mail.beimborn.com (8.12.11.20060308/8.12.11/Submit) id l6GDLJVB002185 for emacs-orgmode@gnu.org; Mon, 16 Jul 2007 14:21:19 +0100 Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: org-mode mailing list Hi again, There seem to be a number of hardcoded regexps currently used for matching heading tags, all very similar looking, and typically something like: [ \t]*\\(:[[:alnum:]_@:]+:\\)?[ \t]*\\($\\|\r\\) Is there any reason why these shouldn't be factored out into a new defcustom org-tags-regexp? Not only would this make for more reliable code as per the DRY principle, but it would also some new possibilities: It seems a lot of people are already using "@" as a tag prefix to indicate GTD contexts, which the code currently allows, and is a nice way of keeping distinct tag "namespaces". Additionally I would like to have tags to denote time estimates for actions: <10min i.e. it's a 10 minute job worst case <30min i.e. it's a half an hour job worst case <60min etc. <120min <4hrs <1day (currently, the "<" prefix confuses the code); and maybe something else, like "+" to prefix tags which denote actions forming part of a bigger picture e.g. "+health" for any actions/projects related to living more healthily (less elisp hacking and more sunlight might be a good start ;-) Thanks, Adam