I know this is old stuff, but... On Tue,13.Jan.09, 11:10:49, JoeHill wrote: > > I'm used to ~/bin being automatically picked up in my path, so therefore I am > absolutely clueless as to how to add it. Also, considering the potential > consequences to my system, I would rather not do it the wrong way ;) > > This was what came up on a search, is this correct? > > export PATH =$PATH:/new/path/to/add On a new sid install I have this: ,----[ ~/.profile ] | # ~/.profile: executed by the command interpreter for login shells. | # This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login | # exists. | # see /usr/share/doc/bash/examples/startup-files for examples. | # the files are located in the bash-doc package. | | # the default umask is set in /etc/profile; for setting the umask | # for ssh logins, install and configure the libpam-umask package. | #umask 022 | | # if running bash | if [ -n "$BASH_VERSION" ]; then | # include .bashrc if it exists | if [ -f "$HOME/.bashrc" ]; then | . "$HOME/.bashrc" | fi | fi | | # set PATH so it includes user's private bin if it exists | if [ -d "$HOME/bin" ] ; then | PATH="$HOME/bin:$PATH" | fi `---- and there is no .bash_profile. This works with gdm. On my former system I had mostly the same stuff in .bash_profile, but had to setup my terminal emulator to start a login shell (because /bin/sh -> dash). Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein)
Attachment:
signature.asc
Description: Digital signature