2009/9/17 Darren Upsolla <abovefrombe...@hotmail.com>: > >> From: abovefrombe...@hotmail.com >> To: jai...@math.boisestate.edu >> CC: des...@verizon.net; fvwm@fvwm.org >> Subject: Re: FVWM: starting up applications >> Date: Thu, 17 Sep 2009 01:00:59 +0000 >> >> what do i do to see that happen? contact the author? get him to submit >> patches or >> something else? this is really important for first time readers > > any chance we could come to an agreement on this? do i have to do any work - > if so, what?
So is something like the following patch attached what you meant? To be honest, I consider the patch to add bloat over any useful explanation. Plus, since you don't say *which* bits from my original post you consider worthy of inclusion in the manpage, it makes my job a lot harder. Bear in mind also, what was in that post you linked to was information not relevant to the manpage, and offered solutions to a specific example the original poster was having, and that I felt needed a lot of explanation. I wish though you hadn't brought this up -- I feel as though I am needing to justify myself for no good reason. Anyway, see the limited patch attached. I personally don't like it, but if it means others do, I will commit it. Note also I have *NO* idea about the proper XML formatting my patch uses -- I was guessing based on other examples. I hate the docbook XML stuff, FWIW -- it makes writing these things a pain in the arse. I will be issuing an email out about a transition for FVWM 2.6 to something else I have in mind, in due course -- just not yet. Either way, what we have just can't continue. -- Thomas Adam
Index: doc/fvwm/initialization.xml =================================================================== RCS file: /home/cvs/fvwm/fvwm/doc/fvwm/initialization.xml,v retrieving revision 1.5 diff -u -r1.5 initialization.xml --- doc/fvwm/initialization.xml 31 Jul 2007 09:30:15 -0000 1.5 +++ doc/fvwm/initialization.xml 21 Sep 2009 21:25:22 -0000 @@ -9,8 +9,25 @@ <para>During initialization, fvwm searches for a configuration file which describes key and button bindings, and many other -things. The format of these files is described later. Fvwm first -searches for configuration files using the command</para> +things. This file is:</para> + +<programlisting> + <fvwmref cmd="Read"/> <filename>$FVWM_DATADIR/configFvwmDefaults</filename> +</programlisting> + +<para>This file is responsible for also providing function definitions such + as:</para> + +<simplelist> + <member>WindowListFunc</member> + <member>EWMHActivateWindowFunc</member> + <member>UrgencyFunc</member> +</simplelist> + +<para>It should be noted though that this file should never be edited. This +what the personal fvwm2rc file is for.</para> + +<para>Fvwm first searches for configuration files using the command</para> <programlisting> <fvwmref cmd="Read"/> <filename>config</filename> @@ -109,6 +126,11 @@ command (described later) to start up modules, xterms, or whatever you'd like to have started by fvwm.</para> +<para>Note that <emphasis remap='B'>InitFunction</emphasis> is considered +deprecated and will be removed in the future. See below for ways of +emulating <emphasis remap='B'>InitFunction</emphasis> using +<emphasis remap='B'>StartFunction</emphasis> instead.</para> + <para>Fvwm has also a special exit function: <emphasis remap='B'>ExitFunction</emphasis>, executed when exiting or restarting before actually quitting.
