Re: FVWM: Question regarding actions when modifier keys are held down/released
> Another interesting idea - although I think I'm starting to lean toward > having the pager pop up when the desk change is initiated, and then the > only problem is how to allow multiple desk changes without releasing the > Ctrl-Alt keys, and how to make sure the pager closes after releasing the > keys. Well, as Thomas Adam points out, you can just use FvwmPager -transient. You can then use up/down/left/right to move towards a page, then hit any key to dismiss it. With just -transient it wont show other desks, so you'd have to pick the number of desks you want and provide that as a max. For example, I use five here (for six desks): Key Alt_L A C FvwmPager -transient 0 5 So, have a pager that shows 5 desktops (and however many pages you've already defined), summon that pager by hitting ctrl and then alt (because control is used as the modifier) and use the arrow keys to move from page to page. The pager just seems to support doing this, using arrows to move page to page, I mean. I don't know where this is documented. I just happened to notice it when I was testing it. To move a desk, you'd need another keybinding. Unless there is some other key for this, as I'm not even sure where the arrow keys are documented. But you might want to use different keys for moving by a full desk. Either way, here's how you could move a desk up or down, again using zero to five desks (total of size): Key Right A CM GotoDesk 1 0 5 Key Left A CM GotoDesk -1 0 5 Because it uses the same keys as those for summoning the pager you might get some drawing oddities, but it will still move like it's supposed to. This doesn't quite fit your desire of dismissing after landing on your target desk, though, so you mgiht just want to use ctrl + arrow to move (get rid of M modifiers above) so it doesn't interfere with the pager. This will allow the pager to stay up until you dismiss it with something (like space or enter or any key other than arrows, I think). So be sure to do something like this, too: Style FvwmPager Sticky, StaysOnTop > > >I had experimented with using the windows key to do something on its > >own when not being used as a modifier key, but I eventually discarded > >it. I posted about it to the fvwm forums, which can be found here: > >https://fvwmforums.org/phpBB3/viewtopic.php?f=6=2832#p14222 > > Hrm... I get all kinds of warnings when I access that page, and no > information in any of the three posts. Is there another place to access > the information? Sorry about that. It worked briefly but now it seems it has been "archived".. I presume that someone saw mention of the errors and went off to either fix it or just archive the content off to make it available elsewhere... It was a filthy hack anyway. Essentially I re-assign stdout to dev null so that I can import xlib, which will complain about something I can't recall to standard out which fvwm would choke on from a piperead, then I tested to see if a modifier was still held down within a certain timeout so that I could ignore any long presses, eg presses where the modifier was being used as a modifier to press some other key because it took longer to do that then it did to just whack the modifier as a bound key. Then I wrote the command I wanted Fvwm to run to FvwmCommand. But really, use Thomas's suggestion, as usual, it's terse and entirely on point.
Re: FVWM: Question regarding actions when modifier keys are held down/released
On Thu, Aug 29, 2019 at 8:43 AM Dave Weller-Fahy wrote: > > On Thu, Aug 29, 2019 at 2:16 AM Martin Cermak wrote: > > On Wed 2019-08-28 13:03 , Dave Weller-Fahy wrote: > > > My goal is to have the following rules followed. > > > > > > Rules about keys being pressed and (possibly) held. > > > - If Ctrl-Alt are pressed ... > > > - and if no other keys are pressed within some period of time ... > > > - then pop up the pager > > > - and if other keys (such as arrow keys) are pressed ... > > > - then execute some other action > > > > > > Rules about keys being released. > > > - If Ctrl-Alt are released ... > > > - and if the pager is displayed ... > > > - then remove the pager > > > > > > The use case is to have Ctrl-Alt-(up|down|left|right) change desks, > > > > I have this setup too (as an option). But primarily I use > > Ctrl-Alt-(). This gives me a clear idea which > > of my 9 desks (arranged as a 3x3 matrix) I am switching to. > > Nothing visual involved. > > Thanks for the confirmation! I have the Ctrl-Alt-direction (or any other > arbitrary key combination to change desktops) working perfectly: I > should have been more clear on that. The thing I've not been able to > accomplish is getting the pager to pop up when keys are pressed and > then go away when those same keys are released. > > I was reaching the conclusion that what I wanted was not possible with > fvwm (at least, not possible without an external utility), but figured I > would check with the mailing list before giving up and looking for an > external utility to help. I may also try fvwm3 to see if what I want is > possible there. > You can bind a key to a modifier and set the unbound one as your modifier (Key Control_L A M Exec exec executable.nameor Key Alt_L A C Exec exec executable.name or ...) And that can still be used for some other action (Key T A CM Exec exec other-executable.name would still work, for example) but it will cause your executable to be executed even when you're just using the alt and control as modifiers. You could make a wrapper script that uses xlib and does a `display.query_keymap()` to see if the keys are still being held down. Then if after a set time the key isn't still held, you might decide that the wrapper was invoked intentionally and should then call a function in fvwm to toggle your pager. It would take a little getting used to, as you'd train yourself to hold modifier keys for a brief pause when executing stuff other than toggling the pager, but it's not impossible. I had experimented with using the windows key to do something on its own when not being used as a modifier key, but I eventually discarded it. I posted about it to the fvwm forums, which can be found here: https://fvwmforums.org/phpBB3/viewtopic.php?f=6=2832#p14222
Re: FVWM: Controlling initial size of a "gThumb" window
On Thu, Jun 20, 2019 at 12:13 PM Dan Espen wrote: > > Dr Rainer Woitok writes: > > > Dan, > > > > On Thursday, 2019-06-20 08:43:02 -0400, you wrote: > > > >> ... > >> I don't think Fvwm will do that, especially for an application going > >> full screen. If the application was in a window, you might be able to > >> use Fvwm resize. > > > > That's what I've feared ... :-( > > Full screen windows are commonly called override-redirect or unmanaged > windows. > > >> However, it seemed to me that it was pretty straight forward to > >> configure gthumb not to use full screen. > > > > No. The "gthumb" you fought with was version 3.6.2, mine is version > > 3.4.3. Neither is there any point where right-clicking produces a "Re- > > size" option, does removing ~/.config/gthumb/" or pressing the Escape > > key have the effect you described, nor is there a "Fullscreen" option > > under "Settings -> Browser". Bummer. > > Try one of these: > > http://ftp.acc.umu.se/pub/GNOME/sources/gthumb/ > > versions 1.105 to 3.8. > > -- > Dan Espen > I wasn't able to get it to behave in the same way, but the following may work: Style gThumb NoPPosition, InitialMapCommand Resize 20 20 The motivation for NoPPosition is so it wont be able to move itself to it's remembered position at 0 0 when it was fullscreen and as for the Resize you'd probably want to pick a different value.
Re: FVWM: Controlling initial size of a "gThumb" window
On Thu, Jun 20, 2019 at 8:44 AM Dan Espen wrote: > > Dr Rainer Woitok writes: > > > Greetings, > > > > On Wednesday, 2019-06-19 14:32:06 -0700, Ronald F. Guilmette wrote: > > > >> In message , > >> Dan Espen wrote: > >> > >> >So, I'm afraid I can't duplicate your issue but I can see gthumb > >> >is really buggy. > >> > >> I'm not sure that's a proper assumption. > >> ... > > > > Sorry, it was not my intention to fire up a discussion about "gthumb". > > And in particular not on this list. It was just the unwanted behaviour > > of this particular programme which made me look for a way to counter it. > > Sorry, was trying to explain why I could only do so much testing. > > > So let me rephrase my request without mentioning a particular programme: > > > > Is there a way to tell "fvwm" to open a window using a particular init- > > ial size? I'm aware of > > > >Style xxx PositionPlacement HOR VERT > > > > but I'm interested in specifying exactly the other two parameters from a > > normal "WIDTHxHEIGHT+HOR+VERT" X11 geometry specification. And I only > > want to specify an INITIAL size, the user should be able to later manu- > > ally change the window size. > > I don't think Fvwm will do that, especially for an application going > full screen. If the application was in a window, you might be able to > use Fvwm resize. > > However, it seemed to me that it was pretty straight forward to > configure gthumb not to use full screen. > > -- > Dan Espen > Perhaps try the style option NoPPosition on the window in question?
Re: FVWM: Strange problem with localhost
On Mon, Jun 17, 2019 at 4:09 PM Ronald F. Guilmette wrote: > > Sorry if this is off topic, but I'm having a very weird problem with > the name "localhost" and I wonder if perhaps any of you folks could > help me to sort it out. There's probably nothing wrong with localhost per se... > > Basically, once I start up X and fvwm, I see that all of my xterm > windows are automagically inheriting the following environment variable > and the value shown: How did you start up "X"? Which "X" are you running? What OS and are you using a login manager, display manager, etc? > > DISPLAY localhost:0.0 Xorg inherits the DISPLAY value from its environment which is generally set by your display manager (or xinit?) but I thought modern X servers didn't listen on TCP by default. AFAIK, having the host specified in your DISPLAY will make it use tcp for the connection even if the value is localhost and it sounds like maybe your system isn't listening on TCP, which is pretty normal these days. > > For reasons I'm none too clear on, this worked just fine for me earlier, > but I diddled a few things on this system since then and now I seem to > have broken it somehow. Now, when I try to start up *any* browser (and > probably also any X application) I get rather cryptic failure messages. > The one from teh Opera browser is clear enough. It says it cannot connect > to the X server on startup. Perhaps you inadvertently set the value of DISPLAY in one of your dot files and that's the actual problem? > > I futzed around trying to fix this problem for awhile and I managed to > discover that if I manually set DISPLAY instead to just :0.0 then suddenly > all my X applications start to work again. Right, because it stops trying to use the TCP transport and uses local instead. > > Here is the output from the command "getent hosts localhost" on the system > in question: > > ::1 localhost > 127.0.0.1 localhost localhost.tristatelogic.com > > > What am I doing wrong? Why doesn't the default value of localhost:0.0 > for DISPLAY work just as well as :0.0 ? In summary, localhost:0.0 says to use the TCP transport for the connection instead of local and your system is probably not listening on tcp. Not sure how you ended up there, though. I suggest a liberal use of "grep -r DISPLAY" in your home and maybe etc to try and locate the culprit.
doc/fvwm/description.xml edits
I noticed a grammatical error at the beginning of the man page so I started poking around the web site to figure out how to contribute. In accordance with FAQ 5.1, I've fetched the latest release and made my (very minor documentation) changes. In accordance with FAQ 5.2, I've updated the ChangeLog file and created a patch (attached). Initially I was going to delete an extra comma, but once I had the document in front of me I noticed a few other minor things that I've also fixed. While changing stuff I noticed that sometimes an fvwmref element is used around reserved words and other times it's not. What's the rule for when to use an fvwmref and when not? Also, should these files use no more than 79 columns per line? I saw a note about that for source code in CONVENTIONS after making my edits. While looking for instructions on how to contribute, I noticed an issue with the web site. However the http://fvwm.org/documentation/faq/ is generated, under the answer in section 5.2 there is a link to dev_cvs.php that includes the trailing period of the sentence and makes it a broken link. Also under 5.2, there are references to doc/DEVELOPERS and doc/CONVENTIONS but it appears that these files actually exist under docs. The instructions in the CONVENTIONS file appear to be out of date or maybe just incomplete, it refers to fvwm/fvwm.1.in for details on formatting but this file doesn't appear to exist anymore. ? minor-doc-edits.patch Index: ChangeLog === RCS file: /home/cvs/fvwm/fvwm/ChangeLog,v retrieving revision 1.3151 diff -u -u -r1.3151 ChangeLog --- ChangeLog 14 Apr 2013 08:39:09 - 1.3151 +++ ChangeLog 6 Apr 2014 00:44:35 - @@ -1,3 +1,7 @@ +2014-04-05 Stephen Dennison stephenrd(at)gmail(dot)com + * doc/fvwm/description.xml: + fixed minor grammatical errors + 2013-04-14 Dominik Vogt dominik(dot)vogt(at)gmx(dot)de * libs/fsm.c (CompletNewConnectionMsg, FreeAuthenticationData) Index: doc/fvwm/description.xml === RCS file: /home/cvs/fvwm/fvwm/doc/fvwm/description.xml,v retrieving revision 1.1 diff -u -u -r1.1 description.xml --- doc/fvwm/description.xml 10 Mar 2007 05:15:34 - 1.1 +++ doc/fvwm/description.xml 6 Apr 2014 00:44:36 - @@ -22,7 +22,7 @@ feel. Since then, fvwm has been greatly enhanced and practically all fvwm95 features can be achieved by fvwm./para -paraFvwm provides both, a large +paraFvwm provides both a large emphasis remap='I'virtual desktop/emphasis and emphasis remap='I'multiple disjoint desktops/emphasis @@ -35,16 +35,16 @@ paraFvwm provides emphasis remap='I'keyboard accelerators/emphasis -which allow you to perform most window manager functions, -including moving and resizing windows, and operating the menus, +that allow you to perform most window manager functions, +including moving and resizing windows and operating the menus, using keyboard shortcuts./para paraFvwm has also overcome the distinction between configuration commands and action commands that most window managers make. Configuration commands typically set fonts, colors, menu -contents, key and mouse function bindings, while action commands +contents, and key and mouse function bindings, while action commands do things like raise and lower windows. Fvwm makes no such -distinction, and allows anything to be changed at any time./para +distinction and allows anything to be changed at any time./para paraOther noteworthy differences between fvwm and other X11 window managers are the introduction of the fvwmref cmd=Style opt=SloppyFocus/ and fvwmref cmd=Style opt=NeverFocus/
FVWM: Drag to create an xterm
On Thu, 31 Mar 2005 14:49:07 +0100, Tavis Ormandy [EMAIL PROTECTED] wrote: On Thu, Mar 31, 2005 at 02:02:10PM +0200, Uwe Pross wrote: Hi there, recently I saw a demonstration of plan 9 where the presenter clicked on the root window and dragged a rectangle to start a terminal with position and size of the drag gesture. I think this is a really nice way to start and place xterms or other apps. I am thinking of writing a fvwm function to achieve this and stuck currently at following points. - A grid should be drawn while dragging. - Xterm (or another app) should be started on key release. Any suggestions how to achieve the desired behaviour? Wow, that's a really cool idea! The fist part is no problem, it's easy to start an xterm when drawing a rectangle and identifying the pointer position when you started, but I'm not sure how you could find the length and width of the rectangle. Something like this should start an xterm at the stroke start position when you draw a rectangle on the root window: AddToFunc StrokeFuncWrapper + I SetEnv StrokeStart +$[pointer.x]+$[pointer.y] + I StrokeFunc DrawMotion FeedBack StrokeWidth 2 EchoSequence AddToFunc StartStrokeXterm I Exec exec xterm -g $[StrokeStart] Mouse 3 R A StrokeFuncWrapper Stroke N741236987 0 R N StartStrokeXterm I can't think of anyway to identify the geometry of the drawn rectangle, my first thought was to capture the output of EchoSequence, but unfortunately that isn't much use. -- - [EMAIL PROTECTED] | finger me for my gpg key. --- Cool, indeed. I dont appear to have stroke support compiled into mine, but I was able to create an effect sort of like what you describe. I use FvwmEvent in conjunction with a variable to decide whether or not to immediately resize the last window created. Then I bind the middle mouse button to set that variable and to spawn an xterm at the cursor position. # .fvwm2rc modifications # # set default to not resize new windows SetEnv doResizeStuff false Mouse 2 R A PlaceTermWithResize DestroyFunc PlaceTermWithResize AddToFunc PlaceTermWithResize + H Exec exec xterm -geom 10x1+$[pointer.x]+$[pointer.y] + H SetEnv doResizeStuff True #following requires that FvwmEvent has been started already *FvwmEvent: add_window CheckXtermResize DestroyFunc CheckXtermResize AddToFunc CheckXtermResize + I Test ($[doResizeStuff]) Resize + I SetEnv doResizeStuff False # To use it, you click the middle mouse button, drag diagonally, release the button at any time, and click again to set the lower right bounds. I use M instead of I in PlaceTermWithResize because it seemed slightly more correct in appearance. Not entirely correct. With I, you had to click to do the resize. With M, it's already doing the resize, but you have to let go of the button before it will show you the outline... and then you have to click again for it to finish the resize. --s.r.d. p.s.: Oops! I did a reply to the wrong address the first time around... -- 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: Run applicition after key release
On Fri, 25 Feb 2005 00:14:28 +, Thomas Adam [EMAIL PROTECTED] wrote: On Thu, Feb 24, 2005 at 12:54:09PM -0500, Dan Espen wrote: To Fvwm, it looks like you hit the key many times. Indeed. I suppose you could kludge the delay: Key X A M Schedule 1000 exec xterm While this will delay the execution slightly, holding down the key combination will still result in the xserver queing the key press events -- but the rate of xterms launced might diminish as a result. :) Try it and see. -- Thomas Adam -- I know nothing, and understand even less. I liked this solution, so I expanded it a bit to better match the original request. I created the following: #===begin config changes for sample 1=== Key X A CM CarefulOpen xterm -bg black -fg green Key Y A CM CarefulOpen firefox #Set the following variable to the delay in ms to prevent additional windows #from being opened for the duration of that delay SetEnv open_delay_ms 5000 DestroyFunc CarefulOpen AddToFunc CarefulOpen + I PipeRead echo 'Test ( \!\$\[dont_open_$0\] \) DoOpen $*' + I PipeRead echo SetEnv dont_open_$0 True DestroyFunc DoOpen AddToFunc DoOpen + I Exec exec $* + I Schedule 5000 PipeRead echo SetEnv dont_open_$0 False #===end config changes for sample 1=== In this sample, holding ctrl+alt+x will only allow one xterm per five seconds of holding the key down. So if you hold the combo down for only 2-3 seconds, you will only get one xterm - and it gives you that xterm immediately. Unfortunately this has a small limitation, if you try it with the same command, but different argument lists, it can't distinguish between the two of them. ie, the following two would look like a match: Key X A CM CarefulOpen xterm -bg black -fg green Key Y A CM CarefulOpen xterm -bg white -fg black Hit either of them, and you'd have to wait 5 seconds before you could hit the other. This is because the match is done off of just the first argument. So I made this more generic solution as well: #===begin config changes for sample 2=== Key X A CM CarefulOpen_xterm #Set the following variable to the delay in ms to prevent additional windows #from being opened for the duration of that delay SetEnv open_delay_ms 5000 SetEnv safe_to_open_xterm True DestroyFunc CarefulOpen_xterm AddToFunc CarefulOpen_xterm + I Test ($[safe_to_open_xterm]) DoOpen_xterm DestroyFunc DoOpen_xterm AddToFunc DoOpen_xterm + I SetEnv safe_to_open_xterm False + I Exec exec xterm + I Schedule $[open_delay_ms] SetEnv safe_to_open_xterm True #===end config changes for sample 2=== If anyone is feeling more adventurous, they could take sample 1 and escape out the entire argument list to generate a suitable variable name instead of how I have only used the first argument, and that would eliminate the need for copying sample 2 and creating 2 functions for each new command. Could probably replace my 'Exec exec $*' in sample 1 with PipeRead echo $* and then it could be bound to menus and functions instead of just stuff to be exec'ed. --s.r.d. -- 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: How to define a double click on FvwmButtons?
On Thu, 20 Jan 2005 02:30:26 +0800, Yin susu [EMAIL PROTECTED] wrote: As,i know, *MyButtons: (1x5, Frame 0, Icon 48x48/gimp.png, \ Action(Mouse 1) Exec exec gimp) use this,I can start up gimp by click on the button. But how could i start gimp by double click on the buttons? It seems mouse 3 or mouse 4 does no effect. -- Happy for nothing Try binding a function to the mouse button you'd like to double click. Then in the function have it run the gimp on double click and optionally something else on single click. Ex: *MyButtons: (1x5, Frame 0, Icon 48x48/gimp.png, \ Action(Mouse 1) DoSomething) DestroyFunc DoSomething AddToFunc DoSomething + C Echo here is an optional single click if you want it for something + D Exec exec gimp -- 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: Geometry window position
Is there a way to specify the location of the geometry window that appears when moving or resizing windows? Thanks --s.r.d. -- 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: Translucency in Colorset for MenuStyle and firefox
I'm having a problem where my menus' submenus aren't being erased before a new transparency/translucency is computed. In creating a stripped down version of my config, I have noticed that the problem only occurs when menus overlap firefox. If the popup overlaps a firefox window and an xterm, only the portion overlapping firefox is messed up. This will sound a bit confusing, but this is what happens: If I have a given menu, and select an item from the menu which pops up a submenu, and then select an item above the current item that also opens a submenu (still from the same original menu), I get the new menu being drawn over top of the old menu and it doesn't completely erase the old submenu. I'm using gentoo, kernel 2.6.9-gentoo-r4 on a p4 3.2Ghz with 2GB RAM however, I have the same problem on my home system (AMD 3200 xp+, 1.5 GB RAM, kernel 2.6.9). fvwm version 2.5.12 with 'support for: ReadLine, XPM, PNG, Shape, XShm, SM, XRender, XFT, NLS' I have attached a stripped down version of my .fvwm2rc file. Using the stripped down config, I can recreate the error by opening firefox, then left-clicking on the root menu, next to a firefox window, select the Systems menu, and then select Apps. The Apps menu will pop up before the Systems menu has been erased. Any ideas why this happens? Is this a bug in the translucent style? Am I using the translucent style incorrectly? Any help is appreciated. --s.r.d. .fvwm2rc Description: Binary data
FVWM: FVWM as a Display Manager
Out of curiosity has anyone ever thought about using fvwm in place of a display manager? Have any developers thought about creating an fvwm config that would act as a display manager, or implementing a display manager that is fvwm driven? Basically I just want a display manager that will allow either user selection from a menu or a user name and password entry, but I dont' want to have to rely on gnome or kde under-pinings. I was thinking that I could probably just start up a stripped down window session with fvwm and remove all of the default key-bindings. (Or maybe start up a non-privelaged user account that doesn't have a shell entry and have it present the menu...) I could then decorate it with all the eye candy and functionality that gdm provides, but I'm not sure how to go about replacing the currently running fvwm session with an fvwm session running as a different user. So I guess in all of my rambling my question isn't really fvwm specific, but it does relate to fvwm. How do I create a new fvwm session from a currently running fvwm session with different user privelages? --s.r.d. -- 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: immobile windows
I tried to be as detailed as possible so bare with me... This is what happens: I'm using X for a while, but then I need to get up and walk away from the machine for whatever reason. So I call xlock (or maybe it's xlockmore...) to lock my screen, then I get up and walk away. If I'm away for more than say 15 minutes, the machine goes into power save. When I return, I move the mouse, the system comes back up (when I say power save, I just mean the monitors go blank [instead of displaying the xmatrix screensaver from xlock]) and I need to enter my password to use the machine. I type in my password, the screen saver goes away, and I can continue working. There is one problem however, I can't move any of the windows via clicking the titlebar and dragging, via a mouse binding I added for holding alt and clicking anywhere on the window, or by using the Fvwm Window-Ops menu that was a part of a .fvwm2rc that I copied into mine. When I move the mouse to the edge of the window, I cannot resize the window either. It seems as though the only way that I can resize or move the windows is by clicking in the icon in the upper left corner of the titlebar (i forget which one or number corresponds to the position) that calls a function nearly identical to Window-Ops called Window-Ops2 (the only difference being no Title section in the Window-Ops2) and using the Move selection from it. Interestingly enough, another solution is by running timetool, selecting a day at least one day past the current and applying the change so that the display resets(ie both monitors blink off momentarily and then come back on). Sometimes changing the hour is enough, but it has to be a future time. Changing it to a time in the past will not let me move windows regardless as to whether or not the change caused the displays to reset. Also if I have to do this several times in a day, I have to move it at least one day past the currently displayed day as opposed to the real day. The details: RedHat 7.3 Fvwm2 v 2.4.6 on an i386ish machine Dual Monitor display, (2 old and crappy diamond something cards) Running XFree86 (v. whatever came with redhat 7.3) Starting x with the command: startx --+xinerama Key bindings from .fvwm2rc: Mouse 1 TS N Move-or-Resize Mouse 1 FSTW A Move-or-Resize AddToFunc Move-or-Raise I Raise + M Move + D Lower AddToMenu Window-Ops2 Move Move + Resize Resize . . . Oh, and no, the num-lock, caps-lock, etc keys are not pressed. I forget the name of the utility I ran to see if any of the modifier keys were being pressed, but there were none 'stuck' ANY help would be appreciated, my apologies if there are inconsistencies in the details provided, it would be impossible to take the machine with the problems online or transfer any software from it to a computer that does have an internet connection (ie I can't post the .fvwm2rc file or give detailed output for commands run.) --s.r.d. -- 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: Dockable App question
I've noticed in a lot of screenshots that some people make use of a minature xterm as a sort of dockable applet. Where can I find it? On second thought, that doesn't sound very descriptive... here's a link to a screen shot that is using it in the upper left hand corner, bottom-most app. http://www.igs.net/~tril/fvwm/snake.jpg Thanks --s.r.d. -- 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: Losing keybindings
I have had this problem before... Didn't take too long to figure out that num lock was down, so I didn't feel too stupid, however it has happened to me again lately and the num lock was not pressed. I haven't been able to put my finger on exactly what causes it, and when I try to intentionally recreate the problem I can't seem to do it, but every once in a while I go back to my terminal and discover that I can't drag windows around just like the num lock was pressed. The problem has occurred once when I left my terminal for a period of time not greater than 5 minutes with a screen saver running, some applications being xhosted from other machines, and a few local running applications. It has occurred several times while I have screen locked and left the machine running over the weekend, again with several xhosted applications and just a handful of locally running programs. In order to fix the problem I actually have to restart X, not just the window manager. The system is running redhat 7.3 on an intel something or other and whatever version of fvwm2 that came with redhat. The .fvwm2rc is my own custom made file, not based on the one that came with redhat, but put together from scratch. Oh, and it's a dual monitor display system using the xinerama extension on 2 monitors of the same size and resolution. I can't think of any other pertinent information, but if anyone has any ideas as to what might be causing it I'd very much like to hear them. --s.r.d. On Thu, 15 Aug 2002, Rick Koole wrote: hmmm this make me feel awfully stupid thanks On Thu, 15 Aug 2002, Mikhael Goikhman wrote: On 15 Aug 2002 21:19:05 +0200, Rick Koole wrote: I'm using a standard winblows comaptible keyboard, having mapped my two windows keys using xmodmap with the following config keycode 115 = Hyper_L keycode 116 = Hyper_R clear Mod4 add Mod4 = 0xFFED 0xFFEE I'm using key combinations with the windows keys to do windowplacement, desktopswitching and related stuff which works fine when I've just started X. However after a random time these keybindings just stop working... I can't find any regularity in the behavior of the keybindings, whenever they stop, and I press e.g. windows + j , it prints a 'j' in my terminal instead of switching windows. Any clues on this one? fvwm (2.4.8) just doesn't seem to recognize those keybindings after a while. Probably your Num-Lock is pressed, see FAQ #0.1. Regards, Mikhael. -- 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: Documentation (was: Re: FVWM: How do I start modules automatically?)
What would you like to see in such a tutorial? --s.r.d. On Fri, 9 Aug 2002, Dominik Vogt wrote: On Thu, Aug 08, 2002 at 09:07:02PM -0500, Len Philpot wrote: On Thu, Aug 08, 2002 at 02:20:00AM +0200, Dominik Vogt wrote: Place the lines AddToFunc StartFunction + I FvwmAuto 500 in you $HOME/.fvwm2rc file. Although its very big, the man page is a good source of fvwm related information, but don't hesitate to ask questions on the mailing list - that's its main purpose. While I agree the fvwm man page is extensive and a good source of info, it's (unfortunately) hardly a tutorial. Of course, man pages aren't generally meant to be tutorials, but it would certainly be nice to have one somewhere. I saw one other post on the list of a small tutorial and have read that, but that's apparently about it. I get the feeling I won't understand much of anything until some magic moment after reading enough when it all comes together at once... *Sigh* Yes, the documentation is one of the biggest open issues with fvwm, but we don't have the people and/or the infrastructure to do it right. We'd need somebody who is able and willing to set up en environment in which the man page and other doc formats can be generated from a single source. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- 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: Startup
Is there really no one on the list who can help me? On Thu, 16 May 2002, Stephen Dennison wrote: When fvwm starts up, I can see the background being set, I see the applications start up for the pager, and then they are swallowed by the pager and somewhere along the way the banner pops up just before Fvwm is done loading. Is there some sort of support in fvwm to show a splash screen, wait for fvwm to finish starting up, and then display the desktop? (Would FvwmBanner do something like this for me without using too large of an image?) This would hide the background stuff and make the startup look better on my system. --s.r.d. -- 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: Cygwin
I recently compiled fvwm under cygwin. To my amazement it actually worked! Unfortunately it's not exactly... well you know... stable. I was just wondering if anyone else had tried to run fvwm2 under cygwin using the X server supplied by XFree86.org. Oh, and I'm running it on a windows 98 machine, although quite possibly it may soon become a windows 2000 machine. Anyone, I'm interested in hearing if anyone has tried using it under windows with cygwin or other software. Maybe you could provide hints, tips, etc? Thanks. --s.r.d. -- 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]
