Larry Hall (Cygwin) wrote:
On 10/5/2010 10:12 AM, Daniel Barclay wrote:
Larry Hall (Cygwin) wrote:
On 10/4/2010 12:19 PM, Daniel Barclay wrote:
...
Can anyone confirm (or "anti-confirm") this behavior?:
...
When bash is started using the Cygwin shortcut (which runs cygwin.bat,
which execute
On 10/5/2010 10:12 AM, Daniel Barclay wrote:
Larry Hall (Cygwin) wrote:
On 10/4/2010 12:19 PM, Daniel Barclay wrote:
I wrote:
The behavior of "bash --login -i" seems to vary depending on whether
it is a "root" invocation or a nested invocation of bash. This is
inconsistent with the description
Larry Hall (Cygwin) wrote:
On 10/4/2010 12:19 PM, Daniel Barclay wrote:
I wrote:
The behavior of "bash --login -i" seems to vary depending on whether
it is a "root" invocation or a nested invocation of bash. This is
inconsistent with the description man bash, and seems to be a bug.
Can anyone
On 10/4/2010 12:19 PM, Daniel Barclay wrote:
I wrote:
The behavior of "bash --login -i" seems to vary depending on whether
it is a "root" invocation or a nested invocation of bash. This is
inconsistent with the description man bash, and seems to be a bug.
Can anyone confirm (or "anti-confirm")
I wrote:
The behavior of "bash --login -i" seems to vary depending on whether
it is a "root" invocation or a nested invocation of bash. This is
inconsistent with the description man bash, and seems to be a bug.
Can anyone confirm (or "anti-confirm") this behavior?:
Details:
When bash is st
The behavior of "bash --login -i" seems to vary depending on whether
it is a "root" invocation or a nested invocation of bash. This is
inconsistent with the description man bash, and seems to be a bug.
Details:
When bash is started using the Cygwin shortcut (which runs cygwin.bat,
which execu
6 matches
Mail list logo