From: Eli Zaretskii <eliz@gnu.org>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: tastytea@tastytea.de, schwab@linux-m68k.org, 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 22:39:18 +0300 [thread overview]
Message-ID: <834l2zfjbt.fsf@gnu.org> (raw)
In-Reply-To: <87ftmjcrit.fsf@gmail.com> (message from Štěpán Němec on Fri, 02 Aug 2019 21:10:34 +0200)
> From: Štěpán Němec <stepnem@gmail.com>
> Cc: schwab@linux-m68k.org, tastytea@tastytea.de, 36837@debbugs.gnu.org
> Date: Fri, 02 Aug 2019 21:10:34 +0200
>
> >> I.e., instead of restating the obvious (mode hooks are more general
> >> and should be overridden by file-local variables; no disagreement
> >> there), could you provide some concrete counter-arguments to my
> >> arguments?
> >
> > We just did, both of us.
>
> OK. I don't see it that way or just don't get it, I'm sorry.
Once again: file-local variables is a way for a file to override
_every_ other possible setting. That includes any user customizations
and everything else, because all of the other means to give variables
non-default values are not specific to one file, they always affect
more than one.
If that doesn't address your arguments, please consider elaborating
those arguments.
next prev parent reply other threads:[~2019-08-02 19:39 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
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 [this message]
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=834l2zfjbt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36837@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
--cc=stepnem@gmail.com \
--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).