Re: Finder f*ck-ups
Re: Finder f*ck-ups
- Subject: Re: Finder f*ck-ups
- From: "John C. Welch" <email@hidden>
- Date: Fri, 19 Aug 2005 13:04:35 -0500
- Thread-topic: Finder f*ck-ups
On 8/19/05 10:17, "Martin Orpen" <email@hidden> wrote:
>> Why, "Finder F*ck-ups". No, no insinuation there. None at all.
>
> That's a pretty accurate description of what was happening to my
> script and then verified by dragging files in the Finder.
And a mighty accurate and non-disparaging title it was too. Just as calm and
measured as can be.
>
>>
>> The lead sentence in *your* original post:
>>
>> " What's going on with the Finder in Tiger?"
>
> That's a question - not an *insistance*.
And the problem isn't a part of the finder.
>> No, no, not disparaging the Finder team at all. Not even close.
>> Especially
>> when that has little to do with the behavior you're reporting.
>> (This happens
>> on pooched automounts all the time, so I pretty much can guarantee the
>> disappearing files are not exclusive to the DVD issue.)
>
> Dave Lyons - who actually works on the Finder wrote:
>
>> The part about the items later disappearing from Finder is
>> certainly a bug; I believe it's already covered by <rdar://problem/
>> 3949358>.
I'm well aware of that bug. As I said, it's a well-known problem, which
predates Mac OS X 10.4 by quite a lot. I see it happening the most with
automounts, particularly when you hit the problem in Mac OS X 10.3 where the
AFP client only allows for 3 automounts. Then it REALLY gets fun.
>
> John continues:
>
>> Then in almost every single example of what you tried, you show
>> that it's
>> pretty obviously not a Finder bug, but at NO point do you say
>> "Well, it
>> looks like the title of this post was incorrect and misleading, as
>> it's
>> obviously not a Finder bug", because hey, once you get started
>> beating the
>> Finder team, stopping is so dull, because slapping the Finder team
>> is what
>> all the kewl OS X kidz are doing.
>
> Whereas I'd already written:
>
>>> Obviously, the fact that most people will encounter this problem
>>> while using
>>> or scripting the Finder does not mean that the Finder is to blame.
>
> And already called your attention to it.
You created the subject line and failed to correct it. Your action, your
fault. As well, the ranting nature of your post required you to do a lot
more work than you would have had to if you had written it better.
>
> But don't let what people have *actually* written get in the way of
> your obsession with having the *final and definitive word* on any
> subject.
>
> The bug report has been filed. The probable reason isolated. People
> have been warned of something that might cause their scripts to not
> work as expected.
>
> And we've all been reminded that the ability to post the most
> authoritative answer on *every* programming issue seems to be
> inversely proportional to the amount of lines of AppleScript that you
> actually write or post to this list.
Yes, yes, you have a great large ego, let us all admire it in awe as you
swing it about. Because of course, you're aware of all the AppleScript that
everyone on this list has ever written, public or private.
Aka, "Cast out the beam in thine own eye before thou pointest out the mote
in mine".
--
''Look, I don't want to wax philosophic, but I will say that if
you're alive you've got to flap your arms and legs, you've got to
jump around a lot, for life is the very opposite of death, and
therefore you must at [the] very least think noisy and
colorfully, or you're not alive.''
- Mel Brooks
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden