Gerard Roche

With a new feature in the next release you can map multiple commands using `` to separate commands : ``` noremap :w:LspSave ``` I don't know if you need to...

I can add a setting to run an ex command post write, example ``` "vintageous_on_post_write_ex_cmd": ":LspSave" ``` This would run the lsp save command whenever you run any write command...

I would assume that the Vim lsp plugin executes its routine after the file write event e.g. `:autocmd BufWritePost * call TrimWhiteSpace()`. I think it would probably be better for...

In the meantime you can use the Unimpaired plugin commands `]` and `[`, they accept a count. The plugin is provided out-of-the-box. * `]` puts a blank line after the...

@eddiemonge I guess this would be an ok compromise. The private flag is optional and really only to prevent _accidental_ publication of private repositories. But yeah, I'm ok with this...

@lukehorvat The private flag shouldn't be required to prevent accidental publication of a private repository. Publication should be opt-in. It might already work like this, if not, then it should....

@eddiemonge opt-in? You say it will publish if you don't have the private flag set to true, that's opt-out. i.e. you're saying the default value for the private flag is...

@unscriptable I don't understand. - If the name attribute is required then _you_ will need to add a name. your tools _are_ forced to provide a name. - If the...

No I'm not advocating that the prompt for `name` during `bower init` be dropped. Leaving it blank should omit the property, rather than adding a blank one. > prompt for...

@unscriptable :) a name which is redundant and meaningless. I think how `bower init` works is another issue. This issue is more about the bower.json spec.