2
.\" Man page for Fluxbox
4
.\" Copyright (c) 2000 by Wilbert Berendsen <wbsoft@xs4all.nl>
5
.\" Copyright (c) 2001 by Matthew Hawkins <matt@mh.dropbear.id.au>
7
.\" Permission to use, copy, modify, and distribute this documentation for
8
.\" any purpose with or without fee is hereby granted, provided that the
9
.\" above copyright notice and this permission notice appear in all copies.
11
.\" THE DOCUMENTATION IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
12
.\" WARRANTIES WITH REGARD TO THIS DOCUMENTATION INCLUDING ALL IMPLIED
13
.\" WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
14
.\" AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
15
.\" DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
16
.\" PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
17
.\" TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
18
.\" PERFORMANCE OF THIS DOCUMENTATION
20
.\" Parts of the text are taken from website and several README's
21
.\" by His Great Hughesness himself. Why reinvent wheels?
23
.\" Created with NEdit, tested with ``man'' and ``tkman.''
24
.\" This manpage uses only standard groff and tmac.an macros.
25
.\" To all translators who didn't do manpages earlier (like me ;-):
26
.\" Read the Man-Page-Mini-HOWTO and the LDP manpage ``man 7 man''
27
.\" There's all I needed to know about these macros.
29
.\" Updated for bb 0.61 at Sat Sep 9 06:56:04 CEST 2000
31
.\" Changed to fluxbox by Henrik Kinnunen (fluxgen@linuxmail.org)
33
.\" Updated for fluxbox 0.1.5 by Matthew Hawkins <matt@mh.dropbear.id.au>
35
.\" Updated for version 0.1.6 by Rando Christensen <eyez@babblica.net>
37
.\" Updated for version 0.1.7.1 by Stanislav Karchebny <berk@madfire.net>
39
.\" Updated for version 0.1.15 by Tobias Klausmann <klausman@users.sourceforge.net>
41
.\" Updating for version 0.9.10 by <grubert@users.sourceforge.net>
43
.\" ..define sort of <blockquote><pre> macro
57
.TH fluxbox 1 "August 16th, 2004" "0.9.9"
59
fluxbox \- a window manager for X11
61
.BR fluxbox " \-help | \-version"
64
.RI "[ \-rc" " rcfile " "] [ \-display" " display " ]
67
.\" Phirst Phew ParagraPhs taken from blackbox.alug.org
69
Fluxbox is yet another addition to the list of window managers for the Open
70
Group's X Window System, Version 11 Release 6 and above.
71
Fluxbox is built with C++, based on the sources of Blackbox 0.61.0.
74
Fluxbox provides configurable window decorations, a root menu to launch
75
applications and a toolbar that shows the current workspace name, the focused
76
application name and the current time.
77
There is also a workspace menu to add or remove workspaces. The `slit' can be
78
used to dock small applications, e.g. most of the bbtools can use the slit.
80
Fluxbox will iconify windows to the toolbar, in addition to adding the window
81
to the `Icons' submenu of the workspace menu. One click and they reappear.
82
A double-click on the titlebar of a window will shade it i.e. the window will
83
disappear, only the titlebar stays visible.
85
Fluxbox uses its own graphics class to render its images on the fly.
86
By using style files, you can determine at a great level how your desktop looks
87
like. Fluxbox styles are compatible with those of Blackbox, so users migrating
88
can still use their current favourite themes.
90
.\" TODO wmhints support
91
.\" TODO KDE2 GNome support
92
Currently KDE WM hints are not supported, but Fluxbox is already prepared to
93
support the new window manager specification that is now being developed for
94
both Gnome and KDE2.0.
96
Fluxbox supports the following commandline options:
99
Display command line options , then exit.
102
Display version info and exit.
105
Use another rcfile than the default
106
.IR "~/.fluxbox/init" .
108
.BI \-display \ display
109
Start Fluxbox on the specified display.
110
Programs started by Fluxbox will have the
112
environment variable set to this value, too.
115
Display some useful information (defaults and compiled-in features) and exit.
118
Log output to the specified file.
119
.\" ---------------------
121
This program is usually started by the user's startup script, most times called
123
To run fluxbox, modify the script by adding
127
as the last executed command of the script.
128
When Fluxbox terminates, the X session will terminate too.
130
When started, Fluxbox will try to find a default menufile in
131
.IR @pkgdatadir@/menu .
132
You can provide a system-wide menu for your users here.
134
On exit or restart, Fluxbox will save user defaults in the file
136
in the user's home directory.
137
Some resources in this file can be edited by hand.
138
.\" -----------------------
140
Fluxbox includes keyboard handling. In order to customize your keybindings,
143
as described below in the section KEYS FILE.
144
.SS Root window (background):
145
Right click (button 3) will pop up the root menu.
146
With this you can launch your applications.
147
You can customize this menu for your needs.
148
A middle click (button 2) pops up the workspace menu.
149
You can add or remove a workspace, view
150
applications running on all workspace, inspect your icons, and jump directly to
151
any workspace or application.
153
Left clicking (button 1) on an application in the Workspaces menu will bring
154
you to that workspace and raise/focus that application;
155
middle clicking (button 2) will warp the application to the current workspace.
157
The toolbar contains up to eight fields/tools: a workspace name, the iconbar, the systemtray,
158
a clock and arrows for previous and next workspace and windows.
160
The contents can be configured in fluxbox init-file in the entry
162
session.screen0.toolbar.tools: clock, iconbar, workspacename
164
or the toolbar can be turned off by
166
session.screen0.toolbar.visible: false
168
.\" A left click on the toolbar will bring it to the foreground, a
169
.\" middle click will hide it behind other windows (if AlwaysOnTop is not set), and
170
.\" the right button brings up a little menu.
171
Clicking the workspace name brings up the toolbar menu.
172
Using the wheel on workspace name or the clock switches the workspace, this
173
could also be enabled for the whole desktop in the fluxbox menu.
177
is enabled, dragging a window outside the desktop will change to the next desktop.
179
Using the toolbar menu you can enter a name for the current workspace (when finished,
181
One can choose the toolbar's position, in which layer it should be see LAYERs below
182
and if it should hide when the mouse leaves it.
183
The iconbar mode is also set via this menu: None, Icons -- Icons from all
184
workspaces, Workspace Icons, Workspace -- all windows from Workspace, All Windows --
187
Fluxbox manages following layers: Above Dock, Dock, Top, Normal, Bottom, Desktop.
188
Presumably the list is from top to bottom. Slit and toolbar can be assigned to
189
a layer with the menu, applications might be assigned to a layer in the apps file.
190
.\" TODO the apps file has numbers for layers
192
The window that has the focus is the one that recieves keys and mouse events.
193
The focus model is selectable via the Configuration menu.
197
The window must be clicked to get the focus.
200
the focus is transferred to the window under the mouse, after some delay.
203
tabbed windows are activated by moving the mouse into the tab.
204
.SS Window Titlebar and Borders:
205
A left click on any place of the window's border, will raise it.
206
Dragging then moves the window.
207
Dragging the resize grips at the left-bottom and right-bottom
208
corners resizes the window.
209
Middle clicking on border or titlebar will immediately lower the window.
210
Right clicking on border or titlebar pops up the window menu,
211
containing these commands:
213
.B Send To... (in 0.9.7)
214
Send window to another workspace.
215
When you select the workspace with the middle button, Fluxbox will
216
send you along with the application to the selected workspace
219
Shade the window (display titlebar only)
223
The `icon' can be found in the `Icons' submenu of the workspace menu
224
as well as in the toolbar.
227
(Un)Maximize window. Depending on toolbar and slit configuration maximize does
228
cover slit and toolbar or not.
231
(usually left button) Maximize Normal, i.e. Vertical and Horizontal
234
(Un)Maximize window only vertically.
237
(Un)Maximize window only horizontal.
247
A stuck window will always be displayed in the current workspace
250
Activate next client in this window's group.
253
Activate prev client in this window's group.
256
Change the layer of this window.
259
Specify which window settings should be stored in the apps file.
262
Close the application cleanly
264
When you doubleclick on the titlebar of a window, it will `shade', so
265
that only the titlebar stays visible.
266
Another double click will redisplay the window contents.
268
In fluxbox, the window button's configuration is controlled by \ init
269
file entries. The default is:
271
session.titlebar.left: Stick
272
session.titlebar.right: Minimize Maximize Close
274
Clicking the minimize button with any button causes the window to be iconified.
275
Clicking the close button with any button closes the application.
276
The maximize button (if present) maximizes the window in three ways:
277
Button 1 causes full screen maximization, button 2 maximizes the window only
278
vertically, and button 3 only horizontally.
279
The Sticky button sets has the same meaning as the
283
Clicking button 3 in a menu will popdown the menu.
284
Clicking button 1 on the titlebar of any (sub)menu and then dragging it somewhere
285
else will cause the menu to stay visible and not disappear when you click on
288
When you want to drag a window, but cannot see either the bottom handle or its
289
titlebar, you can press Alt + button 1 anywhere in the window and then
291
You can also use Alt + button 1 to raise a partially visible window.
292
Finally, Alt + button 2 lowers a window, and Alt + button 3 resizes the window.
294
This can be disabled in the resource file
298
session.useMod1: \fItrue\fR or \fIfalse\fR
300
A default menu file is installed in
301
.IR @pkgdatadir@/menu .
302
Of course this system-wide menu can be customized for all users at once.
303
But it is also possible to create a personal menu.
304
It is a convention to create a directory
305
.IR "~/.fluxbox/" " (or " "~/fluxbox/" ")"
306
in your home directory, and to create a menu file, e.g.
308
in this directory, or copy the system-wide menu file to this location.
309
Next, we have to tell Fluxbox to load our menu file instead of the default.
310
This is accomplished by adding (or changing) a resource value in the
314
session.menuFile: ~/.fluxbox/menu
316
For this change to take effect, Fluxbox has to be restarted.
317
Be sure that your menu is usable, then choose `Restart' from the default
318
Fluxbox root menu. If only the contents of the menu file changed, only
322
A menu reload can also be forced by sending SIGUSR2.
324
The behaviour of the menu can be configured in the
326
file, with the following entries:
328
session.screen0.menuMode: can be either Click or Delay (default: Delay)
330
session.screen0.menuDelay: in msec (default: 0 )
332
session.screen0.menuDelayClose: in msec (default: 0 )
335
There are up to four fields in a menu line.
336
They are of the form:
338
[tag] (label or filename) {command or filename} <icon filename>
340
The supported tags are as follows:
342
.B [begin] (label for root menu)
343
This tells Fluxbox to start parsing the menu file.
344
This tag is required for Fluxbox to parse your menu file.
345
If it cannot find it, the system default menu is used instead.
348
This tells Fluxbox that it is at the end of a menu.
349
This can either be a submenu or the main root menu.
350
There must be at least one of these tags in your menu to correspond to the
351
required [begin] tag.
353
.B [exec] (label for command) {shell command}
354
Inserts a command item into the menu.
355
When you select the menu item from the menu, Fluxbox runs `shell command.'
357
.B [exit] (label for exit)
358
Inserts an item that shuts down and exits Fluxbox.
359
Any open windows are reparented to the root window before Fluxbox exits.
361
.B [include] (filename)
364
into the current menu. The file has to start with
370
can be the full path to a file or it can begin with
372
which will be expanded into your home directory (e.g.
374
[include] (~/fluxbox/stylesmenu)
377
.I /home/yourusername/fluxbox/stylesmenu
379
If the parameter to include directive is a directory, every file in this
380
path will be included.
382
.B [nop] (label - optional)
383
Insert a non-operational item into the current menu.
384
This can be used to help format the menu into blocks or sections
387
does accept a label, but it is not required, and a blank item will be used
391
will create a nice separator line.
393
.B [style] (label) {filename}
394
This tells Fluxbox to insert an item that, when selected, reads style file
397
and apply the new textures, colors and fonts to the current
400
.B [stylesdir] (directory name)
401
Reads all filenames from the specified directory, assuming that they are all
402
valid style files (directories are ignored), and creates menu items in the
403
current menu for every filename, that, when selected by the user, apply the
404
selected style file to the current session.
405
The labels that are created in the menu are the filenames of the style files.
407
.B [stylesmenu] (label) {directory name}
408
Creates a submenu entry with
410
(that is also the title of the new submenu), and inserts in that submenu all
411
filenames in the specified directory, assuming that they are all valid style
412
files (directories are ignored) in the same way as the
416
.RB Both\ [stylesdir] \ and\ [stylesmenu]
417
commands make it possible to install style files without editing your menu file.
419
.B [submenu] (label) {title for menu - optional}
420
This tells Fluxbox to create and parse a new menu.
421
This menu is inserted as a submenu into the parent menu.
422
These menus are parsed recursively, so there is no limit to the number of levels
423
or nested submenus you can have.
424
The title for the new menu is optional, if none is supplied,
425
the new menu's title is the same as the item label.
428
tag is required to end the submenu.
430
.B [reconfig] (label)
431
When selected, this item rereads the current style and menu files and
433
This is useful for creating a new style or theme, as you don't have to
434
constantly restart Fluxbox every time you save your style.
435
However, Fluxbox automagically rereads the menu whenever it changes.
437
.B [restart] (label) {shell command - optional}
438
This tells Fluxbox to restart.
439
If `shell command' is supplied, it shuts down and runs the command (which is
440
commonly the name of another window manager).
441
If the command is omitted, Fluxbox restarts itself.
444
Inserts a Fluxbox native submenu item, containing numerous configuration
445
options concerning window placement, focus style, window moving style etc.
447
.B [workspaces] (label)
448
This tells Fluxbox to insert a link to the workspaces menu directly
450
This is handy for those users who can't access the
451
workspace menu directly (e.g. if you don't have a 3 button mouse, it's
452
rather hard to middle click to show the workspace menu).
454
Any line that starts with a `#' is considered a comment and ignored by Fluxbox.
455
Also, in the labels/commands/filenames fields,
456
you can escape any character like so:
458
[exec] (\\(my cool\\) \\{XTERM\\}) {xterm -T \\"cool XTERM\\"}
460
Using `\\\\' inserts a literal back-slash into the label/command/filename field.
462
Now let's put together some things.
463
Here is a short example of a menu file:
468
[exec] (rxvt) {rxvt -ls} </usr/X11R6/share/icons/terminal.xpm>
469
[exec] (netscape) {netscape -install}
470
[exec] (The GIMP) {gimp}
472
[exec] (Vim) {rxvt -geometry 132x60 -name VIM -e screen vim}
473
[exec] (Mutt) {rxvt -name mutt -e mutt}
475
[exec] (browser) {mozilla -browser}
476
[exec] (news) {mozilla -news}
477
[exec] (mail) {mozilla -mail}
478
[exec] (edit) {mozilla -edit}
479
[exec] (compose) {mozilla -compose}
481
[submenu] (Window Manager)
482
[exec] (Edit Menus) {nedit ~/.fluxbox/menu}
483
[submenu] (Style) {Which Style?}
484
[stylesdir] (~/.fluxbox/styles)
485
[stylesmenu] (Fluxbox Styles) {@pkgdatadir@/styles}
487
[config] (Config Options)
488
[reconfig] (Reconfigure)
497
Fluxbox enables you to use specialized files that contain
499
resources to specify colors, textures, pixmaps and fonts, and thus
500
the overall look of your window borders, menus and the toolbar.
502
The default installation of Fluxbox provides some of these style files.
503
See fluxstyle(1) to accomodate the growing number of style components.
506
You can customise Fluxbox' key handling through the
508
file. The file takes the format of :
510
<modifier> <key> [...] :<operation>
512
In the example below, Mod1 is the 'Alt' key on the PC keyboard and Mod4 is
513
one of the three extra keys on a pc104 branded with a sickening corporate logo.
516
# Any line starting with a # is a comment.
527
Mod4 b :PrevWorkspace
529
Mod4 r :ExecCommand rxvt
530
Mod4 v :NextWorkspace
533
Control n Mod1 n :NextTab
535
As you can see from the last line, keybinds can be chained in a fashion similar
536
to emacs keybindings.
538
Commands are caseinsensitive, workspace numbering starts at "1", some commands
539
have synonyms, the space between the last key and the :Command is mandatory.
542
.B window manager commands
544
Restart \fIargument\fR
547
SetStyle \fIargument\fR
548
ExecCommand, Execute or Exec \fIcommand\fR
550
.B commands to currently focused window
552
Minimize, MinimizeWindow or Iconify
553
Maximize, MaximizeWindow
557
ResizeTo \fIwidth\fR \fIheight\fR
558
Resize \fIdelta-width\fR \fIdelta-height\fR
559
ResizeHorizontal \fIdelta-width\fR
560
ResizeVertical \fIdelta-height\fR
561
MoveTo \fIx\fR \fIy\fR
562
Move \fIdelta-x\fR \fIdelta-y\fR
563
MoveRight \fIdelta-x\fR
564
MoveLeft \fIdelta-x\fR
566
MoveDown \fIdelta-y\fR
573
SendToWorkspace \fInumber\fR : Sends the current window and takes you with it.
581
.B workspace commands
585
RightWorkspace \fIby-number\fR
586
LeftWorkspace \fIby-number\fR
587
Workspace \fInumber\fR
588
NextWindow \fIby-number\fR
589
PrevWindow \fIby-number\fR
590
NextGroup \fIby-number\fR
591
PrevGroup \fIby-number\fR
593
ShowDesktop - Iconifies all windows.
597
WorkspaceNameDialog - edit workspaces name dialog (old SetWorkspaceName)
598
SetWorkspaceName \fIname\fR
600
.B Prev/NextWindow Parameter
601
NextWindow and PrevWindow take an integer parameter.
603
0 or unspecified = Default/current behavior - no skipping
605
2 = Skip stuck windows
606
3 = Skip lower tabs/stuck windows
607
4 = Skip shaded windows
608
5 = Skip lower tabs/shaded windows
609
6 = Skip stuck windows/shaded windows
610
7 = Skip lower tabs/stuck windows/shaded windows
616
SetResourceValue \fIresourcename\fR \fIresource value\fR
617
BindKey \fIkey string : action\fR - this will append key string and
618
action to your keys file and bind the key
622
Since version 0.1.11, Fluxbox has a feature called autogrouping, that is apps are
623
automatically grouped together if they are in the same group.
624
You can create groups simply by editing the
625
.IR ~/.fluxbox/groups
627
The file takes the format of:
629
<app1> <app2> <app3> ... <appN>
631
where elements can be found with this command:
635
Just launch this command in a terminal and click on the desired app after. It will
636
tell you what to write as element.
637
Each line forms a different group, e.g:
642
This will create two groups, one with netscape and nedit, and one with xterm.
643
The new window will only group itself to other windows on the same workspace
644
and to the last window that was focused.
646
The slit is a special Fluxbox window frame that can contain dockable
647
applications, e.g. the `bbtools.'
648
When applications are run in the slit they have no window borders of their own;
649
instead they are framed in the slit, and they are always visible in the current
651
You can click button 3 on the edge of the slit window to get a menu to
652
determine its position, whether its contained applications should be grouped
653
horizontally or vertically and whether the slit should hide itself when the
656
Most dockable applications use the
658
option to run in the slit.
659
For example, you could put in your
666
Of course to use the slit you must have slit support compiled in.
669
Since version 0.1.10, Fluxbox has the capacity to launch dockapps in the order told
671
.IR ~/.fluxbox/slitlist
674
A simple procedure for getting the slit sequences the way you like it is:
676
1) Run fluxbox with no pre-loaded dockapps.
677
2) Run dockapps individually in the order you want them.
678
3) Re-add dockapps to your auto-run script, e.g. .xinitrc or .xsession. Order doesn't matter here!
680
This sequence will be saved by default to
681
.IR ~/.fluxbox/slitlist
682
and will be maintained in future fluxbox sessions.
684
Users are free to manually edit the slitlist file. It is a simple list of window names,
685
one per dockapp. Similar to the init file it should be edited while not running fluxbox.
686
Otherwise changes may get overwritten.
688
The user also has the option of choosing a different path for the slit list file.
689
The following example
691
file entry changes the path:
693
session.slitlistFile: /home/me/etc/slitsort
695
.SH CONFIGURATION MENU
696
Fluxbox has a few options that are configured by a configure menu.
697
Most are self-explanatory, but here are a few notes:
699
.B Sloppy Window Grouping
700
This option allows you to drop a window-title anywhere on the target window to group it,
701
instead of only on the target window's window-title.
703
.B Maximize Over Slit
704
This option makes maximized windows cover the Slit when they get maximized.
705
Turn this option off if you want your slit to stay visible at all times.
709
resource file is created and maintained by Fluxbox itself.
712
menu, the last selected style file, your workspace names and
713
so on are saved into this file.
714
However, there are some resources in it you might want to edit yourself:
717
This tells Fluxbox where to look for its menu file.
719
session.menuFile: /home/myself/.fluxbox/menu
723
This tells Fluxbox where to find the file describing the keybindings.
725
session.keyFile: /home/myself/.fluxbox/keys
728
.B session.styleFile:
729
This tells Fluxbox where to find the style (theme) file for this session.
731
session.styleFile: @pkgdatadir@/styles/Flux
734
.B session.groupFile:
735
This tells Fluxbox where to find the file for the autogrouping feature.
737
session.groupFile: /home/myself/.fluxbox/groups
740
.B session.slitlistFile:
741
This tells Fluxbox where to find the file that contains the order in which the apps are loaded in the slit.
743
session.slitlistFile: /home/myself/.fluxbox/slitlist
746
.B session.screen0.toolbar.tools:
747
This specifies the tools plugged into the toolbar.
749
workspacename, prevworkspace, nextworkspace, iconbar, systemtray, prevwindow, nextwindow,
753
session.screen0.toolbar.tools: clock, iconbar, workspacename
756
.B session.screen0.strftimeFormat:
757
This adjusts the way the current time is displayed in the toolbar.
761
The default value is:
764
.B session.screen0.rootCommand:
765
This overrides the style's rootCommand. When this value is set, it will keep
766
your background the same, regardless of what any style would like your
769
.B session.autoRaiseDelay:
770
Adjusts the delay (in ms) before focused windows will raise when using the
772
The default value is:
775
.B session.doubleClickInterval:
776
Adjust the delay (in ms) between mouse clicks for Fluxbox to consider a double click.
780
.B session.screen0.edgeSnapThreshold:
781
When moving a window across your screen, Fluxbox is able to have it `snap' to
782
the edges of the screen for easy placement.
783
This variable tells Fluxbox the distance (in pixels) at which the window will
789
This tells Fluxbox how much memory (in Kb) it may use to store cached pixmaps on
791
If your machine runs short of memory, you may lower this value.
795
.B session.cacheLife:
796
This tells Fluxbox how long (in minutes) unused pixmaps may stay in the X
801
.B session.opaqueMove:
802
When moving a window, setting this to
804
will draw the window contents as it moves (nasty on slow systems), if
806
it will only draw an outline of the window border.
808
.B session.imageDither:
812
to, respectively, enable or disable dithering of images. Only necessary
813
on systems with small colour depths (8bpp or less)
815
.B session.colorsPerChannel:
816
This tells Fluxbox how many colors to take from the X server on pseudocolor
817
displays. A channel would be red, green, or blue.
818
Fluxbox will allocate this variable ^ 3 colors and make them always available.
819
Value must be between 2 and 6.
820
When you run Fluxbox on an 8-bit display, you must set this resource to 4.
829
to enable or disable Fluxbox using the toolbar to display iconified windows.
831
.B session.*.iconbar.alignment:
835
can be changed in the iconbar mode menu. If LEFT or RIGHT is specified the
836
iconbar buttons have a fixed with and are left/right aligned.
838
.B session.*.iconbar.clientWidth:
840
is used to specify the iconbar button width for LEFT/RIGHT alignment.
842
.B session.*.iconbar.wheelMode:
847
On - enable mousewheeling on the iconbuttons
848
Off - disables mousewheeling on the iconbuttons
849
Screen - uses the settings of desktopWheeling
852
.B session.*.iconbar.deiconifyMode:
857
Current - deiconifies the window on current workspace
858
Follow - deiconifies the window on the workspace it
859
was iconified from and jumps to that workspace
860
SemiFollow - acts as 'Current' for windows that were actually
861
iconified, and as 'follow' for the others
869
to enable/disable Fluxbox's PWM-like window tabs. Tabs let you group windows
870
together, they will take up identical desktop space (windows smaller or larger
871
than the existing group size get resized automatically) and can be moved as a
872
group around the desktop or to a different workspace.
876
When running Fluxbox in a multiple desktop environment the
880
etc. for any appropriate desktop, and you can customise the behaviour of
881
Fluxbox on each desktop accordingly. A favourite of the man page author
882
with a dual-head Matrox G450 was to autohide the slit and toolbar on
883
screen0 and set it alwaysontop and not autohidden on screen1, with a
884
larger date format on screen1
886
session.screen0.toolbar.onTop: False
887
session.screen0.toolbar.autoHide: True
888
session.screen0.toolbar.placement: BottomCenter
889
session.screen0.toolbar.widthPercent: 42
890
session.screen0.slit.onTop: False
891
session.screen0.slit.autoHide: True
892
session.screen0.slit.placement: TopLeft
893
session.screen0.slit.direction: Vertical
894
session.screen0.strftimeFormat: %I:%M %p
895
session.screen1.toolbar.onTop: True
896
session.screen1.toolbar.autoHide: False
897
session.screen1.toolbar.placement: BottomCenter
898
session.screen1.toolbar.widthPercent: 69
899
session.screen1.slit.onTop: True
900
session.screen1.slit.autoHide: False
901
session.screen1.slit.placement: CenterRight
902
session.screen1.slit.direction: Vertical
903
session.screen1.strftimeFormat: %a %d %R [%s]
905
This way the main workspace (screen0) has the maximum amount of space available
906
and the secondary workspace could show the time and run some withdrawn apps like
907
gkrellm in the slit, always visible yet out of the way of real work.
909
.SH APPLICATIONS SETTINGS
910
Sometimes, you want to force an application to have always the same dimensions,
911
position, and other settings. It is now possible with the new window-submenu
912
called 'Remember...'. Settings are saved in the
914
file. You don't have to edit the file yourself as all manipulations can be
915
done using the 'Remember...' submenu.
918
Force the workspace of the application to be the current one, even if you launch
919
the application from another workspace.
921
.B Dimensions [Width Height]
922
Remember the current dimensions.
924
.B Position ([WINCENTER|CENTER|UPPERLEFT|UPPERRIGHT|LOWERLEFT|LOWERRIGHT]) [X Y]
925
Remember the current position. X and Y are relative to e.g. WINCENTER .
927
.B Shaded state [yes|no]
928
Remember the current shaded state.
930
.B Tab state [yes|no]
931
Remember the current tab state.
934
hides the app from the icon bar
937
hides the app from the list to be reachable via Next/PrevWindow
940
is [IconHidden] + [FocusHidden]
942
.B Decoration state [NONE|NORMAL|TOOL|TINY]
943
Remember the current decoration state.
945
.B Sticky state [yes|no]
946
Remember the current sticky state.
948
.B Jump to workspace [yes|no]
949
This one is only useful if 'Workspace' is set too. The workspace is changed
950
to the workspace containing the application being launched.
952
.B Save settings on close [yes|no]
953
By default, application settings are not saved when a window is closed. Set
954
this option if you want previous settings to be saved when the window is closed.
958
also allows to specify applications that should be started on fluxbox start
960
.B [startup] (options) {application}
963
could be used to specify the screen, not the workspace, on which
964
the application should started. startup is not yet setable by menu.
966
.SS Applications example
967
Here is a short example of an apps file:
972
[Dimensions] (WINCENTER) {1022 747}
978
[Dimensions] {1006 749}
987
Parameters in the 'apps' file are case-sensitive. Application names are taken
988
from the first X-Window WM_CLASS attribute. You can see this attribute by using
989
the xprop command. Transient windows are not affected by application settings.
997
file, and to resolve stylefile and \-directory names.
1000
When no other display was given on the command line, Fluxbox will start on the
1001
display specified by this variable.
1005
fluxbox loads the configuration,
1007
forces reloading of configuration and
1010
.SH AUTHOR and CREDITS
1011
Blackbox was written and maintained by Brad Hughes
1012
.nh \" hyphenation off
1019
Fluxbox is written and maintained by Henrik Kinnunen
1021
<fluxgen@linuxmail.org>
1023
with contributions and patches merged from
1024
many individuals around the world.
1026
The Official Fluxbox website:
1028
.B http://fluxbox.sf.net/
1031
Many compatible themes:
1033
.B http://themes.freshmeat.net/
1036
This manpage was put together by Matthew Hawkins
1038
<matt@mh.dropbear.id.au>
1040
from the original Blackbox man page by Wilbert Berendsen
1044
and subsequently hacked upon by Tobias Klausmann
1046
<klausman@users.sourceforge.net>
1048
<grubert@users.sourceforge.net>
1050
<asenchi@asenchi.com>
1053
Numerous other languages could be available if someone jumps in.
added
removed
doc/fluxbox.1.in
