Date: Tue, 21 Jun 2011 11:29:53 -0400 From: Matthew Pounsett <matt@conundrum.com> To: Lars Kellogg-Stedman <lars@oddbit.com> Cc: freebsd-questions@freebsd.org Subject: Re: sed argument processing b0rked? Message-ID: <BEAFC4EE-9F00-4852-BF6C-2AA5E6BC42AB@conundrum.com> In-Reply-To: <BANLkTik40kE2ds2AvmjykaD3btui1paXkw@mail.gmail.com> References: <73E783DC-E32B-4DE3-AFF6-4A75D1D3A00A@conundrum.com> <BANLkTik40kE2ds2AvmjykaD3btui1paXkw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2011/06/21, at 11:24, Lars Kellogg-Stedman wrote: >>> sed -i'' -e 's/^\(REVOKE ALL ON SCHEMA public FROM = \)postgres/\1pgsql/' \ >> ? -e 's/^\(GRANT ALL ON SCHEMA public TO = \)postgres/\1pgsql/' \ >> ? /tmp/pgdump >> sed: -e: No such file or directory >=20 > If you put a space after -i: >=20 > sed -i '' ... Aha... I knew it had to be something. I couldn't quite wrap my head = around the idea that sed is misbehaving.. it seems way too old and set = in its ways for that. However, I did get the -i'' syntax from = somewhere.. perhaps it's a GNUism and I just forgot where I picked it = up. =20 Thanks for the correction!=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BEAFC4EE-9F00-4852-BF6C-2AA5E6BC42AB>