From: Andreas Vogel <Andreas.Vogel@anvo-it.de>
To: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
Colin Watson <cjwatson@ubuntu.com>
Subject: Re: Ideas for the future
Date: Mon, 05 Mar 2012 17:33:33 +0100 [thread overview]
Message-ID: <4F54EADD.8070104@anvo-it.de> (raw)
In-Reply-To: <4F54B78B.9010707@gmail.com>
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 is set, the terminal box
>>>> will not be shown by default when the entry is executed. Execution of
>>>> submenus should be always silent.
>>> Rather than removing messages better move them to some status bar in
>>> the theme.
>> You didn't get the point. Why should any terminal box open when there is
>> nothing to display?
> I think you don't get mine: if this message goes to status bar it
> doesn't go to the terminal and so it doesn't open.
There are *no* messages at all when executing such entries. No need for
any terminal box or status bar. No messages are removed or need to be
directed to anywhere, because there are no messages, not even one single
character of output. A menuentry flagged as --silent will not produce
any output, never ever. It might produce errors and in this case the
terminal box is opened and the error is shown as it is the case in the
current version.
Anyway, I tried to check out your proposal at least... where can i find
the code handling a status bar?
Andreas
next prev parent reply other threads:[~2012-03-05 16:33 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
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 [this message]
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=4F54EADD.8070104@anvo-it.de \
--to=andreas.vogel@anvo-it.de \
--cc=cjwatson@ubuntu.com \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.com \
/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.