Hi, >> stanza, and its omission does not allow the user to prevent the >> loading of the extra lisp scripts through the intervention of their >> own ~/.vim/ftplugin/scheme.vim. > I'm not familiar enough with either scheme or plain Lisp (Common > Lisp?) to comment on whether the inclusion is appropriate. I assume > the plugin author did it for a reason.
I believe that it was done as a quick lazy hack, in order to add minimal support at a minimal cost. The fact that it is completely outdated, not actively maintained, and that the author belongs to a group that develops a full-fledged Scheme editor (namely Dr Racket, formerly Dr Scheme) makes me believe so. > I would certainly support this. My point was not that scheme MUST > source the Lisp files, only that it is not incorrect for it to do so, > so the slimv plugin author should make his/her plugin work with the > existing runtime, at least for the time being. This has been implemented a couple of days ago, after I discussed with slimv's author. I haven't had the opportunity to try the updated version, though. I would still appreciate that the patch be included, for consistency reasons. It may break a few existing plugins that rely on lisp's code inclusion, but I guess it's better to have this happen now, rather than when vim becomes a decent scheme editor (which it is on the verge of becoming, I believe) in which case it would impact more people. Cheers, P! -- Français, English, 日本語, 한국어 -- 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
