Max Dyckhoff wrote:
Hi Gary, and Yakov,
I'm sorry, I'm feeling terrible today so my bug reports aren't very
comprehensive. More information!
WinXP, GVIM 7.0 compiled by Bram.
I don't have many plugins, the major ones being Lookupfile and associated
plugins and vimoutliner. I seriously suspect vimoutliner is the culprit.
But that is actually only half of the story. The bad << mapping doesn't exist
in a clean vim, even with all my plugins running, it only exists in the current
session of vim that I am using. I run vim with 7 tabs open, each containing at least
two files. I have three tabs full of .cpp files that I am working on, a tab with some
AI scripting files, a tab with some HTML docs that I am writing, a tab with some init
files, a tab with my .vimrc and a tab with my todo.otl file for vimoutliner.
When I reboot I do a :mksession ~/work_session.vim, and when I come back I :so
~/work_session.vim so I can continue where I left off. This saves me loads of
time reopening the 20 or so C files that I am working on at any one time, as
well as all the various supporting files listed above.
This session has been around for a few weeks, and I keep :mksession-ing and
:so-ing it. When I :so it I get an error in one of my HTML docs, but it doesn't
seem to fail so I'm not worrying.
Do you think the session is somehow corrupted? It happens if I make the session
again cleanly (open all the files in a new vim session, :mksession, :so
session, observe strange behaviour), so just trashing the session and starting
again isn't really an option, as the problem will come back within a couple of
days.
Max
The next time the problem happens, don't change windows (not even by opening a
help topic) and immediately do:
:scriptnames
:verbose map <<
:verbose map! <<
:verbose abbrev <<
Keeping the active cursor in the problematic file is important to avoid
missing <buffer> mappings for that file.
Maybe it will give you a hint about where to look next. (The first time the
problem happens in a "clean" session, the culprit might be a script appearing
near the end of the ":scriptnames" listing. But that's only a possibility, not
a certainty.)
Remember that you're the only one with hands-on access to your computer so
you're the one best placed to find the answer to your problem.
Best regards,
Tony.
