From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9068 invoked by alias); 23 Sep 2003 04:08:28 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 9044 invoked from network); 23 Sep 2003 04:08:25 -0000 Received: from unknown (HELO mailo.vtcif.telstra.com.au) (202.12.144.17) by sources.redhat.com with SMTP; 23 Sep 2003 04:08:25 -0000 Received: (from uucp@localhost) by mailo.vtcif.telstra.com.au (8.8.2/8.6.9) id OAA11973 for ; Tue, 23 Sep 2003 14:08:21 +1000 (EST) Received: from maili.vtcif.telstra.com.au(202.12.142.17) via SMTP by mailo.vtcif.telstra.com.au, id smtpda8m9v_; Tue Sep 23 14:07:53 2003 Received: (from uucp@localhost) by maili.vtcif.telstra.com.au (8.8.2/8.6.9) id OAA16722 for ; Tue, 23 Sep 2003 14:07:53 +1000 (EST) Received: from localhost(127.0.0.1), claiming to be "mail.cdn.telstra.com.au" via SMTP by localhost, id smtpd0_PKLo; Tue Sep 23 14:07:38 2003 Received: from WSMSG0004.srv.dir.telstra.com (wsmsg0004.srv.dir.telstra.com [192.74.168.133]) by mail.cdn.telstra.com.au (8.8.2/8.6.9) with ESMTP id OAA19692 for ; Tue, 23 Sep 2003 14:07:38 +1000 (EST) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MIMEOLE: Produced By Microsoft Exchange V6.0.6249.0 Subject: Bug in Bash 2.05b.0(13) with nt-emacs Date: Tue, 23 Sep 2003 05:41:00 -0000 Message-ID: <231DAA6464F5D311B0A30008C7F90735074CABB2@ntmsg0134.corpmail.telstra.com.au> From: "Maslen, David M" To: X-SW-Source: 2003-09/txt/msg01435.txt.bz2 Please accept this fairly brief, bug report. I'm using GNU Emacs 21.3.1 on Windows2000 (not the cygwin build) I'm using cygwins bash 2.05b.0(13) command as my explicit-shell-command fro= m within emacs and have c:\cygwin\bin in my path. This previously allowed me to use bash as the shell from within emacs. After an cygwin upgrade, this no longer worked. Bash would start, but I cou= ld not use any other shell commands (ie. ls) internal bash commands such as= 'cd' did seem to work. Changing my explicit-shell-command to be cygwin's sh command works as bash= used to.=20 Using eshell also seems to be a viable alternative. I don't subscribe to this list, and am not entirely sure that this is the m= ost appropriate place to submit bugs. If I can provide further information, please contact me directly. Otherwise= thanks to the cygwin developers for the work they've done so far in provid= ing a *nix like environment in the windows wilderness. -- David Maslen Solution Designer=20 Phone: (03) 8661 3443=20 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/