Thanks for the reply.
Adding the lines from your .bash_profile to mine restored the
functionality of .bashrc.
I don't have any backups of .bash_profile, but I would guess the the HEX
installation script woped out the origional .bash_profile. ( I try to
never assume anything as we all know h
On Wed, Apr 25, 2018 at 10:49:52PM +0300, Abdullah Ramazanoglu wrote:
> It seems like when ~/.bash_profile did not exist, then ~/.bashrc is called
> directly.
That's not correct.
As a LOGIN shell, bash reads ONE file, searching among the following items
in sequence:
a) ~/.bash_profile
b) ~/.bash
On Wed, Apr 25, 2018 at 03:34:02PM -0400, Stephen P. Molnar wrote:
> Bu bumbling about I discovered
> the it is necessary to source .bashrc inorder to recticate the alias lines
> in .bashrc (note: commenting out the added lines in .bash_profile did not
> solve the problem).
>
> What's going on wh
On Wed, 25 Apr 2018 15:34:02 -0400 Stephen P. Molnar said:
> What's going on what is the fix?
It seems like when ~/.bash_profile did not exist, then ~/.bashrc is called
directly. However, when ~/.bash_profile did exist, then it is called *instead
of* ~/.bashrc and it is up to ~/.bash_profile to s
Hello,
On Wed, Apr 25, 2018 at 03:34:02PM -0400, Stephen P. Molnar wrote:
> Whie the additional lines are necessary for the execution of HEX they seem
> to have wiped oour all of the alias entries I have in .bashrc. Rebooting
> the system does not eliminate the problem! Bu bumbling about I disco
I am running Debian Stretch on my 64-bit Linux platform. I have just
installed the molecular docking program HEX. The installation program
added the line shown below to .bash_profile:
#
# Lines added by 'hex_setup.bin' for Hex 8.0.0
#
export HEX_ROOT=/home/comp/Apps/Hex
export HEX_VERSION=8.
6 matches
Mail list logo
