With recent Ubuntu releases it is assumed:
- bash is the default shell
- vi is symlinked to vim
- tmux version >= 1.9
Required packages:
GNU Stow is a symlink farm manager which takes distinct packages of software and/or data located in separate directories on the filesystem, and makes them appear to be installed in the same place. By default, GNU Stow will symlink top level folders into home directory. That’s ok for most applications, but it does cause some trouble when the application tries to write into the config folders. For example, when VIM writes temporary files to the ~/.vim folder, they will contaminate our git repository. The solution to this is using the no-folding option. No-folding (--no-folding) will create all directory with mkdir and only symlink the config files. This is the stow command I use to to map configs.\
Dotfiles option doesn't work with directories #33
- ~/.xprofile vs ~/.xsession vs ~/.xinitrc
.xprofile is just for setting up the environment when logging in with an X session (usually via a display manager). It is similar to your .profile file, but specific to x sessions. The xprofile files are natively sourced by the following display managers:
GDM - /etc/gdm/Xsession
LightDM - /etc/lightdm/Xsession
LXDM - /etc/lxdm/Xsession
SDDM - /usr/share/sddm/scripts/Xsession
Sourcing xprofile from a session started with xinit
It is possible to source xprofile from a session started with one of the following programs:
startx
xinit
XDM
Any other Display manager which uses ~/.xsession or ~/.xinitrc
.xinitrc is run by xinit (and therefore also startx). In addition to configuration, it is also responsible for starting the root X program (usually a window manager such as Gnome, KDE, i3, etc.). This usually applies when X is started manually by the user (with startx or similar).
.xsession is similar to .xinitrc but is used by display managers (such as lightdm, or sddm) when a user logs in. However, with modern DMs the user can usually choose a window manager to start, and the DM may or may not run the .xsession file.
- ~/.Xdefaults vs ~/.Xresource
Xlib Programming Manual P.441
Prior to X11R2, X resource settings were read from .Xdefaults file
in users home directory and optionally on whatever machine the X client
was running on, so multiple files was hard to maintain.
Later on, xrdb program was made to store users resource settings from
in .Xresources into the XA_RESOURCE_MANAGER property of the root window
on the current X server, so all clients connected to the same server has
access to them. If the user hasn't called xrdb to set the property, then
.Xdefaults is read.
With multiple sessions and servers (-L option) it is possible to bork keybindings beyond repair.