[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#48452: 28.0.50; flymake for elisp does not respect `load-path`
From: |
Max Brieiev |
Subject: |
bug#48452: 28.0.50; flymake for elisp does not respect `load-path` |
Date: |
Fri, 15 Jul 2022 14:53:53 +0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
João Távora <joaotavora@gmail.com> writes:
> But it could make sense to add ~/.emacs.d/elpa/* to the variable, if the
> package you're developing somewhere else has a dependency on other Elpa
> packages.
Yes, to me it seems very common to have a depandency on an Elpa
package, so I was wondering why flymake was complaining about requiring
installed package.
> Or maybe, Max, you can just set this variable it in your file-local
> variables or the dir-locals.el of the package you're developing.
This could work, but doesn't it mean that with each new version of a
dependency, I'll have to change my dir-locals.el, because the version of
the installed package is part of its file path?
> Anyway, because the directories under ~/.emacs.d/elpa are somewhat
> special and/or security-vetted it _could_ make sense to add them to
> the default value of the variable. This would amount to more or less
> the same as calling the underlying process with `-f
> package-initialize` I think.
>
> But I'm still not sure this should be the default, or merely an option
> to the flymake-elisp-byte-compile backend. I think the second is
> safer.
Both possibilities are fine to me.
Another option could be to parse the header section of the current
buffer for `Package-Requires:' clause, and then automatically add listed
dependencies to the `elisp-flymake-byte-compile-load-path'.
In this case, flymake would still had operated in quite restricted
environment, but at the same time it'd recognize package dependencies.
Would that make sense?
- bug#48452: 28.0.50; flymake for elisp does not respect `load-path`, (continued)
- bug#48452: 28.0.50; flymake for elisp does not respect `load-path`, João Távora, 2022/07/18
- bug#48452: 28.0.50; flymake for elisp does not respect `load-path`, Lars Ingebrigtsen, 2022/07/22
- bug#48452: 28.0.50; flymake for elisp does not respect `load-path`, João Távora, 2022/07/22
- bug#48452: 28.0.50; flymake for elisp does not respect `load-path`, Lars Ingebrigtsen, 2022/07/22
- bug#48452: 28.0.50; flymake for elisp does not respect `load-path`, João Távora, 2022/07/22
- bug#48452: 28.0.50; flymake for elisp does not respect `load-path`, Lars Ingebrigtsen, 2022/07/23
- bug#48452: 28.0.50; flymake for elisp does not respect `load-path`, João Távora, 2022/07/23
- bug#48452: 28.0.50; flymake for elisp does not respect `load-path`, Stefan Monnier, 2022/07/23
- bug#48452: 28.0.50; flymake for elisp does not respect `load-path`, Max Brieiev, 2022/07/23
- bug#48452: 28.0.50; flymake for elisp does not respect `load-path`, João Távora, 2022/07/23
- bug#48452: 28.0.50; flymake for elisp does not respect `load-path`,
Max Brieiev <=
- bug#48452: 28.0.50; flymake for elisp does not respect `load-path`, Max Brieiev, 2022/07/14