Description of problem: The latest tcsh update (tcsh-6.14-14.el5_4.2.x86_64, I installed it on Oct 14) has introduced a serious file globbing problem. Version-Release number of selected component (if applicable): tcsh-6.14-14.el5_4.2.x86_64 How reproducible: Every time Steps to Reproduce: 0. /bin/rm -rf /tmp/testdir 1. mkdir /tmp/testdir 2. cd /tmp/testdir 3. touch file 4. echo "hello" * Actual results: \hl\l\o file Expected results: hello file Additional info: I get the same error on an i386 machine. It seems that each character in the double quotes in the argument to the "echo" command is having a backslash prepended to it. This is messing up many commands, including "egrep".
We're seeing the same behavior. It is interesting that the transformation of the quoted string is character specific and some get turned into control characters. For example echo "a" * turns the "a" into "^G". Using "b" turns into "^H", and using "c" results in no output at all. Obviously, this causes lots of interesting behavior for tcsh/csh users.
It looks like the previous "fix" to tcsh tried to do something with the "buildkey" tcsh builtin command. Here's an exerpt from "man tcsh": Control characters in key can be literal (they can be typed by preceding them with the editor command quoted-insert, normally bound to ‘^V’) or written caret-character style, e.g., ‘^A’. Delete is written ‘^?’ (caret-question mark). key and command can contain backslashed escape sequences (in the style of System V echo(1)) as follows: \a Bell \b Backspace \e Escape \f Form feed \n Newline \r Carriage return \t Horizontal tab \v Vertical tab \nnn The ASCII character corresponding to the octal number nnn
Globbing got messed up right after the RHBA-2009:1494-1 patch on Oct. 13th. For example: echo a \; # Works echo a* \; # Fails echo \; # Works find .??* -exec grep syn {} \; -ls # Fails
*** Bug 537127 has been marked as a duplicate of this bug. ***
*** Bug 538431 has been marked as a duplicate of this bug. ***
*** Bug 538837 has been marked as a duplicate of this bug. ***
*** Bug 552985 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0190.html