Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Isaac Dupree <id@isaac.cedarswampstudios.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: menu loop (patch)
Date: Sat, 19 Jul 2008 19:45:21 -0400	[thread overview]
Message-ID: <48827C91.8070807@isaac.cedarswampstudios.org> (raw)
In-Reply-To: <20080719233155.GA16216@pina.cat>

Carles Pina i Estany wrote:
> Hello,
> 
> On Jul/19/2008, Isaac Dupree wrote:
>> Carles Pina i Estany wrote:
>>> fast check in KDE: it's looping
>>>
>>> Also, Iceweasel menus are looping here (maybe because it's executed
>>> in KDE and there is some GTK Widget with a different behaviour? I have
>>> no idea)
>> GTK menubar-menus are looping for me.  But I'm not sure about menus that  
>> consist of selecting from a list in a box (maybe some login window?).  I  
>> don't care personally, because my GRUB-lists are not terribly long...  
>> hmm, if you hold down a (arrow) key in GRUB, is there auto-repeat?
> 
> no, there isn't auto-repeat (this is what the patch that we are talking
> does).
> 
> GRUB-lists shouldn't be terrible long, but quite users needs to go from
> the first option to the last option quite often (at least is what i
> see).

is this because tools tend to add options to the *end* of the list -- 
the same way my browser adds bookmarks to the end of the bookmarks menu? 
  That's the situation I find myself really using looping regularly in 
my OS (Firefox, Linux).

It might be worth the effort to add a config option, if there are people 
who have to deal with their boot-menu on a regular basis (are there? 
probably...).  Then if they're like me, they'll want to be able to fix 
its annoying behavior for the future.  So it's worth it for them; and if 
there are a significant number of people like that, the one-time cost of 
*implementing* the option may be worth it.

-Isaac



  reply	other threads:[~2008-07-19 23:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 21:22 menu loop (patch) 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2008-07-20  6:21 chaac
2008-07-20  8:49 ` Carles Pina i Estany
2008-07-22 21:40 ` Robert Millan
2008-08-05  7:15   ` Vesa Jääskeläinen

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=48827C91.8070807@isaac.cedarswampstudios.org \
    --to=id@isaac.cedarswampstudios.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox