From: chaac@nic.fi
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: menu loop (patch)
Date: Sun, 20 Jul 2008 09:21:47 +0300 (EEST) [thread overview]
Message-ID: <28468376.22461216534908749.JavaMail.chaac@nic.fi> (raw)
"Yoshinori K. Okuji" [okuji@enbug.org] kirjoitti:
> On Saturday 19 July 2008 21:58:09 Robert Millan wrote:
> > On Sat, Jul 19, 2008 at 10:34:46AM -0700, Colin D Bennett wrote:
> > > [...] We could support a setting such as "set menuwrap=1" which
> > > would enable this feature for users who care about it.
> >
> > Isn't this a bit overkill? The time spent adding this config option vastly
> > exceeds any time that could be saved by having or not having menu wrap.
> >
> > > Actually my graphical menu currently *does* wrap around, I guess it
> > > seemed logical to me at the time I wrote the code! 8-) As you can
> > > tell, I am not firmly set on either wrapping or not wrapping.
> >
> > Same here.. my concern with taking arbitrary decisions is, when someone
> > comes later and asks to have it reverted, do we accept the request, and
> > otherwise what rationale do we give her? :-)
>
> Personally, I prefer no wrapping, because it is easier for me to use only
> Up/Down arrow keys, yet locate entries easily. Since I am lazy, I don't want
> to look for Home or End (some keyboards really suck for them!), so when I
> just want to jump to somewhere near to the end, I only keep pushing Down, and
> wait for the cursor to stop. And, this is consistent with Dired mode in
> Emacs, Directory Listing in VIM, and, of course, with GRUB Legacy.
Hi All,
I also like no wrapping mode. But lets assume we have nice graphical menu with "cylinder" of menu entries that roll when you press key up/down. In here it would be really convenient to have wraparound eg. user cant event think any other way here. But this is something I would put into theme configuration file.
Theme could be also loadable for text menu that describes colours and such. We could default to non-wrapping as that has been our way for long time. If user wants to override this in theme then they are free to do so.
In every case I would prefer that home and end keys would go to always to start and to end of the list. Page up/down would rely a bit for wrapping setting so they can clamp to list edges if needed.
Thanks,
Vesa Jääskeläinen
next reply other threads:[~2008-07-20 6:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 6:21 chaac [this message]
2008-07-20 8:49 ` menu loop (patch) Carles Pina i Estany
2008-07-22 21:40 ` Robert Millan
2008-08-05 7:15 ` Vesa Jääskeläinen
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 21:22 Carles Pina i Estany
2008-07-19 15:40 ` Robert Millan
2008-07-19 17:21 ` Carles Pina i Estany
2008-07-19 19:52 ` Robert Millan
2008-07-19 22:12 ` Carles Pina i Estany
2008-07-19 23:26 ` Isaac Dupree
2008-07-19 23:31 ` Carles Pina i Estany
2008-07-19 23:45 ` Isaac Dupree
2008-07-20 4:24 ` Colin D Bennett
2008-07-19 17:34 ` Colin D Bennett
2008-07-19 19:58 ` Robert Millan
2008-07-19 20:31 ` Yoshinori K. Okuji
2008-07-19 22:06 ` Carles Pina i Estany
2008-07-19 22:15 ` Robert Millan
2008-07-19 22:28 ` Colin D Bennett
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=28468376.22461216534908749.JavaMail.chaac@nic.fi \
--to=chaac@nic.fi \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.