On Sat, Jan 23, 2010 at 06:02:05PM -0500, James Vega wrote: > Are you still seeing this? I had been, but when I sat down to give it a > good look this weekend, everything was working fine. If you are still > seeing it, can you try running ???vim -u NORC -N??? to eliminate any > interactions from your vimrc?
I was still seeing this until a week ago. I noticed there hadn't been any activity on the bug since I last commented, so I contacted the author of the script directly. He wasn't aware of the Debian bug, and couldn't reproduce it on his end, so we worked together to fix it. There was a bug in his script that wasn't processing properly if the default shell was csh or tcsh. He has a new version that works for me regardless of where /bin/sh points to; he said he wanted to do more testing before publishing it, and after he was done he'd upload it to the project page at vim.org. I'll reply back here with the version number once I notice it's uploaded so it can be included in future versions. (This is the message I tried to send 12 hours ago; for some reason, it didn't seem to go through, and now I see you've sent him a patch already; oh well, I tried.... But, your patch was the same fix he'd come up with.) Tim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
