From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Gpr8x-0006m3-E8 for mharc-grub-devel@gnu.org; Thu, 30 Nov 2006 14:00:23 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gpr8v-0006kg-OB for grub-devel@gnu.org; Thu, 30 Nov 2006 14:00:21 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gpr8v-0006k0-5T for grub-devel@gnu.org; Thu, 30 Nov 2006 14:00:21 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gpr8u-0006jj-Tt for grub-devel@gnu.org; Thu, 30 Nov 2006 14:00:20 -0500 Received: from [207.69.195.63] (helo=pop-satin.atl.sa.earthlink.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Gpr8u-0003mo-31 for grub-devel@gnu.org; Thu, 30 Nov 2006 14:00:20 -0500 Received: from user-0vvdf2d.cable.mindspring.com ([63.246.188.77] helo=diesel.unsanctioned.org) by pop-satin.atl.sa.earthlink.net with esmtp (Exim 3.36 #1) id 1Gpr8s-0005mV-00 for grub-devel@gnu.org; Thu, 30 Nov 2006 14:00:18 -0500 From: Hollis Blanchard To: The development of GRUB 2 Content-Type: text/plain Date: Thu, 30 Nov 2006 13:00:11 -0600 Message-Id: <1164913211.4067.46.camel@diesel> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) Content-Transfer-Encoding: 7bit Subject: grub2 accessibility: beeps X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2006 19:00:22 -0000 One topic that I've heard a lot about in the past few weeks is accessibility in grub2. Blind users, who otherwise have various devices like screen readers and brail TTYs, need to be able to interact with the bootloader. This can be as simple as using the PC speaker to beep when GRUB starts, and also to beep differently (e.g. different pitch, or different number of beeps) when highlighting different menu entries. Thanks to Vincent, we already have a PC speaker driver (cool!). However, we lack the ability to trigger it when switching menu entries (without selecting one). The problem boils down to this: menuentry "foo" { linux foo } The commands inside the menuentry block are only executed when the entry is selected, not highlighted. Perhaps the menuentry command could be extended to take an optional beep argument: menuentry "foo" { linux foo } But wouldn't it be better to have something more general? Something like menuentry { title "foo" beep pitch duration } { linux foo } Thoughts? -Hollis