From: "Štěpán Němec" <stepnem@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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 17:30:41 +0200 [thread overview]
Message-ID: <877e7vfuu6.fsf@gmail.com> (raw)
In-Reply-To: <83a7crfvbm.fsf@gnu.org>
On Fri, 02 Aug 2019 18:20:13 +0300
Eli Zaretskii wrote:
>> Sure, but isn't that precisely an argument for the reverse order?
>
> No. The logic here is that a mode hook is more general than
> file-local variables (because a mode hook affects _all_ files that are
> visited with that mode).
Precisely. Maybe I'm being thick, but have you (and Andreas) actually
read what I wrote? 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?
--
Štěpán
next prev parent reply other threads:[~2019-08-02 15:30 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e7vfuu6.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=36837@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.