Re: Debianly Correct place to add ~/bin to $PATH ? a new problem
On 20131210_015742, Andrei POPESCU wrote:
> On Lu, 09 dec 13, 12:15:53, Paul E Condon wrote:
> > I've just done a fresh netinst of Wheezy and want to proceed with my
> > personal configuring in a way that is not fighting with the Debian
> > view of how things should be done. I've used Debian since Potato, I
> > think, but have always hacked things until they seemed to be
> > working. Now, I want to try to do things in the way the developers had
> > in mind when they built the install CD images.
> >
> > I see the file ~/.profile . It contains code that tests for the
> > existence of ~/bin/ and adds it to $PATH , if it exists. But it
> > doesn't 'work'. After I have created my ~/bin/. and filled it with
> > some scripts, and rebooted, there is still no mention of ~/bin/ in
> > $PATH . Why?
>
> Most display managers don't source ~/.profile (or /etc/profile). I tried
> to discuss this with developers, but there was hardly any interest so I
> settled for sourcing them in ~/.xsessionrc instead (which is sourced by
> the X startup scripts):
>
>
> ,----[ ~/.xsessionrc ]
> | . /etc/profile
> | . ~/.profile
> `----
I looked for ~/.xsessionrc and find that I don't have such a file in my ~/ !!!
But I do have some strange files that I had notice for several months, namely
#.Xresources# #.muttrc# #test# and #x#
The contents of #.Xresources# and #x# are X resource definitions, but
there are conflicting emacs.geometry values in the two. #.muttrc# is a
Mutt rc file with statements in it, which if executed by Mutt would
completely screw up my current setup of Mutt. #test# is empty. Have
you any idea where these came from? It appears to be an attempt at a
new different way of planting configuration data on a per user basis.
The bottom line is that I don't have an .xsessionrc , and therefore
its not a good place for me to put profile files sourcing.
Suggestions?
--
Paul E Condon
pecondon@mesanetworks.net
Reply to: