From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: message-do-auto-fill
Date: Tue, 16 Oct 2001 20:53:02 +0900 [thread overview]
Message-ID: <yosuitdfg5sx.fsf@jpl.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
Hi,
In latest Gnus CVS, the function `message-setup-fill-variables'
sets the value of `auto-fill-function' to `message-do-auto-fill'
and then `auto-fill-mode' is turned on unconditionally. The
function `message-do-auto-fill' is good for the message-mode.
However, some people do not like `auto-fill-mode'. Is it a
feature of Gnus? If so, people may use a hook to inhibit it as
shown below:
(add-hook 'message-mode-hook 'turn-off-auto-fill)
Otherwise, Gnus should be changed as follows:
2001-10-16 Katsumi Yamaoka <yamaoka@jpl.org>
* message.el (message-setup-fill-variables): Use
`normal-auto-fill-function' instead of `auto-fill-function'.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: message.el.diff --]
[-- Type: text/x-patch, Size: 738 bytes --]
--- message.el~ Sun Oct 14 21:53:39 2001
+++ message.el Tue Oct 16 05:41:38 2001
@@ -1637,6 +1637,7 @@
(setq adaptive-fill-first-line-regexp nil))
(make-local-variable 'adaptive-fill-first-line-regexp)
(make-local-variable 'auto-fill-inhibit-regexp)
+ (make-local-variable 'normal-auto-fill-function)
(let ((quote-prefix-regexp
;; User should change message-cite-prefix-regexp if
;; message-yank-prefix is set to an abnormal value.
@@ -1658,7 +1659,7 @@
adaptive-fill-first-line-regexp))
;;(setq auto-fill-inhibit-regexp "^[A-Z][^: \n\t]+:")
(setq auto-fill-inhibit-regexp nil)
- (setq auto-fill-function 'message-do-auto-fill)))
+ (setq normal-auto-fill-function 'message-do-auto-fill)))
\f
next reply other threads:[~2001-10-16 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 11:53 Katsumi Yamaoka [this message]
2001-10-16 12:56 ` message-do-auto-fill Kai Großjohann
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=yosuitdfg5sx.fsf@jpl.org \
--to=yamaoka@jpl.org \
/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.
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 NNTP newsgroup(s).