From: Sam Ravnborg <sam@ravnborg.org>
To: Shlomi Fish <shlomif@iglu.org.il>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.20-rc3] qconf Search Dialog
Date: Wed, 3 Jan 2007 22:05:35 +0100 [thread overview]
Message-ID: <20070103210535.GA31780@uranus.ravnborg.org> (raw)
In-Reply-To: <200701032201.28384.shlomif@iglu.org.il>
On Wed, Jan 03, 2007 at 10:01:28PM +0200, Shlomi Fish wrote:
>
> Interesting. I didn't notice this search dialog before because its menu item
> was placed in the "File" menu, which is the wrong place for a find command
> (Which should be in an "Edit" or "Search" menu). I believe others have missed
> it as well. Also, it is possible it wasn't available when I wrote the
> preliminary version of the patch back in March.
>
> Aside from that my search dialog has some advantages:
>
> 1. Full text search - if you search for "available" in File->Search you won't
> find anything. Searching for it in Edit->Find will find many things. I think
> File->Search only searches using the identifiers or at most also the title.
>
> 2. Regular expression search.
>
> 3. Displaying the results in a tree, with their context.
>
> All that said, I don't mind merging my modifications into the existing code,
> or replacing it entirely.
Please merge the best of the existing and the new search dialog.
I would prefer it as separate smaller steps.
So one patch where you move the dialog and another where you improve
the search dialog.
Sam
next prev parent reply other threads:[~2007-01-03 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 17:54 [PATCH 2.6.20-rc3] qconf Search Dialog Shlomi Fish
2007-01-03 17:54 ` Randy Dunlap
2007-01-03 20:01 ` Shlomi Fish
2007-01-03 21:05 ` Sam Ravnborg [this message]
2007-01-05 10:44 ` Shlomi Fish
2007-01-05 19:51 ` Randy Dunlap
2007-01-06 3:13 ` Roman Zippel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070103210535.GA31780@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=shlomif@iglu.org.il \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox