bug#25083: 26.0.50; poor interaction between flymake and desktop-save-mode

[Sam Steingold <sds@gnu.org>]

you are making a good point.
however, _I_ (the user) should not have to deal with this myself.
flymake should know how to work with desktop.

however, the problem here is that the check command is merely
"epylint" and it is found in the path which is modified by pyvenv.
I agree that elpy/pyvenv should, ideally, handle that (see
https://github.com/jorgenschaefer/elpy/issues/1035).
however, it is not obvious to me that there is nothing flymake can do
to alleviate my pain.

at the very least, the massive errors on re-start should not be
reported via GUI.


On Thu, Dec 1, 2016 at 2:41 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Sam Steingold <sds@gnu.org>
>> Date: Thu, 01 Dec 2016 14:13:20 -0500
>>
>> When I start Emacs after editing a bunch of Python files,
>> desktop-save-mode restores them and flymake starts syntax checking
>> processes in each of them.
>>
>> However, there is a snag: python virtual environments.
>> Basically, each python projects uses a separate virtual environments
>> which includes its own python packages, and, moreover, its own python
>> and pylint executables(!)
>>
>> This means that flymake fails to find the epylint executable and
>> displays a GUI popup(!) for each(!) python file that I edited in the
>> previous session.  Note that this failure should _not_ be fatal (see PS
>> below).
>
> Isn't there some variable(s) which you could instruct desktop.el to
> save, in order to avoid these problems?  IOW, why doesn't desktop
> restore whatever setup you had before shutting down Emacs, which
> avoided the prompts at that time?



-- 
Sam Steingold <http://sds.podval.org> <http://www.childpsy.net>
<http://steingoldpsychology.com>