From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Alain.Cochard@unistra.fr
Cc: emacs-orgmode@gnu.org
Subject: Re: How to use case sensitive org-search-view?
Date: Tue, 14 Nov 2017 21:35:22 +0100 [thread overview]
Message-ID: <87shdgzjhx.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87efp1vsuq.fsf@fastmail.fm> (Matt Lundin's message of "Tue, 14 Nov 2017 08:26:53 -0600")
Hello,
Matt Lundin <mdl@imapmail.org> writes:
> Alain.Cochard@unistra.fr writes:
>
>> Hello. Sorry about this seemingly basic question, but I spent several
>> hours (literally) googling and experimenting without any progress...
>>
>> Suppose I have an org file with
>>
>> * FOO * foo
>>
>> I would like to use org-search-view (C-c a s) so as to (say) list
>> only the first entry.
>>
>> Among other things I tried using +FOO, +"FOO", +{FOO}, +{\bFOO\b},
>> with case-fold-search being t or nil, with several emacs+org
>> versions, but each time it lists both headlines.
>>
>> Is there a way to perform what I want?
>
> Unfortunately, it looks like org-search-view is hard-coded to be
> case-insensitive. I think a very hackish workaround would be to advise
> org-search-view to create and then remove an "around" advice that
> wraps re-search-forward in a "let" declaration setting
> case-fold-search to nil. But this would be a fairly horrific hack.
>
> In the long run, I believe the Org Mode code would need to be changed
> to make this customizable.
Note that there is `org-occur-case-fold-search'.
We could implement something similar with, e.g.,
`org-agenda-search-view-case-fold-search'. Or maybe use a variable for
every search related function in Org: `org-case-fold-search'.
WDYT?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-11-14 20:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 14:04 Confused about the explanation for 'org-cycle' Alain.Cochard
2017-09-19 5:08 ` Matt Lundin
2017-09-20 10:57 ` Nicolas Goaziou
2017-09-26 8:54 ` Alain.Cochard
2017-09-26 10:41 ` Nicolas Goaziou
2017-09-26 12:48 ` Alain.Cochard
2017-09-28 13:44 ` org-list-empty-line-terminates-plain-lists removed but still mentioned in the manual Alain.Cochard
2017-09-28 14:07 ` Nicolas Goaziou
2017-09-28 14:31 ` Confused about the explanation for 'org-cycle' Nicolas Goaziou
2017-09-28 15:29 ` Robert Horn
2017-09-28 16:10 ` Kyle Meyer
2017-09-28 16:17 ` Eric S Fraga
2017-09-28 21:04 ` Alain.Cochard
2017-09-28 21:22 ` Josiah Schwab
2017-09-28 21:30 ` Nicolas Goaziou
2017-10-05 8:17 ` Alain.Cochard
2017-11-10 17:23 ` How to use case sensitive org-search-view? Alain.Cochard
2017-11-14 14:26 ` Matt Lundin
2017-11-14 15:30 ` Alain.Cochard
2017-11-14 20:35 ` Nicolas Goaziou [this message]
2017-11-14 20:55 ` Tim Cross
2017-11-15 14:02 ` Nicolas Goaziou
2017-11-15 21:14 ` Tim Cross
2017-11-16 10:05 ` Alain.Cochard
2017-11-15 10:49 ` Alain.Cochard
2017-11-15 11:55 ` Nicolas Goaziou
2017-11-15 12:35 ` Alain.Cochard
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=87shdgzjhx.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=Alain.Cochard@unistra.fr \
--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).