GNU bug report logs - #62065
30.0.50; No prompt to confirm unsafe local variables when eglot-ensure used in major mode hook

Previous Next

Full log

Message #8 received at 62065 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Matt Wittmann <mcwitt <at> gmail.com>, João Távora
 <joaotavora <at> gmail.com>
Cc: 62065 <at> debbugs.gnu.org
Subject: Re: bug#62065: 30.0.50;
 No prompt to confirm unsafe local variables when eglot-ensure used in
 major mode hook
Date: Sat, 11 Mar 2023 11:19:24 +0200

> From: Matt Wittmann <mcwitt <at> gmail.com>
> Date: Wed, 8 Mar 2023 12:59:03 -0800
> 
> When attempting to autostart eglot in Python buffers using
> 
>     (add-hook 'python-mode-hook #'eglot-ensure)
> 
> and working in a directory that has unsafe local variables in
> .dir-locals.el, I do not get a minibuffer prompt to confirm whether I
> want to apply unsafe changes.
> 
> Steps to reproduce:
> 
> With the following in ./.dir-locals.el:
> 
>     ((python-mode . ((eval . (setq foo 42)))))
> 
> run
> 
>     emacs -Q --eval "(add-hook 'python-mode-hook #'eglot-ensure)" test.py
> 
> Expected behavior: A buffer named *Local Variables* is displayed with a
> message asking to confirm whether to apply changes, and a minibuffer
> prompt is focused (this is the behavior of `emacs -Q test.py`)
> 
> Actual behavior: *Local Variables* is created but not displayed. There
> is no minibuffer prompt.

João, any comments?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.