Re: FVWM: thomas adam ill
Think about how good we feel now, knowing you are okay... Seconded. Thirded. Scott. :)
Re: Updates in perllib API
Hi Mikhael, H, my previous reply seems to have gone astray ... most of the old API continues to work. Almost: No method add_defaultErrorHandler in FVWM::Module::Tk=HASH(0x9f8ae10) as guessed from FVWM::Module::Tk::addDefaultErrorHandler at /home/ss/fvwm/cvs.0/install.0/share/fvwm/perllib/FVWM/Module.pm line 684. Anyway, it is better to update user modules. Ok. I updated FvwmTabs to the new API. Scott.
Re: updating the html docs in fvwm-web?
Hi Dominik, I *really* need instruction in the docs/DEVELOPER file if we want the man pages on the web page to be up to date. I don't have the slightest idea what I have to do. Help! H, I did start writing some ... not sure if I finished it. Here's what I had - I'll check/commit it soon (bit busy right at this instant). How to upload HTML documentation to www.fvwm.org export web=$HOME/fvwm/fvwm-web/doc/unstable cd $HOME/fvwm/cvs.1/fvwm/doc for f in $(find . -name '*.html' -o -name '*.png' -o -name '*.jpg') ; do dest=$web/$f if [ ! -f $dest ] ; then echo $dest does not exist in fvwm-web continue fi diff -q $f $dest /dev/null if (( $? != 0 )) ; then cp -p --parents $f $web fi done I'll comment it too! :) Scott. :)
Re: www.fvwm.org web server
Hi Renato, If so, I am just asking if it's possible for the www.fvwm.org web server not to specify/override the encoding. Then, presumably, the web browser would determine the encoding from the HTML header it would render correctly. Wouldn't it be easier to change the html man page encoding instead? This problem is only in the man pages, so I suppose that would be an easier fix.. The HTML pages are automatically generated by xsltproc using the DocBook stylesheets. So we'd have to modify the stylesheets which are effectively a standard. To my mind, the problem is the configuration of the web server (it's valid to generate an ISO-8859-1 encoded web page) - we should be fixing the _cause_ of the problem, if we can. Again, this is not my area of expertise. If someone has a better grasp of what's going on what should be happening, please let me know. Scott.
Re: CVS domivogt: * Check for sed, perl and tbl, needed to build docs.
Hi all, Just got back from holiday ... been reading through the posts but I'm confused, maybe I missed something: On Thu, Aug 16, 2007 at 05:48:05PM -0500, FVWM CVS wrote: CVSROOT: /home/cvs/fvwm Module name: fvwm Changes by: domivogt07/08/16 17:48:05 Modified files: . : ChangeLog configure.ac Log message: * Check for sed, perl and tbl, needed to build docs. Why do we need perl to build the documentation? Scott.
Re: CVS domivogt: * Check for sed, perl and tbl, needed to build docs.
Log message: * Check for sed, perl and tbl, needed to build docs. Why do we need perl to build the documentation? Because of the script doc/util/genAllCommands.pl. Pretend it's not there. Delete it from CVS if it really bothers you (I can keep my own version). I only wrote it to assist me in editing the allCommands.html file on the infrequent occassion when a new command is added to FVWM. At the moment I'm quite unhappy with it: Sure. Like I said previously, if you want to automate this further go right ahead. You'll probably agree, perl may not be the best tool for it though. Then, generation of the documentation shouldn't have to depend on perl. Scott.
Re: CVS griph: * run manpage through tbl on build
Hi Viktor, On Thu, Aug 16, 2007 at 05:05:21PM -0500, FVWM CVS wrote: CVSROOT: /home/cvs/fvwm Module name: fvwm Changes by: griph 07/08/16 17:05:21 Modified files: doc: ChangeLog doc/fvwm : Makefile.am focus.xml Log message: * run manpage through tbl on build * include Focus.xml with path to avoid conflict with focus.xml Is xsltproc case-insensitive? Scott.
Re: CVS griph: * run manpage through tbl on build
Hi Viktor, Is xsltproc case-insensitive? With a case-insencitive filesystem (i.e. on Mac OS X or Cygwin). It complained about recorsion in file Focus.xml, line 16, which really was the file focus.xml. And the generated manpage had four leels of recursion around there and did not include the Focus command. I didn't know that Mac OS X had a case insencitive filesystem until I run into this problem. Huh, I didn't know that about Mac OS X either. Thanks for the explanation. Scott.
Re: broken links in groupedCommands.html
Hi Serge, Links for 'Obsolete or Deprecated' commands in file 'doc/groupedCommands.html' are broken (they missing .html suffix). Attached patch fixes this. Applied. Thanks. Scott. :)
Re: CVS domivogt: * Write fvwm in lower case everywhere
Log message: * Write fvwm in lower case everywhere I disagree with this policy. (sigh, FVWM has been popping up all over the place since the last time I cahanged this).. That's because lower case acronyms are counter-intuitive uncommon. The standard convention is to spell acronyms in capitals. Scott.
Re: html-doc; make distcheck fails
Hi Dominik, I notice you made a change to doc/Makefile.am. Did that fix your problem? I'm surprised if it did. No, I just reformatted it slightly: I was referring to this change: - @ cp $(srcdir)/$@ $@ + @cp $(srcdir)/$@ $(top_builddir)/doc/$@ I notice you've changed it to: %.html: $(srcdir)/$@ test x$(top_srcdir) = x$(top_builddir) || \ cp $(srcdir)/$@ $(top_builddir)/doc/$@ Does this fix your problem? Scott.
Re: CVS broken
Hi Dominik, So, configure isn't correctly disabling Xcursor support? Maybe. Does it still compile or link with libxcursor? Yep: (I copied the make output appended -lXcursor) [EMAIL PROTECTED]:~ cd fvwm/cvs.0/build.2/bin [EMAIL PROTECTED]:~/fvwm/cvs.0/build.2/bin gcc -Wall -Wno-implicit-int -g -O2 -o fvwm-root fvwm-root.o -L../libs -L/usr/X11R6/lib -lfvwm -lXpm -lSM -lICE -lXext -lX11 -lm -lpng -lz -lXcursor [EMAIL PROTECTED]:~/fvwm/cvs.0/build.2/bin Can you put the following output in a bzip2 archive and post it to the list: Find attached. And what are the version numbers of your Xrender and Xcursor libraries? [EMAIL PROTECTED]:~ locate Xrender.so /usr/lib/NX/lib/libXrender.so.1 /usr/lib/NX/lib/libXrender.so.1.2 /usr/X11R6/lib/libXrender.so /usr/X11R6/lib/libXrender.so.1 /usr/X11R6/lib/libXrender.so.1.2.2 [EMAIL PROTECTED]:~ locate Xcursor.so /usr/X11R6/lib/libXcursor.so /usr/X11R6/lib/libXcursor.so.1 /usr/X11R6/lib/libXcursor.so.1.0.2 Scott. blank.tar.bz2 Description: application/bzip-compressed-tar
Re: CVS broken
Hi Dominik, I've fixed the problem that shows up in that file. Does it still happen with current cvs if you build from scratch? Fixed now, thanks. Scott.
Re: CVS broken
On Mon, Jul 16, 2007 at 10:04:26PM +0200, Dominik Vogt wrote: On Tue, Jul 17, 2007 at 12:27:15AM +1000, Scott Smedley wrote: But I'm still getting lots of errors in libs/FRender.c. The fix requires that I link with -lXrender. But which makefile to edit? The build/make system is too complicated for me. :( What does the configure summary say? Ah! With Xcursor support? no: Your libXrender version is too old This is on a SUSE 10.1 system. (doesn't seem that old?) So, configure isn't correctly disabling Xcursor support? Scott.
Re: [patch] svg html doc output
Hi Simon, Are you related to Viktor? Just curious. I've made the SVG rendering options documentation section look much better with the new html output. A few descriptive images really makes a difference. It sure does! Your patch is good. Can I ask you to tidy up the formatting a little? Then I can apply it. +programlisting +lt;svg width=120 height=80 + lt;rect fill=red width=40 height=40 x=0 y=0 / replace lt; with where appropriate. +cmdsynopsis + filename + replaceableimage.svg/replaceable + /filename + literal:/literal Please put the before the newline. Thanks, Scott.
Re: Can't compile current CVS (cp ./index.html index.html)
This seems something trivial, but I can't seem to find the real solution. Ditto. (See the Problems building snap-20070713 thread.) Just out of curiosity, what distro are you using? what version of make? Scott.
Re: CVS broken (Was: PictureImageLoader stuff ...)
But I'm still getting lots of errors in libs/FRender.c. The fix requires that I link with -lXrender. But which makefile to edit? The build/make system is too complicated for me. :( Scott.
Re: [patch] svg html doc output
On Sun, Jul 15, 2007 at 09:52:28PM +0200, Simon Griph wrote: I've made the SVG rendering options documentation section look much better with the new html output. A few descriptive images really makes a difference. Looking good. http://www.fvwm.org/doc/unstable/fvwm/fvwm.man.html#svg_rendering_options Now if we can only stop the www.fvwm.org web server from overriding the character encoding ... anyone? Scott.
function oddity
Hi all, I need confirmation I'm not crazy. This works ok (substitute rxvt for xterm if appropriate): AddToFunc fn I Exec exec rxvt $* fn -e sleep 4 this is ok too: AddToFunc fn3 I Test (x rxvt) Exec exec rxvt $* fn3 -e sleep 4 but this isn't: AddToFunc fn2 Test (x rxvt) + I Exec exec rxvt $* fn2 -e sleep 4 (it starts up an interactive shell, instead of sleeping exiting) Am I missing something? or am I going to have to use the source? Scott.
Re: GPLv3?
Hi Dominik, Should we upgrade to the GPLv3? I'm happy for any of my contributions to be licensed using GPLv3. (not that permission is required with the v2 or any later version clause in the existing GPLv2 licence.) I'd like to see FVWM migrate to GPLv3 soon, allowing a reasonable time (~1 month?) for anyone to voice objections about relicensing their own contributions. (Even though legally we don't need to, it would be polite.) I suggest you forward your GPLv3? post to the fvwm mailing list as well. Scott. :)
Re: differences between the docbook manpage and the old manpage
Hi Victor, * use more precise docbook tags in many places Your changes are good. However, a cursory inspection of the HTML output shows something isn't quite right. There's a strange character in the section headings (after the section number). eg. It looks like 1.,Name instead of 1. Name. I haven't time to delve further at the moment. Also, the use of 2 simplelists in fvwm/initialization.xml doesn't have the desired effect (horizontal whitespace) in HTML output. * tables: - The old manpage use manually written tables where needed, the new use docbook generated tbl code for tables. There is a docbook limitation that the entire table must either be in borders or without them. My opinion: tables look better with only iner borders, but it's not worth hacking docbook to get around the limitation. The most annoying thing (to me) about the table output is that it doesn't make efficient use of horizontal space. I think it's a limitation (bug?) of the tbl system. * examples: - keywords in programlistings are marked up (since they are links) but used to be displayed in plain text in the manpage. My opinion: It's a lot of formatting in an example. Maybe fvwmrefs in programlistings shouldn't add extra markup in manpage output. The change is deliberate, but can be altered. Personally I like it because it conveys extra information. What do other users think? * lists: - list take up more space in docbook. My opinion: case to case basis. Most lists have sort items, so they will never split over multiple lines, so it will just be lots of extra whitespace as a result. I agree there's room for improvement here. But, as it's purely cosmetic, I'm unlikely to address it anytime soon. * sections: - Subsections are typeset withoutupper case in docbook. The old man page used uppercase for both sections and subsections. My opinion: don't care That is a known bug (on my TODO list). I don't think man defaults to a case INsensitive search by default so it should definitely be fixed. (I occassionally use case sensitive searches in man pages.) - Subsubsections and subsubsubsection are typeset as subsections. My opinion: should be fixed Are you referring to indentation? * commands: - used to have their own synapsis on the title line, now on its own line. My opinion: the old way looks better Agreed. But I haven't found a suitable way to get the old look. * missing sections: - The sections AUTO-RAISE, BOOLEAN ARGUMENTS and CONDITIONAL COMMANDS AND RETURN CODES are missing in the docbook man page. My opinion: The sections should be restored, unless a motivation for not including them can be given. AUTO-RAISE It doesn't seem consistent to have extra info about a single module. There's already a description of modules in the Module command section. CONDITIONAL COMMANDS AND RETURN CODES Useless. (IMO of course) BOOLEAN ARGUMENTS I must have overlooked this one. I agree that it should be re-included. (preferably as a _sub_ section?) Scott. :)
creation of images on documentation web page
Hi all, How were the images on the documentation web page created? http://www.fvwm.org/documentation/ I need to create another one for a link to the HTML documentation. Would anyone like to volunteer to create one for me? Using: http://www.fvwm.org/doc/unstable/ Scott. :)
use of navgen in fvwm-web
Hi Uwe, I want to modify an entry in fvwm-web/navgen_write/navigation.inc but there is a comment at the top: // This file is generated automatically by navgen. How do I generate this file? Which file should I edit so that it will add a new entry? Scott. :)
Re: Bug in FvwmForm
As you can see in the picture, for some reason, the text on the Timeout label overlaps the text on the last button, so I think that this might be some kind of overflow H. There is a race condition in the FvwmForm module. A button press can trigger a call to RedrawItem() at the same time RedrawTimeout() is being invoked (every second) by a signal handler. (implemented using the alarm() system call.) Scott.
Re: Test (Compare x [,=,==,=, y) -- patch
This is just intended to work as a simple Test modification, by reusing all what's there, and not to provide any advanced conditional functionality, ... get rid of ugly bash tricks to do something as simple as to decide the size of a panel. The if-syntax patch I wrote some time ago robustly solves these issues ( more). http://members.optusnet.com.au/scottsmedley/tmp/if.20060609.patch http://members.optusnet.com.au/scottsmedley/tmp/if.example It may require trivial changes to apply cleanly against current versions of FVWM. At the time I wrote it, it was agreed this feature should be added in the 2.6 release ... that was 2 years, 9 weeks, 6 days, 21 hours and 7 minutes ago. Given that 2.6 still isn't released, are there any objections to committing it now, in 2.5? Scott.
Re: XML doc
Hi Dominik, * There is lots of markup in the examples which should not be there (commands and command options). It conveys extra information (about what is a builtin command). I consider it an improvement, but I can remove it if you feel strongly about it. * All section headers look the same. For example, the header Command Execution and the sub-headers Module and Function Commands or Delayed Execution of Commands look exactly the same. The sub-headers should be indented. Fixed. * The standard man page section headers are not printed in capitals as they should be (the format of GNU style man pages is standardized), e.g. NAME, SYNOPSIS, DESCRIPTION etc. Partially fixed. * The sections are not justified as they should be. Fixed. * The first line of the man page does not contain the usual information: FVWM(mansection) ... something ... FVWM(mansection) Fixed. * There are some examples with long lines ( 80 characters) or very funny formatting. Generally it looks like long lines broken with \\ are not typeset correctly. Fixed. * There is an inappropriate use of a single backtick in this line: undefine(`include') It's a verbatim copy of what's in the original man page. * A lot of text has been removed from the BUGS section. That's definitely an improvement. * THe section command expansion contains rubbish. I cannot reproduce this. Please let me know if you've still got this problem. Scott. :)
Re: XML doc
Hi Dominik, If you do not want to produce this documentation please use: ./configure --disable-htmldoc As the process take four times longer than building the executables, may I suggest that a) the html pages are not built unless you specifically ask for them, Ok. I will change this soon. b) the new man page stuff is disabled by default. Sorry, I don't understand what you mean. For developers, the XML source files supersede the old fvwm man page. Please make any documentation changes here NOT in the fvwm/fvwm.1.in file. Well, I'd be willing to try that, but I am *not* going to search through *400* files for the contents I want to edit (and all cross references). There *must* be a way to have just one file per man page. I'd like to be able to accomodate, but by having everything in one file we'd lose the ability to have separate HTML pages for each command. IMO, that's probably the most useful feature. See: http://members.optusnet.com.au/~scott.fvwm/allCommands.html It's natural to split up the documentation into smaller files. As an analogy, consider the FVWM source code - we don't have a single fvwm.c source file to make searching easier, but lots of separate source files with grouped functionality. I agree though, splitting up the documentation into multiple files has made searching a little harder. But, as Dan indicates, a few simple 'grep' commands should suffice. What about the other markup mentioned at the top of the man page? Ok. I will expand the doc/README file further to include these. Scott. :)
Re: XML doc
Hi Dan, Just woke up and had to try this... That's the kind of enthusiasm I like! :) When it got to the docs, it started printing this warning: make[3]: Entering directory `/home/dane/src/fvwm/build_fvwm2_5_20/doc/fvwm' Generating authors.html ../../../fvwm2_5_20/doc/fvwm/authors.xml:6: warning: failed to load external entity ../../../fvwm2_5_20/doc/fvwm.ent %myents; ^ Entity: line 1: %myents; For some reason, the new *.in files aren't being parsed. What command did you run? (./configure?) Do you still get this problem if you run utils/configure_dev.sh? I think breaking up the docs into one file per command is great. Grep should deal with finding things well enough. Agreed. Scott. :)
Re: XML doc
Hi Dan, I think the key is that I build from OUTSIDE the source dir. I still get the same problems. You are correct - fixed now. Thanks, Scott. :)
Re: XML doc
Hi Dominik, The current state of the XML documentation prevents me from writing any documentation. As almost everything I do has to be documented, it prevents me to do almost anything. I understand your concerns about the man-page output not being rendered perfectly I'll endeavour to fix them for you ASAP. But, that is just cosmetic. If there's a technical reason why you can't edit the XML documentation please let me know so I can address it. We're not talking about source but documentation. In my eyes having split pages is the one feature in html docs that makes it completely unusable: you can not browse or search it in a sensible way. And it's hell to read. A single page with intra- document links is much more usable. We have this too: http://members.optusnet.com.au/~scott.fvwm/fvwm/fvwm.man.html It's the bold link on the front page - it was the first thing I did. In any case, we're talking about Unix, not windoze. I'm confused. What has this got to do with anything? (Perhaps my confusion comes from not having used Windoze since ~1998.) Scott. :)
cross-referenced FVWM documentation
Hi all, I have been working on converting the FVWM documentation into DocBook format. You can view some preliminary HTML results on-line. http://members.optusnet.com.au/~scott.fvwm/index.html The most interesting links, so far, are: All Commands Grouped Commands Modules FVWM man page Comments/criticism/feedback most welcome. Scott. :)
GnomeShowDesks command?
Hi all, I notice that FVWM has a command called GnomeShowDesks, yet it is not documented in the man page. Is that ok? Scott.
Searching the FVWM mailing lists
Can someone please fix the Google search thingy on this page: http://www.fvwm.org/contact/ It should be using: site:www.mail-archive.com not: site:www.hpc.uh.edu The -inurl specifiers probably need updating too. Scott. :)
ModuleConfig.pm
Hi Mikhael, I tried out your ModuleConfig tracker with FvwmTabs - it works great. Should I expect to get an 'observation' if I dynamically change config parameters? (using FvwmTalk or FvwmCommand) The dynamic values are only propogated after I restart FvwmTabs. Also, you need to s/InitialConfig/DefaultConfig/ in the perl POD at the bottom of ModuleConfig.pm. Thanks! SCoTT. :) -- 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]
