All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] normal/cmdline.c : history contains empty lines
Date: Sun, 19 Dec 2004 16:15:26 +0100	[thread overview]
Message-ID: <200412191615.26966.okuji@enbug.org> (raw)
In-Reply-To: <41BE9159.7010500@yahoo.fr>

On Tuesday 14 December 2004 08:08, Vincent Pelletier wrote:
> 2004-12-13 Vincent Pelletier <subdino2004@yahoo.fr>
> * grub_history_get : doesn't add empty lines, exits if called with
> NULL argument
> * grub_cmdline_get : command is added to history after user hit
> "return", when pressing "down" arrow when on the most recent item in
> history an empty line is shown

I agree that empty lines should not be added into the history, but I 
don't think it is a good idea to show an empty line when you go down 
the history. Because I really like to have compatibility with BASH.

I don't know how the current implementation behaves very well, but it 
should work in the same way as GRUB legacy. It should be like this:

PROMPT        HISTORY
grub>         []
foo[RET]
grub>         ["foo"]
bar[RET]
grub>         ["foo", "bar"]
[RET]
grub>         ["foo", "bar"]
[C-p]
grub> bar     ["foo", "bar"]
[C-n]
grub>         ["foo", "bar"]
[C-p]
grub> bar     ["foo", "bar"]
baz[RET]
grub>         ["foo", "bar", "barbaz"]

Okuji



  reply	other threads:[~2004-12-19 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14  7:08 [PATCH] normal/cmdline.c : history contains empty lines Vincent Pelletier
2004-12-19 15:15 ` Yoshinori K. Okuji [this message]
2004-12-19 15:46   ` Vincent Pelletier
2004-12-19 15:59     ` Yoshinori K. Okuji
2004-12-29 19:31 ` Marco Gerards
2004-12-29 19:49   ` Vincent Pelletier
2004-12-29 21:06     ` Marco Gerards

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=200412191615.26966.okuji@enbug.org \
    --to=okuji@enbug.org \
    --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.