From: Kevin Korb <kmk@sanitarium.net>
To: dash@vger.kernel.org
Subject: [bug?] echo -n does not work as described
Date: Wed, 11 Nov 2015 20:56:02 -0500 [thread overview]
Message-ID: <5643F1B2.5050207@sanitarium.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am on dash version 0.5.8.2 on Gentoo Linux (USE=libedit -static).
The echo builtin does not work as described. In the man page:
echo [-n] args...
Print the arguments on the standard output, separated by spaces.
Unless the -n option is present, a newline is output following the
arguments.
However, in actual usage:
% dash
$ echo testing
testing
$ echo -n testing
- -n testing
$ /bin/echo -n testing
testing$
This is causing me problems when I attempt to switch /bin/sh from bash
to dash.
- --
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
- -*~
Kevin Korb Phone: (407) 252-6853
Systems Administrator Internet:
FutureQuest, Inc. Kevin@FutureQuest.net (work)
Orlando, Florida kmk@sanitarium.net (personal)
Web page: http://www.sanitarium.net/
PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
- -*~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlZD8bIACgkQVKC1jlbQAQc0DQCaAt6x4XveLhPjaPiPaSG8ll5a
3ZEAn0J5mkr1wd7Nd2l3Q6xKpB2LZ39+
=lljb
-----END PGP SIGNATURE-----
next reply other threads:[~2015-11-12 2:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 1:56 Kevin Korb [this message]
2015-11-12 3:14 ` [bug?] echo -n does not work as described Eric Blake
2015-11-12 3:40 ` Kevin Korb
2015-11-12 3:46 ` Kevin Korb
2015-11-12 8:35 ` Seb
2015-11-12 16:12 ` Kevin Korb
2015-11-12 21:24 ` Stephane Chazelas
2015-11-12 8:10 ` Bastian Bittorf
2015-11-12 16:11 ` Kevin Korb
2015-11-19 12:36 ` Bastian Bittorf
2015-11-12 10:03 ` Petr Šabata
2015-11-12 16:18 ` Kevin Korb
2015-11-12 16:55 ` Kevin Korb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5643F1B2.5050207@sanitarium.net \
--to=kmk@sanitarium.net \
--cc=dash@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox