Bug#644285: lsb-base: Disabled escape sequences

"Didier 'OdyX' Raboud" <[email protected]>
Newsgroups gmane.linux.debian.devel.lsb
Organization Debian, the Universal OS
Message-ID <[email protected]>
tags 644285 +moreinfo
thanks

Hi Mats, and thanks for your bugreport,

Le 04.10.2011 21:36, Mats Erik Andersson a écrit :
> At a previous time the functions in 'init-functions'
> were allowed to use
> 
>    /bin/echo -e
> 
> whereas presently they are all forced into using
> 
>   /bin/echo -n
> 
> It would be far superior to use
> 
>   /bin/echo -ne
> 
> as this restores to any script author the possibility of
> issueing structured messages using standard escape sequences
> like "\b\t".

On one hand, I understand the desire to have access to "powerful"
structured messages in init scripts. On the other hand, I see some value
in limiting what can be done to the display by init script messages. In
fact, I fail to see valid reasons to use structured messages in init
scripts and your bugreport doesn't show a real-world use case.

By the way, are there init scripts that got broken by this change ?

For now, I'm tempted to tag this bug as +wontfix but am open to get
convinced, hence +moreinfo.

Cheers,

OdyX
signature.asc (application/pgp-signature, 663 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)

iQGcBAEBAgAGBQJPV2HUAAoJEIvPpx7KFjRVb60L/3fjFstFMOVl8PfMK8KcVDrN
BpGAajFjj9lUiEc14l9+EoouHujQn67WnGZ27Tmrw8ksgdn0+m6Mtk5+KXvHKOXM
goUdQxUBGxdWZK2LGR7TXuYJvCAwe5U8z9+nEEJWsu134MXNWaRKIQ2lzl1qDMXc
4brv19UV+qiEId4D9md9nBvoO2foQrFYAwtf7S2caR+jYEKgr+lOj/ILGM0MTq0W
7t99xI19Y+hdzebypKEebPKbpokccnpaVimD+m0LM2v+Js7ZioPR6y70Ki3E6FPG
UpEb15hFTWC+AJWxRUB8G/e//i1+MqQP306Ca86A6Os4scDf+s0Q47HQNd/MTbqi
VGUh6q0MnbXJDYah1fec/NHoZBD9RgXoMj+naye5+y+2l86Hm4kZoepg8sWI6qQg
JQY4+GsZobVvg9Xo+0dJUOfEsHxdqRv7EbvocTA1kkHBava0+zasaadNNW6vzzQZ
e9ckdU7wO99feN4+sC6aK2FSCJX+D2yydzzvDHiR4A==
=ZCDD
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.