Entering ".." in the shell suggests bogus commands

[Thomas Perl]

I accidentally found this: If you enter ".." in the bash prompt, you get the following bogus output:

thp@macbook:~$ ..
Command '..' is available in the following places
 * /bin/..
 * /usr/bin/..
 * /usr/local/bin/..
 * /sbin/..
 * /usr/sbin/..
 * /usr/local/sbin/..
 * /usr/games/..
bash: ..: command not found

[Marcel Stimberg (marcelstimberg)]

Confirmed on gutsy (command-not-found/gutsy uptodate 0.2.8ubuntu2)

Nice one :)

[James Westby (james-w)]

Hi,

In UnifiedDataExtractor/scan there is

def get_executables(package):
    def exec_filter(item_info):
        # lib*.so* are usualy +x so we'll exclude them
        return isinstance(item_info, DebPackage.FileInfo) and item_info.is_executable() and not re.match("^lib.*\\.so.*", os.path.basename(item_info.name))
    return ["/"+item_info.name for item_info in package.items if exec_filter(item_info)]

This bug may be fixed if the exec_filter function also excludes ".."

Thanks,

James

[Thomas Perl (thp)]

In Python, I'd do something like "os.path.isdir(filename)"..

[Zygmunt Krynicki (zyga)]

hello, I'm the author of this code.

The only correct way to fix this is to patch the "existing file" detection code that looks up files already present in the filesystem. It should ignore directories.

[Thomas Perl (thp)]

Here is a patch that fixes the problem by ignoring directories (as suggested by Zygmunt).