X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,TW_RX,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: =?UTF-8?B?UmVuw6kgQmVyYmVy?= Subject: Re: vi in rxvt-Session really slow Date: Fri, 08 Jul 2011 17:03:00 -0500 Lines: 39 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.0 In-Reply-To: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id p68M3iYd014750 On 7/8/2011 2:27 PM, Dieter wrote: > Originally it was set to rxvt-cygwin-native That will only be recognized on systems with a recent terminfo, Linux mostly. I change it to rxvt since I use Solaris most of the time, and it doesn't recognize cygwin or any derivatives (of course I could modify terminfo). > Details to my vi-problem: > When I press Enter after "vi /etc/resolv.conf" it needs around 4 seconds to open > the vi-Editor on a multicore-machine... when I connect to the same machine using > putty or ssh in the basic-bash-console instead of the cygwin-ssh-client in a > rxvt-terminal there is no noticeable delay between pressing Enter and appearing > the vi-screen. > > Any hints? With a Windows console TERM is set to cygwin, which explains the other answer you found. The problem is not on Cygwin, but on the other end, whatever it is... as I said, I don't see the problem with either Solaris or Linux (several versions of both). A workaround could be to use vim (which is the usual vi on Linux) or any of the other variants of vi. A solution depends on what the real problem is, vim has options to not load plugins (which many times are a PITA), not use .vimrc, and to change the terminal type; I would use those to see if the problem is caused by any of those 3. -- René Berber -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple