Re: bashrc problem

2022-01-12 Thread Yamadaえりな
Thanks a lot @Will Mengarini On Wed, Jan 12, 2022 at 8:21 PM Will Mengarini wrote: > * Yamada??? [22-01/12=We 20:10 +0800]: > > Do you mean if .bash_profile exists, .bashrc will be ignored? > > Sometimes. From `man bash`: > When bash is invoked as an interactive login shell, or as a > non

Re: bashrc problem

2022-01-12 Thread Will Mengarini
* Yamada??? [22-01/12=We 20:10 +0800]: > Do you mean if .bash_profile exists, .bashrc will be ignored? Sometimes. From `man bash`: When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /

Re: bashrc problem

2022-01-12 Thread Will Mengarini
* Yamada??? [22-01/12=We 19:49 +0800]: > I have a .bashrc file in my home dir, whose content is shown as follows. > But every time I log into the system, I have to source this file by hand. > > $ which scala > /usr/bin/scala > > $ cat .bashrc > #THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO

Re: bashrc problem

2022-01-12 Thread Yamadaえりな
Do you mean if .bash_profile exists, .bashrc will be ignored? Thanks. On Wed, Jan 12, 2022 at 8:07 PM Will Mengarini wrote: > * Yamada??? [22-01/12=We 19:49 +0800]: > > I have a .bashrc file in my home dir, whose content is shown as follows. > > But every time I log into the system, I have to

bashrc problem

2022-01-12 Thread Yamadaえりな
Hello list I have a .bashrc file in my home dir, whose content is shown as follows. But every time I log into the system, I have to source this file by hand. $ which scala /usr/bin/scala $ cat .bashrc #THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!! export SDKMAN_DIR="$HOME/.sdkman" [

Re: Strange .bashrc Problem

2018-04-25 Thread Stephen P. Molnar
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

Re: Strange .bashrc Problem

2018-04-25 Thread Greg Wooledge
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

Re: Strange .bashrc Problem

2018-04-25 Thread Greg Wooledge
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

Re: Strange .bashrc Problem

2018-04-25 Thread Abdullah Ramazanoglu
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

Re: Strange .bashrc Problem

2018-04-25 Thread Andy Smith
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

Strange .bashrc Problem

2018-04-25 Thread Stephen P. Molnar
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.

Re: .bashrc problem--"ls" output and root prompt

2007-08-22 Thread Ansgar Esztermann
On Tue, Aug 21, 2007 at 04:14:04PM -0700, Dr. Jennifer Nussbaum wrote: > > PS1='\h\w $ '; export PS1 > > So, nothing fancy. How do i get my coloured "ls" back, > and my "#" prompt as sudo'ed root? Use \$ rather than a plain $ to get # as root. A. -- Ansgar Esztermann Researcher & Sysadmin

Re: .bashrc problem--"ls" output and root prompt

2007-08-21 Thread Sergio Cuéllar Valdés
2007/8/21, Dr. Jennifer Nussbaum <[EMAIL PROTECTED]>: > > Im a new Debian Etch user, coming from FreeBSD. When i > first installed my system, running the "ls" command > would > give me coloured output (executables one colour, > directories another). Also, when I sudo'ed to root, i > would get the u

.bashrc problem--"ls" output and root prompt

2007-08-21 Thread Dr. Jennifer Nussbaum
Im a new Debian Etch user, coming from FreeBSD. When i first installed my system, running the "ls" command would give me coloured output (executables one colour, directories another). Also, when I sudo'ed to root, i would get the usual "#" prompt as root. I then copied over my (straightforward)