Re: Menu invoked by FvwmButtons causes a restart
This problem and even the core dump appears to now be fixed for me. :) Just letting you know... Alex Dominik Vogt wrote: On Sat, Jul 06, 2002 at 05:00:21PM +0930, Alex Wallis wrote: With current cvs if I issue the following command in an FvwmConsole... Style * Font shadow=2 3 SE:xft:Luxi Mono:Bold:pixelsize=14 ...then click on an FvwmButtons to invoke any menu it causes fvwm to restart. The above command also resets all window styles such as TitleAtLeft etc... Don't use current cvs. There is a core dump in Flocale.c for me. If you downgrade that file to the version from two days ago it works fine. Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS domivogt: * Icon handling patch.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/07/07 08:46:06 Modified files: . : Tag: branch-2_4 ChangeLog fvwm : Tag: branch-2_4 events.c Log message: * Icon handling patch. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS domivogt: * Fixed NoClose option with unmapped panels in FvwmButtons.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/07/07 18:44:55 Modified files: . : Tag: branch-2_4 NEWS modules: Tag: branch-2_4 ChangeLog modules/FvwmButtons: Tag: branch-2_4 FvwmButtons.c Log message: * Fixed NoClose option with unmapped panels in FvwmButtons. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Notification: incoming/903
FVWM Bug Tracking notification new message incoming/903 Message summary for PR#903 From: [EMAIL PROTECTED] Subject: Moving operation delayed together with XFree86 4.2.0 xtt module Date: Sun, 07 Jul 2002 21:43:41 -0500 0 replies 0 followups ORIGINAL MESSAGE FOLLOWS From [EMAIL PROTECTED] Sun Jul 07 21:43:43 2002 Received: from util2.math.uh.edu ([129.7.128.23]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 17ROV5-c8-00 for [EMAIL PROTECTED]; Sun, 07 Jul 2002 21:43:43 -0500 Received: from malifon.math.uh.edu ([129.7.128.13] ident=mail) by util2.math.uh.edu with esmtp (Exim 4.04) id 17ROV4-00039O-00 for [EMAIL PROTECTED]; Sun, 07 Jul 2002 21:43:42 -0500 Received: from localhost ([127.0.0.1] ident=65534) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 17ROV3-c4-00 for [EMAIL PROTECTED]; Sun, 07 Jul 2002 21:43:41 -0500 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Moving operation delayed together with XFree86 4.2.0 xtt module Message-Id: [EMAIL PROTECTED] Date: Sun, 07 Jul 2002 21:43:41 -0500 Full_Name: Yin Wang Version: 2.5.2, 2.4.8 CVS_Date: OS: Redhat Linux 7.2 X_Server: XFree86-SVGA 4.2.0 Submission from: (NULL) (211.159.89.237) Hi, I've beening using my fvwm 2.5.2 and 2.4.8 with Xfree 86 on a Linux machine. All goes well with XFree86 4.1, but when change to 4.2, loaded with xtt (Xwindow True Type) module, when the windows with old style scrollbar on the left, such as xterm, FvwmConsole appear, all the moving operation of the windows will be delayed, that is, they don't move with the mouse motion, but they move some time later! There is quiet a few seconds between your operation and the window movement, and in that period you can't do any window operation! I think this is probably a fvwm bug. Because xterm moves freely with other Window Managers with xtt loaded on XFree86 4.2. I hope this will be fixed soon. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: OpaqueMove... not enough! ;)
Alas! Andrew Haninger spake thus: OpaqueResize style (that I know of)? OpaqueMove is nice, but I really I'm sure they can work on it. In the mean time, try out Style ResizeOpaque ;-). D'oh! I should learn to RTFM before I post to the list. ;) I think Fvwm comes with about 136,000 words worth of manpages, or something like that. Fun, eh? ResizeOpaque is great, exactly what I wanted. Now Fvwm is perfect ;) Thanks. -- Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- Let's not be too tough on our own ignorance. It's the thing that makes America great. If America weren't incomparably ignorant, how could we have tolerated the last eight years? -- Frank Zappa, Feb 1, 1989 -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: OpaqueMove... not enough! ;)
Now Fvwm is perfect ;) So, with that, Dominik's work is done! Andy -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FvwmPager? (was: Re: FVWM: OpaqueMove... not enough! ;))
Alas! Andrew Haninger spake thus: Now Fvwm is perfect ;) So, with that, Dominik's work is done! Maybe not quite... I'm having some trouble with FvwmPager. Not sure if it's an FvwmPager problem or what, but in fvwm 2.5.2 it doesn't seem to be able to render the pages for anything but the first desk. I find it kind of hard to describe. I use 3x2 pages per desk, but in fvwmpager only the first desk (the 0th desk) actually has 3x2 pages... all the other ones are just blank. The desk is the size of 3x2, but nothing is drawn in the desk (no page outlines, no windows, nothing). Here's a screenshot of it misbehaving: http://members.shaw.ca/feztaa/pics/fvwmpagerbad.png I guess I could settle for only having one desk, but that's kind of annoying. Is this a known issue? Or am I just doing something wrong? -- Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- QOTD: I've always wanted to work in the Federal Mint. And then go on strike. To make less money. -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FvwmPager? (was: Re: FVWM: OpaqueMove... not enough! ;))
On Sun, 7 Jul 2002, Rob 'Feztaa' Park wrote: Alas! Andrew Haninger spake thus: Now Fvwm is perfect ;) So, with that, Dominik's work is done! Maybe not quite... I'm having some trouble with FvwmPager. Not sure if it's an FvwmPager problem or what, but in fvwm 2.5.2 it doesn't seem to be able to render the pages for anything but the first desk. I find it kind of hard to describe. I use 3x2 pages per desk, but in fvwmpager only the first desk (the 0th desk) actually has 3x2 pages... all the other ones are just blank. The desk is the size of 3x2, but nothing is drawn in the desk (no page outlines, no windows, nothing). Here's a screenshot of it misbehaving: http://members.shaw.ca/feztaa/pics/fvwmpagerbad.png I guess I could settle for only having one desk, but that's kind of annoying. Is this a known issue? Or am I just doing something wrong? How do you start the pager in your .fvwm2rc? You should use a line like this: + I Module FvwmPager 0 1 in the startup funcion. 0 and 1 tells the pager the first and last desk to display. //Marcus -- Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- QOTD: I've always wanted to work in the Federal Mint. And then go on strike. To make less money. -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: fvwm-snap-20020706 crash
On Sun, Jul 07, 2002 at 11:08:33AM +0200, Riswick, J.G.A. van wrote: HI I tried the latest snapshot fvwm-snap-20020706.tar.gz but it seems to crash on startup. I tried using no fvwm2rc file, so that a basic menu should appear, but X crashes before fvwm starts up.. Please let me know if you need any more info. That's fixed in the next snapshot. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FvwmPager? (was: Re: FVWM: OpaqueMove... not enough! ;))
On Sun, Jul 07, 2002 at 02:00:01AM -0600, Rob 'Feztaa' Park wrote: I think Fvwm comes with about 136,000 words worth of manpages, or something like that. 20177 lines, 105729 words, 666190 characters :-) Alas! Andrew Haninger spake thus: Now Fvwm is perfect ;) So, with that, Dominik's work is done! *grin* Maybe not quite... I'm having some trouble with FvwmPager. Not sure if it's an FvwmPager problem or what, but in fvwm 2.5.2 it doesn't seem to be able to render the pages for anything but the first desk. I find it kind of hard to describe. I use 3x2 pages per desk, but in fvwmpager only the first desk (the 0th desk) actually has 3x2 pages... all the other ones are just blank. The desk is the size of 3x2, but nothing is drawn in the desk (no page outlines, no windows, nothing). Here's a screenshot of it misbehaving: http://members.shaw.ca/feztaa/pics/fvwmpagerbad.png I guess I could settle for only having one desk, but that's kind of annoying. Hm. Please strip down your config file as much as possible so that this still happens and post it here. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Automatically raise certain windows on mouse enter, flickering of windows and widgets
Hi there... Comments below, again: On Sat, Jul 06, 2002 at 05:40:55PM +0200, Dominik Vogt wrote: On Sat, Jul 06, 2002 at 03:02:01PM +0300, Tom Alsberg wrote: snip / Well, there are other examples, like I noted, with GTK+ buttons, Netscape toolbars, balloon titles in FvwmPager... But what *are* the problems? I'm not a psychic. Well, with GTK+ buttons, sometimes the buttons act like the pointer enters and leaves them a lot of times in a short time period, getting highlighted and un-highlighted - the same with Netscape's toolbars. With FvwmPager, when the pointer goes over a window, and then over another window, in a short period of time, sometimes the balloon showing the title of the window starts to flicker - appears and disappears continuously for a short time. And sometimes windows being automatically raised (e.g. FvwmButtons) start flickering - getting raised and lowered over and over again frequently in a short time... I do not have exact tests for those examples, though, as they do not always happen - only once in a while... Then please try to pin it down. I have no such problems with the functions. I could only pin those problems down to the actual lines in the .fvwm2rc which do the automatic raising and lowering. As I said, it does not always happen... But in some time with this setup, you notice it... But if you use this setup for a while, with some activity with automatically raised and lowered windows, then you'll probably see it a few times. Uh, but I won't. I hate auto raising. I can't use my desktop with it. :-) Oh... Well, I don't really like auto raising of my windows either... I just use it for some little windows like the icon manager, FvwmButtons, XClock, etc. which I want to see without effort (clicking, etc.) at times but I don't want them to consume space all the time... snip / I would ask now - why does this have to be a complex function? Couldn't it be, instead of a complex function, just some AutoRaise/AutoLower style? Well, what would you win with that? You'd still need a complex function to select the windows to use. Well, I suppose just use those windows with the style applied to them... No. Either you give up most of the flexibility or you have to use complex functions. snip / By enter and leave events, do you mean events of FVWM (FvwmEvent), or events in the level of X? It's roughly the same. After all, FVWM does a lot of things on enter and leave, including focus, changing window styles, etc etc. Yes, but it *does not* restack windows triggered by these events. That's the one thing that does not work Why should that be the one thing that does not work, though? snip / Let me explain. You probably think that one EnterNotify event is sent when a window is entered and one LeaveNotify event when the window is left. But that's not true. Let's assume we have two overlapping windows A and B. The most simple case would be windows without any children. In fvwm, the visible window still consists of a lot of sub windows: The top level window (frame), the Wparent window which contains the client window, and more than a dozen decorative windows. Let's assume the pointer is in the client window of A and is moved across the title bar into window B: - pointer moves into the titlebar of A Events: leave client A leave parent A enter title window A - Pointer moves into the border of A Events: leave title window A enter border A - Pointer moves directly into the client window of B. Events: leave border A leave frame A enter frame B enter parent B enter clent B And it get's much worse if pointer grabs are considered: when an application grabs the pointer, it can specify a grab context window. For example, if you open a menu (by a key stroke), the client, parent and frame of B are left and the menu window is entered, *even* if the pointer is not over the menu. The reverse events occur when the grab is released (leave menu, enter frame/ parent/client). The old window even gets enter events if the pointer is no longer over it - immediately followed by the usual leave events and the enter events on the new window hierarchy. Wow... I didn't know it's that complicated... (I hardly ever dealt with those aspects of X - which do not draw in some client window or the root window, or something) (BTW, this grabbing issue is what makes the gv zoom window vanish: the pointer is grabbed by fvwm == zoom window receives a leave event and closes. It should ignore events triggered by grabs). Why does the pointer being grabbed cause the window to receive a leave event? snip / (and *slow*)? Because enter and leave events are by fare the most common events (apart from mouse events). When they are actually communicated to a module, a lot of useless traffic is created. Oh... understood... Not that I know
FVWM: FvwmPager
Hi, I'm using fvwm2.4.0 and when I use the following config *FvwmPager: Label * Current I expected from the man page that when I switch desk, the pager label would change to reflect the Current desk. What happens, however, is that desk 0 is always labeled Current. Am I reading the man page correctly? While I'm on the subject, is there a config option to allow say 3 desks to show up in the pager with the center one being the current one? The only thing I could find was invoking FvwmPager as Module FvwmPager * X and whatever I put for X was always ignored. Thanks, Tom -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: FvwmPager
On Sun, Jul 07, 2002 at 07:51:53AM -0400, Thomas Gardiner wrote:
Hi,
I'm using fvwm2.4.0 and when I use the following config
*FvwmPager: Label * Current
I expected from the man page that when I switch desk, the pager label
would change to reflect the Current desk. What happens, however, is that
desk 0 is always labeled Current. Am I reading the man page correctly?
No, I don't think so. How should the pager know the names you
expect if all you specify is 'Current'? The line above means
Label all ('*') desks as 'Current'. You have to label all the
desks you want to use manually:
*FvwmPager: Label 1 desk1
*FvwmPager: Label 2 desk2
*FvwmPager: Label 3 desk3
And start the pager with
FvwmPager * *
While I'm on the subject, is there a config option to allow say 3 desks to
show up in the pager with the center one being the current one?
No.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
--
Visit the official FVWM web page at URL: http://www.fvwm.org/.
To unsubscribe from the list, send unsubscribe fvwm in the body of a
message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
FVWM: FvwmButtons 'hangon'
Hi there, I would like to create a panel for X-Chat using FvwmButtons, but i seem to have some problems. When X-chat is started, it gets the title X-Chat [1.8.9]: my_nick @ irc.myserver.org / #mychannel So, i define a panel *FvwmButtons: (Icon mini.xchat.xpm, \ Panel(position top,right,delay 0,UseOld,NoClose) \ X-Chat* Nop) However, X-chat doesnt seem to hang itself on the button. The wildcard should be correct, because Style X-Chat* NoTitle removes the title from the X-Chat window. Is there a solution to this problem ? A second problem i have with the FvwmButtons module is the following: i define a button just identical to the one above (i.e. with UseOld and NoClose). When i restart FVWM with the application of the button visible, everything is ok: i can still click the button to show/hide the application. But, after i restart FVWM when the application is in the hidden state, clicking the button doesnt do anything. The application is still running however, but i can't get a hold of it anymore. Is this normal ? Thanks a lot, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Problem with xmms - shaped window
On Sat, Jul 06, 2002 at 02:47:42PM +0200, Dominik Vogt wrote: Upgrade to the latest xmms release. Versions prior to 1.2.4 are *very* buggy in their window handling. The latest release works fine. I had version 1.2.4 running and upgraded to 1.2.7 but still the same problem. I had a try with windowmaker and fvwm-2.4.6 which show not that problem. I also realized that shaped windows like xmms or gkrellm are hard to move. If I try to move them quickly they alway remain a couple of points after the mouse pointer. Shaped windows appear as if the are very sluggish. Moving shaped windows consumes a lot of cpu power as well. I even had a try with fvwm-2.4.6 and windowmaker both move xmms much faster than version 2.5.1. Uwe -- +-- | Uwe Pross | mail : mailto:[EMAIL PROTECTED] | www : http://www.tu-chemnitz.de/~uwp +-- Have a nice day ;-). --- -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FvwmPager? (was: Re: FVWM: OpaqueMove... not enough! ;))
Alas! Dominik Vogt spake thus:
On Sun, Jul 07, 2002 at 02:00:01AM -0600, Rob 'Feztaa' Park wrote:
I think Fvwm comes with about 136,000 words worth of manpages, or
something like that.
20177 lines, 105729 words, 666190 characters :-)
That's not what I came up with:
[EMAIL PROTECTED]:/usr/share/man/man1$ {
-- for i in fvwm* Fvwm*
-- do
-- name=$(echo $i|perl -pi -e 's/\.1$//')
-- man 1 $name|cat
-- done
-- } | wc
26466 136635 1292843
26,466 lines, 136,635 words, 1,292,843 characters. Of course, lines
isn't meaningful here because man autowraps; the wider your terminal,
the less lines you'll get. Also, characters isn't meaninful either,
because the more lines you have, the more spaces there will be to make
up the indentation. So really, words is the only measurement that is
useful ;)
Here's a screenshot of it misbehaving:
http://members.shaw.ca/feztaa/pics/fvwmpagerbad.png
I guess I could settle for only having one desk, but that's kind of
annoying.
Hm. Please strip down your config file as much as possible so
that this still happens and post it here.
Ok, here is the config file that is as stripped as it can possibly be
while still recreating the problem:
DestroyFunc StartFunction
AddToFunc StartFunction
+ I Module FvwmPager 0 1
Those three lines in the .fvwm2rc file, with nothing else, causes this
behaviour.
But, on further inspection, Switching to another page or desk, allowing
the pager to go offscreen, fixes it. Of course, this is not possible
when it's sticky, which is how I want it.
--
Rob 'Feztaa' Park
http://members.shaw.ca/feztaa/
--
Never trust a child farther than you can throw it.
--
Visit the official FVWM web page at URL: http://www.fvwm.org/.
To unsubscribe from the list, send unsubscribe fvwm in the body of a
message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
FVWM: Re: FvwmPager?
Alas! Mikhael Goikhman spake thus: As I said several days ago on this list, this is a known problem in 2.5.2 and 2.5.1. I joined the list after you posted that ;) Any multi-desk pager (FvwmPager 0 3) even without a config will show it. The initial drawing of FvwmPager was completely broken at some point. I fixed all problems in a single desker, but not in a multi-desker. Any chance you'll fix the rest of it? -- Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- She cried, and the judge wiped her tears with my checkbook. -- Tommy Manville -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
RE: FVWM: fvwm-snap-20020706 crash never mind
HI never mind that one, there was a corrupted fvwm2rc file in my home dir. jos -Original Message- From: Riswick, J.G.A. van To: 'fvwm@fvwm.org' Sent: 7/7/2002 11:08 AM Subject: FVWM: fvwm-snap-20020706 crash HI I tried the latest snapshot fvwm-snap-20020706.tar.gz but it seems to crash on startup. I tried using no fvwm2rc file, so that a basic menu should appear, but X crashes before fvwm starts up.. Please let me know if you need any more info. message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: Scroll Lock mode
Hi again, I have been coping with a specific problem ever since i started using fvwm one year ago. For some reason, from time to time my key bindings stopped working, and closing windows by clicking on the button in the top left corner of the window didn't work either. Because i couldn't reproduce the error, i didn't mention it (yet). However, i seem to have found the reason: going into 'Scroll Lock' mode seems to change some things that make fvwm ignore these events. It's a mystery to me how i get into that 'scroll lock' mode, but pressing scroll lock seems to solve the problem every time (and pressing it again causes the events to be ignored again). Is there a solution to this ? cheers, Remko -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Re: FvwmPager?
On Sun, Jul 07, 2002 at 07:38:13PM +, Mikhael Goikhman wrote: On 07 Jul 2002 11:41:01 +0200, Dominik Vogt wrote: On Sun, Jul 07, 2002 at 02:00:01AM -0600, Rob 'Feztaa' Park wrote: Maybe not quite... I'm having some trouble with FvwmPager. Not sure if it's an FvwmPager problem or what, but in fvwm 2.5.2 it doesn't seem to be able to render the pages for anything but the first desk. I find it kind of hard to describe. I use 3x2 pages per desk, but in fvwmpager only the first desk (the 0th desk) actually has 3x2 pages... all the other ones are just blank. The desk is the size of 3x2, but nothing is drawn in the desk (no page outlines, no windows, nothing). Here's a screenshot of it misbehaving: http://members.shaw.ca/feztaa/pics/fvwmpagerbad.png I guess I could settle for only having one desk, but that's kind of annoying. Hm. Please strip down your config file as much as possible so that this still happens and post it here. As I said several days ago on this list, this is a known problem in 2.5.2 and 2.5.1. Any multi-desk pager (FvwmPager 0 3) even without a config will show it. The initial drawing of FvwmPager was completely broken at some point. I fixed all problems in a single desker, but not in a multi-desker. Are you saying that the bug is still in the post-2.5.2 development code? I don't see any problem. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FvwmPager? (was: Re: FVWM: OpaqueMove... not enough! ;))
On Sun, Jul 07, 2002 at 02:10:10PM -0600, Rob 'Feztaa' Park wrote:
Alas! Dominik Vogt spake thus:
On Sun, Jul 07, 2002 at 02:00:01AM -0600, Rob 'Feztaa' Park wrote:
I think Fvwm comes with about 136,000 words worth of manpages, or
something like that.
20177 lines, 105729 words, 666190 characters :-)
That's not what I came up with:
[EMAIL PROTECTED]:/usr/share/man/man1$ {
-- for i in fvwm* Fvwm*
-- do
-- name=$(echo $i|perl -pi -e 's/\.1$//')
-- man 1 $name|cat
-- done
-- } | wc
26466 136635 1292843
Wow, so much code just to cout words. With zsh:
$ wc **/*.1
That's all :-) Of course it counts formatting instructions too.
26,466 lines, 136,635 words, 1,292,843 characters. Of course, lines
isn't meaningful here because man autowraps; the wider your terminal,
the less lines you'll get. Also, characters isn't meaninful either,
because the more lines you have, the more spaces there will be to make
up the indentation. So really, words is the only measurement that is
useful ;)
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
--
Visit the official FVWM web page at URL: http://www.fvwm.org/.
To unsubscribe from the list, send unsubscribe fvwm in the body of a
message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Scroll Lock mode
On Sun, Jul 07, 2002 at 11:00:04PM +0200, Remko Troncon wrote: I have been coping with a specific problem ever since i started using fvwm one year ago. For some reason, from time to time my key bindings stopped working, and closing windows by clicking on the button in the top left corner of the window didn't work either. Oh dear! You've lived with the most frequently encountered problem for a year without knowing that the solution is written in big friendly letters right at the front of the fvwm FAQ. ;-) Because i couldn't reproduce the error, i didn't mention it (yet). However, i seem to have found the reason: going into 'Scroll Lock' mode seems to change some things that make fvwm ignore these events. It's a mystery to me how i get into that 'scroll lock' mode, but pressing scroll lock seems to solve the problem every time (and pressing it again causes the events to be ignored again). Is there a solution to this ? Yes. The one I recommend is to disable the scroll-lock, num-lock and possibly caps-lock keys conpletely. From our FAQ (note that you need at least fvwm-2.4.0 for the IgnoreModifiers command): -- snip 5.5 Why do NumLock, CapsLock and ScrollLock interfere with ClickToFocus and/or my mouse bindings? A: Because they are treated as modifiers. You can use the IgnoreModifiers command to turn individual modifiers off for bindings. With XFree86 the right command is IgnoreModifiers L25 If you changed your modifiers manually or are using a different X server use the 'xmodmap' command to find out which modifiers correspond to the keys you want to switch off. This command creates a lot of extra network traffic, depending on your CPU, network connection, the number of Key Mouse commands in your configuration file and the number of modifiers you want to ignore. If you do not have a lightning fast machine or very few bindings you should not ignore more than two modifiers. So do not ignore scroll-lock if you have no problem with it. A better way to solve this problem is to modify the keyboard mapping of your X server. The commands xmodmap -e clear Lock xmodmap -e clear Mod2 xmodmap -e clear Mod5 remove the CapsLock, NumLock and ScrollLock from the keyboard map. Pressing these keys has no effect then. To re-add them try this: xmodmap -e add Lock = Caps_Lock xmodmap -e add Mod2 = Num_Lock xmodmap -e add Mod5 = Scroll_Lock Fvwm has to be restarted to use the changes made by xmodmap. Please refer to the man page of the xmodmap command for further details. If you disable the CapsLock key in your keyboard map in this way, you can speed up fvwm a bit by removing the Lock modifier from the list of ignored modifiers: IgnoreModifiers -- snip Don't hesitate to ask for further help. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: FvwmPager
On Sun, Jul 07, 2002 at 04:19:50PM -0400, Thomas Gardiner wrote: Okay, then maybe the man page is written incorrectly? I find this in the man page for FvwmPager: *FvwmPager: Label desk label Assigns the text label to desk desk (or the current desk if desk is *) in the pager window. Useful for assigning symbolic names to desktops, i.e. My interpretation of the first sentence is that if I do *FvwmPager: Label * my_label that the current desk should be labeled my_label. I guess I'm misunderstanding this sentence... As for the labels for the rest of the desks, I'm finding that by default they are labeled Desk # where # is the desk number. Ah, sure. I shouldn't have replied without re-reading the man page. The '*' applies to the desk that is currently shown when the pager is created. If you start the pager while desk 2 is shown, the label is applied to desk 2. If you'r on desk 345, it's applied to desk 345. It's not dynamic. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Problem with xmms - shaped window
On Sun, Jul 07, 2002 at 05:08:11PM +0200, Uwe Pross wrote: On Sat, Jul 06, 2002 at 02:47:42PM +0200, Dominik Vogt wrote: Upgrade to the latest xmms release. Versions prior to 1.2.4 are *very* buggy in their window handling. The latest release works fine. I had version 1.2.4 running and upgraded to 1.2.7 but still the same problem. I had a try with windowmaker and fvwm-2.4.6 which show not that problem. I also realized that shaped windows like xmms or gkrellm are hard to move. If I try to move them quickly they alway remain a couple of points after the mouse pointer. Shaped windows appear as if the are very sluggish. Moving shaped windows consumes a lot of cpu power as well. I even had a try with fvwm-2.4.6 and windowmaker both move xmms much faster than version 2.5.1. Um, you're using 2.5.1? Bad choice - and I fear it's even worse. You don't happen to have a snapshot that was mad prior to 6th of March? That explains the problem with slow window movement. It's upgrade time again ;-) 2.5.1 (and the earlier snapshots) don't even deserve to be called 'alpha' quality. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FvwmPager? (was: Re: FVWM: OpaqueMove... not enough! ;))
Alas! Dominik Vogt spake thus:
On Sun, Jul 07, 2002 at 02:10:10PM -0600, Rob 'Feztaa' Park wrote:
Alas! Dominik Vogt spake thus:
On Sun, Jul 07, 2002 at 02:00:01AM -0600, Rob 'Feztaa' Park wrote:
I think Fvwm comes with about 136,000 words worth of manpages, or
something like that.
20177 lines, 105729 words, 666190 characters :-)
That's not what I came up with:
[EMAIL PROTECTED]:/usr/share/man/man1$ {
-- for i in fvwm* Fvwm*
-- do
-- name=$(echo $i|perl -pi -e 's/\.1$//')
-- man 1 $name|cat
-- done
-- } | wc
26466 136635 1292843
Wow, so much code just to cout words. With zsh:
$ wc **/*.1
That's all :-) Of course it counts formatting instructions too.
Exactly -- my way doesn't count formatting stuff. It's not really that
hard, all I'm doing is taking the .1 off the name so that man will
display it, and then counting everything. And I don't know if you store
your fvwm manpages somewhere other than the default location, but
that would count all the words in all the manpages that I have ;)
--
Rob 'Feztaa' Park
http://members.shaw.ca/feztaa/
--
Do people know you have freckles everywhere?
--
Visit the official FVWM web page at URL: http://www.fvwm.org/.
To unsubscribe from the list, send unsubscribe fvwm in the body of a
message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
