All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Reinauer <stepan@coresystems.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: slight oddity in script parser
Date: Fri, 01 Aug 2008 06:26:35 +0200	[thread overview]
Message-ID: <4892907B.8020204@coresystems.de> (raw)
In-Reply-To: <ca0f59980807312123t1c1093b3t1a5839b8b533c925@mail.gmail.com>

Bean wrote:
> On Fri, Aug 1, 2008 at 7:48 AM, Patrick Georgi <patrick@georgi-clan.de> wrote:
>   
>> Hi,
>>
>> I forgot this, so sorry for the separate mail:
>> Currently, the parser expects comments to start at the beginning of the
>> line, so "ls /foo # necessary because of baz" doesn't work properly
>>
>> I think a good scenario would be to have comments start either on "#" at
>> pos0, or on " #". This way, ls /foo#bar continues to work.
>>
>> Also, currently the following is a single comment, which is an unusual
>> feature:
>> # this comment starts here\
>> and continues on this line
>>     
>
> Hi,
>
> Actually, # and \ is handled in the read line function, it can't
> handle complicated situation.
>   

Are you implying it is wrong there and should be moved to the parser?


-- 
coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br.
      Tel.: +49 761 7668825 • Fax: +49 761 7664613
Email: info@coresystems.de  • http://www.coresystems.de/
Registergericht: Amtsgericht Freiburg • HRB 7656
Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866




  reply	other threads:[~2008-08-01  4:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 23:48 slight oddity in script parser Patrick Georgi
2008-08-01  4:23 ` Bean
2008-08-01  4:26   ` Stefan Reinauer [this message]
2008-08-01  4:34     ` Bean
2008-08-01  4:42       ` Stefan Reinauer
2008-08-01  4:47         ` Bean
2008-08-01 10:32           ` Marco Gerards
2008-08-01 10:48             ` Bean
2008-08-01 15:23               ` Marco Gerards
2008-08-01 13:44       ` Robert Millan
2008-08-01 14:17         ` Patrick Georgi

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=4892907B.8020204@coresystems.de \
    --to=stepan@coresystems.de \
    --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.