User's configuration is located in $HOME/.NSCDE
- this place is what is referred as $FVWM_USERDIR
in this
documentation. There was no need to redefine this variable, since it server well for
NsCDE. If user has a plain FVWM configuration in $HOME/.fvwm
it will not be touched and can co-exist with NsCDE in that way. Here is the simple layout of things in
$FVWM_USERDIR
:
app-defaults/
directory:
X resources referenced by the usual XAPPLRESDIR
environment variable.
Files inside are (will be) generated by the Color Style Manager
backdrops/
directory:
If created, user can put custom backdrop sources here, and they can
than be selected by the Backdrop Style Manager
and processed with
current or custom color scheme.
photos/
directory:
User's photos which can be used instead of backdrops if selected in
Backdrop Style Manager or
configured in NsCDE-Backdrops.conf
manually.
backer/
directory:
Generated backdrops referenced by Colorsets 31-38 for FvwmBacker.
backer/bgcache/
subdirectory:
If FVWM3 is used by NsCDE in non-global monitor DesktopConfiguration mode,
Large PNG files are generated from the existing backdrops in share/defaults/backer
.
This directory contains automatically generated hierachy structure of background cache for multiple different X RandR
monitors when NsCDE is used with FVWM3 in non-global DesktopConfiguration mode, which are
matching various combinations of desks across monitors.
Referenced in function f_SetFvwm3NonGlobalBackground of config/NsCDE-Functions.conf
and
in libexec/xrandr_backer
backdrop autocreate script.
fontsets/
directory:
If created, user can put or generate with Font Style Manager own
fontsets here.
icons/
directory:
Populated by dynamic menu action fvwm-menu-desktop.
If directory does not exist, script will create it.
icons/NsCDE/
directory:
NsCDE custom icons. Put here by Color Style Manager and the rest
of the tools. Since icons from here are referenced with a relative
path, whatever is missing here, will be loaded from system's
/usr/local/share/icons/NsCDE
automatically.
libexec/
directory:
If created, colormgr.local
script can be written and put here, as
well as fontmgr.local
and other user's hooks.
palettes/
directory:
User can put custom palette files here, and they can
than be selected by the Color Style Manager and processed for a
preview or applied as new theme.
templates/
directory:
Here, local subdirectory of app-defaults
with tmpl files can be optionally created. Also, it is a good choice for Gkrellm or other
files processed by the libexec/colormgr.local
tmp/
directory:
Place used by parts of the NsCDE and in particular NsCDE's
FvwmScript programs for temporary generated files for previews,
or as scratch and work directory. Tools are usually taking care
to cleanup their garbage from tmp/ on exit.
NsCDE-XYZ.conf
files:
Absolute overrides of /usr/local/etc/nscde/NsCDE-XYZ.conf
files.
If in existence, they will be read instead of system defaults.
XYZ is here placeholder/example for Style, Functions, Keybindings,
Init, Menus etc ...
NsCDE-XYZ.local
files:
Extensions, added values of /usr/local/etc/nscde/NsCDE-XYZ.conf
files.
If in existence, they will be read in right after their .conf main
configurations from system (or local) directory. This is preferred
way to extend functionality or override something not big enough
for a complete "fork" of the config file. Colorset, Backdrops,
Animate, Font-$DPIdpi, Init, and Subpanel are exception of this,
that is, it is preferred (if not only thing possible) to have it as
.conf files only and not .local files.
NsCDE-Style.override
file:
If created, it will be read by the /usr/local/etc/nscde/NsCDE-Style.conf
.
Here, core style for all windows (*) can be overriden prior to reading particular
NsCDE application style overrides and addons, and prior to reading
$FVWM_USERDIR/NsCDE-Style.local
. Here, advanced users can override
or extend core styles which are not customizable by the Window Style Manager. See fvwm(1) for
a huge list of Style options.
Putting core Style options after NsCDE applications in the
/usr/local/etc/nscde/NsCDE-Style.conf
are processed can nullify overrides
for that particular applications, this is why this mechanism is provided.
This file is not created in $FVWM_USERDIR
by setup procedure or Style
Managers, but if created (manually) it will be read and processed.
XYZ is here placeholder/example for Style, Functions, Keybindings, Init, Menus etc ...
NsCDE.conf
: managed by
Window Style Manager, Workspaces and Pages Style
Manager, Pointer Style Manager and users own editor manually. See
the rest of the documentation.
WSM.conf
: read/written by Workspace and Page Manager, WSM and
user's favorite editor. Not an FVWM config file. System default
of this file is /usr/local/etc/nscde/WSM.conf
.
FrontPanel.actions
: user's overrides/addons for Front Panel
icons and actions. Written by editor, that is, manually only.
GeoDB.ini
: part of the Geometry Manager functionality. Written
and read by the bin/confset.py and bin/confget.py on
" and
from Extended and Standard Window Operations menus.
Windows-like ini files are WAY nicer than dconf and such binary
registry-like facilities.
Xdefaults
: Read on startup by xrdb(1).
Xdefaults.local
, Xdefaults.fontdefs
,
Xdefaults.mouse
:
Included with preprocessor directives from Xdefaults
Xset.conf
:
Configuration (a batch file or shell script basically) with
xset(1) parameters for system beep, pointer, keyboard, and DPMS
settings which are managed by their respective Style Managers.
User can put here setxkbmap, xgamma and such additional X server
configuration commands (or whatever one likes). Care must be
taken not to mess lines beggining with #XYZMgr,xxxx till
#end, since this is
internal marker of FvwmScript's buggy WriteToFile
function.
NsCDE-Sandbox.conf
:
If exists, used only in bare sandbox mode, where basic functionality
of the NsCDE is needed, and not full DE-like environment.