All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Andreas Vogel <Andreas.Vogel@anvo-it.de>
Subject: Re: Ideas for the future
Date: Mon, 05 Mar 2012 02:40:57 +0100	[thread overview]
Message-ID: <4F5419A9.1080300@gmail.com> (raw)
In-Reply-To: <20120305013504.GW4285@type.famille.thibault.fr>

On 05.03.2012 02:35, Samuel Thibault wrote:
> Vladimir 'φ-coder/phcoder' Serbinenko, le Mon 05 Mar 2012 02:30:11 +0100, a écrit :
>>> 6) menuentry --enabled 0|1
>>> It's a good practice to show menuentries even if they are not applicable
>>> in different situations (that's common for all major menu systems). If a
>>> menu entry is disabled, it is shown but it is not operable. E.g. one
>>> might have a general grub config file which supports booting a bunch of
>>> ISO images. When an ISO image is not found and instead of not showing a
>>> menuentry for that, those menuentry could be shown as disabled.
>> This seems like just cluttering the view. Remember that in some applications
>> (e.g. braille) menu has to be very concise. We support even the tiny (40x1)
>> terminal geometries.
> Actually, 40x1 is relatively large for a braille device. A lot of them
> are 20x1.
20x1 works as well. The bare minimum is 5x1 (we need 4 positions to 
indicate that there are more entries or more chars in the entry).
For less than 20x1  4 special positions become wasteful and the code 
should probably check those explicitly.
Is less than 20x1 common?
> Samuel
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



  reply	other threads:[~2012-03-05  1:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05  1:13 Ideas for the future Andreas Vogel
2012-03-05  1:30 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05  1:35   ` Samuel Thibault
2012-03-05  1:40     ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-03-05  9:23       ` Samuel Thibault
2012-03-05 11:16   ` Andreas Vogel
2012-03-05 12:54     ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 15:43       ` Andreas Vogel
2012-03-08 13:12         ` [BUG] GRUBs option parsing needs fixing Andreas Vogel
2012-03-08 14:15           ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 14:32             ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 15:03               ` Andreas Vogel
2012-03-08 15:18                 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 15:28                   ` Lennart Sorensen
2012-03-08 15:37                     ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 16:11                       ` Andreas Vogel
2012-03-08 15:45                   ` Andreas Vogel
2012-03-10 19:50                     ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-11  0:08                       ` Andreas Vogel
2012-03-11  1:01                         ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-11  1:59                           ` Andreas Vogel
2012-03-11  2:15                             ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 15:25                 ` Lennart Sorensen
2012-03-08 15:58                   ` Andreas Vogel
2012-03-08 15:24           ` Lennart Sorensen
2012-03-08 14:11         ` Ideas for the future Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 15:14           ` Andreas Vogel
2012-03-08 15:18             ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 16:33       ` Andreas Vogel
2012-03-08 14:23     ` Vladimir 'φ-coder/phcoder' Serbinenko

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=4F5419A9.1080300@gmail.com \
    --to=phcoder@gmail.com \
    --cc=Andreas.Vogel@anvo-it.de \
    --cc=grub-devel@gnu.org \
    --cc=samuel.thibault@ens-lyon.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.