Comments for Coyote Tracks

Comment on Workaround for PEAR/PECL Failure with Message “ERROR: `phpize’ failed” by kdoe

kdoe — Fri, 06 Jan 2012 12:12:03 +0000

It didn’t work for me:

root@dragon:patch -p0 < patch

patching file Builder.php
Hunk #1 succeeded at 472 (offset 8 lines).
patch: **** malformed patch at line 47: 2))));

I tried also the foxed path that Dave give and it didn't work also.

Comment on Workaround for PEAR/PECL Failure with Message “ERROR: `phpize’ failed” by ERROR: `phpize' failed

ERROR: `phpize' failed — Fri, 06 Jan 2012 09:01:33 +0000

[...] php with some option for phpize? kode No, You can try the patch in my previous post. See here what you need to do. Just don't forget to backup Builder.php [...]

Comment on The Problem With Jamie Zawinski and Regular Expressions by Kai MacTane

Kai MacTane — Wed, 04 Jan 2012 03:29:12 +0000

What I've got is this: Jeffrey Freidl, author of the O'Reilly book Mastering Regular Expressions, has done a huge amount of research on the context in which jwz delivered his famous quote. His write-up on all that is at http://regex.info/blog/2006-09-15/247; for the link to the comp.sys.ibm.pc.rt post, search for "awk" in that page. Alternatively, here's a direct link to it on Google Groups (of course, I got that URL from Freidl's wonderful post). I hope that helps!

Comment on The Problem With Jamie Zawinski and Regular Expressions by Frank Bennett

Frank Bennett — Tue, 03 Jan 2012 00:24:11 +0000

I’m working on a book about citations and automated bibliography management, and would like to reference this quote. It’s a bit over the top to obsess about these things, I know, but given the topic of the book, I’d like to pin down the original source as best as I can. Do you have a reference to the 1988 post, or a copy of the text?

Comment on Are We Always New At Everything? by Kai MacTane

Kai MacTane — Sun, 18 Dec 2011 02:54:34 +0000

Heh… I haven’t actually seen the new Twitter revamp yet. It hasn’t rolled out on their website yet, only their iOS and Android apps. I don’t use the official app; instead, I use Seesmic (it handles multiple accounts really well).

So, in another week or so, when the web UI changes, I may have to write a brief addendum to this post. Thanks for the heads-up.

Comment on Are We Always New At Everything? by Lun Esex

Lun Esex — Sun, 18 Dec 2011 02:25:37 +0000

No mention of Twitter’s new revamp? The whole reason they said they did it is because they wanted to make Twitter SIMPLER. Of course, for the official Twitter mobile apps at least, this means that “advanced” things that used to be one or two taps away have gotten buried three or four taps deep now.

Comment on Say It Short by Lun Esex

Lun Esex — Sun, 13 Nov 2011 21:58:37 +0000

There are always exceptions. My previous comments are in terms of generalities, and why API being pronounced as “appy” might fail at them. In that case, in several ways the pronunciation “appy” for API has more than one hurdle, and people don’t seem inclined to make an exception for it.

And, personally, I might say either “gooey” OR “gee-you-eye” for GUI, depending on the situation, and I ALWAYS spell out AVI when speaking it (which I do have occasion to do). I might even say something like “a dot ayy-vee-eye file,” to be especially clear.

Comment on Say It Short by Kai MacTane

Kai MacTane — Sat, 29 Oct 2011 21:31:08 +0000

First off: I’m not sure why WordPress thought a long comment looked “spammy”, and I’m not sure how to stop that. I am sorry.

Second: You’ve already pointed out ANSI and ASCII as acronyms that we pronounce as words (as opposed to abbreviations that we spell out). I can add SCSI to that, if you want one that ends in “Interface”. What others are you thinking of that we spell out that would otherwise be pronounceable as single words? On the list you linked to, I see DVI and HDMI, but both of those are non-pronounceable without spelling them out.

I also see MIDI and GUI, which counter your argument.

There’s also the .AVI file extension. I always pronounced it as “avvy”. I forget whether I’ve ever heard others do so, or had to pronounce it to other people (and what their reaction was if I did). It’s just not used often enough.

Comment on Say It Short by Lun Esex

Lun Esex — Sat, 29 Oct 2011 11:32:53 +0000

I’d guess that it’s simply that pronouncing a three letter acronym as a two syllable word comes out as ungainly.

Plus we’re already really used to pronouncing the “I” at the ends of lots of acronyms (especially when it stands for “Interface”). And one way or another, it looks like anything ending in “I” is going to come out as two syllables if/when pronounced as a word.

(Grr. I kept trying to post the three comments above as a single post and WordPress kept telling me my content looks “a bit spammy.” I’ve had to break it into three and pull out the list of acronyms pronounced like words that I’d put in to see if that gets around it.)

Comment on Say It Short by Lun Esex

Lun Esex — Sat, 29 Oct 2011 11:30:49 +0000

One thing that jumps right out at me about the three letter acronyms at the link in my previous comment that are pronounced like words is that except for ISO they’re all pronounced as a single syllable, as opposed to two in “appie.” In fact more of the acronyms longer than three letters that are pronounced like words are pronounced as a single syllable than as two syllables, too.