From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: 36702@debbugs.gnu.org
Subject: bug#36702: 27.0.50; newline: don't auto-fill regardless of auto-fill-mode
Date: Thu, 18 Jul 2019 14:32:41 +0100 [thread overview]
Message-ID: <87k1cfv56u.fsf@tcd.ie> (raw)
In-Reply-To: <995fa363-a165-c022-ed47-03cb1fd0ac65@easy-emacs.de> ("Andreas Röhler"'s message of "Thu, 18 Jul 2019 07:28:06 +0200")
Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
> On 17.07.19 21:07, Basil L. Contovounesios wrote:
>> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>>
>>> Decoupling it should not break anything. When fixed, just setting an
>>> auto-fill-function will no longer trigger auto-fill in case auto-fill-mode is
>>> off.
>> But auto-fill-function is effectively synonymous with auto-fill-mode.
>
> Consider that a design flaw. Just setting a var should not trigger a mode.
Depends on how you set the variable:
- Most minor modes can be enabled by customising their mode variable.
- The mode variable of auto-fill-mode is auto-fill-function.
- Calling auto-fill-mode directly does little more than set
auto-fill-function.
- In this sense it's similar to a glorified indent-tabs-mode.
- Setting the mode variable of auto-fill-mode and being surprised when
auto-fill ensues in certain cases is a pilot error.
For better or worse, this is all long-standing and documented behaviour,
so unless you have concrete proposals for how to improve on said design
flaw in a backward-compatible way, I'm not sure there's much to be done
except for clarify the documentation where possible.
Thanks,
--
Basil
next prev parent reply other threads:[~2019-07-18 13:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 10:19 bug#36702: 27.0.50; newline: don't auto-fill regardless of auto-fill-mode Andreas Röhler
2019-07-17 10:47 ` Basil L. Contovounesios
2019-07-17 11:02 ` Andreas Röhler
2019-07-17 12:21 ` Basil L. Contovounesios
2019-07-17 13:38 ` Andreas Röhler
2019-07-17 14:25 ` Basil L. Contovounesios
2019-07-17 14:38 ` Basil L. Contovounesios
2019-07-17 17:14 ` Andreas Röhler
2019-07-17 17:47 ` Basil L. Contovounesios
2019-07-17 18:26 ` Andreas Röhler
2019-07-17 19:07 ` Basil L. Contovounesios
2019-07-18 5:28 ` Andreas Röhler
2019-07-18 13:32 ` Basil L. Contovounesios [this message]
2019-09-15 14:35 ` Lars Ingebrigtsen
2019-10-07 5:03 ` Lars Ingebrigtsen
2019-10-07 18:27 ` Basil L. Contovounesios
2019-10-07 18:52 ` Eli Zaretskii
2019-10-07 23:14 ` Basil L. Contovounesios
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=87k1cfv56u.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=36702@debbugs.gnu.org \
--cc=andreas.roehler@easy-emacs.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).