From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: morgad@eclipse.co.uk, git@vger.kernel.org, sean <seanlkml@sympatico.ca>
Subject: Re: problem installing latest cogito
Date: Sat, 21 Jan 2006 12:12:28 -0800 [thread overview]
Message-ID: <7vmzhpl4r7.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <BAYC1-PASMTP061F43C7F760A9FB73B616AE1E0@CEZ.ICE> (seanlkml@sympatico.ca's message of "Sat, 21 Jan 2006 14:49:01 -0500")
sean <seanlkml@sympatico.ca> writes:
> On Sat, 21 Jan 2006 20:48:26 +0100
> Petr Baudis <pasky@suse.cz> wrote:
>
>> > sed -e
>> > 's/\${COGITO_LIB}/\${COGITO_LIB:-\/home\/david\/lib\/cogito\/}/g; \
>> >
>> > s/\${COGITO_SHARE}/\${COGITO_SHARE:-\/home\/david\/share\/cogito\/}/g'
>> > \
>> > $file > $file.new; \
>> > cat $file.new > $file; rm $file.new; \
>> > done
>> > sed: -e expression #1, char 145: unterminated address regex
>
> The problem seems to go away if you remove the quoted end-of-line:
That is not "the quoted end-of-line". Backslashes do not have
any special meaning inside a single quote pair for bourne shell
quoting. The script is passing the backslash to sed.
IIRC, make seems to do different things for the backslash at the
end of line depending on vintage, so if this scriptlet appears
in a Makefile you may have another version dependency. I
usually cop out of this problem by having a separate shell
script and run it from the Makefile, instead of spelling out the
sed commandline in the Makefile.
I got a complaint or two that some version of sed does not like
';' to concatenate more than one commands, and have been trying
to train myself to do either multiple -e options or multi-line
scripts. E.g when I am tempted to say:
sed -e 's/foo/bar/;s/baz/boa/' froboz
Instead, I say either
sed -e 's/foo/bar/' -e 's/baz/boa/' froboz
or
sed -e '
s/foo/bar
s/baz/boa/
' froboz
I do not know how much of the above applies to your immediate
problem, but I hope some of it helps.
next prev parent reply other threads:[~2006-01-21 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 14:08 problem installing latest cogito dave morgan
2006-01-21 19:48 ` Petr Baudis
[not found] ` <20060121144901.33b03395.seanlkml@sympatico.ca>
2006-01-21 19:49 ` sean
2006-01-21 20:12 ` Junio C Hamano [this message]
2006-01-21 21:06 ` Petr Baudis
2006-01-21 21:22 ` dave morgan
2006-01-21 20:03 ` Petr Baudis
[not found] ` <20060121150142.4b1bb47e.seanlkml@sympatico.ca>
2006-01-21 20:01 ` sean
2006-01-21 20:08 ` dave morgan
2006-01-21 21:46 ` Petr Baudis
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=7vmzhpl4r7.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=morgad@eclipse.co.uk \
--cc=pasky@suse.cz \
--cc=seanlkml@sympatico.ca \
/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