[bug-enscript] [bug #31012] enscript seg faults while processing the config file

[Bruce Korb]

Follow-up Comment #3, bug #31012 (project enscript):

1.6.5.2 fixes this issue.  However, you probably should
process --help and --version args before processing
config files, and perhaps describe what's wrong with
the config file when you do process it.  I did, after all,
read the man page when constructing the file.  I read this:

       All other lines are option lines and have format:
       option [arguments ...].
       The following options can be specified:
       AcceptCompositeCharacters: bool
               Specify whether PostScript font's composite characters are
               accepted  as  printable or if they should be considered as
               non-existent.  The default value is false (0).

and interpreted it to mean putting the colon after the name
as a value separator.  The parser ought to tolerate a colon,
an equal sign or just white space as the name/value separator.

$ enscript --help
enscript:/vmem/bkorb/.enscriptrc:2: missing argument: Media:
$ enscript --version
enscript:/vmem/bkorb/.enscriptrc:2: missing argument: Media:
$ rm -f ~/.enscriptrc ; enscript --version
GNU Enscript 1.6.5.2 [...]

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?31012>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/