1 How to build T-gnus with Mule 2.3 based on Emacs 19.34.
6 Unfortunately, some variables for `message' are predefined in lisp/
7 loaddefs.el which is dumped in Mule executable file. It is uninvited,
8 moreover, it has a bad influence. So you should remove these
9 definitions from lisp/loaddefs.el and rebuild Mule. However, if you
10 don't want to rebuild Mule, you may put the following lines in the
11 beginning of .emacs file instead of rebuilding Mule.
13 (let ((symbols '(citation-line-function
14 cite-function courtesy-message default-headers
15 default-mail-headers default-news-headers
16 deletable-headers fcc-handler-function
17 followup-to-function from-style
18 generate-headers-first generate-new-buffers
19 ignored-bounced-headers ignored-cited-headers
20 ignored-mail-headers ignored-news-headers
21 ignored-resent-headers ignored-supersedes-headers
22 included-forward-headers indent-citation-function
23 interactive kill-buffer-on-exit post-method
24 reply-to-function required-mail-headers
25 required-news-headers send-mail-function
26 send-news-function signature
27 signature-before-forwarded-message signature-file
28 signature-separator syntax-checks use-followup-to
29 user-organization-file wide-reply-to-function
33 (setq symbol (car symbols)
35 (makunbound (intern (format "message-%s" symbol)))))
38 INSTALL CUSTOM, APEL, FLIM, SEMI/WEMI
39 =====================================
41 T-gnus requires the latest version of CUSTOM, APEL, FLIM and SEMI or
42 WEMI; you should install these packages before installing T-gnus.
44 As for CUSTOM, you should apply the following patch before building it.
46 ------ cut here ------ cut here ------ cut here ------ cut here ------
47 --- custom-1.9962/cus-face.el~ Wed Mar 4 19:52:39 1998
48 +++ custom-1.9962/cus-face.el Mon Mar 9 08:05:33 1998
50 "Define a new FACE on all frames, ignoring X resources."
51 (interactive "SMake face: ")
52 (or (internal-find-face name)
53 - (let ((face (make-vector 8 nil)))
54 + (let ((face (make-vector face-vector-length nil)))
57 (let* ((frames (frame-list))
58 ------ cut here ------ cut here ------ cut here ------ cut here ------
60 By the way, the latest CUSTOM package for Emacs v19 is available from:
62 ftp://ftp.dina.kvl.dk/pub/Staff/Per.Abrahamsen/custom/custom-1.9962.tar.gz
68 There are three ways of making T-gnus with Mule 2.3 based on Emacs 19.34.
70 1. If you have installed EMU, APEL, FLIM and SEMI or WEMI packages
71 under the standard load-path, for instance:
73 EMU: /usr/local/share/mule/19.34/site-lisp/
74 APEL: /usr/local/share/mule/site-lisp/apel/
75 FLIM: /usr/local/share/mule/site-lisp/flim/
76 SEMI: /usr/local/share/mule/site-lisp/semi/
78 What is more, if you have been replaced old CUSTOM with new CUSTOM
79 or if you have installed new CUSTOM directly under the standard
80 load-path as such as /usr/local/share/mule/19.34/site-lisp/, you
81 may have nothing to be done; type the following commands right now.
83 % ./configure --with-emacs=mule
86 However, if you have installed new CUSTOM in the subdirectory under
87 the standard load-path, use the configure option `--with-addpath='
90 % ./configure --with-emacs=mule\
91 --with-addpath=/usr/local/share/mule/site-lisp/custom/
94 or you can use the file subdirs.el under the parent directory of
95 the subdirectory of CUSTOM to add it into load-path which contain
96 the following contents:
98 (normal-top-level-add-to-load-path
99 '("custom/" "and the other subdirectories.../"))
103 % ./configure --with-emacs=mule
106 2. If you have installed EMU, APEL, FLIM and SEMI or WEMI packages in
107 the non-standard load-path, use the configure option
108 `--with-addpath=' with the colon separated directory names where
109 EMU, APEL or CUSTOM packages are installed. For example:
111 % ./configure --with-emacs=mule\
112 --with-addpath=~/elisp/emu/:~/elisp/apel/:~/elisp/custom/
115 In this case, you have no need to add paths of FLIM, SEMI or WEMI
116 if they are installed under the directory which is same as the
117 parent directory of APEL.
119 3. This is another way to install T-gnus when you have installed EMU,
120 APEL, FLIM and SEMI or WEMI packages in the non-standard load-path.
121 Copy the file `sample.lpath.el' which is included in the
122 distribution to `~/.lpath.el' and modify it suitably for your
123 environment. And then type the following command.
125 % ./configure --with-emacs=mule
129 USING Emacs-W3M (and Emacs W3)
130 ==============================
131 The web based backend `nnshimbun' uses the shimbun modules which are
132 included in Emacs-W3M package (and the other web based backends of T-
133 gnus requires Emacs W3). Emacs-W3M is an interface program to the
134 external command W3M, visit the following pages for more information.
136 http://namazu.org/~tsuchiya/emacs-w3m/
137 http://ei5nazha.yz.yamagata-u.ac.jp/~aito/w3m/
139 If you wish to build T-gnus to be abel to use Emacs-W3M and nnshimbun,
140 you have to specify the path where Emacs-W3M is installed using the
141 configure option `--with-addpath=' (for Emacs W3, use the configure
142 option `--with-w3=' or editing the file `~/.lpath.el'). Here is an
145 % ./configure --with-emacs=mule\
146 --with-addpath=~/elisp/emu/:~/elisp/apel/: ... :~/elisp/w3m/\
147 --with-w3=/usr/local/share/mule/site-lisp/w3/
150 ;; Don't mind if configure says "W3... not found". It is currently
151 ;; malfunction when the configure option `--with-w3=' is not used even
152 ;; if the path of Emacs W3 is specified in the file `~/.lpath.el'.
154 ;; By the way, does anyone know where do we find Emacs W3 package
155 ;; which is suitable to Mule 2.3 based on Emacs 19.34?