recentpopularlog in

kme : configfiles   32

NEWS - stow.git - stow
Enable special handling for "dotfiles" (files or folders whose name begins with a period) in the package directory. If this option is enabled, Stow will add a preprocessing step for each file or folder whose name begins with "dot-", and replace the "dot-" prefix in the name by a period ("."). This is useful when Stow is used to manage collections of dotfiles, to avoid having a package directory full of hidden files.

For example, suppose we have a package containing two files, stow/dot-bashrc and stow/dot-emacs.d/init.el. With this option, Stow will create symlinks from .bashrc to stow/dot-bashrc and from .emacs.d/init.el to stow/dot-emacs.d/init.el. Any other files, whose name does not begin with "dot-", will be processed as usual.
dotfiles  gnustow  tipsandtricks  configfiles  loginscripts 
december 2019 by kme
ingydotnet/...: Dot Dot Dot | https://github.com/
Dot Dot Dot. Contribute to ingydotnet/... development by creating an account on GitHub.
dotfiles  configfiles  bash  shell 
january 2019 by kme
Can I "export" functions in bash? - Unix & Linux Stack Exchange
This is why the 'module' shell function wasn't available to me within 'screen'; because it had been sourced from /etc/profile.d, and was therefore not available to subshells started from screen.
In Bash you can export function definitions to sub-shell with

export -f function_name

Functions are not exported to subprocesses. This is why there are files named .kshrc or .bashrc: To define functions that shoiuld be available in subshells also.
bash  solution  functions  configfiles  dotfiles 
march 2016 by kme
The Bash Shell Startup Files
Some excellent shell functions to atomically add paths to PATH-like environment variables:
# Functions to help us manage paths. Second argument is the name of the
# path variable to be modified (default: PATH)
pathremove () {
local IFS=':'
local NEWPATH
local DIR
local PATHVARIABLE=${2:-PATH}
for DIR in ${!PATHVARIABLE} ; do
if [ "$DIR" != "$1" ] ; then
NEWPATH=${NEWPATH:+$NEWPATH:}$DIR
fi
done
export $PATHVARIABLE="$NEWPATH"
}

pathprepend () {
pathremove $1 $2
local PATHVARIABLE=${2:-PATH}
export $PATHVARIABLE="$1${!PATHVARIABLE:+:${!PATHVARIABLE}}"
}

pathappend () {
pathremove $1 $2
local PATHVARIABLE=${2:-PATH}
export $PATHVARIABLE="${!PATHVARIABLE:+${!PATHVARIABLE}:}$1"
}
bash  profile  startup  rcfiles  configfiles  shellscripting  newbie  explained  sysadmin 
february 2016 by kme
Was The Windows Registry a Good Idea?
Was The Windows Registry a Good Idea? No

Was it better than the implementation of INI files? Yes

Solution : A better implementation of ini files

The two things it solved was speed and centralisation
Ini files are slow, but don't need to be?
Ini files are scattered but don't need to be

If I run a program I would expect it to save my settings in my space not in it's program folder, not in the system folder, not hidden somewhere (seemingly randomly) in the registry, if it's a global setting - isn't that what All Users is for?
windows  registry  configfiles  critique  forthecomments 
october 2015 by kme

Copy this bookmark:





to read