> OS is : mandrake chrooted on ubuntu :) > so timing is not an issue
Well, *nix-like OSes tend to exhibit a wider range of console flow/timing issues, so it's still a possibility. however, if it works with "vim -u NONE", it's likely a startup file/mapping that's interfering >> apropos, so the solution may be elsewhere such as mappings. >> >> If the timeoutlen isn't the culprit, check your mappings. >> Examine the output of [snip] > <End> :gw [snip] >> vim -u NONE file.txt > > works fine :) Sounds like you have some suspect mappings. You can find out which plugin/script is responsible (particularly for the above "<End>" entry) by doing :verbose map :verbose map! I don't have any Ex ":gw" command in my vim7.0 here which makes that all the more suspect. However, I'd guess that was intended to be done without the ":", but it's still a hinky mapping for <end> -tim --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
