Enno
> Thanks, but I am not so happy with introducing a whole batch of new option variables and in addition use those `javascript_node_` variables as fallback. Can't we stick to...
> I don't have a good short term solution but these variables are really starting to make a mess of the global namespace Most natural would be simply inverting the...
> can be trivially managed with the "after-directory" I simply was not aware of it I thought one had to basically copy-paste the definition from VIMRUNTIME to HOME and adapt...
I thought a bit more about it and now disagree: Even though, say, only `&makeprg` can be overridden in an `after/compiler/` file, it is tied to `&errorformat`, see, say, latest...
What one can do, say by a naming scheme, to contain the names of the variables to set these values, at the moment freely left to the maintainer's choice, be...
> I strongly dislike the use of config variables for anything that can be trivially managed with the "after-directory" A point of contention could be what counts as trivial here;...
I just checked against git master. The same issue, but additionally ```python zsh $ blueman-manager Gtk-Message: 13:04:45.579: Failed to load module "window-decorations-gtk-module" Gtk-Message: 13:04:45.579: Failed to load module "colorreload-gtk-module" Traceback...
Comments still welcome
There's ```vim " runtime/ftplugin/rust.vim (lines 19-25) if get(b:, 'current_compiler', '') ==# '' if strlen(findfile('Cargo.toml', '.;')) > 0 compiler cargo else compiler rustc endif endif ``` setting it to the errorformat...
> rg is just for an example. Many tools and scripts use a consistent format that works with vim's quickfix. Yes, ```vim " Compatibility with standard unix tools errorformat CompilerSet...