All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carles Pina i Estany <carles@pina.cat>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: var=foo should be valid?
Date: Mon, 30 Nov 2009 14:48:56 +0100	[thread overview]
Message-ID: <20091130134856.GA328@pinux.info> (raw)
In-Reply-To: <20091130093949.GA6439@riva.ucam.org>


Hello,

On Nov/30/2009, Colin Watson wrote:
> On Sun, Nov 29, 2009 at 06:45:03PM +0000, Carles Pina i Estany wrote:
> > On Nov/29/2009, Carles Pina i Estany wrote:

> (I don't know what the bug you're referring to is; both 'foo=bar' and
> 'set foo=bar' seem to work OK here. I may be missing some subtle
> problem, but if I'm missing it then users will too.)

the problem is easy to fix and I already have the fix ready (either fix
the current the bug or delete the var=foo feature) (well, as I said,
maybe we can re-implement the way that it's implemented now, but we can
discuss it later)

The bug is that if a module hooks into a variable (e.g. gettext does,
grub_register_varaible_hook) and then the user changes the value of the
variable using lang=newlang, the function that gets called is executed
but grub_errno is 16 (I think that was 16). Because I use grub_file_open
and grub_file_open is not working if grub_errno != 0 (no error) when
it's called then the gettext module cannot translate the strings using
the new language.

(I'm talking about the gettext module but potentially can affect other
modules of course)

-- 
Carles Pina i Estany
	http://pinux.info



  reply	other threads:[~2009-11-30 13:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-29 18:39 var=foo should be valid? Carles Pina i Estany
2009-11-29 18:45 ` Carles Pina i Estany
2009-11-29 18:50   ` Carles Pina i Estany
2009-11-30  9:39   ` Colin Watson
2009-11-30 13:48     ` Carles Pina i Estany [this message]
2009-12-04 21:16     ` Robert Millan
2009-12-04 21:21 ` Robert Millan
2009-12-04 21:55   ` Carles Pina i Estany
2009-12-12  0:04     ` Carles Pina i Estany
2009-12-13 12:45       ` Carles Pina i Estany

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=20091130134856.GA328@pinux.info \
    --to=carles@pina.cat \
    --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.