On 08.03.2012 16:14, Andreas Vogel wrote:
Am 08.03.2012 15:11, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
On 05.03.2012 16:43, Andreas Vogel wrote:
Am 05.03.2012 13:54, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
option with an optional argument. By this we would have had what you
prefe
Am 08.03.2012 15:11, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
> On 05.03.2012 16:43, Andreas Vogel wrote:
>> Am 05.03.2012 13:54, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
option with an optional argument. By this we would have had what you
preference and my way too. Regarding
On 05.03.2012 12:16, Andreas Vogel wrote:
if [ "feature" = unavail ] ; then
set hidden=1
else
set hidden=0
fi
menuentry "Boot memtest86" --hidden $hidden { ... }
for looks nicer opposed to
if [ "feature" = unavail ] ; then
set hidden="--hidden
On 05.03.2012 16:43, Andreas Vogel wrote:
Am 05.03.2012 13:54, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
option with an optional argument. By this we would have had what you
preference and my way too. Regarding optional arguments the option
handling in GRUB is actually broken by design, so
Am 05.03.2012 13:54, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
5) menuentry --silent 0|1
When using menuentries which just sets some variables or do some other
(non booting tasks), it's really bothering to see a flickering empty
terminal box just for nothing. When this flag
Am 05.03.2012 13:54, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
>> option with an optional argument. By this we would have had what you
>> preference and my way too. Regarding optional arguments the option
>> handling in GRUB is actually broken by design, so this is,
>> unfortunately, not an op
(CC'ing Colin because of theme stuff and it overlaps with what he needs
for Ubuntu)
By this it would be possible
to use a quite generic theme.txt file for different resolutions, etc.
This is already possible. Use percent notation for desired size and
BTW, another point which might be address
Am 05.03.2012 02:30, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
>> this works already. For submenus this doesn't work as the submenu
>> entries are not re-evaluated after execution of it's menuentries.
>> Example:
>> set lang=us
>> menuentry 'Boot with lang=$lang' { ... ; linux lang=$
Vladimir 'φ-coder/phcoder' Serbinenko, le Mon 05 Mar 2012 02:40:57 +0100, a
écrit :
> 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
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).
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
On 05.03.2012 02:13, Andreas Vogel wrote:
I took the last few nights to divide my previously submitted huge patch
into logical parts (around 10 patches now). Some of them I've submitted
already.
So right now it seems to me that it's useless to waste your time (and my
time too) to submit more pat
I took the last few nights to divide my previously submitted huge patch
into logical parts (around 10 patches now). Some of them I've submitted
already.
So right now it seems to me that it's useless to waste your time (and my
time too) to submit more patches or even to discuss them due to code
fre
13 matches
Mail list logo
