GNU bug report logs - #36702
27.0.50; newline: don't auto-fill regardless of auto-fill-mode

Previous Next

Full log

View this message in rfc822 format

From: "Basil L. Contovounesios" <contovob <at> tcd.ie>
To: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
Cc: 36702 <at> debbugs.gnu.org
Subject: bug#36702: 27.0.50; newline: don't auto-fill regardless of auto-fill-mode
Date: Wed, 17 Jul 2019 11:47:02 +0100

Andreas Röhler <andreas.roehler <at> easy-emacs.de> writes:

> have an auto-fill-function set in a mode.
>
> When testing, noticed that  this auto-fill-function was called by  `newline`
> even if  no auto-fill-mode.

Making auto-fill-function non-nil is effectively the same as enabling
auto-fill-mode.

> See definition of newline from simple.el, line 22:
>
> (auto-fill-function (if arg nil auto-fill-function))
>
> IMO there is also a docu bug, as this auto-filling is switched of by any arg
>
> whilst docu says: With ARG, insert that many newlines -- which sounds unrelated
> if filling.

I don't see a documentation bug, as the behaviour you see is documented
in both docstrings and the Elisp manual.

The docstring of newline says:

  Calls `auto-fill-function' if the current column number is greater
  than the value of `fill-column' and ARG is nil.

The docstring of auto-fill-function says:

  It is called after self-inserting any character specified in
  the `auto-fill-chars' table.

The docstring of self-insert-command says:

  After insertion, `internal-auto-fill' is called if
  `auto-fill-function' is non-nil and if the `auto-fill-chars' table has
  a non-nil value for the inserted character.

So I don't see a bug here.

Thanks,

-- 
Basil

Previous Next

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