summaryrefslogtreecommitdiff
path: root/ale_linters/python/vulture.vim
diff options
context:
space:
mode:
authorOliver Albertini <oliverralbertini@users.noreply.github.com>2021-09-09 20:53:54 -0700
committerGitHub <noreply@github.com>2021-09-10 12:53:54 +0900
commitb504eeb094b26a635f260a92e0b9762ad2eb1862 (patch)
treea8b2a8a6d38c633828eaf9a9b073746af9881b49 /ale_linters/python/vulture.vim
parentc5c58f5bf82bf1cd6782d66e08d22af41de8e8f7 (diff)
downloadale-b504eeb094b26a635f260a92e0b9762ad2eb1862.zip
[python/pyre.vim] Fix pyre persistent behavior (#3895)
It's necessary to provide a `-l` option to pyre with the closest parent directory containing a `.pyre_configuration.local` file, or simply change directory (cwd) to the root of the pyre project. Thanks to Ken Verbosky for the code that fixes this. Error seen when not using such a solution: ``` 1031.473923 on 6: Dropping message 'ƛ Background task unexpectedly quited: Invalid configuration: Cannot find any source files to analyze. Either `source_directories` or `targets` must be specified. ``` Issue with this approach is that if you are editing files under different projects, the `pyre persistent` process is not re-created for each file. We have to do `:ALEStopAlllsps` in order for the process to start with the new working directory. Co-authored-by: Oliver Ruben Albertini <ora@fb.com>
Diffstat (limited to 'ale_linters/python/vulture.vim')
0 files changed, 0 insertions, 0 deletions