Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 76393

Summary:	Bad: problem in "echo"
Product:	[Retired] Red Hat Linux	Reporter:	Onur TAN <tano>
Component:	tcsh	Assignee:	Miloslav Trmač <mitr>
Status:	CLOSED NOTABUG	QA Contact:	Bill Huang <bhuang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-08-19 16:12:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Onur TAN 2002-10-21 09:34:59 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
Bad: I always use csh in my console. the program "echo" could use backslash
options (\t or \n) in RH7.3. I have installed RH8, and the command lines in my
csh scripts can not print a newline (\n) or a tab (\t). When i use tcsh, echo
runs properly. 


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.echo "linux \n"
2.
3.
	

Actual Results:  > linux \n
>

Expected Results:  >linux
 (one blank line)
>

Additional info:

Comment 1 nessus 2002-12-13 23:34:52 UTC

This is a tcsh feature, not a csh feature.  Why don't you use tcsh instead?

(Actually, they are the same executable, but apparently some csh-compatibility
options turn on if you invoke tcsh via csh.)

Comment 2 Miloslav Trmač 2004-08-19 16:12:44 UTC

You can change the behavior by setting the echo_style variable.
Changing the default would break too many existing scripts,
as well as arbitrarily diverging from upstream.