From: Valdis.Kletnieks@vt.edu
To: Danek Duvall <duvall@emufarm.org>
Cc: Con Kolivas <kernel@kolivas.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] O6.1int
Date: Fri, 18 Jul 2003 10:43:49 -0400 [thread overview]
Message-ID: <200307181443.h6IEhnq3002916@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 18 Jul 2003 00:07:49 PDT." <20030718070749.GA12466@lorien.emufarm.org>
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
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" ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next 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 [this message]
2003-07-18 14:47 ` Danek Duvall
2003-07-18 14:52 ` Con Kolivas
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=200307181443.h6IEhnq3002916@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=duvall@emufarm.org \
--cc=kernel@kolivas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).