-
-
-
-
- Next: Next: 4. Graphical styles - Up: Up: Configuring and extending Ion3 - Previous: Previous: 2. Preliminaries: Key concepts - Contents - Index
-
-
-
-
+There are some other options as well; see the documentation +for ioncore.set for details.
-Next we load the configuration for Ion's core, and some kludges: +As a next step, in the actual cfg_ion.lua file, we load +cfg_defaults.lua. However, it is merely a conveniency file for +doing exactly what we will going through below, and what is commented +out in the actual file. If you do not want to load what +cfg_defaults.lua loads, just comment out the corresponding +line, and uncomment the lines for the files that you want:
+--dopath("cfg_defaults")
dopath("cfg_ioncore")
dopath("cfg_kludges")
+dopath("cfg_layouts")
@@ -298,6 +314,8 @@ expression that is used to match against the title and the next is a rule to construct a new title of a match occurs. This particular rule is used to shorten e.g. 'Foo: barbaz<3>' to 'barba...<3>'; for details see the function reference entry for ioncore.defshortening. +Finally, cfg_layouts.lua defines some workspace layouts, available +through the F9 workspace creation query.
To actually be able to do something besides display windows in full screen @@ -305,22 +323,14 @@ mode, we must next load some modules:
-dopath("cfg_modules")
---dopath("mod_query")
---dopath("mod_menu")
---dopath("mod_tiling")
---dopath("mod_statusbar")
+dopath("mod_query")
+dopath("mod_menu")
+dopath("mod_tiling")
+dopath("mod_statusbar")
--dopath("mod_dock")
---dopath("mod_sp")
+dopath("mod_sp")
--We actually load there another file listing the default selection of -modules. If you only want to load additional modules, just uncomment -the corresponding line. If you want to disable loading some modules, -comment out the the line loading cfg_modules, and uncomment -the lines for the modules you want, or add more. -
Shift, Control, Mod1 to Mod5, AnyModifier and Lock. - - - - - + + + + +
X allows binding all of these modifiers to almost any key and while this list of modifiers does not explicitly list keys such as -Alt that are common on modern keyboards, such +Alt that are common on modern keyboards, such keys are bound to one of the ModN. On systems running XFree86 Alt is usually Mod1. On Suns Mod1 is the diamond key and Alt something else. One of the ''flying window'' keys on so called Windows-keyboards is probably mapped to Mod3 if you have -such a key. Use the program xmodmap +such a key. Use the program xmodmap to find out what exactly is bound where.
@@ -614,10 +624,10 @@ default.
Ion ignores the Lock modifier and any ModN () -bound to NumLock or -ScrollLock +bound to NumLock or +ScrollLock by default because such3.2 locking keys may otherwise + HREF="#foot850">3.2 locking keys may otherwise cause confusion.
@@ -630,7 +640,7 @@ cause confusion. Button specifications are similar to key definitions but now instead of specifying modifiers and a key, you specify modifiers and one of the button names Button1 to -Button5. Additionally the +Button5. Additionally the specification may end with an optional area name following an @-sign. Only frames currently support areas, and the supported values in this case are @@ -681,10 +691,10 @@ to it is available virtually everywhere.
- - - - + + + + In the stock configuration file setup, menus are defined in the file cfg_menus.lua as previously mentioned. The mod_menu module must be loaded for one to be able to define menus, and this is done with @@ -821,7 +831,7 @@ handlers (and elsewhere): after which the selected entry is activated. This function is meant to be used for implementing, for example, Win***s-style Alt-Tab handling.3.3
-The so-called ''winprops'' can be used to change how +The so-called ''winprops'' can be used to change how specific windows are handled and to set up some kludges to deal with badly behaving applications. They are defined by calling the function defwinprop with a table containing the properties to set and the @@ -867,7 +877,7 @@ usual method of identifying windows, and how to obtain this information.
- -
- -
- -
- -
- -
-
+Additionally, the winprops +max_size, +min_size, +aspect, +resizeinc, +and +ignore_max_size, +ignore_min_size, +ignore_aspect, +ignore_resizeinc, +may be used to override application-supplied size hints. The four +first ones are tables with the fields w and h, indicating +the width and height size hints in pixels, and the latter ignore +winprop is a boolean. + +
+Finally, the boolean +userpos option may be used to +override the USPosition flag of the size hints. Normally, +when this flag is set, Ion tries to respect the supplied window +position more than when it is not set. Obviously, this makes sense +only for floating windows. + +
+ +
The identification information in the winprop specification is usually the -class, -role, -instance and +class, +role, +instance and name of the window. The name field is a Lua-style regular expression matched against the window's title and the rest are strings that must @@ -1223,8 +1189,8 @@ the same but different name, the longest match is chosen.
-
@@ -1233,7 +1199,7 @@ can be used to list the identification information required to set winprops for a window and all the transient windows managed within it.
- + Another way to get the identification information is to use xprop. Simply run To get class and instance, simply run xprop WM_CLASS and click on the particular window of interest. The class is the latter of @@ -1242,7 +1208,7 @@ windows have this property - use the command xprop WM_ROLE. This method, however, will not work on transients.
- + So-called ''transient windows'' are usually short-lived dialogs (although some programs abuse this property) that have a parent window that they are ''transient for''. On tiled workspaces Ion displays these windows @@ -1251,7 +1217,7 @@ Unfortunately xprop is stupid and can't cope with this situation, returning the parent window's properties when the transient is clicked on. For this reason you'll have to do a little extra work to get the properties for that window.3.4 + HREF="#foot1464">3.4
Finally, it should be mentioned that too many authors these days ''forget'' to set this vital identification to anything meaningful: @@ -1260,14 +1226,14 @@ windows, for example.
-
-
@@ -1284,8 +1250,8 @@ defwinprop{
-
@@ -1313,8 +1279,8 @@ defwinprop{
-
@@ -1351,26 +1317,26 @@ default name formed from the frame's class name and an instance number.
-
-
-
-