emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Adam Spiers <orgmode@adamspiers.org>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: proposal: defconst/defcustom org-tags-regexp
Date: Mon, 16 Jul 2007 14:21:18 +0100	[thread overview]
Message-ID: <20070716132118.GA28297@atlantic.linksys.moosehall> (raw)

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

next             reply	other threads:[~2007-07-16 13:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16 13:21 Adam Spiers [this message]
2007-07-18 21:24 ` proposal: defconst/defcustom org-tags-regexp Carsten Dominik
2007-07-19 13:08   ` Eddward DeVilla
2007-07-19 15:08     ` Carsten Dominik
2007-07-19 16:14       ` Eddward DeVilla
2007-07-20 15:05   ` Adam Spiers
     [not found]     ` <931245f7aaa24436377e537552f1beab@science.uva.nl>
2007-09-01 11:01       ` Adam Spiers
2007-09-02  7:30         ` Carsten Dominik

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=20070716132118.GA28297@atlantic.linksys.moosehall \
    --to=orgmode@adamspiers.org \
    --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

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).