All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: regression in hiddenmenu (Re: [2158] 2009-05-02 Bean <bean123ch@gmail.com>)
Date: Sun, 28 Jun 2009 16:52:07 +0200	[thread overview]
Message-ID: <20090628145207.GA7184@thorin> (raw)
In-Reply-To: <87r5x48o56.fsf@xs4all.nl>

On Sun, Jun 28, 2009 at 03:48:53PM +0200, Marco Gerards wrote:
> Hi,
> 
> Robert Millan <rmh@aybabtu.com> writes:
> 
> > This commit accidentally broke "hiddenmenu" functionality
> > (http://grub.enbug.org/Hiddenmenu).  Instead of displaying the sleep
> > prompt without clearing the screen, and then clearing the screen and
> > drawing the menu, it first clears the screen, draws the menu and then
> > displays the sleep prompt.
> >
> > I haven't followed much on what this change does;  if I understood
> > correctly, the scripting engine has been moved to a module (sh.mod),
> > which due to asciibetical order is processed after normal.mod, which
> > seems to be the cause for this problem.
> >
> > I can suggest a few possible solutions:
> >
> >   - Rename either (kludge! kludge!)
> >
> >   - Put sh.mod back in kernel.
                           ^^^^^
I think I got it wrong;  sh.mod was moved out of normal.mod, it's never
been in kernel AFAICT.

> Why was it moved out?  Is there any good reason for this?  I could
> have missed the discussion, I am quite busy lately...

Actually I missed that discussion too, I hope someone will explain.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-06-28 14:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1M0LDL-0007Vc-4D@cvs.savannah.gnu.org>
2009-06-28 12:35 ` regression in hiddenmenu (Re: [2158] 2009-05-02 Bean <bean123ch@gmail.com>) Robert Millan
2009-06-28 13:48   ` Marco Gerards
2009-06-28 14:52     ` Robert Millan [this message]
2009-06-28 14:59       ` Bean
2009-06-29 13:50         ` Robert Millan

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=20090628145207.GA7184@thorin \
    --to=rmh@aybabtu.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.