Re: Conflicts between "complete" and "complete-filename"

On 5/22/10 2:07 PM, Henning Bekel wrote: > Configuration Information [Automatically generated, do not change]: > Machine: i686 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' - > DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' - > DCONF_VE

Re: How not to expand a environment variable when doing command completion?

> When I type 'cd $HOME/.', bash will expand the command to 'cd > /home/my_user_name/.'. Would you please let me know how to let bash > expand the environment variable? There is no setting to suppress the environment variable expansion. Bash has behaved this way for many years. Chet -- ``The l

Re: How not to expand a environment variable when doing command completion?

On Tue, May 25, 2010 at 9:18 PM, Chet Ramey wrote: >> When I type 'cd $HOME/.', bash will expand the command to 'cd >> /home/my_user_name/.'. Would you please let me know how to let bash >> expand the environment variable? > > There is no setting to suppress the environment variable expansion.  Ba

Re: How not to expand a environment variable when doing command completion?

On 5/25/10 10:28 PM, Peng Yu wrote: > On Tue, May 25, 2010 at 9:18 PM, Chet Ramey wrote: >>> When I type 'cd $HOME/.', bash will expand the command to 'cd >>> /home/my_user_name/.'. Would you please let me know how to let bash >>> expand the environment variable? >> >> There is no setting to suppr