public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Jean Delvare <jdelvare@suse.de>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Michal Marek <mmarek@suse.cz>,
	linux-kbuild@vger.kernel.org,
	Roland Eggner <edvx1@systemanalysen.net>,
	Wang YanQing <udknight@gmail.com>
Subject: Re: Wish: exact matches displayed first
Date: Mon, 6 May 2013 16:27:11 +0200	[thread overview]
Message-ID: <20130506142711.GD3958@free.fr> (raw)
In-Reply-To: <1367849991.4569.108.camel@chaos.site>

Jean, All,

On Mon, May 06, 2013 at 04:19:51PM +0200, Jean Delvare wrote:
> Le Monday 06 May 2013 à 15:53 +0200, Yann E. MORIN a écrit :
> > Thomas, All,
> > 
> > On Mon, May 06, 2013 at 03:04:46PM +0200, Thomas Petazzoni wrote:
> > > On Mon, 6 May 2013 14:54:59 +0200, Yann E. MORIN wrote:
> > > > BTW, did you know that you can search using extended regular expressions?
> > > > Searching for ^PCI$ will yield only the CONFIG_PCI symbol.
> > > 
> > > Wow, I didn't know that. Is this documented/advertised somewhere?
> > 
> > Yes. In Documentation/kbuild/kconfig.txt:
> > 
> >     [...] This will tell you that you can also use
> >     regular expressions (regexes) in the search string, [...]
> 
> Maybe this could be mentioned in the prompt itself, for all the
> ignorants amongst us?

In the search dialog, if you select 'Help', you'll get:

    Search for symbols and display their relations.
    Regular expressions are allowed.
    Example: search for "^FOO"

I guess it being presented in the help text is enough, no? ;-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2013-05-06 14:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06  7:50 Wish: exact matches displayed first Jean Delvare
2013-05-06 10:00 ` Yann E. MORIN
2013-05-06 12:54   ` Yann E. MORIN
2013-05-06 13:04     ` Thomas Petazzoni
2013-05-06 13:53       ` Yann E. MORIN
2013-05-06 14:19         ` Jean Delvare
2013-05-06 14:27           ` Yann E. MORIN [this message]
2013-05-06 14:36             ` Jean Delvare
2013-05-06 14:10     ` Jean Delvare
2013-05-06 13:02 ` [PATCH] kconfig: sort found symbols by relevance Yann E. MORIN
2013-05-06 15:28   ` Jean Delvare
2013-05-06 18:17     ` Yann E. MORIN
2013-05-07  1:35     ` Wang YanQing
2013-05-06 18:20 ` Yann E. MORIN
2013-05-06 19:36   ` Yann E. MORIN
2013-05-06 21:15 ` [PATCH v3] " Yann E. MORIN
2013-05-09 15:27   ` Wang YanQing
2013-05-09 16:12     ` Yann E. MORIN
2013-05-10  0:51       ` Wang YanQing
2013-05-10 10:12         ` Yann E. MORIN

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=20130506142711.GD3958@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=edvx1@systemanalysen.net \
    --cc=jdelvare@suse.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=udknight@gmail.com \
    /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