rpgoldman

@cdowellmdb I think it's good to go. @arnavsinghvi11 didn't like the comments I put in to muffle linters; I prefer to keep them. Is that a show-stopper? If not, do...

> The in-line comments are definitely not a show-stopper, but I'd prefer to leave them out from committed code to ensure they catch any changes needed. Not sure I understand...

Actually, reading further after fixing this, there seem to be a lot of issues with this, and also some pretty scary practices, like using the `~/Library/Calendars` directory in a way...

Would it be possible to do the equivalent of ``` EXPORT python=/usr/local/bin/python3 ``` in your Emacs to make this work? Alternatively, couldn't you work in a virtual environment with the...

Of the two alternatives, it seems like the latter is the most feasible. I could imagine extending the configuration file to contain information on remotely running the checkers. Yes, that...

Still haven't gotten around to fixing this, but haven't forgotten, either. One follow-up question: the doc for `flycheck-pycheckers-args` says "This variable may be risky if used as a file-local variable."...

#71 takes advantage of existing emacs libraries tracking `poetry` virtual environments to pass through a pointer to those virtual environments, when available. Small step towards extending coverage to the [wild...

Thanks: I'm not sure what's going wrong: I am not getting this consistently reproducible. I'm wondering if there's something wrong with the test script and it's not cleaning up after...

Oh, I'm an idiot -- I was trying to replicate this on my *patched* version that has `with-compilation-unit`. Without it, I *can* reproduce the error on my linux box. I...

> For what ever reason, in my platform it only works with > if [ $lisp = clasp ] ; then > not with the "" OK, I'm changing that...