Hello, Am Dienstag, 15. März 2011 21:44:37 UTC+1 schrieb Chet Ramey: > > The bash-4.1 solution, though it modified what the user typed, did not > result in any ambiguity. A filename was a filename, and if it contained > characters that needed to be quoted, readline did so. > > I might be able to finesse this issue and retain the bash-4.2 behavior > by changing state when rewriting the directory name for opendir(2), but > I have to think about it some more.
you elsewhere suggested to write a completion function for cd that does the expansion. May I point out that the expansion of variables is not only a matter with the cd command but for any other command that expects directory or file names? I understand the dilemma, nobody prevents me from creating a directory named '$HOME' but what do I expect when typing cd $HOME/<tab>...? Anyways I just installed Bash 4.2 and many people here would like the old behaviour back. It is quite common to do `ls $VAR/<tab>' and then expecting that $VAR is expanded, I don't think that anybody here has a file name containing a dollar, and if that would be the case, then I doubt that what follows the dollar sign is a name of a variable. Thanks, Peter
