On Sun, 17 Dec 2006 01:23:54 -0600
"Russell L. Harris" <[EMAIL PROTECTED]> wrote:
> Perhaps in the distant past I edited .bashrc and forgot to make
> a note of it, and then an upgrade of bash installed a new
> .bashrc ?
One might think that, especially if a command used to work and you
hadn't c
* Marc Wilson <[EMAIL PROTECTED]> [061216 23:52]:
> On Thu, Dec 14, 2006 at 07:13:39AM -0600, Russell L. Harris wrote:
> > During configuration of another machine running Etch, I discovered
> > that .bash_profile appears to be ignored when logging into X.
>
> No reason why it should be... your .ba
On Thu, Dec 14, 2006 at 07:13:39AM -0600, Russell L. Harris wrote:
> During configuration of another machine running Etch, I discovered
> that .bash_profile appears to be ignored when logging into X.
No reason why it should be... your .bash_profile is, of course, a
configuration file related to th
Russell L. Harris wrote:
During configuration of another machine running Etch, I discovered
that .bash_profile appears to be ignored when logging into X.
Specifically, the problem is that the "~/bin" directory does not
appear in the path when, in an X terminal, I execute:
$ echo $PATH
Howe
Hi RLH,
I think it's normal as .bash_profile is only for login shell. When you open
a X terminal, it won't be read. You can put your path info in .bashrc.
--
Yuwen
5 matches
Mail list logo
