Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: "Kevin Wright" To: Subject: RE: Backspace prob with vim under rxvt - solution - fixdel Date: Fri, 21 Apr 2000 12:01:33 -0700 Message-ID: <00cb01bfabc4$037b1180$8f88f726@holstein.ASPECTDV.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-reply-to: <00ca01bfabbf$0341f260$8f88f726@holstein.ASPECTDV.COM> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Ok, maybe I can put this one to rest. After doing some more searching through vim's online help, I came across a setting called fixdel. Partial output from help fixdel: If your delete key terminal code is wrong, but the code for backspace is alright, you can put this in your .vimrc: :fixdel This works no matter what the actual code for backspace is. This basically works except that it only works in command-mode, not in insert mode. It also works in ex mode, which is a big help. This is something I can live with. Thanks to Bram Moolenaar for putting in online help. It's one of the *many* reasons I use vim. And thanks to Chuck and John for offering assistance. --Kevin -----Original Message----- From: cygwin-owner AT sourceware DOT cygnus DOT com [mailto:cygwin-owner AT sourceware DOT cygnus DOT com]On Behalf Of Kevin Wright Sent: Friday, April 21, 2000 11:26 AM To: cygwin AT sourceware DOT cygnus DOT com Subject: RE: Backspace prob with vim under rxvt Chuck, John, etc. I have some more import information that may pinpoint the real culprit. After some more testing, the backspace problem in vim under rxvt (or wterm) occurs under my build of WindowMaker 0.60 as well as twm (from the X11 build by Suhaib) or if I bring up the rxvt without any window manager. If I use mwm (care of Suhaib's lesstif's build) the problem doesn't occur. What's different about mwm, I have no idea. Here's some more info: STTY SETTING: ~ > stty -a speed 38400 baud; rows 25; columns 80; line = 56; intr = ^C; quit = ^\; erase = ^H; kill = ^U; eof = ^D; eol = M-^?; eol2 = M-^?; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts -ignbrk brkint ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany imaxbel opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -tostop echoctl echoke VIMRC: The problem occurs regardless of whether I have a .vimrc or not. INPUTRC: The problem occurs regardless of whether I have a .inputrc or not. There must be some single point of failure. By the way, I use Exceed 6.1 as my X-server. Thanks for all the help so far. --Kevin -----Original Message----- From: Charles S. Wilson [mailto:cwilson AT ece DOT gatech DOT edu] Sent: Friday, April 21, 2000 9:55 AM To: John A. Turner Cc: Kevin Wright; cygwin AT sourceware DOT cygnus DOT com Subject: Re: Backspace prob with vim under rxvt "John A. Turner" wrote: > > I don't see this behavior. What are your stty settings, CYGWIN > > variable settings, .inputrc contents, and .vimrc contents? > > what do you recommend for those? my .inputrc contains a single line: "set bell-style none" my stty settings are the default ( I run no explicit command in any dot files to set them ) but stty reports: speed 38400 baud; line = -96; eol = M-^?; eol2 = M-^?; CYGWIN=tty ntea nontsec binmode My .vimrc is huge. 'nuff said. My point was not that everyone should copy my settings, but that there may have been some obvious thing in Kevin's settings that was messing things up; e.g. 'stty erase ^h" or something similar but wrong. To tell you the truth, I can't seem to get backspace to *not* work in vim, even after messing up the CYGWIN and stty settings...go figure. > > anyway, when I use your build, with your libX11.dll, it keeps failing > with: > > _X11TransSocketINETConnect: Can't connect: errno = 111 > My build is a true X11 app, and therefore requires an Xserver running on your computer. --Chuck -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com