[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Nasty Workaround
- To: wl-en@lists.airs.net
- Subject: Re: Nasty Workaround
- From: James Harkins <jamshark70@gmail.com>
- Date: Tue, 31 May 2011 06:59:19 +0800
- Delivered-to: wl-en@lists.airs.net
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:date:message-id:from:to:subject:in-reply-to :references:user-agent:mime-version:content-type; bh=d0WQegdl1JGyGglLKfs+jgPKeeredUTKWN9OkTjhGac=; b=kMPB9xXrqHsxq2RLE13C0pUHrZa7SYorGHYOSSUh+lbUP+W24gVGyN8YjVRQtuPaxT 2HyVRB+9IXb+PjdP3CkvWgS5NE/+yFb3qRGxcBZTuADbm5kkQ2+gS1a5W8aUfrYMJuxQ D+x7TwWp9Pf8VxdcJXXzTOU2Fw+WihtQoGr3E=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:message-id:from:to:subject:in-reply-to:references:user-agent :mime-version:content-type; b=RUW8ic+yjTer1u1fTu6faGMKPi1EPbkcByrJ7yyy8EDnu9VHpUqeXhvDdqACiJIW5N DefOBEHd87zJadhUnfmjp9ZmJaA8FnAlJoNz3PNTmporYCj7pueyM4zkxi5qUGZrMZg6 E9Gmr1uwtFaPtt9i4ZJAjJxeNXbY0X/yxJbcU=
- In-reply-to: <m2ei3gxldj.wl%dave@boostpro.com>
- List-help: <mailto:wl-en-ctl@lists.airs.net?body=help>
- List-id: wl-en.lists.airs.net
- List-owner: <mailto:wl-en-admin@lists.airs.net>
- List-post: <mailto:wl-en@lists.airs.net>
- List-software: fml [fml stable 20011102.2100]
- List-unsubscribe: <mailto:wl-en-ctl@lists.airs.net?body=unsubscribe>
- References: <m2ei3gxldj.wl%dave@boostpro.com>
- Reply-to: wl-en@lists.airs.net
- User-agent: Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Gojō) APEL/10.7 Emacs/23.1 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)
At Mon, 30 May 2011 11:23:52 -0400,
Dave Abrahams wrote:
>
>
> I just thought someone with the power/knowledge to fix this problem
> should know... In order to make life with WL tolerable these days, I
> have had to add the following in my WL settings:
>
> ;;
> ;; ***** Nasty workaround ******
> ;;
> ;; for me, Wanderlust hangs trying to send or receive if I wait too
> ;; long between operations that require a connection, or put the
> ;; computer to sleep, etc. Toggling the plugged state every now and
> ;; then seems to fix it though.
I have this in my .emacs, which helped me with a similar problem.
(setq elmo-network-session-idle-timeout 300)
As a workaround, it seems dramatically less nasty.
hjh
--
James Harkins /// dewdrop world
jamshark70@dewdrop-world.net
http://www.dewdrop-world.net
"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman
blog: http://www.dewdrop-world.net/words
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks