On 21/02/09 14:02, Markus Heidelberg wrote:
> Tony Mechelynck, 21.02.2009:
>> On 21/02/09 06:30, Bram Moolenaar wrote:
>>> Ben Fritz wrote:
>>>
>>>> Saw this interesting post to a tip on the wiki:
>>>>
>>>> http://vim.wikia.com/index.php?title=Fix_broken_arrow_key_navigation_in_insert_mode&diff=22116&oldid=prev
>>>>
>>>> Apparently this xterm bug report:
>>>>
>>>> http://bugs.gentoo.org/212546
>>>>
>>>> has been blamed on Vim, but for whatever reason the poster does not
>>>> expect useful help from this list.
>>>>
>>>> Just making sure people were aware of it here.
>>> I'm missing the part where it says what exactly it is that Vim would be
>>> doing wrong. I don't see the problem anyway.
>>>
>> A comment to that bug report says the problem disappears when invoking
>> "xterm -kt vt220". From what I can tell, the problem seems to be related
>> with some gentoo-specific "bugfixes" (sic) to the xterm code and/or
>> configuration.
>
> Which comment in the bug report leads you to such an assumption?
> Gentoo is one of the sane distributions, that believe patches belong to
> upstream instead of damaging the packages. And actually Gentoo doesn't
> add patches to xterm, it fetches
> ftp://invisible-island.net/xterm/xterm-239.tgz, extracts and compiles
> it. The only modifications are these in the build script:
>
> # Fix permissions -- it grabs them from live system, and they can
> # be suid or sgid like they were in pre-unix98 pty or pre-utempter days,
> # respectively (#69510).
> # (info from Thomas Dickey) - Donnie Berkholz
> fperms 0755 /usr/bin/xterm
>
> # restore the navy blue
> sed -i "s:blue2$:blue:" "${D}"${DEFAULTS_DIR}/XTerm-color
>
> # Fix for bug #91453 at Thomas Dickey's suggestion:
> echo "*allowWindowOps: false">> "${D}"/${DEFAULTS_DIR}/XTerm
> echo "*allowWindowOps: false">> "${D}"/${DEFAULTS_DIR}/UXTerm
>
> Whereas if I look into
> http://download.opensuse.org/source/distribution/11.1/repo/oss/suse/src/xterm-236-1.42.src.rpm
> I can see several patches. I don't say there is no reason for them, but
> you can mostly be sure, that Gentoo doesn't introduce bugs with patches,
> as it's done in other distributions.
>
> I use Gentoo and have 239 installed and it works, I also successfully
> tested 235 and 237 (there is no ebuild for your version 236) when
> invoking xterm without arguments. With -kt vt220 it doesn't work
> correctly in all the tested versions. Maybe you can try it once with
> this command line argument?
>
> Markus
>
>
Well, I tried to understand what was said in the various comments to
that bug; maybe I misunderstood, or maybe I thought the mentioned
changes were "Gentoo patches" when they were actually "X.org patches".
Here, without that command-line argument, but not with it, Vim correctly
distinguishes between <Home> <End> <S-Home> <S-End> <C-Home> <C-End>.
With the argument, they are all seen as <kHome> <kEnd> regardless of
Shift and Ctrl (I'm using the "grey" keys, not the "NumLock-off numeric
keyboard", and I checked with the Ctrl-K prefix). "Ordinary" (unshifted
un-Ctrl-ed) arrow keys, and the "ordinary" F1 key (I didn't check the
other F keys), work OK in both cases. In both cases, xterm sets $TERM to
xterm even if started with $TERM unset, or set to the empty string.
Using "export TERM=vt220" within xterm before starting Vim makes all
"special keys" unrecognized: obviously -kt vt220 does not make xterm
behave as a "real" vt220.
Best regards,
Tony.
--
There is a certain impertinence in allowing oneself to be burned for an
opinion.
-- Anatole France
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
