Bug 21134 - tcsh trys to expand filename metacharacters when it shouldn't
Summary: tcsh trys to expand filename metacharacters when it shouldn't
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: tcsh   
(Show other bugs)
Version: 6.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Eido Inoue
QA Contact: Aaron Brown
Depends On:
TreeView+ depends on / blocked
Reported: 2000-11-20 17:37 UTC by Kevin Range
Modified: 2007-04-18 16:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-11-20 17:37:12 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Kevin Range 2000-11-20 17:37:09 UTC
tcsh tries to expand filename metacharacters when it shouldn't (e.g.
when using scp.


rangek@nf00 [~/Projects/new_cpks/H2S_only_B] % scp pinot-noir:* .
scp: No match.

But in bash:

[rangek@nf00 H2S_only_B]$ scp pinot-noir.chem.umn.edu:* .
rangek@pinot-noir.chem.umn.edu's password: 

And everything proceeds as expected, (i.e., the * is expanded by the
shell on pinot-noir, not on nf00).

It seems like bash is smart enough to see the machine:path syntax and
not expand it, while tcsh blindly tries to expand the filename
metacharacters, when by their very nature (refering to another machine)
they cannot be.

Comment 1 Nalin Dahyabhai 2000-11-20 21:30:04 UTC
This is consistent with the behavior for tcsh on the other platforms I've used
it on.  The shell attempts to glob any expression with metacharacters in it,
regardless of whether or not it contains a colon (it could just as well be a set
of files which start with "pinot-noir.chem.umn.edu:").

If this is not the desired behavior, you can either quote the pattern or use
either the "noglob" or "nonomatch" shell variables to customize the behavior.

Note You need to log in before you can comment on or make changes to this bug.