Re: CVS griph: * run manpage through tbl on build

2007-08-20 Thread Scott Smedley
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: CVS griph: * run manpage through tbl on build

2007-08-20 Thread Viktor Griph
On 8/21/07, Scott Smedley <[EMAIL PROTECTED]> wrote:
> 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?
>

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.

/Viktor



Re: CVS griph: * run manpage through tbl on build

2007-08-20 Thread Scott Smedley
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 domivogt: * Check for sed, perl and tbl, needed to build docs.

2007-08-20 Thread Scott Smedley
> > > 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 domivogt: * Check for sed, perl and tbl, needed to build docs.

2007-08-20 Thread Dominik Vogt
On Tue, Aug 21, 2007 at 10:07:31AM +1000, Scott Smedley wrote:
> 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?

Because of the script doc/util/genAllCommands.pl.  At the moment
I'm quite unhappy with it:

 * It's the only part of fvwm that requires perl (except the perl
   library, of course).
 * It's not run automatically.
 * It requires yet another file with special syntax that lists all
   commands.

Ciao

Dominik ^_^  ^_^

 --
Dominik Vogt, dominik.vogt (at) gmx.de


signature.asc
Description: Digital signature


Re: CVS domivogt: * Check for sed, perl and tbl, needed to build docs.

2007-08-20 Thread Scott Smedley
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.



Cygwin-bug#20070820T0621: fvwm Perl -cw warning

2007-08-20 Thread Jari Aalto
Package: fvwm
Version: 2.5.21
Status: 
Severity: minor

Hi,

Here are some porting notes, in case you can take care of them in next
release:

--   Checking perl -cw fvwm-convert-2.4
--   [WARN] fvwm-convert-2.4: report compile warnings to upstream author
Name "main::getline_ok" used only once: possible typo at 
.inst/usr/bin/fvwm-convert-2.4 line 350.


It's customary to start the POD sections with "=pod", not just "=head1".

--   [NOTE] =pod tag is missing, but POD found: 
.inst/usr/bin/fvwm-menu-directory
--   Checking perl -cw fvwm-menu-headlines
--   [NOTE] =pod tag is missing, but POD found: 
.inst/usr/bin/fvwm-menu-headlines
--   Checking perl -cw fvwm-menu-xlock
--   [NOTE] =pod tag is missing, but POD found: .inst/usr/bin/fvwm-menu-xlock
--   Checking perl -cw fvwm-perllib

Jari


-- System Information
Release: 1.5.24 api 0.156 cvs cr-0x5f1
Kernel: 1.5.24 api 0.156 cvs cr-0x5f1
Locale: 

-- Other package information
Info-Pkg-devel-tools: gcc 3.4.4-3, make 3.81-1, libtool 1.5b-2, automake 2-1
Info-Pkg-lang: perl 5.8.8-4, python 2.5.1-2, ruby 1.8.6-1

-- Environment information
CYGWIN: server




Re: Rendering error: http://fvwm.org/donations.php

2007-08-20 Thread Thomas Adam
On Mon, Aug 20, 2007 at 12:40:48PM +0100, seventh guardian wrote:
> On 8/20/07, Thomas Adam <[EMAIL PROTECTED]> wrote:
> > This page is riddled with '//' characters all over the place.  The
> > page source indicates that a block paragraph was meant to be commented
> > out in php (I'm assuming) but instead is being printed literally.
> >
> > This probably wants to be fixed.  :)
> 
> Hopefully fixed :) Thanks
> 
> ..but I can't seem to get the updated page. Probably a caching problem
> from my ISP.. Can you confirm the fix?

Yes, fixed.  The information that's currently there might want expanding
at some point though, even if it is just to say, in addition to what's
there:  "If there's a feature you really would want to see implemented, a
donation might be considered as an extra incentive." or words to that
effect.

-- Thomas Adam



Re: Rendering error: http://fvwm.org/donations.php

2007-08-20 Thread seventh guardian
On 8/20/07, Thomas Adam <[EMAIL PROTECTED]> wrote:
> This page is riddled with '//' characters all over the place.  The
> page source indicates that a block paragraph was meant to be commented
> out in php (I'm assuming) but instead is being printed literally.
>
> This probably wants to be fixed.  :)

Hopefully fixed :) Thanks

..but I can't seem to get the updated page. Probably a caching problem
from my ISP.. Can you confirm the fix?

Cheers,
  Renato



CVS renato fvwm-web: fixed broken php comments within html code

2007-08-20 Thread FVWM CVS
CVSROOT:/home/cvs/fvwm
Module name:fvwm-web
Changes by: renato  07/08/20 06:38:18

Modified files:
.  : ChangeLog donations.php 

Log message:
fixed broken php comments within html code