GNU bug report logs - #36837
26.2; whitespace-mode: whitespace-line-column is not set to local fill-column

Previous Next

Package: emacs;

Reported by: tastytea <tastytea <at> tastytea.de>

Date: Mon, 29 Jul 2019 14:40:02 UTC

Severity: minor

Found in version 26.2

Fixed in version 28.1

Done: Noam Postavsky <npostavs <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Štěpán Němec <stepnem <at> gmail.com>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: tastytea <tastytea <at> tastytea.de>, 36837 <at> debbugs.gnu.org
Subject: bug#36837: 26.2; whitespace-mode: whitespace-line-column is not set to local fill-column
Date: Fri, 02 Aug 2019 17:11:39 +0200
On Fri, 02 Aug 2019 17:04:35 +0200
Andreas Schwab wrote:

> On Aug 02 2019, Štěpán Němec <stepnem <at> gmail.com> wrote:
>
>> Yes, unfortunately, file-local variables are only setup (via
>> `hack-local-variables') _after_ the mode hooks are run (cf.
>> `run-mode-hooks'), so `whitespace-color-on' still sees the original
>> `fill-column' the first time.
>>
>> Intuitively this order seems backwards to me, but I assume there must be
>> a (good?) reason? I'd like to hear it, in any case.
>
> I'd guess the reason is that file local variables should override mode
> stettings.

Sure, but isn't that precisely an argument for the reverse order?
Typically those settings are in defvars/defcustoms and thus if set
before loading the library the user value is respected. And on the other
hand those variables are often used for setup (during loading) which is
not automatically redone when modifying the value after the library is
loaded (such as is the very case of this report), unless using some of
the customize machinery, typically interactively.

-- 
Štěpán




This bug report was last modified 5 years and 85 days ago.

Previous Next


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