From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: beep support?
Date: Fri, 05 Feb 2010 19:24:55 +0100 [thread overview]
Message-ID: <4B6C6277.7090600@gmail.com> (raw)
In-Reply-To: <20100205181118.GE5621@const.c.hospitality.swisscom.com>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
Samuel Thibault wrote:
> Vladimir 'φ-coder/phcoder' Serbinenko, le Fri 05 Feb 2010 17:52:02 +0100, a écrit :
>
>> Could you detail at which events beep should be produced and propose a
>> patch to add appropriate hooks?
>>
>
> A beep just when the menu is first drawn is already a good thing and is
> trivial to add by just calling play in the main menu.
>
> An additional very useful hook would be when browsing between items:
> giving a play file name for each different menu entry for instance.
>
What do you think about a syntax like this:
menuentry "blah bla" {
...
} onselect {
play abcd
}
> Samuel
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2010-02-05 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 13:09 beep support? Samuel Thibault
2010-02-02 14:09 ` Felix Zielcke
2010-02-02 16:04 ` Samuel Thibault
2010-02-02 23:00 ` Samuel Thibault
2010-02-05 16:52 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-02-05 18:11 ` Samuel Thibault
2010-02-05 18:24 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-02-05 18:28 ` Samuel Thibault
2010-02-05 18:28 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-02-05 18:35 ` Samuel Thibault
2010-02-14 18:09 ` Samuel Thibault
2010-02-16 12:48 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-02-07 21:54 ` Samuel Thibault
2010-02-14 0:19 ` Samuel Thibault
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=4B6C6277.7090600@gmail.com \
--to=phcoder@gmail.com \
--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.