From: "Štěpán Němec" <stepnem@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: tastytea <tastytea@tastytea.de>, 36837@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 [thread overview]
Message-ID: <87ftmjfvpw.fsf@gmail.com> (raw)
In-Reply-To: <874l2zvcak.fsf@igel.home>
On Fri, 02 Aug 2019 17:04:35 +0200
Andreas Schwab wrote:
> On Aug 02 2019, Štěpán Němec <stepnem@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
next prev parent reply other threads:[~2019-08-02 15:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 9:17 bug#36837: 26.2; whitespace-mode: whitespace-line-column is not set to local fill-column tastytea
2019-08-02 14:57 ` Štěpán Němec
2019-08-02 15:04 ` Andreas Schwab
2019-08-02 15:11 ` Štěpán Němec [this message]
2019-08-02 15:15 ` Andreas Schwab
2019-08-02 15:22 ` Štěpán Němec
2019-08-02 15:33 ` Andreas Schwab
2019-08-02 15:20 ` Eli Zaretskii
2019-08-02 15:30 ` Štěpán Němec
2019-08-02 18:51 ` Eli Zaretskii
2019-08-02 19:10 ` Štěpán Němec
2019-08-02 19:39 ` Eli Zaretskii
2019-08-02 19:28 ` Noam Postavsky
2019-08-02 19:45 ` Štěpán Němec
2019-08-02 21:14 ` Noam Postavsky
2019-08-02 21:50 ` Štěpán Němec
2019-08-02 21:54 ` Andreas Schwab
2019-08-03 7:50 ` tastytea
2019-08-03 9:23 ` Štěpán Němec
2020-02-24 19:56 ` Noam Postavsky
2020-02-24 20:12 ` Štěpán Němec
2020-02-26 0:38 ` Noam Postavsky
2020-02-28 5:01 ` Eli Zaretskii
2020-02-28 8:14 ` Štěpán Němec
2020-03-02 3:58 ` Noam Postavsky
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=87ftmjfvpw.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=36837@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
--cc=tastytea@tastytea.de \
/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).