On Sun, Apr 27, 2008 at 7:43 AM, Doug Ransom [EMAIL PROTECTED] wrote:
Lignon
s/gn/ng/
--
--
This message is sent to you because you are subscribed to
the mailing list yojimbo-talk@barebones.com.
To unsubscribe, send mail to:
I too have had no end of sync problems since I upgraded to Yojimbo 1.5
I have tried resetting various sync options, etc. etc.. In my case
dotmacsyncclient and/or Yojimbo crashes every time a sync is
attempted, normally after a long time running and whilst consuming
considerable system resources
On Dec 20, 2007 6:26 AM, Robert Sweet [EMAIL PROTECTED] wrote:
[...]
You're not alone, but I have no advice. Leopard kinda sucks.
Nice to know it isn't just me... sort of.
I haven't upgraded to Leopard yet, so I'm quite sure this is all due
to Yojimbo 1.5, although I guess there could be
Thank you for your reply.
I have already submitted crash logs for both Yojimbo and
dotmacsyncclient as well as a detailed report of my system
configuration. Pleas feel free to contact me if you have specific
things you want me to try and I will do the best I can and provide
relevant logs and
This is pretty serious (I heavily rely on PDF's not being distorted). Where
is PDF2RTFService located and who provides it?
--j
On Dec 9, 2007 7:30 AM, Alan Rogers [EMAIL PROTECTED] wrote:
On Dec 8, 2007 11:23 AM, John Stephens [EMAIL PROTECTED] wrote:
Posted 2007-12-07 09:17:19 by Alan
If you are implementing more fine grained control over the keychain, it
would be nifty if sync could still work even if I have not yet unlocked
Yojimbo for interactive access. Maybe Sync could use the state of the login
keychain?
I'm afraid that if I set the password timeout too short, it will
