From: morioka@jaist.ac.jp (守岡 知彦 / MORIOKA Tomohiko)
Subject: patch for message.el, gnus-mh.el and gnus.el
Date: Tue, 16 Apr 1996 23:09:11 JST [thread overview]
Message-ID: <199604161409.XAA10761@mikan.jaist.ac.jp> (raw)
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
I want to use mh-e to write mail, however message.el does not permit
to use other MUA. So I wrote a patch for message.el.
This patch expands a variable `message-buffer-constructor-alist'.
This variable is an alist which key part is buffer name and value part
is functions to build message buffer. Default key is `t'.
This patch does not have implementation for other MUAs. I wrote
buffer-constructor for mh-e and inserted to gnus-mh.el. In addition,
I modified gnus.el for auto-loading.
Maybe you can write other buffer-constructor if you want to use
other user-interface to write message.
[-- Attachment #2: message.el.diff --]
[-- Type: application/octet-stream, Size: 1279 bytes --]
*** message.el-orig Sun Apr 14 16:40:06 1996
--- message.el Tue Apr 16 02:33:57 1996
***************
*** 297,302 ****
--- 297,308 ----
(defvar message-default-news-headers nil
"*A string of header lines to be inserted in outgoing news articles.")
+ ;; 1996/4/16 created by MORIOKA Tomohiko <morioka@jaist.ac.jp>
+ (defvar message-buffer-constructor-alist
+ '((t . message-default-buffer-constructor))
+ "*Alist which key part is buffer name and value part is
+ functions to build message buffer.")
+
;; Note: could use /usr/ucb/mail instead of sendmail;
;; options -t, and -v if not interactive.
(defvar message-mailer-swallows-blank-line
***************
*** 1836,1842 ****
--- 1842,1856 ----
(forward-line 2)))
(sit-for 0)))
+ ;; 1996/4/16 created by MORIOKA Tomohiko <morioka@jaist.ac.jp>
(defun message-pop-to-buffer (name)
+ "Pop to buffer NAME, and warn if it already exists and is modified."
+ (let ((m (cdr (or (assoc name message-buffer-constructor-alist)
+ (assq t message-buffer-constructor-alist)))))
+ (funcall m name)
+ ))
+
+ (defun message-default-buffer-constructor (name)
"Pop to buffer NAME, and warn if it already exists and is modified."
(let ((buffer (get-buffer name)))
(if (and buffer
[-- Attachment #3: gnus-mh.el.diff --]
[-- Type: application/octet-stream, Size: 842 bytes --]
*** gnus-mh.el-orig Sun Apr 14 16:39:59 1996
--- gnus-mh.el Tue Apr 16 02:39:39 1996
***************
*** 118,123 ****
--- 118,139 ----
(cdr reply)))))
(and winconf (set-window-configuration winconf))))))
+ (defun message-buffer-constructor-using-mh-e (name)
+ "message-buffer-constructor for mh-e."
+ (let (mh-letter-mode-hook)
+ (mh-send "" "" "")
+ )
+ (erase-buffer)
+ (use-local-map (copy-keymap (current-local-map)))
+ (local-set-key "\C-c\C-c" 'message-send-for-mh-e)
+ )
+
+ (defun message-send-for-mh-e ()
+ (interactive)
+ (gnus-inews-do-gcc)
+ (mh-send-letter)
+ )
+
(defun gnus-Folder-save-name (newsgroup headers &optional last-folder)
"Generate folder name from NEWSGROUP, HEADERS, and optional LAST-FOLDER.
If variable `gnus-use-long-file-name' is nil, it is +News.group.
[-- Attachment #4: gnus.el.diff --]
[-- Type: application/octet-stream, Size: 205 bytes --]
1977c1977,1978
< ("gnus-mh" gnus-mh-mail-setup gnus-summary-save-article-folder
---
> ("gnus-mh" message-buffer-constructor-using-mh-e
> gnus-mh-mail-setup gnus-summary-save-article-folder
[-- Attachment #5: Type: text/plain, Size: 464 bytes --]
By the way, function `gnus-mh-mail-setup' and
`gnus-mh-mail-send-and-exit' seem not to be used. Why not delete them?
Thanks,
----------------------------------------------------------------------
MORIOKA Tomohiko <morioka@jaist.ac.jp>
Japan advanced Institute of Science and Technology, Hokuriku
Asahi-dai, Tatsu-no-kuchi chô, Nomi, Ishikawa, Japan
----------------------------------------- Frisch, Frei, Freöhlich! ---
next reply other threads:[~1996-04-16 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-16 14:09 守岡 知彦 / MORIOKA Tomohiko [this message]
1996-04-22 1:09 ` Lars Magne Ingebrigtsen
1996-04-22 3:18 ` Steven L Baur
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=199604161409.XAA10761@mikan.jaist.ac.jp \
--to=morioka@jaist.ac.jp \
/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).