Greetings, Kirill Frolov!
> $ which nano
> /cygdrive/c/Program Files/Git/usr/bin/nano
That explains it. Cygwin does not install nano by default.
Fire up your setup.exe and install it, that will fix your issue.
As for the future, I suggest to patch your ~/.profile and exclude
unnecessary/conflicti
On 3/3/2023 10:37 AM, Kirill Frolov via Cygwin wrote:
On 03.03.2023 18:31, Andrey Repin wrote:
Greetings, Kirill Frolov!
Please avoid top-posting in this list.
On 03.03.2023 15:47, Andrey Repin wrote:
Greetings, Kirill Frolov!
When i run nano ~/.bashrc nano opens with [ Directory
On 03.03.2023 18:31, Andrey Repin wrote:
Greetings, Kirill Frolov!
Please avoid top-posting in this list.
On 03.03.2023 15:47, Andrey Repin wrote:
Greetings, Kirill Frolov!
When i run nano ~/.bashrc nano opens with [ Directory '/home/frolo' does not
exist ] error.
Do you r
Greetings, Kirill Frolov!
Please avoid top-posting in this list.
> On 03.03.2023 15:47, Andrey Repin wrote:
>> Greetings, Kirill Frolov!
>>
>>> When i run nano ~/.bashrc nano opens with [ Directory '/home/frolo' does
>>> not exist ] error.
>>
g-nsswitch
#
# Defaults:
# passwd: files db
# group: files db
# db_enum: cache builtin
# db_home: /home/%U
# db_shell: /bin/bash
# db_gecos:
On 03.03.2023 15:47, Andrey Repin wrote:
Greetings, Kirill Frolov!
When i run nano ~/.bashrc nano opens with [ Directory '/home/frolo' does not
Greetings, Kirill Frolov!
> When i run nano ~/.bashrc nano opens with [ Directory '/home/frolo' does
> not exist ] error.
Do you run it from bash prompt or from CMD prompt?
> The file opens with cat ~/.bashrc
Can you please show us the output of
getent passwd "
When i run nano ~/.bashrc nano opens with [ Directory '/home/frolo'
does not exist ] error.
The file opens with cat ~/.bashrc
Cygwin Configuration Diagnostics
Current System Time: Fri Mar 03 12:33:37 2023
Windows 11 Professional Ver 10.0 Build 22621
Path: F:\cygwin64\usr
Greetings, Adam Dinwoodie!
> On Sat, Mar 05, 2022 at 09:26:06AM +0300, lvm wrote:
>> The identical /etc/skel/.bashrc and /etc/defaults/etc/skel/.bashrc contain
>> the same line
>>
>> # export HISTCONTROL=$HISTCONTROL${HISTCONTROL+,}ignoredups
Not a nitpick or
On Sat, Mar 05, 2022 at 09:26:06AM +0300, lvm wrote:
> The identical /etc/skel/.bashrc and /etc/defaults/etc/skel/.bashrc contain
> the same line
>
> # export HISTCONTROL=$HISTCONTROL${HISTCONTROL+,}ignoredups
>
> But HISTCONTROL values should be colon separated, not com
The identical /etc/skel/.bashrc and /etc/defaults/etc/skel/.bashrc contain
the same line
# export HISTCONTROL=$HISTCONTROL${HISTCONTROL+,}ignoredups
But HISTCONTROL values should be colon separated, not comma separated. This
line is commented out, but if someone like me tries to use it without
Keep responses to the list and not the individual responders.
Forwarded on your behalf.
On 8/31/2017 10:32 AM, Michel LaBarre wrote:
> Thanks for the reply.
>
> Quick answer (repeated interleaved below):
> - my .bash_profile does indeed source .bashrc
> - I added an echo t
On 8/30/2017 7:26 PM, Michel LaBarre wrote:
> Playing with set -m/+m and shopt -s lastpipe, in an interactive bash shell,
> I came across a situation
> which is minor unless it has broader implications for others that I do not
> know about.
>
> Specifically if "set +m&
Playing with set -m/+m and shopt -s lastpipe, in an interactive bash shell,
I came across a situation
which is minor unless it has broader implications for others that I do not
know about.
Specifically if "set +m" is present in .bashrc, it looks like job control
(monitor mode) is
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,
OS: Windows 7, Windows 10
Cygwin: latest, x64
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. If I hand
type "source .bashrc" it then sources it.
-- gary furash | furashg...@gmail.com, 520-907-2470
--
o stomp your profile directory with strict POSIX
permissions. Not every application is ready to accept them, you may even lose
the ability to open documents through associations.
> After refresh installing and change the fstab above, then startup mintty.
> But, I didn't see .bashrc/.
,posix=0,nouser
After refresh installing and change the fstab above, then startup mintty.
But, I didn't see .bashrc/.profile/.inputrc/.bash_profile was
generated automatically under home directory. I mean the `/etc/skel/*`
files would be copied to home direcotry.
Thanks
[1]: http://cygwin.com/
able to duplicate this no matter what I do. I have even
> launched a dash shell directly from cmd.exe and done a startxwin from that.
> I do have the following additions at the beginning of my .bashrc and
> .bash_profile
> .bashrc:
> [[ "$-" != *i* ]] && return
&g
shell directly from cmd.exe and done a startxwin from that.
I do have the following additions at the beginning of my .bashrc and
.bash_profile
.bashrc:
[[ "$-" != *i* ]] && return
export BASHRC=${HOME}/.bashrc
if [ "${BASH_PROFILE-unset}" = "unset" ]; th
Earnie Boyd wrote:
>> >>> Then what is the value of $SHELL?
>> >
>> > /bin/bash
>>
>> What user actually starts the session? I've seen this type of thing
>> when the cron daemon starts a session. The profile files are never
>> read.
Don't have cron running. I start it as me, the logged in use
On Thu, Feb 28, 2013 at 9:28 AM, Kevin Layer wrote:
> Earnie Boyd wrote:
>
>>> On Wed, Feb 27, 2013 at 5:16 PM, Kevin Layer wrote:
>>> >
>>> > Did you read the original report and all the replies in the chain?
>>> >
>>> >...it
Earnie Boyd wrote:
>> On Wed, Feb 27, 2013 at 5:16 PM, Kevin Layer wrote:
>> >
>> > Did you read the original report and all the replies in the chain?
>> >
>> >...it requires my .bashrc to be sourced (.bash_profile merely sources
>> >
On Wed, Feb 27, 2013 at 5:16 PM, Kevin Layer wrote:
>
> Did you read the original report and all the replies in the chain?
>
>...it requires my .bashrc to be sourced (.bash_profile merely sources
>.bashrc).
Then what is the value of $SHELL?
--
Earnie
-- https://sites.
Also, strace'ing startxwin was not fruitful--the program hangs without
putting up any windows or doing much work at all.
I'm open to more suggestions...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.c
Btw, this happens on my home and work systems. Both Windows 7
Ultimate x64.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
hing interesting.
I had created a .xinitrc with a single "xterm" call in it, but I was
still running startxwin.exe instead of xinit.exe, so because I had
renamed .startxwinrc to .startxwinrc.disabled, I was running with some
default init file for startxwin.exe.
The xterm that
; As for the assumption, I understand that an error could have
>> > short-circuited the processing of my init file, but in the bash's that
>> > haven't read it,
>> >
>> > . .bashrc
>> >
>> > produces no errors *and* has my aliases a
hort-circuited the processing of my init file, but in the bash's that
> haven't read it,
>
>. .bashrc
>
> produces no errors *and* has my aliases and new prompt.
$HOME/.bashrc isn't always read. It depends on how bash is executed.
If this is a --login you need $HOME
Andrey Repin wrote:
>> Greetings, Kevin Layer!
>>
>> > I know ~/.bashrc hasn't been read because my prompt is not changed and
>> > my aliases are not there.
>>
>> That's just assumption. Not the first-hand knowledge. It may be true, or
>&g
On Wed, Feb 27, 2013 at 11:37:52PM +0400, Andrey Repin wrote:
>Greetings, Kevin Layer!
>
>> I know ~/.bashrc hasn't been read because my prompt is not changed and
>> my aliases are not there.
>
>That's just assumption. Not the first-hand knowledge. It may be true,
Greetings, Kevin Layer!
> I know ~/.bashrc hasn't been read because my prompt is not changed and
> my aliases are not there.
That's just assumption. Not the first-hand knowledge. It may be true, or
not... Best way to know is to place
set -x
around the start of the file and obs
K Stahl wrote:
>> I normally start a terminal in my .xinitrc file (Place it in your home
>> directory):
>>
>> Example:
>>
>> #!/usr/bin/sh
>> urxvt -e bash -l & wmpid=$!
>> wait ${wmpid}
Bash started via .xinitrc *does* read my .bashrc. Inte
Jon TURNEY wrote:
>> On 27/02/2013 00:08, Kevin Layer wrote:
>> > If I put this into .startxwinrc:
>> >
>> > mintty /usr/bin/bash.exe --login -i
>> >
>> > the resulting shell does not read .bash_profile. If I put
>> >
>>
On 27/02/2013 00:08, Kevin Layer wrote:
> If I put this into .startxwinrc:
>
> mintty /usr/bin/bash.exe --login -i
>
> the resulting shell does not read .bash_profile. If I put
>
> mintty /usr/bin/bash.exe -i
>
> it doesn't read .bashrc.
I've tried t
I normally start a terminal in my .xinitrc file (Place it in your home
directory):
Example:
#!/usr/bin/sh
urxvt -e bash -l & wmpid=$!
wait ${wmpid}
Using this scheme, I haven't had the issues the original poster has described.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
e any of my
init files, either.
This is not a new issue. I only started to care about it recently
because I want to use ssh-agent/ssh-add in my .bashrc/.bash_profile.
As for PATH, it's set so that it can find the programs, so I'm pretty
sure that's neither here nor there.
More ideas
Dear Kevin (et al.) -- I use StartXWin all the time,
and start bash from an xterm, and the startup reading
of .bash_profile, etc., proceeds as documented.
Thinking it might be something about mintty, I tested
that as well, with --login and with just -i, and it
all works as expected, reading the p
Robert Pendell wrote:
>> Commonly .bash_profile does source in .bashrc so that it gets executed too.
Exactly what mine does. I just want to be clear: I have not been able
to get bash to source *anything* when started from startxwin.exe.
I've done hours of experimentation an
On 2/27/2013 10:36 AM, Robert Pendell wrote:
Dear Robert -- I think the original poster's
concern was not the general working of bash
with .bash_profile and .bashrc, but the
specific behavior when bash is started by
an instance of mintty which itself is started
by the X windows serv
>
>>> > the resulting shell does not read .bash_profile. If I put
>>> >
>>> >mintty /usr/bin/bash.exe -i
>>> >
>>> > it doesn't read .bashrc.
>>> >
>>> >
>>> > I've been beating my head against this
Arthur Tu wrote:
>> On 2/27/2013 8:08 AM, Kevin Layer wrote:
>> > If I put this into .startxwinrc:
>> >
>> >mintty /usr/bin/bash.exe --login -i
>> >
>> > the resulting shell does not read .bash_profile. If I put
>> >
>>
On 2/27/2013 8:08 AM, Kevin Layer wrote:
If I put this into .startxwinrc:
mintty /usr/bin/bash.exe --login -i
the resulting shell does not read .bash_profile. If I put
mintty /usr/bin/bash.exe -i
it doesn't read .bashrc.
I've been beating my head against this wall for hou
If I put this into .startxwinrc:
mintty /usr/bin/bash.exe --login -i
the resulting shell does not read .bash_profile. If I put
mintty /usr/bin/bash.exe -i
it doesn't read .bashrc.
I've been beating my head against this wall for hours, over a few
days. I've googled my
ether I use an administrator or non-administrator account.
>
> 1. Can anyone suggest a cause and/or solution to the inability of
> the non-administrator to shell out?
>
> 2. What about why the -v option doesn't seem to work when included
> in vim's shell option?
>
&
I goofed in that last post. Echoing the results of shelling out to register a
is done via:
:redir @a
!!ls
:w !cat
:redir END
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Uns
It is often more covenient to use the Windows install of gvim than to fire up
Cygwin's X-windows to run the Cygwin version of gvim. In order to be able to
bang out to run bash commands, I have this in my vimrc:
shell=c:\cygwin\bin\bash.exe\ -i
This allows me to do things like
!!ls
or
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="\[
On 6/20/2012 2:13 PM, gialloporpora wrote:
Hi all,
I have found this good tip:
http://www.mikaelkrok.net/component/content/article/44-java/131-use-cygwin-with-your-best-external-windows-text-editor
to use my Windows text editor to modify files.
I have added this line to my .bashrc file:
alias
term) echo "This is an xterm" ;;
|> */mintty) echo "This is a mintty" ;;
|> esac
|
|Barry, Ken,
|
|Thanks for your valuable scripting examples. It sent me scurrying back to the
|man page to figure out case/esac and command substitution. It's also a good
|reminder of
p is complete, I run "cygwin.bat" but cygwin does not create
the file. bashrc and. bash_profile.
as are his or her home directory. not in C: \ cygwin \ Home \ profile
but instead in C: \ Documents And Settings \ User
I've re-install up to 3 times but do not also fix
Can you help me?
mod
cygwin version 2.761
have a problem when installing cygwin,
I installed it with a clean
when setup is complete, I run "cygwin.bat" but cygwin does not create
the file. bashrc and. bash_profile.
as are his or her home directory. not in C: \ cygwin \ Home \ profile
but instead in C: \
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
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
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 [ $
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
>
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
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 script, and set the prompt colours accordingly. Now
find the file but it jerked back
> to the usual prompt so I was able to look inside my home/user/ directory.
> After using ls -a it showed that this directory was completely empty, no
> .bashrc, no .bash_profile. I'm fairly new to this so I don't know why this
> is happe
dn't find the file but it jerked back
to the usual prompt so I was able to look inside my home/user/ directory.
After using ls -a it showed that this directory was completely empty, no
.bashrc, no .bash_profile. I'm fairly new to this so I don't know why this
is happening? ANy help wo
On Thu, May 19, 2011 at 11:06 PM, Eric Blake wrote:
> "$HOME" expands $HOME, but "~/.bashrc" does _not_ expand ~. For
> tilde-expansion to occur, it must be unquoted.
Not only that, it has to be the first character:
3.5.2 Tilde Expansion
I can. And it's not cygwin-specific.
> for i in "$HOME/.bashrc" "~/.bashrc" ; do
"$HOME" expands $HOME, but "~/.bashrc" does _not_ expand ~. For
tilde-expansion to occur, it must be unquoted.
>if [ -a "$i" ]; then
Use
On 5/19/2011 3:54 PM, Lee Maschmeyer wrote:
>
> Hi all,
>
> For most uses, $HOME and ~ produce identical results. For example, ls
> $HOME
> or ls ~ are the same. But the following script fails:
>
> #!/bin/bash
>
> for i in "$HOME/.bashrc" "~/.bashrc&q
option may be used when the
shell is started to inhibit this behavior.
From your ~/.bash_profile file:
# source the system wide bashrc if it exists
if [ -e /etc/bash.bashrc ] ; then
source /etc/bash.bashrc
fi
Files under /etc/skel are templates that get copied into user home directories
login shell.
/etc/X11/xinit/xinitrc – executed when xwindows start, startup programs
--
View this message in context:
http://old.nabble.com/Order-of-.profile---.bashrc-tp30474750p30476188.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com
jwzumwalt sent the following at Thursday, December 16, 2010 12:39 PM
>
>My prompt and a few other items are not working correctly. I have found
>teh following startup files... are there any more? What is the order or
>priority of configuring?
>
>/etc/bash.bashrc
>/etc/profi
My prompt and a few other items are not working correctly. I have found teh
following startup files... are there any more? What is the order or priority
of configuring?
/etc/bash.bashrc
/etc/profile
/etc/skel/.bashrc
/etc/skel/.bash_profile
/etc/skel/.inputrc
$HOME/.bash_profile - commands
On Tue, Jun 22, 2010 at 9:13 PM, Thomas Shanks wrote:
...
> $ vimdiff /etc/skel/.bashrc ~/.bashrc
> 2 files to edit
> 7 [?47h [27m [24m [0m [H [J [25;1H"/etc/skel/.bashrc" 130L, 3754C
> "~/.bashrc" [25;13H [K [25;13H135L, 3884C 1 [main] gvim 175
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
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_
* 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
t: 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!
rogram creates some terminal links like:
>
> C:\cygwin\bin\run.exe /usr/bin/rxvt.exe -display 127.0.0.1:0 -tn
> rxvt-cygwin -e /bin/bash --login
>
> I just removed the --login option to preserve the results of ~/.bashrc,
> but then need to set up things like my prompt again as I loos
removed the --login option to preserve the results of ~/.bashrc, but
then need to set up things like my prompt again as I loose the other automatic
settings.
This was a new cygwin install, downloaded a couple of days ago.
I was trying to copy the skel/.bash_profile and got this:
$ cp /etc/skel
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 comments in /etc/profile seem to imply that
The ~/.bashrc file wasn't called by default and altering ~/.profile did fix the
problem.
The comments in /etc/profile seem to imply that ~/.bashrc should be run
on a per user basis automatically, but this was not the case.
...
# Setup some default paths. Note that this order will allow
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
>>
* 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 doe
~/.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. I *think* it's the KORN shell
that does... d
Great,
Thank you both. I now have .bash_profile calling ~/.bashrc.
Just had a look at the ~/.profile script on my linux box and I can see where it
is making the call to the local ~/.bashrc file
...
# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
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
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
Hello,
This problem has me stumped.
I have windows XP and cygwin with bash version 3.2.49(23)-release.
I have set my passwd file to include my home directory /home/blueneil.
I have placed .bashrc in my home directory and made it executable.
I have placed .bashrc_profile in my home directory
chengxianle writes:
> Yes, .bash_profile was loaded when run bash as `bash --login'.
> But still, won't load when run as `sh' or `sh --login'.
Look a little further back and you'll find Dave's informative answer to your
original query.
..mark
--
Problem reports: http://cygwin.com/problems
2009/7/12 chengxianle:
> Yes, .bash_profile was loaded when run bash as `bash --login'.
> But still, won't load when run as `sh' or `sh --login'.
Read Dave Korn's reply again.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentati
Hi, Tatsuro
Thanks for your help.
Yes, .bash_profile was loaded when run bash as `bash --login'.
But still, won't load when run as `sh' or `sh --login'.
Jason
2009/7/12 Tatsuro MATSUOKA :
> Hello
>
> Please make the file
>
> .bash_profile
>
>
Sorry
I have misled stories. Please ignore me.
--- Tatsuro MATSUOKA wrote:
> Hello
>
> Please make the file
>
> .bash_profile
>
> and describe
>
> source .bashrc
>
> in it
>
> Regards
>
> Tatsuro
> --- "chengxia...@gmail.c
Hello
Please make the file
.bash_profile
and describe
source .bashrc
in it
Regards
Tatsuro
--- "chengxia...@gmail.com" wrote:
> bash.exe loads my .bashrc in $HOME directory.
> But when i copy bash.exe as sh.exe, .bashrc won't be loaded.
> Rename as anythi
chengxianle wrote:
> bash.exe loads my .bashrc in $HOME directory.
> But when i copy bash.exe as sh.exe, .bashrc won't be loaded.
> Rename as anything(like sh1.exe, sh2.exe, ...) except `sh.exe' works fine!
By design. Invoking bash as 'sh' enters special sh-com
bash.exe loads my .bashrc in $HOME directory.
But when i copy bash.exe as sh.exe, .bashrc won't be loaded.
Rename as anything(like sh1.exe, sh2.exe, ...) except `sh.exe' works fine!
Jason
cygcheck.out
Description: Binary data
--
Problem reports: http://cygwin.com/problem
* 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 .ba
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 i
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
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
or the quick reply.
>
> 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. Did I do
> something wrong?
Have a look at /etc/passwd
ry for the confusion, I had modified my PS1 settings (which I
could
set after manually sourcing .bashrc) so I just put a % for my prompt in
the email.
If I start cygwin normally my prompt looks like this:
d.t...@imb09-02635 ~
$
Also
d.t...@imb09-02635 ~
$ echo $SHELL
/bin/bash
d.t...@imb
odified my PS1 settings (which I could
> set after manually sourcing .bashrc) so I just put a % for my prompt in
> the email.
>
> If I start cygwin normally my prompt looks like this:
>
> d.t...@imb09-02635 ~
> $
>
> Also
>
> d.t...@imb09-02635 ~
> $ echo $SHELL
-3143054254-1418:/cygdrive/c/Documents
and Settings/d.tang:/bin/bash
> In that dir you have .bashrc?
%ls /cygdrive/c/Documents\ and\ Settings/d.tang/.bashrc
/cygdrive/c/Documents and Settings/d.tang/.bashrc
Do you spot anything funny going on?
Your prompt and your home directory. Looks like you
e/c/Documents
>
> and Settings/d.tang:/bin/bash
>
> > In that dir you have .bashrc?
>
> %ls /cygdrive/c/Documents\ and\ Settings/d.tang/.bashrc
> /cygdrive/c/Documents and Settings/d.tang/.bashrc
>
> Do you spot anything funny going on?
Your prompt and your home direc
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 environmen
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.
1 - 100 of 222 matches
Mail list logo
