Emacs configuration.
Emacs config files is supposed to be placed at ~/emacs (emacs dir inside user home directory).
- clone repository to ~/emacs
- to install all used modes run ~/emacs/install/setup.sh
- add line to ~/.emacs initialization file
(load (concat (getenv "HOME") "/emacs/init.el"))
You can use dot tool to create symlinks for all files inside the ~/emacs/home directory.
- clone repository to user home directory (for example C:/Users/username/emacs)
- Set HOME environment variable to home directory (C:/Users/username)
- install windows port of wget
- run git bash (included in git dist for windows) then install all used modes by running setup.sh script (C:/Users/username/emacs/install/setup.sh).
- add line to ~/.emacs initialization file
(load (concat (getenv "HOME") "/emacs/init.el"))
You can use dot tool to create symlinks for all files inside the ~/emacs/home directory.
-
clone repository to ~/emacs
-
to install all used modes run ~/emacs/install/setup.sh
-
add line to ~/.emacs initialization file
(load (concat (getenv "HOME") "/emacs/init.el"))
You can use dot tool to create symlinks for all files inside the ~/emacs/home directory. -
Fix PATH environment problem.
Programs which has launched from spotlight has different environment variables than whose who launched from terminal.
Suppose you add some additional dirs to PATH ($ADDITIONAL_PATH)
Add something like this to your .profile :# patch PATH for terminal programs export PATH=$ADDITIONAL_PATH:$PATH # patch PATH for gui (and spotlight in particular) OLD_GUI_PATH=\`launchctl getenv PATH\` if [[ $OLD_GUI_PATH != *$ADDITIONAL_PATH* ]] then NEW_GUI_PATH=$ADDITIONAL_PATH:$OLD_GUI_PATH launchctl setenv PATH $NEW_GUI_PATH fi