From: "João Távora" <joaotavora@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Max Brieiev <max.brieiev@gmail.com>,
48452@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#48452: 28.0.50; flymake for elisp does not respect `load-path`
Date: Sun, 24 Jul 2022 10:57:23 +0100 [thread overview]
Message-ID: <CALDnm51_xBJR87T-gBsf-LZ99pJnL9=jGjFEKQPZknFiKOVH4g@mail.gmail.com> (raw)
In-Reply-To: <87v8rmyilo.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
On Sun, Jul 24, 2022 at 10:18 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> João Távora <joaotavora@gmail.com> writes:
>
> > Or maybe -- again, I'm just guessing -- the danger is that that bad.el
> > is disguised under /tmp/pcase.el and /tmp/good.el has a perfectly
> > legitimate.
> >
> > (require 'pcase)
> >
> > Simply visitng /tmp/good.el with Flymake on would lead to disaster.
>
> Yes. Sorry, I thought it was self-evident that that's the problem I was
> talking about with having "./" in load-path.
>
OK. I just hope that this thread has left it clear that simply visiting that
/tmp/pcase-not-malicious-at-all.el can lead to "disaster" regardless
of the value in elisp-flymake-byte-compile-load-path .
> If
> > that's the case, it's as easy as applying this patch
>
> [...]
>
> > - ,@(mapcan (lambda (path) (list "-L" path))
> > + ,@(mapcan (lambda (path) (list "-L" (format ":%s"
> path)))
> > elisp-flymake-byte-compile-load-path)
>
> That would be a distinct improvement; yes. (But with a comment about
> what that does, because it's not self explanatory.)
>
> OK, I can do that.
João Távora
[-- Attachment #2: Type: text/html, Size: 1989 bytes --]
next prev parent reply other threads:[~2022-07-24 9:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 20:46 bug#48452: 28.0.50; flymake for elisp does not respect `load-path` Max Brieiev
2022-07-13 11:47 ` Lars Ingebrigtsen
2022-07-13 13:47 ` Max Brieiev
2022-07-13 13:57 ` Lars Ingebrigtsen
2022-07-13 16:24 ` Max Brieiev
2022-07-14 17:15 ` Lars Ingebrigtsen
2022-07-14 20:29 ` João Távora
2022-07-15 9:46 ` Lars Ingebrigtsen
2022-07-15 10:03 ` João Távora
2022-07-16 10:12 ` Lars Ingebrigtsen
2022-07-18 19:17 ` João Távora
2022-07-22 19:52 ` Lars Ingebrigtsen
2022-07-22 21:09 ` João Távora
2022-07-22 21:12 ` Lars Ingebrigtsen
2022-07-22 21:46 ` João Távora
2022-07-23 5:50 ` Lars Ingebrigtsen
2022-07-23 9:24 ` João Távora
2022-07-23 14:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-23 17:45 ` João Távora
2022-07-23 17:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-24 9:18 ` Lars Ingebrigtsen
2022-07-24 9:57 ` João Távora [this message]
2022-07-23 15:05 ` Max Brieiev
2022-07-23 17:16 ` João Távora
2022-07-15 11:53 ` Max Brieiev
2022-07-14 9:22 ` Max Brieiev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALDnm51_xBJR87T-gBsf-LZ99pJnL9=jGjFEKQPZknFiKOVH4g@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=48452@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=max.brieiev@gmail.com \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).