From: Carsten Dominik <dominik@uva.nl>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Case-sensitivity in regular expressions and sparse trees for tags
Date: Fri, 19 Sep 2008 08:09:22 +0200 [thread overview]
Message-ID: <94C4587E-8438-49CF-AD0E-EF79D213504C@uva.nl> (raw)
In-Reply-To: <2AAAC35C-C27C-47DC-804E-4B8617B31260@uva.nl>
On Sep 18, 2008, at 5:43 PM, Carsten Dominik wrote:
> Hi Chris,
>
> On Sep 17, 2008, at 9:38 PM, Chris Randle wrote:
>
>> Hi Gerrit
>>
>> Forgive me if I've misunderstood regular expressions in Emacs or
>> Org-mode in some fundamental way!
>>
>> I have some tags which begin "CD" followed by a number. For example
>>
>> * Tagged Heading :CD123:
>>
>> When I ask for a sparse tree of all tags beginning with "CD", I do
>>
>> 'C-c / T'
>>
>> And ask for tags of
>>
>> {^CD.*}
>>
>> This doesn't return any of the tagged headlines, but this does:
>>
>> {^cd.*}
>>
>> Is this a bug, or my misunderstanding? Obviously this is no
>> show-stopper, I just make sure that all my regexp searches are in
>> lower
>> case, but thought I'd check.
>
> It may be a bug, and a misunderstanding.
>
> 1. I do downcase all tage before they are tested in the matcher.
> 2. This seems to indicate that I do want the matching to be case-
> insensitive.
> 3. I do set case-fold-search to nil, which seems to contradict (2)
>
>
> For now, I recommend to write all regexps with lower case letters.
> I need to try to remember why I did not set case-fold-search.
I am pushing a fix today which will mkae sure that tags matching is
truly case insensitive. So that should make your old regexp work again.
- Carsten
prev parent reply other threads:[~2008-09-19 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 19:38 Case-sensitivity in regular expressions and sparse trees for tags Chris Randle
2008-09-18 15:43 ` Carsten Dominik
2008-09-19 6:09 ` Carsten Dominik [this message]
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=94C4587E-8438-49CF-AD0E-EF79D213504C@uva.nl \
--to=dominik@uva.nl \
--cc=dominik@science.uva.nl \
--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
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).