Timeline for Can I block vim from saving a file that isn't validated using an outside tool?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 20, 2018 at 9:10 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 20, 2018 at 8:21 | answer | added | Rolf | timeline score: 1 | |
| S Jun 13, 2018 at 3:42 | history | suggested | Jens | CC BY-SA 4.0 |
Avoid swallowed words by not using <>
|
| Jun 12, 2018 at 20:50 | review | Suggested edits | |||
| S Jun 13, 2018 at 3:42 | |||||
| Jun 10, 2018 at 15:46 | comment | added | B Layer | Does the python command follow basic shell command execution conventions? Specifically does it optionally allow input via stdin rather than a file and does it return 0 when input is clean and non-zero otherwise? If both of these are true I have a function for you. | |
| Jun 10, 2018 at 15:20 | comment | added | LEI | It might be a better approach to allow writing while linting on save, but automate the checks to block at the build or deploy phase. | |
| Jun 9, 2018 at 9:26 | comment | added | Christian Brabandt |
Might be possible using a custom BufWriteCmd autocommand. I would however not recommend doing that.
|
|
| Jun 9, 2018 at 8:56 | review | First posts | |||
| Jun 9, 2018 at 11:14 | |||||
| Jun 9, 2018 at 8:56 | history | asked | 576i | CC BY-SA 4.0 |