dash.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Korb <kmk@sanitarium.net>
To: Seb <sbb@tuxfamily.org>, dash@vger.kernel.org
Subject: Re: [bug?] echo -n does not work as described
Date: Thu, 12 Nov 2015 11:12:28 -0500	[thread overview]
Message-ID: <5644BA6C.4030400@sanitarium.net> (raw)
In-Reply-To: <20151112083536.GA796@ein.free.fr>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is what I get:
% dash -c 'type echo; echo -n foo; echo foo'
echo is a shell builtin
- -n foo
foo


On 11/12/2015 03:35 AM, Seb wrote:
> On Wed, Nov 11, 2015 at 10:46:02PM -0500, Kevin Korb wrote:
> 
>>>> By the way, 'echo -n' is non-portable, and POSIX says you 
>>>> should use 'printf' instead.
>> 
>> If dash refuses to supply a compatible version of echo then dash
>> must not include a builtin version of echo.  If dash didn't have
>> a broken embedded version of echo I wouldn't have a problem.
> 
> dash just claims to be compatible with POSIX, not with *sh. If you
> look for something like this (lighter than bash but with many of
> its features), glance rather at mksh:
> 
> https://www.mirbsd.org/mksh.htm
> 
> Now, I don't understand the present issue, all seems just work as 
> expected here (0.5.8):
> 
> $ dash -c 'type echo; echo -n foo; echo foo' echo is a shell
> builtin foofoo
> 
> ++ Seb.
> 
> -- To unsubscribe from this list: send the line "unsubscribe dash"
> in the body of a message to majordomo@vger.kernel.org More
> majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

- -- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
	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

iEYEARECAAYFAlZEumwACgkQVKC1jlbQAQciqwCeNRjcqFps3ZNtisqM3UI2rlQn
3NMAn2DAvJuycgyFnDTf10jP3y4Gu8x9
=lCLu
-----END PGP SIGNATURE-----

  reply	other threads:[~2015-11-12 16:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12  1:56 [bug?] echo -n does not work as described Kevin Korb
2015-11-12  3:14 ` 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 [this message]
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=5644BA6C.4030400@sanitarium.net \
    --to=kmk@sanitarium.net \
    --cc=dash@vger.kernel.org \
    --cc=sbb@tuxfamily.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;
as well as URLs for NNTP newsgroup(s).