FVWM: bug in configuration file parsing

From: William L. Sebok <wls_at_astro.umd.edu>
Date: Fri, 6 Aug 1999 15:38:53 -0400 (EDT)

Both fvwm 2.2.2 and fvwm 2.3.5 do not recognize tokens that are surrounded by
double quotes which contain embedded spaces. In particular the line:

MenuStyle midnightblue "light blue" midnightblue "-adobe-new century schoolbook-*-i-*-*-14-*-*-*-*-*-*-*" fvwm

generates:

[FVWM][nocolor]: <<ERROR>> can't parse color light
  and
[GetFontOrFixed]: WARNING -- can't get font -adobe-new, trying 'fixed'[FVWM][scanForPixmap]: <<WARNING>> Couldn't find pixmap height

As system manager of the UMD astronomy department, this bug is a show stopper,
making me unable to upgrade past the current fvwm (2.046). For the past number
of years I have been handing out a .fvwmrc with the above line to new users and
thus upgrading fvwm would now break most users' desktops.

If double quotes won't protect a token from being broken up then what is the
use for double quotes? I can substitute LightBlue for "light blue" but there
is no getting around that some font names have embedded spaces.

Bill Sebok Computer Software Manager, Univ. of Maryland, Astronomy
        Internet: wls_at_astro.umd.edu URL: http://www.astro.umd.edu/~wls/
--
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 Fri Aug 06 1999 - 14:40:09 BST

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