From: Oliver Scholz <oscholz@my.gnus.org>
Subject: Re: patches (Re: auto-fill in body after "^[A-Za-z]: ")
Date: Tue, 16 Oct 2001 02:04:09 +0200 [thread overview]
Message-ID: <m3adys1mdi.fsf@ID-87814.user.dfncis.de> (raw)
In-Reply-To: <vaf7ktw8wsw.fsf@INBOX.auto.gnus.tok.franklin.cs.uni-dortmund.de>
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
* "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
> Oliver Scholz <oscholz@my.gnus.org> writes:
>> Should I make new diffs without the read-only text property then?
> Way cool. Thanks a lot. That way, the diffs might be < 10 lines,
> which means we don't need paperwork from you.
[...]
O.k. here they are.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: message.diff --]
[-- Type: text/x-patch, Size: 622 bytes --]
--- message.el Fri Oct 12 16:39:31 2001
+++ /home/egoge/bin/emacs-lisp/message.el Tue Oct 16 01:51:57 2001
@@ -3943,7 +3943,6 @@
(when message-default-headers
(insert message-default-headers)
(or (bolp) (insert ?\n)))
- (put-text-property (point-min) (point) 'field 'header)
(put-text-property
(point)
(progn
@@ -3979,6 +3978,9 @@
(set-buffer-modified-p nil)
(setq buffer-undo-list nil)
(run-hooks 'message-setup-hook)
+ (save-restriction
+ (message-narrow-to-headers)
+ (put-text-property (point-min) (point-max) 'field 'header))
(message-position-point)
(undo-boundary))
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: gnus-draft.diff --]
[-- Type: text/x-patch, Size: 461 bytes --]
--- gnus-draft.el Sun Sep 23 12:37:11 2001
+++ /home/egoge/bin/emacs-lisp/gnus-draft.el Tue Oct 16 01:52:06 2001
@@ -102,7 +102,8 @@
(save-excursion
(save-restriction
(message-narrow-to-headers)
- (message-remove-header "date")))
+ (message-remove-header "date")
+ (put-text-property (point-min) (point-max) 'field 'header)))
(save-buffer)
(let ((gnus-verbose-backends nil))
(gnus-request-expire-articles (list article) group t))
[-- Attachment #4: Type: text/plain, Size: 58 bytes --]
'oliver
--
25 Vendémiaire an 210 de la Révolution
next prev parent reply other threads:[~2001-10-16 0:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 13:28 auto-fill in body after "^[A-Za-z]: " 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 [this message]
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=m3adys1mdi.fsf@ID-87814.user.dfncis.de \
--to=oscholz@my.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).