[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

New feature of command name completion?

From: Rajnai Mark
Subject: New feature of command name completion?
Date: Thu, 29 Jul 2004 12:39:11 +0200 (CEST)

Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu'
-I../bash/include -I../bash/lib  -g -O2
uname output: Linux pc2089 2.4.18 #7 Tue Sep 10 09:26:10 CEST 2002 i686
Machine Type: i386-pc-linux-gnu

Bash Version: 2.05b
Patch Level: 0
Release Status: release

        I had just upgraded Debian sarge yesterday from woody, but I
realised only now, that the command name complete function (TAB) of bash
doesn't work "correctly", when I want to run a program in an other
        After it I have found that there is a change in command name
completion in bash (slash is no longer appended in some cases...)
that I don't believe a good idea.

        For example:
        There is an executable file: /home/mark/work/prodgen/bin/draw_r,
that I want to run from the /home/mark directory.
        It was enough to start to type "wor+TAB", and the previous bash
version (2.05a-11) completed it to "work/". After it I was able to
continue with typing "prod+TAB" and so an...
        Now: when I type "wor+TAB", this bash completes it to "work "
instead of "work/", as it would be only an argument of a program.... or..
I don't know what is the good of it.
        However the complete function operates rightly in case of typing
"./wor+TAB". The result of this: "./work/" So it can solve my problem, but
I think, the previous version was more useful about command name

Best Regards,
Mark Rajnai

reply via email to

[Prev in Thread] Current Thread [Next in Thread]