|
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
|
|
2559
|
10 @subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2005/02/04 02:51:21 $
|
|
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"
|
|
|
458
|
|
|
459 5.5: Multiple Device Support
|
|
|
460 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display?
|
|
|
461 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
462 * Q5.5.3:: How do I disable gnuserv from opening a new frame?
|
|
|
463 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
|
464 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
|
465
|
|
|
466 6 Connecting to the Internet
|
|
|
467
|
|
|
468 6.0: General Mail and News
|
|
|
469 * Q6.0.1:: What are the various packages for reading mail?
|
|
|
470 * Q6.0.2:: How can I send mail?
|
|
|
471 * Q6.0.3:: How do I get my outgoing mail archived?
|
|
|
472 * Q6.0.4:: How can I read and/or compose MIME messages?
|
|
|
473 * Q6.0.5:: How do I customize the From line?
|
|
|
474 * Q6.0.6:: How do I get my MUA to filter mail for me?
|
|
|
475 * Q6.0.7:: Remote mail reading with an MUA.
|
|
|
476 * Q6.0.8:: An MUA gets an error incorporating new mail.
|
|
|
477 * Q6.0.9:: Why isn't @file{movemail} working?
|
|
|
478 * Q6.0.10:: How do I make my MUA display graphical smilies?
|
|
|
479 * Q6.0.11:: How can I get those oh-so-neat X-Face lines?
|
|
|
480
|
|
|
481 6.1: Reading Mail with VM
|
|
|
482 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
483 * Q6.1.2:: How can I get VM to automatically check for new mail?
|
|
|
484 * 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"?
|
|
|
485 * Q6.1.4:: Is there a mailing list or FAQ for VM?
|
|
|
486 * Q6.1.5:: How do I make VM stay in a single frame?
|
|
|
487 * Q6.1.6:: Customization of VM not covered in the manual, or here.
|
|
|
488
|
|
|
489 6.2: Reading Netnews and Mail with Gnus
|
|
|
490 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
491 * Q6.2.2:: How do I make Gnus stay within a single frame?
|
|
|
492
|
|
|
493 6.3: FTP Access
|
|
|
494 * Q6.3.1:: Can I edit files on other hosts?
|
|
|
495 * Q6.3.2:: What is EFS?
|
|
|
496
|
|
|
497 6.4: Web Browsing with W3
|
|
|
498 * Q6.4.1:: What is W3?
|
|
|
499 * Q6.4.2:: How do I run W3 from behind a firewall?
|
|
|
500 * Q6.4.3:: Is it true that W3 supports style sheets and tables?
|
|
|
501
|
|
|
502 7 Advanced Customization Using XEmacs Lisp
|
|
|
503
|
|
2537
|
504 7.0: Emacs Lisp and @file{init.el}
|
|
|
505 * Q7.0.1:: What version of Emacs am I running?
|
|
|
506 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions?
|
|
|
507 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly.
|
|
|
508 * Q7.0.4:: How can I add directories to the @code{load-path}?
|
|
|
509 * Q7.0.5:: How to check if a lisp function is defined?
|
|
|
510 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer?
|
|
|
511
|
|
|
512 7.1: Emacs Lisp Programming Techniques
|
|
|
513 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
|
514 * Q7.1.2:: Can I generate "fake" keyboard events?
|
|
|
515 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail?
|
|
|
516 * Q7.1.4:: What is the performance hit of @code{let}?
|
|
|
517 * Q7.1.5:: What is the recommended use of @code{setq}?
|
|
|
518 * Q7.1.6:: What is the typical misuse of @code{setq}?
|
|
|
519 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down?
|
|
|
520 * Q7.1.8:: I like recursion, does it slow things down?
|
|
|
521 * Q7.1.9:: How do I put a glyph as annotation in a buffer?
|
|
|
522 * Q7.1.10:: @code{map-extents} won't traverse all of my extents!
|
|
|
523 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
|
524
|
|
|
525 7.2: Mathematics
|
|
2559
|
526 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp?
|
|
|
527 * Q7.2.2:: XEmacs segfaults when I use very big numbers!
|
|
|
528 * Q7.2.3:: Bignums are really slow!
|
|
|
529 * Q7.2.4:: Equal bignums don't compare as equal! What gives?
|
|
2459
|
530
|
|
|
531 8 Other External Packages
|
|
|
532
|
|
|
533 8.0: TeX
|
|
|
534 * Q8.0.1:: Is there something better than LaTeX mode?
|
|
|
535 * Q8.0.2:: What is AUCTeX? Where do you get it?
|
|
|
536 * Q8.0.3:: Problems installing AUCTeX.
|
|
|
537 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline?
|
|
|
538
|
|
|
539 8.1: Other Unbundled Packages
|
|
|
540 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
|
541 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets?
|
|
|
542 * Q8.1.3:: Is there a MatLab mode?
|
|
|
543
|
|
|
544 8.2: Environments Built Around XEmacs
|
|
|
545 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop?
|
|
|
546 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21?
|
|
|
547 * Q8.2.3:: What is/was Energize?
|
|
|
548 * Q8.2.4:: What is Infodock?
|
|
|
549
|
|
|
550 9 What the Future Holds
|
|
|
551
|
|
|
552 9.0: Changes
|
|
|
553 * Q9.0.1:: What new features will be in XEmacs soon?
|
|
|
554 * Q9.0.2:: What's new in XEmacs 21.4?
|
|
|
555 * Q9.0.3:: What's new in XEmacs 21.1?
|
|
|
556 * Q9.0.4:: What's new in XEmacs 20.4?
|
|
|
557 * Q9.0.5:: What's new in XEmacs 20.3?
|
|
|
558 * Q9.0.6:: What's new in XEmacs 20.2?
|
|
|
559
|
|
|
560 10 New information about old XEmacsen
|
|
|
561
|
|
|
562 10.0: XEmacs 21.1
|
|
|
563 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
2559
|
564 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1.
|
|
|
565
|
|
428
|
566 @end detailmenu
|
|
|
567 @end menu
|
|
|
568
|
|
|
569 @node Introduction, Installation, Top, Top
|
|
|
570 @unnumbered 1 Introduction, Policy, Credits
|
|
|
571
|
|
|
572 Learning XEmacs is a lifelong activity. Even people who have used Emacs
|
|
|
573 for years keep discovering new features. Therefore this document cannot
|
|
|
574 be complete. Instead it is aimed at the person who is either
|
|
|
575 considering XEmacs for their own use, or has just obtained it and is
|
|
|
576 wondering what to do next. It is also useful as a reference to
|
|
|
577 available resources.
|
|
|
578
|
|
2417
|
579 The previous maintainer of the FAQ was
|
|
|
580 @email{rossini@@biostat.washington.edu, Anthony Rossini}, who started
|
|
|
581 it, after getting tired of hearing JWZ complain about repeatedly
|
|
|
582 having to answer questions. @email{ben@@xemacs.org, Ben Wing} then
|
|
|
583 took over and did a massive update reorganizing the whole thing. At
|
|
|
584 this point Anthony took back over, but then had to give it up again.
|
|
|
585 Some of the other contributors to this FAQ are listed later in this
|
|
|
586 document.
|
|
428
|
587
|
|
|
588 The previous version was converted to hypertext format, and edited by
|
|
|
589 @email{steve@@xemacs.org, Steven L. Baur}. It was converted back to
|
|
434
|
590 texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}. The FAQ was then
|
|
|
591 maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it
|
|
2417
|
592 on to ChristianNyb@o{}, and then to @email{wambold@@xemacs.org,Sandra Wambold}.
|
|
|
593
|
|
|
594 The current version of the FAQ has been heavily redone by
|
|
|
595 @email{ben@@xemacs.org, Ben Wing}.
|
|
428
|
596
|
|
|
597 If you notice any errors or items which should be added or amended to
|
|
2417
|
598 this FAQ please send email to @email{xemacs-beta@@xemacs.org}.
|
|
|
599 Include @samp{XEmacs FAQ} on the Subject: line.
|
|
428
|
600
|
|
|
601 @menu
|
|
2537
|
602 1.0: What is XEmacs?
|
|
2417
|
603 * Q1.0.1:: What is XEmacs?
|
|
|
604 * Q1.0.2:: What is the current version of XEmacs?
|
|
2537
|
605 * Q1.0.3:: How do you pronounce XEmacs?
|
|
|
606 * Q1.0.4:: What does XEmacs look like?
|
|
|
607 * Q1.0.5:: Who wrote XEmacs?
|
|
|
608 * Q1.0.6:: Who wrote the FAQ?
|
|
|
609
|
|
|
610 1.1: Getting XEmacs
|
|
|
611 * Q1.1.1:: Where can I find XEmacs?
|
|
|
612 * Q1.1.2:: Are binaries available?
|
|
|
613 * Q1.1.3:: How do I get the bleeding-edge sources?
|
|
|
614 * Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual?
|
|
|
615
|
|
|
616 1.2: Versions for Different Operating Systems
|
|
|
617 * Q1.2.1:: Do I need X11 to run XEmacs?
|
|
|
618 * Q1.2.2:: What versions of Unix does XEmacs run on?
|
|
|
619 * Q1.2.3:: Is there a port of XEmacs to Microsoft Windows?
|
|
|
620 * Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
621 * Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
622 * Q1.2.6:: What are the differences between the various MS Windows emacsen?
|
|
|
623 * Q1.2.7:: How does the port cope with differences in the Windows user interface?
|
|
|
624 * Q1.2.8:: Is there a port of XEmacs to the Macintosh?
|
|
|
625 * Q1.2.9:: Is there a port of XEmacs to MS-DOS?
|
|
|
626 * Q1.2.10:: Is there a port of XEmacs to OS/2?
|
|
|
627 * Q1.2.11:: Is there a port of XEmacs to NextStep?
|
|
|
628 * Q1.2.12:: Is there a port of XEmacs to VMS?
|
|
|
629
|
|
|
630 1.3: Getting Started
|
|
|
631 * Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
|
632 * Q1.3.2:: Where do I put my @file{init.el} file?
|
|
|
633 * Q1.3.3:: Can I use the same @file{init.el} with the other Emacs?
|
|
|
634 * Q1.3.4:: Any good XEmacs tutorials around?
|
|
|
635 * Q1.3.5:: May I see an example of a useful XEmacs Lisp function?
|
|
|
636 * Q1.3.6:: And how do I bind it to a key?
|
|
|
637 * Q1.3.7:: What's the difference between a macro and a function?
|
|
|
638 * Q1.3.8:: What is @code{Custom}?
|
|
|
639
|
|
|
640 1.4: Getting Help
|
|
|
641 * Q1.4.1:: Where can I get help?
|
|
|
642 * Q1.4.2:: Which mailing lists are there?
|
|
2559
|
643 * Q1.4.3:: Where are the mailing lists archived?
|
|
|
644 * Q1.4.4:: How can I get two instances of info?
|
|
|
645 * Q1.4.5:: How do I add new Info directories?
|
|
2537
|
646
|
|
|
647 1.5: Contributing to XEmacs
|
|
|
648 * Q1.5.1:: How do I submit changes to the FAQ?
|
|
|
649 * Q1.5.2:: How do I become a beta tester?
|
|
|
650 * Q1.5.3:: How do I contribute to XEmacs itself?
|
|
2559
|
651 * Q1.5.4:: How do I get started developing XEmacs?
|
|
|
652 * Q1.5.5:: What's the basic layout of the code?
|
|
2537
|
653
|
|
|
654 1.6: Politics (XEmacs vs. GNU Emacs)
|
|
|
655 * Q1.6.1:: What is GNU Emacs?
|
|
|
656 * Q1.6.2:: How does XEmacs differ from GNU Emacs?
|
|
|
657 * Q1.6.3:: How much does XEmacs differ?
|
|
|
658 * Q1.6.4:: Is XEmacs "GNU"?
|
|
|
659 * Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
|
660 * Q1.6.6:: Why haven't XEmacs and GNU Emacs merged?
|
|
|
661
|
|
|
662 1.7: External Packages
|
|
2559
|
663 * Q1.7.1:: What is the package system?
|
|
|
664 * Q1.7.2:: Which external packages are there?
|
|
|
665 * Q1.7.3:: Do I need to have the packages to run XEmacs?
|
|
|
666 * Q1.7.4:: Is there a way to find which package has particular functionality?
|
|
2537
|
667
|
|
|
668 1.8: Internationalization
|
|
|
669 * Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
|
670 * Q1.8.2:: How can I help with internationalization?
|
|
|
671 * Q1.8.3:: How do I type non-ASCII characters?
|
|
|
672 * Q1.8.4:: Can XEmacs messages come out in a different language?
|
|
|
673 * Q1.8.5:: Please explain the various input methods in MULE/XEmacs
|
|
|
674 * Q1.8.6:: How do I portably code for MULE/XEmacs?
|
|
|
675 * Q1.8.7:: How about Cyrillic modes?
|
|
|
676 * Q1.8.8:: Does XEmacs support Unicode?
|
|
|
677 * Q1.8.9:: How does XEmacs display Unicode?
|
|
428
|
678 @end menu
|
|
|
679
|
|
2537
|
680 @unnumberedsec 1.0: What is XEmacs?
|
|
2417
|
681
|
|
428
|
682 @node Q1.0.1, Q1.0.2, Introduction, Introduction
|
|
|
683 @unnumberedsubsec Q1.0.1: What is XEmacs?
|
|
|
684
|
|
479
|
685 XEmacs is a powerful, highly customizable open source text editor and
|
|
2417
|
686 application development system, with full GUI support. It is
|
|
|
687 protected under the GNU Public License and related to other versions
|
|
|
688 of Emacs, in particular GNU Emacs. Its emphasis is on modern
|
|
|
689 graphical user interface support and an open software development
|
|
|
690 model, similar to Linux. XEmacs has an active development community
|
|
|
691 numbering in the hundreds (and thousands of active beta testers on top
|
|
|
692 of this), and runs on all versions of MS Windows, on Mac OS X, on
|
|
|
693 Linux, and on nearly every other version of Unix in existence.
|
|
|
694 Support for XEmacs has been supplied by Sun Microsystems, University
|
|
|
695 of Illinois, Lucid, ETL/Electrotechnical Laboratory, Amdahl
|
|
|
696 Corporation, BeOpen, and others, as well as the unpaid time of a great
|
|
|
697 number of individual developers.
|
|
428
|
698
|
|
|
699 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction
|
|
|
700 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs?
|
|
|
701
|
|
2417
|
702 XEmacs versions 21.4.* are releases made from the current stable
|
|
|
703 sources. XEmacs versions 21.5.* (which will be released as 22.0) are
|
|
|
704 releases made from the development sources. Check at
|
|
|
705 @uref{http://www.xemacs.org} for the current minor version. XEmacs
|
|
|
706 versions 21.1.* were the previous stable releases, now retired.
|
|
|
707
|
|
|
708 XEmacs 20.4, released in February 1998, was the last release of v20.
|
|
|
709
|
|
|
710 XEmacs 19.16, released in November, 1997. was the last release of v19,
|
|
|
711 and was also the last version without international language support.
|
|
428
|
712
|
|
|
713 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction
|
|
2537
|
714 @unnumberedsubsec Q1.0.3: How do you pronounce XEmacs?
|
|
|
715
|
|
|
716 The most common pronounciation is @samp{Eks eemax}.
|
|
428
|
717
|
|
|
718 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction
|
|
2537
|
719 @unnumberedsubsec Q1.0.4: What does XEmacs look like?
|
|
|
720
|
|
|
721 Screen snapshots are available at
|
|
|
722 @uref{http://www.xemacs.org/About/Screenshots/index.html}
|
|
|
723 as part of the XEmacs website.
|
|
|
724
|
|
|
725 @node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
|
|
|
726 @unnumberedsubsec Q1.0.5: Who wrote XEmacs?
|
|
|
727
|
|
|
728 XEmacs is the result of the time and effort of many people, and the
|
|
|
729 active developers have changed over time. There are two major
|
|
|
730 components of the XEmacs effort -- writing the code itself and providing
|
|
|
731 all the support work (testing the code, releasing beta and final
|
|
|
732 versions, handling patches, reading bug reports, maintaining the web
|
|
|
733 site, managing the mailing lists, etc. etc.). Neither component would
|
|
|
734 work without the other.
|
|
|
735
|
|
|
736 @subheading CODING
|
|
|
737
|
|
|
738 The primary code contributor over the years has been Ben Wing (active
|
|
|
739 since late 1992). Between 1991 and 1995, large amounts of coding was
|
|
|
740 contributed by Jamie Zawinski and Chuck Thompson. Many other people
|
|
|
741 have authored major subsystems or otherwise contributed large amounts of
|
|
|
742 code, including Andy Piper, Hrvoje Niksic, Jerry James, Jonathan Harris,
|
|
|
743 Kyle Jones, Martin Buchholz, Michael Sperber, Olivier Galibert, Richard
|
|
|
744 Mlynarik, Stig, William Perry and plenty of others.
|
|
|
745
|
|
|
746 Primary XEmacs-specific subsystems and their authors:
|
|
|
747
|
|
|
748 @table @asis
|
|
|
749 @item Objects
|
|
|
750 @itemize @minus
|
|
|
751 @item
|
|
|
752 Conversion from 26-bit to 28-bit pointers and integers, lrecords, lcrecords: Richard Mlynarik, 1994
|
|
|
753 @item
|
|
|
754 Conversion to 32-bit pointers and 31-bit integers: Kyle Jones, Martin Buchholz
|
|
|
755 @item
|
|
|
756 Portable dumper, object descriptions: Olivier Galibert
|
|
|
757 @item
|
|
|
758 KKCC (new garbage collector), ephemerons, weak boxes: Michael Sperber and students
|
|
|
759 @item
|
|
|
760 Random object work (object equal and hash methods, weak lists, lcrecord lists, bit vectors, dynarr, blocktype, opaque, string resizing): Ben Wing
|
|
|
761 @item
|
|
|
762 Profiling: Ben Wing
|
|
|
763 @item
|
|
|
764 Some byte-compilation and hash-table improvements: Martin Buchholz
|
|
|
765 @item
|
|
|
766 Bignum: Jerry James
|
|
|
767 @end itemize
|
|
|
768
|
|
|
769 @item Internationalization/Mule
|
|
|
770 @itemize @minus
|
|
|
771 @item
|
|
|
772 mostly Ben Wing; many ideas for future work, Stephen Turnbull
|
|
|
773 @end itemize
|
|
|
774
|
|
|
775 @item I/O
|
|
|
776 @itemize @minus
|
|
|
777 @item
|
|
|
778 Basic event/event-stream implementation: Jamie Zawinski
|
|
|
779 @item
|
|
|
780 Most event work since 1994: Ben Wing
|
|
|
781 @item
|
|
|
782 Asynchronous stuff (async timeouts, signals, quit-checking): Ben Wing
|
|
|
783 @item
|
|
|
784 Process method abstraction, Windows process work: Kirill Katsnelson
|
|
|
785 @item
|
|
|
786 Misc-user events, async timeouts, most quit-checking and signal code, most other work since 1994: Ben Wing
|
|
|
787 @item
|
|
|
788 Lstreams: Ben Wing
|
|
|
789 @end itemize
|
|
|
790
|
|
|
791 @item Display
|
|
|
792 @itemize @minus
|
|
|
793 @item
|
|
|
794 Redisplay mechanism: implementation, Chuck Thompson; additional work, lots of people
|
|
|
795 @item
|
|
|
796 Glyphs: mostly Ben Wing
|
|
|
797 @item
|
|
|
798 Specifiers: Ben Wing
|
|
|
799 @item
|
|
|
800 Extents: initial implementation, someone at Lucid; rewrite, 1994, Ben Wing
|
|
|
801 @item
|
|
|
802 Widgets: Andy Piper
|
|
|
803 @item
|
|
|
804 JPEG/PNG/TIFF image converters: Ben Wing, William Perry, Jareth Hein, others (see comment in @file{glyphs-eimage.c})
|
|
|
805 @item
|
|
|
806 Menus: Jamie Zawinski, someone at Lucid (Lucid menus)
|
|
|
807 @item
|
|
|
808 Scrollbars: Chuck Thompson, ??? (Lucid scrollbar)
|
|
|
809 @item
|
|
|
810 Multi-device/device-independence work (console/device/etc methods): Ben Wing, prototype by chuck thompson
|
|
|
811 @item
|
|
|
812 Faces: first implementation, Jamie Zawinski; second, chuck; third, Ben Wing
|
|
|
813 @item
|
|
|
814 Fonts/colors: first implementation, Jamie Zawinski; further work, Ben Wing
|
|
|
815 @item
|
|
|
816 Toolbars: implementation, chuck, much interface work, Ben Wing
|
|
|
817 @item
|
|
|
818 Gutters, tabs: andy piper
|
|
|
819 @end itemize
|
|
|
820
|
|
|
821 @item Device subsystems
|
|
|
822 @itemize @minus
|
|
|
823 @item
|
|
|
824 X Windows: Jamie Zawinksi, Ben Wing, others
|
|
|
825 @item
|
|
|
826 GTK: William Perry, Malcolm Purvis
|
|
|
827 @item
|
|
|
828 MS Windows: initial implementation, Jonathan Harris; some more work, Andy Piper, Ben Wing
|
|
|
829 @item
|
|
|
830 TTY: Chuck Thompson, Ben Wing
|
|
|
831 @item
|
|
|
832 Cygwin: Andy Piper
|
|
|
833 @end itemize
|
|
|
834
|
|
|
835 @item Misc
|
|
|
836 @itemize @minus
|
|
|
837 @item
|
|
|
838 Configure: initial porting from fsf, Chuck Thompson; conversion to autoconf 2, much rewriting, Martin Buchholz
|
|
|
839 @item
|
|
|
840 Most initialization-related code: Ben Wing
|
|
|
841 @item
|
|
|
842 Internals manual, much of Lisp manual: Ben Wing
|
|
|
843 @item
|
|
|
844 FSF synching: initial sync with FSF 19, Richard Mlynarik, further work, Ben Wing
|
|
|
845 @end itemize
|
|
|
846 @end table
|
|
|
847
|
|
|
848 @subheading SUPPORT
|
|
|
849
|
|
|
850 Currently, support duties are handled by many different people.
|
|
|
851
|
|
|
852 Release managers have been
|
|
|
853
|
|
|
854 @itemize @minus
|
|
|
855 @item
|
|
|
856 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)
|
|
|
857 @item
|
|
|
858 Vin Shelton (May 2003 - present, 21.4.13 - present)
|
|
|
859 @item
|
|
|
860 Steve Youngs (July 2002 - September 2003, 21.5.8 - 21.5.16)
|
|
|
861 @item
|
|
|
862 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)
|
|
|
863 @item
|
|
|
864 Steve Baur (early 1997 - December 1998, February 1999 - November 1999, 19.15 - 21.2.5, 21.2.9 - 21.2.20)
|
|
|
865 @item
|
|
|
866 Andy Piper (December 1998, 21.2.6)
|
|
|
867 @item
|
|
|
868 Chuck Thompson (June 1994 - September 1996, 19.11 - 19.14)
|
|
|
869 @item
|
|
|
870 Jamie Zawinski (April 1991 - June 1994, 19.0 - 19.10)
|
|
|
871 @end itemize
|
|
|
872
|
|
|
873 The recent overlapping dates are intentional, since two or three trees
|
|
|
874 are maintained simultaneously at any point.
|
|
|
875
|
|
|
876 Other major support work:
|
|
|
877
|
|
|
878 @itemize @minus
|
|
|
879 @item
|
|
|
880 Adrian Aichner wrote and maintains the web site.
|
|
|
881 @item
|
|
|
882 Stephen Turnbull has produced many of the beta and semi-stable releases
|
|
|
883 and has attempted to be the "face" of XEmacs on the newsgroups and
|
|
|
884 mailing lists.
|
|
|
885 @item
|
|
|
886 Steve Youngs currently produces the beta releases (???).
|
|
|
887 @item
|
|
|
888 Steve Youngs, Ville Skytta, and now Norbert Koch have taken turns
|
|
|
889 maintaining the packages.
|
|
|
890 @item
|
|
|
891 Vin Shelton maintains the stable releases.
|
|
|
892 @item
|
|
|
893 Testing - #### Norbert, Adrian, ???
|
|
|
894 @end itemize
|
|
|
895
|
|
|
896 Portraits and email of some of the major developers:
|
|
|
897
|
|
|
898 @itemize @bullet
|
|
|
899 @item @email{andy@@xemacs.org, Andy Piper}
|
|
|
900 @html
|
|
|
901 <br><img src="piper.png" alt="Portrait of Andy Piper"><br>
|
|
|
902 @end html
|
|
|
903
|
|
|
904 @item @email{ben@@xemacs.org, Ben Wing}
|
|
|
905 @html
|
|
|
906 <br><img src="ben.png" alt="Portrait of Ben Wing"><br>
|
|
|
907 @end html
|
|
|
908
|
|
|
909 @item @email{cthomp@@xemacs.org, Chuck Thompson}
|
|
|
910 @html
|
|
|
911 <br><img src="cthomp.png" alt="Portrait of Chuck Thompson"><br>
|
|
|
912 @end html
|
|
|
913
|
|
|
914 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
|
|
|
915
|
|
|
916 @html
|
|
|
917 <br><img src="hniksic.png" alt="Portrait of Hrvoje Niksic"><br>
|
|
|
918 @end html
|
|
|
919
|
|
|
920 @item @email{jwz@@jwz.org, Jamie Zawinski}
|
|
|
921 @html
|
|
|
922 <br><img src="jwz.png" alt="Portrait of Jamie Zawinski"><br>
|
|
|
923 @end html
|
|
|
924
|
|
|
925 @item @email{martin@@xemacs.org, Martin Buchholz}
|
|
|
926 @html
|
|
|
927 <br><img src="martin.png" alt="Portrait of Martin Buchholz"><br>
|
|
|
928 @end html
|
|
|
929
|
|
|
930 @item @email{mly@@adoc.xerox.com, Richard Mlynarik}
|
|
|
931 @html
|
|
|
932 <br><img src="mly.png" alt="Portrait of Richard Mlynarik"><br>
|
|
|
933 @end html
|
|
|
934
|
|
|
935 @item @email{stephen@@xemacs.org, Stephen Turnbull}
|
|
|
936
|
|
|
937 @item @email{steve@@xemacs.org, Steve Baur}
|
|
|
938 @html
|
|
|
939 <br><img src="slb.png" alt="Portrait of Steve Baur"><br>
|
|
|
940 @end html
|
|
|
941 @end itemize
|
|
|
942
|
|
|
943 Many other people have contributed to XEmacs; this is partially
|
|
|
944 enumerated in the @samp{About XEmacs} option in the Help menu.
|
|
|
945
|
|
|
946 @node Q1.0.6, Q1.1.1, Q1.0.5, Introduction
|
|
|
947 @unnumberedsubsec Q1.0.6: Who wrote the FAQ?
|
|
|
948
|
|
|
949 The current version of this FAQ was created by @email{ben@@xemacs.org,
|
|
|
950 Ben Wing}.
|
|
|
951
|
|
|
952 Previous contributors to the FAQ include
|
|
|
953
|
|
|
954 @itemize @bullet
|
|
|
955 @item @email{steve@@xemacs.org, SL Baur}
|
|
|
956
|
|
|
957 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
|
|
|
958
|
|
|
959 @item @email{binge@@aloft.att.com, Curtis.N.Bingham}
|
|
|
960
|
|
|
961 @item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan}
|
|
|
962
|
|
|
963 @item @email{rjc@@cogsci.ed.ac.uk, Richard Caley}
|
|
|
964
|
|
|
965 @item @email{cognot@@ensg.u-nancy.fr, Richard Cognot}
|
|
|
966
|
|
|
967 @item @email{daku@@nortel.ca, Mark Daku}
|
|
|
968
|
|
|
969 @item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque}
|
|
|
970
|
|
|
971 @item @email{eeide@@cs.utah.edu, Eric Eide}
|
|
|
972
|
|
|
973 @item @email{af@@biomath.jussieu.fr, Alain Fauconnet}
|
|
|
974
|
|
|
975 @item @email{cflatter@@nrao.edu, Chris Flatters}
|
|
|
976
|
|
|
977 @item @email{ginsparg@@adra.com, Evelyn Ginsparg}
|
|
|
978
|
|
|
979 @item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall}
|
|
|
980
|
|
|
981 @item @email{dkindred@@cmu.edu, Darrell Kindred}
|
|
|
982
|
|
|
983 @item @email{dmoore@@ucsd.edu, David Moore}
|
|
|
984
|
|
|
985 @item @email{arup+@@cmu.edu, Arup Mukherjee}
|
|
|
986
|
|
|
987 @item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen}
|
|
|
988
|
|
|
989 @item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell}
|
|
|
990
|
|
|
991 @item @email{dworkin@@ccs.neu.edu, Justin Sheehy}
|
|
|
992
|
|
|
993 @item @email{stig@@hackvan.com, Stig}
|
|
|
994
|
|
|
995 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
|
|
|
996 @end itemize
|
|
|
997
|
|
|
998 @unnumberedsec 1.1: Getting XEmacs
|
|
|
999
|
|
|
1000 @node Q1.1.1, Q1.1.2, Q1.0.6, Introduction
|
|
|
1001 @unnumberedsubsec Q1.1.1: Where can I find XEmacs?
|
|
|
1002
|
|
|
1003 To download XEmacs, visit the XEmacs WWW page at
|
|
|
1004 @uref{http://www.xemacs.org/Download/}. The most up-to-date list of
|
|
|
1005 distribution sites can always be found there. Try to pick a site that
|
|
|
1006 is networkologically close to you. If you know of other mirrors of
|
|
|
1007 the XEmacs archives, please send e-mail to
|
|
|
1008 @uref{mailto:webmaster@@xemacs.org} and we will list them here as well.
|
|
|
1009
|
|
|
1010 The canonical distribution point is ftp.xemacs.org, available either
|
|
|
1011 through HTTP (@uref{http://ftp.xemacs.org/}) or anonymous FTP
|
|
|
1012 (@uref{ftp://ftp.xemacs.org/pub/xemacs/}).
|
|
|
1013
|
|
|
1014 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
|
|
|
1015 @unnumberedsubsec Q1.1.2: Are binaries available?
|
|
2417
|
1016
|
|
|
1017 MS Windows binaries are available at
|
|
|
1018 @uref{http://www.xemacs.org/Download/win32/} for the native versions
|
|
|
1019 of 21.4 and 21.1. Cygwin binaries are now available as part of the
|
|
|
1020 standard Cygwin installation process. XEmacs also comes pre-built as
|
|
|
1021 part of many Linux distributions, such as Red Hat and SuSE.
|
|
|
1022
|
|
|
1023 Otherwise, you will need to build XEmacs yourself or get your system
|
|
|
1024 administrator to do it. Generally, this is not a difficult process
|
|
|
1025 under Unix and Mac OS X, as XEmacs has been tested under all of the
|
|
|
1026 common Unix versions and under Mac OS X and comes with an extensive
|
|
|
1027 configure script that is able to automatically detect most aspects of
|
|
|
1028 the configuration of your particular system.
|
|
|
1029
|
|
2537
|
1030 @node Q1.1.3, Q1.1.4, Q1.1.2, Introduction
|
|
|
1031 @unnumberedsubsec Q1.1.3: How do I get the bleeding-edge sources?
|
|
|
1032
|
|
|
1033 If you are interested in developing XEmacs, or getting the absolutely most
|
|
|
1034 recent, up-to-the-moment, bleeding-edge source code, you can directly
|
|
|
1035 access the master CVS source tree (read-only, of course, until you ask for
|
|
|
1036 and are granted permission to directly modify portions of the source tree)
|
|
|
1037 at cvs.xemacs.org. Directions on how to access the source tree are located
|
|
|
1038 at @uref{http://www.xemacs.org/Develop/cvsaccess.html}.
|
|
|
1039
|
|
|
1040 Nightly CVS snapshots are available at
|
|
|
1041 @uref{http://www.dk.xemacs.org/Download/CVS-snapshots/}.
|
|
|
1042
|
|
|
1043 @node Q1.1.4, Q1.2.1, Q1.1.3, Introduction
|
|
|
1044 @unnumberedsubsec Q1.1.4: Where can I obtain a printed copy of the XEmacs User's Manual?
|
|
|
1045
|
|
|
1046 Pre-printed manuals are not available. If you are familiar with
|
|
|
1047 TeX, you can generate your own manual from the XEmacs sources.
|
|
|
1048
|
|
|
1049 HTML and Postscript versions of XEmacs manuals are available from the
|
|
|
1050 XEmacs web site at
|
|
|
1051 @uref{http://www.xemacs.org/Documentation/index.html}.
|
|
|
1052
|
|
|
1053 @unnumberedsec 1.2: Versions for Different Operating Systems
|
|
|
1054
|
|
|
1055 @node Q1.2.1, Q1.2.2, Q1.1.4, Introduction
|
|
|
1056 @unnumberedsubsec Q1.2.1: Do I need X11 to run XEmacs?
|
|
|
1057
|
|
|
1058 No. The name @dfn{XEmacs} is unfortunate in the sense that it is
|
|
|
1059 @strong{not} an X Window System-only version of Emacs. XEmacs has
|
|
|
1060 full color support on a color-capable character terminal.
|
|
|
1061
|
|
|
1062 @node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
|
|
|
1063 @unnumberedsubsec Q1.2.2: What versions of Unix does XEmacs run on?
|
|
|
1064
|
|
2559
|
1065 XEmacs is regularly tested on Linux, Solaris, SunOS, HP/UX, FreeBSD,
|
|
|
1066 OpenBSD, BSD/OS aka BSDI, Tru64 aka DEC/OSF, SCO5, and probably
|
|
|
1067 others. It should work on all versions of Unix created in the last 10
|
|
|
1068 years or so, perhaps with a bit of work on more obscure platforms to
|
|
|
1069 correct bit-rot. It uses a sophisticated configuration system to
|
|
|
1070 auto-detect zillions of features that are implemented differently in
|
|
|
1071 different versions of Unix, so it will probably work on your vendor's
|
|
|
1072 version, possibly with a bit of tweaking, even if we've never heard of
|
|
|
1073 it.
|
|
|
1074
|
|
2537
|
1075 For problems with particular machines and versions of Unix, see the
|
|
|
1076 @file{PROBLEMS} file.
|
|
|
1077
|
|
|
1078 Much effort has gone into making XEmacs work on as many different
|
|
|
1079 machines, configurations, and compilers as possible.
|
|
|
1080
|
|
|
1081 Much effort has gone into making XEmacs 64-bit clean.
|
|
|
1082
|
|
|
1083 Much effort has gone into removing system-specific code, and replacing
|
|
|
1084 such code with autodetection at configure time.
|
|
|
1085
|
|
|
1086 The XEmacs core should build "out of the box" on most Unix-like systems.
|
|
|
1087
|
|
|
1088 XEmacs 21.2 was tested and @samp{make check} succeeded on these Unix
|
|
|
1089 configurations as of 2001-02-10:
|
|
|
1090
|
|
|
1091 @example
|
|
|
1092 alphaev56-dec-osf4.0e (both Compaq C and gcc)
|
|
|
1093 i386-unknown-freebsd4.2
|
|
|
1094 i386-unknown-netbsdelf1.5
|
|
|
1095 i586-sco-sysv5uw7.0.1 (both SCO's cc and gcc)
|
|
|
1096 i686-pc-linux-gnu
|
|
|
1097 hppa2.0-hp-hpux10.20 (both HP's ANSI cc and gcc)
|
|
|
1098 mips-sgi-irix6.5 (both MIPSpro cc and gcc)
|
|
|
1099 rs6000-ibm-aix4.3.0.0 (both IBM's xlc and gcc)
|
|
|
1100 sparc-sun-solaris2.6 (both Sun's Forte C and gcc)
|
|
|
1101 sparc-sun-solaris2.7 (both Sun's Forte C and gcc)
|
|
|
1102 sparc-sun-sunos4.1.4 (gcc)
|
|
|
1103 @end example
|
|
|
1104
|
|
|
1105 Some systems have a dual mode 32-bit/64-bit compiler. On most of
|
|
|
1106 these, XEmacs requires the @samp{--pdump} configure option to build
|
|
|
1107 correctly with the 64-bit version of the compiler.
|
|
|
1108
|
|
|
1109 @example
|
|
|
1110 mips-sgi-irix6.5, CC="gcc -mabi=64"
|
|
|
1111 mips-sgi-irix6.5, CC="cc -64"
|
|
|
1112 rs6000-ibm-aix4.3.0.0, CC="cc -q64"
|
|
|
1113 @end example
|
|
|
1114
|
|
|
1115 On most of these systems, XEmacs also builds with a C++ compiler,
|
|
|
1116 but not "out of the box". This feature is only for use by the
|
|
|
1117 maintainers.
|
|
|
1118
|
|
|
1119 XEmacs 21.2 is known @emph{not} to work on any machines with m680x0
|
|
|
1120 processors. Sorry, all you sun3 and Unix PC nostalgia buffs out there.
|
|
|
1121
|
|
|
1122 VMS has never been supported by XEmacs. In fact, all the old VMS code
|
|
|
1123 inherited from Emacs has been removed. Sorry, all you VMS fans out there.
|
|
|
1124
|
|
|
1125 @node Q1.2.3, Q1.2.4, Q1.2.2, Introduction
|
|
|
1126 @unnumberedsubsec Q1.2.3: Is there a port of XEmacs to Microsoft Windows?
|
|
|
1127
|
|
|
1128 Yes. Beginning with release 21.0, XEmacs has worked under MS Windows
|
|
|
1129 and is fully-featured and actively developed. A group of dedicated
|
|
|
1130 developers actively maintains and improves the Windows-specific
|
|
|
1131 portions of the code. Some of the core developers, in fact, use
|
|
|
1132 Windows as their only development environment, and some features, such
|
|
|
1133 as printing, actually work better on Windows than native Unix and Mac
|
|
|
1134 OS X. The mailing list at @email{xemacs-winnt@@xemacs.org} is dedicated
|
|
|
1135 to that effort (please use the -request address to
|
|
|
1136 subscribe). (Despite its name, XEmacs actually works on all versions
|
|
|
1137 of Windows.)
|
|
|
1138
|
|
|
1139 The list name is misleading, as XEmacs supports and has been compiled on
|
|
|
1140 Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows
|
|
|
1141 XP, and all newer versions of Windows. The MS Windows-specific code is
|
|
|
1142 based on Microsoft Win32 API, and will not work on MS Windows 3.x or on
|
|
|
1143 MS-DOS.
|
|
|
1144
|
|
|
1145 XEmacs also supports the Cygwin and MinGW development and runtime
|
|
|
1146 environments, where it also uses native Windows code for graphical
|
|
|
1147 features. In addition, under Cygwin it is possible to compile XEmacs
|
|
|
1148 to use an X server (and XFree86 is available as part of the standard
|
|
|
1149 Cygwin installation).
|
|
|
1150
|
|
|
1151 @node Q1.2.4, Q1.2.5, Q1.2.3, Introduction
|
|
|
1152 @unnumberedsubsec Q1.2.4: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
1153
|
|
|
1154 Yes, you can, but no you do not need to. In fact, we recommend that you
|
|
|
1155 use a native-GUI version unless you have a specific need for an X
|
|
|
1156 version.
|
|
|
1157
|
|
|
1158 @node Q1.2.5, Q1.2.6, Q1.2.4, Introduction
|
|
|
1159 @unnumberedsubsec Q1.2.5: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
1160
|
|
|
1161 To answer the second part of the question: No, you, you don't need
|
|
|
1162 Cygwin or MinGW to build or to run XEmacs. But if you have them and
|
|
|
1163 want to use them, XEmacs supports these environments.
|
|
|
1164
|
|
|
1165 (One important reason to support Cygwin is that it lets the MS Windows
|
|
|
1166 developers test out their code in a Unix environment without actually
|
|
|
1167 having to have a Unix machine around. For this reason alone, Cygwin
|
|
|
1168 support is likely to remain supported for a long time in XEmacs. Same
|
|
|
1169 goes for the X support under Cygwin, for the same reasons. MinGW
|
|
|
1170 support, on the other hand, depends on volunteers to keep it up to date;
|
|
|
1171 but this is generally not hard.)
|
|
|
1172
|
|
|
1173 Cygwin is a set of tools providing Unix-like API on top of Win32.
|
|
|
1174 It makes it easy to port large Unix programs without significant
|
|
|
1175 changes to their source code. It is a development environment as well
|
|
|
1176 as a runtime environment.
|
|
|
1177
|
|
|
1178 When built with Cygwin, XEmacs supports all display types -- TTY, X &
|
|
|
1179 Win32 GUI, and can be built with support for all three simultaneously.
|
|
|
1180 If you build with Win32 GUI support then the Cygwin version uses the
|
|
|
1181 majority of the Windows-specific code, which is mostly related to
|
|
|
1182 display. If you want to build with X support you need X libraries (and
|
|
2559
|
1183 an X server to display XEmacs on); see @ref{Q2.3.7}. TTY and Win32 GUI
|
|
2537
|
1184 require no additional libraries beyond what comes standard with Cygwin.
|
|
|
1185
|
|
|
1186 The advantages of the Cygwin version are that it integrates well with
|
|
|
1187 the Cygwin environment for existing Cygwin users; uses configure so
|
|
|
1188 building with different features is very easy; and actively supports X &
|
|
|
1189 TTY. Furthermore, the entire Cygwin environment and compiler are free,
|
|
|
1190 whereas Visual C++ costs money.
|
|
|
1191
|
|
|
1192 The disadvantage is that it requires the whole Cygwin environment,
|
|
|
1193 whereas the native port requires only a suitable MS Windows compiler.
|
|
|
1194 Also, it follows the Unix filesystem and process model very closely
|
|
|
1195 (some will undoubtedly view this as an advantage).
|
|
|
1196
|
|
|
1197 See @uref{http://www.cygwin.com/} for more information on
|
|
|
1198 Cygwin.
|
|
|
1199
|
|
|
1200 MinGW is a collection of header files and import libraries that allow
|
|
|
1201 one to use GCC under the Cygwin environment to compile and produce
|
|
|
1202 exactly the same native Win32 programs that you can using Visual C++.
|
|
|
1203 Programs compiled with MinGW make use of the standard Microsoft runtime
|
|
|
1204 library @file{MSVCRT.DLL}, present on all Windows systems, and look,
|
|
|
1205 feel, and act like a standard Visual-C-produced application. (The only
|
|
|
1206 difference is the compiler.) This means that, unlike a
|
|
|
1207 standardly-compiled Cygwin application, no extra runtime support
|
|
|
1208 (e.g. Cygwin's @file{cygwin1.dll}) is required. This, along with the
|
|
|
1209 fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y
|
|
|
1210 environment, for those die-hard Unix hackers out there), is the main
|
|
|
1211 advantage of MinGW. It is also potentially faster than Cygwin because
|
|
|
1212 it has less overhead when calling Windows, but you lose the POSIX
|
|
|
1213 emulation layer, which makes Unix programs harder to port. (But this is
|
|
|
1214 irrelevant for XEmacs since it's already ported to Win32.)
|
|
|
1215
|
|
|
1216 See @uref{http://www.mingw.org/} for more information on MinGW.
|
|
|
1217
|
|
|
1218 @node Q1.2.6, Q1.2.7, Q1.2.5, Introduction
|
|
|
1219 @unnumberedsubsec Q1.2.6: What are the differences between the various MS Windows emacsen?
|
|
|
1220
|
|
|
1221 XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing.
|
|
|
1222 Could you briefly explain the differences between them?
|
|
|
1223
|
|
|
1224 Here is a recount of various Emacs versions running on MS Windows:
|
|
|
1225
|
|
|
1226 @itemize @bullet
|
|
|
1227
|
|
|
1228 @item
|
|
|
1229 XEmacs
|
|
|
1230
|
|
|
1231 @itemize @minus
|
|
|
1232
|
|
|
1233 @item
|
|
|
1234 Beginning with XEmacs 19.12, XEmacs' architecture was redesigned
|
|
|
1235 in such a way to allow clean support of multiple window systems. At
|
|
|
1236 this time the TTY support was added, making X and TTY the first two
|
|
|
1237 "window systems" supported by XEmacs. The 19.12 design is the basis for
|
|
|
1238 the current native MS Windows code.
|
|
|
1239
|
|
|
1240 @item
|
|
|
1241 Some time during 1997, David Hobley (soon joined by Marc Paquette)
|
|
|
1242 imported some of the NT-specific portions of GNU Emacs, making XEmacs
|
|
|
1243 with X support compile under Windows NT, and creating the "X" port.
|
|
|
1244
|
|
|
1245 @item
|
|
|
1246 Several months later, Jonathan Harris sent out initial patches to use
|
|
|
1247 the Win32 API, thus creating the native port. Since then, various
|
|
|
1248 people have contributed, including Kirill M. Katsnelson (contributed
|
|
|
1249 support for menubars, subprocesses and network, as well as loads of
|
|
|
1250 other code), Andy Piper (ported XEmacs to Cygwin environment,
|
|
|
1251 contributed Windows unexec, Windows-specific glyphs and toolbars code,
|
|
|
1252 and more), Ben Wing (loads of improvements; primary MS Windows developer
|
|
|
1253 since 2000), Jeff Sparkes (contributed scrollbars support) and many
|
|
|
1254 others.
|
|
|
1255 @end itemize
|
|
|
1256
|
|
|
1257 @item
|
|
|
1258 NT Emacs
|
|
|
1259
|
|
|
1260 @itemize @minus
|
|
|
1261
|
|
|
1262 @item
|
|
|
1263 NT Emacs was an early version of GNU Emacs 19 modified to compile and
|
|
|
1264 run under MS Windows 95 and NT using the native Win32 API. It was
|
|
|
1265 written by Geoff Voelker, and has long since been incorporated into
|
|
|
1266 the mainline GNU Emacs distribution.
|
|
|
1267 @end itemize
|
|
|
1268
|
|
|
1269 @item
|
|
|
1270 Win-Emacs
|
|
|
1271
|
|
|
1272 @itemize @minus
|
|
|
1273
|
|
|
1274 @item
|
|
|
1275 Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X
|
|
|
1276 compatibility libraries. Win-Emacs was written by Ben Wing. The MS
|
|
|
1277 Windows code never made it back to Lucid Emacs, and its creator (Pearl
|
|
|
1278 Software) has long since gone out of business.
|
|
|
1279 @end itemize
|
|
|
1280
|
|
|
1281 @item
|
|
|
1282 GNU Emacs for DOS
|
|
|
1283
|
|
|
1284 @itemize @minus
|
|
|
1285
|
|
|
1286 @item
|
|
|
1287 GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
|
|
|
1288 port of GCC). Such an Emacs is heavily underfeatured, because it does
|
|
|
1289 not support long file names, lacks proper subprocesses support, and
|
|
|
1290 is far too big compared with typical DOS editors.
|
|
|
1291 @end itemize
|
|
|
1292
|
|
|
1293 @item
|
|
|
1294 GNU Emacs compiled with Win32
|
|
|
1295
|
|
|
1296 @itemize @minus
|
|
|
1297
|
|
|
1298 @item
|
|
|
1299 Starting with GNU Emacs 19.30, it has been possible to compile GNU Emacs
|
|
|
1300 under MS Windows using the DJGPP compiler and X libraries. The result
|
|
|
1301 is very similar to GNU Emacs compiled under MS DOS, only it works
|
|
|
1302 somewhat better because it runs in 32-bit mode, makes use of all the
|
|
|
1303 system memory, supports long file names, etc.
|
|
|
1304 @end itemize
|
|
|
1305
|
|
|
1306 @end itemize
|
|
|
1307
|
|
|
1308 @node Q1.2.7, Q1.2.8, Q1.2.6, Introduction
|
|
|
1309 @unnumberedsubsec Q1.2.7: How does the port cope with differences in the Windows user interface?
|
|
|
1310
|
|
|
1311 The XEmacs (and Emacs in general) user interface is pretty different
|
|
|
1312 from what is expected of a typical MS Windows program. How does the MS
|
|
|
1313 Windows port cope with it?
|
|
|
1314
|
|
|
1315 As a general rule, we follow native MS Windows conventions as much as
|
|
|
1316 possible. 21.4 is a fairly complete Windows application, supporting
|
|
|
1317 native printing, system file dialog boxes, tool tips, etc. In cases
|
|
|
1318 where there's a clear UI conflict, we currently use normal Unix XEmacs
|
|
|
1319 behavior by default, but make sure the MS Windows "look and feel" (mark
|
|
|
1320 via shift-arrow, self-inserting deletes region, Alt selects menu items,
|
|
|
1321 etc.) is easily configurable (respectively: using the variable
|
|
|
1322 @code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact
|
|
|
1323 the default in these versions], or the @file{pc-select} package; using
|
|
|
1324 the @file{pending-del} package; and setting the variable
|
|
|
1325 @code{menu-accelerator-enabled} to @code{menu-force} in 21.4 and above).
|
|
|
1326 In fact, if you use the sample @file{init.el} file as your init file,
|
|
|
1327 you will get all these behaviors automatically turned on.
|
|
|
1328
|
|
|
1329 In future versions, some of these features might be turned on by
|
|
|
1330 default in the MS Windows environment.
|
|
|
1331
|
|
|
1332 @node Q1.2.8, Q1.2.9, Q1.2.7, Introduction
|
|
|
1333 @unnumberedsubsec Q1.2.8: Is there a port of XEmacs to the Macintosh?
|
|
|
1334
|
|
|
1335 Yes.
|
|
|
1336
|
|
|
1337 XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly
|
|
|
1338 will not feel very much like a Mac application as it has no Mac-specific
|
|
|
1339 code in it.
|
|
|
1340
|
|
|
1341 There is also a port of XEmacs 19.14 that works on all recent versions
|
|
|
1342 of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com,
|
|
|
1343 Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY
|
|
|
1344 mode only (one single Macintosh window, 25 colors), but has a large
|
|
|
1345 number of Mac-specific additions. It's available at
|
|
|
1346 @uref{http://homepage.mac.com/pjarvis/xemacs.html}.
|
|
|
1347
|
|
|
1348 @node Q1.2.9, Q1.2.10, Q1.2.8, Introduction
|
|
2559
|
1349 @unnumberedsubsec Q1.2.9: Is there a port of XEmacs to MS-DOS?
|
|
|
1350
|
|
|
1351 No. We have never supported running on MS-DOS or Windows 3.1, and in
|
|
|
1352 fact have long since deleted all MS-DOS-related code. We're not
|
|
|
1353 particularly interested in patches for these platforms, as they would
|
|
|
1354 introduce huge amounts of code clutter due to the woefully
|
|
|
1355 underfeatured nature of these systems. (See GNU Emacs for a port to
|
|
|
1356 MS-DOS.)
|
|
2537
|
1357
|
|
|
1358 @node Q1.2.10, Q1.2.11, Q1.2.9, Introduction
|
|
2559
|
1359 @unnumberedsubsec Q1.2.10: Is there a port of XEmacs to OS/2?
|
|
2537
|
1360
|
|
|
1361 No, but Alexander Nikolaev <avn_1251@@mail.ru> was at one point
|
|
|
1362 working on it.
|
|
|
1363
|
|
2559
|
1364 @node Q1.2.11, Q1.2.12, Q1.2.10, Introduction
|
|
|
1365 @unnumberedsubsec Q1.2.11: Is there a port of XEmacs to NextStep?
|
|
2537
|
1366
|
|
|
1367 Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did
|
|
|
1368 the port of GNU Emacs to NeXTstep and expressed interest in doing the
|
|
|
1369 XEmacs port, but never went any farther.
|
|
|
1370
|
|
2559
|
1371 @node Q1.2.12, Q1.3.1, Q1.2.11, Introduction
|
|
|
1372 @unnumberedsubsec Q1.2.12: Is there a port of XEmacs to VMS?
|
|
2537
|
1373
|
|
|
1374 VMS has never been supported by XEmacs. In fact, all the old VMS code
|
|
|
1375 inherited from GNU Emacs has been removed. Sorry, all you VMS fans
|
|
|
1376 out there.
|
|
|
1377
|
|
|
1378 @unnumberedsec 1.3: Getting Started
|
|
|
1379
|
|
2559
|
1380 @node Q1.3.1, Q1.3.2, Q1.2.12, Introduction
|
|
2537
|
1381 @unnumberedsubsec Q1.3.1: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
|
1382
|
|
|
1383 The @file{init.el} or @file{.emacs} file is used to customize XEmacs to
|
|
|
1384 your tastes. Starting in 21.4, the preferred location for the init file
|
|
|
1385 is @file{~/.xemacs/init.el}; in previous versions, it was
|
|
|
1386 @file{~/.emacs}. 21.4 still accepts the old location, but the first
|
|
|
1387 time you run it, it will ask to migrate your file to the new location.
|
|
|
1388 If you answer yes, the file will be moved, and a "compatibility"
|
|
|
1389 @file{.emacs} file will be placed in the old location so that you can
|
|
|
1390 still run older versions of XEmacs, and versions of GNU Emacs, which
|
|
|
1391 expect the old location. The @file{.emacs} file present is just a stub
|
|
|
1392 that loads the real file in @file{~/.xemacs/init.el}.
|
|
|
1393
|
|
|
1394 No two init files are alike, nor are they expected to be alike, but
|
|
|
1395 that's the point. The XEmacs distribution contains an excellent starter
|
|
|
1396 example in the @file{etc/} directory called @file{sample.init.el}
|
|
|
1397 (starting in 21.4) or @file{sample.emacs} in older versions. Copy this
|
|
|
1398 file from there to @file{~/.xemacs/init.el} (starting in 21.4) or
|
|
|
1399 @file{~/.emacs} in older versions, where @samp{~} means your home
|
|
|
1400 directory, of course. Then edit it to suit.
|
|
|
1401
|
|
|
1402 You may bring the @file{sample.init.el} or @file{sample.emacs} file into
|
|
|
1403 an XEmacs buffer from the menubar. (The menu entry for it is always
|
|
|
1404 under the @samp{Help} menu, but its location under that has changed in
|
|
|
1405 various versions. Recently, look under the @samp{Samples} submenu.) To
|
|
|
1406 determine the location of the @file{etc/} directory type the command
|
|
|
1407 @kbd{C-h v data-directory @key{RET}}.
|
|
|
1408
|
|
|
1409 @node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
|
|
|
1410 @unnumberedsubsec Q1.3.2: Where do I put my @file{init.el} file?
|
|
|
1411
|
|
|
1412 @file{init.el} is the name of the init file starting with 21.4, and is
|
|
|
1413 located in the subdirectory @file{.xemacs/} of your home directory. In
|
|
|
1414 prior versions, the init file is called @file{.emacs} and is located in
|
|
|
1415 your home directory.
|
|
|
1416
|
|
|
1417 Your home directory under Windows is determined by the @samp{HOME}
|
|
|
1418 environment variable. If this is not set, it defaults to @samp{C:\}.
|
|
|
1419 To set this variable, modify @file{AUTOEXEC.BAT} under Windows 95/98, or
|
|
|
1420 select @samp{Control Panel->System->Advanced->Environment Variables...}
|
|
|
1421 under Windows NT/2000.
|
|
|
1422
|
|
|
1423 @node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
|
|
|
1424 @unnumberedsubsec Q1.3.3: Can I use the same @file{init.el} with the other Emacs?
|
|
|
1425
|
|
|
1426 Yes. The sample @file{init.el} included in the XEmacs
|
|
|
1427 distribution will show you how to handle different versions and flavors
|
|
|
1428 of Emacs.
|
|
|
1429
|
|
|
1430 @node Q1.3.4, Q1.3.5, Q1.3.3, Introduction
|
|
|
1431 @unnumberedsubsec Q1.3.4: Any good XEmacs tutorials around?
|
|
|
1432
|
|
|
1433 There's the XEmacs tutorial available from the Help Menu under
|
|
|
1434 @samp{Help->Tutorials}, or by typing @kbd{C-h t}. To check whether
|
|
|
1435 it's available in a non-english language, type @kbd{C-u C-h t TAB}, type
|
|
|
1436 the first letters of your preferred language, then type @key{RET}.
|
|
|
1437
|
|
|
1438 @comment There's an Emacs Lisp tutorial at
|
|
|
1439 @comment
|
|
|
1440 @comment @example
|
|
|
1441 @comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
|
|
|
1442 @comment @end example
|
|
|
1443 @comment
|
|
|
1444 @comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
|
|
|
1445 @comment page at
|
|
|
1446 @comment @iftex
|
|
|
1447 @comment @*
|
|
|
1448 @comment @end iftex
|
|
|
1449 @comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}.
|
|
|
1450
|
|
|
1451 @node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
|
|
|
1452 @unnumberedsubsec Q1.3.5: May I see an example of a useful XEmacs Lisp function?
|
|
|
1453
|
|
|
1454 The following function does a little bit of everything useful. It does
|
|
|
1455 something with the prefix argument, it examines the text around the
|
|
|
1456 cursor, and it's interactive so it may be bound to a key. It inserts
|
|
|
1457 copies of the current word the cursor is sitting on at the cursor. If
|
|
|
1458 you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will
|
|
|
1459 insert 3 copies.
|
|
|
1460
|
|
|
1461 @lisp
|
|
|
1462 (defun double-word (count)
|
|
|
1463 "Insert a copy of the current word underneath the cursor"
|
|
|
1464 (interactive "*p")
|
|
|
1465 (let (here there string)
|
|
|
1466 (save-excursion
|
|
|
1467 (forward-word -1)
|
|
|
1468 (setq here (point))
|
|
|
1469 (forward-word 1)
|
|
|
1470 (setq there (point))
|
|
|
1471 (setq string (buffer-substring here there)))
|
|
|
1472 (while (>= count 1)
|
|
|
1473 (insert string)
|
|
|
1474 (decf count))))
|
|
|
1475 @end lisp
|
|
|
1476
|
|
|
1477 The best way to see what is going on here is to let XEmacs tell you.
|
|
|
1478 Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor
|
|
|
1479 sitting just to the right of the function you want explained. Eg. move
|
|
|
1480 the cursor to the SPACE between @code{interactive} and @samp{"*p"} and
|
|
|
1481 hit @kbd{C-h f} to see what the function @code{interactive} does. Doing
|
|
|
1482 this will tell you that the @code{*} requires a writable buffer, and
|
|
|
1483 @code{p} converts the prefix argument to a number, and
|
|
|
1484 @code{interactive} allows you to execute the command with @kbd{M-x}.
|
|
|
1485
|
|
|
1486 @node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
|
|
|
1487 @unnumberedsubsec Q1.3.6: And how do I bind it to a key?
|
|
|
1488
|
|
|
1489 To bind to a key do:
|
|
|
1490
|
|
|
1491 @lisp
|
|
|
1492 (global-set-key "\C-cd" 'double-word)
|
|
|
1493 @end lisp
|
|
|
1494
|
|
|
1495 Or interactively, @kbd{M-x global-set-key} and follow the prompts.
|
|
|
1496
|
|
|
1497 @node Q1.3.7, Q1.3.8, Q1.3.6, Introduction
|
|
|
1498 @unnumberedsubsec Q1.3.7: What's the difference between a macro and a function?
|
|
|
1499
|
|
|
1500 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual:
|
|
|
1501
|
|
|
1502 @dfn{Macros} enable you to define new control constructs and other
|
|
|
1503 language features. A macro is defined much like a function, but instead
|
|
|
1504 of telling how to compute a value, it tells how to compute another Lisp
|
|
|
1505 expression which will in turn compute the value. We call this
|
|
|
1506 expression the @dfn{expansion} of the macro.
|
|
|
1507
|
|
|
1508 Macros can do this because they operate on the unevaluated expressions
|
|
|
1509 for the arguments, not on the argument values as functions do. They can
|
|
|
1510 therefore construct an expansion containing these argument expressions
|
|
|
1511 or parts of them.
|
|
|
1512
|
|
|
1513 Do not confuse the two terms with @dfn{keyboard macros}, which are
|
|
|
1514 another matter, entirely. A keyboard macro is a key bound to several
|
|
|
1515 other keys. Refer to manual for details.
|
|
|
1516
|
|
|
1517 @node Q1.3.8, Q1.4.1, Q1.3.7, Introduction
|
|
|
1518 @unnumberedsubsec Q1.3.8: What is @code{Custom}?
|
|
|
1519
|
|
|
1520 @code{Custom} is a system for customizing XEmacs options.
|
|
|
1521
|
|
|
1522 You can access @code{Advanced (Customize)} from the @code{Options} menu
|
|
|
1523 or invoking one of customize commands by typing eg.
|
|
|
1524 @kbd{M-x customize}, @kbd{M-x customize-face},
|
|
|
1525 @kbd{M-x customize-variable} or @kbd{M-x customize-apropos}.
|
|
|
1526
|
|
|
1527 There is also new @samp{browser} mode for Customize.
|
|
|
1528 Try it out with @kbd{M-x customize-browse}
|
|
|
1529
|
|
|
1530 @unnumberedsec 1.4: Getting Help
|
|
|
1531
|
|
|
1532 @node Q1.4.1, Q1.4.2, Q1.3.8, Introduction
|
|
|
1533 @unnumberedsubsec Q1.4.1: Where can I get help?
|
|
|
1534
|
|
|
1535 Probably the easiest way, if everything is installed, is to use Info, by
|
|
|
1536 pressing @kbd{C-h i}, or looking for an Info item on the
|
|
|
1537 Help Menu. @kbd{M-x apropos} can be used to look for particular commands.
|
|
|
1538
|
|
|
1539 For items not found in the manual, try reading this FAQ
|
|
|
1540 and reading the Usenet group comp.emacs.xemacs.
|
|
|
1541
|
|
|
1542 If you choose to post to a newsgroup, @strong{please use
|
|
|
1543 comp.emacs.xemacs}. Please do not post XEmacs related questions to
|
|
|
1544 gnu.emacs.help.
|
|
|
1545
|
|
|
1546 If you cannot post or read Usenet news, there is a corresponding mailing
|
|
|
1547 list @email{xemacs-news@@xemacs.org} which is available. It can be
|
|
|
1548 subscribed to via the Mailman Web interface or by sending mail to to
|
|
|
1549 @email{xemacs-news-request@@xemacs.org} with @samp{subscribe} in the
|
|
|
1550 body of the message. See also
|
|
|
1551 @uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a
|
|
|
1552 subscription, you may use the @email{xemacs-news-request@@xemacs.org}
|
|
|
1553 address or the Web interface. Send a message with a subject of
|
|
|
1554 @samp{unsubscribe} to be removed.
|
|
|
1555
|
|
|
1556 @node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
|
|
|
1557 @unnumberedsubsec Q1.4.2: Which mailing lists are there?
|
|
|
1558
|
|
|
1559 For complete, up-to-date info on the lists and how to subscribe, see
|
|
|
1560 @uref{http://www.xemacs.org/Lists/}.
|
|
|
1561
|
|
|
1562 @table @samp
|
|
|
1563
|
|
|
1564 @item comp.emacs.xemacs
|
|
|
1565 is a Usenet newsgroup
|
|
|
1566 for XEmacs users to discuss problems and issues that arise
|
|
|
1567 for them. It's not generally an appropriate place to ask
|
|
|
1568 about apparent bugs (use @samp{xemacs-beta}), or future plans
|
|
|
1569 (use @samp{xemacs-design}).
|
|
|
1570
|
|
|
1571 @item xemacs-announce
|
|
|
1572 is a read-only, low
|
|
|
1573 volume list for announcements concerning the XEmacs project
|
|
|
1574 and new releases of the XEmacs software.
|
|
|
1575
|
|
|
1576 @item xemacs-beta
|
|
2559
|
1577 is an open list for bug reports about beta versions of XEmacs. This
|
|
|
1578 includes the bug reports themselves, by both users and developers, as
|
|
|
1579 well as queries, follow-ups, and discussions further determining their
|
|
|
1580 nature and status. This is the primary channel for this kind of
|
|
|
1581 discussion; related code changes will usually not be applied until
|
|
|
1582 they have been discussed here. When such discussions touch on
|
|
|
1583 significant changes to the code (in particular, structural changes),
|
|
|
1584 or on changes to API's or external functionality, they should be moved
|
|
|
1585 to @samp{xemacs-design}. Requests and proposals for non-bug-related
|
|
|
1586 changes do not belong on @samp{xemacs-beta}, and should be sent to
|
|
|
1587 @samp{xemacs-design} instead.
|
|
2537
|
1588
|
|
|
1589 @item xemacs-beta-ja
|
|
|
1590 is an open list for bug
|
|
|
1591 reports and design discussion related to Mule features,
|
|
|
1592 including Japanese handling, in beta versions of XEmacs.
|
|
|
1593 Japanese is the preferred language of discussion. For most
|
|
|
1594 timely presentation to reviewers, please consider sending
|
|
|
1595 appropriate discussion to @samp{xemacs-mule} or
|
|
|
1596 @samp{xemacs-design} in English when convenient for
|
|
|
1597 the participants in discussion. When possible, bug reports
|
|
|
1598 not related to Mule (including Japanese) should be reported on
|
|
|
1599 @samp{xemacs-beta} in English.
|
|
|
1600
|
|
|
1601 @item xemacs-buildreports
|
|
|
1602 is an open list for
|
|
|
1603 submission of build-reports on beta versions of XEmacs. For
|
|
|
1604 information on what the build-reports should contain, please
|
|
|
1605 see the `etc/BETA' file which is included in each beta
|
|
|
1606 distribution.
|
|
|
1607
|
|
|
1608 @item xemacs-cvs
|
|
|
1609 is a read-only list for notices
|
|
|
1610 and information on what has been committed to the XEmacs CVS
|
|
|
1611 trees, by whom, and for what.
|
|
|
1612
|
|
|
1613 @item xemacs-design
|
|
|
1614 is an open list for
|
|
|
1615 discussing the design of XEmacs. This includes discussion
|
|
|
1616 about planned and ongoing changes to functionality and API
|
|
|
1617 changes and additions as well as requests for them. This is
|
|
|
1618 the primary channel for this kind of discussion; related code
|
|
|
1619 changes will usually not be applied until they have been
|
|
|
1620 discussed here. This does not include bug reports, which go
|
|
|
1621 to @samp{xemacs-beta}.
|
|
|
1622
|
|
|
1623 @item xemacs-mule
|
|
|
1624 is an open mailing list for
|
|
|
1625 discussion of International extensions to XEmacs including
|
|
|
1626 Mule, XIM, I18n issues, etc, and is not confined to
|
|
|
1627 developmental issues. This list is not restricted to
|
|
|
1628 English, postings in all languages are welcome.
|
|
|
1629
|
|
|
1630 @item xemacs-news
|
|
|
1631 is an open list for discussion
|
|
|
1632 and bug reporting for XEmacs. This mailing list is
|
|
|
1633 bi-directionally gatewayed with the USENET newsgroup
|
|
|
1634 comp.emacs.xemacs.
|
|
|
1635
|
|
|
1636 @item xemacs-nt
|
|
|
1637 is a developers-only mailing
|
|
|
1638 list and is intended for people who wish to work actively on
|
|
|
1639 the porting of XEmacs to Microsoft Windows NT and Microsoft
|
|
|
1640 Windows '95.
|
|
|
1641
|
|
|
1642 @item xemacs-patches
|
|
|
1643 is an open, moderated
|
|
|
1644 list for submission of patches to the XEmacs distribution
|
|
|
1645 and its packages. Anyone may subscribe or submit to
|
|
|
1646 xemacs-patches, but all submissions are reviewed by the list
|
|
|
1647 moderator before they are distributed to the
|
|
|
1648 list. Discussion is not appropriate on xemacs-patches.
|
|
|
1649
|
|
|
1650 @item xemacs-users-ja
|
|
|
1651 is an open list for
|
|
|
1652 discussion and bug reporting for XEmacs. Japanese is the
|
|
|
1653 preferred language of discussion. It is not gated to
|
|
|
1654 comp.emacs.xemacs or the @samp{xemacs} list. For
|
|
|
1655 fastest response, bugs not specifically related to Japanese
|
|
|
1656 or Mule features should be reported on
|
|
|
1657 @samp{xemacs-beta} (in English).
|
|
|
1658
|
|
|
1659 @item xemacs-users-ru
|
|
|
1660 is an open list for
|
|
|
1661 discussion and bug reporting for XEmacs. Russian is the
|
|
|
1662 preferred language of discussion. It is not gated to
|
|
|
1663 comp.emacs.xemacs or the @samp{xemacs} list. For
|
|
|
1664 fastest response, bugs not specifically related to Russian
|
|
|
1665 or Mule features should be reported on
|
|
|
1666 @samp{xemacs-beta} (in English).
|
|
|
1667 @end table
|
|
|
1668
|
|
|
1669 @node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
|
|
|
1670 @unnumberedsubsec Q1.4.3: Where are the mailing lists archived?
|
|
|
1671
|
|
|
1672 The archives can be found at @uref{http://list-archive.xemacs.org}
|
|
|
1673
|
|
|
1674 @node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
|
|
|
1675 @unnumberedsubsec Q1.4.4: How can I get two instances of info?
|
|
|
1676
|
|
|
1677 Before 21.4, you can't. The @code{info} package does not provide for
|
|
|
1678 multiple info buffers. In 21.4, this should be fixed. #### how?
|
|
|
1679
|
|
|
1680 @node Q1.4.5, Q1.5.1, Q1.4.4, Introduction
|
|
|
1681 @unnumberedsubsec Q1.4.5: How do I add new Info directories?
|
|
|
1682
|
|
|
1683 You use something like:
|
|
|
1684
|
|
|
1685 @lisp
|
|
|
1686 (setq Info-directory-list (cons
|
|
|
1687 (expand-file-name "~/info")
|
|
|
1688 Info-default-directory-list))
|
|
|
1689 @end lisp
|
|
|
1690
|
|
|
1691 @email{davidm@@prism.kla.com, David Masterson} writes:
|
|
|
1692
|
|
|
1693 @quotation
|
|
|
1694 Emacs Info and XEmacs Info do many things differently. If you're trying to
|
|
|
1695 support a number of versions of Emacs, here are some notes to remember:
|
|
|
1696
|
|
|
1697 @enumerate
|
|
|
1698 @item
|
|
|
1699 Emacs Info scans @code{Info-directory-list} from right-to-left while
|
|
|
1700 XEmacs Info reads it from left-to-right, so append to the @emph{correct}
|
|
|
1701 end of the list.
|
|
|
1702
|
|
|
1703 @item
|
|
|
1704 Use @code{Info-default-directory-list} to initialize
|
|
|
1705 @code{Info-directory-list} @emph{if} it is available at startup, but not
|
|
|
1706 all Emacsen define it.
|
|
|
1707
|
|
|
1708 @item
|
|
|
1709 Emacs Info looks for a standard @file{dir} file in each of the
|
|
|
1710 directories scanned from #1 and magically concatenates them together.
|
|
|
1711
|
|
|
1712 @item
|
|
|
1713 XEmacs Info looks for a @file{localdir} file (which consists of just the
|
|
|
1714 menu entries from a @file{dir} file) in each of the directories scanned
|
|
|
1715 from #1 (except the first), does a simple concatenation of them, and
|
|
|
1716 magically attaches the resulting list to the end of the menu in the
|
|
|
1717 @file{dir} file in the first directory.
|
|
|
1718 @end enumerate
|
|
|
1719
|
|
|
1720 Another alternative is to convert the documentation to HTML with
|
|
|
1721 texi2html and read it from a web browser like Lynx or W3.
|
|
|
1722 @end quotation
|
|
|
1723
|
|
|
1724 @unnumberedsec 1.5: Contributing to XEmacs
|
|
|
1725
|
|
|
1726 @node Q1.5.1, Q1.5.2, Q1.4.5, Introduction
|
|
|
1727 @unnumberedsubsec Q1.5.1: How do I submit changes to the FAQ?
|
|
|
1728
|
|
|
1729 The FAQ is actively maintained and modified regularly. All links should
|
|
|
1730 be up to date. Unfortunately, some of the information is out of date --
|
|
|
1731 a situation which the FAQ maintainer is working on. All submissions are
|
|
|
1732 welcome, please e-mail submissions to @email{faq@@xemacs.org, XEmacs FAQ
|
|
|
1733 maintainers}.
|
|
|
1734
|
|
|
1735 Please make sure that @samp{XEmacs FAQ} appears on the Subject: line.
|
|
|
1736 If you think you have a better way of answering a question, or think a
|
|
|
1737 question should be included, we'd like to hear about it. Questions and
|
|
|
1738 answers included into the FAQ will be edited for spelling and grammar
|
|
|
1739 and will be attributed. Answers appearing without attribution are
|
|
|
1740 either from versions of the FAQ dated before May 1996 or are from
|
|
|
1741 previous FAQ maintainers. Answers quoted from Usenet news articles will
|
|
|
1742 always be attributed, regardless of the author.
|
|
|
1743
|
|
|
1744 @node Q1.5.2, Q1.5.3, Q1.5.1, Introduction
|
|
|
1745 @unnumberedsubsec Q1.5.2: How do I become a beta tester?
|
|
|
1746
|
|
|
1747 Send an email message to @email{xemacs-beta-request@@xemacs.org} with
|
|
|
1748 the line @samp{subscribe} in the body of the message.
|
|
|
1749
|
|
|
1750 Be prepared to get your hands dirty, as beta testers are expected to
|
|
|
1751 identify problems as best they can.
|
|
|
1752
|
|
2559
|
1753 @node Q1.5.3, Q1.5.4, Q1.5.2, Introduction
|
|
2537
|
1754 @unnumberedsubsec Q1.5.3: How do I contribute to XEmacs itself?
|
|
|
1755
|
|
|
1756 It depends on the knowledge and time you possess. If you are able, by
|
|
|
1757 all means become a beta tester (@pxref{Q1.5.2}). If you are a
|
|
|
1758 programmer, try to build XEmacs and see if you can improve it.
|
|
|
1759
|
|
|
1760 Otherwise, you can still help by using XEmacs as your everyday editor
|
|
|
1761 (for pre-built binary versions, @pxref{Q1.1.2}) and reporting bugs you
|
|
|
1762 find to the mailing list.
|
|
|
1763
|
|
|
1764 Another area where we need help is the documentation: We need good
|
|
|
1765 documentation for building XEmacs and for using it. This FAQ is a
|
|
|
1766 small step in that direction.
|
|
|
1767
|
|
|
1768 Ben Wing @email{ben@@xemacs.org} writes:
|
|
|
1769
|
|
|
1770 @quotation
|
|
|
1771 BTW if you have a wish list of things that you want added, you have to
|
|
|
1772 speak up about it! More specifically, you can do the following if you
|
|
|
1773 want a feature added (in increasing order of usefulness):
|
|
|
1774
|
|
|
1775 @itemize @bullet
|
|
|
1776 @item
|
|
|
1777 Make a posting about a feature you want added.
|
|
|
1778
|
|
|
1779 @item
|
|
|
1780 Become a beta tester and make more postings about those same features.
|
|
|
1781
|
|
|
1782 @item
|
|
|
1783 Convince us that you're going to use the features in some cool and
|
|
|
1784 useful way.
|
|
|
1785
|
|
|
1786 @item
|
|
|
1787 Come up with a clear and well-thought-out API concerning the features.
|
|
|
1788
|
|
|
1789 @item
|
|
|
1790 Write the code to implement a feature and send us a patch.
|
|
|
1791 @end itemize
|
|
|
1792
|
|
|
1793 (not that we're necessarily requiring you to write the code, but we can
|
|
|
1794 always hope :)
|
|
|
1795 @end quotation
|
|
|
1796
|
|
2559
|
1797 @node Q1.5.4, Q1.5.5, Q1.5.3, Introduction
|
|
|
1798 @unnumberedsubsec Q1.5.4: How do I get started developing XEmacs?
|
|
|
1799
|
|
|
1800 First, get yourself set up under CVS so that you can access the CVS
|
|
|
1801 repositories containing the XEmacs sources and the XEmacs packages.
|
|
|
1802
|
|
|
1803 Next, set up your layout. This is important, as a good layout will
|
|
|
1804 facilitate getting things done efficiently, while a bad layout will could
|
|
|
1805 lead to disaster, as you can't figure out which code is the most recent,
|
|
|
1806 which can be thrown away, etc. We suggest the following layout: (feel free
|
|
|
1807 to make changes)
|
|
|
1808
|
|
|
1809 @itemize @bullet
|
|
|
1810 @item
|
|
|
1811 Everything goes under @file{/src/xemacs} (use a different directory if
|
|
|
1812 you want). From now, instead of saying @file{/src/xemacs}, we use
|
|
|
1813 @file{<xsrc-top>}, to make it easier in case someone picked a
|
|
|
1814 different directory.
|
|
|
1815
|
|
|
1816 @item
|
|
|
1817 Package source is in @file{<xsrc-top>/package-src}.
|
|
|
1818
|
|
|
1819 @item
|
|
|
1820 Installed packages go under @file{<xsrc-top>/xemacs-packages}, and
|
|
|
1821 @file{<xsrc-top>/mule-packages}.
|
|
|
1822
|
|
|
1823 @item
|
|
|
1824 A "workspace" is a complete copy of the sources, in which you do work of
|
|
|
1825 a particular kind. Workspaces can be differentiated by which branch of
|
|
|
1826 the source tree they extend off of -- usually either the stable or
|
|
|
1827 experimental, unless other branches have been created (for example, Ben
|
|
|
1828 created a branch for his Mule work because (1) the project was long-term
|
|
|
1829 and involved an enormous number of changes, (2) people wanted to be able
|
|
|
1830 to look at what his work in progress, and (3) he wanted to be able to
|
|
|
1831 check things in and in general use source-code control, since it was a
|
|
|
1832 long-term project). Workspaces are also differentiated in what their
|
|
|
1833 purpose is -- general working workspace, workspace for particular
|
|
|
1834 projects, workspace keeping the latest copy of the code in one of the
|
|
|
1835 branches without mods, etc.
|
|
|
1836
|
|
|
1837 @item
|
|
|
1838 Various workspaces are subdirectories under @file{<xsrc-top>}, e.g.:
|
|
|
1839
|
|
|
1840 @itemize @bullet
|
|
|
1841 @item
|
|
|
1842 @file{<xsrc-top>/working} (the workspace you're actively working on,
|
|
|
1843 periodically synched up with the latest trunk)
|
|
|
1844
|
|
|
1845 @item
|
|
|
1846 @file{<xsrc-top>/stable} (for making changes to the stable version of
|
|
|
1847 XEmacs, which sits on a branch)
|
|
|
1848
|
|
|
1849 @item
|
|
|
1850 @file{<xsrc-top>/unsigned-removal} (a workspace for a specific, difficult
|
|
|
1851 task that's going to affect lots of source and take a long time, and
|
|
|
1852 so best done in its own workspace without the interference of other
|
|
|
1853 work you're doing. Also, you can commit just this one large change,
|
|
|
1854 separate from all the other changes).
|
|
|
1855
|
|
|
1856 @item
|
|
|
1857 @file{<xsrc-top>/latest} (a copy of the latest sources on the trunk,
|
|
|
1858 i.e. the experimental version of XEmacs, with no patches in it;
|
|
|
1859 either update it periodically, by hand, or set up a cron job to do it
|
|
|
1860 automatically). Set it up so it can be built, and build it so you
|
|
|
1861 have a working XEmacs. (Building it might also go into the cron job.)
|
|
|
1862
|
|
|
1863 This workspace serves a number of purposes:
|
|
|
1864 @enumerate
|
|
|
1865 @item
|
|
|
1866 You always have a recent version of XEmacs you can compare
|
|
|
1867 against when something you're working on breaks. It's true
|
|
|
1868 that you can do this with cvs diff, but when you need to do
|
|
|
1869 some serious investigation, this method just fails.
|
|
|
1870 @item
|
|
|
1871 You (almost) always have a working, up-to-date executable that
|
|
|
1872 can be used when your executable is crashing and you need to
|
|
|
1873 keep developing it, or when you need an `xemacs' to build
|
|
|
1874 packages, etc.
|
|
|
1875 @item
|
|
|
1876 When creating new workspaces, you can just copy the `latest'
|
|
|
1877 workspace using GNU @code{cp -a}. You have all the .elc's built,
|
|
|
1878 everything else probably configured, any spare files in place
|
|
|
1879 (e.g. some annoying xpm.dll under Windows, etc.).
|
|
|
1880 @end enumerate
|
|
|
1881
|
|
|
1882 @item
|
|
|
1883 @file{<xsrc-top>/latest-stable/} (equivalent to @file{<xsrc-top>/latest/}, but
|
|
|
1884 for the Stable branch of XEmacs, rather than the Experimental branch
|
|
|
1885 of XEmacs). This may or may not be necessary depending on how much
|
|
|
1886 development you do of the stable branch.
|
|
|
1887 @end itemize
|
|
|
1888
|
|
|
1889 @item
|
|
|
1890 @file{<xsrc-top>/xemacsweb} is a workspace for working on the XEmacs
|
|
|
1891 web site.
|
|
|
1892
|
|
|
1893 @item
|
|
|
1894 @file{<xsrc-top>/in-patches} for patches received from email and saved
|
|
|
1895 to files.
|
|
|
1896
|
|
|
1897 @item
|
|
|
1898 @file{<xsrc-top>/out-patches} for locally-generated patches to be sent
|
|
|
1899 to @email{xemacs-patches@@xemacs.org}. Less useful now that the
|
|
|
1900 patcher util has been developed.
|
|
|
1901
|
|
|
1902 @item
|
|
|
1903 @file{<xsrc-top>/build}, for build trees when compiling and testing XEmacs with
|
|
|
1904 various configuration options turned off and on. The scripts in
|
|
|
1905 xemacs-builds/ben (see below) can be used to automate building XEmacs
|
|
|
1906 workspaces with many different configuration options and automatically
|
|
|
1907 filtering out the normal output so that you see only the abnormal
|
|
|
1908 output.
|
|
|
1909
|
|
|
1910 @item
|
|
|
1911 @file{<xsrc-top>/xemacs-builds}, for the xemacs-builds module, which you need
|
|
|
1912 to check out separately in CVS. This contains scripts used for building
|
|
|
1913 XEmacs, automating and simplifying using CVS, etc. Under various
|
|
|
1914 people's directories are their own build and other scripts. The
|
|
|
1915 currently most-maintained scripts are under ben/, where there are easily
|
|
|
1916 configurable scripts that can be used to easily build any workspace
|
|
|
1917 (esp. if you've more or less followed the layout presented above)
|
|
|
1918 unattended, with one or more configuration states (there's a
|
|
|
1919 pre-determined list of the most useful, but it's easy to change). The
|
|
|
1920 output is filtered and split up in various ways so that you can identify
|
|
|
1921 which output came from where, and you can see the output either full or
|
|
|
1922 with all "normal" output except occasional status messages filtered so
|
|
|
1923 that you only see the abnormal ones.
|
|
|
1924 @end itemize
|
|
|
1925
|
|
|
1926 @node Q1.5.5, Q1.6.1, Q1.5.4, Introduction
|
|
|
1927 @unnumberedsubsec Q1.5.5: What's the basic layout of the code?
|
|
|
1928
|
|
|
1929 The file @file{configure} is a shell script to acclimate XEmacs to the
|
|
|
1930 oddities of your processor and operating system. It will create a
|
|
|
1931 file named @file{Makefile} (a script for the @file{make} program), which helps
|
|
|
1932 automate the process of building and installing emacs. See INSTALL
|
|
|
1933 for more detailed information.
|
|
|
1934
|
|
|
1935 The file @file{configure.in} is the input used by the autoconf program to
|
|
|
1936 construct the @file{configure} script. Since XEmacs has configuration
|
|
|
1937 requirements that autoconf can't meet, @file{configure.in} uses an unholy
|
|
|
1938 marriage of custom-baked configuration code and autoconf macros; it
|
|
|
1939 may be wise to avoid rebuilding @file{configure} from @file{configure.in} when
|
|
|
1940 possible.
|
|
|
1941
|
|
|
1942 The file @file{Makefile.in} is a template used by @file{configure} to create
|
|
|
1943 @file{Makefile}.
|
|
|
1944
|
|
|
1945 There are several subdirectories:
|
|
|
1946
|
|
|
1947 @enumerate
|
|
|
1948 @item
|
|
|
1949 @file{src} holds the C code for XEmacs (the XEmacs Lisp interpreter and its
|
|
|
1950 primitives, the redisplay code, and some basic editing functions).
|
|
|
1951 @item
|
|
|
1952 @file{lisp} holds the XEmacs Lisp code for XEmacs (most everything else).
|
|
|
1953 @item
|
|
|
1954 @file{lib-src} holds the source code for some utility programs for use by
|
|
|
1955 or with XEmacs, like movemail and etags.
|
|
|
1956 @item
|
|
|
1957 @file{etc} holds miscellaneous architecture-independent data files
|
|
|
1958 XEmacs uses, like the tutorial text. The contents of the @file{lisp},
|
|
|
1959 @file{info} and @file{man} subdirectories are architecture-independent too.
|
|
|
1960 @item
|
|
|
1961 @file{lwlib} holds the C code for the X toolkit objects used by XEmacs.
|
|
|
1962 @item
|
|
|
1963 @file{info} holds the Info documentation tree for XEmacs.
|
|
|
1964 @item
|
|
|
1965 @file{man} holds the source code for the XEmacs online documentation.
|
|
|
1966 @item
|
|
|
1967 @file{nt} holds files used compiling XEmacs under Microsoft Windows.
|
|
|
1968 @end enumerate
|
|
|
1969
|
|
2537
|
1970 @unnumberedsec 1.6: Politics (XEmacs vs. GNU Emacs)
|
|
|
1971
|
|
2559
|
1972 @node Q1.6.1, Q1.6.2, Q1.5.5, Introduction
|
|
2537
|
1973 @unnumberedsubsec Q1.6.1: What is GNU Emacs?
|
|
|
1974
|
|
|
1975 GNU Emacs and XEmacs are related open-source text editors. Both
|
|
|
1976 derive from GNU Emacs version 18; the split between the two happened
|
|
|
1977 in 1991 (for comparison, the oldest versions of GNU Emacs date from
|
|
|
1978 1984). For information on GNU Emacs, see
|
|
|
1979 @uref{http://www.gnu.org/software/emacs/emacs.html}.
|
|
|
1980
|
|
|
1981 @node Q1.6.2, Q1.6.3, Q1.6.1, Introduction
|
|
|
1982 @unnumberedsubsec Q1.6.2: How does XEmacs differ from GNU Emacs?
|
|
428
|
1983
|
|
|
1984 For a detailed description of the differences between GNU Emacs and
|
|
|
1985 XEmacs and a detailed history of XEmacs, check out the
|
|
|
1986 @example
|
|
430
|
1987 @uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file}
|
|
428
|
1988 @end example
|
|
|
1989
|
|
2417
|
1990 @table @strong
|
|
|
1991 @item User-Visible Editing Features
|
|
|
1992 XEmacs in general tries hard to conform to exist user-interface
|
|
|
1993 standards, and to work "out-of-the-box" without the need for obscure
|
|
|
1994 customization changes. GNU Emacs, particularly version 21, has gotten
|
|
|
1995 better about this (in many cases by copying the XEmacs behavior!), but
|
|
|
1996 still has some weirdnesses. For example, the standard method of
|
|
|
1997 selecting text using the Shift key works out-of-the-box in XEmacs.
|
|
|
1998
|
|
|
1999 XEmacs has a built-in toolbar. Four toolbars can actually be configured
|
|
|
2000 simultaneously: top, bottom, left, and right toolbars.
|
|
|
2001
|
|
|
2002 XEmacs has vertical and horizontal scrollbars. Unlike in GNU Emacs 19
|
|
|
2003 (which provides a primitive form of vertical scrollbar), these are true
|
|
|
2004 toolkit scrollbars. A look-alike Motif scrollbar is provided for those
|
|
|
2005 who don't have Motif. (Even for those who do, the look-alike may be
|
|
|
2006 preferable as it is faster.)
|
|
|
2007
|
|
|
2008 XEmacs has buffer tabs along the top of the frame (although the
|
|
|
2009 position can be changed) that make it very easy to switch buffers.
|
|
|
2010
|
|
|
2011 The menubar under XEmacs is better-designed, with more thought put into
|
|
|
2012 it.
|
|
|
2013
|
|
|
2014 XEmacs can ask questions using popup dialog boxes. Any command executed
|
|
|
2015 from a menu will ask yes/no questions with dialog boxes, while commands
|
|
|
2016 executed via the keyboard will use the minibuffer.
|
|
|
2017
|
|
|
2018 XEmacs under MS Windows provides uses the standard file-dialog box for
|
|
|
2019 opening and saving files. Standard menu-accelerator behavior can easily
|
|
|
2020 be enabled using the Options menu, and integrates well into the existing
|
|
|
2021 keymap.
|
|
|
2022
|
|
|
2023 XEmacs has (still experimental) support for widgets of various sorts --
|
|
|
2024 buttons, text boxes, sliders, progress bars, etc. A progress bar is
|
|
|
2025 used in font lock to show the progress.
|
|
|
2026
|
|
|
2027 Experimental support for drag-and-drop protocols is provided from
|
|
|
2028 XEmacs 21.
|
|
|
2029
|
|
|
2030 @item General Platform Support
|
|
|
2031 If you're running on a machine with audio hardware, you can specify
|
|
|
2032 sound files for XEmacs to play instead of the default X beep. See the
|
|
|
2033 documentation of the function load-sound-file and the variable
|
|
|
2034 sound-alist. XEmacs also supports the network sound protocols NAS and
|
|
|
2035 EsounD.
|
|
|
2036
|
|
|
2037 XEmacs 21 supports database protocols with LISP bindings, currently
|
|
|
2038 including Berkeley DB, LDAP, and PostgreSQL (21.2 only).
|
|
|
2039
|
|
|
2040 XEmacs 20 and 21 support the Canna, Wnn, and SJ3 Japanese input method
|
|
|
2041 servers directly, as well as through the X Input Method (XIM)
|
|
|
2042 protocol. GNU Emacs 20 supports only the XIM protocol. Both Emacsen
|
|
|
2043 support the Quail family of input methods (implemented in LISP) for many
|
|
|
2044 languages.
|
|
|
2045
|
|
|
2046 XEmacs provides support for ToolTalk on systems that have
|
|
|
2047 it.
|
|
|
2048
|
|
|
2049 @item Packaged LISP Libraries
|
|
|
2050 Many more packages are provided standard with XEmacs than with GNU Emacs
|
|
|
2051 19 or 20.
|
|
|
2052
|
|
|
2053 XEmacs 21 supports an integrated package management system which uses
|
|
|
2054 EFS to download, then automatically install prebuilt LISP
|
|
|
2055 libraries. This allows XEmacs users much more straightforward access to
|
|
|
2056 the "latest and greatest" version of any given library.
|
|
|
2057
|
|
|
2058 We are working on a standard method for enabling, disabling and
|
|
|
2059 otherwise controlling packages, which should make them very easy to use.
|
|
|
2060
|
|
|
2061 @item LISP Programming
|
|
|
2062 From XEmacs 20 on, characters are a separate type. Characters can be
|
|
|
2063 converted to integers (and many integers can be converted to
|
|
|
2064 characters), but characters are not integers. GNU Emacs 19, XEmacs 19,
|
|
|
2065 Mule 2.3 (an extensive patch to GNU Emacs 18.55 and 19.x), and GNU Emacs
|
|
|
2066 20 (incorporating Mule 3 and later Mule 4) represent them as integers.
|
|
|
2067
|
|
|
2068 From XEmacs 20 on, the buffer is treated as an array of characters, and
|
|
|
2069 the representation of buffer text is not exposed to LISP. The GNU Emacs
|
|
|
2070 20 functions like buffer-as-multibyte are not supported.
|
|
|
2071
|
|
|
2072 In XEmacs, events are first-class objects. GNU Emacs 19 represents them
|
|
|
2073 as integers, which obscures the differences between a key gesture and
|
|
|
2074 the ancient ASCII code used to represent a particular overlapping subset
|
|
|
2075 of them.
|
|
|
2076
|
|
|
2077 In XEmacs, keymaps are first-class opaque objects. GNU Emacs 19
|
|
|
2078 represents them as complicated combinations of association lists and
|
|
|
2079 vectors. If you use the advertised functional interface to manipulation
|
|
|
2080 of keymaps, the same code will work in XEmacs, GNU Emacs 18, and GNU
|
|
|
2081 Emacs 19; if your code depends on the underlying implementation of
|
|
|
2082 keymaps, it will not.
|
|
|
2083
|
|
|
2084 XEmacs uses "extents" to represent all non-textual aspects of buffers;
|
|
|
2085 GNU Emacs 19 uses two distinct objects, "text properties" and
|
|
|
2086 "overlays", which divide up the functionality between them. Extents are
|
|
|
2087 a superset of the union of the functionality of the two GNU Emacs data
|
|
|
2088 types. The full GNU Emacs 19 interface to text properties and overlays
|
|
|
2089 is supported in XEmacs (with extents being the underlying
|
|
|
2090 representation).
|
|
|
2091
|
|
|
2092 Extents can be made to be copied into strings, and then restored, by
|
|
|
2093 kill and yank. Thus, one can specify this behavior on either "extents"
|
|
|
2094 or "text properties", whereas in GNU Emacs 19 text properties always
|
|
|
2095 have this behavior and overlays never do.
|
|
|
2096
|
|
|
2097 @item Window System Programming Interface
|
|
|
2098 XEmacs uses the MIT "Xt" toolkit instead of raw Xlib calls, which makes
|
|
|
2099 it be a more well-behaved X citizen (and also improves portability). A
|
|
|
2100 result of this is that it is possible to include other Xt "Widgets" in
|
|
|
2101 the XEmacs window. Also, XEmacs understands the standard Xt command-line
|
|
|
2102 arguments.
|
|
|
2103
|
|
|
2104 XEmacs supports Motif applications, generic Xt (e.g. Athena)
|
|
|
2105 applications, and raw Xlib applications. An XEmacs variant which
|
|
|
2106 supports GTK+ is available (integration as an option in the XEmacs
|
|
|
2107 mainline is planned for XEmacs 22), although code to take advantage of
|
|
|
2108 the support is as yet scarce.
|
|
|
2109
|
|
|
2110 An XEmacs frame can be placed within an "external client widget" managed
|
|
|
2111 by another application. This allows an application to use an XEmacs
|
|
|
2112 frame as its text pane rather than the standard Text widget that is
|
|
|
2113 provided with Motif or Athena.
|
|
|
2114
|
|
|
2115 @item Community Participation
|
|
2459
|
2116 Joining the XEmacs development team is simple. Mail to
|
|
|
2117 @email{xemacs-beta@@xemacs.org, XEmacs Developers}, and you're in! (If
|
|
|
2118 you want to be, of course. You're also welcome to just post
|
|
|
2119 development-related questions and bug reports.) The GNU Emacs
|
|
2417
|
2120 development team and internal mailing lists are still by invitation
|
|
|
2121 only.
|
|
|
2122
|
|
|
2123 The "bleeding edge" of mainline XEmacs development is available by
|
|
|
2124 anonymous CVS as are some subsidiary branches (check out the xemacs-gtk
|
|
|
2125 module for the latest in GUI features!)
|
|
|
2126
|
|
|
2127 Development and maintenance of Lisp libraries is separated from the core
|
|
|
2128 editor development at a fairly low level. This provides better
|
|
|
2129 modularization and a better division of responsibility between external
|
|
|
2130 library maintainers and the XEmacs core development team. Even for
|
|
|
2131 packages the size of Gnus, XEmacs users normally have access to a
|
|
|
2132 pre-built version within a few weeks of a major release, and minor
|
|
|
2133 updates often within days.
|
|
|
2134
|
|
|
2135 CVS commit authority is broadly dispersed. Recognized maintainers of
|
|
|
2136 LISP libraries who are willing to maintain XEmacs packaged versions
|
|
|
2137 automatically qualify for CVS accounts for their packages.
|
|
|
2138 @end table
|
|
|
2139
|
|
2537
|
2140 @node Q1.6.3, Q1.6.4, Q1.6.2, Introduction
|
|
|
2141 @unnumberedsubsec Q1.6.3: How much does XEmacs differ?
|
|
2417
|
2142
|
|
|
2143 RMS has asserted at times that XEmacs is merely a "patch" on top of
|
|
2537
|
2144 GNU Emacs (@pxref{Q1.6.4}). In fact, probably not more than 5% of the
|
|
2417
|
2145 code, if that, remains unchanged, and nearly 14 years of work has gone
|
|
|
2146 into XEmacs at this point. (GNU Emacs itself is only than 20 years
|
|
|
2147 old, and thus XEmacs has existed as a separate product for over 2/3 of
|
|
|
2148 the lifespan of GNU Emacs.) As a point of comparison, XEmacs 21.5 has
|
|
|
2149 perhaps 65,000 more lines of C code than GNU Emacs 21.2.
|
|
|
2150
|
|
|
2151 However, the XEmacs developers strive to keep their code compatible with
|
|
|
2152 GNU Emacs, especially on the Lisp level. Much effort goes into
|
|
|
2153 "synching" the XEmacs Elisp code with recent GNU Emacs releases so as to
|
|
|
2154 benefit from GNU Emacs development work. (In contrast, almost no code
|
|
|
2155 from XEmacs has made it into GNU Emacs, and in fact the GNU Emacs
|
|
|
2156 developers are instructed by RMS not to even look at XEmacs source code!
|
|
|
2157 This stems from self-imposed licensing restrictions on the part of GNU
|
|
|
2158 Emacs -- and almost certainly out of hostility, as well.)
|
|
|
2159
|
|
2537
|
2160 @node Q1.6.4, Q1.6.5, Q1.6.3, Introduction
|
|
|
2161 @unnumberedsubsec Q1.6.4: Is XEmacs "GNU"?
|
|
2417
|
2162
|
|
|
2163 RMS insists on the term "GNU XEmacs" and maintains that
|
|
|
2164
|
|
|
2165 @quotation
|
|
|
2166 XEmacs is GNU software because it's a modified version of a
|
|
|
2167 GNU program. And it is GNU software because the FSF is the copyright
|
|
|
2168 holder for most of it, and therefore the legal responsibility for
|
|
|
2169 protecting its free status falls on us whether we want it or not. This
|
|
|
2170 is why the term "GNU XEmacs" is legitimate.
|
|
|
2171 @end quotation
|
|
|
2172
|
|
|
2173 In fact, FSF is @emph{not} the copyright holder for most of the code,
|
|
2537
|
2174 as very little unmodified FSF code remains (@pxref{Q1.6.3}).
|
|
2417
|
2175
|
|
|
2176 Furthermore, RMS's assertion that XEmacs is "GNU" seems rather bizarre
|
|
|
2177 to the XEmacs developers given RMS's hostility and general lack of
|
|
|
2178 interest in cooperation. "GNU" software in general is part of the GNU
|
|
|
2179 Project, is distributed by it on their FTP site, and receives support
|
|
|
2180 (or at least cooperation), as well as implicit endorsement, from it.
|
|
|
2181 The GNU Project, however, has never supported XEmacs and never
|
|
|
2182 distributed XEmacs, and RMS's hostility is the farthest thing possible
|
|
|
2183 from an endorsement. In fact, the GNU Project distributes a number of
|
|
|
2184 non-GNU software projects on the FSF web site, but again XEmacs is not
|
|
|
2185 one of them.
|
|
|
2186
|
|
2537
|
2187 @node Q1.6.5, Q1.6.6, Q1.6.4, Introduction
|
|
|
2188 @unnumberedsubsec Q1.6.5: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
2417
|
2189
|
|
|
2190 Unfortunately even the naming of these two applications has become
|
|
|
2191 politicized. Much of this stems from RMS, who has a history of
|
|
|
2192 politicizing similar issues. (Compare the controversy over "Lignux"
|
|
|
2193 and "GNU/Linux".) We would prefer that the terms "XEmacs" and "GNU
|
|
|
2194 Emacs" be used, which are neutral and acceptable to most people. RMS,
|
|
|
2195 however, is not willing to accept these terms. He insists that, if
|
|
|
2196 his product is called "GNU Emacs", then ours must be called "GNU
|
|
2537
|
2197 XEmacs". (For our opinion of this term, @xref{Q1.6.4}.) On the other
|
|
2417
|
2198 hand, if our product is to be called "XEmacs", as we prefer, then his
|
|
|
2199 product must simply be called "Emacs". The intent of this seems
|
|
|
2200 clear: RMS wants to make sure the names reflect his view that his
|
|
|
2201 version is the "real" Emacs and ours is merely a derivative,
|
|
2537
|
2202 second-class product (@pxref{Q1.6.3}).
|
|
2417
|
2203
|
|
|
2204 The XEmacs developers hope that you will use the neutral terms
|
|
|
2205 "XEmacs" and "GNU Emacs" for these two specific products. "Emacs", on
|
|
|
2206 the other hand, is a generic term for a class of programmable text
|
|
|
2207 editors with a similar look-and-feel, and usually a Lisp-based
|
|
|
2208 extension language. These trace themselves back to early editors such
|
|
|
2209 as EINE, ZWEI, ZMACS and Multics Emacs. @xref{A History of Emacs,,,
|
|
|
2210 internals, XEmacs Internals Manual}.
|
|
|
2211
|
|
|
2212 We also call upon RMS, in the spirit of furthering cooperation, to
|
|
|
2213 stop politicizing this issue and use the neutral terms "XEmacs" and
|
|
|
2214 "GNU Emacs". We have already acceded to RMS' wishes in this respect,
|
|
|
2215 and we expect him to do the same. (In the past, the XEmacs developers
|
|
|
2216 often used the terms "FSF Emacs" or "FSFmacs" or "RMSmacs" in
|
|
|
2217 reference to GNU Emacs; these terms were apparently modeled after RMS'
|
|
|
2218 own usage of "Gosmacs" and "Gosling Emacs" in reference to Unipress
|
|
|
2219 Emacs, produced by James Gosling. RMS, however, considers such terms
|
|
|
2220 to be insulting, so we refrain from using them as much as possible in
|
|
|
2221 preference to GNU Emacs.)
|
|
|
2222
|
|
2537
|
2223 @node Q1.6.6, Q1.7.1, Q1.6.5, Introduction
|
|
|
2224 @unnumberedsubsec Q1.6.6: Why haven't XEmacs and GNU Emacs merged?
|
|
2417
|
2225
|
|
|
2226 There are currently irreconcilable differences in the views about
|
|
|
2227 technical, programming, design, organizational and legal matters
|
|
|
2228 between Richard Stallman (RMS), the author and leader of the GNU Emacs
|
|
|
2229 project, and the XEmacs development team which provide little hope for
|
|
|
2230 a merge to take place in the short-term future. There have been
|
|
|
2231 repeated attempts at merging by all of the major XEmacs developers,
|
|
|
2232 starting from the early days of Lucid Emacs (in 1991), but they have
|
|
|
2233 all failed. RMS has very strong views about how GNU Emacs should be
|
|
|
2234 structured and how his project should be run, and during the repeated
|
|
|
2235 merge efforts has never demonstrated any realistic interest in
|
|
|
2236 sufficiently compromising or ceding control to allow a middle ground
|
|
|
2237 to be found. The basic problem seems to be the very different goals
|
|
|
2238 of RMS and the XEmacs project. The primary goals of the XEmacs
|
|
|
2239 project are technical and organizational -- we want to create the best
|
|
|
2240 editor possible, and to make it as easy as possible for people around
|
|
|
2241 the world to contribute. The primary goals of RMS, on the other hand,
|
|
|
2242 are political, and GNU Emacs, and any potential merge efforts with
|
|
|
2243 XEmacs, are strictly subservient to these goals. In fact, in many
|
|
|
2244 ways RMS sees GNU Emacs as the "poster child" of his aims, the one
|
|
|
2245 program in the GNU project that above all others must set an example
|
|
|
2246 to the world. (This has to do with the fact that GNU Emacs was the
|
|
|
2247 first program in the GNU project, and the only one that he is still
|
|
|
2248 personally involved with on a day-to-day basis.) Given his goals, his
|
|
|
2249 position is completely reasonable -- but unfortunately, makes any
|
|
|
2250 merge impossible.
|
|
|
2251
|
|
|
2252 From the XEmacs perspective, the most intractable issues appear to be
|
|
|
2253 legal and organizational, specifically:
|
|
428
|
2254
|
|
|
2255 @itemize @bullet
|
|
|
2256 @item
|
|
2417
|
2257 RMS requires "legal papers" to be signed for all contributions of code
|
|
|
2258 to GNU Emacs over 10 lines or so, transferring the copyright and all
|
|
|
2259 legal rights to the code to the Free Software Foundation. XEmacs does
|
|
|
2260 not and has never required this, since it has the practical effect of
|
|
|
2261 discouraging individual and in particular corporate contributions --
|
|
|
2262 corporations will almost never sign away their legal rights to code
|
|
|
2263 since it makes it impossible to reuse the code in any product that
|
|
|
2264 whose license is not compatible with the GNU General Public License.
|
|
|
2265 Since RMS has shown no inclination to compromise on this issue, a
|
|
|
2266 merge would require that most of the existing XEmacs code would need
|
|
|
2267 to be thrown away and rewritten -- something the XEmacs developers are
|
|
|
2268 understandably reluctant to do.
|
|
|
2269
|
|
|
2270 @item
|
|
|
2271 A repeated stumbling block in the merge talks has been the issue of
|
|
|
2272 organizational control over the resulting product. RMS has made it
|
|
|
2273 clear that he intends to have final say over design issues in a merged
|
|
|
2274 Emacs. Unfortunately, RMS and the XEmacs developers have repeatedly
|
|
|
2275 clashed over design decisions, and RMS' insistence on getting his way
|
|
|
2276 in such disagreements was the very reason for the split in the first
|
|
|
2277 place. This same issue has come up again and again in merge talks and
|
|
|
2278 we have never been able to come to a satisfactory resolution. To the
|
|
|
2279 extent that RMS is willing to compromise at all, it appears to be of a
|
|
|
2280 purely political rather than technical nature -- "If we support this
|
|
|
2281 feature of yours, we also get to support this other feature of mine."
|
|
|
2282 The XEmacs developers cannot see how such a process would lead to
|
|
|
2283 anything but a mess of incompatible things hodgepodged together.
|
|
|
2284
|
|
|
2285 @item
|
|
|
2286 Because of the years of separate development, distinct and
|
|
|
2287 incompatible interfaces have developed and merging would be extremely
|
|
|
2288 difficult even with the above non-technical issues resolved. The
|
|
|
2289 problem has been exacerbated by the issue of legal papers -- because
|
|
|
2290 XEmacs code is not "kosher" from RMS' perspective, he discourages
|
|
|
2291 developers from even looking at it out of legal concerns. Although it
|
|
|
2292 is still possible to read the XEmacs documentation and run the
|
|
|
2293 program, the practical effect of this prohibition has been to strongly
|
|
|
2294 discourage code-sharing and cooperative development -- although a
|
|
|
2295 great deal of GNU Emacs code has been incorporated into XEmacs,
|
|
|
2296 practically none has gone the other direction.
|
|
428
|
2297 @end itemize
|
|
|
2298
|
|
|
2299 If you have a comment to add regarding the merge, it is a good idea to
|
|
2417
|
2300 avoid posting to the newsgroups, because of the very heated flamewars
|
|
|
2301 that often result. Mail your questions to
|
|
|
2302 @email{xemacs-beta@@xemacs.org} and @email{emacs-devel@@gnu.org}.
|
|
|
2303
|
|
2537
|
2304 @unnumberedsec 1.7: External Packages
|
|
|
2305
|
|
2559
|
2306 @node Q1.7.1, Q1.7.2, Q1.6.6, Introduction
|
|
|
2307 @unnumberedsubsec Q1.7.1: What is the package system?
|
|
|
2308
|
|
|
2309 In order to reduce the size and increase the maintainability of
|
|
|
2310 XEmacs, the majority of the Elisp packages that came with previous
|
|
|
2311 releases have been unbundled. They have been replaced by the package
|
|
|
2312 system. Each elisp add-on (or groups of them when they are small) now
|
|
|
2313 comes in its own tarball that contains a small search hierarchy.
|
|
|
2314
|
|
|
2315 You select just the ones you need. Install them by untarring them into
|
|
|
2316 the right place. On startup XEmacs will find them, set up the load
|
|
|
2317 path correctly, install autoloads, etc, etc.
|
|
|
2318
|
|
|
2319 @xref{Q2.1.1}, for more info on how to download and install the packages.
|
|
|
2320
|
|
|
2321 @node Q1.7.2, Q1.7.3, Q1.7.1, Introduction
|
|
|
2322 @unnumberedsubsec Q1.7.2: Which external packages are there?
|
|
2537
|
2323
|
|
|
2324 @subheading Normal Packages
|
|
|
2325
|
|
|
2326 A very broad collection of elisp packages.
|
|
2417
|
2327
|
|
|
2328 @table @asis
|
|
2537
|
2329 @item Sun
|
|
|
2330 Support for Sparcworks.
|
|
|
2331
|
|
|
2332 @item ada
|
|
|
2333 Ada language support.
|
|
|
2334
|
|
|
2335 @item apel
|
|
|
2336 A Portable Emacs Library. Used by XEmacs MIME support.
|
|
|
2337
|
|
|
2338 @item auctex
|
|
|
2339 Basic TeX/LaTeX support.
|
|
|
2340
|
|
|
2341 @item bbdb
|
|
|
2342 The Big Brother Data Base: a rolodex-like database program.
|
|
|
2343
|
|
|
2344 @item build
|
|
|
2345 Build XEmacs from within (UNIX, Windows).
|
|
|
2346
|
|
|
2347 @item c-support
|
|
|
2348 Basic single-file add-ons for editing C code.
|
|
|
2349
|
|
|
2350 @item calc
|
|
|
2351 Emacs calculator.
|
|
|
2352
|
|
|
2353 @item calendar
|
|
|
2354 Calendar and diary support.
|
|
|
2355
|
|
|
2356 @item cc-mode
|
|
|
2357 C, C++, Objective-C, Java, CORBA IDL, Pike and AWK language support.
|
|
|
2358
|
|
|
2359 @item clearcase
|
|
|
2360 New Clearcase Version Control for XEmacs (UNIX, Windows).
|
|
|
2361
|
|
|
2362 @item clearcase
|
|
|
2363 Support for the Clearcase version control system.
|
|
|
2364
|
|
|
2365 @item cookie
|
|
|
2366 "Fortune cookie"-style messages. Includes Spook (suspicious phrases)
|
|
|
2367 and Yow (Zippy quotes).
|
|
|
2368
|
|
|
2369 @item crisp
|
|
|
2370 Crisp/Brief emulation.
|
|
|
2371
|
|
|
2372 @item debug
|
|
|
2373 GUD, gdb, dbx debugging support.
|
|
|
2374
|
|
|
2375 @item dictionary
|
|
|
2376 Interface to RFC2229 dictionary servers.
|
|
|
2377
|
|
|
2378 @item dired
|
|
|
2379 The DIRectory EDitor is for manipulating, and running commands on
|
|
|
2380 files in a directory.
|
|
|
2381
|
|
|
2382 @item docbookide
|
|
|
2383 DocBook editing support.
|
|
|
2384
|
|
|
2385 @item ecb
|
|
|
2386 Emacs source code browser.
|
|
|
2387
|
|
|
2388 @item ecrypto
|
|
|
2389 Crypto functionality in Emacs Lisp.
|
|
|
2390
|
|
|
2391 @item edebug
|
|
|
2392 An Emacs Lisp debugger.
|
|
|
2393
|
|
|
2394 @item ediff
|
|
|
2395 Interface over GNU patch.
|
|
|
2396
|
|
|
2397 @item edit-utils
|
|
|
2398 Miscellaneous editor extensions, you probably need this.
|
|
|
2399
|
|
|
2400 @item edt
|
|
|
2401 DEC EDIT/EDT emulation.
|
|
|
2402
|
|
|
2403 @item efs
|
|
|
2404 Treat files on remote systems the same as local files.
|
|
|
2405
|
|
|
2406 @item eieio
|
|
|
2407 Enhanced Implementation of Emacs Interpreted Objects.
|
|
|
2408
|
|
|
2409 @item elib
|
|
|
2410 Portable Emacs Lisp utilities library.
|
|
|
2411
|
|
|
2412 @item emerge
|
|
|
2413 Another interface over GNU patch.
|
|
|
2414
|
|
|
2415 @item erc
|
|
|
2416 ERC is an Emacs InternetRelayChat client.
|
|
|
2417
|
|
|
2418 @item escreen
|
|
|
2419 Multiple editing sessions withing a single frame (like screen).
|
|
|
2420
|
|
|
2421 @item eshell
|
|
|
2422 Command shell implemented entirely in Emacs Lisp.
|
|
|
2423
|
|
|
2424 @item ess
|
|
|
2425 ESS: Emacs Speaks Statistics.
|
|
|
2426
|
|
|
2427 @item eterm
|
|
|
2428 Terminal emulation.
|
|
|
2429
|
|
|
2430 @item eudc
|
|
|
2431 Emacs Unified Directory Client (LDAP, PH).
|
|
|
2432
|
|
|
2433 @item footnote
|
|
|
2434 Footnoting in mail message editing modes.
|
|
|
2435
|
|
|
2436 @item forms
|
|
|
2437 Forms editing support (obsolete, use Widget instead).
|
|
|
2438
|
|
|
2439 @item fortran-modes
|
|
|
2440 Fortran support.
|
|
|
2441
|
|
|
2442 @item fortran-modes
|
|
|
2443 Fortran language support.
|
|
|
2444
|
|
|
2445 @item frame-icon
|
|
|
2446 Set up mode-specific icons for each frame under XEmacs.
|
|
|
2447
|
|
|
2448 @item fsf-compat
|
|
|
2449 GNU Emacs compatibility files.
|
|
|
2450
|
|
|
2451 @item games
|
|
|
2452 Tetris, Sokoban, and Snake.
|
|
|
2453
|
|
|
2454 @item general-docs
|
|
|
2455 General documentation. Presently, empty.
|
|
|
2456
|
|
|
2457 @item gnats
|
|
|
2458 XEmacs bug reports.
|
|
|
2459
|
|
|
2460 @item gnus
|
|
|
2461 The Gnus Newsreader and Mailreader.
|
|
|
2462
|
|
|
2463 @item haskell-mode
|
|
|
2464 Haskell editing support.
|
|
|
2465
|
|
|
2466 @item hm--html-menus
|
|
|
2467 HTML editing.
|
|
|
2468
|
|
|
2469 @item hyperbole
|
|
|
2470 Hyperbole: The Everyday Info Manager.
|
|
|
2471
|
|
|
2472 @item ibuffer
|
|
|
2473 Advanced replacement for buffer-menu.
|
|
|
2474
|
|
|
2475 @item idlwave
|
|
|
2476 Editing and Shell mode for the Interactive Data Language.
|
|
|
2477
|
|
|
2478 @item igrep
|
|
|
2479 Enhanced front-end for Grep.
|
|
|
2480
|
|
|
2481 @item ilisp
|
|
|
2482 Front-end for interacting with Inferior Lisp (external lisps).
|
|
|
2483
|
|
|
2484 @item ispell
|
|
|
2485 Spell-checking with GNU ispell.
|
|
|
2486
|
|
|
2487 @item jde
|
|
|
2488 Integrated Development Environment for Java.
|
|
|
2489
|
|
|
2490 @item liece
|
|
|
2491 IRC (Internet Relay Chat) client for Emacs. Note, this package is
|
|
|
2492 deprecated and will be removed, use riece instead.
|
|
|
2493
|
|
|
2494 @item mail-lib
|
|
|
2495 Fundamental lisp files for providing email support.
|
|
|
2496
|
|
|
2497 @item mailcrypt
|
|
|
2498 Support for messaging encryption with PGP.
|
|
|
2499
|
|
|
2500 @item mew
|
|
|
2501 Messaging in an Emacs World; a MIME-based email program.
|
|
|
2502
|
|
|
2503 @item mh-e
|
|
|
2504 The XEmacs Interface to the MH Mail System.
|
|
|
2505
|
|
|
2506 @item mine
|
|
|
2507 Elisp implementation of the game 'Minehunt'.
|
|
|
2508
|
|
|
2509 @item misc-games
|
|
|
2510 Other amusements and diversions.
|
|
|
2511
|
|
|
2512 @item mmm-mode
|
|
|
2513 Support for Multiple Major Modes within a single buffer.
|
|
|
2514
|
|
|
2515 @item net-utils
|
|
|
2516 Miscellaneous Networking Utilities.
|
|
|
2517
|
|
|
2518 @item ocaml
|
|
|
2519 Objective Caml editing support.
|
|
|
2520
|
|
|
2521 @item oo-browser
|
|
|
2522 OO-Browser: The Multi-Language Object-Oriented Code Browser.
|
|
|
2523
|
|
|
2524 @item ocaml
|
|
|
2525 Objective Caml editing support.
|
|
|
2526
|
|
|
2527 @item os-utils
|
|
|
2528 Miscellaneous single-file O/S utilities, for printing, archiving,
|
|
|
2529 compression, remote shells, etc.
|
|
|
2530
|
|
|
2531 @item pc
|
|
|
2532 PC style interface emulation.
|
|
|
2533
|
|
|
2534 @item pcl-cvs
|
|
|
2535 CVS frontend.
|
|
|
2536
|
|
|
2537 @item pcomplete
|
|
|
2538 Provides programmatic completion.
|
|
|
2539
|
|
|
2540 @item perl-modes
|
|
|
2541 Perl support.
|
|
|
2542
|
|
|
2543 @item pgg
|
|
|
2544 Emacs interface to various PGP implementations.
|
|
|
2545
|
|
|
2546 @item prog-modes
|
|
|
2547 Support for various programming languages.
|
|
|
2548
|
|
|
2549 @item ps-print
|
|
|
2550 Printing functions and utilities.
|
|
|
2551
|
|
|
2552 @item psgml
|
|
|
2553 Validated HTML/SGML editing.
|
|
|
2554
|
|
|
2555 @item psgml-dtds
|
|
|
2556 A collection of DTDs for psgml. Note that this package is deprecated
|
|
|
2557 and will be removed in the future, most likely Q2/2003. Instead of using
|
|
|
2558 this, you should install needed DTDs yourself.
|
|
|
2559
|
|
|
2560 @item python-modes
|
|
|
2561 Python language support.
|
|
|
2562
|
|
|
2563 @item reftex
|
|
|
2564 Emacs support for LaTeX cross-references, citations.
|
|
|
2565
|
|
|
2566 @item riece
|
|
|
2567 IRC (Internet Relay Chat) client for Emacs.
|
|
|
2568
|
|
|
2569 @item rmail
|
|
|
2570 An obsolete Emacs mailer. If you do not already use it don't start.
|
|
|
2571
|
|
|
2572 @item ruby-modes
|
|
|
2573 Ruby support.
|
|
|
2574
|
|
|
2575 @item sasl
|
|
|
2576 Simple Authentication and Security Layer (SASL) library.
|
|
|
2577
|
|
|
2578 @item scheme
|
|
|
2579 Front-end support for Inferior Scheme.
|
|
|
2580
|
|
|
2581 @item semantic
|
|
|
2582 Semantic bovinator (Yacc/Lex for XEmacs). Includes Senator.
|
|
|
2583
|
|
|
2584 @item sgml
|
|
|
2585 SGML/Linuxdoc-SGML editing.
|
|
|
2586
|
|
|
2587 @item sh-script
|
|
|
2588 Support for editing shell scripts.
|
|
|
2589
|
|
|
2590 @item sieve
|
|
|
2591 Manage Sieve email filtering scripts.
|
|
|
2592
|
|
|
2593 @item slider
|
|
|
2594 User interface tool.
|
|
|
2595
|
|
|
2596 @item sml-mode
|
|
|
2597 SML editing support.
|
|
|
2598
|
|
|
2599 @item sounds-au
|
|
|
2600 XEmacs Sun sound files.
|
|
|
2601
|
|
|
2602 @item sounds-wav
|
|
|
2603 XEmacs Microsoft sound files.
|
|
|
2604
|
|
|
2605 @item speedbar
|
|
|
2606 Provides a separate frame with convenient references.
|
|
|
2607
|
|
|
2608 @item strokes
|
|
|
2609 Mouse enhancement utility.
|
|
|
2610
|
|
|
2611 @item supercite
|
|
|
2612 An Emacs citation tool for News & Mail messages.
|
|
|
2613
|
|
|
2614 @item texinfo
|
|
|
2615 XEmacs TeXinfo support.
|
|
|
2616
|
|
|
2617 @item text-modes
|
|
|
2618 Miscellaneous support for editing text files.
|
|
|
2619
|
|
|
2620 @item textools
|
|
|
2621 Miscellaneous TeX support.
|
|
|
2622
|
|
|
2623 @item time
|
|
|
2624 Display time & date on the modeline.
|
|
|
2625
|
|
|
2626 @item tm
|
|
|
2627 Emacs MIME support. Not needed for gnus >= 5.8.0.
|
|
|
2628
|
|
|
2629 @item tooltalk
|
|
|
2630 Support for building with Tooltalk.
|
|
|
2631
|
|
|
2632 @item tpu
|
|
|
2633 DEC EDIT/TPU support.
|
|
|
2634
|
|
|
2635 @item tramp
|
|
|
2636 Remote shell-based file editing. This is similar to EFS or Ange-FTP,
|
|
|
2637 but works with rsh/ssh and rcp/scp.
|
|
|
2638
|
|
|
2639 @item vc
|
|
|
2640 Version Control for Free systems.
|
|
|
2641
|
|
|
2642 @item vc-cc
|
|
|
2643 Version Control for ClearCase (UnFree) systems.
|
|
|
2644
|
|
|
2645 @item vhdl
|
|
|
2646 Support for VHDL.
|
|
|
2647
|
|
|
2648 @item view-process
|
|
|
2649 A Unix process browsing tool.
|
|
|
2650
|
|
|
2651 @item viper
|
|
|
2652 VI emulation support.
|
|
|
2653
|
|
|
2654 @item vm
|
|
|
2655 An Emacs mailer.
|
|
|
2656
|
|
|
2657 @item w3
|
|
|
2658 A Web browser.
|
|
|
2659
|
|
|
2660 @item x-symbol
|
|
|
2661 Semi WYSIWYG for LaTeX, HTML, etc, using additional fonts.
|
|
|
2662
|
|
|
2663 @item xemacs-base
|
|
|
2664 Fundamental XEmacs support, you almost certainly need this.
|
|
|
2665
|
|
|
2666 @item xemacs-devel
|
|
|
2667 XEmacs Lisp developer support. This package contains utilities for
|
|
|
2668 supporting Lisp development. It is a single-file package so it may be
|
|
|
2669 tailored.
|
|
|
2670
|
|
|
2671 @item xlib
|
|
|
2672 Emacs interface to X server.
|
|
|
2673
|
|
|
2674 @item xslide
|
|
|
2675 XSL editing support.
|
|
|
2676
|
|
|
2677 @item xslt-process
|
|
|
2678 A minor mode for (X)Emacs which allows running an XSLT processor on a
|
|
|
2679 buffer.
|
|
|
2680
|
|
|
2681 @item xwem
|
|
|
2682 X Emacs Window Manager.
|
|
|
2683
|
|
|
2684 @item zenirc
|
|
|
2685 ZENIRC IRC Client.
|
|
2417
|
2686 @end table
|
|
|
2687
|
|
2537
|
2688 @subheading Mule Support (mule)
|
|
|
2689
|
|
|
2690 MULti-lingual Enhancement. Support for world scripts such as
|
|
|
2691 Latin, Arabic, Cyrillic, Chinese, Japanese, Greek, Hebrew etc.
|
|
|
2692 To use these packages your XEmacs must be compiled with Mule
|
|
|
2693 support.
|
|
|
2694
|
|
|
2695 @table @asis
|
|
|
2696 @item edict
|
|
|
2697 MULE: Lisp Interface to EDICT, Kanji Dictionary.
|
|
|
2698
|
|
|
2699 @item egg-its
|
|
|
2700 MULE: Wnn (4.2 and 6) support. SJ3 support.
|
|
|
2701
|
|
|
2702 @item latin-unity
|
|
|
2703 MULE: find single ISO 8859 character set to encode a buffer.
|
|
|
2704
|
|
|
2705 @item latin-unity
|
|
|
2706 Unify character sets in a buffer. When characters belong to disjoint
|
|
|
2707 character sets, this attempts to translate the characters so
|
|
|
2708 that they belong to one character set. If the buffer coding system is
|
|
|
2709 not sufficient, this suggests different coding systems.
|
|
|
2710
|
|
|
2711 @item leim
|
|
|
2712 MULE: Quail. All non-English and non-Japanese language support.
|
|
|
2713
|
|
|
2714 @item locale
|
|
|
2715 MULE: Localized menubars and localized splash screens.
|
|
|
2716
|
|
|
2717 @item lookup
|
|
|
2718 Dictionary support. (This isn't an English dictionary program)
|
|
|
2719
|
|
|
2720 @item mule-base
|
|
|
2721 MULE: Basic Mule support, required for building with Mule.
|
|
|
2722
|
|
|
2723 @item mule-ucs
|
|
|
2724 MULE: Extended coding systems (including Unicode) for XEmacs.
|
|
|
2725
|
|
|
2726 @item mule-ucs
|
|
|
2727 Extended coding systems (including Unicode) for XEmacs.
|
|
|
2728
|
|
|
2729 @item skk
|
|
|
2730 Another Japanese Language Input Method. Can be used without a
|
|
|
2731 separate process running as a dictionary server.
|
|
|
2732 @end table
|
|
|
2733
|
|
2559
|
2734 @node Q1.7.3, Q1.7.4, Q1.7.2, Introduction
|
|
|
2735 @unnumberedsubsec Q1.7.3: Do I need to have the packages to run XEmacs?
|
|
|
2736
|
|
|
2737 Strictly speaking, no. XEmacs will build and install just fine without
|
|
|
2738 any packages installed. However, only the most basic editing functions
|
|
|
2739 will be available with no packages installed, so installing packages is
|
|
|
2740 an essential part of making your installed XEmacs _useful_.
|
|
|
2741
|
|
|
2742 @node Q1.7.4, Q1.8.1, Q1.7.3, Introduction
|
|
|
2743 @unnumberedsubsec Q1.7.4: Is there a way to find which package has particular functionality?
|
|
|
2744
|
|
|
2745 If you want to find out which package contains the functionality you
|
|
|
2746 are looking for, use @kbd{M-x package-get-package-provider}, and give it a
|
|
|
2747 symbol that is likely to be in that package.
|
|
|
2748
|
|
|
2749 For example, if some code you want to use has a @code{(require 'thingatpt)}
|
|
|
2750 in it:
|
|
|
2751
|
|
|
2752 @example
|
|
|
2753 M-x package-get-package-provider RET thingatpt RET
|
|
|
2754 @end example
|
|
|
2755
|
|
|
2756 which will return something like: @samp{(fsf-compat "1.08").}
|
|
|
2757
|
|
2537
|
2758 @unnumberedsec 1.8: Internationalization
|
|
|
2759
|
|
2559
|
2760 @node Q1.8.1, Q1.8.2, Q1.7.4, Introduction
|
|
2537
|
2761 @unnumberedsubsec Q1.8.1: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
442
|
2762
|
|
|
2763 Both the stable and development versions of XEmacs include
|
|
1135
|
2764 internationalization support (aka MULE). MULE currently (21.4) works on
|
|
|
2765 UNIX and Linux systems. It is possible to build with MULE on Windows
|
|
|
2766 systems, but if you really need MULE on Windows, it is recommended that
|
|
|
2767 you build and use the development (21.5) version, and deal with the
|
|
|
2768 instability of the development tree. Binaries compiled without MULE
|
|
|
2769 support run faster than MULE capable XEmacsen.
|
|
428
|
2770
|
|
2537
|
2771 @node Q1.8.2, Q1.8.3, Q1.8.1, Introduction
|
|
|
2772 @unnumberedsubsec Q1.8.2: How can I help with internationalization?
|
|
430
|
2773
|
|
|
2774 If you would like to help, you may want to join the
|
|
|
2775 @email{xemacs-mule@@xemacs.org} mailing list. Especially needed are
|
|
|
2776 people who speak/write languages other than English, who are willing to
|
|
|
2777 use XEmacs/MULE regularly, and have some experience with Elisp.
|
|
428
|
2778
|
|
1135
|
2779 Translations of the TUTORIAL and man page are welcome, and XEmacs does
|
|
|
2780 support multilingual menus, but we have few current translations.
|
|
|
2781
|
|
2537
|
2782 @xref{Q1.5.2, How do I become a Beta Tester?}.
|
|
|
2783
|
|
|
2784 @node Q1.8.3, Q1.8.4, Q1.8.2, Introduction
|
|
|
2785 @unnumberedsubsec Q1.8.3: How do I type non-ASCII characters?
|
|
2417
|
2786
|
|
2459
|
2787 @xref{Q3.0.6, How can you type in special characters in XEmacs?}, in
|
|
2417
|
2788 part 3 of this FAQ, for some simple methods that also work in non-MULE
|
|
|
2789 builds of XEmacs (but only for one-octet coded character sets, and
|
|
|
2790 mostly for ISO 8859/1). Many of the methods available for Cyrillic
|
|
2537
|
2791 (@pxref{Q1.8.7, How about Cyrillic modes?}) work without MULE. MULE
|
|
|
2792 has more general capabilities. @xref{Q1.8.5, Please explain the
|
|
2417
|
2793 various input methods in MULE/XEmacs}.
|
|
|
2794
|
|
2459
|
2795 @xref{Q4.0.8, How do I display non-ASCII characters?}, which covers
|
|
2417
|
2796 display of non-ASCII characters.
|
|
|
2797
|
|
2537
|
2798 @node Q1.8.4, Q1.8.5, Q1.8.3, Introduction
|
|
|
2799 @unnumberedsubsec Q1.8.4: Can XEmacs messages come out in a different language?
|
|
428
|
2800
|
|
1135
|
2801 The message-catalog support was written but is badly bit-rotted. XEmacs
|
|
|
2802 20 and 21 did @emph{not} support it, and early releases of XEmacs 22
|
|
|
2803 will not either.
|
|
|
2804
|
|
|
2805 However, menubar localization @emph{does} work. To enable it, add to
|
|
|
2806 your @file{Emacs} file entries like this:
|
|
428
|
2807
|
|
|
2808 @example
|
|
440
|
2809 Emacs*XlwMenu.resourceLabels: True
|
|
|
2810 Emacs*XlwMenu.file.labelString: Fichier
|
|
442
|
2811 Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster oeffnen
|
|
428
|
2812 @end example
|
|
|
2813
|
|
|
2814 The name of the resource is derived from the non-localized entry by
|
|
|
2815 removing punctuation and capitalizing as above.
|
|
|
2816
|
|
2537
|
2817 @node Q1.8.5, Q1.8.6, Q1.8.4, Introduction
|
|
|
2818 @unnumberedsubsec Q1.8.5: Please explain the various input methods in MULE/XEmacs
|
|
428
|
2819
|
|
1135
|
2820 Mule supports a wide variety of input methods. There are three basic
|
|
|
2821 classes: Lisp implementations, generic platform support, and library
|
|
|
2822 interfaces.
|
|
|
2823
|
|
|
2824 @emph{Lisp implementations} include Quail, which provides table-driven input
|
|
|
2825 methods for almost all the character sets that Mule supports (including
|
|
|
2826 all of the ISO 8859 family, the Indic languages, Thai, and so on), and
|
|
|
2827 SKK, for Japanese. (SKK also supports an interface to an external
|
|
|
2828 "dictionary server" process.) Quail supports both typical "dead-key"
|
|
|
2829 methods (eg, in the "latin-1-prefix" method, @kbd{" a} produces ä, LATIN
|
|
|
2830 SMALL LETTER A WITH DIAERESIS), and the complex dictionary-based phonetic
|
|
|
2831 methods used for Asian ideographic languages like Chinese.
|
|
|
2832
|
|
|
2833 Lisp implementations can be less powerful (but they are not perceptibly
|
|
|
2834 inefficient), and of course are not portable to non-Emacs applications.
|
|
|
2835 The incompatibility can be very annoying. On the other hand, they
|
|
|
2836 require no special platform support or external libraries, so if you can
|
|
|
2837 display the characters, Mule can input them for you and you can edit,
|
|
|
2838 anywhere.
|
|
|
2839
|
|
|
2840 @emph{Generic platform support} is currently limited to the X Input
|
|
|
2841 Method (XIM) framework, although support for MSIME (for MS Windows) is
|
|
|
2842 planned, and IIIMF (Sun's Internet-Intranet Input Method Framework)
|
|
|
2843 support is extremely desirable. XIM is enabled at build time by use of
|
|
|
2844 the @samp{--with-xim} flag to @code{configure}. For use of XIM, see
|
|
|
2845 your platform documentation. However, normally the input method you use
|
|
|
2846 is specified via the @samp{LANG} and @samp{XMODIFIERS} environment
|
|
|
2847 variables.
|
|
|
2848
|
|
|
2849 Of course, input skills are portable across most applications. However,
|
|
|
2850 especially in modern GUI systems the habit of using bucky bits has
|
|
|
2851 fallen into sad disuse, and many XIM systems are poorly configured for
|
|
|
2852 use with Emacs. For example, the kinput2 input manager (a separate
|
|
|
2853 process providing an interface between Japanese dictionary servers such
|
|
|
2854 as Canna and Wnn, and the application) tends to gobble up keystrokes
|
|
|
2855 generating Meta characters. This means that to edit while using an XIM
|
|
|
2856 input method, you must toggle the input method off every time you want
|
|
|
2857 to use @kbd{M-f}. Your mileage may vary.
|
|
|
2858
|
|
|
2859 @emph{Library interfaces} are most common for Japanese, although Wnn
|
|
|
2860 supports Chinese (traditional and simplified) and Korean. There are
|
|
|
2861 Chinese and Korean input servers available, but we do not know of any
|
|
|
2862 patches for XEmacs to use them directly. You can use them via
|
|
|
2863 IM-enabled terminals, by manipulating the terminal coding systems. We
|
|
|
2864 describe only the Japanese-oriented systems here. The advantage of
|
|
|
2865 these systems is that they are very powerful, and on platforms where
|
|
|
2866 they are available there is typically a wide range of applications that
|
|
|
2867 support them. Thus your input skills are portable across applications.
|
|
|
2868
|
|
|
2869 Mule provides built-in interfaces to the following input methods: Wnn4,
|
|
|
2870 Wnn6, Canna, and SJ3. These can be configured at build time. There are
|
|
|
2871 patches available (no URL, sorry) to support the SKK server, as well.
|
|
|
2872 Wnn and SJ3 use the @code{egg} user interface. The interface for Canna
|
|
|
2873 is specialized to Canna.
|
|
428
|
2874
|
|
|
2875 Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
|
|
1135
|
2876 University. It is a powerful and complex system. Wnn4 is free and Wnn6
|
|
|
2877 is not. Wnn uses grammatical hints and probability of word association,
|
|
|
2878 so in principle Wnn can be cleverer than other methods.
|
|
|
2879
|
|
|
2880 Canna, made by NEC, supports only Japanese. It is a simple and powerful
|
|
|
2881 system. Canna uses only grammar, but its grammar and dictionary are
|
|
|
2882 quite sophisticated. So for standard modern Japanese, Canna seems
|
|
|
2883 cleverer than Wnn4. In addition, the UNIX version of Canna is free (now
|
|
|
2884 there is a Microsoft Windows version).
|
|
|
2885
|
|
|
2886 SJ3, by Sony, supports only Japanese.
|
|
428
|
2887
|
|
|
2888 Egg consists of following parts:
|
|
|
2889
|
|
|
2890 @enumerate
|
|
|
2891 @item
|
|
|
2892 Input character Translation System (ITS) layer.
|
|
|
2893 It translates ASCII inputs to Kana/PinYin/Hangul characters.
|
|
|
2894
|
|
|
2895 @item
|
|
|
2896 Kana/PinYin/Hangul to Kanji transfer layer.
|
|
1135
|
2897 The interface layer to network Kana-Kanji server (Wnn and Sj3).
|
|
428
|
2898 @end enumerate
|
|
|
2899
|
|
1135
|
2900 These input methods are modal. They have a raw (alphabet) mode, a
|
|
|
2901 phonetic input mode, and Kana-Kanji transfer mode. However there are
|
|
|
2902 mode-less input methods for Egg and Canna. @samp{boiled-egg} is a
|
|
|
2903 mode-less input method running on Egg. For Canna, @samp{canna.el} has a
|
|
|
2904 tiny boiled-egg-like command, @code{(canna-boil)}, and there are some
|
|
|
2905 boiled-egg-like utilities.
|
|
|
2906
|
|
|
2907 Much of this information was provided by @email{morioka@@jaist.ac.jp,
|
|
|
2908 MORIOKA Tomohiko}.
|
|
428
|
2909
|
|
2537
|
2910 @node Q1.8.6, Q1.8.7, Q1.8.5, Introduction
|
|
|
2911 @unnumberedsubsec Q1.8.6: How do I portably code for MULE/XEmacs?
|
|
428
|
2912
|
|
1135
|
2913 MULE has evolved rapidly over the last few years, and the original third
|
|
|
2914 party patch (for GNU Emacs 19), GNU Emacs 20+, and XEmacs 20+ have quite
|
|
|
2915 different implementations. The APIs also vary although recent versions
|
|
|
2916 of XEmacs have tended to converge to the GNU Emacs standard.
|
|
|
2917
|
|
|
2918 MULE implementations are going to continue to evolve. Both GNU Emacs
|
|
|
2919 and XEmacs are working hard on Unicode support, which will involve new
|
|
|
2920 APIs and probably variations on old ones. For XEmacs 22, the old ISO
|
|
|
2921 2022-based system for recognizing encodings will be replaced by a much
|
|
|
2922 more flexible system, which should improve accuracy of automatic coding
|
|
|
2923 detections, but will also involve new APIs.
|
|
|
2924
|
|
428
|
2925 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
|
|
|
2926
|
|
|
2927 @quotation
|
|
1135
|
2928 The application implementor must write separate code for these mule
|
|
|
2929 variants. [Please don't hesitate to report these variants to us; they
|
|
|
2930 are not, strictly speaking, bugs, but they give third-party developers
|
|
|
2931 the same kind of creepy-crawly feeling. We'll do what we can. -- Ed.]
|
|
428
|
2932
|
|
|
2933 MULE and the next version of Emacs are similar but the symbols are very
|
|
|
2934 different---requiring separate code as well.
|
|
|
2935
|
|
|
2936 Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of
|
|
|
2937 emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called
|
|
1135
|
2938 @code{emu} to provide a common interface. [There is an XEmacs package
|
|
|
2939 of APEL which provides much more comprehensive coverage. Be careful,
|
|
|
2940 however; APEL has problems of its own. -- Ed.]
|
|
428
|
2941
|
|
|
2942 I have the following suggestions about dealing with mule variants:
|
|
|
2943
|
|
|
2944 @itemize @bullet
|
|
|
2945 @item
|
|
|
2946 @code{(featurep 'mule)} @code{t} on all mule variants
|
|
|
2947
|
|
|
2948 @item
|
|
|
2949 @code{(boundp 'MULE)} is @code{t} on only MULE. Maybe the next version
|
|
|
2950 of Emacs will not have this symbol.
|
|
|
2951
|
|
|
2952 @item
|
|
|
2953 MULE has a variable @code{mule-version}. Perhaps the next version of
|
|
|
2954 Emacs will have this variable as well.
|
|
|
2955 @end itemize
|
|
|
2956
|
|
|
2957 Following is a sample to distinguish mule variants:
|
|
|
2958
|
|
|
2959 @lisp
|
|
|
2960 (if (featurep 'mule)
|
|
|
2961 (cond ((boundp 'MULE)
|
|
|
2962 ;; for original Mule
|
|
|
2963 )
|
|
440
|
2964 ((string-match "XEmacs" emacs-version)
|
|
|
2965 ;; for XEmacs with Mule
|
|
|
2966 )
|
|
|
2967 (t
|
|
|
2968 ;; for next version of Emacs
|
|
|
2969 ))
|
|
428
|
2970 ;; for old emacs variants
|
|
|
2971 )
|
|
|
2972 @end lisp
|
|
|
2973 @end quotation
|
|
|
2974
|
|
2537
|
2975 @node Q1.8.7, Q1.8.8, Q1.8.6, Introduction
|
|
|
2976 @unnumberedsubsec Q1.8.7: How about Cyrillic modes?
|
|
428
|
2977
|
|
|
2978 @email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes:
|
|
|
2979
|
|
|
2980 @quotation
|
|
|
2981 There is a cyrillic mode in the file @file{mysetup.zip} in
|
|
|
2982 @iftex
|
|
|
2983 @*
|
|
|
2984 @end iftex
|
|
|
2985 @uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}. This is a
|
|
|
2986 modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el}
|
|
|
2987 which can be obtained from
|
|
|
2988 @end quotation
|
|
|
2989
|
|
871
|
2990 @uref{http://www.math.uga.edu/~valery/russian.el}.
|
|
428
|
2991
|
|
|
2992 @email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes:
|
|
|
2993
|
|
|
2994 @quotation
|
|
|
2995 There is another cyrillic mode for both GNU Emacs and XEmacs by
|
|
|
2996 @email{manin@@camelot.mssm.edu, Dmitrii
|
|
|
2997 (Mitya) Manin} at
|
|
|
2998 @iftex
|
|
|
2999
|
|
|
3000 @end iftex
|
|
|
3001 @uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}.
|
|
|
3002 @c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead.
|
|
|
3003 @c Changed to russian host instead
|
|
|
3004 @end quotation
|
|
|
3005
|
|
|
3006 @email{rebecca.ore@@op.net, Rebecca Ore} writes:
|
|
|
3007
|
|
|
3008 @quotation
|
|
|
3009 The fullest resource I found on Russian language use (in and out of
|
|
661
|
3010 XEmacs) is @uref{http://www.ibiblio.org/sergei/Software/Software.html}
|
|
428
|
3011 @end quotation
|
|
|
3012
|
|
2537
|
3013 @node Q1.8.8, Q1.8.9, Q1.8.7, Introduction
|
|
|
3014 @unnumberedsubsec Q1.8.8: Does XEmacs support Unicode?
|
|
2417
|
3015
|
|
|
3016 To get Unicode support, you need a Mule-enabled XEmacs.
|
|
|
3017
|
|
|
3018 21.5 has internal support for Unicode and supports it fully, although we
|
|
|
3019 don't yet use it as the internal encoding.
|
|
|
3020
|
|
|
3021 21.4 supports Unicode partially -- as an external encoding for files,
|
|
2537
|
3022 processes, and terminals, but without font support. @xref{Q1.8.9, How
|
|
2417
|
3023 does XEmacs display Unicode?}. To get Unicode support in 21.4,
|
|
|
3024 install Mule-UCS from packages in the usual way, and put
|
|
745
|
3025
|
|
1616
|
3026 @example
|
|
745
|
3027 (require 'un-define)
|
|
|
3028 (set-coding-priority-list '(utf-8))
|
|
1616
|
3029 (set-coding-category-system 'utf-8 'utf-8)
|
|
|
3030 @end example
|
|
|
3031
|
|
|
3032 in your init file to enable the UTF-8 coding system. You may wish to
|
|
|
3033 view the documentation of @code{set-coding-priority-list} if you find
|
|
|
3034 that files that are not UTF-8 are being mis-recognized as UTF-8.
|
|
745
|
3035
|
|
2417
|
3036 Install standard national fonts (not Unicode fonts) for all character
|
|
2537
|
3037 sets you use. @xref{Q1.8.9, How does XEmacs display Unicode??}.
|
|
745
|
3038
|
|
|
3039 Mule-UCS also supports 16-bit forms of Unicode (UTF-16). It does not
|
|
|
3040 support 31-bit forms of Unicode (UTF-32 or UCS-4).
|
|
|
3041
|
|
2537
|
3042 @node Q1.8.9, , Q1.8.8, Introduction
|
|
|
3043 @unnumberedsubsec Q1.8.9: How does XEmacs display Unicode?
|
|
745
|
3044
|
|
|
3045 Mule doesn't have a Unicode charset internally, so there's nothing to
|
|
|
3046 bind a Unicode registry to. It would not be straightforward to create,
|
|
|
3047 either, because Unicode is not ISO 2022-compatible. You'd have to
|
|
|
3048 translate it to multiple 96x96 pages.
|
|
|
3049
|
|
|
3050 This means that Mule-UCS uses ordinary national fonts for display. This
|
|
|
3051 is not really a problem, except for those languages that use the Unified
|
|
|
3052 Han characters. The problem here is that Mule-UCS maps from Unicode
|
|
|
3053 code points to national character sets in a deterministic way. By
|
|
|
3054 default, this means that Japanese fonts are tried first, then Chinese,
|
|
|
3055 then Korean. To change the priority ordering, use the command
|
|
|
3056 `un-define-change-charset-order'.
|
|
|
3057
|
|
|
3058 It also means you can't use Unicode fonts directly, at least not without
|
|
|
3059 extreme hackery. You can run -nw with (set-terminal-coding-system
|
|
|
3060 'utf-8) if you really want a Unicode font for some reason.
|
|
|
3061
|
|
|
3062 Real Unicode support will be introduced in XEmacs 22.0.
|
|
|
3063
|
|
2459
|
3064 @node Installation, Editing, Introduction, Top
|
|
2417
|
3065 @unnumbered 2 Installation and Troubleshooting
|
|
428
|
3066
|
|
|
3067 This is part 2 of the XEmacs Frequently Asked Questions list. This
|
|
2417
|
3068 section is devoted to Installation, Maintenance and Troubleshooting.
|
|
428
|
3069
|
|
|
3070 @menu
|
|
2559
|
3071 2.0: Installation (General)
|
|
|
3072 * Q2.0.1:: How do I build and install XEmacs?
|
|
|
3073 * Q2.0.2:: Where do I find external libraries?
|
|
|
3074 * Q2.0.3:: How do I specify the paths that XEmacs uses for finding files?
|
|
|
3075 * Q2.0.4:: Running XEmacs without installing
|
|
|
3076 * Q2.0.5:: XEmacs is too big
|
|
|
3077
|
|
|
3078 2.1: Package Installation
|
|
|
3079 * Q2.1.1:: How do I install the packages?
|
|
|
3080 * Q2.1.2:: Can I install the packages individually?
|
|
|
3081 * Q2.1.3:: Can I install the packages automatically?
|
|
|
3082 * Q2.1.4:: Can I upgrade or remove packages?
|
|
|
3083 * Q2.1.5:: Which packages to install?
|
|
|
3084 * Q2.1.6:: Can you describe the package location process in more detail?
|
|
|
3085 * Q2.1.7:: EFS fails with "500 AUTH not understood"
|
|
|
3086
|
|
|
3087 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
|
3088 * Q2.2.1:: Libraries in non-standard locations
|
|
|
3089 * Q2.2.2:: Why can't I strip XEmacs?
|
|
|
3090
|
|
|
3091 2.3: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
3092 * Q2.3.1:: What exactly are all the different ways to build XEmacs under Windows?
|
|
|
3093 * Q2.3.2:: What compiler/libraries do I need to compile XEmacs?
|
|
|
3094 * Q2.3.3:: How do I compile the native port?
|
|
|
3095 * Q2.3.4:: What do I need for Cygwin?
|
|
|
3096 * Q2.3.5:: How do I compile under Cygwin?
|
|
|
3097 * Q2.3.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
|
3098 * Q2.3.7:: How do I compile with X support?
|
|
|
3099 * Q2.3.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
|
3100
|
|
|
3101 2.4: General Troubleshooting
|
|
|
3102 * Q2.4.1:: How do I deal with bugs or with problems building, installing, or running?
|
|
|
3103 * Q2.4.2:: Help! XEmacs just crashed on me!
|
|
|
3104 * Q2.4.3:: XEmacs crashes and I compiled it myself.
|
|
|
3105 * Q2.4.4:: How to debug an XEmacs problem with a debugger
|
|
|
3106 * Q2.4.5:: I get a cryptic error message when trying to do something.
|
|
|
3107 * Q2.4.6:: XEmacs hangs when I try to do something.
|
|
|
3108 * Q2.4.7:: I get an error message when XEmacs is running in batch mode.
|
|
|
3109 * Q2.4.8:: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
|
3110 * Q2.4.9:: @kbd{C-g} doesn't work for me. Is it broken?
|
|
|
3111 * Q2.4.10:: How do I debug process-related problems?
|
|
|
3112 * Q2.4.11:: XEmacs is outputting lots of X errors.
|
|
|
3113 * Q2.4.12:: After upgrading, XEmacs won't do `foo' any more!
|
|
|
3114
|
|
|
3115 2.5: Startup-Related Problems
|
|
|
3116 * Q2.5.1:: XEmacs cannot connect to my X Terminal!
|
|
|
3117 * Q2.5.2:: Startup problems related to paths or package locations.
|
|
|
3118 * Q2.5.3:: XEmacs won't start without network.
|
|
|
3119 * Q2.5.4:: Startup warnings about deducing proper fonts?
|
|
|
3120 * Q2.5.5:: Warnings from incorrect key modifiers.
|
|
|
3121 * Q2.5.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
428
|
3122 @end menu
|
|
|
3123
|
|
2559
|
3124 @unnumberedsec 2.0: Installation (General)
|
|
2417
|
3125
|
|
428
|
3126 @node Q2.0.1, Q2.0.2, Installation, Installation
|
|
2559
|
3127 @unnumberedsubsec Q2.0.1: How do I build and install XEmacs?
|
|
|
3128
|
|
|
3129 See the file @file{etc/NEWS} for information on new features and other
|
|
|
3130 user-visible changes since the last version of XEmacs.
|
|
|
3131
|
|
|
3132 The file @file{INSTALL} in the top-level directory says how to bring
|
|
|
3133 up XEmacs on Unix and Cygwin, once you have loaded the entire subtree
|
|
|
3134 of this directory.
|
|
|
3135
|
|
|
3136 See the file @file{nt/README} for instructions on building XEmacs for
|
|
|
3137 Microsoft Windows.
|
|
|
3138
|
|
|
3139 @xref{Q2.1.1}, for the installation of (essential) add on packages.
|
|
2417
|
3140
|
|
|
3141 @node Q2.0.2, Q2.0.3, Q2.0.1, Installation
|
|
2559
|
3142 @unnumberedsubsec Q2.0.2: Where do I find external libraries?
|
|
2417
|
3143
|
|
2459
|
3144 All external libraries used by XEmacs can be found on the XEmacs web
|
|
2417
|
3145 site
|
|
|
3146 @iftex
|
|
|
3147 @*
|
|
|
3148 @end iftex
|
|
2459
|
3149 @uref{http://www.xemacs.org/Download/optLibs.html}.
|
|
2417
|
3150
|
|
|
3151 The library versions available here are known to work with XEmacs.
|
|
|
3152 (Newer versions will probably work as well but we can't guarantee it.)
|
|
|
3153 We try to keep the libraries up-to-date but may not always succeed.
|
|
2459
|
3154 Check the above page for the canonical locations of the external libraries,
|
|
|
3155 allowing you to download the latest, bleeding-edge versions.
|
|
2417
|
3156
|
|
2559
|
3157 @node Q2.0.3, Q2.0.4, Q2.0.2, Installation
|
|
|
3158 @unnumberedsubsec Q2.0.3: How do I specify the paths that XEmacs uses for finding files?
|
|
2417
|
3159
|
|
|
3160 You can specify what paths to use by using a number of different flags
|
|
|
3161 when running configure. See the section MAKE VARIABLES in the top-level
|
|
|
3162 file INSTALL in the XEmacs distribution for a listing of those flags.
|
|
|
3163
|
|
|
3164 Most of the time, however, the simplest fix is: @strong{do not} specify
|
|
|
3165 paths as you might for GNU Emacs. XEmacs can generally determine the
|
|
|
3166 necessary paths dynamically at run time. The only path that generally
|
|
|
3167 needs to be specified is the root directory to install into. That can
|
|
|
3168 be specified by passing the @code{--prefix} flag to configure. For a
|
|
|
3169 description of the XEmacs install tree, please consult the @file{NEWS}
|
|
|
3170 file.
|
|
|
3171
|
|
2559
|
3172 @node Q2.0.4, Q2.0.5, Q2.0.3, Installation
|
|
|
3173 @unnumberedsubsec Q2.0.4: Running XEmacs without installing
|
|
442
|
3174
|
|
|
3175 How can I just try XEmacs without installing it?
|
|
428
|
3176
|
|
|
3177 XEmacs will run in place without requiring installation and copying of
|
|
|
3178 the Lisp directories, and without having to specify a special build-time
|
|
|
3179 flag. It's the copying of the Lisp directories that requires so much
|
|
|
3180 space. XEmacs is largely written in Lisp.
|
|
|
3181
|
|
|
3182 A good method is to make a shell alias for xemacs:
|
|
|
3183
|
|
|
3184 @example
|
|
2459
|
3185 alias xemacs=/src/xemacs-21.5/src/xemacs
|
|
428
|
3186 @end example
|
|
|
3187
|
|
|
3188 (You will obviously use whatever directory you downloaded the source
|
|
2459
|
3189 tree to instead of @file{/src/xemacs-21.5}).
|
|
428
|
3190
|
|
|
3191 This will let you run XEmacs without massive copying.
|
|
|
3192
|
|
2559
|
3193 @node Q2.0.5, Q2.1.1, Q2.0.4, Installation
|
|
|
3194 @unnumberedsubsec Q2.0.5: XEmacs is too big
|
|
428
|
3195
|
|
442
|
3196 The space required by the installation directories can be
|
|
428
|
3197 reduced dramatically if desired. Gzip all the .el files. Remove all
|
|
442
|
3198 the packages you'll never want to use. Remove the TexInfo manuals.
|
|
428
|
3199 Remove the Info (and use just hardcopy versions of the manual). Remove
|
|
|
3200 most of the stuff in etc. Remove or gzip all the source code. Gzip or
|
|
|
3201 remove the C source code. Configure it so that copies are not made of
|
|
1138
|
3202 the support lisp.
|
|
428
|
3203
|
|
|
3204 These are all Emacs Lisp source code and bytecompiled object code. You
|
|
|
3205 may safely gzip everything named *.el here. You may remove any package
|
|
|
3206 you don't use. @emph{Nothing bad will happen if you delete a package
|
|
|
3207 that you do not use}. You must be sure you do not use it though, so be
|
|
|
3208 conservative at first.
|
|
|
3209
|
|
1648
|
3210 Any package with the possible exceptions of xemacs-base, and EFS are
|
|
|
3211 candidates for removal. Ask yourself, @emph{Do I ever want to use this
|
|
|
3212 package?} If the answer is no, then it is a candidate for removal.
|
|
428
|
3213
|
|
|
3214 First, gzip all the .el files. Then go about package by package and
|
|
|
3215 start gzipping the .elc files. Then run XEmacs and do whatever it is
|
|
1648
|
3216 you normally do. If nothing bad happens, then remove the package. You
|
|
|
3217 can remove a package via the PUI interface
|
|
|
3218 (@code{M-x pui-list-packages}, then press @kbd{d} to mark the packages
|
|
|
3219 you wish to delete, and then @kbd{x} to delete them.
|
|
|
3220
|
|
|
3221 Another method is to do @code{M-x package-get-delete-package}.
|
|
428
|
3222
|
|
2559
|
3223 @unnumberedsec 2.1: Package Installation
|
|
|
3224
|
|
|
3225 @node Q2.1.1, Q2.1.2, Q2.0.5, Installation
|
|
|
3226 @unnumberedsubsec Q2.1.1: How do I install the packages?
|
|
|
3227
|
|
|
3228 There are three ways to install the packages.
|
|
|
3229
|
|
|
3230 @enumerate
|
|
|
3231 @item
|
|
|
3232 Manually, all at once, using the 'Sumo Tarball'.
|
|
|
3233 @item
|
|
|
3234 Manually, using individual package tarballs.
|
|
|
3235 @item
|
|
|
3236 Automatically, using the package tools from XEmacs.
|
|
|
3237 @end enumerate
|
|
|
3238
|
|
|
3239 If you don't want to mess with the packages, it is easiest to just
|
|
|
3240 grab them manually, all at once. (For the other two ways,
|
|
|
3241 @xref{Q2.1.2}, and @xref{Q2.1.3}.) Download the file
|
|
|
3242
|
|
|
3243 @file{xemacs-sumo.tar.gz}
|
|
|
3244
|
|
|
3245 For an XEmacs compiled with Mule you also need
|
|
|
3246
|
|
|
3247 @file{xemacs-mule-sumo.tar.gz}
|
|
|
3248
|
|
|
3249 These are in the @file{packages} directory on your XEmacs mirror
|
|
|
3250 archive: @uref{ftp://ftp.xemacs.org/pub/xemacs/packages} or its
|
|
|
3251 mirrors. N.B. They are called 'Sumo Tarballs' for good reason. They
|
|
|
3252 are currently about 19MB and 4.5MB (gzipped) respectively.
|
|
|
3253
|
|
|
3254 Install them on Unix and Mac OS X using the shell/Terminal command
|
|
|
3255
|
|
|
3256 @code{cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xf -}
|
|
|
3257
|
|
|
3258 Where @samp{$prefix} is what you gave to the @samp{--prefix} flag to
|
|
|
3259 @file{configure}, and defaults to @file{/usr/local}.
|
|
|
3260
|
|
|
3261 If you have GNU tar you can use:
|
|
|
3262
|
|
|
3263 @code{cd $prefix/lib/xemacs ; tar zxvf <tarballname>}
|
|
|
3264
|
|
|
3265 If you have the packages somewhere nonstandard and don't want to
|
|
|
3266 bother with @samp{$prefix} (for example, you're a developer and are
|
|
|
3267 compiling the packages yourself, and want your own private copy of
|
|
|
3268 everything), you can also directly specify this using @file{configure}.
|
|
|
3269 To do this under 21.5 and above use the @samp{--package-prefix} parameter
|
|
|
3270 to specify the directory under which you untarred the above tarballs.
|
|
|
3271 Under 21.4 and previous you need to use @samp{--package-path},
|
|
|
3272 something like this:
|
|
|
3273
|
|
|
3274 @example
|
|
|
3275 configure --package-path="~/.xemacs::/src/xemacs/site-packages:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages" ...
|
|
|
3276 @end example
|
|
|
3277
|
|
|
3278 Under Windows, you need to place the above @samp{tar.gz} files in the
|
|
|
3279 directory specified using the @samp{PACKAGE_PREFIX} value in
|
|
|
3280 @file{nt/config.inc} and by default is @file{\Program Files\XEmacs}.
|
|
|
3281 (To untar a @samp{tar.gz} file you will need to use a utility such as
|
|
|
3282 WinZip, unless you have Cygwin or a similar environment installed, in
|
|
|
3283 which case the above Unix shell command should work fine.) If you want
|
|
|
3284 the packages somewhere else, just change @samp{PACKAGE_PREFIX}.
|
|
|
3285
|
|
|
3286 Note that XEmacs finds the packages automatically anywhere underneath
|
|
|
3287 the directory tree where it expects to find the packages. All you
|
|
|
3288 need to do is put stuff there; you don't need to run any program to
|
|
|
3289 tell XEmacs to find the packges, or do anything of that sort.
|
|
|
3290
|
|
|
3291 However, XEmacs will only notice newly installed packages when it
|
|
|
3292 starts up, so you will have to restart if you are already running
|
|
|
3293 XEmacs.
|
|
|
3294
|
|
|
3295 For more details, @xref{Startup Paths,,,xemacs, the XEmacs User's
|
|
|
3296 Manual}, and @xref{Packages,,,xemacs, the XEmacs User's Manual}.
|
|
|
3297
|
|
|
3298 As the Sumo tarballs are not regenerated as often as the individual
|
|
|
3299 packages, it is recommended that you use the automatic package tools
|
|
|
3300 afterwards to pick up any recent updates.
|
|
|
3301
|
|
|
3302 @emph{NOTE}: For detailed information about how the package
|
|
|
3303 hierarchies work, @xref{Package Overview,,,lispref, the XEmacs Lisp
|
|
|
3304 Reference Manual}.
|
|
|
3305
|
|
|
3306 @node Q2.1.2, Q2.1.3, Q2.1.1, Installation
|
|
|
3307 @unnumberedsubsec Q2.1.2: Can I install the packages individually?
|
|
|
3308
|
|
|
3309 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.
|
|
|
3310
|
|
|
3311 Note: If you are upgrading packages already installed, it's best to
|
|
|
3312 remove the old package first (@pxref{Q2.1.4}).
|
|
|
3313
|
|
|
3314 For example if we are installing the @samp{xemacs-base}
|
|
|
3315 package (version 1.48):
|
|
|
3316
|
|
|
3317 @example
|
|
|
3318 mkdir $prefix/lib/xemacs/xemacs-packages RET # if it does not exist yet
|
|
|
3319 cd $prefix/lib/xemacs/xemacs-packages RET
|
|
|
3320 gunzip -c /path/to/xemacs-base-1.48-pkg.tar.gz | tar xvf - RET
|
|
|
3321 @end example
|
|
|
3322
|
|
|
3323 Or if you have GNU tar, the last step can be:
|
|
|
3324
|
|
|
3325 @example
|
|
|
3326 tar zxvf /path/to/xemacs-base-1.48-pkg.tar.gz RET
|
|
|
3327 @end example
|
|
|
3328
|
|
|
3329 For MULE related packages, it is best to untar into the @samp{mule-packages}
|
|
|
3330 hierarchy, i.e. for the @samp{mule-base} package, version 1.37:
|
|
|
3331
|
|
|
3332 @example
|
|
|
3333 mkdir $prefix/lib/xemacs/mule-packages RET # if it does not exist yet
|
|
|
3334 cd $prefix/lib/xemacs/mule-packages RET
|
|
|
3335 gunzip -c /path/to/mule-base-1.37-pkg.tar.gz | tar xvf - RET
|
|
|
3336 @end example
|
|
|
3337
|
|
|
3338 Or if you have GNU tar, the last step can be:
|
|
|
3339
|
|
|
3340 @example
|
|
|
3341 tar zxvf /path/to/mule-base-1.37-pkg.tar.gz RET
|
|
|
3342 @end example
|
|
|
3343
|
|
|
3344 @node Q2.1.3, Q2.1.4, Q2.1.2, Installation
|
|
|
3345 @unnumberedsubsec Q2.1.3: Can I install the packages automatically?
|
|
|
3346
|
|
|
3347 XEmacs comes with some tools to make the periodic updating and
|
|
|
3348 installing easier. It will notice if new packages or versions are
|
|
|
3349 available and will fetch them from the FTP site.
|
|
|
3350
|
|
|
3351 Unfortunately this requires that a few packages are already in place.
|
|
|
3352 You will have to install them by hand as above or use a SUMO tarball.
|
|
|
3353 This requirement will hopefully go away in the future. The packages
|
|
|
3354 you need are:
|
|
|
3355
|
|
|
3356 @example
|
|
|
3357 efs - To fetch the files from the FTP site or mirrors.
|
|
|
3358 xemacs-base - Needed by efs.
|
|
|
3359 @end example
|
|
|
3360
|
|
|
3361 and optionally:
|
|
|
3362
|
|
|
3363 @example
|
|
|
3364 mailcrypt - For PGP verification of the package-index file.
|
|
|
3365 @end example
|
|
|
3366
|
|
|
3367 After installing these by hand, fire up XEmacs and follow these
|
|
|
3368 steps.
|
|
|
3369
|
|
|
3370 @enumerate
|
|
|
3371 @item
|
|
|
3372 Choose a download site.
|
|
|
3373 @itemize @bullet
|
|
|
3374 @item
|
|
|
3375 via menu: Tools -> Packages -> Set Download Site
|
|
|
3376 @item
|
|
|
3377 via keyb: M-x customize-variable RET package-get-remote RET
|
|
|
3378 (put in the details of remote host and directory)
|
|
|
3379 @end itemize
|
|
|
3380
|
|
|
3381 If the package tarballs _AND_ the package-index file are in a
|
|
|
3382 local directory, you can: M-x pui-set-local-package-get-directory RET
|
|
|
3383
|
|
|
3384 @item
|
|
|
3385 Obtain a list of packages and display the list in a buffer named
|
|
|
3386 "*Packages*".
|
|
|
3387 @itemize @bullet
|
|
|
3388 @item
|
|
|
3389 menu: Tools -> Packages -> List & Install
|
|
|
3390 @item
|
|
|
3391 keyb: M-x pui-list-packages RET
|
|
|
3392 @end itemize
|
|
|
3393
|
|
|
3394 XEmacs will now connect to the remote site and download the
|
|
|
3395 latest package-index file.
|
|
|
3396
|
|
|
3397 The resulting buffer, "*Packages*" has brief instructions at the
|
|
|
3398 end of the buffer.
|
|
|
3399
|
|
|
3400 @item
|
|
|
3401 Choose the packages you wish to install.
|
|
|
3402 @itemize @bullet
|
|
|
3403 @item
|
|
|
3404 mouse: Click button 2 on the package name.
|
|
|
3405 @item
|
|
|
3406 keyb: RET on the package name
|
|
|
3407 @end itemize
|
|
|
3408
|
|
|
3409 @item
|
|
|
3410 Make sure you have everything you need.
|
|
|
3411 @itemize @bullet
|
|
|
3412 @item
|
|
|
3413 menu: Packages -> Add Required
|
|
|
3414 @item
|
|
|
3415 keyb: r
|
|
|
3416 @end itemize
|
|
|
3417
|
|
|
3418 XEmacs will now search for packages that are required by the
|
|
|
3419 ones that you have chosen to install and offer to select
|
|
|
3420 those packages also.
|
|
|
3421
|
|
|
3422 For novices and gurus alike, this step can save your bacon.
|
|
|
3423 It's easy to forget to install a critical package.
|
|
|
3424
|
|
|
3425 @item
|
|
|
3426 Download and install the packages.
|
|
|
3427 @itemize @bullet
|
|
|
3428 @item
|
|
|
3429 menu: Packages -> Install/Remove Selected
|
|
|
3430 @item
|
|
|
3431 keyb: x
|
|
|
3432 @end itemize
|
|
|
3433 @end enumerate
|
|
|
3434
|
|
|
3435 @node Q2.1.4, Q2.1.5, Q2.1.3, Installation
|
|
|
3436 @unnumberedsubsec Q2.1.4: Can I upgrade or remove packages?
|
|
|
3437
|
|
|
3438 As the exact files and their locations contained in a package may
|
|
|
3439 change it is recommended to remove a package first before installing a
|
|
|
3440 new version. In order to facilitate removal each package contains an
|
|
|
3441 pgkinfo/MANIFEST.pkgname file which list all the files belong to the
|
|
|
3442 package. M-x package-admin-delete-binary-package RET can be used to
|
|
|
3443 remove a package using this file.
|
|
|
3444
|
|
|
3445 Note that the interactive package tools included with XEmacs already do
|
|
|
3446 this for you.
|
|
|
3447
|
|
|
3448 @node Q2.1.5, Q2.1.6, Q2.1.4, Installation
|
|
|
3449 @unnumberedsubsec Q2.1.5: Which packages to install?
|
|
|
3450
|
|
|
3451 Unless you are an advanced user, just install everything.
|
|
|
3452
|
|
|
3453 If you really want to install only what's absolutely needed, a good
|
|
|
3454 minimal set of packages for XEmacs-latin1 would be
|
|
|
3455
|
|
|
3456 @example
|
|
|
3457 xemacs-base, xemacs-devel, c-support, cc-mode, debug, dired, efs,
|
|
|
3458 edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes,
|
|
|
3459 text-modes, time, mailcrypt
|
|
|
3460 @end example
|
|
|
3461
|
|
|
3462 If you are using the XEmacs package tools, don't forget to do:
|
|
|
3463
|
|
|
3464 @example
|
|
|
3465 Packages -> Add Required
|
|
|
3466 @end example
|
|
|
3467
|
|
|
3468 To make sure you have everything that the packages you have chosen to
|
|
|
3469 install need.
|
|
|
3470
|
|
|
3471 @xref{Q1.7.2}, for a description of the various packages.
|
|
|
3472
|
|
|
3473 @node Q2.1.6, Q2.1.7, Q2.1.5, Installation
|
|
|
3474 @unnumberedsubsec Q2.1.6: Can you describe the package location process in more detail?
|
|
|
3475
|
|
|
3476 On startup XEmacs looks for packages in so-called package hierarchies.
|
|
|
3477 Normally, there are three system wide hierarchies, like this:
|
|
|
3478
|
|
|
3479 @example
|
|
|
3480 $prefix/lib/xemacs/xemacs-packages/
|
|
|
3481 Normal packages go here.
|
|
|
3482
|
|
|
3483 $prefix/lib/xemacs/mule-packages/
|
|
|
3484 Mule packages go here and are only searched by MULE-enabled XEmacsen.
|
|
|
3485
|
|
|
3486 $prefix/lib/xemacs/site-packages/
|
|
|
3487 Local and 3rd party packages go here.
|
|
|
3488 @end example
|
|
|
3489
|
|
|
3490 This is what you get when you untar the SUMO tarballs under
|
|
|
3491 @file{$prefix/lib/xemacs}.
|
|
|
3492
|
|
|
3493 @file{$prefix} is specified using the @samp{--prefix} parameter to
|
|
|
3494 @file{configure}, and defaults to @file{usr/local}.
|
|
|
3495
|
|
|
3496 If the package path is not explicitly specified, XEmacs looks for the
|
|
|
3497 package directory @file{xemacs-packages} (and @file{mule-packages} and
|
|
|
3498 @file{site-packages}) first under @samp{~/.xemacs}, then for a sister
|
|
|
3499 directory @file{lib/xemacs-VERSION} of the directory in which the
|
|
|
3500 XEmacs executable is located, then for a sister directory
|
|
|
3501 @file{lib/xemacs}. The XEmacs executable (under Unix at least) is
|
|
|
3502 installed by default in @file{/usr/local/bin}; this explains why
|
|
|
3503 XEmacs in its default installation will find packages that you put
|
|
|
3504 under @file{/usr/local/lib/xemacs}.
|
|
|
3505
|
|
|
3506 You can specify where exactly XEmacs looks for packages by using the
|
|
|
3507 @samp{--package-prefix} or @samp{--package-path} parameters to
|
|
|
3508 @file{configure} (or the equivalent settings in @file{config.inc},
|
|
|
3509 under Windows), or setting the @samp{EMACSPACKAGEPATH} environment
|
|
|
3510 variable (which has the same format as @samp{--package-path}).
|
|
|
3511 @xref{Q2.1.1}.
|
|
|
3512
|
|
|
3513 See @file{configure.usage} for more info about the format of these
|
|
|
3514 @file{configure} parameters.
|
|
|
3515
|
|
|
3516 In addition to the system wide packages, each user can have his own
|
|
|
3517 packages installed under @file{~/.xemacs/}. If you want to install
|
|
|
3518 packages there using the interactive tools, you need to set
|
|
|
3519 @code{package-get-install-to-user-init-directory} to @code{t}.
|
|
|
3520
|
|
|
3521 The site-packages hierarchy replaces the old @file{site-lisp}
|
|
|
3522 directory. XEmacs no longer looks into a @file{site-lisp} directly by
|
|
|
3523 default. A good place to put @file{site-start.el} would be in
|
|
|
3524 @file{$prefix/lib/xemacs/site-packages/lisp/}.
|
|
|
3525
|
|
|
3526 @node Q2.1.7, Q2.2.1, Q2.1.6, Installation
|
|
|
3527 @unnumberedsubsec Q2.1.7: EFS fails with "500 AUTH not understood" (NEW)
|
|
2417
|
3528
|
|
|
3529 A typical error: FTP Error: USER request failed; 500 AUTH not understood.
|
|
|
3530
|
|
|
3531 Thanks to giacomo boffi @email{giacomo.boffi@@polimi.it} who recommends
|
|
|
3532 on comp.emacs.xemacs:
|
|
|
3533
|
|
|
3534 tell your ftp client to not attempt AUTH authentication (or do not
|
|
|
3535 use FTP servers that don't understand AUTH)
|
|
|
3536
|
|
|
3537 and notes that you need to add an element (often "-u") to
|
|
|
3538 `efs-ftp-program-args'. Use M-x customize-variable, and verify the
|
|
|
3539 needed flag with `man ftp' or other local documentation.
|
|
|
3540
|
|
2559
|
3541 @unnumberedsec 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
|
3542
|
|
|
3543 @node Q2.2.1, Q2.2.2, Q2.1.7, Installation
|
|
|
3544 @unnumberedsubsec Q2.2.1: Libraries in non-standard locations
|
|
428
|
3545
|
|
2459
|
3546 If your libraries are in a non-standard location, you can specify the location
|
|
|
3547 using the following flags to @file{configure}:
|
|
|
3548
|
|
|
3549 @example
|
|
|
3550 --site-libraries=WHATEVER
|
|
|
3551 --site-includes=WHATEVER
|
|
|
3552 @end example
|
|
|
3553
|
|
|
3554 If you have multiple paths to specify, use the following syntax:
|
|
428
|
3555
|
|
|
3556 @example
|
|
|
3557 --site-libraries='/path/one /path/two /path/etc'
|
|
|
3558 @end example
|
|
|
3559
|
|
2559
|
3560 @node Q2.2.2, Q2.3.1, Q2.2.1, Installation
|
|
|
3561 @unnumberedsubsec Q2.2.2: Why can't I strip XEmacs?
|
|
428
|
3562
|
|
|
3563 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:
|
|
|
3564
|
|
|
3565 @quotation
|
|
|
3566 Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The
|
|
|
3567 link gives you a bare-boned emacs (called temacs). temacs is then run,
|
|
|
3568 preloading some of the lisp files. The result is then dumped into a new
|
|
|
3569 executable, named xemacs, which will contain all of the preloaded lisp
|
|
|
3570 functions and data.
|
|
|
3571
|
|
|
3572 Now, during the dump itself, the executable (code+data+symbols) is
|
|
|
3573 written on disk using a special unexec() function. This function is
|
|
|
3574 obviously heavily system dependent. And on some systems, it leads to an
|
|
|
3575 executable which, although valid, cannot be stripped without damage. If
|
|
|
3576 memory serves, this is especially the case for AIX binaries. On other
|
|
462
|
3577 architectures it might work OK.
|
|
428
|
3578
|
|
|
3579 The Right Way to strip the emacs binary is to strip temacs prior to
|
|
|
3580 dumping xemacs. This will always work, although you can do that only if
|
|
|
3581 you install from sources (as temacs is @file{not} part of the binary
|
|
|
3582 kits).
|
|
|
3583 @end quotation
|
|
|
3584
|
|
|
3585 @email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes:
|
|
|
3586
|
|
|
3587 @quotation
|
|
|
3588 Here is the trick:
|
|
|
3589
|
|
|
3590 @enumerate
|
|
|
3591 @item
|
|
|
3592 [ ./configure; make ]
|
|
|
3593
|
|
|
3594 @item
|
|
|
3595 rm src/xemacs
|
|
|
3596
|
|
|
3597 @item
|
|
|
3598 strip src/temacs
|
|
|
3599
|
|
|
3600 @item
|
|
|
3601 make
|
|
|
3602
|
|
|
3603 @item
|
|
|
3604 cp src/xemacs /usr/local/bin/xemacs
|
|
|
3605
|
|
|
3606 @item
|
|
|
3607 cp lib-src/DOC-19.16-XEmacs
|
|
|
3608 @iftex
|
|
|
3609 \ @*
|
|
|
3610 @end iftex
|
|
|
3611 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
|
|
|
3612 @end enumerate
|
|
|
3613 @end quotation
|
|
|
3614
|
|
2559
|
3615 @unnumberedsec 2.3: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
3616
|
|
|
3617 @node Q2.3.1, Q2.3.2, Q2.2.2, Installation
|
|
|
3618 @unnumberedsubsec Q2.3.1: What exactly are all the different ways to build XEmacs under Windows?
|
|
2417
|
3619
|
|
|
3620 XEmacs can be built in several ways in the MS Windows environment.
|
|
|
3621
|
|
|
3622 The standard way is what we call the "native" port. It uses the Win32
|
|
|
3623 API and has no connection with X whatsoever -- it does not require X
|
|
|
3624 libraries to build, nor does it require an X server to run. The native
|
|
|
3625 port is the most reliable version and provides the best graphical
|
|
|
3626 support. Almost all development is geared towards this version, and
|
|
|
3627 there is little reason not to use it.
|
|
|
3628
|
|
|
3629 The second way to build is the Cygwin port. It takes advantage of
|
|
2537
|
3630 Cygnus emulation library under Win32. @xref{Q1.2.5, What are Cygwin
|
|
2417
|
3631 and MinGW, and do I need them to run XEmacs?}, for more information.
|
|
|
3632
|
|
|
3633 A third way is the MinGW port. It uses the Cygwin environment to
|
|
2537
|
3634 build but does not require it at runtime. @xref{Q1.2.5, What are
|
|
2417
|
3635 Cygwin and MinGW, and do I need them to run XEmacs?}, for more
|
|
|
3636 information.
|
|
|
3637
|
|
|
3638 Finally, you might also be able to build the non-Cygwin, non-MinGW "X"
|
|
|
3639 port. This was actually the first version of XEmacs that ran under MS
|
|
|
3640 Windows, and although the code is still in XEmacs, it's essentially
|
|
|
3641 orphaned and it's unlikely it will compile without a lot of work. If
|
|
|
3642 you want an MS Windows versin of XEmacs that supports X, use the Cygwin
|
|
|
3643 version. (The X support there is actively maintained, so that Windows
|
|
|
3644 developers can test the X support in XEmacs.)
|
|
|
3645
|
|
2559
|
3646 @node Q2.3.2, Q2.3.3, Q2.3.1, Installation
|
|
|
3647 @unnumberedsubsec Q2.3.2: What compiler/libraries do I need to compile XEmacs?
|
|
2417
|
3648
|
|
|
3649 You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have
|
|
|
3650 some beta testers currently trying to compile with VC.NET, aka version
|
|
|
3651 7.0, but we can't yet report complete success.) For the Cygwin and
|
|
|
3652 MinGW versions, you need the Cygwin environment, which comes with GCC,
|
|
2537
|
3653 the compiler used for those versions. @xref{Q1.2.5, What are Cygwin
|
|
2417
|
3654 and MinGW, and do I need them to run XEmacs?}, for more information on
|
|
|
3655 Cygwin and MinGW.
|
|
|
3656
|
|
2559
|
3657 @node Q2.3.3, Q2.3.4, Q2.3.2, Installation
|
|
|
3658 @unnumberedsubsec Q2.3.3: How do I compile the native port?
|
|
2417
|
3659
|
|
|
3660 Please read the file @file{nt/README} in the XEmacs distribution, which
|
|
|
3661 contains the full description.
|
|
|
3662
|
|
2559
|
3663 @node Q2.3.4, Q2.3.5, Q2.3.3, Installation
|
|
|
3664 @unnumberedsubsec Q2.3.4: What do I need for Cygwin?
|
|
2417
|
3665
|
|
|
3666 You can find the Cygwin tools and compiler at:
|
|
|
3667
|
|
|
3668 @uref{http://www.cygwin.com/}
|
|
|
3669
|
|
|
3670 Click on the @samp{Install or update now!} link, which will download a
|
|
|
3671 file @file{setup.exe}, which you can use to download everything
|
|
|
3672 else. (You will need to pick a mirror site; @samp{mirrors.rcn.net} is
|
|
|
3673 probably the best.) You should go ahead and install everything --
|
|
|
3674 you'll get various ancillary libraries that XEmacs needs or likes,
|
|
|
3675 e.g. XPM, PNG, JPEG, TIFF, etc. You can also get X Windows here, if you
|
|
|
3676 want to compile under X.
|
|
|
3677
|
|
|
3678 If you want to compile without X, you will need the @file{xpm-nox}
|
|
|
3679 library, which must be specifically selected in the Cygwin netinstaller;
|
|
|
3680 it is not selected by default. The package has had various names.
|
|
|
3681 Currently it is called @file{cygXpm-noX4.dll}.
|
|
|
3682
|
|
2559
|
3683 @node Q2.3.5, Q2.3.6, Q2.3.4, Installation
|
|
|
3684 @unnumberedsubsec Q2.3.5: How do I compile under Cygwin?
|
|
2417
|
3685
|
|
|
3686 Similar as on Unix; use the usual `configure' and `make' process.
|
|
|
3687 Some problems to watch out for:
|
|
|
3688
|
|
|
3689 @itemize @bullet
|
|
|
3690 @item
|
|
|
3691 make sure HOME is set. This controls where you
|
|
|
3692 @file{init.el} file comes from;
|
|
|
3693
|
|
|
3694 @item
|
|
|
3695 @samp{CYGWIN} needs to be set to @samp{tty} for process support to work;
|
|
|
3696
|
|
|
3697 @item
|
|
|
3698 picking up some other grep or other UNIX-like tools can kill configure;
|
|
|
3699
|
|
|
3700 @item
|
|
|
3701 static heap too small, adjust @file{src/sheap-adjust.h} to a more positive
|
|
|
3702 number;
|
|
|
3703
|
|
|
3704 @item
|
|
|
3705 (Unconfirmed) The Cygwin version doesn't understand
|
|
|
3706 @file{//machine/path} type paths so you will need to manually mount a
|
|
|
3707 directory of this form under a unix style directory for a build to work
|
|
|
3708 on the directory;
|
|
|
3709
|
|
|
3710 @item
|
|
|
3711 If you're building @strong{WITHOUT} X11, don't forget to change symlinks
|
|
|
3712 @file{/usr/lib/libXpm.a} and @file{/usr/lib/libXpm.dll.a} to point to
|
|
|
3713 the non-X versions of these libraries. By default they point to the X
|
|
|
3714 versions. So:
|
|
|
3715
|
|
|
3716 @example
|
|
|
3717 /usr/lib/libXpm.a -> /usr/lib/libXpm-noX.a
|
|
|
3718 /usr/lib/libXpm.dll.a -> /usr/lib/libXpm-noX.dll.a
|
|
|
3719 @end example
|
|
|
3720
|
|
|
3721 (This advice may now be obsolete because of the availability of the
|
|
|
3722 cygXpm-noX4.dll package from Cygwin. Send confirmation to
|
|
|
3723 @email{faq@@xemacs.org}.)
|
|
|
3724
|
|
|
3725 @item
|
|
|
3726 Other problems are listed in the @file{PROBLEMS} file, in the top-level
|
|
|
3727 directory of the XEmacs sources.
|
|
|
3728
|
|
|
3729 @end itemize
|
|
|
3730
|
|
|
3731
|
|
2559
|
3732 @node Q2.3.6, Q2.3.7, Q2.3.5, Installation
|
|
|
3733 @unnumberedsubsec Q2.3.6: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
2417
|
3734
|
|
|
3735 Similar to the method for Unix. Things to remember:
|
|
|
3736
|
|
|
3737 @itemize @bullet
|
|
|
3738 @item
|
|
|
3739 Specify the target host on the command line for @file{./configure}, e.g.
|
|
|
3740 @samp{./configure i586-pc-mingw32}.
|
|
|
3741
|
|
|
3742 @item
|
|
|
3743 Be sure that your build directory is mounted such that it has the
|
|
|
3744 same path either as a cygwin path (@file{/build/xemacs}) or as a Windows
|
|
|
3745 path (@file{c:\build\xemacs}).
|
|
|
3746
|
|
|
3747 @item
|
|
|
3748 Build @samp{gcc -mno-cygwin} versions of the extra libs, i.e. @file{libpng},
|
|
|
3749 @file{compface}, etc.
|
|
|
3750
|
|
|
3751 @item
|
|
|
3752 Specify the target location of the extra libs on the command line
|
|
|
3753 to @file{configure}, e.g.
|
|
|
3754 @samp{./configure --site-prefixes=/build/libs i586-pc-mingw32}.
|
|
|
3755 @end itemize
|
|
|
3756
|
|
2559
|
3757 @node Q2.3.7, Q2.3.8, Q2.3.6, Installation
|
|
|
3758 @unnumberedsubsec Q2.3.7: How do I compile with X support?
|
|
2417
|
3759
|
|
|
3760 To compile under Cygwin, all you need to do is install XFree86, which
|
|
|
3761 is available as part of the standard Cygwin installation.
|
|
|
3762 @uref{http://www.cygwin.com/}. Once installed, @file{configure}
|
|
|
3763 should automatically find the X libraries and compile with X support.
|
|
|
3764
|
|
|
3765 As noted above, the non-Cygwin X support is basically orphaned, and
|
|
|
3766 probably won't work. But if it want to try, it's described in
|
|
|
3767 @file{nt/README} in some detail. Basically, you need to get X11
|
|
2459
|
3768 libraries from @uref{http://ftp.x.org}, and compile them. If the
|
|
2417
|
3769 precompiled versions are available somewhere, we don't know of it.
|
|
|
3770
|
|
2559
|
3771 @node Q2.3.8, Q2.4.1, Q2.3.7, Installation
|
|
|
3772 @unnumberedsubsec Q2.3.8: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
1058
|
3773
|
|
|
3774 The Cygwin binary distributed with the netinstaller uses an external DLL
|
|
|
3775 to handle XPM images (such as toolbar buttons). You may get an error like
|
|
|
3776
|
|
2559
|
3777 @example
|
|
|
3778 This application has failed to start because cygXpm-noX4.dll was not found.
|
|
|
3779 Re-installing the application may fix this problem.
|
|
|
3780 @end example
|
|
1058
|
3781
|
|
|
3782 Andy Piper <andy@@xemacs.org> sez:
|
|
|
3783
|
|
2559
|
3784 @example
|
|
|
3785 cygXpm-noX4 is part of the cygwin distribution under libraries or
|
|
|
3786 graphics, but is not installed by default. You need to run the
|
|
|
3787 cygwin setup again and select this package.
|
|
|
3788 @end example
|
|
1058
|
3789
|
|
|
3790 Ie, reinstalling XEmacs won't help because it is not part of the XEmacs
|
|
|
3791 distribution.
|
|
|
3792
|
|
2559
|
3793 @unnumberedsec 2.4: General Troubleshooting
|
|
|
3794
|
|
|
3795 @node Q2.4.1, Q2.4.2, Q2.3.8, Installation
|
|
|
3796 @unnumberedsubsec Q2.4.1: How do I deal with bugs or with problems building, installing, or running?
|
|
|
3797
|
|
|
3798 The file @file{PROBLEMS} contains information on many common problems that
|
|
|
3799 occur in building, installing and running XEmacs.
|
|
|
3800
|
|
|
3801 Reports of bugs in XEmacs should be sent to
|
|
|
3802 @email{xemacs-beta@@xemacs.org}. You can also post to the newsgroup
|
|
|
3803 comp.emacs.xemacs (or equivalentlt, send to the mailing list
|
|
|
3804 @email{xemacs@@xemacs.org}), but it is less likely that the developers
|
|
|
3805 will see it in a timely fashion. @xref{Bugs,,, xemacs, the XEmacs
|
|
|
3806 User's Manual}, for more information on how to report bugs.
|
|
|
3807 @xref{Q1.4.2}, for more information on mailing lists relating to
|
|
|
3808 XEmacs.
|
|
|
3809
|
|
|
3810 There are three ways to read the Bugs section.
|
|
|
3811
|
|
|
3812 @enumerate
|
|
|
3813 @item
|
|
|
3814 In a printed copy of the XEmacs manual.
|
|
|
3815
|
|
|
3816 @item
|
|
|
3817 With Info. First, start XEmacs. From the menu, select
|
|
|
3818 @samp{Help->Info (Online Docs)->Info Contents} to enter Info, then
|
|
|
3819 click on @samp{XEmacs}, then on @samp{Bugs}. Or, use the keyboard: do
|
|
|
3820 @kbd{C-h i} to enter Info, then @kbd{m XEmacs RET} to get to the Emacs
|
|
|
3821 manual, then @kbd{m Bugs RET} to get to the section on bugs. Or use
|
|
|
3822 standalone Info in a like manner. (Standalone Info is part of the
|
|
|
3823 Texinfo distribution, not part of the XEmacs distribution.)
|
|
|
3824
|
|
|
3825 @item
|
|
|
3826 By hand. Do
|
|
|
3827 @example
|
|
|
3828 cat info/xemacs* | more "+/^File: xemacs.info, Node: Bugs,"
|
|
|
3829 @end example
|
|
|
3830 @end enumerate
|
|
|
3831
|
|
|
3832 @node Q2.4.2, Q2.4.3, Q2.4.1, Installation
|
|
|
3833 @unnumberedsubsec Q2.4.2: Help! XEmacs just crashed on me!
|
|
428
|
3834
|
|
|
3835 First of all, don't panic. Whenever XEmacs crashes, it tries extremely
|
|
|
3836 hard to auto-save all of your files before dying. (The main time that
|
|
|
3837 this will not happen is if the machine physically lost power or if you
|
|
|
3838 killed the XEmacs process using @code{kill -9}). The next time you try
|
|
|
3839 to edit those files, you will be informed that a more recent auto-save
|
|
|
3840 file exists. You can use @kbd{M-x recover-file} to retrieve the
|
|
|
3841 auto-saved version of the file.
|
|
|
3842
|
|
462
|
3843 You can use the command @kbd{M-x recover-session} after a crash to pick
|
|
|
3844 up where you left off.
|
|
428
|
3845
|
|
|
3846 Now, XEmacs is not perfect, and there may occasionally be times, or
|
|
|
3847 particular sequences of actions, that cause it to crash. If you can
|
|
|
3848 come up with a reproducible way of doing this (or even if you have a
|
|
|
3849 pretty good memory of exactly what you were doing at the time), the
|
|
2417
|
3850 maintainers would be very interested in knowing about it. The best
|
|
|
3851 way to report a bug is using @kbd{M-x report-emacs-bug} (or by
|
|
|
3852 selecting @samp{Send Bug Report...} from the Help menu). If that
|
|
|
3853 won't work (e.g. you can't get XEmacs working at all), send ordinary
|
|
|
3854 mail to @email{xemacs-beta@@xemacs.org}. @emph{MAKE SURE} to include
|
|
|
3855 the output from the crash, especially including the Lisp backtrace, as
|
|
|
3856 well as the XEmacs configuration from @kbd{M-x describe-installation}
|
|
|
3857 (or equivalently, the file @file{Installation} in the top of the build
|
|
|
3858 tree). Note that the developers do @emph{not} usually follow
|
|
|
3859 @samp{comp.emacs.xemacs} on a regular basis; thus, this is better for
|
|
|
3860 general questions about XEmacs than bug reports.
|
|
428
|
3861
|
|
1183
|
3862 If at all possible, include a C stack backtrace of the core dump that
|
|
2417
|
3863 was produced. This shows where exactly things went wrong, and makes
|
|
|
3864 it much easier to diagnose problems. To do this under Unix and Mac OS
|
|
|
3865 X, you need to locate the core file (it's called @file{core}, and is
|
|
|
3866 usually sitting in the directory that you started XEmacs from, or your
|
|
|
3867 home directory if that other directory was not writable). Then, go to
|
|
|
3868 that directory and execute a command like:
|
|
428
|
3869
|
|
|
3870 @example
|
|
|
3871 gdb `which xemacs` core
|
|
|
3872 @end example
|
|
|
3873
|
|
|
3874 and then issue the command @samp{where} to get the stack backtrace. You
|
|
|
3875 might have to use @code{dbx} or some similar debugger in place of
|
|
|
3876 @code{gdb}. If you don't have any such debugger available, complain to
|
|
|
3877 your system administrator.
|
|
|
3878
|
|
2417
|
3879 It's possible that a core file didn't get produced or the stack trace
|
|
|
3880 from gdb is garbage, in which case you're out of luck unless you can
|
|
|
3881 reproduce the bug. A nonexistent core file can happen in some
|
|
|
3882 circumstances on some operating systems, depending on what exactly
|
|
|
3883 triggered the crash. It's also possible, however, that your limits
|
|
|
3884 are set to turn them off. You may be able to reenable them using a
|
|
|
3885 command like @samp{unlimit coredumpsize} or @samp{ulimit -c}. (To find
|
|
|
3886 out how your limits are set, use the command @samp{limit}.) However, if
|
|
|
3887 you didn't explicitly set your limits this way, go complain to your
|
|
|
3888 system administrator and tell him not to disable core files by
|
|
|
3889 default.
|
|
|
3890
|
|
|
3891 A garbaged stack trace can happen for various reasons. Some versions
|
|
|
3892 of gdb are broken on certain operating systems and aren't able to read
|
|
|
3893 the core file. It's also possible that the stack got overwritten
|
|
|
3894 during the crash. A very simple reason, however, is that your version
|
|
|
3895 of XEmacs was compiled without debugging information or had the
|
|
|
3896 debugging information stripped. A compilation with optimization can
|
|
|
3897 also result in partly or completely garbaged stack trace. In such
|
|
|
3898 cases, you will need to recompile XEmacs with debugging information
|
|
2559
|
3899 and without optimization; @xref{Q2.4.4, How to debug an XEmacs problem
|
|
2417
|
3900 with a debugger}. Note also that core files currently don't work at
|
|
|
3901 all under Cygwin, and the only way to get a backtrace is to run XEmacs
|
|
|
3902 from gdb.
|
|
|
3903
|
|
|
3904 If you cannot get a backtrace from the core dump, but can reproduce
|
|
|
3905 the problem, try running XEmacs under gdb. The goal is to get clean C
|
|
|
3906 and Lisp backtraces and submit a bug report including full
|
|
|
3907 configuration information as described above, as this will greatly
|
|
|
3908 assist in the process of tracking down the bug. However, even partial
|
|
|
3909 information is better than none. The process of getting backtraces
|
|
2559
|
3910 from gdb is described in detail in @ref{Q2.4.4, How to debug an XEmacs
|
|
2417
|
3911 problem with a debugger}.
|
|
428
|
3912
|
|
1183
|
3913 If you're under Microsoft Windows, you're out of luck unless you happen
|
|
|
3914 to have a debugging aid installed on your system, for example Visual
|
|
|
3915 C++. In this case, the crash will result in a message giving you the
|
|
|
3916 option to enter a debugger (for example, by pressing @samp{Cancel}). Do
|
|
|
3917 this and locate the stack-trace window. (If your XEmacs was built
|
|
|
3918 without debugging information, the stack trace may not be very useful.)
|
|
|
3919
|
|
428
|
3920 When making a problem report make sure that:
|
|
|
3921
|
|
|
3922 @enumerate
|
|
|
3923 @item
|
|
|
3924 Report @strong{all} of the information output by XEmacs during the
|
|
|
3925 crash.
|
|
|
3926
|
|
|
3927 @item
|
|
2417
|
3928 You mention what O/S and Hardware you are running XEmacs on.
|
|
428
|
3929
|
|
|
3930 @item
|
|
|
3931 What version of XEmacs you are running.
|
|
|
3932
|
|
|
3933 @item
|
|
|
3934 What build options you are using.
|
|
|
3935
|
|
|
3936 @item
|
|
2417
|
3937 If the problem is related to graphics and you are running Unix or Mac
|
|
|
3938 OS X, we will also need to know what version of the X Window System
|
|
|
3939 you are running, and what window manager you are using.
|
|
1183
|
3940
|
|
|
3941 @item
|
|
|
3942 If the problem happened on a TTY, please include the terminal type.
|
|
2417
|
3943
|
|
|
3944 @item
|
|
|
3945 Try very hard to get both C and Lisp backtraces, as described above.
|
|
428
|
3946 @end enumerate
|
|
|
3947
|
|
1135
|
3948 Much of the information above is automatically generated by @kbd{M-x
|
|
|
3949 report-emacs-bug}. Even more, and often useful, information can be
|
|
|
3950 generated by redirecting the output of @code{make} and @code{make check}
|
|
|
3951 to a file (@file{beta.err} is the default used by @code{build-report}),
|
|
|
3952 and executing @kbd{M-x build-report}.
|
|
|
3953
|
|
2417
|
3954
|
|
2559
|
3955 @node Q2.4.3, Q2.4.4, Q2.4.2, Installation
|
|
|
3956 @unnumberedsubsec Q2.4.3: XEmacs crashes and I compiled it myself.
|
|
2417
|
3957
|
|
|
3958 There have been a variety of reports of crashes due to compilers with
|
|
|
3959 buggy optimizers. If you are compiling with optimization, consider
|
|
2559
|
3960 turning it off (@pxref{Q2.4.4, How to debug an XEmacs problem with a
|
|
2417
|
3961 debugger}) and recompiling.
|
|
|
3962
|
|
|
3963 Please see the @file{PROBLEMS} file that comes with XEmacs (it's in
|
|
|
3964 the top-level source directory) to read what it says about your
|
|
|
3965 platform.
|
|
|
3966
|
|
|
3967 If you compiled XEmacs using @samp{--use-union-type} (or the option
|
|
|
3968 @samp{USE_UNION_TYPE} in @file{config.inc} under Windows), try
|
|
|
3969 recompiling again without it. The union type has been known to trigger
|
|
|
3970 compiler errors in a number of cases.
|
|
|
3971
|
|
2559
|
3972 @node Q2.4.4, Q2.4.5, Q2.4.3, Installation
|
|
|
3973 @unnumberedsubsec Q2.4.4: How to debug an XEmacs problem with a debugger
|
|
428
|
3974
|
|
|
3975 If XEmacs does crash on you, one of the most productive things you can
|
|
|
3976 do to help get the bug fixed is to poke around a bit with the debugger.
|
|
|
3977 Here are some hints:
|
|
|
3978
|
|
|
3979 @itemize @bullet
|
|
|
3980 @item
|
|
|
3981 First of all, if the crash is at all reproducible, consider very
|
|
563
|
3982 strongly recompiling your XEmacs with debugging symbols and with no
|
|
|
3983 optimization (e.g. with GCC use the compiler flags @samp{-g -O0} --
|
|
|
3984 that's an "oh" followed by a zero), and with the configure options
|
|
2417
|
3985 @samp{--debug=yes} and @samp{--error-checking=all}. This will make
|
|
|
3986 your XEmacs run somewhat slower, but you are a lot more likely to
|
|
|
3987 catch the problem earlier (closer to its source). It makes it a lot
|
|
|
3988 easier to determine what's going on with a debugger. The way to
|
|
|
3989 control the compiler flags is with the configuration option
|
|
|
3990 @samp{--cflags}. If you have a recent version of 21.5, you should use
|
|
|
3991 @samp{--without-optimization} in preference to directly setting
|
|
|
3992 @samp{--cflags}.
|
|
1258
|
3993
|
|
|
3994 @item
|
|
|
3995 If it's not a true crash (@emph{i.e.}, XEmacs is hung, or a zombie
|
|
|
3996 process), or it's inconvenient to run XEmacs again because XEmacs is
|
|
|
3997 already running or is running in batch mode as part of a bunch of
|
|
|
3998 scripts, you may be able to attach to the existing process with your
|
|
2417
|
3999 debugger. Under Unix and Mac OS X, the typical way to do this is to
|
|
|
4000 first use some variant of the @samp{ps} command to figure out the
|
|
|
4001 process ID of XEmacs, for example @samp{ps -auxww | grep xemacs} under
|
|
|
4002 a BSD variant, @samp{ps -elf | grep xemacs} under Linux or System V,
|
|
|
4003 or @samp{ps -aW | grep xemacs} under Cygwin. Then run
|
|
|
4004
|
|
|
4005 @example
|
|
|
4006 gdb /path/to/xemacs/xemacs ####
|
|
|
4007 @end example
|
|
|
4008
|
|
|
4009 Where @code{####} is the process id of your XEmacs. (If you're not
|
|
|
4010 sure, try using @samp{which xemacs}.) When gdb attaches, the xemacs
|
|
|
4011 will stop and you can type @samp{where} in gdb to get a stack trace as
|
|
|
4012 usual. To get things moving again, you can just type @samp{quit} in
|
|
|
4013 gdb. It'll tell you the program is running and ask if you want to
|
|
|
4014 quit anyways. Say @samp{y} and it'll quit and have your emacs
|
|
|
4015 continue from where it was at.
|
|
|
4016
|
|
|
4017 If you're running another debugger, a similar method may work, or you
|
|
|
4018 may have to run the debugger first and then use the @code{attach}
|
|
|
4019 command or something similar.
|
|
|
4020
|
|
|
4021 Under Microsoft Windows, use the menu item @samp{Build->Start
|
|
|
4022 Debug->Attach to Process...} and select the XEmacs process from the list
|
|
|
4023 given.
|
|
1258
|
4024
|
|
|
4025 @item
|
|
|
4026 If you're able to run XEmacs under a debugger and reproduce the crash,
|
|
|
4027 here are some things you can do:
|
|
428
|
4028
|
|
|
4029 @item
|
|
|
4030 If XEmacs is hitting an assertion failure, put a breakpoint on
|
|
|
4031 @code{assert_failed()}.
|
|
|
4032
|
|
|
4033 @item
|
|
|
4034 If XEmacs is hitting some weird Lisp error that's causing it to crash
|
|
|
4035 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is
|
|
2417
|
4036 declared static in @file{eval.c}.
|
|
428
|
4037
|
|
|
4038 @item
|
|
563
|
4039 If XEmacs is outputting lots of X errors, put a breakpoint on
|
|
2417
|
4040 @code{x_error_handler()}; that will tell you which call is causing
|
|
|
4041 them. Note that the result may not be very useful by default because
|
|
|
4042 X Windows normally operates asynchronously: A bunch of commands are
|
|
|
4043 buffered up and then sent to the server all at once. This greatly
|
|
|
4044 improves performance over a network but means that an error may not be
|
|
|
4045 reported until the server receives the commands, which can be long
|
|
|
4046 after XEmacs made the erroneous calls. For best results, you need to
|
|
|
4047 make the X server synchronous before getting the backtrace. This can
|
|
|
4048 be done by starting XEmacs with the @samp{-sync} option or executing
|
|
|
4049 the Lisp code @code{(x-debug-mode t)}.
|
|
563
|
4050
|
|
|
4051 @item
|
|
428
|
4052 Internally, you will probably see lots of variables that hold objects of
|
|
1258
|
4053 type @code{Lisp_Object}. These are references to Lisp objects.
|
|
|
4054 Printing them out with the debugger probably won't be too
|
|
|
4055 useful---you'll likely just see a number. To decode them, do this:
|
|
428
|
4056
|
|
|
4057 @example
|
|
2417
|
4058 call debug_print (OBJECT)
|
|
428
|
4059 @end example
|
|
|
4060
|
|
|
4061 where @var{OBJECT} is whatever you want to decode (it can be a variable,
|
|
1258
|
4062 a function call, etc.). This uses the Lisp printing routines to out a
|
|
|
4063 readable representation on the TTY from which the xemacs process was
|
|
|
4064 invoked.
|
|
428
|
4065
|
|
2417
|
4066 Under 21.5 and later, @code{dp} is defined as an easier-to-type equivalent
|
|
|
4067 of @code{debug_print}. You can also try @code{dpa} if you can't see
|
|
|
4068 the output from @code{debug_print} (this will return a string containing
|
|
|
4069 the output), or use @code{debug_p3} if @code{debug_print} itself triggers
|
|
|
4070 a crash (this is a less comprehensive but super-safe way to print out
|
|
|
4071 a Lisp object).
|
|
|
4072
|
|
428
|
4073 @item
|
|
|
4074 If you want to get a Lisp backtrace showing the Lisp call
|
|
|
4075 stack, do this:
|
|
|
4076
|
|
|
4077 @example
|
|
2417
|
4078 call debug_backtrace ()
|
|
428
|
4079 @end example
|
|
|
4080
|
|
2417
|
4081 Under 21.5 and later, @code{db} is defined as an easier-to-type equivalent
|
|
|
4082 of @code{debug_backtrace}.
|
|
|
4083
|
|
|
4084 @item
|
|
|
4085 Using @code{debug_print} and @code{debug_backtrace} has two
|
|
|
4086 disadvantages - they can only be used with a running (including hung
|
|
|
4087 or zombie) xemacs process, and they do not display the internal C
|
|
|
4088 structure of a Lisp Object. Even if all you've got is a core dump,
|
|
|
4089 all is not lost.
|
|
428
|
4090
|
|
|
4091 If you're using GDB, there are some macros in the file
|
|
438
|
4092 @file{src/.gdbinit} in the XEmacs source distribution that should make
|
|
|
4093 it easier for you to decode Lisp objects. This file is automatically
|
|
|
4094 read by gdb if gdb is run in the directory where xemacs was built, and
|
|
|
4095 contains these useful macros to inspect the state of xemacs:
|
|
|
4096
|
|
|
4097 @table @code
|
|
|
4098 @item pobj
|
|
|
4099 Usage: pobj lisp_object @*
|
|
|
4100 Print the internal C representation of a lisp object.
|
|
|
4101
|
|
|
4102 @item xtype
|
|
|
4103 Usage: xtype lisp_object @*
|
|
|
4104 Print the Lisp type of a lisp object.
|
|
|
4105
|
|
|
4106 @item lbt
|
|
|
4107 Usage: lbt @*
|
|
|
4108 Print the current Lisp stack trace.
|
|
1258
|
4109 Requires a running xemacs process. (It works by calling the db
|
|
|
4110 routine described above.)
|
|
438
|
4111
|
|
|
4112 @item ldp
|
|
|
4113 Usage: ldp lisp_object @*
|
|
|
4114 Print a Lisp Object value using the Lisp printer.
|
|
1258
|
4115 Requires a running xemacs process. (It works by calling the dp
|
|
|
4116 routine described above.)
|
|
438
|
4117
|
|
|
4118 @item run-temacs
|
|
|
4119 Usage: run-temacs @*
|
|
|
4120 Run temacs interactively, like xemacs.
|
|
|
4121 Use this with debugging tools (like purify) that cannot deal with dumping,
|
|
|
4122 or when temacs builds successfully, but xemacs does not.
|
|
|
4123
|
|
|
4124 @item dump-temacs
|
|
|
4125 Usage: dump-temacs @*
|
|
|
4126 Run the dumping part of the build procedure.
|
|
|
4127 Use when debugging temacs, not xemacs!
|
|
|
4128 Use this when temacs builds successfully, but xemacs does not.
|
|
|
4129
|
|
|
4130 @item check-xemacs
|
|
|
4131 Usage: check-xemacs @*
|
|
|
4132 Run the test suite. Equivalent to 'make check'.
|
|
|
4133
|
|
|
4134 @item check-temacs
|
|
|
4135 Usage: check-temacs @*
|
|
|
4136 Run the test suite on temacs. Equivalent to 'make check-temacs'.
|
|
|
4137 Use this with debugging tools (like purify) that cannot deal with dumping,
|
|
|
4138 or when temacs builds successfully, but xemacs does not.
|
|
|
4139 @end table
|
|
428
|
4140
|
|
|
4141 If you are using Sun's @file{dbx} debugger, there is an equivalent file
|
|
438
|
4142 @file{src/.dbxrc}, which defines the same commands for dbx.
|
|
428
|
4143
|
|
|
4144 @item
|
|
|
4145 If you're using a debugger to get a C stack backtrace and you're seeing
|
|
|
4146 stack traces with some of the innermost frames mangled, it may be due to
|
|
|
4147 dynamic linking. (This happens especially under Linux.) Consider
|
|
|
4148 reconfiguring with @samp{--dynamic=no}. Also, sometimes (again under
|
|
|
4149 Linux), stack backtraces of core dumps will have the frame where the
|
|
|
4150 fatal signal occurred mangled; if you can obtain a stack trace while
|
|
|
4151 running the XEmacs process under a debugger, the stack trace should be
|
|
|
4152 clean.
|
|
|
4153
|
|
1183
|
4154 @email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so
|
|
|
4155 version 1.8 if dynamic linking and debugging is a problem on Linux.
|
|
428
|
4156
|
|
|
4157 @item
|
|
|
4158 If you're using a debugger to get a C stack backtrace and you're
|
|
|
4159 getting a completely mangled and bogus stack trace, it's probably due to
|
|
|
4160 one of the following:
|
|
|
4161
|
|
|
4162 @enumerate a
|
|
|
4163 @item
|
|
|
4164 Your executable has been stripped. Bad news. Tell your sysadmin not to
|
|
|
4165 do this---it doesn't accomplish anything except to save a bit of disk
|
|
|
4166 space, and makes debugging much much harder.
|
|
|
4167
|
|
|
4168 @item
|
|
|
4169 Your stack is getting trashed. Debugging this is hard; you have to do a
|
|
|
4170 binary-search type of narrowing down where the crash occurs, until you
|
|
|
4171 figure out exactly which line is causing the problem. Of course, this
|
|
1258
|
4172 only works if the bug is highly reproducible. Also, in many cases if
|
|
|
4173 you run XEmacs from the debugger, the debugger can protect the stack
|
|
|
4174 somewhat. However, if the stack is being smashed, it is typically the
|
|
|
4175 case that there is a wild pointer somewhere in the program, often quite
|
|
|
4176 far from where the crash occurs.
|
|
428
|
4177
|
|
|
4178 @item
|
|
|
4179 If your stack trace has exactly one frame in it, with address 0x0, this
|
|
|
4180 could simply mean that XEmacs attempted to execute code at that address,
|
|
|
4181 e.g. through jumping to a null function pointer. Unfortunately, under
|
|
|
4182 those circumstances, GDB under Linux doesn't know how to get a stack
|
|
1183
|
4183 trace. (Yes, this is the fourth Linux-related problem I've mentioned. I
|
|
428
|
4184 have no idea why GDB under Linux is so bogus. Complain to the GDB
|
|
1183
|
4185 authors, or to comp.os.linux.development.system.) Again, you'll have to
|
|
428
|
4186 use the narrowing-down process described above.
|
|
|
4187
|
|
|
4188 @item
|
|
462
|
4189 You will get a Lisp backtrace output when XEmacs crashes, so you'll have
|
|
|
4190 something useful.
|
|
428
|
4191
|
|
|
4192 @end enumerate
|
|
|
4193
|
|
|
4194 @item
|
|
|
4195 If you compile with the newer gcc variants gcc-2.8 or egcs, you will
|
|
438
|
4196 also need gdb 4.17 or above. Earlier releases of gdb can't handle the
|
|
|
4197 debug information generated by the newer compilers.
|
|
428
|
4198
|
|
|
4199 @item
|
|
438
|
4200 In versions of XEmacs before 21.2.27, @file{src/.gdbinit} was named
|
|
|
4201 @file{src/gdbinit}. This had the disadvantage of not being sourced
|
|
|
4202 automatically by gdb, so you had to set that up yourself.
|
|
428
|
4203
|
|
1183
|
4204 @item
|
|
|
4205 If you are running Microsoft Windows, the the file @file{nt/README} for
|
|
|
4206 further information about debugging XEmacs.
|
|
|
4207
|
|
428
|
4208 @end itemize
|
|
|
4209
|
|
2559
|
4210 @node Q2.4.5, Q2.4.6, Q2.4.4, Installation
|
|
|
4211 @unnumberedsubsec Q2.4.5: I get a cryptic error message when trying to do something.
|
|
2417
|
4212
|
|
|
4213 When I try to use some particular option of some particular package, I
|
|
|
4214 get a cryptic error message in the minibuffer.
|
|
|
4215
|
|
|
4216 If the message went by too quickly, use @samp{Help->Recent Messages}
|
|
|
4217 from the menubar (or type @kbd{C-h l}) to see recent messages.
|
|
|
4218
|
|
|
4219 If you can't figure out what's going on, select
|
|
|
4220 @samp{Options->Troubleshooting->Debug on Error} from the menubar (or
|
|
|
4221 type @kbd{M-:} then @kbd{(setq debug-on-error t)}) then try and make
|
|
|
4222 the error happen again. This will put in the debugger (you can get
|
|
|
4223 out of this and continue what you were doing before by typing @kbd{c})
|
|
|
4224 and give you a backtrace that may be enlightening. If not, try
|
|
|
4225 reading through this FAQ; if that fails, you could try posting to
|
|
|
4226 @samp{comp.emacs.xemacs} (making sure to include the backtrace) and
|
|
|
4227 someone may be able to help. If you can identify which XEmacs Lisp
|
|
|
4228 source file the error is coming from you can get a more detailed stack
|
|
|
4229 backtrace by doing the following:
|
|
428
|
4230
|
|
|
4231 @enumerate
|
|
|
4232 @item
|
|
2417
|
4233 Visit the .el file in an XEmacs buffer.
|
|
|
4234
|
|
|
4235 @item
|
|
|
4236 Issue the command @kbd{M-x eval-current-buffer}.
|
|
|
4237
|
|
|
4238 @item
|
|
|
4239 Reproduce the error.
|
|
428
|
4240 @end enumerate
|
|
|
4241
|
|
2417
|
4242 For more information on debugging Lisp code, @xref{Debugging,,,
|
|
|
4243 lispref, XEmacs Lisp Reference Manual}.
|
|
|
4244
|
|
2559
|
4245 @node Q2.4.6, Q2.4.7, Q2.4.5, Installation
|
|
|
4246 @unnumberedsubsec Q2.4.6: XEmacs hangs when I try to do something.
|
|
2417
|
4247
|
|
|
4248 XEmacs might just be slow; some operations take a long time. XEmacs
|
|
|
4249 may also be waiting on a response from the network, for example when
|
|
|
4250 you are trying to send mail.
|
|
|
4251
|
|
|
4252 You can usually interrupt XEmacs by typing @kbd{C-g}. If not (for
|
|
|
4253 example, Lisp code explicitly disabled this by setting
|
|
|
4254 @code{inhibit-quit}), you can use the "critical quit" mechanism by
|
|
|
4255 typing @kbd{Control-Shift-G}. This should also pop you into the
|
|
|
4256 debugger and give you a backtrace, which can tell you where the
|
|
2559
|
4257 problem is (@pxref{Q2.4.4, How to debug an XEmacs problem with a
|
|
2417
|
4258 debugger}). (Note that setting @code{debug-on-quit} or selecting
|
|
|
4259 @samp{Options->Troubleshooting->Debug on Quit} will also cause regular
|
|
|
4260 @kbd{C-g} to enter the debugger and give you a backtrace.)
|
|
|
4261
|
|
|
4262 If you can't interrupt XEmacs this way, or for some reason XEmacs is
|
|
|
4263 not talking to the keyboard, you can try sending the @samp{SIGINT}
|
|
|
4264 signal using the @samp{kill} command.
|
|
|
4265
|
|
|
4266 If the Lisp backtrace isn't enlightening, or if XEmacs is so hung that
|
|
|
4267 you can't interrupt it at all, you could try attaching to the process
|
|
2559
|
4268 and getting a C stack backtrace. @xref{Q2.4.4, How to debug an XEmacs
|
|
2417
|
4269 problem with a debugger}.
|
|
|
4270
|
|
2559
|
4271 @node Q2.4.7, Q2.4.8, Q2.4.6, Installation
|
|
|
4272 @unnumberedsubsec Q2.4.7: I get an error message when XEmacs is running in batch mode.
|
|
2417
|
4273
|
|
|
4274 Typically this happens when you are trying to compile some Elisp code.
|
|
|
4275 If you are doing this as part of XEmacs or the XEmacs packages, you
|
|
|
4276 should automatically get a backtrace, which can help you determine the
|
|
|
4277 source of the problem. In other cases, you can get equivalent results
|
|
|
4278 by setting the environment variable @samp{XEMACSDEBUG} to @samp{(setq
|
|
|
4279 stack-trace-on-error t load-always-display-messages t
|
|
|
4280 load-ignore-out-of-date-elc-files t load-show-full-path-in-messages
|
|
|
4281 t)} (this needs to be all on one line; to set an environment variable,
|
|
|
4282 use @samp{export XEMACSDEBUG='FOO'} under @samp{bash}, @samp{zsh},
|
|
|
4283 etc. or @samp{setenv XEMACSDEBUG 'FOO'} under @samp{csh} and
|
|
|
4284 @samp{tcsh}). @samp{XEMACSDEBUG} specifies Lisp code that will be
|
|
|
4285 executed at startup time.
|
|
|
4286
|
|
|
4287 If the backtrace is not sufficiently useful in helping you diagnose
|
|
|
4288 the problem, you should consider using a debugger such as GDB.
|
|
2559
|
4289 @xref{Q2.4.4, How to debug an XEmacs problem with a debugger}. You
|
|
2417
|
4290 probably want to set a breakpoint on @code{signal_1}. Since such
|
|
|
4291 errors often occur during compiling, which is often triggered by a
|
|
|
4292 complex command run from a make suite, it may be easier to attach to
|
|
|
4293 the process once it's running.
|
|
|
4294
|
|
|
4295 Under Microsoft Windows (and perhaps other operating systems), there
|
|
|
4296 is another useful trick you can do if you have configured with
|
|
|
4297 debugging support (configure option @samp{--debug} or setting
|
|
|
4298 @samp{DEBUG_XEMACS} in @file{nt/config.inc}). Set the environment
|
|
|
4299 variable @samp{XEMACSDEBUG} (as described above) to @samp{(setq
|
|
|
4300 debug-on-error t)}. Then, when an error occurs noninteractively,
|
|
|
4301 instead of trying to invoke the Lisp debugger (which obviously won't
|
|
|
4302 work), XEmacs will break out to a C debugger using
|
|
|
4303 @code{(force-debugging-signal t)}. @emph{NOTE}: This runs
|
|
|
4304 @code{abort()}!!! (As well as and after executing INT 3 under MS
|
|
|
4305 Windows, which should invoke a debugger if it's active.) This is
|
|
|
4306 guaranteed to kill XEmacs! (But in this situation, XEmacs is about to
|
|
|
4307 die anyway, and if no debugger is present, this will usefully dump
|
|
|
4308 core.)
|
|
|
4309
|
|
2559
|
4310 @node Q2.4.8, Q2.4.9, Q2.4.7, Installation
|
|
|
4311 @unnumberedsubsec Q2.4.8: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
2417
|
4312
|
|
|
4313 XEmacs has various facilities for debugging event handling.
|
|
|
4314
|
|
|
4315 First, try setting the variable @code{debug-emacs-events} to non-zero.
|
|
|
4316 This will output various information showing which events are being
|
|
|
4317 received and how they are being translated. This may show you, for
|
|
|
4318 example, that a key command is getting intercepted using
|
|
|
4319 @code{key-translation-map}; this problem can otherwise be very tricky
|
|
|
4320 to debug.
|
|
|
4321
|
|
|
4322 Under X, you can see exactly which events are being received from the
|
|
|
4323 window system by setting @code{x-debug-events} to non-zero. (The value
|
|
|
4324 @samp{1} gives you regular output, and @samp{2} gives you verbose
|
|
|
4325 output, including all parameters.)
|
|
|
4326
|
|
|
4327 A similar facility exists under MS Windows: Set
|
|
|
4328 @code{debug-mswindows-events} to non-zero. (The value @samp{1} gives
|
|
|
4329 you regular output. The value @samp{2} gives you verbose output,
|
|
|
4330 including all parameters. The value @samp{3} gives you
|
|
|
4331 super-gorily-detailed output.)
|
|
|
4332
|
|
2559
|
4333 @node Q2.4.9, Q2.4.10, Q2.4.8, Installation
|
|
|
4334 @unnumberedsubsec Q2.4.9: @kbd{C-g} doesn't work for me. Is it broken?
|
|
2417
|
4335
|
|
|
4336 @kbd{C-g} does work for most people in most circumstances. If it
|
|
|
4337 doesn't, there are two possible explanations:
|
|
|
4338
|
|
|
4339 @enumerate
|
|
|
4340 @item
|
|
|
4341 XEmacs is hung in a way that prevents @kbd{C-g} from working. This
|
|
|
4342 can happen when code is wrapped with a binding of @code{inhibit-quit}
|
|
|
4343 to @code{t}; you should still be able interrupt XEmacs using "critical
|
|
|
4344 quit". On the other hand, XEmacs may be seriously wedged. (If you're
|
|
|
4345 lucky, sending @samp{SIGINT} to the XEmacs process will interrupt it.)
|
|
2559
|
4346 @xref{Q2.4.6, XEmacs hangs when I try to do something.}.
|
|
2417
|
4347
|
|
|
4348 @item
|
|
|
4349 @kbd{C-g} is indeed broken on your system. To test, try executing
|
|
|
4350 @code{(while t)} from the @samp{*scratch*} buffer. If @kbd{C-g}
|
|
|
4351 doesn't interrupt, then it's broken. This used to happen with systems
|
|
|
4352 where @samp{SIGIO} was broken, but @samp{BROKEN_SIGIO} wasn't defined.
|
|
|
4353 However, there may not be very many such systems nowadays.
|
|
|
4354 @end enumerate
|
|
|
4355
|
|
2559
|
4356 @node Q2.4.10, Q2.4.11, Q2.4.9, Installation
|
|
|
4357 @unnumberedsubsec Q2.4.10: How do I debug process-related problems?
|
|
2417
|
4358
|
|
|
4359 Under MS Windows, you can set the variable
|
|
|
4360 @code{debug-mswindows-process-command-lines} to non-@samp{nil} to get
|
|
|
4361 information on exactly what is getting passed to a process. This can
|
|
|
4362 be useful in determining problems with quoting. (Under Unix, a process
|
|
|
4363 receives each argument separately, but under MS Windows a single
|
|
|
4364 command line is received, and arguments with spaces or other special
|
|
|
4365 characters in them must be quoted. Unfortunately this means that each
|
|
|
4366 process, potentially at least, has its own quoting conventions, and
|
|
|
4367 the code to process quoting conventions in @file{cmd.exe}, the Visual
|
|
|
4368 C++ startup code and the like is baroque and poorly documented.
|
|
|
4369 XEmacs uses the variable
|
|
|
4370 @code{mswindows-construct-process-command-line-alist} to construct a
|
|
|
4371 command line from a list of arguments based on the command to be run,
|
|
|
4372 but it is (and cannot be) a perfect solution.)
|
|
|
4373
|
|
2559
|
4374 @node Q2.4.11, Q2.4.12, Q2.4.10, Installation
|
|
|
4375 @unnumberedsubsec Q2.4.11: XEmacs is outputting lots of X errors.
|
|
563
|
4376
|
|
|
4377 If this is happening, we would very much like to know what's causing
|
|
2559
|
4378 them. To find this out, see @ref{Q2.4.4, How to debug an XEmacs
|
|
2417
|
4379 problem with a debugger}. Try to get both a C and Lisp backtrace, and
|
|
|
4380 send them along with the full error output to
|
|
|
4381 @email{xemacs-beta@@xemacs.org}.
|
|
|
4382
|
|
2559
|
4383 @node Q2.4.12, Q2.5.1, Q2.4.11, Installation
|
|
|
4384 @unnumberedsubsec Q2.4.12: After upgrading, XEmacs won't do `foo' any more!
|
|
2417
|
4385
|
|
|
4386 You have been used to doing `foo', but now when you invoke it (or
|
|
|
4387 click the toolbar button or select the menu item), nothing (or an
|
|
|
4388 error) happens. The simplest explanation is that you are missing a
|
|
|
4389 package that is essential to you. You can either track it down and
|
|
|
4390 install it (there is a list of packages and brief descriptions of
|
|
|
4391 their contents in @file{etc/PACKAGES}), or install the `Sumo Tarball'
|
|
2559
|
4392 (@pxref{Q2.1.2, How do I figure out which packages to install?}).
|
|
2417
|
4393
|
|
|
4394 @c #### should xref to XEmacs manual here
|
|
|
4395
|
|
2559
|
4396 @unnumberedsec 2.5: Startup-Related Problems
|
|
|
4397
|
|
|
4398 @node Q2.5.1, Q2.5.2, Q2.4.12, Installation
|
|
|
4399 @unnumberedsubsec Q2.5.1: XEmacs cannot connect to my X Terminal!
|
|
2417
|
4400
|
|
|
4401 Help! I can not get XEmacs to display on my Envizex X-terminal!
|
|
|
4402
|
|
|
4403 Try setting the @code{DISPLAY} variable using the numeric IP address of
|
|
|
4404 the host you are running XEmacs from.
|
|
|
4405
|
|
2559
|
4406 @node Q2.5.2, Q2.5.3, Q2.5.1, Installation
|
|
|
4407 @unnumberedsubsec Q2.5.2 Startup problems related to paths or package locations.
|
|
|
4408
|
|
|
4409 First of all, if XEmacs can't find the packages, check to make sure
|
|
|
4410 that you put the packages in the right place, or that you told XEmacs
|
|
|
4411 where to look for the packages when you compiled it. @xref{Q2.1.1}.
|
|
|
4412
|
|
|
4413 If something is still going wrong, or you get a startup warning about
|
|
|
4414 not being able to deduce some paths, you can get detailed information
|
|
|
4415 on the path-searching process at startup by setting the environment
|
|
|
4416 variable @samp{EMACSDEBUGPATHS} to a non-null value. One thing to
|
|
|
4417 look for if you're having package problems is the value of
|
|
|
4418 @samp{configure-package-path}. This corresponds to what was compiled
|
|
|
4419 into XEmacs using the @samp{--package-prefix} or @samp{--package-path}
|
|
|
4420 parameter (@pxref{Q2.1.1}). If this has the value of @samp{nil},
|
|
|
4421 this means that no value was compiled into XEmacs using these parameters.
|
|
|
4422
|
|
|
4423 @node Q2.5.3, Q2.5.4, Q2.5.2, Installation
|
|
|
4424 @unnumberedsubsec Q2.5.3: XEmacs won't start without network.
|
|
434
|
4425
|
|
|
4426 If XEmacs starts when you're on the network, but fails when you're not
|
|
|
4427 on the network, you may be missing a "localhost" entry in your
|
|
|
4428 @file{/etc/hosts} file. The file should contain an entry like:
|
|
|
4429
|
|
|
4430 @example
|
|
|
4431 127.0.0.1 localhost
|
|
|
4432 @end example
|
|
|
4433
|
|
|
4434 Add that line, and XEmacs will be happy.
|
|
|
4435
|
|
2559
|
4436 @node Q2.5.4, Q2.5.5, Q2.5.3, Installation
|
|
|
4437 @unnumberedsubsec Q2.5.4: Startup warnings about deducing proper fonts?
|
|
2417
|
4438
|
|
|
4439 How can I avoid the startup warnings about deducing proper fonts?
|
|
|
4440
|
|
|
4441 This is highly dependent on your installation, but try with the
|
|
|
4442 following font as your base font for XEmacs and see what it does:
|
|
|
4443
|
|
|
4444 @format
|
|
|
4445 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
|
|
|
4446 @end format
|
|
|
4447
|
|
|
4448 More precisely, do the following in your resource file:
|
|
|
4449
|
|
|
4450 @format
|
|
|
4451 Emacs.default.attributeFont: \
|
|
|
4452 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
|
|
|
4453 @end format
|
|
|
4454
|
|
|
4455 If you just don't want to see the @samp{*Warnings*} buffer at startup
|
|
|
4456 time, you can set this:
|
|
428
|
4457
|
|
|
4458 @lisp
|
|
2417
|
4459 (setq display-warning-minimum-level 'error)
|
|
428
|
4460 @end lisp
|
|
|
4461
|
|
2417
|
4462 The buffer still exists; it just isn't in your face.
|
|
|
4463
|
|
2559
|
4464 @node Q2.5.5, Q2.5.6, Q2.5.4, Installation
|
|
|
4465 @unnumberedsubsec Q2.5.5: Warnings from incorrect key modifiers.
|
|
2417
|
4466
|
|
|
4467 The following information comes from the @file{PROBLEMS} file that comes
|
|
|
4468 with XEmacs.
|
|
|
4469
|
|
|
4470 If you're having troubles with HP/UX it is because HP/UX defines the
|
|
|
4471 modifiers wrong in X. Here is a shell script to fix the problem; be
|
|
|
4472 sure that it is run after VUE configures the X server.
|
|
428
|
4473
|
|
|
4474 @example
|
|
2417
|
4475 #! /bin/sh
|
|
|
4476 xmodmap 2> /dev/null - << EOF
|
|
|
4477 keysym Alt_L = Meta_L
|
|
|
4478 keysym Alt_R = Meta_R
|
|
|
4479 EOF
|
|
|
4480
|
|
|
4481 xmodmap - << EOF
|
|
|
4482 clear mod1
|
|
|
4483 keysym Mode_switch = NoSymbol
|
|
|
4484 add mod1 = Meta_L
|
|
|
4485 keysym Meta_R = Mode_switch
|
|
|
4486 add mod2 = Mode_switch
|
|
|
4487 EOF
|
|
428
|
4488 @end example
|
|
|
4489
|
|
2559
|
4490 @node Q2.5.6, , Q2.5.5, Installation
|
|
|
4491 @unnumberedsubsec Q2.5.6: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
2417
|
4492
|
|
|
4493 Yes.
|
|
|
4494
|
|
|
4495 The console was there because @file{temacs} (and in turn, @file{xemacs})
|
|
|
4496 was a console application, and Windows typically creates a new
|
|
|
4497 console for a console process unless the creating process requests that
|
|
|
4498 one isn't created. This used to be fixed with @file{runemacs}, a small
|
|
|
4499 Windows application that existed merely to start @file{xemacs}, stating
|
|
|
4500 that it didn't want a console.
|
|
|
4501
|
|
|
4502 XEmacs 21.4 fixes this cleanly by the virtue of being a true "GUI"
|
|
|
4503 application. The explanation of what that means is included for
|
|
|
4504 educational value.
|
|
|
4505
|
|
|
4506 When building an application to be run in a Win32 environment, you must
|
|
|
4507 state which sub-system it is to run in. Valid subsystems include
|
|
|
4508 "console" and "gui". The subsystem you use affects the run time
|
|
|
4509 libraries linked into your application, the start up function that is
|
|
|
4510 run before control is handed over to your application, the entry point
|
|
|
4511 to your program, and how Windows normally invokes your program. (Console
|
|
|
4512 programs automatically get a console created for them at startup if
|
|
|
4513 their stdin/stdout don't point anywhere useful, which is the case when
|
|
|
4514 run from the GUI. This is a stupid design, of course -- instead, the
|
|
|
4515 console should get created only when the first I/O actually occurs!
|
|
|
4516 GUI programs have an equally stupid design: When called from
|
|
|
4517 @file{CMD.EXE}/@file{COMMAND.COM}, their stdin/stdout will be set to
|
|
|
4518 point nowhere useful, even though the command shell has its own
|
|
|
4519 stdin/stdout. It's as if someone who had learned a bit about stdio but
|
|
|
4520 had no actual knowledge of interprocess communication designed the
|
|
|
4521 scheme; unfortunately, the whole process-communication aspect of the
|
|
|
4522 Win32 API is equally badly designed.) For example, the entry point for a
|
|
|
4523 console app is "main" (which is what you'd expect for a C/C++ program),
|
|
|
4524 but the entry point for a "gui" app is "WinMain". This confuses and
|
|
|
4525 annoys a lot of programmers who've grown up on Unix systems, where the
|
|
|
4526 kernel doesn't really care whether your application is a gui program or
|
|
|
4527 not.
|
|
|
4528
|
|
|
4529 For reasons not altogether clear, and are lost in the mists of time and
|
|
|
4530 tradition, XEmacs on Win32 started out as a console application, and
|
|
|
4531 therefore a console was automatically created for it. (It may have been
|
|
|
4532 made a console application partly because a console is needed in some
|
|
|
4533 circumstances, especially under Win95, to interrupt, terminate, or send
|
|
|
4534 signals to a child process, and because of the bogosity mentioned above
|
|
|
4535 with GUI programs and the standard command shell. Currently, XEmacs
|
|
|
4536 just creates and immediately hides a console when necessary, and
|
|
|
4537 works around the "no useful stdio" problem by creating its own console
|
|
|
4538 window as necessary to display messages in.)
|
|
|
4539
|
|
2459
|
4540 @node Editing, Display, Installation, Top
|
|
|
4541 @unnumbered 3 Editing Functions
|
|
2417
|
4542
|
|
|
4543 This is part 3 of the XEmacs Frequently Asked Questions list. This
|
|
2459
|
4544 section is devoted to the editing-related capabilities of XEmacs (the
|
|
|
4545 keyboard, mouse, buffers, text selections, etc.) and how to customize
|
|
|
4546 them.
|
|
2417
|
4547
|
|
|
4548 @menu
|
|
|
4549 3.0: The Keyboard
|
|
2459
|
4550 * Q3.0.1:: How can I customize the keyboard?
|
|
|
4551 * Q3.0.2:: How can I bind complex functions (or macros) to keys?
|
|
|
4552 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down?
|
|
|
4553 * Q3.0.4:: Globally binding @kbd{Delete}?
|
|
|
4554 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
|
4555 * Q3.0.6:: How can you type in special characters in XEmacs?
|
|
|
4556 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys?
|
|
|
4557 * Q3.0.8:: How do I map the arrow keys?
|
|
|
4558 * Q3.0.9:: HP Alt key as Meta.
|
|
|
4559 * Q3.0.10:: Why does edt emulation not work?
|
|
|
4560 * Q3.0.11:: How can I emulate VI and use it as my default mode?
|
|
2417
|
4561
|
|
|
4562 3.1: The Mouse
|
|
|
4563 * Q3.1.1:: How can I turn off Mouse pasting?
|
|
|
4564 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons?
|
|
|
4565 * Q3.1.3:: Clicking the left button does not do anything in buffer list.
|
|
|
4566 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3?
|
|
2459
|
4567 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
|
4568
|
|
|
4569 3.2: Buffers, Text Editing
|
|
|
4570 * Q3.2.1:: Can I have the end of the buffer delimited in some way?
|
|
|
4571 * Q3.2.2:: How do I insert today's date into a buffer?
|
|
|
4572 * Q3.2.3:: How do I get a single minibuffer frame?
|
|
|
4573 * Q3.2.4:: How can I enable auto-indent and/or Filladapt?
|
|
|
4574 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
4575
|
|
|
4576 3.3: Text Selections
|
|
|
4577 * Q3.3.1:: How do I select a rectangular region?
|
|
|
4578 * Q3.3.2:: How can I turn off or change highlighted selections?
|
|
|
4579 * Q3.3.3:: How do I cause typing on an active region to remove it?
|
|
|
4580 * Q3.3.4:: Can I turn off the highlight during isearch?
|
|
|
4581 * Q3.3.5:: Why is killing so slow?
|
|
|
4582 * Q3.3.6:: Why does @kbd{M-w} take so long?
|
|
|
4583
|
|
|
4584 3.4: Editing Source Code
|
|
|
4585 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode?
|
|
|
4586 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly?
|
|
2417
|
4587 @end menu
|
|
|
4588
|
|
|
4589 @unnumberedsec 3.0: The Keyboard
|
|
|
4590
|
|
2459
|
4591 @node Q3.0.1, Q3.0.2, Editing, Editing
|
|
|
4592 @unnumberedsubsec Q3.0.1: How can I customize the keyboard?
|
|
|
4593
|
|
|
4594 #### Write me.
|
|
|
4595
|
|
|
4596 @node Q3.0.2, Q3.0.3, Q3.0.1, Editing
|
|
|
4597 @unnumberedsubsec Q3.0.2: How can I bind complex functions (or macros) to keys?
|
|
428
|
4598
|
|
|
4599 As an example, say you want the @kbd{paste} key on a Sun keyboard to
|
|
|
4600 insert the current Primary X selection at point. You can accomplish this
|
|
|
4601 with:
|
|
|
4602
|
|
|
4603 @lisp
|
|
|
4604 (define-key global-map [f18] 'x-insert-selection)
|
|
|
4605 @end lisp
|
|
|
4606
|
|
|
4607 However, this only works if there is a current X selection (the
|
|
|
4608 selection will be highlighted). The functionality I like is for the
|
|
|
4609 @kbd{paste} key to insert the current X selection if there is one,
|
|
|
4610 otherwise insert the contents of the clipboard. To do this you need to
|
|
|
4611 pass arguments to @code{x-insert-selection}. This is done by wrapping
|
|
|
4612 the call in a 'lambda form:
|
|
|
4613
|
|
|
4614 @lisp
|
|
|
4615 (global-set-key [f18]
|
|
|
4616 (lambda () (interactive) (x-insert-selection t nil)))
|
|
|
4617 @end lisp
|
|
|
4618
|
|
|
4619 This binds the f18 key to a @dfn{generic} functional object. The
|
|
|
4620 interactive spec is required because only interactive functions can be
|
|
|
4621 bound to keys.
|
|
|
4622
|
|
|
4623 For the FAQ example you could use:
|
|
|
4624
|
|
|
4625 @lisp
|
|
|
4626 (global-set-key [(control ?.)]
|
|
|
4627 (lambda () (interactive) (scroll-up 1)))
|
|
440
|
4628 (global-set-key [(control ?;)]
|
|
|
4629 (lambda () (interactive) (scroll-up -1)))
|
|
428
|
4630 @end lisp
|
|
|
4631
|
|
|
4632 This is fine if you only need a few functions within the lambda body.
|
|
2417
|
4633 If you're doing more it's cleaner to define a separate function.
|
|
2459
|
4634 @xref{Q3.0.3, How do I bind C-. and C-; to scroll one line up and
|
|
2417
|
4635 down?}.
|
|
|
4636
|
|
2459
|
4637 @node Q3.0.3, Q3.0.4, Q3.0.2, Editing
|
|
|
4638 @unnumberedsubsec Q3.0.3: How do I bind C-. and C-; to scroll one line up and down?
|
|
428
|
4639
|
|
|
4640 Add the following (Thanks to @email{mly@@adoc.xerox.com, Richard Mlynarik} and
|
|
|
4641 @email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}:
|
|
|
4642
|
|
|
4643 @lisp
|
|
|
4644 (defun scroll-up-one-line ()
|
|
|
4645 (interactive)
|
|
|
4646 (scroll-up 1))
|
|
|
4647
|
|
|
4648 (defun scroll-down-one-line ()
|
|
|
4649 (interactive)
|
|
|
4650 (scroll-down 1))
|
|
|
4651
|
|
|
4652 (global-set-key [(control ?.)] 'scroll-up-one-line) ; C-.
|
|
440
|
4653 (global-set-key [(control ?;)] 'scroll-down-one-line) ; C-;
|
|
428
|
4654 @end lisp
|
|
|
4655
|
|
|
4656 The key point is that you can only bind simple functions to keys; you
|
|
2417
|
4657 can not bind a key to a function that you're also passing arguments
|
|
2459
|
4658 to. (@pxref{Q3.0.2, How can I bind complex functions (or macros) to
|
|
2417
|
4659 keys?} for a better answer).
|
|
|
4660
|
|
2459
|
4661 @node Q3.0.4, Q3.0.5, Q3.0.3, Editing
|
|
|
4662 @unnumberedsubsec Q3.0.4: Globally binding @kbd{Delete}?
|
|
428
|
4663
|
|
|
4664 I cannot manage to globally bind my @kbd{Delete} key to something other
|
|
|
4665 than the default. How does one do this?
|
|
|
4666
|
|
462
|
4667 Answer: The problem is that many modes explicitly bind @kbd{Delete}. To
|
|
|
4668 get around this, try the following:
|
|
|
4669
|
|
428
|
4670 @lisp
|
|
|
4671 (defun foo ()
|
|
|
4672 (interactive)
|
|
|
4673 (message "You hit DELETE"))
|
|
|
4674
|
|
462
|
4675 (define-key key-translation-map 'delete 'redirected-delete)
|
|
|
4676 (global-set-key 'redirected-delete 'foo)
|
|
428
|
4677 @end lisp
|
|
|
4678
|
|
2459
|
4679 @node Q3.0.5, Q3.0.6, Q3.0.4, Editing
|
|
|
4680 @unnumberedsubsec Q3.0.5: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
428
|
4681
|
|
|
4682 The following works in GNU Emacs 19:
|
|
|
4683
|
|
|
4684 @lisp
|
|
|
4685 (global-set-key [help] 'help-command);; Help
|
|
|
4686 @end lisp
|
|
|
4687
|
|
462
|
4688 The following works in XEmacs with the addition of shift:
|
|
428
|
4689
|
|
|
4690 @lisp
|
|
|
4691 (global-set-key [(shift help)] 'help-command);; Help
|
|
|
4692 @end lisp
|
|
|
4693
|
|
|
4694 But it doesn't work alone. This is in the file @file{PROBLEMS} which
|
|
|
4695 should have come with your XEmacs installation: @emph{Emacs ignores the
|
|
|
4696 @kbd{help} key when running OLWM}.
|
|
|
4697
|
|
|
4698 OLWM grabs the @kbd{help} key, and retransmits it to the appropriate
|
|
|
4699 client using
|
|
|
4700 @iftex
|
|
|
4701 @*
|
|
|
4702 @end iftex
|
|
|
4703 @code{XSendEvent}. Allowing Emacs to react to synthetic
|
|
|
4704 events is a security hole, so this is turned off by default. You can
|
|
|
4705 enable it by setting the variable @code{x-allow-sendevents} to t. You
|
|
|
4706 can also cause fix this by telling OLWM to not grab the help key, with
|
|
|
4707 the null binding @code{OpenWindows.KeyboardCommand.Help:}.
|
|
|
4708
|
|
2459
|
4709 @node Q3.0.6, Q3.0.7, Q3.0.5, Editing
|
|
|
4710 @unnumberedsubsec Q3.0.6: How can you type in special characters in XEmacs?
|
|
428
|
4711 One way is to use the package @code{x-compose}. Then you can use
|
|
|
4712 sequences like @kbd{Compose " a} to get ä, etc.
|
|
|
4713
|
|
462
|
4714 Another way is to use the @code{iso-insert} package. Then you can use
|
|
|
4715 sequences like @kbd{C-x 8 " a} to get ä, etc.
|
|
428
|
4716
|
|
|
4717 @email{glynn@@sensei.co.uk, Glynn Clements} writes:
|
|
|
4718
|
|
|
4719 @quotation
|
|
|
4720 It depends upon your X server.
|
|
|
4721
|
|
|
4722 Generally, the simplest way is to define a key as Multi_key with
|
|
|
4723 xmodmap, e.g.
|
|
|
4724 @c hey, show some respect, willya -- there's xkeycaps, isn't there? --
|
|
|
4725 @c chr ;)
|
|
|
4726 @example
|
|
440
|
4727 xmodmap -e 'keycode 0xff20 = Multi_key'
|
|
428
|
4728 @end example
|
|
|
4729
|
|
|
4730 You will need to pick an appropriate keycode. Use xev to find out the
|
|
|
4731 keycodes for each key.
|
|
|
4732
|
|
|
4733 [NB: On a `Windows' keyboard, recent versions of XFree86 automatically
|
|
|
4734 define the right `Windows' key as Multi_key'.]
|
|
|
4735
|
|
|
4736 Once you have Multi_key defined, you can use e.g.
|
|
|
4737 @example
|
|
440
|
4738 Multi a ' => á
|
|
|
4739 Multi e " => ë
|
|
|
4740 Multi c , => ç
|
|
428
|
4741 @end example
|
|
|
4742
|
|
|
4743 etc.
|
|
|
4744
|
|
|
4745 Also, recent versions of XFree86 define various AltGr-<key>
|
|
|
4746 combinations as dead keys, i.e.
|
|
|
4747 @example
|
|
440
|
4748 AltGr [ => dead_diaeresis
|
|
|
4749 AltGr ] => dead_tilde
|
|
|
4750 AltGr ; => dead_acute
|
|
428
|
4751 @end example
|
|
|
4752 etc.
|
|
|
4753
|
|
|
4754 Running @samp{xmodmap -pk} will list all of the defined keysyms.
|
|
|
4755 @end quotation
|
|
|
4756
|
|
1135
|
4757 For the related problem of @emph{displaying} non-ASCII characters in a
|
|
2459
|
4758 non-Mule XEmacs, @xref{Q4.0.8, How do I display non-ASCII characters?}.
|
|
|
4759
|
|
|
4760 @node Q3.0.7, Q3.0.8, Q3.0.6, Editing
|
|
|
4761 @unnumberedsubsec Q3.0.7: Can I turn on @dfn{sticky} modifier keys?
|
|
428
|
4762
|
|
|
4763 Yes, with @code{(setq modifier-keys-are-sticky t)}. This will give the
|
|
|
4764 effect of being able to press and release Shift and have the next
|
|
|
4765 character typed come out in upper case. This will affect all the other
|
|
|
4766 modifier keys like Control and Meta as well.
|
|
|
4767
|
|
|
4768 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
|
4769
|
|
|
4770 @quotation
|
|
|
4771 One thing about the sticky modifiers is that if you move the mouse out
|
|
|
4772 of the frame and back in, it cancels all currently ``stuck'' modifiers.
|
|
|
4773 @end quotation
|
|
|
4774
|
|
2459
|
4775 @node Q3.0.8, Q3.0.9, Q3.0.7, Editing
|
|
|
4776 @unnumberedsubsec Q3.0.8: How do I map the arrow keys?
|
|
428
|
4777 @c New
|
|
|
4778 Say you want to map @kbd{C-@key{right}} to forward-word:
|
|
|
4779
|
|
|
4780 @email{sds@@usa.net, Sam Steingold} writes:
|
|
|
4781
|
|
|
4782 @quotation
|
|
|
4783 @lisp
|
|
|
4784 ; both XEmacs and Emacs
|
|
|
4785 (define-key global-map [(control right)] 'forward-word)
|
|
|
4786 @end lisp
|
|
|
4787 or
|
|
|
4788 @lisp
|
|
|
4789 ; Emacs only
|
|
|
4790 (define-key global-map [C-right] 'forward-word)
|
|
|
4791 @end lisp
|
|
|
4792 or
|
|
|
4793 @lisp
|
|
|
4794 ; ver > 20, both
|
|
|
4795 (define-key global-map (kbd "C-<right>") 'forward-word)
|
|
|
4796 @end lisp
|
|
|
4797 @end quotation
|
|
|
4798
|
|
2459
|
4799 @node Q3.0.9, Q3.0.10, Q3.0.8, Editing
|
|
|
4800 @unnumberedsubsec Q3.0.9: HP Alt key as Meta.
|
|
2417
|
4801
|
|
|
4802 How can I make XEmacs recognize the Alt key of my HP workstation as a
|
|
|
4803 Meta key?
|
|
|
4804
|
|
|
4805 Put the following line into a file and load it with xmodmap(1) before
|
|
|
4806 starting XEmacs:
|
|
428
|
4807
|
|
|
4808 @example
|
|
2417
|
4809 remove Mod1 = Mode_switch
|
|
428
|
4810 @end example
|
|
|
4811
|
|
2459
|
4812 @node Q3.0.10, Q3.0.11, Q3.0.9, Editing
|
|
|
4813 @unnumberedsubsec Q3.0.10: Why does edt emulation not work?
|
|
2417
|
4814
|
|
|
4815 We don't know, but you can use tpu-edt emulation instead, which works
|
|
|
4816 fine and is a little fancier than the standard edt emulation. To do
|
|
|
4817 this, add the following line to your @file{init.el}:
|
|
|
4818
|
|
|
4819 @lisp
|
|
|
4820 (tpu-edt)
|
|
|
4821 @end lisp
|
|
|
4822
|
|
|
4823 If you don't want it to replace @kbd{C-h} with an edt-style help menu
|
|
|
4824 add this as well:
|
|
428
|
4825
|
|
|
4826 @lisp
|
|
2417
|
4827 (global-set-key [(control h)] 'help-for-help)
|
|
428
|
4828 @end lisp
|
|
|
4829
|
|
2459
|
4830 @node Q3.0.11, Q3.1.1, Q3.0.10, Editing
|
|
|
4831 @unnumberedsubsec Q3.0.11: How can I emulate VI and use it as my default mode?
|
|
2417
|
4832
|
|
|
4833 Our recommended VI emulator is viper. To make viper-mode the default,
|
|
|
4834 add this to your @file{init.el}:
|
|
428
|
4835
|
|
|
4836 @lisp
|
|
2417
|
4837 (viper-mode)
|
|
428
|
4838 @end lisp
|
|
|
4839
|
|
2417
|
4840 @email{kifer@@CS.SunySB.EDU, Michael Kifer} writes:
|
|
|
4841
|
|
|
4842 @quotation
|
|
|
4843 This should be added as close to the top of @file{init.el} as you can get
|
|
|
4844 it, otherwise some minor modes may not get viper-ized.
|
|
|
4845 @end quotation
|
|
|
4846
|
|
|
4847 @unnumberedsec 3.1: The Mouse
|
|
|
4848
|
|
2459
|
4849 @node Q3.1.1, Q3.1.2, Q3.0.11, Editing
|
|
2417
|
4850 @unnumberedsubsec Q3.1.1: How can I turn off Mouse pasting?
|
|
428
|
4851
|
|
|
4852 I keep hitting the middle mouse button by accident and getting stuff
|
|
|
4853 pasted into my buffer so how can I turn this off?
|
|
|
4854
|
|
|
4855 Here is an alternative binding, whereby the middle mouse button selects
|
|
|
4856 (but does not cut) the expression under the mouse. Clicking middle on a
|
|
|
4857 left or right paren will select to the matching one. Note that you can
|
|
|
4858 use @code{define-key} or @code{global-set-key}.
|
|
|
4859
|
|
|
4860 @lisp
|
|
|
4861 (defun mouse-set-point-and-select (event)
|
|
|
4862 "Sets the point at the mouse location, then marks following form"
|
|
|
4863 (interactive "@@e")
|
|
|
4864 (mouse-set-point event)
|
|
|
4865 (mark-sexp 1))
|
|
|
4866 (define-key global-map [button2] 'mouse-set-point-and-select)
|
|
|
4867 @end lisp
|
|
|
4868
|
|
2459
|
4869 @node Q3.1.2, Q3.1.3, Q3.1.1, Editing
|
|
2417
|
4870 @unnumberedsubsec Q3.1.2: How do I set control/meta/etc modifiers on mouse buttons?
|
|
428
|
4871
|
|
|
4872 Use, for instance, @code{[(meta button1)]}. For example, here is a common
|
|
|
4873 setting for Common Lisp programmers who use the bundled @code{ilisp}
|
|
|
4874 package, whereby meta-button1 on a function name will find the file where
|
|
|
4875 the function name was defined, and put you at that location in the source
|
|
|
4876 file.
|
|
|
4877
|
|
|
4878 [Inside a function that gets called by the lisp-mode-hook and
|
|
|
4879 ilisp-mode-hook]
|
|
|
4880
|
|
|
4881 @lisp
|
|
|
4882 (local-set-key [(meta button1)] 'edit-definitions-lisp)
|
|
|
4883 @end lisp
|
|
|
4884
|
|
2459
|
4885 @node Q3.1.3, Q3.1.4, Q3.1.2, Editing
|
|
2417
|
4886 @unnumberedsubsec Q3.1.3: Clicking the left button does not do anything in buffer list.
|
|
428
|
4887
|
|
|
4888 I do @kbd{C-x C-b} to get a list of buffers and the entries get
|
|
|
4889 highlighted when I move the mouse over them but clicking the left mouse
|
|
|
4890 does not do anything.
|
|
|
4891
|
|
|
4892 Use the middle mouse button.
|
|
|
4893
|
|
2459
|
4894 @node Q3.1.4, Q3.1.5, Q3.1.3, Editing
|
|
2417
|
4895 @unnumberedsubsec Q3.1.4: How can I get a list of buffers when I hit mouse button 3?
|
|
428
|
4896
|
|
|
4897 The following code will replace the default popup on button3:
|
|
|
4898
|
|
|
4899 @lisp
|
|
|
4900 (global-set-key [button3] 'popup-buffer-menu)
|
|
|
4901 @end lisp
|
|
|
4902
|
|
2459
|
4903 @node Q3.1.5, Q3.2.1, Q3.1.4, Editing
|
|
|
4904 @unnumberedsubsec Q3.1.5: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
428
|
4905
|
|
|
4906 By default XEmacs pastes X selections where the mouse pointer is. How
|
|
|
4907 do I disable this?
|
|
|
4908
|
|
|
4909 Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank
|
|
|
4910 @key{RET}}.
|
|
|
4911
|
|
2417
|
4912 To get XEmacs to paste at the text cursor, add this your @file{init.el}:
|
|
428
|
4913
|
|
|
4914 @lisp
|
|
|
4915 (setq mouse-yank-at-point t)
|
|
|
4916 @end lisp
|
|
|
4917
|
|
2459
|
4918 You can also change this with Customize. Select from the
|
|
|
4919 @code{Options} menu @code{Advanced
|
|
|
4920 (Customize)->Emacs->Editing->Mouse->Yank At Point...} or type @kbd{M-x
|
|
|
4921 customize @key{RET} mouse @key{RET}}.
|
|
|
4922
|
|
|
4923 @unnumberedsec 3.2: Buffers, Text Editing
|
|
|
4924
|
|
|
4925 @node Q3.2.1, Q3.2.2, Q3.1.5, Editing
|
|
|
4926 @unnumberedsubsec Q3.2.1: Can I have the end of the buffer delimited in some way?
|
|
|
4927
|
|
|
4928 Say, with: @samp{[END]}?
|
|
|
4929
|
|
|
4930 Try this:
|
|
|
4931
|
|
|
4932 @lisp
|
|
|
4933 (let ((ext (make-extent (point-min) (point-max))))
|
|
|
4934 (set-extent-property ext 'start-closed t)
|
|
|
4935 (set-extent-property ext 'end-closed t)
|
|
|
4936 (set-extent-property ext 'detachable nil)
|
|
|
4937 (set-extent-end-glyph ext (make-glyph [string :data "[END]"])))
|
|
|
4938 @end lisp
|
|
|
4939
|
|
|
4940 Since this is XEmacs, you can specify an icon to be shown on
|
|
|
4941 window-system devices. To do so, change the @code{make-glyph} call to
|
|
|
4942 something like this:
|
|
|
4943
|
|
|
4944 @lisp
|
|
|
4945 (make-glyph '([xpm :file "~/something.xpm"]
|
|
|
4946 [string :data "[END]"]))
|
|
|
4947 @end lisp
|
|
|
4948
|
|
|
4949 You can inline the @sc{xpm} definition yourself by specifying
|
|
|
4950 @code{:data} instead of @code{:file}. Here is such a full-featured
|
|
|
4951 version that works on both X and TTY devices:
|
|
|
4952
|
|
|
4953 @lisp
|
|
|
4954 (let ((ext (make-extent (point-min) (point-max))))
|
|
|
4955 (set-extent-property ext 'start-closed t)
|
|
|
4956 (set-extent-property ext 'end-closed t)
|
|
|
4957 (set-extent-property ext 'detachable nil)
|
|
|
4958 (set-extent-end-glyph ext (make-glyph '([xpm :data "\
|
|
|
4959 /* XPM */
|
|
|
4960 static char* eye = @{
|
|
|
4961 \"20 11 7 2\",
|
|
|
4962 \"__ c None\"
|
|
|
4963 \"_` c #7f7f7f\",
|
|
|
4964 \"_a c #fefefe\",
|
|
|
4965 \"_b c #7f0000\",
|
|
|
4966 \"_c c #fefe00\",
|
|
|
4967 \"_d c #fe0000\",
|
|
|
4968 \"_e c #bfbfbf\",
|
|
|
4969 \"___________`_`_`___b_b_b_b_________`____\",
|
|
|
4970 \"_________`_`_`___b_c_c_c_b_b____________\",
|
|
|
4971 \"_____`_`_`_e___b_b_c_c_c___b___b_______`\",
|
|
|
4972 \"___`_`_e_a___b_b_d___b___b___b___b______\",
|
|
|
4973 \"_`_`_e_a_e___b_b_d_b___b___b___b___b____\",
|
|
|
4974 \"_`_`_a_e_a___b_b_d___b___b___b___b___b__\",
|
|
|
4975 \"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\",
|
|
|
4976 \"___`_`_e_a___b_b_b_d_c___b___b___d_b____\",
|
|
|
4977 \"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\",
|
|
|
4978 \"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\",
|
|
|
4979 \"___`_____`_`_`_`___b_b_b_b_b_b__________\",
|
|
|
4980 @} ;"]
|
|
|
4981 [string :data "[END]"]))))
|
|
|
4982 @end lisp
|
|
|
4983
|
|
|
4984 Note that you might want to make this a function, and put it to a hook.
|
|
|
4985 We leave that as an exercise for the reader.
|
|
|
4986
|
|
|
4987 @node Q3.2.2, Q3.2.3, Q3.2.1, Editing
|
|
|
4988 @unnumberedsubsec Q3.2.2: How do I insert today's date into a buffer?
|
|
2417
|
4989
|
|
|
4990 Like this:
|
|
428
|
4991
|
|
|
4992 @lisp
|
|
2459
|
4993 (insert (current-time-string))
|
|
2417
|
4994 @end lisp
|
|
|
4995
|
|
2459
|
4996 @node Q3.2.3, Q3.2.4, Q3.2.2, Editing
|
|
|
4997 @unnumberedsubsec Q3.2.3: How do I get a single minibuffer frame?
|
|
|
4998
|
|
|
4999 @email{acs@@acm.org, Vin Shelton} writes:
|
|
2417
|
5000
|
|
|
5001 @lisp
|
|
2459
|
5002 (setq initial-frame-plist '(minibuffer nil))
|
|
|
5003 (setq default-frame-plist '(minibuffer nil))
|
|
|
5004 (setq default-minibuffer-frame
|
|
|
5005 (make-frame
|
|
|
5006 '(minibuffer only
|
|
|
5007 width 86
|
|
|
5008 height 1
|
|
|
5009 menubar-visible-p nil
|
|
|
5010 default-toolbar-visible-p nil
|
|
|
5011 name "minibuffer"
|
|
|
5012 top -2
|
|
|
5013 left -2
|
|
|
5014 has-modeline-p nil)))
|
|
|
5015 (frame-notice-user-settings)
|
|
2417
|
5016 @end lisp
|
|
|
5017
|
|
2459
|
5018 @strong{Please note:} The single minibuffer frame may not be to everyone's
|
|
|
5019 taste, and there any number of other XEmacs options settings that may
|
|
|
5020 make it difficult or inconvenient to use.
|
|
|
5021
|
|
|
5022 @node Q3.2.4, Q3.2.5, Q3.2.3, Editing
|
|
|
5023 @unnumberedsubsec Q3.2.4: How can I enable auto-indent and/or Filladapt?
|
|
|
5024
|
|
|
5025 Put the following line in your @file{init.el}:
|
|
428
|
5026
|
|
|
5027 @lisp
|
|
2459
|
5028 (setq indent-line-function 'indent-relative-maybe)
|
|
428
|
5029 @end lisp
|
|
|
5030
|
|
2459
|
5031 If you want to get fancy, try the @code{filladapt} package available
|
|
|
5032 standard with XEmacs. Put this into your @file{init.el}:
|
|
428
|
5033
|
|
|
5034 @lisp
|
|
2459
|
5035 (require 'filladapt)
|
|
|
5036 (setq-default filladapt-mode t)
|
|
|
5037 (add-hook 'c-mode-hook 'turn-off-filladapt-mode)
|
|
428
|
5038 @end lisp
|
|
|
5039
|
|
2459
|
5040 This will enable Filladapt for all modes except C mode, where it doesn't
|
|
|
5041 work well. To turn Filladapt on only in particular major modes, remove
|
|
|
5042 the @code{(setq-default ...)} line and use
|
|
|
5043 @code{turn-on-filladapt-mode}, like this:
|
|
428
|
5044
|
|
|
5045 @lisp
|
|
2459
|
5046 (add-hook 'text-mode-hook 'turn-on-filladapt-mode)
|
|
428
|
5047 @end lisp
|
|
2417
|
5048
|
|
2459
|
5049 You can customize filling and adaptive filling with Customize.
|
|
|
5050 Select from the @code{Options} menu
|
|
|
5051 @code{Advanced (Customize)->Emacs->Editing->Fill->Fill...}
|
|
|
5052 or type @kbd{M-x customize @key{RET} fill @key{RET}}.
|
|
|
5053
|
|
|
5054 Note that well-behaving text-lookalike modes will run
|
|
|
5055 @code{text-mode-hook} by default (e.g. that's what Message does). For
|
|
|
5056 the nasty ones, you'll have to provide the @code{add-hook}s yourself.
|
|
|
5057
|
|
|
5058 Please note that the @code{fa-extras} package is no longer useful.
|
|
|
5059
|
|
|
5060 @node Q3.2.5, Q3.3.1, Q3.2.4, Editing
|
|
|
5061 @unnumberedsubsec Q3.2.5: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
5062
|
|
|
5063 Try the following lisp in your @file{init.el}:
|
|
2417
|
5064
|
|
|
5065 @lisp
|
|
2459
|
5066 (setq default-major-mode 'text-mode)
|
|
|
5067 (setq text-mode-hook 'turn-on-auto-fill)
|
|
2417
|
5068 @end lisp
|
|
|
5069
|
|
2459
|
5070 @strong{WARNING}: note that changing the value of
|
|
|
5071 @code{default-major-mode} from @code{fundamental-mode} can break a large
|
|
|
5072 amount of built-in code that expects newly created buffers to be in
|
|
|
5073 @code{fundamental-mode}. (Changing from @code{fundamental-mode} to
|
|
|
5074 @code{text-mode} might not wreak too much havoc, but changing to
|
|
|
5075 something more exotic like a lisp-mode would break many Emacs packages).
|
|
|
5076
|
|
|
5077 Note that Emacs by default starts up in buffer @code{*scratch*} in
|
|
|
5078 @code{initial-major-mode}, which defaults to
|
|
|
5079 @code{lisp-interaction-mode}. Thus adding the following form to your
|
|
|
5080 Emacs init file will cause the initial @code{*scratch*} buffer to be put
|
|
|
5081 into auto-fill'ed @code{text-mode}:
|
|
2417
|
5082
|
|
|
5083 @lisp
|
|
2459
|
5084 (setq initial-major-mode
|
|
|
5085 (lambda ()
|
|
|
5086 (text-mode)
|
|
|
5087 (turn-on-auto-fill)))
|
|
2417
|
5088 @end lisp
|
|
|
5089
|
|
2459
|
5090 Note that after your init file is loaded, if
|
|
|
5091 @code{inhibit-startup-message} is @code{nil} (the default) and the
|
|
|
5092 startup buffer is @code{*scratch*} then the startup message will be
|
|
|
5093 inserted into @code{*scratch*}; it will be removed after a timeout by
|
|
|
5094 erasing the entire @code{*scratch*} buffer. Keep in mind this default
|
|
|
5095 usage of @code{*scratch*} if you desire any prior manipulation of
|
|
|
5096 @code{*scratch*} from within your Emacs init file. In particular,
|
|
|
5097 anything you insert into @code{*scratch*} from your init file will be
|
|
|
5098 later erased. Also, if you change the mode of the @code{*scratch*}
|
|
|
5099 buffer, be sure that this will not interfere with possible later
|
|
|
5100 insertion of the startup message (e.g. if you put @code{*scratch*} into
|
|
|
5101 a nonstandard mode that has automatic font lock rules, then the startup
|
|
|
5102 message might get fontified in a strange foreign manner, e.g. as code in
|
|
|
5103 some programming language).
|
|
|
5104
|
|
|
5105 @unnumberedsec 3.3: Text Selections
|
|
|
5106
|
|
|
5107 @node Q3.3.1, Q3.3.2, Q3.2.5, Editing
|
|
|
5108 @unnumberedsubsec Q3.3.1: How do I select a rectangular region?
|
|
2417
|
5109
|
|
|
5110 Just select the region normally, then use the rectangle commands (e.g.
|
|
|
5111 @code{kill-rectangle} on it. The region does not highlight as a
|
|
|
5112 rectangle, but the commands work just fine.
|
|
|
5113
|
|
|
5114 To actually sweep out rectangular regions with the mouse you can use
|
|
|
5115 @code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}.
|
|
|
5116 Then use rectangle commands.
|
|
|
5117
|
|
|
5118 You can also do the following to change default behavior to sweep out
|
|
|
5119 rectangular regions:
|
|
|
5120
|
|
|
5121 @lisp
|
|
|
5122 (setq mouse-track-rectangle-p t)
|
|
|
5123 @end lisp
|
|
|
5124
|
|
2459
|
5125 You can also change this with Customize.
|
|
2417
|
5126 Select from the @code{Options} menu
|
|
|
5127 @code{Advanced (Customize)->Emacs->Editing->Mouse->Track Rectangle...} or type
|
|
|
5128 @kbd{M-x customize @key{RET} mouse @key{RET}}.
|
|
|
5129
|
|
|
5130
|
|
|
5131 @example
|
|
|
5132 mouse-track-do-rectangle: (event)
|
|
|
5133 -- an interactive compiled Lisp function.
|
|
|
5134 Like `mouse-track' but selects rectangles instead of regions.
|
|
|
5135 @end example
|
|
|
5136
|
|
2459
|
5137 @node Q3.3.2, Q3.3.3, Q3.3.1, Editing
|
|
|
5138 @unnumberedsubsec Q3.3.2: How can I turn off or change highlighted selections?
|
|
428
|
5139
|
|
|
5140 The @code{zmacs} mode allows for what some might call gratuitous
|
|
|
5141 highlighting for selected regions (either by setting mark or by using
|
|
|
5142 the mouse). This is the default behavior. To turn off, add the
|
|
2417
|
5143 following line to your @file{init.el} file:
|
|
428
|
5144
|
|
|
5145 @lisp
|
|
|
5146 (setq zmacs-regions nil)
|
|
|
5147 @end lisp
|
|
|
5148
|
|
2417
|
5149 You can also change this with Customize. Select from the
|
|
|
5150 @code{Options} menu
|
|
|
5151 @code{Advanced (Customize)->Emacs->Editing->Basics->Zmacs Regions}
|
|
|
5152 or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
|
|
|
5153
|
|
|
5154 To change the face for selection, look at @code{Options->Advanced (Customize)}
|
|
|
5155 on the menubar.
|
|
|
5156
|
|
2459
|
5157 @node Q3.3.3, Q3.3.4, Q3.3.2, Editing
|
|
|
5158 @unnumberedsubsec Q3.3.3: How do I cause typing on an active region to remove it?
|
|
428
|
5159
|
|
|
5160 I want to change things so that if I select some text and start typing,
|
|
|
5161 the typed text replaces the selected text, similar to Motif.
|
|
|
5162
|
|
|
5163 You want to use something called @dfn{pending delete}. Pending delete
|
|
|
5164 is what happens when you select a region (with the mouse or keyboard)
|
|
|
5165 and you press a key to replace the selected region by the key you typed.
|
|
|
5166 Usually backspace kills the selected region.
|
|
|
5167
|
|
2164
|
5168 To get this behavior, ensure that you have the @file{pc} package
|
|
|
5169 installed, and add the following lines to your
|
|
2417
|
5170 @file{init.el}:
|
|
428
|
5171
|
|
|
5172 @lisp
|
|
438
|
5173 (cond
|
|
|
5174 ((fboundp 'turn-on-pending-delete)
|
|
|
5175 (turn-on-pending-delete))
|
|
|
5176 ((fboundp 'pending-delete-on)
|
|
|
5177 (pending-delete-on t)))
|
|
428
|
5178 @end lisp
|
|
|
5179
|
|
1138
|
5180 Note that this will work with both Backspace and Delete. This code is a
|
|
438
|
5181 tad more complicated than it has to be for XEmacs in order to make it
|
|
|
5182 more portable.
|
|
428
|
5183
|
|
2459
|
5184 @node Q3.3.4, Q3.3.5, Q3.3.3, Editing
|
|
|
5185 @unnumberedsubsec Q3.3.4: Can I turn off the highlight during isearch?
|
|
428
|
5186
|
|
|
5187 I do not like my text highlighted while I am doing isearch as I am not
|
|
|
5188 able to see what's underneath. How do I turn it off?
|
|
|
5189
|
|
2417
|
5190 Put the following in your @file{init.el}:
|
|
428
|
5191
|
|
|
5192 @lisp
|
|
|
5193 (setq isearch-highlight nil)
|
|
|
5194 @end lisp
|
|
|
5195
|
|
2459
|
5196 You can also change this with Customize. Type
|
|
428
|
5197 @kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}.
|
|
|
5198
|
|
|
5199 Note also that isearch-highlight affects query-replace and ispell.
|
|
|
5200 Instead of disabling isearch-highlight you may find that a better
|
|
|
5201 solution consists of customizing the @code{isearch} face.
|
|
|
5202
|
|
2459
|
5203 @node Q3.3.5, Q3.3.6, Q3.3.4, Editing
|
|
|
5204 @unnumberedsubsec Q3.3.5: Why is killing so slow?
|
|
892
|
5205
|
|
|
5206 This actually is an X Windows question, although you'll notice it with
|
|
|
5207 keyboard operations as well as while using the GUI. Basically, there
|
|
|
5208 are four ways to communicate interprogram via the X server:
|
|
|
5209
|
|
|
5210 @table @strong
|
|
|
5211 @item Primary selection
|
|
|
5212 a transient selection that gets replaced every time a new selection is made
|
|
|
5213
|
|
|
5214 @item Secondary selection
|
|
|
5215 for "exchanging" with the primary selection
|
|
|
5216
|
|
|
5217 @item Cut buffers
|
|
|
5218 a clipboard internal to the X server (deprecated)
|
|
|
5219
|
|
|
5220 @item Clipboard selection
|
|
|
5221 a selection with a notification protocol that allows a separate app to
|
|
|
5222 manage the clipboard
|
|
|
5223 @end table
|
|
|
5224
|
|
|
5225 The cut buffers are deprecated because managing them is even more
|
|
|
5226 inefficient than the clipboard notification protocol. The primary
|
|
|
5227 selection works fine for many users and applications, but is not very
|
|
|
5228 robust under intensive or sophisticated use.
|
|
|
5229
|
|
|
5230 In Motif and MS Windows, a clipboard has become the primary means for
|
|
|
5231 managing cut and paste. These means that "modern" applications tend to
|
|
|
5232 be oriented toward a true clipboard, rather than the primary selection.
|
|
|
5233 (On Windows, there is nothing equivalent to the primary selection.)
|
|
|
5234 It's not that XEmacs doesn't support the simple primary selection
|
|
|
5235 method, it's that more and more other applications don't.
|
|
|
5236
|
|
|
5237 So the slowdown occurs because XEmacs now engages in the clipboard
|
|
|
5238 notification protocol on @emph{every} kill. This is especially slow on
|
|
|
5239 Motif.
|
|
|
5240
|
|
|
5241 With most people running most clients and server on the same host, and
|
|
|
5242 many of the rest working over very fast communication, you may expect
|
|
|
5243 that the situation is not going to improve.
|
|
|
5244
|
|
|
5245 There are a number of workarounds. The most effective is to use a
|
|
|
5246 special command to do selection ownership only when you intend to paste
|
|
|
5247 to another application. Useful commands are @code{kill-primary-selection}
|
|
|
5248 and @code{copy-primary-selection}. These work only on text selected
|
|
|
5249 with the mouse (probably; experiment), and are bound by default to the
|
|
|
5250 @kbd{Cut} and @kbd{Copy}, respectively, buttons on the toolbar.
|
|
|
5251 @code{copy-primary-selection} is also bound to @kbd{C-Insert}. You can
|
|
|
5252 yank the clipboard contents with @code{yank-primary-selection}, bound to
|
|
|
5253 the @kbd{Paste} toolbar button and @kbd{Sh-Insert}.
|
|
|
5254
|
|
|
5255 If you are communicating by cut and paste with applications that use the
|
|
|
5256 primary selection, then you can customize
|
|
|
5257 @code{interprogram-cut-function} to @code{nil}, restoring the XEmacs
|
|
|
5258 version 20 behavior. How can you tell if a program will support this?
|
|
|
5259 Motifly-correct programs require the clipboard; you lose. For others,
|
|
|
5260 only by trying it. You also need to customize the complementary
|
|
|
5261 @code{interprogram-paste-function} to @code{nil}. (Otherwise
|
|
|
5262 XEmacs-to-XEmacs pastes will not work correctly.)
|
|
|
5263
|
|
|
5264 You may get some relief on Motif by setting
|
|
|
5265 @code{x-selection-strict-motif-ownership} to nil, but this means you will
|
|
|
5266 only intermittently be able to paste XEmacs kills to Motif applications.
|
|
|
5267
|
|
|
5268 Thanks to Jeff Mincy and Glynn Clements for corrections.
|
|
|
5269
|
|
2459
|
5270 @node Q3.3.6, Q3.4.1, Q3.3.5, Editing
|
|
|
5271 @unnumberedsubsec Q3.3.6: Why does @kbd{M-w} take so long?
|
|
2417
|
5272
|
|
|
5273 It actually doesn't. It leaves the region visible for a second so that
|
|
|
5274 you can see what area is being yanked. If you start working, though, it
|
|
|
5275 will immediately complete its operation. In other words, it will only
|
|
|
5276 delay for a second if you let it.
|
|
|
5277
|
|
2459
|
5278 @unnumberedsec 3.4: Editing Source Code
|
|
|
5279
|
|
|
5280 @node Q3.4.1, Q3.4.2, Q3.3.6, Editing
|
|
|
5281 @unnumberedsubsec Q3.4.1: I do not like cc-mode. How do I use the old c-mode?
|
|
2417
|
5282
|
|
|
5283 Well, first off, consider if you really want to do this. cc-mode is
|
|
|
5284 much more powerful than the old c-mode. If you're having trouble
|
|
|
5285 getting your old offsets to work, try using @code{c-set-offset} instead.
|
|
|
5286 You might also consider using the package @code{cc-compat}.
|
|
|
5287
|
|
|
5288 But, if you still insist, add the following lines to your @file{init.el}:
|
|
|
5289
|
|
|
5290 @lisp
|
|
|
5291 (fmakunbound 'c-mode)
|
|
|
5292 (makunbound 'c-mode-map)
|
|
|
5293 (fmakunbound 'c++-mode)
|
|
|
5294 (makunbound 'c++-mode-map)
|
|
|
5295 (makunbound 'c-style-alist)
|
|
|
5296 (load-library "old-c-mode")
|
|
|
5297 (load-library "old-c++-mode")
|
|
|
5298 @end lisp
|
|
|
5299
|
|
|
5300 This must be done before any other reference is made to either c-mode or
|
|
|
5301 c++-mode.
|
|
|
5302
|
|
2459
|
5303 @node Q3.4.2, , Q3.4.1, Editing
|
|
|
5304 @unnumberedsubsec Q3.4.2: How do you make XEmacs indent CL if-clauses correctly?
|
|
2417
|
5305
|
|
|
5306 I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the
|
|
|
5307 same amount instead of indenting the 3rd clause differently from the
|
|
|
5308 first two.
|
|
|
5309
|
|
2459
|
5310 The package @code{cl-indent} that comes with XEmacs sets up this kind
|
|
|
5311 of indentation by default. @code{cl-indent} also knows about many
|
|
|
5312 other CL-specific forms. To use @code{cl-indent}, one can do this:
|
|
2417
|
5313
|
|
|
5314 @lisp
|
|
2459
|
5315 (setq lisp-indent-function 'common-lisp-indent-function)
|
|
2417
|
5316 @end lisp
|
|
|
5317
|
|
|
5318 One can also customize @file{cl-indent.el} so it mimics the default
|
|
|
5319 @code{if} indentation @code{then} indented more than the @code{else}.
|
|
|
5320 Here's how:
|
|
|
5321
|
|
|
5322 @lisp
|
|
|
5323 (put 'if 'common-lisp-indent-function '(nil nil &body))
|
|
|
5324 @end lisp
|
|
|
5325
|
|
2459
|
5326 @node Display, External Subsystems, Editing, Top
|
|
|
5327 @unnumbered 4 Display Functions
|
|
428
|
5328
|
|
|
5329 This is part 4 of the XEmacs Frequently Asked Questions list. This
|
|
2459
|
5330 section is devoted to the display-related capabilities of XEmacs
|
|
|
5331 (fonts, colors, modeline, menubar, toolbar, scrollbar, etc.) and how
|
|
|
5332 to customize them.
|
|
|
5333
|
|
|
5334 @menu
|
|
|
5335 4.0: Textual Fonts and Colors
|
|
|
5336 * Q4.0.1:: How do I specify a font?
|
|
|
5337 * Q4.0.2:: How do I set the text, menu and modeline fonts?
|
|
|
5338 * Q4.0.3:: How can I set color options from @file{init.el}?
|
|
|
5339 * Q4.0.4:: How can I set the colors when highlighting a region?
|
|
|
5340 * Q4.0.5:: How can I limit color map usage?
|
|
|
5341 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them.
|
|
|
5342 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs?
|
|
|
5343 * Q4.0.8:: How do I display non-ASCII characters?
|
|
|
5344 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}.
|
|
|
5345
|
|
|
5346 4.1: Syntax Highlighting (Font Lock)
|
|
|
5347 * Q4.1.1:: How can I do source code highlighting using font-lock?
|
|
|
5348 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
5349
|
|
|
5350 4.2: The Modeline
|
|
|
5351 * Q4.2.1:: How can I make the modeline go away?
|
|
|
5352 * Q4.2.2:: How do you have XEmacs display the line number in the modeline?
|
|
|
5353 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline?
|
|
|
5354 * Q4.2.4:: How can I change the modeline color based on the mode used?
|
|
|
5355
|
|
|
5356 4.3: The Cursor
|
|
|
5357 * Q4.3.1:: Is there a way to make the bar cursor thicker?
|
|
|
5358 * Q4.3.2:: Is there a way to get back the block cursor?
|
|
|
5359 * Q4.3.3:: Can I make the cursor blink?
|
|
|
5360
|
|
|
5361 4.4: The Menubar
|
|
|
5362 * Q4.4.1:: How do I get rid of the menubar?
|
|
|
5363 * Q4.4.2:: How can I customize the menubar?
|
|
|
5364 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
5365 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
5366 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
5367
|
|
|
5368 4.5: The Toolbar
|
|
|
5369 * Q4.5.1:: How do I get rid of the toolbar?
|
|
|
5370 * Q4.5.2:: How can I customize the toolbar?
|
|
|
5371 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar?
|
|
|
5372 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar
|
|
|
5373
|
|
|
5374 4.6: Scrollbars and Scrolling
|
|
|
5375 * Q4.6.1:: How can I disable the scrollbar?
|
|
|
5376 * Q4.6.2:: How can I change the scrollbar width?
|
|
|
5377 * Q4.6.3:: How can I use resources to change scrollbar colors?
|
|
|
5378 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this?
|
|
|
5379 * Q4.6.5:: Scrolling one line at a time.
|
|
|
5380 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
5381 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
5382
|
|
|
5383 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
5384 * Q4.7.1:: How can I disable the gutter tabs?
|
|
|
5385 * Q4.7.2:: How can I disable the progress bar?
|
|
|
5386 * Q4.7.3:: There are bugs in the gutter or widgets.
|
|
|
5387 * Q4.7.4:: How can I customize the gutter or gutter tabs?
|
|
|
5388 @end menu
|
|
|
5389
|
|
|
5390 @unnumberedsec 4.0: Textual Fonts and Colors
|
|
|
5391
|
|
|
5392 @node Q4.0.1, Q4.0.2, Display, Display
|
|
|
5393 @unnumberedsubsec Q4.0.1: How do I specify a font?
|
|
|
5394
|
|
|
5395 #### Update me.
|
|
|
5396
|
|
|
5397 In 21.4 and above, you can use the @samp{Options} menu to change the font.
|
|
|
5398 You can also do it in your init file, e.g. like this (for MS Windows):
|
|
|
5399
|
|
|
5400 @display
|
|
|
5401 (set-face-font 'default "Lucida Console:Regular:10")
|
|
|
5402 (set-face-font 'modeline "MS Sans Serif:Regular:10")
|
|
|
5403 @end display
|
|
|
5404
|
|
|
5405 @node Q4.0.2, Q4.0.3, Q4.0.1, Display
|
|
|
5406 @unnumberedsubsec Q4.0.2: How do I set the text, menu and modeline fonts?
|
|
|
5407
|
|
|
5408 #### Update me.
|
|
|
5409
|
|
|
5410 Note that you should use @samp{Emacs.} and not @samp{Emacs*} when
|
|
|
5411 setting face values.
|
|
|
5412
|
|
|
5413 In @file{.Xresources}:
|
|
|
5414
|
|
|
5415 @example
|
|
|
5416 Emacs.default.attributeFont: -*-*-medium-r-*-*-*-120-*-*-m-*-*-*
|
|
|
5417 Emacs*menubar*font: fixed
|
|
|
5418 Emacs.modeline.attributeFont: fixed
|
|
|
5419 @end example
|
|
|
5420
|
|
|
5421 This is confusing because @samp{default} and @samp{modeline} are face
|
|
|
5422 names, and can be found listed with all faces in the current mode by
|
|
|
5423 using @kbd{M-x set-face-font (enter) ?}. They use the face-specific
|
|
|
5424 resource @samp{attributeFont}.
|
|
|
5425
|
|
|
5426 On the other hand, @samp{menubar} is a normal X thing that uses the
|
|
|
5427 resource @samp{font}. With Motif it @emph{may be} necessary to use
|
|
|
5428 @samp{fontList} @emph{instead of} @samp{font}. In @emph{non-Motif}
|
|
|
5429 configurations with Mule it @emph{is} necessary to use @samp{fontSet}
|
|
|
5430 instead of @samp{font}. (Sorry, there just is no simple recipe here.)
|
|
|
5431
|
|
|
5432 @node Q4.0.3, Q4.0.4, Q4.0.2, Display
|
|
|
5433 @unnumberedsubsec Q4.0.3: How can I set color options from @file{init.el}?
|
|
|
5434
|
|
|
5435 How can I set the most commonly used color options from my
|
|
|
5436 @file{init.el} instead of from my @file{.Xresources}?
|
|
|
5437
|
|
|
5438 Like this:
|
|
|
5439
|
|
|
5440 @lisp
|
|
|
5441 (set-face-background 'default "bisque") ; frame background
|
|
|
5442 (set-face-foreground 'default "black") ; normal text
|
|
|
5443 (set-face-background 'zmacs-region "red") ; When selecting w/
|
|
|
5444 ; mouse
|
|
|
5445 (set-face-foreground 'zmacs-region "yellow")
|
|
|
5446 (set-face-font 'default "*courier-bold-r*120-100-100*")
|
|
|
5447 (set-face-background 'highlight "blue") ; Ie when selecting
|
|
|
5448 ; buffers
|
|
|
5449 (set-face-foreground 'highlight "yellow")
|
|
|
5450 (set-face-background 'modeline "blue") ; Line at bottom
|
|
|
5451 ; of buffer
|
|
|
5452 (set-face-foreground 'modeline "white")
|
|
|
5453 (set-face-font 'modeline "*bold-r-normal*140-100-100*")
|
|
|
5454 (set-face-background 'isearch "yellow") ; When highlighting
|
|
|
5455 ; while searching
|
|
|
5456 (set-face-foreground 'isearch "red")
|
|
|
5457 (setq x-pointer-foreground-color "black") ; Adds to bg color,
|
|
|
5458 ; so keep black
|
|
|
5459 (setq x-pointer-background-color "blue") ; This is color
|
|
|
5460 ; you really
|
|
|
5461 ; want ptr/crsr
|
|
|
5462 @end lisp
|
|
|
5463
|
|
|
5464 @node Q4.0.4, Q4.0.5, Q4.0.3, Display
|
|
|
5465 @unnumberedsubsec Q4.0.4: How can I set the colors when highlighting a region?
|
|
|
5466
|
|
|
5467 How can I set the background/foreground colors when highlighting a
|
|
|
5468 region?
|
|
|
5469
|
|
|
5470 You can change the face @code{zmacs-region} either in your
|
|
|
5471 @file{.Xresources}:
|
|
|
5472
|
|
|
5473 @example
|
|
|
5474 Emacs.zmacs-region.attributeForeground: firebrick
|
|
|
5475 Emacs.zmacs-region.attributeBackground: lightseagreen
|
|
|
5476 @end example
|
|
|
5477
|
|
|
5478 or in your @file{init.el}:
|
|
|
5479
|
|
|
5480 @lisp
|
|
|
5481 (set-face-background 'zmacs-region "red")
|
|
|
5482 (set-face-foreground 'zmacs-region "yellow")
|
|
|
5483 @end lisp
|
|
|
5484
|
|
|
5485 @node Q4.0.5, Q4.0.6, Q4.0.4, Display
|
|
|
5486 @unnumberedsubsec Q4.0.5: How can I limit color map usage?
|
|
|
5487
|
|
|
5488 I'm using Netscape (or another color grabber like XEmacs);
|
|
|
5489 is there any way to limit the number of available colors in the color map?
|
|
|
5490
|
|
|
5491 Answer: No, but you can start Netscape before XEmacs, and it will use
|
|
|
5492 the closest available color if the colormap is full. You can also limit
|
|
|
5493 the number of colors Netscape uses, using the flags -mono, -ncols <#> or
|
|
|
5494 -install (for mono, limiting to <#> colors, or for using a private color
|
|
|
5495 map).
|
|
|
5496
|
|
|
5497 If you have the money, another solution would be to use a truecolor or
|
|
|
5498 direct color video.
|
|
|
5499
|
|
|
5500 @node Q4.0.6, Q4.0.7, Q4.0.5, Display
|
|
|
5501 @unnumberedsubsec Q4.0.6: My tty supports color, but XEmacs doesn't use them.
|
|
|
5502
|
|
|
5503 XEmacs tries to automatically determine whether your tty supports color,
|
|
|
5504 but sometimes guesses wrong. In that case, you can make XEmacs Do The
|
|
|
5505 Right Thing using this Lisp code:
|
|
|
5506
|
|
|
5507 @lisp
|
|
|
5508 (if (eq 'tty (device-type))
|
|
|
5509 (set-device-class nil 'color))
|
|
|
5510 @end lisp
|
|
|
5511
|
|
|
5512 @node Q4.0.7, Q4.0.8, Q4.0.6, Display
|
|
|
5513 @unnumberedsubsec Q4.0.7: Can I have pixmap backgrounds in XEmacs?
|
|
|
5514 @c New
|
|
|
5515 @email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes:
|
|
|
5516
|
|
|
5517 @quotation
|
|
|
5518 There are several ways to do it. For example, you could specify a
|
|
|
5519 default pixmap image to use in your @file{~/.Xresources}, e.g.,
|
|
|
5520
|
|
|
5521
|
|
|
5522 @example
|
|
|
5523 Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm
|
|
|
5524 @end example
|
|
|
5525
|
|
|
5526
|
|
|
5527 and then reload ~/.Xresources and restart XEmacs. Alternatively,
|
|
|
5528 since each face can have its own pixmap background, a better way
|
|
|
5529 would be to set a face's pixmap within your XEmacs init file, e.g.,
|
|
|
5530
|
|
|
5531 @lisp
|
|
|
5532 (set-face-background-pixmap 'default "/path/to/image.xpm")
|
|
|
5533 (set-face-background-pixmap 'bold "/path/to/another_image.xpm")
|
|
|
5534 @end lisp
|
|
|
5535
|
|
|
5536 and so on. You can also do this interactively via @kbd{M-x edit-faces}.
|
|
|
5537
|
|
|
5538 @end quotation
|
|
|
5539
|
|
|
5540 @node Q4.0.8, Q4.0.9, Q4.0.7, Display
|
|
|
5541 @unnumberedsubsec Q4.0.8: How do I display non-ASCII characters?
|
|
|
5542 @c New
|
|
|
5543
|
|
|
5544 If you're using a Mule-enabled XEmacs, then display is automatic. If
|
|
|
5545 you're not seeing the characters you expect, either (1) you don't have
|
|
|
5546 appropriate fonts available or (2) XEmacs did not correctly detect the
|
|
|
5547 coding system (@pxref{Recognize Coding, , , xemacs}). In case (1),
|
|
|
5548 install fonts as is customary for your platform. In case (2), you
|
|
|
5549 need to tell XEmacs explicitly what coding systems you're using.
|
|
|
5550 @ref{Specify Coding, , , xemacs}.
|
|
|
5551
|
|
|
5552 If your XEmacs is not Mule-enabled, and for some reason getting a
|
|
|
5553 Mule-enabled XEmacs seems like the wrong thing to do, all is not lost.
|
|
|
5554 You can arrange it by brute force. In @file{event-Xt.c} (suppress the
|
|
|
5555 urge to look in this file---play Doom instead, because you'll survive
|
|
|
5556 longer), it is written:
|
|
|
5557
|
|
|
5558 @quotation
|
|
|
5559 In a non-Mule world, a user can still have a multi-lingual editor, by
|
|
|
5560 doing @code{(set-face-font "-*-iso8859-2" (current-buffer))} for all
|
|
|
5561 their Latin-2 buffers, etc.
|
|
|
5562 @end quotation
|
|
|
5563
|
|
|
5564 For the related problem of @emph{inputting} non-ASCII characters in a
|
|
|
5565 non-Mule XEmacs, @xref{Q3.0.6, How can you type in special characters
|
|
|
5566 in XEmacs?}.
|
|
|
5567
|
|
|
5568 @node Q4.0.9, Q4.1.1, Q4.0.8, Display
|
|
|
5569 @unnumberedsubsec Q4.0.9: Font selections in don't get saved after @code{Save Options}.
|
|
|
5570
|
|
|
5571 @email{mannj@@ll.mit.edu, John Mann} writes:
|
|
|
5572
|
|
|
5573 @quotation
|
|
|
5574 You have to go to @samp{Options->Menubars} and unselect
|
|
|
5575 @samp{Frame-Local Font Menu}. If this option is selected, font changes
|
|
|
5576 are only applied to the @emph{current} frame and do @emph{not} get saved
|
|
|
5577 when you save options.
|
|
|
5578 @end quotation
|
|
|
5579
|
|
|
5580 Also, set the following in your @file{init.el}:
|
|
|
5581
|
|
|
5582 @lisp
|
|
|
5583 (setq options-save-faces t)
|
|
|
5584 @end lisp
|
|
|
5585
|
|
|
5586 @unnumberedsec 4.1: Syntax Highlighting (Font Lock)
|
|
|
5587
|
|
|
5588 @node Q4.1.1, Q4.1.2, Q4.0.9, Display
|
|
|
5589 @unnumberedsubsec Q4.1.1: How can I do source code highlighting using font-lock?
|
|
|
5590
|
|
|
5591 For most modes, font-lock is already set up and just needs to be turned
|
|
|
5592 on. This can be done by adding the line:
|
|
|
5593
|
|
|
5594 @lisp
|
|
|
5595 (require 'font-lock)
|
|
|
5596 @end lisp
|
|
|
5597
|
|
|
5598 to your @file{init.el}. (You can turn it on for the
|
|
|
5599 current buffer and session only by @kbd{M-x font-lock-mode}.) See the
|
|
|
5600 file @file{etc/sample.init.el} (@file{etc/sample.emacs} in XEmacs
|
|
|
5601 versions prior to 21.4) for more information.
|
|
|
5602
|
|
|
5603 @c the old way:
|
|
|
5604 @c (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
|
|
|
5605 @c (add-hook 'dired-mode-hook 'turn-on-font-lock)
|
|
|
5606
|
|
|
5607 See also @code{Syntax Highlighting} from the @code{Options} menu.
|
|
|
5608 Remember to save options.
|
|
|
5609
|
|
|
5610 @node Q4.1.2, Q4.2.1, Q4.1.1, Display
|
|
|
5611 @unnumberedsubsec Q4.1.2: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
5612
|
|
|
5613 Use the following code in your @file{init.el}:
|
|
|
5614
|
|
|
5615 @lisp
|
|
|
5616 (setq-default font-lock-maximum-decoration t)
|
|
|
5617 @end lisp
|
|
|
5618
|
|
|
5619 See also @code{Syntax Highlighting} from the @code{Options} menu.
|
|
|
5620 Remember to save options.
|
|
|
5621
|
|
|
5622 @unnumberedsec 4.2: The Modeline
|
|
|
5623
|
|
|
5624 @node Q4.2.1, Q4.2.2, Q4.1.2, Display
|
|
|
5625 @unnumberedsubsec Q4.2.1: How can I make the modeline go away?
|
|
|
5626
|
|
|
5627 @lisp
|
|
|
5628 (set-specifier has-modeline-p nil)
|
|
|
5629 @end lisp
|
|
|
5630
|
|
|
5631 @node Q4.2.2, Q4.2.3, Q4.2.1, Display
|
|
|
5632 @unnumberedsubsec Q4.2.2: How do you have XEmacs display the line number in the modeline?
|
|
|
5633
|
|
|
5634 Add the following line to your @file{init.el} file to
|
|
|
5635 display the line number:
|
|
|
5636
|
|
|
5637 @lisp
|
|
|
5638 (line-number-mode 1)
|
|
|
5639 @end lisp
|
|
|
5640
|
|
|
5641 Use the following to display the column number:
|
|
|
5642
|
|
|
5643 @lisp
|
|
|
5644 (column-number-mode 1)
|
|
|
5645 @end lisp
|
|
|
5646
|
|
|
5647 Or select from the @code{Options} menu
|
|
|
5648 @iftex
|
|
|
5649 @*
|
|
|
5650 @end iftex
|
|
|
5651 @code{Advanced (Customize)->Emacs->Editing->Basics->Line Number Mode}
|
|
|
5652 and/or
|
|
|
5653 @iftex
|
|
|
5654 @*
|
|
|
5655 @end iftex
|
|
|
5656 @code{Advanced (Customize)->Emacs->Editing->Basics->Column Number Mode}
|
|
|
5657
|
|
|
5658 Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
|
|
|
5659
|
|
|
5660 @node Q4.2.3, Q4.2.4, Q4.2.2, Display
|
|
|
5661 @unnumberedsubsec Q4.2.3: How do I get XEmacs to put the time of day on the modeline?
|
|
|
5662
|
|
|
5663 Add the following line to your @file{init.el} file to
|
|
|
5664 display the time:
|
|
|
5665
|
|
|
5666 @lisp
|
|
|
5667 (display-time)
|
|
|
5668 @end lisp
|
|
|
5669
|
|
|
5670 See @code{Customize} from the @code{Options} menu for customization.
|
|
|
5671
|
|
|
5672 @node Q4.2.4, Q4.3.1, Q4.2.3, Display
|
|
|
5673 @unnumberedsubsec Q4.2.4: How can I change the modeline color based on the mode used?
|
|
|
5674
|
|
|
5675 You can use something like the following:
|
|
|
5676
|
|
|
5677 @lisp
|
|
|
5678 (add-hook 'lisp-mode-hook
|
|
|
5679 (lambda ()
|
|
|
5680 (set-face-background 'modeline "red" (current-buffer))))
|
|
|
5681 @end lisp
|
|
|
5682
|
|
|
5683 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
|
|
|
5684 colors change from the default set in your @file{init.el}.
|
|
|
5685 The change will only be made in the buffer you just entered (which
|
|
|
5686 contains the Lisp file you are editing) and will not affect the modeline
|
|
|
5687 colors anywhere else.
|
|
|
5688
|
|
|
5689 Notes:
|
|
|
5690
|
|
|
5691 @itemize @bullet
|
|
|
5692
|
|
|
5693 @item The hook is the mode name plus @code{-hook}. eg. c-mode-hook,
|
|
|
5694 c++-mode-hook, emacs-lisp-mode-hook (used for your
|
|
|
5695 @file{init.el} or a @file{xx.el} file),
|
|
|
5696 lisp-interaction-mode-hook (the @samp{*scratch*} buffer),
|
|
|
5697 text-mode-hook, etc.
|
|
|
5698
|
|
|
5699 @item
|
|
|
5700 Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)},
|
|
|
5701 otherwise you will erase anything that anybody has already put on the
|
|
|
5702 hook.
|
|
|
5703
|
|
|
5704 @item
|
|
|
5705 You can also do @code{(set-face-font 'modeline @var{font})},
|
|
|
5706 eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*"
|
|
|
5707 (current-buffer))} if you wish the modeline font to vary based on the
|
|
|
5708 current mode.
|
|
|
5709 @end itemize
|
|
|
5710
|
|
|
5711 There are additional modeline faces, @code{modeline-buffer-id},
|
|
|
5712 @code{modeline-mousable}, and @code{modeline-mousable-minor-mode}, which
|
|
|
5713 you may want to customize.
|
|
|
5714
|
|
|
5715 @unnumberedsec 4.3: The Cursor
|
|
|
5716
|
|
|
5717 @node Q4.3.1, Q4.3.2, Q4.2.4, Display
|
|
|
5718 @unnumberedsubsec Q4.3.1: Is there a way to make the bar cursor thicker?
|
|
|
5719
|
|
|
5720 I'd like to have the bar cursor a little thicker, as I tend to "lose" it
|
|
|
5721 often.
|
|
|
5722
|
|
|
5723 For a 1 pixel bar cursor, use:
|
|
|
5724
|
|
|
5725 @lisp
|
|
|
5726 (setq bar-cursor t)
|
|
|
5727 @end lisp
|
|
|
5728
|
|
|
5729 For a 2 pixel bar cursor, use:
|
|
|
5730
|
|
|
5731 @lisp
|
|
|
5732 (setq bar-cursor 'anything-else)
|
|
|
5733 @end lisp
|
|
|
5734
|
|
|
5735 You can also change these with Customize.
|
|
|
5736 Select from the @code{Options} menu
|
|
|
5737 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
|
|
|
5738 @kbd{M-x customize @key{RET} display @key{RET}}.
|
|
|
5739
|
|
|
5740 You can use a color to make it stand out better:
|
|
|
5741
|
|
|
5742 @example
|
|
|
5743 Emacs*cursorColor: Red
|
|
|
5744 @end example
|
|
|
5745
|
|
|
5746 @node Q4.3.2, Q4.3.3, Q4.3.1, Display
|
|
|
5747 @unnumberedsubsec Q4.3.2: Is there a way to get back the block cursor?
|
|
|
5748
|
|
|
5749 @lisp
|
|
|
5750 (setq bar-cursor nil)
|
|
|
5751 @end lisp
|
|
|
5752
|
|
|
5753 You can also change this with Customize.
|
|
|
5754 Select from the @code{Options} menu
|
|
|
5755 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
|
|
|
5756 @kbd{M-x customize @key{RET} display @key{RET}}.
|
|
|
5757
|
|
|
5758 @node Q4.3.3, Q4.4.1, Q4.3.2, Display
|
|
|
5759 @unnumberedsubsec Q4.3.3: Can I make the cursor blink?
|
|
|
5760
|
|
|
5761 Yes, like this:
|
|
|
5762
|
|
|
5763 @lisp
|
|
|
5764 (blink-cursor-mode)
|
|
|
5765 @end lisp
|
|
|
5766
|
|
|
5767 This function toggles between a steady cursor and a blinking cursor.
|
|
|
5768 You may also set this mode from the menu bar by selecting
|
|
|
5769 @samp{Options->Display->Blinking Cursor}. Remember to save options.
|
|
|
5770
|
|
|
5771 @unnumberedsec 4.4: The Menubar
|
|
|
5772
|
|
|
5773 @node Q4.4.1, Q4.4.2, Q4.3.3, Display
|
|
|
5774 @unnumberedsubsec Q4.4.1: How do I get rid of the menubar?
|
|
|
5775
|
|
|
5776 @lisp
|
|
|
5777 (set-specifier menubar-visible-p nil)
|
|
|
5778 @end lisp
|
|
|
5779
|
|
|
5780 @node Q4.4.2, Q4.4.3, Q4.4.1, Display
|
|
|
5781 @unnumberedsubsec Q4.4.2: How can I customize the menubar?
|
|
|
5782
|
|
|
5783 For an extensive menubar, add this line to your @file{init.el}:
|
|
|
5784
|
|
|
5785 @lisp
|
|
|
5786 (load "big-menubar")
|
|
|
5787 @end lisp
|
|
|
5788
|
|
|
5789 If you'd like to write your own, this file provides as good a set of
|
|
|
5790 examples as any to start from. The file is located in edit-utils
|
|
|
5791 package.
|
|
|
5792
|
|
|
5793 @node Q4.4.3, Q4.4.4, Q4.4.2, Display
|
|
|
5794 @unnumberedsubsec Q4.4.3: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
5795
|
|
|
5796 #### Write me.
|
|
|
5797
|
|
|
5798 @node Q4.4.4, Q4.4.5, Q4.4.3, Display
|
|
|
5799 @unnumberedsubsec Q4.4.4: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
5800
|
|
|
5801 Add the following to your @file{init.el} (suit to fit):
|
|
|
5802
|
|
|
5803 @lisp
|
|
|
5804 (setq buffers-menu-max-size 20)
|
|
|
5805 @end lisp
|
|
|
5806
|
|
|
5807 For no limit, use an argument of @samp{nil}.
|
|
|
5808
|
|
|
5809 You can also change this with Customize. Select from the
|
|
|
5810 @code{Options} menu
|
|
|
5811 @code{Advanced (Customize)->Emacs->Environment->Menu->Buffers Menu->Max Size...}
|
|
|
5812 or type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}.
|
|
|
5813
|
|
|
5814 @node Q4.4.5, Q4.5.1, Q4.4.4, Display
|
|
|
5815 @unnumberedsubsec Q4.4.5: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
5816
|
|
|
5817 I am trying to use a resource like @code{Emacs*menubar*font} to set the
|
|
|
5818 font of the menubar but it's not working.
|
|
|
5819
|
|
|
5820 In Motif, the use of @samp{font} resources is obsoleted in order to
|
|
|
5821 support internationalization. If you are using the real Motif menubar,
|
|
|
5822 this resource is not recognized at all; you have to say:
|
|
|
5823
|
|
|
5824 @example
|
|
|
5825 Emacs*menubar*fontList: FONT
|
|
|
5826 @end example
|
|
|
5827
|
|
|
5828 If you are using the Lucid menubar, for backward compatibility with
|
|
|
5829 existing user configurations, the @samp{font} resource is recognized.
|
|
|
5830 Since this is not supported by Motif itself, the code is a kludge and
|
|
|
5831 the @samp{font} resource will be recognized only if the @samp{fontList}
|
|
|
5832 resource resource is unset. This means that the resource
|
|
|
5833
|
|
|
5834 @example
|
|
|
5835 *fontList: FONT
|
|
|
5836 @end example
|
|
|
5837
|
|
|
5838 will override
|
|
|
5839
|
|
|
5840 @example
|
|
|
5841 Emacs*menubar*font: FONT
|
|
|
5842 @end example
|
|
|
5843
|
|
|
5844 even though the latter is more specific.
|
|
|
5845
|
|
|
5846 In non-Motif configurations using @samp{--with-mule} and
|
|
|
5847 @samp{--with-xfs} it @emph{is} necessary to use the @code{fontSet}
|
|
|
5848 resource @emph{instead of} the @code{font} resource. The backward
|
|
|
5849 compatibility kludge was never implemented for non-Motif builds.
|
|
|
5850 Example:
|
|
|
5851
|
|
|
5852 @example
|
|
|
5853 *fontSet: FONT
|
|
|
5854 @end example
|
|
|
5855
|
|
|
5856 @unnumberedsec 4.5: The Toolbar
|
|
|
5857
|
|
|
5858 @node Q4.5.1, Q4.5.2, Q4.4.5, Display
|
|
|
5859 @unnumberedsubsec Q4.5.1: How do I get rid of the toolbar?
|
|
|
5860
|
|
|
5861 #### Write me.
|
|
|
5862
|
|
|
5863 @node Q4.5.2, Q4.5.3, Q4.5.1, Display
|
|
|
5864 @unnumberedsubsec Q4.5.2: How can I customize the toolbar?
|
|
|
5865
|
|
|
5866 #### Write me.
|
|
|
5867
|
|
|
5868 @node Q4.5.3, Q4.5.4, Q4.5.2, Display
|
|
|
5869 @unnumberedsubsec Q4.5.3: How can I bind a key to a function to toggle the toolbar?
|
|
|
5870
|
|
|
5871 Try something like:
|
|
|
5872
|
|
|
5873 @lisp
|
|
|
5874 (defun my-toggle-toolbar ()
|
|
|
5875 (interactive)
|
|
|
5876 (set-specifier default-toolbar-visible-p
|
|
|
5877 (not (specifier-instance default-toolbar-visible-p))))
|
|
|
5878 (global-set-key "\C-xT" 'my-toggle-toolbar)
|
|
|
5879 @end lisp
|
|
|
5880
|
|
|
5881 @ignore
|
|
|
5882 @c Probably not relevant any more
|
|
|
5883 There are redisplay bugs in 19.14 that may make the preceding result in
|
|
|
5884 a messed-up display, especially for frames with multiple windows. You
|
|
|
5885 may need to resize the frame before XEmacs completely realizes the
|
|
|
5886 toolbar is really gone.
|
|
|
5887 @end ignore
|
|
|
5888
|
|
|
5889 Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct
|
|
|
5890 code.
|
|
|
5891
|
|
|
5892 @node Q4.5.4, Q4.6.1, Q4.5.3, Display
|
|
|
5893 @unnumberedsubsec Q4.5.4: @samp{Can't instantiate image error...} in toolbar
|
|
|
5894
|
|
|
5895 @email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes:
|
|
|
5896
|
|
|
5897 I just installed the XEmacs (20.4-2) RPMS that I downloaded from
|
|
|
5898 @uref{http://www.xemacs.org/}. Everything works fine, except that when
|
|
|
5899 I place my mouse over the toolbar, it beeps and gives me this message:
|
|
|
5900
|
|
|
5901 @example
|
|
|
5902 Can't instantiate image (probably cached):
|
|
|
5903 [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data
|
|
|
5904 (16 16 <strange control characters> ...
|
|
|
5905 @end example
|
|
|
5906
|
|
|
5907 @email{kyle_jones@@wonderworks.com, Kyle Jones} writes:
|
|
|
5908 @quotation
|
|
|
5909 This is problem specific to some Chips and Technologies video
|
|
|
5910 chips, when running XFree86. Putting
|
|
|
5911
|
|
|
5912 @code{Option "sw_cursor"}
|
|
|
5913
|
|
|
5914 in @file{XF86Config} gets rid of the problem.
|
|
|
5915 @end quotation
|
|
|
5916
|
|
|
5917 @unnumberedsec 4.6: Scrollbars and Scrolling
|
|
|
5918
|
|
|
5919 @node Q4.6.1, Q4.6.2, Q4.5.4, Display
|
|
|
5920 @unnumberedsubsec Q4.6.1: How can I disable the scrollbar?
|
|
|
5921
|
|
|
5922 To disable them for all frames, add the following line to
|
|
|
5923 your @file{.Xresources}:
|
|
|
5924
|
|
|
5925 @example
|
|
|
5926 Emacs.scrollBarWidth: 0
|
|
|
5927 @end example
|
|
|
5928
|
|
|
5929 Or select @samp{Options->Display->Scrollbars}.
|
|
|
5930 Remember to save options.
|
|
|
5931
|
|
|
5932 To turn the scrollbar off on a per-frame basis, use the following
|
|
|
5933 function:
|
|
|
5934
|
|
|
5935 @lisp
|
|
|
5936 (set-specifier scrollbar-width 0 (selected-frame))
|
|
|
5937 @end lisp
|
|
|
5938
|
|
|
5939 You can actually turn the scrollbars on at any level you want by
|
|
|
5940 substituting for (selected-frame) in the above command. For example, to
|
|
|
5941 turn the scrollbars off only in a single buffer:
|
|
|
5942
|
|
|
5943 @lisp
|
|
|
5944 (set-specifier scrollbar-width 0 (current-buffer))
|
|
|
5945 @end lisp
|
|
|
5946
|
|
|
5947 @node Q4.6.2, Q4.6.3, Q4.6.1, Display
|
|
|
5948 @unnumberedsubsec Q4.6.2: How can I change the scrollbar width?
|
|
|
5949
|
|
|
5950 #### Write me.
|
|
|
5951
|
|
|
5952 @node Q4.6.3, Q4.6.4, Q4.6.2, Display
|
|
|
5953 @unnumberedsubsec Q4.6.3: How can I use resources to change scrollbar colors?
|
|
|
5954
|
|
|
5955 Here's a recap of how to use resources to change your scrollbar colors:
|
|
|
5956
|
|
|
5957 @example
|
|
|
5958 ! Motif scrollbars
|
|
|
5959
|
|
|
5960 Emacs*XmScrollBar.Background: skyblue
|
|
|
5961 Emacs*XmScrollBar.troughColor: lightgray
|
|
|
5962
|
|
|
5963 ! Athena scrollbars
|
|
|
5964
|
|
|
5965 Emacs*Scrollbar.Foreground: skyblue
|
|
|
5966 Emacs*Scrollbar.Background: lightgray
|
|
|
5967 @end example
|
|
|
5968
|
|
|
5969 Note the capitalization of @code{Scrollbar} for the Athena widget.
|
|
|
5970
|
|
|
5971 @node Q4.6.4, Q4.6.5, Q4.6.3, Display
|
|
|
5972 @unnumberedsubsec Q4.6.4: Moving the scrollbar can move the point; can I disable this?
|
|
|
5973
|
|
|
5974 When I move the scrollbar in an XEmacs window, it moves the point as
|
|
|
5975 well, which should not be the default behavior. Is this a bug or a
|
|
|
5976 feature? Can I disable it?
|
|
|
5977
|
|
|
5978 The current behavior is a feature, not a bug. Point remains at the same
|
|
|
5979 buffer position as long as that position does not scroll off the screen.
|
|
|
5980 In that event, point will end up in either the upper-left or lower-left
|
|
|
5981 hand corner.
|
|
|
5982
|
|
|
5983 This cannot be changed.
|
|
|
5984
|
|
|
5985 @node Q4.6.5, Q4.6.6, Q4.6.4, Display
|
|
|
5986 @unnumberedsubsec Q4.6.5: Scrolling one line at a time.
|
|
|
5987
|
|
|
5988 Can the cursor keys scroll the screen a line at a time, rather than the
|
|
|
5989 default half page jump? I tend it to find it disorienting.
|
|
|
5990
|
|
|
5991 Use the following:
|
|
|
5992
|
|
|
5993 @lisp
|
|
|
5994 (setq scroll-step 1)
|
|
|
5995 @end lisp
|
|
|
5996
|
|
|
5997 You can also change this with Customize. Select from the
|
|
|
5998 @code{Options} menu
|
|
|
5999 @code{Advanced (Customize)->Emacs->Environment->Windows->Scroll Step...}
|
|
|
6000 or type @kbd{M-x customize @key{RET} windows @key{RET}}.
|
|
|
6001
|
|
|
6002 @node Q4.6.6, Q4.6.7, Q4.6.5, Display
|
|
|
6003 @unnumberedsubsec Q4.6.6: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
6004
|
|
|
6005 Do @code{(setq truncate-lines t)} in the mode-hooks for any modes
|
|
|
6006 in which you want lines truncated.
|
|
|
6007
|
|
|
6008 More precisely: If @code{truncate-lines} is nil, horizontal scrollbars
|
|
|
6009 will never appear. Otherwise, they will appear only if the value of
|
|
|
6010 @code{scrollbar-height} for that buffer/window/etc. is non-zero. If you
|
|
|
6011 do
|
|
|
6012
|
|
|
6013 @lisp
|
|
|
6014 (set-specifier scrollbar-height 0)
|
|
|
6015 @end lisp
|
|
|
6016
|
|
|
6017 then horizontal scrollbars will not appear in truncated buffers unless
|
|
|
6018 the package specifically asked for them.
|
|
|
6019
|
|
|
6020 @node Q4.6.7, Q4.7.1, Q4.6.6, Display
|
|
|
6021 @unnumberedsubsec Q4.6.7: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
6022
|
|
|
6023 @code{auto-show-mode} controls whether or not a horizontal scrollbar
|
|
|
6024 magically appears when a line is too long to be displayed. This is
|
|
|
6025 enabled by default. To turn it off, put the following in your
|
|
|
6026 @file{init.el}:
|
|
|
6027
|
|
|
6028 @lisp
|
|
|
6029 (setq auto-show-mode nil)
|
|
|
6030 (setq-default auto-show-mode nil)
|
|
|
6031 @end lisp
|
|
|
6032
|
|
|
6033 @unnumberedsec 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
6034
|
|
|
6035 @node Q4.7.1, Q4.7.2, Q4.6.7, Display
|
|
|
6036 @unnumberedsubsec Q4.7.1: How can I disable the gutter tabs?
|
|
|
6037
|
|
|
6038 #### Write me.
|
|
|
6039
|
|
|
6040 @node Q4.7.2, Q4.7.3, Q4.7.1, Display
|
|
|
6041 @unnumberedsubsec Q4.7.2: How can I disable the progress bar?
|
|
|
6042
|
|
|
6043 #### Write me.
|
|
|
6044
|
|
|
6045 @node Q4.7.3, Q4.7.4, Q4.7.2, Display
|
|
|
6046 @unnumberedsubsec Q4.7.3: There are bugs in the gutter or widgets.
|
|
|
6047
|
|
|
6048 #### Write me.
|
|
|
6049
|
|
|
6050 @node Q4.7.4, , Q4.7.3, Display
|
|
|
6051 @unnumberedsubsec Q4.7.4: How can I customize the gutter or gutter tabs?
|
|
|
6052
|
|
|
6053 #### Write me.
|
|
|
6054
|
|
|
6055 @node External Subsystems, Internet, Display, Top
|
|
|
6056 @unnumbered 5 Interfacing with the Operating System and External Devices
|
|
|
6057
|
|
|
6058 This is part 5 of the XEmacs Frequently Asked Questions list. This
|
|
2417
|
6059 section is devoted to the various ways that XEmacs interfaces with the
|
|
|
6060 operating system, with other processes and with external devices such
|
|
|
6061 as speakers and the printer.
|
|
428
|
6062
|
|
|
6063 @menu
|
|
2459
|
6064 5.0: X Window System and Resources
|
|
|
6065 * Q5.0.1:: Where is a list of X resources?
|
|
|
6066 * Q5.0.2:: How can I detect a color display?
|
|
|
6067 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}?
|
|
|
6068 * Q5.0.4:: How can I have the window title area display the full path?
|
|
|
6069 * Q5.0.5:: @samp{xemacs -name junk} doesn't work?
|
|
|
6070 * Q5.0.6:: @samp{-iconic} doesn't work.
|
|
|
6071
|
|
|
6072 5.1: Microsoft Windows
|
|
|
6073 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
|
6074 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
|
6075
|
|
|
6076 5.2: Printing
|
|
|
6077 * Q5.2.1:: What do I need to change to make printing work?
|
|
|
6078 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer?
|
|
|
6079 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
|
6080 * Q5.2.4:: Can you print under MS Windows?
|
|
|
6081
|
|
|
6082 5.3: Sound
|
|
|
6083 * Q5.3.1:: How do I turn off the sound?
|
|
|
6084 * Q5.3.2:: How do I get funky sounds instead of a boring beep?
|
|
|
6085 * Q5.3.3:: What are NAS and ESD (EsounD)?
|
|
|
6086 * Q5.3.4:: Sunsite sounds don't play.
|
|
|
6087
|
|
|
6088 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
6089 * Q5.4.1:: What is an interior shell?
|
|
|
6090 * Q5.4.2:: How do I start up a second shell buffer?
|
|
|
6091 * Q5.4.3:: Telnet from shell filters too much
|
|
|
6092 * Q5.4.4:: Strange things are happening in Shell Mode.
|
|
|
6093 * Q5.4.5:: XEmacs complains "No such file or directory, diff"
|
|
|
6094
|
|
|
6095 5.5: Multiple Device Support
|
|
|
6096 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display?
|
|
|
6097 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
6098 * Q5.5.3:: How do I disable gnuserv from opening a new frame?
|
|
|
6099 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
|
6100 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
428
|
6101 @end menu
|
|
|
6102
|
|
2459
|
6103 @unnumberedsec 5.0: X Window System and Resources
|
|
|
6104
|
|
|
6105 @node Q5.0.1, Q5.0.2, External Subsystems, External Subsystems
|
|
|
6106 @unnumberedsubsec Q5.0.1: Where is a list of X resources?
|
|
2417
|
6107
|
|
|
6108 Search through the @file{NEWS} file for @samp{X Resources}. A fairly
|
|
|
6109 comprehensive list is given after it.
|
|
|
6110
|
|
|
6111 In addition, an @file{app-defaults} file @file{etc/Emacs.ad} is
|
|
|
6112 supplied, listing the defaults. The file @file{etc/sample.Xresources}
|
|
|
6113 gives a different set of defaults that you might consider for
|
|
|
6114 installation in your @file{~/.Xresources} file. It is nearly the same
|
|
|
6115 as @file{etc/Emacs.ad}, but a few entries are altered. Be careful about
|
|
|
6116 installing the contents of this file into your @file{.Xresources} (or
|
|
|
6117 legacy @file{.Xdefaults}) file if you use GNU Emacs under X11 as well.
|
|
|
6118
|
|
2459
|
6119 @node Q5.0.2, Q5.0.3, Q5.0.1, External Subsystems
|
|
|
6120 @unnumberedsubsec Q5.0.2: How can I detect a color display?
|
|
2417
|
6121
|
|
|
6122 You can test the return value of the function @code{(device-class)}, as
|
|
|
6123 in:
|
|
|
6124
|
|
|
6125 @lisp
|
|
|
6126 (when (eq (device-class) 'color)
|
|
|
6127 (set-face-foreground 'font-lock-comment-face "Grey")
|
|
|
6128 (set-face-foreground 'font-lock-string-face "Red")
|
|
|
6129 ....
|
|
|
6130 )
|
|
|
6131 @end lisp
|
|
|
6132
|
|
2459
|
6133 @node Q5.0.3, Q5.0.4, Q5.0.2, External Subsystems
|
|
|
6134 @unnumberedsubsec Q5.0.3: How can I get the icon to just say @samp{XEmacs}?
|
|
2417
|
6135
|
|
|
6136 I'd like the icon to just say @samp{XEmacs}, and not include the name of
|
|
|
6137 the current file in it.
|
|
|
6138
|
|
|
6139 Add the following line to your @file{init.el}:
|
|
|
6140
|
|
|
6141 @lisp
|
|
|
6142 (setq frame-icon-title-format "XEmacs")
|
|
|
6143 @end lisp
|
|
|
6144
|
|
2459
|
6145 @node Q5.0.4, Q5.0.5, Q5.0.3, External Subsystems
|
|
|
6146 @unnumberedsubsec Q5.0.4: How can I have the window title area display the full path?
|
|
2417
|
6147
|
|
|
6148 I'd like to have the window title area display the full directory/name
|
|
|
6149 of the current buffer file and not just the name.
|
|
|
6150
|
|
|
6151 Add the following line to your @file{init.el}:
|
|
|
6152
|
|
|
6153 @lisp
|
|
|
6154 (setq frame-title-format "%S: %f")
|
|
|
6155 @end lisp
|
|
|
6156
|
|
|
6157 A more sophisticated title might be:
|
|
|
6158
|
|
|
6159 @lisp
|
|
|
6160 (setq frame-title-format
|
|
|
6161 '("%S: " (buffer-file-name "%f"
|
|
|
6162 (dired-directory dired-directory "%b"))))
|
|
|
6163 @end lisp
|
|
|
6164
|
|
|
6165 That is, use the file name, or the dired-directory, or the buffer name.
|
|
|
6166
|
|
2459
|
6167 @node Q5.0.5, Q5.0.6, Q5.0.4, External Subsystems
|
|
|
6168 @unnumberedsubsec Q5.0.5: @samp{xemacs -name junk} doesn't work?
|
|
2417
|
6169
|
|
|
6170 When I run @samp{xterm -name junk}, I get an xterm whose class name
|
|
|
6171 according to xprop, is @samp{junk}. This is the way it's supposed to
|
|
|
6172 work, I think. When I run @samp{xemacs -name junk} the class name is
|
|
|
6173 not set to @samp{junk}. It's still @samp{emacs}. What does
|
|
|
6174 @samp{xemacs -name} really do? The reason I ask is that my window
|
|
|
6175 manager (fvwm) will make a window sticky and I use XEmacs to read my
|
|
|
6176 mail. I want that XEmacs window to be sticky, without having to use the
|
|
|
6177 window manager's function to set the window sticky. What gives?
|
|
|
6178
|
|
|
6179 @samp{xemacs -name} sets the application name for the program (that is,
|
|
|
6180 the thing which normally comes from @samp{argv[0]}). Using @samp{-name}
|
|
|
6181 is the same as making a copy of the executable with that new name. The
|
|
|
6182 @code{WM_CLASS} property on each frame is set to the frame-name, and the
|
|
|
6183 application-class. So, if you did @samp{xemacs -name FOO} and then
|
|
|
6184 created a frame named @var{BAR}, you'd get an X window with WM_CLASS =
|
|
|
6185 @code{( "BAR", "Emacs")}. However, the resource hierarchy for this
|
|
|
6186 widget would be:
|
|
|
6187
|
|
|
6188 @example
|
|
|
6189 Name: FOO .shell .container .BAR
|
|
|
6190 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
|
|
|
6191 @end example
|
|
|
6192
|
|
|
6193 instead of the default
|
|
|
6194
|
|
|
6195 @example
|
|
|
6196 Name: xemacs.shell .container .emacs
|
|
|
6197 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
|
|
|
6198 @end example
|
|
|
6199
|
|
|
6200
|
|
|
6201 It is arguable that the first element of WM_CLASS should be set to the
|
|
|
6202 application-name instead of the frame-name, but I think that's less
|
|
|
6203 flexible, since it does not give you the ability to have multiple frames
|
|
|
6204 with different WM_CLASS properties. Another possibility would be for
|
|
|
6205 the default frame name to come from the application name instead of
|
|
|
6206 simply being @samp{emacs}. However, at this point, making that change
|
|
|
6207 would be troublesome: it would mean that many users would have to make
|
|
|
6208 yet another change to their resource files (since the default frame name
|
|
|
6209 would suddenly change from @samp{emacs} to @samp{xemacs}, or whatever
|
|
|
6210 the executable happened to be named), so we'd rather avoid it.
|
|
|
6211
|
|
|
6212 To make a frame with a particular name use:
|
|
|
6213
|
|
|
6214 @lisp
|
|
|
6215 (make-frame '((name . "the-name")))
|
|
|
6216 @end lisp
|
|
|
6217
|
|
2459
|
6218 @node Q5.0.6, Q5.1.1, Q5.0.5, External Subsystems
|
|
|
6219 @unnumberedsubsec Q5.0.6: @samp{-iconic} doesn't work.
|
|
2417
|
6220
|
|
|
6221 When I start up XEmacs using @samp{-iconic} it doesn't work right.
|
|
|
6222 Using @samp{-unmapped} on the command line, and setting the
|
|
|
6223 @code{initiallyUnmapped} X Resource don't seem to help much either...
|
|
|
6224
|
|
|
6225 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
|
6226
|
|
|
6227 @quotation
|
|
|
6228 Ugh, this stuff is such an incredible mess that I've about given up
|
|
|
6229 getting it to work. The principal problem is numerous window-manager
|
|
|
6230 bugs...
|
|
|
6231 @end quotation
|
|
|
6232
|
|
2459
|
6233 @unnumberedsec 5.1: Microsoft Windows
|
|
|
6234
|
|
|
6235 @node Q5.1.1, Q5.1.2, Q5.0.6, External Subsystems
|
|
|
6236 @unnumberedsubsec Q5.1.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
2417
|
6237
|
|
|
6238 In his flavor of Emacs 20, Richard Stallman has renamed all the @samp{win32-*}
|
|
|
6239 symbols to @samp{w32-*}. Does XEmacs do the same?
|
|
|
6240
|
|
|
6241 We consider such a move counter-productive, thus we do not use the
|
|
|
6242 @samp{w32} prefix. (His rather questionable justification was that he
|
|
|
6243 did not consider Windows to be a "winning" platform.) However, the name
|
|
|
6244 @samp{Win32} is not particularly descriptive outside the Windows world,
|
|
|
6245 and using just @samp{windows-} would be too generic. So we chose a
|
|
|
6246 compromise, the prefix @samp{mswindows-} for Windows-related variables
|
|
|
6247 and functions.
|
|
|
6248
|
|
|
6249 Thus all the XEmacs variables and functions directly related to either
|
|
|
6250 the Windows GUI or OS are prefixed @samp{mswindows-} (except for a
|
|
|
6251 couple of debugging variables, prefixed @samp{debug-mswindows-}). From
|
|
|
6252 an architectural perspective, however, we believe that this is mostly a
|
|
|
6253 non-issue because there should be a very small number of
|
|
|
6254 window-systems-specific variables anyway. Whenever possible, we try to
|
|
|
6255 provide generic interfaces that apply to all window systems.
|
|
|
6256
|
|
|
6257 @c not true:
|
|
|
6258 @c The user variables
|
|
|
6259 @c that share functionality with existing NT Emacs variables are be named
|
|
|
6260 @c with our convention, but we provide the GNU Emacs names as
|
|
|
6261 @c compatibility aliases.
|
|
|
6262
|
|
2459
|
6263 @node Q5.1.2, Q5.2.1, Q5.1.1, External Subsystems
|
|
|
6264 @unnumberedsubsec Q5.1.2: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
2417
|
6265
|
|
|
6266 @unnumberedsubsubsec Associating a new file type with XEmacs.
|
|
|
6267
|
|
|
6268 In Explorer select @samp{View->Options->File Types}, press @samp{[New
|
|
|
6269 Type...]} and fill in the dialog box, e.g.:
|
|
|
6270
|
|
|
6271 @example
|
|
|
6272 Description of type: Emacs Lisp source
|
|
|
6273 Associated extension: el
|
|
|
6274 Content Type (MIME): text/plain
|
|
|
6275 @end example
|
|
|
6276
|
|
|
6277 then press @samp{[New...]} and fill in the @samp{Action} dialog box as
|
|
|
6278 follows:
|
|
|
6279
|
|
|
6280 @example
|
|
|
6281 Action:
|
|
|
6282 Open
|
|
|
6283
|
|
|
6284 Application used to perform action:
|
|
|
6285 D:\Full\path\for\xemacs.exe "%1"
|
|
|
6286
|
|
|
6287 [x] Use DDE
|
|
|
6288
|
|
|
6289 DDE Message:
|
|
|
6290 open("%1")
|
|
|
6291
|
|
|
6292 Application:
|
|
|
6293 <leave blank>
|
|
|
6294
|
|
|
6295 DDE Application Not Running:
|
|
|
6296 <leave blank>
|
|
|
6297
|
|
|
6298 Topic:
|
|
|
6299 <leave blank>
|
|
|
6300 @end example
|
|
|
6301
|
|
|
6302 @unnumberedsubsubsec Associating an existing file type with XEmacs.
|
|
|
6303
|
|
|
6304 In Explorer select @samp{View->Options->File Types}. Click on the file
|
|
|
6305 type in the list and press @samp{[Edit...]}. If the file type already
|
|
|
6306 has an @samp{Open} action, double click on it and fill in the
|
|
|
6307 @samp{Action} dialog box as described above; otherwise create a new
|
|
|
6308 action.
|
|
|
6309
|
|
|
6310 If the file type has more than one action listed, you probably want to
|
|
|
6311 make the @samp{Open} action that you just edited the default by clicking on
|
|
|
6312 it and pressing @samp{Set Default}.
|
|
|
6313
|
|
|
6314 Note for Windows 2000 users: Under Windows 2000, get to @samp{File Types}
|
|
|
6315 using @samp{Control Panel->Folder Options->File Types}.
|
|
|
6316
|
|
2459
|
6317 @unnumberedsec 5.2: Printing
|
|
|
6318
|
|
|
6319 @node Q5.2.1, Q5.2.2, Q5.1.2, External Subsystems
|
|
|
6320 @unnumberedsubsec Q5.2.1: What do I need to change to make printing work?
|
|
2417
|
6321
|
|
|
6322 For regular printing there are two variables that can be customized.
|
|
|
6323
|
|
|
6324 @table @code
|
|
|
6325 @item lpr-command
|
|
|
6326 This should be set to a command that takes standard input and sends
|
|
|
6327 it to a printer. Something like:
|
|
|
6328
|
|
|
6329 @lisp
|
|
|
6330 (setq lpr-command "lp")
|
|
|
6331 @end lisp
|
|
|
6332
|
|
|
6333 @item lpr-switches
|
|
|
6334 This should be set to a list that contains whatever the print command
|
|
|
6335 requires to do its job. Something like:
|
|
|
6336
|
|
|
6337 @lisp
|
|
|
6338 (setq lpr-switches '("-depson"))
|
|
|
6339 @end lisp
|
|
|
6340 @end table
|
|
|
6341
|
|
|
6342 For postscript printing there are three analogous variables to
|
|
|
6343 customize.
|
|
|
6344
|
|
|
6345 @table @code
|
|
|
6346 @item ps-lpr-command
|
|
|
6347 This should be set to a command that takes postscript on standard input
|
|
|
6348 and directs it to a postscript printer.
|
|
|
6349
|
|
|
6350 @item ps-lpr-switches
|
|
|
6351 This should be set to a list of switches required for
|
|
|
6352 @code{ps-lpr-command} to do its job.
|
|
|
6353
|
|
|
6354 @item ps-print-color-p
|
|
|
6355 This boolean variable should be set @code{t} if printing will be done in
|
|
|
6356 color, otherwise it should be set to @code{nil}.
|
|
|
6357 @end table
|
|
|
6358
|
|
|
6359 NOTE: It is an undocumented limitation in XEmacs that postscript
|
|
|
6360 printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a
|
|
|
6361 window system environment. It cannot be used outside of X11.
|
|
|
6362
|
|
2459
|
6363 @node Q5.2.2, Q5.2.3, Q5.2.1, External Subsystems
|
|
|
6364 @unnumberedsubsec Q5.2.2: How can I print WYSIWYG a font-locked buffer?
|
|
2417
|
6365
|
|
|
6366 Font-lock looks nice. How can I print (WYSIWYG) the highlighted
|
|
|
6367 document?
|
|
|
6368
|
|
|
6369 The package @code{ps-print}, which is now included with XEmacs, provides
|
|
|
6370 the ability to do this. The source code contains complete instructions
|
|
|
6371 on its use, in
|
|
|
6372 @file{$prefix/lib/xemacs/xemacs-packages/lisp/ps-print/ps-print.el},
|
|
|
6373 being the default location of an installed ps-print package.
|
|
|
6374
|
|
2459
|
6375 @node Q5.2.3, Q5.2.4, Q5.2.2, External Subsystems
|
|
|
6376 @unnumberedsubsec Q5.2.3: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
2417
|
6377
|
|
|
6378 My printer is a Postscript printer and @code{lpr} only works for
|
|
|
6379 Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x
|
|
|
6380 lpr-buffer} to work?
|
|
|
6381
|
|
|
6382 Put something like this in your @file{init.el}:
|
|
428
|
6383
|
|
|
6384 @lisp
|
|
2417
|
6385 (setq lpr-command "a2ps")
|
|
|
6386 (setq lpr-switches '("-p" "-1"))
|
|
|
6387 @end lisp
|
|
|
6388
|
|
|
6389 If you don't use a2ps to convert ASCII to postscript (why not, it's
|
|
|
6390 free?), replace with the command you do use. Note also that some
|
|
|
6391 versions of a2ps require a @samp{-Pprinter} to ensure spooling.
|
|
|
6392
|
|
2459
|
6393 @node Q5.2.4, Q5.3.1, Q5.2.3, External Subsystems
|
|
|
6394 @unnumberedsubsec Q5.2.4: Can you print under MS Windows?
|
|
2417
|
6395
|
|
|
6396 As of 21.4, printing works on Windows, using simply
|
|
|
6397 @samp{File->Print BUFFER...}, and can be configured with
|
|
|
6398 @samp{File->Page Setup...}.
|
|
|
6399
|
|
|
6400 Prior to 21.4, there is no built-in support, but there are some clever
|
|
|
6401 hacks out there. If you know how, please let us know and we'll put it
|
|
|
6402 here.
|
|
|
6403
|
|
2459
|
6404 @unnumberedsec 5.3: Sound
|
|
|
6405
|
|
|
6406 @node Q5.3.1, Q5.3.2, Q5.2.4, External Subsystems
|
|
|
6407 @unnumberedsubsec Q5.3.1: How do I turn off the sound?
|
|
2417
|
6408
|
|
|
6409 Add the following line to your @file{init.el}:
|
|
|
6410
|
|
|
6411 @lisp
|
|
|
6412 (setq bell-volume 0)
|
|
|
6413 (setq sound-alist nil)
|
|
|
6414 @end lisp
|
|
|
6415
|
|
|
6416 That will make your XEmacs totally silent---even the default ding sound
|
|
|
6417 (TTY beep on TTY-s) will be gone.
|
|
|
6418
|
|
|
6419 You can also change these with Customize. Select from the
|
|
|
6420 @code{Options} menu @code{Advanced
|
|
|
6421 (Customize)->Emacs->Environment->Sound->Sound...} or type @kbd{M-x
|
|
|
6422 customize @key{RET} sound @key{RET}}.
|
|
|
6423
|
|
|
6424
|
|
2459
|
6425 @node Q5.3.2, Q5.3.3, Q5.3.1, External Subsystems
|
|
|
6426 @unnumberedsubsec Q5.3.2: How do I get funky sounds instead of a boring beep?
|
|
2417
|
6427
|
|
|
6428 Make sure your XEmacs was compiled with sound support, and then put this
|
|
|
6429 in your @file{init.el}:
|
|
|
6430
|
|
|
6431 @lisp
|
|
|
6432 (load-default-sounds)
|
|
|
6433 @end lisp
|
|
|
6434
|
|
2459
|
6435 @node Q5.3.3, Q5.3.4, Q5.3.2, External Subsystems
|
|
|
6436 @unnumberedsubsec Q5.3.3: What are NAS and ESD (EsounD)?
|
|
|
6437
|
|
|
6438 @dfn{Network Audio System} (NAS) is a client-server sound library for X.
|
|
|
6439
|
|
|
6440 @uref{http://radscan.com/nas.html}.
|
|
|
6441
|
|
|
6442 To build XEmacs with it, use the @file{configure} flag @samp{--with-sound=nas}.
|
|
|
6443
|
|
|
6444 @dfn{Enlightened Sound Daemon} (ESD or EsounD) is yet another sound system.
|
|
|
6445
|
|
|
6446 @uref{http://www.tux.org/~ricdude/EsounD.html}.
|
|
|
6447
|
|
|
6448 To build XEmacs with it, use the @file{configure} flag @samp{--with-sound=esd}.
|
|
|
6449
|
|
|
6450 You can specify support for both with a flag like @samp{--with-sound=nas,esd}.
|
|
|
6451
|
|
|
6452 @node Q5.3.4, Q5.4.1, Q5.3.3, External Subsystems
|
|
|
6453 @unnumberedsubsec Q5.3.4: Sunsite sounds don't play.
|
|
2417
|
6454
|
|
|
6455 I'm having some trouble with sounds I've downloaded from sunsite. They
|
|
|
6456 play when I run them through @code{showaudio} or cat them directly to
|
|
|
6457 @file{/dev/audio}, but XEmacs refuses to play them.
|
|
|
6458
|
|
|
6459 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
|
|
|
6460
|
|
|
6461 @quotation
|
|
|
6462 [Many of] These files have an (erroneous) 24byte header that tells about
|
|
|
6463 the format that they have been recorded in. If you cat them to
|
|
|
6464 @file{/dev/audio}, the header will be ignored and the default behavior
|
|
|
6465 for /dev/audio will be used. This happens to be 8kHz uLaw. It is
|
|
|
6466 probably possible to fix the header by piping through @code{sox} and
|
|
|
6467 passing explicit parameters for specifying the sampling format; you then
|
|
|
6468 need to perform a 'null' conversion from SunAudio to SunAudio.
|
|
|
6469 @end quotation
|
|
|
6470
|
|
2459
|
6471 @unnumberedsec 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
6472
|
|
|
6473 @node Q5.4.1, Q5.4.2, Q5.3.4, External Subsystems
|
|
|
6474 @unnumberedsubsec Q5.4.1: What is an interior shell?
|
|
2417
|
6475
|
|
|
6476 #### Write me.
|
|
|
6477
|
|
2459
|
6478 @node Q5.4.2, Q5.4.3, Q5.4.1, External Subsystems
|
|
|
6479 @unnumberedsubsec Q5.4.2: How do I start up a second shell buffer?
|
|
2417
|
6480
|
|
|
6481 In the @code{*shell*} buffer:
|
|
|
6482
|
|
|
6483 @lisp
|
|
|
6484 M-x rename-buffer @key{RET} *shell-1* @key{RET}
|
|
|
6485 M-x shell RET
|
|
|
6486 @end lisp
|
|
|
6487
|
|
|
6488 This will then start a second shell. The key is that no buffer named
|
|
|
6489 @samp{*shell*} can exist. It might be preferable to use @kbd{M-x
|
|
|
6490 rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x
|
|
|
6491 rename-buffer}.
|
|
|
6492
|
|
|
6493 Alternately, you can set the variable @code{shell-multiple-shells}.
|
|
|
6494 If the value of this variable is non-nil, each time shell mode is invoked,
|
|
|
6495 a new shell is made
|
|
|
6496
|
|
2459
|
6497 @node Q5.4.3, Q5.4.4, Q5.4.2, External Subsystems
|
|
|
6498 @unnumberedsubsec Q5.4.3: Telnet from shell filters too much
|
|
2417
|
6499
|
|
|
6500 I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke
|
|
|
6501 and use a telnet session within it. Everything works fine except that
|
|
|
6502 now all @samp{^M}'s are filtered out by Emacs. Fixes?
|
|
|
6503
|
|
|
6504 Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather
|
|
|
6505 than doing rsh or telnet within the local shell buffer. You can also
|
|
|
6506 use @kbd{M-x ssh} to open secure remote session if you have @code{ssh}
|
|
|
6507 installed.
|
|
|
6508
|
|
2459
|
6509 @node Q5.4.4, Q5.4.5, Q5.4.3, External Subsystems
|
|
|
6510 @unnumberedsubsec Q5.4.4: Strange things are happening in Shell Mode.
|
|
2417
|
6511
|
|
|
6512 Sometimes (i.e. it's not repeatable, and I can't work out why it
|
|
|
6513 happens) when I'm typing into shell mode, I hit return and only a
|
|
|
6514 portion of the command is given to the shell, and a blank prompt is
|
|
|
6515 returned. If I hit return again, the rest of the previous command is
|
|
|
6516 given to the shell.
|
|
|
6517
|
|
|
6518 @email{martin@@xemacs.org, Martin Buchholz} writes:
|
|
|
6519
|
|
|
6520 @quotation
|
|
|
6521 There is a known problem with interaction between @code{csh} and the
|
|
|
6522 @code{filec} option and XEmacs. You should add the following to your
|
|
|
6523 @file{.cshrc}:
|
|
|
6524
|
|
|
6525 @example
|
|
|
6526 if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec
|
|
|
6527 @end example
|
|
|
6528 @end quotation
|
|
|
6529
|
|
2459
|
6530 @node Q5.4.5, Q5.5.1, Q5.4.4, External Subsystems
|
|
|
6531 @unnumberedsubsec Q5.4.5: XEmacs complains "No such file or directory, diff"
|
|
2417
|
6532
|
|
|
6533 or "ispell" or other commands that seem related to whatever you just
|
|
|
6534 tried to do (M-x ediff or M-$, for example).
|
|
|
6535
|
|
|
6536 There are a large number of common (in the sense that "everyone has
|
|
|
6537 these, they really do") Unix utilities that are not provided with
|
|
|
6538 XEmacs. The GNU Project's implementations are available for Windows in
|
|
|
6539 the the Cygwin distribution (@uref{http://www.cygwin.com/}), which also
|
|
|
6540 provides a complete Unix emulation environment (and thus makes ports of
|
|
|
6541 Unix utilities nearly trivial). Another implementation is that from
|
|
|
6542 MinGW (@uref{http://www.mingw.org/msys.shtml}). If you know of others,
|
|
|
6543 please let us know!
|
|
|
6544
|
|
2459
|
6545 @unnumberedsec 5.5: Multiple Device Support
|
|
|
6546
|
|
|
6547 @node Q5.5.1, Q5.5.2, Q5.4.5, External Subsystems
|
|
|
6548 @unnumberedsubsec Q5.5.1: How do I open a frame on another screen of my multi-headed display?
|
|
2417
|
6549
|
|
|
6550 Use the command @kbd{M-x make-frame-on-display}. This command is also
|
|
|
6551 on the File menu in the menubar.
|
|
|
6552
|
|
|
6553 The command @code{make-frame-on-tty} also exists, which will establish a
|
|
|
6554 connection to any tty-like device. Opening the TTY devices should be
|
|
|
6555 left to @code{gnuclient}, though.
|
|
|
6556
|
|
2459
|
6557 @node Q5.5.2, Q5.5.3, Q5.5.1, External Subsystems
|
|
|
6558 @unnumberedsubsec Q5.5.2: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
6559
|
|
|
6560 Yes. Use @code{gnuclient -nw}.
|
|
|
6561
|
|
|
6562 Also see @ref{Q5.5.3, How do I disable gnuserv from opening a new frame?}.
|
|
|
6563
|
|
|
6564 @node Q5.5.3, Q5.5.4, Q5.5.2, External Subsystems
|
|
|
6565 @unnumberedsubsec Q5.5.3: How do I disable gnuserv from opening a new frame?
|
|
2417
|
6566
|
|
|
6567 If you set the @code{gnuserv-frame} variable to the frame that should be
|
|
|
6568 used to display buffers that are pulled up, a new frame will not be
|
|
|
6569 created. For example, you could put
|
|
|
6570
|
|
|
6571 @lisp
|
|
|
6572 (setq gnuserv-frame (selected-frame))
|
|
428
|
6573 @end lisp
|
|
|
6574
|
|
2417
|
6575 early on in your @file{init.el}, to ensure that the first frame created
|
|
|
6576 is the one used for your gnuserv buffers.
|
|
|
6577
|
|
|
6578 There is an option to set the gnuserv target to the current frame. See
|
|
|
6579 @code{Options->Display->"Other Window" Location->Make Current Frame Gnuserv Target}
|
|
|
6580
|
|
|
6581 You can also change this with Customize. Select from the
|
|
|
6582 @code{Options} menu @code{Advanced
|
|
|
6583 (Customize)->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type
|
|
|
6584 @kbd{M-x customize @key{RET} gnuserv @key{RET}}.
|
|
|
6585
|
|
|
6586
|
|
2459
|
6587 @node Q5.5.4, Q5.5.5, Q5.5.3, External Subsystems
|
|
|
6588 @unnumberedsubsec Q5.5.4: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
2417
|
6589
|
|
|
6590 Put the following in your @file{init.el} file to start the server:
|
|
|
6591
|
|
|
6592 @lisp
|
|
|
6593 (gnuserv-start)
|
|
|
6594 @end lisp
|
|
|
6595
|
|
|
6596 Start your first XEmacs as usual. After that, you can do:
|
|
|
6597
|
|
|
6598 @example
|
|
|
6599 gnuclient randomfilename
|
|
|
6600 @end example
|
|
|
6601
|
|
|
6602 from the command line to get your existing XEmacs process to open a new
|
|
|
6603 frame and visit randomfilename in that window. When you're done editing
|
|
|
6604 randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the
|
|
|
6605 frame.
|
|
|
6606
|
|
|
6607 See also man page of gnuclient.
|
|
|
6608
|
|
2459
|
6609 @node Q5.5.5, , Q5.5.4, External Subsystems
|
|
|
6610 @unnumberedsubsec Q5.5.5: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
2417
|
6611
|
|
|
6612 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
|
|
|
6613 @quotation
|
|
|
6614 Here is one of the solutions, we have this in a script called
|
|
|
6615 @file{etc/editclient.sh}.
|
|
|
6616 @example
|
|
|
6617 #!/bin/sh
|
|
|
6618 if gnuclient -batch -eval t >/dev/null 2>&1
|
|
|
6619 then
|
|
|
6620 exec gnuclient $@{1+"$@@"@}
|
|
|
6621 else
|
|
|
6622 xemacs -unmapped -f gnuserv-start &
|
|
|
6623 until gnuclient -batch -eval t >/dev/null 2>&1
|
|
|
6624 do
|
|
|
6625 sleep 1
|
|
|
6626 done
|
|
|
6627 exec gnuclient $@{1+"$@@"@}
|
|
|
6628 fi
|
|
|
6629 @end example
|
|
|
6630
|
|
|
6631 Note that there is a known problem when running XEmacs and 'gnuclient
|
|
|
6632 -nw' on the same TTY.
|
|
|
6633 @end quotation
|
|
|
6634
|
|
2459
|
6635 @node Internet, Advanced, External Subsystems, Top
|
|
|
6636 @unnumbered 6 Connecting to the Internet
|
|
|
6637
|
|
|
6638 This is part 6 of the XEmacs Frequently Asked Questions list. This
|
|
|
6639 section is devoted connecting to the Internet.
|
|
|
6640
|
|
|
6641 @menu
|
|
|
6642 6.0: General Mail and News
|
|
|
6643 * Q6.0.1:: What are the various packages for reading mail?
|
|
|
6644 * Q6.0.2:: How can I send mail?
|
|
|
6645 * Q6.0.3:: How do I get my outgoing mail archived?
|
|
|
6646 * Q6.0.4:: How can I read and/or compose MIME messages?
|
|
|
6647 * Q6.0.5:: How do I customize the From line?
|
|
|
6648 * Q6.0.6:: How do I get my MUA to filter mail for me?
|
|
|
6649 * Q6.0.7:: Remote mail reading with an MUA.
|
|
|
6650 * Q6.0.8:: An MUA gets an error incorporating new mail.
|
|
|
6651 * Q6.0.9:: Why isn't @file{movemail} working?
|
|
|
6652 * Q6.0.10:: How do I make my MUA display graphical smilies?
|
|
|
6653 * Q6.0.11:: How can I get those oh-so-neat X-Face lines?
|
|
|
6654
|
|
|
6655 6.1: Reading Mail with VM
|
|
|
6656 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
6657 * Q6.1.2:: How can I get VM to automatically check for new mail?
|
|
|
6658 * 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"?
|
|
|
6659 * Q6.1.4:: Is there a mailing list or FAQ for VM?
|
|
|
6660 * Q6.1.5:: How do I make VM stay in a single frame?
|
|
|
6661 * Q6.1.6:: Customization of VM not covered in the manual, or here.
|
|
|
6662
|
|
|
6663 6.2: Reading Netnews and Mail with Gnus
|
|
|
6664 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
6665 * Q6.2.2:: How do I make Gnus stay within a single frame?
|
|
|
6666
|
|
|
6667 6.3: FTP Access
|
|
|
6668 * Q6.3.1:: Can I edit files on other hosts?
|
|
|
6669 * Q6.3.2:: What is EFS?
|
|
|
6670
|
|
|
6671 6.4: Web Browsing with W3
|
|
|
6672 * Q6.4.1:: What is W3?
|
|
|
6673 * Q6.4.2:: How do I run W3 from behind a firewall?
|
|
|
6674 * Q6.4.3:: Is it true that W3 supports style sheets and tables?
|
|
|
6675 @end menu
|
|
|
6676
|
|
|
6677 @unnumberedsec 6.0: General Mail and News
|
|
|
6678
|
|
|
6679 @node Q6.0.1, Q6.0.2, Internet, Internet
|
|
|
6680 @unnumberedsubsec Q6.0.1: What are the various packages for reading mail?
|
|
|
6681
|
|
|
6682 #### Write me.
|
|
|
6683
|
|
|
6684 @node Q6.0.2, Q6.0.3, Q6.0.1, Internet
|
|
|
6685 @unnumberedsubsec Q6.0.2: How can I send mail?
|
|
|
6686
|
|
|
6687 Under Unix and Mac OS X, the @samp{sendmail} package is normally used
|
|
|
6688 for this.
|
|
|
6689 #### Write me.
|
|
|
6690
|
|
|
6691 Under Windows, you need to use @samp{smtpmail}, which communicates
|
|
|
6692 directly with the mail server, as there is no @file{sendmail} program
|
|
|
6693 running. To get it working, use code like the following in your
|
|
|
6694 @file{init.el} file:
|
|
|
6695
|
|
|
6696 @lisp
|
|
|
6697 ;; Get mail working under Windows.
|
|
|
6698 (setq message-send-mail-function 'smtpmail-send-it) ; for message/Gnus
|
|
|
6699 (setq send-mail-function 'smtpmail-send-it) ; for C-x m, etc.
|
|
|
6700 ;; the following ensures that mail problems can be debugged: it logs a trace
|
|
|
6701 ;; of the SMTP conversation to *trace of SMTP session to <somewhere>*.
|
|
|
6702 (setq smtpmail-debug-info t)
|
|
|
6703 ;; Substitute your info here.
|
|
|
6704 ;(setq user-mail-address "ben@@xemacs.org")
|
|
|
6705 ;(setq user-full-name "Ben Wing")
|
|
|
6706 ;(setq smtpmail-default-smtp-server "smtp.myserver.myisp.com")
|
|
|
6707 ;; The following two aren't completely necessary but may help.
|
|
|
6708 ;(setq smtpmail-local-domain "666.com")
|
|
|
6709 ;(setq smtpmail-sendto-domain "666.com")
|
|
|
6710 ;; If your SMTP server requires a username/password to authenticate, as
|
|
|
6711 ;; many do nowadays, set them like this:
|
|
|
6712 ;(setq smtpmail-auth-credentials ; or use ~/.authinfo
|
|
|
6713 ; '(("smtp.myserver.myisp.com" 25 "USER@@SOMEWHERE" "PASSWORD")))
|
|
|
6714
|
|
|
6715 ;; Other possibilities for getting smtpmail to work:
|
|
|
6716 ;;
|
|
|
6717 ;; If for some reason you need to authenticate using the STARTTLS protocol
|
|
|
6718 ;; (don't look into this unless you know what it is), use
|
|
|
6719 ;; (setq smtpmail-starttls-credentials
|
|
|
6720 ;; '(("YOUR SMTP HOST" 25 "~/.my_smtp_tls.key" "~/.my_smtp_tls.cert")))
|
|
|
6721 ;; Requires external program
|
|
|
6722 ;; ftp://ftp.opaopa.org/pub/elisp/starttls-*.tar.gz.
|
|
|
6723 ;; See http://www.ietf.org/rfc/rfc2246.txt,
|
|
|
6724 ;; http://www.ietf.org/rfc/rfc2487.txt
|
|
|
6725 @end lisp
|
|
|
6726
|
|
|
6727 The lines you need to care about are those that set
|
|
|
6728 @code{user-mail-address}, @code{user-full-name},
|
|
|
6729 @code{smtpmail-default-smtp-server}, and
|
|
|
6730 @code{smtpmail-auth-credentials}. You need to set these with,
|
|
|
6731 respectively, your email address, your full name, the SMTP server you
|
|
|
6732 use for outgoing mail, and the username and password you need to log
|
|
|
6733 in to your SMTP server. (If for some reason your SMTP server doesn't
|
|
|
6734 require logging in to send mail, don't uncomment this last line.)
|
|
|
6735
|
|
|
6736 The other settings may be useful in specific cases, but you should know what
|
|
|
6737 you're doing before enabling them.
|
|
|
6738
|
|
|
6739 @node Q6.0.3, Q6.0.4, Q6.0.2, Internet
|
|
|
6740 @unnumberedsubsec Q6.0.3: How do I get my outgoing mail archived?
|
|
|
6741
|
|
|
6742 @lisp
|
|
|
6743 (setq mail-archive-file-name "~/outbox")
|
|
|
6744 @end lisp
|
|
|
6745
|
|
|
6746 @node Q6.0.4, Q6.0.5, Q6.0.3, Internet
|
|
|
6747 @unnumberedsubsec Q6.0.4: How can I read and/or compose MIME messages?
|
|
|
6748
|
|
|
6749 VM, MH-E and GNUS support MIME natively. Other MUAs may or may not
|
|
|
6750 have MIME support; refer to their documentation and other resources,
|
|
|
6751 such as web pages and mailing lists. Packages like SEMI/WEMI may be
|
|
|
6752 useful in connection with MUAs like mew and Wanderlust.
|
|
|
6753
|
|
|
6754 @node Q6.0.5, Q6.0.6, Q6.0.4, Internet
|
|
|
6755 @unnumberedsubsec Q6.0.5: How do I customize the From line?
|
|
|
6756
|
|
|
6757 How do I change the @samp{From:} line? I have set gnus-user-from-line
|
|
|
6758 to
|
|
|
6759 @example
|
|
|
6760 Gail Gurman <gail.gurman@@sybase.com>
|
|
|
6761 @end example
|
|
|
6762 @noindent , but XEmacs Gnus doesn't use
|
|
|
6763 it. [This should apply to all MUA's. --ed] Instead it uses
|
|
|
6764 @example
|
|
|
6765 Gail Mara Gurman @email{gailg@@deall}
|
|
|
6766 @end example
|
|
|
6767 @noindent and then complains
|
|
|
6768 that it's incorrect. Also, as you perhaps can see, my Message-ID is
|
|
|
6769 screwy. How can I change that?
|
|
|
6770
|
|
|
6771 @email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes:
|
|
|
6772
|
|
|
6773 @quotation
|
|
|
6774 Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or
|
|
|
6775 @code{mail-host-address} to @samp{sybase.com}.
|
|
|
6776 @end quotation
|
|
|
6777
|
|
|
6778 @node Q6.0.6, Q6.0.7, Q6.0.5, Internet
|
|
|
6779 @unnumberedsubsec Q6.0.6: How do I get my MUA to filter mail for me?
|
|
|
6780
|
|
|
6781 One possibility is to use procmail to split your mail before it gets to
|
|
|
6782 the MUA. I prefer this personally, since there are many strange and
|
|
|
6783 wonderful things one can do with procmail. Procmail may be found at
|
|
|
6784 @uref{http://www.procmail.org/}.
|
|
|
6785
|
|
|
6786 Also see the Mail Filtering FAQ at:
|
|
|
6787 @iftex
|
|
|
6788 @*
|
|
|
6789 @end iftex
|
|
|
6790 @uref{http://www.faqs.org/faqs/mail/filtering-faq/}.
|
|
|
6791
|
|
|
6792 @node Q6.0.7, Q6.0.8, Q6.0.6, Internet
|
|
|
6793 @unnumberedsubsec Q6.0.7: Remote mail reading with an MUA.
|
|
|
6794
|
|
|
6795 My mailbox lives at the office on a big honkin server. My regular INBOX
|
|
|
6796 lives on my honkin desktop machine. I now can PPP to the office from
|
|
|
6797 home which is far from honking... I'd like to be able to read mail at
|
|
|
6798 home without storing it here and I'd like to use xemacs and the MUA at
|
|
|
6799 home... Is there a recommended setup?
|
|
|
6800
|
|
|
6801 @email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes:
|
|
|
6802
|
|
|
6803 @quotation
|
|
|
6804 There are several ways to do this.
|
|
|
6805
|
|
|
6806 @enumerate
|
|
|
6807 @item
|
|
|
6808 Set your display to your home machine and run dxpc or one of the other X
|
|
|
6809 compressors.
|
|
|
6810
|
|
|
6811 @item
|
|
|
6812 NFS mount your desktop machine on your home machine and modify your pop
|
|
|
6813 command on your home machine to rsh to your desktop machine and actually
|
|
|
6814 do the pop get's.
|
|
|
6815
|
|
|
6816 @item
|
|
|
6817 Run a POP server on your desktop machine as well and do a sort of two
|
|
|
6818 tiered POP get.
|
|
|
6819 @end enumerate
|
|
|
6820 @end quotation
|
|
|
6821
|
|
|
6822 @email{wmperry@@monolith.spry.com, William Perry} adds:
|
|
|
6823
|
|
|
6824 @quotation
|
|
|
6825 Or you could run a pop script periodically on your desktop machine, and
|
|
|
6826 just use ange-ftp or NFS to get to your mailbox. I used to do this all
|
|
|
6827 the time back at IU.
|
|
|
6828 @end quotation
|
|
|
6829
|
|
|
6830 @node Q6.0.8, Q6.0.9, Q6.0.7, Internet
|
|
|
6831 @unnumberedsubsec Q6.0.8: An MUA gets an error incorporating new mail.
|
|
|
6832
|
|
|
6833 rmail and VM, and probably other MUA's as well, get new mail from
|
|
|
6834 your mailbox (called @file{/var/mail/$USER} or @file{/var/spool/mail/$USER}
|
|
|
6835 or something similar) using a program called @code{movemail}.
|
|
|
6836 This program interlocks with @code{/bin/mail} using the protocol
|
|
|
6837 defined by @code{/bin/mail}.
|
|
|
6838
|
|
|
6839 There are various different protocols in general use, which you need to
|
|
|
6840 specify using the @samp{--mail-locking} option to @file{configure}:
|
|
|
6841
|
|
|
6842 @table @samp
|
|
|
6843 @item lockf
|
|
|
6844 POSIX file locking with @code{lockf()}
|
|
|
6845 @item flock
|
|
|
6846 BSD file locking with @code{flock()}
|
|
|
6847 @item dot
|
|
|
6848 To manipulate mail file @file{foo}, first create file @file{foo.lock}
|
|
|
6849 @item locking
|
|
|
6850 Use @code{locking()}, Microsoft's renamed @code{flock()}
|
|
|
6851 @item mmdf
|
|
|
6852 Use @code{lk_open()} and @code{lk_close()} as defined by the Multi-channel
|
|
|
6853 Memo Distribution Facility
|
|
|
6854 @item pop
|
|
|
6855 Retrieve mail using POP (the Post Office Protocol). This is the
|
|
|
6856 default for Cygwin/MinGW.
|
|
|
6857 @end table
|
|
|
6858
|
|
|
6859 @strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
|
|
|
6860 SYSTEM, YOU CAN LOSE MAIL!}
|
|
|
6861
|
|
|
6862 Usually the value is correctly determined automatically:
|
|
|
6863 @file{configure} tries to detect the method in use, and defaults exist
|
|
|
6864 on systems for which this doesn't work.
|
|
|
6865
|
|
|
6866 However, if you run into problems incorporating new mail, it may be
|
|
|
6867 because an incorrect method is being used.
|
|
|
6868
|
|
|
6869 If your system uses the lock file protocol, and permissions are set
|
|
|
6870 so that ordinary users cannot write lock files in the mail spool
|
|
|
6871 directory, you may need to make @file{movemail} setgid to a
|
|
|
6872 suitable group such as @samp{mail}. You can use these commands (as
|
|
|
6873 root):
|
|
|
6874
|
|
|
6875 @example
|
|
|
6876 chgrp mail movemail
|
|
|
6877 chmod 2755 movemail
|
|
|
6878 @end example
|
|
|
6879
|
|
|
6880 If you are using the @samp{pop} locking method, @file{movemail} must
|
|
|
6881 be setuid root.
|
|
|
6882
|
|
|
6883 Installation normally copies movemail from the build directory to an
|
|
|
6884 installation directory which is usually under @file{/usr/local/lib}.
|
|
|
6885 The installed copy of @file{movemail} is usually in the directory
|
|
|
6886 @file{/usr/local/lib/xemacs-VERSION/TARGET} (for example,
|
|
|
6887 @file{/usr/local/lib/xemacs-21.4.15/i686-pc-cygwin}). You must change
|
|
|
6888 the group and mode of the installed copy; changing the group and mode
|
|
|
6889 of the build directory copy is ineffective.
|
|
|
6890
|
|
|
6891 @node Q6.0.9, Q6.0.10, Q6.0.8, Internet
|
|
|
6892 @unnumberedsubsec Q6.0.9: Why isn't @file{movemail} working?
|
|
|
6893
|
|
|
6894 @xref{Q6.0.8}.
|
|
|
6895
|
|
|
6896 Note also that older versions of Mozilla came with a @file{movemail}
|
|
|
6897 program that is @strong{not} compatible with XEmacs. Do not use it.
|
|
|
6898 Always use the @file{movemail} installed with your XEmacs. Failure to
|
|
|
6899 do so can result in lost mail.
|
|
|
6900
|
|
|
6901 @node Q6.0.10, Q6.0.11, Q6.0.9, Internet
|
|
|
6902 @unnumberedsubsec Q6.0.10: How do I make my MUA display graphical smilies?
|
|
|
6903 For mh-e use the following:
|
|
|
6904
|
|
|
6905 @lisp
|
|
|
6906 (add-hook 'mh-show-mode-hook '(lambda ()
|
|
|
6907 (smiley-region (point-min)
|
|
|
6908 (point-max))))
|
|
|
6909 @end lisp
|
|
|
6910
|
|
|
6911 @email{bill@@carpenter.ORG, WJCarpenter} writes:
|
|
|
6912 For VM use the following:
|
|
|
6913 @lisp
|
|
|
6914 (autoload 'smiley-region "smiley" nil t)
|
|
|
6915 (add-hook 'vm-select-message-hook
|
|
|
6916 '(lambda ()
|
|
|
6917 (smiley-region (point-min)
|
|
|
6918 (point-max))))
|
|
|
6919 @end lisp
|
|
|
6920
|
|
|
6921 For tm use the following:
|
|
|
6922 @lisp
|
|
|
6923 (autoload 'smiley-buffer "smiley" nil t)
|
|
|
6924 (add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer)
|
|
|
6925 @end lisp
|
|
|
6926
|
|
|
6927 @node Q6.0.11, Q6.1.1, Q6.0.10, Internet
|
|
|
6928 @unnumberedsubsec Q6.0.11: How can I get those oh-so-neat X-Face lines?
|
|
|
6929
|
|
|
6930 Firstly there is an ftp site which describes X-faces and has the
|
|
|
6931 associated tools mentioned below, at
|
|
|
6932 @uref{http://ftp.cs.indiana.edu/pub/faces/}.
|
|
|
6933
|
|
|
6934 Then the steps are
|
|
|
6935
|
|
|
6936 @enumerate
|
|
|
6937 @item
|
|
|
6938 Create 48x48x1 bitmap with your favorite tool
|
|
|
6939
|
|
|
6940 @item
|
|
|
6941 Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc.,
|
|
|
6942 and then compile the face.
|
|
|
6943
|
|
|
6944 @item
|
|
|
6945 @example
|
|
|
6946 cat file.xbm | xbm2ikon |compface > file.face
|
|
|
6947 @end example
|
|
|
6948
|
|
|
6949 @item
|
|
|
6950 Then be sure to quote things that are necessary for emacs strings:
|
|
|
6951
|
|
|
6952 @example
|
|
|
6953 cat ./file.face | sed 's/\\/\\\\/g'
|
|
|
6954 @iftex
|
|
|
6955 \ @*
|
|
|
6956 @end iftex
|
|
|
6957 | sed 's/\"/\\\"/g' > ./file.face.quoted
|
|
|
6958 @end example
|
|
|
6959
|
|
|
6960 @item
|
|
|
6961 Then set up emacs to include the file as a mail header - there were a
|
|
|
6962 couple of suggestions here---either something like:
|
|
|
6963
|
|
|
6964 @lisp
|
|
|
6965 (setq mail-default-headers
|
|
|
6966 "X-Face: @email{Ugly looking text string here}")
|
|
|
6967 @end lisp
|
|
|
6968
|
|
|
6969 Or, alternatively, as:
|
|
|
6970
|
|
|
6971 @lisp
|
|
|
6972 (defun mail-insert-x-face ()
|
|
|
6973 (save-excursion
|
|
|
6974 (goto-char (point-min))
|
|
|
6975 (search-forward mail-header-separator)
|
|
|
6976 (beginning-of-line)
|
|
|
6977 (insert "X-Face:")
|
|
|
6978 (insert-file-contents "~/.face")))
|
|
|
6979
|
|
|
6980 (add-hook 'mail-setup-hook 'mail-insert-x-face)
|
|
|
6981 @end lisp
|
|
|
6982 @end enumerate
|
|
|
6983
|
|
|
6984 However, 2 things might be wrong:
|
|
|
6985
|
|
|
6986 Some versions of pbmtoicon produces some header lines that is not
|
|
|
6987 expected by the version of compface that I grabbed. So I found I had to
|
|
|
6988 include a @code{tail +3} in the pipeline like this:
|
|
|
6989
|
|
|
6990 @example
|
|
|
6991 cat file.xbm | xbm2ikon | tail +3 |compface > file.face
|
|
|
6992 @end example
|
|
|
6993
|
|
|
6994 Some people have also found that if one uses the @code{(insert-file)}
|
|
|
6995 method, one should NOT quote the face string using the sed script .
|
|
|
6996
|
|
|
6997 It might also be helpful to use @email{stig@@hackvan.com, Stig's} script
|
|
|
6998 xbm2face (included in the compface distribution at XEmacs.org) to do the
|
|
|
6999 conversion.
|
|
|
7000
|
|
|
7001 Contributors for this item:
|
|
|
7002
|
|
|
7003 Paul Emsley,
|
|
|
7004 Ricardo Marek,
|
|
|
7005 Amir J. Katz,
|
|
|
7006 Glen McCort,
|
|
|
7007 Heinz Uphoff,
|
|
|
7008 Peter Arius,
|
|
|
7009 Paul Harrison, and
|
|
|
7010 Vegard Vesterheim
|
|
|
7011
|
|
|
7012 @unnumberedsec 6.1: Reading Mail with VM
|
|
|
7013
|
|
|
7014 @node Q6.1.1, Q6.1.2, Q6.0.11, Internet
|
|
|
7015 @unnumberedsubsec Q6.1.1: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
7016
|
|
|
7017 Use @code{vm-spool-files}, like this for example:
|
|
|
7018
|
|
|
7019 @lisp
|
|
|
7020 (setq vm-spool-files '("/var/spool/mail/wing"
|
|
|
7021 "netcom23.netcom.com:110:pass:wing:MYPASS"))
|
|
|
7022 @end lisp
|
|
|
7023
|
|
|
7024 Of course substitute your actual password for MYPASS.
|
|
|
7025
|
|
|
7026 @node Q6.1.2, Q6.1.3, Q6.1.1, Internet
|
|
|
7027 @unnumberedsubsec Q6.1.2: How can I get VM to automatically check for new mail?
|
|
|
7028
|
|
|
7029 @email{turner@@lanl.gov, John Turner} writes:
|
|
|
7030
|
|
|
7031 @quotation
|
|
|
7032 Use the following:
|
|
|
7033
|
|
|
7034 @lisp
|
|
|
7035 (setq vm-auto-get-new-mail 60)
|
|
|
7036 @end lisp
|
|
|
7037 @end quotation
|
|
|
7038
|
|
|
7039 @node Q6.1.3, Q6.1.4, Q6.1.2, Internet
|
|
|
7040 @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"?
|
|
|
7041
|
|
|
7042 Set @code{vm-reply-ignored-addresses} to a list, like
|
|
|
7043
|
|
|
7044 @lisp
|
|
|
7045 (setq vm-reply-ignored-addresses
|
|
|
7046 '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com"
|
|
|
7047 "wing@@netcom.com" "wing@@xemacs.org"))
|
|
|
7048 @end lisp
|
|
|
7049
|
|
|
7050 Note that each string is a regular expression.
|
|
|
7051
|
|
|
7052 @node Q6.1.4, Q6.1.5, Q6.1.3, Internet
|
|
|
7053 @unnumberedsubsec Q6.1.4: Is there a mailing list or FAQ for VM?
|
|
|
7054
|
|
|
7055 A FAQ for VM exists at @uref{http://www.wonderworks.com/vm/FAQ.html}.
|
|
|
7056
|
|
|
7057 VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug.
|
|
|
7058
|
|
|
7059 @node Q6.1.5, Q6.1.6, Q6.1.4, Internet
|
|
|
7060 @unnumberedsubsec Q6.1.5: How do I make VM stay in a single frame?
|
|
|
7061
|
|
|
7062 John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes:
|
|
|
7063
|
|
|
7064 @quotation
|
|
|
7065 @lisp
|
|
|
7066 ; Don't use multiple frames
|
|
|
7067 (setq vm-frame-per-composition nil)
|
|
|
7068 (setq vm-frame-per-folder nil)
|
|
|
7069 (setq vm-frame-per-edit nil)
|
|
|
7070 (setq vm-frame-per-summary nil)
|
|
|
7071 @end lisp
|
|
|
7072 @end quotation
|
|
|
7073
|
|
|
7074 @node Q6.1.6, Q6.2.1, Q6.1.5, Internet
|
|
|
7075 @unnumberedsubsec Q6.1.6: Customization of VM not covered in the manual, or here.
|
|
|
7076
|
|
|
7077 @email{boffi@@hp735.stru.polimi.it, giacomo boffi} writes:
|
|
|
7078
|
|
|
7079 @quotation
|
|
|
7080 The meta-answer is to look into the file @file{vm-vars.el}, in the vm
|
|
|
7081 directory of the lisp library.
|
|
|
7082
|
|
|
7083 @file{vm-vars.el} contains, initializes and carefully describes, with
|
|
|
7084 examples of usage, the plethora of user options that @emph{fully}
|
|
|
7085 control VM's behavior.
|
|
|
7086
|
|
|
7087 Enter vm-vars, @code{forward-search} for toolbar, find the variables
|
|
|
7088 that control the toolbar placement, appearance, existence, copy to your
|
|
|
7089 @file{init.el} or @file{.vm} and modify according to the
|
|
|
7090 detailed instructions.
|
|
|
7091
|
|
|
7092 The above also applies to all the various features of VM: search for
|
|
|
7093 some keywords, maybe the first you conjure isn't appropriate, find the
|
|
|
7094 appropriate variables, copy and experiment.
|
|
|
7095 @end quotation
|
|
|
7096
|
|
|
7097 @unnumberedsec 6.2: Reading Netnews and Mail with Gnus
|
|
|
7098
|
|
|
7099 @node Q6.2.1, Q6.2.2, Q6.1.6, Internet
|
|
|
7100 @unnumberedsubsec Q6.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
7101
|
|
|
7102 The Gnus numbering issues are not meant for mere mortals to know them.
|
|
|
7103 If you feel you @emph{must} enter the muddy waters of Gnus, visit the
|
|
|
7104 excellent FAQ, maintained by Justin Sheehy, at:
|
|
|
7105
|
|
|
7106 @example
|
|
|
7107 @uref{http://my.gnus.org/FAQ/}
|
|
|
7108 @end example
|
|
|
7109
|
|
|
7110 See also Gnus home page
|
|
|
7111 @example
|
|
|
7112 @uref{http://www.gnus.org/}
|
|
|
7113 @end example
|
|
|
7114
|
|
|
7115 @node Q6.2.2, Q6.3.1, Q6.2.1, Internet
|
|
|
7116 @unnumberedsubsec Q6.2.2: How do I make Gnus stay within a single frame?
|
|
|
7117
|
|
|
7118 The toolbar code to start Gnus opens the new frame---and it's a feature
|
|
|
7119 rather than a bug. If you don't like it, but would still like to click
|
|
|
7120 on the seemly icon, use the following code:
|
|
|
7121
|
|
|
7122 @lisp
|
|
|
7123 (defun toolbar-news ()
|
|
|
7124 (gnus))
|
|
|
7125 @end lisp
|
|
|
7126
|
|
|
7127 It will redefine the callback function of the icon to just call
|
|
|
7128 @code{gnus}, without all the fancy frame stuff.
|
|
|
7129
|
|
|
7130 @unnumberedsec 6.3: FTP Access
|
|
|
7131
|
|
|
7132 @node Q6.3.1, Q6.3.2, Q6.2.2, Internet
|
|
|
7133 @unnumberedsubsec Q6.3.1: Can I edit files on other hosts?
|
|
|
7134
|
|
|
7135 Yes. Of course XEmacs can use any network file system (such as NFS or
|
|
|
7136 Windows file sharing) you have available, and includes some
|
|
|
7137 optimizations and safety features appropriate to those environments.
|
|
|
7138
|
|
|
7139 It is also possible to transparently edit files via FTP, ssh, or rsh. That
|
|
|
7140 is, XEmacs makes a local copy using the transport in the background, and
|
|
|
7141 automatically refreshes the remote original from that copy when you save
|
|
|
7142 it. XEmacs also is capable of doing file system manipulations like
|
|
|
7143 creating and removing directories and files. The FTP interface is
|
|
|
7144 provided by the standard @samp{efs} package @ref{Top, EFS, , efs}. The
|
|
|
7145 ssh/rsh interface is provided by the optional @samp{tramp} package
|
|
|
7146 @ref{Top, TRAMP, , tramp}.
|
|
|
7147
|
|
|
7148 @node Q6.3.2, Q6.4.1, Q6.3.1, Internet
|
|
|
7149 @unnumberedsubsec Q6.3.2: What is EFS?
|
|
|
7150
|
|
|
7151 #### Write me.
|
|
|
7152
|
|
|
7153 @unnumberedsec 6.4: Web Browsing with W3
|
|
|
7154
|
|
|
7155 @node Q6.4.1, Q6.4.2, Q6.3.2, Internet
|
|
|
7156 @unnumberedsubsec Q6.4.1: What is W3?
|
|
|
7157
|
|
|
7158 W3 is an advanced graphical browser written in Emacs lisp that runs on
|
|
|
7159 XEmacs. It has full support for cascaded style sheets, and more...
|
|
|
7160
|
|
|
7161 It has a home web page at
|
|
|
7162 @uref{http://www.cs.indiana.edu/elisp/w3/docs.html}.
|
|
|
7163
|
|
|
7164 @node Q6.4.2, Q6.4.3, Q6.4.1, Internet
|
|
|
7165 @unnumberedsubsec Q6.4.2: How do I run W3 from behind a firewall?
|
|
|
7166
|
|
|
7167 There is a long, well-written, detailed section in the W3 manual that
|
|
|
7168 describes how to do this. Look in the section entitled "Firewalls".
|
|
|
7169
|
|
|
7170 @node Q6.4.3, , Q6.4.2, Internet
|
|
|
7171 @unnumberedsubsec Q6.4.3: Is it true that W3 supports style sheets and tables?
|
|
|
7172
|
|
|
7173 Yes, and much more. W3, as distributed with the latest XEmacs is a
|
|
|
7174 full-featured web browser.
|
|
|
7175
|
|
|
7176 @node Advanced, Other Packages, Internet, Top
|
|
|
7177 @unnumbered 7 Advanced Customization Using XEmacs Lisp
|
|
|
7178
|
|
|
7179 This is part 7 of the XEmacs Frequently Asked Questions list. This
|
|
|
7180 section is devoted to advanced customization using XEmacs Lisp.
|
|
|
7181
|
|
|
7182 @menu
|
|
2537
|
7183 7.0: Emacs Lisp and @file{init.el}
|
|
|
7184 * Q7.0.1:: What version of Emacs am I running?
|
|
|
7185 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions?
|
|
|
7186 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly.
|
|
|
7187 * Q7.0.4:: How can I add directories to the @code{load-path}?
|
|
|
7188 * Q7.0.5:: How to check if a lisp function is defined?
|
|
|
7189 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer?
|
|
|
7190
|
|
|
7191 7.1: Emacs Lisp Programming Techniques
|
|
|
7192 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
|
7193 * Q7.1.2:: Can I generate "fake" keyboard events?
|
|
|
7194 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail?
|
|
|
7195 * Q7.1.4:: What is the performance hit of @code{let}?
|
|
|
7196 * Q7.1.5:: What is the recommended use of @code{setq}?
|
|
|
7197 * Q7.1.6:: What is the typical misuse of @code{setq}?
|
|
|
7198 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down?
|
|
|
7199 * Q7.1.8:: I like recursion, does it slow things down?
|
|
|
7200 * Q7.1.9:: How do I put a glyph as annotation in a buffer?
|
|
|
7201 * Q7.1.10:: @code{map-extents} won't traverse all of my extents!
|
|
|
7202 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
|
7203
|
|
|
7204 7.2: Mathematics
|
|
|
7205 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp?
|
|
|
7206 * Q7.2.2:: XEmacs segfaults when I use very big numbers!
|
|
|
7207 * Q7.2.3:: Bignums are really slow!
|
|
|
7208 * Q7.2.4:: Equal bignums don't compare as equal! What gives?
|
|
2459
|
7209 @end menu
|
|
|
7210
|
|
2537
|
7211 @unnumberedsec 7.0: Emacs Lisp and @file{init.el}
|
|
2459
|
7212
|
|
|
7213 @node Q7.0.1, Q7.0.2, Advanced, Advanced
|
|
2537
|
7214 @unnumberedsubsec Q7.0.1: What version of Emacs am I running?
|
|
2459
|
7215
|
|
|
7216 How can @file{init.el} determine which of the family of
|
|
|
7217 Emacsen I am using?
|
|
|
7218
|
|
|
7219 To determine if you are currently running GNU Emacs 18, GNU Emacs 19,
|
|
|
7220 XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the
|
|
|
7221 example given in @file{etc/sample.init.el} (@file{etc/sample.emacs} in
|
|
|
7222 XEmacs versions prior to 21.4). There are other nifty things in there
|
|
|
7223 as well!
|
|
|
7224
|
|
|
7225 For all new code, all you really need to do is:
|
|
|
7226
|
|
|
7227 @lisp
|
|
|
7228 (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
|
|
|
7229 @end lisp
|
|
|
7230
|
|
2537
|
7231 @node Q7.0.2, Q7.0.3, Q7.0.1, Advanced
|
|
|
7232 @unnumberedsubsec Q7.0.2: How can I evaluate Emacs-Lisp expressions?
|
|
2459
|
7233
|
|
|
7234 I know I can evaluate Elisp expressions from @code{*scratch*} buffer
|
|
|
7235 with @kbd{C-j} after the expression. How do I do it from another
|
|
|
7236 buffer?
|
|
|
7237
|
|
|
7238 Press @kbd{M-:} (the default binding of @code{eval-expression}), and
|
|
|
7239 enter the expression to the minibuffer.
|
|
|
7240
|
|
2537
|
7241 @node Q7.0.3, Q7.0.4, Q7.0.2, Advanced
|
|
|
7242 @unnumberedsubsec Q7.0.3: @code{(setq tab-width 6)} behaves oddly.
|
|
2459
|
7243
|
|
|
7244 If you put @code{(setq tab-width 6)} in your
|
|
|
7245 @file{init.el} file it does not work! Is there a reason
|
|
|
7246 for this? If you do it at the EVAL prompt it works fine!! How strange.
|
|
|
7247
|
|
|
7248 Use @code{setq-default} instead, since @code{tab-width} is
|
|
|
7249 all-buffer-local.
|
|
|
7250
|
|
2537
|
7251 @node Q7.0.4, Q7.0.5, Q7.0.3, Advanced
|
|
|
7252 @unnumberedsubsec Q7.0.4: How can I add directories to the @code{load-path}?
|
|
2459
|
7253
|
|
|
7254 Here are two ways to do that, one that puts your directories at the
|
|
|
7255 front of the load-path, the other at the end:
|
|
|
7256
|
|
|
7257 @lisp
|
|
|
7258 ;;; Add things at the beginning of the load-path, do not add
|
|
|
7259 ;;; duplicate directories:
|
|
|
7260 (pushnew "bar" load-path :test 'equal)
|
|
|
7261
|
|
|
7262 (pushnew "foo" load-path :test 'equal)
|
|
|
7263
|
|
|
7264 ;;; Add things at the end, unconditionally
|
|
|
7265 (setq load-path (nconc load-path '("foo" "bar")))
|
|
|
7266 @end lisp
|
|
|
7267
|
|
|
7268 @email{keithh@@nortel.ca, keith (k.p.) hanlan} writes:
|
|
|
7269
|
|
|
7270 @quotation
|
|
|
7271 To add directories using Unix shell metacharacters use
|
|
|
7272 @file{expand-file-name} like this:
|
|
|
7273
|
|
|
7274 @lisp
|
|
|
7275 (push (expand-file-name "~keithh/.emacsdir") load-path)
|
|
|
7276 @end lisp
|
|
|
7277 @end quotation
|
|
|
7278
|
|
2537
|
7279 @node Q7.0.5, Q7.0.6, Q7.0.4, Advanced
|
|
|
7280 @unnumberedsubsec Q7.0.5: How to check if a lisp function is defined?
|
|
2459
|
7281
|
|
|
7282 Use the following elisp:
|
|
|
7283
|
|
|
7284 @lisp
|
|
|
7285 (fboundp 'foo)
|
|
|
7286 @end lisp
|
|
|
7287
|
|
|
7288 It's almost always a mistake to test @code{emacs-version} or any similar
|
|
|
7289 variables.
|
|
|
7290
|
|
|
7291 Instead, use feature-tests, such as @code{featurep}, @code{boundp},
|
|
|
7292 @code{fboundp}, or even simple behavioral tests, eg.:
|
|
|
7293
|
|
|
7294 @lisp
|
|
|
7295 (defvar foo-old-losing-code-p
|
|
|
7296 (condition-case nil (progn (losing-code t) nil)
|
|
|
7297 (wrong-number-of-arguments t)))
|
|
|
7298 @end lisp
|
|
|
7299
|
|
|
7300 There is an incredible amount of broken code out there which could work
|
|
|
7301 much better more often in more places if it did the above instead of
|
|
|
7302 trying to divine its environment from the value of one variable.
|
|
|
7303
|
|
2537
|
7304 @node Q7.0.6, Q7.1.1, Q7.0.5, Advanced
|
|
|
7305 @unnumberedsubsec Q7.0.6: Can I force the output of @code{(face-list)} to a buffer?
|
|
2459
|
7306
|
|
|
7307 It would be good having it in a buffer, as the output of
|
|
|
7308 @code{(face-list)} is too wide to fit to a minibuffer.
|
|
|
7309
|
|
|
7310 Evaluate the expression in the @samp{*scratch*} buffer with point after
|
|
|
7311 the rightmost paren and typing @kbd{C-j}.
|
|
|
7312
|
|
|
7313 If the minibuffer smallness is the only problem you encounter, you can
|
|
|
7314 simply press @kbd{C-h l} to get the former minibuffer contents in a
|
|
|
7315 buffer.
|
|
|
7316
|
|
2537
|
7317 @unnumberedsec 7.1: Emacs Lisp Programming Techniques
|
|
|
7318
|
|
|
7319 @node Q7.1.1, Q7.1.2, Q7.0.6, Advanced
|
|
|
7320 @unnumberedsubsec Q7.1.1: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
2459
|
7321
|
|
|
7322 @email{clerik@@naggum.no, Erik Naggum} writes;
|
|
|
7323
|
|
|
7324 @quotation
|
|
|
7325 Emacs has a legacy of keyboards that produced characters with modifier
|
|
|
7326 bits, and therefore map a variety of input systems into this scheme even
|
|
|
7327 today. XEmacs is instead optimized for X events. This causes an
|
|
|
7328 incompatibility in the way key sequences are specified, but both Emacs
|
|
|
7329 and XEmacs will accept a key sequence as a vector of lists of modifiers
|
|
|
7330 that ends with a key, e.g., to bind @kbd{M-C-a}, you would say
|
|
|
7331 @code{[(meta control a)]} in both Emacsen. XEmacs has an abbreviated
|
|
|
7332 form for a single key, just (meta control a). Emacs has an abbreviated
|
|
|
7333 form for the Control and the Meta modifiers to string-characters (the
|
|
|
7334 ASCII characters), as in @samp{\M-\C-a}. XEmacs users need to be aware
|
|
|
7335 that the abbreviated form works only for one-character key sequences,
|
|
|
7336 while Emacs users need to be aware that the string-character is rather
|
|
|
7337 limited. Specifically, the string-character can accommodate only 256
|
|
|
7338 different values, 128 of which have the Meta modifier and 128 of which
|
|
|
7339 have not. In each of these blocks, only 32 characters have the Control
|
|
|
7340 modifier. Whereas @code{[(meta control A)]} differs from @code{[(meta
|
|
|
7341 control a)]} because the case differs, @samp{\M-\C-a} and @samp{\M-\C-A}
|
|
|
7342 do not. Programmers are advised to use the full common form, both
|
|
|
7343 because it is more readable and less error-prone, and because it is
|
|
|
7344 supported by both Emacsen.
|
|
|
7345 @end quotation
|
|
|
7346
|
|
|
7347 Another (even safer) way to be sure of the key-sequences is to use the
|
|
|
7348 @code{read-kbd-macro} function, which takes a string like @samp{C-c
|
|
|
7349 <up>}, and converts it to the internal key representation of the Emacs
|
|
|
7350 you use. The function is available both on XEmacs and GNU Emacs.
|
|
|
7351
|
|
2537
|
7352 @node Q7.1.2, Q7.1.3, Q7.1.1, Advanced
|
|
|
7353 @unnumberedsubsec Q7.1.2: Can I generate "fake" keyboard events?
|
|
2459
|
7354
|
|
|
7355 I wonder if there is an interactive function that can generate
|
|
|
7356 @dfn{fake} keyboard events. This way, I could simply map them inside
|
|
|
7357 XEmacs.
|
|
|
7358
|
|
|
7359 This seems to work:
|
|
|
7360
|
|
|
7361 @lisp
|
|
|
7362 (defun cg--generate-char-event (ch)
|
|
|
7363 "Generate an event, as if ch has been typed"
|
|
|
7364 (dispatch-event (character-to-event ch)))
|
|
|
7365
|
|
|
7366 ;; Backspace and Delete stuff
|
|
|
7367 (global-set-key [backspace]
|
|
|
7368 (lambda () (interactive) (cg--generate-char-event 127)))
|
|
|
7369 (global-set-key [unknown_keysym_0x4]
|
|
|
7370 (lambda () (interactive) (cg--generate-char-event 4)))
|
|
|
7371 @end lisp
|
|
|
7372
|
|
2537
|
7373 @node Q7.1.3, Q7.1.4, Q7.1.2, Advanced
|
|
|
7374 @unnumberedsubsec Q7.1.3: Could you explain @code{read-kbd-macro} in more detail?
|
|
2459
|
7375
|
|
|
7376 The @code{read-kbd-macro} function returns the internal Emacs
|
|
|
7377 representation of a human-readable string (which is its argument).
|
|
|
7378 Thus:
|
|
|
7379
|
|
|
7380 @lisp
|
|
|
7381 (read-kbd-macro "C-c C-a")
|
|
|
7382 @result{} [(control ?c) (control ?a)]
|
|
|
7383
|
|
|
7384 (read-kbd-macro "C-c C-. <up>")
|
|
|
7385 @result{} [(control ?c) (control ?.) up]
|
|
|
7386 @end lisp
|
|
|
7387
|
|
|
7388 In GNU Emacs the same forms will be evaluated to what GNU Emacs
|
|
|
7389 understands internally---the sequences @code{"\C-x\C-c"} and @code{[3
|
|
|
7390 67108910 up]}, respectively.
|
|
|
7391
|
|
|
7392 The exact @dfn{human-readable} syntax is defined in the docstring of
|
|
|
7393 @code{edmacro-mode}. I'll repeat it here, for completeness.
|
|
|
7394
|
|
|
7395 @quotation
|
|
|
7396 Format of keyboard macros during editing:
|
|
|
7397
|
|
|
7398 Text is divided into @dfn{words} separated by whitespace. Except for
|
|
|
7399 the words described below, the characters of each word go directly as
|
|
|
7400 characters of the macro. The whitespace that separates words is
|
|
|
7401 ignored. Whitespace in the macro must be written explicitly, as in
|
|
|
7402 @kbd{foo @key{SPC} bar @key{RET}}.
|
|
|
7403
|
|
|
7404 @itemize @bullet
|
|
|
7405 @item
|
|
|
7406 The special words @kbd{RET}, @kbd{SPC}, @kbd{TAB}, @kbd{DEL}, @kbd{LFD},
|
|
|
7407 @kbd{ESC}, and @kbd{NUL} represent special control characters. The
|
|
|
7408 words must be written in uppercase.
|
|
|
7409
|
|
|
7410 @item
|
|
|
7411 A word in angle brackets, e.g., @code{<return>}, @code{<down>}, or
|
|
|
7412 @code{<f1>}, represents a function key. (Note that in the standard
|
|
|
7413 configuration, the function key @code{<return>} and the control key
|
|
|
7414 @key{RET} are synonymous.) You can use angle brackets on the words
|
|
|
7415 @key{RET}, @key{SPC}, etc., but they are not required there.
|
|
|
7416
|
|
|
7417 @item
|
|
|
7418 Keys can be written by their @sc{ascii} code, using a backslash followed
|
|
|
7419 by up to six octal digits. This is the only way to represent keys with
|
|
|
7420 codes above \377.
|
|
|
7421
|
|
|
7422 @item
|
|
|
7423 One or more prefixes @kbd{M-} (meta), @kbd{C-} (control), @kbd{S-}
|
|
|
7424 (shift), @kbd{A-} (alt), @kbd{H-} (hyper), and @kbd{s-} (super) may
|
|
|
7425 precede a character or key notation. For function keys, the prefixes
|
|
|
7426 may go inside or outside of the brackets: @code{C-<down>} @equiv{}
|
|
|
7427 @code{<C-down>}. The prefixes may be written in any order: @kbd{M-C-x}
|
|
|
7428 @equiv{} @kbd{C-M-x}.
|
|
|
7429
|
|
|
7430 Prefixes are not allowed on multi-key words, e.g., @kbd{C-abc}, except
|
|
|
7431 that the Meta prefix is allowed on a sequence of digits and optional
|
|
|
7432 minus sign: @kbd{M--123} @equiv{} @kbd{M-- M-1 M-2 M-3}.
|
|
|
7433
|
|
|
7434 @item
|
|
|
7435 The @code{^} notation for control characters also works: @kbd{^M}
|
|
|
7436 @equiv{} @kbd{C-m}.
|
|
|
7437
|
|
|
7438 @item
|
|
|
7439 Double angle brackets enclose command names: @code{<<next-line>>} is
|
|
|
7440 shorthand for @kbd{M-x next-line @key{RET}}.
|
|
|
7441
|
|
|
7442 @item
|
|
|
7443 Finally, @code{REM} or @code{;;} causes the rest of the line to be
|
|
|
7444 ignored as a comment.
|
|
|
7445 @end itemize
|
|
|
7446
|
|
|
7447 Any word may be prefixed by a multiplier in the form of a decimal number
|
|
|
7448 and @code{*}: @code{3*<right>} @equiv{} @code{<right> <right> <right>},
|
|
|
7449 and @code{10*foo} @equiv{}
|
|
|
7450 @iftex
|
|
|
7451 @*
|
|
|
7452 @end iftex
|
|
|
7453 @code{foofoofoofoofoofoofoofoofoofoo}.
|
|
|
7454
|
|
|
7455 Multiple text keys can normally be strung together to form a word, but
|
|
|
7456 you may need to add whitespace if the word would look like one of the
|
|
|
7457 above notations: @code{; ; ;} is a keyboard macro with three semicolons,
|
|
|
7458 but @code{;;;} is a comment. Likewise, @code{\ 1 2 3} is four keys but
|
|
|
7459 @code{\123} is a single key written in octal, and @code{< right >} is
|
|
|
7460 seven keys but @code{<right>} is a single function key. When in doubt,
|
|
|
7461 use whitespace.
|
|
|
7462 @end quotation
|
|
|
7463
|
|
2537
|
7464 @node Q7.1.4, Q7.1.5, Q7.1.3, Advanced
|
|
|
7465 @unnumberedsubsec Q7.1.4: What is the performance hit of @code{let}?
|
|
2459
|
7466
|
|
|
7467 In most cases, not noticeable. Besides, there's no avoiding
|
|
|
7468 @code{let}---you have to bind your local variables, after all. Some
|
|
|
7469 pose a question whether to nest @code{let}s, or use one @code{let} per
|
|
|
7470 function. I think because of clarity and maintenance (and possible
|
|
|
7471 future implementation), @code{let}-s should be used (nested) in a way to
|
|
|
7472 provide the clearest code.
|
|
|
7473
|
|
2537
|
7474 @node Q7.1.5, Q7.1.6, Q7.1.4, Advanced
|
|
|
7475 @unnumberedsubsec Q7.1.5: What is the recommended use of @code{setq}?
|
|
2459
|
7476
|
|
|
7477 @itemize @bullet
|
|
|
7478 @item Global variables
|
|
|
7479
|
|
|
7480 You will typically @code{defvar} your global variable to a default
|
|
|
7481 value, and use @code{setq} to set it later.
|
|
|
7482
|
|
|
7483 It is never a good practice to @code{setq} user variables (like
|
|
|
7484 @code{case-fold-search}, etc.), as it ignores the user's choice
|
|
|
7485 unconditionally. Note that @code{defvar} doesn't change the value of a
|
|
|
7486 variable if it was bound previously. If you wish to change a
|
|
|
7487 user-variable temporarily, use @code{let}:
|
|
|
7488
|
|
|
7489 @lisp
|
|
|
7490 (let ((case-fold-search nil))
|
|
|
7491 ... ; code with searches that must be case-sensitive
|
|
|
7492 ...)
|
|
|
7493 @end lisp
|
|
|
7494
|
|
|
7495 You will notice the user-variables by their docstrings beginning with an
|
|
|
7496 asterisk (a convention).
|
|
|
7497
|
|
|
7498 @item Local variables
|
|
|
7499
|
|
|
7500 Bind them with @code{let}, which will unbind them (or restore their
|
|
|
7501 previous value, if they were bound) after exiting from the @code{let}
|
|
|
7502 form. Change the value of local variables with @code{setq} or whatever
|
|
|
7503 you like (e.g. @code{incf}, @code{setf} and such). The @code{let} form
|
|
|
7504 can even return one of its local variables.
|
|
|
7505
|
|
|
7506 Typical usage:
|
|
|
7507
|
|
|
7508 @lisp
|
|
|
7509 ;; iterate through the elements of the list returned by
|
|
|
7510 ;; `hairy-function-that-returns-list'
|
|
|
7511 (let ((l (hairy-function-that-returns-list)))
|
|
|
7512 (while l
|
|
|
7513 ... do something with (car l) ...
|
|
|
7514 (setq l (cdr l))))
|
|
|
7515 @end lisp
|
|
|
7516
|
|
|
7517 Another typical usage includes building a value simply to work with it.
|
|
|
7518
|
|
|
7519 @lisp
|
|
|
7520 ;; Build the mode keymap out of the key-translation-alist
|
|
|
7521 (let ((inbox (file-truename (expand-file-name box)))
|
|
|
7522 (i 0))
|
|
|
7523 ... code dealing with inbox ...
|
|
|
7524 inbox)
|
|
|
7525 @end lisp
|
|
|
7526
|
|
|
7527 This piece of code uses the local variable @code{inbox}, which becomes
|
|
|
7528 unbound (or regains old value) after exiting the form. The form also
|
|
|
7529 returns the value of @code{inbox}, which can be reused, for instance:
|
|
|
7530
|
|
|
7531 @lisp
|
|
|
7532 (setq foo-processed-inbox
|
|
|
7533 (let .....))
|
|
|
7534 @end lisp
|
|
|
7535 @end itemize
|
|
|
7536
|
|
2537
|
7537 @node Q7.1.6, Q7.1.7, Q7.1.5, Advanced
|
|
|
7538 @unnumberedsubsec Q7.1.6: What is the typical misuse of @code{setq}?
|
|
2459
|
7539
|
|
|
7540 A typical misuse is probably @code{setq}ing a variable that was meant to
|
|
|
7541 be local. Such a variable will remain bound forever, never to be
|
|
|
7542 garbage-collected. For example, the code doing:
|
|
|
7543
|
|
|
7544 @lisp
|
|
|
7545 (defun my-function (whatever)
|
|
|
7546 (setq a nil)
|
|
|
7547 ... build a large list ...
|
|
|
7548 ... and exit ...)
|
|
|
7549 @end lisp
|
|
|
7550
|
|
|
7551 does a bad thing, as @code{a} will keep consuming memory, never to be
|
|
|
7552 unbound. The correct thing is to do it like this:
|
|
|
7553
|
|
|
7554 @lisp
|
|
|
7555 (defun my-function (whatever)
|
|
|
7556 (let (a) ; default initialization is to nil
|
|
|
7557 ... build a large list ...
|
|
|
7558 ... and exit, unbinding `a' in the process ...)
|
|
|
7559 @end lisp
|
|
|
7560
|
|
|
7561 Not only is this prettier syntactically, but it makes it possible for
|
|
|
7562 Emacs to garbage-collect the objects which @code{a} used to reference.
|
|
|
7563
|
|
|
7564 Note that even global variables should not be @code{setq}ed without
|
|
|
7565 @code{defvar}ing them first, because the byte-compiler issues warnings.
|
|
|
7566 The reason for the warning is the following:
|
|
|
7567
|
|
|
7568 @lisp
|
|
|
7569 (defun flurgoze nil) ; ok, global internal variable
|
|
|
7570 ...
|
|
|
7571
|
|
|
7572 (setq flurghoze t) ; ops! a typo, but semantically correct.
|
|
|
7573 ; however, the byte-compiler warns.
|
|
|
7574
|
|
|
7575 While compiling toplevel forms:
|
|
|
7576 ** assignment to free variable flurghoze
|
|
|
7577 @end lisp
|
|
|
7578
|
|
2537
|
7579 @node Q7.1.7, Q7.1.8, Q7.1.6, Advanced
|
|
|
7580 @unnumberedsubsec Q7.1.7: I like the @code{do} form of cl, does it slow things down?
|
|
2459
|
7581
|
|
|
7582 It shouldn't. Here is what Dave Gillespie has to say about cl.el
|
|
|
7583 performance:
|
|
|
7584
|
|
|
7585 @quotation
|
|
|
7586 Many of the advanced features of this package, such as @code{defun*},
|
|
|
7587 @code{loop}, and @code{setf}, are implemented as Lisp macros. In
|
|
|
7588 byte-compiled code, these complex notations will be expanded into
|
|
|
7589 equivalent Lisp code which is simple and efficient. For example, the
|
|
|
7590 forms
|
|
|
7591
|
|
|
7592 @lisp
|
|
|
7593 (incf i n)
|
|
|
7594 (push x (car p))
|
|
|
7595 @end lisp
|
|
|
7596
|
|
|
7597 are expanded at compile-time to the Lisp forms
|
|
|
7598
|
|
|
7599 @lisp
|
|
|
7600 (setq i (+ i n))
|
|
|
7601 (setcar p (cons x (car p)))
|
|
|
7602 @end lisp
|
|
|
7603
|
|
|
7604 which are the most efficient ways of doing these respective operations
|
|
|
7605 in Lisp. Thus, there is no performance penalty for using the more
|
|
|
7606 readable @code{incf} and @code{push} forms in your compiled code.
|
|
|
7607
|
|
|
7608 @emph{Interpreted} code, on the other hand, must expand these macros
|
|
|
7609 every time they are executed. For this reason it is strongly
|
|
|
7610 recommended that code making heavy use of macros be compiled. (The
|
|
|
7611 features labelled @dfn{Special Form} instead of @dfn{Function} in this
|
|
|
7612 manual are macros.) A loop using @code{incf} a hundred times will
|
|
|
7613 execute considerably faster if compiled, and will also garbage-collect
|
|
|
7614 less because the macro expansion will not have to be generated, used,
|
|
|
7615 and thrown away a hundred times.
|
|
|
7616
|
|
|
7617 You can find out how a macro expands by using the @code{cl-prettyexpand}
|
|
|
7618 function.
|
|
|
7619 @end quotation
|
|
|
7620
|
|
2537
|
7621 @node Q7.1.8, Q7.1.9, Q7.1.7, Advanced
|
|
|
7622 @unnumberedsubsec Q7.1.8: I like recursion, does it slow things down?
|
|
2459
|
7623
|
|
|
7624 Yes. The Emacs byte-compiler cannot do much to optimize recursion. But
|
|
|
7625 think well whether this is a real concern in Emacs. Much of the Emacs
|
|
|
7626 slowness comes from internal mechanisms such as redisplay, or from the
|
|
|
7627 fact that it is an interpreter.
|
|
|
7628
|
|
|
7629 Please try not to make your code much uglier to gain a very small speed
|
|
|
7630 gain. It's not usually worth it.
|
|
|
7631
|
|
2537
|
7632 @node Q7.1.9, Q7.1.10, Q7.1.8, Advanced
|
|
|
7633 @unnumberedsubsec Q7.1.9: How do I put a glyph as annotation in a buffer?
|
|
2459
|
7634
|
|
|
7635 Here is a solution that will insert the glyph annotation at the
|
|
|
7636 beginning of buffer:
|
|
|
7637
|
|
|
7638 @lisp
|
|
|
7639 (make-annotation (make-glyph '([FORMAT :file FILE]
|
|
|
7640 [string :data "fallback-text"]))
|
|
|
7641 (point-min)
|
|
|
7642 'text
|
|
|
7643 (current-buffer))
|
|
|
7644 @end lisp
|
|
|
7645
|
|
|
7646 Replace @samp{FORMAT} with an unquoted symbol representing the format of
|
|
|
7647 the image (e.g. @code{xpm}, @code{xbm}, @code{gif}, @code{jpeg}, etc.)
|
|
|
7648 Instead of @samp{FILE}, use the image file name
|
|
|
7649 (e.g.
|
|
|
7650 @iftex
|
|
|
7651 @*
|
|
|
7652 @end iftex
|
|
|
7653 @file{/usr/local/lib/xemacs-21.4/etc/recycle.xpm}).
|
|
|
7654
|
|
|
7655 You can turn this to a function (that optionally prompts you for a file
|
|
|
7656 name), and inserts the glyph at @code{(point)} instead of
|
|
|
7657 @code{(point-min)}.
|
|
|
7658
|
|
2537
|
7659 @node Q7.1.10, Q7.1.11, Q7.1.9, Advanced
|
|
|
7660 @unnumberedsubsec Q7.1.10: @code{map-extents} won't traverse all of my extents!
|
|
2459
|
7661
|
|
|
7662 I tried to use @code{map-extents} to do an operation on all the extents
|
|
|
7663 in a region. However, it seems to quit after processing a random number
|
|
|
7664 of extents. Is it buggy?
|
|
|
7665
|
|
|
7666 No. The documentation of @code{map-extents} states that it will iterate
|
|
|
7667 across the extents as long as @var{function} returns @code{nil}.
|
|
|
7668 Unexperienced programmers often forget to return @code{nil} explicitly,
|
|
|
7669 which results in buggy code. For instance, the following code is
|
|
|
7670 supposed to delete all the extents in a buffer, and issue as many
|
|
|
7671 @samp{fubar!} messages.
|
|
|
7672
|
|
|
7673 @lisp
|
|
|
7674 (map-extents (lambda (ext ignore)
|
|
|
7675 (delete-extent ext)
|
|
|
7676 (message "fubar!")))
|
|
|
7677 @end lisp
|
|
|
7678
|
|
|
7679 Instead, it will delete only the first extent, and stop right there --
|
|
|
7680 because @code{message} will return a non-nil value. The correct code
|
|
|
7681 is:
|
|
|
7682
|
|
|
7683 @lisp
|
|
|
7684 (map-extents (lambda (ext ignore)
|
|
|
7685 (delete-extent ext)
|
|
|
7686 (message "fubar!")
|
|
|
7687 nil))
|
|
|
7688 @end lisp
|
|
|
7689
|
|
2537
|
7690 @node Q7.1.11, Q7.2.1, Q7.1.10, Advanced
|
|
|
7691 @unnumberedsubsec Q7.1.11: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
2459
|
7692 @c New
|
|
|
7693
|
|
|
7694 @email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
|
|
|
7695 @quotation
|
|
|
7696 Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence},
|
|
|
7697 press a key (say @key{RET} in the Gnus Group buffer), and get the
|
|
|
7698 results using @kbd{M-x profile-results}. It should give you an idea of
|
|
|
7699 where the time is being spent.
|
|
|
7700 @end quotation
|
|
|
7701
|
|
2537
|
7702 @unnumberedsec 7.2: Mathematics
|
|
|
7703
|
|
|
7704 @node Q7.2.1, Q7.2.2, Q7.1.11, Advanced
|
|
|
7705 @unnumberedsubsec Q7.2.1: What are bignums, ratios, and bigfloats in Lisp?
|
|
2459
|
7706
|
|
|
7707 Thanks to @email{james@@xemacs.org, Jerry James}, XEmacs 21.5.18 and
|
|
|
7708 later can use the capabilities of multiple-precision libraries that may
|
|
|
7709 be available for your platform. The GNU Multiple Precision (GMP) and
|
|
|
7710 BSD Multiple Precision (MP) libraries are partially supported. GMP
|
|
|
7711 gives you @dfn{bignums} (arbitrary precision integers), @dfn{ratios}
|
|
|
7712 (arbitrary precision fractions), and @dfn{bigfloats} (arbitrary
|
|
|
7713 precision floating point numbers). GNU MP is better-supported by XEmacs
|
|
|
7714 at the time of writing (2004-04-06). BSD MP support does not include
|
|
|
7715 ratios or bigfloats, and it throws errors that aren't understood.
|
|
|
7716
|
|
|
7717 In most cases, bignum support should be transparent to users and Lisp
|
|
|
7718 programmers. A bignum-enabled XEmacs will automatically convert from
|
|
|
7719 fixnums to bignums and back in pure integer arithmetic, and for GNU MP,
|
|
|
7720 from floats to bigfloats. (Bigfloats must be explicitly coerced to
|
|
|
7721 other types, even if they are exactly representable by less precise
|
|
|
7722 types.) The Lisp reader and printer have been enhanced to handle
|
|
|
7723 bignums, as have the mathematical functions. Rationals (fixnums,
|
|
|
7724 bignums, and ratios) are printed using the @samp{%d}, @samp{%o},
|
|
|
7725 @samp{%x}, and @samp{%u} format conversions. The read syntax for ratios
|
|
|
7726 is @samp{3/5}.
|
|
|
7727
|
|
|
7728 User-visible changes in behavior include (in probable order of annoyance)
|
|
|
7729
|
|
|
7730 @itemize
|
|
|
7731 @item
|
|
|
7732 Arithmetic can cause a segfault, depending on your MP library
|
|
2537
|
7733 @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}.
|
|
2459
|
7734
|
|
|
7735 @item
|
|
|
7736 Terminology is not Common-Lisp-conforming. For example, ``integer'' for
|
|
|
7737 Emacs Lisp means what Common Lisp calls ``fixnum''. This issue is being
|
|
|
7738 investigated, but the use of ``integer'' for fixnum is pervasive and may
|
|
|
7739 cause backward-compatibility and GNU-Emacs-compatibility problems.
|
|
|
7740
|
|
|
7741 @item
|
|
|
7742 Many operations that used to cause a range error now succeed, with
|
|
|
7743 intermediate results and return values coerced to bignums as needed.
|
|
|
7744
|
|
|
7745 @item
|
|
|
7746 An atom with ratio read syntax now returns a number, not a symbol.
|
|
|
7747
|
|
|
7748 @item
|
|
|
7749 The @samp{%u} format conversion will now give an error if its argument
|
|
|
7750 is negative. (Without MP, it prints a number which Lisp can't read.)
|
|
|
7751 @end itemize
|
|
|
7752
|
|
|
7753 @emph{Surgeon General's Warning}: The automatic conversions cannot be
|
|
|
7754 disabled at runtime. New functions have been added which produce
|
|
|
7755 ratios, so there should be few surprises with type conflicts, but they
|
|
|
7756 can't be ruled out. ``Arbitrary'' precision means precisely what it
|
|
|
7757 says. If you work with extremely large numbers, your machine may
|
|
|
7758 arbitrarily decide to hand you an unpleasant surprise rather than a
|
|
2537
|
7759 bignum @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}.
|
|
2459
|
7760
|
|
|
7761 To configure with GNU MP, add
|
|
|
7762 @samp{--use-number-lib=gmp}
|
|
|
7763 to your invocation of @file{configure}. For BSD MP, use
|
|
|
7764 @samp{--use-number-lib=mp}.
|
|
|
7765
|
|
|
7766 If you would like to help with bignum support, especially on BSD MP,
|
|
|
7767 please subscribe to the @uref{http://www.xemacs.org/Lists/#xemacs-beta,
|
|
|
7768 XEmacs Beta mailing list}, and book up on @file{number-gmp.h} and
|
|
|
7769 @file{number-mp.h}. Jerry has promised to write internals documentation
|
|
|
7770 eventually, but if your skills run more to analysis and documentation
|
|
|
7771 than to writing new code, feel free to fill in the gap!
|
|
|
7772
|
|
|
7773
|
|
2537
|
7774 @node Q7.2.2, Q7.2.3, Q7.2.1, Advanced
|
|
|
7775 @unnumberedsubsec Q7.2.2: XEmacs segfaults when I use very big numbers!
|
|
2459
|
7776
|
|
|
7777 GMP by default allocates temporaries on the stack. If you run out of
|
|
|
7778 stack space, you're dead; there is no way that we know of to reliably
|
|
|
7779 detect this condition, because @samp{alloca} is typically implemented to
|
|
|
7780 be @emph{fast} rather than robust. If you just need a little more
|
|
|
7781 oomph, use a bigger stack (@emph{e.g.}, the @file{ulimit -s} command in
|
|
|
7782 bash(1)). If you want robustness at the cost of speed, configure GMP
|
|
|
7783 with @samp{--disable-alloca} and rebuild the GMP library.
|
|
|
7784
|
|
|
7785 We do not know whether BSD MP uses @samp{alloca} or not. Please send
|
|
|
7786 any information you have as a bug report (@kbd{M-x report-xemacs-bug
|
|
|
7787 @key{RET}}), which will give us platform information. (We do know that
|
|
|
7788 BSD MP implementations vary across vendors, but how much, we do not know
|
|
|
7789 yet.)
|
|
|
7790
|
|
|
7791
|
|
2537
|
7792 @node Q7.2.3, Q7.2.4, Q7.2.2, Advanced
|
|
|
7793 @unnumberedsubsec Q7.2.3: Bignums are really slow!
|
|
2459
|
7794
|
|
|
7795 Many Linux distributions compile all their packages for the i386, and
|
|
|
7796 this is costly. An optimized version can give you two or three orders
|
|
|
7797 of magnitude better performance for a Pentium III or IV. (Yes, really.
|
|
|
7798 See @uref{http://www.swox.com/gmp/gmp-speed.html}.)
|
|
|
7799
|
|
|
7800
|
|
2537
|
7801 @node Q7.2.4, , Q7.2.3, Advanced
|
|
|
7802 @unnumberedsubsec Q7.2.4: Equal bignums don't compare as equal! What gives?
|
|
2459
|
7803
|
|
|
7804 Ah, Grasshopper, I see you are using @code{(eq x y)}. The Bodhisattva
|
|
|
7805 CLTL2 warned of the illusion that equal numbers would be @samp{eq}!
|
|
|
7806 Meditate on the deeper truths of @samp{eql}, in which numbers of the same
|
|
|
7807 type which have equal values compare equal, and @samp{=}, which does any
|
|
|
7808 necessary type coercions before comparing for equality.
|
|
|
7809
|
|
|
7810 Yeah, yeah, it has always worked for integer types, because fixnums and
|
|
|
7811 characters have an immediate representation. Sorry about that;
|
|
|
7812 arbitrary precision obviously requires consing new objects because the
|
|
|
7813 objects are ``large'' and of variable size, and the definition of
|
|
|
7814 @samp{eq} does not permit different objects to compare as equal.
|
|
|
7815
|
|
|
7816 @node Other Packages, Current Events, Advanced, Top
|
|
|
7817 @unnumbered 8 Other External Packages
|
|
|
7818
|
|
|
7819 This is part 8 of the XEmacs Frequently Asked Questions list. This
|
|
|
7820 section is devoted to miscellaneous external packages not covered
|
|
|
7821 elsewhere in XEmacs.
|
|
|
7822
|
|
|
7823 @menu
|
|
2537
|
7824 8.0: TeX
|
|
2459
|
7825 * Q8.0.1:: Is there something better than LaTeX mode?
|
|
|
7826 * Q8.0.2:: What is AUCTeX? Where do you get it?
|
|
|
7827 * Q8.0.3:: Problems installing AUCTeX.
|
|
|
7828 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline?
|
|
|
7829
|
|
|
7830 8.1: Other Unbundled Packages
|
|
|
7831 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
|
7832 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets?
|
|
|
7833 * Q8.1.3:: Is there a MatLab mode?
|
|
|
7834
|
|
|
7835 8.2: Environments Built Around XEmacs
|
|
|
7836 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop?
|
|
|
7837 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21?
|
|
|
7838 * Q8.2.3:: What is/was Energize?
|
|
|
7839 * Q8.2.4:: What is Infodock?
|
|
|
7840 @end menu
|
|
|
7841
|
|
|
7842 @unnumberedsec 8.0: TeX
|
|
|
7843
|
|
|
7844 @node Q8.0.1, Q8.0.2, Other Packages, Other Packages
|
|
|
7845 @unnumberedsubsec Q8.0.1: Is there something better than LaTeX mode?
|
|
2417
|
7846
|
|
|
7847 @email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes:
|
|
|
7848
|
|
|
7849 @quotation
|
|
|
7850 The standard TeX modes leave much to be desired, and are somewhat
|
|
2459
|
7851 leniently maintained. Serious TeX users use AUCTeX (@pxref{Q8.0.2,
|
|
2417
|
7852 What is AUCTeX? Where do you get it?}).
|
|
|
7853 @end quotation
|
|
|
7854
|
|
2459
|
7855 @node Q8.0.2, Q8.0.3, Q8.0.1, Other Packages
|
|
|
7856 @unnumberedsubsec Q8.0.2: What is AUCTeX? Where do you get it?
|
|
2417
|
7857
|
|
|
7858 AUCTeX is a complex and sophisticated editing package dedicated to TeX
|
|
|
7859 and related text formatting languages, including LaTeX and Texinfo.
|
|
|
7860 It provides support for running TeX on a file or part of a file,
|
|
|
7861 include files, and of course shortcuts for entering common TeX macros,
|
|
|
7862 LaTeX environments, etc, and for fontlock.
|
|
|
7863
|
|
|
7864 AUCTeX is a standard package provided by XEmacs. You can get it as
|
|
|
7865 usual through the @kbd{M-x list-packages} interface. It is also
|
|
|
7866 included in the (non-Mule) SUMO package. The AUCTeX XEmacs package is
|
|
|
7867 maintained by Uwe Brauer <GET MAIL ADDRESS>.
|
|
|
7868
|
|
|
7869 AUCTeX is extremely complicated, and its developers primarily
|
|
|
7870 use GNU Emacs. Not all features of the bleeding edge version
|
|
|
7871 of AUCTeX are immediately ported to XEmacs; if you need
|
|
|
7872 these, you may be better off getting the most recent versions
|
|
|
7873 from the GNU AUCTeX project on @uref{http://savannah.gnu.org}.
|
|
|
7874
|
|
2459
|
7875 @node Q8.0.3, Q8.0.4, Q8.0.2, Other Packages
|
|
|
7876 @unnumberedsubsec Q8.0.3: Problems installing AUCTeX.
|
|
2417
|
7877
|
|
|
7878 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
|
|
|
7879
|
|
|
7880 @quotation
|
|
|
7881 AUCTeX works fine on both stock Emacs and XEmacs has been doing so for
|
|
|
7882 a very very long time. This is mostly due to the work of
|
|
|
7883 @email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu}
|
|
|
7884 package. Which leads to what is probably the problem...
|
|
|
7885 @end quotation
|
|
|
7886
|
|
|
7887 Most problems with AUCTeX are one of two things:
|
|
|
7888
|
|
|
7889 @itemize @bullet
|
|
|
7890 @item
|
|
|
7891 The TeX-lisp-directory in @file{tex-site.el} and the makefile don't
|
|
|
7892 match.
|
|
|
7893
|
|
|
7894 Fix: make sure you configure AUCTeX properly @strong{before} installing.
|
|
|
7895
|
|
|
7896 @item
|
|
|
7897 You have an old version of easymenu.el in your path.
|
|
|
7898
|
|
|
7899 Fix: use @code{locate-library} and remove old versions to make sure it
|
|
|
7900 @strong{only} finds the one that came with XEmacs.
|
|
|
7901 @end itemize
|
|
|
7902
|
|
2459
|
7903 @node Q8.0.4, Q8.1.1, Q8.0.3, Other Packages
|
|
|
7904 @unnumberedsubsec Q8.0.4: How do I turn off current chapter from AUCTeX modeline?
|
|
2417
|
7905
|
|
|
7906 With AUCTeX, fast typing is hard because the current chapter, section
|
|
|
7907 etc. are given in the modeline. How can I turn this off?
|
|
|
7908
|
|
|
7909 It's not AUCTeX, it comes from @code{func-menu} in @file{func-menu.el}.
|
|
|
7910
|
|
|
7911 @c Add this code to your @file{init.el} to turn it off:
|
|
|
7912 @c
|
|
|
7913 @c @lisp
|
|
|
7914 @c (setq fume-display-in-modeline-p nil)
|
|
|
7915 @c @end lisp
|
|
|
7916 @c
|
|
|
7917 @c Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
|
|
|
7918 @c mode:
|
|
|
7919 @c
|
|
|
7920 @c @lisp
|
|
|
7921 @c (add-hook 'TeX-mode-hook
|
|
|
7922 @c '(lambda () (setq fume-display-in-modeline-p nil)))
|
|
|
7923 @c @end lisp
|
|
|
7924 @c
|
|
|
7925 @email{dhughes@@origin-at.co.uk, David Hughes} writes:
|
|
|
7926
|
|
|
7927 @quotation
|
|
|
7928 Try this; you'll still get the function name displayed in the modeline,
|
|
|
7929 but it won't attempt to keep track when you modify the file. To refresh
|
|
|
7930 when it gets out of synch, you simply need click on the @samp{Rescan
|
|
|
7931 Buffer} option in the function-menu.
|
|
|
7932
|
|
|
7933 @lisp
|
|
|
7934 (setq-default fume-auto-rescan-buffer-p nil)
|
|
|
7935 @end lisp
|
|
|
7936 @end quotation
|
|
|
7937
|
|
2459
|
7938 @unnumberedsec 8.1: Other Unbundled Packages
|
|
|
7939
|
|
|
7940 @node Q8.1.1, Q8.1.2, Q8.0.4, Other Packages
|
|
|
7941 @unnumberedsubsec Q8.1.1: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
2417
|
7942
|
|
|
7943 The reason for an Emacs package not to be included in XEmacs is
|
|
|
7944 usually one or more of the following:
|
|
|
7945
|
|
|
7946 @enumerate
|
|
|
7947 @item
|
|
|
7948 The package has not been ported to XEmacs. This will typically happen
|
|
|
7949 when it uses GNU-Emacs-specific features, which make it fail under
|
|
|
7950 XEmacs.
|
|
|
7951
|
|
|
7952 Porting a package to XEmacs can range from a trivial amount of change to
|
|
|
7953 a partial or full rewrite. Fortunately, the authors of modern packages
|
|
|
7954 usually choose to support both Emacsen themselves.
|
|
|
7955
|
|
|
7956 @item
|
|
|
7957 The package has been decided not to be appropriate for XEmacs. It may
|
|
|
7958 have an equivalent or better replacement within XEmacs, in which case
|
|
|
7959 the developers may choose not to burden themselves with supporting an
|
|
|
7960 additional package.
|
|
|
7961
|
|
|
7962 Each package bundled with XEmacs means more work for the maintainers,
|
|
|
7963 whether they want it or not. If you are ready to take over the
|
|
|
7964 maintenance responsibilities for the package you port, be sure to say
|
|
|
7965 so---we will more likely include it.
|
|
|
7966
|
|
|
7967 @item
|
|
|
7968 The package simply hasn't been noted by the XEmacs development. If
|
|
|
7969 that's the case, the messages like yours are very useful for attracting
|
|
|
7970 our attention.
|
|
|
7971
|
|
|
7972 @item
|
|
|
7973 The package was noted by the developers, but they simply haven't yet
|
|
|
7974 gotten around to including/porting it. Wait for the next release or,
|
|
|
7975 even better, offer your help. It will be gladly accepted and
|
|
|
7976 appreciated.
|
|
|
7977 @end enumerate
|
|
|
7978
|
|
2459
|
7979 @node Q8.1.2, Q8.1.3, Q8.1.1, Other Packages
|
|
|
7980 @unnumberedsubsec Q8.1.2: Are there any Emacs Lisp Spreadsheets?
|
|
2417
|
7981
|
|
|
7982 Yes. Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at
|
|
428
|
7983 @iftex
|
|
|
7984 @*
|
|
|
7985 @end iftex
|
|
2459
|
7986 @uref{http://acs.ist.psu.edu/dismal/dismal.html}.
|
|
|
7987
|
|
|
7988 @node Q8.1.3, Q8.2.1, Q8.1.2, Other Packages
|
|
|
7989 @unnumberedsubsec Q8.1.3: Is there a MatLab mode?
|
|
2417
|
7990
|
|
|
7991 Yes, a matlab mode and other items are available at the
|
|
2459
|
7992 @uref{http://www.mathworks.com/matlabcentral/files/104/matlab.el}.
|
|
|
7993
|
|
|
7994 @unnumberedsec 8.2: Environments Built Around XEmacs
|
|
|
7995
|
|
|
7996 @node Q8.2.1, Q8.2.2, Q8.1.3, Other Packages
|
|
|
7997 @unnumberedsubsec Q8.2.1: What are SPARCworks, EOS, and WorkShop?
|
|
2417
|
7998
|
|
|
7999 SPARCworks was a development environment from Sun (circa 1993-1996)
|
|
|
8000 and consisted of compilers (C, C++, FORTRAN 77, Fortran 90, Ada, and
|
|
|
8001 Pascal), a debugger, and other tools such as TeamWare (for
|
|
|
8002 configuration management), MakeTool, etc.
|
|
428
|
8003
|
|
|
8004 EOS is the integration of XEmacs with the SPARCworks debugger. It
|
|
|
8005 allows one to use an XEmacs frame to view code (complete with
|
|
|
8006 fontification, etc.), set breakpoints, print variables, etc., while
|
|
2417
|
8007 using the SPARCworks debugger.
|
|
|
8008
|
|
|
8009 EOS stands for "Era on SPARCworks"; Era stood for "Emacs Rewritten
|
|
|
8010 Again" and was the name used by Sun for its modified version of Lucid
|
|
|
8011 Emacs (later XEmacs) in the early-mid 90's. This is documented in
|
|
|
8012 more detail in the history section of the XEmacs About page.
|
|
|
8013
|
|
|
8014 EOS was replaced around 1996 with a newer graphical development
|
|
|
8015 environment called Sun WorkShop. The current status of this is
|
|
|
8016 unknown.
|
|
|
8017
|
|
2459
|
8018 @node Q8.2.2, Q8.2.3, Q8.2.1, Other Packages
|
|
|
8019 @unnumberedsubsec Q8.2.2: How do I start the Sun Workshop support in XEmacs 21?
|
|
428
|
8020
|
|
|
8021 Add the switch ---with-workshop to the configure command when building
|
|
|
8022 XEmacs and put the following in one of your startup files
|
|
|
8023 (e.g. site-start.el or .emacs):
|
|
|
8024
|
|
|
8025 @lisp
|
|
|
8026 (when (featurep 'tooltalk)
|
|
|
8027 (load "tooltalk-macros")
|
|
|
8028 (load "tooltalk-util")
|
|
|
8029 (load "tooltalk-init"))
|
|
|
8030 (when (featurep 'sparcworks)
|
|
|
8031 (load "sunpro-init")
|
|
|
8032 (load "ring")
|
|
|
8033 (load "comint")
|
|
|
8034 (load "annotations")
|
|
|
8035 (sunpro-startup))
|
|
|
8036 @end lisp
|
|
|
8037
|
|
|
8038 If you are not using the latest Workshop (5.0) you have to apply the
|
|
|
8039 following patch:
|
|
|
8040
|
|
|
8041 @format
|
|
|
8042 --- /opt/SUNWspro/lib/eserve.el.ORIG Fri May 14 15:23:26 1999
|
|
|
8043 +++ /opt/SUNWspro/lib/eserve.el Fri May 14 15:24:54 1999
|
|
|
8044 @@@@ -42,7 +42,7 @@@@
|
|
|
8045 (defvar running-xemacs nil "t if we're running XEmacs")
|
|
|
8046 (defvar running-emacs nil "t if we're running GNU Emacs 19")
|
|
438
|
8047
|
|
428
|
8048 -(if (string-match "^\\(19\\|20\\)\..*\\(XEmacs\\|Lucid\\)" emacs-version)
|
|
|
8049 +(if (string-match "\\(XEmacs\\|Lucid\\)" emacs-version)
|
|
|
8050 (setq running-xemacs t)
|
|
|
8051 (setq running-emacs t))
|
|
438
|
8052 @end format
|
|
428
|
8053
|
|
2459
|
8054 @node Q8.2.3, Q8.2.4, Q8.2.2, Other Packages
|
|
|
8055 @unnumberedsubsec Q8.2.3: What is/was Energize?
|
|
2417
|
8056
|
|
|
8057 The "Energize Programming System" was a C and C++ development environment
|
|
|
8058 sold by Lucid, Inc. It was the reason why Lucid Emacs, now XEmacs, was
|
|
|
8059 created in the first place. Unfortunately, Lucid went out of business in
|
|
|
8060 1994. The rights to sell it in Japan were purchased by INS
|
|
|
8061 Engineering (which briefly employed Stig Hackvan aka Jonathan
|
|
|
8062 Stigelman to work on Japanese support for XEmacs, in late 1994 and
|
|
|
8063 early 1995) and Tartan bought the rights to sell it in the rest of the
|
|
|
8064 world. However, INS is not selling Energize at this point and may or
|
|
|
8065 may not have ever done so; Tartan certainly never did.
|
|
|
8066
|
|
2459
|
8067 @node Q8.2.4, , Q8.2.3, Other Packages
|
|
|
8068 @unnumberedsubsec Q8.2.4: What is Infodock?
|
|
428
|
8069
|
|
660
|
8070 @uref{http://sourceforge.net/projects/infodock/, InfoDock} is an
|
|
|
8071 integrated productivity toolset, mainly aimed at technical people,
|
|
|
8072 hosted at SourceForge.
|
|
428
|
8073
|
|
|
8074 InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of
|
|
|
8075 the power of Emacs, but with an easier to use and more comprehensive
|
|
|
8076 menu-based user interface. The bottom portion of this text describes
|
|
|
8077 how it differs from XEmacs and GNU Emacs from the Free Software
|
|
|
8078 Foundation.
|
|
|
8079
|
|
|
8080 InfoDock is aimed at people who want a free, turn-key productivity
|
|
|
8081 environment. Although InfoDock is customizable, it is not intended for
|
|
|
8082 people who like basic versions of Emacs which need to be customized
|
|
|
8083 extensively for local use; standard Emacs distributions are better for
|
|
|
8084 such uses. InfoDock is for those people who want a complete,
|
|
|
8085 pre-customized environment in one package, which they need not touch
|
|
|
8086 more than once or twice a year to update to new revisions.
|
|
|
8087
|
|
|
8088 InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX,
|
|
|
8089 and Intel Linux systems. It is intended for use on a color display,
|
|
|
8090 although most features will work on monochrome monitors. Simply unpack
|
|
|
8091 InfoDock according to the instructions in the ID-INSTALL file and you
|
|
|
8092 are ready to run.
|
|
|
8093
|
|
|
8094 The InfoDock Manual is concise, yet sufficient as a user guide for users
|
|
|
8095 who have never used an Emacs-type editor before. For users who are
|
|
|
8096 already familiar with Emacs, it supplements the information in the GNU
|
|
|
8097 Emacs Manual.
|
|
|
8098
|
|
|
8099 InfoDock menus are much more extensive and more mature than standard
|
|
|
8100 Emacs menus. Each menu offers a @samp{Manual} item which displays
|
|
|
8101 documentation associated with the menu's functions.
|
|
|
8102
|
|
|
8103 @noindent
|
|
|
8104 Four types of menubars are provided:
|
|
|
8105 @enumerate
|
|
|
8106 @item
|
|
|
8107 An extensive menubar providing access to global InfoDock commands.
|
|
|
8108 @item
|
|
|
8109 Mode-specific menubars tailored to the current major mode.
|
|
|
8110 @item
|
|
|
8111 A simple menubar for basic editing to help novices get started with InfoDock.
|
|
|
8112 @item
|
|
|
8113 The standard XEmacs menubar.
|
|
|
8114 @end enumerate
|
|
|
8115
|
|
|
8116 Most modes also include mode-specific popup menus. Additionally, region and
|
|
|
8117 rectangle popup menus are included.
|
|
|
8118
|
|
|
8119 @samp{Hyperbole}, the everyday information manager, is a core part of
|
|
|
8120 InfoDock. This provides context-sensitive mouse keys, a rolodex-type
|
|
|
8121 contact manager, programmable hypertext buttons, and an autonumbered
|
|
|
8122 outliner with embedded hyperlink anchors.
|
|
|
8123
|
|
|
8124 The @samp{OO-Browser}, a multi-language object-oriented code browser, is a
|
|
|
8125 standard part of InfoDock.
|
|
|
8126
|
|
|
8127 InfoDock saves a more extensive set of user options than other Emacs
|
|
|
8128 versions.
|
|
|
8129
|
|
|
8130 InfoDock inserts a useful file header in many file types, showing the
|
|
|
8131 author, summary, and last modification time of each file. A summary
|
|
|
8132 program can then be used to summarize all of the files in a directory,
|
|
|
8133 for easy MANIFEST file creation.
|
|
|
8134
|
|
|
8135 Your working set of buffers is automatically saved and restored (if you
|
|
|
8136 answer yes to a prompt) between InfoDock sessions.
|
|
|
8137
|
|
|
8138 Refined color choices for code highlighting are provided for both dark and
|
|
|
8139 light background display frames.
|
|
|
8140
|
|
|
8141 The @kbd{C-z} key prefix performs frame-based commands which parallel the
|
|
|
8142 @kbd{C-x} key prefix for window-based commands.
|
|
|
8143
|
|
|
8144 The Smart Menu system is included for producing command menus on dumb
|
|
|
8145 terminals.
|
|
|
8146
|
|
|
8147 Lisp libraries are better categorized according to function.
|
|
|
8148
|
|
|
8149 Extensions and improvements to many areas of Emacs are included, such as:
|
|
|
8150 paragraph filling, mail reading with Rmail, shell handling, outlining, code
|
|
|
8151 highlighting and browsing, and man page browsing.
|
|
|
8152
|
|
|
8153 InfoDock questions, answers and discussion should go to the mail list
|
|
|
8154 @iftex
|
|
|
8155 @*
|
|
|
8156 @end iftex
|
|
|
8157 @email{infodock@@infodock.com}. Use
|
|
|
8158 @email{infodock-request@@infodock.com} to be added or removed from the
|
|
|
8159 list. Always include your InfoDock version number when sending help
|
|
|
8160 requests.
|
|
|
8161
|
|
2459
|
8162 @node Current Events, Legacy Versions, Other Packages, Top
|
|
|
8163 @unnumbered 9 What the Future Holds
|
|
|
8164
|
|
|
8165 This is part 9 of the XEmacs Frequently Asked Questions list. This
|
|
611
|
8166 section will change frequently, and (in theory) should contain any
|
|
|
8167 interesting items that have transpired recently. (But in practice it's
|
|
|
8168 not getting updated like this.)
|
|
|
8169
|
|
|
8170 This section also contains descriptions of the new features in all the
|
|
|
8171 recent releases of XEmacs. For the most part, the information below is
|
|
|
8172 a synopsis of the more complete information that can be found in the
|
|
|
8173 file @file{NEWS} in the @file{etc} directory of the XEmacs distribution.
|
|
|
8174 You can view this file in XEmacs using @kbd{C-h n} or the @samp{Help}
|
|
|
8175 menu.
|
|
|
8176
|
|
|
8177 Information on older versions of XEmacs can be find in @file{ONEWS} in
|
|
|
8178 the same directory, or @file{OONEWS} for really old versions.
|
|
|
8179
|
|
428
|
8180 @menu
|
|
2537
|
8181 9.0: Changes
|
|
2459
|
8182 * Q9.0.1:: What new features will be in XEmacs soon?
|
|
|
8183 * Q9.0.2:: What's new in XEmacs 21.4?
|
|
|
8184 * Q9.0.3:: What's new in XEmacs 21.1?
|
|
|
8185 * Q9.0.4:: What's new in XEmacs 20.4?
|
|
|
8186 * Q9.0.5:: What's new in XEmacs 20.3?
|
|
|
8187 * Q9.0.6:: What's new in XEmacs 20.2?
|
|
428
|
8188 @end menu
|
|
|
8189
|
|
2459
|
8190 @unnumberedsec 9.0: Changes
|
|
|
8191
|
|
|
8192 @node Q9.0.1, Q9.0.2, Current Events, Current Events
|
|
|
8193 @unnumberedsubsec Q9.0.1: What new features will be in XEmacs soon?
|
|
611
|
8194
|
|
2417
|
8195 #### Write me.
|
|
428
|
8196
|
|
2459
|
8197 @node Q9.0.2, Q9.0.3, Q9.0.1, Current Events
|
|
|
8198 @unnumberedsubsec Q9.0.2: What's new in XEmacs 21.4?
|
|
611
|
8199
|
|
|
8200 21.4 was the "stable" version of the 21.2 series, which was considered
|
|
|
8201 "experimental" throughout its life; thus there were no "official"
|
|
|
8202 releases at all. In essence, XEmacs is now following the "alternating"
|
|
|
8203 scheme of Linux, where at any point there are at least two different
|
|
|
8204 development branches, one "stable" and one "experimental". Periodic
|
|
|
8205 releases happen in both branches, but those in the experimental branch
|
|
|
8206 are not tested as well, and there's no guarantee they will work at all.
|
|
|
8207 The experiemental branch is open to any and all code that's acceptable
|
|
|
8208 to the developers; the stable branch, however, is in general limited
|
|
|
8209 only to bug fixes, and all contributions are carefully reviewed to make
|
|
|
8210 sure they will increase and not decrease stability.
|
|
|
8211
|
|
|
8212 21.3 never existed at all; it was decided to follow the Linux scheme
|
|
|
8213 exactly, where odd-numbered series are experimental and even-numbered
|
|
|
8214 ones stable.
|
|
|
8215
|
|
|
8216 The following lists summarizes the essential changes made in this
|
|
|
8217 version. For a fuller list, see the @file{NEWS} in the @file{etc}
|
|
|
8218 directory of the XEmacs distribution, or use @kbd{C-h n} or the
|
|
|
8219 @samp{Help} menu to view this file inside of XEmacs.
|
|
|
8220
|
|
676
|
8221 @unnumberedsubsubsec User-visible changes in XEmacs 21.4
|
|
611
|
8222
|
|
|
8223 @itemize @bullet
|
|
|
8224
|
|
|
8225 @item
|
|
|
8226 The delete key now deletes forward by default.
|
|
|
8227 @item
|
|
|
8228 Shifted motion keys now select text by default.
|
|
|
8229 @item
|
|
|
8230 You can now build XEmacs with support for GTK+ widget set.
|
|
|
8231 @item
|
|
|
8232 ~/.xemacs/init.el is now the preferred location for the init
|
|
|
8233 file. (XEmacs now supports a `~/.xemacs/init.el' startup file. Custom
|
|
|
8234 file will move to ~/.xemacs/custom.el.)
|
|
|
8235 @item
|
|
|
8236 Much-improved sample init.el, showing how to use many useful features.
|
|
|
8237 @item
|
|
|
8238 XEmacs support for menu accelerators has been much improved.
|
|
|
8239 @item
|
|
|
8240 Default menubar improvements. (Default menubar has many new commands and
|
|
|
8241 better organization. The font-menu is now available under MS Windows.)
|
|
|
8242 @item
|
|
2417
|
8243 Dialog box improvements, including a real file dialog box. (XEmacs now
|
|
|
8244 has a proper file dialog box under MS Windows (and GTK)! The old
|
|
|
8245 clunky file dialog box is improved. Keyboard traversal now works
|
|
|
8246 correctly in MS Windows dialog boxes. There is a Search dialog box
|
|
|
8247 available from @samp{Edit->Find...})
|
|
611
|
8248 @item
|
|
|
8249 New buffer tabs.
|
|
|
8250 @item
|
|
|
8251 There is a new MS Windows installer, netinstall, ported from Cygwin.
|
|
|
8252 @item
|
|
|
8253 The subprocess quote-handling mechanism under Windows is much improved.
|
|
|
8254 @item
|
|
|
8255 Printing support now available under MS Windows.
|
|
|
8256 @item
|
|
|
8257 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).)
|
|
|
8258 @item
|
|
|
8259 Mail spool locking now works correctly.
|
|
|
8260 @item
|
|
|
8261 International support changes. (The default coding-priority-list is now
|
|
|
8262 safer. International keysyms are now supported under X. MS Windows
|
|
|
8263 1251 code page now supported. Czech, Thai, Cyrillic-KOI8, Vietnamese,
|
|
|
8264 Ethiopic now supported. Proper support for words in Latin 3 and Latin
|
|
|
8265 4.)
|
|
|
8266 @item
|
|
|
8267 Help buffers contain hyperlinks, and other changes.
|
|
|
8268 @item
|
|
|
8269 The modeline's text is now scrollable.
|
|
|
8270 @item
|
|
|
8271 The mouse wheel under MS Windows now functions correctly.
|
|
|
8272 @item
|
|
|
8273 Interactive searching and matching case improvements. (Incremental search will now highlight all visible matches. Interactive searches always respect uppercase characters.)
|
|
|
8274 @item
|
|
|
8275 Rectangle functions rewritten to avoid inserting extra spaces.
|
|
|
8276 @item
|
|
|
8277 New command `kill-entire-line' that always kills the entire line.
|
|
|
8278 @item
|
|
|
8279 Default values correctly stored in minibuffer histories.
|
|
|
8280 @item
|
|
|
8281 You can now create "indirect buffers", like in GNU Emacs.
|
|
|
8282 @item
|
|
|
8283 Pixel-based scrolling has been implemented.
|
|
|
8284 @item
|
|
|
8285 Operation progress can be displayed using graphical widgets.
|
|
|
8286 @item
|
|
|
8287 User names following a tilde can now be completed at file name prompts.
|
|
|
8288 @item
|
|
|
8289 XEmacs can now play sound using Enlightenment Sound Daemon (ESD).
|
|
|
8290 @item
|
|
|
8291 X-Face support is now available under MS Windows.
|
|
|
8292 @item
|
|
|
8293 The PostgreSQL Relational Database Management System is now supported.
|
|
|
8294 @item
|
|
|
8295 Indentation no longer indents comments that begin at column zero.
|
|
|
8296 @item
|
|
|
8297 Face and variable settings can have comments in Customize.
|
|
|
8298 @item
|
|
|
8299 New locations for early package hierarchies.
|
|
|
8300 @item
|
|
|
8301 The `auto-save' library has been greatly improved.
|
|
|
8302 @item
|
|
|
8303 New variable `mswindows-alt-by-itself-activates-menu'.
|
|
|
8304 @item
|
|
|
8305 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.)
|
|
|
8306 @item
|
|
|
8307 Etags changes. See @file{NEWS} for full details.
|
|
|
8308 @end itemize
|
|
|
8309
|
|
676
|
8310 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.4
|
|
611
|
8311
|
|
|
8312 Not yet written.
|
|
|
8313
|
|
661
|
8314 @c APA: Texi2html produces invalid HTML from an empty list of bullets!
|
|
|
8315 @c Please uncomment following list when it does contain bullets.
|
|
|
8316 @c @itemize @bullet
|
|
|
8317 @c @end itemize
|
|
611
|
8318
|
|
2459
|
8319 @node Q9.0.3, Q9.0.4, Q9.0.2, Current Events
|
|
|
8320 @unnumberedsubsec Q9.0.3: What's new in XEmacs 21.1?
|
|
611
|
8321
|
|
|
8322 21.1 was the "stable" version of "experimental" 21.0 series.
|
|
2459
|
8323 @xref{Q9.0.2, What's new in XEmacs 21.4?}.
|
|
611
|
8324
|
|
|
8325 The following lists summarizes the essential changes made in this
|
|
|
8326 version. For a fuller list, see the @file{NEWS} in the @file{etc}
|
|
|
8327 directory of the XEmacs distribution, or use @kbd{C-h n} or the
|
|
|
8328 @samp{Help} menu to view this file inside of XEmacs.
|
|
|
8329
|
|
676
|
8330 @unnumberedsubsubsec User-visible changes in XEmacs 21.1
|
|
611
|
8331
|
|
|
8332 @itemize @bullet
|
|
|
8333
|
|
|
8334 @item
|
|
2459
|
8335 XEmacs is now supported under Microsoft Windows 95/98 and Windows
|
|
2417
|
8336 NT/2000/XP operating systems. To discuss Windows-specific issues,
|
|
|
8337 subscribe to the mailing list at
|
|
|
8338 @email{xemacs-winnt-request@@xemacs.org}.
|
|
611
|
8339
|
|
|
8340 @item
|
|
|
8341 XEmacs has been unbundled into constituent installable packages.
|
|
|
8342
|
|
|
8343 @item
|
|
|
8344 @strong{Other notable changes}: The @samp{Options} menu has been ported to
|
|
|
8345 Custom; XEmacs now is able to choose X visuals and use private
|
|
|
8346 colormaps; You can drag the vertical divider of "horizontally"
|
|
|
8347 (side-by-side) split windows.
|
|
|
8348
|
|
|
8349 @item
|
|
|
8350 @strong{Building changes}: XEmacs can be built with support for 31-bit Lisp
|
|
|
8351 integers and 32-bit pointers (previously, it was 28-bit integers and
|
|
|
8352 pointers); XEmacs can be built with LDAP support; @file{dir} files can be
|
|
|
8353 removed in the Info subsystem, and will be regenerated on-the-fly.
|
|
|
8354
|
|
|
8355 @item
|
|
|
8356 @strong{New packages}: @file{imenu}, @file{popper}, @file{gdb-highlight}
|
|
|
8357
|
|
|
8358 @item
|
|
|
8359 @strong{Package changes}: Many changes to @file{cc-mode}, @file{gnus},
|
|
|
8360 @file{gnuclient}. See @file{NEWS} for full details.
|
|
|
8361
|
|
|
8362 @item
|
|
|
8363 @strong{New commands, variables and functions}:
|
|
|
8364 @code{center-to-window-line} (like @code{recenter} but doesn't force a
|
|
|
8365 redisplay); variable @code{user-full-name} (customize what your full
|
|
|
8366 name looks like in mail); @kbd{M-x customize-changed-options} (customize
|
|
|
8367 options whose default values changes because you upgraded your XEmacs);
|
|
|
8368 @kbd{M-x add-log-convert} (converts an old-style ChangeLog buffer to
|
|
|
8369 new-style); @kbd{M-x zap-up-to-char} (like @code{zap-to-char} but
|
|
|
8370 doesn't delete the char searched for); commands to store, retrieve and
|
|
|
8371 increment numbers in registers, useful for macros.
|
|
|
8372
|
|
|
8373 @item
|
|
|
8374 @strong{Changes to commands, variables, and functions}: @kbd{M-x
|
|
|
8375 query-replace} and friends operate only on the region when it's active;
|
|
|
8376 @code{echo-keystrokes} can now be a floating-point number; @kbd{M-.}
|
|
|
8377 searches exact tag matches before inexact ones; function
|
|
|
8378 @code{user-full-name} with no arguments returns the var
|
|
|
8379 @code{user-full-name}; a prefix arg to @kbd{M-:} and @kbd{C-h c} inserts
|
|
|
8380 the result in the current buffer.
|
|
1138
|
8381
|
|
611
|
8382 @item
|
|
|
8383 @strong{Other changes}: Under X, new application class @samp{XEmacs};
|
|
|
8384 byte-compilation of user-specs now works.
|
|
|
8385
|
|
|
8386 @item
|
|
|
8387 @strong{XEmacs/Mule (internationalization) changes}: Mule support now
|
|
|
8388 works on TTY's; Egg/SJ3 input method now officially supported (Quail and
|
|
|
8389 Egg/Skk already available through LEIM since 20.3); localized Japanese
|
|
|
8390 menubars if XEmacs is built with the right support.
|
|
|
8391
|
|
|
8392 @end itemize
|
|
|
8393
|
|
676
|
8394 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.1
|
|
611
|
8395
|
|
|
8396 @itemize @bullet
|
|
|
8397
|
|
|
8398 @item
|
|
|
8399 @strong{Specifier changes}: The window locale now has a higher
|
|
|
8400 precedence than the buffer locale when instantiating; new macro
|
|
|
8401 @code{let-specifier}; new specifiers
|
|
|
8402 @code{vertical-scrollbar-visible-p}, horizontal-scrollbar-visible-p',
|
|
|
8403 @code{scrollbar-on-left-p}, @code{scrollbar-on-top-p},
|
|
|
8404 @code{vertical-divider-always-visible-p},
|
|
|
8405 @code{vertical-divider-shadow-thickness},
|
|
|
8406 @code{vertical-divider-line-width}, @code{vertical-divider-spacing};
|
|
|
8407 specifiers and symbols whose value is a specifier allowed as modeline
|
|
|
8408 specifications.
|
|
|
8409
|
|
|
8410 @item
|
|
|
8411 @strong{Frame focus changes}: @code{focus-follows-mouse} works like FSF,
|
|
|
8412 prevents any attempt to permanently change the selected frame; new
|
|
|
8413 function @code{focus-frame} sets the window system focus a frame; new
|
|
|
8414 special forms @code{save-selected-frame} and @code{with-selected-frame}.
|
|
|
8415
|
|
|
8416 @item
|
|
|
8417 @strong{Window function changes}: @code{select-window} now has optional
|
|
|
8418 argument @var{NORECORD} to inhibit recording a buffer change;
|
|
|
8419 @code{vertical-motion} now correctly handles optional @var{WINDOW}
|
|
|
8420 argument and has new optional argument @var{PIXELS}, to have the
|
|
|
8421 returned values be in pixels; new function
|
|
|
8422 @code{vertical-motion-pixels}; new functions
|
|
|
8423 @code{window-text-area-pixel-@{width,height,edges@}}; new functions
|
|
|
8424 @code{shrink-window-pixels} and @code{enlarge-window-pixels}; new
|
|
|
8425 function @code{window-displayed-text-pixel-height}.
|
|
|
8426
|
|
|
8427 @item
|
|
|
8428 @strong{Other function changes}: Arithmetic comparison functions
|
|
|
8429 @code{<}, @code{>}, @code{=}, @code{/=} now accept a variable number of
|
|
|
8430 arguments; hashtables now have a consistent read/print syntax; keyword
|
|
|
8431 symbols cannot be set to a value other than themselves; @code{concat} no
|
|
|
8432 longer accepts integer arguments; new function @code{string}, like
|
|
|
8433 @code{list}, @code{vector}, etc.; new function @code{temp-directory}
|
|
|
8434 (OS-independent way to get a temp directory); @code{load-average} has
|
|
|
8435 optional argument @var{USE-FLOATS}; @code{make-event} implemented
|
|
|
8436 completely; new function @code{function-interactive} (returns a
|
|
|
8437 function's interactive spec); new functions @code{lmessage},
|
|
|
8438 @code{lwarn} (printf-like versions of @code{display-wessage},
|
|
|
8439 @code{display-warning}); new keyword @code{:version} to
|
|
|
8440 @code{defcustom}.
|
|
|
8441
|
|
|
8442 @item
|
|
|
8443 @strong{Performance}: when the new GNU Malloc aka Doug Lea Malloc is
|
|
|
8444 available, it will be used (better performance on libc6 Linux systems);
|
|
|
8445 tracking line-numbers in modeline is now efficient; profiling records a
|
|
|
8446 call-count of all called functions, retrievable through
|
|
|
8447 @code{profile-call-count-results}.
|
|
|
8448
|
|
|
8449 @item
|
|
|
8450 @strong{Startup and path searching}: code to assemble paths at startup
|
|
|
8451 rewritten for new package system; new function @code{split-path} (splits
|
|
|
8452 by @code{path-separator}); @code{Info-default-directory-list} obsolete,
|
|
|
8453 use @code{Info-directory-list} instead; site-lisp is deprecated and no
|
|
|
8454 longer on the load-path by default.
|
|
|
8455
|
|
|
8456 @end itemize
|
|
|
8457
|
|
2459
|
8458 @node Q9.0.4, Q9.0.5, Q9.0.3, Current Events
|
|
|
8459 @unnumberedsubsec Q9.0.4: What's new in XEmacs 20.4?
|
|
611
|
8460
|
|
|
8461 XEmacs 20.4 is a bugfix release with no user-visible changes.
|
|
|
8462 @c Filled in from NEWS file of 20.5-b33
|
|
|
8463
|
|
2459
|
8464 @node Q9.0.5, Q9.0.6, Q9.0.4, Current Events
|
|
|
8465 @unnumberedsubsec Q9.0.5: What's new in XEmacs 20.3?
|
|
428
|
8466
|
|
|
8467 XEmacs 20.3 was released in November 1997. It contains many bugfixes,
|
|
|
8468 and a number of new features, including Autoconf 2 based configuration,
|
|
|
8469 additional support for Mule (Multi-language extensions to Emacs), many
|
|
|
8470 more customizations, multiple frames on TTY-s, support for multiple info
|
|
|
8471 directories, an enhanced gnuclient, improvements to regexp matching,
|
|
|
8472 increased MIME support, and many, many synches with GNU Emacs 20.
|
|
|
8473
|
|
|
8474 The XEmacs/Mule support has been only seriously tested in a Japanese
|
|
|
8475 locale, and no doubt many problems still remain. The support for
|
|
|
8476 ISO-Latin-1 and Japanese is fairly strong. MULE support comes at a
|
|
440
|
8477 price---about a 30% slowdown from 19.16. We're making progress on
|
|
428
|
8478 improving performance and XEmacs 20.3 compiled without Mule (which is
|
|
|
8479 the default) is definitely faster than XEmacs 19.16.
|
|
|
8480
|
|
|
8481 XEmacs 20.3 is the first non-beta v20 release, and will be the
|
|
|
8482 basis for all further development.
|
|
|
8483
|
|
2459
|
8484 @node Q9.0.6, , Q9.0.5, Current Events
|
|
|
8485 @unnumberedsubsec Q9.0.6: What's new in XEmacs 20.2?
|
|
611
|
8486
|
|
|
8487 The biggest changes in 20.2 include integration of EFS (the next
|
|
|
8488 generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a
|
|
|
8489 major mode for editing Tex and LaTeX, and a lot of other stuff). Many
|
|
|
8490 bugs from 20.0 have been fixed for this release. 20.2 also contains a
|
|
|
8491 new system for customizing XEmacs options, invoked via @kbd{M-x
|
|
|
8492 customize}.
|
|
|
8493
|
|
|
8494 XEmacs 20.2 is the development release (20.0 was beta), and is no longer
|
|
|
8495 considered unstable.
|
|
|
8496
|
|
|
8497 For older news, see the file @file{ONEWS} in the @file{etc} directory of
|
|
|
8498 the XEmacs distribution.
|
|
428
|
8499
|
|
2417
|
8500 @node Legacy Versions, , Current Events, Top
|
|
2459
|
8501 @unnumbered 10 New information about old XEmacsen
|
|
|
8502
|
|
|
8503 This is part 10 of the XEmacs Frequently Asked Questions list. It will
|
|
1495
|
8504 occasionally be updated to reflect new information about versions which
|
|
|
8505 are no longer being revised by the XEmacs Project. The primary purpose
|
|
|
8506 is advice on compatibility of older XEmacsen with new packages and
|
|
|
8507 updated versions of packages, but bug fixes (which will not be applied
|
|
|
8508 to released XEmacsen, but users can apply themselves) are also accepted.
|
|
|
8509
|
|
|
8510 @menu
|
|
2537
|
8511 10.0: XEmacs 21.1
|
|
2459
|
8512 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
2559
|
8513 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1.
|
|
1495
|
8514 @end menu
|
|
|
8515
|
|
2459
|
8516 @unnumberedsec 10.0: XEmacs 21.1
|
|
|
8517
|
|
2559
|
8518 @node Q10.0.1, Q10.0.2, Legacy Versions, Legacy Versions
|
|
2459
|
8519 @unnumberedsubsec Q10.0.1: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
1495
|
8520
|
|
|
8521 @email{eeide@@cs.utah.edu, Eric Eide} wrote:
|
|
|
8522
|
|
|
8523 @quotation
|
|
|
8524 Previously I wrote:
|
|
|
8525
|
|
|
8526 Eric> Summary: with Gnus 5.10.1 in XEmacs 21.1.14, I don't see
|
|
|
8527 Eric> any smileys :-(.
|
|
|
8528
|
|
|
8529 After a bit of sleuthing, I discovered the essence of the problem.
|
|
|
8530 For me, the form:
|
|
|
8531
|
|
|
8532 @lisp
|
|
|
8533 (with-temp-buffer
|
|
|
8534 (insert-file-contents "foo.xpm")
|
|
|
8535 (buffer-string))
|
|
|
8536 @end lisp
|
|
|
8537
|
|
|
8538 returns the empty string. This is because something somewhere
|
|
|
8539 replaces the XPM data with a glyph --- I haven't figured out where
|
|
|
8540 this occurs.
|
|
|
8541 @end quotation
|
|
|
8542
|
|
|
8543 @email{kyle_jones@@wonderworks.com, Kyle Jones} replies:
|
|
|
8544
|
|
|
8545 @quotation
|
|
|
8546 Do this:
|
|
|
8547
|
|
|
8548 @lisp
|
|
|
8549 (setq format-alist nil)
|
|
|
8550 @end lisp
|
|
|
8551
|
|
|
8552 The image-mode stuff is gone from format-alist in the 21.4
|
|
|
8553 branch, praise be.
|
|
|
8554 @end quotation
|
|
|
8555
|
|
2559
|
8556 @node Q10.0.2, , Q10.0.1, Legacy Versions
|
|
|
8557 @unnumberedsubsec Q10.0.2: XEmacs won't start on Windows in XEmacs 21.1.
|
|
|
8558
|
|
|
8559 XEmacs relies on a process called "dumping" to generate a working
|
|
|
8560 executable. Under MS-Windows this process effectively fixes the memory
|
|
|
8561 addresses of information in the executable. When XEmacs starts up it tries
|
|
|
8562 to reserve these memory addresses so that the dumping process can be
|
|
|
8563 reversed -- putting the information back at the correct addresses.
|
|
|
8564 Unfortunately some .DLLs (for instance the soundblaster driver) occupy
|
|
|
8565 memory addresses that can conflict with those needed by the dumped XEmacs
|
|
|
8566 executable. In this instance XEmacs will fail to start without any
|
|
|
8567 explanation. Note that this is extremely machine specific.
|
|
|
8568
|
|
|
8569 21.1.10 includes a fix for this that makes more intelligent guesses
|
|
|
8570 about which memory addresses will be free, and this should cure the
|
|
|
8571 problem for most people. 21.4 implements "portable dumping", which
|
|
|
8572 eliminates the problem altogether. We recommend you use the 21.4
|
|
|
8573 binaries, but you can use the 21.1 binaries if you are very paranoid
|
|
|
8574 about stability. @xref{Q1.1.2, Are binaries available?}.
|
|
|
8575
|
|
428
|
8576 @bye
|
