GRRRR I tried "package update" and package mgr in Emacs kept telling me
that Org 9.3.6 was the latest.  Now I look @ orgmode.org and see 9.3.7 -
I'll try that first
after I figure out how to get that "package" or whatever that thing is to
actually show the latest
versions of packages.

On Sun, Jun 28, 2020 at 5:27 PM Nathan Neff <nathan.n...@gmail.com> wrote:

>
>
> On Sun, Jun 28, 2020 at 4:12 PM Kyle Meyer <k...@kyleam.com> wrote:
>
>> 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).
>>
>
> Thanks - I'm using Org 9.3.6 and I'm getting no matches when using emacs -q
>
> I had some other issues w/regexes and Bastien fixed them in "maint":
>
> https://code.orgmode.org/bzg/org-mode/commit/c0d08b7efe740c17a3eec28984161c05e43da5ef
>
> Is it relatively easy to try org-mode's "maint" version (e.g. just check
> out branch from
> https://code.orgmode.org/bzg/org-mode ?)  I'll try using the "maint"
> version to see what's up.
>
> Thanks,
> --Nate
>
>

Reply via email to