From: Carl Worth <cworth@cworth.org>
To: Jan Janak <jan@ryngle.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH] makefile: Tell echo to interpret escape sequences.
Date: Mon, 23 Nov 2009 03:41:04 +0100 [thread overview]
Message-ID: <874oomgdz3.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <1258893877-28436-1-git-send-email-jan@ryngle.com>
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
next prev parent reply other threads:[~2009-11-23 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 12:44 [PATCH] makefile: Tell echo to interpret escape sequences Jan Janak
2009-11-23 2:41 ` Carl Worth [this message]
2009-11-23 3:02 ` Jan Janak
2009-11-23 7:05 ` Karl Wiberg
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: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874oomgdz3.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=jan@ryngle.com \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).