On Jan 6, 4:21 am, Adrien "Axioplase" Piérard <axioplase [email protected]> wrote: > Hello, > > As a scheme and common lisp programmer, I have started using a very > nice plugin recently, namely "slimv" > (http://www.vim.org/scripts/script.php?script_id=2531). > It currently has an issue which seems to be rooted in vim's defaut > configuration : whenever a scheme file is loaded, the slimv's lisp > related ftplugins are all executed as well and wreak havoc. > According to slimv's author, > > > No, there is currently no option to choose what languages to activate > > slimv for. And the problem with scheme is that even if you try to just > > simply delete the scheme related files (e.g. > > vimfiles/ftplugin/scheme/slimv-scheme.vim), slimv will be loaded > > because of vim's built-in ftplugin/scheme.vim, which contains this > > line: > > runtime! ftplugin/lisp.vim ftplugin/lisp_*.vim ftplugin/lisp/*.vim > > that explicitly loads all "lisp" related filetype plugins for scheme > > files, therefore also vimfiles/ftplugin/lisp/slimv-lisp.vim. > > Even though this may have been convenient, I believe that this is a > bug and should be fixed accordingly, by separating scheme and lisp in > the distribution of vim. >
Scheme IS Lisp. http://en.wikipedia.org/wiki/Scheme_(programming_language) says, "Scheme is one of the two main dialects of the programming language Lisp." It should be completely possible for the plugin author to set some global or buffer-local variable to indicate which language is actually being used (or maybe just check the 'filetype' option) and act accordingly. This is a plugin bug, not a Vim bug. -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
