All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Device instability, gettext and default
Date: Mon, 05 Mar 2012 13:37:52 +0100	[thread overview]
Message-ID: <4F54B3A0.5020607@gmail.com> (raw)
In-Reply-To: <4F54A8B6.2010604@anvo-it.de>

On 05.03.2012 12:51, Andreas Vogel wrote:
> Am 05.03.2012 01:34, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
>> On 05.03.2012 01:20, Andreas Vogel wrote:
>>> Am 05.03.2012 01:03, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
>>>>> options? Any special reason?
>>>> 2) Why do you refuse to allow short options for all of the menuentry
>>>> Because it shares the space with options to menuentry.
>>> Don't understand what you mean. What is shared?
>> menuentry "title" hello {
>>     echo $1; sleep 10
>> }
> I'm really sorry, but i still don't understand.... and I'd really like
> to understand it.
>
> Why is it OK for the menuentry command to accept long options but not OK
> to accept short options? What is the difference here handling long
> options opposed to handling short options?
The menuentry itself might want to define options on its own. Space of 
long options is large enough to easily avoid conflicts but the space of 
short ones isn't.
>
>
>
>


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



      reply	other threads:[~2012-03-05 12:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 13:37 Device instability, gettext and default Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-03 14:27 ` Jordi Mallach
2012-03-03 14:51 ` Andreas Vogel
2012-03-03 15:06   ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-03 19:48 ` Andreas Vogel
2012-03-03 20:04   ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-03 20:08 ` Andreas Vogel
2012-03-03 20:10   ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-04 23:51 ` Andreas Vogel
2012-03-05  0:03   ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05  0:20     ` Andreas Vogel
2012-03-05  0:34       ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 11:51         ` Andreas Vogel
2012-03-05 12:37           ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]

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=4F54B3A0.5020607@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.