Gnus development mailing list
 help / color / mirror / Atom feed
From: Oliver Scholz <epameinondas@gmx.de>
Cc: ding@gnus.org
Subject: Re: auto-fill in body after "^[A-Za-z]: "
Date: Fri, 12 Oct 2001 22:53:25 +0200	[thread overview]
Message-ID: <m3vghk7f7e.fsf@ID-87814.user.dfncis.de> (raw)
In-Reply-To: <vafsncphu81.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 12 Oct 2001 15:18:54 +0200")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> 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.
> 
> I have just committed a modified form of your changes to CVS.  The
> text property is added from message-setup-1 rather than from a hook
> (this also avoids searching), and the fill variables are set from
> message-setup-fill-variables rather than from a hook.
> 
> Please test.
> 
> Does this work on XEmacs?  Not sure about the support of text
> properties there.  Does this code work on Emacs 20 on a tty?
[...]

Emacs 20: It does work on Emacs 20 on a tty. However I found two bugs:

*  In `message-setup-1':
     (put-text-property
        (point)
        (progn
        (insert mail-header-separator "\n")
        (1- (point)))
        'read-only nil) ;; that should be 'read-only t

* there are some headers that are inserted *after* the text-property
  'field 'header is set. In my header the whole block:

>  Date: Fri, 12 Oct 2001 22:33:24 +0200
>  In-Reply-To: <vafsncphu81.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 12 Oct 2001 15:18:54 +0200")
>  Message-ID: <m3wv207g4r.fsf@ID-87814.user.dfncis.de>
>  Gcc: nnfolder+archive:misc-mail
>  From: Oliver Scholz <epameinondas@gmx.de>
>  X-attribution: os
>  --text follows this line--

So they have not the 'header text property and if you add a header
line manually between these lines it will not have this property, too.

I did not investigate in this yet, because I'm too tired. I will look
at it again tomorrow.

    'oliver

-- 
Oliver Scholz
Taunusstr. 25
60329 Frankfurt am Main
Tel. 069  97 40 99 42



  parent reply	other threads:[~2001-10-12 20:53 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 [this message]
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 ` auto-fill in body after "^[A-Za-z]: " Simon Josefsson
2001-10-12 16:45   ` 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=m3vghk7f7e.fsf@ID-87814.user.dfncis.de \
    --to=epameinondas@gmx.de \
    --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).