Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: auto-fill in body after "^[A-Za-z]: "
Date: Fri, 12 Oct 2001 17:51:32 +0200	[thread overview]
Message-ID: <iluzo6wx3ej.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <m3y9mht2b0.fsf@ID-87814.user.dfncis.de> (Oliver Scholz's message of "12 Oct 2001 15:28:51 +0200")

Oliver Scholz <epameinondas@gmx.de> writes:

> This is the offspring from a discussion on gnu.emacs.gnus about the
> fact that something like "Suggestion: bla bla ..." breaks auto-fill in
> message buffer. I have added the following to my .emacs to correct
> that behaviour while still inhibiting auto-fill in the header. Kai
> suggested that I should mail my code to this list.
>
> (defun os-header-set-text-property ()
>   "Put a text-property \"field\" with value \"header\" to the header lines."
>   (save-excursion
>     (put-text-property (point-min)
> 		       (re-search-forward
> 			(concat "^"
> 				mail-header-separator) nil nil 1)
> 		       'field 'header)))
>
>
> (defun message-do-auto-fill ()
>   "Test if point is in message-header before auto-filling."
>   (unless (text-property-any (line-beginning-position) (point) 'field 'header)
>     (do-auto-fill)))

This doesn't work if I manually add a header, right?  It wouldn't have
the proper text property.

Maybe the above be replaced by something such as the following?

(defun message-do-auto-fill ()
  (when (> (point) (save-excursion (rfc822-goto-eoh)))
    (do-auto-fill)))

(Btw, use `gnus-point-at-bol' instead of `line-beginning-position' to
make it works in XEmacs as well.)




  parent reply	other threads:[~2001-10-12 15:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-12 13:28 Oliver Scholz
2001-10-12 13:18 ` Kai Großjohann
2001-10-12 14:57   ` David S. Goldberg
2001-10-12 20:53   ` Oliver Scholz
2001-10-12 22:18     ` Kai Großjohann
2001-10-13 12:34       ` Oliver Scholz
2001-10-13 19:52         ` Kai Großjohann
2001-10-13 12:42       ` Oliver Scholz
2001-10-13 12:48       ` Oliver Scholz
2001-10-13 20:36         ` patches (Re: auto-fill in body after "^[A-Za-z]: ") Oliver Scholz
2001-10-13 19:55           ` Kai Großjohann
2001-10-14  1:02             ` Henrik Enberg
2001-10-15 20:47               ` Oliver Scholz
2001-10-15 20:37                 ` Kai Großjohann
2001-10-16  0:04                   ` Oliver Scholz
2001-10-16  8:27                     ` Kai Großjohann
2001-10-19  6:41                       ` Per Abrahamsen
2001-10-19  9:21                         ` Kai Großjohann
2001-10-19 10:10                           ` Per Abrahamsen
2001-10-19 11:41                             ` Kai Großjohann
2001-10-19 13:27                               ` Per Abrahamsen
2001-10-19 16:29                                 ` Kai Großjohann
2001-10-13 19:56           ` Kai Großjohann
2001-10-12 15:51 ` Simon Josefsson [this message]
2001-10-12 16:45   ` auto-fill in body after "^[A-Za-z]: " Kai Großjohann
2001-10-12 17:05     ` Paul Jarc
2001-10-12 17:10       ` Paul Jarc
2001-10-12 17:16       ` Kai Großjohann
2001-10-12 17:09     ` ShengHuo ZHU
2001-10-12 17:22       ` Kai Großjohann
2001-10-12 17:19     ` Simon Josefsson
2001-10-12 18:53   ` Oliver Scholz

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=iluzo6wx3ej.fsf@barbar.josefsson.org \
    --to=jas@extundo.com \
    --cc=ding@gnus.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).