From: Carl Worth <cworth@cworth.org>
To: Jan Janak <jan@ryngle.com>, notmuch@notmuchmail.org
In-Reply-To: <1258893877-28436-1-git-send-email-jan@ryngle.com>
References: <1258893877-28436-1-git-send-email-jan@ryngle.com>
Date: Mon, 23 Nov 2009 03:41:04 +0100
Message-ID: <874oomgdz3.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [notmuch] [PATCH] makefile: Tell echo to interpret escape
 sequences.
Precedence: list

On Sun, 22 Nov 2009 13:44:37 +0100, Jan Janak <jan@ryngle.com> wrote:
> The initial message that informs the user about the possibility to use
> make V=1 contains a \n at the end, but echo wouldn't interpret that
> properly without the -e command line option.

Patch doesn't work for me.

Before patch:

	0:~/src/notmuch:(master)$ make
	Use "make V=1" to see the verbose compile lines.
	  CC	notmuch-new.o
	  CXX	notmuch

After patch:

	0:~/src/notmuch:(master)$ make 
	-e Use "make V=1" to see the verbose compile lines.
	  CC	debugger.o
	-e   CC	gmime-filter-reply.o
	-e   CC	notmuch.o

It's a shame that simple things like "echo" aren't easy to use portably.
(And yes, I know that autoconf has a bunch of tests for echo, such as
how to get the behavior of "echo -n", etc.)

-Carl