As a feature request, it would be useful to have the ability to toggle linting on or off. Sometimes I'm working on a codebase that is full of lint errors, but it is infeasible or impossible for me to fix them. The preference there would be to temporarily disable linting while I'm working on those files.
I'll think about this.
@w0rp what do you think about not creating autocmds by default but allow user to setup that? This would solve this issue as you could just use augroup Name | au! | augroup END to disable linters. Other option would be check inside lint function for buffer variable.
I'd rather have the autocmd commands by default, and users can use the global options to turn them off. It's better if simply installing the plugin does something useful.
I can throw my hat in the ring of 'I would really like the ability to execute a command to turn Ale on and off'.
It's especially useful in my workflow where I generally have a single vim instance in a project directory with many buffers open that I am working on, and sometimes I need to view various files in dependency directories, and the sign column goes crazy, because those deps don't operate with the same linting requirements.
I.E. An ideal workflow would:
:AleEnable
:AleDisable
or even
:ALEToggle
To go the Syntastic route.
It'll happen eventually. Either someone else will do it, or I'll do it when I finally get the time.
This has been implemented by now, and I just documented the command, ALEToggle.
Just what I was looking for, great! And thank you!!
// in my .vimrc
map <leader>at :ALEToggle<CR>
Most helpful comment
This has been implemented by now, and I just documented the command,
ALEToggle.