From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: device syntax
Date: Thu, 28 Oct 2004 18:59:03 +0000 [thread overview]
Message-ID: <87is8uvfd4.fsf@marco.marco-g.com> (raw)
In-Reply-To: <20041021112630.GA22854@artax.karlin.mff.cuni.cz> (Tomas Ebenlendr's message of "Thu, 21 Oct 2004 13:26:30 +0200")
Tomas Ebenlendr <ebik@artax.karlin.mff.cuni.cz> writes:
> Hmm, and what if there are quotes, or newlines in name? I think that we
> should be able to pass /any/ string to bios/firmware. Question is what
> characters we want to escape. If escaped characters will be e.g. quotes,
> the need of using this will be very little. If we escape commas, many
> names will get horrible. So what about this solution, extended by '\' as
> escaping character, using \" for char '"', \\ for '\' and \xxx for
> nonprintable or other characters?
Escaping is used to remove the meaning of commandline stuff so you can
pass it to commands. And the command line parser does this already.
I think we should not use escaping *ever* for other reasons.
--
Marco
next prev parent reply other threads:[~2004-10-28 17:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 2:14 device syntax Hollis Blanchard
2004-10-20 8:58 ` Marco Gerards
2004-10-20 7:33 ` Tomas Ebenlendr
2004-10-20 9:47 ` Marco Gerards
2004-10-20 10:13 ` Tomas Ebenlendr
2004-10-20 14:14 ` Hollis Blanchard
2004-10-20 14:04 ` Hollis Blanchard
2004-10-20 14:44 ` M. Gerards
2004-10-20 15:22 ` Hollis Blanchard
2004-10-21 10:53 ` Yoshinori K. Okuji
2004-10-21 11:26 ` Tomas Ebenlendr
2004-10-21 11:33 ` Yoshinori K. Okuji
2004-10-28 18:59 ` Marco Gerards [this message]
2004-10-21 14:54 ` Hollis Blanchard
2004-10-28 19:02 ` Marco Gerards
2004-10-29 1:40 ` Hollis Blanchard
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=87is8uvfd4.fsf@marco.marco-g.com \
--to=metgerards@student.han.nl \
--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.