<div dir="ltr"><span style="font-family:Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:12.8px">As mentioned on other bug reports, this is an order-of-inclusion issue. </span><br style="font-family:Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:12.8px"><br style="font-family:Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:12.8px"><div style="font-family:Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:12.8px">  1: /usr/share/vim/vimrc</div><div style="font-family:Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:12.8px">  2: /usr/share/vim/vim80/debian.<wbr>vim</div><div style="font-family:Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:12.8px">  3: /etc/vim/vimrc.local</div><div style="font-family:Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:12.8px">  4: /usr/share/vim/vim80/defaults.<wbr>vim</div><div style="font-family:Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:12.8px">  [snip]</div><div><br><font face="Roboto, Helvetica Neue, Helvetica, Arial, sans-serif"><span style="font-size:12.8px">defaults.vim is being loaded *after* vimrc.local, which means that vimrc.local is useless for overriding the package default settings. This is not the expected behavior. </span></font><br><br><font face="Roboto, Helvetica Neue, Helvetica, Arial, sans-serif"><span style="font-size:12.8px">Suggesting that each individual user on a system should supply their own .vimrc is a ridiculous non-solution, especially since the functionality exists to set system-wide defaults. </span></font><br><br><font face="Roboto, Helvetica Neue, Helvetica, Arial, sans-serif"><span style="font-size:12.8px">Prematurely closed bugs:</span></font><br><font face="Roboto, Helvetica Neue, Helvetica, Arial, sans-serif"><span style="font-size:12.8px"><a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837761">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837761</a><br></span></font><a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837880">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837880</a><br><br>The solution is simple, and it is simply baffling that it has been resisted by the package maintainers. Why should users have to completely disable the defaults, just to disable a single problematic configuration item? <br><br></div></div>