You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
This may be a problem with AtomLinter in general, but I am observing it on OS X with linter-pylint.
Every time I make a change to a file, a temporary directory (e.g., AtomLinter115411-4367-112mt9bsource.python) is created in my ${TMPDIR}. This is totally understandable.
However, once AtomLinter is finished doing its business, those directories are not removed (despite now being empty), so there end up being thousands of them (so many that rm -fr "${TMPDIR}/AtomLinter"* won't work because the command line is too long after expansion).
This is annoying. It would be nice if these directories were removed automatically.
If this issue is more appropriate to the core package, please let me know, and I'll refile it there.
The text was updated successfully, but these errors were encountered:
This may be a problem with AtomLinter in general, but I am observing it on OS X with linter-pylint.
Every time I make a change to a file, a temporary directory (e.g.,
AtomLinter115411-4367-112mt9bsource.python
) is created in my${TMPDIR}
. This is totally understandable.However, once AtomLinter is finished doing its business, those directories are not removed (despite now being empty), so there end up being thousands of them (so many that
rm -fr "${TMPDIR}/AtomLinter"*
won't work because the command line is too long after expansion).This is annoying. It would be nice if these directories were removed automatically.
If this issue is more appropriate to the core package, please let me know, and I'll refile it there.
The text was updated successfully, but these errors were encountered: