Re: FVWM: Moving windows on mouse 2 button-down instead of button-up?
On Tue, Jul 27, 2010 at 12:23:57PM -0400, Chris Siebenmann wrote: > This doesn't happen for other buttons, eg I also have 'Mouse 1 > T N Move' and if I use mouse button 1 on window titles they move > immediately without waiting for button-up. It's also worth mentioning (for the archives) that the behaviour mentioned here, is directly related to the setting of *ClickTime* -- the higher the value, the longer delay there will be between button press, and action. -- Thomas Adam
Re: FVWM: Visual nastiness on Fedora 13
On Mon, Jul 26, 2010 at 06:30:20PM +0100, - Tethys wrote: > I've upgraded from F11 to F13. Since then, my fvwm doesn't look as > pleasing as it used to. I've kept the same ~/.fvwm/config file. > However, I now have borders around my icons, where previously there > weren't any. This only seems to apply to applications that set their > own icons. If I explicitly add an icon with a Style in my config file, > it appears without a border, as I'd expect. Secondly, my pager now has > inactive windows being mostly black, where previously they were grey. > Again, nothing has changed in my ~/.fvwm/config. Look at the following style conditions: IconBackgroundRelief IconBackgrouondColorset I suspect in your case, you just need to set IconBackgroundRelief 0, or somesuch. -- Thomas Adam
Re: FVWM: Visual nastiness on Fedora 13
On Wed, Jul 28, 2010 at 9:46 AM, Thomas Adam wrote: > I suspect in your case, you just need to set IconBackgroundRelief 0, or > somesuch. Yep, that fixed it. It still doesn't explain why the relief appeared when using the same config file and the same version of fvwm as my previous install. But at least it works now. Thanks. Tet -- “It seems intuitively obvious to me, which means that it might be wrong.” -- Chris Torek
Re: FVWM: Visual nastiness on Fedora 13
On 28 July 2010 12:02, - Tethys wrote: > On Wed, Jul 28, 2010 at 9:46 AM, Thomas Adam wrote: > >> I suspect in your case, you just need to set IconBackgroundRelief 0, or >> somesuch. > > Yep, that fixed it. It still doesn't explain why the relief appeared > when using the same config file and the same version of fvwm as my > previous install. But at least it works now. Thanks. Because FVWM is only meant to draw the relief under certain conditions by default. -- Thomas Adam
Re: FVWM: Bug with turning off user states on specific windows in fvwm 2.5.30?
On Tue, Jul 27, 2010 at 11:21:29PM +0100, Thomas Adam wrote: > On Tue, Jul 27, 2010 at 06:08:59PM -0400, Chris Siebenmann wrote: > > | On Tue, Jul 27, 2010 at 01:00:24PM -0400, Chris Siebenmann wrote: > > | > > | [.. other stuff snipped..] > > | > > | > So, either I'm missing something about fvwm 2.5.30, or there's a bug > > | > here. All things considered, the first is probably more likely -- does > > | > anyone have any ideas? > > | > > | UpdateStyles? Shouldn't be needed though as style lines are updated > > | automatically. Certainly I don't have a problem with the stuff you've > > | posted. > > > > I tried putting UpdateStyles at the end of both functions and it didn't > > seem to make a difference in what happened; it still looks like the > > window I was repeatedly iconifying and deiconifying was not getting its > > user state 1 turned off. > > > > (Also, I tried inverting the sense of the user state, so that user state > > 1 started out off, things were guarded with 'ThisWindow (!State 1)', and > > I used 'WindowStyle State 1' to turn it on, and this behaved the same > > way.) > > Committed a fix to CVS for this. Really, this time. Bloody CVS! Of course, this isn't helped by the fact that the email announcements from CVS are taking up to 9 hours to get sent out for some stupid reason. Chris -- please "cvs up" -- does this fix things for you? -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
Re: FVWM: Bug with turning off user states on specific windows in fvwm 2.5.30?
| > Committed a fix to CVS for this. | | Really, this time. Bloody CVS! Of course, this isn't helped by the | fact that the email announcements from CVS are taking up to 9 hours to | get sent out for some stupid reason. | | Chris -- please "cvs up" -- does this fix things for you? I've done this and it does indeed fix the problem; everything works fine now, with the states updating when I expect them to and so on. (And as a result, icons now place the way I'd like them to.) Thank you for the fix! (And the information on how to do use user states to solve my problem in the first place.) - cks
Re: FVWM: CMD_Exec() leaks an extra file descriptor to children
On Tue, Jul 27, 2010 at 10:49:10PM +0100, Thomas Adam wrote:
> On Tue, Jul 27, 2010 at 12:21:17PM -0400, Chris Siebenmann wrote:
> > There's a small file descriptor leak in CMD_Exec() in fvwm/builtins.c;
> > it opens /dev/null, dup2()s it to standard input, and then never closes
> > the original file descriptor before exec'ing the command.
> >
> > The neurotically correct fix for this (in what I think is the right
> > fvwm coding style) is:
> >
> > --- fvwm/builtins.c 31 Dec 2009 17:44:56 - 1.437
> > +++ fvwm/builtins.c 27 Jul 2010 16:17:52 -
> > @@ -2459,6 +2459,10 @@
> > fvmm_deinstall_signals();
> > fd = open("/dev/null", O_RDONLY, 0);
> > dup2(fd,STDIN_FILENO);
> > + if (fd != STDIN_FILENO)
> > + {
> > + (void)close(fd);
> > + }
> > if (fvwm_setpgrp() == -1)
> > {
> > fvwm_msg(ERR, "exec_function", "setpgrp failed (%s)",
> >
> > (It seems extremely unlikely that fvwm would ever have stdin closed at
> > this point, so the less neurotic fix is just '(void)close(fd);'.)
>
> You've not read any of the documentation about submitting patches.
> Nevermind, I will modify this and apply it to CVS soon -- I can't/won't
> apply it as-is.
Fixed in CVS.
-- Thomas Adam
--
"It was the cruelest game I've ever played and it's played inside my head."
-- "Hush The Warmth", Gorky's Zygotic Mynci.
Re: FVWM: Bug with turning off user states on specific windows in fvwm 2.5.30?
On Wed, Jul 28, 2010 at 04:44:04PM -0400, Chris Siebenmann wrote: > | > Committed a fix to CVS for this. > | > | Really, this time. Bloody CVS! Of course, this isn't helped by the > | fact that the email announcements from CVS are taking up to 9 hours to > | get sent out for some stupid reason. > | > | Chris -- please "cvs up" -- does this fix things for you? > > I've done this and it does indeed fix the problem; everything works > fine now, with the states updating when I expect them to and so on. > (And as a result, icons now place the way I'd like them to.) > > Thank you for the fix! > (And the information on how to do use user states to solve my problem in > the first place.) Thanks for testing. Next time, please report such observations to fvwm-work...@. -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
FVWM: FVWM Book?
Hello all, I toy with this idea at least three times a year, which must mean something. :) I know I've asked this in the past of most people, but I will ask it again -- not so much in terms of the particulars -- but if there's enough interest. Would a book on FVWM be useful? I am thinking more in terms of discussing how/what to do with FVWM, and what's needed to achieve it. The standards behind how FVWM manages windows, and how FVWM allows the user to control what this means, etc. In the past I have called for a co-contributor, but this has fallen though, so I figure if it's ever to get off the ground, I'll probably have to go it alone, alas. What do people think? Whilst I realise the idea is a little odd, seeing as a window manager changes a lot, but there's a tonne of stuff that could so easily be written to make it somewhat timeless over different revisions of FVWM. Kindly, -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
Re: FVWM: FVWM Book?
On 28/07/10 06:35 PM, Thomas Adam wrote: Hello all, I toy with this idea at least three times a year, which must mean something. :) I know I've asked this in the past of most people, but I will ask it again -- not so much in terms of the particulars -- but if there's enough interest. Would a book on FVWM be useful? I would find it useful. There's enough documentation in electronic format, but it's so much easier to flip through pages of a book, especially for this kind of thing I think it is a good idea. (Would I actually buy the book is another question. Technical books are usually quite expensive, and I am poor, but if I could I would.) What do people think? Whilst I realise the idea is a little odd, seeing as a window manager changes a lot, but there's a tonne of stuff that could so easily be written to make it somewhat timeless over different revisions of FVWM. No offence, but I don't think FVWM changes that much, so you should be fine.
Re: FVWM: FVWM Book?
On Wed, Jul 28, 2010 at 4:27 PM, sokuban wrote: > On 28/07/10 06:35 PM, Thomas Adam wrote: >> >> Hello all, >> >> I toy with this idea at least three times a year, which must mean >> something. >> :) I know I've asked this in the past of most people, but I will ask it >> again -- not so much in terms of the particulars -- but if there's enough >> interest. >> >> Would a book on FVWM be useful? > > I would find it useful. There's enough documentation in electronic format, > but it's so much easier to flip through pages of a book, especially for this > kind of thing I think it is a good idea. > > (Would I actually buy the book is another question. Technical books are > usually quite expensive, and I am poor, but if I could I would.) > >> What do people think? Whilst I realise the idea is a little odd, seeing >> as >> a window manager changes a lot, but there's a tonne of stuff that could so >> easily be written to make it somewhat timeless over different revisions of >> FVWM. > > No offence, but I don't think FVWM changes that much, so you should be fine. > > Hello, You can count on me to buy it Thomas. What I would find useful is an ebook (pdf) version with a great index. So I could search a term in all the document. Dual deal (book + ebook) would be great! Regards.
