CentOS requiring "\" after files with no extension

[westrock2000]

I setup 64 Bit CentOS at home, and it does a very strange thing where it requires a \ after a file with no extension in order for the OS to accept the name of the file.

What I mean is, if I type

bash> more /home/user/textfi <TAB>
it returns...
bash> more /home/user/textfile\

where as if had a txt extension it would be fine

bash> more /home/user/textfi <TAB>
would return...
bash> more /home/user/textfile.txt

The reason this is a problem is because
bash> ls /home/user/textfile
returns "no file or directory", while
bash> ls /home/user/textfile\
returns correctly

Konquerer can't even copy the files. Once you select and copy them, paste errors out saying "can't copy file"

I have never seen a *nix distro that acted like this, especially considering the fact that extensions mean nothing in *nix. The CentOS we are using at work does not behave like this. And I really don't think its useable in this state.

Any ideas? I saw some threads about other OS's that mentioned the /etc/bashrc, but they didn't really say what to change.
[backslah no extension backslash after file name with no extension]

 

[Boomslang]

Does the filename have a space at the end of it?

Try creating a new file with a space at the end by enclosing the name and space in quotes:

touch "test "

The behavior should be as you describe.

Now try without a space:

touch test2

What happens when you tab-complete this one?