Chet Ramey wrote:
I can't reproduce this with bash-4.4, even when setting `direxpand' before performing completion on a pathname beginning with `../'. It is possible that you or your vendor compiled bash with directory expansion enabled by default (--enable-direxpand-default), which turns this on.
--- Bingo. I checked the build script and it's set to 'on'. Not sure how it got that way, but I'm going to have trouble walking w/both feet in mouth... Still not recovered from that root-canal just yet, I guess. Oh so fun... Sorry for line noise.
