From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#48452: 28.0.50; flymake for elisp does not respect `load-path` Date: Sat, 23 Jul 2022 07:50:54 +0200 Message-ID: <87wnc474xt.fsf@gnus.org> References: <8735unafob.fsf@gmail.com> <877d4hs084.fsf@gnus.org> <87v8s1untg.fsf@gmail.com> <874jzlp12v.fsf@gnus.org> <87wnchc75r.fsf@gmail.com> <87ilnzaa49.fsf@gnus.org> <87cze7780j.fsf@gmail.com> <87r12mogh9.fsf@gnus.org> <87fsj1tlgn.fsf@gnus.org> <87sfmy1b95.fsf@gmail.com> <87r12d9b8f.fsf@gnus.org> <87k08497in.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2100"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Max Brieiev , 48452@debbugs.gnu.org To: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jul 23 07:52:12 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oF83f-0000Ms-VW for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 23 Jul 2022 07:52:11 +0200 Original-Received: from localhost ([::1]:39084 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oF83e-0007vt-Hd for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 23 Jul 2022 01:52:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49382) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oF83W-0007vl-9b for bug-gnu-emacs@gnu.org; Sat, 23 Jul 2022 01:52:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:53151) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oF83W-0004Qf-1H for bug-gnu-emacs@gnu.org; Sat, 23 Jul 2022 01:52:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oF83V-0008Q0-Qi for bug-gnu-emacs@gnu.org; Sat, 23 Jul 2022 01:52:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 23 Jul 2022 05:52:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 48452 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 48452-submit@debbugs.gnu.org id=B48452.165855546832283 (code B ref 48452); Sat, 23 Jul 2022 05:52:01 +0000 Original-Received: (at 48452) by debbugs.gnu.org; 23 Jul 2022 05:51:08 +0000 Original-Received: from localhost ([127.0.0.1]:42900 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oF82d-0008Od-O0 for submit@debbugs.gnu.org; Sat, 23 Jul 2022 01:51:08 -0400 Original-Received: from quimby.gnus.org ([95.216.78.240]:46622) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oF82a-0008Nf-Qr for 48452@debbugs.gnu.org; Sat, 23 Jul 2022 01:51:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :Date:References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=sJE4aJZt3SFTu+IHIkWl//6N5+4v0jbsRaO/fxfIwWw=; b=jTU3tZzvYCkPaUGdWp5sxHuj9V mYNwCRh1/OwxsWhKD9EsNCxPaw5UBIh1zyWUJk82DeiWTPkBDhe2bFJnexTpq9FW2NLhN23HMnwJW jneqANxeYG1nEQ3dFupSmDzszfzSxQZPBnyU818bDYS2dUpzKd0lx3KaJYGwvfeQFrWA=; Original-Received: from [84.212.220.105] (helo=joga) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oF82R-0007QT-5a; Sat, 23 Jul 2022 07:50:57 +0200 In-Reply-To: ("=?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?="'s message of "Fri, 22 Jul 2022 22:46:08 +0100") Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAAGFBMVEXT1dSztbSeoJ+Y mpmdn56+wL+/wcD////N7HCyAAAAAWJLR0QHFmGI6wAAAAd0SU1FB+YHFwUvE+NOWlEAAAEhSURB VDjLzZPdkYQgDMfDznDPBHTfGbYBZBvwowC9CrT/Ji6R9QxoAZs8OORniEn+Any52ej8bTj0rrsi 9Y6v6AY3mjL+6KcYdtCUZOxTHGN4u9R0RUKKBDoGLskUtB699Zaevx5FZYPsLbYKyc8UBQwUOwE4 wQYLqAye0AqAhNRK4VkbeAIKoNhXCrOjqMGujYKfjM6MZUdQZxxXKQ7f1LhmzKBPsNLh30RBfkUC yOdqG3TUShFZwcwgrjJlcVV/1bXz9oP2cEvdHrYcI5l1brGY7sxj13yR7FzsowSUkwGXq1e7XVeb xXAAIQZAAiwgtPjATSq380PW7mRDMa/gp4+obSFReMRd1J2bXDXg7RB1FQdoYupCuv2nXn0Y4Mvt D0/KJg0bENQTAAAAJXRFWHRkYXRlOmNyZWF0ZQAyMDIyLTA3LTIzVDA1OjQ3OjE5KzAwOjAwgx6e qQAAACV0RVh0ZGF0ZTptb2RpZnkAMjAyMi0wNy0yM1QwNTo0NzoxOSswMDowMPJDJhUAAAAASUVO RK5CYII= X-Now-Playing: Rival Consoles's _Odyssey, Sonne_: "Soul (Bonus Track) -feat. Peter Broderick-" X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:237664 Archived-At: Jo=C3=A3o T=C3=A1vora writes: > If you don't elaborate, we have no way of understanding whether this > is a genuine expansion of the "disaster vector" that is already > intrinsic to this particular Flymake backend. I think I already mentioned the problem of editing files in /tmp/? That's the whole point of not having ./ in load-path -- you can inadvertently load code under control of an attacker. It seems to me that there's two useful values for load-path in the Flymake backend: Either just the standard load-path (so that you actually get the same results as when doing a batch byte-compile) or the current running load-path (so that you get the same results as when you `require' the file from your .emacs, say). Altering the load-path to also include the ELPA directories doesn't really help much, because people have all kinds of code that's not in ELPA (but is in their load-path).