[arch-general] Colorized Output Listing
Dave Reisner
d at falconindy.com
Fri Aug 20 10:18:14 EDT 2010
On Fri, Aug 20, 2010 at 08:07:02PM +0600, reflexing wrote:
> On Fri, Aug 20, 2010 at 8:04 PM, Dave Reisner <d at falconindy.com> wrote:
>
> > On Fri, Aug 20, 2010 at 10:03:30AM -0400, Dave Reisner wrote:
> > > On Fri, Aug 20, 2010 at 07:53:17PM +0600, reflexing wrote:
> > > > Guys, does ArchLinux source ~/.profile file? If not, why?
> > > > I better prefer to set i.e. aliases for all my shells, not only BASH…
> > > >
> > > > --
> > > > Jabber: reflexing at reflexing.ru, ICQ: 8163230, Skype on demand.
> > >
> > > Read the INVOCATION section of bash(1).
> > >
> > > d
> >
> > Er, that is to say.. it has nothing to do with your distro. Sourcing
> > files out of your home directory is reliant on the shell.
> >
> > d
> >
>
> It worked for me in RHEL but didn't worked in ArchLinux, please confirm.
>
> --
> Jabber: reflexing at reflexing.ru, ICQ: 8163230, Skype on demand.
Since you didn't read the man page, I'll quote it here for you:
When bash is invoked as an interactive login shell, or as a
non-interactive shell with the --login option, it first reads and
executes com‐ mands from the file /etc/profile, if that file exists.
After reading that file, it looks for ~/.bash_profile, ~/.bash_login,
and ~/.pro‐ file, in that order, and reads and executes commands from
the first one that exists and is readable. The --noprofile option
may be used when the shell is started to inhibit this behavior.
Short form: if .bash_profile and/or .bash_login exist, .profile will
never be read. Again, this is all distro agnostic.
d
More information about the arch-general
mailing list