[debbugs-tracker] bug#22781: closed (25.1.50; auto-fill-function gets not to work in some major-mode)

[GNU bug Tracking System]

Your message dated Tue, 23 Feb 2016 19:34:05 +0900
with message-id <address@hidden>
and subject line Re: bug#22781: 25.1.50; auto-fill-function gets not to work in 
some major-mode
has caused the debbugs.gnu.org bug report #22781,
regarding 25.1.50; auto-fill-function gets not to work in some major-mode
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
22781: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22781
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 25.1.50; auto-fill-function gets not to work in some major-mode
>
>
>
>
> Date: 
>
> Tue, 23 Feb 2016 17:59:28 +0900
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (i686-pc-cygwin)
>
>
>
>
> Hi,
>
> Recipe:
>
> $ emacs -Q
> Eval: (with-temp-buffer (message-mode))
>
> Then `auto-fill-mode' will get not to work when editing at least
> a *.texi file using `texinfo-mode'.  In that case the value of
> `auto-fill-function' is `message-do-auto-fill'.  This is because
> `message-setup-fill-variables' sets `normal-auto-fill-function'
> to `message-do-auto-fill'.  The change was made in the revono:
>
> 66d9ef95c0f9407d2a6d26bcd7ed84a303294b53
>
> Regards,
>
> In GNU Emacs 25.1.50.1 (i686-pc-cygwin, GTK+ Version 3.14.13)
>  of 2016-02-23 built on localhost
> Windowing system distributor 'The Cygwin/X Project', version 11.0.11702000
> Configured using:
>  'configure --with-x-toolkit=gtk3 --with-xwidgets'
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#22781: 25.1.50; auto-fill-function gets not to work in some major-mode
>
>
>
>
> Date: 
>
> Tue, 23 Feb 2016 19:34:05 +0900
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (i686-pc-cygwin)
>
>
>
>
> On Tue, 23 Feb 2016 20:59:38 +1100, Lars Ingebrigtsen wrote:
> > Oops.  I think I meant to type `setq-local', but I typed `setq-default'
> > instead...
>
> > Fixed now.
>
> I verified that the problem has gone.  Thanks Lars!
>
>
> --- End Message ---