unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 36702@debbugs.gnu.org
Subject: bug#36702: 27.0.50; newline: don't auto-fill regardless of auto-fill-mode
Date: Wed, 17 Jul 2019 15:38:30 +0200	[thread overview]
Message-ID: <1440ccd1-2fbb-4f49-4b08-eb01d4b47e06@easy-emacs.de> (raw)
In-Reply-To: <87ims0hmxb.fsf@tcd.ie>


On 17.07.19 14:21, Basil L. Contovounesios wrote:
> severity 36702 minor
> found 36702 26.2.90
> tags 36702 + patch
> quit
>
> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>
>> On 17.07.19 12:47, Basil L. Contovounesios wrote:
>>
>>> 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.
>> Did you try the test-function delivered?
> Yes.
>
>> It inserts a newline in an empty buffer.
>>
>> May that condition being matched then?
> Ah, are you referring to the condition that the current column number be
> greater than fill-column?  This condition is enforced by the default
> value of normal-auto-fill-function when auto-fill-mode is enabled,
> namely do-auto-fill.  A different auto-fill-function mightn't enforce
> it.
>
> In general, there are multiple conditions guarding calls to
> auto-fill-function (see e.g. internal-auto-fill and
> internal_self_insert), and I'm not sure the docstring of newline is the
> right place to discuss these things.

 From my point of view it's not that much about the docu but about the 
design.

Users should not be forced to add an extra argument to prevent auto-fill 
when it is about a newline.


>   How's the following clarification
> for emacs-26 instead?
>
>

See above.







  reply	other threads:[~2019-07-17 13:38 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 [this message]
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
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=1440ccd1-2fbb-4f49-4b08-eb01d4b47e06@easy-emacs.de \
    --to=andreas.roehler@easy-emacs.de \
    --cc=36702@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    /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).