FVWM: Thank you for 2.6!
Hi, Just wanted to say a big thank you to the people who released 2.6, who was that? i think an interview would be interesting! Does fvwn accept donations or can users show their appreciation somehow? A very happy fvwm user, Jason
Re: fvwm-2.6.0 bug(?)
On 19 April 2011 03:53, des...@verizon.net wrote: I'm not seeing email on the fix for delayed menu building. Yes -- it can take up to a day for some of the commit emails to come through -- I am not sure why, as this never used to be the case. -- Thomas Adam
fvwm 2.6.1 - error with make deb-inplace
Hi!I've compiled fvwm 2.6.1 tarball on my Debian Lenny with make deb-inplace and get the following output at the end:fakeroot dh_gencontrol -P`cd .. pwd`/inst-2.6.1dh_gencontrol: Compatibility levels before 4 are deprecated.fakeroot dh_md5sums -P`cd .. pwd`/inst-2.6.1dh_md5sums: Compatibility levels before 4 are deprecated.fakeroot dh_builddeb -P`cd .. pwd`/inst-2.6.1dpkg-deb: building package `fvwm' in `../fvwm_2.6.1-0.20110419_i386.deb'.dh_builddeb: Compatibility levels before 4 are deprecated.dpkg-genchanges: including full source code in upload/bin/sh: debsign: command not foundmake[1]: [inplace] Error 127 (ignored)fakeroot dh_clean -P`cd .. pwd`/inst-2.6.1dh_clean: Compatibility levels before 4 are deprecated.rm -rf `cd .. pwd`/inst-2.6.1(cd .. ls fvwm_2.6.1-0.`date +%Y%m%d`*)fvwm_2.6.1-0.20110419.dsc fvwm_2.6.1-0.20110419_i386.changes fvwm_2.6.1-0.20110419_i386.deb fvwm_2.6.1-0.20110419.tar.gzmake[1]: Leaving directory `/home/tf/sources/fvwm/fvwm-2.6.1'As I installed package 'devscripts' which includes debsign I got this:fakeroot dh_gencontrol -P`cd .. pwd`/inst-2.6.1dh_gencontrol: Compatibility levels before 4 are deprecated.fakeroot dh_md5sums -P`cd .. pwd`/inst-2.6.1dh_md5sums: Compatibility levels before 4 are deprecated.fakeroot dh_builddeb -P`cd .. pwd`/inst-2.6.1dpkg-deb: building package `fvwm' in `../fvwm_2.6.1-0.20110419_i386.deb'.dh_builddeb: Compatibility levels before 4 are deprecated.dpkg-genchanges: including full source code in uploadsignfile ../fvwm_2.6.1-0.20110419.dsc Fvwm Workers fvwm-workers@fvwm.orggpg: skipped Fvwm Workers fvwm-workers@fvwm.org: secret key not availablegpg: [stdin]: clearsign failed: secret key not availabledebsign: gpg error occurred! Abortingmake[1]: [inplace] Error 2 (ignored)fakeroot dh_clean -P`cd .. pwd`/inst-2.6.1dh_clean: Compatibility levels before 4 are deprecated.rm -rf `cd .. pwd`/inst-2.6.1(cd .. ls fvwm_2.6.1-0.`date +%Y%m%d`*)fvwm_2.6.1-0.20110419.dsc fvwm_2.6.1-0.20110419_i386_1.deb fvwm_2.6.1-0.20110419_i386.debfvwm_2.6.1-0.20110419.dsc.asc fvwm_2.6.1-0.20110419_i386.changes fvwm_2.6.1-0.20110419.tar.gzThe package works, so it's only an info to Fvwm team ;-)Regards,Thomas--Life is like a box of chocolates - never know what you're gonna get.Schon gehrt? WEB.DE hat einen genialen Phishing-Filter in dieToolbar eingebaut! http://produkte.web.de/go/toolbar
Re: fvwm 2.6.1 - error with make deb-inplace
On Tue, Apr 19, 2011 at 03:46:32PM +0200, Thomas Funk wrote: Hi! I've compiled fvwm 2.6.1 tarball on my Debian Lenny with make deb-inplace and get the following output at the end: fakeroot dh_gencontrol -P`cd .. pwd`/inst-2.6.1 dh_gencontrol: Compatibility levels before 4 are deprecated. fakeroot dh_md5sums -P`cd .. pwd`/inst-2.6.1 dh_md5sums: Compatibility levels before 4 are deprecated. fakeroot dh_builddeb -P`cd .. pwd`/inst-2.6.1 dpkg-deb: building package `fvwm' in `../fvwm_2.6.1-0.20110419_i386.deb'. dh_builddeb: Compatibility levels before 4 are deprecated. Not surprising. This hasn't been updated to use DH7. The package works, so it's only an info to Fvwm team ;-) I wish we could simply *remove* this, but we had that conversation in the past [1]. I hence have no intention of caring whether this works or not; it's not my problem per se, but it annoys me this is allowed to sit in the FVWM tree and *bitrot* because the person who wants responsibility for it only ever pops his head out of the parapet when the status quo is challenged on getting it removed in favour of upstream's version. -- Thomas Adam [1] http://www.mail-archive.com/fvwm-workers@fvwm.org/msg01785.html
Re: fvwm-2.6.0 bug(?)
Sergey Vlasov v...@altlinux.ru writes: On Mon, 18 Apr 2011 13:46:22 -0400 des...@verizon.net wrote: Thomas Adam tho...@fvwm.org writes: On Mon, Apr 18, 2011 at 02:14:38PM -0300, Jim Diamond wrote: I am running fvwm 2.6.0 on Slackware64 13.1. When it starts up it (apparently) runs fvwm-menu-desktop, which sends out the following complaints: -- WARNING: '/etc/kde/xdg/menus/applications-kmenuedit.menu' does not exist Unknown 'DefaultLayout': ... I think it's a bug in the kde config files. Actually DefaultLayout and Layout are valid freedesktop menu tags, but they are not implemented in fvwm-menu-desktop. These tags are optional, but should be ignored silently instead of printing such debug output. Ah, sorry. I should have said I think the first line is a bug in the kde config files. (The message about kmenuedit.) I've committed fixes for the Layout and DefaultLayout elements. If anyone has a system they can test this on, it would be nice to get some feedback. Just run fvwm-menu-desktop. From the command line is okay and look for error messages.
Resizing screens
Due to my laptop developing a flaky panel connector, I recently got an external monitor for it. Switching outputs works great (with xrandr), but now I've got two outputs with different native resolutions, and I'd like to get fvwm to handle this nicely. The first thing is that X will now send a ConfigureEvent for the root window of the screen when the size of the screen changes. I wrote up the obvious patch to update Scr and screens[0] in FScreen, and it seems to work. I'm not sure if there's anything more that needs to be done in fvwm to deal with the size of the Screen changing; it seems like the effects are at worst annoying (Windows off of the Screen because it shrank, windows placed relative to the right and bottom not moving) and nothing is relying on the screen size not to change from one X event to another, but I'm sure I'm not testing everything. Are there tricky things I might miss in this area? I'm interested in getting the dynamic addition of monitor edges within the screen area working as well, but I haven't gotten anything to emulate that, and messing with my real video and window manager is a bit of a pain. I seem to remember xrandr support being mentioned as a todo-list item, but I haven't been able to find it on any todo lists. Are there notes or a plan for what exactly that would entail? (Presumably there's no need for fvwm to *set* the xrandr configuration, although the xrandr program seems to be a bit flaky about staying in sync with its documentation and being clear about what combinations don't have any effect.) -Daniel *This .sig left intentionally blank*
