From: adrian15 <adrian15sgd@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: echo gives internal error with \n
Date: Fri, 03 Aug 2007 19:55:16 +0200 [thread overview]
Message-ID: <46B36C04.6070101@gmail.com> (raw)
In-Reply-To: <878x98fu19.fsf@xs4all.nl>
Marco Gerards escribió:
> adrian15 <adrian15sgd@gmail.com> writes:
>
>> I've activated the echo command (also the pause command) which it is
>> equivalent to the echo command... and have done some tests:
>
> The problem is in the parser.
I see.
>> Two conclusions from these tests:
>>
>> 1) When you use \n in string that does not begin with " then it gives an
>> internal error. I do not see anything special on echo.c so I suppose
>> it's the fault of the parser, however I have not studied the parser
>> yet... so marco_g what's your opinnion?
>
> True, Bean sent in a patch to fix this.
:) I knew this already.
>
>> 2) The -e option is not implemented. :) I've checked the code and it is
>> not. However I doubt if it's going to work... I ask myself if the grub>
>> string always appears at the beginning of the line.
>
> Do you want to implement this? ;-)
>
> This should not be hard to do.
Implementation is easy but what's difficult for me is the design decision.
Here there are three possible scenarios:
1a) When grub> is showed it does begin in the last character position
(not in a new line).
This might imply rewriting the end of the programs so that they end
with something similar to: grub_printf("\n");
1b) Same than 1a but the execution of the last grub_printf("\n"); is
automatically run from the "program than runs one command after another
one. (I do not know the name in grub2.)" depending on a new special flag
of the program.
2) The echo command with a -e option sets a variable which is checked
each time the grub> line is going to be written. Depending on the
variable grub_printf("\ngrub>"); or grub_printf("grub>"); is run.
At what implementation were you thinking to issue this problem?
>
>> pause is equivalent to echo command but if you want to check what I am
>> saying check my other email that contains a patch for having both echo
>> and pause commands.
Well... I think you do not need to check my patch... the idea is that
pause command is the echo command plus a pause. Something like:
pause.sh:
echo $@ ; read
exit
So the pause command can have all the echo command power.
I also might work in the read command although I have to think more
about it.
adrian15
prev parent reply other threads:[~2007-08-03 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 11:13 echo gives internal error with \n adrian15
2007-07-22 13:27 ` Marco Gerards
2007-08-03 17:55 ` adrian15 [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=46B36C04.6070101@gmail.com \
--to=adrian15sgd@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.