Re: SOLVED: Keychain use on Mac OS 10.5

On Wed, 12 Mar 2008, Claus Atzenbeck wrote:
> No, it was not the terminal. I used Alpine running inside screen that comes
> with Mac OS (/usr/bin/screen). This caused the problem. I compiled screen from
> Fink (/sw/bin/screen) and it works perfectly. This is reproducible and
> independent of the Terminal settings.

I don't quite understand the underlying 'magic' that screen uses.  But 
this sounds like screen does something (like run under another user?) 
that makes any app unable to talk to the keychain because it can't 
"connect to the window server".  I don't exactly know how that works too,
but it essentially requires the user to really be there live, not ssh-ed in
for example.

(Though I haven't actually used screen *routinely* in a long time.  I do use
it once in a while if I start a long compile over ssh via a laptop, just so
I can reconnect if the WiFi connection cuts out for example..  I finally
just got used to using multiple literal terminal windows and using cmd keys
to switch between them.  Leopard's Terminal has tabbing, but I actually
use the earlier Terminal because of the cmd-doubleclick behavior on the old
Terminal.)
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info