X-Spam-Check-By: sourceware.org Message-ID: <83c75fec0605301033p1fe219a9ve490ce0559a7daf4@mail.gmail.com> Date: Tue, 30 May 2006 21:33:51 +0400 From: "burning shadow" To: cygwin AT cygwin DOT com Subject: Re: bash 3.x path completion problems In-Reply-To: <83c75fec0605301007n57fbcd80x2e828e10dda436ed@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <83c75fec0605300940s4bb1363s5aa58d8b42e195c3 AT mail DOT gmail DOT com> <83c75fec0605301007n57fbcd80x2e828e10dda436ed AT mail DOT gmail DOT com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > Like I said, it's unlikely that this is the thing that makes the difference, but you could > always have a quick try with the latest snapshot just in case: > http://cygwin.com/snapshots. It might also be trying the different cygwin terminals, xterm > and rxvt as well as plain old dos console. Oh, by the way. I'm working via SSH using PuTTY client. Maybe this is the case. I'll try snapshots later, thanks. -- 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/