bug with spaces in regexp search

bug with spaces in regexp search

[Samuel Wales]

With the headline "********* text search much faster than tag search"
and an agenda text search:

  {faster than} does not return it
  {faster\ than} also

I think of {...} as a single token even if it has spaces in it.

Thanks.

Samuel


Settings:

  (setf org-agenda-search-view-always-boolean t)
  (setf org-agenda-search-view-force-full-words t)

-- 
Q: How many CDC "scientists" does it take to change a lightbulb?
A: "You only think it's dark." [CDC has denied a deadly serious
disease for 25 years]
==========
Retrovirus: http://www.wpinstitute.org/xmrv/index.html -- PLEASE DONATE
===
I would like to see the original Lo et al. 2010 NIH/FDA XMRV paper.

Re: bug with spaces in regexp search

[Noorul Islam]

On Thu, Sep 23, 2010 at 2:06 AM, Samuel Wales <samologist@gmail.com> wrote:
> With the headline "********* text search much faster than tag search"
> and an agenda text search:
>
>  {faster than} does not return it
>  {faster\ than} also
>
> I think of {...} as a single token even if it has spaces in it.
>
> Thanks.
>
> Samuel
>
>
> Settings:
>
>  (setf org-agenda-search-view-always-boolean t)
>  (setf org-agenda-search-view-force-full-words t)
>

I have both these variables set as nil and search works.

This is what I did.

In org agenda buffer. I typed M-x org-search-view and then typed in
"faster than" which displayed the expected result.

release_7.01h-555-g90cc
Org-mode version 7.01trans (release_7.01h.555.g90cc)
GNU Emacs 23.1.1 (i686-pc-linux-gnu, GTK+ Version 2.12.12) of
2010-01-30 on noorul

Thanks and Regards
Noorul

Re: bug with spaces in regexp search

[Samuel Wales]

Meaning?

Re: bug with spaces in regexp search

[Noorul Islam K M]

Samuel Wales <samologist@gmail.com> writes:

> Meaning?

I meant,

I have both these variables set as nil

org-agenda-search-view-always-boolean
org-agenda-search-view-force-full-words

and then in org agenda buffer. I typed M-x org-search-view and then
typed in "faster than" which displayed the expected filtered result.

I am running

Org-mode version 7.01trans (release_7.01h.555.g90cc)
GNU Emacs 23.1.1 (i686-pc-linux-gnu, GTK+ Version 2.12.12) of
2010-01-30 on noorul

Does that make it clear?

Thanks and Regards
Noorul

Re: bug with spaces in regexp search

[Carsten Dominik]

On Sep 22, 2010, at 10:36 PM, Samuel Wales wrote:

> With the headline "********* text search much faster than tag search"

Is that so?

> and an agenda text search:
>
>  {faster than} does not return it
>  {faster\ than} also

Either of these should now (after pulling) do the trick.

Cheers

- Carsten

>
> I think of {...} as a single token even if it has spaces in it.
>
> Thanks.
>
> Samuel
>
>
> Settings:
>
>  (setf org-agenda-search-view-always-boolean t)
>  (setf org-agenda-search-view-force-full-words t)
>
> --  
> Q: How many CDC "scientists" does it take to change a lightbulb?
> A: "You only think it's dark." [CDC has denied a deadly serious
> disease for 25 years]
> ==========
> Retrovirus: http://www.wpinstitute.org/xmrv/index.html -- PLEASE  
> DONATE
> ===
> I would like to see the original Lo et al. 2010 NIH/FDA XMRV paper.
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: bug with spaces in regexp search

[Samuel Wales]

Why is that important?

Re: bug with spaces in regexp search

[Samuel Wales]

Thanks, Carsten.  :)

On 2010-09-22, Carsten Dominik <carsten.dominik@gmail.com> wrote:
> On Sep 22, 2010, at 10:36 PM, Samuel Wales wrote:
>
>> With the headline "********* text search much faster than tag search"
>
> Is that so?

Yes, by an order of magnitude.

Re: Re: bug with spaces in regexp search

[David Maus]

[-- Attachment #1.1: Type: text/plain, Size: 282 bytes --]

Samuel Wales wrote:
>Why is that important?

Noorul tried to reproduce the bug, but couldn't.  Trying to reproduce
a reported bug is (sometimes) important for the developers.

Best,
  -- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de

[-- Attachment #1.2: Type: application/pgp-signature, Size: 230 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: bug with spaces in regexp search

[Samuel Wales]

The bug has been fixed, so the following is moot.

Ah, but he didn't .  :)  Hence my question.  :)

I appreciated the effort to help, but I was wondering what he was
trying to say, because he used strings instead of regexps and he used
different settings for both variables.  The bug was with regexps (i.e.
{...}) and not strings.

In other words, he did not attempt to reproduce the bug, but instead
changed 3 conditions back to a known-working state.  It was not a
surprise that it worked.  :)

But, again, I appreciated the effort to help.

I was unable to type more than a few words at the time I asked.  I
hope this clarifies conclusively.

Re: Re: bug with spaces in regexp search

[Samuel Wales]

In other words, I was wondering why he reported the failure to
reproduce a bug that I did not report on.

Perhaps he had some other point he was making.  Or perhaps he was
confused about what the bug was.

Hence my question.

Re: bug with spaces in regexp search

[Noorul Islam K M]

Samuel Wales <samologist@gmail.com> writes:

> The bug has been fixed, so the following is moot.
>
> Ah, but he didn't .  :)  Hence my question.  :)
>
> I appreciated the effort to help, but I was wondering what he was
> trying to say, because he used strings instead of regexps and he used
> different settings for both variables.  The bug was with regexps (i.e.
> {...}) and not strings.
>

I tried to reproduce it and I think I missed the regexp part. I am sorry
about that. 

> In other words, he did not attempt to reproduce the bug, but instead
> changed 3 conditions back to a known-working state.  It was not a
> surprise that it worked.  :)
>
> But, again, I appreciated the effort to help.
>
> I was unable to type more than a few words at the time I asked.  I
> hope this clarifies conclusively.

Your one liner reply to the mail confused me and I again typed in the
same thing. If you could have typed in the first paragraph in this mail
as your initial reply I could have tried with regexp.

Since now that Carsten has fixed the bug and it has not been ignored
because of my mistake, I think you are happy.

Thanks and Regards
Noorul