From: Pavel Machek <pavel@suse.cz>
To: euphoria@inbox.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: losing a menuconfig session to a typo
Date: Tue, 16 Dec 2008 22:10:10 +0100 [thread overview]
Message-ID: <20081216211009.GA2041@ucw.cz> (raw)
In-Reply-To: <CCCA86B6E10.000005AEeuphoria@inbox.com>
On Mon 2008-12-15 13:03:28, euphoria@inbox.com wrote:
> It's easy to accidentally lose a menuconfig session. Scenarios start with a
> user being accustomed to hitting [right-arrow][return] to exit from a typical
> menu. Perhaps the user prefers his underutilized numeric keypad over adding to
> the beating [escape] takes. Scenarios finish with the user accidentally
> issuing [right-arrow][return] to "Do you wish to save? <Yes> <No>". I only
> lost a quick change, but it's easy to imagine how a few hours of menuconfig
> time might go away. "It'll just take a few minutes to whip my distro's kernel
> into shape." Yeah right. Four hours of guesswork and research later, you're
> tired, thinking about the make command to follow, [right-arrow][return] as
> usual, wait! no! damndamndamn!, yer snookered.
>
> There are a variety of simple ways to address this. First, change the menu.
> Swapping the order of the <Yes> and <No> would be begging for even more
> trouble. However, the <Yes>/<No> decision could be made a <Yes>/<Maybe>/<No>
> decision. This leaves <Yes>, the predominant choice, in place. <Maybe>, in
> the disputed position, could simply present the same menu. Someone might even
> have a little well-deserved fun with <Maybe> menus. This doesn't
seem all that
Too ugly to live. But maybe periodically saving config to
.config.autosave once in 5 minutes...?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2008-12-17 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 21:03 losing a menuconfig session to a typo euphoria
2008-12-16 21:10 ` Pavel Machek [this message]
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=20081216211009.GA2041@ucw.cz \
--to=pavel@suse.cz \
--cc=euphoria@inbox.com \
--cc=linux-kernel@vger.kernel.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