On 10 November 2011 10:33, Vincent Hoffman wrote:
> On 10/11/2011 07:00, per...@pluto.rain.com wrote:
>
>> Vincent Hoffman wrote:
>>
>> bsd sed (correctly according to SUS at least, I believe[1])
>>> appends a newline when writing to standard out, gnu sed doesnt.
>>>
>> The wonderful thing abou
On 10/11/2011 07:00, per...@pluto.rain.com wrote:
Vincent Hoffman wrote:
bsd sed (correctly according to SUS at least, I believe[1])
appends a newline when writing to standard out, gnu sed doesnt.
The wonderful thing about standards is that there are so many to
choose from -- Tanenbaum
is
Vincent Hoffman wrote:
> bsd sed (correctly according to SUS at least, I believe[1])
> appends a newline when writing to standard out, gnu sed doesnt.
The wonderful thing about standards is that there are so many to
choose from -- Tanenbaum
> is there any easy way to make our sed do the same a
On 11/09/11 05:30, Vincent Hoffman wrote:
'Hi all,
I'm trying to move a script from a linux box to a freebsd box.
All going well as its just a bash script and bash is bash, however there
is one line I'm unable to use directly, as bsd sed (correctly according
to SUS at least, I believe[1]
On 09/11/2011 10:30, Vincent Hoffman wrote:
is there any easy way to make our sed do the same as gnu sed here?
for now I have encapsulated the whole thing in a subshell
[backup@banshee ~]$ echo -n $(echo -n "/boot:7:1:5; /:7:1:5;
/var:7:1:5" | sed -n 's/[[:space:]]*;[[:space:]]*/;/gp')
/boot:7:1
'Hi all,
I'm trying to move a script from a linux box to a freebsd box.
All going well as its just a bash script and bash is bash, however there
is one line I'm unable to use directly, as bsd sed (correctly according
to SUS at least, I believe[1]) appends a newline when writing to
standard
