Re: Bug#519535: history expansion: modifier completion missing

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Mar 17,  9:57am, Peter Stephenson wrote:
} Subject: Re: Bug#519535: history expansion: modifier completion missing
}
} On Mon, 16 Mar 2009 19:44:34 -0700
} Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
} > I don't know how the generic quoting code plays in, but I suspect this
} > is done this way *because* history expansion takes place so early.  If
} > it looks like a history expansion and it got this far, then it must be
} > a *failed* history expansion and needs to be quoted if it matches any
} > other completion -- otherwise the history expansion will fail *again*
} > after accept-line, and spoil the whole command.
} 
} That's quite possible. The quote code is hair-raising enough (see
} utils.c around line 4504) that it's quite hard to tell.

Yes, I can see where it might be hard to follow exactly how we come
to be passing through there.  And it certainly looks as if at least
tildes as well as histchars should be getting quoted.  Are the other
backslashes perhaps being added here but removed elsewhere?

} It's being called from multiquote() within callcompfunc() in
} compcore.c, which is called for all top-level completion widgets. The
} commenting in that last function is quite amusing in an infuriating
} sort of way: there are three, and all of them are in blocks marked
} with "#if 0".

Apparently Sven only felt it necessary to remind himself why he did NOT
do things.  There must be some discussion of group numbers lurking in
the list archives.