Re: New 2.5.22 release?

2007-08-31 Thread Viktor Griph
On 8/28/07, Dominik Vogt [EMAIL PROTECTED] wrote:
 On Tue, Aug 28, 2007 at 01:57:22PM +0100, seventh guardian wrote:
  On 8/28/07, Dominik Vogt [EMAIL PROTECTED] wrote:
   On Tue, Aug 21, 2007 at 11:34:55AM +0200, Dominik Vogt wrote:
By the way, there's another issue with the build process:
   
 * The documentation has a build error when building on a multi
   core machine with -j 2.
   
I think there are some dependencies missing.
  
   Fixed.  Multiple targets were using the same temporary files.  I
   think we can release 2.5.22 now.  Any volunteers?
 
  Hum I guess I can do it this time.. But I need to do it slowly :)

 That's the best way to do it anyway :-)

Yes, hold it for a little longer. I want to investigate bug #4405.

I think it's crashing on windowlist.c:753 (If I follow the diffs from
version 2.5.21 correctly).  Which would mean that wthe window list
contains a NULL window. I want to try to reproduce it using the
supplied minimal config before you release anything.

/Viktor



Re: New 2.5.22 release?

2007-08-30 Thread seventh guardian
On 8/30/07, seventh guardian [EMAIL PROTECTED] wrote:
 On 8/30/07, Viktor Griph [EMAIL PROTECTED] wrote:
  On Thu, 30 Aug 2007, seventh guardian wrote:
   On 8/30/07, seventh guardian [EMAIL PROTECTED] wrote:
   On 8/29/07, seventh guardian [EMAIL PROTECTED] wrote:
   On 8/29/07, Viktor Griph [EMAIL PROTECTED] wrote:
   On 8/29/07, seventh guardian [EMAIL PROTECTED] wrote:
   On 8/29/07, Viktor Griph [EMAIL PROTECTED] wrote:
   On 8/29/07, seventh guardian [EMAIL PROTECTED] wrote:
   Ok, everything is done except putting the tarballs in the ftp dir (I
   seem to have forgotten my password.. already emailed Jason about
   this).
  
   there is no password for the incoming folder.
  
   oh.. but it doesn't work with username renato and pass ..
  
   $ ftp ftp.fvwm.org
   Connected to ftp.fvwm.org (129.7.128.20).
   220 UH Math FTP server
   Name (ftp.fvwm.org:renato):
   530 Please login with USER and PASS.
   SSL not available
   331 Please specify the password.
   Password:
   530 Login incorrect.
   Login failed.
   ftp 221 Goodbye.
  
   or for any other username (tried guest and fvwm)
  
   use anonymous
  
  
   Done! Thanks!!
  
   Now I seem to have some trouble logging into cvs.. I'll check again 
   later...
  
   It must have been some network problem at my uni.. At home it worked 
   fine.
  
   All done, 2.6.22 is released :)
  
 
  Did you notify Jason of the upload?

 I did. But he still hasn't replied to my password change request..

And the download link is still dead.. bummer... Maybe he's on holiday..

Is he the only person who can do it?

  Renato



Re: New 2.5.22 release?

2007-08-30 Thread Dan Espen
seventh guardian [EMAIL PROTECTED] writes:
 And the download link is still dead.. bummer... Maybe he's on holiday..

Very likely, it's pretty hot in Houston this time of year.

 Is he the only person who can do it?

Jason is at the University of Houston and has donated his time to
Fvwm since Sept 1995.  I've never seen anyone else from the university
step in when he was away, so my guess is we have to be patient.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: New 2.5.22 release?

2007-08-29 Thread Viktor Griph
On 8/29/07, seventh guardian [EMAIL PROTECTED] wrote:
 Ok, everything is done except putting the tarballs in the ftp dir (I
 seem to have forgotten my password.. already emailed Jason about
 this).

there is no password for the incoming folder.

/Viktor



Re: New 2.5.22 release?

2007-08-29 Thread seventh guardian
On 8/29/07, Viktor Griph [EMAIL PROTECTED] wrote:
 On 8/29/07, seventh guardian [EMAIL PROTECTED] wrote:
  Ok, everything is done except putting the tarballs in the ftp dir (I
  seem to have forgotten my password.. already emailed Jason about
  this).

 there is no password for the incoming folder.

oh.. but it doesn't work with username renato and pass ..

$ ftp ftp.fvwm.org
Connected to ftp.fvwm.org (129.7.128.20).
220 UH Math FTP server
Name (ftp.fvwm.org:renato):
530 Please login with USER and PASS.
SSL not available
331 Please specify the password.
Password:
530 Login incorrect.
Login failed.
ftp 221 Goodbye.

or for any other username (tried guest and fvwm)

If I specify the full path I get this:

$ ftp ftp.fvwm.org/pub/incoming/fvwm
ftp: ftp.fvwm.org/pub/incoming/fvwm: Name or service not known
ftp

Thanks!
  Renato



Re: New 2.5.22 release?

2007-08-29 Thread Viktor Griph
On 8/29/07, seventh guardian [EMAIL PROTECTED] wrote:
 On 8/29/07, Viktor Griph [EMAIL PROTECTED] wrote:
  On 8/29/07, seventh guardian [EMAIL PROTECTED] wrote:
   Ok, everything is done except putting the tarballs in the ftp dir (I
   seem to have forgotten my password.. already emailed Jason about
   this).
 
  there is no password for the incoming folder.

 oh.. but it doesn't work with username renato and pass ..

 $ ftp ftp.fvwm.org
 Connected to ftp.fvwm.org (129.7.128.20).
 220 UH Math FTP server
 Name (ftp.fvwm.org:renato):
 530 Please login with USER and PASS.
 SSL not available
 331 Please specify the password.
 Password:
 530 Login incorrect.
 Login failed.
 ftp 221 Goodbye.

 or for any other username (tried guest and fvwm)

use anonymous

/Viktor



Re: New 2.5.22 release?

2007-08-28 Thread Dominik Vogt
On Tue, Aug 21, 2007 at 11:34:55AM +0200, Dominik Vogt wrote:
 By the way, there's another issue with the build process:
 
  * The documentation has a build error when building on a multi
core machine with -j 2.
 
 I think there are some dependencies missing.

Fixed.  Multiple targets were using the same temporary files.  I
think we can release 2.5.22 now.  Any volunteers?

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-28 Thread seventh guardian
On 8/28/07, Dominik Vogt [EMAIL PROTECTED] wrote:
 On Tue, Aug 21, 2007 at 11:34:55AM +0200, Dominik Vogt wrote:
  By the way, there's another issue with the build process:
 
   * The documentation has a build error when building on a multi
 core machine with -j 2.
 
  I think there are some dependencies missing.

 Fixed.  Multiple targets were using the same temporary files.  I
 think we can release 2.5.22 now.  Any volunteers?

Hum I guess I can do it this time.. But I need to do it slowly :)

By the way, can you please read the header of the ANNOUNCE to see if it's ok?

Cheers,
  Renato



Re: New 2.5.22 release?

2007-08-28 Thread Dominik Vogt
On Tue, Aug 28, 2007 at 01:57:22PM +0100, seventh guardian wrote:
 On 8/28/07, Dominik Vogt [EMAIL PROTECTED] wrote:
  On Tue, Aug 21, 2007 at 11:34:55AM +0200, Dominik Vogt wrote:
   By the way, there's another issue with the build process:
  
* The documentation has a build error when building on a multi
  core machine with -j 2.
  
   I think there are some dependencies missing.
 
  Fixed.  Multiple targets were using the same temporary files.  I
  think we can release 2.5.22 now.  Any volunteers?
 
 Hum I guess I can do it this time.. But I need to do it slowly :)

That's the best way to do it anyway :-)

 By the way, can you please read the header of the ANNOUNCE to
 see if it's ok?

I think it's okay.

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-21 Thread Dominik Vogt
On Sun, Aug 19, 2007 at 11:52:09PM +0200, Viktor Griph wrote:
 On 8/19/07, Dominik Vogt [EMAIL PROTECTED] wrote:
  On Sun, Aug 19, 2007 at 12:42:15AM +0200, Dominik Vogt wrote:
   On Sat, Aug 18, 2007 at 10:09:46PM +0200, Viktor Griph wrote:
On 8/18/07, Dominik Vogt [EMAIL PROTECTED] wrote:
 Can you eliminate the use of tables then?  I think we just have a
 couple of them.
 
  Allright, with your latest commit there is one table left in
  doc/commands/Menu.xml and four more tables in
  doc/modules/FvwmTabs.xml.
 
 The one in Menu.ml is now replaced, as is the keybindings in
 FvwmTabs.xml. The other three tables inFvwmTabs.xml are slightly more
 complicated. Also FvwmTabs.1 is not set to be installed (or even
 built) from the xml source. The old FvwmTabs.1 man page will be
 installed with the current setup.

The man page is not built and istalled, but the HTML documentation
is (see doc/commands/Makefile.am).

By the way, there's another issue with the build process:

 * The documentation has a build error when building on a multi
   core machine with -j 2.

I think there are some dependencies missing.

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-19 Thread Dominik Vogt
On Sun, Aug 19, 2007 at 12:42:15AM +0200, Dominik Vogt wrote:
 On Sat, Aug 18, 2007 at 10:09:46PM +0200, Viktor Griph wrote:
  On 8/18/07, Dominik Vogt [EMAIL PROTECTED] wrote:
   Can you eliminate the use of tables then?  I think we just have a
   couple of them.

Allright, with your latest commit there is one table left in
doc/commands/Menu.xml and four more tables in
doc/modules/FvwmTabs.xml.

Also, some acronyms use arconym ... /acronym and some use
emphasis remap='SM' ... /emphasis.  The old man page had two
uses of .SM: Acronyms and key names.  But cleaning this up is not
necessary before the release.

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-19 Thread Viktor Griph
On 8/19/07, Dominik Vogt [EMAIL PROTECTED] wrote:
 On Sun, Aug 19, 2007 at 12:42:15AM +0200, Dominik Vogt wrote:
  On Sat, Aug 18, 2007 at 10:09:46PM +0200, Viktor Griph wrote:
   On 8/18/07, Dominik Vogt [EMAIL PROTECTED] wrote:
Can you eliminate the use of tables then?  I think we just have a
couple of them.

 Allright, with your latest commit there is one table left in
 doc/commands/Menu.xml and four more tables in
 doc/modules/FvwmTabs.xml.

The one in Menu.ml is now replaced, as is the keybindings in
FvwmTabs.xml. The other three tables inFvwmTabs.xml are slightly more
complicated. Also FvwmTabs.1 is not set to be installed (or even
built) from the xml source. The old FvwmTabs.1 man page will be
installed with the current setup.

 Also, some acronyms use arconym ... /acronym and some use
 emphasis remap='SM' ... /emphasis.  The old man page had two
 uses of .SM: Acronyms and key names.  But cleaning this up is not
 necessary before the release.

I think there are more of the imila stuff out there. I've been
changeing countless emphasis tags into more specific tags, and they
never seem to get to an end.

/Viktor



Re: New 2.5.22 release?

2007-08-18 Thread Dominik Vogt
On Fri, Aug 17, 2007 at 06:13:49PM +0200, Viktor Griph wrote:
 On Fri, 17 Aug 2007, Dominik Vogt wrote:
 
 On Fri, Aug 17, 2007 at 05:26:30PM +0200, Viktor Griph wrote:
 On Fri, 17 Aug 2007, Dominik Vogt wrote:
 Yes.  I'm now looking at the issues brought up by requiring sed,
 perl and tbl for building the docs.
 
 So, is everything ready for release?
 
 And is it really helpful to have tables in the man page?  What's
 the benefit of
 
 Other than the table with visuals and depth info I  don't really see any 
 use for them. I've been changing informaltable to variablelist in 
 several places already.
 
 
+--++
|  Formatting Directive| Description|
+--++
|%l, %c  %r   | Insert the next item   |
|  | label.  Up to three labels |
|  | can be used.  The item |
|  | column is left-aligned |
|  | (%l), centered (%c) or |
|  | right-aligned (%r).|
+--++
|%i| Inserts the mini icon. |
 
 over
 
%l, %c, %r
Insert the next item label.  Up to three labels can be
used.  The item column is left-aligned (%l), centered
(%c) or right-aligned (%r).
%i
Inserts the mini icon.
 
 I find the table harder to read, but t's easier to find an entry
 you are looking for.  It is also very uncommon to have man pages
 with ASCII tables.
 
 I also find the variablelist better than tables for describing meaning of 
 certain directives. They use the space more efficient and they don't have 
 an ugly frame.

Can you eliminate the use of tables then?  I think we just have a
couple of them.

 Speaking of the depth/visual table: Sholud it really read
 
   Note that if you use a private color map (i.e., fvwm is started
   with the -C or the -I options), then others defaults are used.
^^^
 ? I'm not a master of Engish grammar, but that s looks bad to me.

That's a typo.

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-18 Thread Viktor Griph
On 8/18/07, Dominik Vogt [EMAIL PROTECTED] wrote:
 On Fri, Aug 17, 2007 at 06:13:49PM +0200, Viktor Griph wrote:
  On Fri, 17 Aug 2007, Dominik Vogt wrote:
 
  On Fri, Aug 17, 2007 at 05:26:30PM +0200, Viktor Griph wrote:
  On Fri, 17 Aug 2007, Dominik Vogt wrote:
  Yes.  I'm now looking at the issues brought up by requiring sed,
  perl and tbl for building the docs.
  
  So, is everything ready for release?
  
  And is it really helpful to have tables in the man page?  What's
  the benefit of
 
  Other than the table with visuals and depth info I  don't really see any
  use for them. I've been changing informaltable to variablelist in
  several places already.
 
  
 +--++
 |  Formatting Directive| Description|
 +--++
 |%l, %c  %r   | Insert the next item   |
 |  | label.  Up to three labels |
 |  | can be used.  The item |
 |  | column is left-aligned |
 |  | (%l), centered (%c) or |
 |  | right-aligned (%r).|
 +--++
 |%i| Inserts the mini icon. |
  
  over
  
 %l, %c, %r
 Insert the next item label.  Up to three labels can be
 used.  The item column is left-aligned (%l), centered
 (%c) or right-aligned (%r).
 %i
 Inserts the mini icon.
  
  I find the table harder to read, but t's easier to find an entry
  you are looking for.  It is also very uncommon to have man pages
  with ASCII tables.
 
  I also find the variablelist better than tables for describing meaning of
  certain directives. They use the space more efficient and they don't have
  an ugly frame.

 Can you eliminate the use of tables then?  I think we just have a
 couple of them.

The only remaining table it the one in the description of the
color-limit option. That is a legimate table. I'm not sure exactly how
to eliminate it. (Thst'd the only tsble that existed in the old man
page.)

/Viktor



Re: New 2.5.22 release?

2007-08-18 Thread Dominik Vogt
On Sat, Aug 18, 2007 at 10:09:46PM +0200, Viktor Griph wrote:
 On 8/18/07, Dominik Vogt [EMAIL PROTECTED] wrote:
  Can you eliminate the use of tables then?  I think we just have a
  couple of them.
 
 The only remaining table it the one in the description of the
 color-limit option. That is a legimate table. I'm not sure exactly how
 to eliminate it. (Thst'd the only tsble that existed in the old man
 page.)

Hm, it could be written like this:

  XFree-4.3 or better pre-allocate only 85  colors.   If  no pre-
  allocated palette is auto detected the defaults are as follow:

  Display depth 8 (256 colors)

  PseudoColor: 68 (4x4x4 color cube + 4 grey)
  GrayScale:   64 regular grey
  DirectColor: 32 (3x3x3 color cube + 5 grey)

  Display depth 4 (16 colors)

  PseudoColor: 10 (2x2x2 color cube + 2 grey)
  GrayScale:8 regular grey
  DirectColor: 10 (2x2x2 color cube + 2 grey)

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-17 Thread Dominik Vogt
On Fri, Aug 17, 2007 at 05:26:30PM +0200, Viktor Griph wrote:
 On Fri, 17 Aug 2007, Dominik Vogt wrote:
 Yes.  I'm now looking at the issues brought up by requiring sed,
 perl and tbl for building the docs.
 
 So, is everything ready for release?

And is it really helpful to have tables in the man page?  What's
the benefit of

+--++
|  Formatting Directive| Description|
+--++
|%l, %c  %r   | Insert the next item   |
|  | label.  Up to three labels |
|  | can be used.  The item |
|  | column is left-aligned |
|  | (%l), centered (%c) or |
|  | right-aligned (%r).|
+--++ 
|%i| Inserts the mini icon. | 

over

%l, %c, %r
Insert the next item label.  Up to three labels can be
used.  The item column is left-aligned (%l), centered
(%c) or right-aligned (%r).
%i
Inserts the mini icon.

I find the table harder to read, but t's easier to find an entry
you are looking for.  It is also very uncommon to have man pages
with ASCII tables.

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-17 Thread Viktor Griph
On 8/17/07, Dominik Vogt [EMAIL PROTECTED] wrote:

   * Single quotes are written ' not \'
   * A line must not begin with a single quote

Both these fixed.

 Has this been doen?

  * The boolean arguments section is still missing from the new
manpage.


Yes, booleanArgs.xml is put there. Maybe we should crosslink all
boolean arguments to commands to it in the html output, but that can
wait.

Shall the ItemFormat and CursorStyle context tables be changed to
variable lists?

/Viktor



Re: New 2.5.22 release?

2007-08-17 Thread Thomas Adam
On Fri, Aug 17, 2007 at 12:42:50AM +0200, Viktor Griph wrote:
 On Fri, 17 Aug 2007, Dominik Vogt wrote:

 On Thu, Aug 16, 2007 at 10:13:19PM +0200, Viktor Griph wrote:
 On Thu, 16 Aug 2007, Viktor Griph wrote:
 On Thu, 16 Aug 2007, Dominik Vogt wrote:
 Most important: the generated man page is still broken.  For
 example:


 allbox tab(:); lB lB lB.  T{   T}:T{ depth 8 (256 colors) T}:T{
 depth 4 (16 colors) T} l l l l l l l l l.  T{ PseudoColor T}:T{ 68
 (4 cc + 4 grey) T}:T{ 10 (2 cc + 2 grey) T} T{ GrayScale T}:T{ 64
 regular grey T}:T{ 8 regular grey T} T{ DirectColor T}:T{ 32 (3 cc
 + 5 grey) T}:T{ 10 (2 cc + 2 grey) T}

 There are three other places with similar broken formatting in fvwm.1.

 I'll look into it if you can give me some hint on how to fix automake 
 for
 the doc directory on my macbook.

 Does that formatting show up in your processed output?

 Yes, that's from the formatted man page.

 It is formatting
 for tbl(1), which seems to be used by docbook for tables. Is it feasable
 to require tbl for building fvwm.1? I think it has been around for a long
 time, but I don't know for how long. GNU roff runs preprocessors
 automatic, but for compatibility it has to be done at build time.

 I really don't know what you are talking about, but gnu tbl is
 installed on my machine.  Are you saying that tbl is required for
 generating the man page or for viewing it?  And when I run

 tbl was required for viewing it until my latest commt. Now it should only 
 be required for generating it. I'm not sure exactly why your version of man 
 doesn't process tbl input, but it didn't work on a solaris 9 machine I have 
 access to either, so I igured it has to be done at build stage for 
 compatibility.

Exactly.  It's a leagcy thing which isn't likely ever to go away.  Suffice
it to say it works on OpenSolairs, for instance, without a problem.

-- Thomas Adam

--
He wants you back, he screams into the night air, like a fireman going
through a window that has no fire. -- Mike Myers, This Poem Sucks.



Re: New 2.5.22 release?

2007-08-16 Thread Dominik Vogt
On Mon, Aug 13, 2007 at 10:58:09PM +0200, Viktor Griph wrote:
 On Mon, 13 Aug 2007, Dominik Vogt wrote:
 On Mon, Aug 13, 2007 at 11:08:57AM +0100, seventh guardian wrote:
 On 8/6/07, Dominik Vogt [EMAIL PROTECTED] wrote:
 On Mon, Aug 06, 2007 at 02:02:35PM +0100, seventh guardian wrote:
 The NEWS file is getting long, so I believe a new release would be
 good.
 
 Yes.
 
 Ok, so where do we stand now?
 
 * The new module code should be safe [done]
 
 * Is everything related to the manpage fixed?
 
 No, not at all.  The only thing fixed is that building the docs
 does not require GNU make anymore.  All other points on the list
 remain.
 
 The fixmes are gone. Perl isn't needed for building but it's unconvinient 
 to add commands, but that can be fixed after release. Were there any other 
 points?

Most important: the generated man page is still broken.  For
example:


  allbox tab(:); lB lB lB.  T{   T}:T{ depth 8 (256 colors) T}:T{
  depth 4 (16 colors) T} l l l l l l l l l.  T{ PseudoColor T}:T{ 68
  (4 cc + 4 grey) T}:T{ 10 (2 cc + 2 grey) T} T{ GrayScale T}:T{ 64
  regular grey T}:T{ 8 regular grey T} T{ DirectColor T}:T{ 32 (3 cc
  + 5 grey) T}:T{ 10 (2 cc + 2 grey) T}

There are three other places with similar broken formatting in fvwm.1.

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-16 Thread Viktor Griph

On Thu, 16 Aug 2007, Dominik Vogt wrote:


On Mon, Aug 13, 2007 at 10:58:09PM +0200, Viktor Griph wrote:

On Mon, 13 Aug 2007, Dominik Vogt wrote:

On Mon, Aug 13, 2007 at 11:08:57AM +0100, seventh guardian wrote:

On 8/6/07, Dominik Vogt [EMAIL PROTECTED] wrote:

On Mon, Aug 06, 2007 at 02:02:35PM +0100, seventh guardian wrote:

The NEWS file is getting long, so I believe a new release would be
good.


Yes.


Ok, so where do we stand now?

* The new module code should be safe [done]

* Is everything related to the manpage fixed?


No, not at all.  The only thing fixed is that building the docs
does not require GNU make anymore.  All other points on the list
remain.


The fixmes are gone. Perl isn't needed for building but it's unconvinient
to add commands, but that can be fixed after release. Were there any other
points?


Most important: the generated man page is still broken.  For
example:


 allbox tab(:); lB lB lB.  T{   T}:T{ depth 8 (256 colors) T}:T{
 depth 4 (16 colors) T} l l l l l l l l l.  T{ PseudoColor T}:T{ 68
 (4 cc + 4 grey) T}:T{ 10 (2 cc + 2 grey) T} T{ GrayScale T}:T{ 64
 regular grey T}:T{ 8 regular grey T} T{ DirectColor T}:T{ 32 (3 cc
 + 5 grey) T}:T{ 10 (2 cc + 2 grey) T}

There are three other places with similar broken formatting in fvwm.1.


I'll look into it if you can give me some hint on how to fix automake for 
the doc directory on my macbook.


/Viktor



Re: New 2.5.22 release?

2007-08-16 Thread Dominik Vogt
On Thu, Aug 16, 2007 at 07:42:36PM +0200, Viktor Griph wrote:
 On Thu, 16 Aug 2007, Dominik Vogt wrote:
 
 On Mon, Aug 13, 2007 at 10:58:09PM +0200, Viktor Griph wrote:
 On Mon, 13 Aug 2007, Dominik Vogt wrote:
 On Mon, Aug 13, 2007 at 11:08:57AM +0100, seventh guardian wrote:
 On 8/6/07, Dominik Vogt [EMAIL PROTECTED] wrote:
 On Mon, Aug 06, 2007 at 02:02:35PM +0100, seventh guardian wrote:
 The NEWS file is getting long, so I believe a new release would be
 good.
 
 Yes.
 
 Ok, so where do we stand now?
 
 * The new module code should be safe [done]
 
 * Is everything related to the manpage fixed?
 
 No, not at all.  The only thing fixed is that building the docs
 does not require GNU make anymore.  All other points on the list
 remain.
 
 The fixmes are gone. Perl isn't needed for building but it's unconvinient
 to add commands, but that can be fixed after release. Were there any other
 points?
 
 Most important: the generated man page is still broken.  For
 example:
 
 
  allbox tab(:); lB lB lB.  T{   T}:T{ depth 8 (256 colors) T}:T{
  depth 4 (16 colors) T} l l l l l l l l l.  T{ PseudoColor T}:T{ 68
  (4 cc + 4 grey) T}:T{ 10 (2 cc + 2 grey) T} T{ GrayScale T}:T{ 64
  regular grey T}:T{ 8 regular grey T} T{ DirectColor T}:T{ 32 (3 cc
  + 5 grey) T}:T{ 10 (2 cc + 2 grey) T}
 
 There are three other places with similar broken formatting in fvwm.1.
 
 I'll look into it if you can give me some hint on how to fix automake for 
 the doc directory on my macbook.

What's the problem?

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-16 Thread Viktor Griph

yOn Thu, 16 Aug 2007, Viktor Griph wrote:


On Thu, 16 Aug 2007, Dominik Vogt wrote:


On Thu, Aug 16, 2007 at 07:42:36PM +0200, Viktor Griph wrote:


I'll look into it if you can give me some hint on how to fix automake for
the doc directory on my macbook.


What's the problem?



doc/fvwm/Makefile.am:14: BUILD_FILES was already defined in condition TRUE, 
which implies condition FVWM_BUILD_HTMLDOC_TRUE

 BUILD_FILES (User, where = doc/fvwm/Makefile.am:14) +=
 {
   TRUE =
 }
doc/fvwm/Makefile.am:14: BUILD_FILES was already defined in condition TRUE, 
which implies condition FVWM_BUILD_MANDOC_TRUE


 BUILD_FILES (User, where = doc/fvwm/Makefile.am:14) +=
 {
   FVWM_BUILD_HTMLDOC_TRUE = $(HTML_FILES)
   TRUE =
 }
+ exit 3



This is with automake 1.6.3 and autoconf 2.59.

/Viktor



Re: New 2.5.22 release?

2007-08-16 Thread Dominik Vogt
On Thu, Aug 16, 2007 at 09:08:51PM +0200, Viktor Griph wrote:
 yOn Thu, 16 Aug 2007, Viktor Griph wrote:
 
 On Thu, 16 Aug 2007, Dominik Vogt wrote:
 
 On Thu, Aug 16, 2007 at 07:42:36PM +0200, Viktor Griph wrote:
 
 I'll look into it if you can give me some hint on how to fix automake for
 the doc directory on my macbook.
 
 What's the problem?
 
 
 doc/fvwm/Makefile.am:14: BUILD_FILES was already defined in condition 
 TRUE, which implies condition FVWM_BUILD_HTMLDOC_TRUE
  BUILD_FILES (User, where = doc/fvwm/Makefile.am:14) +=
  {
TRUE =
  }
 doc/fvwm/Makefile.am:14: BUILD_FILES was already defined in condition 
 TRUE, which implies condition FVWM_BUILD_MANDOC_TRUE
 
  BUILD_FILES (User, where = doc/fvwm/Makefile.am:14) +=
  {
FVWM_BUILD_HTMLDOC_TRUE = $(HTML_FILES)
TRUE =
  }
 + exit 3
 
 
 This is with automake 1.6.3 and autoconf 2.59.

I tried to fix it without understanding the problem. Does it work
now?

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-16 Thread Viktor Griph

On Thu, 16 Aug 2007, Dominik Vogt wrote:


On Thu, Aug 16, 2007 at 09:08:51PM +0200, Viktor Griph wrote:

yOn Thu, 16 Aug 2007, Viktor Griph wrote:


On Thu, 16 Aug 2007, Dominik Vogt wrote:


On Thu, Aug 16, 2007 at 07:42:36PM +0200, Viktor Griph wrote:


I'll look into it if you can give me some hint on how to fix automake for
the doc directory on my macbook.


What's the problem?



doc/fvwm/Makefile.am:14: BUILD_FILES was already defined in condition
TRUE, which implies condition FVWM_BUILD_HTMLDOC_TRUE
BUILD_FILES (User, where = doc/fvwm/Makefile.am:14) +=
{
  TRUE =
}
doc/fvwm/Makefile.am:14: BUILD_FILES was already defined in condition
TRUE, which implies condition FVWM_BUILD_MANDOC_TRUE

BUILD_FILES (User, where = doc/fvwm/Makefile.am:14) +=
{
  FVWM_BUILD_HTMLDOC_TRUE = $(HTML_FILES)
  TRUE =
}
+ exit 3



This is with automake 1.6.3 and autoconf 2.59.


I tried to fix it without understanding the problem. Does it work
now?



yes, thanks

/Viktor



Re: New 2.5.22 release?

2007-08-16 Thread Viktor Griph

On Fri, 17 Aug 2007, Dominik Vogt wrote:


On Thu, Aug 16, 2007 at 10:13:19PM +0200, Viktor Griph wrote:

On Thu, 16 Aug 2007, Viktor Griph wrote:

On Thu, 16 Aug 2007, Dominik Vogt wrote:

Most important: the generated man page is still broken.  For
example:


allbox tab(:); lB lB lB.  T{   T}:T{ depth 8 (256 colors) T}:T{
depth 4 (16 colors) T} l l l l l l l l l.  T{ PseudoColor T}:T{ 68
(4 cc + 4 grey) T}:T{ 10 (2 cc + 2 grey) T} T{ GrayScale T}:T{ 64
regular grey T}:T{ 8 regular grey T} T{ DirectColor T}:T{ 32 (3 cc
+ 5 grey) T}:T{ 10 (2 cc + 2 grey) T}

There are three other places with similar broken formatting in fvwm.1.


I'll look into it if you can give me some hint on how to fix automake for
the doc directory on my macbook.


Does that formatting show up in your processed output?


Yes, that's from the formatted man page.


It is formatting
for tbl(1), which seems to be used by docbook for tables. Is it feasable
to require tbl for building fvwm.1? I think it has been around for a long
time, but I don't know for how long. GNU roff runs preprocessors
automatic, but for compatibility it has to be done at build time.


I really don't know what you are talking about, but gnu tbl is
installed on my machine.  Are you saying that tbl is required for
generating the man page or for viewing it?  And when I run


tbl was required for viewing it until my latest commt. Now it should only 
be required for generating it. I'm not sure exactly why your version of 
man doesn't process tbl input, but it didn't work on a solaris 9 machine I 
have access to either, so I igured it has to be done at build stage for 
compatibility.




 $ nroff fvwm.1 | col -bx

manually, I still have that markup in the output.



Does it work with the latest Makefile?

/Viktor



Re: New 2.5.22 release?

2007-08-16 Thread Dominik Vogt
On Fri, Aug 17, 2007 at 12:42:50AM +0200, Viktor Griph wrote:
 On Fri, 17 Aug 2007, Dominik Vogt wrote:
 
 On Thu, Aug 16, 2007 at 10:13:19PM +0200, Viktor Griph wrote:
 On Thu, 16 Aug 2007, Viktor Griph wrote:
 On Thu, 16 Aug 2007, Dominik Vogt wrote:
 Most important: the generated man page is still broken.  For
 example:
 
 
 allbox tab(:); lB lB lB.  T{   T}:T{ depth 8 (256 colors) T}:T{
 depth 4 (16 colors) T} l l l l l l l l l.  T{ PseudoColor T}:T{ 68
 (4 cc + 4 grey) T}:T{ 10 (2 cc + 2 grey) T} T{ GrayScale T}:T{ 64
 regular grey T}:T{ 8 regular grey T} T{ DirectColor T}:T{ 32 (3 cc
 + 5 grey) T}:T{ 10 (2 cc + 2 grey) T}
 
 There are three other places with similar broken formatting in fvwm.1.
 
 I'll look into it if you can give me some hint on how to fix automake for
 the doc directory on my macbook.
 
 Does that formatting show up in your processed output?
 
 Yes, that's from the formatted man page.
 
 It is formatting
 for tbl(1), which seems to be used by docbook for tables. Is it feasable
 to require tbl for building fvwm.1? I think it has been around for a long
 time, but I don't know for how long. GNU roff runs preprocessors
 automatic, but for compatibility it has to be done at build time.
 
 I really don't know what you are talking about, but gnu tbl is
 installed on my machine.  Are you saying that tbl is required for
 generating the man page or for viewing it?  And when I run
 
 tbl was required for viewing it until my latest commt. Now it should only 
 be required for generating it. I'm not sure exactly why your version of 
 man doesn't process tbl input, but it didn't work on a solaris 9 machine I 
 have access to either, so I igured it has to be done at build stage for 
 compatibility.
 
 
  $ nroff fvwm.1 | col -bx
 
 manually, I still have that markup in the output.
 
 
 Does it work with the latest Makefile?

Yes.  I'm now looking at the issues brought up by requiring sed,
perl and tbl for building the docs.

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-14 Thread seventh guardian
On 8/13/07, Viktor Griph [EMAIL PROTECTED] wrote:
 On Mon, 13 Aug 2007, Dominik Vogt wrote:

  On Mon, Aug 13, 2007 at 11:08:57AM +0100, seventh guardian wrote:
  On 8/6/07, Dominik Vogt [EMAIL PROTECTED] wrote:
  On Mon, Aug 06, 2007 at 02:02:35PM +0100, seventh guardian wrote:
  The NEWS file is getting long, so I believe a new release would be
  good.
 
  Yes.
 
  Ok, so where do we stand now?
 
  * The new module code should be safe [done]
 
  * Is everything related to the manpage fixed?
 
  No, not at all.  The only thing fixed is that building the docs
  does not require GNU make anymore.  All other points on the list
  remain.

 The fixmes are gone. Perl isn't needed for building but it's unconvinient
 to add commands, but that can be fixed after release. Were there any other
 points?

Bump! Dominik?

  Renato



Re: New 2.5.22 release?

2007-08-13 Thread seventh guardian
On 8/13/07, seventh guardian [EMAIL PROTECTED] wrote:
 On 8/6/07, Dominik Vogt [EMAIL PROTECTED] wrote:
  On Mon, Aug 06, 2007 at 02:02:35PM +0100, seventh guardian wrote:
   The NEWS file is getting long, so I believe a new release would be
   good.
 
  Yes.

 Ok, so where do we stand now?

 * The new module code should be safe [done]

 * Is everything related to the manpage fixed?

 * Regarding the lower-case vs upper-case discussion, we can change
 everything to upper-case later if we agree to. Most things are as they
 was before, so there should be no problem regarding the release.

 Once these points are all covered I think we should release. As I
 said, the NEWS file entry is getting too long.

By the way, I can probably start changing the license localy. If I
manage to finish it before the release, then good. Else, I'll apply
the changes afterwards.

I'll start by the fvwm dir, so if someone wants to help they can do
the fvwmlib dir and the module dirs. Hum, probably a temporary branch
could be useful for a cooperative work..

Cheers,
  Renato



Re: New 2.5.22 release?

2007-08-13 Thread seventh guardian
On 8/13/07, Viktor Griph [EMAIL PROTECTED] wrote:
 On Mon, 13 Aug 2007, seventh guardian wrote:

  On 8/6/07, Dominik Vogt [EMAIL PROTECTED] wrote:
  On Mon, Aug 06, 2007 at 02:02:35PM +0100, seventh guardian wrote:
  The NEWS file is getting long, so I believe a new release would be
  good.
 
  Yes.
 
  Ok, so where do we stand now?
 
  * The new module code should be safe [done]

 Are startup modules fixed?

Yes.

  * Is everything related to the manpage fixed?

 I believe so.

  Once these points are all covered I think we should release. As I
  said, the NEWS file entry is getting too long.

 I have some problems with a fresh checkout on MacOS X

 $ utils/configure_dev.sh --prefix=/home/viktor/fvwm/install
 + aclocal
 + autoheader
 + automake --add-missing
 configure.ac: installing `./install-sh'
 configure.ac: installing `./mkinstalldirs'
 configure.ac: installing `./missing'
 configure.ac:313: installing `./config.guess'
 configure.ac:313: installing `./config.sub'
 bin/Makefile.am: installing `./depcomp'
 doc/fvwm/Makefile.am:14: BUILD_FILES was already defined in condition
 TRUE, which implies condition FVWM_BUILD_HTMLDOC_TRUE
BUILD_FILES (User, where = doc/fvwm/Makefile.am:14) +=
{
  TRUE =
}
 doc/fvwm/Makefile.am:14: BUILD_FILES was already defined in condition
 TRUE, which implies condition FVWM_BUILD_MANDOC_TRUE

BUILD_FILES (User, where = doc/fvwm/Makefile.am:14) +=
{
  FVWM_BUILD_HTMLDOC_TRUE = $(HTML_FILES)
  TRUE =
}
 doc/fvwm/Makefile.am:14: BUILD_FILES was already defined in condition
 TRUE, which implies condition FVWM_BUILD_HTMLDOC_TRUE
BUILD_FILES (User, where = doc/fvwm/Makefile.am:14) +=
{
  TRUE =
}
 doc/fvwm/Makefile.am:14: BUILD_FILES was already defined in condition
 TRUE, whic
 h implies condition FVWM_BUILD_MANDOC_TRUE

BUILD_FILES (User, where = doc/fvwm/Makefile.am:14) +=
{
  FVWM_BUILD_HTMLDOC_TRUE = $(HTML_FILES)
  TRUE =
}
 + exit 3

 $ automake --version
 automake (GNU automake) 1.6.3

 $ autoconf --version
 autoconf (GNU Autoconf) 2.59


I believe we should fix this and then release.
  Renato



Re: New 2.5.22 release?

2007-08-13 Thread Viktor Griph

On Mon, 13 Aug 2007, Dominik Vogt wrote:


On Mon, Aug 13, 2007 at 11:08:57AM +0100, seventh guardian wrote:

On 8/6/07, Dominik Vogt [EMAIL PROTECTED] wrote:

On Mon, Aug 06, 2007 at 02:02:35PM +0100, seventh guardian wrote:

The NEWS file is getting long, so I believe a new release would be
good.


Yes.


Ok, so where do we stand now?

* The new module code should be safe [done]

* Is everything related to the manpage fixed?


No, not at all.  The only thing fixed is that building the docs
does not require GNU make anymore.  All other points on the list
remain.


The fixmes are gone. Perl isn't needed for building but it's unconvinient 
to add commands, but that can be fixed after release. Were there any other 
points?


/Viktor



Re: New 2.5.22 release?

2007-08-07 Thread Viktor Griph

On Tue, 7 Aug 2007, Scott Smedley wrote:


The documentation:

 * There are several FIXME comments in the generated
   documentation.  Try this:

 $ cd doc
 $ find . -type f | xargs grep -I FIXME


All the FIXME stuff in the docbook-xsl/ subdirectory can be safely ignored.

A better check:

$ cd doc
$ find . -name '*.xml' | xargs grep -i FIXME

There are only 2 matches. Both minor  not a reason to preclude a
2.5.22 release.



* The boolean arguments section is still missing from the new manpage.


On a separate issue:

I am keen to implement Viktor's suggestion to build the documentation
on 'make dist'. See:

http://thread.gmane.org/gmane.comp.window-managers.fvwm.devel/3173

(It doesn't have to happen before 2.5.22) I think this is a very good
idea. Among other things, it would alleviate some of DV's concerns about
slow build times.

DV: As you have a much better grasp of the build system than I, is this
   something you might like to tackle? If not, some implementation
   advice would be very helpful.



The manpage is currently built on make dist. Maybe the configure uption 
for controlling man output should be removed. Html output is not built on 
make dist yet.


/Viktor



Re: New 2.5.22 release?

2007-08-07 Thread Dominik Vogt
On Tue, Aug 07, 2007 at 11:49:18AM +1000, Scott Smedley wrote:
 1 month has elapsed since DV expressed a desire to relicence FVWM with
 GPLv3. I think we can go ahead with this now.

Let's do that later.  It's a lot of work and many many files have
to be touched.  The documentation issue is big enough for now.

   The documentation:
   
* There are several FIXME comments in the generated
  documentation.  Try this:
   
$ cd doc
$ find . -type f | xargs grep -I FIXME
 
 All the FIXME stuff in the docbook-xsl/ subdirectory can be safely ignored.

Allright.

 A better check:
 
   $ cd doc
   $ find . -name '*.xml' | xargs grep -i FIXME 
 
 There are only 2 matches. Both minor  not a reason to preclude a
 2.5.22 release.

I'm not going to release fvwm with a big fat FIXME and a broken
paragraph in the man page.

* GNU make is needed to build it.
 
 I'm so glad someone is helping on this - I find the build system
 complicated.

Done.

   * There is a Perl script to generate some part of the
 documentation (doc/util/genAllCommands.pl).  Fvwm does not
 require Perl to be built and I have no intention to change
 that.
 
 That perl script is used to create the alphabetically-sorted table on
 this page:
 
 http://www.fvwm.org/doc/unstable/allCommands.html
 
 It is run manually (usually be me) anytime a new command is documented.
 So, no need to worry about Perl dependencies.

1) I think this is not acceptable.  It's too difficult to add new
   commands right now.  I'm working on a solution to have just
   functable.c as a source for the commands list and to eliminate
   all other tables.  The script must be run automatically when
   I'm done (and there is no real reason to require running it
   manually).

2) With a package conforming to the GNU standards, it should be
   possible to build a new tarbarr from the tarball.  The script
   would be a regular part of the build process and can not be
   written in Perl.

 On a separate issue:
 
 I am keen to implement Viktor's suggestion to build the documentation
 on 'make dist'. See: 
 
 http://thread.gmane.org/gmane.comp.window-managers.fvwm.devel/3173
 
 (It doesn't have to happen before 2.5.22) I think this is a very good
 idea. Among other things, it would alleviate some of DV's concerns about
 slow build times.
 
 DV: As you have a much better grasp of the build system than I, is this
 something you might like to tackle? If not, some implementation
 advice would be very helpful.

Yes, I'm planning to do this, but it's not necessary for this
release.  Let's not do too many things at the same time.

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-07 Thread Dominik Vogt
On Tue, Aug 07, 2007 at 11:49:18AM +1000, Scott Smedley wrote:
* GNU make is needed to build it.
 
 I'm so glad someone is helping on this - I find the build system
 complicated.

It *is* complicated.  As a rule of thumb, always run

  $ make distcheck

when you work on the installation process.  By eliminating the
errors you can learn a lot about how automake works.  And don't
hesitate to ask if you don't understand something.

The distcheck target does the following:

 * Generate the tarball.
 * Unpack the tarball.
 * Build and install the tarball with separate source, build and
   install directories.  It write protects the directories during
   build steps when they are not allowed to be written.
 * Deinstall and check that everything is removed.

Common errors are that the Makefile tried to create a file in the
source directory and that files are left in the install directory
after make uninstall.  It's difficult to understand from the
error messages though.

The autoconf/automake documentation is also very good:

  http://www.gnu.org/software/autoconf/manual/
  http://www.gnu.org/software/automake/manual/

And there used to be the autobook, but it's no longer available
as postscript, only as a paper copy and html files.

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-07 Thread seventh guardian
On 8/7/07, Scott Smedley [EMAIL PROTECTED] wrote:
   It is run manually (usually be me) anytime a new command is documented.
   So, no need to worry about Perl dependencies.
 
  1) I think this is not acceptable.  It's too difficult to add new
 commands right now.

 Difficult to document new commands? I disagree.

I think Dominik meant adding new commands to fvwm. Indeed there are a
lot of places to change just for adding one command

 I'm working on a solution to have just
 functable.c as a source for the commands list and to eliminate
 all other tables.  The script must be run automatically when
 I'm done (and there is no real reason to require running it
 manually).

Please let me know how you're planning on doing that. I'm thinking of
a way to add support for .so modules to fvwm, and a way of dynamically
registering commands would be nice :)

Cheers,
  Renato



Re: New 2.5.22 release?

2007-08-07 Thread Dominik Vogt
On Tue, Aug 07, 2007 at 03:17:02PM +0100, Thomas Adam wrote:
 On 07/08/07, Scott Smedley [EMAIL PROTECTED] wrote:
  write fvwm in lower case
 
  Why?
 
 Agreed.  FVWM is an acronym; it should be written as such, which means
 in upper case.

And why should acronyms be written in capitals?

Fvwm is a name, and it's written fvwm almost everywhere.  I
unified the spelling years ago, and I see no reason to change it
again.  fvwm works just fine.  The remaining occurences of
FVWM are there just because I hesitated to change them.

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature


Re: New 2.5.22 release?

2007-08-07 Thread Viktor Griph
On 8/7/07, Scott Smedley [EMAIL PROTECTED] wrote:
  I'm not going to release fvwm with a big fat FIXME

 I didn't realise Viktor had already made a change to install the new
 man page. The old man page is still around.

 VG: any reason for installing the new man page  still building the old one?

No reason in particular I think it can sefely be deleted from CVS, but
I'm not sure how fvwm-web works with the new manpage (Ok, it's a
separate page, but the old man2html generated page still exists, and
the new man page doesn't blend into the style of that page). The old
documentation is outdated, and couldn't be used for a release. That's
why I changed to install the new one. The fixmes should be gone now.

/Viktor



Re: New 2.5.22 release?

2007-08-07 Thread Thomas Adam
On Tue, Aug 07, 2007 at 08:21:20PM +0200, Dominik Vogt wrote:
 On Tue, Aug 07, 2007 at 03:17:02PM +0100, Thomas Adam wrote:
  On 07/08/07, Scott Smedley [EMAIL PROTECTED] wrote:
   write fvwm in lower case
  
   Why?
  
  Agreed.  FVWM is an acronym; it should be written as such, which means
  in upper case.
 
 And why should acronyms be written in capitals?

Because the individual letters stand for something.

-- Thomas Adam

--
He wants you back, he screams into the night air, like a fireman going
through a window that has no fire. -- Mike Myers, This Poem Sucks.



Re: New 2.5.22 release?

2007-08-06 Thread Dominik Vogt
On Mon, Aug 06, 2007 at 02:02:35PM +0100, seventh guardian wrote:
 The NEWS file is getting long, so I believe a new release would be
 good.

Yes.

 Should we wait a couple of days for testing the recent changes
 to the module code? Is there any other issue that may prevent the
 release?

The documentation:

 * There are several FIXME comments in the generated
   documentation.  Try this:

 $ cd doc
 $ find . -type f | xargs grep -I FIXME

 * GNU make is needed to build it.

I'm working on the second problem

Ciao

Dominik ^_^  ^_^

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


signature.asc
Description: Digital signature