Having shot myself in the foot by rewriting already pushed history, it occurred to me that perhaps I could have the commits list in interactive rebase reflect the commits’ push status in color. If lines of commits that I’ve already pushed to a remote were colored red (or any sufficiently differentiating color), I might actually notice when I’m about to screw up again.
To illustrate what I mean, here’s a mockup I made. This is what it would look like if this was my commit history, and 8b0ce7b was the last commit I had already pushed to a remote:
I have no previous experience in modifying syntax highlighting code, and I have no idea if what I’m suggesting is even possible with vim, so I figured I’d open this request first in case it’s a silly idea, or conversely, if you deem this useful enough to implement yourself.
From what romainl only linked to (the relevant parts of links should be quoted when answering):
You can tell syntastic which checkers to run for a given filetype by setting a variable ’g:syntastic__checkers’ to a list of checkers, e.g.
let g:syntastic_php_checkers = [”php”, ”phpcs”, ”phpmd”]
As for your question about invocation: according to the FAQ, the ”command line is constructed using an internal function named
makeprgBuild(), which provides a number of options that allow you to customise every part of the command that gets run. You can set these options using global variables”. (See this answer.)
The Include directive, when given a directory as parameter (such as /etc/proftpd/conf.d/, as in the stock /etc/proftpd/proftpd.conf), causes all files in said directory to be read, not just ones ending in .conf. This causes problems if, for instance, I’m using vim to edit a file in the included directory while the proftpd service is being (re)started: vim stores a .swp file in the same directory, and proftpd may fail to start with ”fatal: unknown configuration directive” when it tries to parse the .swp file.