Re: `gud-common-init'

[Paul Pogonyshev]

>  > 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.

Actually I tried to debug `etags' with command line

        etags --language none --regex '/^Pattern[ \t]+[a-zA-Z0-9]+/' ...

I agree it's not something you need every day, but it came out as a big
surprise for me when I saw how this command line was passed to `etags'.

Paul