git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Andreas Schwab" <schwab@linux-m68k.org>,
	"Miklos Vajna" <vmiklos@frugalware.org>,
	"Santi Béjar" <santi@agolina.net>,
	git@vger.kernel.org
Subject: Re: [RFC] war on echo in scripts
Date: Fri, 09 Jul 2010 09:30:43 -0700	[thread overview]
Message-ID: <7vk4p4mxcc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20100709143011.GA1980@burratino> (Jonathan Nieder's message of "Fri\, 9 Jul 2010 09\:30\:11 -0500")

Jonathan Nieder <jrnieder@gmail.com> writes:

> Junio C Hamano wrote:
>> Jonathan Nieder <jrnieder@gmail.com> writes:
>
>>> +echo() {
>>> +	printf '%s\n' "$*"
>>> +}
>>
>> As long as we don't have "echo -n" and "echo -e", this should
>> work, but...
>
> Yes, it’s ugly.  And it could make for surprises in user scripts.

The latter could be avoided with "s/echo/sane_echo/"; we do that already
for grep don't we?

  reply	other threads:[~2010-07-09 16:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 22:55 [PATCH] rebase -i: use 'read -r' to avoid backslash acting as an escape character Miklos Vajna
2010-07-07  5:25 ` Junio C Hamano
2010-07-07  9:16   ` Miklos Vajna
2010-07-07  9:22     ` Santi Béjar
2010-07-07  9:46       ` Miklos Vajna
2010-07-08  0:29         ` Junio C Hamano
2010-07-08 10:35           ` Miklos Vajna
2010-07-08 17:14             ` [RFC] war on echo in scripts Jonathan Nieder
2010-07-08 22:57               ` Andreas Schwab
2010-07-09  2:46                 ` Jonathan Nieder
2010-07-09  3:47                   ` Sverre Rabbelier
2010-07-09  4:46                   ` Junio C Hamano
2010-07-09 14:30                     ` Jonathan Nieder
2010-07-09 16:30                       ` Junio C Hamano [this message]
2010-07-09 11:52                   ` Ævar Arnfjörð Bjarmason
2010-07-09 14:10                     ` Jonathan Nieder

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vk4p4mxcc.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=santi@agolina.net \
    --cc=schwab@linux-m68k.org \
    --cc=vmiklos@frugalware.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).