on Fri, 28 Dec 2001 03:37:18PM -0500, Brian Nelson insinuated:
> Well, that's not my only beef with WMaker. Also on that list:
[...]
> - won't save the omnipresent attribute across sessions (I had to hack
what version are you running? i've got 0.41, and it saves that
attribute fine ...
<[EMA
"Karsten M. Self" writes:
> on Fri, Dec 28, 2001 at 11:17:46AM -0500, Noah Meyerhans ([EMAIL PROTECTED])
> wrote:
> > On Fri, Dec 28, 2001 at 09:50:58AM -0500, Brian Nelson wrote:
> > >
> > > No, but it's a known bug in wmaker that's been there for a while. For
> > > me, making any window omni
on Fri, Dec 28, 2001 at 11:17:46AM -0500, Noah Meyerhans ([EMAIL PROTECTED])
wrote:
> On Fri, Dec 28, 2001 at 09:50:58AM -0500, Brian Nelson wrote:
> >
> > No, but it's a known bug in wmaker that's been there for a while. For
> > me, making any window omnipresent will pin the cpu usage at 100%.
On Fri, Dec 28, 2001 at 09:50:58AM -0500, Brian Nelson wrote:
>
> No, but it's a known bug in wmaker that's been there for a while. For
> me, making any window omnipresent will pin the cpu usage at 100%. I
> gave up on wmaker and switched to KDE.
>
Actually, it is trivial to work around. Ther
wrenkin <[EMAIL PROTECTED]> writes:
> I really like Windowmaker, and the recent release of 0.80 has caused me
> to give it another shot. the reason I left it was because it was a CPU
> hog. Whenever I ran it, a few minutes after starting up it would shoot
> to 30% CPU usage, and xfree68_s3 (The Tr
I really like Windowmaker, and the recent release of 0.80 has caused me to give
it another shot. the reason I left it was because it was a CPU hog. Whenever I
ran it, a few minutes after starting up it would shoot to 30% CPU usage, and
xfree68_s3 (The Trio64+ is not supported in Xfree 4.1.0) wou
6 matches
Mail list logo
