X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: Date: Wed, 16 Jul 2008 14:33:08 -0400 From: "Mark J. Reed" To: cygwin AT cygwin DOT com Subject: Re: Freeze with the letter "e" In-Reply-To: <4cee11bc0807161103v79d2c893of1765539f1bd02ad@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <005101c8e5ef$2ba90220$34ef5248 AT SweetLou> <20080714203321 DOT GC22253 AT ednor DOT casa DOT cgf DOT cx> <487D80AB DOT 5000702 AT cs DOT cmu DOT edu> <20080716145359 DOT GA28882 AT ednor DOT casa DOT cgf DOT cx> <4cee11bc0807161103v79d2c893of1765539f1bd02ad AT mail DOT gmail DOT com> X-Google-Sender-Auth: 28857a3969d48225 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 On Wed, Jul 16, 2008 at 2:03 PM, Sam Hanes wrote: > I think what he's trying to say In Mr. Faylor's his own inimitable way... > is that having DOS-style (CR-LF) line > endings in a *NIX-style file (which uses LF line endings) can have > very strange results Apparently! I've seen several threads on this list about similar problems, some of which seemed to affect only specific readline-aware applications (e.g. gnupg) and not others. Which makes me curious about the specific types of entries which could have such an effect when altered by the insertion of a CR. My own .inputrc has never gotten more complicated than "set editing-mode vi", so I'm admittedly pretty ignorant of the general realm of inputrc parameters, but seeing an example of one of the offending files might be educational. -- Mark J. Reed -- 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/