GNU bug report logs - #70310
flymake in elisp buffer elides warning on a blank first line

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Mattias Engdegård <mattias.engdegard <at> gmail.com>
Subject: bug#70310: closed (Re: bug#70310: flymake in elisp buffer elides
 warning on a blank first line)
Date: Thu, 11 Apr 2024 12:05:03 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#70310: flymake in elisp buffer elides warning on a blank first line

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 70310 <at> debbugs.gnu.org.

-- 
70310: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=70310
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Mattias Engdegård <mattias.engdegard <at> gmail.com>
To: Dmitry Gutov <dmitry <at> gutov.dev>
Cc: 70310-done <at> debbugs.gnu.org, Spencer Baugh <sbaugh <at> janestreet.com>,
 João Távora <joaotavora <at> gmail.com>
Subject: Re: bug#70310: flymake in elisp buffer elides warning on a blank
 first line
Date: Thu, 11 Apr 2024 14:04:21 +0200

9 apr. 2024 kl. 22.10 skrev Dmitry Gutov <dmitry <at> gutov.dev>:

> Some brief experiment shows that these lines are relevant, though I'm not sure why, given that the byte-compiler's output is the same, whether the first line is empty or not:

Yes, I got as far as you did and wondered where this information ends up and if we need to do something there.
Then I stopped overthinking it and just bolted on some clamps (b436f430e38).
Seems to work, so I'm closing the bug.

[Message part 3 (message/rfc822, inline)]

From: Mattias Engdegård <mattias.engdegard <at> gmail.com>
To: Emacs Bug Report <bug-gnu-emacs <at> gnu.org>
Cc: João Távora <joaotavora <at> gmail.com>
Subject: flymake in elisp buffer elides warning on a blank first line
Date: Tue, 9 Apr 2024 15:45:50 +0200

On Emacs master:

1. Open an Elisp file.
2. Enable flymake.
3. Insert a blank line at the top.

This should result in a warning about a missing 'lexical-binding' cookie but none is shown.
Making the first line non-empty, even a single space, makes the warning appear.

Previous Next

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