From: Jude DaShiell <jdashiel@panix.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gentoo handbook
Date: Mon, 12 Oct 2020 02:47:02 -0400 [thread overview]
Message-ID: <alpine.NEB.2.23.451.2010120245410.25171@panix1.panix.com> (raw)
In-Reply-To: <1593e821-2614-2dc9-9edd-0ce4e6645b71@whjeon.com>
On Mon, 12 Oct 2020, WooHyung Jeon wrote:
> Date: Sun, 11 Oct 2020 21:30:59
> From: WooHyung Jeon <dev@whjeon.com>
> Reply-To: gentoo-user@lists.gentoo.org
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] gentoo handbook
>
> On 2020-10-11 ?? 8:55, Dale wrote:
> > Neil Bothwick wrote:
> >> On Sat, 10 Oct 2020 22:09:00 -0400, Jude DaShiell wrote:
> >>
> >>> A feature that would be useful for menuconfig would be the ability once
> >>> a search is done to jump onto the desired search item directly (if the
> >>> item were available at all).
> >> That's already there. Options that are available have a number next to
> >> them. Press that to jump to the option.
> >>
> >>
> >
> >
> > Wow!!! O_O I never noticed that. It works too. I did a search for speak
> > and saw a number next to the results and hit it, 1 in my case, and it went
> > right to it. I'm not going to mention how many times I went digging to find
> > something in the past. It embarrassing. ;-)
> >
> > Now that is cool. I just hope I remember to use it the next time. :/
> >
> > Dale
> >
> > :-) :-)
>
> Just watch out and read carefully where you landed on.
> It could take you to the dependent option, before the specific
> one. For example, even if you searched 'A' and select the number
> left-side of 'A', it could land on option 'B' because it must
> enabled before you can play with 'A'.
>
> I surprised twice. First, as you did, when I first noticed I
> can select with the number, and Secondly, when I noticed it
> sometimes didn't bring me to the specified option :)
>
--
Didn't read about any of this in the handbook, probably some material on
inside menuconfig might be where this stuff could go.
next prev parent reply other threads:[~2020-10-12 6:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 2:09 [gentoo-user] gentoo handbook Jude DaShiell
2020-10-11 11:30 ` Ashley Dixon
2020-10-11 15:38 ` Jude DaShiell
2020-10-11 11:40 ` Neil Bothwick
2020-10-11 11:55 ` Dale
2020-10-11 16:52 ` John Covici
2020-10-11 17:05 ` Jude DaShiell
2020-10-12 1:30 ` WooHyung Jeon
2020-10-12 6:47 ` Jude DaShiell [this message]
2020-10-24 8:41 ` Paul Ezvan
-- strict thread matches above, loose matches on Subject: below --
2020-11-14 18:48 Jude DaShiell
2020-11-14 19:46 ` antlists
2020-11-14 22:15 ` Rich Freeman
2020-11-15 12:45 ` Michael
2020-11-15 14:34 ` Jude DaShiell
2020-11-15 15:46 ` Michael
2020-11-15 18:54 ` Neil Bothwick
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=alpine.NEB.2.23.451.2010120245410.25171@panix1.panix.com \
--to=jdashiel@panix.com \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox