RE: FVWM: Erroneous .fvwm2rc parsing

From: <esteffl_at_pbi.net>
Date: Mon, 27 Sep 1999 13:46:09 -0700

  well, I would say that the sh behaviour is a bug:-))

  sometime it is hard to distinguish the bug from the feature... (maybe it
is indeed a bug in fvwmrc parsing, it depends on what behaviour they wanted)

        erik

> -----Original Message-----
> From: jason [mailto:jason_at_sdf.lonestar.org]
> Sent: Monday, September 27, 1999 1:26 PM
> To: Steffl, Erik
> Cc: 'fvwm mailing list'
> Subject: RE: FVWM: Erroneous .fvwm2rc parsing
>
>
>
> Yes, I knew that's what its purpose was. I just didn't expect it to
> apply on a comment line, so I thought it was a bug. This is
> how /bin/sh
> works, e.g.:
>
> #!/bin/sh
> # \
> echo hello
> echo world
>
> produces the ouput:
>
> hello
> world
>
> when executed, since everything on a comment line is ignored.
> I wasn't
> aware that fvwm implements this differently, especially since the way
> /bin/sh implements it seems more natural to me. Oh, well.
> I'm glad to
> hear that it's not a bug. ;-)
>
> -jason
>
>
> On Mon, 27 Sep 1999 esteffl_at_pbi.net wrote:
>
> > Jason,
> >
> > the \ character is often used to `unspecial` the special
> characters, in
> > this case meaning that the new line right after it would
> NOT be considered
> > an end of line - i.e. the next line is basically the same
> line for the
> > purposes of the program that reads the file.
> >
> > it's probably clear enough, but here's an example anyway:
> >
> > first line \
> > second line
> >
> > would be read as one line:
> >
> > first line second line
> >
> > your MenuStyle command is thus commented out.
> >
> > erik
> >
>

--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Sep 27 1999 - 15:49:44 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:38:02 BST