Re: [RFA] 12843

[Tom Tromey <tromey@redhat.com>]

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

Tom> I am not sure how to handle file names with quotes; IIUC typical
Tom> escaping syntax won't work because it is already used in DOS-style file
Tom> names.  This matters since I think MI clients already have to play funny
Tom> games here :-(

Eli> Can we standardize on quoting with ".." instead?

I don't think so, because that is already accepted by linespec, so
compatibility problems apply.

Eli> If we must use '..' style quoting, then how about doubling the ' to
Eli> express a literal quote character?

It would work for me.

Tom> Furthermore I think that quoted text should always be a token: we should
Tom> not try to extend the token boundaries or break the token up.  That is:
Tom> Valid:    break 'file.c':function
Tom> Invalid:  break 'file.c:function'
Tom> Invalid:  break 'file'.c:function

Eli> What about these:

Eli>  break 'file with spaces.c:function:with:colons'
Eli>  break 'file with spaces.c':'function:with:colons'

Eli> ?  Do you propose just the latter to be valid?

Yes, just the latter.

The former would attempt to find a function with the quoted name,
following the "quoted text is a single token" rule.

Tom