Darrell Fuhriman wrote:
>> So you've mainly abandoned Perl for Ruby but you decided to pop a shot
>> at Perl anyway - and it turned out to be Ruby's fault? :)
>
> Well, it's partially my fault for not checking my quoting (hardly unique
> to ruby). But why should "actual-carriage-return{1}actual-ne
So you've mainly abandoned Perl for Ruby but you decided to pop a
shot at Perl anyway - and it turned out to be Ruby's fault? :)
Well, it's partially my fault for not checking my quoting (hardly
unique to ruby). But why should "actual-carriage-return{1}actual-
newline{1}" work differently fr
On 8 Oct 2008, at 18:43, Darrell Fuhriman wrote:
Urrrggh... the problem seems to be coming up because I'm calling it
as a rake task. Rake was converting the \r\n to actual carriage
return+newline in the call to the shell.
So you've mainly abandoned Perl for Ruby but you decided to pop a sho
Is that different from what you observed? If so which version of
Perl are you using?
Urrrggh... the problem seems to be coming up because I'm calling it as
a rake task. Rake was converting the \r\n to actual carriage return
+newline in the call to the shell.
ie:
perl -i.bak -ne 's/ date
On 8 Oct 2008, at 17:29, Darrell Fuhriman wrote:
You *remove* all \r\n, replacing it with nothing
Yes, which is what I wanted. What I didn't want is to remove all
solitary \n, which is what it did.
If I were to have used s/af//, I would not expect it to convert
'wtf' to 'w', but that's
You *remove* all \r\n, replacing it with nothing
Yes, which is what I wanted. What I didn't want is to remove all
solitary \n, which is what it did.
If I were to have used s/af//, I would not expect it to convert 'wtf'
to 'w', but that's the equivalent of what it did.
Darrell
On Wed, 8 Oct 2008 08:52:40 -0700, Darrell Fuhriman
wrote:
>
> I know, hating perl -- fish in a barrel. I've been doing a lot more
> stuff in ruby lately, but I still like perl for a few things. In this
> case, I had a file which had some spurious carriage returns, which I
> needed to rem
I know, hating perl -- fish in a barrel. I've been doing a lot more
stuff in ruby lately, but I still like perl for a few things. In this
case, I had a file which had some spurious carriage returns, which I
needed to remove so postgres wouldn't complain about them. As it
happens, the car
* Ricardo SIGNES [2008-10-08 15:10]:
> Replacing hypermail was divine.
Hmm, I am not really hating the Hypermail install used by the W3C
(see http://lists.w3.org/Archives/Public/ for examples). Is it
just a particularly beaten-into-submission install? (It is
patched, at least, I see that much.)
* Léon Brocard [2008-10-08T04:53:22]
So much hate, but let's start here:
http://lists.launchpad.net/drizzle-discuss/msg01658.html
OH GOD YOU HAVE AWAKENED THE HATE WITHIN.
That archive is generated by MhonArc which is either a branch of the Hypermail
archiver or was intended (for some unkn
So much hate, but let's start here:
http://lists.launchpad.net/drizzle-discuss/msg01658.html
Now email messages can contain headers, this is true. However, let's
take a wild stab in the dark here: when I'm trying to browse a mailing
list archive maybe the one thing I'm most interested in the ac
11 matches
Mail list logo
