Christian Brabandt

> Why should &iskeyword be set in syntax/*.vim? That's probably mostly old syntax file from before `:syn iskeyword` was available. In general however those changes should come via their respective...

Thanks, can I ask you to check back with the maintainers of the file first?

I would check the header of the file. Sometimes an upstream repository is given, you can send your PR over there then. Most Maintainers however use email and many are...

ping @dkearns

1) Using help files is not recommended, since Vim does set some (built-in) options for those filetypes. Does that reproduce with a non-helpfile? 2) I thought it was documented that...

> Ok, but note that the example code in tag-function is still broken, because it tried to redefine global function CompareFilenames without using bang Yeah, that complains when sourcing it...

That is not possible. You can either drop the undo changes completely, by setting the 'undolevels' to `-1` or you can join new modifications with existing modifications using `:undojoin`. But...

your are essentially just recommending to prune and disable undo (that is what I said before). And that means you will **delete** all your undo changes once your re-edit a...

I see that it is not so nice. There is the ":undojoin" command. But as said before, it can only join changes to an existing undochange. However after you initially...

We can at least add `:undojoin` the compression (in case there are additional changes to the plugin). And certainly we should cleanup the gzip plugin. Not sure if [this](https://github.com/chrisbra/vim/blob/c412d2b66a28d7741069594fb37b2f0d68005948/runtime/autoload/gzip.vim) helps...