From: Jude DaShiell <jdashiel@panix.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gentoo handbook
Date: Sun, 11 Oct 2020 13:05:01 -0400 [thread overview]
Message-ID: <alpine.NEB.2.23.451.2010111301440.29528@panix1.panix.com> (raw)
In-Reply-To: <m3362k66y5.wl-covici@ccs.covici.com>
On Sun, 11 Oct 2020, John Covici wrote:
> Date: Sun, 11 Oct 2020 12:52:34
> From: John Covici <covici@ccs.covici.com>
> Reply-To: gentoo-user@lists.gentoo.org
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] gentoo handbook
>
> On Sun, 11 Oct 2020 07:55:46 -0400,
> Dale wrote:
> >
> > [1 <text/plain; ISO-8859-1 (8bit)>]
> > 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. :/
>
> I didn't know that either and have been doing this for years!
>
>
--
If nothing else at least three of us learned something useful today.
I suppose the shortest way to explain what I did extra before running make
menuconfig was to emerge espeakup. Having done that espeakup emerged
about 35 packages many of which it likely would need. I'm pretty sure
that step was correct, what if anything else to do after that before make
menuconfig I don't yet know.
next prev parent reply other threads:[~2020-10-11 17:05 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 [this message]
2020-10-12 1:30 ` WooHyung Jeon
2020-10-12 6:47 ` Jude DaShiell
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.2010111301440.29528@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