Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #11314

Enhancement: bash should have uniform escape syntaxes for `echo -e`, `printf` and `$'ANSI_C_style_escape'`.

From Arthur200000 <arthur200126@163.com>
Newsgroups gnu.bash.bug
Subject Enhancement: bash should have uniform escape syntaxes for `echo -e`, `printf` and `$'ANSI_C_style_escape'`.
Date 2015-08-11 02:30 +0800
Message-ID <mailman.8088.1439231469.904.bug-bash@gnu.org> (permalink)

Show all headers | View raw


Configuration Information:
Machine Type: i686-pc-cygwin, i686-pc-msys, x86_86-linux-gnu, x86_64-Apple-Darwin

Bash Version: 4.3
Patch Level: 30
Release Status: release

Description:
	Bash has different escape syntaxes for `echo -e`, `printf` and `$'ANSI_C_style_escape'`. Take a specific point, `printf` and `$'C_Style'` accepts octals not starting with 0, but `echo -e` doesn't. 
	This is causing quite a lot of confusion.
	
	On older versions of bash, like bash 3.2 on OS X, `echo` doesn't understand `\e` but `printf` and `$'C_style'` does. I believe this is quite a aged problem.

Repeat-By:
	printf 'printf starts the bold\33[1m\n'; echo $'C escape should end it\33[0m'; echo -e 'echo -e does nothing but giving crap\33[1;31m'

Back to gnu.bash.bug | Previous | Next | Find similar


Thread

Enhancement: bash should have uniform escape syntaxes for `echo -e`, `printf` and `$'ANSI_C_style_escape'`. Arthur200000 <arthur200126@163.com> - 2015-08-11 02:30 +0800

csiph-web