GNOME.org
 

sawfish r4458 - in trunk: . man

Author: chrisb
Date: Thu Apr  2 19:13:25 2009
New Revision: 4458
URL: http://svn.gnome.org/viewvc/sawfish?rev=4458&view=rev

Log:
2009-04-02  Christopher Bratusek <zanghar freenet de>
        * man/faq.texi: major update [Teika]

        * man/sawfish.texi: major update [Teika

Modified:
   trunk/ChangeLog
   trunk/man/faq.texi
   trunk/man/sawfish.texi

Modified: trunk/man/faq.texi
==============================================================================
--- trunk/man/faq.texi	(original)
+++ trunk/man/faq.texi	Thu Apr  2 19:13:25 2009
@@ -4,120 +4,82 @@
 
 @enumerate
 
- item Why is it now called @emph{Sawfish}?
+ item How can I get informations on Sawfish?
 
-Because the old name (@samp{Sawmill}) was already being used by another
-company, who were in the process of registering it as a trademark.
-
-The rename should be mostly painless, all old binaries still work for
-the time being, but will be phased out over time (final phasing out
-started around 1.5.0). Where before you would execute a program called
- file{sawmill*}, replace it by @file{sawfish*}. E.g. @file{sawmill}
-becomes @file{sawfish}, and @file{sawmill-client} becomes
- file{sawfish-client} 
-
-Your @file{~/.sawmill} directory will automatically be renamed
- file{~/.sawfish} unless it would overwrite an existing file. Only
-user configuration @file{~/.sawfish[/]rc} will be checked currently,
- file{~/.sawmillrc} is not used anymore (it was also read up to
-version 1.3.5).
-
-My apologies for any inconvenience caused.
-
-
- item But why @emph{Sawfish}, and not <insert your favourite
-alternative>?
-
-Well I had to choose something! And hopefully it satisfies the main
-requirements:
-
- itemize @bullet
- item There are no other computer-related users of the name (as checked
-in April 2000,)
+ itemize
+ item Homepage: @url{http://sawfish.wikia.com/}.
+ item Mailing list: Please subscribe at @url{http://mail.gnome.org/mailman/listinfo/sawfish-list}. You can browse the archives at @url{http://mail.gnome.org/archives/sawfish-list/}.
+ item IRC: Join @code{#sawfish} on @code{irc.freenode.net}.
+ end itemize
 
- item It's similar enough to the old name to hopefully carry some
-recognition across,
+ item How do I read the Info manual?
 
- item It has no tenuous relationship to window-managing.
- end itemize
+Either execute the command @samp{info sawfish}, or enter the Info mode
+within Emacs (@kbd{C-h i}) and type @kbd{g (sawfish) RET}.
 
+If you're using Gnome, then try executing @samp{gnome-help-browser
+info:sawfish}.
 
 @item I installed Sawfish but it's not working!  All I see when I
 start X is the default stipple background: no programs, no menus, no
 pager.
 
-This is exactly what it's supposed to do. Sawfish is a @emph{window
-manager} and as such is not responsible for setting the background,
-starting programs or displaying a pager---these can all be done using
-separate applications (e.g. by using a desktop environment such as
-Gnome).
-
-The default menu binding is somewhat obscure; you must middle-click on
-the background to bring up the menus (If you have a two-button mouse,
-try clicking both buttons simultaneously)
+This is exactly what it's supposed to do, but first try middle-click
+(by default) on the background. This invokes the menu. (If you have a
+two-button mouse, try clicking both buttons simultaneously).
 
-If, after reading this, you still think that Sawfish isn't working,
-please send mail describing the problem to the Sawfish mailing list
- email{sawfish-list@@gnome.org}
-
-
- item How do I add customizations?
-
-There are several files controlling this:
-
- table @file
- item ~/.sawfishrc and ~/.sawfish/rc
-Hand written lisp code, loaded at startup. This is where almost all
-explicit customization should be done. You can choose using a stand
-alone file @file{.sawfishrc} or a @file{rc} file inside the
- file{ sawfish} directory to keep a more compact layout. This will be
-referenced @file{.sawfish[/]rc} as shorthand.
-
- item sawfish-defaults
-This lisp library is only loaded if there's no @file{.sawfish[/]rc} file.
-
- item ~/.sawfish/custom
-This stores customizations created by the configuration tool; it
+Why this is so? Because Sawfish is minimal - Sawfish is a @emph{window
+manager} and as such is not responsible for setting the background,
+starting programs or displaying a pager --- these can all be done
+using separate applications (e.g. by using a desktop environment such
+as Gnome).
+
+ item How do I customize Sawfish?
+
+There're two ways, by the configurator GUI and by preparing lisp
+code. The GUI can be run by middle-clicking background ->
+``Customize''. Most customizations similar to other window managers
+can be done through GUI.
+
+For customizations by lisp, first understand that in the startup, three
+files are read, in the order: @file{sawfish-defaults},
+ file{~/.sawfish/custom}, @file{.sawfishrc}.
+
+ table @asis
+ item @file{sawfish-defaults}
+This is a system default lisp library. It loads some of the common
+window manager features. More precisely, it currently does:
+
+ itemize
+ item Gnome setup, by opening @code{sawfish.wm.gnome.integration},
+if Gnome is running.
+ item Error handling enhancements, by opening
+ code{sawfish wm ext error-handler}
+ end itemize
+ item @file{~/.sawfish/custom}
+This stores customizations created by the configurator GUI; it
 shouldn't really be edited manually.
 
-This file is loaded @emph{after} @file{sawfish-defaults}, but @emph{before}
- file{ sawfish[/]rc}.
- end table
-
-
- item I created @file{.sawfish[/]rc}, now things have changed?
-
-If a @file{~/.sawfish[/]rc} file exists, it prevents
- file{sawfish-defaults} from being loaded. But it's
- file{sawfish-defaults} that loads some of the common window manager
-features, so add the line
+ item @file{~/.sawfish/rc}  or @file{~/.sawfishrc}
+This is the file you edit. It is a hand written lisp code, and almost
+all explicit customization should be done here.
+
+Choose either @file{~/.sawfish/rc} or @file{~/.sawfishrc}. The
+former is recommended, because the directory @file{~/.sawfish} is
+anyway created to store @file{custom}, and you can also put other lisp
+scripts, like user-contributed codes there.
+
+If this file is present, then @file{sawfish-defaults} isn't read by
+default. But it loads standard features, so if you want it, add the
+following line to your @file{~/.sawfishrc} (or @file{~/.sawfish/rc})
+file:
 
 @lisp
 (require 'sawfish-defaults)
 @end lisp
 
- noindent to your @file{.sawfish[/]rc} file if you want to start with all
-the standard features loaded.
-
-
- item What's this @code{sawfish-client} program?
-
-This allows you to connect to a window manager process and evaluate
-arbitrary Lisp forms. Do @samp{sawfish-client -?} for more details
-(@samp{sawfish-client -} for a read-eval-print loop)
-
-By default you can only connect from the host running the wm (through a
-unix-domain socket). To enable the network based server, evaluate the
-lisp form @code{(server-net-init)}.
-
-Note however that this connects through the X server, meaning that
-anyone who can open windows on your display can also execute any Lisp
-code on the host running the window manager (and by extension,
- emph{execute any program}).
-
-So @emph{don't} run the net server with X access control disabled
-(unless you're not connected to a network)
-
+In fact, @file{sawfish-defaults} is an alias of @file{sawfish.wm.defaults}.
+ end table
 
 @item How do I bind a key to execute a shell command?
 
@@ -137,20 +99,21 @@
 See the @samp{Popup Menus} node in the Info manual (@pxref{Popup
 Menus})
 
+ item How do I compile Lisp files?
 
- item How do I restart Sawfish?
-
-From a shell lauch the following command: @code{sawfish-client -q -f restart}
-
-
- item How do I read the Info manual?
+Use the shell command:
 
-Either execute the command @samp{info sawfish}, or enter the Info mode
-within Emacs (@kbd{C-h i}) and type @kbd{g (sawfish) RET}.
+ example
+sawfish --batch -l compiler -f compile-batch @var{files dots{}}
+ end example
 
-If you're using Gnome, then try executing @samp{gnome-help-browser
-info:sawfish}.
+ noindent where @var{files dots{}} are the names of the files you want
+to compile. They will normally have @file{.jl} suffixes, the compiler
+will create associated files with @file{.jlc} suffixes containing the
+compiled Lisp code.
 
+Remember that always the latest code is read, i.e., if the source is
+newer than the byte compiled file, the source is used, unlike emacs.
 
 @item How do I create a new theme?
 
@@ -186,6 +149,27 @@
 languages. Get the latest @code{gtk-engines} from
 @url{ftp://ftp.gnome.org/}
 
+ item What's this @code{sawfish-client} program?
+
+This allows you to connect to a window manager process and evaluate
+arbitrary Lisp forms. Do @samp{sawfish-client -?} for more details
+(@samp{sawfish-client -} for a read-eval-print loop)
+
+By default you can only connect from the host running the wm (through a
+unix-domain socket). To enable the network based server, evaluate the
+lisp form @code{(server-net-init)}.
+
+Note however that this connects through the X server, meaning that
+anyone who can open windows on your display can also execute any Lisp
+code on the host running the window manager (and by extension,
+ emph{execute any program}).
+
+So @emph{don't} run the net server with X access control disabled
+(unless you're not connected to a network).
+
+ item How do I restart Sawfish?
+
+From a shell lauch the following command: @code{sawfish-client -q -f restart}
 
 @item Why don't you use GUILE?
 
@@ -195,7 +179,7 @@
 autoloading, built-in event-loop, @dots{})
 
 But before you flame me: yes I do think scheme is a more elegant
-language
+language.
 
 
 @item Will you add feature @var{x}?
@@ -215,17 +199,6 @@
 window).
 
 
- item Is there a Sawfish mailing list?
-
-Yes. Please subscribe at @url{http://mail.gnome.org/mailman/listinfo/sawfish-list}. 
-You can browse the archives at @url{http://mail.gnome.org/archives/sawfish-list/}.
-
-
- item Is there a Sawfish IRC channel?
-
-Yes, there is. Join @code{#sawfish} on @code{irc.freenode.net}.
-
-
 @item Why does Sawfish look weird/crash on Solaris?
 
 Sawfish works stably on Solaris, but you may need to do two things:
@@ -239,12 +212,12 @@
 Recompile GTK+ using the @samp{--disable-xim} option to configure
 @end enumerate
 
-
 @item Why don't some windows ever get focused?
 
-If you don't have the option `give focus to windows even when they
-haven't asked for it' set to nil (define-special-variable ignore-window-input-hint nil),
-then windows that don't ask for focus don't get it.
+If you don't have the option ``give focus to windows even when they
+haven't asked for it'' set to nil (define-special-variable
+ignore-window-input-hint nil), then windows that don't ask for focus
+don't get it.
 
 Windows ask to receive focus by setting their WM_HINTS property
 appropriately; for example if I xprop a gnome-terminal:
@@ -283,18 +256,43 @@
 files that you have installed locally.
 
 
- item How do I compile Lisp files?
+ item Historical question: Why is it now called @emph{Sawfish}?
 
-Use the shell command:
+Because the old name (@samp{Sawmill}) was already being used by another
+company, who were in the process of registering it as a trademark.
 
- example
-sawfish --batch -l compiler -f compile-batch @var{files dots{}}
- end example
+The rename should be mostly painless, all old binaries still work for
+the time being, but will be phased out over time (final phasing out
+started around 1.5.0). Where before you would execute a program called
+ file{sawmill*}, replace it by @file{sawfish*}. E.g. @file{sawmill}
+becomes @file{sawfish}, and @file{sawmill-client} becomes
+ file{sawfish-client} 
 
- noindent where @var{files dots{}} are the names of the files you want
-to compile. They will normally have @file{.jl} suffixes, the compiler
-will create associated files with @file{.jlc} suffixes containing the
-compiled Lisp code.
+Your @file{~/.sawmill} directory will automatically be renamed
+ file{~/.sawfish} unless it would overwrite an existing file. Only
+user configuration @file{~/.sawfish[/]rc} will be checked currently,
+ file{~/.sawmillrc} is not used anymore (it was also read up to
+version 1.3.5).
+
+My apologies for any inconvenience caused.
+
+ item Historical question: But why @emph{Sawfish}, and not <insert your favourite
+alternative>?
+
+Well I had to choose something! And hopefully it satisfies the main
+requirements:
+
+ itemize @bullet
+ item There are no other computer-related users of the name (as checked
+in April 2000,)
+
+ item It's similar enough to the old name to hopefully carry some
+recognition across,
+
+ item It has no tenuous relationship to window-managing.
+ end itemize
 
+Incidentally, there was no meaning to the name ``Sawmill'', the author
+grepped @file{/usr/dict/words} for something containing ``wm''.
 
 @end enumerate

Modified: trunk/man/sawfish.texi
==============================================================================
--- trunk/man/sawfish.texi	(original)
+++ trunk/man/sawfish.texi	Thu Apr  2 19:13:25 2009
@@ -3,10 +3,10 @@
 @settitle sawfish Programming Manual
 @footnotestyle end
 
- set EDITION 0.13
- set VERSION 1.3.5
- set UPDATED 16 Dec 2008
- set UPDATE-MONTH Dec 2008
+ set EDITION 0.14
+ set VERSION 1.5.0
+ set UPDATED 28 Mar 2009
+ set UPDATE-MONTH Mar 2009
 
 @ifinfo
 @direntry
@@ -151,9 +151,7 @@
 instead of dynamic scope. This manual assumes at least a basic
 knowledge of the language.
 
- c Incidentally, there is no meaning to the name ``Sawmill'', the author
- c grepped @file{/usr/dict/words} for something containing ``wm''.
-
+Homepage and mailing list are listed in @xref{FAQ}.
 
 @node News, Colors, Introduction, Top
 
@@ -243,8 +241,8 @@
 
 Sawfish supports two types of fonts: X11 core fonts (fontsets and
 fontstructs) and Xft fonts.  Calling code must look up fonts by
-giving both a name and a type: an @code{"xlfd"} argument indicates the
-core fonts, and @code{"Xft"} indicates Xft fonts.  These types are
+giving both a name and a type: an @code{xlfd} argument indicates the
+core fonts, and @code{Xft} indicates Xft fonts.  These types are
 always literal strings.
 
 @defun font-type-exists-p type
@@ -255,8 +253,8 @@
 @defun get-font-typed type name
 Return a font object representing the X11 font specified by the string
 @var{name}.  Argument @var{type} indicates the type of font to look
-for; it must be one of the strings @code{"xlfd"} for a X11 core fonts
-(based on fontsets or a fontstructs), or @code{"Xft"} for an Xft font.
+for; it must be one of the strings @code{xlfd} for a X11 core fonts
+(based on fontsets or a fontstructs), or @code{Xft} for an Xft font.
 
 Signals an error if @var{type} is not one of the literal strings
 listed above.  Also signals an error if no font named @var{name}
@@ -280,8 +278,8 @@
 @end defun
 
 @defun font-type font
-Returns a string indicating the font's class.  This is @code{"xlfd"}
-for X11 core fonts, or @code{"Xft"} for Xft fonts.
+Returns a string indicating the font's class.  This is @code{xlfd}
+for X11 core fonts, or @code{Xft} for Xft fonts.
 @end defun
 
 @defun font-height font
@@ -769,7 +767,6 @@
 Return a list of symbols defining the X11 window manager protocols
 supported by client @var{window}.
 @end defun
-
 @defun window-supports-wm-protocol-p window atom
 Return true if @var{window} includes @var{atom} in its
 @code{WM_PROTOCOLS} property.
@@ -789,6 +786,7 @@
 * Iconifying Windows::
 * Window Stickiness::
 * Ignored Windows::
+* Avoided Windows::
 * Maximizing Windows::
 * Animating Windows::
 * Cycling Between Windows::
@@ -832,6 +830,7 @@
 If the optional third argument @var{checker} is non-nil, then @var{checker}
 is returned if the requested property does not exist. This is used to
 distinguish the assigned value of @code{nil} from property's absence.
+A symbol is usually a good choice for @var{checker}.
 @end defun
 
 @defun map-window-properties function window
@@ -843,7 +842,7 @@
 
 @defun window-plist window
 Returns the property list of the window @var{window} which is of the form
- code{(prop value prop value ...)}. 
+ code{(prop value prop value ...)}.
 
 Do not attempt to change properties by modifying the property list in place.
 Use window-put instead.
@@ -887,7 +886,7 @@
 Return the list of windows that window @var{child} is a transient
 for.  If @var{indirectly} is true, then return the list of all
 ancestors rather than parents.
- end defun 
+ end defun
 
 @defun transient-children parent &optional indirectly
 Return the list of windows that are transients for window
@@ -1556,7 +1555,7 @@
 @deffn Function lower-window* window
 @deffnx Command lower-window window
 Lower @var{window} and possibly associated windows to the bottom of
-their stacking depths. 
+their stacking depths.
 @end deffn
 
 @deffn Function raise-window* window
@@ -1830,7 +1829,6 @@
 When a managed window is destroyed, the @code{destroy-notify-hook} will
 subsequently be invoked (@pxref{Standard Hooks}).
 
-
 @node Shading Windows, Iconifying Windows, Destroying Windows, Windows
 @section Shading Windows
 @cindex Shading windows
@@ -2008,9 +2006,10 @@
 for all environments.
 @end defun
 
- node Ignored Windows, Maximizing Windows, Window Stickiness, Windows
+ node Ignored Windows, Avoided Windows, Window Stickiness, Windows
 @section Ignored Windows
 @cindex Windows, ignored
+ cindex ignored
 
 Sawfish has a general concept of ``ignored'' windows; the user does
 not interact normally with those windows.  The concept is actually
@@ -2098,10 +2097,10 @@
  end defun
 
  menu
-* Simple Maximization::         
-* Maximizing Without Overlap::  
-* Maximizing Without Borders::  
-* Unmaximizing::                
+* Simple Maximization::
+* Maximizing Without Overlap::
+* Maximizing Without Borders::
+* Unmaximizing::
  end menu
 
  node Simple Maximization, Maximizing Without Overlap, Maximizing Windows, Maximizing Windows
@@ -2166,7 +2165,7 @@
  @code{bottom-border}, @code{left-border}, @code{right-border},
  @code{top-left-border}, @code{top-right-border},
  @code{bottom-left-border}, @code{bottom-right-border}, or
- @code{title} 
+ @code{title}
  end defun
 
  defvar maximize-raises
@@ -2248,83 +2247,87 @@
 The ``fullscreen'' category maximizes the window to the current
 screen.
 
- deffn Command maximize-window-fullscreen window
+ deffn Function maximize-window-fullscreen window
+ deffnx Command maximize-window-fullscreen window
 Maximize both dimensions of @var{window} on the screen, removing
 window decorations and making the window edges flush with the screen
 sides.
 
-If defined, @var{direction} may be either @code{vertical} or
+If defined, @var{direction} is a symbol, either @code{vertical} or
 @code{horizontal}, and maximization will only occur for that
 direction.
- end deffn
+ end deffn
 
- deffn Command maximize-window-fullscreen-toggle window
+ deffn Function maximize-window-fullscreen-toggle window
+ deffnx Command maximize-window-fullscreen-toggle window
 Toggle the state of @var{window} between maximized and unmaximized in
 the screen, removing window decorations and making the window edges
 flush with the screen sides.
 
-If defined, @var{direction} may be either @code{vertical} or
+If defined, @var{direction} is a symbol, either @code{vertical} or
 @code{horizontal}, and maximization will only occur for that
 direction.
- end deffn
+ end deffn
 
 The ``fullxinerama'' category maximizes the window to the entire
 Xinerama display.
 
- deffn Command maximize-window-fullxinerama window
+ deffn Function maximize-window-fullxinerama window
+ deffnx Command maximize-window-fullxinerama window
 Maximize both dimensions of @var{window} across all Xinerama screens,
 removing window decorations and making the window edges flush with the
 screen sides.
 
-If defined, @var{direction} may be either @code{vertical} or
+If defined, @var{direction} is a symbol, either @code{vertical} or
 @code{horizontal}, and maximization will only occur for that
 direction.
- end deffn
+ end deffn
 
- deffn Command maximize-window-fullxinerama-toggle window
+ deffn Function maximize-window-fullxinerama-toggle window
+ deffnx Command maximize-window-fullxinerama-toggle window
 Toggle the state of @var{window} between maximized and unmaximized
 across all Xinerama screeens, removing window decorations and making
 the window edges flush with the screen sides.
 
-If defined, @var{direction} may be either @code{vertical} or
+If defined, @var{direction} is a symbol, either @code{vertical} or
 @code{horizontal}, and maximization will only occur for that
 direction.
- end deffn
+ end deffn
 
- node Unmaximizing,  , Maximizing Without Borders, Maximizing Windows
- subsection Unmaximizing
+ node Unmaximizing,  , Maximizing Without Borders, Maximizing Windows
+ subsection Unmaximizing
 
 One command restores windows from all the different types of
 maximization.
 
- deffn Command unmaximize-window window &optional direction
+ deffn Command unmaximize-window window &optional direction
 Restore the position and dimensions of @var{window} to their original,
 unmaximized, states.
 
 Positions and dimensions that were not maximized are not affected by
 unmaximizing.
- end deffn
 
- defun window-unmaximized-position window
+If defined, @var{direction} is a symbol, either @code{vertical} or
+ code{horizontal}, and maximization will only occur for that
+direction.
+ end deffn
+
+ defun window-unmaximized-position window
 Returns a cons-cell @code{(@var{x} . @var{y})} indicating the position
 that the @code{window} would unmaximize to.
 
 Sawfish preserves the positions of maximized axes only, so a
 vertically maximized window will be restored to its original @var{y}
 coordinate, but its @var{x} coordinate may have changed.
- end defun
+ end defun
 
- defun window-unmaximized-position window
+ defun window-unmaximized-dimensions window
 Returns a cons-cell @code{(@var{w} . @var{h})} indicating the
 dimensions that @code{window} would unmaximize to.
 
 Sawfish preserves the dimensions of maximized axes only, so a
 vertically maximized window will be restored to its original @var{h}
 dimension, but its @var{w} coordinate may have changed.
- end defun
-
- defun window-maximized-horizontally-p window
-Return @code{t} when @var{window} is horizontally maximized.
 @end defun
 
 @node Animating Windows, Cycling Between Windows, Maximizing Windows, Windows
@@ -2629,7 +2632,7 @@
 @defun window-group-menu &optional w
 Return a menu definition suitable for @code{popup-menu}.  This menu
 will allow the user to assign the window @var{w} into any group of a
-managed window, or into a brand new group.  The window's current group 
+managed window, or into a brand new group.  The window's current group
 is checked or otherwise marked.
 @end defun
 
@@ -2734,9 +2737,9 @@
 for the GUI, including such things as its required data type.
 
 @menu
-* Defgroup and Defcustom::      
-* Customization Files::         
-* Customized Variable Status::  
+* Defgroup and Defcustom::
+* Customization Files::
+* Customized Variable Status::
 @end menu
 
 @node Defgroup and Defcustom, Customization Files, Customization, Customization
@@ -4427,11 +4430,11 @@
 This is to handle the case where two windows of the same size are
 created one after the other, so that the user is sure to see (at least
 part of) both windows.
- end itemize
 
 @item @code{none}
 Make no changes to the window's position.  The window remains wherever
 the X server placed it initially.
+ end itemize
 
 @end defvar
 
@@ -4439,6 +4442,11 @@
 the window object as an argument, and manipulating its position with,
 e.g., @code{move-window-to}.
 
+The window to be placed avoids overlapping with already existing
+``avoided'' windows (@pxref{Avoided Windows}), unless
+the position is explicitly specified by coordinates, or placement mode
+ code{interactively} is used.
+
 @defvar stagger-placement-step
 In @code{stagger} placement mode, the distance down and to the right
 from the previously placed window to the new one.  This is measured
@@ -4455,32 +4463,6 @@
 placing windows.
 @end defvar
 
-``Avoided'' windows should be kept unobscured by other windows
-wherever possible.  In particular, first-fit and best-fit methods will
-attempt to place new windows away from them, and maximized windows
-will not stretch over them.
-
- defun window-avoided-p window
-Return t if @var{window} should be kept unobscured by other windows
-wherever possible.
- end defun
-
- defun avoided-windows &optional window
-Returns a list of all windows that should be left unobscured where
-possible.  If @var{window} is defined, then it defines a window that
-will be never returned in the list.
- end defun
-
- defvar dont-avoid-ignored
-When non-nil, ignored windows aren't avoided by default.  Defaults to
-non-nil.
- end defvar
-
- defvar avoid-by-default
-When non-nil, any unspecified windows are avoided by default.
-Defaults to nil.
- end defvar
-
 You can define your own placement modes.
 
 @defun define-placement-mode name fun &keywords for-normal for-dialogs
@@ -4868,14 +4850,12 @@
 After triple-clicking with the @key{Alt} key held down, Sawfish will
 receive a @kbd{Alt-Off3} event.
 
-
 @defvar multi-click-delay
 An integer indicating the maximum number of milliseconds between
 successive clicks.  Defaults to 250 milliseconds at startup; if
 @code{nil}, Sawfish uses 250 milliseconds.
 @end defvar
 
-
 @node Event Matching, Synthetic Events, Event Actions, Events
 @section Event Matching
 @cindex Event Matching
@@ -4929,7 +4909,7 @@
 @menu
 * Old-style Command Definition::  Emacs-Lisp style
 * New-style Command Definition::  Common-Lisp style
-* Interactive Calling Specification::  
+* Interactive Calling Specification::
 * Operations on Commands::	Accessors and the like
 * Invoking Commands::           call-commmand, command hooks
 * Default Commands::            Sawfish ships with a few commands
@@ -5394,7 +5374,7 @@
 
 If there is a mouse update current event, the position is read
 directly from that event.  Otherwise it is read from the server.  If
- var{from-server} is non-nil then the position is read directly from 
+ var{from-server} is non-nil then the position is read directly from
 the server in any case.
 @end defun
 
@@ -6013,7 +5993,7 @@
 @defvrx {Window Hook} after-resize-hook
 Called after completion of an interactive move or resize.  In addition
 to the window, the hook is called with a list of symbols indicating how
-the window was moved or resized: 
+the window was moved or resized:
 @code{horizontal} and @code{vertical} for movement,
 @code{right}, @code{left}, @code{bottom} and @code{top} for resizing.
 @end defvr
@@ -6237,11 +6217,12 @@
 @vtable @code
 
 @item ignored
-When set, the window is ignored in many operations.
+When set, the window is ignored in many operations. @xref{Ignored
+Windows}.
 
 @item avoid
-When set, the window will not be covered when maximizing, or when
-placing using the first-fit or best-fit methods
+When set, the window will not be covered by other windows when they
+are maximized or newly placed. @xref{Avoided Windows}.
 
 @item workspaces
 A list of integers defining the workspaces that the window is a member of, or
@@ -6439,7 +6420,7 @@
 @end defun
 
 @defun x-configure-window window attrs
-Reconfigure the window associated with @var{window}.  @var{Attrs} is 
+Reconfigure the window associated with @var{window}.  @var{Attrs} is
 an alist mapping attribute names to values.  Allowed attribute names
 are @code{x}, @code{y}, @code{width}, @code{height} and
 @code{border-width}.
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]