At 8:28 PM -0500 1/8/2003, Erik Price wrote:
>On Wednesday, January 8, 2003, at 10:38 AM, Ken Williams wrote:
>
>>The Allegory of the Cave springs to mind. =)
>
>Is that an Empire Strikes Back reference?
>
>"Luke, the cave... remember your experience at the cave..." -- Yoda
Youngsters these days,
On Wednesday, January 8, 2003, at 10:38 AM, Ken Williams wrote:
The funny thing is that I never did find a value (though I played
with the
plist values) that looked right, so I just learned to live with it,
and now
it is right, but looks WEIRD!
The Allegory of the Cave springs to mind. =)
On 9:38 AM -0600 on 1/8/2003, Ken Williams wrote:
>Not much good anymore. I'm now just another schmoe trying to figure out how I can
>use iSync to save the world, and whether I want to switch from Omniweb to Safari.
Some nice features, but with a couple dozen shortcuts leveraging %@ in OmniWeb,
On Tuesday, January 7, 2003, at 06:33 PM, Chris Nandor wrote:
I use 120 x 40 too, and had the same problem, also with Monaco 9.
Great
minds think alike. :-)
Heh.
The funny thing is that I never did find a value (though I played with
the
plist values) that looked right, so I just learned t
"William H. Magill" wrote:
> This is the real issue.
>
> I've been through many Unix upgrades on many different platforms and
> they all have exactly the same characteristic.
>
> There is hardware which runs releases which run fine on the hardware
> which existed when they were released. But tha
At 1:49 PM -0800 1/7/03, Daniel Stillwaggon wrote:
Same here, had to recompile lynx (btw, the fink lynx didn't work for
me, I had to download source) and MySQL, but everything else went
smoothly.
Right, I forgot that one. MySQL server ran fine, but the client had
to be recompiled.
In fairnes
In article ,
[EMAIL PROTECTED] (Heather Madrone) wrote:
> OTOH, I stuck Perl 5.8 in /usr/local, and I've had no difficulty
> with it whatsoever.
Yay!
--
Chris Nandor [EMAIL PROTECTED]http://pudge.net/
Open Source Development Ne
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Ken Williams) wrote:
> I suppose it depends on the size of your windows - mine are usually 120
> x 40. The annoying extra pixel is probably a rounding error spread
> over the width of the window, so the exact number will probably vary.
I use
Thanks to everyone for the responses. Again I apologize for re-opening this
OT thread. I'm very intrigued now, as several of the respondees are in very
similar circumstances. BTW I have a(n) ibook600 with lot's of UNIX stuff
built/configured/tweaked. I use my machine in a big way at work, so I can'
Thought that I'd go ahead and provide another data point...
On Tuesday, Jan 7, 2003, at 05:50 US/Pacific, Kee Hinckley wrote:
Well those of us who had a completely painless upgrade obviously don't
have anything to say. My upgrade to Jaguar was virtually trouble
free. I did have to recompil
On Tuesday, January 7, 2003, at 02:37 PM, Jeffrey Melloy wrote:
You really shouldn't seeing any stuff like that that's entirely
random. My bet would be bad RAM. I'd say dig out your hardware
checkup disk and run it. If it's not ram, it's almost definitely a
hardware problem, since that's ab
On Tuesday, January 7, 2003, at 12:25 PM, Chris Devers wrote:
And no, I haven't messed with Perl or Apache or anything like that. I'm
seeing this behavior on two G3s, of which one behaved this way almost
from
the start with Jaguar.
This is the real issue.
I've been through many Unix upgrades o
You really shouldn't seeing any stuff like that that's entirely random.
My bet would be bad RAM. I'd say dig out your hardware checkup disk
and run it. If it's not ram, it's almost definitely a hardware
problem, since that's about the only stuff that runs in kernel space.
On Tuesday, January
I thought the Monaco 9 font was incredibly hard to read in the
Terminal app, so I changed it to Courier New and upped the
size to 12.
At 12:25 PM -0500 1/7/03, Chris Devers wrote:
>That is, it's much nicer, everything seems to run faster and there's a lot
>more polish to many of the system applica
On Mon, 6 Jan 2003, Rich & Michaela wrote:
> I've avoided the upgrade to Jaguar for a number of reasons.
Just to be contrary -- as everyone else seems to be saying that Jaguar has
been great for them -- I'll see Ken a "two steps forward and one step
back" and raise you an "the candle that burns t
fwiw,
I paid, installed, and have not had any problems whatsoever. If
anything, previous problems created by me by upgrading Perl and Apache
all vanished because they got set back to the vendor provided versions.
I have now installed Jaguar on a PB400, iMac350, and iBook600 (all G3
machines) a
At 11:05 PM -0600 1/6/03, Rich & Michaela wrote:
I've avoided the upgrade to Jaguar for a number of reasons.
- Annoyed over being charged for what still seems like a maintenance
release to me.
Apple's mistake there was in the numbering, not the charging. It's
definitely as much an upgrade as
On Tuesday, January 7, 2003, at 06:57 AM, Erik Price wrote:
I'm not trying to invalidate the claims of the afflicted, I merely
want to mention that there's probably at least as many people who
aren't having problems (and for whom Jaguar offers worthwhile niceties
that aren't available in 10.1
The Jaguar upgrade went fairly smooth for me. I didn't have to do too
much tweaking and re-customization. I mainly moved to Jaguar for a speed
increase, and to fix various bugs, especially regarding Windows-related
things at the office.
My PowerBook remains at 10.1.5 though, since Jaguar won't
On Tuesday, January 7, 2003, at 12:05 AM, Rich & Michaela wrote:
Sorry for the rant. I don't mean to open up these old threads (wounds),
but I still don't see Jaguar's silver lining. So for now, I'm staying
put
at 10.1.5 and hoping that by the time I'm able to buy a new machine
(~12
months),
I've avoided the upgrade to Jaguar for a number of reasons.
- Annoyed over being charged for what still seems like a maintenance
release to me.
- Listening to all of the pain you folks and others have gone through
getting things to work.
I'd really like to get there, but I have dozens (hundreds
On Monday, January 6, 2003, at 03:48 PM, John Siracusa wrote:
On 1/6/03 4:40 PM, John Siracusa wrote:
On 1/6/03 4:15 PM, Ken Williams wrote:
What finally worked was to add the following to any of my .term
files,
and to ~/Library/Preferences/com.apple.Terminal.plist :
FontWidthSpacing
On 1/6/03 4:40 PM, John Siracusa wrote:
> On 1/6/03 4:15 PM, Ken Williams wrote:
>> What finally worked was to add the following to any of my .term files,
>> and to ~/Library/Preferences/com.apple.Terminal.plist :
>>
>>FontWidthSpacing
>>1.002
>
> Hm, doesn't work for me. Also, m
On 1/6/03 4:15 PM, Ken Williams wrote:
> What finally worked was to add the following to any of my .term files,
> and to ~/Library/Preferences/com.apple.Terminal.plist :
>
>FontWidthSpacing
>1.002
Hm, doesn't work for me. Also, my plist files have the value in
tags, not . I tri
Hi,
I upgraded to Jaguar this weekend and was annoyed to find that
Terminal.app had screwed up the horizontal font spacing in my setup.
I'm no font layout snob, but for some reason this was really annoying -
using Monaco 9, there was a column of pixels missing between columns 1
and 2 of text,
25 matches
Mail list logo