Re: Finder f*ck-ups
Re: Finder f*ck-ups
- Subject: Re: Finder f*ck-ups
- From: Martin Orpen <email@hidden>
- Date: Fri, 19 Aug 2005 15:02:46 +0100
On 19 Aug 2005, at 14:44, John C. Welch wrote:
On 8/19/05 06:29, "Martin Orpen" <email@hidden> wrote:
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.
[snip]
But your insistence, in spite of clear evidence that this isn't a
Finder
problem, that it IS a Finder problem of some kind, tells me that
while you
are possibly the greatest scripter whom ever lived, your
troubleshooting
skills need some work, as you are prone to jump to conclusions
about a
problem.
Likewise, your reading skills are as suspect as my
troubleshooting :^)
What other people do is immaterial. The fact that you labeled, or even
insinuated this as a Finder bug is incorrect. Period.
Lucky that I didn't do any of that then...
According to you I've *insisted*, and *insinuated* and *labeled* this
as a Finder bug.
You're putting up straw men as fast as Deatherage.
In the meantime I've located what looks to be more likely to be the
source of the problem - thanks for your invaluable assistance.
--
Martin Orpen
_______________________________________________
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