On 2008-10-30, Tim Johnson <[EMAIL PROTECTED]> wrote: > On Thursday 30 October 2008, Tim Johnson wrote: > > I'm using vim 7.1 on kubuntu 7.10 > > A very bizarre and disturbing thing is occuring. > > When I start vim, it logs one and only one file. > > regardless of the file on the command line. > > Furthermore, if I do :ls! regardless of where I have > > started vim, I am logging the same directory. > I mistated "logs one and only one file". Should have > written "loads one and only one file". I have solved > it by > 1)run vim --help > 2)take note of the --noplugin switch and invoked vim > with that switch. Loaded normally. > 3)Surveyed my .vim directory looking at plugin and > ftpplugin directories, saw a session.vim file in > the ~/.vim/plugin directory and deleted it. > that solved the problem. > However, since I depend on vim so much and :-) and am > called on to trouble-shoot vim so seldom, I'd welcome > comments and links to a "In case of Emergency" site(s) > for vim if such exists. Or a list of "vim gotchas"
In my experience, gotchas are where you find them. Rather than a list of gotchas, it helps to have some idea of how your OS and vim operate and some knowledge of basic troubleshooting. For example, when you execute "vim" at a shell prompt, the shell could execute an alias, a function, or the first instance of an executable file named "vim" in your PATH. You should be able to determine which it is. When vim starts, it conditionally loads a whole bunch of stuff. To find out what that is, execute ":scriptnames". To avoid loading any of it, start vim as "vim -u NONE". Other options, such as the --noplugin you found, can be used to further select what's loaded and what's not. It helps to be familiar with at least the concepts described in ":help startup". The ":version" command or --version option can be used to find out what kind of vim you have: the version, the patch level, the features it was compiled with and the libraries it was linked with. The ":verbose set <option>?" command is really useful for finding where an option was set, in case the problem is that an option is being changed unexpectedly. There are a lot of tools and techniques available for troubleshooting vim. Like troubleshooting anything else, which you use depends on your knowledge of the system and of the events that preceded the problem. HTH, Gary --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
