emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Nathan Neff <nathan.neff@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Using regular expressions in custom agenda views
Date: Sun, 28 Jun 2020 17:12:11 -0400	[thread overview]
Message-ID: <87366ec2tw.fsf@kyleam.com> (raw)
In-Reply-To: <CAC=HedAu3o-wG=AB6NLyyqBaoR1QJ4gDn9KPeTrJvX=P8_rhFw@mail.gmail.com>

Nathan Neff writes:

> I'm having a difficult time using regular expressions in custom
> "tags-todo" agenda views.
>
> Is it possible to create custom agenda views using regular expressions,
> and if so, do I need to escape certain characters?
>
> I can't get a simple regex like this to work, so I'm suspecting that
> I'm doing something wrong or, it's simply not possible to create custom
> agenda views that use regular expressions to search for tags.
>
> For example, this expression doesn't even find headings with :projectA:
> as a tag
>
>   (setq org-agenda-custom-commands
>   '(
>      ("1" tags-todo "{projectA}")))

My understanding is that the above should work.  I tried your
org-agenda-custom-commands value with this agenda file:

    * TODO a                                                           :projectA:
    * TODO b                                                           :projectB:
    * TODO c                                                           :project:

With an otherwise vanilla configuration and master (0c1740c91) checked
out, I see

    Headlines with TAGS match: {projectA}
    Press ‘C-u r’ to search again
      scratch:    TODO a                                                                  :projectA:

I see the same thing on maint (3ed035ce3).


  reply	other threads:[~2020-06-28 21:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-28 20:05 Using regular expressions in custom agenda views Nathan Neff
2020-06-28 21:12 ` Kyle Meyer [this message]
2020-06-28 22:27   ` Nathan Neff
2020-06-28 22:28     ` Nathan Neff
2020-06-28 22:39       ` Nathan Neff
2020-06-28 22:48         ` Nathan Neff
2020-06-28 22:54           ` Nathan Neff

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=87366ec2tw.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nathan.neff@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).