Ken Brown cornell.edu> writes:
>
> Another (easier) thing you could do is try various snapshots between
> versions 1.7.10 and 1.7.11 of cygwin1.dll and pinpoint exactly when the
> problem first occurred.
>
> Ken
>
>
Sadly, even the oldest cygwin1.dll snapshot (from 7/30/11) seems to have t
Corinna --
> This problem is fixed in CVS for a while. Please test the latest
> developer snapshot from http://cygwin.com/snapshots/
Aha! Thanks!
-- Pat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin
On 03/08/2012 02:45 AM, Harry Simons wrote:
Basically, I want my scripts to be able to run flawlessly on both
Fedora and Cygwin/Windows systems.
I have a universal .bashrc file that I use on Linux, Cygwin
and the occasional FreeBSD or NetBSD systems. In it I make
use of "uname -s" to handle pe
On Sun, Mar 11, 2012 at 12:35:02AM +0100, Fredrik Ludvigsen wrote:
> I think I solved this,
>
> the files
>
> >/etc/bash.bash_logout
> >/etc/profile.d
> >/etc/profile.d/tzset.sh
> >/etc/profile.d/tzset.csh
> >/etc/profile.d/lang.csh
> >/etc/profile.d/lang.sh
> >/etc/bash.bashrc
> >/etc/skel/.inpu
OMG I didn't realize I had to exit the shell and start a new one. Thanks, it
worked!
Old shell console:
$ splitpath
/usr/local/bin
/usr/bin
/cygdrive/c/WINDOWS/system32
/cygdrive/c/WINDOWS
/cygdrive/c/WINDOWS/System32/Wbem
/cygdrive/c/WINDOWS/system32/WindowsPowerShell/v1
On 3/11/2012 3:42 PM, Ken Brown wrote:
On 3/11/2012 3:19 PM, Jack Profit wrote:
After upgrading my cygwin environment this morning to version
1.7.11-1, I am no longer able to use cygwin bash as a shell within
native GnuEmacs (Windows).
When I invoke M-x shell, I now get the following output in
On 3/11/2012 3:19 PM, Jack Profit wrote:
After upgrading my cygwin environment this morning to version
1.7.11-1, I am no longer able to use cygwin bash as a shell within
native GnuEmacs (Windows).
When I invoke M-x shell, I now get the following output in the shell window:
bash: cannot set term
After upgrading my cygwin environment this morning to version
1.7.11-1, I am no longer able to use cygwin bash as a shell within
native GnuEmacs (Windows).
When I invoke M-x shell, I now get the following output in the shell window:
bash: cannot set terminal process group (-1): Inappropriate ioct
Leo letterboxes.org> writes:
>
>
> On 01/03/2012, at 3:35 AM, wytten wrote:
>
> >
> > I have the same issue. More information: If you back down cygwin bash to
> > BASH_VERSION='3.2.51(24)-release', the messages about job control no longer
> > appear when bash starts. However I still can't i
On Mar 9 17:09, Pat Tressel wrote:
> Got another console / bash oddity that just started...
>
> When I start a bash window with C:\cygwin\Cygwin.bat, which runs bash as...
>
> bash --login -i
>
> ...doing ^C gets no response: It doesn't clear typing, it doesn't go
> back to the shell, it doesn
10 matches
Mail list logo