Re: CVS migo: * FvwmButtons: new button option Id
On 25 Aug 2002 22:45:13 -0500, FVWM CVS wrote: Log message: * FvwmButtons: new button option Id * FvwmButtons: new dynamical messages ChangeButton and ExpandButtonVars The old undocumented SendToModule syntax is removed. Instead, use something like: *FvwmButtons: (Id note1, Title 13:30 - Dinner, Icon dinner.xpm) SendToModule FvwmButtons ChangeButton note1 \ Title 18:00 - Go Home, Icon go.xpm You don't need to always define Id, the old-style id (number or +x+y) works as usual. The ExpandButtonVars is intended to expand $title, $icon and similar in the button context, but currently it only expands $bg, $top, $left etc. -SendToModule FvwmButtons ExpandButtonVars note1 \ Exec xmessage The current title: $title, fg: $fg Regards, Mikhael. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS domivogt: * -Wall fix.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/08/26 04:22:48 Modified files: modules: ChangeLog modules/FvwmButtons: dynamic.c Log message: * -Wall fix. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS domivogt: * Fixed typos.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/08/26 06:48:23 Modified files: docs : DEVELOPERS Log message: * Fixed typos. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS domivogt: * Fixed (?) snapshot building.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/08/26 07:00:16 Modified files: docs : DEVELOPERS modules: ChangeLog modules/FvwmButtons: dynamic.c Log message: * Fixed (?) snapshot building. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Problems building snap-20020826
? fvwm-snap-20020523.tar.gz
? fvwm-snap-20020524.tar.gz
P docs/DEVELOPERS
P modules/ChangeLog
P modules/FvwmButtons/dynamic.c
configure.in:423: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:470: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:487: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:674: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:818: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:857: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:872: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:877: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:423: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:470: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:487: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:674: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:818: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:857: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:872: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:877: warning: AC_TRY_RUN called without default to allow cross
compiling
loading cache ./config.cache
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking whether to enable command logging... no
checking whether to enable debugging messages... no
checking whether to enable fancy pixmap titlebars... yes
checking imagepath... /usr/include/X11/bitmaps:/usr/include/X11/pixmaps
checking for gcc... (cached) gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking how to run the C preprocessor... (cached) gcc -E
checking for POSIXized ISC... no
checking for minix/config.h... (cached) no
checking for X... (cached) libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for dnet_ntoa in -ldnet... (cached) no
checking for dnet_ntoa in -ldnet_stub... (cached) no
checking for gethostbyname... (cached) yes
checking for connect... (cached) yes
checking for remove... (cached) yes
checking for shmat... (cached) yes
checking for IceConnectionNumber in -lICE... (cached) yes
checking host system type... i686-pc-linux-gnu
checking whether to enable GNOME window manager hints... yes
checking whether to enable Extended WM Hints Support... yes
checking for SmcOpenConnection in -lSM... yes
checking for XShapeQueryExtension in -lXext... yes
checking for XineramaIsActive in -lXinerama... yes
checking whether to enable Xinerama emulation on one screen (useful only for
developers)... no
checking for XRenderComposite in -lXrender... yes
checking for freetype-config... (cached) no
checking for FreeType - version = 6.1.0... no
*** The freetype-config script installed by FreeType 2 could not be found.
*** If FreeType 2 was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the FT2_CONFIG environment variable to the
*** full path to freetype-config.
checking for XpmReadFileToXpmImage in -lXpm... yes
checking for X11/xpm.h... yes
checking for Xpm 3.4g or better... yes
checking for png_read_info in -lpng... yes
checking for png.h... yes
checking for libpng 1.0.4a or better... yes
checking whether byte ordering is bigendian... (cached) no
checking for rplay_create in -lrplay... no
checking for stroke_init in -lstroke... no
checking with termcap... checking for readline in -lreadline... no
checking with ncurses... checking for readline in -lreadline... yes
checking for readline/history.h... yes
checking for _Xsetlocale in -lX11... (cached) no
checking for XOpenOM in -lX11... (cached) yes
checking for libiconv_open in -liconv... (cached) no
checking for iconv_open... (cached) yes
checking check if second arg of iconv is const... no
checking for nl_langinfo (CODESET)... yes
checking for fribidi-config... no
checking for stdarg.h... (cached) yes
checking for vfprintf... (cached) yes
checking for waitpid... (cached) yes
checking for cpp... (cached) /usr/bin/cpp
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln -s works... (cached) yes
checking whether make sets ${MAKE}... (cached) yes
checking for ranlib... (cached) ranlib
checking for perl... (cached) /usr/local/bin/perl
checking for
Re: CVS domivogt: * Fixed (?) snapshot building.
FC == FVWM CVS fvwm-workers@fvwm.org writes: FC Fixed (?) snapshot building. I tried to push another snapshot but ran into the same error. - J -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
CVS migo: * another attempt to work around a buggy X11/extensions/shape.h
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: migo02/08/26 09:39:29 Modified files: . : ChangeLog NEWS docs : ANNOUNCE modules: ChangeLog modules/FvwmButtons: dynamic.c Log message: * another attempt to work around a buggy X11/extensions/shape.h * NEWS: mention FvwmButtons additions and TitleStyle MultiPixmap (post-factum) * added ANNOUNCE for 2.5.3 (post-factum) -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: CVS domivogt: * Fixed (?) snapshot building.
On 26 Aug 2002 09:29:28 -0500, Jason L Tibbitts III wrote: FC == FVWM CVS fvwm-workers@fvwm.org writes: FC Fixed (?) snapshot building. I tried to push another snapshot but ran into the same error. Actually, the errors are not the same. Can you make another run? Regards, Mikhael. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Problems building snap-20020826
? fvwm-snap-20020523.tar.gz
? fvwm-snap-20020524.tar.gz
P ChangeLog
P NEWS
P docs/ANNOUNCE
P modules/ChangeLog
P modules/FvwmButtons/dynamic.c
configure.in:423: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:470: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:487: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:674: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:818: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:857: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:872: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:877: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:423: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:470: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:487: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:674: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:818: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:857: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:872: warning: AC_TRY_RUN called without default to allow cross
compiling
configure.in:877: warning: AC_TRY_RUN called without default to allow cross
compiling
loading cache ./config.cache
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking whether to enable command logging... no
checking whether to enable debugging messages... no
checking whether to enable fancy pixmap titlebars... yes
checking imagepath... /usr/include/X11/bitmaps:/usr/include/X11/pixmaps
checking for gcc... (cached) gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking how to run the C preprocessor... (cached) gcc -E
checking for POSIXized ISC... no
checking for minix/config.h... (cached) no
checking for X... (cached) libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for dnet_ntoa in -ldnet... (cached) no
checking for dnet_ntoa in -ldnet_stub... (cached) no
checking for gethostbyname... (cached) yes
checking for connect... (cached) yes
checking for remove... (cached) yes
checking for shmat... (cached) yes
checking for IceConnectionNumber in -lICE... (cached) yes
checking host system type... i686-pc-linux-gnu
checking whether to enable GNOME window manager hints... yes
checking whether to enable Extended WM Hints Support... yes
checking for SmcOpenConnection in -lSM... yes
checking for XShapeQueryExtension in -lXext... yes
checking for XineramaIsActive in -lXinerama... yes
checking whether to enable Xinerama emulation on one screen (useful only for
developers)... no
checking for XRenderComposite in -lXrender... yes
checking for freetype-config... (cached) no
checking for FreeType - version = 6.1.0... no
*** The freetype-config script installed by FreeType 2 could not be found.
*** If FreeType 2 was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the FT2_CONFIG environment variable to the
*** full path to freetype-config.
checking for XpmReadFileToXpmImage in -lXpm... yes
checking for X11/xpm.h... yes
checking for Xpm 3.4g or better... yes
checking for png_read_info in -lpng... yes
checking for png.h... yes
checking for libpng 1.0.4a or better... yes
checking whether byte ordering is bigendian... (cached) no
checking for rplay_create in -lrplay... no
checking for stroke_init in -lstroke... no
checking with termcap... checking for readline in -lreadline... no
checking with ncurses... checking for readline in -lreadline... yes
checking for readline/history.h... yes
checking for _Xsetlocale in -lX11... (cached) no
checking for XOpenOM in -lX11... (cached) yes
checking for libiconv_open in -liconv... (cached) no
checking for iconv_open... (cached) yes
checking check if second arg of iconv is const... no
checking for nl_langinfo (CODESET)... yes
checking for fribidi-config... no
checking for stdarg.h... (cached) yes
checking for vfprintf... (cached) yes
checking for waitpid... (cached) yes
checking for cpp... (cached) /usr/bin/cpp
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln -s works... (cached) yes
checking whether make sets ${MAKE}... (cached) yes
checking for ranlib... (cached) ranlib
checking for perl... (cached)
CVS migo: * add more includes to satisfy X11/extensions/shape.h
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: migo02/08/26 11:22:46 Modified files: modules/FvwmButtons: dynamic.c Log message: * add more includes to satisfy X11/extensions/shape.h -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: Problems building snap-20020826
BTW, the machine I'm building on runs Red Hat 7.1, and has XFree86 4.0.3 installed. I know it's old but I expect that others would run into the same issue. - J -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: Multipixel titlebar
HI, Last weekend I tried the last snapshot since I was curious about what was happening, what is new. And what a surprise! Multipixel titlebar is working again!!! Kudos to Suzanne (who wrote the first patch) and the fvwm developers that put the patch in the development tree. BTW I think this deserve a note in the Changelog :-) -- Christian Lyra POP-PR - RNP The master programmer moves from program to program without fear. No change in management can harm him. He will not be fired, even if the project is cancelled. Why is this? He is filled with Tao. The Tao Of Programing -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: .fvwm2rc syntax guide?
On Sun, Aug 25, 2002 at 08:29:50PM -0400, Dan Espen wrote: Are you aware that you can start fvwm with no config file at all, press F1 or any mouse button on the root window and fvwm will offer to create a few different configurations for you? yes, it is mentioned in the man but it appears at line 365 in a very modest 2 line sentence (context: .fvwm2rc). it is repeated in a somewhat more extended version at ~1100 (Built in KM Bindings). while I agree that structurally these are apropriate locations, i believe not many newbies can spot and pick up the message (i personally missed them when first read/ scanned through the manual. mind you it is 8000+ lines of heavy text). I think it would be helpful to - to put a To the Impatient setion at the very begining of the man with this info - mention this also in one of the INSTALL and/or README files (e.g. README.sysrc). imre -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: .fvwm2rc syntax guide?
--- Imre Vida [EMAIL PROTECTED] a écrit : On Sun, Aug 25, 2002 at 08:29:50PM -0400, Dan Espen wrote: Are you aware that you can start fvwm with no config file at all, press F1 or any mouse button on the root window and fvwm will offer to create a few different configurations for you? yes, it is mentioned in the man but it appears at line 365 in a very modest 2 line sentence (context: .fvwm2rc). it is repeated in a somewhat more extended version at ~1100 (Built in KM Bindings). while I agree that structurally these are apropriate locations, i believe not many newbies can spot and pick up the message (i personally missed them when first read/ scanned through the manual. mind you it is 8000+ lines of heavy text). I think it would be helpful to - to put a To the Impatient setion at the very begining of the man with this info - mention this also in one of the INSTALL and/or README files (e.g. README.sysrc). Welcome to *nix I think the man page should remain as it is. The man page format is standard. Man page _is_ a reference. Man page _is not_ a tutorial. Will never be. If you are impatient and newbie in the same time the chances of screwing things up are big, so my advice is to start with a configuration file that _works_ and modify it to suit your needs, I think somebody wrote a tutorial for fvwm. Use it. Good luck imre Calin ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: Restricted region for fvwm?
Hi, is it possible to restrict the region, where FVWM places new windows and to which windows are maximised (in order to save some space at the borders for the GNOME panels)? Thanks in advance Matthias -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: Hide PagerDisplay in FvwmPager
Short version: I'd like FvwmPager to _not_ draw its own PagerDisplay window in the pager view. Is there a way to achieve this? I'm using fvwm 2.4.8. from the Debian distribution. Long version: I use a large grid of desks and like to see them all at once in the pager when navigating between desks, hence the pager view is quite big, practically fuillscreen. Normally, I have the PagerDisplay iconified, effectively hidden since I don't display icons, and deiconify it (and make it topmost) on demand via a hotkey for navigation. I then navigate using Alt+cursor-keys, the PagerDisplay being sticky hence remaining on-screen. Unfortunately, in the pager view, the PagerDisplay window then always obscures the current desk. This is a bit annoying, somewhat as if the text cursor in a text editor would always obscure the current character under the cursor. Since there isn't much use anyway for the PagerDisplay window to be present in the pager view, I'd like to get rid of it there. -- Niklas Matthies -- Good judgement comes from experience, and experience comes from bad judgement. -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Restricted region for fvwm?
On 26 Aug 2002 21:58:44 +0200, Matthias Burghardt wrote: is it possible to restrict the region, where FVWM places new windows and to which windows are maximised (in order to save some space at the borders for the GNOME panels)? Yes, in 2.5.x see the EWMHBaseStrut description in the man page. But there maybe temporary problems with it when MinOverlapPlacement used. I don't have the latest GNOME and KDE, but I would think their panels and maybe other apps should have options for window managers to reserve them the desktop space using EWMH hints. In this case EWMHBaseStrut is not needed, since FVWM by default respects these hints. Regards, Mikhael. -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Hide PagerDisplay in FvwmPager
On 26 Aug 2002 22:47:03 +0200, Niklas Matthies wrote: Short version: I'd like FvwmPager to _not_ draw its own PagerDisplay window in the pager view. Is there a way to achieve this? I'm using fvwm 2.4.8. from the Debian distribution. Long version: I use a large grid of desks and like to see them all at once in the pager when navigating between desks, hence the pager view is quite big, practically fuillscreen. Normally, I have the PagerDisplay iconified, effectively hidden since I don't display icons, and deiconify it (and make it topmost) on demand via a hotkey for navigation. I then navigate using Alt+cursor-keys, the PagerDisplay being sticky hence remaining on-screen. Unfortunately, in the pager view, the PagerDisplay window then always obscures the current desk. This is a bit annoying, somewhat as if the text cursor in a text editor would always obscure the current character under the cursor. Since there isn't much use anyway for the PagerDisplay window to be present in the pager view, I'd like to get rid of it there. You can't do this in 2.4.8. In 2.5.x, use: *FvwmPager: UseSkipList Then all WindowListSkip windows are not shown in the pager, like: Style FvwmPager WindowListSkip Regards, Mikhael. -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: .fvwm2rc syntax guide?
On Sun, Aug 25, 2002 at 10:20:47PM +, Mikhael Goikhman wrote: On 25 Aug 2002 16:18:42 -0500, Len Philpot wrote: 2. When I configure a Popup StartMenu, is there a way to accurately control where it appears on screen, in regard to the Start button? If I understood MenuStyle a bit better, maybe the answer is there (PopupOffset, or whatever it's called)...? Yes, you may do this accurately in 2.5.1+, scan NEWS file. In 2.4.x, you may do this too using Rectangle or Mouse hint (there are examples in fvwm-themes), but not as accurately as in 2.5.x. I'm using FvwmTaskBar, with no RootMenu configured, but rather all the same entries on the StartMenu. It pops up just fine when I click the task bar button, but the position is relative to the mouse pointer, not to the task bar. That's what I'm trying to achieve. I'm currently running 2.4.6, BTW (latest RPM for RedHat 7.x I could locate in a quick search). Here's what I've tried to pin down the location: AddToMenu StartMenu Root x y SelectInPlace ...where x and y are various offsets. I would expect x to be 0 and y to basically be height_of_root_window - height_of_menu - height_of_taskbar. In this intance, referencing the lower left corner of the menu would have been more convenient and less prone to change, although menu's typically _do_ drop down, so I see the value in the upperleft reference point. Trouble is, it doesn't seem to make any difference at all what I put there - Nothing ever changes. My MenuStyle is : MenuStyle * Foreground black, Background grey70, Greyed grey90,\ HilightBack grey60, ActiveFore black, Hilight3DThickness -1, \ font -adobe-helvetica-medium-r-*-*-12-*-*-*-*-*-*-*, Animation,\ PopupDelay 55, PopdownDelay 5, TitleWarpOff, SeparatorsLong,\ TrianglesRelief, PopupOffset 0 95 ...with the exception that it's actually all on one line. It works as expected, but is something there interfering? What exactly annoys you about menus and windows? Provide configurations. It's just that I prefer the mouse pointer to stay where it is when I click it. In general, I'm not a big fan of anything in the UI responding or taking any kind of action without an explicit instruction on the part of the user. I'd rather not even have the menu selection move with the mouse without the button being down, given a choice, and I don't care for highlighting icons that change as you mouseover them (so popular in Windows, Gnome, KDE, etc.), but that's just my personal GUI preferences. I like intefaces that are totally static until acted upon by the user. Once again, just my preference. Even under Windows, I don't turn on the option to jump to the active control. With those sort of things active, I tend to spend more time looking for the mouse pointer. The way I have it now, I have no warping happening, at least none I've noticed, so I'm happy with that. Let me clarify something - I may have inadvertently come across as critical of fvwm and the way things are done. That was not intentional, but rather just the product of frustration (indeed, I even stated such in one post). I usually never write when in such a state, as I always regret it later. I'll state again: I like what I'm learning of fvwm and I'm appreciative of the help; it's just that the learning process is somewhat painful at times (at least, it smarts here and there...). -- +-+ | Len Philpothttp://philpot.org/ | | [EMAIL PROTECTED] [EMAIL PROTECTED] (alt) | +-+ -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
