Greetings, Chris J. Breisch!
> On 3/1/2013 10:49 AM, Kevin Layer wrote:
>>
>> Don't have cron running. I start it as me, the logged in user, from a
>> mouse click or running "startxwin" in a mintty. Behaves the same
>> either way.
> Well, I am unable to duplicate this no matter what I do. I hav
On 3/1/2013 10:49 AM, Kevin Layer wrote:
Don't have cron running. I start it as me, the logged in user, from a
mouse click or running "startxwin" in a mintty. Behaves the same
either way.
Well, I am unable to duplicate this no matter what I do. I have even
launched a dash shell directly fro
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 requires my .bashrc to be sourced (.bash_profile merely sources
>>>
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
>> >.bashrc).
>>
>> Then what is the value of $SHELL?
/bin
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.google.com/site/earn
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
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}
Turns out, I'm mistaken, but I found out something interesting.
I had created a .xinitrc with a single "xte
Earnie Boyd wrote:
>> On Wed, Feb 27, 2013 at 3:15 PM, Kevin Layer wrote:
>> > That was one of the experiments I did, and I saw no evidence that any
>> > commands were executed. I even passed it as the argument to the
>> > invocation.
>> >
>> > As for the assumption, I understand that an error co
On Wed, Feb 27, 2013 at 3:15 PM, Kevin Layer wrote:
> That was one of the experiments I did, and I saw no evidence that any
> commands were executed. I even passed it as the argument to the
> invocation.
>
> As for the assumption, I understand that an error could have
> short-circuited the process
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
>> not... Best way to know is to place
>> set -x
>> around t
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, or
>not... Best way to know is to
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 observe the results.
>
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. Interesting!
I'll play more with this tonight to see if
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
>> >
>> > mintty /usr/bin/bash.exe -i
>> >
>> > it doesn't read .bashrc.
>>
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 to reproduce this, but it seem to work
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:
Eliot, thanks for the reply.
The passwd/group was an interesting thought. Unfortunately:
@oob2$ mkpasswd -l > passwd.new
@oob2$ diff passwd passwd.new
@oob2$ mkgroup -l > group.new
@oob2$ diff group group.new
@oob2$
It's not just mintty. When I run xterm, it doesn't source any of my
init fil
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 and done many variation
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 server in .startxw
On Tue, Feb 26, 2013 at 10:20 PM, Kevin Layer <> wrote:
> 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
>>> >
>>> >m
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
>> >
>> >mintty /usr/bin/bash.exe -i
>> >
>> > it doesn't read .bashrc.
>> >
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 hours, over a f
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 ass off, but I can
26 matches
Mail list logo
