From: Con Kolivas <kernel@kolivas.org>
To: Valdis.Kletnieks@vt.edu, Danek Duvall <duvall@emufarm.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] O6.1int
Date: Sat, 19 Jul 2003 00:52:37 +1000 [thread overview]
Message-ID: <200307190052.38021.kernel@kolivas.org> (raw)
In-Reply-To: <200307181443.h6IEhnq3002916@turing-police.cc.vt.edu>
On Sat, 19 Jul 2003 00:43, Valdis.Kletnieks@vt.edu wrote:
> On Fri, 18 Jul 2003 00:07:49 PDT, Danek Duvall said:
> > I did discover under O6.1int that I could make xmms block indefinitely
> > when opening a window, with fvwm's wire frame manual placement, which I
> > hadn't ever noticed before, but I'm not sure if that's because it
> > actually wasn't there before, or I just placed the windows more quickly.
>
> This could be a result of fvwm grabbing the X server while the wireframe
> stuff is going on, and xmms being blocked trying to update the image on
> screen (think "scrolling song title" ;)
I'm pretty sure if you were really unlucky you could hit just the wrong timing
with O6.1 which might do this. O7 I believe addresses this.
Con
prev parent reply other threads:[~2003-07-18 15:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 2:13 [PATCH] O6.1int Con Kolivas
2003-07-17 2:39 ` Wade
2003-07-17 7:45 ` Felipe Alfaro Solana
2003-07-17 7:53 ` Con Kolivas
[not found] ` <20030717045435.GA630@lorien.emufarm.org>
[not found] ` <200307171712.20193.kernel@kolivas.org>
[not found] ` <200307171635.25730.kernel@kolivas.org>
2003-07-17 8:04 ` Danek Duvall
2003-07-17 8:21 ` Con Kolivas
2003-07-17 8:52 ` Eugene Teo
2003-07-17 9:06 ` Mike Galbraith
2003-07-18 7:07 ` Danek Duvall
2003-07-18 9:40 ` Rudo Thomas
2003-07-18 9:45 ` Zwane Mwaikambo
2003-07-18 14:43 ` Valdis.Kletnieks
2003-07-18 14:47 ` Danek Duvall
2003-07-18 14:52 ` Con Kolivas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200307190052.38021.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=duvall@emufarm.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.