Closed kyptin closed 10 years ago
Hello,
Thanks for the descriptive problem description. lispwords
was a global setting until 7.4.201, when it became a global-local option:
https://groups.google.com/forum/#!topic/vim_dev/6Abi8nsY2Dc
As a consequence of this, set lispwords+=log-wrap
will append the global value, and setlocal lispwords+=log-wrap
will append the local value.
Apparently, set lispwords+=
also truncates the local value, presumably to cause &lispwords
to fall through to the global value.
So, if you have Vim version 7.4.201+, please confirm if using setlocal
solves your problem. If you have an earlier version, then this is a different problem.
Thanks for reporting!
Hmm, I wasn't aware of the global vs. global-local distinction, nor of the setlocal
command. Good to know!
I am using Vim 7.4.258, and I confirm that using setlocal
instead of set
makes it work perfectly. Many thanks!
Incidentally, thanks for all your work in the Clojure ecosystem, and kudos on getting a patch accepted for Vim. :-)
Hey, thanks for your work on vim-clojure-static. Definitely a timesaver for me!
I've stripped down my
.vimrc
file to an approximately minimal example:When I open a
.clj
file in Vim, everything works as expected, and I can type:set lispwords?
to get:…which looks good to me.
However, when I add the following line to my
.vimrc
:…I can quit Vim, open up the same
.clj
file, and get lispwords equal to:As you can see, in this case, lispwords is its default value, plus
log-wrap
. As you can imagine, this means my Vim experience involves a lot of manual indentation.Any idea what's going on here?
For what it's worth, I have Vim version 7.4, and I'm running on the latest version of this plugin.