On Sat, Jan 02, 2010 at 03:50:48PM +0000, Thomas Adam wrote: > All, > > Are there any outstanding bug-fixes which haven't yet been looked into, but > were at one point reported to this list?
Here are a few grammatical fixes for the documentation. They weren't reported on the list, but I hope you apply them anyway. --Paul Vojta, [email protected] Index: doc/commands/Menu.xml =================================================================== RCS file: /home/cvs/fvwm/fvwm/doc/commands/Menu.xml,v retrieving revision 1.5 diff -u -r1.5 Menu.xml --- doc/commands/Menu.xml 19 Aug 2007 21:43:39 -0000 1.5 +++ doc/commands/Menu.xml 2 Jan 2010 21:51:45 -0000 @@ -139,7 +139,7 @@ <replaceable>x</replaceable> and <replaceable>y</replaceable> -specify how far the menu is moved from it's default position. By +specify how far the menu is moved from its default position. By default, the numeric value given is interpreted as a percentage of the context rectangle's width (height), but with a trailing '<fvwmopt cmd="Menu" opt="m"/>' @@ -226,7 +226,7 @@ as an option. This might happen for example if you want the menu always in the top right corner of the screen.</para> -<para>Where do you want a menu to appear when you click on it's menu +<para>Where do you want a menu to appear when you click on its menu item? The default is to place the title under the cursor, but if you want it where the position arguments say, use the <fvwmopt cmd="Menu" opt="SelectInPlace"/> Index: doc/commands/Style.xml =================================================================== RCS file: /home/cvs/fvwm/fvwm/doc/commands/Style.xml,v retrieving revision 1.12 diff -u -r1.12 Style.xml --- doc/commands/Style.xml 2 Aug 2009 15:04:08 -0000 1.12 +++ doc/commands/Style.xml 2 Jan 2010 21:51:47 -0000 @@ -1085,7 +1085,7 @@ <para> <fvwmopt cmd="Style" opt="StickyIcon"/> -makes the window sticky when its iconified. It de-iconifies on +makes the window sticky when it's iconified. It de-iconifies on top the active desktop. <fvwmopt cmd="Style" opt="SlipperyIcon"/> reverts back to the default. @@ -1122,7 +1122,7 @@ style.</para> <para><fvwmopt cmd="Style" opt="StickyIcon"/> -makes the window sticky when its iconified. It de-iconifies on +makes the window sticky when it's iconified. It de-iconifies on top the active desktop. <fvwmopt cmd="Style" opt="SlipperyIcon"/> reverts back to the default.</para> @@ -1653,7 +1653,7 @@ <para><fvwmopt cmd="Style" opt="NoUsePPosition"/> instructs fvwm to ignore the program specified position (PPosition hint) when adding new windows. Using PPosition is required for -some applications, but if you do not have one of those its a real +some applications, but if you do not have one of those it's a real headache. Many programs set PPosition to something obnoxious like 0,0 (upper left corner). Note: <emphasis>!UsePPosition</emphasis> Index: docs/ChangeLog =================================================================== RCS file: /home/cvs/fvwm/fvwm/docs/ChangeLog,v retrieving revision 1.233 diff -u -r1.233 ChangeLog --- docs/ChangeLog 2 Jan 2010 17:49:04 -0000 1.233 +++ docs/ChangeLog 2 Jan 2010 21:51:47 -0000 @@ -472,7 +472,7 @@ * FAQ: Added Maximize but don't cover (3.21), and Positioning a window using arithmetic (7.15). - Remove hot-spot information since its in the man page. + Remove hot-spot information since it's in the man page. 2002-08-12 Dan Espen <[email protected]> @@ -836,7 +836,7 @@ * TODO (Bugfixes): Remove TODO items: "Allow env var to specify an additional read directory ($FVWMRCDIR or $FVWMHOME or something - similiar)?" (Its done.) + similiar)?" (It's done.) "Add better overall icon handling options?" (I can only guess what it meant, but I think the default box covers it.) @@ -847,7 +847,7 @@ so that FvwmForm can be used as a "Help" form." Done. "Run profiling on FVWM to see if I can speed it up any more" - Its been done. + It's been done. (We could dispense with the TODO file completely and rely on Jitterbug instead.) Index: docs/FAQ =================================================================== RCS file: /home/cvs/fvwm/fvwm/docs/FAQ,v retrieving revision 1.165 diff -u -r1.165 FAQ --- docs/FAQ 22 Jan 2009 01:32:16 -0000 1.165 +++ docs/FAQ 2 Jan 2010 21:51:50 -0000 @@ -1454,7 +1454,7 @@ A: Fvwm has some builtin idea of what the buttons do, and some applications can request that certain buttons not be shown. - For example, its normal for Fvwm to suppress the iconify button + For example, it's normal for Fvwm to suppress the iconify button (builtin button 4, the second button from the right) on a transient (dialog) window. @@ -2290,7 +2290,7 @@ up like a normal X app where the WM draws the borders. With MWWM=MWM, it works ok too except that for the main window, no borders are drawn by the WM and Rose draws - it's own borders (I have fvwm respecting MWM decor + its own borders (I have fvwm respecting MWM decor hints). (This is correct as mentioned by the Knowledgebase pages above.) I don't recall what Rose looks like with dtwm, but I suspect it's quite close to @@ -2500,7 +2500,7 @@ allocate colors. Older hardware uses something called 8 bit color. You can also - mis-configure newer hardware so that its only using 8 bit color. + mis-configure newer hardware so that it's only using 8 bit color. When you use 8 bit color, your display can only have 256 colors on it at once. @@ -3201,7 +3201,7 @@ + I Iconify You can use FvwmEvent to remove the Icons when each window is - returned to it's non Iconic state. + returned to its non Iconic state. DestroyFunc DeThumbnail AddToFunc DeThumbnail
