Re: .bashrc not sourced

On 3/29/2016 11:04 AM, Gary Furash wrote: When I log on w/ Mintty or Bash (via the bat file) it takes me to my home directory but doesn't automatically source .bashrc. It's only in non-login shells that .bashrc gets sourced by default. If you want it to be sourced in login shells, you should

Re: Bashrc distinguish between mintty and x-windows xterm

Andy gmail.com> writes: > For the record, this in .bashrc seems to work well in xterm's white > background > and mintty's black background. > > case "$(< /proc/$PPID/exename)" in >*/xterm) function setPS1() { > PS1="\[\033]0;\w\007\033[32m\]\u@\h \[\033[35m\w\033[0m\]\n$" ; > echo

Re: Bashrc distinguish between mintty and x-windows xterm

Andy wrote: | Ken Jackson jackson.io> writes: |> Fri, May 25, 2012 at 09:32AM -0400 Buchbinder, Barry |> (NIH/NIAID) [E] wrote: |>> Andrew Hancock sent the following at Friday, May 25, 2012 12:42 AM |>>>Barry, it works flawlessly. Thanks immensely! |>> |>> But I forgot to export ThisTerm, ot

Re: Bashrc distinguish between mintty and x-windows xterm

Ken Jackson jackson.io> writes: > Fri, May 25, 2012 at 09:32AM -0400 Buchbinder, Barry > (NIH/NIAID) [E] wrote: >> Andrew Hancock sent the following at Friday, May 25, 2012 12:42 AM >>>Barry, it works flawlessly. Thanks immensely! >> >> But I forgot to export ThisTerm, otherwise it is always

Re: Bashrc distinguish between mintty and x-windows xterm

Fri, May 25, 2012 at 09:32AM -0400 Buchbinder, Barry (NIH/NIAID) [E] wrote: > Andrew Hancock sent the following at Friday, May 25, 2012 12:42 AM > >Barry, it works flawlessly. Thanks immensely! > > But I forgot to export ThisTerm, otherwise it is always unset when > a subshell is launched. A

RE: Bashrc distinguish between mintty and x-windows xterm

Andrew Hancock sent the following at Friday, May 25, 2012 12:42 AM >Barry, it works flawlessly. Thanks immensely! You are very welcome. But I forgot to export ThisTerm, otherwise it is always unset when a subshell is launched. # Only set ThisTerm if not set. if [ -z "${ThisTerm}" ] then if [ $

Re: Bashrc distinguish between mintty and x-windows xterm

Buchbinder, Barry (NIH/NIAID) [E] niaid.nih.gov> writes: > > # Only set ThisTerm if not set. > if [ -z "${ThisTerm}" ] > then >   if [ ${PPID} = 1 ] >   then > ThisTerm=cmd >   else > if [ "$(cat /proc/${PPID}/exename)" = '/usr/bin/mintty' ] > then >   ThisTerm=mintty > else > 

RE: Bashrc distinguish between mintty and x-windows xterm

Andy sent the following at Monday, May 21, 2012 8:39 PM >My bashrc sets the color of the prompt depending on $TERM. My x-windows >xterm has a white background and the cygwin default terminal, which has >a black background, use to not have $TERM=xterm. I could distinguish >between them in the bashrc

Re: .bashrc and.bash_profile missing

On Wed, Jun 29, 2011 at 9:42 AM, Ballaw wrote: > > I have used cygwin for Netbeans for about 6 months and today when I open the > shell I get: > bash: $'\r': command not found In the past, when I get the error "'\r': command not found" from bash in Cygwin, the cause has always been that the shell

Re: .bashrc file not run

Thorsten Kampe a écrit : * John Morrison (Fri, 12 Feb 2010 09:17:15 -) Thanks for that clarification; should I change the base-files? Or create ~/.profile as a copy/link? to ~/.bash_profile? There is no need for a ~/.profile. Only keep ~/.bash_profile IMHO, .bash_profile is a piece of

Re: .bashrc file not run

On Fri, February 12, 2010 3:42 pm, Thorsten Kampe wrote: > * John Morrison (Fri, 12 Feb 2010 09:17:15 -) >> >> Thanks for that clarification; should I change the base-files? Or >> create >> ~/.profile as a copy/link? to ~/.bash_profile? > > There is no need for a ~/.profile. Only keep ~/.bash_

Re: .bashrc file not run

* John Morrison (Fri, 12 Feb 2010 09:17:15 -) > > Thanks for that clarification; should I change the base-files? Or create > ~/.profile as a copy/link? to ~/.bash_profile? There is no need for a ~/.profile. Only keep ~/.bash_profile Thorsten -- Problem reports: http://cygwin.com/pro

Re: .bashrc file not run

Yes it is all working now, as long as I don't use --login for bash. I guess the failure to copy the skel/.bash_profile may have been the root of the problem. Neil - Original Message From: John Morrison To: cygwin@cygwin.com Sent: Fri, February 12, 2010 9:58:04 AM Subjec

Re: .bashrc file not run

On Fri, February 12, 2010 9:51 am, Neil Blue wrote: > I created the ~/.profile in response to the email from Csaba Raduly. the > bash man page does say it will look for ~/.profile as well. It does, but you can't expect default behaviour from a non default file! ;) > The setup program creates some

Re: .bashrc file not run

34:15 AM Subject: Re: .bashrc file not run On Fri, February 12, 2010 9:17 am, Neil Blue wrote: > The ~/.bashrc file wasn't called by default and altering ~/.profile did > fix the problem. Hi Neil, Where did you get the ~/.profile from? It's not a base-file file... > The comme

Re: .bashrc file not run

nce has been changed and why... Thanks, J. > Neil > > > - Original Message > From: John Morrison > To: cygwin@cygwin.com > Sent: Fri, February 12, 2010 8:26:24 AM > Subject: Re: .bashrc file not run > > ~/.bash_profile should already be setup to call ~/.bashrc > >

Re: .bashrc file not run

uot; fi ... I still need to start bash without --login however as any settings such as PATH that are configured in ~/.bashrc are lost, but it does run the ~/.bashrc file. Neil - Original Message From: John Morrison To: cygwin@cygwin.com Sent: Fri, February 12, 2010 8:26:24 AM Subject: R

Re: .bashrc file not run

On Fri, February 12, 2010 8:53 am, Thorsten Kampe wrote: > * John Morrison (Fri, 12 Feb 2010 08:26:24 -) >> >> ~/.bash_profile should already be setup to call ~/.bashrc >> >> it should have been in the base-files package which creates the >> /etc/skel >> files which should be copied when the us

Re: .bashrc file not run

* John Morrison (Fri, 12 Feb 2010 08:26:24 -) > > ~/.bash_profile should already be setup to call ~/.bashrc > > it should have been in the base-files package which creates the /etc/skel > files which should be copied when the user first log's on. > > AFAIK bash doesn't use a ~/.profile file.

Re: .bashrc file not run

eady set-up for me. > > Thanks again for the help. > > Cheers > Neil > > > > ----- Original Message > From: Csaba Raduly > To: cygwin@cygwin.com > Sent: Thu, February 11, 2010 3:30:15 PM > Subject: Re: .bashrc file not run > > On Thu, Feb 11, 20

Re: .bashrc file not run

if [ -f "$HOME/.bashrc" ]; then . "$HOME/.bashrc" fi fi ... I guess I am too used to having this already set-up for me. Thanks again for the help. Cheers Neil - Original Message From: Csaba Raduly To: cygwin@cygwin.com Sent: Thu, February 11, 2010 3

Re: .bashrc file not run

On Thu, Feb 11, 2010 at 4:06 PM, Thomas Wolff wrote: > On 11.02.2010 15:55, Neil Blue wrote: > > By design (and documentation), bash runs *only* .profile (and /etc/profile) > if started as a "login shell". Not quite. >From "info bash" , Node: Bash Startup Files When Bash is invoked as an interac

Re: .bashrc file not run

On 11.02.2010 15:55, Neil Blue wrote: Hello, This problem has me stumped. Me too, a while ago. ... When I login, the environment settings I put in .bashrc don't get run. If I source ~/.bashrc they are included as expected. Also I have added some configuration to /etc/bash.bashrc it does

Re: .bashrc

* Andy Koppe (Mon, 29 Jun 2009 09:43:44 +0100) > 2009/6/29 Dave Tang: > > So I've changed my home directory to /home/d.tang in my passwd file. I > > copied the .bashrc into my new home directory. > > > > But when I restart cygwin, it still doesn't load the .bashrc. > > Bash on Cygwin is normally i

Re: .bashrc

On Mon, 29 Jun 2009 18:43:44 +1000, Andy Koppe wrote: 2009/6/29 Dave Tang: So I've changed my home directory to /home/d.tang in my passwd file. I copied the .bashrc into my new home directory. But when I restart cygwin, it still doesn't load the .bashrc. Bash on Cygwin is normally invoked

Re: .bashrc

2009/6/29 Dave Tang: > So I've changed my home directory to /home/d.tang in my passwd file. I > copied the .bashrc into my new home directory. > > But when I restart cygwin, it still doesn't load the .bashrc. Bash on Cygwin is normally invoked as a login shell, in which case it doesn't source .bas

Re: .bashrc

On Mon, 29 Jun 2009 17:41:08 +1000, Thorsten Kampe wrote: * Dave Tang (Mon, 29 Jun 2009 17:34:44 +1000) Dave, don't send emails to my private email address. Keep the Reply-to to the list. Sorry about that, will remember that. Have a look at /etc/passwd how HOME is set. Check if that fi

Re: .bashrc

* Dave Tang (Mon, 29 Jun 2009 17:34:44 +1000) Dave, don't send emails to my private email address. Keep the Reply-to to the list. > > Doesn't really matter. The important thing is your home directory. Set > > it to /home/d.tang > > > > T. > > Thanks for the quick reply. > > So I've changed m

Re: .bashrc

On Mon, 29 Jun 2009 17:21:21 +1000, Thorsten Kampe wrote: * Dave Tang (Mon, 29 Jun 2009 17:11:26 +1000) >> Do you spot anything funny going on? > > Your prompt and your home directory. Looks like you're not using bash > (but zsh maybe) and not using the defaults. Ah sorry for the confusion,

Re: .bashrc

* Dave Tang (Mon, 29 Jun 2009 17:11:26 +1000) > >> Do you spot anything funny going on? > > > > Your prompt and your home directory. Looks like you're not using bash > > (but zsh maybe) and not using the defaults. > > Ah sorry for the confusion, I had modified my PS1 settings (which I could > se

Re: .bashrc

On Mon, 29 Jun 2009 16:52:25 +1000, Thorsten Kampe wrote: * Dave Tang (Mon, 29 Jun 2009 16:21:04 +1000) %whoami d.tang %echo $HOME /cygdrive/c/Documents and Settings/d.tang %cat /etc/passwd d.tang:unused_by_nt/2000/xp:11418:10545:d.tang,U-IMBPC\d.tang,S-1-5-21-2360347544-2198861549-3143054

Re: .bashrc

* Dave Tang (Mon, 29 Jun 2009 16:21:04 +1000) > %whoami > d.tang > > %echo $HOME > /cygdrive/c/Documents and Settings/d.tang > > %cat /etc/passwd > d.tang:unused_by_nt/2000/xp:11418:10545:d.tang,U-IMBPC\d.tang,S-1-5-21-2360347544-2198861549-3143054254-1418:/cygdrive/c/Documents > > and Setting

Re: .bashrc

On Mon, 29 Jun 2009 15:54:37 +1000, Linda Walsh wrote: Dave Tang wrote: Hello, I have cygwin installed on Windows XP and for some reason my .bashrc file isn't loaded on startup. I read the FAQ "Why doesn't bash read my .bashrc file on startup?" but my HOME environment variable is set up

Re: .bashrc

Dave Tang wrote: Hello, I have cygwin installed on Windows XP and for some reason my .bashrc file isn't loaded on startup. I read the FAQ "Why doesn't bash read my .bashrc file on startup?" but my HOME environment variable is set up i.e. when I echo $HOME it is correct. I actually copied my .

Re: bashrc question

* Stephen H. Dawson (Tue, 12 Jun 2007 15:30:33 -0400) > I am running the latest version of Cygwin on XP Pro. Don't think so. CopSSH is no Cygwin application. > Since day 1, I have been getting an error message at startup, "bash: > $'\r': command not found". Working with a friend, he said I need a

Re: bashrc question

dos2unix .bashrc On Tue, 2007-06-12 at 15:30 -0400, Stephen H. Dawson wrote: > Hello, > > > I am running the latest version of Cygwin on XP Pro. Since day 1, I have > been getting an error message at startup, "bash: $'\r': command not found". > Working with a friend, he said I need a bashrc fi

Re: .bashrc question

On 12/20/05, Luke Vanderfluit <[EMAIL PROTECTED]> wrote: > Hi Jim. > > Jim Roberts wrote: > > >Try launching rxvt like this: > > > >C:\Cygwin\bin\rxvt.exe -geometry 80x29 -sb -sl 1 -bg Black -fg > >green -bd LightSeaGreen -fn Courier -font 7x15 -e /usr/bin/bash > >--login -i > > > > > Hurrah, t

Re: .bashrc question

Hi Jim. Jim Roberts wrote: On 12/20/05, Luke Vanderfluit <[EMAIL PROTECTED]> wrote: Hi. I have been trying to get an alias to work. I start my bash shell from cygwin.bat with the following command: bash --login -i -c 'rxvt -geometry 80x29 -sb -sl 1 -bg Black -fg green -bd LightSeaGre

Re: .bashrc question

On 12/20/05, Luke Vanderfluit <[EMAIL PROTECTED]> wrote: > Hi. > > I have been trying to get an alias to work. > > I start my bash shell from cygwin.bat with the following command: > > bash --login -i -c 'rxvt -geometry 80x29 -sb -sl 1 -bg Black -fg > green -bd LightSeaGreen -fn Courier -font 7

RE: .bashrc not working (and yes I've read the FAQ etc as you'll see)

Some thoughts which others have thought before me: 1. /etc/password should reference shell and home to use 2. /etc/profile is executed at 'login ...' a. Note comments on /etc/profile.d 3. $HOME/.bashrc, $HOME/.inputrc are executed (for bash) 4. If you use scripts and intend to import

Re: .bashrc not working (and yes I've read the FAQ etc as you'll see)

On Fri, 18 Feb 2005, J. David Boyd wrote: > "Steve Mayes" <[EMAIL PROTECTED]> writes: > > .bashrc not working > > [snip] > > The --login and -i switches are used. Stare at these two lines for a moment, and then read the "INVOCATION" section of the bas

Re: .bashrc not working (and yes I've read the FAQ etc as you'll see)

"Steve Mayes" <[EMAIL PROTECTED]> writes: > Hi, > > Forgive the defensive addendum but I've no wish to be either flamed or > ignored when I've tried available pathways to solving this. > > Situation: > > .bashrc not working and yes my $home variable is correctly defined but I > put a copy of .b

RE: .bashrc not working (and yes I've read the FAQ etc as you'll see)

Steve wrote: >Forgive the defensive addendum but I've no wish to be either flamed or >ignored when I've tried available pathways to solving this. Must ... resist ... urge ... to flame ... }:-)> >Situation: > >.bashrc not working and yes my $home variable is correctly >defined but I >put a

RE: .bashrc not working (and yes I've read the FAQ etc as you'll see)

Steve Mayes wrote on Friday, February 18, 2005 11:01 AM: > Hi, > > Forgive the defensive addendum but I've no wish to be either > flamed or ignored when I've tried available pathways to solving this. > > Situation: > > .bashrc not working and yes my $home variable is correctly > defined [snip]

Re: .bashrc not called for non-interactive ssh sessions

What kind of script hacks did you do differently from the environment stuff mentioned by Pekka? And although I appreciate hearing about workarounds, if this is really a bug, let us work on actually fixing it! On Fri, 22 Oct 2004 01:28:20 + (UTC), Christopher Cobb <[EMAIL PROTECTED]> wrote: >

Re: .bashrc not called for non-interactive ssh sessions: SOLUTION

Hi there, I solved similar problem by enabling line PermitUserEnvironment yes in /etc/sshd_config and copying my .bashrc as ~/.ssh/environment In man pages of sshd it says: " 6. Reads the file $HOME/.ssh/environment, if it exists, and users are allowed to change their enviro

Re: .bashrc not called for non-interactive ssh sessions

I'm not totally sure what you're asking... My shell in /etc/passwd is /bin/bash. Just in case I copied the /etc/defaults/profile to /etc/profile and added a check if that even gets called. /etc/profile *doesn't* get called with a non-interactive ssh which is the correct behavior - only the users

Re: .bashrc not called for non-interactive ssh sessions

Philip Nemec gmail.com> writes: > But ssh cygwinbox pwd does *not* call ~/.bashrc... This annoys me no end. I have had to write some quite hackish scripts to get around this. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.

Re: .bashrc not called for non-interactive ssh sessions

At 07:48 PM 10/21/2004, you wrote: >As best as I can tell from the archives and man pages, ~/.bashrc >should be called when starting an ssh session - both interactive and >non-interactive. Tests on my Linux box behave as expected: > >ssh linuxbox >ssh linuxbox pwd >ssh cygwinbox > >But ssh cygwinb

Re: .bashrc

On Mon, 21 Jun 2004, Vasoczki Ferenc wrote: > Hi! > > I installed the cygwin again, and read the SGT settings. > It wrote, i should edit my .bashrc, but there is no .bashrc after > install in /home/myuser directory, only a .bash_history ? > > How can i tell to cygwin to create 1 ? > Vaso The late

Re: .bashrc

There is a default .bashrc you can use in /etc/skel Erik --- Vasoczki Ferenc <[EMAIL PROTECTED]> wrote: > Hi! > > I installed the cygwin again, and read the SGT > settings. > It wrote, i should edit my .bashrc, but there is no > .bashrc after install in /home/myuser > directory, only a .bash_hi

RE: bashrc

> From: Igor Pechtchanski > Sent: Thursday, June 17, 2004 7:37 PM > On Thu, 17 Jun 2004, Chris W wrote: > > > Hannu E K Nevalainen wrote: > > > > >Type this at the bash prompt; > > >$ MANPAGER="${MANPAGER}p ^INVOCATION" man bash > > >and hit enter. > > > > What is that supposed to do? All I get i

Re: bashrc

On Thu, 17 Jun 2004, Chris W wrote: > Hannu E K Nevalainen wrote: > > >Type this at the bash prompt; > >$ MANPAGER="${MANPAGER}p ^INVOCATION" man bash > >and hit enter. > > What is that supposed to do? All I get is an error. That's supposed to show you the part of the bash manpage dealing with i

Re: bashrc

Hannu E K Nevalainen wrote: Type this at the bash prompt; $ MANPAGER="${MANPAGER}p ^INVOCATION" man bash and hit enter. What is that supposed to do? All I get is an error. p: not found Error executing formatting or display command. System command (cd "/usr/share/man" && (echo ".pl 1100i"; /usr/

RE: bashrc

> From: Chris W > Sent: Wednesday, June 16, 2004 5:05 PM > Where do I put my .bashrc file so it reads my settings and alias commands? This is really off topic, but anyway... Type this at the bash prompt; $ MANPAGER="${MANPAGER}p ^INVOCATION" man bash and hit enter. Read the third paragraph tho

Re: bashrc

Chris W wrote: Where do I put my .bashrc file so it reads my settings and alias commands? In you home directory. You might want to read the output of $ man bash section INVOCATION, for more information about this.. HTH rlc -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem r

RE: bashrc

> -Original Message- > From: cygwin-owner On Behalf Of Chris W > Sent: 16 June 2004 16:05 > To: cygwin > Subject: bashrc > > Where do I put my .bashrc file so it reads my settings and > alias commands? ~ cheers, DaveK -- Can't think of a witty .sigline today -- Unsubs

Re: .bashrc is ignored

Hoss wrote: > I'm a newbie to cygwin and I'm trying to setup .bashrc to start when I launch > a cygwin terminal (using rxvt in fact). my .bashrc is ignored which I think > is because the %HOME% environment variable is not set *before* I run > bash/rxvt. > When I do set it, it simply causes bash to

Re: .bashrc is ignored

On Mon, 12 Apr 2004, Hoss wrote: > hi. > > I'm a newbie to cygwin and I'm trying to setup .bashrc to start when I > launch a cygwin terminal (using rxvt in fact). my .bashrc is ignored > which I think is because the %HOME% environment variable is not set > *before* I run bash/rxvt. When I do set

Re: .bashrc is ignored

At 09:55 AM 4/12/2004, you wrote: >hi. > >I'm a newbie to cygwin and I'm trying to setup .bashrc to start when I launch a >cygwin terminal (using rxvt in fact). my .bashrc is ignored which I think is >because the %HOME% environment variable is not set *before* I run bash/rxvt. >When I do set it,

Re: .bashrc issues caused by spaces in the pathname of my user profile

On Sun, 25 Jan 2004 f00roaxddchalmersse wrote: > I have fairly recently installed cygwin into my Windows 98 system and I > have run into the unfortunate coincidence of having spaces in my username. > That seems to have caused Bash to fail reading the .bashrc file of my > /home/User Name directory

Re: .bashrc not getting sourced?

> My question is pretty simple: is editing the /etc/profile the > recommended way to get my ~/.bashrc file sourced? I say: no. > And if not, > what is. > > It should be noted that I found a message by Gary R. Van Sickle > suggesting that .bash_profile might be a better way to do things, > but

Re: .bashrc not getting sourced?

Wow. That was allot of discussion and conjecture on this topic. Did anyone think of looking at the GNU bash documentation before posting? http://www.lns.cornell.edu/public/COMP/info/bash/bashref_7.html#SEC65 Seems to me this answers the question quite well about where this kind of check is

Re: .bashrc not getting sourced?

I believe that .bash_login, .bash_profile or .profile is the file you're wanting to use in this instance. man bash { snip } When an interactive shell that is not a login shell is started, bash reads and executes commands from ~/.bashrc, if that file exists. This may be inh

Re: .bashrc not getting sourced?

I searched the archives and found a note from Larry suggesting that I review the archives for 12-03-2001. I did this for all of Nov, Dec, and Jan and did not find at least two mentions of the problem as he suggested. My question is pretty simple: is editing the /etc/profile the recommended wa

Re: .bashrc not getting sourced?

IIRC, if you check the archives, you should find that the behavior of sourcing the .bashrc file in /etc/profile was discontinued in later cygwin releases. The fact that you have it from over a year ago is probably because the cygwin install does not overwrite files that have been modified or e

Re: .bashrc not getting sourced?

Roland, My /etc/profile contains exactly the line you quote. It is the last line of that file, immediately following a "cd $HOME" command. This file bears the modification date May 10, 2001. It may be a coincidence, but that's right when I installed Cygwin for the first time on what was then a