Improve README with ftdetect gotcha

[ixti]

See:

• Vim sets filetype to HTML (not Slim) when using 'doctype html' #38
• 1ac9ebd

[rapind]

Interesting to note that we had set filetype=slim in master a couple years ago, but it was changed back for some reason (not sure why). See: 1ac9ebd

[ixti]

@igas @rapind What do you think about the PR now?

[ixti]

Instead of brute forcing filetype, I think we should just inform users of the issue and how to fix it.

[rapind]

@ixti I definitely think this is an improvement. It's kind of a strange use case that has you scratching your head, so documenting it is definitely nice for user's that hit it.

[rapind]

did you mean which overrides previous values instead of which does not overrides?

[rapind]

set fieltype does override. setf does not.

[ixti]

@rapind although I understand your point of view (and I'm actually gonna use set filetype=slim in my .vimrc). I think there is a pretty small but still possible chance of causing issue for some potential user of this plugin if we will go obtrusive way.

And personally I think that any plugin should do as little as possible by default. So that user would configure/enable necessary behavior himself as he needs.

[rapind]

I've also changed it locally. I just think it'll impact more people by being unobtrusive, and I haven't been able to think of a scenario where being obtrusive would impact anyone (why would they assign something else to .slim?).

I'm happy enough with a mention in the readme though. We've probably discussed it to death at this point :)

[ixti]

@rapind I can't recall at the moment but I remember I saw couple of absolutely different projects using same filename extensions for their files.

[ixti]

@minad Please merge this, if you have no objections.

[ixti]

This PR does not changes current behavior, but adds README description of it and how to change to be more "enforced".

[minad]

@ixti @genki @rapind I cannot really judge this and it would be good if we have someone maintaining the vim scripts. Is any one of you willing to do so?

[ixti]

@minad I'm not proficient in VimL to call myself a good candidate to be a maintainer, but I'm definitely will be happy to help. In any case, this particular change is not adding changes to the vim script itself ;)) it's adding explanation to the README why current version does not work in a very specific situation as one might expect, and how to avoid this.

[rapind]

@minad I've literally never even touched VimL. At most just tweaked my own configs. I don't even get a chance to use slim much these days either :(

[ixti]

Closing this due to no activity (I assume no interest as well) from maintainers side.

[minad]

@ixti As I wrote above, there is a need of someone maintaining this. Even if the maintainers are not very proficient in Viml, they could still take care that the PRs get tested and merged...