`gud-common-init'

[Nick Roberts]

 > As far as I can tell, `gud-common-init' does not try to handle
 > command lines like this:
 > 
 >      --option "enquoted argument with spaces"
 > 
 > If it does, there must be a bug that prevents the above command
 > line from being parsed into arguments correctly.
 > 
 > Is this behaviour not seemed desirable?  Maybe it should be
 > implemented?  (I'm willing to have a try.)

Can you give real example of where this would be needed other than a file
which has spaces in its name. I think that we previously decided not to
encourage this practice.

Nick