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

From: Bernt Hansen <bernt@norang.ca>
To: garjola@garjola.net
Cc: emacs-orgmode@gnu.org
Subject: Re: Converting tags to TODO states
Date: Tue, 16 Apr 2019 09:26:16 -0400	[thread overview]
Message-ID: <87pnpm84jr.fsf@norang.ca> (raw)
In-Reply-To: <87mukrwbxu.fsf@pc-117-162.i-did-not-set--mail-host-address--so-tickle-me> (garjola@garjola.net's message of "Mon, 15 Apr 2019 17:00:29 +0200")

garjola@garjola.net writes:

> Hi,
>
> For my GTD implementation with org-mode, I have been using the :next:
> tag for my next actions. I would like now to use a "NEXT" TODO keyword,
> which means that I need to convert all :next: tags with "TODO" headlines
> into "NEXT" headlines without the :next: tag. 
>
> I have *a lot* of org files, so an automatic procedure is needed. Since
> I am not fluent in elisp, I was going to write a python script to do
> this, but maybe there is already a way to do this conversion with
> org-mode itself?
>
> The tricky thing I see with parsing is dealing with the ":" in the case
> of multiple tags (I know how to do this in python, but I don't in
> elisp).
>
> Thanks for any hint you can provide.
>
> Garjola

As this is a one-time change I would just use the agenda and bulk
operations to fix your entries.

If the files already contribute to your agenda (I assume they do) 
you can just run a tag match on :next:

C-c a m next RET

and mark all the entries returned with 

m (repeat for each task)

then add a NEXT todo keyword

B t NEXT RET

and mark all the tasks again

m (repeat for each task)

and remove the :next: tag

B - next RET

and save your files.

HTH,
Bernt

next prev parent reply	other threads:[~2019-04-16 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 15:00 Converting tags to TODO states garjola
2019-04-16 13:26 ` Bernt Hansen [this message]
2019-04-16 16:36   ` garjola

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=87pnpm84jr.fsf@norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=garjola@garjola.net \
    /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).