Re: FVWM: Laptop backlight control applet
Carsten Kunze writes: >> Stuart Longland hat am 29. Dezember 2019 >> um 13:54 geschrieben: Under Linux I have key bindings set up that >> call this Python script installed in /usr/local/bin: >> >> https://gitlab.com/wavexx/acpilight/blob/06fcb7452e8b79107860425af4aecc1dac9e06b1/xbacklight >> >> The relevant files in /sys are owned by the 'video' group. >> >> Not sure what would be used on BSD or Unix though and you don't say >> what OS you're using. > > I'm using Linux. Unfortunately I'm more looking for a graphical app > (best would be something which can be added to stalonetray). The search "xbacklight gui" suggests there are multiple choices. Perhaps this one: https://github.com/theelous3/xbacklight-tooltip -- Dan Espen
Re: FVWM: howto conditionally add menu entries?
Stuart Longland writes:
> On 3/8/19 1:56 pm, hw wrote:
>> If I was to write some program to create the root menu, I would always
>> need to modify the program when new optional configurations are to be
>> added so it could recognize them. That is something I would prefer to
>> avoid.
>
> Well no, the program will need to store its state somewhere, and have
> that state updated so that next time it is called by FVWM, its output
> reflects the new state.
The script may or may not have to save state, it could just be looking
at data. Here is a fragment where a perl subroutine is given a
menu title and a command, it looks at the command and if the command
can be found (using "which") it goes on to add the menu entry:
# arg 1, the menu title
# arg 2-n, the command
sub Add {
($desc,$func,$accel)=@_;
($f1, $f2)=split(" ",$func);
if ( $f1 eq "Exec" ) {
$x=`which $f2 2>&1`;
$rc=$?;
if ( $rc != 0 ) {
# print "cant find , rc $rc, cmd o/p $x\n";
return;
}
}
...
--
Dan Espen
Re: FVWM: howto conditionally add menu entries?
hw writes:
> Dan Espen writes:
>
>> hw writes:
>>
>>> Hi,
>>>
>>> how can I conditionally add menu entries? For example:
>>>
>>>
>>> [...]
>>> Read fvwm-functions-starters-common.fvwm
>>> Read fvwm-functions-starters-games.fvwm quiet
>>> Read fvwm-functions-starters-local.fvwm quiet
>>> [...]
>>>
>>>
>>> DestroyMenu Main
>>> AddToMenu Main
>>> + "Main"Title
>>> + "Common" PopUp Common
>>> + "Games" PopUp Games
>>> + "Local" PopUp Local
>>>
>>>
>>> I want the "Common" and "Games" entries in the menu only when the files
>>> defining them (like fvwm-functions-starters-games.fvwm) can be read.
>>>
>>> I thought I could use something like
>>>
>>> DestroyMenu Main
>>> AddToMenu Main
>>> + Test (f fvwm-functions-starters-games.fvwm) AddToMenu Main "Games" PopUp
>>> Games
>>>
>>>
>>> and that doesn't work in that the menu entry doesn't show up regardless
>>> of the existance of the file. There doesn't seem to be a way to test
>>> whether something is defined or not; if there was, I could test if a
>>> menu has been defined and only then add it to another menu.
>>
>> Try PipeRead. Use shell, Perl, Python, your choice.
>
> How would that work? I'm trying to make a kinda dynamic configuration,
> meaning that there is supposed to be a basic configuration accompanied
> by optional configurations. An optional configuration needs to make an
> entry for its sub-menu into the root menu if the optional configuration
> is available.
>
> If I was to write some program to create the root menu, I would always
> need to modify the program when new optional configurations are to be
> added so it could recognize them. That is something I would prefer to
> avoid.
>
> Hm, having that said, I can make it so that the optional configurations
> add themselves to the root menu. All they need is a line like
>
> AddToMenu Main "Games" PopUp Games
>
> Unfortunately, that raises the question how I can make it so that the
> entries in the root menu appear in a desired order and with the title at
> the top rather than somewhere in between the entries ... Is there a way
> to sort menu entries once no more entries are being added?
>
> I'm probably not the first one to try this. It can't be this difficult,
> can it?
No, it's not difficult at all.
I have a number of scripts that work with PipeRead, here is a very short
one:
#!/usr/bin/perl
print "DestroyFunc LockTerm\n";
$_ = `uname -s`;
chomp;
if ( /Linux/ ) {
print "AddToFunc LockTerm I Exec exec gnome-screensaver-command -l\n";
exit 0;
}
print "AddToFunc LockTerm I Exec exec myscreensaver -lock\n";
This creates a "LockTerm" function which is different when running on Linux.
(I used the same configuration file on Solaris systems.)
Doing sorts, file existence tests, just about anything should be
obvious. Just only print commands when you want to generate Fvwm
commands.
If you look at fvwm-menu-desktop you'll see how far you can go with
this.
--
Dan Espen
Re: FVWM: howto conditionally add menu entries?
hw writes: > Hi, > > how can I conditionally add menu entries? For example: > > > [...] > Read fvwm-functions-starters-common.fvwm > Read fvwm-functions-starters-games.fvwm quiet > Read fvwm-functions-starters-local.fvwm quiet > [...] > > > DestroyMenu Main > AddToMenu Main > + "Main"Title > + "Common" PopUp Common > + "Games" PopUp Games > + "Local" PopUp Local > > > I want the "Common" and "Games" entries in the menu only when the files > defining them (like fvwm-functions-starters-games.fvwm) can be read. > > I thought I could use something like > > DestroyMenu Main > AddToMenu Main > + Test (f fvwm-functions-starters-games.fvwm) AddToMenu Main "Games" PopUp > Games > > > and that doesn't work in that the menu entry doesn't show up regardless > of the existance of the file. There doesn't seem to be a way to test > whether something is defined or not; if there was, I could test if a > menu has been defined and only then add it to another menu. Try PipeRead. Use shell, Perl, Python, your choice. -- Dan Espen
Re: FVWM: meaning of '+ I', '+ M', '+ D'?
hw writes: > Hi, > > what is the meaning of '+ I', '+ M', '+ D' when adding stuff to > functions or menues? That doesn't seem to be explained in the man page > ... > > Why does '+ I' work and '+I' doesn't? The description of plus from the man page: + Used to continue adding to the last specified decor, function or menu. See the discussion for AddToDecor, AddToFunc, and AddToMenu. So this lets you do: AddToFunc ExecWarp + I $1 + I Wait $0 + I Warp $0 which is the same as: AddToFunc ExecWarp I $1 AddToFunc ExecWarp I Wait $0 AddToFunc ExecWarp I Warp $0 The reason "+I" is invalid, is because the "+" is a command and must be space separated from it's arguments. The letters are explained in the description of AddToFunc: The letter before the action tells what kind of action triggers the command which follows it. 'I' stands for "Immediate", and is executed as soon as the function is invoked. 'M' stands for "Motion", i.e. if the user starts moving the mouse. 'C' stands for "Click", i.e., if the user presses and releases the mouse button. 'H' stands for "Hold", i.e. if the user presses a mouse button and holds it down for more than ClickTime milliseconds. 'D' stands for "Double-click". The action 'I' causes an action to be performed on the button-press, if the function is invoked with prior knowledge of which window to act on. These letters are only used in functions, menus have a different syntax. -- Dan Espen
Re: FVWM: Controlling initial size of a "gThumb" window
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
Re: FVWM: Controlling initial size of a "gThumb" window
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
Re: FVWM: Controlling initial size of a "gThumb" window
Dr Rainer Woitok writes: > Greetings, > > even though I'm using Xubuntu 16.04 I nevertheless use Gnome's "gthumb" > as image viewer. However, I cannot find a way to keep "gthumb" from op- > ening a fullscreen window when fired up. > > So I ran "man fvwm" and checked the stlye options, but "MaxWindowSize" > isn't really what I want, because it prevents me from later manually in- > creasing the window. Is there some way to just specify an INITIAL wind- > ow size or even window geometry? I'm on Fedora. I installed gthumb and tried to start it up without any input files. Core dump. So, I gave it an input png file. It started up in a window. I clicked the big square in the bogus extra window options bar and got a screen sized window. I was able to right click and select resize to make the window smaller. Then I looked in settings/browser and selected open image in full screen. Then I quit and restarted. Rather I attempted to restart, now even with an image on the command line gthumb crashes on start up. So, I removed the user configuration it created: rm -rf .config/gthumb Now it crashes on startup. Nope, another test, now it starts and it starts with the image in full screen mode. So, I can hit escape to get a regular size window. Now I click on settings/browser and turn off full screen. No joy, back to crashing on start up. So, I'm afraid I can't duplicate your issue but I can see gthumb is really buggy. Starting from a command line, I see various error messages, this is one recent one: home> gthumb me.jpg (gthumb:23283): GLib-ERROR **: 08:48:49.891: gmem.c:170: failed to allocate 140737488355328 bytes Trace/breakpoint trap (core dumped) home> gthumb -v gthumb 3.6.2, Copyright © 2001-2010 Free Software Foundation, Inc. Hopefully, this post shows how to clear an existing set of options or if you can get gthumb started, you can see where to turn off full screen. Damn thing just started again for me. I'm going to uninstall it. -- Dan Espen
Re: Do we still need color-limit/visual options in fvwm?
Thomas Adam <tho...@fvwm.org> writes: > Hi all, > > Just looking through a few things, and I thought I'd ask whether fvwm needs to > stlil support color limiting, and color depths for XServers with less than > TrueColor? > > These days, 24-bit seems to be the standard, and indeed, I've never yet come > across a server still using only 256 colours. Whilst I appreciate you can > still go and find such things, do we actually need fvwm to supprort it? It's not the server, it's the hardware in the workstation graphics card. Back when I was using Sun hardware it was required. I put the original code in that tried to force colors to familiar named colors with the idea that colors with common names would be already be in use. A while later the old code was ifdef'd with the current color cube logic. I think there is no risk in removing the common name logic but that won't reduce executable size. I don't think the color limiting stuff is large enough to make any difference. If you think otherwise, consider making it a build option. -- Dan Espen
Re: Some advices about the new static website
Thomas Funk <t.f...@web.de> writes: > On 04/08/2016 11:08 PM, Thomas Adam wrote: >> On Fri, Apr 08, 2016 at 09:44:48PM +0200, Thomas Funk wrote: >>> What about the perlib pages and the ... uhm ... 'unstable' documentation >>> pages (http://fvwm.org/doc/unstable/index.html)? Will they appear again >>> in the future? >> >> perllib maybe (althought woefully out of date, and it's on my TODO list to >> look at). > > I could help you if you like as I did much inside Fvwm-Nightshade with > perllib. > >> As for unstable man pages, no. There's no such thing any more, and >> hasn't been for a long time now. > > 'unstable' was only used as example. As I remember the same pages exists > on 'stable', too. But it would be a shame to lost those pages. Also Dan > did much work on the linking on the FVWM page. We don't have stable and unstable anymore so references to stable and unstable should be removed. -- Dan Espen
Re: FVWM website: WAS: [Re: FVWM code moved to Github]
Jaimos Skriletz <jaimosskril...@boisestate.edu> writes: > Also I am unsure if these various markdown files, FAQ.md, AUTHORS.md, > DEVELOPERS.md, etc should be located and maintained on the webpage or > in $FVWM.GIT source. I think either can work with git.io so it is > probably a matter of preference. But agreed, these markdown files > should all be collected and maintained in a single place. If I recall correctly, we created Changelog, and AUTHORS in the source tree because its a recommended part of a GNU source tree. (Similar to INSTALL, README, NEWS.) -- Dan Espen
Re: FVWM website: WAS: [Re: FVWM code moved to Github]
Thomas Adam <tho...@fvwm.org> writes: R> On 23 March 2016 at 22:21, Dan Espen <des...@verizon.net> wrote: > Excellent. Then set yourself up with a Github account, and let me > know your username, and I'll add you to the fvwmorg and you can do > something with the website repository. My account is named "danespen". > Note that I'm getting married this weekend and will then be away on > honey moon for two weeks. Enjoy and don't even think about Fvwm. I've no specific plans for retirement. I'm on my own and starting over. -- Dan Espen
Re: FVWM website: WAS: [Re: FVWM code moved to Github]
Jason L Tibbitts III <ti...@math.uh.edu> writes: >>>>>> "JS" == Jaimos Skriletz <jaimosskril...@boisestate.edu> writes: > > JS> who controls the domain name fvwm.org, > > A whois query shows that it's me. Not sure why, maybe I paid, but paid for you? From: Gandi <support-re...@gandi.net> Subject: [GANDI] fvwm.org domain name renewed To: des...@verizon.net Date: Fri, 26 Jul 2013 16:58:29 +0200 (2 years, 34 weeks, 4 days ago) Dear Customer, We are pleased to confirm that you have successfully renewed the following domain that is registered at Gandi: fvwm.org This domain has been renewed for 3 year(s), and the new the new expiration date is therefore 2017-12-29 05:00:00 As a reminder for your records, the handle that you used to renew this domain is XX. -- Dan Espen
Re: FVWM website: WAS: [Re: FVWM code moved to Github]
Thomas Adam <tho...@fvwm.org> writes: > On Wed, Mar 23, 2016 at 09:19:18PM -0400, Dan Espen wrote: >> Yep, I'm referring to the web pages. >> I have some CSS based pages at work using themes. >> The themes aren't really important to me, but since >> I doubt GIT is going to give us PHP I think we'll be better off without >> the PHP. > > Have a look at this: > > https://help.github.com/articles/about-github-pages-and-jekyll/ > > I think this would be a good way to go, and would reduce the need for us to > potentially write any HTML. > > I'm all for using Jekyll in this case! My first impression, it's Github only. I lean toward writing plain HTML/CSS with a little JavaScript for maximum portability and familiarity. Meanwhile, I committed fvwm-web changes yesterday, but those changes have not shown up at fvwm.org. Jason, what's up? -- Dan Espen
Re: FVWM website: WAS: [Re: FVWM code moved to Github]
Thomas Adam <tho...@fvwm.org> writes: > On 23 March 2016 at 22:21, Dan Espen <des...@verizon.net> wrote: >> I think we're embarking on a lot of work. > > Which aspect, specifically? Note that if you're referring just to the > website, then you might be right---I don't know enough about HTML/CSS > to make that call. However, it requires someone with enough > understanding to put in place something static which can be hosted on: > > https://github.com/fvwmorg/fvwmorg.github.io > > Note that this repository as-named, assumes hosting under github.io, > which as I understand it makes thing a lot easier. Certainly, > removing PHP at this point is definitely a good idea, as we're not > gaining anything from its use any more that CSS can't provide. I > consider this a good thing. Yep, I'm referring to the web pages. I have some CSS based pages at work using themes. The themes aren't really important to me, but since I doubt GIT is going to give us PHP I think we'll be better off without the PHP. >> As a start I've updated the download instructions to send users to GIT. > > OK. > >> I know you have the web stuff on GIT but if I make changes there they >> won't get to fvwm.org. > > That's OK -- because we can leave what's hosted on fvwm.org > as-is---and start to do something proper with fvwmorg.github.io -- > that's your play area. Go forth and have a blast. Note that I'm > envisaging something which is self-hosting. That is to say, something > we can redirect to from fvwm.org -- I see that as a positive thing > indeed. We own the domain name, I'm not clear on the details but I think once we move the pages we can just make Fvwm.org be the git pages. >> Jason, let us know if/when you start pulling the web pages from GIT. > > See previous paragraph, I do not think this is the right approach at all. I don't see the difference. Right now Jason pulls from CVS to build the pages at fvwm.org. He said he's willing to pull from Git instead. So, the fvwm-web can be in CVS or GIT, it doesn't matter, we just need Jason to decide where he wants to pull from. >> I'm pretty good with HTML/CSS. PHP gives us some nice stuff, but I >> guess we can live without it. > > Excellent. Then set yourself up with a Github account, and let me > know your username, and I'll add you to the fvwmorg and you can do > something with the website repository. Okay, will get to that sometime. > Note that I'm getting married this weekend and will then be away on > honey moon for two weeks. Well, CONGRATULATIONS. That's just great. I was married in 1964. I'm retiring as of March 31. -- Dan Espen
Re: FVWM website: WAS: [Re: FVWM code moved to Github]
Thomas Adam <tho...@fvwm.org> writes: > On Sun, Mar 20, 2016 at 08:16:13PM -0400, Dan Espen wrote: >> Moving the Fvwm-web source to Github won't help if we still need to >> publish using Jason's services. > > So I've taken a look at this, and have noted the following: > > * PHP is used to regenerate the theming components of the site; > * PHP is used to render in from the fvwm repo, the contents of files from: > > NEWS > FAQ > > * PHP is used to ensure the theme is applied consistently for the borders for > "window" (the default theme). > > What happens via github.io pages is that static content can be used for this. > > I'm starting to think that we have no desire or need for PHP at all for the > website. Before the use of static HTML generators, etc., it made a lot of > sense. Additionally, there's a lot one can do with CSS which mitigates the > need for PHP as we're currently using it for the website. > > As for the linking in NEWS/FAQ -- the NEWS file in particular is obsoleted, > given that git commit logs can be used to gather the same information. That > said, if we do retain NEWS for releases, we can just upload a separate set of > notes for that against each release in the releases area of Github [1]. It's > a part of the process. > > The FAQ therfore, is part of the website and it should be moved into that > repository. > > I've since renamed the fvwm-web repository [2] to match the expectations of > what github.io expects. > > I'd really (REALLY!) be interested in someone coming up with a proof of > concept on what a FVWM website might look like using a static HTML generator > that github.io accepts, just to prove my points above. I won't be doing that > work, however, but if someone does want to give this a go, do please let us > know! > > Kindly, > Thomas Adam > > [1] https://github.com/fvwmorg/fvwm/releases > [2] https://github.com/fvwmorg/fvwmorg.github.io I think we're embarking on a lot of work. As a start I've updated the download instructions to send users to GIT. I know you have the web stuff on GIT but if I make changes there they won't get to fvwm.org. Jason, let us know if/when you start pulling the web pages from GIT. I'm pretty good with HTML/CSS. PHP gives us some nice stuff, but I guess we can live without it. -- Dan Espen
Re: FVWM code moved to Github
Thomas Adam <tho...@fvwm.org> writes: > Hi all, > > I know we've had these discussions in the past, but I think now is the time we > actually do something about them. > > I appreciate I've swooped in here, and just done this, but the discussion[0] > happened once before, and given the recent circumstances with the borked CVS > repository, it seemed unfair to leave an impending release hanging. > > To that end, I have therefore created an organisation on Github[1] which at > the moment houses what I'm now calling the "official" FVWM repository [2]. > This has been converted from the existing FVWM CVS repository (branch-2_6). > > The 2.6.6 release now has a tarball uploaded and can be found here[3]. > > I've not changed fvwm-web, but this will likely be converted as well and put > on [1] in due course. > > Note that as an organisation on Github, we have a lot more freedom, in that > more than one person who is a member of the fvwmorg organisation will be able > to do things like handle releases, etc., and that should something happen, > it's not anything in our control that we'd need to worry about. > > This has absolutely *no* reflection on Jason at all. He's spent the last > twenty odd years managing this, and to have all of this go through one person > is not scalable, especially when something goes wrong. So we should be really > thankful indeed for Jason's efforts, and to note that I hope he continues to > manage the hosting/mailing lists, but the code... that's now better handled by > us. Moving away from CVS is also long overdue. > > So what happens next? Well, I need existing fvwm-workers who had commit-bit > access to let me know so I can add you to the organisation. > > Additionally, I have the following outstanding items: > > * Convert fvwm-web, and add to fvwmorg on GH; > * Rip out the existing CVS docs and put something else in place; > * Update the release procedure > * Put our logo on the front of the landing page for fvwmorg on GH > > Any questions, do please let me know. I'm not clear on what we can do with Github. You mention leaving the web pages and mailing lists on fvwm.org. For that we need Jason. Is it possible to move the whole project to github or some other hosting site? Moving the Fvwm-web source to Github won't help if we still need to publish using Jason's services. -- Dan Espen
Re: Release 2.6.6?
Thomas Adam <tho...@fvwm.org> writes: > Hi, > > I'm getting quite a few emails off-list, asking me when 2.6.6 is going to be > released. I know it's been a while, so I'm thinking of doing this this > evening at some point. > > Any objections? The CVS branch seesm stable enough to me. No objections at all. It's long overdue. Every time I look I get distracted by the 2.7 branch, which should be eliminated. But I don't know how to turn 2.6 into the new head. So, just doing 2.6.6 would be fine. -- Dan Espen
Re: FVWM: Is it possible to resize automatically icons in AddToMenu?
Thomas Funk <t.f...@web.de> writes: > Oleksandr Gavenko wrote: >> On 2015-12-12, Dan Espen wrote: > [snip] >>> You should try fvwm-menu-desktop if you haven't done so already. >>> Use the size= parameter to control the icon sizes. >> >> $ fvwm-menu-desktop | grep size || echo fail >> fail >> >> $ fvwm-menu-desktop --version >> 2.6.5 >> >> Too old or Debian maintainer broke script? > [snip] > > Dan refers in his statement to the new fvwm-menu-desktop located in the > CVS version of FVWM. > > If you want to use it, you need from CVS: > - fvwm-menu-desktop (new Python based xdg menu generator) > => copy it to /usr/bin/ > - fvwm-menu-desktop-config.fpl (configuration GUI) > => copy it to /usr/share/fvwm/ > - fvwm-menu-desktop.1 (new man page) > => copy it to /usr/share/man/man1/ Not sure a manual install is a good idea. To download the latest version from CVS: cvs -d :pserver:anonym...@cvs.fvwm.org:/home/cvs/fvwm checkout -r branch-2_6 fvwm To build it: utils/configure_dev.sh /configure make make install (as root) You'll probably find you need a few -devel packages. > Or you could download it from here (if you won't follow the CVS > instructions from the FVWM web page): > https://github.com/Fvwm-Nightshade/Fvwm-Nightshade/blob/release-0.6/bin/fvwm-menu-desktop2 > https://github.com/Fvwm-Nightshade/Fvwm-Nightshade/blob/release-0.6/fvwm/fvwm-menu-desktop2-config.fpl > https://github.com/Fvwm-Nightshade/Fvwm-Nightshade/blob/release-0.6/man/fvwm-menu-desktop2.1.gz Hmm, heard of it but know nothing about the Nightshade project. I see on their page: Works with FVWM 2.6.5 without loosing new Xdg menu support from FVWM CVS version. Not sure that's a good thing. I guess it's time I did a new stable release. I retire this spring, maybe I'll find time then. > Add this to your config: > > # Dynamic menu realized with DynamicPopupAction > AddToMenu MenuRoot DynamicPopupAction FuncMenuRoot > > DestroyFunc FuncMenuRoot > AddToFunc FuncMenuRoot > + I DestroyMenu MenuRoot > + I AddToMenu MenuRoot DynamicPopupAction MenuRoot > + I AddToMenu MenuRoot "$[gt.Root Menu]" Title > + I Popup FvwmMenu > + I AddToMenu MenuRoot "" Nop > > # Remark: FuncMenuRoot exchanges your current root menu. Add your other > # entries after the Nop line. > > #--- > # Dynamic FvwmMenu sub menu for XDG menus > # realized with DynamicPopupAction > #--- > AddToMenu FvwmMenu DynamicPopupAction FuncXdgMenusInRoot > > DestroyFunc FuncXdgMenusInRoot > AddToFunc FuncXdgMenusInRoot > + I AddToMenu FvwmMenu DynamicPopupAction FuncXdgMenusInRoot > + I Test (f $[FVWM_USERDIR]/.menu) Read $[FVWM_USERDIR]/.menu > + I PipeRead 'fvwm-menu-desktop --insert-in-menu MenuRoot > > $[FVWM_USERDIR]/.menu && echo "Read $[FVWM_USERDIR]/.menu"' > > # Remark: if you're using the scripts from Fvwm-Nightshade don't forget > # the '2' behind fvwm-menu-desktop ;-) > > For more information see the new fvwm-menu-desktop man page. > > [snip] >> How is script supposed to manage icon size? It resize them and store under >> ~/.cache/fvwm dir? > [snip] > > You can set the wanted icon size via configuration GUI or command line. > Default location for resized icons is ~/.fvwm/icons/ > > -- Thomas -- Thanks. -- Dan Espen
Re: FVWM: Is it possible to resize automatically icons in AddToMenu?
Oleksandr Gavenko <gaven...@gmail.com> writes: > Look to syntax %...% in: > > DestroyMenu MenuMyDev > AddToMenu MenuMyDev "My Dev Menu" Title > + %iceweasel.png% Exec exec firefox -no-remote -P devel > > ImagePath control colon search path for icons and I have broad definition to > gather different sources (as many as possible): > > m4_define(`m4_IMGPATH', `$[FVWM_USERDIR]/images')m4_dnl > m4_define(`m4_ICONPATH', `$[FVWM_USERDIR]/icons')m4_dnl > > ImagePath m4_ICONPATH:m4_IMGPATH:+ > > ImagePath +:/usr/share/icons/gnome/16x16/places > ImagePath +:/usr/share/icons/gnome/32x32/apps > ImagePath +:/usr/share/icons/gnome-colors-common/32x32/apps > ImagePath +:/usr/share/icons/locolor/32x32/apps > # ImagePath +:/usr/share/icons/hicolor/16x16/apps > ImagePath +:/usr/share/icons/hicolor/22x22/apps > ImagePath +:/usr/share/icons/hicolor/24x24/apps > ImagePath +:/usr/share/icons/hicolor/32x32/apps > ImagePath +:/usr/share/icons/hicolor/48x48/apps > # ImagePath +:/usr/share/icons/hicolor/64x64/apps > # This paths contain large icons for some apps, they make menus look ugly... > # ImagePath +:/usr/share/app-install/icons/ > # ImagePath +:/usr/share/pixmaps I don't see the logic of adding all the different icon sizes to your image path. They all have the same names, so only the first size you mention is going to be found. > Some paths commented because they provide too big images. Fvwm uses exact > size of image when it displays icon. Some of them occupy half of screen! > > Are there any syntax: > > (1) to set maximum allowed icon size for displaying (and ignore large image)? > (2) to specify how resize image (scale down any that bigger then ...)? No. You wouldn't want your icon resized each time it's displayed. Better to pick the size you want at startup time like fvwm-menu-desktop does. > I can't control which icon is supplied by package in Debian repository. That > is true for: > > /usr/share/app-install/icons/ > /usr/share/pixmaps/ > > Most package doesn't respect /usr/share/icons/hicolor/24x24/apps like > directories and place icons in above paths. > > Auto-generated /etc/X11/fvwm/menudefs.hook uses full path to icon so I can't > select desired size by ImagePath. > > Some 3rd-party packages I install in /opt hierarchy and usually they also have > single BIG icon. > > I like to see (2) option e.g. something like: > > + %iceweasel.png%32% Exec exec firefox -no-remote -P devel > > but (1) option also take a lot of images from /usr/share/pixmaps like > directories. > > Another option is to preprocess /etc/X11/fvwm/menudefs.hook and place resized > images into predefined path. > > Or carefully craft processing of /etc/xdg/menus/*.menu. I use xdg.Menu and > xdg.DesktopEntry Python classes to build menus myself. > > If Fvwm hold menu images into memory (without loading on demand) - present of > (2) option looks natural for me. You've lost me. menudefs.hook looks to me like some kind of menu generator. You should try fvwm-menu-desktop if you haven't done so already. Use the size= parameter to control the icon sizes. -- Dan Espen
Re: FVWM: Forcing window decorations
Tethys <tet...@gmail.com> writes: > On Fri, Oct 30, 2015 at 4:43 PM, Jaimos Skriletz > <jaimosskril...@boisestate.edu> wrote: > >> There is no bug here from my perspective. FVWM is correctly honoring the >> hint/state set by the GTK3 apps that use this feature. It would be a bug if >> FVWM did not honor this. Now there is a feature request here, to allow FVWM >> to be configured to ignore this hint/state on particular windows. But this >> would be a feature of FVWM to ignore the hint. > > We're getting into somewhat meaningless semantics here. But for me > it's a clear bug. FVWM's job is to manage windows. If it doesn't > manage windows because a misbehaving application asks it not to, > that's not sensible behaviour. My desire to have my desktop behave the > way I want trumps the application developers' desire to screw me over. Did my suggestion from yesterday get missed? You should try: Style * GNOMEIgnoreHints If that doesn't do it, I'll build a recent version of one of these from source and try to find out what's going on. -- Dan Espen
Re: FVWM: Forcing window decorations
Tethys <tet...@gmail.com> writes: > How can I force decorations onto windows? Having upgraded to Fedora > 22, I now find that many of my windows now appear to be doing client > side decorations, presumably in anticipation of Wayland. But it's > horrendous. I want my own window decorations back. How can I achieve > this? > > A good example of this behaviour is evince. I've tried explicitly > telling it I want a title bar, handles, etc: > >Style "Evince" Title, Handles, BorderWidth 5, HandleWidth 5 > > but that seems to be ignored. Any ideas? See attached screenshot. Try: Style * EWMHIgnoreWindowType Then contact the Evince developers and tell them NO, NO, NO! Let us know if that works. My copy of Evince doesn't display that problem, so my suggestion is purely a guess. -- Dan Espen
Re: FVWM: Forcing window decorations
Tethys <tet...@gmail.com> writes: > On Thu, Oct 29, 2015 at 8:14 PM, Dan Espen <des...@verizon.net> wrote: > >> Style * EWMHIgnoreWindowType > > Nope, that didn't work. I'll buzz the evince developers, but I'm > pretty much certain they'll ignore me. I don't exist in their brave > new Gnome3 world. > > I wish I knew enough about this to work out what was going on. I'd > guessed that evince was setting some kind of hint to tell the window > manager to not decorate it. But EWMHIgnoreWindowType should be enough > to override that, no? There's nothing in my config file to set > NoTitle, yet the evince window has that property set. > > FWIW, eog and totem are examples of other applications that suffer > from the same problem. My eog is also okay. Perhaps: GNOMEIgnoreHints -- Dan Espen
Re: FVWM: fvwm showing kill icon when starting and restarting
lee <l...@yagibdah.de> writes: > Hi, > > what could be the reason for fvwm showing its kill icon on startup and > when restarting? Do you mean kill cursor? > It seems to do that since after I made some change to the configuration, > and I don't remember what that change was. When it first happened, I > thought "ok, it's been restarted like so often and might be confused and > this will go away on a fresh start" --- but it didn't. > > The configuration is here: https://github.com/lee-/fvwm Somewhere in there you're issuing a Delete or Destroy not in a window context. -- Dan Espen
Re: FVWM: Is there a way to ignore other windows when placing one?
elliot s <elliot...@gmail.com> writes: > If fvwm can (be made to) optionally ignore lower layers during > auto-placement, that would work. Long ago, Fvwm got so many options that I'm unable to keep track. MinOverlapPlacementPenalties has a series of arguments including "below" that may help. -- Dan Espen
Re: SOLVED: Re: FVWM: fvwm showing kill icon when starting and restarting
lee <l...@yagibdah.de> writes: > Dan Espen <des...@verizon.net> writes: > >> lee <l...@yagibdah.de> writes: >> >>> Hi, >>> >>> what could be the reason for fvwm showing its kill icon on startup and >>> when restarting? >> >> Do you mean kill cursor? > > I guess so --- it's some icon which is probably supposed to look like a > skull with bones under it. I vaguely remember having seen that > somewhere many years ago, and this icon reminds me of it. > >>> It seems to do that since after I made some change to the configuration, >>> and I don't remember what that change was. When it first happened, I >>> thought "ok, it's been restarted like so often and might be confused and >>> this will go away on a fresh start" --- but it didn't. >>> >>> The configuration is here: https://github.com/lee-/fvwm >> >> Somewhere in there you're issuing a Delete or Destroy not in a window >> context. > > "not in a window context"? I'm only destroying functions ... Oh, I > found it! I used "Destroy" where I should have put "DestroyFunc". Glad to hear. I think you have "not in a window context" figured out. A title bar button has a window context, a destroy on a window button "knows" which window to destroy. A root window key binding for destroy doesn't know which window to destroy (there is no window context), so fvwm changes the mouse pointer to the skull you saw waiting for a click on a window to know which window to destroy. -- Dan Espen
Re: FVWM: Is there a way to ignore other windows when placing one?
lee <l...@yagibdah.de> writes: > Hi, > > the subject pretty much says it: > > Can I somehow make it so that fvwm ignores particular windows when > figuring out where to place a new one? Not that I know of. What are you trying to do? -- Dan Espen
Re: FVWM: fvwm through tightvnc: windows disappear or are hidden
KARR, DAVID dk0...@att.com writes: I'm new to fvwm, although I used X11 a lot in the previous millenium. I'm connecting from my Win7 laptop to an Ubuntu box with tightvnc, running tightvncserver on the ubuntu box and TightVNCViewer on the Win7 laptop. I get to the ubuntu box through an intermediate jumpserver, and I have a local port forward so the Win7 laptop can use the vnc port. In my ~/.vnc/xstartup file, the last line runs exec /usr/bin/fvwm. When I run the client and connect to the port, I can get to the fvwm context menu and create an xterm, and from there create other windows. The strange thing is that after I've been working with this for a few minutes, and then perhaps switch the focus to other windows on my Win7 box and then later return to the vnc client window, I find that all I see is a grey fvwm background. I can create another xterm window, and if I do ps -elf | grep xterm, I see the original xterm window, not to mention other windows that I've created. Also, if I select Restart fvwm from the context menu, I briefly see all the other windows that I've created, and then they disappear. I've gone through this sequence a few times now, and it's repeatable. Why might those windows be disappearing? Is this a fvwm problem, or a TightVNCViewer problem? I'm replying to your first post, but I've read the other 2. Because you saw windows in the pager, I'm guessing you moved them to another page or desk somehow. Could be you minimized them and had no icons available too. When you go through the auto configuration step, Fvwm creates a $HOME/.fvwm/.fvwm2rc file. Read it to see how to create key bindings and to see if you have bindings to toggle full screen. If you don't already have one, they are easy to create. You can access the built in menu with F1 (or Shift F1) if unshifted F1 got assigned. As you might be catching on, Fvwm is for people that like total control of their system. Good luck. -- Dan Espen
Re: FVWM: Schedule Periodic ceases working after some days
michael.gros...@gmx.de writes: Hi! As I reported some years earlier, the FVWM pager crashes sometimes (say, it disappears sporadically when I switch desktops). To fix this, my FVWM config has this code since Debian Wheezy: AddToFunc StartFunction + I Schedule Periodic 2000 crashGuardPager DestroyFunc crashGuardPager AddToFunc crashGuardPager + I All (minipager) Nop + I TestRc (NoMatch) crashHandlerPager DestroyFunc crashHandlerPager AddToFunc crashHandlerPager + I SetEnv SAVED_DESKTOP_NUMBER_MINI + I paintMinipager Every time the pager disappears, this code automatically creates a new one within 2 seconds (by letting the function 'paintMinipager' doing this job). So far, so good. Now, my Xen based virtual Debian Wheezy VNC machine with FVWM 2.5.30 has an uptime of 13 days and 7 hours, and once again, the pager disappeared. I waited, but it didn't reappear. The current version of Fvwm in CVS is 2.66. I don't remember the Pager issue, but I guess it could be fixed. Did you submit a stack dump? I can set up a Schedule test, but it sounds like it's going to take a couple of weeks to recreate the problem. I don't see anything in the current code that would cause a problem. I suggest you start with running something current. -- Dan Espen
Re: FVWM: Schedule Periodic ceases working after some days
michael.gros...@gmx.de writes: The last time I tried to replace the Debian packaged FVWM version by a downloaded one was in March 2013, I don't know what a Debian menu looks like, but current Fvwm has fvwm-menu-desktop which is a menu built from the XDG menu files on your system. Very likely the menu fvwm-menu-desktop generates is identical to your Debian menu. -- Dan Espen
Re: FVWM: fvwm startup procedure
Ethan Raynor ethanrayno...@gmail.com writes: On Thu, Jun 11, 2015 at 12:20 AM, Thomas Adam tho...@fvwm.org wrote: On 10 June 2015 at 23:56, Ethan Raynor ethanrayno...@gmail.com wrote: For example, there must be a file somewhere which has some key bindings for default things, or some function definitions, etc., for alt-tab. Is that true? I was wondering where this is documented, if at all. http://fvwmforums.org/wiki/Tips/FVWMStartupProcedure/ Wowza! This document is amazing! Is there some reason why most of this isn't referenced in the man page, may I ask? I agree, really nice. Except for where Thomas talks about function setRCDefaults, I think you'll find it all in the man page. The tutorial style is good for explaining how all the parts work together. The man page is meant to be a complete reference. This means you have to find all the pieces. -- Dan Espen
Re: System clock in FVWM: A new discovery!
Michael Großer michael.gros...@gmx.de writes: Hi! This is not a question but a report about a new discovery. Back in 2010, when I discovered FVWM as a useful window manager, I needed a digital clock, which simply shows date, time and weekday. I searched and filtered quite long and found xclock. I've been using dclock since forever: http://fvwm.org/screenshots/desktops/Dan-desk-1280x1024/screenshot.gif -- Dan Espen
Re: FVWM: Recent problem with control and shift modification characters
don fisher h...@comcast.net writes: I have been using FVWM since it was introduced, with great pleasure. My last system was Fedora 18 running fvwm2 2.6.5. I recently moved to openSuse 3.2 running fvwm2 2.6.6. I have encountered a problem that I cannot resolve. All of the modifier keys, esc, ctrl and shift do not appear to provide the control options they used to. I ran xev and the keys appear to be present, at least in the root window where xev runs. Can you suggest where these keys are being trapped? I assume it is in openSuse, but am not aware of a way to diagnose the problem. Is there any thing that I can enable to show if these keystrokes are being delivered to fvwm? Since Suse is KDE based, I need to have a strong argument before posting to their list, it indeed it is something they have done. I did move the 2.6.5 version to openSuse and still experience the same problem. It may be me being stupid, but I would appreciate any help. FAQ question 0.1? http://www.fvwm.org/documentation/faq/#0.1 (Check your numlock key.) -- Dan Espen
Re: FVWM: Sloppy Focus option
Walter Alejandro Iglesias e...@roquesor.com writes: Hello Dan, First of all have a good year. See, Openbox has a configuration option that allows sloppy focus to ignore the pointer when it's still. Then when you unmiximize a window it doesn't lose the focus if the pointer passively cross its boundaries. I couldn't get this in FVWM with any combination of FocusStyle (remember I'm talking about Sloppy Focus). I could barely workaround the issue by adding WarpToWindow to my own maximize function, but it doesn't solve the problem for ewmh fullscreen (i.e. firefox, mplayer, etc.). Any idea of what can I do? Time ago you pointed me where to modify fvwm C code and I could customize some default option myself. That's the kind of help I most value - though I understand that what I'm asking you this time can be too complex. Hi, Question should go to f...@fvwm.org. I've copied them. Not sure of the answer myself. -- Dan Espen
Re: FVWM: Mouse 1 R A Menu not working
Hernan G Solari hgsol...@gmail.com writes: Thanks Charlie and Jaimos Using D instead of R as context in Mouse 1 R A .. produces the same behavior. Apparently it is the context Root what it is not being recognized If I try to set a key as Key F4 R A . it ignores the key, using other contexts it works. But ... when I run xwininfo -children and I point to the Root window I get Root window id: 0x195 (the root window) (has no name) Parent window id: 0x0 (none) Meaning that it is the root window. Puzzling (The X-server is NOUVEAU the free server for nvidia cards) in the vesa server I had similar problems with Nouveau. Installing the Nvidia driver cured the problem. -- Dan Espen
Re: CVS dane: new file ChangeLog-pre-2.6.6
Thomas Adam tho...@fvwm.org writes: On 15 Sep 2014 18:30, c...@math.uh.edu wrote: CVSROOT: /home/cvs/fvwm Module name: fvwm Changes by: dane 14/09/15 12:30:08 Modified files: . : Tag: branch-2_6 ChangeLog Added files: . : Tag: branch-2_6 ChangeLog-pre-2.6.6 Log message: new file ChangeLog-pre-2.6.6 Ah. I was just about to do this and now you've saved me the bother. Thanks. :-) No problem. Not sure I want to work in the mvwm tree. Not fond of the name, and don't want to see FvwmCPP go away. BTW, I keep multiple versions of Fvwm installed and can pick which one I want to use. Simply a matter of a startup script that puts the right version of Fvwm in my $PATH. -- Dan Espen
Re: FVWM: Smart maximize
Piotr Isajew p...@ex.com.pl writes: Hi, I wonder, if there is a command to do smart maximize in fvwm? The command would move and resize current window to use the largest free area of desktop, but not covering any other windows. Is there something like this? Try this one: Key F2 A 4 Maximize grow grow -- Dan Espen
Re: FVWM: Smart maximize
Piotr Isajew p...@ex.com.pl writes: On Sat, Nov 24, 2012 at 07:53:16AM -0500, Dan Espen wrote: Key F2 A 4 Maximize grow grow Thanks, Dan. It's almost what I want. It expands the window using all the available space based on it's current location. What I'm looking for is a way to do the same, but in the largest available area of the screen. So for complete solution I need also a way to move that window to the largest free area of the screen before that maximize. But it's a move forward anyway, so thanks once again :) I guess you are thinking of the largest free rectangular area. I'm not aware of any such feature. -- Dan Espen
Re: FVWM: Smart maximize
Piotr Isajew p...@ex.com.pl writes: On Sat, Nov 24, 2012 at 08:37:03AM -0500, Dan Espen wrote: I guess you are thinking of the largest free rectangular area. yes, that's right I'm not aware of any such feature. I'll try to look for a solution myself. If I find something I'll post it to the list. If you want to go that far, I recommend using FvwmPerl and the module interface. You can ask Fvwm for a list of windows with Send_Windowlist. -- Dan Espen
Re: FVWM: SendKey Multicast ...
Bastian bastian-fvwm-org-20121...@t6l.de writes: Hi List, I wonder if it is somehow possible to send key events (typed in a head-window) to a set of other client-windows... This could help in doing small sized cluster/VM administration ... If you are trying to generate a keystroke for an xterm, the xterm won't accept a synthetic keystroke unless you've selected allow sendevents. (Its a security hole to allow it.) Do some Google searches on xwindows synthetic. The first hit I got discussed the issues in the context of a security exploit. It also mentioned some programs. Fvwm doesn't have a command to generate keystrokes. (Note: this reply was first posted in 2002.) -- Dan Espen
Re: FVWM: set style by state
Bastian bastian-fvwm-org-20121...@t6l.de writes: Hi list, someone may has an idea of how to make a State of a window visible. e.g. if a window has State 10 true, give it a big red border. Behind this, I try to do tag arbitrary windows (even from different pages) with State 10 to true and then calling on another Page All (State 10) MoveToPage. This works, but I do not see it, when windows are tagged. State is for conditional expressions. We need more information about what you are trying to do. Perhaps when you set the state, you should also set the style. -- Dan Espen
Re: FVWM: Speed on Interactive Move/Resize
Walter Alejandro Iglesias e...@roquesor.com writes: Hello, On interactive Move/Resize the default step is 5 pixels, 100p holding Shift and 1p holding Ctrl. Is there a way of customize that? Currently no. The values 1,5,100 are defined in: libs/default.h #define DEFAULT_KDB_SHORTCUT_MOVE_DISTANCE 5 /* pixels */ #define KDB_SHORTCUT_MOVE_DISTANCE_SMALL 1 /* pixels */ #define KDB_SHORTCUT_MOVE_DISTANCE_BIG 100 /* pixels */ And the logic is in: libs/Target.c -- Dan Espen
Re: FVWM: Speed on Interactive Move/Resize
Walter Alejandro Iglesias e...@roquesor.com writes: On Sun, Oct 28, 2012 at 02:24:42PM -0400, Dan Espen wrote: Walter Alejandro Iglesias e...@roquesor.com writes: Hello, On interactive Move/Resize the default step is 5 pixels, 100p holding Shift and 1p holding Ctrl. Is there a way of customize that? Currently no. The values 1,5,100 are defined in: libs/default.h #define DEFAULT_KDB_SHORTCUT_MOVE_DISTANCE 5 /* pixels */ #define KDB_SHORTCUT_MOVE_DISTANCE_SMALL 1 /* pixels */ #define KDB_SHORTCUT_MOVE_DISTANCE_BIG 100 /* pixels */ And the logic is in: libs/Target.c -- Dan Espen Hi Dan, Good to know what you point above. Thanks. I'd like to start learning about Xlib programing. I found this: http://www.tronche.com/gui/x/xlib-tutorial/ Could you point me (advice) to more related documentation? Where/how is it convenient to start? Visit the Developer section at the Fvwm web site. -- Dan Espen
Re: Snapshots
Thomas Adam tho...@fvwm.org writes: On 14 August 2012 15:23, Jason L Tibbitts III ti...@math.uh.edu wrote: OK, snapshots are back. At least they appear to be working OK, though ChangeLog and NEWS don't seem to have been updated in quite some time. Please ensure you're creating snapshots off branch-2_6. Yep, that must be 2.7 since the NEWS isn't current. Maybe we should take steps to remove 2.7? -- Dan Espen
Re: FVWM: fvwm-menu-desktop improvement: add keybindings to items
Stuart Longland redhat...@gentoo.org writes: Hi all, I've been a long time user of Linux, and since about 1996, I've moved between many window managers and desktop environments. I started out with FVWM, on Red Hat 4.0, and since then have moved between environments such as FVWM95 (mainly on Slackware), MWM, OLVWM, WindowMaker, KDE, Gnome (1 2), XFCE (3 4), LXDE, CTWM, and numerous others. I still quite often find myself oscillating between KDE and FVWM; often the former on more high-end systems, and the latter where I want something minimal. Recently I've got fed up of KDE's antics, and have started setting up FVWM2 proper. I wanted a convenient way of updating the menus from the KDE menus. Luckily, there's fvwm-menu-desktop. However, I struck a couple of snags. One, is that the documentation seems out of date. It tells us to use the --desktop option, which is now obsolete. Easily fixed once I realised what was wrong, but still worth noting. Second, it initially couldn't find the root menu. It was looking for /etc/xdg/menus/applications.menu, but couldn't find it. I did notice a kde-4-applications.menu however, so I symlinked it, and that worked. Third thing I noticed, is that there were no keybindings (-prefixed characters) generated, and if a menu happened to contain a symbol, that symbol was falsely interpreted as a key-binding. So I concocted the attached patch. This is a patch against the 2.6.3 release of FVWM's fvwm-menu-desktop. It first prefixes characters with a second so they don't get gobbled up. Next, it looks for the first letter or digit that isn't already allocated to another menu item, and prefixes that with an . The end result is a menu that looks like this: DestroyMenu FvwmMenu-Utilities AddToMenu FvwmMenu-Utilities Utilities Title +Akonaditray Exec akonaditray +Ark Exec ark -caption Ark +Disk Utility Exec palimpsest +Filelight Exec filelight +HP Device Manager Exec hp-toolbox +KAlarm Exec kalarm -caption KAlarm +KCalc Exec kcalc -caption KCalc +KCharSelect Exec kcharselect -caption KCharSelect +KDE Groupware Wizard Exec groupwarewizard +KGpg Exec kgpg +KJots Exec kjots -caption KJots +KNotes Exec knotes +KTeaTime Exec kteatime A better solution might be to see if there is some sort of keybinding mnemonic field in the .menu file; I didn't look into this, but this works well enough for my needs, and so I submit it here in the hope it may be helpful to someone else. Recently I started working on a new version of fvwm-menu-desktop. Using the new version I'm able to edit menu descriptions using Alacarte to include where desired and have shortcuts appear in the menus. Plus it gets the mini-icons right. I'll redo the documentation when I'm ready to commit the changes. If you like, I'll send you a copy. -- Dan Espen
Re: FVWM: GSoc backup mentor
Thomas Adam tho...@fvwm.org writes: On 28 February 2012 00:26, Dan Espen des...@verizon.net wrote: Am I the only one that can't figure out those Captchas? Hmm -- I've never had a problem with them in the past, although I didn't need to register since I already had a google account. I had one, but it has another purpose. Use this: dan1espen -- Dan Espen
Re: FVWM: Unhide a hidden taskbar
Thomas Adam tho...@fvwm.org writes: On Wed, Jan 04, 2012 at 03:56:00AM -0800, Leo Simon wrote: Tried to post this on the forum but it wouldn't let me log on. Right -- and you forget/entered incorrectly which piece of information? I accidently Iconified my task bar and don't see any way to get it back. Could you please advise if there is one? There is no such thing as my task bar -- either you're using FvwmButtons or FvwmTaskBar, in which case if you really mean iconified, then see: Next (SomeName) Iconify Off Amongst many other ways of doing the same thing. More specific answers will come with more specific information from you, if the above doesn't help you. Yep. When I lose windows I use the built in Alt-Tab to find the window. Pretty much the only time I use Alt-Tab. -- Dan Espen
Re: FVWM: disallowing the transfer of focus while a key is pressed
f...@stefan-klinger.de writes: Hi Dan, thank's for the suggestions, but unfortunately they both don't do what I'm looking for: On Fri, Dec 30, 2011 at 10:45:13PM -0500, Dan Espen wrote: Does this work the way you want: Key F7 A M Move This basically starts moving the window with the mouse, which is what I want to avoid in this situation. Key F7 A M Move 10p 10p This leaves the mouse cursor where it is, which means that the window to be moved looses the focus as soon as it is not under the cursor any more (focus follows mouse, not sloppy). Even with sloppy focus, a lower non-root window under the mouse cursor gets the focus. In fact, to disable switchingg focus while a modifier is held down would allow me to use SloppyFocus instead. Okay still trying to understand all the issues. This isn't animated move but I think it will work with animated move too: DestroyFunc My_AM AddToFunc My_AM + I Pick SetEnv B $[w.id] + I WindowId $[B] move $* Warp + I WindowId $[B] Raise key 1 a C My_AM 0 0 warp key 2 a C My_AM 50-50w 0 warp key 3 a C My_AM -0 0 warp Worked for the cases I tried. I also tried it with layer changing my that didn't seem to help. -- Dan Espen
Re: FVWM: disallowing the transfer of focus while a key is pressed
f...@stefan-klinger.de writes: On Sat, Dec 31, 2011 at 01:14:38AM +, Thomas Adam wrote: So set a reasonable delay for you binding: Schedule 700 Close Sorry, that won't help in general. Maybe you want to read my initial mail? Does this work the way you want: Key F7 A M Move But this doesn't: Key F7 A M Move 10p 10p -- Dan Espen
Re: FVWM: xterm does not receive focus
Alexander Burger a...@software-lab.de writes: Thanks Thomas and Hans, now I tried some variations from Hans's config, without avail. Thomas Dickey (Xterm author) will show up here sooner or later (he always has in the past). If you are impatient you might try to track him down.
Re: FVWM: Highly Ignorant - But Seeking Help
John Meissen [EMAIL PROTECTED] writes: Thomas Adam said: 2008/8/6 Robert Heller [EMAIL PROTECTED]: I use the FvwmIconBox, so I have these lines in my .fvwmrc file: That's a pity. Why the sarcasm? Making that sort of judgmental statement without justification doesn't do anything to facilitate understanding. I've been following the list for a while now because I'm in a similar situation. I used FVWM for years, and had to abandon it because when I updated my system the configuration had changed enough that I couldn't reconstruct what I had before. I've been limping with Enlightenment while I try to understand how to get back. Your comment doesn't help at all. It's a pity, why? Because FvwmIconBox doesn't work well? Because it's been deprecated in favor of something better? Because you think it's stupid? I'm sure Thomas meant no insult. There's no accounting for taste. Personally I like root window icons and I've seen a number of people on this list rail against them. as well as: PixmapPath /usr/X11R6/include/X11/pixmaps/ IconPath /usr/X11R6/include/X11/bitmaps Both of which are wrong - you should be using ImagePath here, and even then those two locations are part of the default ImagePath anyway (c.f.: fvwm-config -I). If I recall, one or both of which used to be right. So are they wrong because they're not used anymore, or because they're used for something else and aren't appropriate? For the 2 reasons Thomas cited. Now there is just an ImagePath and second because those locations should be built in which you can check with the command fvwm-config -I. Hmm, they're not built into my hand built copy. The FVWM config used to be clean and simple. It's now very different, and much more procedural. What little docs there are don't help much, so this list is the primary source for understanding. I would like to understand, as I'm sure the OP would. More explanation and less short, snappy answers would help. There are a lot of docs. Most people complain that there is too much documentation. The main problem is there are so many features no one can remember all the commands. The best solution I've found is read the man page with something that provides search capability (like XEmacs).
Re: FVWM: In Style command , how to find the application name, mplayer or MPlayer or gmplayer?
Thomas Adam [EMAIL PROTECTED] writes: Hi -- On 18/02/2008, for.register for.register [EMAIL PROTECTED] wrote: Hi, Style MPlayer !Title, !Borders Style Conky !Title, !Borders Style feh !Title, !Borders the above config works, but the following don't work Style gmplayer !Title, !Borders Style conky !Title, !Borders Style Feh !Title, !Borders so, my question is how to find the exact name in the above config? Use xprop to find the class, which generally works well. Or FvwmIdent. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: Commands NOT executed sequentially?
Emilie Ann Phillips [EMAIL PROTECTED] writes: On Jan 1, 2008 4:49 PM, Attila Nemeth [EMAIL PROTECTED] wrote: DestroyFunc HelperFnc AddToFunc HelperFnc + I ThisWindow Exec exec echo $[w.y]:$[w.x]:$[w.id] ~/.fvwm/wlist.txt DestroyFunc WSelect AddToFunc WSelect + I Exec exec rm -f ~/.fvwm/wlist.txt ; touch ~/.fvwm/wlist.txt + I All (!Iconic, CurrentPage, AcceptsFocus) HelperFnc + I PipeRead ~/.fvwm/SelectWindow.sh Now, all this is not relaible. Most of the time it works, but somtimes the wlist.txt file ends up empty or missing some windows. Like if the PipeRead kicked in too early. Is it possible that the lines in an fvwm function (WSelect in this case) are NOT executed sequentially? If you look at the documentation for Exec (http://fvwm.org/documentation/manpages/unstable/fvwm.php#lbBW) it specifies that Exec doesn't wait for the command to complete. So what is probably happening is that you are starting to run SelectWindow.sh before you finish writing to wlist.txt Right, and one solution is to use Piperead instead of Exec. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: dragging windows inside the pager
[EMAIL PROTECTED] writes: On Thu, 22 Nov 2007 13:16:22 -0800, [EMAIL PROTECTED] said: On Thu, 22 Nov 2007 15:42:31 +, Chris G [EMAIL PROTECTED] said: uh Thu, Nov 22, 2007 at 03:35:57PM +, seventh guardian wrote: [snip] If you middle-click on the page itself that's what it does, it changes the page. But when you middle-click (drag) a window, it should move.. I can't understand why it doesn't.. I have fvwm2 (2.5.21 at this end) installed on two fedora 7 systems, on neither does middle button drag a window. Middle button does the expected thing in other places. a-ha! I knew i was not crazy! :) i am on ubuntu 6.06 now it works - it happened once before. I can drag things around. But I am sure this will stop as it has the last time. So, the question is - can I cause fvwm to dump some sort of a state, or something, which I could compare to the output when things don't work to figure out what the hell is going on? Ah, you should have said it works and then it doesn't work. Check the FAQ, question 0.1. You are turning numlock on. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: closing an existing menu and opening another with one keystroke
robert muth [EMAIL PROTECTED] writes: I have a bunch of menus assigned to function keys. When I want to browse them, I have close the previous one using say the ESC key before open a new one. Is there a way to combine them into one? Make the other menus you want to use submenus with hotkeys assigned. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: starting application on specific page
Paul Novak [EMAIL PROTECTED] writes: On Thu, Nov 08, 2007 at 12:34:48PM +, Thomas Adam wrote: in my config file and I want to start an exterm on desk 0, page 0 0 and another on desk 0, page 0 1. In my InitFunction I have this line for the second x term instance: ... I'd also ask you -why- you don't just forget this approach and use: Style minnie StartsOnPage 0 0 1 Or something similar. if you ever decided to change minnie to another terminal emulator, then not all of them honour the -xrm hints. I've wondered silently about his for years. Thank you for answering it! I'm running Slackware 12.0 with fvwm2 version 2.4.20 (because that's what Slackware 12.0 comes with). I'd like to start firefox on a particular page. I can't get that to work with version 2.4.20. If I upgraded to fvwm2 2.5.* and figure out the new syntax, would I be able to pick the page that any application (including firefox) starts on? I think 2.4.x should work with Firefox. I'm using 2.5.x now but I think it's been working all along. The full incantation I use is DestroyFunc PageR AddToFunc PageR I Style $0 StartsOnPage $1 $2 $3, SkipMapping, RandomPlacement PageR Seamonkey-bin 0 0 1 PageR Netscape 0 0 1 PageR Mozilla* 0 0 1 (The Mozilla* entry will do Firefox.) -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: matching window class and name in styles
Thomas Adam [EMAIL PROTECTED] writes: On 08/11/2007, Anton Kazennikov [EMAIL PROTECTED] wrote: Hello all! Is there any possibility to match window class and name in styles? For example, Psi IM has WM_CLASS psi/mainwnd for roster list, and psi/ps i for chat windows, and I want assign different styles to them. If there isn't such possibility, will be it implemented in future? It's not possible to match *both* for the same style, no. There is a branch in CVS which breaks existing compatibility to try and do this though. If the windows have 2 different class values, Fvwm should be able to match to each one, providing that value isn't also the name or resource. (Fvwm matches all 3.) I thought the issue with the branch in CVS was that it was too big a change before the mythical 2.6 release, not that it broke compatibility. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: Function question
Thomas Adam [EMAIL PROTECTED] writes: On 24/09/2007, Ryan Daly [EMAIL PROTECTED] wrote: All: Is there an easy way to have a command and/or a function to accept a key press as an input? What I'd like to do is define a key binding that would allow me to MoveToDesk a window. The desk number would be provided by the key I press (meaning 0,1,2,3, etc.). Is there any way to do this? Not easily. You're better off writing out the explicit cases. Or having the first keypress raise a menu then the second keypress select a hot key in the menu. Menus are plenty fast enough that they can go by almost faster than you can see them. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: about Libstoreke
K.Moriyama [EMAIL PROTECTED] writes: Hello. There is Libstoreke of 2 types below in web of Libstoreke libstroke-0.5.1.tar.gz libstroke-0.5.1fvwm.tar.gz Which is used? ( for fvwm-2.5.21.tar.gz ) According to this page: http://www.etla.net/libstroke/ you should use the second one. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: fvwm-snap-20070624: make install fails without --enable-html
Harald Dunkel [EMAIL PROTECTED] writes: Hi folks, I had already sent this to fvwm-workers, but without luck. Anybody reading this list? Lots of people are reading this list. Patches get applied but most of people with commit priviledges seem to be busy lately. I know I am. Be patient. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: Gnome panel logout button
Harald Kirsch [EMAIL PROTECTED] writes: Am 02.07.2007 10:47 schrieb David Vilar: BTW, what does the option '--sm-disable' do? To be honest, I have no clue. This is a relict of my first attempts to get some gnome services, like the gnome-panel, to work under fvwm. The manual says Disable connection to session manager. And since I think this session manager thing is merely trying to be helpful rathern than being helpful, I thought to keep it as uninformed as possible.-) The session manager remembers applications you were running when you shut down and restarts them when you start up. Not something I would use. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: ModulePath (was: Pager not appearing)
Scott Smedley [EMAIL PROTECTED] writes: Comment out the line that starts with ModulePath in your .fvwm2rc -- this is about the only thing likely to cause the pager not to load. Thank you, that solved the problem. Should we consider outputting a warning message when ModulePath is used? Or even obsoleting this command? Valid use of the command is rare, but it should not be obsoleted, However, if you can detect usage of the command where the built in directory is removed instead of just adding to the path, that might be worth issuing a warning. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: ModulePath (was: Pager not appearing)
Thomas Adam [EMAIL PROTECTED] writes: On 06/06/07, Scott Smedley [EMAIL PROTECTED] wrote: Comment out the line that starts with ModulePath in your .fvwm2rc -- this is about the only thing likely to cause the pager not to load. Thank you, that solved the problem. Should we consider outputting a warning message when ModulePath is used? Or even obsoleting this command? I'd vote for no. It's useful (for those who know what they're doing) to be able to change it, The only time I know of any users who have used it is often a hang-on from an upgrade of 2.2.X - 2.4.X - 2.5.X where redefining the ModulePath was quite common for configs distributed along with distributions (think AnotherLevel, for instance). It's not often we see these sorts of questions, anyway. The 2.2 and 2.4 conversion scripts both warned about ModulePath. It used to be necessary, but now should only be used for user written modules and should normally only add to the path not reset it. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: WARNING ROOKIE alert
Window managers are not responsible for loading .Xdefaults. Some of the desktop environments like KDE take on tasks like that. What I do is start up in runlevel 3 and start X with the startx command. That will read your ~/.xinitrc where you can do: xrdb -load .Xdefaults If you are using a login manager (starting at runlevel 5) the procedure may vary. What you want to do is load the x-resources before you start fvwm. -Original Message- Date: Mon, 04 Jun 2007 07:57:08 -0500 From: Billy N. Patton [EMAIL PROTECTED] User-Agent: Thunderbird 1.5.0.10 (X11/20070221) To: fvwm fvwm@lists.math.uh.edu Subject: FVWM: WARNING ROOKIE alert I've just started using fvwm2 fvwm2 -version FVWM version 2.4.17 compiled on Dec 10 2003 at 14:03:49 with support for: ReadLine, XPM, GNOME WM hints, Shape, SM, Xinerama I had been using the default KDE, but it is such a waste or resources. I use xterms, firefox and thunderbird and that's 99% of my usage of a gui. I've done the tutorial, and I'll probably do it again. I'm going to take this in baby steps. First question. How do I get fvwm to read my .Xdefaults? I have my xterms set up just how I want them, for @ 15 years now. When I login to fvwm it doesn't read my .Xdefaults. I have to pop an xterm execute xrdb .Xdefaults kill that xterm then everything is OK
Re: FVWM: Pager not appearing
Brian Postow [EMAIL PROTECTED] writes: I'm sorry if this is a FAQ, but I haven't seen it anywhere. I have a .fvwm2rc file that I've been very happy with for several years. However, recently my machine re-booted and all of the sudden the pager doesn't appear. My .fvwm2rc file has DeskTopSize 3x3 *FvwmPagerDeskTopScale 32 Module FvwmPager 0 3 What Thomas said, and always start modules in the StartFunction. AddToFunc StartFunction I Module FvwmPager -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: How to run same/similar fvwm on two different screens/systems?
Chris G [EMAIL PROTECTED] writes: I have a small network at home and I'm running Slackware on two systems. My main system has fvwm2 all set up as I like it on a 1600x1200 screen. I now want to set up fvwm2 with a similar layout on the second system which has a 1024x768 screen. I have set up NFS so that the second system sees the same home directory as my main system (that's the way I want it for lots of other reasons anyway). What's the easiest way to get fvwm2 set up on the second system? I start X manually using startx and, as far as I can see, that always reads .xinitrc to see what to do so how can I start fvwm2 with a different .fvwm2rc file on the two different systems? Or is there a cleverer way to do it - e.g. can I specify screen positions and sizes in percentage terms rather than absolute pixel terms? This isn't strictly Fvwm, but some of my apps are partly controlled by X resources. Here is part of my config for XEmacs: ! Geometry changes based on screen size: #if ( HEIGHT == 900 ) /* Traditional Sparc */ Emacs.geometry: 81x55+0+0 #elif ( HEIGHT == 1024 ) /* Sparc 21 inch */ Emacs.geometry: 81x63+0+0 #elif ( HEIGHT == 768 ) /* Exceed in 1024x768 mode */ Emacs.geometry: 81x46+0+0 #elif ( HEIGHT == 1200 ) /* My home machine, 1600x1200 use side x side layout */ Emacs.geometry: 81x56+0+0 #else /* other sizes, take guess... */ Emacs.geometry: 81x40+0+0 #endif -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: a drag
Bernard Lang [EMAIL PROTECTED] writes: Hi, I have been a quiet FVWM2 user for about 10 years, solving my own problems, and modifying my fvwm2rc file as needed. I just switched to a new machine (64 bits) and everything is wrong, and I cannot solve my problems any longer. model name : Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz Mandriva Linux release 2007.0 (Official) for x86_64 What version of Fvwm2 are you using? -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: a drag
Bernard Lang [EMAIL PROTECTED] writes: * Thomas Adam [EMAIL PROTECTED], le 07-05-07, a =EF=BF=BDcrit: On 07/05/07, Bernard Lang [EMAIL PROTECTED] wrote: =20 Starting with simple things : I used to drag windows by pressing mouse-left on the title-bar, dragging and releasing in the right place. =20 FYI, strings is overkill, a simple: =20 fvwm --version =20 would have done. Can you please use 2.5.21 -- 2.5.10 is very old and some significant improvements to FVWM's 64-bit support have been made since that version. 2.5.10 is the one that came packaged for urpmi on my Mandriva Linux. ... I am moderately eager to recompile things myself. But you seem to suspect that could be the source of my problems ? Yes, as far as we know current Fvwm2 works with 64bit systems. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: raise/focus issue
tomdeb [EMAIL PROTECTED] writes: Hi, I am using unicode-rxvt as a terminal and when urxvt does not have focus, the window seems to be darken or tinted and it gets more difficult to read an unfocused terminal. Is there any style to disable this behaviour ? See the urxvt man page for fading. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: sidebars and icons in XPM or PNG?
Michelle Konzack [EMAIL PROTECTED] writes:
Am 2007-05-04 20:26:08, schrieb Hans Voss:
I would go for PNG because of it being newer and I believe that it
also supports transparancy (and XPM did not).
XPM is supporting pransparency ;-)
/* XPM */
static char * 31x31_mutt_xpm[] =3D {
32 32 121 2,
c None,
.c #282728,
+c #121112,
@c #00,
#c #C7C3C7,
$c #767476,
%c #504E50,
None is transparency
That's shape, transparency would partially
block the image below.
--
Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: Beginners-Infos /Example-Files(simple,please) ?
[EMAIL PROTECTED] writes: Yes, I have undertaken several attempts to do this, received some sporadic help from people, and then they dropped off the planet. Which is fine... I also still seem to be, despite some enthusiasm from other people, the only person still actively contributing information to the FVWM Wiki, as well as churning out FVWM documentatio for LG. If you're the only person contributing, does this mean that FVWM is slowly dying? Long ago, we changed the project rules from one person in charge to fvwm-workers in charge. One of the goals was to keep the project viable no matter who left. As long as enough people hang around to keep passing on commit priviledges, I don't think the project will ever die. It would be nice to have a better default config. Someone has to identify the current bad defaults and suggest changes. Fvwm is mostly aimed at people that don't mind reading docs and fiddling with config files. There are related projects that generate config files. Ie. fvwm-themes and maybe more. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: Beginners-Infos /Example-Files(simple,please) ?
Elliot Sowadsky [EMAIL PROTECTED] writes: Perhaps the default config should have everything rather than nothing. It's easier to remove features you dont like than to add what you dont know how. JG That statement is a paradox. JG What does everything means? Everything for you? Everything for me? JG Everything for Thomas? mmm, nah, that's impossible. By making JG everything for anyone, you defeat the original purpose, of making it JG to be everything for everyone. The only way to have everything for JG everyone it to have a very basic default, so you can work your own JG from the ground. JG For the complexity and variety of configuration potentially available JG on FVWM, that suggestion is just impossible to achieve. Load it up w/ all the modules and commandsand a startup message mentioning where the config file is to strip stuff out and where to find the doc. Once they start stripping stuff out, theyll catch on. Don't forget that when you start with an empty config file you get a built in menu that lets you invoke the FvwmForm setup form. That will configure FvwmBacker, FvwmButtons, FvwmIconBox, etc. (9 modules). -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: can window frame colors be dependent on the host that runs the app?
Charles T. Smith [EMAIL PROTECTED] writes: I typically have windows from various hosts on my desktop and sometimes it gets confusing. It would be really nice if each host could be assigned a particular frame color. Is there a way to do that? I see you got advice to use -class and it messed up your xresource matching. With rxvt I'm using -name, -n and -title. I forget which one does the trick. XTerm has similar options. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: FVWM and KDM
seventh guardian [EMAIL PROTECTED] writes: On 3/16/07, Arvin Schnell [EMAIL PROTECTED] wrote: Hi, since I could not find examples about controlling KDM from FVWM I figured it out myself. You can see my results here: http://arvin.schnell-web.net/linux/kdm-fvwm.html Maybe you want to include this in your examples distributed with FVWM or in your FAQ. I find this very interesting. In fact I wanted to do this back when I used kdm. Now that I use qingy I want a way to do this with it, but that's yet to be implemented, I believe. I didn't find it very interesting. I tried kdmctl but it seems to want something else to be running: home kdmctl Cannot connect socket '/var/run/xdmctl/dmctl-:40/socket'. And it lacked a man page: home man kdmctl No manual entry for kdmctl So, If I wanted a menu entry to shutdown my computer I'd enable shutdown for sudo without a password. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: Turn off automatic hotkeys in WindowList menu
GoogleGuy [EMAIL PROTECTED] writes: Hi All, I've been wanting to turn off the automatic hotkeys in the WindowList menu, and the man said I needed the AutomaticHotkeysOff option. However, I can't get it to work. Right now my menu definition looks like so: MenuStyle WindowList ItemFormat %.0s%.4|%.10i%.5l%.5l%.5r%2.3%10|, \ ActiveFore, HilightBack, TitleUnderlines1, \ Hilight3DOff, PopupOffset 0, SeparatorsLong, TrianglesSolid, \ MenuColorset 14, ActiveColorset 16, GreyedColorset 17, \ BorderWidth 1, \ Font xft:Arial:Bold:size=10pt, \ AutomaticHotkeysOff But, this doesn't work. Am I missing something obvious here? Any pointers will be gladly accepted. I don't know if we lost the formatting in transmission, but: The first 2 lines need to be joined with a backslash. A few of the lines have a trailing space after the backslash which will cause the line to end and the rest to be ignored. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: build failure: cannot find -lXext on FC6
Peter Scott [EMAIL PROTECTED] writes: I have just upgraded(?) from Fedora Core 5 to Fedora Core 6, and since I like fvwm a lot and have an excellent config file for fvwm, I tried building fvwm-2.5.18. but it fails in the final steps. ./configure works cleanly with no options. make bombs with this error message: gcc -DFVWM_MODULEDIR=\/usr/local/libexec/fvwm/2.5.16\ -DFVWM_DATADIR=\/usr/local/share/fvwm\ -DFVWM_CONFDIR=\/usr/local/etc\ -DFVWM_COLORSET_PRIVATE=1 -DLOCALEDIR=\/usr/local/share/locale\ -Wall ... -L/usr/lib64 -lXpm -lstroke -lSM -lICE -lXext -lX11 -lm -lpng -lz /usr/bin/ld: cannot find -lXext collect2: ld returned 1 exit status make[2]: *** [fvwm] Error 1 [...] libXext is installed: locate libXext yields: /usr/lib/libXext.so.6 /usr/lib/libXext.so.6.4.0 /usr/lib64/libXext.so.6 /usr/lib64/libXext.so.6.4.0 You appear to be missing the soft link for the library itself. It should look something like: lrwxrwxrwx /usr/X11R6/lib/libXext.so - libXext.so.6.4 lrwxrwxrwx /usr/X11R6/lib/libXext.so.6 - libXext.so.6.4 -rwxr-xr-x /usr/X11R6/lib/libXext.so.6.4 There needs to be one file named libXext.so. Create a soft link. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: Strange behavior w/ FC6
[EMAIL PROTECTED] writes: All: I'm not sure if this is the right place to ask this or not...but here goes. When using XDM w/ FC6, and I log in and attempt to have it start my FVWM desktop, strange things happen. My fonts are not correct. What does that mean. Do you see fonts? Are they the right size? Look in your fvwm config file. What fonts does it call for? Can you use those fonts for any other program? Sometimes FvwmIconMan has place holders when there are no windows present to fill the space. Various environment settings are not correct. Not sure about this. Have you installed any icon packcage? Has anyone else experienced this? Any hints anyone can pass along would be greatly appreciated. What version of fvwm are you running? How did you install it? -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: default .fvwm2rc file - what should I use?
Macintyre, Ross A [EMAIL PROTECTED] writes: Hi, I hope someone can help. I've just installed FC5 on a number of machines and installed fvwm-2.4.19-1. For some people who didn't have .fvwmrc or .fvwm2rc files, fvwm did not work. Please define 'did not work'. What should happen is that the user presses any button on the root window and a menu appears giving options to build an initial .fvwm2rc file. Please don't send any html to this list. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: XMMS_Playlist is always StickyPage and StickyDesk
Viktor Griph [EMAIL PROTECTED] writes: On Mon, 25 Sep 2006, Michelle Konzack wrote: Am 2006-09-25 16:06:12, schrieb Viktor Griph: Not having used XMMS, this is just a wild guess, but you might try to style it with EWMHIgnoreWindowType. Before I tell you, that this option is not in my Fvwm2 manpage, I have tried it. - No change! The option was added in fvwm 2.5.15 and is in the manpager. If you are using a version prior to 2.5.15 I suggest that you upgrade. You may however test to see if the style EWMHIgnoreWindowType would help in the particular way. Just do the following test: 1) Does Stick off make the window bahave as you want? 2) If so, does WindowStyle Slippery make the window bad again? If you answered yes to both questions you'll want the EWMHIgnoreWindowType style for that window. If not, then something else is wrong with the application. Sorry, I've been ignoring this thread. I just took a look at my XMMS options. One of them is 'show on all desktops'. Set or unset it as desired. -- Dan Espen E-mail: [EMAIL PROTECTED]
FVWM: fvwm crystal
Fvwm Crystal is being discussed on Slashdot: http://slashdot.org/article.pl?sid=06/09/17/1414255 -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: automatically generated menus
Emilie Ann Phillips [EMAIL PROTECTED] writes: I just changed versions of linux on my machine. During the transition, I have been using the default environment -- kde -- since I figured it would have the most useful tools for configuring the system. Now that I have configured/broken everything that I was intending to, I am going to switch back to fvwm. The biggest tool that I would like to carry over to fvwm is the dynamically generated menus. I have heard some discussions on this list that people don't like the freedesktop.org standards that kde uses and as I understand fvwm doesn't natively support it. Is there a built in way in fvwm to generate menus based on all the applications installed on the system? Alternatively, does anyone already have a script for parsing the kde .desktop files and generating menus from them? Try: man fvwm-menu-desktop NAME fvwm-menu-desktop - builds GNOME and KDE menus and style commands for FVWM -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: FVWM for government system
Thomson, David-P63356 [EMAIL PROTECTED] writes: FVWM Developers, I was told I can only ask questions on here if I am sufficiently vague about what we are doing. I work for a government contractor and we are currently working on a contract for one of those 3-lettered agencies to do something with PCs and I am in charge (at the moment) of the UI design. Suffice it to say that our final project will be used by most every gov/mil agency at some point in the coming years. We did a market survey of window managers for the UI a while back and actually have chosen FVWM. Enough said... Here's my hopefully simple task: learn enough about FVWM to modify it to meet our needs. Seeing as I am still an amateur in modifying WMs, I hope to pick all your brains, and maybe get a little help while writing these changes. Having FVWM on many MANY systems in 3-letter abbreviated organizations and special operations type organizations along with getting your beloved FVWM to become pretty ubiquitous may be motivating factors. Let me know if this is the place to ask questions and if any of you are willing and able. My first task involves SELinux security labels and per-window decoration. Dave Please don't send html to this list. To ask questions about fvwm, use the email address [EMAIL PROTECTED] SELinux security labels seem to be properties of the file system, not x windows. I'm not clear on what you want to do. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: Color / ForeColor no longer supported?
Peter Daum [EMAIL PROTECTED] writes: Hi, already for a while now (I think it started shortly after 2.5.15) the specification of a foreground color for a window (something like Style * Color red/green or ForeColor red) has been silently ignored. Are these commands obsoleted by the newer colorset stuff and only the documentation not yet adjusted or is it just a bug (background is still honored). Is there a simple workaround? See this thread: http://www.mail-archive.com/fvwm-workers@lists.math.uh.edu/msg15103.html -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: Latest Beta and Eclipse
Jake Colman [EMAIL PROTECTED] writes: Several weeks ago I posed a problem with the display performance of Eclipse when using FVWM 2.5.7. A reasonable poster suggested that I should at least upgrade to a newer version. I jave just installed v2.5.16 and Eclipse performance now seems reasonable and roughly equivalent to using it under CDE. My problem now is with screen flicker. If I display a modal dialgoue (e.g., the plugins list on top of the Help dialogue), as I scroll the plugins list the Help dialogue is constantly being repainted. This is certainly annoying and also makes the display less responsive. Are there configuration settings that I should be looking at, or are there settings that I should be posting, that might explain some of this? Review the fvwm man page for saveunder and backingstore. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: Latest Beta and Eclipse
Thomas Adam [EMAIL PROTECTED] writes: On Tue, Jul 18, 2006 at 11:31:13AM -0400, Dan Espen wrote: Review the fvwm man page for saveunder and backingstore. I've never had any luck with using these, and found FVWM to crash a lot when they were enabled. I also fail to see how that would help, when purportedly, the issue isn't happening on the antiquated FVWM 2.2.2 version. Just to be clear, I don't see how they would help either, I just think they are related to display speed and redraws so it couldn't hurt to investigate. The man page mentions how to check the X server. If Fvwm crashes, it would be good to report the bug. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: ChangeLog vs modules/ChangeLog ?
seventh guardian [EMAIL PROTECTED] writes: Hi. I have a question regarding the use of the ChangeLogs. Obviously, changes to the fvwm core are reported in the root ChangeLog. But what about changes to modules? I ask this because I've allways logged my changes to the root one, but now think I should have done it to modues/ChangeLog. On the other hand, there are lots of module changes in the root changelog.. So, what is our ChangeLog policy? If it is module stuff - modules/ChangeLog, rest - ChangeLog, then I guess module stuff should be moved to the correct modules/ChangeLog. If not, then we would be better served with just one ChangeLog, in wich case we should merge both. The Changelogs were getting huge so they were split up. Using Emacs, you find the right one using C-x 4 a. Otherwise it's the first one above the directory your in. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: debug.c still useful?
seventh guardian [EMAIL PROTECTED] writes: Hi. After some checking around, it seems that the file libs/debug.c isn't used anymore. The file was created in 1998 as a debuging library, but it seems to have been replaced by simpler solutions. It's part of libfvwm.a, and the *.c code is surrounded by a #ifdef DEBUG, so never gets compiled. The whole file is empty at the moment, except for an int variable that is there (outside the #ifdef) expressly to prevent an empty file, as some compilers don't like that (it's written on the coments). On the other hand, the header file fvwmlib.h has its macros and structs allways defined, (but there is no compiled code!). Nothing is ever used, so I think it's safe to remove it. These are the only places where you find the macros (which need to be removed ): - DB() is in a #if 0 part of module_interface.c (but the rest of the file already uses the DBUG macro) and in focus. - __FILE__ and __LINE__ is in a ifdef'ed to 0 part of focus.h where alternative debuging macros are defined. It's a big decision to remove a whole file, so I need a second opinion.. Is the file still useful or may I remove it? The whole debug facility is rarely used, and I can't remember it ever being useful. I find the stuff in FvwmAnimate/FvwmForm suits my own personal needs. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: Libtool ltdl on fvwm
Dominik Vogt [EMAIL PROTECTED] writes: --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 07, 2006 at 11:05:36PM +0100, seventh guardian wrote: It all starts with this snip from docs/TODO: =20 - Implement (or at least investigate) dynamic loading of functions on systems that support it? =20 (There is more on that on that file. These are just the first two lines) =20 Recently I began testing GNU's Libtool on a project of mine, particulary using Ltdl. Ltdl is a dynamic library loading framework. It allows dynamic loading of modules for an application, or or as a last resort for systems not supporting it, either preloading (linking just before execution) or static linking (during the compilation time). It's very portable and flexible, as you can see from here: http://www.gnu.org/software/libtool/manual.html#Tested-platforms =20 Anyway, it would be great to have the facility to load new styles or functions from a library (a ltdl module). Minimalistic systems would just load (or compile, depending on the arch) the very basic functions and styles, while more feature-rich systems would load all of them. The unoficial feature patchsets would be replaced by style modules (it has nothing to do with the current fvwm modules).. And so on. The text on docs/TODO explains the whole idea. For those interested in this, you can find libtool's manual here: http://www.gnu.org/software/libtool/manual.html =20 For now I'm studying the fvwm code to see where this fits. I'm thinking of trying it out (in a my local private branch, as this is definitely not a 2.5 feature). If I get to do anything I'll inform you. Paul added this TODO item ages ago. Specifically he suggested to make libfvwm a shared library. I am well aware of Libtool's capabilities, but never was very fond of the idea to use it. No matter how portable it is, we'd ask for a lot of problems with library versioning (modules finding a wrong version of the lib). The idea to allow dynamic loading of features is nice. But frankly I think the fvwm core is nowhere near as modular to allow features being taken out of it. (And even this is an euphemism for the state of the code). The TODO item is for modules. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: debug code cleanup patch #1
Bob Woodside [EMAIL PROTECTED] writes: On Thursday 06 July 2006 16:19, Dominik Vogt wrote: On Thu, Jul 06, 2006 at 08:23:50PM +0100, seventh guardian wrote: On 7/6/06, Dominik Vogt [EMAIL PROTECTED] wrote: The patch looks fine. I'll commit it. By the way, do you have commit privileges for CVS? No, I don't.. Am I ready for it? :) I think so :-) Any second vote for Renato? I'll cast a second . Third. Renato, if you haven't seen it already, check the Fvwm web site Developer section for getting commit access. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: Periodic command
Viktor Griph [EMAIL PROTECTED] writes: On Wed, 5 Jul 2006, Scott Smedley wrote: Hi Dominik, Can you have multiple peridic commands or just one? Multiple. I suggest to replace the command Periodic with some option to the Schedu le command The current specification for Schedule is: Schedule delay_ms [command_id] command So, would something like the following do? Schedule delay_ms [command_id] [Periodic] command Perhaps someone has a better suggestion? I think the above is good. The only problem with it is that if someone has a function named Periodic and use to execute that with Schedulte the above will break that config. One way to avoid that, and also give room for more possible options to Schedule in the future, is to put options before the delay. That way any string before the delay number could be read as an option. So Schedule [Periodic] delay_ms [command_id] command would be a possible easier to parse syntax. How about: Schedule delay_ms x repeat_ms [command_id] command Ie: Schedule 1000 x 2000 Schedule x 5000 -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: Title font color broken
Serge (gentoosiast) Koksharov [EMAIL PROTECTED] writes: On Sun, Jun 04, 2006 at 11:15:29AM +0200, Dominik Vogt wrote: Unfortunately I never got any feedback on this from the person who reported it first. The problem was that in some cases the GC used to draw the title was not set before drawing, but it seems the old code relied on this not being done. I'd be grateful if someone could look into this problem or at least give me a minimal config to reproduce it. I can confirm Dan's bugreport. And it easily reproducable with minimal config: I compile FVWM like this: aclocal autoheader automake --add-missing autoreconf ./configure --prefix=$HOME/usr --oldincludedir=$HOME/usr/include \ --enable-xft --disable-xinerama --enable-iconv --disable-bidi \ --enable-perllib --enable-nls --enable-gtk --with-x --without-rplay-library \ --without-gnome make make install Then I move entire ~/.fvwm directory somewhere: $ mv ~/.fvwm ~/usr/src Create new empty directory: mkdir ~/.fvwm Create '~/.fvwm/config' file consisting of two lines: Style * ForeColor red Style * HilightFore red Launch FVWM and see that titles of both active and inactive windows are black, but not red. I hope you can reproduce it as well and fix this bug. If not, you can provide me with instructions what to do next and I'll be more than glad to help. Dominik posted a patch containing the commit that caused the problem. He asked for help trying to recreate the original problem he was trying to patch. We could just revert his patch, but the original problem would remain unsolved. I haven't had any time to look into this yet. -- Dan Espen E-mail: [EMAIL PROTECTED]
Title font color broken
It's been a while since I've updated to CVS. Maybe a month or 2. After the last update, the text in my window titles is black. These commands have no effect: Style * ForeColor white Style * HilightFore white So far, I don't see the change that broke this. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: Title font color broken
Thomas Adam [EMAIL PROTECTED] writes: On Sat, Jun 03, 2006 at 11:57:58AM -0400, Dan Espen wrote: It's been a while since I've updated to CVS Maybe a month or 2 . After the last update, the text in my window titles is black. These commands have no effect: Style * ForeColor HilightFore Last I heard those commands were being deprecated in favour of using colorsets. Good thing someone is still using them so we don't break things that are only deprecated. Actually, I don't see anything in the man page about colorsets being required. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: Project Support Open Source (SOS) wanted to donation to your project
Any opinions on this? Bob Mutch [EMAIL PROTECTED] writes: Hi Dan, Sent it to the list if that will help and to the top contributors also. Current we are donating $10,000 to 200 projects which is $50 per project. Please let me know what license your project is under and the page and location in the page where this is stated. We will be asking other companies to donate to the list we are compiling also. This is the acknowledgement I would like placed. a href=http:/www.seocompany.ca/SEO Company/a financially supports the free and open source software (FOSS) community with Project SOS (Support Open Source). Find below the 5 requirements and 7 questions I need answers for. Sorry to have to send you a form letter like this but I am currently over 100 emails behind on this project. Requirements: 1. The project must have a website. 2. You must place an acknowledgment of the each donation on your site. 3. Your project must be currently active and has produced a software product. 4. Your software product must be released under a free open source software license and this must be stated somewhere on your site. 5. You must have a PayPal address or PayPal service that donations can be sent to. Questions: 1. Will you be able to place an acknowledgement of each donation on your website? 2. What page would you be putting the acknowledgement on? 3. What is your PayPal account email? 4. What license is your software project released under (GPL, LGPL, BSD, GNU, OSI approved, or what ever) and what is the URL of the page where the license information is posted? 5. What was the date of the first version of your software? 6. How many different versions of the projects software have been released? 7. Is your project currently active? Also check out my Project SOS page. http://www.seocompany.ca/project-support-open-source.html If you don't mind you can digg me at digg.com and even leave a comment after you get a donation. http://digg.com/software/Company_throwing_money_at_open_source_projects If you blog or have friends that blog you may want to ask them to blog up on the project. The more noise we make the more companies that will use my list to make donations and the more money that will be sent to support your project. Thanks! Bob Mutch 519-636-6663 [EMAIL PROTECTED] http://www.seocompany.ca/project-support-open-source.html bobmutchseo -- Yahoo IM [EMAIL PROTECTED] -- MSN Messenger bobmutchseo -- AIM -Original Message- From: Dan Espen [mailto:[EMAIL PROTECTED] Sent: May 19, 2006 5:30 PM To: [EMAIL PROTECTED] Subject: Re: Project Support Open Source (SOS) wanted to donation to your project Bob Mutch [EMAIL PROTECTED] writes: Hi my name is Bob Mutch and I am the owner of Solutions with Service, a Canadian company that uses open source software products. I have started a project called Project SOS (Support Open Source) to help fund free and open source software projects. I would like to make a donation to your open source work http://www.fvwm.org/ though our project. Here is the page that how the donations work. http://www.seocompany.ca/project-support-open-source.html Seems to be a broken link. There has been a post on digg.com with a few comments from open source developers that have received donations already. http://digg.com/software/Company_throwing_money_at_open_source_projects Do you have a page where you give acknowledgement to your sponsors? Let me know! Fvwm is far from 'my' project. I'm an occasional contributor. If you don't mind this being mentioned in a public mail list, send this mail to [EMAIL PROTECTED] Otherwise, I can send you a list of a few of the top contributors. -- Dan Espen E-mail: [EMAIL PROTECTED] -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: fvwm and GTK dialoges (fonts) [Arghhhhh]
Michelle Konzack [EMAIL PROTECTED] writes:
Hello,
Maybe I fing here a GTK (1.2) specialist...
I have some tools (BASH scripts) which use Xdialog and one of
the tools (picture attached) I use regulary drives me crazy...
The left dialog is run from crontab and it shows the list
in fixed font but the Date/Time and the phrase are in a TOO BIG
font.
+---[ '/home/michelle.konzack/.tdnewmsg/gtkrc' ]--
|
| style tdnewmsg-fixed {
| font=-*-fixed-medium-r-normal--9-*-*-*-*-*-iso8859-1
| }
|
| widget *GtkCList style tdnewmsg-fixed
+-
The right dialog is run from a FvwmButton or a menu, where the
fixed font is ignored but the Date/Time and the phrase is right.
This give me a Arghh!
Can anyone give me some hints HOW to setup the Dialog with fixed
font in the LIST-Box and the small font in the rest of the dialog?
I mean ALWAYS, and not only from crontab OR FvwmButton.
Oh yes, since some weeks I am coding with GTK+2.0 which give me
other problems... The scalable fonts are TOOO small and I
can not make it bigger.
You can't post attachments here.
Put them on the web somewhere and post a link.
I don't think this is an Fvwm question.
I'm not a Gtk expert.
Most of my use is thru Gtk-Perl.
For Gtk1, I used the Gtk preferences dialog to control font size.
For Gtk2, you can also use preference dialogs, but if
you don't want global control you can do this:
my $font_desc = Gtk2::Pango::FontDescription-from_string (Nimbus bold 8);
$object-modify_font ($font_desc);
(The 8 is the font size.)
--
Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: Style's wildcard don't work with Firefox
Serge (gentoosiast) Koksharov [EMAIL PROTECTED] writes: Hi, I'm encountered strange behaviour in FVWM 2.5 CVS version with Firefox. If I have following line in my ~/.fvwm/config: Style * IconOverride, Icon $[FVWM_USERDIR]/icons/myicon.png Firefox when iconified uses its default built-in icon, not myicon.png. But if I change this line to: Style Firefox-bin IconOverride, Icon $[FVWM_USERDIR]/icons/myicon.png All works fine, and Firefox uses myicon.png. I tried this with empty config also, it still works as described. So, I guess, 'Style * IconOverride' for some reason don't influence Firefox. What it is? Firefox incorrect behaviour? Or some quirk in FVWM? It's 'Style * Icon' that doesn't work as you expect. Search for Style ** in the man page. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: Wine problem
Thomas Adam [EMAIL PROTECTED] writes: On Mon, May 08, 2006 at 08:11:10AM +0200, Leonardo Cosmai wrote: I have IBexpert, a program that runs under Wine. Ibexpert has a layout Under Wine? Let's try and see what you mean by that: 1. You mean it's self-contained within a wine window, in which case that's nothing to do with FVWM, or: 2. You've told Wine not to manage its windows in favour of allowing the window manager to try and do so (always a bad idea -- you've no idea just how troublesome that can be; and it's not even FVWM's fault). I wonder which it is... I don't use wine, but I remember this in my ~/.wine/config: ; Allow the window manager to manage created windows Managed = Y You should make sure yours is set to Y. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: yet another documentation fixes
Thomas Adam [EMAIL PROTECTED] writes: On Wed, Mar 29, 2006 at 02:21:05AM +0400, Serge (gentoosiast) Koksharov wrote : Greetings everyone, As promised, I found and corrected another bunch of typos and other inconsistencies in the docs. Apply against the latest CVS sources of the 2.5 branch. But that's not all, more will follow when I find time to check remaining part of the docs. See you later. There's a mistake in one of your fixes: @@ -36,7 +68,7 @@ * sample.fvwmrc/system.fvwm2rc-sample-1: replaced all mentions of `rsh' with `ssh'. rsh is obsolete and inherently insecure. We shouldn't teach our users bad things, - should we? + shouldn't we? The phrase: We shouldn't teach our users bad things, should we? is the correct one. The negation of NOT teaching the users bad things has already been done. It is neither correct English or grammatically correct to say: We shouldn't teach our users bad things, shouldn't we? Check what got checked in. I made a fix in that area. I need to review some of your other fixes --- whilst you've made a fantastic effort in doing so, I can already see one or two technical mistakes that need changing. I'll have to apply this patch and somehow reverse engineer your changes. But thank you ever so much for your efforts. Gee, I hope all the mistakes aren't my fault. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: fvwm 2.5.x (bug|spell)fixing patch
Dan Espen [EMAIL PROTECTED] writes: Serge (gentoosiast) Koksharov [EMAIL PROTECTED] writes: Hi, dear FVWM developers, I created this patch which should apply cleanly against FVWM CVS sources of the 2.5 development branch. It mostly fixes documentation typos, mispellings, formatting errors, etc... Also it fixes delay in one of the FvwmAnimate animations. Please keep in mind, that I'm FVWM newbie, so doublecheck my work. I'll keep an eye on your project and try to help as much as I can. Thanks. You sure found a lot of spelling errors. It might take me a while, but I'll apply the patch. In fvwm-perllib.in explicitely' should be explicitly. Best wishes! P.S. could my name be added to the AUTHORS file? There already one guy who helped with documentation fixing. Sure. I applied that patch a couple of days ago, but I never saw the email from the CVS update. The amount of errors you found in the documentation was impressive. No only did you find spelling errors, and grammatical errors, but also just plain wrong things, and misplaced things. I wonder, how did you do that? -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: fvwm 2.5.x (bug|spell)fixing patch
Serge (gentoosiast) Koksharov [EMAIL PROTECTED] writes: Hi, dear FVWM developers, I created this patch which should apply cleanly against FVWM CVS sources of the 2.5 development branch. It mostly fixes documentation typos, mispellings, formatting errors, etc... Also it fixes delay in one of the FvwmAnimate animations. Please keep in mind, that I'm FVWM newbie, so doublecheck my work. I'll keep an eye on your project and try to help as much as I can. Thanks. You sure found a lot of spelling errors. It might take me a while, but I'll apply the patch. In fvwm-perllib.in explicitely' should be explicitly. Best wishes! P.S. could my name be added to the AUTHORS file? There already one guy who helped with documentation fixing. Sure. -- Dan Espen E-mail: [EMAIL PROTECTED]
