[email protected] writes: > Hi, > > (I am using vim (console) on Linux.) > > When debugging vim setting it is possible to get informations > what code part has changed a setting/option at last as far as > I know. > > Is it possible to get informations about what code has changed > a setting/option before it was changed by the code which changed > it at last? > > This way it would be possible to either optimize scripts/.vimrc > or to remove superflous parts especially in .vimrc. >
One surefire way is to keep .vimrc under cvs. Recommit with every change. You then have access to any past version and quickly see what changed and be able to figure out what it did. Cvs isn't too hard to learn to use.. but will take some learning. You might think it would hamper you in using vim but the way I do is create a symlink ~/.vimrc linked to the .vimrc under cvs. You can edit add subtract all you want, just like any file... but you do have to remember to use a few cvs commands to commit the file when you've made a change your not sure of. Using symlinks like that for cvs files might not be such a good idea on a multi user machine but if the machine is your own and you have no other users to worry about.. then no problems. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
