|
442
|
1 \input texinfo.tex @c -*- mode: texinfo; coding: iso-2022-8 -*-
|
|
428
|
2 @c %**start of header
|
|
|
3 @setfilename ../info/xemacs-faq.info
|
|
|
4 @settitle Frequently asked questions about XEmacs
|
|
|
5 @setchapternewpage off
|
|
|
6 @c %**end of header
|
|
|
7 @finalout
|
|
|
8 @titlepage
|
|
|
9 @title XEmacs FAQ
|
|
3018
|
10 @subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2005/10/24 20:39:47 $
|
|
428
|
11 @sp 1
|
|
2417
|
12 @author Ben Wing <ben@@xemacs.org>
|
|
1869
|
13 @author Tony Rossini <rossini@@u.washington.edu>
|
|
428
|
14 @author Chuck Thompson <cthomp@@xemacs.org>
|
|
|
15 @author Steve Baur <steve@@xemacs.org>
|
|
|
16 @author Andreas Kaempf <andreas@@sccon.com>
|
|
|
17 @author Christian Nyb@o{} <chr@@mediascience.no>
|
|
434
|
18 @author Sandra Wambold <wambold@@xemacs.org>
|
|
428
|
19 @page
|
|
|
20 @end titlepage
|
|
|
21
|
|
|
22 @ifinfo
|
|
|
23 @dircategory XEmacs Editor
|
|
|
24 @direntry
|
|
440
|
25 * FAQ: (xemacs-faq). XEmacs FAQ.
|
|
428
|
26 @end direntry
|
|
|
27 @end ifinfo
|
|
|
28
|
|
2417
|
29 @ignore
|
|
|
30 *****************************************
|
|
|
31 ***** To update the menus and nodes *****
|
|
|
32 *****************************************
|
|
|
33
|
|
|
34 First, the first argument to @node (the name itself) needs to be correct.
|
|
|
35 Use a macro if necessary to update the @node names from the
|
|
|
36 @unnumberedsubsec commands. Also note that the command we're about to
|
|
|
37 run will not correctly fix up the part of the menu to the right of a ::.
|
|
|
38 It will leave existing text in place but not change anything. If you
|
|
|
39 make a lot of changes and want to update this semi-automatically, use
|
|
|
40 M-x occur to pick out all @unnumberedsubsec lines then do some editing
|
|
|
41 magic to coerce them into the right format and cut and paste as necessary:
|
|
|
42
|
|
|
43 1. M-x occur @unnumberedsubsec
|
|
|
44 2. <select a rectangle including all text before the Q#.#.#>
|
|
|
45 3. C-x r t *<space>
|
|
|
46 4. go to the top and use the following macro to get the indentation right.
|
|
|
47
|
|
|
48 (setq last-kbd-macro (read-kbd-macro
|
|
|
49 "C-s : RET : <right> M-x indent- to- column RET 14 RET <home> <down>"))
|
|
|
50
|
|
|
51 5. Cut and paste the menus into the detailmenu at the top and
|
|
|
52 individual menus at the top of the appropriate chapters. (#### I
|
|
|
53 wonder, does texinfo-master-menu generate the detailmenu from the
|
|
|
54 individual menus or vice-versa or neither?)
|
|
|
55
|
|
|
56 Then,
|
|
|
57
|
|
2559
|
58 6. C-u C-c C-u m (C-u M-x texinfo-master-menu) will update the menus
|
|
2417
|
59 and nodes. However, it appears that even though it tries to
|
|
|
60 preserve the existing menu structure as much as possible, it
|
|
|
61 doesn't do a perfect job. It messes up in at least two ways: The
|
|
|
62 indentation in the part of the main menu above the detailmenu will
|
|
|
63 be screwed up, and the #.0 titles will be removed from both the
|
|
|
64 detailmenu and the individual chapter menus. In addition,
|
|
|
65 sometimes random things get screwed up in individual parts of the
|
|
|
66 menus. Therefore:
|
|
|
67
|
|
2559
|
68 1. Use the Lisp line below to get the spacing correct for the Q#.#.#
|
|
|
69 menu entries.
|
|
|
70
|
|
|
71 (set (make-local-variable 'texinfo-column-for-description) 14)
|
|
|
72
|
|
|
73 2. Copy the whole detailmenu beforehand.
|
|
|
74 3. Run C-u C-c C-u m to fix up the nodes.
|
|
|
75 4. Run `fix-main-menu' and `fix-omitted-menu-lines'.
|
|
|
76 5. Check the new detailmenu carefully to see if anything is screwed up
|
|
2417
|
77 compared to the old detailmenu you copied.
|
|
2559
|
78 6. If so, paste back the appropriate sections and fix up the corresponding
|
|
2417
|
79 part of the chapter-specific menu.
|
|
|
80
|
|
|
81 (defun fix-main-menu ()
|
|
|
82 (interactive)
|
|
|
83 (save-restriction
|
|
|
84 (let (p q)
|
|
2559
|
85 (goto-char (point-min))
|
|
|
86 (re-search-forward "^@menu")
|
|
2417
|
87 (setq p (match-beginning 0))
|
|
|
88 (re-search-forward "^$")
|
|
|
89 (setq q (match-end 0))
|
|
|
90 (narrow-to-region p q)
|
|
|
91 (goto-char p)
|
|
|
92 (while (search-forward ":: " nil t)
|
|
|
93 (indent-to-column 26)))))
|
|
|
94
|
|
|
95 (defun fix-omitted-menu-lines ()
|
|
|
96 (interactive)
|
|
|
97 (save-excursion
|
|
2559
|
98 (loop for x from 1 to 10 do
|
|
2417
|
99 (goto-char (point-min))
|
|
|
100 (re-search-forward (format "@unnumberedsec \\(%d.0: .*\\)" x))
|
|
|
101 (let ((line (match-string 1)))
|
|
2559
|
102 (re-search-backward "^@menu")
|
|
2417
|
103 (forward-line 1)
|
|
2559
|
104 (unless (looking-at "[0-9]+.0:")
|
|
2417
|
105 (insert line)
|
|
|
106 (insert "\n"))
|
|
|
107 (goto-char (point-min))
|
|
2559
|
108 (re-search-forward "^@menu")
|
|
2417
|
109 (search-forward (format "Q%d.0.1:" x))
|
|
|
110 (forward-line -1)
|
|
2559
|
111 (unless (looking-at "[0-9]+.0:")
|
|
|
112 (insert "\n")
|
|
|
113 (insert line))))))
|
|
2417
|
114
|
|
|
115 *****************************************
|
|
|
116 ***** Other work *****
|
|
|
117 *****************************************
|
|
|
118
|
|
|
119 When you've rearranged and renumbered a bunch of nodes, you can get
|
|
|
120 the numbers agreeing again. The macro below assumes that the
|
|
|
121 unnumberedsubsec number is correct, and fixes up the node to agree.
|
|
|
122 Only the first part of the node is fixed and the other parts may still
|
|
|
123 be wrong; but they will be fixed as part of
|
|
|
124 @code{texinfo-master-menu}.
|
|
|
125
|
|
|
126 (setq last-kbd-macro (read-kbd-macro
|
|
|
127 "<f1> unnumberedsubsec SPC RET C-s : RET <left> C-x C-x <f3> <home> <up> <C-right> <right> C-s , RET <left> C-x C-x <f4> <home> 2*<down>"))
|
|
|
128 @end ignore
|
|
|
129
|
|
|
130
|
|
428
|
131 @node Top, Introduction, (dir), (dir)
|
|
|
132 @top XEmacs FAQ
|
|
|
133
|
|
|
134 This is the guide to the XEmacs Frequently Asked Questions list---a
|
|
|
135 compendium of questions and answers pertaining to one of the finest
|
|
442
|
136 programs ever written. XEmacs is much more than just a Text Editor.
|
|
|
137
|
|
|
138 This FAQ is freely redistributable. This FAQ is distributed in the hope
|
|
|
139 that it will be useful, but WITHOUT ANY WARRANTY; without even the
|
|
|
140 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
|
428
|
141
|
|
|
142 If you have a Web browser, the official hypertext version is at
|
|
|
143 @iftex
|
|
|
144 @*
|
|
|
145 @end iftex
|
|
1143
|
146 @uref{http://www.xemacs.org/FAQ/xemacs-faq.html}
|
|
428
|
147
|
|
|
148 @ifset CANONICAL
|
|
|
149 @html
|
|
|
150 This document is available in several different formats:
|
|
|
151 @itemize @bullet
|
|
|
152 @item
|
|
|
153 @uref{xemacs-faq.txt, As a single ASCII file}, produced by
|
|
|
154 @code{makeinfo --no-headers}
|
|
|
155 @item
|
|
|
156 @uref{xemacs-faq.dvi, As a .dvi file}, as used with
|
|
|
157 @uref{http://www.tug.org, TeX.}
|
|
|
158 @item
|
|
|
159 As a PostScript file @uref{xemacs-faq-a4.ps, in A4 format},
|
|
|
160 as well as in @uref{xemacs-faq-letter.ps, letter format}
|
|
|
161 @item
|
|
|
162 In html format, @uref{xemacs-faq_1.html, split by chapter}, or in
|
|
|
163 @uref{xemacs-faq.html, one monolithic} document.
|
|
|
164 @item
|
|
|
165 The canonical version of the FAQ is the texinfo document
|
|
|
166 @uref{xemacs-faq.texi, man/xemacs-faq.texi}.
|
|
|
167 @item
|
|
|
168 If you do not have makeinfo installed, you may @uref{xemacs-faq.info,
|
|
|
169 download the faq} in info format, and install it in @file{<XEmacs
|
|
|
170 library directory>/info/}. For example in
|
|
462
|
171 @file{/usr/local/lib/xemacs-21.4/info/}.
|
|
428
|
172
|
|
|
173 @end itemize
|
|
|
174
|
|
|
175 @end html
|
|
|
176
|
|
|
177 @end ifset
|
|
|
178
|
|
|
179 @c end ifset points to CANONICAL
|
|
|
180
|
|
|
181 @menu
|
|
2417
|
182 * Introduction:: Introduction, Policy, Credits.
|
|
|
183 * Installation:: Installation and Troubleshooting.
|
|
2459
|
184 * Editing:: Editing Functions.
|
|
|
185 * Display:: Display Functions.
|
|
2417
|
186 * External Subsystems:: Interfacing with the OS and External Devices.
|
|
|
187 * Internet:: Connecting to the Internet.
|
|
|
188 * Advanced:: Advanced Customization Using XEmacs Lisp.
|
|
2459
|
189 * Other Packages:: Other External Packages.
|
|
2417
|
190 * Current Events:: What the Future Holds.
|
|
|
191 * Legacy Versions:: New information about old XEmacsen.
|
|
428
|
192
|
|
|
193 @detailmenu
|
|
|
194 --- The Detailed Node Listing ---
|
|
|
195
|
|
2417
|
196 1 Introduction, Policy, Credits
|
|
|
197
|
|
2537
|
198 1.0: What is XEmacs?
|
|
2417
|
199 * Q1.0.1:: What is XEmacs?
|
|
|
200 * Q1.0.2:: What is the current version of XEmacs?
|
|
2537
|
201 * Q1.0.3:: How do you pronounce XEmacs?
|
|
|
202 * Q1.0.4:: What does XEmacs look like?
|
|
|
203 * Q1.0.5:: Who wrote XEmacs?
|
|
|
204 * Q1.0.6:: Who wrote the FAQ?
|
|
|
205
|
|
|
206 1.1: Getting XEmacs
|
|
|
207 * Q1.1.1:: Where can I find XEmacs?
|
|
|
208 * Q1.1.2:: Are binaries available?
|
|
|
209 * Q1.1.3:: How do I get the bleeding-edge sources?
|
|
|
210 * Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual?
|
|
|
211
|
|
|
212 1.2: Versions for Different Operating Systems
|
|
|
213 * Q1.2.1:: Do I need X11 to run XEmacs?
|
|
|
214 * Q1.2.2:: What versions of Unix does XEmacs run on?
|
|
|
215 * Q1.2.3:: Is there a port of XEmacs to Microsoft Windows?
|
|
|
216 * Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
217 * Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
218 * Q1.2.6:: What are the differences between the various MS Windows emacsen?
|
|
|
219 * Q1.2.7:: How does the port cope with differences in the Windows user interface?
|
|
|
220 * Q1.2.8:: Is there a port of XEmacs to the Macintosh?
|
|
|
221 * Q1.2.9:: Is there a port of XEmacs to MS-DOS?
|
|
|
222 * Q1.2.10:: Is there a port of XEmacs to OS/2?
|
|
|
223 * Q1.2.11:: Is there a port of XEmacs to NextStep?
|
|
|
224 * Q1.2.12:: Is there a port of XEmacs to VMS?
|
|
|
225
|
|
|
226 1.3: Getting Started
|
|
|
227 * Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
|
228 * Q1.3.2:: Where do I put my @file{init.el} file?
|
|
|
229 * Q1.3.3:: Can I use the same @file{init.el} with the other Emacs?
|
|
|
230 * Q1.3.4:: Any good XEmacs tutorials around?
|
|
|
231 * Q1.3.5:: May I see an example of a useful XEmacs Lisp function?
|
|
|
232 * Q1.3.6:: And how do I bind it to a key?
|
|
|
233 * Q1.3.7:: What's the difference between a macro and a function?
|
|
|
234 * Q1.3.8:: What is @code{Custom}?
|
|
|
235
|
|
|
236 1.4: Getting Help
|
|
|
237 * Q1.4.1:: Where can I get help?
|
|
|
238 * Q1.4.2:: Which mailing lists are there?
|
|
2559
|
239 * Q1.4.3:: Where are the mailing lists archived?
|
|
|
240 * Q1.4.4:: How can I get two instances of info?
|
|
|
241 * Q1.4.5:: How do I add new Info directories?
|
|
2537
|
242
|
|
|
243 1.5: Contributing to XEmacs
|
|
|
244 * Q1.5.1:: How do I submit changes to the FAQ?
|
|
|
245 * Q1.5.2:: How do I become a beta tester?
|
|
|
246 * Q1.5.3:: How do I contribute to XEmacs itself?
|
|
2559
|
247 * Q1.5.4:: How do I get started developing XEmacs?
|
|
|
248 * Q1.5.5:: What's the basic layout of the code?
|
|
2537
|
249
|
|
|
250 1.6: Politics (XEmacs vs. GNU Emacs)
|
|
|
251 * Q1.6.1:: What is GNU Emacs?
|
|
|
252 * Q1.6.2:: How does XEmacs differ from GNU Emacs?
|
|
|
253 * Q1.6.3:: How much does XEmacs differ?
|
|
|
254 * Q1.6.4:: Is XEmacs "GNU"?
|
|
|
255 * Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
|
256 * Q1.6.6:: Why haven't XEmacs and GNU Emacs merged?
|
|
|
257
|
|
|
258 1.7: External Packages
|
|
2559
|
259 * Q1.7.1:: What is the package system?
|
|
|
260 * Q1.7.2:: Which external packages are there?
|
|
|
261 * Q1.7.3:: Do I need to have the packages to run XEmacs?
|
|
|
262 * Q1.7.4:: Is there a way to find which package has particular functionality?
|
|
2537
|
263
|
|
|
264 1.8: Internationalization
|
|
|
265 * Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
|
266 * Q1.8.2:: How can I help with internationalization?
|
|
|
267 * Q1.8.3:: How do I type non-ASCII characters?
|
|
|
268 * Q1.8.4:: Can XEmacs messages come out in a different language?
|
|
|
269 * Q1.8.5:: Please explain the various input methods in MULE/XEmacs
|
|
|
270 * Q1.8.6:: How do I portably code for MULE/XEmacs?
|
|
|
271 * Q1.8.7:: How about Cyrillic modes?
|
|
|
272 * Q1.8.8:: Does XEmacs support Unicode?
|
|
|
273 * Q1.8.9:: How does XEmacs display Unicode?
|
|
2417
|
274
|
|
|
275 2 Installation and Troubleshooting
|
|
|
276
|
|
2559
|
277 2.0: Installation (General)
|
|
|
278 * Q2.0.1:: How do I build and install XEmacs?
|
|
|
279 * Q2.0.2:: Where do I find external libraries?
|
|
|
280 * Q2.0.3:: How do I specify the paths that XEmacs uses for finding files?
|
|
|
281 * Q2.0.4:: Running XEmacs without installing
|
|
|
282 * Q2.0.5:: XEmacs is too big
|
|
|
283
|
|
|
284 2.1: Package Installation
|
|
|
285 * Q2.1.1:: How do I install the packages?
|
|
|
286 * Q2.1.2:: Can I install the packages individually?
|
|
|
287 * Q2.1.3:: Can I install the packages automatically?
|
|
|
288 * Q2.1.4:: Can I upgrade or remove packages?
|
|
|
289 * Q2.1.5:: Which packages to install?
|
|
|
290 * Q2.1.6:: Can you describe the package location process in more detail?
|
|
|
291 * Q2.1.7:: EFS fails with "500 AUTH not understood"
|
|
|
292
|
|
|
293 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
|
294 * Q2.2.1:: Libraries in non-standard locations
|
|
|
295 * Q2.2.2:: Why can't I strip XEmacs?
|
|
|
296
|
|
|
297 2.3: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
298 * Q2.3.1:: What exactly are all the different ways to build XEmacs under Windows?
|
|
|
299 * Q2.3.2:: What compiler/libraries do I need to compile XEmacs?
|
|
|
300 * Q2.3.3:: How do I compile the native port?
|
|
|
301 * Q2.3.4:: What do I need for Cygwin?
|
|
|
302 * Q2.3.5:: How do I compile under Cygwin?
|
|
|
303 * Q2.3.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
|
304 * Q2.3.7:: How do I compile with X support?
|
|
|
305 * Q2.3.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
|
306
|
|
|
307 2.4: General Troubleshooting
|
|
|
308 * Q2.4.1:: How do I deal with bugs or with problems building, installing, or running?
|
|
|
309 * Q2.4.2:: Help! XEmacs just crashed on me!
|
|
|
310 * Q2.4.3:: XEmacs crashes and I compiled it myself.
|
|
|
311 * Q2.4.4:: How to debug an XEmacs problem with a debugger
|
|
|
312 * Q2.4.5:: I get a cryptic error message when trying to do something.
|
|
|
313 * Q2.4.6:: XEmacs hangs when I try to do something.
|
|
|
314 * Q2.4.7:: I get an error message when XEmacs is running in batch mode.
|
|
|
315 * Q2.4.8:: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
|
316 * Q2.4.9:: @kbd{C-g} doesn't work for me. Is it broken?
|
|
|
317 * Q2.4.10:: How do I debug process-related problems?
|
|
|
318 * Q2.4.11:: XEmacs is outputting lots of X errors.
|
|
|
319 * Q2.4.12:: After upgrading, XEmacs won't do `foo' any more!
|
|
|
320
|
|
|
321 2.5: Startup-Related Problems
|
|
|
322 * Q2.5.1:: XEmacs cannot connect to my X Terminal!
|
|
|
323 * Q2.5.2:: Startup problems related to paths or package locations.
|
|
|
324 * Q2.5.3:: XEmacs won't start without network.
|
|
|
325 * Q2.5.4:: Startup warnings about deducing proper fonts?
|
|
|
326 * Q2.5.5:: Warnings from incorrect key modifiers.
|
|
|
327 * Q2.5.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
2417
|
328
|
|
2459
|
329 3 Editing Functions
|
|
2417
|
330
|
|
|
331 3.0: The Keyboard
|
|
2459
|
332 * Q3.0.1:: How can I customize the keyboard?
|
|
|
333 * Q3.0.2:: How can I bind complex functions (or macros) to keys?
|
|
|
334 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down?
|
|
|
335 * Q3.0.4:: Globally binding @kbd{Delete}?
|
|
|
336 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
|
337 * Q3.0.6:: How can you type in special characters in XEmacs?
|
|
|
338 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys?
|
|
|
339 * Q3.0.8:: How do I map the arrow keys?
|
|
|
340 * Q3.0.9:: HP Alt key as Meta.
|
|
|
341 * Q3.0.10:: Why does edt emulation not work?
|
|
|
342 * Q3.0.11:: How can I emulate VI and use it as my default mode?
|
|
2417
|
343
|
|
|
344 3.1: The Mouse
|
|
|
345 * Q3.1.1:: How can I turn off Mouse pasting?
|
|
|
346 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons?
|
|
|
347 * Q3.1.3:: Clicking the left button does not do anything in buffer list.
|
|
|
348 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3?
|
|
2459
|
349 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
|
350
|
|
|
351 3.2: Buffers, Text Editing
|
|
|
352 * Q3.2.1:: Can I have the end of the buffer delimited in some way?
|
|
|
353 * Q3.2.2:: How do I insert today's date into a buffer?
|
|
|
354 * Q3.2.3:: How do I get a single minibuffer frame?
|
|
|
355 * Q3.2.4:: How can I enable auto-indent and/or Filladapt?
|
|
|
356 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
357
|
|
|
358 3.3: Text Selections
|
|
|
359 * Q3.3.1:: How do I select a rectangular region?
|
|
|
360 * Q3.3.2:: How can I turn off or change highlighted selections?
|
|
|
361 * Q3.3.3:: How do I cause typing on an active region to remove it?
|
|
|
362 * Q3.3.4:: Can I turn off the highlight during isearch?
|
|
|
363 * Q3.3.5:: Why is killing so slow?
|
|
|
364 * Q3.3.6:: Why does @kbd{M-w} take so long?
|
|
|
365
|
|
|
366 3.4: Editing Source Code
|
|
|
367 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode?
|
|
|
368 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly?
|
|
|
369
|
|
|
370 4 Display Functions
|
|
|
371
|
|
|
372 4.0: Textual Fonts and Colors
|
|
|
373 * Q4.0.1:: How do I specify a font?
|
|
|
374 * Q4.0.2:: How do I set the text, menu and modeline fonts?
|
|
|
375 * Q4.0.3:: How can I set color options from @file{init.el}?
|
|
|
376 * Q4.0.4:: How can I set the colors when highlighting a region?
|
|
|
377 * Q4.0.5:: How can I limit color map usage?
|
|
|
378 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them.
|
|
|
379 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs?
|
|
|
380 * Q4.0.8:: How do I display non-ASCII characters?
|
|
|
381 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}.
|
|
|
382
|
|
|
383 4.1: Syntax Highlighting (Font Lock)
|
|
|
384 * Q4.1.1:: How can I do source code highlighting using font-lock?
|
|
|
385 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
386
|
|
|
387 4.2: The Modeline
|
|
|
388 * Q4.2.1:: How can I make the modeline go away?
|
|
|
389 * Q4.2.2:: How do you have XEmacs display the line number in the modeline?
|
|
|
390 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline?
|
|
|
391 * Q4.2.4:: How can I change the modeline color based on the mode used?
|
|
|
392
|
|
|
393 4.3: The Cursor
|
|
|
394 * Q4.3.1:: Is there a way to make the bar cursor thicker?
|
|
|
395 * Q4.3.2:: Is there a way to get back the block cursor?
|
|
|
396 * Q4.3.3:: Can I make the cursor blink?
|
|
|
397
|
|
|
398 4.4: The Menubar
|
|
|
399 * Q4.4.1:: How do I get rid of the menubar?
|
|
|
400 * Q4.4.2:: How can I customize the menubar?
|
|
|
401 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
402 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
403 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
404
|
|
|
405 4.5: The Toolbar
|
|
|
406 * Q4.5.1:: How do I get rid of the toolbar?
|
|
|
407 * Q4.5.2:: How can I customize the toolbar?
|
|
|
408 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar?
|
|
|
409 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar
|
|
|
410
|
|
|
411 4.6: Scrollbars and Scrolling
|
|
|
412 * Q4.6.1:: How can I disable the scrollbar?
|
|
|
413 * Q4.6.2:: How can I change the scrollbar width?
|
|
|
414 * Q4.6.3:: How can I use resources to change scrollbar colors?
|
|
|
415 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this?
|
|
|
416 * Q4.6.5:: Scrolling one line at a time.
|
|
|
417 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
418 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
419
|
|
|
420 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
421 * Q4.7.1:: How can I disable the gutter tabs?
|
|
|
422 * Q4.7.2:: How can I disable the progress bar?
|
|
|
423 * Q4.7.3:: There are bugs in the gutter or widgets.
|
|
|
424 * Q4.7.4:: How can I customize the gutter or gutter tabs?
|
|
|
425
|
|
|
426 5 Interfacing with the Operating System and External Devices
|
|
|
427
|
|
|
428 5.0: X Window System and Resources
|
|
|
429 * Q5.0.1:: Where is a list of X resources?
|
|
|
430 * Q5.0.2:: How can I detect a color display?
|
|
|
431 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}?
|
|
|
432 * Q5.0.4:: How can I have the window title area display the full path?
|
|
|
433 * Q5.0.5:: @samp{xemacs -name junk} doesn't work?
|
|
|
434 * Q5.0.6:: @samp{-iconic} doesn't work.
|
|
|
435
|
|
|
436 5.1: Microsoft Windows
|
|
|
437 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
|
438 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
|
439
|
|
|
440 5.2: Printing
|
|
|
441 * Q5.2.1:: What do I need to change to make printing work?
|
|
|
442 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer?
|
|
|
443 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
|
444 * Q5.2.4:: Can you print under MS Windows?
|
|
|
445
|
|
|
446 5.3: Sound
|
|
|
447 * Q5.3.1:: How do I turn off the sound?
|
|
|
448 * Q5.3.2:: How do I get funky sounds instead of a boring beep?
|
|
|
449 * Q5.3.3:: What are NAS and ESD (EsounD)?
|
|
|
450 * Q5.3.4:: Sunsite sounds don't play.
|
|
|
451
|
|
|
452 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
453 * Q5.4.1:: What is an interior shell?
|
|
|
454 * Q5.4.2:: How do I start up a second shell buffer?
|
|
|
455 * Q5.4.3:: Telnet from shell filters too much
|
|
|
456 * Q5.4.4:: Strange things are happening in Shell Mode.
|
|
|
457 * Q5.4.5:: XEmacs complains "No such file or directory, diff"
|
|
2995
|
458 * Q5.4.6:: Cygwin error "fork_copy: linked dll/bss pass 0 failed"
|
|
2459
|
459
|
|
|
460 5.5: Multiple Device Support
|
|
|
461 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display?
|
|
|
462 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
463 * Q5.5.3:: How do I disable gnuserv from opening a new frame?
|
|
|
464 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
|
465 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
|
466
|
|
|
467 6 Connecting to the Internet
|
|
|
468
|
|
|
469 6.0: General Mail and News
|
|
|
470 * Q6.0.1:: What are the various packages for reading mail?
|
|
|
471 * Q6.0.2:: How can I send mail?
|
|
|
472 * Q6.0.3:: How do I get my outgoing mail archived?
|
|
|
473 * Q6.0.4:: How can I read and/or compose MIME messages?
|
|
|
474 * Q6.0.5:: How do I customize the From line?
|
|
|
475 * Q6.0.6:: How do I get my MUA to filter mail for me?
|
|
|
476 * Q6.0.7:: Remote mail reading with an MUA.
|
|
|
477 * Q6.0.8:: An MUA gets an error incorporating new mail.
|
|
|
478 * Q6.0.9:: Why isn't @file{movemail} working?
|
|
|
479 * Q6.0.10:: How do I make my MUA display graphical smilies?
|
|
|
480 * Q6.0.11:: How can I get those oh-so-neat X-Face lines?
|
|
|
481
|
|
|
482 6.1: Reading Mail with VM
|
|
|
483 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
484 * Q6.1.2:: How can I get VM to automatically check for new mail?
|
|
|
485 * Q6.1.3:: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"?
|
|
|
486 * Q6.1.4:: Is there a mailing list or FAQ for VM?
|
|
|
487 * Q6.1.5:: How do I make VM stay in a single frame?
|
|
|
488 * Q6.1.6:: Customization of VM not covered in the manual, or here.
|
|
|
489
|
|
|
490 6.2: Reading Netnews and Mail with Gnus
|
|
|
491 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
492 * Q6.2.2:: How do I make Gnus stay within a single frame?
|
|
|
493
|
|
|
494 6.3: FTP Access
|
|
|
495 * Q6.3.1:: Can I edit files on other hosts?
|
|
|
496 * Q6.3.2:: What is EFS?
|
|
|
497
|
|
|
498 6.4: Web Browsing with W3
|
|
|
499 * Q6.4.1:: What is W3?
|
|
|
500 * Q6.4.2:: How do I run W3 from behind a firewall?
|
|
|
501 * Q6.4.3:: Is it true that W3 supports style sheets and tables?
|
|
|
502
|
|
|
503 7 Advanced Customization Using XEmacs Lisp
|
|
|
504
|
|
2537
|
505 7.0: Emacs Lisp and @file{init.el}
|
|
|
506 * Q7.0.1:: What version of Emacs am I running?
|
|
|
507 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions?
|
|
|
508 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly.
|
|
|
509 * Q7.0.4:: How can I add directories to the @code{load-path}?
|
|
|
510 * Q7.0.5:: How to check if a lisp function is defined?
|
|
|
511 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer?
|
|
|
512
|
|
|
513 7.1: Emacs Lisp Programming Techniques
|
|
|
514 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
|
515 * Q7.1.2:: Can I generate "fake" keyboard events?
|
|
|
516 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail?
|
|
|
517 * Q7.1.4:: What is the performance hit of @code{let}?
|
|
|
518 * Q7.1.5:: What is the recommended use of @code{setq}?
|
|
|
519 * Q7.1.6:: What is the typical misuse of @code{setq}?
|
|
|
520 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down?
|
|
|
521 * Q7.1.8:: I like recursion, does it slow things down?
|
|
|
522 * Q7.1.9:: How do I put a glyph as annotation in a buffer?
|
|
|
523 * Q7.1.10:: @code{map-extents} won't traverse all of my extents!
|
|
|
524 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
|
525
|
|
|
526 7.2: Mathematics
|
|
2559
|
527 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp?
|
|
|
528 * Q7.2.2:: XEmacs segfaults when I use very big numbers!
|
|
|
529 * Q7.2.3:: Bignums are really slow!
|
|
|
530 * Q7.2.4:: Equal bignums don't compare as equal! What gives?
|
|
2459
|
531
|
|
|
532 8 Other External Packages
|
|
|
533
|
|
|
534 8.0: TeX
|
|
|
535 * Q8.0.1:: Is there something better than LaTeX mode?
|
|
|
536 * Q8.0.2:: What is AUCTeX? Where do you get it?
|
|
|
537 * Q8.0.3:: Problems installing AUCTeX.
|
|
|
538 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline?
|
|
|
539
|
|
|
540 8.1: Other Unbundled Packages
|
|
|
541 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
|
542 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets?
|
|
|
543 * Q8.1.3:: Is there a MatLab mode?
|
|
|
544
|
|
|
545 8.2: Environments Built Around XEmacs
|
|
|
546 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop?
|
|
|
547 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21?
|
|
|
548 * Q8.2.3:: What is/was Energize?
|
|
|
549 * Q8.2.4:: What is Infodock?
|
|
|
550
|
|
|
551 9 What the Future Holds
|
|
|
552
|
|
|
553 9.0: Changes
|
|
|
554 * Q9.0.1:: What new features will be in XEmacs soon?
|
|
|
555 * Q9.0.2:: What's new in XEmacs 21.4?
|
|
|
556 * Q9.0.3:: What's new in XEmacs 21.1?
|
|
|
557 * Q9.0.4:: What's new in XEmacs 20.4?
|
|
|
558 * Q9.0.5:: What's new in XEmacs 20.3?
|
|
|
559 * Q9.0.6:: What's new in XEmacs 20.2?
|
|
|
560
|
|
|
561 10 New information about old XEmacsen
|
|
|
562
|
|
|
563 10.0: XEmacs 21.1
|
|
|
564 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
2559
|
565 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1.
|
|
|
566
|
|
428
|
567 @end detailmenu
|
|
|
568 @end menu
|
|
|
569
|
|
|
570 @node Introduction, Installation, Top, Top
|
|
|
571 @unnumbered 1 Introduction, Policy, Credits
|
|
|
572
|
|
|
573 Learning XEmacs is a lifelong activity. Even people who have used Emacs
|
|
|
574 for years keep discovering new features. Therefore this document cannot
|
|
|
575 be complete. Instead it is aimed at the person who is either
|
|
|
576 considering XEmacs for their own use, or has just obtained it and is
|
|
|
577 wondering what to do next. It is also useful as a reference to
|
|
|
578 available resources.
|
|
|
579
|
|
2417
|
580 The previous maintainer of the FAQ was
|
|
|
581 @email{rossini@@biostat.washington.edu, Anthony Rossini}, who started
|
|
|
582 it, after getting tired of hearing JWZ complain about repeatedly
|
|
|
583 having to answer questions. @email{ben@@xemacs.org, Ben Wing} then
|
|
|
584 took over and did a massive update reorganizing the whole thing. At
|
|
|
585 this point Anthony took back over, but then had to give it up again.
|
|
|
586 Some of the other contributors to this FAQ are listed later in this
|
|
|
587 document.
|
|
428
|
588
|
|
|
589 The previous version was converted to hypertext format, and edited by
|
|
|
590 @email{steve@@xemacs.org, Steven L. Baur}. It was converted back to
|
|
434
|
591 texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}. The FAQ was then
|
|
|
592 maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it
|
|
2417
|
593 on to ChristianNyb@o{}, and then to @email{wambold@@xemacs.org,Sandra Wambold}.
|
|
|
594
|
|
|
595 The current version of the FAQ has been heavily redone by
|
|
|
596 @email{ben@@xemacs.org, Ben Wing}.
|
|
428
|
597
|
|
|
598 If you notice any errors or items which should be added or amended to
|
|
2417
|
599 this FAQ please send email to @email{xemacs-beta@@xemacs.org}.
|
|
|
600 Include @samp{XEmacs FAQ} on the Subject: line.
|
|
428
|
601
|
|
|
602 @menu
|
|
2537
|
603 1.0: What is XEmacs?
|
|
2417
|
604 * Q1.0.1:: What is XEmacs?
|
|
|
605 * Q1.0.2:: What is the current version of XEmacs?
|
|
2537
|
606 * Q1.0.3:: How do you pronounce XEmacs?
|
|
|
607 * Q1.0.4:: What does XEmacs look like?
|
|
|
608 * Q1.0.5:: Who wrote XEmacs?
|
|
|
609 * Q1.0.6:: Who wrote the FAQ?
|
|
|
610
|
|
|
611 1.1: Getting XEmacs
|
|
|
612 * Q1.1.1:: Where can I find XEmacs?
|
|
|
613 * Q1.1.2:: Are binaries available?
|
|
|
614 * Q1.1.3:: How do I get the bleeding-edge sources?
|
|
|
615 * Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual?
|
|
|
616
|
|
|
617 1.2: Versions for Different Operating Systems
|
|
|
618 * Q1.2.1:: Do I need X11 to run XEmacs?
|
|
|
619 * Q1.2.2:: What versions of Unix does XEmacs run on?
|
|
|
620 * Q1.2.3:: Is there a port of XEmacs to Microsoft Windows?
|
|
|
621 * Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
622 * Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
623 * Q1.2.6:: What are the differences between the various MS Windows emacsen?
|
|
|
624 * Q1.2.7:: How does the port cope with differences in the Windows user interface?
|
|
|
625 * Q1.2.8:: Is there a port of XEmacs to the Macintosh?
|
|
|
626 * Q1.2.9:: Is there a port of XEmacs to MS-DOS?
|
|
|
627 * Q1.2.10:: Is there a port of XEmacs to OS/2?
|
|
|
628 * Q1.2.11:: Is there a port of XEmacs to NextStep?
|
|
|
629 * Q1.2.12:: Is there a port of XEmacs to VMS?
|
|
|
630
|
|
|
631 1.3: Getting Started
|
|
|
632 * Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
|
633 * Q1.3.2:: Where do I put my @file{init.el} file?
|
|
|
634 * Q1.3.3:: Can I use the same @file{init.el} with the other Emacs?
|
|
|
635 * Q1.3.4:: Any good XEmacs tutorials around?
|
|
|
636 * Q1.3.5:: May I see an example of a useful XEmacs Lisp function?
|
|
|
637 * Q1.3.6:: And how do I bind it to a key?
|
|
|
638 * Q1.3.7:: What's the difference between a macro and a function?
|
|
|
639 * Q1.3.8:: What is @code{Custom}?
|
|
|
640
|
|
|
641 1.4: Getting Help
|
|
|
642 * Q1.4.1:: Where can I get help?
|
|
|
643 * Q1.4.2:: Which mailing lists are there?
|
|
2559
|
644 * Q1.4.3:: Where are the mailing lists archived?
|
|
|
645 * Q1.4.4:: How can I get two instances of info?
|
|
|
646 * Q1.4.5:: How do I add new Info directories?
|
|
2537
|
647
|
|
|
648 1.5: Contributing to XEmacs
|
|
|
649 * Q1.5.1:: How do I submit changes to the FAQ?
|
|
|
650 * Q1.5.2:: How do I become a beta tester?
|
|
|
651 * Q1.5.3:: How do I contribute to XEmacs itself?
|
|
2559
|
652 * Q1.5.4:: How do I get started developing XEmacs?
|
|
|
653 * Q1.5.5:: What's the basic layout of the code?
|
|
2537
|
654
|
|
|
655 1.6: Politics (XEmacs vs. GNU Emacs)
|
|
|
656 * Q1.6.1:: What is GNU Emacs?
|
|
|
657 * Q1.6.2:: How does XEmacs differ from GNU Emacs?
|
|
|
658 * Q1.6.3:: How much does XEmacs differ?
|
|
|
659 * Q1.6.4:: Is XEmacs "GNU"?
|
|
|
660 * Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
|
661 * Q1.6.6:: Why haven't XEmacs and GNU Emacs merged?
|
|
|
662
|
|
|
663 1.7: External Packages
|
|
2559
|
664 * Q1.7.1:: What is the package system?
|
|
|
665 * Q1.7.2:: Which external packages are there?
|
|
|
666 * Q1.7.3:: Do I need to have the packages to run XEmacs?
|
|
|
667 * Q1.7.4:: Is there a way to find which package has particular functionality?
|
|
2537
|
668
|
|
|
669 1.8: Internationalization
|
|
|
670 * Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
|
671 * Q1.8.2:: How can I help with internationalization?
|
|
|
672 * Q1.8.3:: How do I type non-ASCII characters?
|
|
|
673 * Q1.8.4:: Can XEmacs messages come out in a different language?
|
|
|
674 * Q1.8.5:: Please explain the various input methods in MULE/XEmacs
|
|
|
675 * Q1.8.6:: How do I portably code for MULE/XEmacs?
|
|
|
676 * Q1.8.7:: How about Cyrillic modes?
|
|
|
677 * Q1.8.8:: Does XEmacs support Unicode?
|
|
|
678 * Q1.8.9:: How does XEmacs display Unicode?
|
|
428
|
679 @end menu
|
|
|
680
|
|
2537
|
681 @unnumberedsec 1.0: What is XEmacs?
|
|
2417
|
682
|
|
428
|
683 @node Q1.0.1, Q1.0.2, Introduction, Introduction
|
|
|
684 @unnumberedsubsec Q1.0.1: What is XEmacs?
|
|
|
685
|
|
479
|
686 XEmacs is a powerful, highly customizable open source text editor and
|
|
2417
|
687 application development system, with full GUI support. It is
|
|
|
688 protected under the GNU Public License and related to other versions
|
|
|
689 of Emacs, in particular GNU Emacs. Its emphasis is on modern
|
|
|
690 graphical user interface support and an open software development
|
|
|
691 model, similar to Linux. XEmacs has an active development community
|
|
|
692 numbering in the hundreds (and thousands of active beta testers on top
|
|
|
693 of this), and runs on all versions of MS Windows, on Mac OS X, on
|
|
|
694 Linux, and on nearly every other version of Unix in existence.
|
|
|
695 Support for XEmacs has been supplied by Sun Microsystems, University
|
|
|
696 of Illinois, Lucid, ETL/Electrotechnical Laboratory, Amdahl
|
|
|
697 Corporation, BeOpen, and others, as well as the unpaid time of a great
|
|
|
698 number of individual developers.
|
|
428
|
699
|
|
|
700 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction
|
|
|
701 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs?
|
|
|
702
|
|
2417
|
703 XEmacs versions 21.4.* are releases made from the current stable
|
|
|
704 sources. XEmacs versions 21.5.* (which will be released as 22.0) are
|
|
|
705 releases made from the development sources. Check at
|
|
|
706 @uref{http://www.xemacs.org} for the current minor version. XEmacs
|
|
|
707 versions 21.1.* were the previous stable releases, now retired.
|
|
|
708
|
|
|
709 XEmacs 20.4, released in February 1998, was the last release of v20.
|
|
|
710
|
|
|
711 XEmacs 19.16, released in November, 1997. was the last release of v19,
|
|
|
712 and was also the last version without international language support.
|
|
428
|
713
|
|
|
714 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction
|
|
2537
|
715 @unnumberedsubsec Q1.0.3: How do you pronounce XEmacs?
|
|
|
716
|
|
|
717 The most common pronounciation is @samp{Eks eemax}.
|
|
428
|
718
|
|
|
719 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction
|
|
2537
|
720 @unnumberedsubsec Q1.0.4: What does XEmacs look like?
|
|
|
721
|
|
|
722 Screen snapshots are available at
|
|
|
723 @uref{http://www.xemacs.org/About/Screenshots/index.html}
|
|
|
724 as part of the XEmacs website.
|
|
|
725
|
|
|
726 @node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
|
|
|
727 @unnumberedsubsec Q1.0.5: Who wrote XEmacs?
|
|
|
728
|
|
|
729 XEmacs is the result of the time and effort of many people, and the
|
|
|
730 active developers have changed over time. There are two major
|
|
|
731 components of the XEmacs effort -- writing the code itself and providing
|
|
|
732 all the support work (testing the code, releasing beta and final
|
|
|
733 versions, handling patches, reading bug reports, maintaining the web
|
|
|
734 site, managing the mailing lists, etc. etc.). Neither component would
|
|
|
735 work without the other.
|
|
|
736
|
|
|
737 @subheading CODING
|
|
|
738
|
|
|
739 The primary code contributor over the years has been Ben Wing (active
|
|
|
740 since late 1992). Between 1991 and 1995, large amounts of coding was
|
|
|
741 contributed by Jamie Zawinski and Chuck Thompson. Many other people
|
|
|
742 have authored major subsystems or otherwise contributed large amounts of
|
|
|
743 code, including Andy Piper, Hrvoje Niksic, Jerry James, Jonathan Harris,
|
|
|
744 Kyle Jones, Martin Buchholz, Michael Sperber, Olivier Galibert, Richard
|
|
|
745 Mlynarik, Stig, William Perry and plenty of others.
|
|
|
746
|
|
|
747 Primary XEmacs-specific subsystems and their authors:
|
|
|
748
|
|
|
749 @table @asis
|
|
|
750 @item Objects
|
|
|
751 @itemize @minus
|
|
|
752 @item
|
|
|
753 Conversion from 26-bit to 28-bit pointers and integers, lrecords, lcrecords: Richard Mlynarik, 1994
|
|
|
754 @item
|
|
|
755 Conversion to 32-bit pointers and 31-bit integers: Kyle Jones, Martin Buchholz
|
|
|
756 @item
|
|
|
757 Portable dumper, object descriptions: Olivier Galibert
|
|
|
758 @item
|
|
|
759 KKCC (new garbage collector), ephemerons, weak boxes: Michael Sperber and students
|
|
|
760 @item
|
|
|
761 Random object work (object equal and hash methods, weak lists, lcrecord lists, bit vectors, dynarr, blocktype, opaque, string resizing): Ben Wing
|
|
|
762 @item
|
|
|
763 Profiling: Ben Wing
|
|
|
764 @item
|
|
|
765 Some byte-compilation and hash-table improvements: Martin Buchholz
|
|
|
766 @item
|
|
|
767 Bignum: Jerry James
|
|
|
768 @end itemize
|
|
|
769
|
|
|
770 @item Internationalization/Mule
|
|
|
771 @itemize @minus
|
|
|
772 @item
|
|
|
773 mostly Ben Wing; many ideas for future work, Stephen Turnbull
|
|
|
774 @end itemize
|
|
|
775
|
|
|
776 @item I/O
|
|
|
777 @itemize @minus
|
|
|
778 @item
|
|
|
779 Basic event/event-stream implementation: Jamie Zawinski
|
|
|
780 @item
|
|
|
781 Most event work since 1994: Ben Wing
|
|
|
782 @item
|
|
|
783 Asynchronous stuff (async timeouts, signals, quit-checking): Ben Wing
|
|
|
784 @item
|
|
|
785 Process method abstraction, Windows process work: Kirill Katsnelson
|
|
|
786 @item
|
|
|
787 Misc-user events, async timeouts, most quit-checking and signal code, most other work since 1994: Ben Wing
|
|
|
788 @item
|
|
|
789 Lstreams: Ben Wing
|
|
|
790 @end itemize
|
|
|
791
|
|
|
792 @item Display
|
|
|
793 @itemize @minus
|
|
|
794 @item
|
|
|
795 Redisplay mechanism: implementation, Chuck Thompson; additional work, lots of people
|
|
|
796 @item
|
|
|
797 Glyphs: mostly Ben Wing
|
|
|
798 @item
|
|
|
799 Specifiers: Ben Wing
|
|
|
800 @item
|
|
|
801 Extents: initial implementation, someone at Lucid; rewrite, 1994, Ben Wing
|
|
|
802 @item
|
|
|
803 Widgets: Andy Piper
|
|
|
804 @item
|
|
|
805 JPEG/PNG/TIFF image converters: Ben Wing, William Perry, Jareth Hein, others (see comment in @file{glyphs-eimage.c})
|
|
|
806 @item
|
|
|
807 Menus: Jamie Zawinski, someone at Lucid (Lucid menus)
|
|
|
808 @item
|
|
|
809 Scrollbars: Chuck Thompson, ??? (Lucid scrollbar)
|
|
|
810 @item
|
|
|
811 Multi-device/device-independence work (console/device/etc methods): Ben Wing, prototype by chuck thompson
|
|
|
812 @item
|
|
|
813 Faces: first implementation, Jamie Zawinski; second, chuck; third, Ben Wing
|
|
|
814 @item
|
|
|
815 Fonts/colors: first implementation, Jamie Zawinski; further work, Ben Wing
|
|
|
816 @item
|
|
|
817 Toolbars: implementation, chuck, much interface work, Ben Wing
|
|
|
818 @item
|
|
|
819 Gutters, tabs: andy piper
|
|
|
820 @end itemize
|
|
|
821
|
|
|
822 @item Device subsystems
|
|
|
823 @itemize @minus
|
|
|
824 @item
|
|
|
825 X Windows: Jamie Zawinksi, Ben Wing, others
|
|
|
826 @item
|
|
|
827 GTK: William Perry, Malcolm Purvis
|
|
|
828 @item
|
|
|
829 MS Windows: initial implementation, Jonathan Harris; some more work, Andy Piper, Ben Wing
|
|
|
830 @item
|
|
|
831 TTY: Chuck Thompson, Ben Wing
|
|
|
832 @item
|
|
|
833 Cygwin: Andy Piper
|
|
|
834 @end itemize
|
|
|
835
|
|
|
836 @item Misc
|
|
|
837 @itemize @minus
|
|
|
838 @item
|
|
|
839 Configure: initial porting from fsf, Chuck Thompson; conversion to autoconf 2, much rewriting, Martin Buchholz
|
|
|
840 @item
|
|
|
841 Most initialization-related code: Ben Wing
|
|
|
842 @item
|
|
|
843 Internals manual, much of Lisp manual: Ben Wing
|
|
|
844 @item
|
|
|
845 FSF synching: initial sync with FSF 19, Richard Mlynarik, further work, Ben Wing
|
|
|
846 @end itemize
|
|
|
847 @end table
|
|
|
848
|
|
|
849 @subheading SUPPORT
|
|
|
850
|
|
|
851 Currently, support duties are handled by many different people.
|
|
|
852
|
|
|
853 Release managers have been
|
|
|
854
|
|
|
855 @itemize @minus
|
|
|
856 @item
|
|
|
857 Stephen Turnbull (April 2001 - January 2003, March 2004 - present, 21.2.47 - 21.4.12, 21.5.2 - 21.5.7, 21.5.17 - present)
|
|
|
858 @item
|
|
|
859 Vin Shelton (May 2003 - present, 21.4.13 - present)
|
|
|
860 @item
|
|
|
861 Steve Youngs (July 2002 - September 2003, 21.5.8 - 21.5.16)
|
|
|
862 @item
|
|
|
863 Martin Buchholz (December 1998, November 1999 - May 2001, 21.2.7 - 21.2.8, 21.2.21 - 21.2.46, 21.5.0 - 21.5.1)
|
|
|
864 @item
|
|
|
865 Steve Baur (early 1997 - December 1998, February 1999 - November 1999, 19.15 - 21.2.5, 21.2.9 - 21.2.20)
|
|
|
866 @item
|
|
|
867 Andy Piper (December 1998, 21.2.6)
|
|
|
868 @item
|
|
|
869 Chuck Thompson (June 1994 - September 1996, 19.11 - 19.14)
|
|
|
870 @item
|
|
|
871 Jamie Zawinski (April 1991 - June 1994, 19.0 - 19.10)
|
|
|
872 @end itemize
|
|
|
873
|
|
|
874 The recent overlapping dates are intentional, since two or three trees
|
|
|
875 are maintained simultaneously at any point.
|
|
|
876
|
|
|
877 Other major support work:
|
|
|
878
|
|
|
879 @itemize @minus
|
|
|
880 @item
|
|
|
881 Adrian Aichner wrote and maintains the web site.
|
|
|
882 @item
|
|
|
883 Stephen Turnbull has produced many of the beta and semi-stable releases
|
|
|
884 and has attempted to be the "face" of XEmacs on the newsgroups and
|
|
|
885 mailing lists.
|
|
|
886 @item
|
|
|
887 Steve Youngs currently produces the beta releases (???).
|
|
|
888 @item
|
|
|
889 Steve Youngs, Ville Skytta, and now Norbert Koch have taken turns
|
|
|
890 maintaining the packages.
|
|
|
891 @item
|
|
|
892 Vin Shelton maintains the stable releases.
|
|
|
893 @item
|
|
|
894 Testing - #### Norbert, Adrian, ???
|
|
|
895 @end itemize
|
|
|
896
|
|
|
897 Portraits and email of some of the major developers:
|
|
|
898
|
|
|
899 @itemize @bullet
|
|
|
900 @item @email{andy@@xemacs.org, Andy Piper}
|
|
|
901 @html
|
|
|
902 <br><img src="piper.png" alt="Portrait of Andy Piper"><br>
|
|
|
903 @end html
|
|
|
904
|
|
|
905 @item @email{ben@@xemacs.org, Ben Wing}
|
|
|
906 @html
|
|
|
907 <br><img src="ben.png" alt="Portrait of Ben Wing"><br>
|
|
|
908 @end html
|
|
|
909
|
|
|
910 @item @email{cthomp@@xemacs.org, Chuck Thompson}
|
|
|
911 @html
|
|
|
912 <br><img src="cthomp.png" alt="Portrait of Chuck Thompson"><br>
|
|
|
913 @end html
|
|
|
914
|
|
|
915 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
|
|
|
916
|
|
|
917 @html
|
|
|
918 <br><img src="hniksic.png" alt="Portrait of Hrvoje Niksic"><br>
|
|
|
919 @end html
|
|
|
920
|
|
|
921 @item @email{jwz@@jwz.org, Jamie Zawinski}
|
|
|
922 @html
|
|
|
923 <br><img src="jwz.png" alt="Portrait of Jamie Zawinski"><br>
|
|
|
924 @end html
|
|
|
925
|
|
|
926 @item @email{martin@@xemacs.org, Martin Buchholz}
|
|
|
927 @html
|
|
|
928 <br><img src="martin.png" alt="Portrait of Martin Buchholz"><br>
|
|
|
929 @end html
|
|
|
930
|
|
|
931 @item @email{mly@@adoc.xerox.com, Richard Mlynarik}
|
|
|
932 @html
|
|
|
933 <br><img src="mly.png" alt="Portrait of Richard Mlynarik"><br>
|
|
|
934 @end html
|
|
|
935
|
|
|
936 @item @email{stephen@@xemacs.org, Stephen Turnbull}
|
|
|
937
|
|
|
938 @item @email{steve@@xemacs.org, Steve Baur}
|
|
|
939 @html
|
|
|
940 <br><img src="slb.png" alt="Portrait of Steve Baur"><br>
|
|
|
941 @end html
|
|
|
942 @end itemize
|
|
|
943
|
|
|
944 Many other people have contributed to XEmacs; this is partially
|
|
|
945 enumerated in the @samp{About XEmacs} option in the Help menu.
|
|
|
946
|
|
|
947 @node Q1.0.6, Q1.1.1, Q1.0.5, Introduction
|
|
|
948 @unnumberedsubsec Q1.0.6: Who wrote the FAQ?
|
|
|
949
|
|
|
950 The current version of this FAQ was created by @email{ben@@xemacs.org,
|
|
|
951 Ben Wing}.
|
|
|
952
|
|
|
953 Previous contributors to the FAQ include
|
|
|
954
|
|
|
955 @itemize @bullet
|
|
|
956 @item @email{steve@@xemacs.org, SL Baur}
|
|
|
957
|
|
|
958 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
|
|
|
959
|
|
|
960 @item @email{binge@@aloft.att.com, Curtis.N.Bingham}
|
|
|
961
|
|
|
962 @item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan}
|
|
|
963
|
|
|
964 @item @email{rjc@@cogsci.ed.ac.uk, Richard Caley}
|
|
|
965
|
|
|
966 @item @email{cognot@@ensg.u-nancy.fr, Richard Cognot}
|
|
|
967
|
|
|
968 @item @email{daku@@nortel.ca, Mark Daku}
|
|
|
969
|
|
|
970 @item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque}
|
|
|
971
|
|
|
972 @item @email{eeide@@cs.utah.edu, Eric Eide}
|
|
|
973
|
|
|
974 @item @email{af@@biomath.jussieu.fr, Alain Fauconnet}
|
|
|
975
|
|
|
976 @item @email{cflatter@@nrao.edu, Chris Flatters}
|
|
|
977
|
|
|
978 @item @email{ginsparg@@adra.com, Evelyn Ginsparg}
|
|
|
979
|
|
|
980 @item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall}
|
|
|
981
|
|
|
982 @item @email{dkindred@@cmu.edu, Darrell Kindred}
|
|
|
983
|
|
|
984 @item @email{dmoore@@ucsd.edu, David Moore}
|
|
|
985
|
|
|
986 @item @email{arup+@@cmu.edu, Arup Mukherjee}
|
|
|
987
|
|
|
988 @item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen}
|
|
|
989
|
|
|
990 @item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell}
|
|
|
991
|
|
|
992 @item @email{dworkin@@ccs.neu.edu, Justin Sheehy}
|
|
|
993
|
|
|
994 @item @email{stig@@hackvan.com, Stig}
|
|
|
995
|
|
|
996 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
|
|
|
997 @end itemize
|
|
|
998
|
|
|
999 @unnumberedsec 1.1: Getting XEmacs
|
|
|
1000
|
|
|
1001 @node Q1.1.1, Q1.1.2, Q1.0.6, Introduction
|
|
|
1002 @unnumberedsubsec Q1.1.1: Where can I find XEmacs?
|
|
|
1003
|
|
|
1004 To download XEmacs, visit the XEmacs WWW page at
|
|
|
1005 @uref{http://www.xemacs.org/Download/}. The most up-to-date list of
|
|
|
1006 distribution sites can always be found there. Try to pick a site that
|
|
|
1007 is networkologically close to you. If you know of other mirrors of
|
|
|
1008 the XEmacs archives, please send e-mail to
|
|
|
1009 @uref{mailto:webmaster@@xemacs.org} and we will list them here as well.
|
|
|
1010
|
|
|
1011 The canonical distribution point is ftp.xemacs.org, available either
|
|
|
1012 through HTTP (@uref{http://ftp.xemacs.org/}) or anonymous FTP
|
|
|
1013 (@uref{ftp://ftp.xemacs.org/pub/xemacs/}).
|
|
|
1014
|
|
|
1015 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
|
|
|
1016 @unnumberedsubsec Q1.1.2: Are binaries available?
|
|
2417
|
1017
|
|
|
1018 MS Windows binaries are available at
|
|
|
1019 @uref{http://www.xemacs.org/Download/win32/} for the native versions
|
|
|
1020 of 21.4 and 21.1. Cygwin binaries are now available as part of the
|
|
|
1021 standard Cygwin installation process. XEmacs also comes pre-built as
|
|
|
1022 part of many Linux distributions, such as Red Hat and SuSE.
|
|
|
1023
|
|
|
1024 Otherwise, you will need to build XEmacs yourself or get your system
|
|
|
1025 administrator to do it. Generally, this is not a difficult process
|
|
|
1026 under Unix and Mac OS X, as XEmacs has been tested under all of the
|
|
|
1027 common Unix versions and under Mac OS X and comes with an extensive
|
|
|
1028 configure script that is able to automatically detect most aspects of
|
|
|
1029 the configuration of your particular system.
|
|
|
1030
|
|
2537
|
1031 @node Q1.1.3, Q1.1.4, Q1.1.2, Introduction
|
|
|
1032 @unnumberedsubsec Q1.1.3: How do I get the bleeding-edge sources?
|
|
|
1033
|
|
|
1034 If you are interested in developing XEmacs, or getting the absolutely most
|
|
|
1035 recent, up-to-the-moment, bleeding-edge source code, you can directly
|
|
|
1036 access the master CVS source tree (read-only, of course, until you ask for
|
|
|
1037 and are granted permission to directly modify portions of the source tree)
|
|
|
1038 at cvs.xemacs.org. Directions on how to access the source tree are located
|
|
|
1039 at @uref{http://www.xemacs.org/Develop/cvsaccess.html}.
|
|
|
1040
|
|
|
1041 Nightly CVS snapshots are available at
|
|
|
1042 @uref{http://www.dk.xemacs.org/Download/CVS-snapshots/}.
|
|
|
1043
|
|
|
1044 @node Q1.1.4, Q1.2.1, Q1.1.3, Introduction
|
|
|
1045 @unnumberedsubsec Q1.1.4: Where can I obtain a printed copy of the XEmacs User's Manual?
|
|
|
1046
|
|
|
1047 Pre-printed manuals are not available. If you are familiar with
|
|
|
1048 TeX, you can generate your own manual from the XEmacs sources.
|
|
|
1049
|
|
|
1050 HTML and Postscript versions of XEmacs manuals are available from the
|
|
|
1051 XEmacs web site at
|
|
|
1052 @uref{http://www.xemacs.org/Documentation/index.html}.
|
|
|
1053
|
|
|
1054 @unnumberedsec 1.2: Versions for Different Operating Systems
|
|
|
1055
|
|
|
1056 @node Q1.2.1, Q1.2.2, Q1.1.4, Introduction
|
|
|
1057 @unnumberedsubsec Q1.2.1: Do I need X11 to run XEmacs?
|
|
|
1058
|
|
|
1059 No. The name @dfn{XEmacs} is unfortunate in the sense that it is
|
|
|
1060 @strong{not} an X Window System-only version of Emacs. XEmacs has
|
|
|
1061 full color support on a color-capable character terminal.
|
|
|
1062
|
|
|
1063 @node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
|
|
|
1064 @unnumberedsubsec Q1.2.2: What versions of Unix does XEmacs run on?
|
|
|
1065
|
|
2559
|
1066 XEmacs is regularly tested on Linux, Solaris, SunOS, HP/UX, FreeBSD,
|
|
|
1067 OpenBSD, BSD/OS aka BSDI, Tru64 aka DEC/OSF, SCO5, and probably
|
|
|
1068 others. It should work on all versions of Unix created in the last 10
|
|
|
1069 years or so, perhaps with a bit of work on more obscure platforms to
|
|
|
1070 correct bit-rot. It uses a sophisticated configuration system to
|
|
|
1071 auto-detect zillions of features that are implemented differently in
|
|
|
1072 different versions of Unix, so it will probably work on your vendor's
|
|
|
1073 version, possibly with a bit of tweaking, even if we've never heard of
|
|
|
1074 it.
|
|
|
1075
|
|
2537
|
1076 For problems with particular machines and versions of Unix, see the
|
|
|
1077 @file{PROBLEMS} file.
|
|
|
1078
|
|
|
1079 Much effort has gone into making XEmacs work on as many different
|
|
|
1080 machines, configurations, and compilers as possible.
|
|
|
1081
|
|
|
1082 Much effort has gone into making XEmacs 64-bit clean.
|
|
|
1083
|
|
|
1084 Much effort has gone into removing system-specific code, and replacing
|
|
|
1085 such code with autodetection at configure time.
|
|
|
1086
|
|
|
1087 The XEmacs core should build "out of the box" on most Unix-like systems.
|
|
|
1088
|
|
|
1089 XEmacs 21.2 was tested and @samp{make check} succeeded on these Unix
|
|
|
1090 configurations as of 2001-02-10:
|
|
|
1091
|
|
|
1092 @example
|
|
|
1093 alphaev56-dec-osf4.0e (both Compaq C and gcc)
|
|
|
1094 i386-unknown-freebsd4.2
|
|
|
1095 i386-unknown-netbsdelf1.5
|
|
|
1096 i586-sco-sysv5uw7.0.1 (both SCO's cc and gcc)
|
|
|
1097 i686-pc-linux-gnu
|
|
|
1098 hppa2.0-hp-hpux10.20 (both HP's ANSI cc and gcc)
|
|
|
1099 mips-sgi-irix6.5 (both MIPSpro cc and gcc)
|
|
|
1100 rs6000-ibm-aix4.3.0.0 (both IBM's xlc and gcc)
|
|
|
1101 sparc-sun-solaris2.6 (both Sun's Forte C and gcc)
|
|
|
1102 sparc-sun-solaris2.7 (both Sun's Forte C and gcc)
|
|
|
1103 sparc-sun-sunos4.1.4 (gcc)
|
|
|
1104 @end example
|
|
|
1105
|
|
3018
|
1106 Some systems have a dual mode 32-bit/64-bit compiler. On most of these,
|
|
|
1107 XEmacs requires the @samp{--pdump} (in XEmacs 21.5,
|
|
|
1108 @samp{--enable-pdump}) configure option to build correctly with the
|
|
|
1109 64-bit version of the compiler.
|
|
2537
|
1110
|
|
|
1111 @example
|
|
|
1112 mips-sgi-irix6.5, CC="gcc -mabi=64"
|
|
|
1113 mips-sgi-irix6.5, CC="cc -64"
|
|
|
1114 rs6000-ibm-aix4.3.0.0, CC="cc -q64"
|
|
|
1115 @end example
|
|
|
1116
|
|
|
1117 On most of these systems, XEmacs also builds with a C++ compiler,
|
|
|
1118 but not "out of the box". This feature is only for use by the
|
|
|
1119 maintainers.
|
|
|
1120
|
|
|
1121 XEmacs 21.2 is known @emph{not} to work on any machines with m680x0
|
|
|
1122 processors. Sorry, all you sun3 and Unix PC nostalgia buffs out there.
|
|
|
1123
|
|
|
1124 VMS has never been supported by XEmacs. In fact, all the old VMS code
|
|
|
1125 inherited from Emacs has been removed. Sorry, all you VMS fans out there.
|
|
|
1126
|
|
|
1127 @node Q1.2.3, Q1.2.4, Q1.2.2, Introduction
|
|
|
1128 @unnumberedsubsec Q1.2.3: Is there a port of XEmacs to Microsoft Windows?
|
|
|
1129
|
|
|
1130 Yes. Beginning with release 21.0, XEmacs has worked under MS Windows
|
|
|
1131 and is fully-featured and actively developed. A group of dedicated
|
|
|
1132 developers actively maintains and improves the Windows-specific
|
|
|
1133 portions of the code. Some of the core developers, in fact, use
|
|
|
1134 Windows as their only development environment, and some features, such
|
|
|
1135 as printing, actually work better on Windows than native Unix and Mac
|
|
|
1136 OS X. The mailing list at @email{xemacs-winnt@@xemacs.org} is dedicated
|
|
|
1137 to that effort (please use the -request address to
|
|
|
1138 subscribe). (Despite its name, XEmacs actually works on all versions
|
|
|
1139 of Windows.)
|
|
|
1140
|
|
|
1141 The list name is misleading, as XEmacs supports and has been compiled on
|
|
|
1142 Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows
|
|
|
1143 XP, and all newer versions of Windows. The MS Windows-specific code is
|
|
|
1144 based on Microsoft Win32 API, and will not work on MS Windows 3.x or on
|
|
|
1145 MS-DOS.
|
|
|
1146
|
|
|
1147 XEmacs also supports the Cygwin and MinGW development and runtime
|
|
|
1148 environments, where it also uses native Windows code for graphical
|
|
|
1149 features. In addition, under Cygwin it is possible to compile XEmacs
|
|
|
1150 to use an X server (and XFree86 is available as part of the standard
|
|
|
1151 Cygwin installation).
|
|
|
1152
|
|
|
1153 @node Q1.2.4, Q1.2.5, Q1.2.3, Introduction
|
|
|
1154 @unnumberedsubsec Q1.2.4: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
1155
|
|
|
1156 Yes, you can, but no you do not need to. In fact, we recommend that you
|
|
|
1157 use a native-GUI version unless you have a specific need for an X
|
|
|
1158 version.
|
|
|
1159
|
|
|
1160 @node Q1.2.5, Q1.2.6, Q1.2.4, Introduction
|
|
|
1161 @unnumberedsubsec Q1.2.5: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
1162
|
|
|
1163 To answer the second part of the question: No, you, you don't need
|
|
|
1164 Cygwin or MinGW to build or to run XEmacs. But if you have them and
|
|
|
1165 want to use them, XEmacs supports these environments.
|
|
|
1166
|
|
|
1167 (One important reason to support Cygwin is that it lets the MS Windows
|
|
|
1168 developers test out their code in a Unix environment without actually
|
|
|
1169 having to have a Unix machine around. For this reason alone, Cygwin
|
|
|
1170 support is likely to remain supported for a long time in XEmacs. Same
|
|
|
1171 goes for the X support under Cygwin, for the same reasons. MinGW
|
|
|
1172 support, on the other hand, depends on volunteers to keep it up to date;
|
|
|
1173 but this is generally not hard.)
|
|
|
1174
|
|
|
1175 Cygwin is a set of tools providing Unix-like API on top of Win32.
|
|
|
1176 It makes it easy to port large Unix programs without significant
|
|
|
1177 changes to their source code. It is a development environment as well
|
|
|
1178 as a runtime environment.
|
|
|
1179
|
|
|
1180 When built with Cygwin, XEmacs supports all display types -- TTY, X &
|
|
|
1181 Win32 GUI, and can be built with support for all three simultaneously.
|
|
|
1182 If you build with Win32 GUI support then the Cygwin version uses the
|
|
|
1183 majority of the Windows-specific code, which is mostly related to
|
|
|
1184 display. If you want to build with X support you need X libraries (and
|
|
2559
|
1185 an X server to display XEmacs on); see @ref{Q2.3.7}. TTY and Win32 GUI
|
|
2537
|
1186 require no additional libraries beyond what comes standard with Cygwin.
|
|
|
1187
|
|
|
1188 The advantages of the Cygwin version are that it integrates well with
|
|
|
1189 the Cygwin environment for existing Cygwin users; uses configure so
|
|
|
1190 building with different features is very easy; and actively supports X &
|
|
|
1191 TTY. Furthermore, the entire Cygwin environment and compiler are free,
|
|
|
1192 whereas Visual C++ costs money.
|
|
|
1193
|
|
|
1194 The disadvantage is that it requires the whole Cygwin environment,
|
|
|
1195 whereas the native port requires only a suitable MS Windows compiler.
|
|
|
1196 Also, it follows the Unix filesystem and process model very closely
|
|
|
1197 (some will undoubtedly view this as an advantage).
|
|
|
1198
|
|
|
1199 See @uref{http://www.cygwin.com/} for more information on
|
|
|
1200 Cygwin.
|
|
|
1201
|
|
|
1202 MinGW is a collection of header files and import libraries that allow
|
|
|
1203 one to use GCC under the Cygwin environment to compile and produce
|
|
|
1204 exactly the same native Win32 programs that you can using Visual C++.
|
|
|
1205 Programs compiled with MinGW make use of the standard Microsoft runtime
|
|
|
1206 library @file{MSVCRT.DLL}, present on all Windows systems, and look,
|
|
|
1207 feel, and act like a standard Visual-C-produced application. (The only
|
|
|
1208 difference is the compiler.) This means that, unlike a
|
|
|
1209 standardly-compiled Cygwin application, no extra runtime support
|
|
|
1210 (e.g. Cygwin's @file{cygwin1.dll}) is required. This, along with the
|
|
|
1211 fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y
|
|
|
1212 environment, for those die-hard Unix hackers out there), is the main
|
|
|
1213 advantage of MinGW. It is also potentially faster than Cygwin because
|
|
|
1214 it has less overhead when calling Windows, but you lose the POSIX
|
|
|
1215 emulation layer, which makes Unix programs harder to port. (But this is
|
|
|
1216 irrelevant for XEmacs since it's already ported to Win32.)
|
|
|
1217
|
|
|
1218 See @uref{http://www.mingw.org/} for more information on MinGW.
|
|
|
1219
|
|
|
1220 @node Q1.2.6, Q1.2.7, Q1.2.5, Introduction
|
|
|
1221 @unnumberedsubsec Q1.2.6: What are the differences between the various MS Windows emacsen?
|
|
|
1222
|
|
|
1223 XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing.
|
|
|
1224 Could you briefly explain the differences between them?
|
|
|
1225
|
|
|
1226 Here is a recount of various Emacs versions running on MS Windows:
|
|
|
1227
|
|
|
1228 @itemize @bullet
|
|
|
1229
|
|
|
1230 @item
|
|
|
1231 XEmacs
|
|
|
1232
|
|
|
1233 @itemize @minus
|
|
|
1234
|
|
|
1235 @item
|
|
|
1236 Beginning with XEmacs 19.12, XEmacs' architecture was redesigned
|
|
|
1237 in such a way to allow clean support of multiple window systems. At
|
|
|
1238 this time the TTY support was added, making X and TTY the first two
|
|
|
1239 "window systems" supported by XEmacs. The 19.12 design is the basis for
|
|
|
1240 the current native MS Windows code.
|
|
|
1241
|
|
|
1242 @item
|
|
|
1243 Some time during 1997, David Hobley (soon joined by Marc Paquette)
|
|
|
1244 imported some of the NT-specific portions of GNU Emacs, making XEmacs
|
|
|
1245 with X support compile under Windows NT, and creating the "X" port.
|
|
|
1246
|
|
|
1247 @item
|
|
|
1248 Several months later, Jonathan Harris sent out initial patches to use
|
|
|
1249 the Win32 API, thus creating the native port. Since then, various
|
|
|
1250 people have contributed, including Kirill M. Katsnelson (contributed
|
|
|
1251 support for menubars, subprocesses and network, as well as loads of
|
|
|
1252 other code), Andy Piper (ported XEmacs to Cygwin environment,
|
|
|
1253 contributed Windows unexec, Windows-specific glyphs and toolbars code,
|
|
|
1254 and more), Ben Wing (loads of improvements; primary MS Windows developer
|
|
|
1255 since 2000), Jeff Sparkes (contributed scrollbars support) and many
|
|
|
1256 others.
|
|
|
1257 @end itemize
|
|
|
1258
|
|
|
1259 @item
|
|
|
1260 NT Emacs
|
|
|
1261
|
|
|
1262 @itemize @minus
|
|
|
1263
|
|
|
1264 @item
|
|
|
1265 NT Emacs was an early version of GNU Emacs 19 modified to compile and
|
|
|
1266 run under MS Windows 95 and NT using the native Win32 API. It was
|
|
|
1267 written by Geoff Voelker, and has long since been incorporated into
|
|
|
1268 the mainline GNU Emacs distribution.
|
|
|
1269 @end itemize
|
|
|
1270
|
|
|
1271 @item
|
|
|
1272 Win-Emacs
|
|
|
1273
|
|
|
1274 @itemize @minus
|
|
|
1275
|
|
|
1276 @item
|
|
|
1277 Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X
|
|
|
1278 compatibility libraries. Win-Emacs was written by Ben Wing. The MS
|
|
|
1279 Windows code never made it back to Lucid Emacs, and its creator (Pearl
|
|
|
1280 Software) has long since gone out of business.
|
|
|
1281 @end itemize
|
|
|
1282
|
|
|
1283 @item
|
|
|
1284 GNU Emacs for DOS
|
|
|
1285
|
|
|
1286 @itemize @minus
|
|
|
1287
|
|
|
1288 @item
|
|
|
1289 GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
|
|
|
1290 port of GCC). Such an Emacs is heavily underfeatured, because it does
|
|
|
1291 not support long file names, lacks proper subprocesses support, and
|
|
|
1292 is far too big compared with typical DOS editors.
|
|
|
1293 @end itemize
|
|
|
1294
|
|
|
1295 @item
|
|
|
1296 GNU Emacs compiled with Win32
|
|
|
1297
|
|
|
1298 @itemize @minus
|
|
|
1299
|
|
|
1300 @item
|
|
|
1301 Starting with GNU Emacs 19.30, it has been possible to compile GNU Emacs
|
|
|
1302 under MS Windows using the DJGPP compiler and X libraries. The result
|
|
|
1303 is very similar to GNU Emacs compiled under MS DOS, only it works
|
|
|
1304 somewhat better because it runs in 32-bit mode, makes use of all the
|
|
|
1305 system memory, supports long file names, etc.
|
|
|
1306 @end itemize
|
|
|
1307
|
|
|
1308 @end itemize
|
|
|
1309
|
|
|
1310 @node Q1.2.7, Q1.2.8, Q1.2.6, Introduction
|
|
|
1311 @unnumberedsubsec Q1.2.7: How does the port cope with differences in the Windows user interface?
|
|
|
1312
|
|
|
1313 The XEmacs (and Emacs in general) user interface is pretty different
|
|
|
1314 from what is expected of a typical MS Windows program. How does the MS
|
|
|
1315 Windows port cope with it?
|
|
|
1316
|
|
|
1317 As a general rule, we follow native MS Windows conventions as much as
|
|
|
1318 possible. 21.4 is a fairly complete Windows application, supporting
|
|
|
1319 native printing, system file dialog boxes, tool tips, etc. In cases
|
|
|
1320 where there's a clear UI conflict, we currently use normal Unix XEmacs
|
|
|
1321 behavior by default, but make sure the MS Windows "look and feel" (mark
|
|
|
1322 via shift-arrow, self-inserting deletes region, Alt selects menu items,
|
|
|
1323 etc.) is easily configurable (respectively: using the variable
|
|
|
1324 @code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact
|
|
|
1325 the default in these versions], or the @file{pc-select} package; using
|
|
|
1326 the @file{pending-del} package; and setting the variable
|
|
|
1327 @code{menu-accelerator-enabled} to @code{menu-force} in 21.4 and above).
|
|
|
1328 In fact, if you use the sample @file{init.el} file as your init file,
|
|
|
1329 you will get all these behaviors automatically turned on.
|
|
|
1330
|
|
|
1331 In future versions, some of these features might be turned on by
|
|
|
1332 default in the MS Windows environment.
|
|
|
1333
|
|
|
1334 @node Q1.2.8, Q1.2.9, Q1.2.7, Introduction
|
|
|
1335 @unnumberedsubsec Q1.2.8: Is there a port of XEmacs to the Macintosh?
|
|
|
1336
|
|
|
1337 Yes.
|
|
|
1338
|
|
|
1339 XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly
|
|
|
1340 will not feel very much like a Mac application as it has no Mac-specific
|
|
|
1341 code in it.
|
|
|
1342
|
|
|
1343 There is also a port of XEmacs 19.14 that works on all recent versions
|
|
|
1344 of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com,
|
|
|
1345 Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY
|
|
|
1346 mode only (one single Macintosh window, 25 colors), but has a large
|
|
|
1347 number of Mac-specific additions. It's available at
|
|
|
1348 @uref{http://homepage.mac.com/pjarvis/xemacs.html}.
|
|
|
1349
|
|
|
1350 @node Q1.2.9, Q1.2.10, Q1.2.8, Introduction
|
|
2559
|
1351 @unnumberedsubsec Q1.2.9: Is there a port of XEmacs to MS-DOS?
|
|
|
1352
|
|
|
1353 No. We have never supported running on MS-DOS or Windows 3.1, and in
|
|
|
1354 fact have long since deleted all MS-DOS-related code. We're not
|
|
|
1355 particularly interested in patches for these platforms, as they would
|
|
|
1356 introduce huge amounts of code clutter due to the woefully
|
|
|
1357 underfeatured nature of these systems. (See GNU Emacs for a port to
|
|
|
1358 MS-DOS.)
|
|
2537
|
1359
|
|
|
1360 @node Q1.2.10, Q1.2.11, Q1.2.9, Introduction
|
|
2559
|
1361 @unnumberedsubsec Q1.2.10: Is there a port of XEmacs to OS/2?
|
|
2537
|
1362
|
|
|
1363 No, but Alexander Nikolaev <avn_1251@@mail.ru> was at one point
|
|
|
1364 working on it.
|
|
|
1365
|
|
2559
|
1366 @node Q1.2.11, Q1.2.12, Q1.2.10, Introduction
|
|
|
1367 @unnumberedsubsec Q1.2.11: Is there a port of XEmacs to NextStep?
|
|
2537
|
1368
|
|
|
1369 Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did
|
|
|
1370 the port of GNU Emacs to NeXTstep and expressed interest in doing the
|
|
|
1371 XEmacs port, but never went any farther.
|
|
|
1372
|
|
2559
|
1373 @node Q1.2.12, Q1.3.1, Q1.2.11, Introduction
|
|
|
1374 @unnumberedsubsec Q1.2.12: Is there a port of XEmacs to VMS?
|
|
2537
|
1375
|
|
|
1376 VMS has never been supported by XEmacs. In fact, all the old VMS code
|
|
|
1377 inherited from GNU Emacs has been removed. Sorry, all you VMS fans
|
|
|
1378 out there.
|
|
|
1379
|
|
|
1380 @unnumberedsec 1.3: Getting Started
|
|
|
1381
|
|
2559
|
1382 @node Q1.3.1, Q1.3.2, Q1.2.12, Introduction
|
|
2537
|
1383 @unnumberedsubsec Q1.3.1: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
|
1384
|
|
|
1385 The @file{init.el} or @file{.emacs} file is used to customize XEmacs to
|
|
|
1386 your tastes. Starting in 21.4, the preferred location for the init file
|
|
|
1387 is @file{~/.xemacs/init.el}; in previous versions, it was
|
|
|
1388 @file{~/.emacs}. 21.4 still accepts the old location, but the first
|
|
|
1389 time you run it, it will ask to migrate your file to the new location.
|
|
|
1390 If you answer yes, the file will be moved, and a "compatibility"
|
|
|
1391 @file{.emacs} file will be placed in the old location so that you can
|
|
|
1392 still run older versions of XEmacs, and versions of GNU Emacs, which
|
|
|
1393 expect the old location. The @file{.emacs} file present is just a stub
|
|
|
1394 that loads the real file in @file{~/.xemacs/init.el}.
|
|
|
1395
|
|
|
1396 No two init files are alike, nor are they expected to be alike, but
|
|
|
1397 that's the point. The XEmacs distribution contains an excellent starter
|
|
|
1398 example in the @file{etc/} directory called @file{sample.init.el}
|
|
|
1399 (starting in 21.4) or @file{sample.emacs} in older versions. Copy this
|
|
|
1400 file from there to @file{~/.xemacs/init.el} (starting in 21.4) or
|
|
|
1401 @file{~/.emacs} in older versions, where @samp{~} means your home
|
|
|
1402 directory, of course. Then edit it to suit.
|
|
|
1403
|
|
|
1404 You may bring the @file{sample.init.el} or @file{sample.emacs} file into
|
|
|
1405 an XEmacs buffer from the menubar. (The menu entry for it is always
|
|
|
1406 under the @samp{Help} menu, but its location under that has changed in
|
|
|
1407 various versions. Recently, look under the @samp{Samples} submenu.) To
|
|
|
1408 determine the location of the @file{etc/} directory type the command
|
|
|
1409 @kbd{C-h v data-directory @key{RET}}.
|
|
|
1410
|
|
|
1411 @node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
|
|
|
1412 @unnumberedsubsec Q1.3.2: Where do I put my @file{init.el} file?
|
|
|
1413
|
|
|
1414 @file{init.el} is the name of the init file starting with 21.4, and is
|
|
|
1415 located in the subdirectory @file{.xemacs/} of your home directory. In
|
|
|
1416 prior versions, the init file is called @file{.emacs} and is located in
|
|
|
1417 your home directory.
|
|
|
1418
|
|
|
1419 Your home directory under Windows is determined by the @samp{HOME}
|
|
|
1420 environment variable. If this is not set, it defaults to @samp{C:\}.
|
|
|
1421 To set this variable, modify @file{AUTOEXEC.BAT} under Windows 95/98, or
|
|
|
1422 select @samp{Control Panel->System->Advanced->Environment Variables...}
|
|
|
1423 under Windows NT/2000.
|
|
|
1424
|
|
|
1425 @node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
|
|
|
1426 @unnumberedsubsec Q1.3.3: Can I use the same @file{init.el} with the other Emacs?
|
|
|
1427
|
|
|
1428 Yes. The sample @file{init.el} included in the XEmacs
|
|
|
1429 distribution will show you how to handle different versions and flavors
|
|
|
1430 of Emacs.
|
|
|
1431
|
|
|
1432 @node Q1.3.4, Q1.3.5, Q1.3.3, Introduction
|
|
|
1433 @unnumberedsubsec Q1.3.4: Any good XEmacs tutorials around?
|
|
|
1434
|
|
|
1435 There's the XEmacs tutorial available from the Help Menu under
|
|
|
1436 @samp{Help->Tutorials}, or by typing @kbd{C-h t}. To check whether
|
|
|
1437 it's available in a non-english language, type @kbd{C-u C-h t TAB}, type
|
|
|
1438 the first letters of your preferred language, then type @key{RET}.
|
|
|
1439
|
|
|
1440 @comment There's an Emacs Lisp tutorial at
|
|
|
1441 @comment
|
|
|
1442 @comment @example
|
|
|
1443 @comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
|
|
|
1444 @comment @end example
|
|
|
1445 @comment
|
|
|
1446 @comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
|
|
|
1447 @comment page at
|
|
|
1448 @comment @iftex
|
|
|
1449 @comment @*
|
|
|
1450 @comment @end iftex
|
|
|
1451 @comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}.
|
|
|
1452
|
|
|
1453 @node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
|
|
|
1454 @unnumberedsubsec Q1.3.5: May I see an example of a useful XEmacs Lisp function?
|
|
|
1455
|
|
|
1456 The following function does a little bit of everything useful. It does
|
|
|
1457 something with the prefix argument, it examines the text around the
|
|
|
1458 cursor, and it's interactive so it may be bound to a key. It inserts
|
|
|
1459 copies of the current word the cursor is sitting on at the cursor. If
|
|
|
1460 you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will
|
|
|
1461 insert 3 copies.
|
|
|
1462
|
|
|
1463 @lisp
|
|
|
1464 (defun double-word (count)
|
|
|
1465 "Insert a copy of the current word underneath the cursor"
|
|
|
1466 (interactive "*p")
|
|
|
1467 (let (here there string)
|
|
|
1468 (save-excursion
|
|
|
1469 (forward-word -1)
|
|
|
1470 (setq here (point))
|
|
|
1471 (forward-word 1)
|
|
|
1472 (setq there (point))
|
|
|
1473 (setq string (buffer-substring here there)))
|
|
|
1474 (while (>= count 1)
|
|
|
1475 (insert string)
|
|
|
1476 (decf count))))
|
|
|
1477 @end lisp
|
|
|
1478
|
|
|
1479 The best way to see what is going on here is to let XEmacs tell you.
|
|
|
1480 Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor
|
|
|
1481 sitting just to the right of the function you want explained. Eg. move
|
|
|
1482 the cursor to the SPACE between @code{interactive} and @samp{"*p"} and
|
|
|
1483 hit @kbd{C-h f} to see what the function @code{interactive} does. Doing
|
|
|
1484 this will tell you that the @code{*} requires a writable buffer, and
|
|
|
1485 @code{p} converts the prefix argument to a number, and
|
|
|
1486 @code{interactive} allows you to execute the command with @kbd{M-x}.
|
|
|
1487
|
|
|
1488 @node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
|
|
|
1489 @unnumberedsubsec Q1.3.6: And how do I bind it to a key?
|
|
|
1490
|
|
|
1491 To bind to a key do:
|
|
|
1492
|
|
|
1493 @lisp
|
|
|
1494 (global-set-key "\C-cd" 'double-word)
|
|
|
1495 @end lisp
|
|
|
1496
|
|
|
1497 Or interactively, @kbd{M-x global-set-key} and follow the prompts.
|
|
|
1498
|
|
|
1499 @node Q1.3.7, Q1.3.8, Q1.3.6, Introduction
|
|
|
1500 @unnumberedsubsec Q1.3.7: What's the difference between a macro and a function?
|
|
|
1501
|
|
|
1502 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual:
|
|
|
1503
|
|
|
1504 @dfn{Macros} enable you to define new control constructs and other
|
|
|
1505 language features. A macro is defined much like a function, but instead
|
|
|
1506 of telling how to compute a value, it tells how to compute another Lisp
|
|
|
1507 expression which will in turn compute the value. We call this
|
|
|
1508 expression the @dfn{expansion} of the macro.
|
|
|
1509
|
|
|
1510 Macros can do this because they operate on the unevaluated expressions
|
|
|
1511 for the arguments, not on the argument values as functions do. They can
|
|
|
1512 therefore construct an expansion containing these argument expressions
|
|
|
1513 or parts of them.
|
|
|
1514
|
|
|
1515 Do not confuse the two terms with @dfn{keyboard macros}, which are
|
|
|
1516 another matter, entirely. A keyboard macro is a key bound to several
|
|
|
1517 other keys. Refer to manual for details.
|
|
|
1518
|
|
|
1519 @node Q1.3.8, Q1.4.1, Q1.3.7, Introduction
|
|
|
1520 @unnumberedsubsec Q1.3.8: What is @code{Custom}?
|
|
|
1521
|
|
|
1522 @code{Custom} is a system for customizing XEmacs options.
|
|
|
1523
|
|
|
1524 You can access @code{Advanced (Customize)} from the @code{Options} menu
|
|
|
1525 or invoking one of customize commands by typing eg.
|
|
|
1526 @kbd{M-x customize}, @kbd{M-x customize-face},
|
|
|
1527 @kbd{M-x customize-variable} or @kbd{M-x customize-apropos}.
|
|
|
1528
|
|
|
1529 There is also new @samp{browser} mode for Customize.
|
|
|
1530 Try it out with @kbd{M-x customize-browse}
|
|
|
1531
|
|
|
1532 @unnumberedsec 1.4: Getting Help
|
|
|
1533
|
|
|
1534 @node Q1.4.1, Q1.4.2, Q1.3.8, Introduction
|
|
|
1535 @unnumberedsubsec Q1.4.1: Where can I get help?
|
|
|
1536
|
|
|
1537 Probably the easiest way, if everything is installed, is to use Info, by
|
|
|
1538 pressing @kbd{C-h i}, or looking for an Info item on the
|
|
|
1539 Help Menu. @kbd{M-x apropos} can be used to look for particular commands.
|
|
|
1540
|
|
|
1541 For items not found in the manual, try reading this FAQ
|
|
|
1542 and reading the Usenet group comp.emacs.xemacs.
|
|
|
1543
|
|
|
1544 If you choose to post to a newsgroup, @strong{please use
|
|
|
1545 comp.emacs.xemacs}. Please do not post XEmacs related questions to
|
|
|
1546 gnu.emacs.help.
|
|
|
1547
|
|
|
1548 If you cannot post or read Usenet news, there is a corresponding mailing
|
|
|
1549 list @email{xemacs-news@@xemacs.org} which is available. It can be
|
|
|
1550 subscribed to via the Mailman Web interface or by sending mail to to
|
|
|
1551 @email{xemacs-news-request@@xemacs.org} with @samp{subscribe} in the
|
|
|
1552 body of the message. See also
|
|
|
1553 @uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a
|
|
|
1554 subscription, you may use the @email{xemacs-news-request@@xemacs.org}
|
|
|
1555 address or the Web interface. Send a message with a subject of
|
|
|
1556 @samp{unsubscribe} to be removed.
|
|
|
1557
|
|
|
1558 @node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
|
|
|
1559 @unnumberedsubsec Q1.4.2: Which mailing lists are there?
|
|
|
1560
|
|
|
1561 For complete, up-to-date info on the lists and how to subscribe, see
|
|
|
1562 @uref{http://www.xemacs.org/Lists/}.
|
|
|
1563
|
|
|
1564 @table @samp
|
|
|
1565
|
|
|
1566 @item comp.emacs.xemacs
|
|
|
1567 is a Usenet newsgroup
|
|
|
1568 for XEmacs users to discuss problems and issues that arise
|
|
|
1569 for them. It's not generally an appropriate place to ask
|
|
|
1570 about apparent bugs (use @samp{xemacs-beta}), or future plans
|
|
|
1571 (use @samp{xemacs-design}).
|
|
|
1572
|
|
|
1573 @item xemacs-announce
|
|
|
1574 is a read-only, low
|
|
|
1575 volume list for announcements concerning the XEmacs project
|
|
|
1576 and new releases of the XEmacs software.
|
|
|
1577
|
|
|
1578 @item xemacs-beta
|
|
2559
|
1579 is an open list for bug reports about beta versions of XEmacs. This
|
|
|
1580 includes the bug reports themselves, by both users and developers, as
|
|
|
1581 well as queries, follow-ups, and discussions further determining their
|
|
|
1582 nature and status. This is the primary channel for this kind of
|
|
|
1583 discussion; related code changes will usually not be applied until
|
|
|
1584 they have been discussed here. When such discussions touch on
|
|
|
1585 significant changes to the code (in particular, structural changes),
|
|
|
1586 or on changes to API's or external functionality, they should be moved
|
|
|
1587 to @samp{xemacs-design}. Requests and proposals for non-bug-related
|
|
|
1588 changes do not belong on @samp{xemacs-beta}, and should be sent to
|
|
|
1589 @samp{xemacs-design} instead.
|
|
2537
|
1590
|
|
|
1591 @item xemacs-beta-ja
|
|
|
1592 is an open list for bug
|
|
|
1593 reports and design discussion related to Mule features,
|
|
|
1594 including Japanese handling, in beta versions of XEmacs.
|
|
|
1595 Japanese is the preferred language of discussion. For most
|
|
|
1596 timely presentation to reviewers, please consider sending
|
|
|
1597 appropriate discussion to @samp{xemacs-mule} or
|
|
|
1598 @samp{xemacs-design} in English when convenient for
|
|
|
1599 the participants in discussion. When possible, bug reports
|
|
|
1600 not related to Mule (including Japanese) should be reported on
|
|
|
1601 @samp{xemacs-beta} in English.
|
|
|
1602
|
|
|
1603 @item xemacs-buildreports
|
|
|
1604 is an open list for
|
|
|
1605 submission of build-reports on beta versions of XEmacs. For
|
|
|
1606 information on what the build-reports should contain, please
|
|
|
1607 see the `etc/BETA' file which is included in each beta
|
|
|
1608 distribution.
|
|
|
1609
|
|
|
1610 @item xemacs-cvs
|
|
|
1611 is a read-only list for notices
|
|
|
1612 and information on what has been committed to the XEmacs CVS
|
|
|
1613 trees, by whom, and for what.
|
|
|
1614
|
|
|
1615 @item xemacs-design
|
|
|
1616 is an open list for
|
|
|
1617 discussing the design of XEmacs. This includes discussion
|
|
|
1618 about planned and ongoing changes to functionality and API
|
|
|
1619 changes and additions as well as requests for them. This is
|
|
|
1620 the primary channel for this kind of discussion; related code
|
|
|
1621 changes will usually not be applied until they have been
|
|
|
1622 discussed here. This does not include bug reports, which go
|
|
|
1623 to @samp{xemacs-beta}.
|
|
|
1624
|
|
|
1625 @item xemacs-mule
|
|
|
1626 is an open mailing list for
|
|
|
1627 discussion of International extensions to XEmacs including
|
|
|
1628 Mule, XIM, I18n issues, etc, and is not confined to
|
|
|
1629 developmental issues. This list is not restricted to
|
|
|
1630 English, postings in all languages are welcome.
|
|
|
1631
|
|
|
1632 @item xemacs-news
|
|
|
1633 is an open list for discussion
|
|
|
1634 and bug reporting for XEmacs. This mailing list is
|
|
|
1635 bi-directionally gatewayed with the USENET newsgroup
|
|
|
1636 comp.emacs.xemacs.
|
|
|
1637
|
|
|
1638 @item xemacs-nt
|
|
|
1639 is a developers-only mailing
|
|
|
1640 list and is intended for people who wish to work actively on
|
|
|
1641 the porting of XEmacs to Microsoft Windows NT and Microsoft
|
|
|
1642 Windows '95.
|
|
|
1643
|
|
|
1644 @item xemacs-patches
|
|
|
1645 is an open, moderated
|
|
|
1646 list for submission of patches to the XEmacs distribution
|
|
|
1647 and its packages. Anyone may subscribe or submit to
|
|
|
1648 xemacs-patches, but all submissions are reviewed by the list
|
|
|
1649 moderator before they are distributed to the
|
|
|
1650 list. Discussion is not appropriate on xemacs-patches.
|
|
|
1651
|
|
|
1652 @item xemacs-users-ja
|
|
|
1653 is an open list for
|
|
|
1654 discussion and bug reporting for XEmacs. Japanese is the
|
|
|
1655 preferred language of discussion. It is not gated to
|
|
|
1656 comp.emacs.xemacs or the @samp{xemacs} list. For
|
|
|
1657 fastest response, bugs not specifically related to Japanese
|
|
|
1658 or Mule features should be reported on
|
|
|
1659 @samp{xemacs-beta} (in English).
|
|
|
1660
|
|
|
1661 @item xemacs-users-ru
|
|
|
1662 is an open list for
|
|
|
1663 discussion and bug reporting for XEmacs. Russian is the
|
|
|
1664 preferred language of discussion. It is not gated to
|
|
|
1665 comp.emacs.xemacs or the @samp{xemacs} list. For
|
|
|
1666 fastest response, bugs not specifically related to Russian
|
|
|
1667 or Mule features should be reported on
|
|
|
1668 @samp{xemacs-beta} (in English).
|
|
|
1669 @end table
|
|
|
1670
|
|
|
1671 @node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
|
|
|
1672 @unnumberedsubsec Q1.4.3: Where are the mailing lists archived?
|
|
|
1673
|
|
|
1674 The archives can be found at @uref{http://list-archive.xemacs.org}
|
|
|
1675
|
|
|
1676 @node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
|
|
|
1677 @unnumberedsubsec Q1.4.4: How can I get two instances of info?
|
|
|
1678
|
|
|
1679 Before 21.4, you can't. The @code{info} package does not provide for
|
|
|
1680 multiple info buffers. In 21.4, this should be fixed. #### how?
|
|
|
1681
|
|
|
1682 @node Q1.4.5, Q1.5.1, Q1.4.4, Introduction
|
|
|
1683 @unnumberedsubsec Q1.4.5: How do I add new Info directories?
|
|
|
1684
|
|
|
1685 You use something like:
|
|
|
1686
|
|
|
1687 @lisp
|
|
|
1688 (setq Info-directory-list (cons
|
|
|
1689 (expand-file-name "~/info")
|
|
|
1690 Info-default-directory-list))
|
|
|
1691 @end lisp
|
|
|
1692
|
|
|
1693 @email{davidm@@prism.kla.com, David Masterson} writes:
|
|
|
1694
|
|
|
1695 @quotation
|
|
|
1696 Emacs Info and XEmacs Info do many things differently. If you're trying to
|
|
|
1697 support a number of versions of Emacs, here are some notes to remember:
|
|
|
1698
|
|
|
1699 @enumerate
|
|
|
1700 @item
|
|
|
1701 Emacs Info scans @code{Info-directory-list} from right-to-left while
|
|
|
1702 XEmacs Info reads it from left-to-right, so append to the @emph{correct}
|
|
|
1703 end of the list.
|
|
|
1704
|
|
|
1705 @item
|
|
|
1706 Use @code{Info-default-directory-list} to initialize
|
|
|
1707 @code{Info-directory-list} @emph{if} it is available at startup, but not
|
|
|
1708 all Emacsen define it.
|
|
|
1709
|
|
|
1710 @item
|
|
|
1711 Emacs Info looks for a standard @file{dir} file in each of the
|
|
|
1712 directories scanned from #1 and magically concatenates them together.
|
|
|
1713
|
|
|
1714 @item
|
|
|
1715 XEmacs Info looks for a @file{localdir} file (which consists of just the
|
|
|
1716 menu entries from a @file{dir} file) in each of the directories scanned
|
|
|
1717 from #1 (except the first), does a simple concatenation of them, and
|
|
|
1718 magically attaches the resulting list to the end of the menu in the
|
|
|
1719 @file{dir} file in the first directory.
|
|
|
1720 @end enumerate
|
|
|
1721
|
|
|
1722 Another alternative is to convert the documentation to HTML with
|
|
|
1723 texi2html and read it from a web browser like Lynx or W3.
|
|
|
1724 @end quotation
|
|
|
1725
|
|
|
1726 @unnumberedsec 1.5: Contributing to XEmacs
|
|
|
1727
|
|
|
1728 @node Q1.5.1, Q1.5.2, Q1.4.5, Introduction
|
|
|
1729 @unnumberedsubsec Q1.5.1: How do I submit changes to the FAQ?
|
|
|
1730
|
|
|
1731 The FAQ is actively maintained and modified regularly. All links should
|
|
|
1732 be up to date. Unfortunately, some of the information is out of date --
|
|
|
1733 a situation which the FAQ maintainer is working on. All submissions are
|
|
|
1734 welcome, please e-mail submissions to @email{faq@@xemacs.org, XEmacs FAQ
|
|
|
1735 maintainers}.
|
|
|
1736
|
|
|
1737 Please make sure that @samp{XEmacs FAQ} appears on the Subject: line.
|
|
|
1738 If you think you have a better way of answering a question, or think a
|
|
|
1739 question should be included, we'd like to hear about it. Questions and
|
|
|
1740 answers included into the FAQ will be edited for spelling and grammar
|
|
|
1741 and will be attributed. Answers appearing without attribution are
|
|
|
1742 either from versions of the FAQ dated before May 1996 or are from
|
|
|
1743 previous FAQ maintainers. Answers quoted from Usenet news articles will
|
|
|
1744 always be attributed, regardless of the author.
|
|
|
1745
|
|
|
1746 @node Q1.5.2, Q1.5.3, Q1.5.1, Introduction
|
|
|
1747 @unnumberedsubsec Q1.5.2: How do I become a beta tester?
|
|
|
1748
|
|
|
1749 Send an email message to @email{xemacs-beta-request@@xemacs.org} with
|
|
|
1750 the line @samp{subscribe} in the body of the message.
|
|
|
1751
|
|
|
1752 Be prepared to get your hands dirty, as beta testers are expected to
|
|
|
1753 identify problems as best they can.
|
|
|
1754
|
|
2559
|
1755 @node Q1.5.3, Q1.5.4, Q1.5.2, Introduction
|
|
2537
|
1756 @unnumberedsubsec Q1.5.3: How do I contribute to XEmacs itself?
|
|
|
1757
|
|
|
1758 It depends on the knowledge and time you possess. If you are able, by
|
|
|
1759 all means become a beta tester (@pxref{Q1.5.2}). If you are a
|
|
|
1760 programmer, try to build XEmacs and see if you can improve it.
|
|
|
1761
|
|
|
1762 Otherwise, you can still help by using XEmacs as your everyday editor
|
|
|
1763 (for pre-built binary versions, @pxref{Q1.1.2}) and reporting bugs you
|
|
|
1764 find to the mailing list.
|
|
|
1765
|
|
|
1766 Another area where we need help is the documentation: We need good
|
|
|
1767 documentation for building XEmacs and for using it. This FAQ is a
|
|
|
1768 small step in that direction.
|
|
|
1769
|
|
|
1770 Ben Wing @email{ben@@xemacs.org} writes:
|
|
|
1771
|
|
|
1772 @quotation
|
|
|
1773 BTW if you have a wish list of things that you want added, you have to
|
|
|
1774 speak up about it! More specifically, you can do the following if you
|
|
|
1775 want a feature added (in increasing order of usefulness):
|
|
|
1776
|
|
|
1777 @itemize @bullet
|
|
|
1778 @item
|
|
|
1779 Make a posting about a feature you want added.
|
|
|
1780
|
|
|
1781 @item
|
|
|
1782 Become a beta tester and make more postings about those same features.
|
|
|
1783
|
|
|
1784 @item
|
|
|
1785 Convince us that you're going to use the features in some cool and
|
|
|
1786 useful way.
|
|
|
1787
|
|
|
1788 @item
|
|
|
1789 Come up with a clear and well-thought-out API concerning the features.
|
|
|
1790
|
|
|
1791 @item
|
|
|
1792 Write the code to implement a feature and send us a patch.
|
|
|
1793 @end itemize
|
|
|
1794
|
|
|
1795 (not that we're necessarily requiring you to write the code, but we can
|
|
|
1796 always hope :)
|
|
|
1797 @end quotation
|
|
|
1798
|
|
2559
|
1799 @node Q1.5.4, Q1.5.5, Q1.5.3, Introduction
|
|
|
1800 @unnumberedsubsec Q1.5.4: How do I get started developing XEmacs?
|
|
|
1801
|
|
|
1802 First, get yourself set up under CVS so that you can access the CVS
|
|
|
1803 repositories containing the XEmacs sources and the XEmacs packages.
|
|
|
1804
|
|
|
1805 Next, set up your layout. This is important, as a good layout will
|
|
|
1806 facilitate getting things done efficiently, while a bad layout will could
|
|
|
1807 lead to disaster, as you can't figure out which code is the most recent,
|
|
|
1808 which can be thrown away, etc. We suggest the following layout: (feel free
|
|
|
1809 to make changes)
|
|
|
1810
|
|
|
1811 @itemize @bullet
|
|
|
1812 @item
|
|
|
1813 Everything goes under @file{/src/xemacs} (use a different directory if
|
|
|
1814 you want). From now, instead of saying @file{/src/xemacs}, we use
|
|
|
1815 @file{<xsrc-top>}, to make it easier in case someone picked a
|
|
|
1816 different directory.
|
|
|
1817
|
|
|
1818 @item
|
|
|
1819 Package source is in @file{<xsrc-top>/package-src}.
|
|
|
1820
|
|
|
1821 @item
|
|
|
1822 Installed packages go under @file{<xsrc-top>/xemacs-packages}, and
|
|
|
1823 @file{<xsrc-top>/mule-packages}.
|
|
|
1824
|
|
|
1825 @item
|
|
|
1826 A "workspace" is a complete copy of the sources, in which you do work of
|
|
|
1827 a particular kind. Workspaces can be differentiated by which branch of
|
|
|
1828 the source tree they extend off of -- usually either the stable or
|
|
|
1829 experimental, unless other branches have been created (for example, Ben
|
|
|
1830 created a branch for his Mule work because (1) the project was long-term
|
|
|
1831 and involved an enormous number of changes, (2) people wanted to be able
|
|
|
1832 to look at what his work in progress, and (3) he wanted to be able to
|
|
|
1833 check things in and in general use source-code control, since it was a
|
|
|
1834 long-term project). Workspaces are also differentiated in what their
|
|
|
1835 purpose is -- general working workspace, workspace for particular
|
|
|
1836 projects, workspace keeping the latest copy of the code in one of the
|
|
|
1837 branches without mods, etc.
|
|
|
1838
|
|
|
1839 @item
|
|
|
1840 Various workspaces are subdirectories under @file{<xsrc-top>}, e.g.:
|
|
|
1841
|
|
|
1842 @itemize @bullet
|
|
|
1843 @item
|
|
|
1844 @file{<xsrc-top>/working} (the workspace you're actively working on,
|
|
|
1845 periodically synched up with the latest trunk)
|
|
|
1846
|
|
|
1847 @item
|
|
|
1848 @file{<xsrc-top>/stable} (for making changes to the stable version of
|
|
|
1849 XEmacs, which sits on a branch)
|
|
|
1850
|
|
|
1851 @item
|
|
|
1852 @file{<xsrc-top>/unsigned-removal} (a workspace for a specific, difficult
|
|
|
1853 task that's going to affect lots of source and take a long time, and
|
|
|
1854 so best done in its own workspace without the interference of other
|
|
|
1855 work you're doing. Also, you can commit just this one large change,
|
|
|
1856 separate from all the other changes).
|
|
|
1857
|
|
|
1858 @item
|
|
|
1859 @file{<xsrc-top>/latest} (a copy of the latest sources on the trunk,
|
|
|
1860 i.e. the experimental version of XEmacs, with no patches in it;
|
|
|
1861 either update it periodically, by hand, or set up a cron job to do it
|
|
|
1862 automatically). Set it up so it can be built, and build it so you
|
|
|
1863 have a working XEmacs. (Building it might also go into the cron job.)
|
|
|
1864
|
|
|
1865 This workspace serves a number of purposes:
|
|
|
1866 @enumerate
|
|
|
1867 @item
|
|
|
1868 You always have a recent version of XEmacs you can compare
|
|
|
1869 against when something you're working on breaks. It's true
|
|
|
1870 that you can do this with cvs diff, but when you need to do
|
|
|
1871 some serious investigation, this method just fails.
|
|
|
1872 @item
|
|
|
1873 You (almost) always have a working, up-to-date executable that
|
|
|
1874 can be used when your executable is crashing and you need to
|
|
|
1875 keep developing it, or when you need an `xemacs' to build
|
|
|
1876 packages, etc.
|
|
|
1877 @item
|
|
|
1878 When creating new workspaces, you can just copy the `latest'
|
|
|
1879 workspace using GNU @code{cp -a}. You have all the .elc's built,
|
|
|
1880 everything else probably configured, any spare files in place
|
|
|
1881 (e.g. some annoying xpm.dll under Windows, etc.).
|
|
|
1882 @end enumerate
|
|
|
1883
|
|
|
1884 @item
|
|
|
1885 @file{<xsrc-top>/latest-stable/} (equivalent to @file{<xsrc-top>/latest/}, but
|
|
|
1886 for the Stable branch of XEmacs, rather than the Experimental branch
|
|
|
1887 of XEmacs). This may or may not be necessary depending on how much
|
|
|
1888 development you do of the stable branch.
|
|
|
1889 @end itemize
|
|
|
1890
|
|
|
1891 @item
|
|
|
1892 @file{<xsrc-top>/xemacsweb} is a workspace for working on the XEmacs
|
|
|
1893 web site.
|
|
|
1894
|
|
|
1895 @item
|
|
|
1896 @file{<xsrc-top>/in-patches} for patches received from email and saved
|
|
|
1897 to files.
|
|
|
1898
|
|
|
1899 @item
|
|
|
1900 @file{<xsrc-top>/out-patches} for locally-generated patches to be sent
|
|
|
1901 to @email{xemacs-patches@@xemacs.org}. Less useful now that the
|
|
|
1902 patcher util has been developed.
|
|
|
1903
|
|
|
1904 @item
|
|
|
1905 @file{<xsrc-top>/build}, for build trees when compiling and testing XEmacs with
|
|
|
1906 various configuration options turned off and on. The scripts in
|
|
|
1907 xemacs-builds/ben (see below) can be used to automate building XEmacs
|
|
|
1908 workspaces with many different configuration options and automatically
|
|
|
1909 filtering out the normal output so that you see only the abnormal
|
|
|
1910 output.
|
|
|
1911
|
|
|
1912 @item
|
|
|
1913 @file{<xsrc-top>/xemacs-builds}, for the xemacs-builds module, which you need
|
|
|
1914 to check out separately in CVS. This contains scripts used for building
|
|
|
1915 XEmacs, automating and simplifying using CVS, etc. Under various
|
|
|
1916 people's directories are their own build and other scripts. The
|
|
|
1917 currently most-maintained scripts are under ben/, where there are easily
|
|
|
1918 configurable scripts that can be used to easily build any workspace
|
|
|
1919 (esp. if you've more or less followed the layout presented above)
|
|
|
1920 unattended, with one or more configuration states (there's a
|
|
|
1921 pre-determined list of the most useful, but it's easy to change). The
|
|
|
1922 output is filtered and split up in various ways so that you can identify
|
|
|
1923 which output came from where, and you can see the output either full or
|
|
|
1924 with all "normal" output except occasional status messages filtered so
|
|
|
1925 that you only see the abnormal ones.
|
|
|
1926 @end itemize
|
|
|
1927
|
|
|
1928 @node Q1.5.5, Q1.6.1, Q1.5.4, Introduction
|
|
|
1929 @unnumberedsubsec Q1.5.5: What's the basic layout of the code?
|
|
|
1930
|
|
|
1931 The file @file{configure} is a shell script to acclimate XEmacs to the
|
|
|
1932 oddities of your processor and operating system. It will create a
|
|
|
1933 file named @file{Makefile} (a script for the @file{make} program), which helps
|
|
|
1934 automate the process of building and installing emacs. See INSTALL
|
|
|
1935 for more detailed information.
|
|
|
1936
|
|
|
1937 The file @file{configure.in} is the input used by the autoconf program to
|
|
|
1938 construct the @file{configure} script. Since XEmacs has configuration
|
|
|
1939 requirements that autoconf can't meet, @file{configure.in} uses an unholy
|
|
|
1940 marriage of custom-baked configuration code and autoconf macros; it
|
|
|
1941 may be wise to avoid rebuilding @file{configure} from @file{configure.in} when
|
|
|
1942 possible.
|
|
|
1943
|
|
|
1944 The file @file{Makefile.in} is a template used by @file{configure} to create
|
|
|
1945 @file{Makefile}.
|
|
|
1946
|
|
|
1947 There are several subdirectories:
|
|
|
1948
|
|
|
1949 @enumerate
|
|
|
1950 @item
|
|
|
1951 @file{src} holds the C code for XEmacs (the XEmacs Lisp interpreter and its
|
|
|
1952 primitives, the redisplay code, and some basic editing functions).
|
|
|
1953 @item
|
|
|
1954 @file{lisp} holds the XEmacs Lisp code for XEmacs (most everything else).
|
|
|
1955 @item
|
|
|
1956 @file{lib-src} holds the source code for some utility programs for use by
|
|
|
1957 or with XEmacs, like movemail and etags.
|
|
|
1958 @item
|
|
|
1959 @file{etc} holds miscellaneous architecture-independent data files
|
|
|
1960 XEmacs uses, like the tutorial text. The contents of the @file{lisp},
|
|
|
1961 @file{info} and @file{man} subdirectories are architecture-independent too.
|
|
|
1962 @item
|
|
|
1963 @file{lwlib} holds the C code for the X toolkit objects used by XEmacs.
|
|
|
1964 @item
|
|
|
1965 @file{info} holds the Info documentation tree for XEmacs.
|
|
|
1966 @item
|
|
|
1967 @file{man} holds the source code for the XEmacs online documentation.
|
|
|
1968 @item
|
|
|
1969 @file{nt} holds files used compiling XEmacs under Microsoft Windows.
|
|
|
1970 @end enumerate
|
|
|
1971
|
|
2537
|
1972 @unnumberedsec 1.6: Politics (XEmacs vs. GNU Emacs)
|
|
|
1973
|
|
2559
|
1974 @node Q1.6.1, Q1.6.2, Q1.5.5, Introduction
|
|
2537
|
1975 @unnumberedsubsec Q1.6.1: What is GNU Emacs?
|
|
|
1976
|
|
|
1977 GNU Emacs and XEmacs are related open-source text editors. Both
|
|
|
1978 derive from GNU Emacs version 18; the split between the two happened
|
|
|
1979 in 1991 (for comparison, the oldest versions of GNU Emacs date from
|
|
|
1980 1984). For information on GNU Emacs, see
|
|
|
1981 @uref{http://www.gnu.org/software/emacs/emacs.html}.
|
|
|
1982
|
|
|
1983 @node Q1.6.2, Q1.6.3, Q1.6.1, Introduction
|
|
|
1984 @unnumberedsubsec Q1.6.2: How does XEmacs differ from GNU Emacs?
|
|
428
|
1985
|
|
|
1986 For a detailed description of the differences between GNU Emacs and
|
|
|
1987 XEmacs and a detailed history of XEmacs, check out the
|
|
|
1988 @example
|
|
430
|
1989 @uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file}
|
|
428
|
1990 @end example
|
|
|
1991
|
|
2417
|
1992 @table @strong
|
|
|
1993 @item User-Visible Editing Features
|
|
|
1994 XEmacs in general tries hard to conform to exist user-interface
|
|
|
1995 standards, and to work "out-of-the-box" without the need for obscure
|
|
|
1996 customization changes. GNU Emacs, particularly version 21, has gotten
|
|
|
1997 better about this (in many cases by copying the XEmacs behavior!), but
|
|
|
1998 still has some weirdnesses. For example, the standard method of
|
|
|
1999 selecting text using the Shift key works out-of-the-box in XEmacs.
|
|
|
2000
|
|
|
2001 XEmacs has a built-in toolbar. Four toolbars can actually be configured
|
|
|
2002 simultaneously: top, bottom, left, and right toolbars.
|
|
|
2003
|
|
|
2004 XEmacs has vertical and horizontal scrollbars. Unlike in GNU Emacs 19
|
|
|
2005 (which provides a primitive form of vertical scrollbar), these are true
|
|
|
2006 toolkit scrollbars. A look-alike Motif scrollbar is provided for those
|
|
|
2007 who don't have Motif. (Even for those who do, the look-alike may be
|
|
|
2008 preferable as it is faster.)
|
|
|
2009
|
|
|
2010 XEmacs has buffer tabs along the top of the frame (although the
|
|
|
2011 position can be changed) that make it very easy to switch buffers.
|
|
|
2012
|
|
|
2013 The menubar under XEmacs is better-designed, with more thought put into
|
|
|
2014 it.
|
|
|
2015
|
|
|
2016 XEmacs can ask questions using popup dialog boxes. Any command executed
|
|
|
2017 from a menu will ask yes/no questions with dialog boxes, while commands
|
|
|
2018 executed via the keyboard will use the minibuffer.
|
|
|
2019
|
|
|
2020 XEmacs under MS Windows provides uses the standard file-dialog box for
|
|
|
2021 opening and saving files. Standard menu-accelerator behavior can easily
|
|
|
2022 be enabled using the Options menu, and integrates well into the existing
|
|
|
2023 keymap.
|
|
|
2024
|
|
|
2025 XEmacs has (still experimental) support for widgets of various sorts --
|
|
|
2026 buttons, text boxes, sliders, progress bars, etc. A progress bar is
|
|
|
2027 used in font lock to show the progress.
|
|
|
2028
|
|
|
2029 Experimental support for drag-and-drop protocols is provided from
|
|
|
2030 XEmacs 21.
|
|
|
2031
|
|
|
2032 @item General Platform Support
|
|
|
2033 If you're running on a machine with audio hardware, you can specify
|
|
|
2034 sound files for XEmacs to play instead of the default X beep. See the
|
|
|
2035 documentation of the function load-sound-file and the variable
|
|
|
2036 sound-alist. XEmacs also supports the network sound protocols NAS and
|
|
|
2037 EsounD.
|
|
|
2038
|
|
|
2039 XEmacs 21 supports database protocols with LISP bindings, currently
|
|
|
2040 including Berkeley DB, LDAP, and PostgreSQL (21.2 only).
|
|
|
2041
|
|
|
2042 XEmacs 20 and 21 support the Canna, Wnn, and SJ3 Japanese input method
|
|
|
2043 servers directly, as well as through the X Input Method (XIM)
|
|
|
2044 protocol. GNU Emacs 20 supports only the XIM protocol. Both Emacsen
|
|
|
2045 support the Quail family of input methods (implemented in LISP) for many
|
|
|
2046 languages.
|
|
|
2047
|
|
|
2048 XEmacs provides support for ToolTalk on systems that have
|
|
|
2049 it.
|
|
|
2050
|
|
|
2051 @item Packaged LISP Libraries
|
|
|
2052 Many more packages are provided standard with XEmacs than with GNU Emacs
|
|
|
2053 19 or 20.
|
|
|
2054
|
|
|
2055 XEmacs 21 supports an integrated package management system which uses
|
|
|
2056 EFS to download, then automatically install prebuilt LISP
|
|
|
2057 libraries. This allows XEmacs users much more straightforward access to
|
|
|
2058 the "latest and greatest" version of any given library.
|
|
|
2059
|
|
|
2060 We are working on a standard method for enabling, disabling and
|
|
|
2061 otherwise controlling packages, which should make them very easy to use.
|
|
|
2062
|
|
|
2063 @item LISP Programming
|
|
|
2064 From XEmacs 20 on, characters are a separate type. Characters can be
|
|
|
2065 converted to integers (and many integers can be converted to
|
|
|
2066 characters), but characters are not integers. GNU Emacs 19, XEmacs 19,
|
|
|
2067 Mule 2.3 (an extensive patch to GNU Emacs 18.55 and 19.x), and GNU Emacs
|
|
|
2068 20 (incorporating Mule 3 and later Mule 4) represent them as integers.
|
|
|
2069
|
|
|
2070 From XEmacs 20 on, the buffer is treated as an array of characters, and
|
|
|
2071 the representation of buffer text is not exposed to LISP. The GNU Emacs
|
|
|
2072 20 functions like buffer-as-multibyte are not supported.
|
|
|
2073
|
|
|
2074 In XEmacs, events are first-class objects. GNU Emacs 19 represents them
|
|
|
2075 as integers, which obscures the differences between a key gesture and
|
|
|
2076 the ancient ASCII code used to represent a particular overlapping subset
|
|
|
2077 of them.
|
|
|
2078
|
|
|
2079 In XEmacs, keymaps are first-class opaque objects. GNU Emacs 19
|
|
|
2080 represents them as complicated combinations of association lists and
|
|
|
2081 vectors. If you use the advertised functional interface to manipulation
|
|
|
2082 of keymaps, the same code will work in XEmacs, GNU Emacs 18, and GNU
|
|
|
2083 Emacs 19; if your code depends on the underlying implementation of
|
|
|
2084 keymaps, it will not.
|
|
|
2085
|
|
|
2086 XEmacs uses "extents" to represent all non-textual aspects of buffers;
|
|
|
2087 GNU Emacs 19 uses two distinct objects, "text properties" and
|
|
|
2088 "overlays", which divide up the functionality between them. Extents are
|
|
|
2089 a superset of the union of the functionality of the two GNU Emacs data
|
|
|
2090 types. The full GNU Emacs 19 interface to text properties and overlays
|
|
|
2091 is supported in XEmacs (with extents being the underlying
|
|
|
2092 representation).
|
|
|
2093
|
|
|
2094 Extents can be made to be copied into strings, and then restored, by
|
|
|
2095 kill and yank. Thus, one can specify this behavior on either "extents"
|
|
|
2096 or "text properties", whereas in GNU Emacs 19 text properties always
|
|
|
2097 have this behavior and overlays never do.
|
|
|
2098
|
|
|
2099 @item Window System Programming Interface
|
|
|
2100 XEmacs uses the MIT "Xt" toolkit instead of raw Xlib calls, which makes
|
|
|
2101 it be a more well-behaved X citizen (and also improves portability). A
|
|
|
2102 result of this is that it is possible to include other Xt "Widgets" in
|
|
|
2103 the XEmacs window. Also, XEmacs understands the standard Xt command-line
|
|
|
2104 arguments.
|
|
|
2105
|
|
|
2106 XEmacs supports Motif applications, generic Xt (e.g. Athena)
|
|
|
2107 applications, and raw Xlib applications. An XEmacs variant which
|
|
|
2108 supports GTK+ is available (integration as an option in the XEmacs
|
|
|
2109 mainline is planned for XEmacs 22), although code to take advantage of
|
|
|
2110 the support is as yet scarce.
|
|
|
2111
|
|
|
2112 An XEmacs frame can be placed within an "external client widget" managed
|
|
|
2113 by another application. This allows an application to use an XEmacs
|
|
|
2114 frame as its text pane rather than the standard Text widget that is
|
|
|
2115 provided with Motif or Athena.
|
|
|
2116
|
|
|
2117 @item Community Participation
|
|
2459
|
2118 Joining the XEmacs development team is simple. Mail to
|
|
|
2119 @email{xemacs-beta@@xemacs.org, XEmacs Developers}, and you're in! (If
|
|
|
2120 you want to be, of course. You're also welcome to just post
|
|
|
2121 development-related questions and bug reports.) The GNU Emacs
|
|
2417
|
2122 development team and internal mailing lists are still by invitation
|
|
|
2123 only.
|
|
|
2124
|
|
|
2125 The "bleeding edge" of mainline XEmacs development is available by
|
|
|
2126 anonymous CVS as are some subsidiary branches (check out the xemacs-gtk
|
|
|
2127 module for the latest in GUI features!)
|
|
|
2128
|
|
|
2129 Development and maintenance of Lisp libraries is separated from the core
|
|
|
2130 editor development at a fairly low level. This provides better
|
|
|
2131 modularization and a better division of responsibility between external
|
|
|
2132 library maintainers and the XEmacs core development team. Even for
|
|
|
2133 packages the size of Gnus, XEmacs users normally have access to a
|
|
|
2134 pre-built version within a few weeks of a major release, and minor
|
|
|
2135 updates often within days.
|
|
|
2136
|
|
|
2137 CVS commit authority is broadly dispersed. Recognized maintainers of
|
|
|
2138 LISP libraries who are willing to maintain XEmacs packaged versions
|
|
|
2139 automatically qualify for CVS accounts for their packages.
|
|
|
2140 @end table
|
|
|
2141
|
|
2537
|
2142 @node Q1.6.3, Q1.6.4, Q1.6.2, Introduction
|
|
|
2143 @unnumberedsubsec Q1.6.3: How much does XEmacs differ?
|
|
2417
|
2144
|
|
|
2145 RMS has asserted at times that XEmacs is merely a "patch" on top of
|
|
2537
|
2146 GNU Emacs (@pxref{Q1.6.4}). In fact, probably not more than 5% of the
|
|
2417
|
2147 code, if that, remains unchanged, and nearly 14 years of work has gone
|
|
|
2148 into XEmacs at this point. (GNU Emacs itself is only than 20 years
|
|
|
2149 old, and thus XEmacs has existed as a separate product for over 2/3 of
|
|
|
2150 the lifespan of GNU Emacs.) As a point of comparison, XEmacs 21.5 has
|
|
|
2151 perhaps 65,000 more lines of C code than GNU Emacs 21.2.
|
|
|
2152
|
|
|
2153 However, the XEmacs developers strive to keep their code compatible with
|
|
|
2154 GNU Emacs, especially on the Lisp level. Much effort goes into
|
|
|
2155 "synching" the XEmacs Elisp code with recent GNU Emacs releases so as to
|
|
|
2156 benefit from GNU Emacs development work. (In contrast, almost no code
|
|
|
2157 from XEmacs has made it into GNU Emacs, and in fact the GNU Emacs
|
|
|
2158 developers are instructed by RMS not to even look at XEmacs source code!
|
|
|
2159 This stems from self-imposed licensing restrictions on the part of GNU
|
|
|
2160 Emacs -- and almost certainly out of hostility, as well.)
|
|
|
2161
|
|
2537
|
2162 @node Q1.6.4, Q1.6.5, Q1.6.3, Introduction
|
|
|
2163 @unnumberedsubsec Q1.6.4: Is XEmacs "GNU"?
|
|
2417
|
2164
|
|
|
2165 RMS insists on the term "GNU XEmacs" and maintains that
|
|
|
2166
|
|
|
2167 @quotation
|
|
|
2168 XEmacs is GNU software because it's a modified version of a
|
|
|
2169 GNU program. And it is GNU software because the FSF is the copyright
|
|
|
2170 holder for most of it, and therefore the legal responsibility for
|
|
|
2171 protecting its free status falls on us whether we want it or not. This
|
|
|
2172 is why the term "GNU XEmacs" is legitimate.
|
|
|
2173 @end quotation
|
|
|
2174
|
|
|
2175 In fact, FSF is @emph{not} the copyright holder for most of the code,
|
|
2537
|
2176 as very little unmodified FSF code remains (@pxref{Q1.6.3}).
|
|
2417
|
2177
|
|
|
2178 Furthermore, RMS's assertion that XEmacs is "GNU" seems rather bizarre
|
|
|
2179 to the XEmacs developers given RMS's hostility and general lack of
|
|
|
2180 interest in cooperation. "GNU" software in general is part of the GNU
|
|
|
2181 Project, is distributed by it on their FTP site, and receives support
|
|
|
2182 (or at least cooperation), as well as implicit endorsement, from it.
|
|
|
2183 The GNU Project, however, has never supported XEmacs and never
|
|
|
2184 distributed XEmacs, and RMS's hostility is the farthest thing possible
|
|
|
2185 from an endorsement. In fact, the GNU Project distributes a number of
|
|
|
2186 non-GNU software projects on the FSF web site, but again XEmacs is not
|
|
|
2187 one of them.
|
|
|
2188
|
|
2537
|
2189 @node Q1.6.5, Q1.6.6, Q1.6.4, Introduction
|
|
|
2190 @unnumberedsubsec Q1.6.5: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
2417
|
2191
|
|
|
2192 Unfortunately even the naming of these two applications has become
|
|
|
2193 politicized. Much of this stems from RMS, who has a history of
|
|
|
2194 politicizing similar issues. (Compare the controversy over "Lignux"
|
|
|
2195 and "GNU/Linux".) We would prefer that the terms "XEmacs" and "GNU
|
|
|
2196 Emacs" be used, which are neutral and acceptable to most people. RMS,
|
|
|
2197 however, is not willing to accept these terms. He insists that, if
|
|
|
2198 his product is called "GNU Emacs", then ours must be called "GNU
|
|
2537
|
2199 XEmacs". (For our opinion of this term, @xref{Q1.6.4}.) On the other
|
|
2417
|
2200 hand, if our product is to be called "XEmacs", as we prefer, then his
|
|
|
2201 product must simply be called "Emacs". The intent of this seems
|
|
|
2202 clear: RMS wants to make sure the names reflect his view that his
|
|
|
2203 version is the "real" Emacs and ours is merely a derivative,
|
|
2537
|
2204 second-class product (@pxref{Q1.6.3}).
|
|
2417
|
2205
|
|
|
2206 The XEmacs developers hope that you will use the neutral terms
|
|
|
2207 "XEmacs" and "GNU Emacs" for these two specific products. "Emacs", on
|
|
|
2208 the other hand, is a generic term for a class of programmable text
|
|
|
2209 editors with a similar look-and-feel, and usually a Lisp-based
|
|
|
2210 extension language. These trace themselves back to early editors such
|
|
|
2211 as EINE, ZWEI, ZMACS and Multics Emacs. @xref{A History of Emacs,,,
|
|
|
2212 internals, XEmacs Internals Manual}.
|
|
|
2213
|
|
|
2214 We also call upon RMS, in the spirit of furthering cooperation, to
|
|
|
2215 stop politicizing this issue and use the neutral terms "XEmacs" and
|
|
|
2216 "GNU Emacs". We have already acceded to RMS' wishes in this respect,
|
|
|
2217 and we expect him to do the same. (In the past, the XEmacs developers
|
|
|
2218 often used the terms "FSF Emacs" or "FSFmacs" or "RMSmacs" in
|
|
|
2219 reference to GNU Emacs; these terms were apparently modeled after RMS'
|
|
|
2220 own usage of "Gosmacs" and "Gosling Emacs" in reference to Unipress
|
|
|
2221 Emacs, produced by James Gosling. RMS, however, considers such terms
|
|
|
2222 to be insulting, so we refrain from using them as much as possible in
|
|
|
2223 preference to GNU Emacs.)
|
|
|
2224
|
|
2537
|
2225 @node Q1.6.6, Q1.7.1, Q1.6.5, Introduction
|
|
|
2226 @unnumberedsubsec Q1.6.6: Why haven't XEmacs and GNU Emacs merged?
|
|
2417
|
2227
|
|
|
2228 There are currently irreconcilable differences in the views about
|
|
|
2229 technical, programming, design, organizational and legal matters
|
|
|
2230 between Richard Stallman (RMS), the author and leader of the GNU Emacs
|
|
|
2231 project, and the XEmacs development team which provide little hope for
|
|
|
2232 a merge to take place in the short-term future. There have been
|
|
|
2233 repeated attempts at merging by all of the major XEmacs developers,
|
|
|
2234 starting from the early days of Lucid Emacs (in 1991), but they have
|
|
|
2235 all failed. RMS has very strong views about how GNU Emacs should be
|
|
|
2236 structured and how his project should be run, and during the repeated
|
|
|
2237 merge efforts has never demonstrated any realistic interest in
|
|
|
2238 sufficiently compromising or ceding control to allow a middle ground
|
|
|
2239 to be found. The basic problem seems to be the very different goals
|
|
|
2240 of RMS and the XEmacs project. The primary goals of the XEmacs
|
|
|
2241 project are technical and organizational -- we want to create the best
|
|
|
2242 editor possible, and to make it as easy as possible for people around
|
|
|
2243 the world to contribute. The primary goals of RMS, on the other hand,
|
|
|
2244 are political, and GNU Emacs, and any potential merge efforts with
|
|
|
2245 XEmacs, are strictly subservient to these goals. In fact, in many
|
|
|
2246 ways RMS sees GNU Emacs as the "poster child" of his aims, the one
|
|
|
2247 program in the GNU project that above all others must set an example
|
|
|
2248 to the world. (This has to do with the fact that GNU Emacs was the
|
|
|
2249 first program in the GNU project, and the only one that he is still
|
|
|
2250 personally involved with on a day-to-day basis.) Given his goals, his
|
|
|
2251 position is completely reasonable -- but unfortunately, makes any
|
|
|
2252 merge impossible.
|
|
|
2253
|
|
|
2254 From the XEmacs perspective, the most intractable issues appear to be
|
|
|
2255 legal and organizational, specifically:
|
|
428
|
2256
|
|
|
2257 @itemize @bullet
|
|
|
2258 @item
|
|
2417
|
2259 RMS requires "legal papers" to be signed for all contributions of code
|
|
|
2260 to GNU Emacs over 10 lines or so, transferring the copyright and all
|
|
|
2261 legal rights to the code to the Free Software Foundation. XEmacs does
|
|
|
2262 not and has never required this, since it has the practical effect of
|
|
|
2263 discouraging individual and in particular corporate contributions --
|
|
|
2264 corporations will almost never sign away their legal rights to code
|
|
|
2265 since it makes it impossible to reuse the code in any product that
|
|
|
2266 whose license is not compatible with the GNU General Public License.
|
|
|
2267 Since RMS has shown no inclination to compromise on this issue, a
|
|
|
2268 merge would require that most of the existing XEmacs code would need
|
|
|
2269 to be thrown away and rewritten -- something the XEmacs developers are
|
|
|
2270 understandably reluctant to do.
|
|
|
2271
|
|
|
2272 @item
|
|
|
2273 A repeated stumbling block in the merge talks has been the issue of
|
|
|
2274 organizational control over the resulting product. RMS has made it
|
|
|
2275 clear that he intends to have final say over design issues in a merged
|
|
|
2276 Emacs. Unfortunately, RMS and the XEmacs developers have repeatedly
|
|
|
2277 clashed over design decisions, and RMS' insistence on getting his way
|
|
|
2278 in such disagreements was the very reason for the split in the first
|
|
|
2279 place. This same issue has come up again and again in merge talks and
|
|
|
2280 we have never been able to come to a satisfactory resolution. To the
|
|
|
2281 extent that RMS is willing to compromise at all, it appears to be of a
|
|
|
2282 purely political rather than technical nature -- "If we support this
|
|
|
2283 feature of yours, we also get to support this other feature of mine."
|
|
|
2284 The XEmacs developers cannot see how such a process would lead to
|
|
|
2285 anything but a mess of incompatible things hodgepodged together.
|
|
|
2286
|
|
|
2287 @item
|
|
|
2288 Because of the years of separate development, distinct and
|
|
|
2289 incompatible interfaces have developed and merging would be extremely
|
|
|
2290 difficult even with the above non-technical issues resolved. The
|
|
|
2291 problem has been exacerbated by the issue of legal papers -- because
|
|
|
2292 XEmacs code is not "kosher" from RMS' perspective, he discourages
|
|
|
2293 developers from even looking at it out of legal concerns. Although it
|
|
|
2294 is still possible to read the XEmacs documentation and run the
|
|
|
2295 program, the practical effect of this prohibition has been to strongly
|
|
|
2296 discourage code-sharing and cooperative development -- although a
|
|
|
2297 great deal of GNU Emacs code has been incorporated into XEmacs,
|
|
|
2298 practically none has gone the other direction.
|
|
428
|
2299 @end itemize
|
|
|
2300
|
|
|
2301 If you have a comment to add regarding the merge, it is a good idea to
|
|
2417
|
2302 avoid posting to the newsgroups, because of the very heated flamewars
|
|
|
2303 that often result. Mail your questions to
|
|
|
2304 @email{xemacs-beta@@xemacs.org} and @email{emacs-devel@@gnu.org}.
|
|
|
2305
|
|
2537
|
2306 @unnumberedsec 1.7: External Packages
|
|
|
2307
|
|
2559
|
2308 @node Q1.7.1, Q1.7.2, Q1.6.6, Introduction
|
|
|
2309 @unnumberedsubsec Q1.7.1: What is the package system?
|
|
|
2310
|
|
|
2311 In order to reduce the size and increase the maintainability of
|
|
|
2312 XEmacs, the majority of the Elisp packages that came with previous
|
|
|
2313 releases have been unbundled. They have been replaced by the package
|
|
|
2314 system. Each elisp add-on (or groups of them when they are small) now
|
|
|
2315 comes in its own tarball that contains a small search hierarchy.
|
|
|
2316
|
|
|
2317 You select just the ones you need. Install them by untarring them into
|
|
|
2318 the right place. On startup XEmacs will find them, set up the load
|
|
|
2319 path correctly, install autoloads, etc, etc.
|
|
|
2320
|
|
|
2321 @xref{Q2.1.1}, for more info on how to download and install the packages.
|
|
|
2322
|
|
|
2323 @node Q1.7.2, Q1.7.3, Q1.7.1, Introduction
|
|
|
2324 @unnumberedsubsec Q1.7.2: Which external packages are there?
|
|
2537
|
2325
|
|
|
2326 @subheading Normal Packages
|
|
|
2327
|
|
|
2328 A very broad collection of elisp packages.
|
|
2417
|
2329
|
|
|
2330 @table @asis
|
|
2537
|
2331 @item Sun
|
|
|
2332 Support for Sparcworks.
|
|
|
2333
|
|
|
2334 @item ada
|
|
|
2335 Ada language support.
|
|
|
2336
|
|
|
2337 @item apel
|
|
|
2338 A Portable Emacs Library. Used by XEmacs MIME support.
|
|
|
2339
|
|
|
2340 @item auctex
|
|
|
2341 Basic TeX/LaTeX support.
|
|
|
2342
|
|
|
2343 @item bbdb
|
|
|
2344 The Big Brother Data Base: a rolodex-like database program.
|
|
|
2345
|
|
|
2346 @item build
|
|
|
2347 Build XEmacs from within (UNIX, Windows).
|
|
|
2348
|
|
|
2349 @item c-support
|
|
|
2350 Basic single-file add-ons for editing C code.
|
|
|
2351
|
|
|
2352 @item calc
|
|
|
2353 Emacs calculator.
|
|
|
2354
|
|
|
2355 @item calendar
|
|
|
2356 Calendar and diary support.
|
|
|
2357
|
|
|
2358 @item cc-mode
|
|
|
2359 C, C++, Objective-C, Java, CORBA IDL, Pike and AWK language support.
|
|
|
2360
|
|
|
2361 @item clearcase
|
|
|
2362 New Clearcase Version Control for XEmacs (UNIX, Windows).
|
|
|
2363
|
|
|
2364 @item clearcase
|
|
|
2365 Support for the Clearcase version control system.
|
|
|
2366
|
|
|
2367 @item cookie
|
|
|
2368 "Fortune cookie"-style messages. Includes Spook (suspicious phrases)
|
|
|
2369 and Yow (Zippy quotes).
|
|
|
2370
|
|
|
2371 @item crisp
|
|
|
2372 Crisp/Brief emulation.
|
|
|
2373
|
|
|
2374 @item debug
|
|
|
2375 GUD, gdb, dbx debugging support.
|
|
|
2376
|
|
|
2377 @item dictionary
|
|
|
2378 Interface to RFC2229 dictionary servers.
|
|
|
2379
|
|
|
2380 @item dired
|
|
|
2381 The DIRectory EDitor is for manipulating, and running commands on
|
|
|
2382 files in a directory.
|
|
|
2383
|
|
|
2384 @item docbookide
|
|
|
2385 DocBook editing support.
|
|
|
2386
|
|
|
2387 @item ecb
|
|
|
2388 Emacs source code browser.
|
|
|
2389
|
|
|
2390 @item ecrypto
|
|
|
2391 Crypto functionality in Emacs Lisp.
|
|
|
2392
|
|
|
2393 @item edebug
|
|
|
2394 An Emacs Lisp debugger.
|
|
|
2395
|
|
|
2396 @item ediff
|
|
|
2397 Interface over GNU patch.
|
|
|
2398
|
|
|
2399 @item edit-utils
|
|
|
2400 Miscellaneous editor extensions, you probably need this.
|
|
|
2401
|
|
|
2402 @item edt
|
|
|
2403 DEC EDIT/EDT emulation.
|
|
|
2404
|
|
|
2405 @item efs
|
|
|
2406 Treat files on remote systems the same as local files.
|
|
|
2407
|
|
|
2408 @item eieio
|
|
|
2409 Enhanced Implementation of Emacs Interpreted Objects.
|
|
|
2410
|
|
|
2411 @item elib
|
|
|
2412 Portable Emacs Lisp utilities library.
|
|
|
2413
|
|
|
2414 @item emerge
|
|
|
2415 Another interface over GNU patch.
|
|
|
2416
|
|
|
2417 @item erc
|
|
|
2418 ERC is an Emacs InternetRelayChat client.
|
|
|
2419
|
|
|
2420 @item escreen
|
|
|
2421 Multiple editing sessions withing a single frame (like screen).
|
|
|
2422
|
|
|
2423 @item eshell
|
|
|
2424 Command shell implemented entirely in Emacs Lisp.
|
|
|
2425
|
|
|
2426 @item ess
|
|
|
2427 ESS: Emacs Speaks Statistics.
|
|
|
2428
|
|
|
2429 @item eterm
|
|
|
2430 Terminal emulation.
|
|
|
2431
|
|
|
2432 @item eudc
|
|
|
2433 Emacs Unified Directory Client (LDAP, PH).
|
|
|
2434
|
|
|
2435 @item footnote
|
|
|
2436 Footnoting in mail message editing modes.
|
|
|
2437
|
|
|
2438 @item forms
|
|
|
2439 Forms editing support (obsolete, use Widget instead).
|
|
|
2440
|
|
|
2441 @item fortran-modes
|
|
|
2442 Fortran support.
|
|
|
2443
|
|
|
2444 @item fortran-modes
|
|
|
2445 Fortran language support.
|
|
|
2446
|
|
|
2447 @item frame-icon
|
|
|
2448 Set up mode-specific icons for each frame under XEmacs.
|
|
|
2449
|
|
|
2450 @item fsf-compat
|
|
|
2451 GNU Emacs compatibility files.
|
|
|
2452
|
|
|
2453 @item games
|
|
|
2454 Tetris, Sokoban, and Snake.
|
|
|
2455
|
|
|
2456 @item general-docs
|
|
|
2457 General documentation. Presently, empty.
|
|
|
2458
|
|
|
2459 @item gnats
|
|
|
2460 XEmacs bug reports.
|
|
|
2461
|
|
|
2462 @item gnus
|
|
|
2463 The Gnus Newsreader and Mailreader.
|
|
|
2464
|
|
|
2465 @item haskell-mode
|
|
|
2466 Haskell editing support.
|
|
|
2467
|
|
|
2468 @item hm--html-menus
|
|
|
2469 HTML editing.
|
|
|
2470
|
|
|
2471 @item hyperbole
|
|
|
2472 Hyperbole: The Everyday Info Manager.
|
|
|
2473
|
|
|
2474 @item ibuffer
|
|
|
2475 Advanced replacement for buffer-menu.
|
|
|
2476
|
|
|
2477 @item idlwave
|
|
|
2478 Editing and Shell mode for the Interactive Data Language.
|
|
|
2479
|
|
|
2480 @item igrep
|
|
|
2481 Enhanced front-end for Grep.
|
|
|
2482
|
|
|
2483 @item ilisp
|
|
|
2484 Front-end for interacting with Inferior Lisp (external lisps).
|
|
|
2485
|
|
|
2486 @item ispell
|
|
|
2487 Spell-checking with GNU ispell.
|
|
|
2488
|
|
|
2489 @item jde
|
|
|
2490 Integrated Development Environment for Java.
|
|
|
2491
|
|
|
2492 @item liece
|
|
|
2493 IRC (Internet Relay Chat) client for Emacs. Note, this package is
|
|
|
2494 deprecated and will be removed, use riece instead.
|
|
|
2495
|
|
|
2496 @item mail-lib
|
|
|
2497 Fundamental lisp files for providing email support.
|
|
|
2498
|
|
|
2499 @item mailcrypt
|
|
|
2500 Support for messaging encryption with PGP.
|
|
|
2501
|
|
|
2502 @item mew
|
|
|
2503 Messaging in an Emacs World; a MIME-based email program.
|
|
|
2504
|
|
|
2505 @item mh-e
|
|
|
2506 The XEmacs Interface to the MH Mail System.
|
|
|
2507
|
|
|
2508 @item mine
|
|
|
2509 Elisp implementation of the game 'Minehunt'.
|
|
|
2510
|
|
|
2511 @item misc-games
|
|
|
2512 Other amusements and diversions.
|
|
|
2513
|
|
|
2514 @item mmm-mode
|
|
|
2515 Support for Multiple Major Modes within a single buffer.
|
|
|
2516
|
|
|
2517 @item net-utils
|
|
|
2518 Miscellaneous Networking Utilities.
|
|
|
2519
|
|
|
2520 @item ocaml
|
|
|
2521 Objective Caml editing support.
|
|
|
2522
|
|
|
2523 @item oo-browser
|
|
|
2524 OO-Browser: The Multi-Language Object-Oriented Code Browser.
|
|
|
2525
|
|
|
2526 @item ocaml
|
|
|
2527 Objective Caml editing support.
|
|
|
2528
|
|
|
2529 @item os-utils
|
|
|
2530 Miscellaneous single-file O/S utilities, for printing, archiving,
|
|
|
2531 compression, remote shells, etc.
|
|
|
2532
|
|
|
2533 @item pc
|
|
|
2534 PC style interface emulation.
|
|
|
2535
|
|
|
2536 @item pcl-cvs
|
|
|
2537 CVS frontend.
|
|
|
2538
|
|
|
2539 @item pcomplete
|
|
|
2540 Provides programmatic completion.
|
|
|
2541
|
|
|
2542 @item perl-modes
|
|
|
2543 Perl support.
|
|
|
2544
|
|
|
2545 @item pgg
|
|
|
2546 Emacs interface to various PGP implementations.
|
|
|
2547
|
|
|
2548 @item prog-modes
|
|
|
2549 Support for various programming languages.
|
|
|
2550
|
|
|
2551 @item ps-print
|
|
|
2552 Printing functions and utilities.
|
|
|
2553
|
|
|
2554 @item psgml
|
|
|
2555 Validated HTML/SGML editing.
|
|
|
2556
|
|
|
2557 @item psgml-dtds
|
|
|
2558 A collection of DTDs for psgml. Note that this package is deprecated
|
|
|
2559 and will be removed in the future, most likely Q2/2003. Instead of using
|
|
|
2560 this, you should install needed DTDs yourself.
|
|
|
2561
|
|
|
2562 @item python-modes
|
|
|
2563 Python language support.
|
|
|
2564
|
|
|
2565 @item reftex
|
|
|
2566 Emacs support for LaTeX cross-references, citations.
|
|
|
2567
|
|
|
2568 @item riece
|
|
|
2569 IRC (Internet Relay Chat) client for Emacs.
|
|
|
2570
|
|
|
2571 @item rmail
|
|
|
2572 An obsolete Emacs mailer. If you do not already use it don't start.
|
|
|
2573
|
|
|
2574 @item ruby-modes
|
|
|
2575 Ruby support.
|
|
|
2576
|
|
|
2577 @item sasl
|
|
|
2578 Simple Authentication and Security Layer (SASL) library.
|
|
|
2579
|
|
|
2580 @item scheme
|
|
|
2581 Front-end support for Inferior Scheme.
|
|
|
2582
|
|
|
2583 @item semantic
|
|
|
2584 Semantic bovinator (Yacc/Lex for XEmacs). Includes Senator.
|
|
|
2585
|
|
|
2586 @item sgml
|
|
|
2587 SGML/Linuxdoc-SGML editing.
|
|
|
2588
|
|
|
2589 @item sh-script
|
|
|
2590 Support for editing shell scripts.
|
|
|
2591
|
|
|
2592 @item sieve
|
|
|
2593 Manage Sieve email filtering scripts.
|
|
|
2594
|
|
|
2595 @item slider
|
|
|
2596 User interface tool.
|
|
|
2597
|
|
|
2598 @item sml-mode
|
|
|
2599 SML editing support.
|
|
|
2600
|
|
|
2601 @item sounds-au
|
|
|
2602 XEmacs Sun sound files.
|
|
|
2603
|
|
|
2604 @item sounds-wav
|
|
|
2605 XEmacs Microsoft sound files.
|
|
|
2606
|
|
|
2607 @item speedbar
|
|
|
2608 Provides a separate frame with convenient references.
|
|
|
2609
|
|
|
2610 @item strokes
|
|
|
2611 Mouse enhancement utility.
|
|
|
2612
|
|
|
2613 @item supercite
|
|
|
2614 An Emacs citation tool for News & Mail messages.
|
|
|
2615
|
|
|
2616 @item texinfo
|
|
|
2617 XEmacs TeXinfo support.
|
|
|
2618
|
|
|
2619 @item text-modes
|
|
|
2620 Miscellaneous support for editing text files.
|
|
|
2621
|
|
|
2622 @item textools
|
|
|
2623 Miscellaneous TeX support.
|
|
|
2624
|
|
|
2625 @item time
|
|
|
2626 Display time & date on the modeline.
|
|
|
2627
|
|
|
2628 @item tm
|
|
|
2629 Emacs MIME support. Not needed for gnus >= 5.8.0.
|
|
|
2630
|
|
|
2631 @item tooltalk
|
|
|
2632 Support for building with Tooltalk.
|
|
|
2633
|
|
|
2634 @item tpu
|
|
|
2635 DEC EDIT/TPU support.
|
|
|
2636
|
|
|
2637 @item tramp
|
|
|
2638 Remote shell-based file editing. This is similar to EFS or Ange-FTP,
|
|
|
2639 but works with rsh/ssh and rcp/scp.
|
|
|
2640
|
|
|
2641 @item vc
|
|
|
2642 Version Control for Free systems.
|
|
|
2643
|
|
|
2644 @item vc-cc
|
|
|
2645 Version Control for ClearCase (UnFree) systems.
|
|
|
2646
|
|
|
2647 @item vhdl
|
|
|
2648 Support for VHDL.
|
|
|
2649
|
|
|
2650 @item view-process
|
|
|
2651 A Unix process browsing tool.
|
|
|
2652
|
|
|
2653 @item viper
|
|
|
2654 VI emulation support.
|
|
|
2655
|
|
|
2656 @item vm
|
|
|
2657 An Emacs mailer.
|
|
|
2658
|
|
|
2659 @item w3
|
|
|
2660 A Web browser.
|
|
|
2661
|
|
|
2662 @item x-symbol
|
|
|
2663 Semi WYSIWYG for LaTeX, HTML, etc, using additional fonts.
|
|
|
2664
|
|
|
2665 @item xemacs-base
|
|
|
2666 Fundamental XEmacs support, you almost certainly need this.
|
|
|
2667
|
|
|
2668 @item xemacs-devel
|
|
|
2669 XEmacs Lisp developer support. This package contains utilities for
|
|
|
2670 supporting Lisp development. It is a single-file package so it may be
|
|
|
2671 tailored.
|
|
|
2672
|
|
|
2673 @item xlib
|
|
|
2674 Emacs interface to X server.
|
|
|
2675
|
|
|
2676 @item xslide
|
|
|
2677 XSL editing support.
|
|
|
2678
|
|
|
2679 @item xslt-process
|
|
|
2680 A minor mode for (X)Emacs which allows running an XSLT processor on a
|
|
|
2681 buffer.
|
|
|
2682
|
|
|
2683 @item xwem
|
|
|
2684 X Emacs Window Manager.
|
|
|
2685
|
|
|
2686 @item zenirc
|
|
|
2687 ZENIRC IRC Client.
|
|
2417
|
2688 @end table
|
|
|
2689
|
|
2537
|
2690 @subheading Mule Support (mule)
|
|
|
2691
|
|
|
2692 MULti-lingual Enhancement. Support for world scripts such as
|
|
|
2693 Latin, Arabic, Cyrillic, Chinese, Japanese, Greek, Hebrew etc.
|
|
|
2694 To use these packages your XEmacs must be compiled with Mule
|
|
|
2695 support.
|
|
|
2696
|
|
|
2697 @table @asis
|
|
|
2698 @item edict
|
|
|
2699 MULE: Lisp Interface to EDICT, Kanji Dictionary.
|
|
|
2700
|
|
|
2701 @item egg-its
|
|
|
2702 MULE: Wnn (4.2 and 6) support. SJ3 support.
|
|
|
2703
|
|
|
2704 @item latin-unity
|
|
|
2705 MULE: find single ISO 8859 character set to encode a buffer.
|
|
|
2706
|
|
|
2707 @item latin-unity
|
|
|
2708 Unify character sets in a buffer. When characters belong to disjoint
|
|
|
2709 character sets, this attempts to translate the characters so
|
|
|
2710 that they belong to one character set. If the buffer coding system is
|
|
|
2711 not sufficient, this suggests different coding systems.
|
|
|
2712
|
|
|
2713 @item leim
|
|
|
2714 MULE: Quail. All non-English and non-Japanese language support.
|
|
|
2715
|
|
|
2716 @item locale
|
|
|
2717 MULE: Localized menubars and localized splash screens.
|
|
|
2718
|
|
|
2719 @item lookup
|
|
|
2720 Dictionary support. (This isn't an English dictionary program)
|
|
|
2721
|
|
|
2722 @item mule-base
|
|
|
2723 MULE: Basic Mule support, required for building with Mule.
|
|
|
2724
|
|
|
2725 @item mule-ucs
|
|
|
2726 MULE: Extended coding systems (including Unicode) for XEmacs.
|
|
|
2727
|
|
|
2728 @item mule-ucs
|
|
|
2729 Extended coding systems (including Unicode) for XEmacs.
|
|
|
2730
|
|
|
2731 @item skk
|
|
|
2732 Another Japanese Language Input Method. Can be used without a
|
|
|
2733 separate process running as a dictionary server.
|
|
|
2734 @end table
|
|
|
2735
|
|
2559
|
2736 @node Q1.7.3, Q1.7.4, Q1.7.2, Introduction
|
|
|
2737 @unnumberedsubsec Q1.7.3: Do I need to have the packages to run XEmacs?
|
|
|
2738
|
|
|
2739 Strictly speaking, no. XEmacs will build and install just fine without
|
|
|
2740 any packages installed. However, only the most basic editing functions
|
|
|
2741 will be available with no packages installed, so installing packages is
|
|
|
2742 an essential part of making your installed XEmacs _useful_.
|
|
|
2743
|
|
|
2744 @node Q1.7.4, Q1.8.1, Q1.7.3, Introduction
|
|
|
2745 @unnumberedsubsec Q1.7.4: Is there a way to find which package has particular functionality?
|
|
|
2746
|
|
|
2747 If you want to find out which package contains the functionality you
|
|
|
2748 are looking for, use @kbd{M-x package-get-package-provider}, and give it a
|
|
|
2749 symbol that is likely to be in that package.
|
|
|
2750
|
|
|
2751 For example, if some code you want to use has a @code{(require 'thingatpt)}
|
|
|
2752 in it:
|
|
|
2753
|
|
|
2754 @example
|
|
|
2755 M-x package-get-package-provider RET thingatpt RET
|
|
|
2756 @end example
|
|
|
2757
|
|
|
2758 which will return something like: @samp{(fsf-compat "1.08").}
|
|
|
2759
|
|
2537
|
2760 @unnumberedsec 1.8: Internationalization
|
|
|
2761
|
|
2559
|
2762 @node Q1.8.1, Q1.8.2, Q1.7.4, Introduction
|
|
2537
|
2763 @unnumberedsubsec Q1.8.1: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
442
|
2764
|
|
|
2765 Both the stable and development versions of XEmacs include
|
|
1135
|
2766 internationalization support (aka MULE). MULE currently (21.4) works on
|
|
|
2767 UNIX and Linux systems. It is possible to build with MULE on Windows
|
|
|
2768 systems, but if you really need MULE on Windows, it is recommended that
|
|
|
2769 you build and use the development (21.5) version, and deal with the
|
|
|
2770 instability of the development tree. Binaries compiled without MULE
|
|
|
2771 support run faster than MULE capable XEmacsen.
|
|
428
|
2772
|
|
2537
|
2773 @node Q1.8.2, Q1.8.3, Q1.8.1, Introduction
|
|
|
2774 @unnumberedsubsec Q1.8.2: How can I help with internationalization?
|
|
430
|
2775
|
|
|
2776 If you would like to help, you may want to join the
|
|
|
2777 @email{xemacs-mule@@xemacs.org} mailing list. Especially needed are
|
|
|
2778 people who speak/write languages other than English, who are willing to
|
|
|
2779 use XEmacs/MULE regularly, and have some experience with Elisp.
|
|
428
|
2780
|
|
1135
|
2781 Translations of the TUTORIAL and man page are welcome, and XEmacs does
|
|
|
2782 support multilingual menus, but we have few current translations.
|
|
|
2783
|
|
2537
|
2784 @xref{Q1.5.2, How do I become a Beta Tester?}.
|
|
|
2785
|
|
|
2786 @node Q1.8.3, Q1.8.4, Q1.8.2, Introduction
|
|
|
2787 @unnumberedsubsec Q1.8.3: How do I type non-ASCII characters?
|
|
2417
|
2788
|
|
2459
|
2789 @xref{Q3.0.6, How can you type in special characters in XEmacs?}, in
|
|
2417
|
2790 part 3 of this FAQ, for some simple methods that also work in non-MULE
|
|
|
2791 builds of XEmacs (but only for one-octet coded character sets, and
|
|
|
2792 mostly for ISO 8859/1). Many of the methods available for Cyrillic
|
|
2537
|
2793 (@pxref{Q1.8.7, How about Cyrillic modes?}) work without MULE. MULE
|
|
|
2794 has more general capabilities. @xref{Q1.8.5, Please explain the
|
|
2417
|
2795 various input methods in MULE/XEmacs}.
|
|
|
2796
|
|
2459
|
2797 @xref{Q4.0.8, How do I display non-ASCII characters?}, which covers
|
|
2417
|
2798 display of non-ASCII characters.
|
|
|
2799
|
|
2537
|
2800 @node Q1.8.4, Q1.8.5, Q1.8.3, Introduction
|
|
|
2801 @unnumberedsubsec Q1.8.4: Can XEmacs messages come out in a different language?
|
|
428
|
2802
|
|
1135
|
2803 The message-catalog support was written but is badly bit-rotted. XEmacs
|
|
|
2804 20 and 21 did @emph{not} support it, and early releases of XEmacs 22
|
|
|
2805 will not either.
|
|
|
2806
|
|
|
2807 However, menubar localization @emph{does} work. To enable it, add to
|
|
|
2808 your @file{Emacs} file entries like this:
|
|
428
|
2809
|
|
|
2810 @example
|
|
440
|
2811 Emacs*XlwMenu.resourceLabels: True
|
|
|
2812 Emacs*XlwMenu.file.labelString: Fichier
|
|
442
|
2813 Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster oeffnen
|
|
428
|
2814 @end example
|
|
|
2815
|
|
|
2816 The name of the resource is derived from the non-localized entry by
|
|
|
2817 removing punctuation and capitalizing as above.
|
|
|
2818
|
|
2537
|
2819 @node Q1.8.5, Q1.8.6, Q1.8.4, Introduction
|
|
|
2820 @unnumberedsubsec Q1.8.5: Please explain the various input methods in MULE/XEmacs
|
|
428
|
2821
|
|
1135
|
2822 Mule supports a wide variety of input methods. There are three basic
|
|
|
2823 classes: Lisp implementations, generic platform support, and library
|
|
|
2824 interfaces.
|
|
|
2825
|
|
|
2826 @emph{Lisp implementations} include Quail, which provides table-driven input
|
|
|
2827 methods for almost all the character sets that Mule supports (including
|
|
|
2828 all of the ISO 8859 family, the Indic languages, Thai, and so on), and
|
|
|
2829 SKK, for Japanese. (SKK also supports an interface to an external
|
|
|
2830 "dictionary server" process.) Quail supports both typical "dead-key"
|
|
|
2831 methods (eg, in the "latin-1-prefix" method, @kbd{" a} produces ä, LATIN
|
|
|
2832 SMALL LETTER A WITH DIAERESIS), and the complex dictionary-based phonetic
|
|
|
2833 methods used for Asian ideographic languages like Chinese.
|
|
|
2834
|
|
|
2835 Lisp implementations can be less powerful (but they are not perceptibly
|
|
|
2836 inefficient), and of course are not portable to non-Emacs applications.
|
|
|
2837 The incompatibility can be very annoying. On the other hand, they
|
|
|
2838 require no special platform support or external libraries, so if you can
|
|
|
2839 display the characters, Mule can input them for you and you can edit,
|
|
|
2840 anywhere.
|
|
|
2841
|
|
|
2842 @emph{Generic platform support} is currently limited to the X Input
|
|
|
2843 Method (XIM) framework, although support for MSIME (for MS Windows) is
|
|
|
2844 planned, and IIIMF (Sun's Internet-Intranet Input Method Framework)
|
|
|
2845 support is extremely desirable. XIM is enabled at build time by use of
|
|
|
2846 the @samp{--with-xim} flag to @code{configure}. For use of XIM, see
|
|
|
2847 your platform documentation. However, normally the input method you use
|
|
|
2848 is specified via the @samp{LANG} and @samp{XMODIFIERS} environment
|
|
|
2849 variables.
|
|
|
2850
|
|
|
2851 Of course, input skills are portable across most applications. However,
|
|
|
2852 especially in modern GUI systems the habit of using bucky bits has
|
|
|
2853 fallen into sad disuse, and many XIM systems are poorly configured for
|
|
|
2854 use with Emacs. For example, the kinput2 input manager (a separate
|
|
|
2855 process providing an interface between Japanese dictionary servers such
|
|
|
2856 as Canna and Wnn, and the application) tends to gobble up keystrokes
|
|
|
2857 generating Meta characters. This means that to edit while using an XIM
|
|
|
2858 input method, you must toggle the input method off every time you want
|
|
|
2859 to use @kbd{M-f}. Your mileage may vary.
|
|
|
2860
|
|
|
2861 @emph{Library interfaces} are most common for Japanese, although Wnn
|
|
|
2862 supports Chinese (traditional and simplified) and Korean. There are
|
|
|
2863 Chinese and Korean input servers available, but we do not know of any
|
|
|
2864 patches for XEmacs to use them directly. You can use them via
|
|
|
2865 IM-enabled terminals, by manipulating the terminal coding systems. We
|
|
|
2866 describe only the Japanese-oriented systems here. The advantage of
|
|
|
2867 these systems is that they are very powerful, and on platforms where
|
|
|
2868 they are available there is typically a wide range of applications that
|
|
|
2869 support them. Thus your input skills are portable across applications.
|
|
|
2870
|
|
|
2871 Mule provides built-in interfaces to the following input methods: Wnn4,
|
|
|
2872 Wnn6, Canna, and SJ3. These can be configured at build time. There are
|
|
|
2873 patches available (no URL, sorry) to support the SKK server, as well.
|
|
|
2874 Wnn and SJ3 use the @code{egg} user interface. The interface for Canna
|
|
|
2875 is specialized to Canna.
|
|
428
|
2876
|
|
|
2877 Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
|
|
1135
|
2878 University. It is a powerful and complex system. Wnn4 is free and Wnn6
|
|
|
2879 is not. Wnn uses grammatical hints and probability of word association,
|
|
|
2880 so in principle Wnn can be cleverer than other methods.
|
|
|
2881
|
|
|
2882 Canna, made by NEC, supports only Japanese. It is a simple and powerful
|
|
|
2883 system. Canna uses only grammar, but its grammar and dictionary are
|
|
|
2884 quite sophisticated. So for standard modern Japanese, Canna seems
|
|
|
2885 cleverer than Wnn4. In addition, the UNIX version of Canna is free (now
|
|
|
2886 there is a Microsoft Windows version).
|
|
|
2887
|
|
|
2888 SJ3, by Sony, supports only Japanese.
|
|
428
|
2889
|
|
|
2890 Egg consists of following parts:
|
|
|
2891
|
|
|
2892 @enumerate
|
|
|
2893 @item
|
|
|
2894 Input character Translation System (ITS) layer.
|
|
|
2895 It translates ASCII inputs to Kana/PinYin/Hangul characters.
|
|
|
2896
|
|
|
2897 @item
|
|
|
2898 Kana/PinYin/Hangul to Kanji transfer layer.
|
|
1135
|
2899 The interface layer to network Kana-Kanji server (Wnn and Sj3).
|
|
428
|
2900 @end enumerate
|
|
|
2901
|
|
1135
|
2902 These input methods are modal. They have a raw (alphabet) mode, a
|
|
|
2903 phonetic input mode, and Kana-Kanji transfer mode. However there are
|
|
|
2904 mode-less input methods for Egg and Canna. @samp{boiled-egg} is a
|
|
|
2905 mode-less input method running on Egg. For Canna, @samp{canna.el} has a
|
|
|
2906 tiny boiled-egg-like command, @code{(canna-boil)}, and there are some
|
|
|
2907 boiled-egg-like utilities.
|
|
|
2908
|
|
|
2909 Much of this information was provided by @email{morioka@@jaist.ac.jp,
|
|
|
2910 MORIOKA Tomohiko}.
|
|
428
|
2911
|
|
2537
|
2912 @node Q1.8.6, Q1.8.7, Q1.8.5, Introduction
|
|
|
2913 @unnumberedsubsec Q1.8.6: How do I portably code for MULE/XEmacs?
|
|
428
|
2914
|
|
1135
|
2915 MULE has evolved rapidly over the last few years, and the original third
|
|
|
2916 party patch (for GNU Emacs 19), GNU Emacs 20+, and XEmacs 20+ have quite
|
|
|
2917 different implementations. The APIs also vary although recent versions
|
|
|
2918 of XEmacs have tended to converge to the GNU Emacs standard.
|
|
|
2919
|
|
|
2920 MULE implementations are going to continue to evolve. Both GNU Emacs
|
|
|
2921 and XEmacs are working hard on Unicode support, which will involve new
|
|
|
2922 APIs and probably variations on old ones. For XEmacs 22, the old ISO
|
|
|
2923 2022-based system for recognizing encodings will be replaced by a much
|
|
|
2924 more flexible system, which should improve accuracy of automatic coding
|
|
|
2925 detections, but will also involve new APIs.
|
|
|
2926
|
|
428
|
2927 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
|
|
|
2928
|
|
|
2929 @quotation
|
|
1135
|
2930 The application implementor must write separate code for these mule
|
|
|
2931 variants. [Please don't hesitate to report these variants to us; they
|
|
|
2932 are not, strictly speaking, bugs, but they give third-party developers
|
|
|
2933 the same kind of creepy-crawly feeling. We'll do what we can. -- Ed.]
|
|
428
|
2934
|
|
|
2935 MULE and the next version of Emacs are similar but the symbols are very
|
|
|
2936 different---requiring separate code as well.
|
|
|
2937
|
|
|
2938 Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of
|
|
|
2939 emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called
|
|
1135
|
2940 @code{emu} to provide a common interface. [There is an XEmacs package
|
|
|
2941 of APEL which provides much more comprehensive coverage. Be careful,
|
|
|
2942 however; APEL has problems of its own. -- Ed.]
|
|
428
|
2943
|
|
|
2944 I have the following suggestions about dealing with mule variants:
|
|
|
2945
|
|
|
2946 @itemize @bullet
|
|
|
2947 @item
|
|
|
2948 @code{(featurep 'mule)} @code{t} on all mule variants
|
|
|
2949
|
|
|
2950 @item
|
|
|
2951 @code{(boundp 'MULE)} is @code{t} on only MULE. Maybe the next version
|
|
|
2952 of Emacs will not have this symbol.
|
|
|
2953
|
|
|
2954 @item
|
|
|
2955 MULE has a variable @code{mule-version}. Perhaps the next version of
|
|
|
2956 Emacs will have this variable as well.
|
|
|
2957 @end itemize
|
|
|
2958
|
|
|
2959 Following is a sample to distinguish mule variants:
|
|
|
2960
|
|
|
2961 @lisp
|
|
|
2962 (if (featurep 'mule)
|
|
|
2963 (cond ((boundp 'MULE)
|
|
|
2964 ;; for original Mule
|
|
|
2965 )
|
|
440
|
2966 ((string-match "XEmacs" emacs-version)
|
|
|
2967 ;; for XEmacs with Mule
|
|
|
2968 )
|
|
|
2969 (t
|
|
|
2970 ;; for next version of Emacs
|
|
|
2971 ))
|
|
428
|
2972 ;; for old emacs variants
|
|
|
2973 )
|
|
|
2974 @end lisp
|
|
|
2975 @end quotation
|
|
|
2976
|
|
2537
|
2977 @node Q1.8.7, Q1.8.8, Q1.8.6, Introduction
|
|
|
2978 @unnumberedsubsec Q1.8.7: How about Cyrillic modes?
|
|
428
|
2979
|
|
|
2980 @email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes:
|
|
|
2981
|
|
|
2982 @quotation
|
|
|
2983 There is a cyrillic mode in the file @file{mysetup.zip} in
|
|
|
2984 @iftex
|
|
|
2985 @*
|
|
|
2986 @end iftex
|
|
|
2987 @uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}. This is a
|
|
|
2988 modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el}
|
|
|
2989 which can be obtained from
|
|
|
2990 @end quotation
|
|
|
2991
|
|
871
|
2992 @uref{http://www.math.uga.edu/~valery/russian.el}.
|
|
428
|
2993
|
|
|
2994 @email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes:
|
|
|
2995
|
|
|
2996 @quotation
|
|
|
2997 There is another cyrillic mode for both GNU Emacs and XEmacs by
|
|
|
2998 @email{manin@@camelot.mssm.edu, Dmitrii
|
|
|
2999 (Mitya) Manin} at
|
|
|
3000 @iftex
|
|
|
3001
|
|
|
3002 @end iftex
|
|
|
3003 @uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}.
|
|
|
3004 @c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead.
|
|
|
3005 @c Changed to russian host instead
|
|
|
3006 @end quotation
|
|
|
3007
|
|
|
3008 @email{rebecca.ore@@op.net, Rebecca Ore} writes:
|
|
|
3009
|
|
|
3010 @quotation
|
|
|
3011 The fullest resource I found on Russian language use (in and out of
|
|
661
|
3012 XEmacs) is @uref{http://www.ibiblio.org/sergei/Software/Software.html}
|
|
428
|
3013 @end quotation
|
|
|
3014
|
|
2537
|
3015 @node Q1.8.8, Q1.8.9, Q1.8.7, Introduction
|
|
|
3016 @unnumberedsubsec Q1.8.8: Does XEmacs support Unicode?
|
|
2417
|
3017
|
|
|
3018 To get Unicode support, you need a Mule-enabled XEmacs.
|
|
|
3019
|
|
|
3020 21.5 has internal support for Unicode and supports it fully, although we
|
|
|
3021 don't yet use it as the internal encoding.
|
|
|
3022
|
|
|
3023 21.4 supports Unicode partially -- as an external encoding for files,
|
|
2537
|
3024 processes, and terminals, but without font support. @xref{Q1.8.9, How
|
|
2417
|
3025 does XEmacs display Unicode?}. To get Unicode support in 21.4,
|
|
|
3026 install Mule-UCS from packages in the usual way, and put
|
|
745
|
3027
|
|
1616
|
3028 @example
|
|
745
|
3029 (require 'un-define)
|
|
|
3030 (set-coding-priority-list '(utf-8))
|
|
1616
|
3031 (set-coding-category-system 'utf-8 'utf-8)
|
|
|
3032 @end example
|
|
|
3033
|
|
|
3034 in your init file to enable the UTF-8 coding system. You may wish to
|
|
|
3035 view the documentation of @code{set-coding-priority-list} if you find
|
|
|
3036 that files that are not UTF-8 are being mis-recognized as UTF-8.
|
|
745
|
3037
|
|
2417
|
3038 Install standard national fonts (not Unicode fonts) for all character
|
|
2537
|
3039 sets you use. @xref{Q1.8.9, How does XEmacs display Unicode??}.
|
|
745
|
3040
|
|
|
3041 Mule-UCS also supports 16-bit forms of Unicode (UTF-16). It does not
|
|
|
3042 support 31-bit forms of Unicode (UTF-32 or UCS-4).
|
|
|
3043
|
|
2537
|
3044 @node Q1.8.9, , Q1.8.8, Introduction
|
|
|
3045 @unnumberedsubsec Q1.8.9: How does XEmacs display Unicode?
|
|
745
|
3046
|
|
|
3047 Mule doesn't have a Unicode charset internally, so there's nothing to
|
|
|
3048 bind a Unicode registry to. It would not be straightforward to create,
|
|
|
3049 either, because Unicode is not ISO 2022-compatible. You'd have to
|
|
|
3050 translate it to multiple 96x96 pages.
|
|
|
3051
|
|
|
3052 This means that Mule-UCS uses ordinary national fonts for display. This
|
|
|
3053 is not really a problem, except for those languages that use the Unified
|
|
|
3054 Han characters. The problem here is that Mule-UCS maps from Unicode
|
|
|
3055 code points to national character sets in a deterministic way. By
|
|
|
3056 default, this means that Japanese fonts are tried first, then Chinese,
|
|
|
3057 then Korean. To change the priority ordering, use the command
|
|
|
3058 `un-define-change-charset-order'.
|
|
|
3059
|
|
|
3060 It also means you can't use Unicode fonts directly, at least not without
|
|
|
3061 extreme hackery. You can run -nw with (set-terminal-coding-system
|
|
|
3062 'utf-8) if you really want a Unicode font for some reason.
|
|
|
3063
|
|
|
3064 Real Unicode support will be introduced in XEmacs 22.0.
|
|
|
3065
|
|
2459
|
3066 @node Installation, Editing, Introduction, Top
|
|
2417
|
3067 @unnumbered 2 Installation and Troubleshooting
|
|
428
|
3068
|
|
|
3069 This is part 2 of the XEmacs Frequently Asked Questions list. This
|
|
2417
|
3070 section is devoted to Installation, Maintenance and Troubleshooting.
|
|
428
|
3071
|
|
|
3072 @menu
|
|
2559
|
3073 2.0: Installation (General)
|
|
|
3074 * Q2.0.1:: How do I build and install XEmacs?
|
|
|
3075 * Q2.0.2:: Where do I find external libraries?
|
|
|
3076 * Q2.0.3:: How do I specify the paths that XEmacs uses for finding files?
|
|
|
3077 * Q2.0.4:: Running XEmacs without installing
|
|
|
3078 * Q2.0.5:: XEmacs is too big
|
|
|
3079
|
|
|
3080 2.1: Package Installation
|
|
|
3081 * Q2.1.1:: How do I install the packages?
|
|
|
3082 * Q2.1.2:: Can I install the packages individually?
|
|
|
3083 * Q2.1.3:: Can I install the packages automatically?
|
|
|
3084 * Q2.1.4:: Can I upgrade or remove packages?
|
|
|
3085 * Q2.1.5:: Which packages to install?
|
|
|
3086 * Q2.1.6:: Can you describe the package location process in more detail?
|
|
|
3087 * Q2.1.7:: EFS fails with "500 AUTH not understood"
|
|
|
3088
|
|
|
3089 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
|
3090 * Q2.2.1:: Libraries in non-standard locations
|
|
|
3091 * Q2.2.2:: Why can't I strip XEmacs?
|
|
|
3092
|
|
|
3093 2.3: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
3094 * Q2.3.1:: What exactly are all the different ways to build XEmacs under Windows?
|
|
|
3095 * Q2.3.2:: What compiler/libraries do I need to compile XEmacs?
|
|
|
3096 * Q2.3.3:: How do I compile the native port?
|
|
|
3097 * Q2.3.4:: What do I need for Cygwin?
|
|
|
3098 * Q2.3.5:: How do I compile under Cygwin?
|
|
|
3099 * Q2.3.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
|
3100 * Q2.3.7:: How do I compile with X support?
|
|
|
3101 * Q2.3.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
|
3102
|
|
|
3103 2.4: General Troubleshooting
|
|
|
3104 * Q2.4.1:: How do I deal with bugs or with problems building, installing, or running?
|
|
|
3105 * Q2.4.2:: Help! XEmacs just crashed on me!
|
|
|
3106 * Q2.4.3:: XEmacs crashes and I compiled it myself.
|
|
|
3107 * Q2.4.4:: How to debug an XEmacs problem with a debugger
|
|
|
3108 * Q2.4.5:: I get a cryptic error message when trying to do something.
|
|
|
3109 * Q2.4.6:: XEmacs hangs when I try to do something.
|
|
|
3110 * Q2.4.7:: I get an error message when XEmacs is running in batch mode.
|
|
|
3111 * Q2.4.8:: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
|
3112 * Q2.4.9:: @kbd{C-g} doesn't work for me. Is it broken?
|
|
|
3113 * Q2.4.10:: How do I debug process-related problems?
|
|
|
3114 * Q2.4.11:: XEmacs is outputting lots of X errors.
|
|
|
3115 * Q2.4.12:: After upgrading, XEmacs won't do `foo' any more!
|
|
|
3116
|
|
|
3117 2.5: Startup-Related Problems
|
|
|
3118 * Q2.5.1:: XEmacs cannot connect to my X Terminal!
|
|
|
3119 * Q2.5.2:: Startup problems related to paths or package locations.
|
|
|
3120 * Q2.5.3:: XEmacs won't start without network.
|
|
|
3121 * Q2.5.4:: Startup warnings about deducing proper fonts?
|
|
|
3122 * Q2.5.5:: Warnings from incorrect key modifiers.
|
|
|
3123 * Q2.5.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
428
|
3124 @end menu
|
|
|
3125
|
|
2559
|
3126 @unnumberedsec 2.0: Installation (General)
|
|
2417
|
3127
|
|
428
|
3128 @node Q2.0.1, Q2.0.2, Installation, Installation
|
|
2559
|
3129 @unnumberedsubsec Q2.0.1: How do I build and install XEmacs?
|
|
|
3130
|
|
|
3131 See the file @file{etc/NEWS} for information on new features and other
|
|
|
3132 user-visible changes since the last version of XEmacs.
|
|
|
3133
|
|
|
3134 The file @file{INSTALL} in the top-level directory says how to bring
|
|
|
3135 up XEmacs on Unix and Cygwin, once you have loaded the entire subtree
|
|
|
3136 of this directory.
|
|
|
3137
|
|
|
3138 See the file @file{nt/README} for instructions on building XEmacs for
|
|
|
3139 Microsoft Windows.
|
|
|
3140
|
|
|
3141 @xref{Q2.1.1}, for the installation of (essential) add on packages.
|
|
2417
|
3142
|
|
|
3143 @node Q2.0.2, Q2.0.3, Q2.0.1, Installation
|
|
2559
|
3144 @unnumberedsubsec Q2.0.2: Where do I find external libraries?
|
|
2417
|
3145
|
|
2459
|
3146 All external libraries used by XEmacs can be found on the XEmacs web
|
|
2417
|
3147 site
|
|
|
3148 @iftex
|
|
|
3149 @*
|
|
|
3150 @end iftex
|
|
2459
|
3151 @uref{http://www.xemacs.org/Download/optLibs.html}.
|
|
2417
|
3152
|
|
|
3153 The library versions available here are known to work with XEmacs.
|
|
|
3154 (Newer versions will probably work as well but we can't guarantee it.)
|
|
|
3155 We try to keep the libraries up-to-date but may not always succeed.
|
|
2459
|
3156 Check the above page for the canonical locations of the external libraries,
|
|
|
3157 allowing you to download the latest, bleeding-edge versions.
|
|
2417
|
3158
|
|
2559
|
3159 @node Q2.0.3, Q2.0.4, Q2.0.2, Installation
|
|
|
3160 @unnumberedsubsec Q2.0.3: How do I specify the paths that XEmacs uses for finding files?
|
|
2417
|
3161
|
|
|
3162 You can specify what paths to use by using a number of different flags
|
|
|
3163 when running configure. See the section MAKE VARIABLES in the top-level
|
|
|
3164 file INSTALL in the XEmacs distribution for a listing of those flags.
|
|
|
3165
|
|
|
3166 Most of the time, however, the simplest fix is: @strong{do not} specify
|
|
|
3167 paths as you might for GNU Emacs. XEmacs can generally determine the
|
|
|
3168 necessary paths dynamically at run time. The only path that generally
|
|
|
3169 needs to be specified is the root directory to install into. That can
|
|
|
3170 be specified by passing the @code{--prefix} flag to configure. For a
|
|
|
3171 description of the XEmacs install tree, please consult the @file{NEWS}
|
|
|
3172 file.
|
|
|
3173
|
|
2559
|
3174 @node Q2.0.4, Q2.0.5, Q2.0.3, Installation
|
|
|
3175 @unnumberedsubsec Q2.0.4: Running XEmacs without installing
|
|
442
|
3176
|
|
|
3177 How can I just try XEmacs without installing it?
|
|
428
|
3178
|
|
|
3179 XEmacs will run in place without requiring installation and copying of
|
|
|
3180 the Lisp directories, and without having to specify a special build-time
|
|
|
3181 flag. It's the copying of the Lisp directories that requires so much
|
|
|
3182 space. XEmacs is largely written in Lisp.
|
|
|
3183
|
|
|
3184 A good method is to make a shell alias for xemacs:
|
|
|
3185
|
|
|
3186 @example
|
|
2459
|
3187 alias xemacs=/src/xemacs-21.5/src/xemacs
|
|
428
|
3188 @end example
|
|
|
3189
|
|
|
3190 (You will obviously use whatever directory you downloaded the source
|
|
2459
|
3191 tree to instead of @file{/src/xemacs-21.5}).
|
|
428
|
3192
|
|
|
3193 This will let you run XEmacs without massive copying.
|
|
|
3194
|
|
2559
|
3195 @node Q2.0.5, Q2.1.1, Q2.0.4, Installation
|
|
|
3196 @unnumberedsubsec Q2.0.5: XEmacs is too big
|
|
428
|
3197
|
|
442
|
3198 The space required by the installation directories can be
|
|
428
|
3199 reduced dramatically if desired. Gzip all the .el files. Remove all
|
|
442
|
3200 the packages you'll never want to use. Remove the TexInfo manuals.
|
|
428
|
3201 Remove the Info (and use just hardcopy versions of the manual). Remove
|
|
|
3202 most of the stuff in etc. Remove or gzip all the source code. Gzip or
|
|
|
3203 remove the C source code. Configure it so that copies are not made of
|
|
1138
|
3204 the support lisp.
|
|
428
|
3205
|
|
|
3206 These are all Emacs Lisp source code and bytecompiled object code. You
|
|
|
3207 may safely gzip everything named *.el here. You may remove any package
|
|
|
3208 you don't use. @emph{Nothing bad will happen if you delete a package
|
|
|
3209 that you do not use}. You must be sure you do not use it though, so be
|
|
|
3210 conservative at first.
|
|
|
3211
|
|
1648
|
3212 Any package with the possible exceptions of xemacs-base, and EFS are
|
|
|
3213 candidates for removal. Ask yourself, @emph{Do I ever want to use this
|
|
|
3214 package?} If the answer is no, then it is a candidate for removal.
|
|
428
|
3215
|
|
|
3216 First, gzip all the .el files. Then go about package by package and
|
|
|
3217 start gzipping the .elc files. Then run XEmacs and do whatever it is
|
|
1648
|
3218 you normally do. If nothing bad happens, then remove the package. You
|
|
|
3219 can remove a package via the PUI interface
|
|
|
3220 (@code{M-x pui-list-packages}, then press @kbd{d} to mark the packages
|
|
|
3221 you wish to delete, and then @kbd{x} to delete them.
|
|
|
3222
|
|
|
3223 Another method is to do @code{M-x package-get-delete-package}.
|
|
428
|
3224
|
|
2559
|
3225 @unnumberedsec 2.1: Package Installation
|
|
|
3226
|
|
|
3227 @node Q2.1.1, Q2.1.2, Q2.0.5, Installation
|
|
|
3228 @unnumberedsubsec Q2.1.1: How do I install the packages?
|
|
|
3229
|
|
|
3230 There are three ways to install the packages.
|
|
|
3231
|
|
|
3232 @enumerate
|
|
|
3233 @item
|
|
|
3234 Manually, all at once, using the 'Sumo Tarball'.
|
|
|
3235 @item
|
|
|
3236 Manually, using individual package tarballs.
|
|
|
3237 @item
|
|
|
3238 Automatically, using the package tools from XEmacs.
|
|
|
3239 @end enumerate
|
|
|
3240
|
|
|
3241 If you don't want to mess with the packages, it is easiest to just
|
|
|
3242 grab them manually, all at once. (For the other two ways,
|
|
|
3243 @xref{Q2.1.2}, and @xref{Q2.1.3}.) Download the file
|
|
|
3244
|
|
|
3245 @file{xemacs-sumo.tar.gz}
|
|
|
3246
|
|
|
3247 For an XEmacs compiled with Mule you also need
|
|
|
3248
|
|
|
3249 @file{xemacs-mule-sumo.tar.gz}
|
|
|
3250
|
|
|
3251 These are in the @file{packages} directory on your XEmacs mirror
|
|
|
3252 archive: @uref{ftp://ftp.xemacs.org/pub/xemacs/packages} or its
|
|
|
3253 mirrors. N.B. They are called 'Sumo Tarballs' for good reason. They
|
|
|
3254 are currently about 19MB and 4.5MB (gzipped) respectively.
|
|
|
3255
|
|
|
3256 Install them on Unix and Mac OS X using the shell/Terminal command
|
|
|
3257
|
|
|
3258 @code{cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xf -}
|
|
|
3259
|
|
|
3260 Where @samp{$prefix} is what you gave to the @samp{--prefix} flag to
|
|
|
3261 @file{configure}, and defaults to @file{/usr/local}.
|
|
|
3262
|
|
|
3263 If you have GNU tar you can use:
|
|
|
3264
|
|
|
3265 @code{cd $prefix/lib/xemacs ; tar zxvf <tarballname>}
|
|
|
3266
|
|
3018
|
3267 If you have the packages somewhere nonstandard and don't want to bother
|
|
|
3268 with @samp{$prefix} (for example, you're a developer and are compiling
|
|
|
3269 the packages yourself, and want your own private copy of everything),
|
|
|
3270 you can also directly specify this using @file{configure}. To do this
|
|
|
3271 with 21.5 and above use the @samp{--with-package-prefix} parameter to
|
|
|
3272 specify the directory under which you untarred the above tarballs.
|
|
|
3273 Under 21.4 and previous you need to use @samp{--package-path}. Using
|
|
|
3274 these options looks something like this:
|
|
2559
|
3275
|
|
|
3276 @example
|
|
|
3277 configure --package-path="~/.xemacs::/src/xemacs/site-packages:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages" ...
|
|
|
3278 @end example
|
|
|
3279
|
|
|
3280 Under Windows, you need to place the above @samp{tar.gz} files in the
|
|
|
3281 directory specified using the @samp{PACKAGE_PREFIX} value in
|
|
|
3282 @file{nt/config.inc} and by default is @file{\Program Files\XEmacs}.
|
|
|
3283 (To untar a @samp{tar.gz} file you will need to use a utility such as
|
|
|
3284 WinZip, unless you have Cygwin or a similar environment installed, in
|
|
|
3285 which case the above Unix shell command should work fine.) If you want
|
|
|
3286 the packages somewhere else, just change @samp{PACKAGE_PREFIX}.
|
|
|
3287
|
|
|
3288 Note that XEmacs finds the packages automatically anywhere underneath
|
|
|
3289 the directory tree where it expects to find the packages. All you
|
|
|
3290 need to do is put stuff there; you don't need to run any program to
|
|
|
3291 tell XEmacs to find the packges, or do anything of that sort.
|
|
|
3292
|
|
|
3293 However, XEmacs will only notice newly installed packages when it
|
|
|
3294 starts up, so you will have to restart if you are already running
|
|
|
3295 XEmacs.
|
|
|
3296
|
|
|
3297 For more details, @xref{Startup Paths,,,xemacs, the XEmacs User's
|
|
|
3298 Manual}, and @xref{Packages,,,xemacs, the XEmacs User's Manual}.
|
|
|
3299
|
|
|
3300 As the Sumo tarballs are not regenerated as often as the individual
|
|
|
3301 packages, it is recommended that you use the automatic package tools
|
|
|
3302 afterwards to pick up any recent updates.
|
|
|
3303
|
|
|
3304 @emph{NOTE}: For detailed information about how the package
|
|
|
3305 hierarchies work, @xref{Package Overview,,,lispref, the XEmacs Lisp
|
|
|
3306 Reference Manual}.
|
|
|
3307
|
|
|
3308 @node Q2.1.2, Q2.1.3, Q2.1.1, Installation
|
|
|
3309 @unnumberedsubsec Q2.1.2: Can I install the packages individually?
|
|
|
3310
|
|
|
3311 Yes, you can download individual packages from the FTP site (@pxref{Q2.1.1}). Since packages are automatically noticed at startup, you just have to put them in the right place.
|
|
|
3312
|
|
|
3313 Note: If you are upgrading packages already installed, it's best to
|
|
|
3314 remove the old package first (@pxref{Q2.1.4}).
|
|
|
3315
|
|
|
3316 For example if we are installing the @samp{xemacs-base}
|
|
|
3317 package (version 1.48):
|
|
|
3318
|
|
|
3319 @example
|
|
|
3320 mkdir $prefix/lib/xemacs/xemacs-packages RET # if it does not exist yet
|
|
|
3321 cd $prefix/lib/xemacs/xemacs-packages RET
|
|
|
3322 gunzip -c /path/to/xemacs-base-1.48-pkg.tar.gz | tar xvf - RET
|
|
|
3323 @end example
|
|
|
3324
|
|
|
3325 Or if you have GNU tar, the last step can be:
|
|
|
3326
|
|
|
3327 @example
|
|
|
3328 tar zxvf /path/to/xemacs-base-1.48-pkg.tar.gz RET
|
|
|
3329 @end example
|
|
|
3330
|
|
|
3331 For MULE related packages, it is best to untar into the @samp{mule-packages}
|
|
|
3332 hierarchy, i.e. for the @samp{mule-base} package, version 1.37:
|
|
|
3333
|
|
|
3334 @example
|
|
|
3335 mkdir $prefix/lib/xemacs/mule-packages RET # if it does not exist yet
|
|
|
3336 cd $prefix/lib/xemacs/mule-packages RET
|
|
|
3337 gunzip -c /path/to/mule-base-1.37-pkg.tar.gz | tar xvf - RET
|
|
|
3338 @end example
|
|
|
3339
|
|
|
3340 Or if you have GNU tar, the last step can be:
|
|
|
3341
|
|
|
3342 @example
|
|
|
3343 tar zxvf /path/to/mule-base-1.37-pkg.tar.gz RET
|
|
|
3344 @end example
|
|
|
3345
|
|
|
3346 @node Q2.1.3, Q2.1.4, Q2.1.2, Installation
|
|
|
3347 @unnumberedsubsec Q2.1.3: Can I install the packages automatically?
|
|
|
3348
|
|
|
3349 XEmacs comes with some tools to make the periodic updating and
|
|
|
3350 installing easier. It will notice if new packages or versions are
|
|
|
3351 available and will fetch them from the FTP site.
|
|
|
3352
|
|
|
3353 Unfortunately this requires that a few packages are already in place.
|
|
|
3354 You will have to install them by hand as above or use a SUMO tarball.
|
|
|
3355 This requirement will hopefully go away in the future. The packages
|
|
|
3356 you need are:
|
|
|
3357
|
|
|
3358 @example
|
|
|
3359 efs - To fetch the files from the FTP site or mirrors.
|
|
|
3360 xemacs-base - Needed by efs.
|
|
|
3361 @end example
|
|
|
3362
|
|
|
3363 and optionally:
|
|
|
3364
|
|
|
3365 @example
|
|
|
3366 mailcrypt - For PGP verification of the package-index file.
|
|
|
3367 @end example
|
|
|
3368
|
|
|
3369 After installing these by hand, fire up XEmacs and follow these
|
|
|
3370 steps.
|
|
|
3371
|
|
|
3372 @enumerate
|
|
|
3373 @item
|
|
|
3374 Choose a download site.
|
|
|
3375 @itemize @bullet
|
|
|
3376 @item
|
|
|
3377 via menu: Tools -> Packages -> Set Download Site
|
|
|
3378 @item
|
|
|
3379 via keyb: M-x customize-variable RET package-get-remote RET
|
|
|
3380 (put in the details of remote host and directory)
|
|
|
3381 @end itemize
|
|
|
3382
|
|
|
3383 If the package tarballs _AND_ the package-index file are in a
|
|
|
3384 local directory, you can: M-x pui-set-local-package-get-directory RET
|
|
|
3385
|
|
|
3386 @item
|
|
|
3387 Obtain a list of packages and display the list in a buffer named
|
|
|
3388 "*Packages*".
|
|
|
3389 @itemize @bullet
|
|
|
3390 @item
|
|
|
3391 menu: Tools -> Packages -> List & Install
|
|
|
3392 @item
|
|
|
3393 keyb: M-x pui-list-packages RET
|
|
|
3394 @end itemize
|
|
|
3395
|
|
|
3396 XEmacs will now connect to the remote site and download the
|
|
|
3397 latest package-index file.
|
|
|
3398
|
|
|
3399 The resulting buffer, "*Packages*" has brief instructions at the
|
|
|
3400 end of the buffer.
|
|
|
3401
|
|
|
3402 @item
|
|
|
3403 Choose the packages you wish to install.
|
|
|
3404 @itemize @bullet
|
|
|
3405 @item
|
|
|
3406 mouse: Click button 2 on the package name.
|
|
|
3407 @item
|
|
|
3408 keyb: RET on the package name
|
|
|
3409 @end itemize
|
|
|
3410
|
|
|
3411 @item
|
|
|
3412 Make sure you have everything you need.
|
|
|
3413 @itemize @bullet
|
|
|
3414 @item
|
|
|
3415 menu: Packages -> Add Required
|
|
|
3416 @item
|
|
|
3417 keyb: r
|
|
|
3418 @end itemize
|
|
|
3419
|
|
|
3420 XEmacs will now search for packages that are required by the
|
|
|
3421 ones that you have chosen to install and offer to select
|
|
|
3422 those packages also.
|
|
|
3423
|
|
|
3424 For novices and gurus alike, this step can save your bacon.
|
|
|
3425 It's easy to forget to install a critical package.
|
|
|
3426
|
|
|
3427 @item
|
|
|
3428 Download and install the packages.
|
|
|
3429 @itemize @bullet
|
|
|
3430 @item
|
|
|
3431 menu: Packages -> Install/Remove Selected
|
|
|
3432 @item
|
|
|
3433 keyb: x
|
|
|
3434 @end itemize
|
|
|
3435 @end enumerate
|
|
|
3436
|
|
|
3437 @node Q2.1.4, Q2.1.5, Q2.1.3, Installation
|
|
|
3438 @unnumberedsubsec Q2.1.4: Can I upgrade or remove packages?
|
|
|
3439
|
|
|
3440 As the exact files and their locations contained in a package may
|
|
|
3441 change it is recommended to remove a package first before installing a
|
|
|
3442 new version. In order to facilitate removal each package contains an
|
|
|
3443 pgkinfo/MANIFEST.pkgname file which list all the files belong to the
|
|
|
3444 package. M-x package-admin-delete-binary-package RET can be used to
|
|
|
3445 remove a package using this file.
|
|
|
3446
|
|
|
3447 Note that the interactive package tools included with XEmacs already do
|
|
|
3448 this for you.
|
|
|
3449
|
|
|
3450 @node Q2.1.5, Q2.1.6, Q2.1.4, Installation
|
|
|
3451 @unnumberedsubsec Q2.1.5: Which packages to install?
|
|
|
3452
|
|
|
3453 Unless you are an advanced user, just install everything.
|
|
|
3454
|
|
|
3455 If you really want to install only what's absolutely needed, a good
|
|
|
3456 minimal set of packages for XEmacs-latin1 would be
|
|
|
3457
|
|
|
3458 @example
|
|
|
3459 xemacs-base, xemacs-devel, c-support, cc-mode, debug, dired, efs,
|
|
|
3460 edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes,
|
|
|
3461 text-modes, time, mailcrypt
|
|
|
3462 @end example
|
|
|
3463
|
|
|
3464 If you are using the XEmacs package tools, don't forget to do:
|
|
|
3465
|
|
|
3466 @example
|
|
|
3467 Packages -> Add Required
|
|
|
3468 @end example
|
|
|
3469
|
|
|
3470 To make sure you have everything that the packages you have chosen to
|
|
|
3471 install need.
|
|
|
3472
|
|
|
3473 @xref{Q1.7.2}, for a description of the various packages.
|
|
|
3474
|
|
|
3475 @node Q2.1.6, Q2.1.7, Q2.1.5, Installation
|
|
|
3476 @unnumberedsubsec Q2.1.6: Can you describe the package location process in more detail?
|
|
|
3477
|
|
|
3478 On startup XEmacs looks for packages in so-called package hierarchies.
|
|
|
3479 Normally, there are three system wide hierarchies, like this:
|
|
|
3480
|
|
|
3481 @example
|
|
|
3482 $prefix/lib/xemacs/xemacs-packages/
|
|
|
3483 Normal packages go here.
|
|
|
3484
|
|
|
3485 $prefix/lib/xemacs/mule-packages/
|
|
|
3486 Mule packages go here and are only searched by MULE-enabled XEmacsen.
|
|
|
3487
|
|
|
3488 $prefix/lib/xemacs/site-packages/
|
|
|
3489 Local and 3rd party packages go here.
|
|
|
3490 @end example
|
|
|
3491
|
|
|
3492 This is what you get when you untar the SUMO tarballs under
|
|
|
3493 @file{$prefix/lib/xemacs}.
|
|
|
3494
|
|
|
3495 @file{$prefix} is specified using the @samp{--prefix} parameter to
|
|
|
3496 @file{configure}, and defaults to @file{usr/local}.
|
|
|
3497
|
|
|
3498 If the package path is not explicitly specified, XEmacs looks for the
|
|
|
3499 package directory @file{xemacs-packages} (and @file{mule-packages} and
|
|
|
3500 @file{site-packages}) first under @samp{~/.xemacs}, then for a sister
|
|
|
3501 directory @file{lib/xemacs-VERSION} of the directory in which the
|
|
|
3502 XEmacs executable is located, then for a sister directory
|
|
|
3503 @file{lib/xemacs}. The XEmacs executable (under Unix at least) is
|
|
|
3504 installed by default in @file{/usr/local/bin}; this explains why
|
|
|
3505 XEmacs in its default installation will find packages that you put
|
|
|
3506 under @file{/usr/local/lib/xemacs}.
|
|
|
3507
|
|
|
3508 You can specify where exactly XEmacs looks for packages by using the
|
|
3018
|
3509 @samp{--with-package-prefix} or @samp{--with-package-path} parameters to
|
|
|
3510 @file{configure} (or the equivalent settings in @file{config.inc}, under
|
|
|
3511 Windows), or setting the @samp{EMACSPACKAGEPATH} environment variable
|
|
|
3512 (which has the same format as @samp{--with-package-path}). @xref{Q2.1.1}.
|
|
2559
|
3513
|
|
|
3514 See @file{configure.usage} for more info about the format of these
|
|
|
3515 @file{configure} parameters.
|
|
|
3516
|
|
|
3517 In addition to the system wide packages, each user can have his own
|
|
|
3518 packages installed under @file{~/.xemacs/}. If you want to install
|
|
|
3519 packages there using the interactive tools, you need to set
|
|
|
3520 @code{package-get-install-to-user-init-directory} to @code{t}.
|
|
|
3521
|
|
|
3522 The site-packages hierarchy replaces the old @file{site-lisp}
|
|
|
3523 directory. XEmacs no longer looks into a @file{site-lisp} directly by
|
|
|
3524 default. A good place to put @file{site-start.el} would be in
|
|
|
3525 @file{$prefix/lib/xemacs/site-packages/lisp/}.
|
|
|
3526
|
|
|
3527 @node Q2.1.7, Q2.2.1, Q2.1.6, Installation
|
|
|
3528 @unnumberedsubsec Q2.1.7: EFS fails with "500 AUTH not understood" (NEW)
|
|
2417
|
3529
|
|
|
3530 A typical error: FTP Error: USER request failed; 500 AUTH not understood.
|
|
|
3531
|
|
|
3532 Thanks to giacomo boffi @email{giacomo.boffi@@polimi.it} who recommends
|
|
|
3533 on comp.emacs.xemacs:
|
|
|
3534
|
|
|
3535 tell your ftp client to not attempt AUTH authentication (or do not
|
|
|
3536 use FTP servers that don't understand AUTH)
|
|
|
3537
|
|
|
3538 and notes that you need to add an element (often "-u") to
|
|
|
3539 `efs-ftp-program-args'. Use M-x customize-variable, and verify the
|
|
|
3540 needed flag with `man ftp' or other local documentation.
|
|
|
3541
|
|
2559
|
3542 @unnumberedsec 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
|
3543
|
|
|
3544 @node Q2.2.1, Q2.2.2, Q2.1.7, Installation
|
|
|
3545 @unnumberedsubsec Q2.2.1: Libraries in non-standard locations
|
|
428
|
3546
|
|
2459
|
3547 If your libraries are in a non-standard location, you can specify the location
|
|
3018
|
3548 using the following flags to @file{configure}. Under 21.4 or earlier:
|
|
2459
|
3549
|
|
|
3550 @example
|
|
|
3551 --site-libraries=WHATEVER
|
|
|
3552 --site-includes=WHATEVER
|
|
|
3553 @end example
|
|
|
3554
|
|
3018
|
3555 Under 21.5 or later:
|
|
|
3556
|
|
|
3557 @example
|
|
|
3558 --with-site-libraries=WHATEVER
|
|
|
3559 --with-site-includes=WHATEVER
|
|
|
3560 @end example
|
|
|
3561
|
|
2459
|
3562 If you have multiple paths to specify, use the following syntax:
|
|
428
|
3563
|
|
|
3564 @example
|
|
|
3565 --site-libraries='/path/one /path/two /path/etc'
|
|
|
3566 @end example
|
|
|
3567
|
|
3018
|
3568 If the libraries and headers reside in the directories @samp{lib} and
|
|
|
3569 @samp{include} of a common root (say @samp{/sw}) then both can be
|
|
|
3570 specified with a single option:
|
|
|
3571
|
|
|
3572 @example
|
|
|
3573 --site-prefixes=WHATEVER
|
|
|
3574 @end example
|
|
|
3575
|
|
|
3576 or for 21.5:
|
|
|
3577
|
|
|
3578 @example
|
|
|
3579 --with-site-prefixes=WHATEVER
|
|
|
3580 @end example
|
|
|
3581
|
|
2559
|
3582 @node Q2.2.2, Q2.3.1, Q2.2.1, Installation
|
|
|
3583 @unnumberedsubsec Q2.2.2: Why can't I strip XEmacs?
|
|
428
|
3584
|
|
|
3585 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:
|
|
|
3586
|
|
|
3587 @quotation
|
|
|
3588 Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The
|
|
|
3589 link gives you a bare-boned emacs (called temacs). temacs is then run,
|
|
|
3590 preloading some of the lisp files. The result is then dumped into a new
|
|
|
3591 executable, named xemacs, which will contain all of the preloaded lisp
|
|
|
3592 functions and data.
|
|
|
3593
|
|
|
3594 Now, during the dump itself, the executable (code+data+symbols) is
|
|
|
3595 written on disk using a special unexec() function. This function is
|
|
|
3596 obviously heavily system dependent. And on some systems, it leads to an
|
|
|
3597 executable which, although valid, cannot be stripped without damage. If
|
|
|
3598 memory serves, this is especially the case for AIX binaries. On other
|
|
462
|
3599 architectures it might work OK.
|
|
428
|
3600
|
|
|
3601 The Right Way to strip the emacs binary is to strip temacs prior to
|
|
|
3602 dumping xemacs. This will always work, although you can do that only if
|
|
|
3603 you install from sources (as temacs is @file{not} part of the binary
|
|
|
3604 kits).
|
|
|
3605 @end quotation
|
|
|
3606
|
|
|
3607 @email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes:
|
|
|
3608
|
|
|
3609 @quotation
|
|
|
3610 Here is the trick:
|
|
|
3611
|
|
|
3612 @enumerate
|
|
|
3613 @item
|
|
|
3614 [ ./configure; make ]
|
|
|
3615
|
|
|
3616 @item
|
|
|
3617 rm src/xemacs
|
|
|
3618
|
|
|
3619 @item
|
|
|
3620 strip src/temacs
|
|
|
3621
|
|
|
3622 @item
|
|
|
3623 make
|
|
|
3624
|
|
|
3625 @item
|
|
|
3626 cp src/xemacs /usr/local/bin/xemacs
|
|
|
3627
|
|
|
3628 @item
|
|
|
3629 cp lib-src/DOC-19.16-XEmacs
|
|
|
3630 @iftex
|
|
|
3631 \ @*
|
|
|
3632 @end iftex
|
|
|
3633 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
|
|
|
3634 @end enumerate
|
|
|
3635 @end quotation
|
|
|
3636
|
|
2559
|
3637 @unnumberedsec 2.3: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
3638
|
|
|
3639 @node Q2.3.1, Q2.3.2, Q2.2.2, Installation
|
|
|
3640 @unnumberedsubsec Q2.3.1: What exactly are all the different ways to build XEmacs under Windows?
|
|
2417
|
3641
|
|
|
3642 XEmacs can be built in several ways in the MS Windows environment.
|
|
|
3643
|
|
|
3644 The standard way is what we call the "native" port. It uses the Win32
|
|
|
3645 API and has no connection with X whatsoever -- it does not require X
|
|
|
3646 libraries to build, nor does it require an X server to run. The native
|
|
|
3647 port is the most reliable version and provides the best graphical
|
|
|
3648 support. Almost all development is geared towards this version, and
|
|
|
3649 there is little reason not to use it.
|
|
|
3650
|
|
|
3651 The second way to build is the Cygwin port. It takes advantage of
|
|
2537
|
3652 Cygnus emulation library under Win32. @xref{Q1.2.5, What are Cygwin
|
|
2417
|
3653 and MinGW, and do I need them to run XEmacs?}, for more information.
|
|
|
3654
|
|
|
3655 A third way is the MinGW port. It uses the Cygwin environment to
|
|
2537
|
3656 build but does not require it at runtime. @xref{Q1.2.5, What are
|
|
2417
|
3657 Cygwin and MinGW, and do I need them to run XEmacs?}, for more
|
|
|
3658 information.
|
|
|
3659
|
|
|
3660 Finally, you might also be able to build the non-Cygwin, non-MinGW "X"
|
|
|
3661 port. This was actually the first version of XEmacs that ran under MS
|
|
|
3662 Windows, and although the code is still in XEmacs, it's essentially
|
|
|
3663 orphaned and it's unlikely it will compile without a lot of work. If
|
|
|
3664 you want an MS Windows versin of XEmacs that supports X, use the Cygwin
|
|
|
3665 version. (The X support there is actively maintained, so that Windows
|
|
|
3666 developers can test the X support in XEmacs.)
|
|
|
3667
|
|
2559
|
3668 @node Q2.3.2, Q2.3.3, Q2.3.1, Installation
|
|
|
3669 @unnumberedsubsec Q2.3.2: What compiler/libraries do I need to compile XEmacs?
|
|
2417
|
3670
|
|
|
3671 You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have
|
|
|
3672 some beta testers currently trying to compile with VC.NET, aka version
|
|
|
3673 7.0, but we can't yet report complete success.) For the Cygwin and
|
|
|
3674 MinGW versions, you need the Cygwin environment, which comes with GCC,
|
|
2537
|
3675 the compiler used for those versions. @xref{Q1.2.5, What are Cygwin
|
|
2417
|
3676 and MinGW, and do I need them to run XEmacs?}, for more information on
|
|
|
3677 Cygwin and MinGW.
|
|
|
3678
|
|
2559
|
3679 @node Q2.3.3, Q2.3.4, Q2.3.2, Installation
|
|
|
3680 @unnumberedsubsec Q2.3.3: How do I compile the native port?
|
|
2417
|
3681
|
|
|
3682 Please read the file @file{nt/README} in the XEmacs distribution, which
|
|
|
3683 contains the full description.
|
|
|
3684
|
|
2559
|
3685 @node Q2.3.4, Q2.3.5, Q2.3.3, Installation
|
|
|
3686 @unnumberedsubsec Q2.3.4: What do I need for Cygwin?
|
|
2417
|
3687
|
|
|
3688 You can find the Cygwin tools and compiler at:
|
|
|
3689
|
|
|
3690 @uref{http://www.cygwin.com/}
|
|
|
3691
|
|
|
3692 Click on the @samp{Install or update now!} link, which will download a
|
|
|
3693 file @file{setup.exe}, which you can use to download everything
|
|
|
3694 else. (You will need to pick a mirror site; @samp{mirrors.rcn.net} is
|
|
|
3695 probably the best.) You should go ahead and install everything --
|
|
|
3696 you'll get various ancillary libraries that XEmacs needs or likes,
|
|
|
3697 e.g. XPM, PNG, JPEG, TIFF, etc. You can also get X Windows here, if you
|
|
|
3698 want to compile under X.
|
|
|
3699
|
|
|
3700 If you want to compile without X, you will need the @file{xpm-nox}
|
|
|
3701 library, which must be specifically selected in the Cygwin netinstaller;
|
|
|
3702 it is not selected by default. The package has had various names.
|
|
|
3703 Currently it is called @file{cygXpm-noX4.dll}.
|
|
|
3704
|
|
2559
|
3705 @node Q2.3.5, Q2.3.6, Q2.3.4, Installation
|
|
|
3706 @unnumberedsubsec Q2.3.5: How do I compile under Cygwin?
|
|
2417
|
3707
|
|
|
3708 Similar as on Unix; use the usual `configure' and `make' process.
|
|
|
3709 Some problems to watch out for:
|
|
|
3710
|
|
|
3711 @itemize @bullet
|
|
|
3712 @item
|
|
|
3713 make sure HOME is set. This controls where you
|
|
|
3714 @file{init.el} file comes from;
|
|
|
3715
|
|
|
3716 @item
|
|
|
3717 @samp{CYGWIN} needs to be set to @samp{tty} for process support to work;
|
|
|
3718
|
|
|
3719 @item
|
|
|
3720 picking up some other grep or other UNIX-like tools can kill configure;
|
|
|
3721
|
|
|
3722 @item
|
|
|
3723 static heap too small, adjust @file{src/sheap-adjust.h} to a more positive
|
|
|
3724 number;
|
|
|
3725
|
|
|
3726 @item
|
|
|
3727 (Unconfirmed) The Cygwin version doesn't understand
|
|
|
3728 @file{//machine/path} type paths so you will need to manually mount a
|
|
|
3729 directory of this form under a unix style directory for a build to work
|
|
|
3730 on the directory;
|
|
|
3731
|
|
|
3732 @item
|
|
|
3733 If you're building @strong{WITHOUT} X11, don't forget to change symlinks
|
|
|
3734 @file{/usr/lib/libXpm.a} and @file{/usr/lib/libXpm.dll.a} to point to
|
|
|
3735 the non-X versions of these libraries. By default they point to the X
|
|
|
3736 versions. So:
|
|
|
3737
|
|
|
3738 @example
|
|
|
3739 /usr/lib/libXpm.a -> /usr/lib/libXpm-noX.a
|
|
|
3740 /usr/lib/libXpm.dll.a -> /usr/lib/libXpm-noX.dll.a
|
|
|
3741 @end example
|
|
|
3742
|
|
|
3743 (This advice may now be obsolete because of the availability of the
|
|
|
3744 cygXpm-noX4.dll package from Cygwin. Send confirmation to
|
|
|
3745 @email{faq@@xemacs.org}.)
|
|
|
3746
|
|
|
3747 @item
|
|
|
3748 Other problems are listed in the @file{PROBLEMS} file, in the top-level
|
|
|
3749 directory of the XEmacs sources.
|
|
|
3750
|
|
|
3751 @end itemize
|
|
|
3752
|
|
|
3753
|
|
2559
|
3754 @node Q2.3.6, Q2.3.7, Q2.3.5, Installation
|
|
|
3755 @unnumberedsubsec Q2.3.6: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
2417
|
3756
|
|
|
3757 Similar to the method for Unix. Things to remember:
|
|
|
3758
|
|
|
3759 @itemize @bullet
|
|
|
3760 @item
|
|
|
3761 Specify the target host on the command line for @file{./configure}, e.g.
|
|
|
3762 @samp{./configure i586-pc-mingw32}.
|
|
|
3763
|
|
|
3764 @item
|
|
|
3765 Be sure that your build directory is mounted such that it has the
|
|
|
3766 same path either as a cygwin path (@file{/build/xemacs}) or as a Windows
|
|
|
3767 path (@file{c:\build\xemacs}).
|
|
|
3768
|
|
|
3769 @item
|
|
|
3770 Build @samp{gcc -mno-cygwin} versions of the extra libs, i.e. @file{libpng},
|
|
|
3771 @file{compface}, etc.
|
|
|
3772
|
|
|
3773 @item
|
|
|
3774 Specify the target location of the extra libs on the command line
|
|
3018
|
3775 to @file{configure}, e.g.for 21.4 or earlier
|
|
|
3776 @samp{./configure --site-prefixes=/build/libs i586-pc-mingw32} and for
|
|
|
3777 21.5 or later
|
|
|
3778 @samp{./configure --with-site-prefixes=/build/libs i586-pc-mingw32}.
|
|
2417
|
3779 @end itemize
|
|
|
3780
|
|
2559
|
3781 @node Q2.3.7, Q2.3.8, Q2.3.6, Installation
|
|
|
3782 @unnumberedsubsec Q2.3.7: How do I compile with X support?
|
|
2417
|
3783
|
|
|
3784 To compile under Cygwin, all you need to do is install XFree86, which
|
|
|
3785 is available as part of the standard Cygwin installation.
|
|
|
3786 @uref{http://www.cygwin.com/}. Once installed, @file{configure}
|
|
|
3787 should automatically find the X libraries and compile with X support.
|
|
|
3788
|
|
|
3789 As noted above, the non-Cygwin X support is basically orphaned, and
|
|
|
3790 probably won't work. But if it want to try, it's described in
|
|
|
3791 @file{nt/README} in some detail. Basically, you need to get X11
|
|
2459
|
3792 libraries from @uref{http://ftp.x.org}, and compile them. If the
|
|
2417
|
3793 precompiled versions are available somewhere, we don't know of it.
|
|
|
3794
|
|
2559
|
3795 @node Q2.3.8, Q2.4.1, Q2.3.7, Installation
|
|
|
3796 @unnumberedsubsec Q2.3.8: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
1058
|
3797
|
|
|
3798 The Cygwin binary distributed with the netinstaller uses an external DLL
|
|
|
3799 to handle XPM images (such as toolbar buttons). You may get an error like
|
|
|
3800
|
|
2559
|
3801 @example
|
|
|
3802 This application has failed to start because cygXpm-noX4.dll was not found.
|
|
|
3803 Re-installing the application may fix this problem.
|
|
|
3804 @end example
|
|
1058
|
3805
|
|
|
3806 Andy Piper <andy@@xemacs.org> sez:
|
|
|
3807
|
|
2559
|
3808 @example
|
|
|
3809 cygXpm-noX4 is part of the cygwin distribution under libraries or
|
|
|
3810 graphics, but is not installed by default. You need to run the
|
|
|
3811 cygwin setup again and select this package.
|
|
|
3812 @end example
|
|
1058
|
3813
|
|
|
3814 Ie, reinstalling XEmacs won't help because it is not part of the XEmacs
|
|
|
3815 distribution.
|
|
|
3816
|
|
2559
|
3817 @unnumberedsec 2.4: General Troubleshooting
|
|
|
3818
|
|
|
3819 @node Q2.4.1, Q2.4.2, Q2.3.8, Installation
|
|
|
3820 @unnumberedsubsec Q2.4.1: How do I deal with bugs or with problems building, installing, or running?
|
|
|
3821
|
|
|
3822 The file @file{PROBLEMS} contains information on many common problems that
|
|
|
3823 occur in building, installing and running XEmacs.
|
|
|
3824
|
|
|
3825 Reports of bugs in XEmacs should be sent to
|
|
|
3826 @email{xemacs-beta@@xemacs.org}. You can also post to the newsgroup
|
|
|
3827 comp.emacs.xemacs (or equivalentlt, send to the mailing list
|
|
|
3828 @email{xemacs@@xemacs.org}), but it is less likely that the developers
|
|
|
3829 will see it in a timely fashion. @xref{Bugs,,, xemacs, the XEmacs
|
|
|
3830 User's Manual}, for more information on how to report bugs.
|
|
|
3831 @xref{Q1.4.2}, for more information on mailing lists relating to
|
|
|
3832 XEmacs.
|
|
|
3833
|
|
|
3834 There are three ways to read the Bugs section.
|
|
|
3835
|
|
|
3836 @enumerate
|
|
|
3837 @item
|
|
|
3838 In a printed copy of the XEmacs manual.
|
|
|
3839
|
|
|
3840 @item
|
|
|
3841 With Info. First, start XEmacs. From the menu, select
|
|
|
3842 @samp{Help->Info (Online Docs)->Info Contents} to enter Info, then
|
|
|
3843 click on @samp{XEmacs}, then on @samp{Bugs}. Or, use the keyboard: do
|
|
|
3844 @kbd{C-h i} to enter Info, then @kbd{m XEmacs RET} to get to the Emacs
|
|
|
3845 manual, then @kbd{m Bugs RET} to get to the section on bugs. Or use
|
|
|
3846 standalone Info in a like manner. (Standalone Info is part of the
|
|
|
3847 Texinfo distribution, not part of the XEmacs distribution.)
|
|
|
3848
|
|
|
3849 @item
|
|
|
3850 By hand. Do
|
|
|
3851 @example
|
|
|
3852 cat info/xemacs* | more "+/^File: xemacs.info, Node: Bugs,"
|
|
|
3853 @end example
|
|
|
3854 @end enumerate
|
|
|
3855
|
|
|
3856 @node Q2.4.2, Q2.4.3, Q2.4.1, Installation
|
|
|
3857 @unnumberedsubsec Q2.4.2: Help! XEmacs just crashed on me!
|
|
428
|
3858
|
|
|
3859 First of all, don't panic. Whenever XEmacs crashes, it tries extremely
|
|
|
3860 hard to auto-save all of your files before dying. (The main time that
|
|
|
3861 this will not happen is if the machine physically lost power or if you
|
|
|
3862 killed the XEmacs process using @code{kill -9}). The next time you try
|
|
|
3863 to edit those files, you will be informed that a more recent auto-save
|
|
|
3864 file exists. You can use @kbd{M-x recover-file} to retrieve the
|
|
|
3865 auto-saved version of the file.
|
|
|
3866
|
|
462
|
3867 You can use the command @kbd{M-x recover-session} after a crash to pick
|
|
|
3868 up where you left off.
|
|
428
|
3869
|
|
|
3870 Now, XEmacs is not perfect, and there may occasionally be times, or
|
|
|
3871 particular sequences of actions, that cause it to crash. If you can
|
|
|
3872 come up with a reproducible way of doing this (or even if you have a
|
|
|
3873 pretty good memory of exactly what you were doing at the time), the
|
|
2417
|
3874 maintainers would be very interested in knowing about it. The best
|
|
|
3875 way to report a bug is using @kbd{M-x report-emacs-bug} (or by
|
|
|
3876 selecting @samp{Send Bug Report...} from the Help menu). If that
|
|
|
3877 won't work (e.g. you can't get XEmacs working at all), send ordinary
|
|
|
3878 mail to @email{xemacs-beta@@xemacs.org}. @emph{MAKE SURE} to include
|
|
|
3879 the output from the crash, especially including the Lisp backtrace, as
|
|
|
3880 well as the XEmacs configuration from @kbd{M-x describe-installation}
|
|
|
3881 (or equivalently, the file @file{Installation} in the top of the build
|
|
|
3882 tree). Note that the developers do @emph{not} usually follow
|
|
|
3883 @samp{comp.emacs.xemacs} on a regular basis; thus, this is better for
|
|
|
3884 general questions about XEmacs than bug reports.
|
|
428
|
3885
|
|
1183
|
3886 If at all possible, include a C stack backtrace of the core dump that
|
|
2417
|
3887 was produced. This shows where exactly things went wrong, and makes
|
|
|
3888 it much easier to diagnose problems. To do this under Unix and Mac OS
|
|
|
3889 X, you need to locate the core file (it's called @file{core}, and is
|
|
|
3890 usually sitting in the directory that you started XEmacs from, or your
|
|
|
3891 home directory if that other directory was not writable). Then, go to
|
|
|
3892 that directory and execute a command like:
|
|
428
|
3893
|
|
|
3894 @example
|
|
|
3895 gdb `which xemacs` core
|
|
|
3896 @end example
|
|
|
3897
|
|
|
3898 and then issue the command @samp{where} to get the stack backtrace. You
|
|
|
3899 might have to use @code{dbx} or some similar debugger in place of
|
|
|
3900 @code{gdb}. If you don't have any such debugger available, complain to
|
|
|
3901 your system administrator.
|
|
|
3902
|
|
2417
|
3903 It's possible that a core file didn't get produced or the stack trace
|
|
|
3904 from gdb is garbage, in which case you're out of luck unless you can
|
|
|
3905 reproduce the bug. A nonexistent core file can happen in some
|
|
|
3906 circumstances on some operating systems, depending on what exactly
|
|
|
3907 triggered the crash. It's also possible, however, that your limits
|
|
|
3908 are set to turn them off. You may be able to reenable them using a
|
|
|
3909 command like @samp{unlimit coredumpsize} or @samp{ulimit -c}. (To find
|
|
|
3910 out how your limits are set, use the command @samp{limit}.) However, if
|
|
|
3911 you didn't explicitly set your limits this way, go complain to your
|
|
|
3912 system administrator and tell him not to disable core files by
|
|
|
3913 default.
|
|
|
3914
|
|
|
3915 A garbaged stack trace can happen for various reasons. Some versions
|
|
|
3916 of gdb are broken on certain operating systems and aren't able to read
|
|
|
3917 the core file. It's also possible that the stack got overwritten
|
|
|
3918 during the crash. A very simple reason, however, is that your version
|
|
|
3919 of XEmacs was compiled without debugging information or had the
|
|
|
3920 debugging information stripped. A compilation with optimization can
|
|
|
3921 also result in partly or completely garbaged stack trace. In such
|
|
|
3922 cases, you will need to recompile XEmacs with debugging information
|
|
2559
|
3923 and without optimization; @xref{Q2.4.4, How to debug an XEmacs problem
|
|
2417
|
3924 with a debugger}. Note also that core files currently don't work at
|
|
|
3925 all under Cygwin, and the only way to get a backtrace is to run XEmacs
|
|
|
3926 from gdb.
|
|
|
3927
|
|
|
3928 If you cannot get a backtrace from the core dump, but can reproduce
|
|
|
3929 the problem, try running XEmacs under gdb. The goal is to get clean C
|
|
|
3930 and Lisp backtraces and submit a bug report including full
|
|
|
3931 configuration information as described above, as this will greatly
|
|
|
3932 assist in the process of tracking down the bug. However, even partial
|
|
|
3933 information is better than none. The process of getting backtraces
|
|
2559
|
3934 from gdb is described in detail in @ref{Q2.4.4, How to debug an XEmacs
|
|
2417
|
3935 problem with a debugger}.
|
|
428
|
3936
|
|
1183
|
3937 If you're under Microsoft Windows, you're out of luck unless you happen
|
|
|
3938 to have a debugging aid installed on your system, for example Visual
|
|
|
3939 C++. In this case, the crash will result in a message giving you the
|
|
|
3940 option to enter a debugger (for example, by pressing @samp{Cancel}). Do
|
|
|
3941 this and locate the stack-trace window. (If your XEmacs was built
|
|
|
3942 without debugging information, the stack trace may not be very useful.)
|
|
|
3943
|
|
428
|
3944 When making a problem report make sure that:
|
|
|
3945
|
|
|
3946 @enumerate
|
|
|
3947 @item
|
|
|
3948 Report @strong{all} of the information output by XEmacs during the
|
|
|
3949 crash.
|
|
|
3950
|
|
|
3951 @item
|
|
2417
|
3952 You mention what O/S and Hardware you are running XEmacs on.
|
|
428
|
3953
|
|
|
3954 @item
|
|
|
3955 What version of XEmacs you are running.
|
|
|
3956
|
|
|
3957 @item
|
|
|
3958 What build options you are using.
|
|
|
3959
|
|
|
3960 @item
|
|
2417
|
3961 If the problem is related to graphics and you are running Unix or Mac
|
|
|
3962 OS X, we will also need to know what version of the X Window System
|
|
|
3963 you are running, and what window manager you are using.
|
|
1183
|
3964
|
|
|
3965 @item
|
|
|
3966 If the problem happened on a TTY, please include the terminal type.
|
|
2417
|
3967
|
|
|
3968 @item
|
|
|
3969 Try very hard to get both C and Lisp backtraces, as described above.
|
|
428
|
3970 @end enumerate
|
|
|
3971
|
|
1135
|
3972 Much of the information above is automatically generated by @kbd{M-x
|
|
|
3973 report-emacs-bug}. Even more, and often useful, information can be
|
|
|
3974 generated by redirecting the output of @code{make} and @code{make check}
|
|
|
3975 to a file (@file{beta.err} is the default used by @code{build-report}),
|
|
|
3976 and executing @kbd{M-x build-report}.
|
|
|
3977
|
|
2417
|
3978
|
|
2559
|
3979 @node Q2.4.3, Q2.4.4, Q2.4.2, Installation
|
|
|
3980 @unnumberedsubsec Q2.4.3: XEmacs crashes and I compiled it myself.
|
|
2417
|
3981
|
|
|
3982 There have been a variety of reports of crashes due to compilers with
|
|
|
3983 buggy optimizers. If you are compiling with optimization, consider
|
|
2559
|
3984 turning it off (@pxref{Q2.4.4, How to debug an XEmacs problem with a
|
|
2417
|
3985 debugger}) and recompiling.
|
|
|
3986
|
|
|
3987 Please see the @file{PROBLEMS} file that comes with XEmacs (it's in
|
|
|
3988 the top-level source directory) to read what it says about your
|
|
|
3989 platform.
|
|
|
3990
|
|
3018
|
3991 If you compiled XEmacs 21.4 or ealier using @samp{--use-union-type}, or
|
|
|
3992 21.5 or later using @samp{--enable-union-type} (or in either case used
|
|
|
3993 the option @samp{USE_UNION_TYPE} in @file{config.inc} under Windows),
|
|
|
3994 try recompiling again without it. The union type has been known to
|
|
|
3995 trigger compiler errors in a number of cases.
|
|
2417
|
3996
|
|
2559
|
3997 @node Q2.4.4, Q2.4.5, Q2.4.3, Installation
|
|
|
3998 @unnumberedsubsec Q2.4.4: How to debug an XEmacs problem with a debugger
|
|
428
|
3999
|
|
|
4000 If XEmacs does crash on you, one of the most productive things you can
|
|
|
4001 do to help get the bug fixed is to poke around a bit with the debugger.
|
|
|
4002 Here are some hints:
|
|
|
4003
|
|
|
4004 @itemize @bullet
|
|
|
4005 @item
|
|
|
4006 First of all, if the crash is at all reproducible, consider very
|
|
563
|
4007 strongly recompiling your XEmacs with debugging symbols and with no
|
|
|
4008 optimization (e.g. with GCC use the compiler flags @samp{-g -O0} --
|
|
|
4009 that's an "oh" followed by a zero), and with the configure options
|
|
3018
|
4010 @samp{--debug=yes} and @samp{--error-checking=all}
|
|
|
4011 (@samp{--enable-debug=yes} and @samp{--enable-error-checking=all} on
|
|
|
4012 XEmacs 21.5 or later). This will make your XEmacs run somewhat slower,
|
|
|
4013 but you are a lot more likely to catch the problem earlier (closer to
|
|
|
4014 its source). It makes it a lot easier to determine what's going on with
|
|
|
4015 a debugger. The way to control the compiler flags is with the
|
|
|
4016 configuration option @samp{--cflags} (@samp{--with-cflags} in 21.5). If
|
|
|
4017 you have a recent version of 21.5, you should use
|
|
2417
|
4018 @samp{--without-optimization} in preference to directly setting
|
|
|
4019 @samp{--cflags}.
|
|
1258
|
4020
|
|
|
4021 @item
|
|
|
4022 If it's not a true crash (@emph{i.e.}, XEmacs is hung, or a zombie
|
|
|
4023 process), or it's inconvenient to run XEmacs again because XEmacs is
|
|
|
4024 already running or is running in batch mode as part of a bunch of
|
|
|
4025 scripts, you may be able to attach to the existing process with your
|
|
2417
|
4026 debugger. Under Unix and Mac OS X, the typical way to do this is to
|
|
|
4027 first use some variant of the @samp{ps} command to figure out the
|
|
|
4028 process ID of XEmacs, for example @samp{ps -auxww | grep xemacs} under
|
|
|
4029 a BSD variant, @samp{ps -elf | grep xemacs} under Linux or System V,
|
|
|
4030 or @samp{ps -aW | grep xemacs} under Cygwin. Then run
|
|
|
4031
|
|
|
4032 @example
|
|
|
4033 gdb /path/to/xemacs/xemacs ####
|
|
|
4034 @end example
|
|
|
4035
|
|
|
4036 Where @code{####} is the process id of your XEmacs. (If you're not
|
|
|
4037 sure, try using @samp{which xemacs}.) When gdb attaches, the xemacs
|
|
|
4038 will stop and you can type @samp{where} in gdb to get a stack trace as
|
|
|
4039 usual. To get things moving again, you can just type @samp{quit} in
|
|
|
4040 gdb. It'll tell you the program is running and ask if you want to
|
|
|
4041 quit anyways. Say @samp{y} and it'll quit and have your emacs
|
|
|
4042 continue from where it was at.
|
|
|
4043
|
|
|
4044 If you're running another debugger, a similar method may work, or you
|
|
|
4045 may have to run the debugger first and then use the @code{attach}
|
|
|
4046 command or something similar.
|
|
|
4047
|
|
|
4048 Under Microsoft Windows, use the menu item @samp{Build->Start
|
|
|
4049 Debug->Attach to Process...} and select the XEmacs process from the list
|
|
|
4050 given.
|
|
1258
|
4051
|
|
|
4052 @item
|
|
|
4053 If you're able to run XEmacs under a debugger and reproduce the crash,
|
|
|
4054 here are some things you can do:
|
|
428
|
4055
|
|
|
4056 @item
|
|
|
4057 If XEmacs is hitting an assertion failure, put a breakpoint on
|
|
|
4058 @code{assert_failed()}.
|
|
|
4059
|
|
|
4060 @item
|
|
|
4061 If XEmacs is hitting some weird Lisp error that's causing it to crash
|
|
|
4062 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is
|
|
2417
|
4063 declared static in @file{eval.c}.
|
|
428
|
4064
|
|
|
4065 @item
|
|
563
|
4066 If XEmacs is outputting lots of X errors, put a breakpoint on
|
|
2417
|
4067 @code{x_error_handler()}; that will tell you which call is causing
|
|
|
4068 them. Note that the result may not be very useful by default because
|
|
|
4069 X Windows normally operates asynchronously: A bunch of commands are
|
|
|
4070 buffered up and then sent to the server all at once. This greatly
|
|
|
4071 improves performance over a network but means that an error may not be
|
|
|
4072 reported until the server receives the commands, which can be long
|
|
|
4073 after XEmacs made the erroneous calls. For best results, you need to
|
|
|
4074 make the X server synchronous before getting the backtrace. This can
|
|
|
4075 be done by starting XEmacs with the @samp{-sync} option or executing
|
|
|
4076 the Lisp code @code{(x-debug-mode t)}.
|
|
563
|
4077
|
|
|
4078 @item
|
|
428
|
4079 Internally, you will probably see lots of variables that hold objects of
|
|
1258
|
4080 type @code{Lisp_Object}. These are references to Lisp objects.
|
|
|
4081 Printing them out with the debugger probably won't be too
|
|
|
4082 useful---you'll likely just see a number. To decode them, do this:
|
|
428
|
4083
|
|
|
4084 @example
|
|
2417
|
4085 call debug_print (OBJECT)
|
|
428
|
4086 @end example
|
|
|
4087
|
|
|
4088 where @var{OBJECT} is whatever you want to decode (it can be a variable,
|
|
1258
|
4089 a function call, etc.). This uses the Lisp printing routines to out a
|
|
|
4090 readable representation on the TTY from which the xemacs process was
|
|
|
4091 invoked.
|
|
428
|
4092
|
|
2417
|
4093 Under 21.5 and later, @code{dp} is defined as an easier-to-type equivalent
|
|
|
4094 of @code{debug_print}. You can also try @code{dpa} if you can't see
|
|
|
4095 the output from @code{debug_print} (this will return a string containing
|
|
|
4096 the output), or use @code{debug_p3} if @code{debug_print} itself triggers
|
|
|
4097 a crash (this is a less comprehensive but super-safe way to print out
|
|
|
4098 a Lisp object).
|
|
|
4099
|
|
428
|
4100 @item
|
|
|
4101 If you want to get a Lisp backtrace showing the Lisp call
|
|
|
4102 stack, do this:
|
|
|
4103
|
|
|
4104 @example
|
|
2417
|
4105 call debug_backtrace ()
|
|
428
|
4106 @end example
|
|
|
4107
|
|
2417
|
4108 Under 21.5 and later, @code{db} is defined as an easier-to-type equivalent
|
|
|
4109 of @code{debug_backtrace}.
|
|
|
4110
|
|
|
4111 @item
|
|
|
4112 Using @code{debug_print} and @code{debug_backtrace} has two
|
|
|
4113 disadvantages - they can only be used with a running (including hung
|
|
|
4114 or zombie) xemacs process, and they do not display the internal C
|
|
|
4115 structure of a Lisp Object. Even if all you've got is a core dump,
|
|
|
4116 all is not lost.
|
|
428
|
4117
|
|
|
4118 If you're using GDB, there are some macros in the file
|
|
438
|
4119 @file{src/.gdbinit} in the XEmacs source distribution that should make
|
|
|
4120 it easier for you to decode Lisp objects. This file is automatically
|
|
|
4121 read by gdb if gdb is run in the directory where xemacs was built, and
|
|
|
4122 contains these useful macros to inspect the state of xemacs:
|
|
|
4123
|
|
|
4124 @table @code
|
|
|
4125 @item pobj
|
|
|
4126 Usage: pobj lisp_object @*
|
|
|
4127 Print the internal C representation of a lisp object.
|
|
|
4128
|
|
|
4129 @item xtype
|
|
|
4130 Usage: xtype lisp_object @*
|
|
|
4131 Print the Lisp type of a lisp object.
|
|
|
4132
|
|
|
4133 @item lbt
|
|
|
4134 Usage: lbt @*
|
|
|
4135 Print the current Lisp stack trace.
|
|
1258
|
4136 Requires a running xemacs process. (It works by calling the db
|
|
|
4137 routine described above.)
|
|
438
|
4138
|
|
|
4139 @item ldp
|
|
|
4140 Usage: ldp lisp_object @*
|
|
|
4141 Print a Lisp Object value using the Lisp printer.
|
|
1258
|
4142 Requires a running xemacs process. (It works by calling the dp
|
|
|
4143 routine described above.)
|
|
438
|
4144
|
|
|
4145 @item run-temacs
|
|
|
4146 Usage: run-temacs @*
|
|
|
4147 Run temacs interactively, like xemacs.
|
|
|
4148 Use this with debugging tools (like purify) that cannot deal with dumping,
|
|
|
4149 or when temacs builds successfully, but xemacs does not.
|
|
|
4150
|
|
|
4151 @item dump-temacs
|
|
|
4152 Usage: dump-temacs @*
|
|
|
4153 Run the dumping part of the build procedure.
|
|
|
4154 Use when debugging temacs, not xemacs!
|
|
|
4155 Use this when temacs builds successfully, but xemacs does not.
|
|
|
4156
|
|
|
4157 @item check-xemacs
|
|
|
4158 Usage: check-xemacs @*
|
|
|
4159 Run the test suite. Equivalent to 'make check'.
|
|
|
4160
|
|
|
4161 @item check-temacs
|
|
|
4162 Usage: check-temacs @*
|
|
|
4163 Run the test suite on temacs. Equivalent to 'make check-temacs'.
|
|
|
4164 Use this with debugging tools (like purify) that cannot deal with dumping,
|
|
|
4165 or when temacs builds successfully, but xemacs does not.
|
|
|
4166 @end table
|
|
428
|
4167
|
|
|
4168 If you are using Sun's @file{dbx} debugger, there is an equivalent file
|
|
438
|
4169 @file{src/.dbxrc}, which defines the same commands for dbx.
|
|
428
|
4170
|
|
|
4171 @item
|
|
|
4172 If you're using a debugger to get a C stack backtrace and you're seeing
|
|
|
4173 stack traces with some of the innermost frames mangled, it may be due to
|
|
|
4174 dynamic linking. (This happens especially under Linux.) Consider
|
|
3018
|
4175 reconfiguring with @samp{--dynamic=no} (@samp{--with-dynamic=no} in 21.5
|
|
|
4176 or later). Also, sometimes (again under Linux), stack backtraces of
|
|
|
4177 core dumps will have the frame where the fatal signal occurred mangled;
|
|
|
4178 if you can obtain a stack trace while running the XEmacs process under a
|
|
|
4179 debugger, the stack trace should be clean.
|
|
428
|
4180
|
|
1183
|
4181 @email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so
|
|
|
4182 version 1.8 if dynamic linking and debugging is a problem on Linux.
|
|
428
|
4183
|
|
|
4184 @item
|
|
|
4185 If you're using a debugger to get a C stack backtrace and you're
|
|
|
4186 getting a completely mangled and bogus stack trace, it's probably due to
|
|
|
4187 one of the following:
|
|
|
4188
|
|
|
4189 @enumerate a
|
|
|
4190 @item
|
|
|
4191 Your executable has been stripped. Bad news. Tell your sysadmin not to
|
|
|
4192 do this---it doesn't accomplish anything except to save a bit of disk
|
|
|
4193 space, and makes debugging much much harder.
|
|
|
4194
|
|
|
4195 @item
|
|
|
4196 Your stack is getting trashed. Debugging this is hard; you have to do a
|
|
|
4197 binary-search type of narrowing down where the crash occurs, until you
|
|
|
4198 figure out exactly which line is causing the problem. Of course, this
|
|
1258
|
4199 only works if the bug is highly reproducible. Also, in many cases if
|
|
|
4200 you run XEmacs from the debugger, the debugger can protect the stack
|
|
|
4201 somewhat. However, if the stack is being smashed, it is typically the
|
|
|
4202 case that there is a wild pointer somewhere in the program, often quite
|
|
|
4203 far from where the crash occurs.
|
|
428
|
4204
|
|
|
4205 @item
|
|
|
4206 If your stack trace has exactly one frame in it, with address 0x0, this
|
|
|
4207 could simply mean that XEmacs attempted to execute code at that address,
|
|
|
4208 e.g. through jumping to a null function pointer. Unfortunately, under
|
|
|
4209 those circumstances, GDB under Linux doesn't know how to get a stack
|
|
1183
|
4210 trace. (Yes, this is the fourth Linux-related problem I've mentioned. I
|
|
428
|
4211 have no idea why GDB under Linux is so bogus. Complain to the GDB
|
|
1183
|
4212 authors, or to comp.os.linux.development.system.) Again, you'll have to
|
|
428
|
4213 use the narrowing-down process described above.
|
|
|
4214
|
|
|
4215 @item
|
|
462
|
4216 You will get a Lisp backtrace output when XEmacs crashes, so you'll have
|
|
|
4217 something useful.
|
|
428
|
4218
|
|
|
4219 @end enumerate
|
|
|
4220
|
|
|
4221 @item
|
|
|
4222 If you compile with the newer gcc variants gcc-2.8 or egcs, you will
|
|
438
|
4223 also need gdb 4.17 or above. Earlier releases of gdb can't handle the
|
|
|
4224 debug information generated by the newer compilers.
|
|
428
|
4225
|
|
|
4226 @item
|
|
438
|
4227 In versions of XEmacs before 21.2.27, @file{src/.gdbinit} was named
|
|
|
4228 @file{src/gdbinit}. This had the disadvantage of not being sourced
|
|
|
4229 automatically by gdb, so you had to set that up yourself.
|
|
428
|
4230
|
|
1183
|
4231 @item
|
|
|
4232 If you are running Microsoft Windows, the the file @file{nt/README} for
|
|
|
4233 further information about debugging XEmacs.
|
|
|
4234
|
|
428
|
4235 @end itemize
|
|
|
4236
|
|
2559
|
4237 @node Q2.4.5, Q2.4.6, Q2.4.4, Installation
|
|
|
4238 @unnumberedsubsec Q2.4.5: I get a cryptic error message when trying to do something.
|
|
2417
|
4239
|
|
|
4240 When I try to use some particular option of some particular package, I
|
|
|
4241 get a cryptic error message in the minibuffer.
|
|
|
4242
|
|
|
4243 If the message went by too quickly, use @samp{Help->Recent Messages}
|
|
|
4244 from the menubar (or type @kbd{C-h l}) to see recent messages.
|
|
|
4245
|
|
|
4246 If you can't figure out what's going on, select
|
|
|
4247 @samp{Options->Troubleshooting->Debug on Error} from the menubar (or
|
|
|
4248 type @kbd{M-:} then @kbd{(setq debug-on-error t)}) then try and make
|
|
|
4249 the error happen again. This will put in the debugger (you can get
|
|
|
4250 out of this and continue what you were doing before by typing @kbd{c})
|
|
|
4251 and give you a backtrace that may be enlightening. If not, try
|
|
|
4252 reading through this FAQ; if that fails, you could try posting to
|
|
|
4253 @samp{comp.emacs.xemacs} (making sure to include the backtrace) and
|
|
|
4254 someone may be able to help. If you can identify which XEmacs Lisp
|
|
|
4255 source file the error is coming from you can get a more detailed stack
|
|
|
4256 backtrace by doing the following:
|
|
428
|
4257
|
|
|
4258 @enumerate
|
|
|
4259 @item
|
|
2417
|
4260 Visit the .el file in an XEmacs buffer.
|
|
|
4261
|
|
|
4262 @item
|
|
|
4263 Issue the command @kbd{M-x eval-current-buffer}.
|
|
|
4264
|
|
|
4265 @item
|
|
|
4266 Reproduce the error.
|
|
428
|
4267 @end enumerate
|
|
|
4268
|
|
2417
|
4269 For more information on debugging Lisp code, @xref{Debugging,,,
|
|
|
4270 lispref, XEmacs Lisp Reference Manual}.
|
|
|
4271
|
|
2559
|
4272 @node Q2.4.6, Q2.4.7, Q2.4.5, Installation
|
|
|
4273 @unnumberedsubsec Q2.4.6: XEmacs hangs when I try to do something.
|
|
2417
|
4274
|
|
|
4275 XEmacs might just be slow; some operations take a long time. XEmacs
|
|
|
4276 may also be waiting on a response from the network, for example when
|
|
|
4277 you are trying to send mail.
|
|
|
4278
|
|
|
4279 You can usually interrupt XEmacs by typing @kbd{C-g}. If not (for
|
|
|
4280 example, Lisp code explicitly disabled this by setting
|
|
|
4281 @code{inhibit-quit}), you can use the "critical quit" mechanism by
|
|
|
4282 typing @kbd{Control-Shift-G}. This should also pop you into the
|
|
|
4283 debugger and give you a backtrace, which can tell you where the
|
|
2559
|
4284 problem is (@pxref{Q2.4.4, How to debug an XEmacs problem with a
|
|
2417
|
4285 debugger}). (Note that setting @code{debug-on-quit} or selecting
|
|
|
4286 @samp{Options->Troubleshooting->Debug on Quit} will also cause regular
|
|
|
4287 @kbd{C-g} to enter the debugger and give you a backtrace.)
|
|
|
4288
|
|
|
4289 If you can't interrupt XEmacs this way, or for some reason XEmacs is
|
|
|
4290 not talking to the keyboard, you can try sending the @samp{SIGINT}
|
|
|
4291 signal using the @samp{kill} command.
|
|
|
4292
|
|
|
4293 If the Lisp backtrace isn't enlightening, or if XEmacs is so hung that
|
|
|
4294 you can't interrupt it at all, you could try attaching to the process
|
|
2559
|
4295 and getting a C stack backtrace. @xref{Q2.4.4, How to debug an XEmacs
|
|
2417
|
4296 problem with a debugger}.
|
|
|
4297
|
|
2559
|
4298 @node Q2.4.7, Q2.4.8, Q2.4.6, Installation
|
|
|
4299 @unnumberedsubsec Q2.4.7: I get an error message when XEmacs is running in batch mode.
|
|
2417
|
4300
|
|
|
4301 Typically this happens when you are trying to compile some Elisp code.
|
|
|
4302 If you are doing this as part of XEmacs or the XEmacs packages, you
|
|
|
4303 should automatically get a backtrace, which can help you determine the
|
|
|
4304 source of the problem. In other cases, you can get equivalent results
|
|
|
4305 by setting the environment variable @samp{XEMACSDEBUG} to @samp{(setq
|
|
|
4306 stack-trace-on-error t load-always-display-messages t
|
|
|
4307 load-ignore-out-of-date-elc-files t load-show-full-path-in-messages
|
|
|
4308 t)} (this needs to be all on one line; to set an environment variable,
|
|
|
4309 use @samp{export XEMACSDEBUG='FOO'} under @samp{bash}, @samp{zsh},
|
|
|
4310 etc. or @samp{setenv XEMACSDEBUG 'FOO'} under @samp{csh} and
|
|
|
4311 @samp{tcsh}). @samp{XEMACSDEBUG} specifies Lisp code that will be
|
|
|
4312 executed at startup time.
|
|
|
4313
|
|
|
4314 If the backtrace is not sufficiently useful in helping you diagnose
|
|
|
4315 the problem, you should consider using a debugger such as GDB.
|
|
2559
|
4316 @xref{Q2.4.4, How to debug an XEmacs problem with a debugger}. You
|
|
2417
|
4317 probably want to set a breakpoint on @code{signal_1}. Since such
|
|
|
4318 errors often occur during compiling, which is often triggered by a
|
|
|
4319 complex command run from a make suite, it may be easier to attach to
|
|
|
4320 the process once it's running.
|
|
|
4321
|
|
3018
|
4322 Under Microsoft Windows (and perhaps other operating systems), there is
|
|
|
4323 another useful trick you can do if you have configured with debugging
|
|
|
4324 support (configure option @samp{--debug} (@samp{--with-debug} in 21.5)
|
|
|
4325 or setting @samp{DEBUG_XEMACS} in @file{nt/config.inc}). Set the
|
|
|
4326 environment variable @samp{XEMACSDEBUG} (as described above) to
|
|
|
4327 @samp{(setq debug-on-error t)}. Then, when an error occurs
|
|
|
4328 noninteractively, instead of trying to invoke the Lisp debugger (which
|
|
|
4329 obviously won't work), XEmacs will break out to a C debugger using
|
|
2417
|
4330 @code{(force-debugging-signal t)}. @emph{NOTE}: This runs
|
|
|
4331 @code{abort()}!!! (As well as and after executing INT 3 under MS
|
|
|
4332 Windows, which should invoke a debugger if it's active.) This is
|
|
|
4333 guaranteed to kill XEmacs! (But in this situation, XEmacs is about to
|
|
|
4334 die anyway, and if no debugger is present, this will usefully dump
|
|
|
4335 core.)
|
|
|
4336
|
|
2559
|
4337 @node Q2.4.8, Q2.4.9, Q2.4.7, Installation
|
|
|
4338 @unnumberedsubsec Q2.4.8: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
2417
|
4339
|
|
|
4340 XEmacs has various facilities for debugging event handling.
|
|
|
4341
|
|
|
4342 First, try setting the variable @code{debug-emacs-events} to non-zero.
|
|
|
4343 This will output various information showing which events are being
|
|
|
4344 received and how they are being translated. This may show you, for
|
|
|
4345 example, that a key command is getting intercepted using
|
|
|
4346 @code{key-translation-map}; this problem can otherwise be very tricky
|
|
|
4347 to debug.
|
|
|
4348
|
|
|
4349 Under X, you can see exactly which events are being received from the
|
|
|
4350 window system by setting @code{x-debug-events} to non-zero. (The value
|
|
|
4351 @samp{1} gives you regular output, and @samp{2} gives you verbose
|
|
|
4352 output, including all parameters.)
|
|
|
4353
|
|
|
4354 A similar facility exists under MS Windows: Set
|
|
|
4355 @code{debug-mswindows-events} to non-zero. (The value @samp{1} gives
|
|
|
4356 you regular output. The value @samp{2} gives you verbose output,
|
|
|
4357 including all parameters. The value @samp{3} gives you
|
|
|
4358 super-gorily-detailed output.)
|
|
|
4359
|
|
2559
|
4360 @node Q2.4.9, Q2.4.10, Q2.4.8, Installation
|
|
|
4361 @unnumberedsubsec Q2.4.9: @kbd{C-g} doesn't work for me. Is it broken?
|
|
2417
|
4362
|
|
|
4363 @kbd{C-g} does work for most people in most circumstances. If it
|
|
|
4364 doesn't, there are two possible explanations:
|
|
|
4365
|
|
|
4366 @enumerate
|
|
|
4367 @item
|
|
|
4368 XEmacs is hung in a way that prevents @kbd{C-g} from working. This
|
|
|
4369 can happen when code is wrapped with a binding of @code{inhibit-quit}
|
|
|
4370 to @code{t}; you should still be able interrupt XEmacs using "critical
|
|
|
4371 quit". On the other hand, XEmacs may be seriously wedged. (If you're
|
|
|
4372 lucky, sending @samp{SIGINT} to the XEmacs process will interrupt it.)
|
|
2559
|
4373 @xref{Q2.4.6, XEmacs hangs when I try to do something.}.
|
|
2417
|
4374
|
|
|
4375 @item
|
|
|
4376 @kbd{C-g} is indeed broken on your system. To test, try executing
|
|
|
4377 @code{(while t)} from the @samp{*scratch*} buffer. If @kbd{C-g}
|
|
|
4378 doesn't interrupt, then it's broken. This used to happen with systems
|
|
|
4379 where @samp{SIGIO} was broken, but @samp{BROKEN_SIGIO} wasn't defined.
|
|
|
4380 However, there may not be very many such systems nowadays.
|
|
|
4381 @end enumerate
|
|
|
4382
|
|
2559
|
4383 @node Q2.4.10, Q2.4.11, Q2.4.9, Installation
|
|
|
4384 @unnumberedsubsec Q2.4.10: How do I debug process-related problems?
|
|
2417
|
4385
|
|
|
4386 Under MS Windows, you can set the variable
|
|
|
4387 @code{debug-mswindows-process-command-lines} to non-@samp{nil} to get
|
|
|
4388 information on exactly what is getting passed to a process. This can
|
|
|
4389 be useful in determining problems with quoting. (Under Unix, a process
|
|
|
4390 receives each argument separately, but under MS Windows a single
|
|
|
4391 command line is received, and arguments with spaces or other special
|
|
|
4392 characters in them must be quoted. Unfortunately this means that each
|
|
|
4393 process, potentially at least, has its own quoting conventions, and
|
|
|
4394 the code to process quoting conventions in @file{cmd.exe}, the Visual
|
|
|
4395 C++ startup code and the like is baroque and poorly documented.
|
|
|
4396 XEmacs uses the variable
|
|
|
4397 @code{mswindows-construct-process-command-line-alist} to construct a
|
|
|
4398 command line from a list of arguments based on the command to be run,
|
|
|
4399 but it is (and cannot be) a perfect solution.)
|
|
|
4400
|
|
2559
|
4401 @node Q2.4.11, Q2.4.12, Q2.4.10, Installation
|
|
|
4402 @unnumberedsubsec Q2.4.11: XEmacs is outputting lots of X errors.
|
|
563
|
4403
|
|
|
4404 If this is happening, we would very much like to know what's causing
|
|
2559
|
4405 them. To find this out, see @ref{Q2.4.4, How to debug an XEmacs
|
|
2417
|
4406 problem with a debugger}. Try to get both a C and Lisp backtrace, and
|
|
|
4407 send them along with the full error output to
|
|
|
4408 @email{xemacs-beta@@xemacs.org}.
|
|
|
4409
|
|
2559
|
4410 @node Q2.4.12, Q2.5.1, Q2.4.11, Installation
|
|
|
4411 @unnumberedsubsec Q2.4.12: After upgrading, XEmacs won't do `foo' any more!
|
|
2417
|
4412
|
|
|
4413 You have been used to doing `foo', but now when you invoke it (or
|
|
|
4414 click the toolbar button or select the menu item), nothing (or an
|
|
|
4415 error) happens. The simplest explanation is that you are missing a
|
|
|
4416 package that is essential to you. You can either track it down and
|
|
|
4417 install it (there is a list of packages and brief descriptions of
|
|
|
4418 their contents in @file{etc/PACKAGES}), or install the `Sumo Tarball'
|
|
2559
|
4419 (@pxref{Q2.1.2, How do I figure out which packages to install?}).
|
|
2417
|
4420
|
|
|
4421 @c #### should xref to XEmacs manual here
|
|
|
4422
|
|
2559
|
4423 @unnumberedsec 2.5: Startup-Related Problems
|
|
|
4424
|
|
|
4425 @node Q2.5.1, Q2.5.2, Q2.4.12, Installation
|
|
|
4426 @unnumberedsubsec Q2.5.1: XEmacs cannot connect to my X Terminal!
|
|
2417
|
4427
|
|
|
4428 Help! I can not get XEmacs to display on my Envizex X-terminal!
|
|
|
4429
|
|
|
4430 Try setting the @code{DISPLAY} variable using the numeric IP address of
|
|
|
4431 the host you are running XEmacs from.
|
|
|
4432
|
|
2559
|
4433 @node Q2.5.2, Q2.5.3, Q2.5.1, Installation
|
|
|
4434 @unnumberedsubsec Q2.5.2 Startup problems related to paths or package locations.
|
|
|
4435
|
|
|
4436 First of all, if XEmacs can't find the packages, check to make sure
|
|
|
4437 that you put the packages in the right place, or that you told XEmacs
|
|
|
4438 where to look for the packages when you compiled it. @xref{Q2.1.1}.
|
|
|
4439
|
|
|
4440 If something is still going wrong, or you get a startup warning about
|
|
|
4441 not being able to deduce some paths, you can get detailed information
|
|
|
4442 on the path-searching process at startup by setting the environment
|
|
|
4443 variable @samp{EMACSDEBUGPATHS} to a non-null value. One thing to
|
|
|
4444 look for if you're having package problems is the value of
|
|
|
4445 @samp{configure-package-path}. This corresponds to what was compiled
|
|
|
4446 into XEmacs using the @samp{--package-prefix} or @samp{--package-path}
|
|
|
4447 parameter (@pxref{Q2.1.1}). If this has the value of @samp{nil},
|
|
|
4448 this means that no value was compiled into XEmacs using these parameters.
|
|
|
4449
|
|
|
4450 @node Q2.5.3, Q2.5.4, Q2.5.2, Installation
|
|
|
4451 @unnumberedsubsec Q2.5.3: XEmacs won't start without network.
|
|
434
|
4452
|
|
|
4453 If XEmacs starts when you're on the network, but fails when you're not
|
|
|
4454 on the network, you may be missing a "localhost" entry in your
|
|
|
4455 @file{/etc/hosts} file. The file should contain an entry like:
|
|
|
4456
|
|
|
4457 @example
|
|
|
4458 127.0.0.1 localhost
|
|
|
4459 @end example
|
|
|
4460
|
|
|
4461 Add that line, and XEmacs will be happy.
|
|
|
4462
|
|
2559
|
4463 @node Q2.5.4, Q2.5.5, Q2.5.3, Installation
|
|
|
4464 @unnumberedsubsec Q2.5.4: Startup warnings about deducing proper fonts?
|
|
2417
|
4465
|
|
|
4466 How can I avoid the startup warnings about deducing proper fonts?
|
|
|
4467
|
|
|
4468 This is highly dependent on your installation, but try with the
|
|
|
4469 following font as your base font for XEmacs and see what it does:
|
|
|
4470
|
|
|
4471 @format
|
|
|
4472 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
|
|
|
4473 @end format
|
|
|
4474
|
|
|
4475 More precisely, do the following in your resource file:
|
|
|
4476
|
|
|
4477 @format
|
|
|
4478 Emacs.default.attributeFont: \
|
|
|
4479 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
|
|
|
4480 @end format
|
|
|
4481
|
|
|
4482 If you just don't want to see the @samp{*Warnings*} buffer at startup
|
|
|
4483 time, you can set this:
|
|
428
|
4484
|
|
|
4485 @lisp
|
|
2417
|
4486 (setq display-warning-minimum-level 'error)
|
|
428
|
4487 @end lisp
|
|
|
4488
|
|
2417
|
4489 The buffer still exists; it just isn't in your face.
|
|
|
4490
|
|
2559
|
4491 @node Q2.5.5, Q2.5.6, Q2.5.4, Installation
|
|
|
4492 @unnumberedsubsec Q2.5.5: Warnings from incorrect key modifiers.
|
|
2417
|
4493
|
|
|
4494 The following information comes from the @file{PROBLEMS} file that comes
|
|
|
4495 with XEmacs.
|
|
|
4496
|
|
|
4497 If you're having troubles with HP/UX it is because HP/UX defines the
|
|
|
4498 modifiers wrong in X. Here is a shell script to fix the problem; be
|
|
|
4499 sure that it is run after VUE configures the X server.
|
|
428
|
4500
|
|
|
4501 @example
|
|
2417
|
4502 #! /bin/sh
|
|
|
4503 xmodmap 2> /dev/null - << EOF
|
|
|
4504 keysym Alt_L = Meta_L
|
|
|
4505 keysym Alt_R = Meta_R
|
|
|
4506 EOF
|
|
|
4507
|
|
|
4508 xmodmap - << EOF
|
|
|
4509 clear mod1
|
|
|
4510 keysym Mode_switch = NoSymbol
|
|
|
4511 add mod1 = Meta_L
|
|
|
4512 keysym Meta_R = Mode_switch
|
|
|
4513 add mod2 = Mode_switch
|
|
|
4514 EOF
|
|
428
|
4515 @end example
|
|
|
4516
|
|
2559
|
4517 @node Q2.5.6, , Q2.5.5, Installation
|
|
|
4518 @unnumberedsubsec Q2.5.6: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
2417
|
4519
|
|
|
4520 Yes.
|
|
|
4521
|
|
|
4522 The console was there because @file{temacs} (and in turn, @file{xemacs})
|
|
|
4523 was a console application, and Windows typically creates a new
|
|
|
4524 console for a console process unless the creating process requests that
|
|
|
4525 one isn't created. This used to be fixed with @file{runemacs}, a small
|
|
|
4526 Windows application that existed merely to start @file{xemacs}, stating
|
|
|
4527 that it didn't want a console.
|
|
|
4528
|
|
|
4529 XEmacs 21.4 fixes this cleanly by the virtue of being a true "GUI"
|
|
|
4530 application. The explanation of what that means is included for
|
|
|
4531 educational value.
|
|
|
4532
|
|
|
4533 When building an application to be run in a Win32 environment, you must
|
|
|
4534 state which sub-system it is to run in. Valid subsystems include
|
|
|
4535 "console" and "gui". The subsystem you use affects the run time
|
|
|
4536 libraries linked into your application, the start up function that is
|
|
|
4537 run before control is handed over to your application, the entry point
|
|
|
4538 to your program, and how Windows normally invokes your program. (Console
|
|
|
4539 programs automatically get a console created for them at startup if
|
|
|
4540 their stdin/stdout don't point anywhere useful, which is the case when
|
|
|
4541 run from the GUI. This is a stupid design, of course -- instead, the
|
|
|
4542 console should get created only when the first I/O actually occurs!
|
|
|
4543 GUI programs have an equally stupid design: When called from
|
|
|
4544 @file{CMD.EXE}/@file{COMMAND.COM}, their stdin/stdout will be set to
|
|
|
4545 point nowhere useful, even though the command shell has its own
|
|
|
4546 stdin/stdout. It's as if someone who had learned a bit about stdio but
|
|
|
4547 had no actual knowledge of interprocess communication designed the
|
|
|
4548 scheme; unfortunately, the whole process-communication aspect of the
|
|
|
4549 Win32 API is equally badly designed.) For example, the entry point for a
|
|
|
4550 console app is "main" (which is what you'd expect for a C/C++ program),
|
|
|
4551 but the entry point for a "gui" app is "WinMain". This confuses and
|
|
|
4552 annoys a lot of programmers who've grown up on Unix systems, where the
|
|
|
4553 kernel doesn't really care whether your application is a gui program or
|
|
|
4554 not.
|
|
|
4555
|
|
|
4556 For reasons not altogether clear, and are lost in the mists of time and
|
|
|
4557 tradition, XEmacs on Win32 started out as a console application, and
|
|
|
4558 therefore a console was automatically created for it. (It may have been
|
|
|
4559 made a console application partly because a console is needed in some
|
|
|
4560 circumstances, especially under Win95, to interrupt, terminate, or send
|
|
|
4561 signals to a child process, and because of the bogosity mentioned above
|
|
|
4562 with GUI programs and the standard command shell. Currently, XEmacs
|
|
|
4563 just creates and immediately hides a console when necessary, and
|
|
|
4564 works around the "no useful stdio" problem by creating its own console
|
|
|
4565 window as necessary to display messages in.)
|
|
|
4566
|
|
2459
|
4567 @node Editing, Display, Installation, Top
|
|
|
4568 @unnumbered 3 Editing Functions
|
|
2417
|
4569
|
|
|
4570 This is part 3 of the XEmacs Frequently Asked Questions list. This
|
|
2459
|
4571 section is devoted to the editing-related capabilities of XEmacs (the
|
|
|
4572 keyboard, mouse, buffers, text selections, etc.) and how to customize
|
|
|
4573 them.
|
|
2417
|
4574
|
|
|
4575 @menu
|
|
|
4576 3.0: The Keyboard
|
|
2459
|
4577 * Q3.0.1:: How can I customize the keyboard?
|
|
|
4578 * Q3.0.2:: How can I bind complex functions (or macros) to keys?
|
|
|
4579 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down?
|
|
|
4580 * Q3.0.4:: Globally binding @kbd{Delete}?
|
|
|
4581 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
|
4582 * Q3.0.6:: How can you type in special characters in XEmacs?
|
|
|
4583 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys?
|
|
|
4584 * Q3.0.8:: How do I map the arrow keys?
|
|
|
4585 * Q3.0.9:: HP Alt key as Meta.
|
|
|
4586 * Q3.0.10:: Why does edt emulation not work?
|
|
|
4587 * Q3.0.11:: How can I emulate VI and use it as my default mode?
|
|
2417
|
4588
|
|
|
4589 3.1: The Mouse
|
|
|
4590 * Q3.1.1:: How can I turn off Mouse pasting?
|
|
|
4591 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons?
|
|
|
4592 * Q3.1.3:: Clicking the left button does not do anything in buffer list.
|
|
|
4593 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3?
|
|
2459
|
4594 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
|
4595
|
|
|
4596 3.2: Buffers, Text Editing
|
|
|
4597 * Q3.2.1:: Can I have the end of the buffer delimited in some way?
|
|
|
4598 * Q3.2.2:: How do I insert today's date into a buffer?
|
|
|
4599 * Q3.2.3:: How do I get a single minibuffer frame?
|
|
|
4600 * Q3.2.4:: How can I enable auto-indent and/or Filladapt?
|
|
|
4601 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
4602
|
|
|
4603 3.3: Text Selections
|
|
|
4604 * Q3.3.1:: How do I select a rectangular region?
|
|
|
4605 * Q3.3.2:: How can I turn off or change highlighted selections?
|
|
|
4606 * Q3.3.3:: How do I cause typing on an active region to remove it?
|
|
|
4607 * Q3.3.4:: Can I turn off the highlight during isearch?
|
|
|
4608 * Q3.3.5:: Why is killing so slow?
|
|
|
4609 * Q3.3.6:: Why does @kbd{M-w} take so long?
|
|
|
4610
|
|
|
4611 3.4: Editing Source Code
|
|
|
4612 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode?
|
|
|
4613 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly?
|
|
2417
|
4614 @end menu
|
|
|
4615
|
|
|
4616 @unnumberedsec 3.0: The Keyboard
|
|
|
4617
|
|
2459
|
4618 @node Q3.0.1, Q3.0.2, Editing, Editing
|
|
|
4619 @unnumberedsubsec Q3.0.1: How can I customize the keyboard?
|
|
|
4620
|
|
|
4621 #### Write me.
|
|
|
4622
|
|
|
4623 @node Q3.0.2, Q3.0.3, Q3.0.1, Editing
|
|
|
4624 @unnumberedsubsec Q3.0.2: How can I bind complex functions (or macros) to keys?
|
|
428
|
4625
|
|
|
4626 As an example, say you want the @kbd{paste} key on a Sun keyboard to
|
|
|
4627 insert the current Primary X selection at point. You can accomplish this
|
|
|
4628 with:
|
|
|
4629
|
|
|
4630 @lisp
|
|
|
4631 (define-key global-map [f18] 'x-insert-selection)
|
|
|
4632 @end lisp
|
|
|
4633
|
|
|
4634 However, this only works if there is a current X selection (the
|
|
|
4635 selection will be highlighted). The functionality I like is for the
|
|
|
4636 @kbd{paste} key to insert the current X selection if there is one,
|
|
|
4637 otherwise insert the contents of the clipboard. To do this you need to
|
|
|
4638 pass arguments to @code{x-insert-selection}. This is done by wrapping
|
|
|
4639 the call in a 'lambda form:
|
|
|
4640
|
|
|
4641 @lisp
|
|
|
4642 (global-set-key [f18]
|
|
|
4643 (lambda () (interactive) (x-insert-selection t nil)))
|
|
|
4644 @end lisp
|
|
|
4645
|
|
|
4646 This binds the f18 key to a @dfn{generic} functional object. The
|
|
|
4647 interactive spec is required because only interactive functions can be
|
|
|
4648 bound to keys.
|
|
|
4649
|
|
|
4650 For the FAQ example you could use:
|
|
|
4651
|
|
|
4652 @lisp
|
|
|
4653 (global-set-key [(control ?.)]
|
|
|
4654 (lambda () (interactive) (scroll-up 1)))
|
|
440
|
4655 (global-set-key [(control ?;)]
|
|
|
4656 (lambda () (interactive) (scroll-up -1)))
|
|
428
|
4657 @end lisp
|
|
|
4658
|
|
|
4659 This is fine if you only need a few functions within the lambda body.
|
|
2417
|
4660 If you're doing more it's cleaner to define a separate function.
|
|
2459
|
4661 @xref{Q3.0.3, How do I bind C-. and C-; to scroll one line up and
|
|
2417
|
4662 down?}.
|
|
|
4663
|
|
2459
|
4664 @node Q3.0.3, Q3.0.4, Q3.0.2, Editing
|
|
|
4665 @unnumberedsubsec Q3.0.3: How do I bind C-. and C-; to scroll one line up and down?
|
|
428
|
4666
|
|
|
4667 Add the following (Thanks to @email{mly@@adoc.xerox.com, Richard Mlynarik} and
|
|
|
4668 @email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}:
|
|
|
4669
|
|
|
4670 @lisp
|
|
|
4671 (defun scroll-up-one-line ()
|
|
|
4672 (interactive)
|
|
|
4673 (scroll-up 1))
|
|
|
4674
|
|
|
4675 (defun scroll-down-one-line ()
|
|
|
4676 (interactive)
|
|
|
4677 (scroll-down 1))
|
|
|
4678
|
|
|
4679 (global-set-key [(control ?.)] 'scroll-up-one-line) ; C-.
|
|
440
|
4680 (global-set-key [(control ?;)] 'scroll-down-one-line) ; C-;
|
|
428
|
4681 @end lisp
|
|
|
4682
|
|
|
4683 The key point is that you can only bind simple functions to keys; you
|
|
2417
|
4684 can not bind a key to a function that you're also passing arguments
|
|
2459
|
4685 to. (@pxref{Q3.0.2, How can I bind complex functions (or macros) to
|
|
2417
|
4686 keys?} for a better answer).
|
|
|
4687
|
|
2459
|
4688 @node Q3.0.4, Q3.0.5, Q3.0.3, Editing
|
|
|
4689 @unnumberedsubsec Q3.0.4: Globally binding @kbd{Delete}?
|
|
428
|
4690
|
|
|
4691 I cannot manage to globally bind my @kbd{Delete} key to something other
|
|
|
4692 than the default. How does one do this?
|
|
|
4693
|
|
462
|
4694 Answer: The problem is that many modes explicitly bind @kbd{Delete}. To
|
|
|
4695 get around this, try the following:
|
|
|
4696
|
|
428
|
4697 @lisp
|
|
|
4698 (defun foo ()
|
|
|
4699 (interactive)
|
|
|
4700 (message "You hit DELETE"))
|
|
|
4701
|
|
462
|
4702 (define-key key-translation-map 'delete 'redirected-delete)
|
|
|
4703 (global-set-key 'redirected-delete 'foo)
|
|
428
|
4704 @end lisp
|
|
|
4705
|
|
2459
|
4706 @node Q3.0.5, Q3.0.6, Q3.0.4, Editing
|
|
|
4707 @unnumberedsubsec Q3.0.5: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
428
|
4708
|
|
|
4709 The following works in GNU Emacs 19:
|
|
|
4710
|
|
|
4711 @lisp
|
|
|
4712 (global-set-key [help] 'help-command);; Help
|
|
|
4713 @end lisp
|
|
|
4714
|
|
462
|
4715 The following works in XEmacs with the addition of shift:
|
|
428
|
4716
|
|
|
4717 @lisp
|
|
|
4718 (global-set-key [(shift help)] 'help-command);; Help
|
|
|
4719 @end lisp
|
|
|
4720
|
|
|
4721 But it doesn't work alone. This is in the file @file{PROBLEMS} which
|
|
|
4722 should have come with your XEmacs installation: @emph{Emacs ignores the
|
|
|
4723 @kbd{help} key when running OLWM}.
|
|
|
4724
|
|
|
4725 OLWM grabs the @kbd{help} key, and retransmits it to the appropriate
|
|
|
4726 client using
|
|
|
4727 @iftex
|
|
|
4728 @*
|
|
|
4729 @end iftex
|
|
|
4730 @code{XSendEvent}. Allowing Emacs to react to synthetic
|
|
|
4731 events is a security hole, so this is turned off by default. You can
|
|
|
4732 enable it by setting the variable @code{x-allow-sendevents} to t. You
|
|
|
4733 can also cause fix this by telling OLWM to not grab the help key, with
|
|
|
4734 the null binding @code{OpenWindows.KeyboardCommand.Help:}.
|
|
|
4735
|
|
2459
|
4736 @node Q3.0.6, Q3.0.7, Q3.0.5, Editing
|
|
|
4737 @unnumberedsubsec Q3.0.6: How can you type in special characters in XEmacs?
|
|
428
|
4738 One way is to use the package @code{x-compose}. Then you can use
|
|
|
4739 sequences like @kbd{Compose " a} to get ä, etc.
|
|
|
4740
|
|
462
|
4741 Another way is to use the @code{iso-insert} package. Then you can use
|
|
|
4742 sequences like @kbd{C-x 8 " a} to get ä, etc.
|
|
428
|
4743
|
|
|
4744 @email{glynn@@sensei.co.uk, Glynn Clements} writes:
|
|
|
4745
|
|
|
4746 @quotation
|
|
|
4747 It depends upon your X server.
|
|
|
4748
|
|
|
4749 Generally, the simplest way is to define a key as Multi_key with
|
|
|
4750 xmodmap, e.g.
|
|
|
4751 @c hey, show some respect, willya -- there's xkeycaps, isn't there? --
|
|
|
4752 @c chr ;)
|
|
|
4753 @example
|
|
440
|
4754 xmodmap -e 'keycode 0xff20 = Multi_key'
|
|
428
|
4755 @end example
|
|
|
4756
|
|
|
4757 You will need to pick an appropriate keycode. Use xev to find out the
|
|
|
4758 keycodes for each key.
|
|
|
4759
|
|
|
4760 [NB: On a `Windows' keyboard, recent versions of XFree86 automatically
|
|
|
4761 define the right `Windows' key as Multi_key'.]
|
|
|
4762
|
|
|
4763 Once you have Multi_key defined, you can use e.g.
|
|
|
4764 @example
|
|
440
|
4765 Multi a ' => á
|
|
|
4766 Multi e " => ë
|
|
|
4767 Multi c , => ç
|
|
428
|
4768 @end example
|
|
|
4769
|
|
|
4770 etc.
|
|
|
4771
|
|
|
4772 Also, recent versions of XFree86 define various AltGr-<key>
|
|
|
4773 combinations as dead keys, i.e.
|
|
|
4774 @example
|
|
440
|
4775 AltGr [ => dead_diaeresis
|
|
|
4776 AltGr ] => dead_tilde
|
|
|
4777 AltGr ; => dead_acute
|
|
428
|
4778 @end example
|
|
|
4779 etc.
|
|
|
4780
|
|
|
4781 Running @samp{xmodmap -pk} will list all of the defined keysyms.
|
|
|
4782 @end quotation
|
|
|
4783
|
|
1135
|
4784 For the related problem of @emph{displaying} non-ASCII characters in a
|
|
2459
|
4785 non-Mule XEmacs, @xref{Q4.0.8, How do I display non-ASCII characters?}.
|
|
|
4786
|
|
|
4787 @node Q3.0.7, Q3.0.8, Q3.0.6, Editing
|
|
|
4788 @unnumberedsubsec Q3.0.7: Can I turn on @dfn{sticky} modifier keys?
|
|
428
|
4789
|
|
|
4790 Yes, with @code{(setq modifier-keys-are-sticky t)}. This will give the
|
|
|
4791 effect of being able to press and release Shift and have the next
|
|
|
4792 character typed come out in upper case. This will affect all the other
|
|
|
4793 modifier keys like Control and Meta as well.
|
|
|
4794
|
|
|
4795 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
|
4796
|
|
|
4797 @quotation
|
|
|
4798 One thing about the sticky modifiers is that if you move the mouse out
|
|
|
4799 of the frame and back in, it cancels all currently ``stuck'' modifiers.
|
|
|
4800 @end quotation
|
|
|
4801
|
|
2459
|
4802 @node Q3.0.8, Q3.0.9, Q3.0.7, Editing
|
|
|
4803 @unnumberedsubsec Q3.0.8: How do I map the arrow keys?
|
|
428
|
4804 @c New
|
|
|
4805 Say you want to map @kbd{C-@key{right}} to forward-word:
|
|
|
4806
|
|
|
4807 @email{sds@@usa.net, Sam Steingold} writes:
|
|
|
4808
|
|
|
4809 @quotation
|
|
|
4810 @lisp
|
|
|
4811 ; both XEmacs and Emacs
|
|
|
4812 (define-key global-map [(control right)] 'forward-word)
|
|
|
4813 @end lisp
|
|
|
4814 or
|
|
|
4815 @lisp
|
|
|
4816 ; Emacs only
|
|
|
4817 (define-key global-map [C-right] 'forward-word)
|
|
|
4818 @end lisp
|
|
|
4819 or
|
|
|
4820 @lisp
|
|
|
4821 ; ver > 20, both
|
|
|
4822 (define-key global-map (kbd "C-<right>") 'forward-word)
|
|
|
4823 @end lisp
|
|
|
4824 @end quotation
|
|
|
4825
|
|
2459
|
4826 @node Q3.0.9, Q3.0.10, Q3.0.8, Editing
|
|
|
4827 @unnumberedsubsec Q3.0.9: HP Alt key as Meta.
|
|
2417
|
4828
|
|
|
4829 How can I make XEmacs recognize the Alt key of my HP workstation as a
|
|
|
4830 Meta key?
|
|
|
4831
|
|
|
4832 Put the following line into a file and load it with xmodmap(1) before
|
|
|
4833 starting XEmacs:
|
|
428
|
4834
|
|
|
4835 @example
|
|
2417
|
4836 remove Mod1 = Mode_switch
|
|
428
|
4837 @end example
|
|
|
4838
|
|
2459
|
4839 @node Q3.0.10, Q3.0.11, Q3.0.9, Editing
|
|
|
4840 @unnumberedsubsec Q3.0.10: Why does edt emulation not work?
|
|
2417
|
4841
|
|
|
4842 We don't know, but you can use tpu-edt emulation instead, which works
|
|
|
4843 fine and is a little fancier than the standard edt emulation. To do
|
|
|
4844 this, add the following line to your @file{init.el}:
|
|
|
4845
|
|
|
4846 @lisp
|
|
|
4847 (tpu-edt)
|
|
|
4848 @end lisp
|
|
|
4849
|
|
|
4850 If you don't want it to replace @kbd{C-h} with an edt-style help menu
|
|
|
4851 add this as well:
|
|
428
|
4852
|
|
|
4853 @lisp
|
|
2417
|
4854 (global-set-key [(control h)] 'help-for-help)
|
|
428
|
4855 @end lisp
|
|
|
4856
|
|
2459
|
4857 @node Q3.0.11, Q3.1.1, Q3.0.10, Editing
|
|
|
4858 @unnumberedsubsec Q3.0.11: How can I emulate VI and use it as my default mode?
|
|
2417
|
4859
|
|
|
4860 Our recommended VI emulator is viper. To make viper-mode the default,
|
|
|
4861 add this to your @file{init.el}:
|
|
428
|
4862
|
|
|
4863 @lisp
|
|
2417
|
4864 (viper-mode)
|
|
428
|
4865 @end lisp
|
|
|
4866
|
|
2417
|
4867 @email{kifer@@CS.SunySB.EDU, Michael Kifer} writes:
|
|
|
4868
|
|
|
4869 @quotation
|
|
|
4870 This should be added as close to the top of @file{init.el} as you can get
|
|
|
4871 it, otherwise some minor modes may not get viper-ized.
|
|
|
4872 @end quotation
|
|
|
4873
|
|
|
4874 @unnumberedsec 3.1: The Mouse
|
|
|
4875
|
|
2459
|
4876 @node Q3.1.1, Q3.1.2, Q3.0.11, Editing
|
|
2417
|
4877 @unnumberedsubsec Q3.1.1: How can I turn off Mouse pasting?
|
|
428
|
4878
|
|
|
4879 I keep hitting the middle mouse button by accident and getting stuff
|
|
|
4880 pasted into my buffer so how can I turn this off?
|
|
|
4881
|
|
|
4882 Here is an alternative binding, whereby the middle mouse button selects
|
|
|
4883 (but does not cut) the expression under the mouse. Clicking middle on a
|
|
|
4884 left or right paren will select to the matching one. Note that you can
|
|
|
4885 use @code{define-key} or @code{global-set-key}.
|
|
|
4886
|
|
|
4887 @lisp
|
|
|
4888 (defun mouse-set-point-and-select (event)
|
|
|
4889 "Sets the point at the mouse location, then marks following form"
|
|
|
4890 (interactive "@@e")
|
|
|
4891 (mouse-set-point event)
|
|
|
4892 (mark-sexp 1))
|
|
|
4893 (define-key global-map [button2] 'mouse-set-point-and-select)
|
|
|
4894 @end lisp
|
|
|
4895
|
|
2459
|
4896 @node Q3.1.2, Q3.1.3, Q3.1.1, Editing
|
|
2417
|
4897 @unnumberedsubsec Q3.1.2: How do I set control/meta/etc modifiers on mouse buttons?
|
|
428
|
4898
|
|
|
4899 Use, for instance, @code{[(meta button1)]}. For example, here is a common
|
|
|
4900 setting for Common Lisp programmers who use the bundled @code{ilisp}
|
|
|
4901 package, whereby meta-button1 on a function name will find the file where
|
|
|
4902 the function name was defined, and put you at that location in the source
|
|
|
4903 file.
|
|
|
4904
|
|
|
4905 [Inside a function that gets called by the lisp-mode-hook and
|
|
|
4906 ilisp-mode-hook]
|
|
|
4907
|
|
|
4908 @lisp
|
|
|
4909 (local-set-key [(meta button1)] 'edit-definitions-lisp)
|
|
|
4910 @end lisp
|
|
|
4911
|
|
2459
|
4912 @node Q3.1.3, Q3.1.4, Q3.1.2, Editing
|
|
2417
|
4913 @unnumberedsubsec Q3.1.3: Clicking the left button does not do anything in buffer list.
|
|
428
|
4914
|
|
|
4915 I do @kbd{C-x C-b} to get a list of buffers and the entries get
|
|
|
4916 highlighted when I move the mouse over them but clicking the left mouse
|
|
|
4917 does not do anything.
|
|
|
4918
|
|
|
4919 Use the middle mouse button.
|
|
|
4920
|
|
2459
|
4921 @node Q3.1.4, Q3.1.5, Q3.1.3, Editing
|
|
2417
|
4922 @unnumberedsubsec Q3.1.4: How can I get a list of buffers when I hit mouse button 3?
|
|
428
|
4923
|
|
|
4924 The following code will replace the default popup on button3:
|
|
|
4925
|
|
|
4926 @lisp
|
|
|
4927 (global-set-key [button3] 'popup-buffer-menu)
|
|
|
4928 @end lisp
|
|
|
4929
|
|
2459
|
4930 @node Q3.1.5, Q3.2.1, Q3.1.4, Editing
|
|
|
4931 @unnumberedsubsec Q3.1.5: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
428
|
4932
|
|
|
4933 By default XEmacs pastes X selections where the mouse pointer is. How
|
|
|
4934 do I disable this?
|
|
|
4935
|
|
|
4936 Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank
|
|
|
4937 @key{RET}}.
|
|
|
4938
|
|
2417
|
4939 To get XEmacs to paste at the text cursor, add this your @file{init.el}:
|
|
428
|
4940
|
|
|
4941 @lisp
|
|
|
4942 (setq mouse-yank-at-point t)
|
|
|
4943 @end lisp
|
|
|
4944
|
|
2459
|
4945 You can also change this with Customize. Select from the
|
|
|
4946 @code{Options} menu @code{Advanced
|
|
|
4947 (Customize)->Emacs->Editing->Mouse->Yank At Point...} or type @kbd{M-x
|
|
|
4948 customize @key{RET} mouse @key{RET}}.
|
|
|
4949
|
|
|
4950 @unnumberedsec 3.2: Buffers, Text Editing
|
|
|
4951
|
|
|
4952 @node Q3.2.1, Q3.2.2, Q3.1.5, Editing
|
|
|
4953 @unnumberedsubsec Q3.2.1: Can I have the end of the buffer delimited in some way?
|
|
|
4954
|
|
|
4955 Say, with: @samp{[END]}?
|
|
|
4956
|
|
|
4957 Try this:
|
|
|
4958
|
|
|
4959 @lisp
|
|
|
4960 (let ((ext (make-extent (point-min) (point-max))))
|
|
|
4961 (set-extent-property ext 'start-closed t)
|
|
|
4962 (set-extent-property ext 'end-closed t)
|
|
|
4963 (set-extent-property ext 'detachable nil)
|
|
|
4964 (set-extent-end-glyph ext (make-glyph [string :data "[END]"])))
|
|
|
4965 @end lisp
|
|
|
4966
|
|
|
4967 Since this is XEmacs, you can specify an icon to be shown on
|
|
|
4968 window-system devices. To do so, change the @code{make-glyph} call to
|
|
|
4969 something like this:
|
|
|
4970
|
|
|
4971 @lisp
|
|
|
4972 (make-glyph '([xpm :file "~/something.xpm"]
|
|
|
4973 [string :data "[END]"]))
|
|
|
4974 @end lisp
|
|
|
4975
|
|
|
4976 You can inline the @sc{xpm} definition yourself by specifying
|
|
|
4977 @code{:data} instead of @code{:file}. Here is such a full-featured
|
|
|
4978 version that works on both X and TTY devices:
|
|
|
4979
|
|
|
4980 @lisp
|
|
|
4981 (let ((ext (make-extent (point-min) (point-max))))
|
|
|
4982 (set-extent-property ext 'start-closed t)
|
|
|
4983 (set-extent-property ext 'end-closed t)
|
|
|
4984 (set-extent-property ext 'detachable nil)
|
|
|
4985 (set-extent-end-glyph ext (make-glyph '([xpm :data "\
|
|
|
4986 /* XPM */
|
|
|
4987 static char* eye = @{
|
|
|
4988 \"20 11 7 2\",
|
|
|
4989 \"__ c None\"
|
|
|
4990 \"_` c #7f7f7f\",
|
|
|
4991 \"_a c #fefefe\",
|
|
|
4992 \"_b c #7f0000\",
|
|
|
4993 \"_c c #fefe00\",
|
|
|
4994 \"_d c #fe0000\",
|
|
|
4995 \"_e c #bfbfbf\",
|
|
|
4996 \"___________`_`_`___b_b_b_b_________`____\",
|
|
|
4997 \"_________`_`_`___b_c_c_c_b_b____________\",
|
|
|
4998 \"_____`_`_`_e___b_b_c_c_c___b___b_______`\",
|
|
|
4999 \"___`_`_e_a___b_b_d___b___b___b___b______\",
|
|
|
5000 \"_`_`_e_a_e___b_b_d_b___b___b___b___b____\",
|
|
|
5001 \"_`_`_a_e_a___b_b_d___b___b___b___b___b__\",
|
|
|
5002 \"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\",
|
|
|
5003 \"___`_`_e_a___b_b_b_d_c___b___b___d_b____\",
|
|
|
5004 \"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\",
|
|
|
5005 \"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\",
|
|
|
5006 \"___`_____`_`_`_`___b_b_b_b_b_b__________\",
|
|
|
5007 @} ;"]
|
|
|
5008 [string :data "[END]"]))))
|
|
|
5009 @end lisp
|
|
|
5010
|
|
|
5011 Note that you might want to make this a function, and put it to a hook.
|
|
|
5012 We leave that as an exercise for the reader.
|
|
|
5013
|
|
|
5014 @node Q3.2.2, Q3.2.3, Q3.2.1, Editing
|
|
|
5015 @unnumberedsubsec Q3.2.2: How do I insert today's date into a buffer?
|
|
2417
|
5016
|
|
|
5017 Like this:
|
|
428
|
5018
|
|
|
5019 @lisp
|
|
2459
|
5020 (insert (current-time-string))
|
|
2417
|
5021 @end lisp
|
|
|
5022
|
|
2459
|
5023 @node Q3.2.3, Q3.2.4, Q3.2.2, Editing
|
|
|
5024 @unnumberedsubsec Q3.2.3: How do I get a single minibuffer frame?
|
|
|
5025
|
|
|
5026 @email{acs@@acm.org, Vin Shelton} writes:
|
|
2417
|
5027
|
|
|
5028 @lisp
|
|
2459
|
5029 (setq initial-frame-plist '(minibuffer nil))
|
|
|
5030 (setq default-frame-plist '(minibuffer nil))
|
|
|
5031 (setq default-minibuffer-frame
|
|
|
5032 (make-frame
|
|
|
5033 '(minibuffer only
|
|
|
5034 width 86
|
|
|
5035 height 1
|
|
|
5036 menubar-visible-p nil
|
|
|
5037 default-toolbar-visible-p nil
|
|
|
5038 name "minibuffer"
|
|
|
5039 top -2
|
|
|
5040 left -2
|
|
|
5041 has-modeline-p nil)))
|
|
|
5042 (frame-notice-user-settings)
|
|
2417
|
5043 @end lisp
|
|
|
5044
|
|
2459
|
5045 @strong{Please note:} The single minibuffer frame may not be to everyone's
|
|
|
5046 taste, and there any number of other XEmacs options settings that may
|
|
|
5047 make it difficult or inconvenient to use.
|
|
|
5048
|
|
|
5049 @node Q3.2.4, Q3.2.5, Q3.2.3, Editing
|
|
|
5050 @unnumberedsubsec Q3.2.4: How can I enable auto-indent and/or Filladapt?
|
|
|
5051
|
|
|
5052 Put the following line in your @file{init.el}:
|
|
428
|
5053
|
|
|
5054 @lisp
|
|
2459
|
5055 (setq indent-line-function 'indent-relative-maybe)
|
|
428
|
5056 @end lisp
|
|
|
5057
|
|
2459
|
5058 If you want to get fancy, try the @code{filladapt} package available
|
|
|
5059 standard with XEmacs. Put this into your @file{init.el}:
|
|
428
|
5060
|
|
|
5061 @lisp
|
|
2459
|
5062 (require 'filladapt)
|
|
|
5063 (setq-default filladapt-mode t)
|
|
|
5064 (add-hook 'c-mode-hook 'turn-off-filladapt-mode)
|
|
428
|
5065 @end lisp
|
|
|
5066
|
|
2459
|
5067 This will enable Filladapt for all modes except C mode, where it doesn't
|
|
|
5068 work well. To turn Filladapt on only in particular major modes, remove
|
|
|
5069 the @code{(setq-default ...)} line and use
|
|
|
5070 @code{turn-on-filladapt-mode}, like this:
|
|
428
|
5071
|
|
|
5072 @lisp
|
|
2459
|
5073 (add-hook 'text-mode-hook 'turn-on-filladapt-mode)
|
|
428
|
5074 @end lisp
|
|
2417
|
5075
|
|
2459
|
5076 You can customize filling and adaptive filling with Customize.
|
|
|
5077 Select from the @code{Options} menu
|
|
|
5078 @code{Advanced (Customize)->Emacs->Editing->Fill->Fill...}
|
|
|
5079 or type @kbd{M-x customize @key{RET} fill @key{RET}}.
|
|
|
5080
|
|
|
5081 Note that well-behaving text-lookalike modes will run
|
|
|
5082 @code{text-mode-hook} by default (e.g. that's what Message does). For
|
|
|
5083 the nasty ones, you'll have to provide the @code{add-hook}s yourself.
|
|
|
5084
|
|
|
5085 Please note that the @code{fa-extras} package is no longer useful.
|
|
|
5086
|
|
|
5087 @node Q3.2.5, Q3.3.1, Q3.2.4, Editing
|
|
|
5088 @unnumberedsubsec Q3.2.5: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
5089
|
|
|
5090 Try the following lisp in your @file{init.el}:
|
|
2417
|
5091
|
|
|
5092 @lisp
|
|
2459
|
5093 (setq default-major-mode 'text-mode)
|
|
2769
|
5094 (add-hook 'text-mode-hook 'turn-on-auto-fill)
|
|
2417
|
5095 @end lisp
|
|
|
5096
|
|
2459
|
5097 @strong{WARNING}: note that changing the value of
|
|
|
5098 @code{default-major-mode} from @code{fundamental-mode} can break a large
|
|
|
5099 amount of built-in code that expects newly created buffers to be in
|
|
|
5100 @code{fundamental-mode}. (Changing from @code{fundamental-mode} to
|
|
|
5101 @code{text-mode} might not wreak too much havoc, but changing to
|
|
|
5102 something more exotic like a lisp-mode would break many Emacs packages).
|
|
|
5103
|
|
|
5104 Note that Emacs by default starts up in buffer @code{*scratch*} in
|
|
|
5105 @code{initial-major-mode}, which defaults to
|
|
|
5106 @code{lisp-interaction-mode}. Thus adding the following form to your
|
|
|
5107 Emacs init file will cause the initial @code{*scratch*} buffer to be put
|
|
|
5108 into auto-fill'ed @code{text-mode}:
|
|
2417
|
5109
|
|
|
5110 @lisp
|
|
2459
|
5111 (setq initial-major-mode
|
|
|
5112 (lambda ()
|
|
|
5113 (text-mode)
|
|
|
5114 (turn-on-auto-fill)))
|
|
2417
|
5115 @end lisp
|
|
|
5116
|
|
2459
|
5117 Note that after your init file is loaded, if
|
|
|
5118 @code{inhibit-startup-message} is @code{nil} (the default) and the
|
|
|
5119 startup buffer is @code{*scratch*} then the startup message will be
|
|
|
5120 inserted into @code{*scratch*}; it will be removed after a timeout by
|
|
|
5121 erasing the entire @code{*scratch*} buffer. Keep in mind this default
|
|
|
5122 usage of @code{*scratch*} if you desire any prior manipulation of
|
|
|
5123 @code{*scratch*} from within your Emacs init file. In particular,
|
|
|
5124 anything you insert into @code{*scratch*} from your init file will be
|
|
|
5125 later erased. Also, if you change the mode of the @code{*scratch*}
|
|
|
5126 buffer, be sure that this will not interfere with possible later
|
|
|
5127 insertion of the startup message (e.g. if you put @code{*scratch*} into
|
|
|
5128 a nonstandard mode that has automatic font lock rules, then the startup
|
|
|
5129 message might get fontified in a strange foreign manner, e.g. as code in
|
|
|
5130 some programming language).
|
|
|
5131
|
|
|
5132 @unnumberedsec 3.3: Text Selections
|
|
|
5133
|
|
|
5134 @node Q3.3.1, Q3.3.2, Q3.2.5, Editing
|
|
|
5135 @unnumberedsubsec Q3.3.1: How do I select a rectangular region?
|
|
2417
|
5136
|
|
|
5137 Just select the region normally, then use the rectangle commands (e.g.
|
|
|
5138 @code{kill-rectangle} on it. The region does not highlight as a
|
|
|
5139 rectangle, but the commands work just fine.
|
|
|
5140
|
|
|
5141 To actually sweep out rectangular regions with the mouse you can use
|
|
|
5142 @code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}.
|
|
|
5143 Then use rectangle commands.
|
|
|
5144
|
|
|
5145 You can also do the following to change default behavior to sweep out
|
|
|
5146 rectangular regions:
|
|
|
5147
|
|
|
5148 @lisp
|
|
|
5149 (setq mouse-track-rectangle-p t)
|
|
|
5150 @end lisp
|
|
|
5151
|
|
2459
|
5152 You can also change this with Customize.
|
|
2417
|
5153 Select from the @code{Options} menu
|
|
|
5154 @code{Advanced (Customize)->Emacs->Editing->Mouse->Track Rectangle...} or type
|
|
|
5155 @kbd{M-x customize @key{RET} mouse @key{RET}}.
|
|
|
5156
|
|
|
5157
|
|
|
5158 @example
|
|
|
5159 mouse-track-do-rectangle: (event)
|
|
|
5160 -- an interactive compiled Lisp function.
|
|
|
5161 Like `mouse-track' but selects rectangles instead of regions.
|
|
|
5162 @end example
|
|
|
5163
|
|
2459
|
5164 @node Q3.3.2, Q3.3.3, Q3.3.1, Editing
|
|
|
5165 @unnumberedsubsec Q3.3.2: How can I turn off or change highlighted selections?
|
|
428
|
5166
|
|
|
5167 The @code{zmacs} mode allows for what some might call gratuitous
|
|
|
5168 highlighting for selected regions (either by setting mark or by using
|
|
|
5169 the mouse). This is the default behavior. To turn off, add the
|
|
2417
|
5170 following line to your @file{init.el} file:
|
|
428
|
5171
|
|
|
5172 @lisp
|
|
|
5173 (setq zmacs-regions nil)
|
|
|
5174 @end lisp
|
|
|
5175
|
|
2417
|
5176 You can also change this with Customize. Select from the
|
|
|
5177 @code{Options} menu
|
|
|
5178 @code{Advanced (Customize)->Emacs->Editing->Basics->Zmacs Regions}
|
|
|
5179 or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
|
|
|
5180
|
|
|
5181 To change the face for selection, look at @code{Options->Advanced (Customize)}
|
|
|
5182 on the menubar.
|
|
|
5183
|
|
2459
|
5184 @node Q3.3.3, Q3.3.4, Q3.3.2, Editing
|
|
|
5185 @unnumberedsubsec Q3.3.3: How do I cause typing on an active region to remove it?
|
|
428
|
5186
|
|
|
5187 I want to change things so that if I select some text and start typing,
|
|
|
5188 the typed text replaces the selected text, similar to Motif.
|
|
|
5189
|
|
|
5190 You want to use something called @dfn{pending delete}. Pending delete
|
|
|
5191 is what happens when you select a region (with the mouse or keyboard)
|
|
|
5192 and you press a key to replace the selected region by the key you typed.
|
|
|
5193 Usually backspace kills the selected region.
|
|
|
5194
|
|
2164
|
5195 To get this behavior, ensure that you have the @file{pc} package
|
|
|
5196 installed, and add the following lines to your
|
|
2417
|
5197 @file{init.el}:
|
|
428
|
5198
|
|
|
5199 @lisp
|
|
438
|
5200 (cond
|
|
|
5201 ((fboundp 'turn-on-pending-delete)
|
|
|
5202 (turn-on-pending-delete))
|
|
|
5203 ((fboundp 'pending-delete-on)
|
|
|
5204 (pending-delete-on t)))
|
|
428
|
5205 @end lisp
|
|
|
5206
|
|
1138
|
5207 Note that this will work with both Backspace and Delete. This code is a
|
|
438
|
5208 tad more complicated than it has to be for XEmacs in order to make it
|
|
|
5209 more portable.
|
|
428
|
5210
|
|
2459
|
5211 @node Q3.3.4, Q3.3.5, Q3.3.3, Editing
|
|
|
5212 @unnumberedsubsec Q3.3.4: Can I turn off the highlight during isearch?
|
|
428
|
5213
|
|
|
5214 I do not like my text highlighted while I am doing isearch as I am not
|
|
|
5215 able to see what's underneath. How do I turn it off?
|
|
|
5216
|
|
2417
|
5217 Put the following in your @file{init.el}:
|
|
428
|
5218
|
|
|
5219 @lisp
|
|
|
5220 (setq isearch-highlight nil)
|
|
|
5221 @end lisp
|
|
|
5222
|
|
2459
|
5223 You can also change this with Customize. Type
|
|
428
|
5224 @kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}.
|
|
|
5225
|
|
|
5226 Note also that isearch-highlight affects query-replace and ispell.
|
|
|
5227 Instead of disabling isearch-highlight you may find that a better
|
|
|
5228 solution consists of customizing the @code{isearch} face.
|
|
|
5229
|
|
2459
|
5230 @node Q3.3.5, Q3.3.6, Q3.3.4, Editing
|
|
|
5231 @unnumberedsubsec Q3.3.5: Why is killing so slow?
|
|
892
|
5232
|
|
|
5233 This actually is an X Windows question, although you'll notice it with
|
|
|
5234 keyboard operations as well as while using the GUI. Basically, there
|
|
|
5235 are four ways to communicate interprogram via the X server:
|
|
|
5236
|
|
|
5237 @table @strong
|
|
|
5238 @item Primary selection
|
|
|
5239 a transient selection that gets replaced every time a new selection is made
|
|
|
5240
|
|
|
5241 @item Secondary selection
|
|
|
5242 for "exchanging" with the primary selection
|
|
|
5243
|
|
|
5244 @item Cut buffers
|
|
|
5245 a clipboard internal to the X server (deprecated)
|
|
|
5246
|
|
|
5247 @item Clipboard selection
|
|
|
5248 a selection with a notification protocol that allows a separate app to
|
|
|
5249 manage the clipboard
|
|
|
5250 @end table
|
|
|
5251
|
|
|
5252 The cut buffers are deprecated because managing them is even more
|
|
|
5253 inefficient than the clipboard notification protocol. The primary
|
|
|
5254 selection works fine for many users and applications, but is not very
|
|
|
5255 robust under intensive or sophisticated use.
|
|
|
5256
|
|
|
5257 In Motif and MS Windows, a clipboard has become the primary means for
|
|
|
5258 managing cut and paste. These means that "modern" applications tend to
|
|
|
5259 be oriented toward a true clipboard, rather than the primary selection.
|
|
|
5260 (On Windows, there is nothing equivalent to the primary selection.)
|
|
|
5261 It's not that XEmacs doesn't support the simple primary selection
|
|
|
5262 method, it's that more and more other applications don't.
|
|
|
5263
|
|
|
5264 So the slowdown occurs because XEmacs now engages in the clipboard
|
|
|
5265 notification protocol on @emph{every} kill. This is especially slow on
|
|
|
5266 Motif.
|
|
|
5267
|
|
|
5268 With most people running most clients and server on the same host, and
|
|
|
5269 many of the rest working over very fast communication, you may expect
|
|
|
5270 that the situation is not going to improve.
|
|
|
5271
|
|
|
5272 There are a number of workarounds. The most effective is to use a
|
|
|
5273 special command to do selection ownership only when you intend to paste
|
|
|
5274 to another application. Useful commands are @code{kill-primary-selection}
|
|
|
5275 and @code{copy-primary-selection}. These work only on text selected
|
|
|
5276 with the mouse (probably; experiment), and are bound by default to the
|
|
|
5277 @kbd{Cut} and @kbd{Copy}, respectively, buttons on the toolbar.
|
|
|
5278 @code{copy-primary-selection} is also bound to @kbd{C-Insert}. You can
|
|
|
5279 yank the clipboard contents with @code{yank-primary-selection}, bound to
|
|
|
5280 the @kbd{Paste} toolbar button and @kbd{Sh-Insert}.
|
|
|
5281
|
|
|
5282 If you are communicating by cut and paste with applications that use the
|
|
|
5283 primary selection, then you can customize
|
|
|
5284 @code{interprogram-cut-function} to @code{nil}, restoring the XEmacs
|
|
|
5285 version 20 behavior. How can you tell if a program will support this?
|
|
|
5286 Motifly-correct programs require the clipboard; you lose. For others,
|
|
|
5287 only by trying it. You also need to customize the complementary
|
|
|
5288 @code{interprogram-paste-function} to @code{nil}. (Otherwise
|
|
|
5289 XEmacs-to-XEmacs pastes will not work correctly.)
|
|
|
5290
|
|
|
5291 You may get some relief on Motif by setting
|
|
|
5292 @code{x-selection-strict-motif-ownership} to nil, but this means you will
|
|
|
5293 only intermittently be able to paste XEmacs kills to Motif applications.
|
|
|
5294
|
|
|
5295 Thanks to Jeff Mincy and Glynn Clements for corrections.
|
|
|
5296
|
|
2459
|
5297 @node Q3.3.6, Q3.4.1, Q3.3.5, Editing
|
|
|
5298 @unnumberedsubsec Q3.3.6: Why does @kbd{M-w} take so long?
|
|
2417
|
5299
|
|
|
5300 It actually doesn't. It leaves the region visible for a second so that
|
|
|
5301 you can see what area is being yanked. If you start working, though, it
|
|
|
5302 will immediately complete its operation. In other words, it will only
|
|
|
5303 delay for a second if you let it.
|
|
|
5304
|
|
2459
|
5305 @unnumberedsec 3.4: Editing Source Code
|
|
|
5306
|
|
|
5307 @node Q3.4.1, Q3.4.2, Q3.3.6, Editing
|
|
|
5308 @unnumberedsubsec Q3.4.1: I do not like cc-mode. How do I use the old c-mode?
|
|
2417
|
5309
|
|
|
5310 Well, first off, consider if you really want to do this. cc-mode is
|
|
|
5311 much more powerful than the old c-mode. If you're having trouble
|
|
|
5312 getting your old offsets to work, try using @code{c-set-offset} instead.
|
|
|
5313 You might also consider using the package @code{cc-compat}.
|
|
|
5314
|
|
|
5315 But, if you still insist, add the following lines to your @file{init.el}:
|
|
|
5316
|
|
|
5317 @lisp
|
|
|
5318 (fmakunbound 'c-mode)
|
|
|
5319 (makunbound 'c-mode-map)
|
|
|
5320 (fmakunbound 'c++-mode)
|
|
|
5321 (makunbound 'c++-mode-map)
|
|
|
5322 (makunbound 'c-style-alist)
|
|
|
5323 (load-library "old-c-mode")
|
|
|
5324 (load-library "old-c++-mode")
|
|
|
5325 @end lisp
|
|
|
5326
|
|
|
5327 This must be done before any other reference is made to either c-mode or
|
|
|
5328 c++-mode.
|
|
|
5329
|
|
2459
|
5330 @node Q3.4.2, , Q3.4.1, Editing
|
|
|
5331 @unnumberedsubsec Q3.4.2: How do you make XEmacs indent CL if-clauses correctly?
|
|
2417
|
5332
|
|
|
5333 I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the
|
|
|
5334 same amount instead of indenting the 3rd clause differently from the
|
|
|
5335 first two.
|
|
|
5336
|
|
2459
|
5337 The package @code{cl-indent} that comes with XEmacs sets up this kind
|
|
|
5338 of indentation by default. @code{cl-indent} also knows about many
|
|
|
5339 other CL-specific forms. To use @code{cl-indent}, one can do this:
|
|
2417
|
5340
|
|
|
5341 @lisp
|
|
2459
|
5342 (setq lisp-indent-function 'common-lisp-indent-function)
|
|
2417
|
5343 @end lisp
|
|
|
5344
|
|
|
5345 One can also customize @file{cl-indent.el} so it mimics the default
|
|
|
5346 @code{if} indentation @code{then} indented more than the @code{else}.
|
|
|
5347 Here's how:
|
|
|
5348
|
|
|
5349 @lisp
|
|
|
5350 (put 'if 'common-lisp-indent-function '(nil nil &body))
|
|
|
5351 @end lisp
|
|
|
5352
|
|
2459
|
5353 @node Display, External Subsystems, Editing, Top
|
|
|
5354 @unnumbered 4 Display Functions
|
|
428
|
5355
|
|
|
5356 This is part 4 of the XEmacs Frequently Asked Questions list. This
|
|
2459
|
5357 section is devoted to the display-related capabilities of XEmacs
|
|
|
5358 (fonts, colors, modeline, menubar, toolbar, scrollbar, etc.) and how
|
|
|
5359 to customize them.
|
|
|
5360
|
|
|
5361 @menu
|
|
|
5362 4.0: Textual Fonts and Colors
|
|
|
5363 * Q4.0.1:: How do I specify a font?
|
|
|
5364 * Q4.0.2:: How do I set the text, menu and modeline fonts?
|
|
|
5365 * Q4.0.3:: How can I set color options from @file{init.el}?
|
|
|
5366 * Q4.0.4:: How can I set the colors when highlighting a region?
|
|
|
5367 * Q4.0.5:: How can I limit color map usage?
|
|
|
5368 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them.
|
|
|
5369 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs?
|
|
|
5370 * Q4.0.8:: How do I display non-ASCII characters?
|
|
|
5371 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}.
|
|
|
5372
|
|
|
5373 4.1: Syntax Highlighting (Font Lock)
|
|
|
5374 * Q4.1.1:: How can I do source code highlighting using font-lock?
|
|
|
5375 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
5376
|
|
|
5377 4.2: The Modeline
|
|
|
5378 * Q4.2.1:: How can I make the modeline go away?
|
|
|
5379 * Q4.2.2:: How do you have XEmacs display the line number in the modeline?
|
|
|
5380 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline?
|
|
|
5381 * Q4.2.4:: How can I change the modeline color based on the mode used?
|
|
|
5382
|
|
|
5383 4.3: The Cursor
|
|
|
5384 * Q4.3.1:: Is there a way to make the bar cursor thicker?
|
|
|
5385 * Q4.3.2:: Is there a way to get back the block cursor?
|
|
|
5386 * Q4.3.3:: Can I make the cursor blink?
|
|
|
5387
|
|
|
5388 4.4: The Menubar
|
|
|
5389 * Q4.4.1:: How do I get rid of the menubar?
|
|
|
5390 * Q4.4.2:: How can I customize the menubar?
|
|
|
5391 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
5392 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
5393 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
5394
|
|
|
5395 4.5: The Toolbar
|
|
|
5396 * Q4.5.1:: How do I get rid of the toolbar?
|
|
|
5397 * Q4.5.2:: How can I customize the toolbar?
|
|
|
5398 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar?
|
|
|
5399 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar
|
|
|
5400
|
|
|
5401 4.6: Scrollbars and Scrolling
|
|
|
5402 * Q4.6.1:: How can I disable the scrollbar?
|
|
|
5403 * Q4.6.2:: How can I change the scrollbar width?
|
|
|
5404 * Q4.6.3:: How can I use resources to change scrollbar colors?
|
|
|
5405 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this?
|
|
|
5406 * Q4.6.5:: Scrolling one line at a time.
|
|
|
5407 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
5408 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
5409
|
|
|
5410 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
5411 * Q4.7.1:: How can I disable the gutter tabs?
|
|
|
5412 * Q4.7.2:: How can I disable the progress bar?
|
|
|
5413 * Q4.7.3:: There are bugs in the gutter or widgets.
|
|
|
5414 * Q4.7.4:: How can I customize the gutter or gutter tabs?
|
|
|
5415 @end menu
|
|
|
5416
|
|
|
5417 @unnumberedsec 4.0: Textual Fonts and Colors
|
|
|
5418
|
|
|
5419 @node Q4.0.1, Q4.0.2, Display, Display
|
|
|
5420 @unnumberedsubsec Q4.0.1: How do I specify a font?
|
|
|
5421
|
|
|
5422 #### Update me.
|
|
|
5423
|
|
|
5424 In 21.4 and above, you can use the @samp{Options} menu to change the font.
|
|
|
5425 You can also do it in your init file, e.g. like this (for MS Windows):
|
|
|
5426
|
|
|
5427 @display
|
|
|
5428 (set-face-font 'default "Lucida Console:Regular:10")
|
|
|
5429 (set-face-font 'modeline "MS Sans Serif:Regular:10")
|
|
|
5430 @end display
|
|
|
5431
|
|
|
5432 @node Q4.0.2, Q4.0.3, Q4.0.1, Display
|
|
|
5433 @unnumberedsubsec Q4.0.2: How do I set the text, menu and modeline fonts?
|
|
|
5434
|
|
|
5435 #### Update me.
|
|
|
5436
|
|
|
5437 Note that you should use @samp{Emacs.} and not @samp{Emacs*} when
|
|
|
5438 setting face values.
|
|
|
5439
|
|
|
5440 In @file{.Xresources}:
|
|
|
5441
|
|
|
5442 @example
|
|
|
5443 Emacs.default.attributeFont: -*-*-medium-r-*-*-*-120-*-*-m-*-*-*
|
|
|
5444 Emacs*menubar*font: fixed
|
|
|
5445 Emacs.modeline.attributeFont: fixed
|
|
|
5446 @end example
|
|
|
5447
|
|
|
5448 This is confusing because @samp{default} and @samp{modeline} are face
|
|
|
5449 names, and can be found listed with all faces in the current mode by
|
|
|
5450 using @kbd{M-x set-face-font (enter) ?}. They use the face-specific
|
|
|
5451 resource @samp{attributeFont}.
|
|
|
5452
|
|
|
5453 On the other hand, @samp{menubar} is a normal X thing that uses the
|
|
|
5454 resource @samp{font}. With Motif it @emph{may be} necessary to use
|
|
|
5455 @samp{fontList} @emph{instead of} @samp{font}. In @emph{non-Motif}
|
|
|
5456 configurations with Mule it @emph{is} necessary to use @samp{fontSet}
|
|
|
5457 instead of @samp{font}. (Sorry, there just is no simple recipe here.)
|
|
|
5458
|
|
|
5459 @node Q4.0.3, Q4.0.4, Q4.0.2, Display
|
|
|
5460 @unnumberedsubsec Q4.0.3: How can I set color options from @file{init.el}?
|
|
|
5461
|
|
|
5462 How can I set the most commonly used color options from my
|
|
|
5463 @file{init.el} instead of from my @file{.Xresources}?
|
|
|
5464
|
|
|
5465 Like this:
|
|
|
5466
|
|
|
5467 @lisp
|
|
|
5468 (set-face-background 'default "bisque") ; frame background
|
|
|
5469 (set-face-foreground 'default "black") ; normal text
|
|
|
5470 (set-face-background 'zmacs-region "red") ; When selecting w/
|
|
|
5471 ; mouse
|
|
|
5472 (set-face-foreground 'zmacs-region "yellow")
|
|
|
5473 (set-face-font 'default "*courier-bold-r*120-100-100*")
|
|
|
5474 (set-face-background 'highlight "blue") ; Ie when selecting
|
|
|
5475 ; buffers
|
|
|
5476 (set-face-foreground 'highlight "yellow")
|
|
|
5477 (set-face-background 'modeline "blue") ; Line at bottom
|
|
|
5478 ; of buffer
|
|
|
5479 (set-face-foreground 'modeline "white")
|
|
|
5480 (set-face-font 'modeline "*bold-r-normal*140-100-100*")
|
|
|
5481 (set-face-background 'isearch "yellow") ; When highlighting
|
|
|
5482 ; while searching
|
|
|
5483 (set-face-foreground 'isearch "red")
|
|
|
5484 (setq x-pointer-foreground-color "black") ; Adds to bg color,
|
|
|
5485 ; so keep black
|
|
|
5486 (setq x-pointer-background-color "blue") ; This is color
|
|
|
5487 ; you really
|
|
|
5488 ; want ptr/crsr
|
|
|
5489 @end lisp
|
|
|
5490
|
|
|
5491 @node Q4.0.4, Q4.0.5, Q4.0.3, Display
|
|
|
5492 @unnumberedsubsec Q4.0.4: How can I set the colors when highlighting a region?
|
|
|
5493
|
|
|
5494 How can I set the background/foreground colors when highlighting a
|
|
|
5495 region?
|
|
|
5496
|
|
|
5497 You can change the face @code{zmacs-region} either in your
|
|
|
5498 @file{.Xresources}:
|
|
|
5499
|
|
|
5500 @example
|
|
|
5501 Emacs.zmacs-region.attributeForeground: firebrick
|
|
|
5502 Emacs.zmacs-region.attributeBackground: lightseagreen
|
|
|
5503 @end example
|
|
|
5504
|
|
|
5505 or in your @file{init.el}:
|
|
|
5506
|
|
|
5507 @lisp
|
|
|
5508 (set-face-background 'zmacs-region "red")
|
|
|
5509 (set-face-foreground 'zmacs-region "yellow")
|
|
|
5510 @end lisp
|
|
|
5511
|
|
|
5512 @node Q4.0.5, Q4.0.6, Q4.0.4, Display
|
|
|
5513 @unnumberedsubsec Q4.0.5: How can I limit color map usage?
|
|
|
5514
|
|
|
5515 I'm using Netscape (or another color grabber like XEmacs);
|
|
|
5516 is there any way to limit the number of available colors in the color map?
|
|
|
5517
|
|
|
5518 Answer: No, but you can start Netscape before XEmacs, and it will use
|
|
|
5519 the closest available color if the colormap is full. You can also limit
|
|
|
5520 the number of colors Netscape uses, using the flags -mono, -ncols <#> or
|
|
|
5521 -install (for mono, limiting to <#> colors, or for using a private color
|
|
|
5522 map).
|
|
|
5523
|
|
|
5524 If you have the money, another solution would be to use a truecolor or
|
|
|
5525 direct color video.
|
|
|
5526
|
|
|
5527 @node Q4.0.6, Q4.0.7, Q4.0.5, Display
|
|
|
5528 @unnumberedsubsec Q4.0.6: My tty supports color, but XEmacs doesn't use them.
|
|
|
5529
|
|
|
5530 XEmacs tries to automatically determine whether your tty supports color,
|
|
|
5531 but sometimes guesses wrong. In that case, you can make XEmacs Do The
|
|
|
5532 Right Thing using this Lisp code:
|
|
|
5533
|
|
|
5534 @lisp
|
|
|
5535 (if (eq 'tty (device-type))
|
|
|
5536 (set-device-class nil 'color))
|
|
|
5537 @end lisp
|
|
|
5538
|
|
|
5539 @node Q4.0.7, Q4.0.8, Q4.0.6, Display
|
|
|
5540 @unnumberedsubsec Q4.0.7: Can I have pixmap backgrounds in XEmacs?
|
|
|
5541 @c New
|
|
|
5542 @email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes:
|
|
|
5543
|
|
|
5544 @quotation
|
|
|
5545 There are several ways to do it. For example, you could specify a
|
|
|
5546 default pixmap image to use in your @file{~/.Xresources}, e.g.,
|
|
|
5547
|
|
|
5548
|
|
|
5549 @example
|
|
|
5550 Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm
|
|
|
5551 @end example
|
|
|
5552
|
|
|
5553
|
|
|
5554 and then reload ~/.Xresources and restart XEmacs. Alternatively,
|
|
|
5555 since each face can have its own pixmap background, a better way
|
|
|
5556 would be to set a face's pixmap within your XEmacs init file, e.g.,
|
|
|
5557
|
|
|
5558 @lisp
|
|
|
5559 (set-face-background-pixmap 'default "/path/to/image.xpm")
|
|
|
5560 (set-face-background-pixmap 'bold "/path/to/another_image.xpm")
|
|
|
5561 @end lisp
|
|
|
5562
|
|
|
5563 and so on. You can also do this interactively via @kbd{M-x edit-faces}.
|
|
|
5564
|
|
|
5565 @end quotation
|
|
|
5566
|
|
|
5567 @node Q4.0.8, Q4.0.9, Q4.0.7, Display
|
|
|
5568 @unnumberedsubsec Q4.0.8: How do I display non-ASCII characters?
|
|
|
5569 @c New
|
|
|
5570
|
|
|
5571 If you're using a Mule-enabled XEmacs, then display is automatic. If
|
|
|
5572 you're not seeing the characters you expect, either (1) you don't have
|
|
|
5573 appropriate fonts available or (2) XEmacs did not correctly detect the
|
|
|
5574 coding system (@pxref{Recognize Coding, , , xemacs}). In case (1),
|
|
|
5575 install fonts as is customary for your platform. In case (2), you
|
|
|
5576 need to tell XEmacs explicitly what coding systems you're using.
|
|
|
5577 @ref{Specify Coding, , , xemacs}.
|
|
|
5578
|
|
|
5579 If your XEmacs is not Mule-enabled, and for some reason getting a
|
|
|
5580 Mule-enabled XEmacs seems like the wrong thing to do, all is not lost.
|
|
|
5581 You can arrange it by brute force. In @file{event-Xt.c} (suppress the
|
|
|
5582 urge to look in this file---play Doom instead, because you'll survive
|
|
|
5583 longer), it is written:
|
|
|
5584
|
|
|
5585 @quotation
|
|
|
5586 In a non-Mule world, a user can still have a multi-lingual editor, by
|
|
|
5587 doing @code{(set-face-font "-*-iso8859-2" (current-buffer))} for all
|
|
|
5588 their Latin-2 buffers, etc.
|
|
|
5589 @end quotation
|
|
|
5590
|
|
|
5591 For the related problem of @emph{inputting} non-ASCII characters in a
|
|
|
5592 non-Mule XEmacs, @xref{Q3.0.6, How can you type in special characters
|
|
|
5593 in XEmacs?}.
|
|
|
5594
|
|
|
5595 @node Q4.0.9, Q4.1.1, Q4.0.8, Display
|
|
|
5596 @unnumberedsubsec Q4.0.9: Font selections in don't get saved after @code{Save Options}.
|
|
|
5597
|
|
|
5598 @email{mannj@@ll.mit.edu, John Mann} writes:
|
|
|
5599
|
|
|
5600 @quotation
|
|
|
5601 You have to go to @samp{Options->Menubars} and unselect
|
|
|
5602 @samp{Frame-Local Font Menu}. If this option is selected, font changes
|
|
|
5603 are only applied to the @emph{current} frame and do @emph{not} get saved
|
|
|
5604 when you save options.
|
|
|
5605 @end quotation
|
|
|
5606
|
|
|
5607 Also, set the following in your @file{init.el}:
|
|
|
5608
|
|
|
5609 @lisp
|
|
|
5610 (setq options-save-faces t)
|
|
|
5611 @end lisp
|
|
|
5612
|
|
|
5613 @unnumberedsec 4.1: Syntax Highlighting (Font Lock)
|
|
|
5614
|
|
|
5615 @node Q4.1.1, Q4.1.2, Q4.0.9, Display
|
|
|
5616 @unnumberedsubsec Q4.1.1: How can I do source code highlighting using font-lock?
|
|
|
5617
|
|
|
5618 For most modes, font-lock is already set up and just needs to be turned
|
|
|
5619 on. This can be done by adding the line:
|
|
|
5620
|
|
|
5621 @lisp
|
|
|
5622 (require 'font-lock)
|
|
|
5623 @end lisp
|
|
|
5624
|
|
|
5625 to your @file{init.el}. (You can turn it on for the
|
|
|
5626 current buffer and session only by @kbd{M-x font-lock-mode}.) See the
|
|
|
5627 file @file{etc/sample.init.el} (@file{etc/sample.emacs} in XEmacs
|
|
|
5628 versions prior to 21.4) for more information.
|
|
|
5629
|
|
|
5630 @c the old way:
|
|
|
5631 @c (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
|
|
|
5632 @c (add-hook 'dired-mode-hook 'turn-on-font-lock)
|
|
|
5633
|
|
|
5634 See also @code{Syntax Highlighting} from the @code{Options} menu.
|
|
|
5635 Remember to save options.
|
|
|
5636
|
|
|
5637 @node Q4.1.2, Q4.2.1, Q4.1.1, Display
|
|
|
5638 @unnumberedsubsec Q4.1.2: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
5639
|
|
|
5640 Use the following code in your @file{init.el}:
|
|
|
5641
|
|
|
5642 @lisp
|
|
|
5643 (setq-default font-lock-maximum-decoration t)
|
|
|
5644 @end lisp
|
|
|
5645
|
|
|
5646 See also @code{Syntax Highlighting} from the @code{Options} menu.
|
|
|
5647 Remember to save options.
|
|
|
5648
|
|
|
5649 @unnumberedsec 4.2: The Modeline
|
|
|
5650
|
|
|
5651 @node Q4.2.1, Q4.2.2, Q4.1.2, Display
|
|
|
5652 @unnumberedsubsec Q4.2.1: How can I make the modeline go away?
|
|
|
5653
|
|
|
5654 @lisp
|
|
|
5655 (set-specifier has-modeline-p nil)
|
|
|
5656 @end lisp
|
|
|
5657
|
|
|
5658 @node Q4.2.2, Q4.2.3, Q4.2.1, Display
|
|
|
5659 @unnumberedsubsec Q4.2.2: How do you have XEmacs display the line number in the modeline?
|
|
|
5660
|
|
|
5661 Add the following line to your @file{init.el} file to
|
|
|
5662 display the line number:
|
|
|
5663
|
|
|
5664 @lisp
|
|
|
5665 (line-number-mode 1)
|
|
|
5666 @end lisp
|
|
|
5667
|
|
|
5668 Use the following to display the column number:
|
|
|
5669
|
|
|
5670 @lisp
|
|
|
5671 (column-number-mode 1)
|
|
|
5672 @end lisp
|
|
|
5673
|
|
|
5674 Or select from the @code{Options} menu
|
|
|
5675 @iftex
|
|
|
5676 @*
|
|
|
5677 @end iftex
|
|
|
5678 @code{Advanced (Customize)->Emacs->Editing->Basics->Line Number Mode}
|
|
|
5679 and/or
|
|
|
5680 @iftex
|
|
|
5681 @*
|
|
|
5682 @end iftex
|
|
|
5683 @code{Advanced (Customize)->Emacs->Editing->Basics->Column Number Mode}
|
|
|
5684
|
|
|
5685 Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
|
|
|
5686
|
|
|
5687 @node Q4.2.3, Q4.2.4, Q4.2.2, Display
|
|
|
5688 @unnumberedsubsec Q4.2.3: How do I get XEmacs to put the time of day on the modeline?
|
|
|
5689
|
|
|
5690 Add the following line to your @file{init.el} file to
|
|
|
5691 display the time:
|
|
|
5692
|
|
|
5693 @lisp
|
|
|
5694 (display-time)
|
|
|
5695 @end lisp
|
|
|
5696
|
|
|
5697 See @code{Customize} from the @code{Options} menu for customization.
|
|
|
5698
|
|
|
5699 @node Q4.2.4, Q4.3.1, Q4.2.3, Display
|
|
|
5700 @unnumberedsubsec Q4.2.4: How can I change the modeline color based on the mode used?
|
|
|
5701
|
|
|
5702 You can use something like the following:
|
|
|
5703
|
|
|
5704 @lisp
|
|
|
5705 (add-hook 'lisp-mode-hook
|
|
|
5706 (lambda ()
|
|
|
5707 (set-face-background 'modeline "red" (current-buffer))))
|
|
|
5708 @end lisp
|
|
|
5709
|
|
|
5710 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
|
|
|
5711 colors change from the default set in your @file{init.el}.
|
|
|
5712 The change will only be made in the buffer you just entered (which
|
|
|
5713 contains the Lisp file you are editing) and will not affect the modeline
|
|
|
5714 colors anywhere else.
|
|
|
5715
|
|
|
5716 Notes:
|
|
|
5717
|
|
|
5718 @itemize @bullet
|
|
|
5719
|
|
|
5720 @item The hook is the mode name plus @code{-hook}. eg. c-mode-hook,
|
|
|
5721 c++-mode-hook, emacs-lisp-mode-hook (used for your
|
|
|
5722 @file{init.el} or a @file{xx.el} file),
|
|
|
5723 lisp-interaction-mode-hook (the @samp{*scratch*} buffer),
|
|
|
5724 text-mode-hook, etc.
|
|
|
5725
|
|
|
5726 @item
|
|
|
5727 Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)},
|
|
|
5728 otherwise you will erase anything that anybody has already put on the
|
|
|
5729 hook.
|
|
|
5730
|
|
|
5731 @item
|
|
|
5732 You can also do @code{(set-face-font 'modeline @var{font})},
|
|
|
5733 eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*"
|
|
|
5734 (current-buffer))} if you wish the modeline font to vary based on the
|
|
|
5735 current mode.
|
|
|
5736 @end itemize
|
|
|
5737
|
|
|
5738 There are additional modeline faces, @code{modeline-buffer-id},
|
|
|
5739 @code{modeline-mousable}, and @code{modeline-mousable-minor-mode}, which
|
|
|
5740 you may want to customize.
|
|
|
5741
|
|
|
5742 @unnumberedsec 4.3: The Cursor
|
|
|
5743
|
|
|
5744 @node Q4.3.1, Q4.3.2, Q4.2.4, Display
|
|
|
5745 @unnumberedsubsec Q4.3.1: Is there a way to make the bar cursor thicker?
|
|
|
5746
|
|
|
5747 I'd like to have the bar cursor a little thicker, as I tend to "lose" it
|
|
|
5748 often.
|
|
|
5749
|
|
|
5750 For a 1 pixel bar cursor, use:
|
|
|
5751
|
|
|
5752 @lisp
|
|
|
5753 (setq bar-cursor t)
|
|
|
5754 @end lisp
|
|
|
5755
|
|
|
5756 For a 2 pixel bar cursor, use:
|
|
|
5757
|
|
|
5758 @lisp
|
|
|
5759 (setq bar-cursor 'anything-else)
|
|
|
5760 @end lisp
|
|
|
5761
|
|
|
5762 You can also change these with Customize.
|
|
|
5763 Select from the @code{Options} menu
|
|
|
5764 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
|
|
|
5765 @kbd{M-x customize @key{RET} display @key{RET}}.
|
|
|
5766
|
|
|
5767 You can use a color to make it stand out better:
|
|
|
5768
|
|
|
5769 @example
|
|
|
5770 Emacs*cursorColor: Red
|
|
|
5771 @end example
|
|
|
5772
|
|
|
5773 @node Q4.3.2, Q4.3.3, Q4.3.1, Display
|
|
|
5774 @unnumberedsubsec Q4.3.2: Is there a way to get back the block cursor?
|
|
|
5775
|
|
|
5776 @lisp
|
|
|
5777 (setq bar-cursor nil)
|
|
|
5778 @end lisp
|
|
|
5779
|
|
|
5780 You can also change this with Customize.
|
|
|
5781 Select from the @code{Options} menu
|
|
|
5782 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
|
|
|
5783 @kbd{M-x customize @key{RET} display @key{RET}}.
|
|
|
5784
|
|
|
5785 @node Q4.3.3, Q4.4.1, Q4.3.2, Display
|
|
|
5786 @unnumberedsubsec Q4.3.3: Can I make the cursor blink?
|
|
|
5787
|
|
|
5788 Yes, like this:
|
|
|
5789
|
|
|
5790 @lisp
|
|
|
5791 (blink-cursor-mode)
|
|
|
5792 @end lisp
|
|
|
5793
|
|
|
5794 This function toggles between a steady cursor and a blinking cursor.
|
|
|
5795 You may also set this mode from the menu bar by selecting
|
|
|
5796 @samp{Options->Display->Blinking Cursor}. Remember to save options.
|
|
|
5797
|
|
|
5798 @unnumberedsec 4.4: The Menubar
|
|
|
5799
|
|
|
5800 @node Q4.4.1, Q4.4.2, Q4.3.3, Display
|
|
|
5801 @unnumberedsubsec Q4.4.1: How do I get rid of the menubar?
|
|
|
5802
|
|
|
5803 @lisp
|
|
|
5804 (set-specifier menubar-visible-p nil)
|
|
|
5805 @end lisp
|
|
|
5806
|
|
|
5807 @node Q4.4.2, Q4.4.3, Q4.4.1, Display
|
|
|
5808 @unnumberedsubsec Q4.4.2: How can I customize the menubar?
|
|
|
5809
|
|
|
5810 For an extensive menubar, add this line to your @file{init.el}:
|
|
|
5811
|
|
|
5812 @lisp
|
|
|
5813 (load "big-menubar")
|
|
|
5814 @end lisp
|
|
|
5815
|
|
|
5816 If you'd like to write your own, this file provides as good a set of
|
|
|
5817 examples as any to start from. The file is located in edit-utils
|
|
|
5818 package.
|
|
|
5819
|
|
|
5820 @node Q4.4.3, Q4.4.4, Q4.4.2, Display
|
|
|
5821 @unnumberedsubsec Q4.4.3: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
5822
|
|
|
5823 #### Write me.
|
|
|
5824
|
|
|
5825 @node Q4.4.4, Q4.4.5, Q4.4.3, Display
|
|
|
5826 @unnumberedsubsec Q4.4.4: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
5827
|
|
|
5828 Add the following to your @file{init.el} (suit to fit):
|
|
|
5829
|
|
|
5830 @lisp
|
|
|
5831 (setq buffers-menu-max-size 20)
|
|
|
5832 @end lisp
|
|
|
5833
|
|
|
5834 For no limit, use an argument of @samp{nil}.
|
|
|
5835
|
|
|
5836 You can also change this with Customize. Select from the
|
|
|
5837 @code{Options} menu
|
|
|
5838 @code{Advanced (Customize)->Emacs->Environment->Menu->Buffers Menu->Max Size...}
|
|
|
5839 or type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}.
|
|
|
5840
|
|
|
5841 @node Q4.4.5, Q4.5.1, Q4.4.4, Display
|
|
|
5842 @unnumberedsubsec Q4.4.5: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
5843
|
|
|
5844 I am trying to use a resource like @code{Emacs*menubar*font} to set the
|
|
|
5845 font of the menubar but it's not working.
|
|
|
5846
|
|
|
5847 In Motif, the use of @samp{font} resources is obsoleted in order to
|
|
|
5848 support internationalization. If you are using the real Motif menubar,
|
|
|
5849 this resource is not recognized at all; you have to say:
|
|
|
5850
|
|
|
5851 @example
|
|
|
5852 Emacs*menubar*fontList: FONT
|
|
|
5853 @end example
|
|
|
5854
|
|
|
5855 If you are using the Lucid menubar, for backward compatibility with
|
|
|
5856 existing user configurations, the @samp{font} resource is recognized.
|
|
|
5857 Since this is not supported by Motif itself, the code is a kludge and
|
|
|
5858 the @samp{font} resource will be recognized only if the @samp{fontList}
|
|
|
5859 resource resource is unset. This means that the resource
|
|
|
5860
|
|
|
5861 @example
|
|
|
5862 *fontList: FONT
|
|
|
5863 @end example
|
|
|
5864
|
|
|
5865 will override
|
|
|
5866
|
|
|
5867 @example
|
|
|
5868 Emacs*menubar*font: FONT
|
|
|
5869 @end example
|
|
|
5870
|
|
|
5871 even though the latter is more specific.
|
|
|
5872
|
|
|
5873 In non-Motif configurations using @samp{--with-mule} and
|
|
|
5874 @samp{--with-xfs} it @emph{is} necessary to use the @code{fontSet}
|
|
|
5875 resource @emph{instead of} the @code{font} resource. The backward
|
|
|
5876 compatibility kludge was never implemented for non-Motif builds.
|
|
|
5877 Example:
|
|
|
5878
|
|
|
5879 @example
|
|
|
5880 *fontSet: FONT
|
|
|
5881 @end example
|
|
|
5882
|
|
|
5883 @unnumberedsec 4.5: The Toolbar
|
|
|
5884
|
|
|
5885 @node Q4.5.1, Q4.5.2, Q4.4.5, Display
|
|
|
5886 @unnumberedsubsec Q4.5.1: How do I get rid of the toolbar?
|
|
|
5887
|
|
|
5888 #### Write me.
|
|
|
5889
|
|
|
5890 @node Q4.5.2, Q4.5.3, Q4.5.1, Display
|
|
|
5891 @unnumberedsubsec Q4.5.2: How can I customize the toolbar?
|
|
|
5892
|
|
|
5893 #### Write me.
|
|
|
5894
|
|
|
5895 @node Q4.5.3, Q4.5.4, Q4.5.2, Display
|
|
|
5896 @unnumberedsubsec Q4.5.3: How can I bind a key to a function to toggle the toolbar?
|
|
|
5897
|
|
|
5898 Try something like:
|
|
|
5899
|
|
|
5900 @lisp
|
|
|
5901 (defun my-toggle-toolbar ()
|
|
|
5902 (interactive)
|
|
|
5903 (set-specifier default-toolbar-visible-p
|
|
|
5904 (not (specifier-instance default-toolbar-visible-p))))
|
|
|
5905 (global-set-key "\C-xT" 'my-toggle-toolbar)
|
|
|
5906 @end lisp
|
|
|
5907
|
|
|
5908 @ignore
|
|
|
5909 @c Probably not relevant any more
|
|
|
5910 There are redisplay bugs in 19.14 that may make the preceding result in
|
|
|
5911 a messed-up display, especially for frames with multiple windows. You
|
|
|
5912 may need to resize the frame before XEmacs completely realizes the
|
|
|
5913 toolbar is really gone.
|
|
|
5914 @end ignore
|
|
|
5915
|
|
|
5916 Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct
|
|
|
5917 code.
|
|
|
5918
|
|
|
5919 @node Q4.5.4, Q4.6.1, Q4.5.3, Display
|
|
|
5920 @unnumberedsubsec Q4.5.4: @samp{Can't instantiate image error...} in toolbar
|
|
|
5921
|
|
|
5922 @email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes:
|
|
|
5923
|
|
|
5924 I just installed the XEmacs (20.4-2) RPMS that I downloaded from
|
|
|
5925 @uref{http://www.xemacs.org/}. Everything works fine, except that when
|
|
|
5926 I place my mouse over the toolbar, it beeps and gives me this message:
|
|
|
5927
|
|
|
5928 @example
|
|
|
5929 Can't instantiate image (probably cached):
|
|
|
5930 [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data
|
|
|
5931 (16 16 <strange control characters> ...
|
|
|
5932 @end example
|
|
|
5933
|
|
|
5934 @email{kyle_jones@@wonderworks.com, Kyle Jones} writes:
|
|
|
5935 @quotation
|
|
|
5936 This is problem specific to some Chips and Technologies video
|
|
|
5937 chips, when running XFree86. Putting
|
|
|
5938
|
|
|
5939 @code{Option "sw_cursor"}
|
|
|
5940
|
|
|
5941 in @file{XF86Config} gets rid of the problem.
|
|
|
5942 @end quotation
|
|
|
5943
|
|
|
5944 @unnumberedsec 4.6: Scrollbars and Scrolling
|
|
|
5945
|
|
|
5946 @node Q4.6.1, Q4.6.2, Q4.5.4, Display
|
|
|
5947 @unnumberedsubsec Q4.6.1: How can I disable the scrollbar?
|
|
|
5948
|
|
|
5949 To disable them for all frames, add the following line to
|
|
|
5950 your @file{.Xresources}:
|
|
|
5951
|
|
|
5952 @example
|
|
|
5953 Emacs.scrollBarWidth: 0
|
|
|
5954 @end example
|
|
|
5955
|
|
|
5956 Or select @samp{Options->Display->Scrollbars}.
|
|
|
5957 Remember to save options.
|
|
|
5958
|
|
|
5959 To turn the scrollbar off on a per-frame basis, use the following
|
|
|
5960 function:
|
|
|
5961
|
|
|
5962 @lisp
|
|
|
5963 (set-specifier scrollbar-width 0 (selected-frame))
|
|
|
5964 @end lisp
|
|
|
5965
|
|
|
5966 You can actually turn the scrollbars on at any level you want by
|
|
|
5967 substituting for (selected-frame) in the above command. For example, to
|
|
|
5968 turn the scrollbars off only in a single buffer:
|
|
|
5969
|
|
|
5970 @lisp
|
|
|
5971 (set-specifier scrollbar-width 0 (current-buffer))
|
|
|
5972 @end lisp
|
|
|
5973
|
|
|
5974 @node Q4.6.2, Q4.6.3, Q4.6.1, Display
|
|
|
5975 @unnumberedsubsec Q4.6.2: How can I change the scrollbar width?
|
|
|
5976
|
|
|
5977 #### Write me.
|
|
|
5978
|
|
|
5979 @node Q4.6.3, Q4.6.4, Q4.6.2, Display
|
|
|
5980 @unnumberedsubsec Q4.6.3: How can I use resources to change scrollbar colors?
|
|
|
5981
|
|
|
5982 Here's a recap of how to use resources to change your scrollbar colors:
|
|
|
5983
|
|
|
5984 @example
|
|
|
5985 ! Motif scrollbars
|
|
|
5986
|
|
|
5987 Emacs*XmScrollBar.Background: skyblue
|
|
|
5988 Emacs*XmScrollBar.troughColor: lightgray
|
|
|
5989
|
|
|
5990 ! Athena scrollbars
|
|
|
5991
|
|
|
5992 Emacs*Scrollbar.Foreground: skyblue
|
|
|
5993 Emacs*Scrollbar.Background: lightgray
|
|
|
5994 @end example
|
|
|
5995
|
|
|
5996 Note the capitalization of @code{Scrollbar} for the Athena widget.
|
|
|
5997
|
|
|
5998 @node Q4.6.4, Q4.6.5, Q4.6.3, Display
|
|
|
5999 @unnumberedsubsec Q4.6.4: Moving the scrollbar can move the point; can I disable this?
|
|
|
6000
|
|
|
6001 When I move the scrollbar in an XEmacs window, it moves the point as
|
|
|
6002 well, which should not be the default behavior. Is this a bug or a
|
|
|
6003 feature? Can I disable it?
|
|
|
6004
|
|
|
6005 The current behavior is a feature, not a bug. Point remains at the same
|
|
|
6006 buffer position as long as that position does not scroll off the screen.
|
|
|
6007 In that event, point will end up in either the upper-left or lower-left
|
|
|
6008 hand corner.
|
|
|
6009
|
|
|
6010 This cannot be changed.
|
|
|
6011
|
|
|
6012 @node Q4.6.5, Q4.6.6, Q4.6.4, Display
|
|
|
6013 @unnumberedsubsec Q4.6.5: Scrolling one line at a time.
|
|
|
6014
|
|
|
6015 Can the cursor keys scroll the screen a line at a time, rather than the
|
|
|
6016 default half page jump? I tend it to find it disorienting.
|
|
|
6017
|
|
|
6018 Use the following:
|
|
|
6019
|
|
|
6020 @lisp
|
|
|
6021 (setq scroll-step 1)
|
|
|
6022 @end lisp
|
|
|
6023
|
|
|
6024 You can also change this with Customize. Select from the
|
|
|
6025 @code{Options} menu
|
|
|
6026 @code{Advanced (Customize)->Emacs->Environment->Windows->Scroll Step...}
|
|
|
6027 or type @kbd{M-x customize @key{RET} windows @key{RET}}.
|
|
|
6028
|
|
|
6029 @node Q4.6.6, Q4.6.7, Q4.6.5, Display
|
|
|
6030 @unnumberedsubsec Q4.6.6: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
6031
|
|
|
6032 Do @code{(setq truncate-lines t)} in the mode-hooks for any modes
|
|
|
6033 in which you want lines truncated.
|
|
|
6034
|
|
|
6035 More precisely: If @code{truncate-lines} is nil, horizontal scrollbars
|
|
|
6036 will never appear. Otherwise, they will appear only if the value of
|
|
|
6037 @code{scrollbar-height} for that buffer/window/etc. is non-zero. If you
|
|
|
6038 do
|
|
|
6039
|
|
|
6040 @lisp
|
|
|
6041 (set-specifier scrollbar-height 0)
|
|
|
6042 @end lisp
|
|
|
6043
|
|
|
6044 then horizontal scrollbars will not appear in truncated buffers unless
|
|
|
6045 the package specifically asked for them.
|
|
|
6046
|
|
|
6047 @node Q4.6.7, Q4.7.1, Q4.6.6, Display
|
|
|
6048 @unnumberedsubsec Q4.6.7: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
6049
|
|
|
6050 @code{auto-show-mode} controls whether or not a horizontal scrollbar
|
|
|
6051 magically appears when a line is too long to be displayed. This is
|
|
|
6052 enabled by default. To turn it off, put the following in your
|
|
|
6053 @file{init.el}:
|
|
|
6054
|
|
|
6055 @lisp
|
|
|
6056 (setq auto-show-mode nil)
|
|
|
6057 (setq-default auto-show-mode nil)
|
|
|
6058 @end lisp
|
|
|
6059
|
|
|
6060 @unnumberedsec 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
6061
|
|
|
6062 @node Q4.7.1, Q4.7.2, Q4.6.7, Display
|
|
|
6063 @unnumberedsubsec Q4.7.1: How can I disable the gutter tabs?
|
|
|
6064
|
|
|
6065 #### Write me.
|
|
|
6066
|
|
|
6067 @node Q4.7.2, Q4.7.3, Q4.7.1, Display
|
|
|
6068 @unnumberedsubsec Q4.7.2: How can I disable the progress bar?
|
|
|
6069
|
|
|
6070 #### Write me.
|
|
|
6071
|
|
|
6072 @node Q4.7.3, Q4.7.4, Q4.7.2, Display
|
|
|
6073 @unnumberedsubsec Q4.7.3: There are bugs in the gutter or widgets.
|
|
|
6074
|
|
|
6075 #### Write me.
|
|
|
6076
|
|
|
6077 @node Q4.7.4, , Q4.7.3, Display
|
|
|
6078 @unnumberedsubsec Q4.7.4: How can I customize the gutter or gutter tabs?
|
|
|
6079
|
|
|
6080 #### Write me.
|
|
|
6081
|
|
|
6082 @node External Subsystems, Internet, Display, Top
|
|
|
6083 @unnumbered 5 Interfacing with the Operating System and External Devices
|
|
|
6084
|
|
|
6085 This is part 5 of the XEmacs Frequently Asked Questions list. This
|
|
2417
|
6086 section is devoted to the various ways that XEmacs interfaces with the
|
|
|
6087 operating system, with other processes and with external devices such
|
|
|
6088 as speakers and the printer.
|
|
428
|
6089
|
|
|
6090 @menu
|
|
2459
|
6091 5.0: X Window System and Resources
|
|
|
6092 * Q5.0.1:: Where is a list of X resources?
|
|
|
6093 * Q5.0.2:: How can I detect a color display?
|
|
|
6094 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}?
|
|
|
6095 * Q5.0.4:: How can I have the window title area display the full path?
|
|
|
6096 * Q5.0.5:: @samp{xemacs -name junk} doesn't work?
|
|
|
6097 * Q5.0.6:: @samp{-iconic} doesn't work.
|
|
|
6098
|
|
|
6099 5.1: Microsoft Windows
|
|
|
6100 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
|
6101 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
|
6102
|
|
|
6103 5.2: Printing
|
|
|
6104 * Q5.2.1:: What do I need to change to make printing work?
|
|
|
6105 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer?
|
|
|
6106 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
|
6107 * Q5.2.4:: Can you print under MS Windows?
|
|
|
6108
|
|
|
6109 5.3: Sound
|
|
|
6110 * Q5.3.1:: How do I turn off the sound?
|
|
|
6111 * Q5.3.2:: How do I get funky sounds instead of a boring beep?
|
|
|
6112 * Q5.3.3:: What are NAS and ESD (EsounD)?
|
|
|
6113 * Q5.3.4:: Sunsite sounds don't play.
|
|
|
6114
|
|
|
6115 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
6116 * Q5.4.1:: What is an interior shell?
|
|
|
6117 * Q5.4.2:: How do I start up a second shell buffer?
|
|
|
6118 * Q5.4.3:: Telnet from shell filters too much
|
|
|
6119 * Q5.4.4:: Strange things are happening in Shell Mode.
|
|
|
6120 * Q5.4.5:: XEmacs complains "No such file or directory, diff"
|
|
2995
|
6121 * Q5.4.6:: Cygwin error "fork_copy: linked dll/bss pass 0 failed"
|
|
2459
|
6122
|
|
|
6123 5.5: Multiple Device Support
|
|
|
6124 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display?
|
|
|
6125 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
6126 * Q5.5.3:: How do I disable gnuserv from opening a new frame?
|
|
|
6127 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
|
6128 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
428
|
6129 @end menu
|
|
|
6130
|
|
2459
|
6131 @unnumberedsec 5.0: X Window System and Resources
|
|
|
6132
|
|
|
6133 @node Q5.0.1, Q5.0.2, External Subsystems, External Subsystems
|
|
|
6134 @unnumberedsubsec Q5.0.1: Where is a list of X resources?
|
|
2417
|
6135
|
|
|
6136 Search through the @file{NEWS} file for @samp{X Resources}. A fairly
|
|
|
6137 comprehensive list is given after it.
|
|
|
6138
|
|
|
6139 In addition, an @file{app-defaults} file @file{etc/Emacs.ad} is
|
|
|
6140 supplied, listing the defaults. The file @file{etc/sample.Xresources}
|
|
|
6141 gives a different set of defaults that you might consider for
|
|
|
6142 installation in your @file{~/.Xresources} file. It is nearly the same
|
|
|
6143 as @file{etc/Emacs.ad}, but a few entries are altered. Be careful about
|
|
|
6144 installing the contents of this file into your @file{.Xresources} (or
|
|
|
6145 legacy @file{.Xdefaults}) file if you use GNU Emacs under X11 as well.
|
|
|
6146
|
|
2459
|
6147 @node Q5.0.2, Q5.0.3, Q5.0.1, External Subsystems
|
|
|
6148 @unnumberedsubsec Q5.0.2: How can I detect a color display?
|
|
2417
|
6149
|
|
|
6150 You can test the return value of the function @code{(device-class)}, as
|
|
|
6151 in:
|
|
|
6152
|
|
|
6153 @lisp
|
|
|
6154 (when (eq (device-class) 'color)
|
|
|
6155 (set-face-foreground 'font-lock-comment-face "Grey")
|
|
|
6156 (set-face-foreground 'font-lock-string-face "Red")
|
|
|
6157 ....
|
|
|
6158 )
|
|
|
6159 @end lisp
|
|
|
6160
|
|
2459
|
6161 @node Q5.0.3, Q5.0.4, Q5.0.2, External Subsystems
|
|
|
6162 @unnumberedsubsec Q5.0.3: How can I get the icon to just say @samp{XEmacs}?
|
|
2417
|
6163
|
|
|
6164 I'd like the icon to just say @samp{XEmacs}, and not include the name of
|
|
|
6165 the current file in it.
|
|
|
6166
|
|
|
6167 Add the following line to your @file{init.el}:
|
|
|
6168
|
|
|
6169 @lisp
|
|
|
6170 (setq frame-icon-title-format "XEmacs")
|
|
|
6171 @end lisp
|
|
|
6172
|
|
2459
|
6173 @node Q5.0.4, Q5.0.5, Q5.0.3, External Subsystems
|
|
|
6174 @unnumberedsubsec Q5.0.4: How can I have the window title area display the full path?
|
|
2417
|
6175
|
|
|
6176 I'd like to have the window title area display the full directory/name
|
|
|
6177 of the current buffer file and not just the name.
|
|
|
6178
|
|
|
6179 Add the following line to your @file{init.el}:
|
|
|
6180
|
|
|
6181 @lisp
|
|
|
6182 (setq frame-title-format "%S: %f")
|
|
|
6183 @end lisp
|
|
|
6184
|
|
|
6185 A more sophisticated title might be:
|
|
|
6186
|
|
|
6187 @lisp
|
|
|
6188 (setq frame-title-format
|
|
|
6189 '("%S: " (buffer-file-name "%f"
|
|
|
6190 (dired-directory dired-directory "%b"))))
|
|
|
6191 @end lisp
|
|
|
6192
|
|
|
6193 That is, use the file name, or the dired-directory, or the buffer name.
|
|
|
6194
|
|
2459
|
6195 @node Q5.0.5, Q5.0.6, Q5.0.4, External Subsystems
|
|
|
6196 @unnumberedsubsec Q5.0.5: @samp{xemacs -name junk} doesn't work?
|
|
2417
|
6197
|
|
|
6198 When I run @samp{xterm -name junk}, I get an xterm whose class name
|
|
|
6199 according to xprop, is @samp{junk}. This is the way it's supposed to
|
|
|
6200 work, I think. When I run @samp{xemacs -name junk} the class name is
|
|
|
6201 not set to @samp{junk}. It's still @samp{emacs}. What does
|
|
|
6202 @samp{xemacs -name} really do? The reason I ask is that my window
|
|
|
6203 manager (fvwm) will make a window sticky and I use XEmacs to read my
|
|
|
6204 mail. I want that XEmacs window to be sticky, without having to use the
|
|
|
6205 window manager's function to set the window sticky. What gives?
|
|
|
6206
|
|
|
6207 @samp{xemacs -name} sets the application name for the program (that is,
|
|
|
6208 the thing which normally comes from @samp{argv[0]}). Using @samp{-name}
|
|
|
6209 is the same as making a copy of the executable with that new name. The
|
|
|
6210 @code{WM_CLASS} property on each frame is set to the frame-name, and the
|
|
|
6211 application-class. So, if you did @samp{xemacs -name FOO} and then
|
|
|
6212 created a frame named @var{BAR}, you'd get an X window with WM_CLASS =
|
|
|
6213 @code{( "BAR", "Emacs")}. However, the resource hierarchy for this
|
|
|
6214 widget would be:
|
|
|
6215
|
|
|
6216 @example
|
|
|
6217 Name: FOO .shell .container .BAR
|
|
|
6218 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
|
|
|
6219 @end example
|
|
|
6220
|
|
|
6221 instead of the default
|
|
|
6222
|
|
|
6223 @example
|
|
|
6224 Name: xemacs.shell .container .emacs
|
|
|
6225 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
|
|
|
6226 @end example
|
|
|
6227
|
|
|
6228
|
|
|
6229 It is arguable that the first element of WM_CLASS should be set to the
|
|
|
6230 application-name instead of the frame-name, but I think that's less
|
|
|
6231 flexible, since it does not give you the ability to have multiple frames
|
|
|
6232 with different WM_CLASS properties. Another possibility would be for
|
|
|
6233 the default frame name to come from the application name instead of
|
|
|
6234 simply being @samp{emacs}. However, at this point, making that change
|
|
|
6235 would be troublesome: it would mean that many users would have to make
|
|
|
6236 yet another change to their resource files (since the default frame name
|
|
|
6237 would suddenly change from @samp{emacs} to @samp{xemacs}, or whatever
|
|
|
6238 the executable happened to be named), so we'd rather avoid it.
|
|
|
6239
|
|
|
6240 To make a frame with a particular name use:
|
|
|
6241
|
|
|
6242 @lisp
|
|
|
6243 (make-frame '((name . "the-name")))
|
|
|
6244 @end lisp
|
|
|
6245
|
|
2459
|
6246 @node Q5.0.6, Q5.1.1, Q5.0.5, External Subsystems
|
|
|
6247 @unnumberedsubsec Q5.0.6: @samp{-iconic} doesn't work.
|
|
2417
|
6248
|
|
|
6249 When I start up XEmacs using @samp{-iconic} it doesn't work right.
|
|
|
6250 Using @samp{-unmapped} on the command line, and setting the
|
|
|
6251 @code{initiallyUnmapped} X Resource don't seem to help much either...
|
|
|
6252
|
|
|
6253 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
|
6254
|
|
|
6255 @quotation
|
|
|
6256 Ugh, this stuff is such an incredible mess that I've about given up
|
|
|
6257 getting it to work. The principal problem is numerous window-manager
|
|
|
6258 bugs...
|
|
|
6259 @end quotation
|
|
|
6260
|
|
2459
|
6261 @unnumberedsec 5.1: Microsoft Windows
|
|
|
6262
|
|
|
6263 @node Q5.1.1, Q5.1.2, Q5.0.6, External Subsystems
|
|
|
6264 @unnumberedsubsec Q5.1.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
2417
|
6265
|
|
|
6266 In his flavor of Emacs 20, Richard Stallman has renamed all the @samp{win32-*}
|
|
|
6267 symbols to @samp{w32-*}. Does XEmacs do the same?
|
|
|
6268
|
|
|
6269 We consider such a move counter-productive, thus we do not use the
|
|
|
6270 @samp{w32} prefix. (His rather questionable justification was that he
|
|
|
6271 did not consider Windows to be a "winning" platform.) However, the name
|
|
|
6272 @samp{Win32} is not particularly descriptive outside the Windows world,
|
|
|
6273 and using just @samp{windows-} would be too generic. So we chose a
|
|
|
6274 compromise, the prefix @samp{mswindows-} for Windows-related variables
|
|
|
6275 and functions.
|
|
|
6276
|
|
|
6277 Thus all the XEmacs variables and functions directly related to either
|
|
|
6278 the Windows GUI or OS are prefixed @samp{mswindows-} (except for a
|
|
|
6279 couple of debugging variables, prefixed @samp{debug-mswindows-}). From
|
|
|
6280 an architectural perspective, however, we believe that this is mostly a
|
|
|
6281 non-issue because there should be a very small number of
|
|
|
6282 window-systems-specific variables anyway. Whenever possible, we try to
|
|
|
6283 provide generic interfaces that apply to all window systems.
|
|
|
6284
|
|
|
6285 @c not true:
|
|
|
6286 @c The user variables
|
|
|
6287 @c that share functionality with existing NT Emacs variables are be named
|
|
|
6288 @c with our convention, but we provide the GNU Emacs names as
|
|
|
6289 @c compatibility aliases.
|
|
|
6290
|
|
2459
|
6291 @node Q5.1.2, Q5.2.1, Q5.1.1, External Subsystems
|
|
|
6292 @unnumberedsubsec Q5.1.2: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
2417
|
6293
|
|
|
6294 @unnumberedsubsubsec Associating a new file type with XEmacs.
|
|
|
6295
|
|
|
6296 In Explorer select @samp{View->Options->File Types}, press @samp{[New
|
|
|
6297 Type...]} and fill in the dialog box, e.g.:
|
|
|
6298
|
|
|
6299 @example
|
|
|
6300 Description of type: Emacs Lisp source
|
|
|
6301 Associated extension: el
|
|
|
6302 Content Type (MIME): text/plain
|
|
|
6303 @end example
|
|
|
6304
|
|
|
6305 then press @samp{[New...]} and fill in the @samp{Action} dialog box as
|
|
|
6306 follows:
|
|
|
6307
|
|
|
6308 @example
|
|
|
6309 Action:
|
|
|
6310 Open
|
|
|
6311
|
|
|
6312 Application used to perform action:
|
|
|
6313 D:\Full\path\for\xemacs.exe "%1"
|
|
|
6314
|
|
|
6315 [x] Use DDE
|
|
|
6316
|
|
|
6317 DDE Message:
|
|
|
6318 open("%1")
|
|
|
6319
|
|
|
6320 Application:
|
|
|
6321 <leave blank>
|
|
|
6322
|
|
|
6323 DDE Application Not Running:
|
|
|
6324 <leave blank>
|
|
|
6325
|
|
|
6326 Topic:
|
|
|
6327 <leave blank>
|
|
|
6328 @end example
|
|
|
6329
|
|
|
6330 @unnumberedsubsubsec Associating an existing file type with XEmacs.
|
|
|
6331
|
|
|
6332 In Explorer select @samp{View->Options->File Types}. Click on the file
|
|
|
6333 type in the list and press @samp{[Edit...]}. If the file type already
|
|
|
6334 has an @samp{Open} action, double click on it and fill in the
|
|
|
6335 @samp{Action} dialog box as described above; otherwise create a new
|
|
|
6336 action.
|
|
|
6337
|
|
|
6338 If the file type has more than one action listed, you probably want to
|
|
|
6339 make the @samp{Open} action that you just edited the default by clicking on
|
|
|
6340 it and pressing @samp{Set Default}.
|
|
|
6341
|
|
|
6342 Note for Windows 2000 users: Under Windows 2000, get to @samp{File Types}
|
|
|
6343 using @samp{Control Panel->Folder Options->File Types}.
|
|
|
6344
|
|
2459
|
6345 @unnumberedsec 5.2: Printing
|
|
|
6346
|
|
|
6347 @node Q5.2.1, Q5.2.2, Q5.1.2, External Subsystems
|
|
|
6348 @unnumberedsubsec Q5.2.1: What do I need to change to make printing work?
|
|
2417
|
6349
|
|
|
6350 For regular printing there are two variables that can be customized.
|
|
|
6351
|
|
|
6352 @table @code
|
|
|
6353 @item lpr-command
|
|
|
6354 This should be set to a command that takes standard input and sends
|
|
|
6355 it to a printer. Something like:
|
|
|
6356
|
|
|
6357 @lisp
|
|
|
6358 (setq lpr-command "lp")
|
|
|
6359 @end lisp
|
|
|
6360
|
|
|
6361 @item lpr-switches
|
|
|
6362 This should be set to a list that contains whatever the print command
|
|
|
6363 requires to do its job. Something like:
|
|
|
6364
|
|
|
6365 @lisp
|
|
|
6366 (setq lpr-switches '("-depson"))
|
|
|
6367 @end lisp
|
|
|
6368 @end table
|
|
|
6369
|
|
|
6370 For postscript printing there are three analogous variables to
|
|
|
6371 customize.
|
|
|
6372
|
|
|
6373 @table @code
|
|
|
6374 @item ps-lpr-command
|
|
|
6375 This should be set to a command that takes postscript on standard input
|
|
|
6376 and directs it to a postscript printer.
|
|
|
6377
|
|
|
6378 @item ps-lpr-switches
|
|
|
6379 This should be set to a list of switches required for
|
|
|
6380 @code{ps-lpr-command} to do its job.
|
|
|
6381
|
|
|
6382 @item ps-print-color-p
|
|
|
6383 This boolean variable should be set @code{t} if printing will be done in
|
|
|
6384 color, otherwise it should be set to @code{nil}.
|
|
|
6385 @end table
|
|
|
6386
|
|
|
6387 NOTE: It is an undocumented limitation in XEmacs that postscript
|
|
|
6388 printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a
|
|
|
6389 window system environment. It cannot be used outside of X11.
|
|
|
6390
|
|
2459
|
6391 @node Q5.2.2, Q5.2.3, Q5.2.1, External Subsystems
|
|
|
6392 @unnumberedsubsec Q5.2.2: How can I print WYSIWYG a font-locked buffer?
|
|
2417
|
6393
|
|
|
6394 Font-lock looks nice. How can I print (WYSIWYG) the highlighted
|
|
|
6395 document?
|
|
|
6396
|
|
|
6397 The package @code{ps-print}, which is now included with XEmacs, provides
|
|
|
6398 the ability to do this. The source code contains complete instructions
|
|
|
6399 on its use, in
|
|
|
6400 @file{$prefix/lib/xemacs/xemacs-packages/lisp/ps-print/ps-print.el},
|
|
|
6401 being the default location of an installed ps-print package.
|
|
|
6402
|
|
2459
|
6403 @node Q5.2.3, Q5.2.4, Q5.2.2, External Subsystems
|
|
|
6404 @unnumberedsubsec Q5.2.3: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
2417
|
6405
|
|
|
6406 My printer is a Postscript printer and @code{lpr} only works for
|
|
|
6407 Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x
|
|
|
6408 lpr-buffer} to work?
|
|
|
6409
|
|
|
6410 Put something like this in your @file{init.el}:
|
|
428
|
6411
|
|
|
6412 @lisp
|
|
2417
|
6413 (setq lpr-command "a2ps")
|
|
|
6414 (setq lpr-switches '("-p" "-1"))
|
|
|
6415 @end lisp
|
|
|
6416
|
|
|
6417 If you don't use a2ps to convert ASCII to postscript (why not, it's
|
|
|
6418 free?), replace with the command you do use. Note also that some
|
|
|
6419 versions of a2ps require a @samp{-Pprinter} to ensure spooling.
|
|
|
6420
|
|
2459
|
6421 @node Q5.2.4, Q5.3.1, Q5.2.3, External Subsystems
|
|
|
6422 @unnumberedsubsec Q5.2.4: Can you print under MS Windows?
|
|
2417
|
6423
|
|
|
6424 As of 21.4, printing works on Windows, using simply
|
|
|
6425 @samp{File->Print BUFFER...}, and can be configured with
|
|
|
6426 @samp{File->Page Setup...}.
|
|
|
6427
|
|
|
6428 Prior to 21.4, there is no built-in support, but there are some clever
|
|
|
6429 hacks out there. If you know how, please let us know and we'll put it
|
|
|
6430 here.
|
|
|
6431
|
|
2459
|
6432 @unnumberedsec 5.3: Sound
|
|
|
6433
|
|
|
6434 @node Q5.3.1, Q5.3.2, Q5.2.4, External Subsystems
|
|
|
6435 @unnumberedsubsec Q5.3.1: How do I turn off the sound?
|
|
2417
|
6436
|
|
|
6437 Add the following line to your @file{init.el}:
|
|
|
6438
|
|
|
6439 @lisp
|
|
|
6440 (setq bell-volume 0)
|
|
|
6441 (setq sound-alist nil)
|
|
|
6442 @end lisp
|
|
|
6443
|
|
|
6444 That will make your XEmacs totally silent---even the default ding sound
|
|
|
6445 (TTY beep on TTY-s) will be gone.
|
|
|
6446
|
|
|
6447 You can also change these with Customize. Select from the
|
|
|
6448 @code{Options} menu @code{Advanced
|
|
|
6449 (Customize)->Emacs->Environment->Sound->Sound...} or type @kbd{M-x
|
|
|
6450 customize @key{RET} sound @key{RET}}.
|
|
|
6451
|
|
|
6452
|
|
2459
|
6453 @node Q5.3.2, Q5.3.3, Q5.3.1, External Subsystems
|
|
|
6454 @unnumberedsubsec Q5.3.2: How do I get funky sounds instead of a boring beep?
|
|
2417
|
6455
|
|
|
6456 Make sure your XEmacs was compiled with sound support, and then put this
|
|
|
6457 in your @file{init.el}:
|
|
|
6458
|
|
|
6459 @lisp
|
|
|
6460 (load-default-sounds)
|
|
|
6461 @end lisp
|
|
|
6462
|
|
2459
|
6463 @node Q5.3.3, Q5.3.4, Q5.3.2, External Subsystems
|
|
|
6464 @unnumberedsubsec Q5.3.3: What are NAS and ESD (EsounD)?
|
|
|
6465
|
|
|
6466 @dfn{Network Audio System} (NAS) is a client-server sound library for X.
|
|
|
6467
|
|
|
6468 @uref{http://radscan.com/nas.html}.
|
|
|
6469
|
|
3018
|
6470 To build XEmacs with it, use the @file{configure} flag
|
|
|
6471 @samp{--with-sound=nas} (@samp{--enable-sound=nas} in 21.5 or later).
|
|
2459
|
6472
|
|
|
6473 @dfn{Enlightened Sound Daemon} (ESD or EsounD) is yet another sound system.
|
|
|
6474
|
|
|
6475 @uref{http://www.tux.org/~ricdude/EsounD.html}.
|
|
|
6476
|
|
3018
|
6477 To build XEmacs with it, use the @file{configure} flag
|
|
|
6478 @samp{--with-sound=esd} (@samp{--enable-sound=esd} in 21.5 or later).
|
|
|
6479
|
|
|
6480 You can specify support for both with a flag like
|
|
|
6481 @samp{--with-sound=nas,esd} (@samp{--enable-sound=nas,esd} in 21.5 or
|
|
|
6482 later).
|
|
2459
|
6483
|
|
|
6484 @node Q5.3.4, Q5.4.1, Q5.3.3, External Subsystems
|
|
|
6485 @unnumberedsubsec Q5.3.4: Sunsite sounds don't play.
|
|
2417
|
6486
|
|
|
6487 I'm having some trouble with sounds I've downloaded from sunsite. They
|
|
|
6488 play when I run them through @code{showaudio} or cat them directly to
|
|
|
6489 @file{/dev/audio}, but XEmacs refuses to play them.
|
|
|
6490
|
|
|
6491 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
|
|
|
6492
|
|
|
6493 @quotation
|
|
|
6494 [Many of] These files have an (erroneous) 24byte header that tells about
|
|
|
6495 the format that they have been recorded in. If you cat them to
|
|
|
6496 @file{/dev/audio}, the header will be ignored and the default behavior
|
|
|
6497 for /dev/audio will be used. This happens to be 8kHz uLaw. It is
|
|
|
6498 probably possible to fix the header by piping through @code{sox} and
|
|
|
6499 passing explicit parameters for specifying the sampling format; you then
|
|
|
6500 need to perform a 'null' conversion from SunAudio to SunAudio.
|
|
|
6501 @end quotation
|
|
|
6502
|
|
2459
|
6503 @unnumberedsec 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
6504
|
|
|
6505 @node Q5.4.1, Q5.4.2, Q5.3.4, External Subsystems
|
|
|
6506 @unnumberedsubsec Q5.4.1: What is an interior shell?
|
|
2417
|
6507
|
|
|
6508 #### Write me.
|
|
|
6509
|
|
2459
|
6510 @node Q5.4.2, Q5.4.3, Q5.4.1, External Subsystems
|
|
|
6511 @unnumberedsubsec Q5.4.2: How do I start up a second shell buffer?
|
|
2417
|
6512
|
|
|
6513 In the @code{*shell*} buffer:
|
|
|
6514
|
|
|
6515 @lisp
|
|
|
6516 M-x rename-buffer @key{RET} *shell-1* @key{RET}
|
|
|
6517 M-x shell RET
|
|
|
6518 @end lisp
|
|
|
6519
|
|
|
6520 This will then start a second shell. The key is that no buffer named
|
|
|
6521 @samp{*shell*} can exist. It might be preferable to use @kbd{M-x
|
|
|
6522 rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x
|
|
|
6523 rename-buffer}.
|
|
|
6524
|
|
|
6525 Alternately, you can set the variable @code{shell-multiple-shells}.
|
|
|
6526 If the value of this variable is non-nil, each time shell mode is invoked,
|
|
|
6527 a new shell is made
|
|
|
6528
|
|
2459
|
6529 @node Q5.4.3, Q5.4.4, Q5.4.2, External Subsystems
|
|
|
6530 @unnumberedsubsec Q5.4.3: Telnet from shell filters too much
|
|
2417
|
6531
|
|
|
6532 I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke
|
|
|
6533 and use a telnet session within it. Everything works fine except that
|
|
|
6534 now all @samp{^M}'s are filtered out by Emacs. Fixes?
|
|
|
6535
|
|
|
6536 Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather
|
|
|
6537 than doing rsh or telnet within the local shell buffer. You can also
|
|
|
6538 use @kbd{M-x ssh} to open secure remote session if you have @code{ssh}
|
|
|
6539 installed.
|
|
|
6540
|
|
2459
|
6541 @node Q5.4.4, Q5.4.5, Q5.4.3, External Subsystems
|
|
|
6542 @unnumberedsubsec Q5.4.4: Strange things are happening in Shell Mode.
|
|
2417
|
6543
|
|
|
6544 Sometimes (i.e. it's not repeatable, and I can't work out why it
|
|
|
6545 happens) when I'm typing into shell mode, I hit return and only a
|
|
|
6546 portion of the command is given to the shell, and a blank prompt is
|
|
|
6547 returned. If I hit return again, the rest of the previous command is
|
|
|
6548 given to the shell.
|
|
|
6549
|
|
|
6550 @email{martin@@xemacs.org, Martin Buchholz} writes:
|
|
|
6551
|
|
|
6552 @quotation
|
|
|
6553 There is a known problem with interaction between @code{csh} and the
|
|
|
6554 @code{filec} option and XEmacs. You should add the following to your
|
|
|
6555 @file{.cshrc}:
|
|
|
6556
|
|
|
6557 @example
|
|
|
6558 if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec
|
|
|
6559 @end example
|
|
|
6560 @end quotation
|
|
|
6561
|
|
2995
|
6562 @node Q5.4.5, Q5.4.6, Q5.4.4, External Subsystems
|
|
2459
|
6563 @unnumberedsubsec Q5.4.5: XEmacs complains "No such file or directory, diff"
|
|
2417
|
6564
|
|
|
6565 or "ispell" or other commands that seem related to whatever you just
|
|
|
6566 tried to do (M-x ediff or M-$, for example).
|
|
|
6567
|
|
|
6568 There are a large number of common (in the sense that "everyone has
|
|
|
6569 these, they really do") Unix utilities that are not provided with
|
|
|
6570 XEmacs. The GNU Project's implementations are available for Windows in
|
|
|
6571 the the Cygwin distribution (@uref{http://www.cygwin.com/}), which also
|
|
|
6572 provides a complete Unix emulation environment (and thus makes ports of
|
|
|
6573 Unix utilities nearly trivial). Another implementation is that from
|
|
|
6574 MinGW (@uref{http://www.mingw.org/msys.shtml}). If you know of others,
|
|
|
6575 please let us know!
|
|
|
6576
|
|
2995
|
6577 @node Q5.4.6, Q5.5.1, Q5.4.5, External Subsystems
|
|
|
6578 @unnumberedsubsec Q5.4.6: Cygwin error "fork_copy: linked dll/bss pass 0 failed"
|
|
|
6579
|
|
|
6580 If you are getting an error like
|
|
|
6581
|
|
|
6582 @example
|
|
|
6583 17797832 [main] bash 3468 fork_copy: linked dll/bss pass 0 failed,
|
|
|
6584 0x675000..0x6756A0, done 0, windows pid 2708, Win 32 error 487
|
|
|
6585 bash: fork: resource temporarily unavailable
|
|
|
6586 @end example
|
|
|
6587
|
|
|
6588 when trying to run bash using @kbd{M-x shell}, then you need to rebase
|
|
|
6589 your Cygwin DLL's. This is a known problem with Cygwin. To fix:
|
|
|
6590
|
|
|
6591 @enumerate
|
|
|
6592 @item
|
|
|
6593 Download the @file{rebase} utility from Cygwin setup (it's under
|
|
|
6594 @samp{System}).
|
|
|
6595 @item
|
|
|
6596 Kill @strong{all} of your Cygwin processes, including all of your
|
|
|
6597 shells and all background processes. Use @code{ps -a} to list all the
|
|
|
6598 processes you need to kill.
|
|
|
6599 @item
|
|
|
6600 From a DOS prompt, run @file{ash} (@strong{not} @file{bash},
|
|
|
6601 @file{tcsh} or @file{zsh}). Do not try to be clever and @code{exec
|
|
|
6602 /bin/ash} from your last shell; it won't work.
|
|
|
6603 @item
|
|
|
6604 Type @code{/bin/rebaseall -v}.
|
|
|
6605 @end enumerate
|
|
|
6606
|
|
|
6607 The problem should now be fixed -- at least, until you install another
|
|
|
6608 Cygwin package with DLL's, in which case you may have to repeat the
|
|
|
6609 procedure.
|
|
|
6610
|
|
2459
|
6611 @unnumberedsec 5.5: Multiple Device Support
|
|
|
6612
|
|
2995
|
6613 @node Q5.5.1, Q5.5.2, Q5.4.6, External Subsystems
|
|
2459
|
6614 @unnumberedsubsec Q5.5.1: How do I open a frame on another screen of my multi-headed display?
|
|
2417
|
6615
|
|
|
6616 Use the command @kbd{M-x make-frame-on-display}. This command is also
|
|
|
6617 on the File menu in the menubar.
|
|
|
6618
|
|
|
6619 The command @code{make-frame-on-tty} also exists, which will establish a
|
|
|
6620 connection to any tty-like device. Opening the TTY devices should be
|
|
|
6621 left to @code{gnuclient}, though.
|
|
|
6622
|
|
2459
|
6623 @node Q5.5.2, Q5.5.3, Q5.5.1, External Subsystems
|
|
|
6624 @unnumberedsubsec Q5.5.2: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
6625
|
|
|
6626 Yes. Use @code{gnuclient -nw}.
|
|
|
6627
|
|
|
6628 Also see @ref{Q5.5.3, How do I disable gnuserv from opening a new frame?}.
|
|
|
6629
|
|
|
6630 @node Q5.5.3, Q5.5.4, Q5.5.2, External Subsystems
|
|
|
6631 @unnumberedsubsec Q5.5.3: How do I disable gnuserv from opening a new frame?
|
|
2417
|
6632
|
|
|
6633 If you set the @code{gnuserv-frame} variable to the frame that should be
|
|
|
6634 used to display buffers that are pulled up, a new frame will not be
|
|
|
6635 created. For example, you could put
|
|
|
6636
|
|
|
6637 @lisp
|
|
|
6638 (setq gnuserv-frame (selected-frame))
|
|
428
|
6639 @end lisp
|
|
|
6640
|
|
2417
|
6641 early on in your @file{init.el}, to ensure that the first frame created
|
|
|
6642 is the one used for your gnuserv buffers.
|
|
|
6643
|
|
|
6644 There is an option to set the gnuserv target to the current frame. See
|
|
|
6645 @code{Options->Display->"Other Window" Location->Make Current Frame Gnuserv Target}
|
|
|
6646
|
|
|
6647 You can also change this with Customize. Select from the
|
|
|
6648 @code{Options} menu @code{Advanced
|
|
|
6649 (Customize)->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type
|
|
|
6650 @kbd{M-x customize @key{RET} gnuserv @key{RET}}.
|
|
|
6651
|
|
|
6652
|
|
2459
|
6653 @node Q5.5.4, Q5.5.5, Q5.5.3, External Subsystems
|
|
|
6654 @unnumberedsubsec Q5.5.4: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
2417
|
6655
|
|
|
6656 Put the following in your @file{init.el} file to start the server:
|
|
|
6657
|
|
|
6658 @lisp
|
|
|
6659 (gnuserv-start)
|
|
|
6660 @end lisp
|
|
|
6661
|
|
|
6662 Start your first XEmacs as usual. After that, you can do:
|
|
|
6663
|
|
|
6664 @example
|
|
|
6665 gnuclient randomfilename
|
|
|
6666 @end example
|
|
|
6667
|
|
|
6668 from the command line to get your existing XEmacs process to open a new
|
|
|
6669 frame and visit randomfilename in that window. When you're done editing
|
|
|
6670 randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the
|
|
|
6671 frame.
|
|
|
6672
|
|
|
6673 See also man page of gnuclient.
|
|
|
6674
|
|
2459
|
6675 @node Q5.5.5, , Q5.5.4, External Subsystems
|
|
|
6676 @unnumberedsubsec Q5.5.5: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
2417
|
6677
|
|
|
6678 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
|
|
|
6679 @quotation
|
|
|
6680 Here is one of the solutions, we have this in a script called
|
|
|
6681 @file{etc/editclient.sh}.
|
|
|
6682 @example
|
|
|
6683 #!/bin/sh
|
|
|
6684 if gnuclient -batch -eval t >/dev/null 2>&1
|
|
|
6685 then
|
|
|
6686 exec gnuclient $@{1+"$@@"@}
|
|
|
6687 else
|
|
|
6688 xemacs -unmapped -f gnuserv-start &
|
|
|
6689 until gnuclient -batch -eval t >/dev/null 2>&1
|
|
|
6690 do
|
|
|
6691 sleep 1
|
|
|
6692 done
|
|
|
6693 exec gnuclient $@{1+"$@@"@}
|
|
|
6694 fi
|
|
|
6695 @end example
|
|
|
6696
|
|
|
6697 Note that there is a known problem when running XEmacs and 'gnuclient
|
|
|
6698 -nw' on the same TTY.
|
|
|
6699 @end quotation
|
|
|
6700
|
|
2459
|
6701 @node Internet, Advanced, External Subsystems, Top
|
|
|
6702 @unnumbered 6 Connecting to the Internet
|
|
|
6703
|
|
|
6704 This is part 6 of the XEmacs Frequently Asked Questions list. This
|
|
|
6705 section is devoted connecting to the Internet.
|
|
|
6706
|
|
|
6707 @menu
|
|
|
6708 6.0: General Mail and News
|
|
|
6709 * Q6.0.1:: What are the various packages for reading mail?
|
|
|
6710 * Q6.0.2:: How can I send mail?
|
|
|
6711 * Q6.0.3:: How do I get my outgoing mail archived?
|
|
|
6712 * Q6.0.4:: How can I read and/or compose MIME messages?
|
|
|
6713 * Q6.0.5:: How do I customize the From line?
|
|
|
6714 * Q6.0.6:: How do I get my MUA to filter mail for me?
|
|
|
6715 * Q6.0.7:: Remote mail reading with an MUA.
|
|
|
6716 * Q6.0.8:: An MUA gets an error incorporating new mail.
|
|
|
6717 * Q6.0.9:: Why isn't @file{movemail} working?
|
|
|
6718 * Q6.0.10:: How do I make my MUA display graphical smilies?
|
|
|
6719 * Q6.0.11:: How can I get those oh-so-neat X-Face lines?
|
|
|
6720
|
|
|
6721 6.1: Reading Mail with VM
|
|
|
6722 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
6723 * Q6.1.2:: How can I get VM to automatically check for new mail?
|
|
|
6724 * Q6.1.3:: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"?
|
|
|
6725 * Q6.1.4:: Is there a mailing list or FAQ for VM?
|
|
|
6726 * Q6.1.5:: How do I make VM stay in a single frame?
|
|
|
6727 * Q6.1.6:: Customization of VM not covered in the manual, or here.
|
|
|
6728
|
|
|
6729 6.2: Reading Netnews and Mail with Gnus
|
|
|
6730 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
6731 * Q6.2.2:: How do I make Gnus stay within a single frame?
|
|
|
6732
|
|
|
6733 6.3: FTP Access
|
|
|
6734 * Q6.3.1:: Can I edit files on other hosts?
|
|
|
6735 * Q6.3.2:: What is EFS?
|
|
|
6736
|
|
|
6737 6.4: Web Browsing with W3
|
|
|
6738 * Q6.4.1:: What is W3?
|
|
|
6739 * Q6.4.2:: How do I run W3 from behind a firewall?
|
|
|
6740 * Q6.4.3:: Is it true that W3 supports style sheets and tables?
|
|
|
6741 @end menu
|
|
|
6742
|
|
|
6743 @unnumberedsec 6.0: General Mail and News
|
|
|
6744
|
|
|
6745 @node Q6.0.1, Q6.0.2, Internet, Internet
|
|
|
6746 @unnumberedsubsec Q6.0.1: What are the various packages for reading mail?
|
|
|
6747
|
|
|
6748 #### Write me.
|
|
|
6749
|
|
|
6750 @node Q6.0.2, Q6.0.3, Q6.0.1, Internet
|
|
|
6751 @unnumberedsubsec Q6.0.2: How can I send mail?
|
|
|
6752
|
|
|
6753 Under Unix and Mac OS X, the @samp{sendmail} package is normally used
|
|
|
6754 for this.
|
|
|
6755 #### Write me.
|
|
|
6756
|
|
|
6757 Under Windows, you need to use @samp{smtpmail}, which communicates
|
|
|
6758 directly with the mail server, as there is no @file{sendmail} program
|
|
|
6759 running. To get it working, use code like the following in your
|
|
|
6760 @file{init.el} file:
|
|
|
6761
|
|
|
6762 @lisp
|
|
|
6763 ;; Get mail working under Windows.
|
|
|
6764 (setq message-send-mail-function 'smtpmail-send-it) ; for message/Gnus
|
|
|
6765 (setq send-mail-function 'smtpmail-send-it) ; for C-x m, etc.
|
|
|
6766 ;; the following ensures that mail problems can be debugged: it logs a trace
|
|
|
6767 ;; of the SMTP conversation to *trace of SMTP session to <somewhere>*.
|
|
|
6768 (setq smtpmail-debug-info t)
|
|
|
6769 ;; Substitute your info here.
|
|
|
6770 ;(setq user-mail-address "ben@@xemacs.org")
|
|
|
6771 ;(setq user-full-name "Ben Wing")
|
|
|
6772 ;(setq smtpmail-default-smtp-server "smtp.myserver.myisp.com")
|
|
|
6773 ;; The following two aren't completely necessary but may help.
|
|
|
6774 ;(setq smtpmail-local-domain "666.com")
|
|
|
6775 ;(setq smtpmail-sendto-domain "666.com")
|
|
|
6776 ;; If your SMTP server requires a username/password to authenticate, as
|
|
|
6777 ;; many do nowadays, set them like this:
|
|
|
6778 ;(setq smtpmail-auth-credentials ; or use ~/.authinfo
|
|
|
6779 ; '(("smtp.myserver.myisp.com" 25 "USER@@SOMEWHERE" "PASSWORD")))
|
|
|
6780
|
|
|
6781 ;; Other possibilities for getting smtpmail to work:
|
|
|
6782 ;;
|
|
|
6783 ;; If for some reason you need to authenticate using the STARTTLS protocol
|
|
|
6784 ;; (don't look into this unless you know what it is), use
|
|
|
6785 ;; (setq smtpmail-starttls-credentials
|
|
|
6786 ;; '(("YOUR SMTP HOST" 25 "~/.my_smtp_tls.key" "~/.my_smtp_tls.cert")))
|
|
|
6787 ;; Requires external program
|
|
|
6788 ;; ftp://ftp.opaopa.org/pub/elisp/starttls-*.tar.gz.
|
|
|
6789 ;; See http://www.ietf.org/rfc/rfc2246.txt,
|
|
|
6790 ;; http://www.ietf.org/rfc/rfc2487.txt
|
|
|
6791 @end lisp
|
|
|
6792
|
|
|
6793 The lines you need to care about are those that set
|
|
|
6794 @code{user-mail-address}, @code{user-full-name},
|
|
|
6795 @code{smtpmail-default-smtp-server}, and
|
|
|
6796 @code{smtpmail-auth-credentials}. You need to set these with,
|
|
|
6797 respectively, your email address, your full name, the SMTP server you
|
|
|
6798 use for outgoing mail, and the username and password you need to log
|
|
|
6799 in to your SMTP server. (If for some reason your SMTP server doesn't
|
|
|
6800 require logging in to send mail, don't uncomment this last line.)
|
|
|
6801
|
|
|
6802 The other settings may be useful in specific cases, but you should know what
|
|
|
6803 you're doing before enabling them.
|
|
|
6804
|
|
|
6805 @node Q6.0.3, Q6.0.4, Q6.0.2, Internet
|
|
|
6806 @unnumberedsubsec Q6.0.3: How do I get my outgoing mail archived?
|
|
|
6807
|
|
|
6808 @lisp
|
|
|
6809 (setq mail-archive-file-name "~/outbox")
|
|
|
6810 @end lisp
|
|
|
6811
|
|
|
6812 @node Q6.0.4, Q6.0.5, Q6.0.3, Internet
|
|
|
6813 @unnumberedsubsec Q6.0.4: How can I read and/or compose MIME messages?
|
|
|
6814
|
|
|
6815 VM, MH-E and GNUS support MIME natively. Other MUAs may or may not
|
|
|
6816 have MIME support; refer to their documentation and other resources,
|
|
|
6817 such as web pages and mailing lists. Packages like SEMI/WEMI may be
|
|
|
6818 useful in connection with MUAs like mew and Wanderlust.
|
|
|
6819
|
|
|
6820 @node Q6.0.5, Q6.0.6, Q6.0.4, Internet
|
|
|
6821 @unnumberedsubsec Q6.0.5: How do I customize the From line?
|
|
|
6822
|
|
|
6823 How do I change the @samp{From:} line? I have set gnus-user-from-line
|
|
|
6824 to
|
|
|
6825 @example
|
|
|
6826 Gail Gurman <gail.gurman@@sybase.com>
|
|
|
6827 @end example
|
|
|
6828 @noindent , but XEmacs Gnus doesn't use
|
|
|
6829 it. [This should apply to all MUA's. --ed] Instead it uses
|
|
|
6830 @example
|
|
|
6831 Gail Mara Gurman @email{gailg@@deall}
|
|
|
6832 @end example
|
|
|
6833 @noindent and then complains
|
|
|
6834 that it's incorrect. Also, as you perhaps can see, my Message-ID is
|
|
|
6835 screwy. How can I change that?
|
|
|
6836
|
|
|
6837 @email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes:
|
|
|
6838
|
|
|
6839 @quotation
|
|
|
6840 Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or
|
|
|
6841 @code{mail-host-address} to @samp{sybase.com}.
|
|
|
6842 @end quotation
|
|
|
6843
|
|
|
6844 @node Q6.0.6, Q6.0.7, Q6.0.5, Internet
|
|
|
6845 @unnumberedsubsec Q6.0.6: How do I get my MUA to filter mail for me?
|
|
|
6846
|
|
|
6847 One possibility is to use procmail to split your mail before it gets to
|
|
|
6848 the MUA. I prefer this personally, since there are many strange and
|
|
|
6849 wonderful things one can do with procmail. Procmail may be found at
|
|
|
6850 @uref{http://www.procmail.org/}.
|
|
|
6851
|
|
|
6852 Also see the Mail Filtering FAQ at:
|
|
|
6853 @iftex
|
|
|
6854 @*
|
|
|
6855 @end iftex
|
|
|
6856 @uref{http://www.faqs.org/faqs/mail/filtering-faq/}.
|
|
|
6857
|
|
|
6858 @node Q6.0.7, Q6.0.8, Q6.0.6, Internet
|
|
|
6859 @unnumberedsubsec Q6.0.7: Remote mail reading with an MUA.
|
|
|
6860
|
|
|
6861 My mailbox lives at the office on a big honkin server. My regular INBOX
|
|
|
6862 lives on my honkin desktop machine. I now can PPP to the office from
|
|
|
6863 home which is far from honking... I'd like to be able to read mail at
|
|
|
6864 home without storing it here and I'd like to use xemacs and the MUA at
|
|
|
6865 home... Is there a recommended setup?
|
|
|
6866
|
|
|
6867 @email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes:
|
|
|
6868
|
|
|
6869 @quotation
|
|
|
6870 There are several ways to do this.
|
|
|
6871
|
|
|
6872 @enumerate
|
|
|
6873 @item
|
|
|
6874 Set your display to your home machine and run dxpc or one of the other X
|
|
|
6875 compressors.
|
|
|
6876
|
|
|
6877 @item
|
|
|
6878 NFS mount your desktop machine on your home machine and modify your pop
|
|
|
6879 command on your home machine to rsh to your desktop machine and actually
|
|
|
6880 do the pop get's.
|
|
|
6881
|
|
|
6882 @item
|
|
|
6883 Run a POP server on your desktop machine as well and do a sort of two
|
|
|
6884 tiered POP get.
|
|
|
6885 @end enumerate
|
|
|
6886 @end quotation
|
|
|
6887
|
|
|
6888 @email{wmperry@@monolith.spry.com, William Perry} adds:
|
|
|
6889
|
|
|
6890 @quotation
|
|
|
6891 Or you could run a pop script periodically on your desktop machine, and
|
|
|
6892 just use ange-ftp or NFS to get to your mailbox. I used to do this all
|
|
|
6893 the time back at IU.
|
|
|
6894 @end quotation
|
|
|
6895
|
|
|
6896 @node Q6.0.8, Q6.0.9, Q6.0.7, Internet
|
|
|
6897 @unnumberedsubsec Q6.0.8: An MUA gets an error incorporating new mail.
|
|
|
6898
|
|
|
6899 rmail and VM, and probably other MUA's as well, get new mail from
|
|
|
6900 your mailbox (called @file{/var/mail/$USER} or @file{/var/spool/mail/$USER}
|
|
|
6901 or something similar) using a program called @code{movemail}.
|
|
|
6902 This program interlocks with @code{/bin/mail} using the protocol
|
|
|
6903 defined by @code{/bin/mail}.
|
|
|
6904
|
|
|
6905 There are various different protocols in general use, which you need to
|
|
3018
|
6906 specify using the @samp{--mail-locking} option
|
|
|
6907 (@samp{--with-mail-locking} in 21.5 or later) to @file{configure}:
|
|
2459
|
6908
|
|
|
6909 @table @samp
|
|
|
6910 @item lockf
|
|
|
6911 POSIX file locking with @code{lockf()}
|
|
|
6912 @item flock
|
|
|
6913 BSD file locking with @code{flock()}
|
|
|
6914 @item dot
|
|
|
6915 To manipulate mail file @file{foo}, first create file @file{foo.lock}
|
|
|
6916 @item locking
|
|
|
6917 Use @code{locking()}, Microsoft's renamed @code{flock()}
|
|
|
6918 @item mmdf
|
|
|
6919 Use @code{lk_open()} and @code{lk_close()} as defined by the Multi-channel
|
|
|
6920 Memo Distribution Facility
|
|
|
6921 @item pop
|
|
|
6922 Retrieve mail using POP (the Post Office Protocol). This is the
|
|
|
6923 default for Cygwin/MinGW.
|
|
|
6924 @end table
|
|
|
6925
|
|
|
6926 @strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
|
|
|
6927 SYSTEM, YOU CAN LOSE MAIL!}
|
|
|
6928
|
|
|
6929 Usually the value is correctly determined automatically:
|
|
|
6930 @file{configure} tries to detect the method in use, and defaults exist
|
|
|
6931 on systems for which this doesn't work.
|
|
|
6932
|
|
|
6933 However, if you run into problems incorporating new mail, it may be
|
|
|
6934 because an incorrect method is being used.
|
|
|
6935
|
|
|
6936 If your system uses the lock file protocol, and permissions are set
|
|
|
6937 so that ordinary users cannot write lock files in the mail spool
|
|
|
6938 directory, you may need to make @file{movemail} setgid to a
|
|
|
6939 suitable group such as @samp{mail}. You can use these commands (as
|
|
|
6940 root):
|
|
|
6941
|
|
|
6942 @example
|
|
|
6943 chgrp mail movemail
|
|
|
6944 chmod 2755 movemail
|
|
|
6945 @end example
|
|
|
6946
|
|
|
6947 If you are using the @samp{pop} locking method, @file{movemail} must
|
|
|
6948 be setuid root.
|
|
|
6949
|
|
|
6950 Installation normally copies movemail from the build directory to an
|
|
|
6951 installation directory which is usually under @file{/usr/local/lib}.
|
|
|
6952 The installed copy of @file{movemail} is usually in the directory
|
|
|
6953 @file{/usr/local/lib/xemacs-VERSION/TARGET} (for example,
|
|
|
6954 @file{/usr/local/lib/xemacs-21.4.15/i686-pc-cygwin}). You must change
|
|
|
6955 the group and mode of the installed copy; changing the group and mode
|
|
|
6956 of the build directory copy is ineffective.
|
|
|
6957
|
|
|
6958 @node Q6.0.9, Q6.0.10, Q6.0.8, Internet
|
|
|
6959 @unnumberedsubsec Q6.0.9: Why isn't @file{movemail} working?
|
|
|
6960
|
|
|
6961 @xref{Q6.0.8}.
|
|
|
6962
|
|
|
6963 Note also that older versions of Mozilla came with a @file{movemail}
|
|
|
6964 program that is @strong{not} compatible with XEmacs. Do not use it.
|
|
|
6965 Always use the @file{movemail} installed with your XEmacs. Failure to
|
|
|
6966 do so can result in lost mail.
|
|
|
6967
|
|
|
6968 @node Q6.0.10, Q6.0.11, Q6.0.9, Internet
|
|
|
6969 @unnumberedsubsec Q6.0.10: How do I make my MUA display graphical smilies?
|
|
|
6970 For mh-e use the following:
|
|
|
6971
|
|
|
6972 @lisp
|
|
|
6973 (add-hook 'mh-show-mode-hook '(lambda ()
|
|
|
6974 (smiley-region (point-min)
|
|
|
6975 (point-max))))
|
|
|
6976 @end lisp
|
|
|
6977
|
|
|
6978 @email{bill@@carpenter.ORG, WJCarpenter} writes:
|
|
|
6979 For VM use the following:
|
|
|
6980 @lisp
|
|
|
6981 (autoload 'smiley-region "smiley" nil t)
|
|
|
6982 (add-hook 'vm-select-message-hook
|
|
|
6983 '(lambda ()
|
|
|
6984 (smiley-region (point-min)
|
|
|
6985 (point-max))))
|
|
|
6986 @end lisp
|
|
|
6987
|
|
|
6988 For tm use the following:
|
|
|
6989 @lisp
|
|
|
6990 (autoload 'smiley-buffer "smiley" nil t)
|
|
|
6991 (add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer)
|
|
|
6992 @end lisp
|
|
|
6993
|
|
|
6994 @node Q6.0.11, Q6.1.1, Q6.0.10, Internet
|
|
|
6995 @unnumberedsubsec Q6.0.11: How can I get those oh-so-neat X-Face lines?
|
|
|
6996
|
|
|
6997 Firstly there is an ftp site which describes X-faces and has the
|
|
|
6998 associated tools mentioned below, at
|
|
|
6999 @uref{http://ftp.cs.indiana.edu/pub/faces/}.
|
|
|
7000
|
|
|
7001 Then the steps are
|
|
|
7002
|
|
|
7003 @enumerate
|
|
|
7004 @item
|
|
|
7005 Create 48x48x1 bitmap with your favorite tool
|
|
|
7006
|
|
|
7007 @item
|
|
|
7008 Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc.,
|
|
|
7009 and then compile the face.
|
|
|
7010
|
|
|
7011 @item
|
|
|
7012 @example
|
|
|
7013 cat file.xbm | xbm2ikon |compface > file.face
|
|
|
7014 @end example
|
|
|
7015
|
|
|
7016 @item
|
|
|
7017 Then be sure to quote things that are necessary for emacs strings:
|
|
|
7018
|
|
|
7019 @example
|
|
|
7020 cat ./file.face | sed 's/\\/\\\\/g'
|
|
|
7021 @iftex
|
|
|
7022 \ @*
|
|
|
7023 @end iftex
|
|
|
7024 | sed 's/\"/\\\"/g' > ./file.face.quoted
|
|
|
7025 @end example
|
|
|
7026
|
|
|
7027 @item
|
|
|
7028 Then set up emacs to include the file as a mail header - there were a
|
|
|
7029 couple of suggestions here---either something like:
|
|
|
7030
|
|
|
7031 @lisp
|
|
|
7032 (setq mail-default-headers
|
|
|
7033 "X-Face: @email{Ugly looking text string here}")
|
|
|
7034 @end lisp
|
|
|
7035
|
|
|
7036 Or, alternatively, as:
|
|
|
7037
|
|
|
7038 @lisp
|
|
|
7039 (defun mail-insert-x-face ()
|
|
|
7040 (save-excursion
|
|
|
7041 (goto-char (point-min))
|
|
|
7042 (search-forward mail-header-separator)
|
|
|
7043 (beginning-of-line)
|
|
|
7044 (insert "X-Face:")
|
|
|
7045 (insert-file-contents "~/.face")))
|
|
|
7046
|
|
|
7047 (add-hook 'mail-setup-hook 'mail-insert-x-face)
|
|
|
7048 @end lisp
|
|
|
7049 @end enumerate
|
|
|
7050
|
|
|
7051 However, 2 things might be wrong:
|
|
|
7052
|
|
|
7053 Some versions of pbmtoicon produces some header lines that is not
|
|
|
7054 expected by the version of compface that I grabbed. So I found I had to
|
|
|
7055 include a @code{tail +3} in the pipeline like this:
|
|
|
7056
|
|
|
7057 @example
|
|
|
7058 cat file.xbm | xbm2ikon | tail +3 |compface > file.face
|
|
|
7059 @end example
|
|
|
7060
|
|
|
7061 Some people have also found that if one uses the @code{(insert-file)}
|
|
|
7062 method, one should NOT quote the face string using the sed script .
|
|
|
7063
|
|
|
7064 It might also be helpful to use @email{stig@@hackvan.com, Stig's} script
|
|
|
7065 xbm2face (included in the compface distribution at XEmacs.org) to do the
|
|
|
7066 conversion.
|
|
|
7067
|
|
|
7068 Contributors for this item:
|
|
|
7069
|
|
|
7070 Paul Emsley,
|
|
|
7071 Ricardo Marek,
|
|
|
7072 Amir J. Katz,
|
|
|
7073 Glen McCort,
|
|
|
7074 Heinz Uphoff,
|
|
|
7075 Peter Arius,
|
|
|
7076 Paul Harrison, and
|
|
|
7077 Vegard Vesterheim
|
|
|
7078
|
|
|
7079 @unnumberedsec 6.1: Reading Mail with VM
|
|
|
7080
|
|
|
7081 @node Q6.1.1, Q6.1.2, Q6.0.11, Internet
|
|
|
7082 @unnumberedsubsec Q6.1.1: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
7083
|
|
|
7084 Use @code{vm-spool-files}, like this for example:
|
|
|
7085
|
|
|
7086 @lisp
|
|
|
7087 (setq vm-spool-files '("/var/spool/mail/wing"
|
|
|
7088 "netcom23.netcom.com:110:pass:wing:MYPASS"))
|
|
|
7089 @end lisp
|
|
|
7090
|
|
|
7091 Of course substitute your actual password for MYPASS.
|
|
|
7092
|
|
|
7093 @node Q6.1.2, Q6.1.3, Q6.1.1, Internet
|
|
|
7094 @unnumberedsubsec Q6.1.2: How can I get VM to automatically check for new mail?
|
|
|
7095
|
|
|
7096 @email{turner@@lanl.gov, John Turner} writes:
|
|
|
7097
|
|
|
7098 @quotation
|
|
|
7099 Use the following:
|
|
|
7100
|
|
|
7101 @lisp
|
|
|
7102 (setq vm-auto-get-new-mail 60)
|
|
|
7103 @end lisp
|
|
|
7104 @end quotation
|
|
|
7105
|
|
|
7106 @node Q6.1.3, Q6.1.4, Q6.1.2, Internet
|
|
|
7107 @unnumberedsubsec Q6.1.3: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"?
|
|
|
7108
|
|
|
7109 Set @code{vm-reply-ignored-addresses} to a list, like
|
|
|
7110
|
|
|
7111 @lisp
|
|
|
7112 (setq vm-reply-ignored-addresses
|
|
|
7113 '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com"
|
|
|
7114 "wing@@netcom.com" "wing@@xemacs.org"))
|
|
|
7115 @end lisp
|
|
|
7116
|
|
|
7117 Note that each string is a regular expression.
|
|
|
7118
|
|
|
7119 @node Q6.1.4, Q6.1.5, Q6.1.3, Internet
|
|
|
7120 @unnumberedsubsec Q6.1.4: Is there a mailing list or FAQ for VM?
|
|
|
7121
|
|
|
7122 A FAQ for VM exists at @uref{http://www.wonderworks.com/vm/FAQ.html}.
|
|
|
7123
|
|
|
7124 VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug.
|
|
|
7125
|
|
|
7126 @node Q6.1.5, Q6.1.6, Q6.1.4, Internet
|
|
|
7127 @unnumberedsubsec Q6.1.5: How do I make VM stay in a single frame?
|
|
|
7128
|
|
|
7129 John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes:
|
|
|
7130
|
|
|
7131 @quotation
|
|
|
7132 @lisp
|
|
|
7133 ; Don't use multiple frames
|
|
|
7134 (setq vm-frame-per-composition nil)
|
|
|
7135 (setq vm-frame-per-folder nil)
|
|
|
7136 (setq vm-frame-per-edit nil)
|
|
|
7137 (setq vm-frame-per-summary nil)
|
|
|
7138 @end lisp
|
|
|
7139 @end quotation
|
|
|
7140
|
|
|
7141 @node Q6.1.6, Q6.2.1, Q6.1.5, Internet
|
|
|
7142 @unnumberedsubsec Q6.1.6: Customization of VM not covered in the manual, or here.
|
|
|
7143
|
|
|
7144 @email{boffi@@hp735.stru.polimi.it, giacomo boffi} writes:
|
|
|
7145
|
|
|
7146 @quotation
|
|
|
7147 The meta-answer is to look into the file @file{vm-vars.el}, in the vm
|
|
|
7148 directory of the lisp library.
|
|
|
7149
|
|
|
7150 @file{vm-vars.el} contains, initializes and carefully describes, with
|
|
|
7151 examples of usage, the plethora of user options that @emph{fully}
|
|
|
7152 control VM's behavior.
|
|
|
7153
|
|
|
7154 Enter vm-vars, @code{forward-search} for toolbar, find the variables
|
|
|
7155 that control the toolbar placement, appearance, existence, copy to your
|
|
|
7156 @file{init.el} or @file{.vm} and modify according to the
|
|
|
7157 detailed instructions.
|
|
|
7158
|
|
|
7159 The above also applies to all the various features of VM: search for
|
|
|
7160 some keywords, maybe the first you conjure isn't appropriate, find the
|
|
|
7161 appropriate variables, copy and experiment.
|
|
|
7162 @end quotation
|
|
|
7163
|
|
|
7164 @unnumberedsec 6.2: Reading Netnews and Mail with Gnus
|
|
|
7165
|
|
|
7166 @node Q6.2.1, Q6.2.2, Q6.1.6, Internet
|
|
|
7167 @unnumberedsubsec Q6.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
7168
|
|
|
7169 The Gnus numbering issues are not meant for mere mortals to know them.
|
|
|
7170 If you feel you @emph{must} enter the muddy waters of Gnus, visit the
|
|
|
7171 excellent FAQ, maintained by Justin Sheehy, at:
|
|
|
7172
|
|
|
7173 @example
|
|
|
7174 @uref{http://my.gnus.org/FAQ/}
|
|
|
7175 @end example
|
|
|
7176
|
|
|
7177 See also Gnus home page
|
|
|
7178 @example
|
|
|
7179 @uref{http://www.gnus.org/}
|
|
|
7180 @end example
|
|
|
7181
|
|
|
7182 @node Q6.2.2, Q6.3.1, Q6.2.1, Internet
|
|
|
7183 @unnumberedsubsec Q6.2.2: How do I make Gnus stay within a single frame?
|
|
|
7184
|
|
|
7185 The toolbar code to start Gnus opens the new frame---and it's a feature
|
|
|
7186 rather than a bug. If you don't like it, but would still like to click
|
|
|
7187 on the seemly icon, use the following code:
|
|
|
7188
|
|
|
7189 @lisp
|
|
|
7190 (defun toolbar-news ()
|
|
|
7191 (gnus))
|
|
|
7192 @end lisp
|
|
|
7193
|
|
|
7194 It will redefine the callback function of the icon to just call
|
|
|
7195 @code{gnus}, without all the fancy frame stuff.
|
|
|
7196
|
|
|
7197 @unnumberedsec 6.3: FTP Access
|
|
|
7198
|
|
|
7199 @node Q6.3.1, Q6.3.2, Q6.2.2, Internet
|
|
|
7200 @unnumberedsubsec Q6.3.1: Can I edit files on other hosts?
|
|
|
7201
|
|
|
7202 Yes. Of course XEmacs can use any network file system (such as NFS or
|
|
|
7203 Windows file sharing) you have available, and includes some
|
|
|
7204 optimizations and safety features appropriate to those environments.
|
|
|
7205
|
|
|
7206 It is also possible to transparently edit files via FTP, ssh, or rsh. That
|
|
|
7207 is, XEmacs makes a local copy using the transport in the background, and
|
|
|
7208 automatically refreshes the remote original from that copy when you save
|
|
|
7209 it. XEmacs also is capable of doing file system manipulations like
|
|
|
7210 creating and removing directories and files. The FTP interface is
|
|
|
7211 provided by the standard @samp{efs} package @ref{Top, EFS, , efs}. The
|
|
|
7212 ssh/rsh interface is provided by the optional @samp{tramp} package
|
|
|
7213 @ref{Top, TRAMP, , tramp}.
|
|
|
7214
|
|
|
7215 @node Q6.3.2, Q6.4.1, Q6.3.1, Internet
|
|
|
7216 @unnumberedsubsec Q6.3.2: What is EFS?
|
|
|
7217
|
|
|
7218 #### Write me.
|
|
|
7219
|
|
|
7220 @unnumberedsec 6.4: Web Browsing with W3
|
|
|
7221
|
|
|
7222 @node Q6.4.1, Q6.4.2, Q6.3.2, Internet
|
|
|
7223 @unnumberedsubsec Q6.4.1: What is W3?
|
|
|
7224
|
|
|
7225 W3 is an advanced graphical browser written in Emacs lisp that runs on
|
|
|
7226 XEmacs. It has full support for cascaded style sheets, and more...
|
|
|
7227
|
|
|
7228 It has a home web page at
|
|
|
7229 @uref{http://www.cs.indiana.edu/elisp/w3/docs.html}.
|
|
|
7230
|
|
|
7231 @node Q6.4.2, Q6.4.3, Q6.4.1, Internet
|
|
|
7232 @unnumberedsubsec Q6.4.2: How do I run W3 from behind a firewall?
|
|
|
7233
|
|
|
7234 There is a long, well-written, detailed section in the W3 manual that
|
|
|
7235 describes how to do this. Look in the section entitled "Firewalls".
|
|
|
7236
|
|
|
7237 @node Q6.4.3, , Q6.4.2, Internet
|
|
|
7238 @unnumberedsubsec Q6.4.3: Is it true that W3 supports style sheets and tables?
|
|
|
7239
|
|
|
7240 Yes, and much more. W3, as distributed with the latest XEmacs is a
|
|
|
7241 full-featured web browser.
|
|
|
7242
|
|
|
7243 @node Advanced, Other Packages, Internet, Top
|
|
|
7244 @unnumbered 7 Advanced Customization Using XEmacs Lisp
|
|
|
7245
|
|
|
7246 This is part 7 of the XEmacs Frequently Asked Questions list. This
|
|
|
7247 section is devoted to advanced customization using XEmacs Lisp.
|
|
|
7248
|
|
|
7249 @menu
|
|
2537
|
7250 7.0: Emacs Lisp and @file{init.el}
|
|
|
7251 * Q7.0.1:: What version of Emacs am I running?
|
|
|
7252 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions?
|
|
|
7253 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly.
|
|
|
7254 * Q7.0.4:: How can I add directories to the @code{load-path}?
|
|
|
7255 * Q7.0.5:: How to check if a lisp function is defined?
|
|
|
7256 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer?
|
|
|
7257
|
|
|
7258 7.1: Emacs Lisp Programming Techniques
|
|
|
7259 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
|
7260 * Q7.1.2:: Can I generate "fake" keyboard events?
|
|
|
7261 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail?
|
|
|
7262 * Q7.1.4:: What is the performance hit of @code{let}?
|
|
|
7263 * Q7.1.5:: What is the recommended use of @code{setq}?
|
|
|
7264 * Q7.1.6:: What is the typical misuse of @code{setq}?
|
|
|
7265 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down?
|
|
|
7266 * Q7.1.8:: I like recursion, does it slow things down?
|
|
|
7267 * Q7.1.9:: How do I put a glyph as annotation in a buffer?
|
|
|
7268 * Q7.1.10:: @code{map-extents} won't traverse all of my extents!
|
|
|
7269 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
|
7270
|
|
|
7271 7.2: Mathematics
|
|
|
7272 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp?
|
|
|
7273 * Q7.2.2:: XEmacs segfaults when I use very big numbers!
|
|
|
7274 * Q7.2.3:: Bignums are really slow!
|
|
|
7275 * Q7.2.4:: Equal bignums don't compare as equal! What gives?
|
|
2459
|
7276 @end menu
|
|
|
7277
|
|
2537
|
7278 @unnumberedsec 7.0: Emacs Lisp and @file{init.el}
|
|
2459
|
7279
|
|
|
7280 @node Q7.0.1, Q7.0.2, Advanced, Advanced
|
|
2537
|
7281 @unnumberedsubsec Q7.0.1: What version of Emacs am I running?
|
|
2459
|
7282
|
|
|
7283 How can @file{init.el} determine which of the family of
|
|
|
7284 Emacsen I am using?
|
|
|
7285
|
|
|
7286 To determine if you are currently running GNU Emacs 18, GNU Emacs 19,
|
|
|
7287 XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the
|
|
|
7288 example given in @file{etc/sample.init.el} (@file{etc/sample.emacs} in
|
|
|
7289 XEmacs versions prior to 21.4). There are other nifty things in there
|
|
|
7290 as well!
|
|
|
7291
|
|
|
7292 For all new code, all you really need to do is:
|
|
|
7293
|
|
|
7294 @lisp
|
|
|
7295 (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
|
|
|
7296 @end lisp
|
|
|
7297
|
|
2537
|
7298 @node Q7.0.2, Q7.0.3, Q7.0.1, Advanced
|
|
|
7299 @unnumberedsubsec Q7.0.2: How can I evaluate Emacs-Lisp expressions?
|
|
2459
|
7300
|
|
|
7301 I know I can evaluate Elisp expressions from @code{*scratch*} buffer
|
|
|
7302 with @kbd{C-j} after the expression. How do I do it from another
|
|
|
7303 buffer?
|
|
|
7304
|
|
|
7305 Press @kbd{M-:} (the default binding of @code{eval-expression}), and
|
|
|
7306 enter the expression to the minibuffer.
|
|
|
7307
|
|
2537
|
7308 @node Q7.0.3, Q7.0.4, Q7.0.2, Advanced
|
|
|
7309 @unnumberedsubsec Q7.0.3: @code{(setq tab-width 6)} behaves oddly.
|
|
2459
|
7310
|
|
|
7311 If you put @code{(setq tab-width 6)} in your
|
|
|
7312 @file{init.el} file it does not work! Is there a reason
|
|
|
7313 for this? If you do it at the EVAL prompt it works fine!! How strange.
|
|
|
7314
|
|
|
7315 Use @code{setq-default} instead, since @code{tab-width} is
|
|
|
7316 all-buffer-local.
|
|
|
7317
|
|
2537
|
7318 @node Q7.0.4, Q7.0.5, Q7.0.3, Advanced
|
|
|
7319 @unnumberedsubsec Q7.0.4: How can I add directories to the @code{load-path}?
|
|
2459
|
7320
|
|
|
7321 Here are two ways to do that, one that puts your directories at the
|
|
|
7322 front of the load-path, the other at the end:
|
|
|
7323
|
|
|
7324 @lisp
|
|
|
7325 ;;; Add things at the beginning of the load-path, do not add
|
|
|
7326 ;;; duplicate directories:
|
|
|
7327 (pushnew "bar" load-path :test 'equal)
|
|
|
7328
|
|
|
7329 (pushnew "foo" load-path :test 'equal)
|
|
|
7330
|
|
|
7331 ;;; Add things at the end, unconditionally
|
|
|
7332 (setq load-path (nconc load-path '("foo" "bar")))
|
|
|
7333 @end lisp
|
|
|
7334
|
|
|
7335 @email{keithh@@nortel.ca, keith (k.p.) hanlan} writes:
|
|
|
7336
|
|
|
7337 @quotation
|
|
|
7338 To add directories using Unix shell metacharacters use
|
|
|
7339 @file{expand-file-name} like this:
|
|
|
7340
|
|
|
7341 @lisp
|
|
|
7342 (push (expand-file-name "~keithh/.emacsdir") load-path)
|
|
|
7343 @end lisp
|
|
|
7344 @end quotation
|
|
|
7345
|
|
2537
|
7346 @node Q7.0.5, Q7.0.6, Q7.0.4, Advanced
|
|
|
7347 @unnumberedsubsec Q7.0.5: How to check if a lisp function is defined?
|
|
2459
|
7348
|
|
|
7349 Use the following elisp:
|
|
|
7350
|
|
|
7351 @lisp
|
|
|
7352 (fboundp 'foo)
|
|
|
7353 @end lisp
|
|
|
7354
|
|
|
7355 It's almost always a mistake to test @code{emacs-version} or any similar
|
|
|
7356 variables.
|
|
|
7357
|
|
|
7358 Instead, use feature-tests, such as @code{featurep}, @code{boundp},
|
|
|
7359 @code{fboundp}, or even simple behavioral tests, eg.:
|
|
|
7360
|
|
|
7361 @lisp
|
|
|
7362 (defvar foo-old-losing-code-p
|
|
|
7363 (condition-case nil (progn (losing-code t) nil)
|
|
|
7364 (wrong-number-of-arguments t)))
|
|
|
7365 @end lisp
|
|
|
7366
|
|
|
7367 There is an incredible amount of broken code out there which could work
|
|
|
7368 much better more often in more places if it did the above instead of
|
|
|
7369 trying to divine its environment from the value of one variable.
|
|
|
7370
|
|
2537
|
7371 @node Q7.0.6, Q7.1.1, Q7.0.5, Advanced
|
|
|
7372 @unnumberedsubsec Q7.0.6: Can I force the output of @code{(face-list)} to a buffer?
|
|
2459
|
7373
|
|
|
7374 It would be good having it in a buffer, as the output of
|
|
|
7375 @code{(face-list)} is too wide to fit to a minibuffer.
|
|
|
7376
|
|
|
7377 Evaluate the expression in the @samp{*scratch*} buffer with point after
|
|
|
7378 the rightmost paren and typing @kbd{C-j}.
|
|
|
7379
|
|
|
7380 If the minibuffer smallness is the only problem you encounter, you can
|
|
|
7381 simply press @kbd{C-h l} to get the former minibuffer contents in a
|
|
|
7382 buffer.
|
|
|
7383
|
|
2537
|
7384 @unnumberedsec 7.1: Emacs Lisp Programming Techniques
|
|
|
7385
|
|
|
7386 @node Q7.1.1, Q7.1.2, Q7.0.6, Advanced
|
|
|
7387 @unnumberedsubsec Q7.1.1: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
2459
|
7388
|
|
|
7389 @email{clerik@@naggum.no, Erik Naggum} writes;
|
|
|
7390
|
|
|
7391 @quotation
|
|
|
7392 Emacs has a legacy of keyboards that produced characters with modifier
|
|
|
7393 bits, and therefore map a variety of input systems into this scheme even
|
|
|
7394 today. XEmacs is instead optimized for X events. This causes an
|
|
|
7395 incompatibility in the way key sequences are specified, but both Emacs
|
|
|
7396 and XEmacs will accept a key sequence as a vector of lists of modifiers
|
|
|
7397 that ends with a key, e.g., to bind @kbd{M-C-a}, you would say
|
|
|
7398 @code{[(meta control a)]} in both Emacsen. XEmacs has an abbreviated
|
|
|
7399 form for a single key, just (meta control a). Emacs has an abbreviated
|
|
|
7400 form for the Control and the Meta modifiers to string-characters (the
|
|
|
7401 ASCII characters), as in @samp{\M-\C-a}. XEmacs users need to be aware
|
|
|
7402 that the abbreviated form works only for one-character key sequences,
|
|
|
7403 while Emacs users need to be aware that the string-character is rather
|
|
|
7404 limited. Specifically, the string-character can accommodate only 256
|
|
|
7405 different values, 128 of which have the Meta modifier and 128 of which
|
|
|
7406 have not. In each of these blocks, only 32 characters have the Control
|
|
|
7407 modifier. Whereas @code{[(meta control A)]} differs from @code{[(meta
|
|
|
7408 control a)]} because the case differs, @samp{\M-\C-a} and @samp{\M-\C-A}
|
|
|
7409 do not. Programmers are advised to use the full common form, both
|
|
|
7410 because it is more readable and less error-prone, and because it is
|
|
|
7411 supported by both Emacsen.
|
|
|
7412 @end quotation
|
|
|
7413
|
|
|
7414 Another (even safer) way to be sure of the key-sequences is to use the
|
|
|
7415 @code{read-kbd-macro} function, which takes a string like @samp{C-c
|
|
|
7416 <up>}, and converts it to the internal key representation of the Emacs
|
|
|
7417 you use. The function is available both on XEmacs and GNU Emacs.
|
|
|
7418
|
|
2537
|
7419 @node Q7.1.2, Q7.1.3, Q7.1.1, Advanced
|
|
|
7420 @unnumberedsubsec Q7.1.2: Can I generate "fake" keyboard events?
|
|
2459
|
7421
|
|
|
7422 I wonder if there is an interactive function that can generate
|
|
|
7423 @dfn{fake} keyboard events. This way, I could simply map them inside
|
|
|
7424 XEmacs.
|
|
|
7425
|
|
|
7426 This seems to work:
|
|
|
7427
|
|
|
7428 @lisp
|
|
|
7429 (defun cg--generate-char-event (ch)
|
|
|
7430 "Generate an event, as if ch has been typed"
|
|
|
7431 (dispatch-event (character-to-event ch)))
|
|
|
7432
|
|
|
7433 ;; Backspace and Delete stuff
|
|
|
7434 (global-set-key [backspace]
|
|
|
7435 (lambda () (interactive) (cg--generate-char-event 127)))
|
|
|
7436 (global-set-key [unknown_keysym_0x4]
|
|
|
7437 (lambda () (interactive) (cg--generate-char-event 4)))
|
|
|
7438 @end lisp
|
|
|
7439
|
|
2537
|
7440 @node Q7.1.3, Q7.1.4, Q7.1.2, Advanced
|
|
|
7441 @unnumberedsubsec Q7.1.3: Could you explain @code{read-kbd-macro} in more detail?
|
|
2459
|
7442
|
|
|
7443 The @code{read-kbd-macro} function returns the internal Emacs
|
|
|
7444 representation of a human-readable string (which is its argument).
|
|
|
7445 Thus:
|
|
|
7446
|
|
|
7447 @lisp
|
|
|
7448 (read-kbd-macro "C-c C-a")
|
|
|
7449 @result{} [(control ?c) (control ?a)]
|
|
|
7450
|
|
|
7451 (read-kbd-macro "C-c C-. <up>")
|
|
|
7452 @result{} [(control ?c) (control ?.) up]
|
|
|
7453 @end lisp
|
|
|
7454
|
|
|
7455 In GNU Emacs the same forms will be evaluated to what GNU Emacs
|
|
|
7456 understands internally---the sequences @code{"\C-x\C-c"} and @code{[3
|
|
|
7457 67108910 up]}, respectively.
|
|
|
7458
|
|
|
7459 The exact @dfn{human-readable} syntax is defined in the docstring of
|
|
|
7460 @code{edmacro-mode}. I'll repeat it here, for completeness.
|
|
|
7461
|
|
|
7462 @quotation
|
|
|
7463 Format of keyboard macros during editing:
|
|
|
7464
|
|
|
7465 Text is divided into @dfn{words} separated by whitespace. Except for
|
|
|
7466 the words described below, the characters of each word go directly as
|
|
|
7467 characters of the macro. The whitespace that separates words is
|
|
|
7468 ignored. Whitespace in the macro must be written explicitly, as in
|
|
|
7469 @kbd{foo @key{SPC} bar @key{RET}}.
|
|
|
7470
|
|
|
7471 @itemize @bullet
|
|
|
7472 @item
|
|
|
7473 The special words @kbd{RET}, @kbd{SPC}, @kbd{TAB}, @kbd{DEL}, @kbd{LFD},
|
|
|
7474 @kbd{ESC}, and @kbd{NUL} represent special control characters. The
|
|
|
7475 words must be written in uppercase.
|
|
|
7476
|
|
|
7477 @item
|
|
|
7478 A word in angle brackets, e.g., @code{<return>}, @code{<down>}, or
|
|
|
7479 @code{<f1>}, represents a function key. (Note that in the standard
|
|
|
7480 configuration, the function key @code{<return>} and the control key
|
|
|
7481 @key{RET} are synonymous.) You can use angle brackets on the words
|
|
|
7482 @key{RET}, @key{SPC}, etc., but they are not required there.
|
|
|
7483
|
|
|
7484 @item
|
|
|
7485 Keys can be written by their @sc{ascii} code, using a backslash followed
|
|
|
7486 by up to six octal digits. This is the only way to represent keys with
|
|
|
7487 codes above \377.
|
|
|
7488
|
|
|
7489 @item
|
|
|
7490 One or more prefixes @kbd{M-} (meta), @kbd{C-} (control), @kbd{S-}
|
|
|
7491 (shift), @kbd{A-} (alt), @kbd{H-} (hyper), and @kbd{s-} (super) may
|
|
|
7492 precede a character or key notation. For function keys, the prefixes
|
|
|
7493 may go inside or outside of the brackets: @code{C-<down>} @equiv{}
|
|
|
7494 @code{<C-down>}. The prefixes may be written in any order: @kbd{M-C-x}
|
|
|
7495 @equiv{} @kbd{C-M-x}.
|
|
|
7496
|
|
|
7497 Prefixes are not allowed on multi-key words, e.g., @kbd{C-abc}, except
|
|
|
7498 that the Meta prefix is allowed on a sequence of digits and optional
|
|
|
7499 minus sign: @kbd{M--123} @equiv{} @kbd{M-- M-1 M-2 M-3}.
|
|
|
7500
|
|
|
7501 @item
|
|
|
7502 The @code{^} notation for control characters also works: @kbd{^M}
|
|
|
7503 @equiv{} @kbd{C-m}.
|
|
|
7504
|
|
|
7505 @item
|
|
|
7506 Double angle brackets enclose command names: @code{<<next-line>>} is
|
|
|
7507 shorthand for @kbd{M-x next-line @key{RET}}.
|
|
|
7508
|
|
|
7509 @item
|
|
|
7510 Finally, @code{REM} or @code{;;} causes the rest of the line to be
|
|
|
7511 ignored as a comment.
|
|
|
7512 @end itemize
|
|
|
7513
|
|
|
7514 Any word may be prefixed by a multiplier in the form of a decimal number
|
|
|
7515 and @code{*}: @code{3*<right>} @equiv{} @code{<right> <right> <right>},
|
|
|
7516 and @code{10*foo} @equiv{}
|
|
|
7517 @iftex
|
|
|
7518 @*
|
|
|
7519 @end iftex
|
|
|
7520 @code{foofoofoofoofoofoofoofoofoofoo}.
|
|
|
7521
|
|
|
7522 Multiple text keys can normally be strung together to form a word, but
|
|
|
7523 you may need to add whitespace if the word would look like one of the
|
|
|
7524 above notations: @code{; ; ;} is a keyboard macro with three semicolons,
|
|
|
7525 but @code{;;;} is a comment. Likewise, @code{\ 1 2 3} is four keys but
|
|
|
7526 @code{\123} is a single key written in octal, and @code{< right >} is
|
|
|
7527 seven keys but @code{<right>} is a single function key. When in doubt,
|
|
|
7528 use whitespace.
|
|
|
7529 @end quotation
|
|
|
7530
|
|
2537
|
7531 @node Q7.1.4, Q7.1.5, Q7.1.3, Advanced
|
|
|
7532 @unnumberedsubsec Q7.1.4: What is the performance hit of @code{let}?
|
|
2459
|
7533
|
|
|
7534 In most cases, not noticeable. Besides, there's no avoiding
|
|
|
7535 @code{let}---you have to bind your local variables, after all. Some
|
|
|
7536 pose a question whether to nest @code{let}s, or use one @code{let} per
|
|
|
7537 function. I think because of clarity and maintenance (and possible
|
|
|
7538 future implementation), @code{let}-s should be used (nested) in a way to
|
|
|
7539 provide the clearest code.
|
|
|
7540
|
|
2537
|
7541 @node Q7.1.5, Q7.1.6, Q7.1.4, Advanced
|
|
|
7542 @unnumberedsubsec Q7.1.5: What is the recommended use of @code{setq}?
|
|
2459
|
7543
|
|
|
7544 @itemize @bullet
|
|
|
7545 @item Global variables
|
|
|
7546
|
|
|
7547 You will typically @code{defvar} your global variable to a default
|
|
|
7548 value, and use @code{setq} to set it later.
|
|
|
7549
|
|
|
7550 It is never a good practice to @code{setq} user variables (like
|
|
|
7551 @code{case-fold-search}, etc.), as it ignores the user's choice
|
|
|
7552 unconditionally. Note that @code{defvar} doesn't change the value of a
|
|
|
7553 variable if it was bound previously. If you wish to change a
|
|
|
7554 user-variable temporarily, use @code{let}:
|
|
|
7555
|
|
|
7556 @lisp
|
|
|
7557 (let ((case-fold-search nil))
|
|
|
7558 ... ; code with searches that must be case-sensitive
|
|
|
7559 ...)
|
|
|
7560 @end lisp
|
|
|
7561
|
|
|
7562 You will notice the user-variables by their docstrings beginning with an
|
|
|
7563 asterisk (a convention).
|
|
|
7564
|
|
|
7565 @item Local variables
|
|
|
7566
|
|
|
7567 Bind them with @code{let}, which will unbind them (or restore their
|
|
|
7568 previous value, if they were bound) after exiting from the @code{let}
|
|
|
7569 form. Change the value of local variables with @code{setq} or whatever
|
|
|
7570 you like (e.g. @code{incf}, @code{setf} and such). The @code{let} form
|
|
|
7571 can even return one of its local variables.
|
|
|
7572
|
|
|
7573 Typical usage:
|
|
|
7574
|
|
|
7575 @lisp
|
|
|
7576 ;; iterate through the elements of the list returned by
|
|
|
7577 ;; `hairy-function-that-returns-list'
|
|
|
7578 (let ((l (hairy-function-that-returns-list)))
|
|
|
7579 (while l
|
|
|
7580 ... do something with (car l) ...
|
|
|
7581 (setq l (cdr l))))
|
|
|
7582 @end lisp
|
|
|
7583
|
|
|
7584 Another typical usage includes building a value simply to work with it.
|
|
|
7585
|
|
|
7586 @lisp
|
|
|
7587 ;; Build the mode keymap out of the key-translation-alist
|
|
|
7588 (let ((inbox (file-truename (expand-file-name box)))
|
|
|
7589 (i 0))
|
|
|
7590 ... code dealing with inbox ...
|
|
|
7591 inbox)
|
|
|
7592 @end lisp
|
|
|
7593
|
|
|
7594 This piece of code uses the local variable @code{inbox}, which becomes
|
|
|
7595 unbound (or regains old value) after exiting the form. The form also
|
|
|
7596 returns the value of @code{inbox}, which can be reused, for instance:
|
|
|
7597
|
|
|
7598 @lisp
|
|
|
7599 (setq foo-processed-inbox
|
|
|
7600 (let .....))
|
|
|
7601 @end lisp
|
|
|
7602 @end itemize
|
|
|
7603
|
|
2537
|
7604 @node Q7.1.6, Q7.1.7, Q7.1.5, Advanced
|
|
|
7605 @unnumberedsubsec Q7.1.6: What is the typical misuse of @code{setq}?
|
|
2459
|
7606
|
|
|
7607 A typical misuse is probably @code{setq}ing a variable that was meant to
|
|
|
7608 be local. Such a variable will remain bound forever, never to be
|
|
|
7609 garbage-collected. For example, the code doing:
|
|
|
7610
|
|
|
7611 @lisp
|
|
|
7612 (defun my-function (whatever)
|
|
|
7613 (setq a nil)
|
|
|
7614 ... build a large list ...
|
|
|
7615 ... and exit ...)
|
|
|
7616 @end lisp
|
|
|
7617
|
|
|
7618 does a bad thing, as @code{a} will keep consuming memory, never to be
|
|
|
7619 unbound. The correct thing is to do it like this:
|
|
|
7620
|
|
|
7621 @lisp
|
|
|
7622 (defun my-function (whatever)
|
|
|
7623 (let (a) ; default initialization is to nil
|
|
|
7624 ... build a large list ...
|
|
|
7625 ... and exit, unbinding `a' in the process ...)
|
|
|
7626 @end lisp
|
|
|
7627
|
|
|
7628 Not only is this prettier syntactically, but it makes it possible for
|
|
|
7629 Emacs to garbage-collect the objects which @code{a} used to reference.
|
|
|
7630
|
|
|
7631 Note that even global variables should not be @code{setq}ed without
|
|
|
7632 @code{defvar}ing them first, because the byte-compiler issues warnings.
|
|
|
7633 The reason for the warning is the following:
|
|
|
7634
|
|
|
7635 @lisp
|
|
|
7636 (defun flurgoze nil) ; ok, global internal variable
|
|
|
7637 ...
|
|
|
7638
|
|
|
7639 (setq flurghoze t) ; ops! a typo, but semantically correct.
|
|
|
7640 ; however, the byte-compiler warns.
|
|
|
7641
|
|
|
7642 While compiling toplevel forms:
|
|
|
7643 ** assignment to free variable flurghoze
|
|
|
7644 @end lisp
|
|
|
7645
|
|
2537
|
7646 @node Q7.1.7, Q7.1.8, Q7.1.6, Advanced
|
|
|
7647 @unnumberedsubsec Q7.1.7: I like the @code{do} form of cl, does it slow things down?
|
|
2459
|
7648
|
|
|
7649 It shouldn't. Here is what Dave Gillespie has to say about cl.el
|
|
|
7650 performance:
|
|
|
7651
|
|
|
7652 @quotation
|
|
|
7653 Many of the advanced features of this package, such as @code{defun*},
|
|
|
7654 @code{loop}, and @code{setf}, are implemented as Lisp macros. In
|
|
|
7655 byte-compiled code, these complex notations will be expanded into
|
|
|
7656 equivalent Lisp code which is simple and efficient. For example, the
|
|
|
7657 forms
|
|
|
7658
|
|
|
7659 @lisp
|
|
|
7660 (incf i n)
|
|
|
7661 (push x (car p))
|
|
|
7662 @end lisp
|
|
|
7663
|
|
|
7664 are expanded at compile-time to the Lisp forms
|
|
|
7665
|
|
|
7666 @lisp
|
|
|
7667 (setq i (+ i n))
|
|
|
7668 (setcar p (cons x (car p)))
|
|
|
7669 @end lisp
|
|
|
7670
|
|
|
7671 which are the most efficient ways of doing these respective operations
|
|
|
7672 in Lisp. Thus, there is no performance penalty for using the more
|
|
|
7673 readable @code{incf} and @code{push} forms in your compiled code.
|
|
|
7674
|
|
|
7675 @emph{Interpreted} code, on the other hand, must expand these macros
|
|
|
7676 every time they are executed. For this reason it is strongly
|
|
|
7677 recommended that code making heavy use of macros be compiled. (The
|
|
|
7678 features labelled @dfn{Special Form} instead of @dfn{Function} in this
|
|
|
7679 manual are macros.) A loop using @code{incf} a hundred times will
|
|
|
7680 execute considerably faster if compiled, and will also garbage-collect
|
|
|
7681 less because the macro expansion will not have to be generated, used,
|
|
|
7682 and thrown away a hundred times.
|
|
|
7683
|
|
|
7684 You can find out how a macro expands by using the @code{cl-prettyexpand}
|
|
|
7685 function.
|
|
|
7686 @end quotation
|
|
|
7687
|
|
2537
|
7688 @node Q7.1.8, Q7.1.9, Q7.1.7, Advanced
|
|
|
7689 @unnumberedsubsec Q7.1.8: I like recursion, does it slow things down?
|
|
2459
|
7690
|
|
|
7691 Yes. The Emacs byte-compiler cannot do much to optimize recursion. But
|
|
|
7692 think well whether this is a real concern in Emacs. Much of the Emacs
|
|
|
7693 slowness comes from internal mechanisms such as redisplay, or from the
|
|
|
7694 fact that it is an interpreter.
|
|
|
7695
|
|
|
7696 Please try not to make your code much uglier to gain a very small speed
|
|
|
7697 gain. It's not usually worth it.
|
|
|
7698
|
|
2537
|
7699 @node Q7.1.9, Q7.1.10, Q7.1.8, Advanced
|
|
|
7700 @unnumberedsubsec Q7.1.9: How do I put a glyph as annotation in a buffer?
|
|
2459
|
7701
|
|
|
7702 Here is a solution that will insert the glyph annotation at the
|
|
|
7703 beginning of buffer:
|
|
|
7704
|
|
|
7705 @lisp
|
|
|
7706 (make-annotation (make-glyph '([FORMAT :file FILE]
|
|
|
7707 [string :data "fallback-text"]))
|
|
|
7708 (point-min)
|
|
|
7709 'text
|
|
|
7710 (current-buffer))
|
|
|
7711 @end lisp
|
|
|
7712
|
|
|
7713 Replace @samp{FORMAT} with an unquoted symbol representing the format of
|
|
|
7714 the image (e.g. @code{xpm}, @code{xbm}, @code{gif}, @code{jpeg}, etc.)
|
|
|
7715 Instead of @samp{FILE}, use the image file name
|
|
|
7716 (e.g.
|
|
|
7717 @iftex
|
|
|
7718 @*
|
|
|
7719 @end iftex
|
|
|
7720 @file{/usr/local/lib/xemacs-21.4/etc/recycle.xpm}).
|
|
|
7721
|
|
|
7722 You can turn this to a function (that optionally prompts you for a file
|
|
|
7723 name), and inserts the glyph at @code{(point)} instead of
|
|
|
7724 @code{(point-min)}.
|
|
|
7725
|
|
2537
|
7726 @node Q7.1.10, Q7.1.11, Q7.1.9, Advanced
|
|
|
7727 @unnumberedsubsec Q7.1.10: @code{map-extents} won't traverse all of my extents!
|
|
2459
|
7728
|
|
|
7729 I tried to use @code{map-extents} to do an operation on all the extents
|
|
|
7730 in a region. However, it seems to quit after processing a random number
|
|
|
7731 of extents. Is it buggy?
|
|
|
7732
|
|
|
7733 No. The documentation of @code{map-extents} states that it will iterate
|
|
|
7734 across the extents as long as @var{function} returns @code{nil}.
|
|
|
7735 Unexperienced programmers often forget to return @code{nil} explicitly,
|
|
|
7736 which results in buggy code. For instance, the following code is
|
|
|
7737 supposed to delete all the extents in a buffer, and issue as many
|
|
|
7738 @samp{fubar!} messages.
|
|
|
7739
|
|
|
7740 @lisp
|
|
|
7741 (map-extents (lambda (ext ignore)
|
|
|
7742 (delete-extent ext)
|
|
|
7743 (message "fubar!")))
|
|
|
7744 @end lisp
|
|
|
7745
|
|
|
7746 Instead, it will delete only the first extent, and stop right there --
|
|
|
7747 because @code{message} will return a non-nil value. The correct code
|
|
|
7748 is:
|
|
|
7749
|
|
|
7750 @lisp
|
|
|
7751 (map-extents (lambda (ext ignore)
|
|
|
7752 (delete-extent ext)
|
|
|
7753 (message "fubar!")
|
|
|
7754 nil))
|
|
|
7755 @end lisp
|
|
|
7756
|
|
2537
|
7757 @node Q7.1.11, Q7.2.1, Q7.1.10, Advanced
|
|
|
7758 @unnumberedsubsec Q7.1.11: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
2459
|
7759 @c New
|
|
|
7760
|
|
|
7761 @email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
|
|
|
7762 @quotation
|
|
|
7763 Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence},
|
|
|
7764 press a key (say @key{RET} in the Gnus Group buffer), and get the
|
|
|
7765 results using @kbd{M-x profile-results}. It should give you an idea of
|
|
|
7766 where the time is being spent.
|
|
|
7767 @end quotation
|
|
|
7768
|
|
2537
|
7769 @unnumberedsec 7.2: Mathematics
|
|
|
7770
|
|
|
7771 @node Q7.2.1, Q7.2.2, Q7.1.11, Advanced
|
|
|
7772 @unnumberedsubsec Q7.2.1: What are bignums, ratios, and bigfloats in Lisp?
|
|
2459
|
7773
|
|
|
7774 Thanks to @email{james@@xemacs.org, Jerry James}, XEmacs 21.5.18 and
|
|
|
7775 later can use the capabilities of multiple-precision libraries that may
|
|
|
7776 be available for your platform. The GNU Multiple Precision (GMP) and
|
|
|
7777 BSD Multiple Precision (MP) libraries are partially supported. GMP
|
|
|
7778 gives you @dfn{bignums} (arbitrary precision integers), @dfn{ratios}
|
|
|
7779 (arbitrary precision fractions), and @dfn{bigfloats} (arbitrary
|
|
|
7780 precision floating point numbers). GNU MP is better-supported by XEmacs
|
|
|
7781 at the time of writing (2004-04-06). BSD MP support does not include
|
|
|
7782 ratios or bigfloats, and it throws errors that aren't understood.
|
|
|
7783
|
|
|
7784 In most cases, bignum support should be transparent to users and Lisp
|
|
|
7785 programmers. A bignum-enabled XEmacs will automatically convert from
|
|
|
7786 fixnums to bignums and back in pure integer arithmetic, and for GNU MP,
|
|
|
7787 from floats to bigfloats. (Bigfloats must be explicitly coerced to
|
|
|
7788 other types, even if they are exactly representable by less precise
|
|
|
7789 types.) The Lisp reader and printer have been enhanced to handle
|
|
|
7790 bignums, as have the mathematical functions. Rationals (fixnums,
|
|
|
7791 bignums, and ratios) are printed using the @samp{%d}, @samp{%o},
|
|
|
7792 @samp{%x}, and @samp{%u} format conversions. The read syntax for ratios
|
|
|
7793 is @samp{3/5}.
|
|
|
7794
|
|
|
7795 User-visible changes in behavior include (in probable order of annoyance)
|
|
|
7796
|
|
|
7797 @itemize
|
|
|
7798 @item
|
|
|
7799 Arithmetic can cause a segfault, depending on your MP library
|
|
2537
|
7800 @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}.
|
|
2459
|
7801
|
|
|
7802 @item
|
|
|
7803 Terminology is not Common-Lisp-conforming. For example, ``integer'' for
|
|
|
7804 Emacs Lisp means what Common Lisp calls ``fixnum''. This issue is being
|
|
|
7805 investigated, but the use of ``integer'' for fixnum is pervasive and may
|
|
|
7806 cause backward-compatibility and GNU-Emacs-compatibility problems.
|
|
|
7807
|
|
|
7808 @item
|
|
|
7809 Many operations that used to cause a range error now succeed, with
|
|
|
7810 intermediate results and return values coerced to bignums as needed.
|
|
|
7811
|
|
|
7812 @item
|
|
|
7813 An atom with ratio read syntax now returns a number, not a symbol.
|
|
|
7814
|
|
|
7815 @item
|
|
|
7816 The @samp{%u} format conversion will now give an error if its argument
|
|
|
7817 is negative. (Without MP, it prints a number which Lisp can't read.)
|
|
|
7818 @end itemize
|
|
|
7819
|
|
|
7820 @emph{Surgeon General's Warning}: The automatic conversions cannot be
|
|
|
7821 disabled at runtime. New functions have been added which produce
|
|
|
7822 ratios, so there should be few surprises with type conflicts, but they
|
|
|
7823 can't be ruled out. ``Arbitrary'' precision means precisely what it
|
|
|
7824 says. If you work with extremely large numbers, your machine may
|
|
|
7825 arbitrarily decide to hand you an unpleasant surprise rather than a
|
|
2537
|
7826 bignum @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}.
|
|
2459
|
7827
|
|
3018
|
7828 To configure with GNU MP, add @samp{--use-number-lib=gmp}
|
|
|
7829 (@samp{--enable-bignum=gmp} in 21.5 or later) to your invocation of
|
|
|
7830 @file{configure}. For BSD MP, use @samp{--use-number-lib=mp}
|
|
|
7831 (@samp{--enable-bignum=mp} for 21.5).
|
|
2459
|
7832
|
|
|
7833 If you would like to help with bignum support, especially on BSD MP,
|
|
|
7834 please subscribe to the @uref{http://www.xemacs.org/Lists/#xemacs-beta,
|
|
|
7835 XEmacs Beta mailing list}, and book up on @file{number-gmp.h} and
|
|
|
7836 @file{number-mp.h}. Jerry has promised to write internals documentation
|
|
|
7837 eventually, but if your skills run more to analysis and documentation
|
|
|
7838 than to writing new code, feel free to fill in the gap!
|
|
|
7839
|
|
|
7840
|
|
2537
|
7841 @node Q7.2.2, Q7.2.3, Q7.2.1, Advanced
|
|
|
7842 @unnumberedsubsec Q7.2.2: XEmacs segfaults when I use very big numbers!
|
|
2459
|
7843
|
|
|
7844 GMP by default allocates temporaries on the stack. If you run out of
|
|
|
7845 stack space, you're dead; there is no way that we know of to reliably
|
|
|
7846 detect this condition, because @samp{alloca} is typically implemented to
|
|
|
7847 be @emph{fast} rather than robust. If you just need a little more
|
|
|
7848 oomph, use a bigger stack (@emph{e.g.}, the @file{ulimit -s} command in
|
|
|
7849 bash(1)). If you want robustness at the cost of speed, configure GMP
|
|
|
7850 with @samp{--disable-alloca} and rebuild the GMP library.
|
|
|
7851
|
|
|
7852 We do not know whether BSD MP uses @samp{alloca} or not. Please send
|
|
|
7853 any information you have as a bug report (@kbd{M-x report-xemacs-bug
|
|
|
7854 @key{RET}}), which will give us platform information. (We do know that
|
|
|
7855 BSD MP implementations vary across vendors, but how much, we do not know
|
|
|
7856 yet.)
|
|
|
7857
|
|
|
7858
|
|
2537
|
7859 @node Q7.2.3, Q7.2.4, Q7.2.2, Advanced
|
|
|
7860 @unnumberedsubsec Q7.2.3: Bignums are really slow!
|
|
2459
|
7861
|
|
|
7862 Many Linux distributions compile all their packages for the i386, and
|
|
|
7863 this is costly. An optimized version can give you two or three orders
|
|
|
7864 of magnitude better performance for a Pentium III or IV. (Yes, really.
|
|
|
7865 See @uref{http://www.swox.com/gmp/gmp-speed.html}.)
|
|
|
7866
|
|
|
7867
|
|
2537
|
7868 @node Q7.2.4, , Q7.2.3, Advanced
|
|
|
7869 @unnumberedsubsec Q7.2.4: Equal bignums don't compare as equal! What gives?
|
|
2459
|
7870
|
|
|
7871 Ah, Grasshopper, I see you are using @code{(eq x y)}. The Bodhisattva
|
|
|
7872 CLTL2 warned of the illusion that equal numbers would be @samp{eq}!
|
|
|
7873 Meditate on the deeper truths of @samp{eql}, in which numbers of the same
|
|
|
7874 type which have equal values compare equal, and @samp{=}, which does any
|
|
|
7875 necessary type coercions before comparing for equality.
|
|
|
7876
|
|
|
7877 Yeah, yeah, it has always worked for integer types, because fixnums and
|
|
|
7878 characters have an immediate representation. Sorry about that;
|
|
|
7879 arbitrary precision obviously requires consing new objects because the
|
|
|
7880 objects are ``large'' and of variable size, and the definition of
|
|
|
7881 @samp{eq} does not permit different objects to compare as equal.
|
|
|
7882
|
|
|
7883 @node Other Packages, Current Events, Advanced, Top
|
|
|
7884 @unnumbered 8 Other External Packages
|
|
|
7885
|
|
|
7886 This is part 8 of the XEmacs Frequently Asked Questions list. This
|
|
|
7887 section is devoted to miscellaneous external packages not covered
|
|
|
7888 elsewhere in XEmacs.
|
|
|
7889
|
|
|
7890 @menu
|
|
2537
|
7891 8.0: TeX
|
|
2459
|
7892 * Q8.0.1:: Is there something better than LaTeX mode?
|
|
|
7893 * Q8.0.2:: What is AUCTeX? Where do you get it?
|
|
|
7894 * Q8.0.3:: Problems installing AUCTeX.
|
|
|
7895 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline?
|
|
|
7896
|
|
|
7897 8.1: Other Unbundled Packages
|
|
|
7898 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
|
7899 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets?
|
|
|
7900 * Q8.1.3:: Is there a MatLab mode?
|
|
|
7901
|
|
|
7902 8.2: Environments Built Around XEmacs
|
|
|
7903 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop?
|
|
|
7904 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21?
|
|
|
7905 * Q8.2.3:: What is/was Energize?
|
|
|
7906 * Q8.2.4:: What is Infodock?
|
|
|
7907 @end menu
|
|
|
7908
|
|
|
7909 @unnumberedsec 8.0: TeX
|
|
|
7910
|
|
|
7911 @node Q8.0.1, Q8.0.2, Other Packages, Other Packages
|
|
|
7912 @unnumberedsubsec Q8.0.1: Is there something better than LaTeX mode?
|
|
2417
|
7913
|
|
|
7914 @email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes:
|
|
|
7915
|
|
|
7916 @quotation
|
|
|
7917 The standard TeX modes leave much to be desired, and are somewhat
|
|
2459
|
7918 leniently maintained. Serious TeX users use AUCTeX (@pxref{Q8.0.2,
|
|
2417
|
7919 What is AUCTeX? Where do you get it?}).
|
|
|
7920 @end quotation
|
|
|
7921
|
|
2459
|
7922 @node Q8.0.2, Q8.0.3, Q8.0.1, Other Packages
|
|
|
7923 @unnumberedsubsec Q8.0.2: What is AUCTeX? Where do you get it?
|
|
2417
|
7924
|
|
|
7925 AUCTeX is a complex and sophisticated editing package dedicated to TeX
|
|
|
7926 and related text formatting languages, including LaTeX and Texinfo.
|
|
|
7927 It provides support for running TeX on a file or part of a file,
|
|
|
7928 include files, and of course shortcuts for entering common TeX macros,
|
|
|
7929 LaTeX environments, etc, and for fontlock.
|
|
|
7930
|
|
|
7931 AUCTeX is a standard package provided by XEmacs. You can get it as
|
|
|
7932 usual through the @kbd{M-x list-packages} interface. It is also
|
|
|
7933 included in the (non-Mule) SUMO package. The AUCTeX XEmacs package is
|
|
|
7934 maintained by Uwe Brauer <GET MAIL ADDRESS>.
|
|
|
7935
|
|
|
7936 AUCTeX is extremely complicated, and its developers primarily
|
|
|
7937 use GNU Emacs. Not all features of the bleeding edge version
|
|
|
7938 of AUCTeX are immediately ported to XEmacs; if you need
|
|
|
7939 these, you may be better off getting the most recent versions
|
|
|
7940 from the GNU AUCTeX project on @uref{http://savannah.gnu.org}.
|
|
|
7941
|
|
2459
|
7942 @node Q8.0.3, Q8.0.4, Q8.0.2, Other Packages
|
|
|
7943 @unnumberedsubsec Q8.0.3: Problems installing AUCTeX.
|
|
2417
|
7944
|
|
|
7945 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
|
|
|
7946
|
|
|
7947 @quotation
|
|
|
7948 AUCTeX works fine on both stock Emacs and XEmacs has been doing so for
|
|
|
7949 a very very long time. This is mostly due to the work of
|
|
|
7950 @email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu}
|
|
|
7951 package. Which leads to what is probably the problem...
|
|
|
7952 @end quotation
|
|
|
7953
|
|
|
7954 Most problems with AUCTeX are one of two things:
|
|
|
7955
|
|
|
7956 @itemize @bullet
|
|
|
7957 @item
|
|
|
7958 The TeX-lisp-directory in @file{tex-site.el} and the makefile don't
|
|
|
7959 match.
|
|
|
7960
|
|
|
7961 Fix: make sure you configure AUCTeX properly @strong{before} installing.
|
|
|
7962
|
|
|
7963 @item
|
|
|
7964 You have an old version of easymenu.el in your path.
|
|
|
7965
|
|
|
7966 Fix: use @code{locate-library} and remove old versions to make sure it
|
|
|
7967 @strong{only} finds the one that came with XEmacs.
|
|
|
7968 @end itemize
|
|
|
7969
|
|
2459
|
7970 @node Q8.0.4, Q8.1.1, Q8.0.3, Other Packages
|
|
|
7971 @unnumberedsubsec Q8.0.4: How do I turn off current chapter from AUCTeX modeline?
|
|
2417
|
7972
|
|
|
7973 With AUCTeX, fast typing is hard because the current chapter, section
|
|
|
7974 etc. are given in the modeline. How can I turn this off?
|
|
|
7975
|
|
|
7976 It's not AUCTeX, it comes from @code{func-menu} in @file{func-menu.el}.
|
|
|
7977
|
|
|
7978 @c Add this code to your @file{init.el} to turn it off:
|
|
|
7979 @c
|
|
|
7980 @c @lisp
|
|
|
7981 @c (setq fume-display-in-modeline-p nil)
|
|
|
7982 @c @end lisp
|
|
|
7983 @c
|
|
|
7984 @c Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
|
|
|
7985 @c mode:
|
|
|
7986 @c
|
|
|
7987 @c @lisp
|
|
|
7988 @c (add-hook 'TeX-mode-hook
|
|
|
7989 @c '(lambda () (setq fume-display-in-modeline-p nil)))
|
|
|
7990 @c @end lisp
|
|
|
7991 @c
|
|
|
7992 @email{dhughes@@origin-at.co.uk, David Hughes} writes:
|
|
|
7993
|
|
|
7994 @quotation
|
|
|
7995 Try this; you'll still get the function name displayed in the modeline,
|
|
|
7996 but it won't attempt to keep track when you modify the file. To refresh
|
|
|
7997 when it gets out of synch, you simply need click on the @samp{Rescan
|
|
|
7998 Buffer} option in the function-menu.
|
|
|
7999
|
|
|
8000 @lisp
|
|
|
8001 (setq-default fume-auto-rescan-buffer-p nil)
|
|
|
8002 @end lisp
|
|
|
8003 @end quotation
|
|
|
8004
|
|
2459
|
8005 @unnumberedsec 8.1: Other Unbundled Packages
|
|
|
8006
|
|
|
8007 @node Q8.1.1, Q8.1.2, Q8.0.4, Other Packages
|
|
|
8008 @unnumberedsubsec Q8.1.1: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
2417
|
8009
|
|
|
8010 The reason for an Emacs package not to be included in XEmacs is
|
|
|
8011 usually one or more of the following:
|
|
|
8012
|
|
|
8013 @enumerate
|
|
|
8014 @item
|
|
|
8015 The package has not been ported to XEmacs. This will typically happen
|
|
|
8016 when it uses GNU-Emacs-specific features, which make it fail under
|
|
|
8017 XEmacs.
|
|
|
8018
|
|
|
8019 Porting a package to XEmacs can range from a trivial amount of change to
|
|
|
8020 a partial or full rewrite. Fortunately, the authors of modern packages
|
|
|
8021 usually choose to support both Emacsen themselves.
|
|
|
8022
|
|
|
8023 @item
|
|
|
8024 The package has been decided not to be appropriate for XEmacs. It may
|
|
|
8025 have an equivalent or better replacement within XEmacs, in which case
|
|
|
8026 the developers may choose not to burden themselves with supporting an
|
|
|
8027 additional package.
|
|
|
8028
|
|
|
8029 Each package bundled with XEmacs means more work for the maintainers,
|
|
|
8030 whether they want it or not. If you are ready to take over the
|
|
|
8031 maintenance responsibilities for the package you port, be sure to say
|
|
|
8032 so---we will more likely include it.
|
|
|
8033
|
|
|
8034 @item
|
|
|
8035 The package simply hasn't been noted by the XEmacs development. If
|
|
|
8036 that's the case, the messages like yours are very useful for attracting
|
|
|
8037 our attention.
|
|
|
8038
|
|
|
8039 @item
|
|
|
8040 The package was noted by the developers, but they simply haven't yet
|
|
|
8041 gotten around to including/porting it. Wait for the next release or,
|
|
|
8042 even better, offer your help. It will be gladly accepted and
|
|
|
8043 appreciated.
|
|
|
8044 @end enumerate
|
|
|
8045
|
|
2459
|
8046 @node Q8.1.2, Q8.1.3, Q8.1.1, Other Packages
|
|
|
8047 @unnumberedsubsec Q8.1.2: Are there any Emacs Lisp Spreadsheets?
|
|
2417
|
8048
|
|
|
8049 Yes. Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at
|
|
428
|
8050 @iftex
|
|
|
8051 @*
|
|
|
8052 @end iftex
|
|
2459
|
8053 @uref{http://acs.ist.psu.edu/dismal/dismal.html}.
|
|
|
8054
|
|
|
8055 @node Q8.1.3, Q8.2.1, Q8.1.2, Other Packages
|
|
|
8056 @unnumberedsubsec Q8.1.3: Is there a MatLab mode?
|
|
2417
|
8057
|
|
|
8058 Yes, a matlab mode and other items are available at the
|
|
2459
|
8059 @uref{http://www.mathworks.com/matlabcentral/files/104/matlab.el}.
|
|
|
8060
|
|
|
8061 @unnumberedsec 8.2: Environments Built Around XEmacs
|
|
|
8062
|
|
|
8063 @node Q8.2.1, Q8.2.2, Q8.1.3, Other Packages
|
|
|
8064 @unnumberedsubsec Q8.2.1: What are SPARCworks, EOS, and WorkShop?
|
|
2417
|
8065
|
|
|
8066 SPARCworks was a development environment from Sun (circa 1993-1996)
|
|
|
8067 and consisted of compilers (C, C++, FORTRAN 77, Fortran 90, Ada, and
|
|
|
8068 Pascal), a debugger, and other tools such as TeamWare (for
|
|
|
8069 configuration management), MakeTool, etc.
|
|
428
|
8070
|
|
|
8071 EOS is the integration of XEmacs with the SPARCworks debugger. It
|
|
|
8072 allows one to use an XEmacs frame to view code (complete with
|
|
|
8073 fontification, etc.), set breakpoints, print variables, etc., while
|
|
2417
|
8074 using the SPARCworks debugger.
|
|
|
8075
|
|
|
8076 EOS stands for "Era on SPARCworks"; Era stood for "Emacs Rewritten
|
|
|
8077 Again" and was the name used by Sun for its modified version of Lucid
|
|
|
8078 Emacs (later XEmacs) in the early-mid 90's. This is documented in
|
|
|
8079 more detail in the history section of the XEmacs About page.
|
|
|
8080
|
|
|
8081 EOS was replaced around 1996 with a newer graphical development
|
|
|
8082 environment called Sun WorkShop. The current status of this is
|
|
|
8083 unknown.
|
|
|
8084
|
|
2459
|
8085 @node Q8.2.2, Q8.2.3, Q8.2.1, Other Packages
|
|
|
8086 @unnumberedsubsec Q8.2.2: How do I start the Sun Workshop support in XEmacs 21?
|
|
428
|
8087
|
|
|
8088 Add the switch ---with-workshop to the configure command when building
|
|
|
8089 XEmacs and put the following in one of your startup files
|
|
|
8090 (e.g. site-start.el or .emacs):
|
|
|
8091
|
|
|
8092 @lisp
|
|
|
8093 (when (featurep 'tooltalk)
|
|
|
8094 (load "tooltalk-macros")
|
|
|
8095 (load "tooltalk-util")
|
|
|
8096 (load "tooltalk-init"))
|
|
|
8097 (when (featurep 'sparcworks)
|
|
|
8098 (load "sunpro-init")
|
|
|
8099 (load "ring")
|
|
|
8100 (load "comint")
|
|
|
8101 (load "annotations")
|
|
|
8102 (sunpro-startup))
|
|
|
8103 @end lisp
|
|
|
8104
|
|
|
8105 If you are not using the latest Workshop (5.0) you have to apply the
|
|
|
8106 following patch:
|
|
|
8107
|
|
|
8108 @format
|
|
|
8109 --- /opt/SUNWspro/lib/eserve.el.ORIG Fri May 14 15:23:26 1999
|
|
|
8110 +++ /opt/SUNWspro/lib/eserve.el Fri May 14 15:24:54 1999
|
|
|
8111 @@@@ -42,7 +42,7 @@@@
|
|
|
8112 (defvar running-xemacs nil "t if we're running XEmacs")
|
|
|
8113 (defvar running-emacs nil "t if we're running GNU Emacs 19")
|
|
438
|
8114
|
|
428
|
8115 -(if (string-match "^\\(19\\|20\\)\..*\\(XEmacs\\|Lucid\\)" emacs-version)
|
|
|
8116 +(if (string-match "\\(XEmacs\\|Lucid\\)" emacs-version)
|
|
|
8117 (setq running-xemacs t)
|
|
|
8118 (setq running-emacs t))
|
|
438
|
8119 @end format
|
|
428
|
8120
|
|
2459
|
8121 @node Q8.2.3, Q8.2.4, Q8.2.2, Other Packages
|
|
|
8122 @unnumberedsubsec Q8.2.3: What is/was Energize?
|
|
2417
|
8123
|
|
|
8124 The "Energize Programming System" was a C and C++ development environment
|
|
|
8125 sold by Lucid, Inc. It was the reason why Lucid Emacs, now XEmacs, was
|
|
|
8126 created in the first place. Unfortunately, Lucid went out of business in
|
|
|
8127 1994. The rights to sell it in Japan were purchased by INS
|
|
|
8128 Engineering (which briefly employed Stig Hackvan aka Jonathan
|
|
|
8129 Stigelman to work on Japanese support for XEmacs, in late 1994 and
|
|
|
8130 early 1995) and Tartan bought the rights to sell it in the rest of the
|
|
|
8131 world. However, INS is not selling Energize at this point and may or
|
|
|
8132 may not have ever done so; Tartan certainly never did.
|
|
|
8133
|
|
2459
|
8134 @node Q8.2.4, , Q8.2.3, Other Packages
|
|
|
8135 @unnumberedsubsec Q8.2.4: What is Infodock?
|
|
428
|
8136
|
|
660
|
8137 @uref{http://sourceforge.net/projects/infodock/, InfoDock} is an
|
|
|
8138 integrated productivity toolset, mainly aimed at technical people,
|
|
|
8139 hosted at SourceForge.
|
|
428
|
8140
|
|
|
8141 InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of
|
|
|
8142 the power of Emacs, but with an easier to use and more comprehensive
|
|
|
8143 menu-based user interface. The bottom portion of this text describes
|
|
|
8144 how it differs from XEmacs and GNU Emacs from the Free Software
|
|
|
8145 Foundation.
|
|
|
8146
|
|
|
8147 InfoDock is aimed at people who want a free, turn-key productivity
|
|
|
8148 environment. Although InfoDock is customizable, it is not intended for
|
|
|
8149 people who like basic versions of Emacs which need to be customized
|
|
|
8150 extensively for local use; standard Emacs distributions are better for
|
|
|
8151 such uses. InfoDock is for those people who want a complete,
|
|
|
8152 pre-customized environment in one package, which they need not touch
|
|
|
8153 more than once or twice a year to update to new revisions.
|
|
|
8154
|
|
|
8155 InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX,
|
|
|
8156 and Intel Linux systems. It is intended for use on a color display,
|
|
|
8157 although most features will work on monochrome monitors. Simply unpack
|
|
|
8158 InfoDock according to the instructions in the ID-INSTALL file and you
|
|
|
8159 are ready to run.
|
|
|
8160
|
|
|
8161 The InfoDock Manual is concise, yet sufficient as a user guide for users
|
|
|
8162 who have never used an Emacs-type editor before. For users who are
|
|
|
8163 already familiar with Emacs, it supplements the information in the GNU
|
|
|
8164 Emacs Manual.
|
|
|
8165
|
|
|
8166 InfoDock menus are much more extensive and more mature than standard
|
|
|
8167 Emacs menus. Each menu offers a @samp{Manual} item which displays
|
|
|
8168 documentation associated with the menu's functions.
|
|
|
8169
|
|
|
8170 @noindent
|
|
|
8171 Four types of menubars are provided:
|
|
|
8172 @enumerate
|
|
|
8173 @item
|
|
|
8174 An extensive menubar providing access to global InfoDock commands.
|
|
|
8175 @item
|
|
|
8176 Mode-specific menubars tailored to the current major mode.
|
|
|
8177 @item
|
|
|
8178 A simple menubar for basic editing to help novices get started with InfoDock.
|
|
|
8179 @item
|
|
|
8180 The standard XEmacs menubar.
|
|
|
8181 @end enumerate
|
|
|
8182
|
|
|
8183 Most modes also include mode-specific popup menus. Additionally, region and
|
|
|
8184 rectangle popup menus are included.
|
|
|
8185
|
|
|
8186 @samp{Hyperbole}, the everyday information manager, is a core part of
|
|
|
8187 InfoDock. This provides context-sensitive mouse keys, a rolodex-type
|
|
|
8188 contact manager, programmable hypertext buttons, and an autonumbered
|
|
|
8189 outliner with embedded hyperlink anchors.
|
|
|
8190
|
|
|
8191 The @samp{OO-Browser}, a multi-language object-oriented code browser, is a
|
|
|
8192 standard part of InfoDock.
|
|
|
8193
|
|
|
8194 InfoDock saves a more extensive set of user options than other Emacs
|
|
|
8195 versions.
|
|
|
8196
|
|
|
8197 InfoDock inserts a useful file header in many file types, showing the
|
|
|
8198 author, summary, and last modification time of each file. A summary
|
|
|
8199 program can then be used to summarize all of the files in a directory,
|
|
|
8200 for easy MANIFEST file creation.
|
|
|
8201
|
|
|
8202 Your working set of buffers is automatically saved and restored (if you
|
|
|
8203 answer yes to a prompt) between InfoDock sessions.
|
|
|
8204
|
|
|
8205 Refined color choices for code highlighting are provided for both dark and
|
|
|
8206 light background display frames.
|
|
|
8207
|
|
|
8208 The @kbd{C-z} key prefix performs frame-based commands which parallel the
|
|
|
8209 @kbd{C-x} key prefix for window-based commands.
|
|
|
8210
|
|
|
8211 The Smart Menu system is included for producing command menus on dumb
|
|
|
8212 terminals.
|
|
|
8213
|
|
|
8214 Lisp libraries are better categorized according to function.
|
|
|
8215
|
|
|
8216 Extensions and improvements to many areas of Emacs are included, such as:
|
|
|
8217 paragraph filling, mail reading with Rmail, shell handling, outlining, code
|
|
|
8218 highlighting and browsing, and man page browsing.
|
|
|
8219
|
|
|
8220 InfoDock questions, answers and discussion should go to the mail list
|
|
|
8221 @iftex
|
|
|
8222 @*
|
|
|
8223 @end iftex
|
|
|
8224 @email{infodock@@infodock.com}. Use
|
|
|
8225 @email{infodock-request@@infodock.com} to be added or removed from the
|
|
|
8226 list. Always include your InfoDock version number when sending help
|
|
|
8227 requests.
|
|
|
8228
|
|
2459
|
8229 @node Current Events, Legacy Versions, Other Packages, Top
|
|
|
8230 @unnumbered 9 What the Future Holds
|
|
|
8231
|
|
|
8232 This is part 9 of the XEmacs Frequently Asked Questions list. This
|
|
611
|
8233 section will change frequently, and (in theory) should contain any
|
|
|
8234 interesting items that have transpired recently. (But in practice it's
|
|
|
8235 not getting updated like this.)
|
|
|
8236
|
|
|
8237 This section also contains descriptions of the new features in all the
|
|
|
8238 recent releases of XEmacs. For the most part, the information below is
|
|
|
8239 a synopsis of the more complete information that can be found in the
|
|
|
8240 file @file{NEWS} in the @file{etc} directory of the XEmacs distribution.
|
|
|
8241 You can view this file in XEmacs using @kbd{C-h n} or the @samp{Help}
|
|
|
8242 menu.
|
|
|
8243
|
|
|
8244 Information on older versions of XEmacs can be find in @file{ONEWS} in
|
|
|
8245 the same directory, or @file{OONEWS} for really old versions.
|
|
|
8246
|
|
428
|
8247 @menu
|
|
2537
|
8248 9.0: Changes
|
|
2459
|
8249 * Q9.0.1:: What new features will be in XEmacs soon?
|
|
|
8250 * Q9.0.2:: What's new in XEmacs 21.4?
|
|
|
8251 * Q9.0.3:: What's new in XEmacs 21.1?
|
|
|
8252 * Q9.0.4:: What's new in XEmacs 20.4?
|
|
|
8253 * Q9.0.5:: What's new in XEmacs 20.3?
|
|
|
8254 * Q9.0.6:: What's new in XEmacs 20.2?
|
|
428
|
8255 @end menu
|
|
|
8256
|
|
2459
|
8257 @unnumberedsec 9.0: Changes
|
|
|
8258
|
|
|
8259 @node Q9.0.1, Q9.0.2, Current Events, Current Events
|
|
|
8260 @unnumberedsubsec Q9.0.1: What new features will be in XEmacs soon?
|
|
611
|
8261
|
|
2417
|
8262 #### Write me.
|
|
428
|
8263
|
|
2459
|
8264 @node Q9.0.2, Q9.0.3, Q9.0.1, Current Events
|
|
|
8265 @unnumberedsubsec Q9.0.2: What's new in XEmacs 21.4?
|
|
611
|
8266
|
|
|
8267 21.4 was the "stable" version of the 21.2 series, which was considered
|
|
|
8268 "experimental" throughout its life; thus there were no "official"
|
|
|
8269 releases at all. In essence, XEmacs is now following the "alternating"
|
|
|
8270 scheme of Linux, where at any point there are at least two different
|
|
|
8271 development branches, one "stable" and one "experimental". Periodic
|
|
|
8272 releases happen in both branches, but those in the experimental branch
|
|
|
8273 are not tested as well, and there's no guarantee they will work at all.
|
|
|
8274 The experiemental branch is open to any and all code that's acceptable
|
|
|
8275 to the developers; the stable branch, however, is in general limited
|
|
|
8276 only to bug fixes, and all contributions are carefully reviewed to make
|
|
|
8277 sure they will increase and not decrease stability.
|
|
|
8278
|
|
|
8279 21.3 never existed at all; it was decided to follow the Linux scheme
|
|
|
8280 exactly, where odd-numbered series are experimental and even-numbered
|
|
|
8281 ones stable.
|
|
|
8282
|
|
|
8283 The following lists summarizes the essential changes made in this
|
|
|
8284 version. For a fuller list, see the @file{NEWS} in the @file{etc}
|
|
|
8285 directory of the XEmacs distribution, or use @kbd{C-h n} or the
|
|
|
8286 @samp{Help} menu to view this file inside of XEmacs.
|
|
|
8287
|
|
676
|
8288 @unnumberedsubsubsec User-visible changes in XEmacs 21.4
|
|
611
|
8289
|
|
|
8290 @itemize @bullet
|
|
|
8291
|
|
|
8292 @item
|
|
|
8293 The delete key now deletes forward by default.
|
|
|
8294 @item
|
|
|
8295 Shifted motion keys now select text by default.
|
|
|
8296 @item
|
|
|
8297 You can now build XEmacs with support for GTK+ widget set.
|
|
|
8298 @item
|
|
|
8299 ~/.xemacs/init.el is now the preferred location for the init
|
|
|
8300 file. (XEmacs now supports a `~/.xemacs/init.el' startup file. Custom
|
|
|
8301 file will move to ~/.xemacs/custom.el.)
|
|
|
8302 @item
|
|
|
8303 Much-improved sample init.el, showing how to use many useful features.
|
|
|
8304 @item
|
|
|
8305 XEmacs support for menu accelerators has been much improved.
|
|
|
8306 @item
|
|
|
8307 Default menubar improvements. (Default menubar has many new commands and
|
|
|
8308 better organization. The font-menu is now available under MS Windows.)
|
|
|
8309 @item
|
|
2417
|
8310 Dialog box improvements, including a real file dialog box. (XEmacs now
|
|
|
8311 has a proper file dialog box under MS Windows (and GTK)! The old
|
|
|
8312 clunky file dialog box is improved. Keyboard traversal now works
|
|
|
8313 correctly in MS Windows dialog boxes. There is a Search dialog box
|
|
|
8314 available from @samp{Edit->Find...})
|
|
611
|
8315 @item
|
|
|
8316 New buffer tabs.
|
|
|
8317 @item
|
|
|
8318 There is a new MS Windows installer, netinstall, ported from Cygwin.
|
|
|
8319 @item
|
|
|
8320 The subprocess quote-handling mechanism under Windows is much improved.
|
|
|
8321 @item
|
|
|
8322 Printing support now available under MS Windows.
|
|
|
8323 @item
|
|
|
8324 Selection improvements. (Kill and yank now interact with the clipboard under Windows. MS Windows support for selection is now much more robust. Motif selection support is now more correct (but slower).)
|
|
|
8325 @item
|
|
|
8326 Mail spool locking now works correctly.
|
|
|
8327 @item
|
|
|
8328 International support changes. (The default coding-priority-list is now
|
|
|
8329 safer. International keysyms are now supported under X. MS Windows
|
|
|
8330 1251 code page now supported. Czech, Thai, Cyrillic-KOI8, Vietnamese,
|
|
|
8331 Ethiopic now supported. Proper support for words in Latin 3 and Latin
|
|
|
8332 4.)
|
|
|
8333 @item
|
|
|
8334 Help buffers contain hyperlinks, and other changes.
|
|
|
8335 @item
|
|
|
8336 The modeline's text is now scrollable.
|
|
|
8337 @item
|
|
|
8338 The mouse wheel under MS Windows now functions correctly.
|
|
|
8339 @item
|
|
|
8340 Interactive searching and matching case improvements. (Incremental search will now highlight all visible matches. Interactive searches always respect uppercase characters.)
|
|
|
8341 @item
|
|
|
8342 Rectangle functions rewritten to avoid inserting extra spaces.
|
|
|
8343 @item
|
|
|
8344 New command `kill-entire-line' that always kills the entire line.
|
|
|
8345 @item
|
|
|
8346 Default values correctly stored in minibuffer histories.
|
|
|
8347 @item
|
|
|
8348 You can now create "indirect buffers", like in GNU Emacs.
|
|
|
8349 @item
|
|
|
8350 Pixel-based scrolling has been implemented.
|
|
|
8351 @item
|
|
|
8352 Operation progress can be displayed using graphical widgets.
|
|
|
8353 @item
|
|
|
8354 User names following a tilde can now be completed at file name prompts.
|
|
|
8355 @item
|
|
|
8356 XEmacs can now play sound using Enlightenment Sound Daemon (ESD).
|
|
|
8357 @item
|
|
|
8358 X-Face support is now available under MS Windows.
|
|
|
8359 @item
|
|
|
8360 The PostgreSQL Relational Database Management System is now supported.
|
|
|
8361 @item
|
|
|
8362 Indentation no longer indents comments that begin at column zero.
|
|
|
8363 @item
|
|
|
8364 Face and variable settings can have comments in Customize.
|
|
|
8365 @item
|
|
|
8366 New locations for early package hierarchies.
|
|
|
8367 @item
|
|
|
8368 The `auto-save' library has been greatly improved.
|
|
|
8369 @item
|
|
|
8370 New variable `mswindows-alt-by-itself-activates-menu'.
|
|
|
8371 @item
|
|
|
8372 Other init-file-related changes. (Init file in your home directory may be called `.emacs.el'. New command-line switches -user-init-file and -user-init-directory.)
|
|
|
8373 @item
|
|
|
8374 Etags changes. See @file{NEWS} for full details.
|
|
|
8375 @end itemize
|
|
|
8376
|
|
676
|
8377 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.4
|
|
611
|
8378
|
|
|
8379 Not yet written.
|
|
|
8380
|
|
661
|
8381 @c APA: Texi2html produces invalid HTML from an empty list of bullets!
|
|
|
8382 @c Please uncomment following list when it does contain bullets.
|
|
|
8383 @c @itemize @bullet
|
|
|
8384 @c @end itemize
|
|
611
|
8385
|
|
2459
|
8386 @node Q9.0.3, Q9.0.4, Q9.0.2, Current Events
|
|
|
8387 @unnumberedsubsec Q9.0.3: What's new in XEmacs 21.1?
|
|
611
|
8388
|
|
|
8389 21.1 was the "stable" version of "experimental" 21.0 series.
|
|
2459
|
8390 @xref{Q9.0.2, What's new in XEmacs 21.4?}.
|
|
611
|
8391
|
|
|
8392 The following lists summarizes the essential changes made in this
|
|
|
8393 version. For a fuller list, see the @file{NEWS} in the @file{etc}
|
|
|
8394 directory of the XEmacs distribution, or use @kbd{C-h n} or the
|
|
|
8395 @samp{Help} menu to view this file inside of XEmacs.
|
|
|
8396
|
|
676
|
8397 @unnumberedsubsubsec User-visible changes in XEmacs 21.1
|
|
611
|
8398
|
|
|
8399 @itemize @bullet
|
|
|
8400
|
|
|
8401 @item
|
|
2459
|
8402 XEmacs is now supported under Microsoft Windows 95/98 and Windows
|
|
2417
|
8403 NT/2000/XP operating systems. To discuss Windows-specific issues,
|
|
|
8404 subscribe to the mailing list at
|
|
|
8405 @email{xemacs-winnt-request@@xemacs.org}.
|
|
611
|
8406
|
|
|
8407 @item
|
|
|
8408 XEmacs has been unbundled into constituent installable packages.
|
|
|
8409
|
|
|
8410 @item
|
|
|
8411 @strong{Other notable changes}: The @samp{Options} menu has been ported to
|
|
|
8412 Custom; XEmacs now is able to choose X visuals and use private
|
|
|
8413 colormaps; You can drag the vertical divider of "horizontally"
|
|
|
8414 (side-by-side) split windows.
|
|
|
8415
|
|
|
8416 @item
|
|
|
8417 @strong{Building changes}: XEmacs can be built with support for 31-bit Lisp
|
|
|
8418 integers and 32-bit pointers (previously, it was 28-bit integers and
|
|
|
8419 pointers); XEmacs can be built with LDAP support; @file{dir} files can be
|
|
|
8420 removed in the Info subsystem, and will be regenerated on-the-fly.
|
|
|
8421
|
|
|
8422 @item
|
|
|
8423 @strong{New packages}: @file{imenu}, @file{popper}, @file{gdb-highlight}
|
|
|
8424
|
|
|
8425 @item
|
|
|
8426 @strong{Package changes}: Many changes to @file{cc-mode}, @file{gnus},
|
|
|
8427 @file{gnuclient}. See @file{NEWS} for full details.
|
|
|
8428
|
|
|
8429 @item
|
|
|
8430 @strong{New commands, variables and functions}:
|
|
|
8431 @code{center-to-window-line} (like @code{recenter} but doesn't force a
|
|
|
8432 redisplay); variable @code{user-full-name} (customize what your full
|
|
|
8433 name looks like in mail); @kbd{M-x customize-changed-options} (customize
|
|
|
8434 options whose default values changes because you upgraded your XEmacs);
|
|
|
8435 @kbd{M-x add-log-convert} (converts an old-style ChangeLog buffer to
|
|
|
8436 new-style); @kbd{M-x zap-up-to-char} (like @code{zap-to-char} but
|
|
|
8437 doesn't delete the char searched for); commands to store, retrieve and
|
|
|
8438 increment numbers in registers, useful for macros.
|
|
|
8439
|
|
|
8440 @item
|
|
|
8441 @strong{Changes to commands, variables, and functions}: @kbd{M-x
|
|
|
8442 query-replace} and friends operate only on the region when it's active;
|
|
|
8443 @code{echo-keystrokes} can now be a floating-point number; @kbd{M-.}
|
|
|
8444 searches exact tag matches before inexact ones; function
|
|
|
8445 @code{user-full-name} with no arguments returns the var
|
|
|
8446 @code{user-full-name}; a prefix arg to @kbd{M-:} and @kbd{C-h c} inserts
|
|
|
8447 the result in the current buffer.
|
|
1138
|
8448
|
|
611
|
8449 @item
|
|
|
8450 @strong{Other changes}: Under X, new application class @samp{XEmacs};
|
|
|
8451 byte-compilation of user-specs now works.
|
|
|
8452
|
|
|
8453 @item
|
|
|
8454 @strong{XEmacs/Mule (internationalization) changes}: Mule support now
|
|
|
8455 works on TTY's; Egg/SJ3 input method now officially supported (Quail and
|
|
|
8456 Egg/Skk already available through LEIM since 20.3); localized Japanese
|
|
|
8457 menubars if XEmacs is built with the right support.
|
|
|
8458
|
|
|
8459 @end itemize
|
|
|
8460
|
|
676
|
8461 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.1
|
|
611
|
8462
|
|
|
8463 @itemize @bullet
|
|
|
8464
|
|
|
8465 @item
|
|
|
8466 @strong{Specifier changes}: The window locale now has a higher
|
|
|
8467 precedence than the buffer locale when instantiating; new macro
|
|
|
8468 @code{let-specifier}; new specifiers
|
|
|
8469 @code{vertical-scrollbar-visible-p}, horizontal-scrollbar-visible-p',
|
|
|
8470 @code{scrollbar-on-left-p}, @code{scrollbar-on-top-p},
|
|
|
8471 @code{vertical-divider-always-visible-p},
|
|
|
8472 @code{vertical-divider-shadow-thickness},
|
|
|
8473 @code{vertical-divider-line-width}, @code{vertical-divider-spacing};
|
|
|
8474 specifiers and symbols whose value is a specifier allowed as modeline
|
|
|
8475 specifications.
|
|
|
8476
|
|
|
8477 @item
|
|
|
8478 @strong{Frame focus changes}: @code{focus-follows-mouse} works like FSF,
|
|
|
8479 prevents any attempt to permanently change the selected frame; new
|
|
|
8480 function @code{focus-frame} sets the window system focus a frame; new
|
|
|
8481 special forms @code{save-selected-frame} and @code{with-selected-frame}.
|
|
|
8482
|
|
|
8483 @item
|
|
|
8484 @strong{Window function changes}: @code{select-window} now has optional
|
|
|
8485 argument @var{NORECORD} to inhibit recording a buffer change;
|
|
|
8486 @code{vertical-motion} now correctly handles optional @var{WINDOW}
|
|
|
8487 argument and has new optional argument @var{PIXELS}, to have the
|
|
|
8488 returned values be in pixels; new function
|
|
|
8489 @code{vertical-motion-pixels}; new functions
|
|
|
8490 @code{window-text-area-pixel-@{width,height,edges@}}; new functions
|
|
|
8491 @code{shrink-window-pixels} and @code{enlarge-window-pixels}; new
|
|
|
8492 function @code{window-displayed-text-pixel-height}.
|
|
|
8493
|
|
|
8494 @item
|
|
|
8495 @strong{Other function changes}: Arithmetic comparison functions
|
|
|
8496 @code{<}, @code{>}, @code{=}, @code{/=} now accept a variable number of
|
|
|
8497 arguments; hashtables now have a consistent read/print syntax; keyword
|
|
|
8498 symbols cannot be set to a value other than themselves; @code{concat} no
|
|
|
8499 longer accepts integer arguments; new function @code{string}, like
|
|
|
8500 @code{list}, @code{vector}, etc.; new function @code{temp-directory}
|
|
|
8501 (OS-independent way to get a temp directory); @code{load-average} has
|
|
|
8502 optional argument @var{USE-FLOATS}; @code{make-event} implemented
|
|
|
8503 completely; new function @code{function-interactive} (returns a
|
|
|
8504 function's interactive spec); new functions @code{lmessage},
|
|
|
8505 @code{lwarn} (printf-like versions of @code{display-wessage},
|
|
|
8506 @code{display-warning}); new keyword @code{:version} to
|
|
|
8507 @code{defcustom}.
|
|
|
8508
|
|
|
8509 @item
|
|
|
8510 @strong{Performance}: when the new GNU Malloc aka Doug Lea Malloc is
|
|
|
8511 available, it will be used (better performance on libc6 Linux systems);
|
|
|
8512 tracking line-numbers in modeline is now efficient; profiling records a
|
|
|
8513 call-count of all called functions, retrievable through
|
|
|
8514 @code{profile-call-count-results}.
|
|
|
8515
|
|
|
8516 @item
|
|
|
8517 @strong{Startup and path searching}: code to assemble paths at startup
|
|
|
8518 rewritten for new package system; new function @code{split-path} (splits
|
|
|
8519 by @code{path-separator}); @code{Info-default-directory-list} obsolete,
|
|
|
8520 use @code{Info-directory-list} instead; site-lisp is deprecated and no
|
|
|
8521 longer on the load-path by default.
|
|
|
8522
|
|
|
8523 @end itemize
|
|
|
8524
|
|
2459
|
8525 @node Q9.0.4, Q9.0.5, Q9.0.3, Current Events
|
|
|
8526 @unnumberedsubsec Q9.0.4: What's new in XEmacs 20.4?
|
|
611
|
8527
|
|
|
8528 XEmacs 20.4 is a bugfix release with no user-visible changes.
|
|
|
8529 @c Filled in from NEWS file of 20.5-b33
|
|
|
8530
|
|
2459
|
8531 @node Q9.0.5, Q9.0.6, Q9.0.4, Current Events
|
|
|
8532 @unnumberedsubsec Q9.0.5: What's new in XEmacs 20.3?
|
|
428
|
8533
|
|
|
8534 XEmacs 20.3 was released in November 1997. It contains many bugfixes,
|
|
|
8535 and a number of new features, including Autoconf 2 based configuration,
|
|
|
8536 additional support for Mule (Multi-language extensions to Emacs), many
|
|
|
8537 more customizations, multiple frames on TTY-s, support for multiple info
|
|
|
8538 directories, an enhanced gnuclient, improvements to regexp matching,
|
|
|
8539 increased MIME support, and many, many synches with GNU Emacs 20.
|
|
|
8540
|
|
|
8541 The XEmacs/Mule support has been only seriously tested in a Japanese
|
|
|
8542 locale, and no doubt many problems still remain. The support for
|
|
|
8543 ISO-Latin-1 and Japanese is fairly strong. MULE support comes at a
|
|
440
|
8544 price---about a 30% slowdown from 19.16. We're making progress on
|
|
428
|
8545 improving performance and XEmacs 20.3 compiled without Mule (which is
|
|
|
8546 the default) is definitely faster than XEmacs 19.16.
|
|
|
8547
|
|
|
8548 XEmacs 20.3 is the first non-beta v20 release, and will be the
|
|
|
8549 basis for all further development.
|
|
|
8550
|
|
2459
|
8551 @node Q9.0.6, , Q9.0.5, Current Events
|
|
|
8552 @unnumberedsubsec Q9.0.6: What's new in XEmacs 20.2?
|
|
611
|
8553
|
|
|
8554 The biggest changes in 20.2 include integration of EFS (the next
|
|
|
8555 generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a
|
|
|
8556 major mode for editing Tex and LaTeX, and a lot of other stuff). Many
|
|
|
8557 bugs from 20.0 have been fixed for this release. 20.2 also contains a
|
|
|
8558 new system for customizing XEmacs options, invoked via @kbd{M-x
|
|
|
8559 customize}.
|
|
|
8560
|
|
|
8561 XEmacs 20.2 is the development release (20.0 was beta), and is no longer
|
|
|
8562 considered unstable.
|
|
|
8563
|
|
|
8564 For older news, see the file @file{ONEWS} in the @file{etc} directory of
|
|
|
8565 the XEmacs distribution.
|
|
428
|
8566
|
|
2417
|
8567 @node Legacy Versions, , Current Events, Top
|
|
2459
|
8568 @unnumbered 10 New information about old XEmacsen
|
|
|
8569
|
|
|
8570 This is part 10 of the XEmacs Frequently Asked Questions list. It will
|
|
1495
|
8571 occasionally be updated to reflect new information about versions which
|
|
|
8572 are no longer being revised by the XEmacs Project. The primary purpose
|
|
|
8573 is advice on compatibility of older XEmacsen with new packages and
|
|
|
8574 updated versions of packages, but bug fixes (which will not be applied
|
|
|
8575 to released XEmacsen, but users can apply themselves) are also accepted.
|
|
|
8576
|
|
|
8577 @menu
|
|
2537
|
8578 10.0: XEmacs 21.1
|
|
2459
|
8579 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
2559
|
8580 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1.
|
|
1495
|
8581 @end menu
|
|
|
8582
|
|
2459
|
8583 @unnumberedsec 10.0: XEmacs 21.1
|
|
|
8584
|
|
2559
|
8585 @node Q10.0.1, Q10.0.2, Legacy Versions, Legacy Versions
|
|
2459
|
8586 @unnumberedsubsec Q10.0.1: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
1495
|
8587
|
|
|
8588 @email{eeide@@cs.utah.edu, Eric Eide} wrote:
|
|
|
8589
|
|
|
8590 @quotation
|
|
|
8591 Previously I wrote:
|
|
|
8592
|
|
|
8593 Eric> Summary: with Gnus 5.10.1 in XEmacs 21.1.14, I don't see
|
|
|
8594 Eric> any smileys :-(.
|
|
|
8595
|
|
|
8596 After a bit of sleuthing, I discovered the essence of the problem.
|
|
|
8597 For me, the form:
|
|
|
8598
|
|
|
8599 @lisp
|
|
|
8600 (with-temp-buffer
|
|
|
8601 (insert-file-contents "foo.xpm")
|
|
|
8602 (buffer-string))
|
|
|
8603 @end lisp
|
|
|
8604
|
|
|
8605 returns the empty string. This is because something somewhere
|
|
|
8606 replaces the XPM data with a glyph --- I haven't figured out where
|
|
|
8607 this occurs.
|
|
|
8608 @end quotation
|
|
|
8609
|
|
|
8610 @email{kyle_jones@@wonderworks.com, Kyle Jones} replies:
|
|
|
8611
|
|
|
8612 @quotation
|
|
|
8613 Do this:
|
|
|
8614
|
|
|
8615 @lisp
|
|
|
8616 (setq format-alist nil)
|
|
|
8617 @end lisp
|
|
|
8618
|
|
|
8619 The image-mode stuff is gone from format-alist in the 21.4
|
|
|
8620 branch, praise be.
|
|
|
8621 @end quotation
|
|
|
8622
|
|
2559
|
8623 @node Q10.0.2, , Q10.0.1, Legacy Versions
|
|
|
8624 @unnumberedsubsec Q10.0.2: XEmacs won't start on Windows in XEmacs 21.1.
|
|
|
8625
|
|
|
8626 XEmacs relies on a process called "dumping" to generate a working
|
|
|
8627 executable. Under MS-Windows this process effectively fixes the memory
|
|
|
8628 addresses of information in the executable. When XEmacs starts up it tries
|
|
|
8629 to reserve these memory addresses so that the dumping process can be
|
|
|
8630 reversed -- putting the information back at the correct addresses.
|
|
|
8631 Unfortunately some .DLLs (for instance the soundblaster driver) occupy
|
|
|
8632 memory addresses that can conflict with those needed by the dumped XEmacs
|
|
|
8633 executable. In this instance XEmacs will fail to start without any
|
|
|
8634 explanation. Note that this is extremely machine specific.
|
|
|
8635
|
|
|
8636 21.1.10 includes a fix for this that makes more intelligent guesses
|
|
|
8637 about which memory addresses will be free, and this should cure the
|
|
|
8638 problem for most people. 21.4 implements "portable dumping", which
|
|
|
8639 eliminates the problem altogether. We recommend you use the 21.4
|
|
|
8640 binaries, but you can use the 21.1 binaries if you are very paranoid
|
|
|
8641 about stability. @xref{Q1.1.2, Are binaries available?}.
|
|
|
8642
|
|
428
|
8643 @bye
|
