|
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
|
|
2995
|
10 @subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2005/10/14 02:11:49 $
|
|
428
|
11 @sp 1
|
|
2417
|
12 @author Ben Wing <ben@@xemacs.org>
|
|
1869
|
13 @author Tony Rossini <rossini@@u.washington.edu>
|
|
428
|
14 @author Chuck Thompson <cthomp@@xemacs.org>
|
|
|
15 @author Steve Baur <steve@@xemacs.org>
|
|
|
16 @author Andreas Kaempf <andreas@@sccon.com>
|
|
|
17 @author Christian Nyb@o{} <chr@@mediascience.no>
|
|
434
|
18 @author Sandra Wambold <wambold@@xemacs.org>
|
|
428
|
19 @page
|
|
|
20 @end titlepage
|
|
|
21
|
|
|
22 @ifinfo
|
|
|
23 @dircategory XEmacs Editor
|
|
|
24 @direntry
|
|
440
|
25 * FAQ: (xemacs-faq). XEmacs FAQ.
|
|
428
|
26 @end direntry
|
|
|
27 @end ifinfo
|
|
|
28
|
|
2417
|
29 @ignore
|
|
|
30 *****************************************
|
|
|
31 ***** To update the menus and nodes *****
|
|
|
32 *****************************************
|
|
|
33
|
|
|
34 First, the first argument to @node (the name itself) needs to be correct.
|
|
|
35 Use a macro if necessary to update the @node names from the
|
|
|
36 @unnumberedsubsec commands. Also note that the command we're about to
|
|
|
37 run will not correctly fix up the part of the menu to the right of a ::.
|
|
|
38 It will leave existing text in place but not change anything. If you
|
|
|
39 make a lot of changes and want to update this semi-automatically, use
|
|
|
40 M-x occur to pick out all @unnumberedsubsec lines then do some editing
|
|
|
41 magic to coerce them into the right format and cut and paste as necessary:
|
|
|
42
|
|
|
43 1. M-x occur @unnumberedsubsec
|
|
|
44 2. <select a rectangle including all text before the Q#.#.#>
|
|
|
45 3. C-x r t *<space>
|
|
|
46 4. go to the top and use the following macro to get the indentation right.
|
|
|
47
|
|
|
48 (setq last-kbd-macro (read-kbd-macro
|
|
|
49 "C-s : RET : <right> M-x indent- to- column RET 14 RET <home> <down>"))
|
|
|
50
|
|
|
51 5. Cut and paste the menus into the detailmenu at the top and
|
|
|
52 individual menus at the top of the appropriate chapters. (#### I
|
|
|
53 wonder, does texinfo-master-menu generate the detailmenu from the
|
|
|
54 individual menus or vice-versa or neither?)
|
|
|
55
|
|
|
56 Then,
|
|
|
57
|
|
2559
|
58 6. C-u C-c C-u m (C-u M-x texinfo-master-menu) will update the menus
|
|
2417
|
59 and nodes. However, it appears that even though it tries to
|
|
|
60 preserve the existing menu structure as much as possible, it
|
|
|
61 doesn't do a perfect job. It messes up in at least two ways: The
|
|
|
62 indentation in the part of the main menu above the detailmenu will
|
|
|
63 be screwed up, and the #.0 titles will be removed from both the
|
|
|
64 detailmenu and the individual chapter menus. In addition,
|
|
|
65 sometimes random things get screwed up in individual parts of the
|
|
|
66 menus. Therefore:
|
|
|
67
|
|
2559
|
68 1. Use the Lisp line below to get the spacing correct for the Q#.#.#
|
|
|
69 menu entries.
|
|
|
70
|
|
|
71 (set (make-local-variable 'texinfo-column-for-description) 14)
|
|
|
72
|
|
|
73 2. Copy the whole detailmenu beforehand.
|
|
|
74 3. Run C-u C-c C-u m to fix up the nodes.
|
|
|
75 4. Run `fix-main-menu' and `fix-omitted-menu-lines'.
|
|
|
76 5. Check the new detailmenu carefully to see if anything is screwed up
|
|
2417
|
77 compared to the old detailmenu you copied.
|
|
2559
|
78 6. If so, paste back the appropriate sections and fix up the corresponding
|
|
2417
|
79 part of the chapter-specific menu.
|
|
|
80
|
|
|
81 (defun fix-main-menu ()
|
|
|
82 (interactive)
|
|
|
83 (save-restriction
|
|
|
84 (let (p q)
|
|
2559
|
85 (goto-char (point-min))
|
|
|
86 (re-search-forward "^@menu")
|
|
2417
|
87 (setq p (match-beginning 0))
|
|
|
88 (re-search-forward "^$")
|
|
|
89 (setq q (match-end 0))
|
|
|
90 (narrow-to-region p q)
|
|
|
91 (goto-char p)
|
|
|
92 (while (search-forward ":: " nil t)
|
|
|
93 (indent-to-column 26)))))
|
|
|
94
|
|
|
95 (defun fix-omitted-menu-lines ()
|
|
|
96 (interactive)
|
|
|
97 (save-excursion
|
|
2559
|
98 (loop for x from 1 to 10 do
|
|
2417
|
99 (goto-char (point-min))
|
|
|
100 (re-search-forward (format "@unnumberedsec \\(%d.0: .*\\)" x))
|
|
|
101 (let ((line (match-string 1)))
|
|
2559
|
102 (re-search-backward "^@menu")
|
|
2417
|
103 (forward-line 1)
|
|
2559
|
104 (unless (looking-at "[0-9]+.0:")
|
|
2417
|
105 (insert line)
|
|
|
106 (insert "\n"))
|
|
|
107 (goto-char (point-min))
|
|
2559
|
108 (re-search-forward "^@menu")
|
|
2417
|
109 (search-forward (format "Q%d.0.1:" x))
|
|
|
110 (forward-line -1)
|
|
2559
|
111 (unless (looking-at "[0-9]+.0:")
|
|
|
112 (insert "\n")
|
|
|
113 (insert line))))))
|
|
2417
|
114
|
|
|
115 *****************************************
|
|
|
116 ***** Other work *****
|
|
|
117 *****************************************
|
|
|
118
|
|
|
119 When you've rearranged and renumbered a bunch of nodes, you can get
|
|
|
120 the numbers agreeing again. The macro below assumes that the
|
|
|
121 unnumberedsubsec number is correct, and fixes up the node to agree.
|
|
|
122 Only the first part of the node is fixed and the other parts may still
|
|
|
123 be wrong; but they will be fixed as part of
|
|
|
124 @code{texinfo-master-menu}.
|
|
|
125
|
|
|
126 (setq last-kbd-macro (read-kbd-macro
|
|
|
127 "<f1> unnumberedsubsec SPC RET C-s : RET <left> C-x C-x <f3> <home> <up> <C-right> <right> C-s , RET <left> C-x C-x <f4> <home> 2*<down>"))
|
|
|
128 @end ignore
|
|
|
129
|
|
|
130
|
|
428
|
131 @node Top, Introduction, (dir), (dir)
|
|
|
132 @top XEmacs FAQ
|
|
|
133
|
|
|
134 This is the guide to the XEmacs Frequently Asked Questions list---a
|
|
|
135 compendium of questions and answers pertaining to one of the finest
|
|
442
|
136 programs ever written. XEmacs is much more than just a Text Editor.
|
|
|
137
|
|
|
138 This FAQ is freely redistributable. This FAQ is distributed in the hope
|
|
|
139 that it will be useful, but WITHOUT ANY WARRANTY; without even the
|
|
|
140 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
|
428
|
141
|
|
|
142 If you have a Web browser, the official hypertext version is at
|
|
|
143 @iftex
|
|
|
144 @*
|
|
|
145 @end iftex
|
|
1143
|
146 @uref{http://www.xemacs.org/FAQ/xemacs-faq.html}
|
|
428
|
147
|
|
|
148 @ifset CANONICAL
|
|
|
149 @html
|
|
|
150 This document is available in several different formats:
|
|
|
151 @itemize @bullet
|
|
|
152 @item
|
|
|
153 @uref{xemacs-faq.txt, As a single ASCII file}, produced by
|
|
|
154 @code{makeinfo --no-headers}
|
|
|
155 @item
|
|
|
156 @uref{xemacs-faq.dvi, As a .dvi file}, as used with
|
|
|
157 @uref{http://www.tug.org, TeX.}
|
|
|
158 @item
|
|
|
159 As a PostScript file @uref{xemacs-faq-a4.ps, in A4 format},
|
|
|
160 as well as in @uref{xemacs-faq-letter.ps, letter format}
|
|
|
161 @item
|
|
|
162 In html format, @uref{xemacs-faq_1.html, split by chapter}, or in
|
|
|
163 @uref{xemacs-faq.html, one monolithic} document.
|
|
|
164 @item
|
|
|
165 The canonical version of the FAQ is the texinfo document
|
|
|
166 @uref{xemacs-faq.texi, man/xemacs-faq.texi}.
|
|
|
167 @item
|
|
|
168 If you do not have makeinfo installed, you may @uref{xemacs-faq.info,
|
|
|
169 download the faq} in info format, and install it in @file{<XEmacs
|
|
|
170 library directory>/info/}. For example in
|
|
462
|
171 @file{/usr/local/lib/xemacs-21.4/info/}.
|
|
428
|
172
|
|
|
173 @end itemize
|
|
|
174
|
|
|
175 @end html
|
|
|
176
|
|
|
177 @end ifset
|
|
|
178
|
|
|
179 @c end ifset points to CANONICAL
|
|
|
180
|
|
|
181 @menu
|
|
2417
|
182 * Introduction:: Introduction, Policy, Credits.
|
|
|
183 * Installation:: Installation and Troubleshooting.
|
|
2459
|
184 * Editing:: Editing Functions.
|
|
|
185 * Display:: Display Functions.
|
|
2417
|
186 * External Subsystems:: Interfacing with the OS and External Devices.
|
|
|
187 * Internet:: Connecting to the Internet.
|
|
|
188 * Advanced:: Advanced Customization Using XEmacs Lisp.
|
|
2459
|
189 * Other Packages:: Other External Packages.
|
|
2417
|
190 * Current Events:: What the Future Holds.
|
|
|
191 * Legacy Versions:: New information about old XEmacsen.
|
|
428
|
192
|
|
|
193 @detailmenu
|
|
|
194 --- The Detailed Node Listing ---
|
|
|
195
|
|
2417
|
196 1 Introduction, Policy, Credits
|
|
|
197
|
|
2537
|
198 1.0: What is XEmacs?
|
|
2417
|
199 * Q1.0.1:: What is XEmacs?
|
|
|
200 * Q1.0.2:: What is the current version of XEmacs?
|
|
2537
|
201 * Q1.0.3:: How do you pronounce XEmacs?
|
|
|
202 * Q1.0.4:: What does XEmacs look like?
|
|
|
203 * Q1.0.5:: Who wrote XEmacs?
|
|
|
204 * Q1.0.6:: Who wrote the FAQ?
|
|
|
205
|
|
|
206 1.1: Getting XEmacs
|
|
|
207 * Q1.1.1:: Where can I find XEmacs?
|
|
|
208 * Q1.1.2:: Are binaries available?
|
|
|
209 * Q1.1.3:: How do I get the bleeding-edge sources?
|
|
|
210 * Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual?
|
|
|
211
|
|
|
212 1.2: Versions for Different Operating Systems
|
|
|
213 * Q1.2.1:: Do I need X11 to run XEmacs?
|
|
|
214 * Q1.2.2:: What versions of Unix does XEmacs run on?
|
|
|
215 * Q1.2.3:: Is there a port of XEmacs to Microsoft Windows?
|
|
|
216 * Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
217 * Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
218 * Q1.2.6:: What are the differences between the various MS Windows emacsen?
|
|
|
219 * Q1.2.7:: How does the port cope with differences in the Windows user interface?
|
|
|
220 * Q1.2.8:: Is there a port of XEmacs to the Macintosh?
|
|
|
221 * Q1.2.9:: Is there a port of XEmacs to MS-DOS?
|
|
|
222 * Q1.2.10:: Is there a port of XEmacs to OS/2?
|
|
|
223 * Q1.2.11:: Is there a port of XEmacs to NextStep?
|
|
|
224 * Q1.2.12:: Is there a port of XEmacs to VMS?
|
|
|
225
|
|
|
226 1.3: Getting Started
|
|
|
227 * Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
|
228 * Q1.3.2:: Where do I put my @file{init.el} file?
|
|
|
229 * Q1.3.3:: Can I use the same @file{init.el} with the other Emacs?
|
|
|
230 * Q1.3.4:: Any good XEmacs tutorials around?
|
|
|
231 * Q1.3.5:: May I see an example of a useful XEmacs Lisp function?
|
|
|
232 * Q1.3.6:: And how do I bind it to a key?
|
|
|
233 * Q1.3.7:: What's the difference between a macro and a function?
|
|
|
234 * Q1.3.8:: What is @code{Custom}?
|
|
|
235
|
|
|
236 1.4: Getting Help
|
|
|
237 * Q1.4.1:: Where can I get help?
|
|
|
238 * Q1.4.2:: Which mailing lists are there?
|
|
2559
|
239 * Q1.4.3:: Where are the mailing lists archived?
|
|
|
240 * Q1.4.4:: How can I get two instances of info?
|
|
|
241 * Q1.4.5:: How do I add new Info directories?
|
|
2537
|
242
|
|
|
243 1.5: Contributing to XEmacs
|
|
|
244 * Q1.5.1:: How do I submit changes to the FAQ?
|
|
|
245 * Q1.5.2:: How do I become a beta tester?
|
|
|
246 * Q1.5.3:: How do I contribute to XEmacs itself?
|
|
2559
|
247 * Q1.5.4:: How do I get started developing XEmacs?
|
|
|
248 * Q1.5.5:: What's the basic layout of the code?
|
|
2537
|
249
|
|
|
250 1.6: Politics (XEmacs vs. GNU Emacs)
|
|
|
251 * Q1.6.1:: What is GNU Emacs?
|
|
|
252 * Q1.6.2:: How does XEmacs differ from GNU Emacs?
|
|
|
253 * Q1.6.3:: How much does XEmacs differ?
|
|
|
254 * Q1.6.4:: Is XEmacs "GNU"?
|
|
|
255 * Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
|
256 * Q1.6.6:: Why haven't XEmacs and GNU Emacs merged?
|
|
|
257
|
|
|
258 1.7: External Packages
|
|
2559
|
259 * Q1.7.1:: What is the package system?
|
|
|
260 * Q1.7.2:: Which external packages are there?
|
|
|
261 * Q1.7.3:: Do I need to have the packages to run XEmacs?
|
|
|
262 * Q1.7.4:: Is there a way to find which package has particular functionality?
|
|
2537
|
263
|
|
|
264 1.8: Internationalization
|
|
|
265 * Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
|
266 * Q1.8.2:: How can I help with internationalization?
|
|
|
267 * Q1.8.3:: How do I type non-ASCII characters?
|
|
|
268 * Q1.8.4:: Can XEmacs messages come out in a different language?
|
|
|
269 * Q1.8.5:: Please explain the various input methods in MULE/XEmacs
|
|
|
270 * Q1.8.6:: How do I portably code for MULE/XEmacs?
|
|
|
271 * Q1.8.7:: How about Cyrillic modes?
|
|
|
272 * Q1.8.8:: Does XEmacs support Unicode?
|
|
|
273 * Q1.8.9:: How does XEmacs display Unicode?
|
|
2417
|
274
|
|
|
275 2 Installation and Troubleshooting
|
|
|
276
|
|
2559
|
277 2.0: Installation (General)
|
|
|
278 * Q2.0.1:: How do I build and install XEmacs?
|
|
|
279 * Q2.0.2:: Where do I find external libraries?
|
|
|
280 * Q2.0.3:: How do I specify the paths that XEmacs uses for finding files?
|
|
|
281 * Q2.0.4:: Running XEmacs without installing
|
|
|
282 * Q2.0.5:: XEmacs is too big
|
|
|
283
|
|
|
284 2.1: Package Installation
|
|
|
285 * Q2.1.1:: How do I install the packages?
|
|
|
286 * Q2.1.2:: Can I install the packages individually?
|
|
|
287 * Q2.1.3:: Can I install the packages automatically?
|
|
|
288 * Q2.1.4:: Can I upgrade or remove packages?
|
|
|
289 * Q2.1.5:: Which packages to install?
|
|
|
290 * Q2.1.6:: Can you describe the package location process in more detail?
|
|
|
291 * Q2.1.7:: EFS fails with "500 AUTH not understood"
|
|
|
292
|
|
|
293 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
|
294 * Q2.2.1:: Libraries in non-standard locations
|
|
|
295 * Q2.2.2:: Why can't I strip XEmacs?
|
|
|
296
|
|
|
297 2.3: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
298 * Q2.3.1:: What exactly are all the different ways to build XEmacs under Windows?
|
|
|
299 * Q2.3.2:: What compiler/libraries do I need to compile XEmacs?
|
|
|
300 * Q2.3.3:: How do I compile the native port?
|
|
|
301 * Q2.3.4:: What do I need for Cygwin?
|
|
|
302 * Q2.3.5:: How do I compile under Cygwin?
|
|
|
303 * Q2.3.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
|
304 * Q2.3.7:: How do I compile with X support?
|
|
|
305 * Q2.3.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
|
306
|
|
|
307 2.4: General Troubleshooting
|
|
|
308 * Q2.4.1:: How do I deal with bugs or with problems building, installing, or running?
|
|
|
309 * Q2.4.2:: Help! XEmacs just crashed on me!
|
|
|
310 * Q2.4.3:: XEmacs crashes and I compiled it myself.
|
|
|
311 * Q2.4.4:: How to debug an XEmacs problem with a debugger
|
|
|
312 * Q2.4.5:: I get a cryptic error message when trying to do something.
|
|
|
313 * Q2.4.6:: XEmacs hangs when I try to do something.
|
|
|
314 * Q2.4.7:: I get an error message when XEmacs is running in batch mode.
|
|
|
315 * Q2.4.8:: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
|
316 * Q2.4.9:: @kbd{C-g} doesn't work for me. Is it broken?
|
|
|
317 * Q2.4.10:: How do I debug process-related problems?
|
|
|
318 * Q2.4.11:: XEmacs is outputting lots of X errors.
|
|
|
319 * Q2.4.12:: After upgrading, XEmacs won't do `foo' any more!
|
|
|
320
|
|
|
321 2.5: Startup-Related Problems
|
|
|
322 * Q2.5.1:: XEmacs cannot connect to my X Terminal!
|
|
|
323 * Q2.5.2:: Startup problems related to paths or package locations.
|
|
|
324 * Q2.5.3:: XEmacs won't start without network.
|
|
|
325 * Q2.5.4:: Startup warnings about deducing proper fonts?
|
|
|
326 * Q2.5.5:: Warnings from incorrect key modifiers.
|
|
|
327 * Q2.5.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
2417
|
328
|
|
2459
|
329 3 Editing Functions
|
|
2417
|
330
|
|
|
331 3.0: The Keyboard
|
|
2459
|
332 * Q3.0.1:: How can I customize the keyboard?
|
|
|
333 * Q3.0.2:: How can I bind complex functions (or macros) to keys?
|
|
|
334 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down?
|
|
|
335 * Q3.0.4:: Globally binding @kbd{Delete}?
|
|
|
336 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
|
337 * Q3.0.6:: How can you type in special characters in XEmacs?
|
|
|
338 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys?
|
|
|
339 * Q3.0.8:: How do I map the arrow keys?
|
|
|
340 * Q3.0.9:: HP Alt key as Meta.
|
|
|
341 * Q3.0.10:: Why does edt emulation not work?
|
|
|
342 * Q3.0.11:: How can I emulate VI and use it as my default mode?
|
|
2417
|
343
|
|
|
344 3.1: The Mouse
|
|
|
345 * Q3.1.1:: How can I turn off Mouse pasting?
|
|
|
346 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons?
|
|
|
347 * Q3.1.3:: Clicking the left button does not do anything in buffer list.
|
|
|
348 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3?
|
|
2459
|
349 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
|
350
|
|
|
351 3.2: Buffers, Text Editing
|
|
|
352 * Q3.2.1:: Can I have the end of the buffer delimited in some way?
|
|
|
353 * Q3.2.2:: How do I insert today's date into a buffer?
|
|
|
354 * Q3.2.3:: How do I get a single minibuffer frame?
|
|
|
355 * Q3.2.4:: How can I enable auto-indent and/or Filladapt?
|
|
|
356 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
357
|
|
|
358 3.3: Text Selections
|
|
|
359 * Q3.3.1:: How do I select a rectangular region?
|
|
|
360 * Q3.3.2:: How can I turn off or change highlighted selections?
|
|
|
361 * Q3.3.3:: How do I cause typing on an active region to remove it?
|
|
|
362 * Q3.3.4:: Can I turn off the highlight during isearch?
|
|
|
363 * Q3.3.5:: Why is killing so slow?
|
|
|
364 * Q3.3.6:: Why does @kbd{M-w} take so long?
|
|
|
365
|
|
|
366 3.4: Editing Source Code
|
|
|
367 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode?
|
|
|
368 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly?
|
|
|
369
|
|
|
370 4 Display Functions
|
|
|
371
|
|
|
372 4.0: Textual Fonts and Colors
|
|
|
373 * Q4.0.1:: How do I specify a font?
|
|
|
374 * Q4.0.2:: How do I set the text, menu and modeline fonts?
|
|
|
375 * Q4.0.3:: How can I set color options from @file{init.el}?
|
|
|
376 * Q4.0.4:: How can I set the colors when highlighting a region?
|
|
|
377 * Q4.0.5:: How can I limit color map usage?
|
|
|
378 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them.
|
|
|
379 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs?
|
|
|
380 * Q4.0.8:: How do I display non-ASCII characters?
|
|
|
381 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}.
|
|
|
382
|
|
|
383 4.1: Syntax Highlighting (Font Lock)
|
|
|
384 * Q4.1.1:: How can I do source code highlighting using font-lock?
|
|
|
385 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
386
|
|
|
387 4.2: The Modeline
|
|
|
388 * Q4.2.1:: How can I make the modeline go away?
|
|
|
389 * Q4.2.2:: How do you have XEmacs display the line number in the modeline?
|
|
|
390 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline?
|
|
|
391 * Q4.2.4:: How can I change the modeline color based on the mode used?
|
|
|
392
|
|
|
393 4.3: The Cursor
|
|
|
394 * Q4.3.1:: Is there a way to make the bar cursor thicker?
|
|
|
395 * Q4.3.2:: Is there a way to get back the block cursor?
|
|
|
396 * Q4.3.3:: Can I make the cursor blink?
|
|
|
397
|
|
|
398 4.4: The Menubar
|
|
|
399 * Q4.4.1:: How do I get rid of the menubar?
|
|
|
400 * Q4.4.2:: How can I customize the menubar?
|
|
|
401 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
402 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
403 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
404
|
|
|
405 4.5: The Toolbar
|
|
|
406 * Q4.5.1:: How do I get rid of the toolbar?
|
|
|
407 * Q4.5.2:: How can I customize the toolbar?
|
|
|
408 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar?
|
|
|
409 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar
|
|
|
410
|
|
|
411 4.6: Scrollbars and Scrolling
|
|
|
412 * Q4.6.1:: How can I disable the scrollbar?
|
|
|
413 * Q4.6.2:: How can I change the scrollbar width?
|
|
|
414 * Q4.6.3:: How can I use resources to change scrollbar colors?
|
|
|
415 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this?
|
|
|
416 * Q4.6.5:: Scrolling one line at a time.
|
|
|
417 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
418 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
419
|
|
|
420 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
421 * Q4.7.1:: How can I disable the gutter tabs?
|
|
|
422 * Q4.7.2:: How can I disable the progress bar?
|
|
|
423 * Q4.7.3:: There are bugs in the gutter or widgets.
|
|
|
424 * Q4.7.4:: How can I customize the gutter or gutter tabs?
|
|
|
425
|
|
|
426 5 Interfacing with the Operating System and External Devices
|
|
|
427
|
|
|
428 5.0: X Window System and Resources
|
|
|
429 * Q5.0.1:: Where is a list of X resources?
|
|
|
430 * Q5.0.2:: How can I detect a color display?
|
|
|
431 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}?
|
|
|
432 * Q5.0.4:: How can I have the window title area display the full path?
|
|
|
433 * Q5.0.5:: @samp{xemacs -name junk} doesn't work?
|
|
|
434 * Q5.0.6:: @samp{-iconic} doesn't work.
|
|
|
435
|
|
|
436 5.1: Microsoft Windows
|
|
|
437 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
|
438 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
|
439
|
|
|
440 5.2: Printing
|
|
|
441 * Q5.2.1:: What do I need to change to make printing work?
|
|
|
442 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer?
|
|
|
443 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
|
444 * Q5.2.4:: Can you print under MS Windows?
|
|
|
445
|
|
|
446 5.3: Sound
|
|
|
447 * Q5.3.1:: How do I turn off the sound?
|
|
|
448 * Q5.3.2:: How do I get funky sounds instead of a boring beep?
|
|
|
449 * Q5.3.3:: What are NAS and ESD (EsounD)?
|
|
|
450 * Q5.3.4:: Sunsite sounds don't play.
|
|
|
451
|
|
|
452 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
453 * Q5.4.1:: What is an interior shell?
|
|
|
454 * Q5.4.2:: How do I start up a second shell buffer?
|
|
|
455 * Q5.4.3:: Telnet from shell filters too much
|
|
|
456 * Q5.4.4:: Strange things are happening in Shell Mode.
|
|
|
457 * Q5.4.5:: XEmacs complains "No such file or directory, diff"
|
|
2995
|
458 * Q5.4.6:: Cygwin error "fork_copy: linked dll/bss pass 0 failed"
|
|
2459
|
459
|
|
|
460 5.5: Multiple Device Support
|
|
|
461 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display?
|
|
|
462 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
463 * Q5.5.3:: How do I disable gnuserv from opening a new frame?
|
|
|
464 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
|
465 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
|
466
|
|
|
467 6 Connecting to the Internet
|
|
|
468
|
|
|
469 6.0: General Mail and News
|
|
|
470 * Q6.0.1:: What are the various packages for reading mail?
|
|
|
471 * Q6.0.2:: How can I send mail?
|
|
|
472 * Q6.0.3:: How do I get my outgoing mail archived?
|
|
|
473 * Q6.0.4:: How can I read and/or compose MIME messages?
|
|
|
474 * Q6.0.5:: How do I customize the From line?
|
|
|
475 * Q6.0.6:: How do I get my MUA to filter mail for me?
|
|
|
476 * Q6.0.7:: Remote mail reading with an MUA.
|
|
|
477 * Q6.0.8:: An MUA gets an error incorporating new mail.
|
|
|
478 * Q6.0.9:: Why isn't @file{movemail} working?
|
|
|
479 * Q6.0.10:: How do I make my MUA display graphical smilies?
|
|
|
480 * Q6.0.11:: How can I get those oh-so-neat X-Face lines?
|
|
|
481
|
|
|
482 6.1: Reading Mail with VM
|
|
|
483 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
484 * Q6.1.2:: How can I get VM to automatically check for new mail?
|
|
|
485 * Q6.1.3:: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"?
|
|
|
486 * Q6.1.4:: Is there a mailing list or FAQ for VM?
|
|
|
487 * Q6.1.5:: How do I make VM stay in a single frame?
|
|
|
488 * Q6.1.6:: Customization of VM not covered in the manual, or here.
|
|
|
489
|
|
|
490 6.2: Reading Netnews and Mail with Gnus
|
|
|
491 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
492 * Q6.2.2:: How do I make Gnus stay within a single frame?
|
|
|
493
|
|
|
494 6.3: FTP Access
|
|
|
495 * Q6.3.1:: Can I edit files on other hosts?
|
|
|
496 * Q6.3.2:: What is EFS?
|
|
|
497
|
|
|
498 6.4: Web Browsing with W3
|
|
|
499 * Q6.4.1:: What is W3?
|
|
|
500 * Q6.4.2:: How do I run W3 from behind a firewall?
|
|
|
501 * Q6.4.3:: Is it true that W3 supports style sheets and tables?
|
|
|
502
|
|
|
503 7 Advanced Customization Using XEmacs Lisp
|
|
|
504
|
|
2537
|
505 7.0: Emacs Lisp and @file{init.el}
|
|
|
506 * Q7.0.1:: What version of Emacs am I running?
|
|
|
507 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions?
|
|
|
508 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly.
|
|
|
509 * Q7.0.4:: How can I add directories to the @code{load-path}?
|
|
|
510 * Q7.0.5:: How to check if a lisp function is defined?
|
|
|
511 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer?
|
|
|
512
|
|
|
513 7.1: Emacs Lisp Programming Techniques
|
|
|
514 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
|
515 * Q7.1.2:: Can I generate "fake" keyboard events?
|
|
|
516 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail?
|
|
|
517 * Q7.1.4:: What is the performance hit of @code{let}?
|
|
|
518 * Q7.1.5:: What is the recommended use of @code{setq}?
|
|
|
519 * Q7.1.6:: What is the typical misuse of @code{setq}?
|
|
|
520 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down?
|
|
|
521 * Q7.1.8:: I like recursion, does it slow things down?
|
|
|
522 * Q7.1.9:: How do I put a glyph as annotation in a buffer?
|
|
|
523 * Q7.1.10:: @code{map-extents} won't traverse all of my extents!
|
|
|
524 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
|
525
|
|
|
526 7.2: Mathematics
|
|
2559
|
527 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp?
|
|
|
528 * Q7.2.2:: XEmacs segfaults when I use very big numbers!
|
|
|
529 * Q7.2.3:: Bignums are really slow!
|
|
|
530 * Q7.2.4:: Equal bignums don't compare as equal! What gives?
|
|
2459
|
531
|
|
|
532 8 Other External Packages
|
|
|
533
|
|
|
534 8.0: TeX
|
|
|
535 * Q8.0.1:: Is there something better than LaTeX mode?
|
|
|
536 * Q8.0.2:: What is AUCTeX? Where do you get it?
|
|
|
537 * Q8.0.3:: Problems installing AUCTeX.
|
|
|
538 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline?
|
|
|
539
|
|
|
540 8.1: Other Unbundled Packages
|
|
|
541 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
|
542 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets?
|
|
|
543 * Q8.1.3:: Is there a MatLab mode?
|
|
|
544
|
|
|
545 8.2: Environments Built Around XEmacs
|
|
|
546 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop?
|
|
|
547 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21?
|
|
|
548 * Q8.2.3:: What is/was Energize?
|
|
|
549 * Q8.2.4:: What is Infodock?
|
|
|
550
|
|
|
551 9 What the Future Holds
|
|
|
552
|
|
|
553 9.0: Changes
|
|
|
554 * Q9.0.1:: What new features will be in XEmacs soon?
|
|
|
555 * Q9.0.2:: What's new in XEmacs 21.4?
|
|
|
556 * Q9.0.3:: What's new in XEmacs 21.1?
|
|
|
557 * Q9.0.4:: What's new in XEmacs 20.4?
|
|
|
558 * Q9.0.5:: What's new in XEmacs 20.3?
|
|
|
559 * Q9.0.6:: What's new in XEmacs 20.2?
|
|
|
560
|
|
|
561 10 New information about old XEmacsen
|
|
|
562
|
|
|
563 10.0: XEmacs 21.1
|
|
|
564 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
2559
|
565 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1.
|
|
|
566
|
|
428
|
567 @end detailmenu
|
|
|
568 @end menu
|
|
|
569
|
|
|
570 @node Introduction, Installation, Top, Top
|
|
|
571 @unnumbered 1 Introduction, Policy, Credits
|
|
|
572
|
|
|
573 Learning XEmacs is a lifelong activity. Even people who have used Emacs
|
|
|
574 for years keep discovering new features. Therefore this document cannot
|
|
|
575 be complete. Instead it is aimed at the person who is either
|
|
|
576 considering XEmacs for their own use, or has just obtained it and is
|
|
|
577 wondering what to do next. It is also useful as a reference to
|
|
|
578 available resources.
|
|
|
579
|
|
2417
|
580 The previous maintainer of the FAQ was
|
|
|
581 @email{rossini@@biostat.washington.edu, Anthony Rossini}, who started
|
|
|
582 it, after getting tired of hearing JWZ complain about repeatedly
|
|
|
583 having to answer questions. @email{ben@@xemacs.org, Ben Wing} then
|
|
|
584 took over and did a massive update reorganizing the whole thing. At
|
|
|
585 this point Anthony took back over, but then had to give it up again.
|
|
|
586 Some of the other contributors to this FAQ are listed later in this
|
|
|
587 document.
|
|
428
|
588
|
|
|
589 The previous version was converted to hypertext format, and edited by
|
|
|
590 @email{steve@@xemacs.org, Steven L. Baur}. It was converted back to
|
|
434
|
591 texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}. The FAQ was then
|
|
|
592 maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it
|
|
2417
|
593 on to ChristianNyb@o{}, and then to @email{wambold@@xemacs.org,Sandra Wambold}.
|
|
|
594
|
|
|
595 The current version of the FAQ has been heavily redone by
|
|
|
596 @email{ben@@xemacs.org, Ben Wing}.
|
|
428
|
597
|
|
|
598 If you notice any errors or items which should be added or amended to
|
|
2417
|
599 this FAQ please send email to @email{xemacs-beta@@xemacs.org}.
|
|
|
600 Include @samp{XEmacs FAQ} on the Subject: line.
|
|
428
|
601
|
|
|
602 @menu
|
|
2537
|
603 1.0: What is XEmacs?
|
|
2417
|
604 * Q1.0.1:: What is XEmacs?
|
|
|
605 * Q1.0.2:: What is the current version of XEmacs?
|
|
2537
|
606 * Q1.0.3:: How do you pronounce XEmacs?
|
|
|
607 * Q1.0.4:: What does XEmacs look like?
|
|
|
608 * Q1.0.5:: Who wrote XEmacs?
|
|
|
609 * Q1.0.6:: Who wrote the FAQ?
|
|
|
610
|
|
|
611 1.1: Getting XEmacs
|
|
|
612 * Q1.1.1:: Where can I find XEmacs?
|
|
|
613 * Q1.1.2:: Are binaries available?
|
|
|
614 * Q1.1.3:: How do I get the bleeding-edge sources?
|
|
|
615 * Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual?
|
|
|
616
|
|
|
617 1.2: Versions for Different Operating Systems
|
|
|
618 * Q1.2.1:: Do I need X11 to run XEmacs?
|
|
|
619 * Q1.2.2:: What versions of Unix does XEmacs run on?
|
|
|
620 * Q1.2.3:: Is there a port of XEmacs to Microsoft Windows?
|
|
|
621 * Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
622 * Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
623 * Q1.2.6:: What are the differences between the various MS Windows emacsen?
|
|
|
624 * Q1.2.7:: How does the port cope with differences in the Windows user interface?
|
|
|
625 * Q1.2.8:: Is there a port of XEmacs to the Macintosh?
|
|
|
626 * Q1.2.9:: Is there a port of XEmacs to MS-DOS?
|
|
|
627 * Q1.2.10:: Is there a port of XEmacs to OS/2?
|
|
|
628 * Q1.2.11:: Is there a port of XEmacs to NextStep?
|
|
|
629 * Q1.2.12:: Is there a port of XEmacs to VMS?
|
|
|
630
|
|
|
631 1.3: Getting Started
|
|
|
632 * Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
|
633 * Q1.3.2:: Where do I put my @file{init.el} file?
|
|
|
634 * Q1.3.3:: Can I use the same @file{init.el} with the other Emacs?
|
|
|
635 * Q1.3.4:: Any good XEmacs tutorials around?
|
|
|
636 * Q1.3.5:: May I see an example of a useful XEmacs Lisp function?
|
|
|
637 * Q1.3.6:: And how do I bind it to a key?
|
|
|
638 * Q1.3.7:: What's the difference between a macro and a function?
|
|
|
639 * Q1.3.8:: What is @code{Custom}?
|
|
|
640
|
|
|
641 1.4: Getting Help
|
|
|
642 * Q1.4.1:: Where can I get help?
|
|
|
643 * Q1.4.2:: Which mailing lists are there?
|
|
2559
|
644 * Q1.4.3:: Where are the mailing lists archived?
|
|
|
645 * Q1.4.4:: How can I get two instances of info?
|
|
|
646 * Q1.4.5:: How do I add new Info directories?
|
|
2537
|
647
|
|
|
648 1.5: Contributing to XEmacs
|
|
|
649 * Q1.5.1:: How do I submit changes to the FAQ?
|
|
|
650 * Q1.5.2:: How do I become a beta tester?
|
|
|
651 * Q1.5.3:: How do I contribute to XEmacs itself?
|
|
2559
|
652 * Q1.5.4:: How do I get started developing XEmacs?
|
|
|
653 * Q1.5.5:: What's the basic layout of the code?
|
|
2537
|
654
|
|
|
655 1.6: Politics (XEmacs vs. GNU Emacs)
|
|
|
656 * Q1.6.1:: What is GNU Emacs?
|
|
|
657 * Q1.6.2:: How does XEmacs differ from GNU Emacs?
|
|
|
658 * Q1.6.3:: How much does XEmacs differ?
|
|
|
659 * Q1.6.4:: Is XEmacs "GNU"?
|
|
|
660 * Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
|
661 * Q1.6.6:: Why haven't XEmacs and GNU Emacs merged?
|
|
|
662
|
|
|
663 1.7: External Packages
|
|
2559
|
664 * Q1.7.1:: What is the package system?
|
|
|
665 * Q1.7.2:: Which external packages are there?
|
|
|
666 * Q1.7.3:: Do I need to have the packages to run XEmacs?
|
|
|
667 * Q1.7.4:: Is there a way to find which package has particular functionality?
|
|
2537
|
668
|
|
|
669 1.8: Internationalization
|
|
|
670 * Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
|
671 * Q1.8.2:: How can I help with internationalization?
|
|
|
672 * Q1.8.3:: How do I type non-ASCII characters?
|
|
|
673 * Q1.8.4:: Can XEmacs messages come out in a different language?
|
|
|
674 * Q1.8.5:: Please explain the various input methods in MULE/XEmacs
|
|
|
675 * Q1.8.6:: How do I portably code for MULE/XEmacs?
|
|
|
676 * Q1.8.7:: How about Cyrillic modes?
|
|
|
677 * Q1.8.8:: Does XEmacs support Unicode?
|
|
|
678 * Q1.8.9:: How does XEmacs display Unicode?
|
|
428
|
679 @end menu
|
|
|
680
|
|
2537
|
681 @unnumberedsec 1.0: What is XEmacs?
|
|
2417
|
682
|
|
428
|
683 @node Q1.0.1, Q1.0.2, Introduction, Introduction
|
|
|
684 @unnumberedsubsec Q1.0.1: What is XEmacs?
|
|
|
685
|
|
479
|
686 XEmacs is a powerful, highly customizable open source text editor and
|
|
2417
|
687 application development system, with full GUI support. It is
|
|
|
688 protected under the GNU Public License and related to other versions
|
|
|
689 of Emacs, in particular GNU Emacs. Its emphasis is on modern
|
|
|
690 graphical user interface support and an open software development
|
|
|
691 model, similar to Linux. XEmacs has an active development community
|
|
|
692 numbering in the hundreds (and thousands of active beta testers on top
|
|
|
693 of this), and runs on all versions of MS Windows, on Mac OS X, on
|
|
|
694 Linux, and on nearly every other version of Unix in existence.
|
|
|
695 Support for XEmacs has been supplied by Sun Microsystems, University
|
|
|
696 of Illinois, Lucid, ETL/Electrotechnical Laboratory, Amdahl
|
|
|
697 Corporation, BeOpen, and others, as well as the unpaid time of a great
|
|
|
698 number of individual developers.
|
|
428
|
699
|
|
|
700 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction
|
|
|
701 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs?
|
|
|
702
|
|
2417
|
703 XEmacs versions 21.4.* are releases made from the current stable
|
|
|
704 sources. XEmacs versions 21.5.* (which will be released as 22.0) are
|
|
|
705 releases made from the development sources. Check at
|
|
|
706 @uref{http://www.xemacs.org} for the current minor version. XEmacs
|
|
|
707 versions 21.1.* were the previous stable releases, now retired.
|
|
|
708
|
|
|
709 XEmacs 20.4, released in February 1998, was the last release of v20.
|
|
|
710
|
|
|
711 XEmacs 19.16, released in November, 1997. was the last release of v19,
|
|
|
712 and was also the last version without international language support.
|
|
428
|
713
|
|
|
714 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction
|
|
2537
|
715 @unnumberedsubsec Q1.0.3: How do you pronounce XEmacs?
|
|
|
716
|
|
|
717 The most common pronounciation is @samp{Eks eemax}.
|
|
428
|
718
|
|
|
719 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction
|
|
2537
|
720 @unnumberedsubsec Q1.0.4: What does XEmacs look like?
|
|
|
721
|
|
|
722 Screen snapshots are available at
|
|
|
723 @uref{http://www.xemacs.org/About/Screenshots/index.html}
|
|
|
724 as part of the XEmacs website.
|
|
|
725
|
|
|
726 @node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
|
|
|
727 @unnumberedsubsec Q1.0.5: Who wrote XEmacs?
|
|
|
728
|
|
|
729 XEmacs is the result of the time and effort of many people, and the
|
|
|
730 active developers have changed over time. There are two major
|
|
|
731 components of the XEmacs effort -- writing the code itself and providing
|
|
|
732 all the support work (testing the code, releasing beta and final
|
|
|
733 versions, handling patches, reading bug reports, maintaining the web
|
|
|
734 site, managing the mailing lists, etc. etc.). Neither component would
|
|
|
735 work without the other.
|
|
|
736
|
|
|
737 @subheading CODING
|
|
|
738
|
|
|
739 The primary code contributor over the years has been Ben Wing (active
|
|
|
740 since late 1992). Between 1991 and 1995, large amounts of coding was
|
|
|
741 contributed by Jamie Zawinski and Chuck Thompson. Many other people
|
|
|
742 have authored major subsystems or otherwise contributed large amounts of
|
|
|
743 code, including Andy Piper, Hrvoje Niksic, Jerry James, Jonathan Harris,
|
|
|
744 Kyle Jones, Martin Buchholz, Michael Sperber, Olivier Galibert, Richard
|
|
|
745 Mlynarik, Stig, William Perry and plenty of others.
|
|
|
746
|
|
|
747 Primary XEmacs-specific subsystems and their authors:
|
|
|
748
|
|
|
749 @table @asis
|
|
|
750 @item Objects
|
|
|
751 @itemize @minus
|
|
|
752 @item
|
|
|
753 Conversion from 26-bit to 28-bit pointers and integers, lrecords, lcrecords: Richard Mlynarik, 1994
|
|
|
754 @item
|
|
|
755 Conversion to 32-bit pointers and 31-bit integers: Kyle Jones, Martin Buchholz
|
|
|
756 @item
|
|
|
757 Portable dumper, object descriptions: Olivier Galibert
|
|
|
758 @item
|
|
|
759 KKCC (new garbage collector), ephemerons, weak boxes: Michael Sperber and students
|
|
|
760 @item
|
|
|
761 Random object work (object equal and hash methods, weak lists, lcrecord lists, bit vectors, dynarr, blocktype, opaque, string resizing): Ben Wing
|
|
|
762 @item
|
|
|
763 Profiling: Ben Wing
|
|
|
764 @item
|
|
|
765 Some byte-compilation and hash-table improvements: Martin Buchholz
|
|
|
766 @item
|
|
|
767 Bignum: Jerry James
|
|
|
768 @end itemize
|
|
|
769
|
|
|
770 @item Internationalization/Mule
|
|
|
771 @itemize @minus
|
|
|
772 @item
|
|
|
773 mostly Ben Wing; many ideas for future work, Stephen Turnbull
|
|
|
774 @end itemize
|
|
|
775
|
|
|
776 @item I/O
|
|
|
777 @itemize @minus
|
|
|
778 @item
|
|
|
779 Basic event/event-stream implementation: Jamie Zawinski
|
|
|
780 @item
|
|
|
781 Most event work since 1994: Ben Wing
|
|
|
782 @item
|
|
|
783 Asynchronous stuff (async timeouts, signals, quit-checking): Ben Wing
|
|
|
784 @item
|
|
|
785 Process method abstraction, Windows process work: Kirill Katsnelson
|
|
|
786 @item
|
|
|
787 Misc-user events, async timeouts, most quit-checking and signal code, most other work since 1994: Ben Wing
|
|
|
788 @item
|
|
|
789 Lstreams: Ben Wing
|
|
|
790 @end itemize
|
|
|
791
|
|
|
792 @item Display
|
|
|
793 @itemize @minus
|
|
|
794 @item
|
|
|
795 Redisplay mechanism: implementation, Chuck Thompson; additional work, lots of people
|
|
|
796 @item
|
|
|
797 Glyphs: mostly Ben Wing
|
|
|
798 @item
|
|
|
799 Specifiers: Ben Wing
|
|
|
800 @item
|
|
|
801 Extents: initial implementation, someone at Lucid; rewrite, 1994, Ben Wing
|
|
|
802 @item
|
|
|
803 Widgets: Andy Piper
|
|
|
804 @item
|
|
|
805 JPEG/PNG/TIFF image converters: Ben Wing, William Perry, Jareth Hein, others (see comment in @file{glyphs-eimage.c})
|
|
|
806 @item
|
|
|
807 Menus: Jamie Zawinski, someone at Lucid (Lucid menus)
|
|
|
808 @item
|
|
|
809 Scrollbars: Chuck Thompson, ??? (Lucid scrollbar)
|
|
|
810 @item
|
|
|
811 Multi-device/device-independence work (console/device/etc methods): Ben Wing, prototype by chuck thompson
|
|
|
812 @item
|
|
|
813 Faces: first implementation, Jamie Zawinski; second, chuck; third, Ben Wing
|
|
|
814 @item
|
|
|
815 Fonts/colors: first implementation, Jamie Zawinski; further work, Ben Wing
|
|
|
816 @item
|
|
|
817 Toolbars: implementation, chuck, much interface work, Ben Wing
|
|
|
818 @item
|
|
|
819 Gutters, tabs: andy piper
|
|
|
820 @end itemize
|
|
|
821
|
|
|
822 @item Device subsystems
|
|
|
823 @itemize @minus
|
|
|
824 @item
|
|
|
825 X Windows: Jamie Zawinksi, Ben Wing, others
|
|
|
826 @item
|
|
|
827 GTK: William Perry, Malcolm Purvis
|
|
|
828 @item
|
|
|
829 MS Windows: initial implementation, Jonathan Harris; some more work, Andy Piper, Ben Wing
|
|
|
830 @item
|
|
|
831 TTY: Chuck Thompson, Ben Wing
|
|
|
832 @item
|
|
|
833 Cygwin: Andy Piper
|
|
|
834 @end itemize
|
|
|
835
|
|
|
836 @item Misc
|
|
|
837 @itemize @minus
|
|
|
838 @item
|
|
|
839 Configure: initial porting from fsf, Chuck Thompson; conversion to autoconf 2, much rewriting, Martin Buchholz
|
|
|
840 @item
|
|
|
841 Most initialization-related code: Ben Wing
|
|
|
842 @item
|
|
|
843 Internals manual, much of Lisp manual: Ben Wing
|
|
|
844 @item
|
|
|
845 FSF synching: initial sync with FSF 19, Richard Mlynarik, further work, Ben Wing
|
|
|
846 @end itemize
|
|
|
847 @end table
|
|
|
848
|
|
|
849 @subheading SUPPORT
|
|
|
850
|
|
|
851 Currently, support duties are handled by many different people.
|
|
|
852
|
|
|
853 Release managers have been
|
|
|
854
|
|
|
855 @itemize @minus
|
|
|
856 @item
|
|
|
857 Stephen Turnbull (April 2001 - January 2003, March 2004 - present, 21.2.47 - 21.4.12, 21.5.2 - 21.5.7, 21.5.17 - present)
|
|
|
858 @item
|
|
|
859 Vin Shelton (May 2003 - present, 21.4.13 - present)
|
|
|
860 @item
|
|
|
861 Steve Youngs (July 2002 - September 2003, 21.5.8 - 21.5.16)
|
|
|
862 @item
|
|
|
863 Martin Buchholz (December 1998, November 1999 - May 2001, 21.2.7 - 21.2.8, 21.2.21 - 21.2.46, 21.5.0 - 21.5.1)
|
|
|
864 @item
|
|
|
865 Steve Baur (early 1997 - December 1998, February 1999 - November 1999, 19.15 - 21.2.5, 21.2.9 - 21.2.20)
|
|
|
866 @item
|
|
|
867 Andy Piper (December 1998, 21.2.6)
|
|
|
868 @item
|
|
|
869 Chuck Thompson (June 1994 - September 1996, 19.11 - 19.14)
|
|
|
870 @item
|
|
|
871 Jamie Zawinski (April 1991 - June 1994, 19.0 - 19.10)
|
|
|
872 @end itemize
|
|
|
873
|
|
|
874 The recent overlapping dates are intentional, since two or three trees
|
|
|
875 are maintained simultaneously at any point.
|
|
|
876
|
|
|
877 Other major support work:
|
|
|
878
|
|
|
879 @itemize @minus
|
|
|
880 @item
|
|
|
881 Adrian Aichner wrote and maintains the web site.
|
|
|
882 @item
|
|
|
883 Stephen Turnbull has produced many of the beta and semi-stable releases
|
|
|
884 and has attempted to be the "face" of XEmacs on the newsgroups and
|
|
|
885 mailing lists.
|
|
|
886 @item
|
|
|
887 Steve Youngs currently produces the beta releases (???).
|
|
|
888 @item
|
|
|
889 Steve Youngs, Ville Skytta, and now Norbert Koch have taken turns
|
|
|
890 maintaining the packages.
|
|
|
891 @item
|
|
|
892 Vin Shelton maintains the stable releases.
|
|
|
893 @item
|
|
|
894 Testing - #### Norbert, Adrian, ???
|
|
|
895 @end itemize
|
|
|
896
|
|
|
897 Portraits and email of some of the major developers:
|
|
|
898
|
|
|
899 @itemize @bullet
|
|
|
900 @item @email{andy@@xemacs.org, Andy Piper}
|
|
|
901 @html
|
|
|
902 <br><img src="piper.png" alt="Portrait of Andy Piper"><br>
|
|
|
903 @end html
|
|
|
904
|
|
|
905 @item @email{ben@@xemacs.org, Ben Wing}
|
|
|
906 @html
|
|
|
907 <br><img src="ben.png" alt="Portrait of Ben Wing"><br>
|
|
|
908 @end html
|
|
|
909
|
|
|
910 @item @email{cthomp@@xemacs.org, Chuck Thompson}
|
|
|
911 @html
|
|
|
912 <br><img src="cthomp.png" alt="Portrait of Chuck Thompson"><br>
|
|
|
913 @end html
|
|
|
914
|
|
|
915 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
|
|
|
916
|
|
|
917 @html
|
|
|
918 <br><img src="hniksic.png" alt="Portrait of Hrvoje Niksic"><br>
|
|
|
919 @end html
|
|
|
920
|
|
|
921 @item @email{jwz@@jwz.org, Jamie Zawinski}
|
|
|
922 @html
|
|
|
923 <br><img src="jwz.png" alt="Portrait of Jamie Zawinski"><br>
|
|
|
924 @end html
|
|
|
925
|
|
|
926 @item @email{martin@@xemacs.org, Martin Buchholz}
|
|
|
927 @html
|
|
|
928 <br><img src="martin.png" alt="Portrait of Martin Buchholz"><br>
|
|
|
929 @end html
|
|
|
930
|
|
|
931 @item @email{mly@@adoc.xerox.com, Richard Mlynarik}
|
|
|
932 @html
|
|
|
933 <br><img src="mly.png" alt="Portrait of Richard Mlynarik"><br>
|
|
|
934 @end html
|
|
|
935
|
|
|
936 @item @email{stephen@@xemacs.org, Stephen Turnbull}
|
|
|
937
|
|
|
938 @item @email{steve@@xemacs.org, Steve Baur}
|
|
|
939 @html
|
|
|
940 <br><img src="slb.png" alt="Portrait of Steve Baur"><br>
|
|
|
941 @end html
|
|
|
942 @end itemize
|
|
|
943
|
|
|
944 Many other people have contributed to XEmacs; this is partially
|
|
|
945 enumerated in the @samp{About XEmacs} option in the Help menu.
|
|
|
946
|
|
|
947 @node Q1.0.6, Q1.1.1, Q1.0.5, Introduction
|
|
|
948 @unnumberedsubsec Q1.0.6: Who wrote the FAQ?
|
|
|
949
|
|
|
950 The current version of this FAQ was created by @email{ben@@xemacs.org,
|
|
|
951 Ben Wing}.
|
|
|
952
|
|
|
953 Previous contributors to the FAQ include
|
|
|
954
|
|
|
955 @itemize @bullet
|
|
|
956 @item @email{steve@@xemacs.org, SL Baur}
|
|
|
957
|
|
|
958 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
|
|
|
959
|
|
|
960 @item @email{binge@@aloft.att.com, Curtis.N.Bingham}
|
|
|
961
|
|
|
962 @item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan}
|
|
|
963
|
|
|
964 @item @email{rjc@@cogsci.ed.ac.uk, Richard Caley}
|
|
|
965
|
|
|
966 @item @email{cognot@@ensg.u-nancy.fr, Richard Cognot}
|
|
|
967
|
|
|
968 @item @email{daku@@nortel.ca, Mark Daku}
|
|
|
969
|
|
|
970 @item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque}
|
|
|
971
|
|
|
972 @item @email{eeide@@cs.utah.edu, Eric Eide}
|
|
|
973
|
|
|
974 @item @email{af@@biomath.jussieu.fr, Alain Fauconnet}
|
|
|
975
|
|
|
976 @item @email{cflatter@@nrao.edu, Chris Flatters}
|
|
|
977
|
|
|
978 @item @email{ginsparg@@adra.com, Evelyn Ginsparg}
|
|
|
979
|
|
|
980 @item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall}
|
|
|
981
|
|
|
982 @item @email{dkindred@@cmu.edu, Darrell Kindred}
|
|
|
983
|
|
|
984 @item @email{dmoore@@ucsd.edu, David Moore}
|
|
|
985
|
|
|
986 @item @email{arup+@@cmu.edu, Arup Mukherjee}
|
|
|
987
|
|
|
988 @item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen}
|
|
|
989
|
|
|
990 @item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell}
|
|
|
991
|
|
|
992 @item @email{dworkin@@ccs.neu.edu, Justin Sheehy}
|
|
|
993
|
|
|
994 @item @email{stig@@hackvan.com, Stig}
|
|
|
995
|
|
|
996 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
|
|
|
997 @end itemize
|
|
|
998
|
|
|
999 @unnumberedsec 1.1: Getting XEmacs
|
|
|
1000
|
|
|
1001 @node Q1.1.1, Q1.1.2, Q1.0.6, Introduction
|
|
|
1002 @unnumberedsubsec Q1.1.1: Where can I find XEmacs?
|
|
|
1003
|
|
|
1004 To download XEmacs, visit the XEmacs WWW page at
|
|
|
1005 @uref{http://www.xemacs.org/Download/}. The most up-to-date list of
|
|
|
1006 distribution sites can always be found there. Try to pick a site that
|
|
|
1007 is networkologically close to you. If you know of other mirrors of
|
|
|
1008 the XEmacs archives, please send e-mail to
|
|
|
1009 @uref{mailto:webmaster@@xemacs.org} and we will list them here as well.
|
|
|
1010
|
|
|
1011 The canonical distribution point is ftp.xemacs.org, available either
|
|
|
1012 through HTTP (@uref{http://ftp.xemacs.org/}) or anonymous FTP
|
|
|
1013 (@uref{ftp://ftp.xemacs.org/pub/xemacs/}).
|
|
|
1014
|
|
|
1015 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
|
|
|
1016 @unnumberedsubsec Q1.1.2: Are binaries available?
|
|
2417
|
1017
|
|
|
1018 MS Windows binaries are available at
|
|
|
1019 @uref{http://www.xemacs.org/Download/win32/} for the native versions
|
|
|
1020 of 21.4 and 21.1. Cygwin binaries are now available as part of the
|
|
|
1021 standard Cygwin installation process. XEmacs also comes pre-built as
|
|
|
1022 part of many Linux distributions, such as Red Hat and SuSE.
|
|
|
1023
|
|
|
1024 Otherwise, you will need to build XEmacs yourself or get your system
|
|
|
1025 administrator to do it. Generally, this is not a difficult process
|
|
|
1026 under Unix and Mac OS X, as XEmacs has been tested under all of the
|
|
|
1027 common Unix versions and under Mac OS X and comes with an extensive
|
|
|
1028 configure script that is able to automatically detect most aspects of
|
|
|
1029 the configuration of your particular system.
|
|
|
1030
|
|
2537
|
1031 @node Q1.1.3, Q1.1.4, Q1.1.2, Introduction
|
|
|
1032 @unnumberedsubsec Q1.1.3: How do I get the bleeding-edge sources?
|
|
|
1033
|
|
|
1034 If you are interested in developing XEmacs, or getting the absolutely most
|
|
|
1035 recent, up-to-the-moment, bleeding-edge source code, you can directly
|
|
|
1036 access the master CVS source tree (read-only, of course, until you ask for
|
|
|
1037 and are granted permission to directly modify portions of the source tree)
|
|
|
1038 at cvs.xemacs.org. Directions on how to access the source tree are located
|
|
|
1039 at @uref{http://www.xemacs.org/Develop/cvsaccess.html}.
|
|
|
1040
|
|
|
1041 Nightly CVS snapshots are available at
|
|
|
1042 @uref{http://www.dk.xemacs.org/Download/CVS-snapshots/}.
|
|
|
1043
|
|
|
1044 @node Q1.1.4, Q1.2.1, Q1.1.3, Introduction
|
|
|
1045 @unnumberedsubsec Q1.1.4: Where can I obtain a printed copy of the XEmacs User's Manual?
|
|
|
1046
|
|
|
1047 Pre-printed manuals are not available. If you are familiar with
|
|
|
1048 TeX, you can generate your own manual from the XEmacs sources.
|
|
|
1049
|
|
|
1050 HTML and Postscript versions of XEmacs manuals are available from the
|
|
|
1051 XEmacs web site at
|
|
|
1052 @uref{http://www.xemacs.org/Documentation/index.html}.
|
|
|
1053
|
|
|
1054 @unnumberedsec 1.2: Versions for Different Operating Systems
|
|
|
1055
|
|
|
1056 @node Q1.2.1, Q1.2.2, Q1.1.4, Introduction
|
|
|
1057 @unnumberedsubsec Q1.2.1: Do I need X11 to run XEmacs?
|
|
|
1058
|
|
|
1059 No. The name @dfn{XEmacs} is unfortunate in the sense that it is
|
|
|
1060 @strong{not} an X Window System-only version of Emacs. XEmacs has
|
|
|
1061 full color support on a color-capable character terminal.
|
|
|
1062
|
|
|
1063 @node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
|
|
|
1064 @unnumberedsubsec Q1.2.2: What versions of Unix does XEmacs run on?
|
|
|
1065
|
|
2559
|
1066 XEmacs is regularly tested on Linux, Solaris, SunOS, HP/UX, FreeBSD,
|
|
|
1067 OpenBSD, BSD/OS aka BSDI, Tru64 aka DEC/OSF, SCO5, and probably
|
|
|
1068 others. It should work on all versions of Unix created in the last 10
|
|
|
1069 years or so, perhaps with a bit of work on more obscure platforms to
|
|
|
1070 correct bit-rot. It uses a sophisticated configuration system to
|
|
|
1071 auto-detect zillions of features that are implemented differently in
|
|
|
1072 different versions of Unix, so it will probably work on your vendor's
|
|
|
1073 version, possibly with a bit of tweaking, even if we've never heard of
|
|
|
1074 it.
|
|
|
1075
|
|
2537
|
1076 For problems with particular machines and versions of Unix, see the
|
|
|
1077 @file{PROBLEMS} file.
|
|
|
1078
|
|
|
1079 Much effort has gone into making XEmacs work on as many different
|
|
|
1080 machines, configurations, and compilers as possible.
|
|
|
1081
|
|
|
1082 Much effort has gone into making XEmacs 64-bit clean.
|
|
|
1083
|
|
|
1084 Much effort has gone into removing system-specific code, and replacing
|
|
|
1085 such code with autodetection at configure time.
|
|
|
1086
|
|
|
1087 The XEmacs core should build "out of the box" on most Unix-like systems.
|
|
|
1088
|
|
|
1089 XEmacs 21.2 was tested and @samp{make check} succeeded on these Unix
|
|
|
1090 configurations as of 2001-02-10:
|
|
|
1091
|
|
|
1092 @example
|
|
|
1093 alphaev56-dec-osf4.0e (both Compaq C and gcc)
|
|
|
1094 i386-unknown-freebsd4.2
|
|
|
1095 i386-unknown-netbsdelf1.5
|
|
|
1096 i586-sco-sysv5uw7.0.1 (both SCO's cc and gcc)
|
|
|
1097 i686-pc-linux-gnu
|
|
|
1098 hppa2.0-hp-hpux10.20 (both HP's ANSI cc and gcc)
|
|
|
1099 mips-sgi-irix6.5 (both MIPSpro cc and gcc)
|
|
|
1100 rs6000-ibm-aix4.3.0.0 (both IBM's xlc and gcc)
|
|
|
1101 sparc-sun-solaris2.6 (both Sun's Forte C and gcc)
|
|
|
1102 sparc-sun-solaris2.7 (both Sun's Forte C and gcc)
|
|
|
1103 sparc-sun-sunos4.1.4 (gcc)
|
|
|
1104 @end example
|
|
|
1105
|
|
|
1106 Some systems have a dual mode 32-bit/64-bit compiler. On most of
|
|
|
1107 these, XEmacs requires the @samp{--pdump} configure option to build
|
|
|
1108 correctly with the 64-bit version of the compiler.
|
|
|
1109
|
|
|
1110 @example
|
|
|
1111 mips-sgi-irix6.5, CC="gcc -mabi=64"
|
|
|
1112 mips-sgi-irix6.5, CC="cc -64"
|
|
|
1113 rs6000-ibm-aix4.3.0.0, CC="cc -q64"
|
|
|
1114 @end example
|
|
|
1115
|
|
|
1116 On most of these systems, XEmacs also builds with a C++ compiler,
|
|
|
1117 but not "out of the box". This feature is only for use by the
|
|
|
1118 maintainers.
|
|
|
1119
|
|
|
1120 XEmacs 21.2 is known @emph{not} to work on any machines with m680x0
|
|
|
1121 processors. Sorry, all you sun3 and Unix PC nostalgia buffs out there.
|
|
|
1122
|
|
|
1123 VMS has never been supported by XEmacs. In fact, all the old VMS code
|
|
|
1124 inherited from Emacs has been removed. Sorry, all you VMS fans out there.
|
|
|
1125
|
|
|
1126 @node Q1.2.3, Q1.2.4, Q1.2.2, Introduction
|
|
|
1127 @unnumberedsubsec Q1.2.3: Is there a port of XEmacs to Microsoft Windows?
|
|
|
1128
|
|
|
1129 Yes. Beginning with release 21.0, XEmacs has worked under MS Windows
|
|
|
1130 and is fully-featured and actively developed. A group of dedicated
|
|
|
1131 developers actively maintains and improves the Windows-specific
|
|
|
1132 portions of the code. Some of the core developers, in fact, use
|
|
|
1133 Windows as their only development environment, and some features, such
|
|
|
1134 as printing, actually work better on Windows than native Unix and Mac
|
|
|
1135 OS X. The mailing list at @email{xemacs-winnt@@xemacs.org} is dedicated
|
|
|
1136 to that effort (please use the -request address to
|
|
|
1137 subscribe). (Despite its name, XEmacs actually works on all versions
|
|
|
1138 of Windows.)
|
|
|
1139
|
|
|
1140 The list name is misleading, as XEmacs supports and has been compiled on
|
|
|
1141 Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows
|
|
|
1142 XP, and all newer versions of Windows. The MS Windows-specific code is
|
|
|
1143 based on Microsoft Win32 API, and will not work on MS Windows 3.x or on
|
|
|
1144 MS-DOS.
|
|
|
1145
|
|
|
1146 XEmacs also supports the Cygwin and MinGW development and runtime
|
|
|
1147 environments, where it also uses native Windows code for graphical
|
|
|
1148 features. In addition, under Cygwin it is possible to compile XEmacs
|
|
|
1149 to use an X server (and XFree86 is available as part of the standard
|
|
|
1150 Cygwin installation).
|
|
|
1151
|
|
|
1152 @node Q1.2.4, Q1.2.5, Q1.2.3, Introduction
|
|
|
1153 @unnumberedsubsec Q1.2.4: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
1154
|
|
|
1155 Yes, you can, but no you do not need to. In fact, we recommend that you
|
|
|
1156 use a native-GUI version unless you have a specific need for an X
|
|
|
1157 version.
|
|
|
1158
|
|
|
1159 @node Q1.2.5, Q1.2.6, Q1.2.4, Introduction
|
|
|
1160 @unnumberedsubsec Q1.2.5: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
1161
|
|
|
1162 To answer the second part of the question: No, you, you don't need
|
|
|
1163 Cygwin or MinGW to build or to run XEmacs. But if you have them and
|
|
|
1164 want to use them, XEmacs supports these environments.
|
|
|
1165
|
|
|
1166 (One important reason to support Cygwin is that it lets the MS Windows
|
|
|
1167 developers test out their code in a Unix environment without actually
|
|
|
1168 having to have a Unix machine around. For this reason alone, Cygwin
|
|
|
1169 support is likely to remain supported for a long time in XEmacs. Same
|
|
|
1170 goes for the X support under Cygwin, for the same reasons. MinGW
|
|
|
1171 support, on the other hand, depends on volunteers to keep it up to date;
|
|
|
1172 but this is generally not hard.)
|
|
|
1173
|
|
|
1174 Cygwin is a set of tools providing Unix-like API on top of Win32.
|
|
|
1175 It makes it easy to port large Unix programs without significant
|
|
|
1176 changes to their source code. It is a development environment as well
|
|
|
1177 as a runtime environment.
|
|
|
1178
|
|
|
1179 When built with Cygwin, XEmacs supports all display types -- TTY, X &
|
|
|
1180 Win32 GUI, and can be built with support for all three simultaneously.
|
|
|
1181 If you build with Win32 GUI support then the Cygwin version uses the
|
|
|
1182 majority of the Windows-specific code, which is mostly related to
|
|
|
1183 display. If you want to build with X support you need X libraries (and
|
|
2559
|
1184 an X server to display XEmacs on); see @ref{Q2.3.7}. TTY and Win32 GUI
|
|
2537
|
1185 require no additional libraries beyond what comes standard with Cygwin.
|
|
|
1186
|
|
|
1187 The advantages of the Cygwin version are that it integrates well with
|
|
|
1188 the Cygwin environment for existing Cygwin users; uses configure so
|
|
|
1189 building with different features is very easy; and actively supports X &
|
|
|
1190 TTY. Furthermore, the entire Cygwin environment and compiler are free,
|
|
|
1191 whereas Visual C++ costs money.
|
|
|
1192
|
|
|
1193 The disadvantage is that it requires the whole Cygwin environment,
|
|
|
1194 whereas the native port requires only a suitable MS Windows compiler.
|
|
|
1195 Also, it follows the Unix filesystem and process model very closely
|
|
|
1196 (some will undoubtedly view this as an advantage).
|
|
|
1197
|
|
|
1198 See @uref{http://www.cygwin.com/} for more information on
|
|
|
1199 Cygwin.
|
|
|
1200
|
|
|
1201 MinGW is a collection of header files and import libraries that allow
|
|
|
1202 one to use GCC under the Cygwin environment to compile and produce
|
|
|
1203 exactly the same native Win32 programs that you can using Visual C++.
|
|
|
1204 Programs compiled with MinGW make use of the standard Microsoft runtime
|
|
|
1205 library @file{MSVCRT.DLL}, present on all Windows systems, and look,
|
|
|
1206 feel, and act like a standard Visual-C-produced application. (The only
|
|
|
1207 difference is the compiler.) This means that, unlike a
|
|
|
1208 standardly-compiled Cygwin application, no extra runtime support
|
|
|
1209 (e.g. Cygwin's @file{cygwin1.dll}) is required. This, along with the
|
|
|
1210 fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y
|
|
|
1211 environment, for those die-hard Unix hackers out there), is the main
|
|
|
1212 advantage of MinGW. It is also potentially faster than Cygwin because
|
|
|
1213 it has less overhead when calling Windows, but you lose the POSIX
|
|
|
1214 emulation layer, which makes Unix programs harder to port. (But this is
|
|
|
1215 irrelevant for XEmacs since it's already ported to Win32.)
|
|
|
1216
|
|
|
1217 See @uref{http://www.mingw.org/} for more information on MinGW.
|
|
|
1218
|
|
|
1219 @node Q1.2.6, Q1.2.7, Q1.2.5, Introduction
|
|
|
1220 @unnumberedsubsec Q1.2.6: What are the differences between the various MS Windows emacsen?
|
|
|
1221
|
|
|
1222 XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing.
|
|
|
1223 Could you briefly explain the differences between them?
|
|
|
1224
|
|
|
1225 Here is a recount of various Emacs versions running on MS Windows:
|
|
|
1226
|
|
|
1227 @itemize @bullet
|
|
|
1228
|
|
|
1229 @item
|
|
|
1230 XEmacs
|
|
|
1231
|
|
|
1232 @itemize @minus
|
|
|
1233
|
|
|
1234 @item
|
|
|
1235 Beginning with XEmacs 19.12, XEmacs' architecture was redesigned
|
|
|
1236 in such a way to allow clean support of multiple window systems. At
|
|
|
1237 this time the TTY support was added, making X and TTY the first two
|
|
|
1238 "window systems" supported by XEmacs. The 19.12 design is the basis for
|
|
|
1239 the current native MS Windows code.
|
|
|
1240
|
|
|
1241 @item
|
|
|
1242 Some time during 1997, David Hobley (soon joined by Marc Paquette)
|
|
|
1243 imported some of the NT-specific portions of GNU Emacs, making XEmacs
|
|
|
1244 with X support compile under Windows NT, and creating the "X" port.
|
|
|
1245
|
|
|
1246 @item
|
|
|
1247 Several months later, Jonathan Harris sent out initial patches to use
|
|
|
1248 the Win32 API, thus creating the native port. Since then, various
|
|
|
1249 people have contributed, including Kirill M. Katsnelson (contributed
|
|
|
1250 support for menubars, subprocesses and network, as well as loads of
|
|
|
1251 other code), Andy Piper (ported XEmacs to Cygwin environment,
|
|
|
1252 contributed Windows unexec, Windows-specific glyphs and toolbars code,
|
|
|
1253 and more), Ben Wing (loads of improvements; primary MS Windows developer
|
|
|
1254 since 2000), Jeff Sparkes (contributed scrollbars support) and many
|
|
|
1255 others.
|
|
|
1256 @end itemize
|
|
|
1257
|
|
|
1258 @item
|
|
|
1259 NT Emacs
|
|
|
1260
|
|
|
1261 @itemize @minus
|
|
|
1262
|
|
|
1263 @item
|
|
|
1264 NT Emacs was an early version of GNU Emacs 19 modified to compile and
|
|
|
1265 run under MS Windows 95 and NT using the native Win32 API. It was
|
|
|
1266 written by Geoff Voelker, and has long since been incorporated into
|
|
|
1267 the mainline GNU Emacs distribution.
|
|
|
1268 @end itemize
|
|
|
1269
|
|
|
1270 @item
|
|
|
1271 Win-Emacs
|
|
|
1272
|
|
|
1273 @itemize @minus
|
|
|
1274
|
|
|
1275 @item
|
|
|
1276 Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X
|
|
|
1277 compatibility libraries. Win-Emacs was written by Ben Wing. The MS
|
|
|
1278 Windows code never made it back to Lucid Emacs, and its creator (Pearl
|
|
|
1279 Software) has long since gone out of business.
|
|
|
1280 @end itemize
|
|
|
1281
|
|
|
1282 @item
|
|
|
1283 GNU Emacs for DOS
|
|
|
1284
|
|
|
1285 @itemize @minus
|
|
|
1286
|
|
|
1287 @item
|
|
|
1288 GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
|
|
|
1289 port of GCC). Such an Emacs is heavily underfeatured, because it does
|
|
|
1290 not support long file names, lacks proper subprocesses support, and
|
|
|
1291 is far too big compared with typical DOS editors.
|
|
|
1292 @end itemize
|
|
|
1293
|
|
|
1294 @item
|
|
|
1295 GNU Emacs compiled with Win32
|
|
|
1296
|
|
|
1297 @itemize @minus
|
|
|
1298
|
|
|
1299 @item
|
|
|
1300 Starting with GNU Emacs 19.30, it has been possible to compile GNU Emacs
|
|
|
1301 under MS Windows using the DJGPP compiler and X libraries. The result
|
|
|
1302 is very similar to GNU Emacs compiled under MS DOS, only it works
|
|
|
1303 somewhat better because it runs in 32-bit mode, makes use of all the
|
|
|
1304 system memory, supports long file names, etc.
|
|
|
1305 @end itemize
|
|
|
1306
|
|
|
1307 @end itemize
|
|
|
1308
|
|
|
1309 @node Q1.2.7, Q1.2.8, Q1.2.6, Introduction
|
|
|
1310 @unnumberedsubsec Q1.2.7: How does the port cope with differences in the Windows user interface?
|
|
|
1311
|
|
|
1312 The XEmacs (and Emacs in general) user interface is pretty different
|
|
|
1313 from what is expected of a typical MS Windows program. How does the MS
|
|
|
1314 Windows port cope with it?
|
|
|
1315
|
|
|
1316 As a general rule, we follow native MS Windows conventions as much as
|
|
|
1317 possible. 21.4 is a fairly complete Windows application, supporting
|
|
|
1318 native printing, system file dialog boxes, tool tips, etc. In cases
|
|
|
1319 where there's a clear UI conflict, we currently use normal Unix XEmacs
|
|
|
1320 behavior by default, but make sure the MS Windows "look and feel" (mark
|
|
|
1321 via shift-arrow, self-inserting deletes region, Alt selects menu items,
|
|
|
1322 etc.) is easily configurable (respectively: using the variable
|
|
|
1323 @code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact
|
|
|
1324 the default in these versions], or the @file{pc-select} package; using
|
|
|
1325 the @file{pending-del} package; and setting the variable
|
|
|
1326 @code{menu-accelerator-enabled} to @code{menu-force} in 21.4 and above).
|
|
|
1327 In fact, if you use the sample @file{init.el} file as your init file,
|
|
|
1328 you will get all these behaviors automatically turned on.
|
|
|
1329
|
|
|
1330 In future versions, some of these features might be turned on by
|
|
|
1331 default in the MS Windows environment.
|
|
|
1332
|
|
|
1333 @node Q1.2.8, Q1.2.9, Q1.2.7, Introduction
|
|
|
1334 @unnumberedsubsec Q1.2.8: Is there a port of XEmacs to the Macintosh?
|
|
|
1335
|
|
|
1336 Yes.
|
|
|
1337
|
|
|
1338 XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly
|
|
|
1339 will not feel very much like a Mac application as it has no Mac-specific
|
|
|
1340 code in it.
|
|
|
1341
|
|
|
1342 There is also a port of XEmacs 19.14 that works on all recent versions
|
|
|
1343 of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com,
|
|
|
1344 Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY
|
|
|
1345 mode only (one single Macintosh window, 25 colors), but has a large
|
|
|
1346 number of Mac-specific additions. It's available at
|
|
|
1347 @uref{http://homepage.mac.com/pjarvis/xemacs.html}.
|
|
|
1348
|
|
|
1349 @node Q1.2.9, Q1.2.10, Q1.2.8, Introduction
|
|
2559
|
1350 @unnumberedsubsec Q1.2.9: Is there a port of XEmacs to MS-DOS?
|
|
|
1351
|
|
|
1352 No. We have never supported running on MS-DOS or Windows 3.1, and in
|
|
|
1353 fact have long since deleted all MS-DOS-related code. We're not
|
|
|
1354 particularly interested in patches for these platforms, as they would
|
|
|
1355 introduce huge amounts of code clutter due to the woefully
|
|
|
1356 underfeatured nature of these systems. (See GNU Emacs for a port to
|
|
|
1357 MS-DOS.)
|
|
2537
|
1358
|
|
|
1359 @node Q1.2.10, Q1.2.11, Q1.2.9, Introduction
|
|
2559
|
1360 @unnumberedsubsec Q1.2.10: Is there a port of XEmacs to OS/2?
|
|
2537
|
1361
|
|
|
1362 No, but Alexander Nikolaev <avn_1251@@mail.ru> was at one point
|
|
|
1363 working on it.
|
|
|
1364
|
|
2559
|
1365 @node Q1.2.11, Q1.2.12, Q1.2.10, Introduction
|
|
|
1366 @unnumberedsubsec Q1.2.11: Is there a port of XEmacs to NextStep?
|
|
2537
|
1367
|
|
|
1368 Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did
|
|
|
1369 the port of GNU Emacs to NeXTstep and expressed interest in doing the
|
|
|
1370 XEmacs port, but never went any farther.
|
|
|
1371
|
|
2559
|
1372 @node Q1.2.12, Q1.3.1, Q1.2.11, Introduction
|
|
|
1373 @unnumberedsubsec Q1.2.12: Is there a port of XEmacs to VMS?
|
|
2537
|
1374
|
|
|
1375 VMS has never been supported by XEmacs. In fact, all the old VMS code
|
|
|
1376 inherited from GNU Emacs has been removed. Sorry, all you VMS fans
|
|
|
1377 out there.
|
|
|
1378
|
|
|
1379 @unnumberedsec 1.3: Getting Started
|
|
|
1380
|
|
2559
|
1381 @node Q1.3.1, Q1.3.2, Q1.2.12, Introduction
|
|
2537
|
1382 @unnumberedsubsec Q1.3.1: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
|
1383
|
|
|
1384 The @file{init.el} or @file{.emacs} file is used to customize XEmacs to
|
|
|
1385 your tastes. Starting in 21.4, the preferred location for the init file
|
|
|
1386 is @file{~/.xemacs/init.el}; in previous versions, it was
|
|
|
1387 @file{~/.emacs}. 21.4 still accepts the old location, but the first
|
|
|
1388 time you run it, it will ask to migrate your file to the new location.
|
|
|
1389 If you answer yes, the file will be moved, and a "compatibility"
|
|
|
1390 @file{.emacs} file will be placed in the old location so that you can
|
|
|
1391 still run older versions of XEmacs, and versions of GNU Emacs, which
|
|
|
1392 expect the old location. The @file{.emacs} file present is just a stub
|
|
|
1393 that loads the real file in @file{~/.xemacs/init.el}.
|
|
|
1394
|
|
|
1395 No two init files are alike, nor are they expected to be alike, but
|
|
|
1396 that's the point. The XEmacs distribution contains an excellent starter
|
|
|
1397 example in the @file{etc/} directory called @file{sample.init.el}
|
|
|
1398 (starting in 21.4) or @file{sample.emacs} in older versions. Copy this
|
|
|
1399 file from there to @file{~/.xemacs/init.el} (starting in 21.4) or
|
|
|
1400 @file{~/.emacs} in older versions, where @samp{~} means your home
|
|
|
1401 directory, of course. Then edit it to suit.
|
|
|
1402
|
|
|
1403 You may bring the @file{sample.init.el} or @file{sample.emacs} file into
|
|
|
1404 an XEmacs buffer from the menubar. (The menu entry for it is always
|
|
|
1405 under the @samp{Help} menu, but its location under that has changed in
|
|
|
1406 various versions. Recently, look under the @samp{Samples} submenu.) To
|
|
|
1407 determine the location of the @file{etc/} directory type the command
|
|
|
1408 @kbd{C-h v data-directory @key{RET}}.
|
|
|
1409
|
|
|
1410 @node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
|
|
|
1411 @unnumberedsubsec Q1.3.2: Where do I put my @file{init.el} file?
|
|
|
1412
|
|
|
1413 @file{init.el} is the name of the init file starting with 21.4, and is
|
|
|
1414 located in the subdirectory @file{.xemacs/} of your home directory. In
|
|
|
1415 prior versions, the init file is called @file{.emacs} and is located in
|
|
|
1416 your home directory.
|
|
|
1417
|
|
|
1418 Your home directory under Windows is determined by the @samp{HOME}
|
|
|
1419 environment variable. If this is not set, it defaults to @samp{C:\}.
|
|
|
1420 To set this variable, modify @file{AUTOEXEC.BAT} under Windows 95/98, or
|
|
|
1421 select @samp{Control Panel->System->Advanced->Environment Variables...}
|
|
|
1422 under Windows NT/2000.
|
|
|
1423
|
|
|
1424 @node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
|
|
|
1425 @unnumberedsubsec Q1.3.3: Can I use the same @file{init.el} with the other Emacs?
|
|
|
1426
|
|
|
1427 Yes. The sample @file{init.el} included in the XEmacs
|
|
|
1428 distribution will show you how to handle different versions and flavors
|
|
|
1429 of Emacs.
|
|
|
1430
|
|
|
1431 @node Q1.3.4, Q1.3.5, Q1.3.3, Introduction
|
|
|
1432 @unnumberedsubsec Q1.3.4: Any good XEmacs tutorials around?
|
|
|
1433
|
|
|
1434 There's the XEmacs tutorial available from the Help Menu under
|
|
|
1435 @samp{Help->Tutorials}, or by typing @kbd{C-h t}. To check whether
|
|
|
1436 it's available in a non-english language, type @kbd{C-u C-h t TAB}, type
|
|
|
1437 the first letters of your preferred language, then type @key{RET}.
|
|
|
1438
|
|
|
1439 @comment There's an Emacs Lisp tutorial at
|
|
|
1440 @comment
|
|
|
1441 @comment @example
|
|
|
1442 @comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
|
|
|
1443 @comment @end example
|
|
|
1444 @comment
|
|
|
1445 @comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
|
|
|
1446 @comment page at
|
|
|
1447 @comment @iftex
|
|
|
1448 @comment @*
|
|
|
1449 @comment @end iftex
|
|
|
1450 @comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}.
|
|
|
1451
|
|
|
1452 @node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
|
|
|
1453 @unnumberedsubsec Q1.3.5: May I see an example of a useful XEmacs Lisp function?
|
|
|
1454
|
|
|
1455 The following function does a little bit of everything useful. It does
|
|
|
1456 something with the prefix argument, it examines the text around the
|
|
|
1457 cursor, and it's interactive so it may be bound to a key. It inserts
|
|
|
1458 copies of the current word the cursor is sitting on at the cursor. If
|
|
|
1459 you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will
|
|
|
1460 insert 3 copies.
|
|
|
1461
|
|
|
1462 @lisp
|
|
|
1463 (defun double-word (count)
|
|
|
1464 "Insert a copy of the current word underneath the cursor"
|
|
|
1465 (interactive "*p")
|
|
|
1466 (let (here there string)
|
|
|
1467 (save-excursion
|
|
|
1468 (forward-word -1)
|
|
|
1469 (setq here (point))
|
|
|
1470 (forward-word 1)
|
|
|
1471 (setq there (point))
|
|
|
1472 (setq string (buffer-substring here there)))
|
|
|
1473 (while (>= count 1)
|
|
|
1474 (insert string)
|
|
|
1475 (decf count))))
|
|
|
1476 @end lisp
|
|
|
1477
|
|
|
1478 The best way to see what is going on here is to let XEmacs tell you.
|
|
|
1479 Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor
|
|
|
1480 sitting just to the right of the function you want explained. Eg. move
|
|
|
1481 the cursor to the SPACE between @code{interactive} and @samp{"*p"} and
|
|
|
1482 hit @kbd{C-h f} to see what the function @code{interactive} does. Doing
|
|
|
1483 this will tell you that the @code{*} requires a writable buffer, and
|
|
|
1484 @code{p} converts the prefix argument to a number, and
|
|
|
1485 @code{interactive} allows you to execute the command with @kbd{M-x}.
|
|
|
1486
|
|
|
1487 @node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
|
|
|
1488 @unnumberedsubsec Q1.3.6: And how do I bind it to a key?
|
|
|
1489
|
|
|
1490 To bind to a key do:
|
|
|
1491
|
|
|
1492 @lisp
|
|
|
1493 (global-set-key "\C-cd" 'double-word)
|
|
|
1494 @end lisp
|
|
|
1495
|
|
|
1496 Or interactively, @kbd{M-x global-set-key} and follow the prompts.
|
|
|
1497
|
|
|
1498 @node Q1.3.7, Q1.3.8, Q1.3.6, Introduction
|
|
|
1499 @unnumberedsubsec Q1.3.7: What's the difference between a macro and a function?
|
|
|
1500
|
|
|
1501 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual:
|
|
|
1502
|
|
|
1503 @dfn{Macros} enable you to define new control constructs and other
|
|
|
1504 language features. A macro is defined much like a function, but instead
|
|
|
1505 of telling how to compute a value, it tells how to compute another Lisp
|
|
|
1506 expression which will in turn compute the value. We call this
|
|
|
1507 expression the @dfn{expansion} of the macro.
|
|
|
1508
|
|
|
1509 Macros can do this because they operate on the unevaluated expressions
|
|
|
1510 for the arguments, not on the argument values as functions do. They can
|
|
|
1511 therefore construct an expansion containing these argument expressions
|
|
|
1512 or parts of them.
|
|
|
1513
|
|
|
1514 Do not confuse the two terms with @dfn{keyboard macros}, which are
|
|
|
1515 another matter, entirely. A keyboard macro is a key bound to several
|
|
|
1516 other keys. Refer to manual for details.
|
|
|
1517
|
|
|
1518 @node Q1.3.8, Q1.4.1, Q1.3.7, Introduction
|
|
|
1519 @unnumberedsubsec Q1.3.8: What is @code{Custom}?
|
|
|
1520
|
|
|
1521 @code{Custom} is a system for customizing XEmacs options.
|
|
|
1522
|
|
|
1523 You can access @code{Advanced (Customize)} from the @code{Options} menu
|
|
|
1524 or invoking one of customize commands by typing eg.
|
|
|
1525 @kbd{M-x customize}, @kbd{M-x customize-face},
|
|
|
1526 @kbd{M-x customize-variable} or @kbd{M-x customize-apropos}.
|
|
|
1527
|
|
|
1528 There is also new @samp{browser} mode for Customize.
|
|
|
1529 Try it out with @kbd{M-x customize-browse}
|
|
|
1530
|
|
|
1531 @unnumberedsec 1.4: Getting Help
|
|
|
1532
|
|
|
1533 @node Q1.4.1, Q1.4.2, Q1.3.8, Introduction
|
|
|
1534 @unnumberedsubsec Q1.4.1: Where can I get help?
|
|
|
1535
|
|
|
1536 Probably the easiest way, if everything is installed, is to use Info, by
|
|
|
1537 pressing @kbd{C-h i}, or looking for an Info item on the
|
|
|
1538 Help Menu. @kbd{M-x apropos} can be used to look for particular commands.
|
|
|
1539
|
|
|
1540 For items not found in the manual, try reading this FAQ
|
|
|
1541 and reading the Usenet group comp.emacs.xemacs.
|
|
|
1542
|
|
|
1543 If you choose to post to a newsgroup, @strong{please use
|
|
|
1544 comp.emacs.xemacs}. Please do not post XEmacs related questions to
|
|
|
1545 gnu.emacs.help.
|
|
|
1546
|
|
|
1547 If you cannot post or read Usenet news, there is a corresponding mailing
|
|
|
1548 list @email{xemacs-news@@xemacs.org} which is available. It can be
|
|
|
1549 subscribed to via the Mailman Web interface or by sending mail to to
|
|
|
1550 @email{xemacs-news-request@@xemacs.org} with @samp{subscribe} in the
|
|
|
1551 body of the message. See also
|
|
|
1552 @uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a
|
|
|
1553 subscription, you may use the @email{xemacs-news-request@@xemacs.org}
|
|
|
1554 address or the Web interface. Send a message with a subject of
|
|
|
1555 @samp{unsubscribe} to be removed.
|
|
|
1556
|
|
|
1557 @node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
|
|
|
1558 @unnumberedsubsec Q1.4.2: Which mailing lists are there?
|
|
|
1559
|
|
|
1560 For complete, up-to-date info on the lists and how to subscribe, see
|
|
|
1561 @uref{http://www.xemacs.org/Lists/}.
|
|
|
1562
|
|
|
1563 @table @samp
|
|
|
1564
|
|
|
1565 @item comp.emacs.xemacs
|
|
|
1566 is a Usenet newsgroup
|
|
|
1567 for XEmacs users to discuss problems and issues that arise
|
|
|
1568 for them. It's not generally an appropriate place to ask
|
|
|
1569 about apparent bugs (use @samp{xemacs-beta}), or future plans
|
|
|
1570 (use @samp{xemacs-design}).
|
|
|
1571
|
|
|
1572 @item xemacs-announce
|
|
|
1573 is a read-only, low
|
|
|
1574 volume list for announcements concerning the XEmacs project
|
|
|
1575 and new releases of the XEmacs software.
|
|
|
1576
|
|
|
1577 @item xemacs-beta
|
|
2559
|
1578 is an open list for bug reports about beta versions of XEmacs. This
|
|
|
1579 includes the bug reports themselves, by both users and developers, as
|
|
|
1580 well as queries, follow-ups, and discussions further determining their
|
|
|
1581 nature and status. This is the primary channel for this kind of
|
|
|
1582 discussion; related code changes will usually not be applied until
|
|
|
1583 they have been discussed here. When such discussions touch on
|
|
|
1584 significant changes to the code (in particular, structural changes),
|
|
|
1585 or on changes to API's or external functionality, they should be moved
|
|
|
1586 to @samp{xemacs-design}. Requests and proposals for non-bug-related
|
|
|
1587 changes do not belong on @samp{xemacs-beta}, and should be sent to
|
|
|
1588 @samp{xemacs-design} instead.
|
|
2537
|
1589
|
|
|
1590 @item xemacs-beta-ja
|
|
|
1591 is an open list for bug
|
|
|
1592 reports and design discussion related to Mule features,
|
|
|
1593 including Japanese handling, in beta versions of XEmacs.
|
|
|
1594 Japanese is the preferred language of discussion. For most
|
|
|
1595 timely presentation to reviewers, please consider sending
|
|
|
1596 appropriate discussion to @samp{xemacs-mule} or
|
|
|
1597 @samp{xemacs-design} in English when convenient for
|
|
|
1598 the participants in discussion. When possible, bug reports
|
|
|
1599 not related to Mule (including Japanese) should be reported on
|
|
|
1600 @samp{xemacs-beta} in English.
|
|
|
1601
|
|
|
1602 @item xemacs-buildreports
|
|
|
1603 is an open list for
|
|
|
1604 submission of build-reports on beta versions of XEmacs. For
|
|
|
1605 information on what the build-reports should contain, please
|
|
|
1606 see the `etc/BETA' file which is included in each beta
|
|
|
1607 distribution.
|
|
|
1608
|
|
|
1609 @item xemacs-cvs
|
|
|
1610 is a read-only list for notices
|
|
|
1611 and information on what has been committed to the XEmacs CVS
|
|
|
1612 trees, by whom, and for what.
|
|
|
1613
|
|
|
1614 @item xemacs-design
|
|
|
1615 is an open list for
|
|
|
1616 discussing the design of XEmacs. This includes discussion
|
|
|
1617 about planned and ongoing changes to functionality and API
|
|
|
1618 changes and additions as well as requests for them. This is
|
|
|
1619 the primary channel for this kind of discussion; related code
|
|
|
1620 changes will usually not be applied until they have been
|
|
|
1621 discussed here. This does not include bug reports, which go
|
|
|
1622 to @samp{xemacs-beta}.
|
|
|
1623
|
|
|
1624 @item xemacs-mule
|
|
|
1625 is an open mailing list for
|
|
|
1626 discussion of International extensions to XEmacs including
|
|
|
1627 Mule, XIM, I18n issues, etc, and is not confined to
|
|
|
1628 developmental issues. This list is not restricted to
|
|
|
1629 English, postings in all languages are welcome.
|
|
|
1630
|
|
|
1631 @item xemacs-news
|
|
|
1632 is an open list for discussion
|
|
|
1633 and bug reporting for XEmacs. This mailing list is
|
|
|
1634 bi-directionally gatewayed with the USENET newsgroup
|
|
|
1635 comp.emacs.xemacs.
|
|
|
1636
|
|
|
1637 @item xemacs-nt
|
|
|
1638 is a developers-only mailing
|
|
|
1639 list and is intended for people who wish to work actively on
|
|
|
1640 the porting of XEmacs to Microsoft Windows NT and Microsoft
|
|
|
1641 Windows '95.
|
|
|
1642
|
|
|
1643 @item xemacs-patches
|
|
|
1644 is an open, moderated
|
|
|
1645 list for submission of patches to the XEmacs distribution
|
|
|
1646 and its packages. Anyone may subscribe or submit to
|
|
|
1647 xemacs-patches, but all submissions are reviewed by the list
|
|
|
1648 moderator before they are distributed to the
|
|
|
1649 list. Discussion is not appropriate on xemacs-patches.
|
|
|
1650
|
|
|
1651 @item xemacs-users-ja
|
|
|
1652 is an open list for
|
|
|
1653 discussion and bug reporting for XEmacs. Japanese is the
|
|
|
1654 preferred language of discussion. It is not gated to
|
|
|
1655 comp.emacs.xemacs or the @samp{xemacs} list. For
|
|
|
1656 fastest response, bugs not specifically related to Japanese
|
|
|
1657 or Mule features should be reported on
|
|
|
1658 @samp{xemacs-beta} (in English).
|
|
|
1659
|
|
|
1660 @item xemacs-users-ru
|
|
|
1661 is an open list for
|
|
|
1662 discussion and bug reporting for XEmacs. Russian is the
|
|
|
1663 preferred language of discussion. It is not gated to
|
|
|
1664 comp.emacs.xemacs or the @samp{xemacs} list. For
|
|
|
1665 fastest response, bugs not specifically related to Russian
|
|
|
1666 or Mule features should be reported on
|
|
|
1667 @samp{xemacs-beta} (in English).
|
|
|
1668 @end table
|
|
|
1669
|
|
|
1670 @node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
|
|
|
1671 @unnumberedsubsec Q1.4.3: Where are the mailing lists archived?
|
|
|
1672
|
|
|
1673 The archives can be found at @uref{http://list-archive.xemacs.org}
|
|
|
1674
|
|
|
1675 @node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
|
|
|
1676 @unnumberedsubsec Q1.4.4: How can I get two instances of info?
|
|
|
1677
|
|
|
1678 Before 21.4, you can't. The @code{info} package does not provide for
|
|
|
1679 multiple info buffers. In 21.4, this should be fixed. #### how?
|
|
|
1680
|
|
|
1681 @node Q1.4.5, Q1.5.1, Q1.4.4, Introduction
|
|
|
1682 @unnumberedsubsec Q1.4.5: How do I add new Info directories?
|
|
|
1683
|
|
|
1684 You use something like:
|
|
|
1685
|
|
|
1686 @lisp
|
|
|
1687 (setq Info-directory-list (cons
|
|
|
1688 (expand-file-name "~/info")
|
|
|
1689 Info-default-directory-list))
|
|
|
1690 @end lisp
|
|
|
1691
|
|
|
1692 @email{davidm@@prism.kla.com, David Masterson} writes:
|
|
|
1693
|
|
|
1694 @quotation
|
|
|
1695 Emacs Info and XEmacs Info do many things differently. If you're trying to
|
|
|
1696 support a number of versions of Emacs, here are some notes to remember:
|
|
|
1697
|
|
|
1698 @enumerate
|
|
|
1699 @item
|
|
|
1700 Emacs Info scans @code{Info-directory-list} from right-to-left while
|
|
|
1701 XEmacs Info reads it from left-to-right, so append to the @emph{correct}
|
|
|
1702 end of the list.
|
|
|
1703
|
|
|
1704 @item
|
|
|
1705 Use @code{Info-default-directory-list} to initialize
|
|
|
1706 @code{Info-directory-list} @emph{if} it is available at startup, but not
|
|
|
1707 all Emacsen define it.
|
|
|
1708
|
|
|
1709 @item
|
|
|
1710 Emacs Info looks for a standard @file{dir} file in each of the
|
|
|
1711 directories scanned from #1 and magically concatenates them together.
|
|
|
1712
|
|
|
1713 @item
|
|
|
1714 XEmacs Info looks for a @file{localdir} file (which consists of just the
|
|
|
1715 menu entries from a @file{dir} file) in each of the directories scanned
|
|
|
1716 from #1 (except the first), does a simple concatenation of them, and
|
|
|
1717 magically attaches the resulting list to the end of the menu in the
|
|
|
1718 @file{dir} file in the first directory.
|
|
|
1719 @end enumerate
|
|
|
1720
|
|
|
1721 Another alternative is to convert the documentation to HTML with
|
|
|
1722 texi2html and read it from a web browser like Lynx or W3.
|
|
|
1723 @end quotation
|
|
|
1724
|
|
|
1725 @unnumberedsec 1.5: Contributing to XEmacs
|
|
|
1726
|
|
|
1727 @node Q1.5.1, Q1.5.2, Q1.4.5, Introduction
|
|
|
1728 @unnumberedsubsec Q1.5.1: How do I submit changes to the FAQ?
|
|
|
1729
|
|
|
1730 The FAQ is actively maintained and modified regularly. All links should
|
|
|
1731 be up to date. Unfortunately, some of the information is out of date --
|
|
|
1732 a situation which the FAQ maintainer is working on. All submissions are
|
|
|
1733 welcome, please e-mail submissions to @email{faq@@xemacs.org, XEmacs FAQ
|
|
|
1734 maintainers}.
|
|
|
1735
|
|
|
1736 Please make sure that @samp{XEmacs FAQ} appears on the Subject: line.
|
|
|
1737 If you think you have a better way of answering a question, or think a
|
|
|
1738 question should be included, we'd like to hear about it. Questions and
|
|
|
1739 answers included into the FAQ will be edited for spelling and grammar
|
|
|
1740 and will be attributed. Answers appearing without attribution are
|
|
|
1741 either from versions of the FAQ dated before May 1996 or are from
|
|
|
1742 previous FAQ maintainers. Answers quoted from Usenet news articles will
|
|
|
1743 always be attributed, regardless of the author.
|
|
|
1744
|
|
|
1745 @node Q1.5.2, Q1.5.3, Q1.5.1, Introduction
|
|
|
1746 @unnumberedsubsec Q1.5.2: How do I become a beta tester?
|
|
|
1747
|
|
|
1748 Send an email message to @email{xemacs-beta-request@@xemacs.org} with
|
|
|
1749 the line @samp{subscribe} in the body of the message.
|
|
|
1750
|
|
|
1751 Be prepared to get your hands dirty, as beta testers are expected to
|
|
|
1752 identify problems as best they can.
|
|
|
1753
|
|
2559
|
1754 @node Q1.5.3, Q1.5.4, Q1.5.2, Introduction
|
|
2537
|
1755 @unnumberedsubsec Q1.5.3: How do I contribute to XEmacs itself?
|
|
|
1756
|
|
|
1757 It depends on the knowledge and time you possess. If you are able, by
|
|
|
1758 all means become a beta tester (@pxref{Q1.5.2}). If you are a
|
|
|
1759 programmer, try to build XEmacs and see if you can improve it.
|
|
|
1760
|
|
|
1761 Otherwise, you can still help by using XEmacs as your everyday editor
|
|
|
1762 (for pre-built binary versions, @pxref{Q1.1.2}) and reporting bugs you
|
|
|
1763 find to the mailing list.
|
|
|
1764
|
|
|
1765 Another area where we need help is the documentation: We need good
|
|
|
1766 documentation for building XEmacs and for using it. This FAQ is a
|
|
|
1767 small step in that direction.
|
|
|
1768
|
|
|
1769 Ben Wing @email{ben@@xemacs.org} writes:
|
|
|
1770
|
|
|
1771 @quotation
|
|
|
1772 BTW if you have a wish list of things that you want added, you have to
|
|
|
1773 speak up about it! More specifically, you can do the following if you
|
|
|
1774 want a feature added (in increasing order of usefulness):
|
|
|
1775
|
|
|
1776 @itemize @bullet
|
|
|
1777 @item
|
|
|
1778 Make a posting about a feature you want added.
|
|
|
1779
|
|
|
1780 @item
|
|
|
1781 Become a beta tester and make more postings about those same features.
|
|
|
1782
|
|
|
1783 @item
|
|
|
1784 Convince us that you're going to use the features in some cool and
|
|
|
1785 useful way.
|
|
|
1786
|
|
|
1787 @item
|
|
|
1788 Come up with a clear and well-thought-out API concerning the features.
|
|
|
1789
|
|
|
1790 @item
|
|
|
1791 Write the code to implement a feature and send us a patch.
|
|
|
1792 @end itemize
|
|
|
1793
|
|
|
1794 (not that we're necessarily requiring you to write the code, but we can
|
|
|
1795 always hope :)
|
|
|
1796 @end quotation
|
|
|
1797
|
|
2559
|
1798 @node Q1.5.4, Q1.5.5, Q1.5.3, Introduction
|
|
|
1799 @unnumberedsubsec Q1.5.4: How do I get started developing XEmacs?
|
|
|
1800
|
|
|
1801 First, get yourself set up under CVS so that you can access the CVS
|
|
|
1802 repositories containing the XEmacs sources and the XEmacs packages.
|
|
|
1803
|
|
|
1804 Next, set up your layout. This is important, as a good layout will
|
|
|
1805 facilitate getting things done efficiently, while a bad layout will could
|
|
|
1806 lead to disaster, as you can't figure out which code is the most recent,
|
|
|
1807 which can be thrown away, etc. We suggest the following layout: (feel free
|
|
|
1808 to make changes)
|
|
|
1809
|
|
|
1810 @itemize @bullet
|
|
|
1811 @item
|
|
|
1812 Everything goes under @file{/src/xemacs} (use a different directory if
|
|
|
1813 you want). From now, instead of saying @file{/src/xemacs}, we use
|
|
|
1814 @file{<xsrc-top>}, to make it easier in case someone picked a
|
|
|
1815 different directory.
|
|
|
1816
|
|
|
1817 @item
|
|
|
1818 Package source is in @file{<xsrc-top>/package-src}.
|
|
|
1819
|
|
|
1820 @item
|
|
|
1821 Installed packages go under @file{<xsrc-top>/xemacs-packages}, and
|
|
|
1822 @file{<xsrc-top>/mule-packages}.
|
|
|
1823
|
|
|
1824 @item
|
|
|
1825 A "workspace" is a complete copy of the sources, in which you do work of
|
|
|
1826 a particular kind. Workspaces can be differentiated by which branch of
|
|
|
1827 the source tree they extend off of -- usually either the stable or
|
|
|
1828 experimental, unless other branches have been created (for example, Ben
|
|
|
1829 created a branch for his Mule work because (1) the project was long-term
|
|
|
1830 and involved an enormous number of changes, (2) people wanted to be able
|
|
|
1831 to look at what his work in progress, and (3) he wanted to be able to
|
|
|
1832 check things in and in general use source-code control, since it was a
|
|
|
1833 long-term project). Workspaces are also differentiated in what their
|
|
|
1834 purpose is -- general working workspace, workspace for particular
|
|
|
1835 projects, workspace keeping the latest copy of the code in one of the
|
|
|
1836 branches without mods, etc.
|
|
|
1837
|
|
|
1838 @item
|
|
|
1839 Various workspaces are subdirectories under @file{<xsrc-top>}, e.g.:
|
|
|
1840
|
|
|
1841 @itemize @bullet
|
|
|
1842 @item
|
|
|
1843 @file{<xsrc-top>/working} (the workspace you're actively working on,
|
|
|
1844 periodically synched up with the latest trunk)
|
|
|
1845
|
|
|
1846 @item
|
|
|
1847 @file{<xsrc-top>/stable} (for making changes to the stable version of
|
|
|
1848 XEmacs, which sits on a branch)
|
|
|
1849
|
|
|
1850 @item
|
|
|
1851 @file{<xsrc-top>/unsigned-removal} (a workspace for a specific, difficult
|
|
|
1852 task that's going to affect lots of source and take a long time, and
|
|
|
1853 so best done in its own workspace without the interference of other
|
|
|
1854 work you're doing. Also, you can commit just this one large change,
|
|
|
1855 separate from all the other changes).
|
|
|
1856
|
|
|
1857 @item
|
|
|
1858 @file{<xsrc-top>/latest} (a copy of the latest sources on the trunk,
|
|
|
1859 i.e. the experimental version of XEmacs, with no patches in it;
|
|
|
1860 either update it periodically, by hand, or set up a cron job to do it
|
|
|
1861 automatically). Set it up so it can be built, and build it so you
|
|
|
1862 have a working XEmacs. (Building it might also go into the cron job.)
|
|
|
1863
|
|
|
1864 This workspace serves a number of purposes:
|
|
|
1865 @enumerate
|
|
|
1866 @item
|
|
|
1867 You always have a recent version of XEmacs you can compare
|
|
|
1868 against when something you're working on breaks. It's true
|
|
|
1869 that you can do this with cvs diff, but when you need to do
|
|
|
1870 some serious investigation, this method just fails.
|
|
|
1871 @item
|
|
|
1872 You (almost) always have a working, up-to-date executable that
|
|
|
1873 can be used when your executable is crashing and you need to
|
|
|
1874 keep developing it, or when you need an `xemacs' to build
|
|
|
1875 packages, etc.
|
|
|
1876 @item
|
|
|
1877 When creating new workspaces, you can just copy the `latest'
|
|
|
1878 workspace using GNU @code{cp -a}. You have all the .elc's built,
|
|
|
1879 everything else probably configured, any spare files in place
|
|
|
1880 (e.g. some annoying xpm.dll under Windows, etc.).
|
|
|
1881 @end enumerate
|
|
|
1882
|
|
|
1883 @item
|
|
|
1884 @file{<xsrc-top>/latest-stable/} (equivalent to @file{<xsrc-top>/latest/}, but
|
|
|
1885 for the Stable branch of XEmacs, rather than the Experimental branch
|
|
|
1886 of XEmacs). This may or may not be necessary depending on how much
|
|
|
1887 development you do of the stable branch.
|
|
|
1888 @end itemize
|
|
|
1889
|
|
|
1890 @item
|
|
|
1891 @file{<xsrc-top>/xemacsweb} is a workspace for working on the XEmacs
|
|
|
1892 web site.
|
|
|
1893
|
|
|
1894 @item
|
|
|
1895 @file{<xsrc-top>/in-patches} for patches received from email and saved
|
|
|
1896 to files.
|
|
|
1897
|
|
|
1898 @item
|
|
|
1899 @file{<xsrc-top>/out-patches} for locally-generated patches to be sent
|
|
|
1900 to @email{xemacs-patches@@xemacs.org}. Less useful now that the
|
|
|
1901 patcher util has been developed.
|
|
|
1902
|
|
|
1903 @item
|
|
|
1904 @file{<xsrc-top>/build}, for build trees when compiling and testing XEmacs with
|
|
|
1905 various configuration options turned off and on. The scripts in
|
|
|
1906 xemacs-builds/ben (see below) can be used to automate building XEmacs
|
|
|
1907 workspaces with many different configuration options and automatically
|
|
|
1908 filtering out the normal output so that you see only the abnormal
|
|
|
1909 output.
|
|
|
1910
|
|
|
1911 @item
|
|
|
1912 @file{<xsrc-top>/xemacs-builds}, for the xemacs-builds module, which you need
|
|
|
1913 to check out separately in CVS. This contains scripts used for building
|
|
|
1914 XEmacs, automating and simplifying using CVS, etc. Under various
|
|
|
1915 people's directories are their own build and other scripts. The
|
|
|
1916 currently most-maintained scripts are under ben/, where there are easily
|
|
|
1917 configurable scripts that can be used to easily build any workspace
|
|
|
1918 (esp. if you've more or less followed the layout presented above)
|
|
|
1919 unattended, with one or more configuration states (there's a
|
|
|
1920 pre-determined list of the most useful, but it's easy to change). The
|
|
|
1921 output is filtered and split up in various ways so that you can identify
|
|
|
1922 which output came from where, and you can see the output either full or
|
|
|
1923 with all "normal" output except occasional status messages filtered so
|
|
|
1924 that you only see the abnormal ones.
|
|
|
1925 @end itemize
|
|
|
1926
|
|
|
1927 @node Q1.5.5, Q1.6.1, Q1.5.4, Introduction
|
|
|
1928 @unnumberedsubsec Q1.5.5: What's the basic layout of the code?
|
|
|
1929
|
|
|
1930 The file @file{configure} is a shell script to acclimate XEmacs to the
|
|
|
1931 oddities of your processor and operating system. It will create a
|
|
|
1932 file named @file{Makefile} (a script for the @file{make} program), which helps
|
|
|
1933 automate the process of building and installing emacs. See INSTALL
|
|
|
1934 for more detailed information.
|
|
|
1935
|
|
|
1936 The file @file{configure.in} is the input used by the autoconf program to
|
|
|
1937 construct the @file{configure} script. Since XEmacs has configuration
|
|
|
1938 requirements that autoconf can't meet, @file{configure.in} uses an unholy
|
|
|
1939 marriage of custom-baked configuration code and autoconf macros; it
|
|
|
1940 may be wise to avoid rebuilding @file{configure} from @file{configure.in} when
|
|
|
1941 possible.
|
|
|
1942
|
|
|
1943 The file @file{Makefile.in} is a template used by @file{configure} to create
|
|
|
1944 @file{Makefile}.
|
|
|
1945
|
|
|
1946 There are several subdirectories:
|
|
|
1947
|
|
|
1948 @enumerate
|
|
|
1949 @item
|
|
|
1950 @file{src} holds the C code for XEmacs (the XEmacs Lisp interpreter and its
|
|
|
1951 primitives, the redisplay code, and some basic editing functions).
|
|
|
1952 @item
|
|
|
1953 @file{lisp} holds the XEmacs Lisp code for XEmacs (most everything else).
|
|
|
1954 @item
|
|
|
1955 @file{lib-src} holds the source code for some utility programs for use by
|
|
|
1956 or with XEmacs, like movemail and etags.
|
|
|
1957 @item
|
|
|
1958 @file{etc} holds miscellaneous architecture-independent data files
|
|
|
1959 XEmacs uses, like the tutorial text. The contents of the @file{lisp},
|
|
|
1960 @file{info} and @file{man} subdirectories are architecture-independent too.
|
|
|
1961 @item
|
|
|
1962 @file{lwlib} holds the C code for the X toolkit objects used by XEmacs.
|
|
|
1963 @item
|
|
|
1964 @file{info} holds the Info documentation tree for XEmacs.
|
|
|
1965 @item
|
|
|
1966 @file{man} holds the source code for the XEmacs online documentation.
|
|
|
1967 @item
|
|
|
1968 @file{nt} holds files used compiling XEmacs under Microsoft Windows.
|
|
|
1969 @end enumerate
|
|
|
1970
|
|
2537
|
1971 @unnumberedsec 1.6: Politics (XEmacs vs. GNU Emacs)
|
|
|
1972
|
|
2559
|
1973 @node Q1.6.1, Q1.6.2, Q1.5.5, Introduction
|
|
2537
|
1974 @unnumberedsubsec Q1.6.1: What is GNU Emacs?
|
|
|
1975
|
|
|
1976 GNU Emacs and XEmacs are related open-source text editors. Both
|
|
|
1977 derive from GNU Emacs version 18; the split between the two happened
|
|
|
1978 in 1991 (for comparison, the oldest versions of GNU Emacs date from
|
|
|
1979 1984). For information on GNU Emacs, see
|
|
|
1980 @uref{http://www.gnu.org/software/emacs/emacs.html}.
|
|
|
1981
|
|
|
1982 @node Q1.6.2, Q1.6.3, Q1.6.1, Introduction
|
|
|
1983 @unnumberedsubsec Q1.6.2: How does XEmacs differ from GNU Emacs?
|
|
428
|
1984
|
|
|
1985 For a detailed description of the differences between GNU Emacs and
|
|
|
1986 XEmacs and a detailed history of XEmacs, check out the
|
|
|
1987 @example
|
|
430
|
1988 @uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file}
|
|
428
|
1989 @end example
|
|
|
1990
|
|
2417
|
1991 @table @strong
|
|
|
1992 @item User-Visible Editing Features
|
|
|
1993 XEmacs in general tries hard to conform to exist user-interface
|
|
|
1994 standards, and to work "out-of-the-box" without the need for obscure
|
|
|
1995 customization changes. GNU Emacs, particularly version 21, has gotten
|
|
|
1996 better about this (in many cases by copying the XEmacs behavior!), but
|
|
|
1997 still has some weirdnesses. For example, the standard method of
|
|
|
1998 selecting text using the Shift key works out-of-the-box in XEmacs.
|
|
|
1999
|
|
|
2000 XEmacs has a built-in toolbar. Four toolbars can actually be configured
|
|
|
2001 simultaneously: top, bottom, left, and right toolbars.
|
|
|
2002
|
|
|
2003 XEmacs has vertical and horizontal scrollbars. Unlike in GNU Emacs 19
|
|
|
2004 (which provides a primitive form of vertical scrollbar), these are true
|
|
|
2005 toolkit scrollbars. A look-alike Motif scrollbar is provided for those
|
|
|
2006 who don't have Motif. (Even for those who do, the look-alike may be
|
|
|
2007 preferable as it is faster.)
|
|
|
2008
|
|
|
2009 XEmacs has buffer tabs along the top of the frame (although the
|
|
|
2010 position can be changed) that make it very easy to switch buffers.
|
|
|
2011
|
|
|
2012 The menubar under XEmacs is better-designed, with more thought put into
|
|
|
2013 it.
|
|
|
2014
|
|
|
2015 XEmacs can ask questions using popup dialog boxes. Any command executed
|
|
|
2016 from a menu will ask yes/no questions with dialog boxes, while commands
|
|
|
2017 executed via the keyboard will use the minibuffer.
|
|
|
2018
|
|
|
2019 XEmacs under MS Windows provides uses the standard file-dialog box for
|
|
|
2020 opening and saving files. Standard menu-accelerator behavior can easily
|
|
|
2021 be enabled using the Options menu, and integrates well into the existing
|
|
|
2022 keymap.
|
|
|
2023
|
|
|
2024 XEmacs has (still experimental) support for widgets of various sorts --
|
|
|
2025 buttons, text boxes, sliders, progress bars, etc. A progress bar is
|
|
|
2026 used in font lock to show the progress.
|
|
|
2027
|
|
|
2028 Experimental support for drag-and-drop protocols is provided from
|
|
|
2029 XEmacs 21.
|
|
|
2030
|
|
|
2031 @item General Platform Support
|
|
|
2032 If you're running on a machine with audio hardware, you can specify
|
|
|
2033 sound files for XEmacs to play instead of the default X beep. See the
|
|
|
2034 documentation of the function load-sound-file and the variable
|
|
|
2035 sound-alist. XEmacs also supports the network sound protocols NAS and
|
|
|
2036 EsounD.
|
|
|
2037
|
|
|
2038 XEmacs 21 supports database protocols with LISP bindings, currently
|
|
|
2039 including Berkeley DB, LDAP, and PostgreSQL (21.2 only).
|
|
|
2040
|
|
|
2041 XEmacs 20 and 21 support the Canna, Wnn, and SJ3 Japanese input method
|
|
|
2042 servers directly, as well as through the X Input Method (XIM)
|
|
|
2043 protocol. GNU Emacs 20 supports only the XIM protocol. Both Emacsen
|
|
|
2044 support the Quail family of input methods (implemented in LISP) for many
|
|
|
2045 languages.
|
|
|
2046
|
|
|
2047 XEmacs provides support for ToolTalk on systems that have
|
|
|
2048 it.
|
|
|
2049
|
|
|
2050 @item Packaged LISP Libraries
|
|
|
2051 Many more packages are provided standard with XEmacs than with GNU Emacs
|
|
|
2052 19 or 20.
|
|
|
2053
|
|
|
2054 XEmacs 21 supports an integrated package management system which uses
|
|
|
2055 EFS to download, then automatically install prebuilt LISP
|
|
|
2056 libraries. This allows XEmacs users much more straightforward access to
|
|
|
2057 the "latest and greatest" version of any given library.
|
|
|
2058
|
|
|
2059 We are working on a standard method for enabling, disabling and
|
|
|
2060 otherwise controlling packages, which should make them very easy to use.
|
|
|
2061
|
|
|
2062 @item LISP Programming
|
|
|
2063 From XEmacs 20 on, characters are a separate type. Characters can be
|
|
|
2064 converted to integers (and many integers can be converted to
|
|
|
2065 characters), but characters are not integers. GNU Emacs 19, XEmacs 19,
|
|
|
2066 Mule 2.3 (an extensive patch to GNU Emacs 18.55 and 19.x), and GNU Emacs
|
|
|
2067 20 (incorporating Mule 3 and later Mule 4) represent them as integers.
|
|
|
2068
|
|
|
2069 From XEmacs 20 on, the buffer is treated as an array of characters, and
|
|
|
2070 the representation of buffer text is not exposed to LISP. The GNU Emacs
|
|
|
2071 20 functions like buffer-as-multibyte are not supported.
|
|
|
2072
|
|
|
2073 In XEmacs, events are first-class objects. GNU Emacs 19 represents them
|
|
|
2074 as integers, which obscures the differences between a key gesture and
|
|
|
2075 the ancient ASCII code used to represent a particular overlapping subset
|
|
|
2076 of them.
|
|
|
2077
|
|
|
2078 In XEmacs, keymaps are first-class opaque objects. GNU Emacs 19
|
|
|
2079 represents them as complicated combinations of association lists and
|
|
|
2080 vectors. If you use the advertised functional interface to manipulation
|
|
|
2081 of keymaps, the same code will work in XEmacs, GNU Emacs 18, and GNU
|
|
|
2082 Emacs 19; if your code depends on the underlying implementation of
|
|
|
2083 keymaps, it will not.
|
|
|
2084
|
|
|
2085 XEmacs uses "extents" to represent all non-textual aspects of buffers;
|
|
|
2086 GNU Emacs 19 uses two distinct objects, "text properties" and
|
|
|
2087 "overlays", which divide up the functionality between them. Extents are
|
|
|
2088 a superset of the union of the functionality of the two GNU Emacs data
|
|
|
2089 types. The full GNU Emacs 19 interface to text properties and overlays
|
|
|
2090 is supported in XEmacs (with extents being the underlying
|
|
|
2091 representation).
|
|
|
2092
|
|
|
2093 Extents can be made to be copied into strings, and then restored, by
|
|
|
2094 kill and yank. Thus, one can specify this behavior on either "extents"
|
|
|
2095 or "text properties", whereas in GNU Emacs 19 text properties always
|
|
|
2096 have this behavior and overlays never do.
|
|
|
2097
|
|
|
2098 @item Window System Programming Interface
|
|
|
2099 XEmacs uses the MIT "Xt" toolkit instead of raw Xlib calls, which makes
|
|
|
2100 it be a more well-behaved X citizen (and also improves portability). A
|
|
|
2101 result of this is that it is possible to include other Xt "Widgets" in
|
|
|
2102 the XEmacs window. Also, XEmacs understands the standard Xt command-line
|
|
|
2103 arguments.
|
|
|
2104
|
|
|
2105 XEmacs supports Motif applications, generic Xt (e.g. Athena)
|
|
|
2106 applications, and raw Xlib applications. An XEmacs variant which
|
|
|
2107 supports GTK+ is available (integration as an option in the XEmacs
|
|
|
2108 mainline is planned for XEmacs 22), although code to take advantage of
|
|
|
2109 the support is as yet scarce.
|
|
|
2110
|
|
|
2111 An XEmacs frame can be placed within an "external client widget" managed
|
|
|
2112 by another application. This allows an application to use an XEmacs
|
|
|
2113 frame as its text pane rather than the standard Text widget that is
|
|
|
2114 provided with Motif or Athena.
|
|
|
2115
|
|
|
2116 @item Community Participation
|
|
2459
|
2117 Joining the XEmacs development team is simple. Mail to
|
|
|
2118 @email{xemacs-beta@@xemacs.org, XEmacs Developers}, and you're in! (If
|
|
|
2119 you want to be, of course. You're also welcome to just post
|
|
|
2120 development-related questions and bug reports.) The GNU Emacs
|
|
2417
|
2121 development team and internal mailing lists are still by invitation
|
|
|
2122 only.
|
|
|
2123
|
|
|
2124 The "bleeding edge" of mainline XEmacs development is available by
|
|
|
2125 anonymous CVS as are some subsidiary branches (check out the xemacs-gtk
|
|
|
2126 module for the latest in GUI features!)
|
|
|
2127
|
|
|
2128 Development and maintenance of Lisp libraries is separated from the core
|
|
|
2129 editor development at a fairly low level. This provides better
|
|
|
2130 modularization and a better division of responsibility between external
|
|
|
2131 library maintainers and the XEmacs core development team. Even for
|
|
|
2132 packages the size of Gnus, XEmacs users normally have access to a
|
|
|
2133 pre-built version within a few weeks of a major release, and minor
|
|
|
2134 updates often within days.
|
|
|
2135
|
|
|
2136 CVS commit authority is broadly dispersed. Recognized maintainers of
|
|
|
2137 LISP libraries who are willing to maintain XEmacs packaged versions
|
|
|
2138 automatically qualify for CVS accounts for their packages.
|
|
|
2139 @end table
|
|
|
2140
|
|
2537
|
2141 @node Q1.6.3, Q1.6.4, Q1.6.2, Introduction
|
|
|
2142 @unnumberedsubsec Q1.6.3: How much does XEmacs differ?
|
|
2417
|
2143
|
|
|
2144 RMS has asserted at times that XEmacs is merely a "patch" on top of
|
|
2537
|
2145 GNU Emacs (@pxref{Q1.6.4}). In fact, probably not more than 5% of the
|
|
2417
|
2146 code, if that, remains unchanged, and nearly 14 years of work has gone
|
|
|
2147 into XEmacs at this point. (GNU Emacs itself is only than 20 years
|
|
|
2148 old, and thus XEmacs has existed as a separate product for over 2/3 of
|
|
|
2149 the lifespan of GNU Emacs.) As a point of comparison, XEmacs 21.5 has
|
|
|
2150 perhaps 65,000 more lines of C code than GNU Emacs 21.2.
|
|
|
2151
|
|
|
2152 However, the XEmacs developers strive to keep their code compatible with
|
|
|
2153 GNU Emacs, especially on the Lisp level. Much effort goes into
|
|
|
2154 "synching" the XEmacs Elisp code with recent GNU Emacs releases so as to
|
|
|
2155 benefit from GNU Emacs development work. (In contrast, almost no code
|
|
|
2156 from XEmacs has made it into GNU Emacs, and in fact the GNU Emacs
|
|
|
2157 developers are instructed by RMS not to even look at XEmacs source code!
|
|
|
2158 This stems from self-imposed licensing restrictions on the part of GNU
|
|
|
2159 Emacs -- and almost certainly out of hostility, as well.)
|
|
|
2160
|
|
2537
|
2161 @node Q1.6.4, Q1.6.5, Q1.6.3, Introduction
|
|
|
2162 @unnumberedsubsec Q1.6.4: Is XEmacs "GNU"?
|
|
2417
|
2163
|
|
|
2164 RMS insists on the term "GNU XEmacs" and maintains that
|
|
|
2165
|
|
|
2166 @quotation
|
|
|
2167 XEmacs is GNU software because it's a modified version of a
|
|
|
2168 GNU program. And it is GNU software because the FSF is the copyright
|
|
|
2169 holder for most of it, and therefore the legal responsibility for
|
|
|
2170 protecting its free status falls on us whether we want it or not. This
|
|
|
2171 is why the term "GNU XEmacs" is legitimate.
|
|
|
2172 @end quotation
|
|
|
2173
|
|
|
2174 In fact, FSF is @emph{not} the copyright holder for most of the code,
|
|
2537
|
2175 as very little unmodified FSF code remains (@pxref{Q1.6.3}).
|
|
2417
|
2176
|
|
|
2177 Furthermore, RMS's assertion that XEmacs is "GNU" seems rather bizarre
|
|
|
2178 to the XEmacs developers given RMS's hostility and general lack of
|
|
|
2179 interest in cooperation. "GNU" software in general is part of the GNU
|
|
|
2180 Project, is distributed by it on their FTP site, and receives support
|
|
|
2181 (or at least cooperation), as well as implicit endorsement, from it.
|
|
|
2182 The GNU Project, however, has never supported XEmacs and never
|
|
|
2183 distributed XEmacs, and RMS's hostility is the farthest thing possible
|
|
|
2184 from an endorsement. In fact, the GNU Project distributes a number of
|
|
|
2185 non-GNU software projects on the FSF web site, but again XEmacs is not
|
|
|
2186 one of them.
|
|
|
2187
|
|
2537
|
2188 @node Q1.6.5, Q1.6.6, Q1.6.4, Introduction
|
|
|
2189 @unnumberedsubsec Q1.6.5: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
2417
|
2190
|
|
|
2191 Unfortunately even the naming of these two applications has become
|
|
|
2192 politicized. Much of this stems from RMS, who has a history of
|
|
|
2193 politicizing similar issues. (Compare the controversy over "Lignux"
|
|
|
2194 and "GNU/Linux".) We would prefer that the terms "XEmacs" and "GNU
|
|
|
2195 Emacs" be used, which are neutral and acceptable to most people. RMS,
|
|
|
2196 however, is not willing to accept these terms. He insists that, if
|
|
|
2197 his product is called "GNU Emacs", then ours must be called "GNU
|
|
2537
|
2198 XEmacs". (For our opinion of this term, @xref{Q1.6.4}.) On the other
|
|
2417
|
2199 hand, if our product is to be called "XEmacs", as we prefer, then his
|
|
|
2200 product must simply be called "Emacs". The intent of this seems
|
|
|
2201 clear: RMS wants to make sure the names reflect his view that his
|
|
|
2202 version is the "real" Emacs and ours is merely a derivative,
|
|
2537
|
2203 second-class product (@pxref{Q1.6.3}).
|
|
2417
|
2204
|
|
|
2205 The XEmacs developers hope that you will use the neutral terms
|
|
|
2206 "XEmacs" and "GNU Emacs" for these two specific products. "Emacs", on
|
|
|
2207 the other hand, is a generic term for a class of programmable text
|
|
|
2208 editors with a similar look-and-feel, and usually a Lisp-based
|
|
|
2209 extension language. These trace themselves back to early editors such
|
|
|
2210 as EINE, ZWEI, ZMACS and Multics Emacs. @xref{A History of Emacs,,,
|
|
|
2211 internals, XEmacs Internals Manual}.
|
|
|
2212
|
|
|
2213 We also call upon RMS, in the spirit of furthering cooperation, to
|
|
|
2214 stop politicizing this issue and use the neutral terms "XEmacs" and
|
|
|
2215 "GNU Emacs". We have already acceded to RMS' wishes in this respect,
|
|
|
2216 and we expect him to do the same. (In the past, the XEmacs developers
|
|
|
2217 often used the terms "FSF Emacs" or "FSFmacs" or "RMSmacs" in
|
|
|
2218 reference to GNU Emacs; these terms were apparently modeled after RMS'
|
|
|
2219 own usage of "Gosmacs" and "Gosling Emacs" in reference to Unipress
|
|
|
2220 Emacs, produced by James Gosling. RMS, however, considers such terms
|
|
|
2221 to be insulting, so we refrain from using them as much as possible in
|
|
|
2222 preference to GNU Emacs.)
|
|
|
2223
|
|
2537
|
2224 @node Q1.6.6, Q1.7.1, Q1.6.5, Introduction
|
|
|
2225 @unnumberedsubsec Q1.6.6: Why haven't XEmacs and GNU Emacs merged?
|
|
2417
|
2226
|
|
|
2227 There are currently irreconcilable differences in the views about
|
|
|
2228 technical, programming, design, organizational and legal matters
|
|
|
2229 between Richard Stallman (RMS), the author and leader of the GNU Emacs
|
|
|
2230 project, and the XEmacs development team which provide little hope for
|
|
|
2231 a merge to take place in the short-term future. There have been
|
|
|
2232 repeated attempts at merging by all of the major XEmacs developers,
|
|
|
2233 starting from the early days of Lucid Emacs (in 1991), but they have
|
|
|
2234 all failed. RMS has very strong views about how GNU Emacs should be
|
|
|
2235 structured and how his project should be run, and during the repeated
|
|
|
2236 merge efforts has never demonstrated any realistic interest in
|
|
|
2237 sufficiently compromising or ceding control to allow a middle ground
|
|
|
2238 to be found. The basic problem seems to be the very different goals
|
|
|
2239 of RMS and the XEmacs project. The primary goals of the XEmacs
|
|
|
2240 project are technical and organizational -- we want to create the best
|
|
|
2241 editor possible, and to make it as easy as possible for people around
|
|
|
2242 the world to contribute. The primary goals of RMS, on the other hand,
|
|
|
2243 are political, and GNU Emacs, and any potential merge efforts with
|
|
|
2244 XEmacs, are strictly subservient to these goals. In fact, in many
|
|
|
2245 ways RMS sees GNU Emacs as the "poster child" of his aims, the one
|
|
|
2246 program in the GNU project that above all others must set an example
|
|
|
2247 to the world. (This has to do with the fact that GNU Emacs was the
|
|
|
2248 first program in the GNU project, and the only one that he is still
|
|
|
2249 personally involved with on a day-to-day basis.) Given his goals, his
|
|
|
2250 position is completely reasonable -- but unfortunately, makes any
|
|
|
2251 merge impossible.
|
|
|
2252
|
|
|
2253 From the XEmacs perspective, the most intractable issues appear to be
|
|
|
2254 legal and organizational, specifically:
|
|
428
|
2255
|
|
|
2256 @itemize @bullet
|
|
|
2257 @item
|
|
2417
|
2258 RMS requires "legal papers" to be signed for all contributions of code
|
|
|
2259 to GNU Emacs over 10 lines or so, transferring the copyright and all
|
|
|
2260 legal rights to the code to the Free Software Foundation. XEmacs does
|
|
|
2261 not and has never required this, since it has the practical effect of
|
|
|
2262 discouraging individual and in particular corporate contributions --
|
|
|
2263 corporations will almost never sign away their legal rights to code
|
|
|
2264 since it makes it impossible to reuse the code in any product that
|
|
|
2265 whose license is not compatible with the GNU General Public License.
|
|
|
2266 Since RMS has shown no inclination to compromise on this issue, a
|
|
|
2267 merge would require that most of the existing XEmacs code would need
|
|
|
2268 to be thrown away and rewritten -- something the XEmacs developers are
|
|
|
2269 understandably reluctant to do.
|
|
|
2270
|
|
|
2271 @item
|
|
|
2272 A repeated stumbling block in the merge talks has been the issue of
|
|
|
2273 organizational control over the resulting product. RMS has made it
|
|
|
2274 clear that he intends to have final say over design issues in a merged
|
|
|
2275 Emacs. Unfortunately, RMS and the XEmacs developers have repeatedly
|
|
|
2276 clashed over design decisions, and RMS' insistence on getting his way
|
|
|
2277 in such disagreements was the very reason for the split in the first
|
|
|
2278 place. This same issue has come up again and again in merge talks and
|
|
|
2279 we have never been able to come to a satisfactory resolution. To the
|
|
|
2280 extent that RMS is willing to compromise at all, it appears to be of a
|
|
|
2281 purely political rather than technical nature -- "If we support this
|
|
|
2282 feature of yours, we also get to support this other feature of mine."
|
|
|
2283 The XEmacs developers cannot see how such a process would lead to
|
|
|
2284 anything but a mess of incompatible things hodgepodged together.
|
|
|
2285
|
|
|
2286 @item
|
|
|
2287 Because of the years of separate development, distinct and
|
|
|
2288 incompatible interfaces have developed and merging would be extremely
|
|
|
2289 difficult even with the above non-technical issues resolved. The
|
|
|
2290 problem has been exacerbated by the issue of legal papers -- because
|
|
|
2291 XEmacs code is not "kosher" from RMS' perspective, he discourages
|
|
|
2292 developers from even looking at it out of legal concerns. Although it
|
|
|
2293 is still possible to read the XEmacs documentation and run the
|
|
|
2294 program, the practical effect of this prohibition has been to strongly
|
|
|
2295 discourage code-sharing and cooperative development -- although a
|
|
|
2296 great deal of GNU Emacs code has been incorporated into XEmacs,
|
|
|
2297 practically none has gone the other direction.
|
|
428
|
2298 @end itemize
|
|
|
2299
|
|
|
2300 If you have a comment to add regarding the merge, it is a good idea to
|
|
2417
|
2301 avoid posting to the newsgroups, because of the very heated flamewars
|
|
|
2302 that often result. Mail your questions to
|
|
|
2303 @email{xemacs-beta@@xemacs.org} and @email{emacs-devel@@gnu.org}.
|
|
|
2304
|
|
2537
|
2305 @unnumberedsec 1.7: External Packages
|
|
|
2306
|
|
2559
|
2307 @node Q1.7.1, Q1.7.2, Q1.6.6, Introduction
|
|
|
2308 @unnumberedsubsec Q1.7.1: What is the package system?
|
|
|
2309
|
|
|
2310 In order to reduce the size and increase the maintainability of
|
|
|
2311 XEmacs, the majority of the Elisp packages that came with previous
|
|
|
2312 releases have been unbundled. They have been replaced by the package
|
|
|
2313 system. Each elisp add-on (or groups of them when they are small) now
|
|
|
2314 comes in its own tarball that contains a small search hierarchy.
|
|
|
2315
|
|
|
2316 You select just the ones you need. Install them by untarring them into
|
|
|
2317 the right place. On startup XEmacs will find them, set up the load
|
|
|
2318 path correctly, install autoloads, etc, etc.
|
|
|
2319
|
|
|
2320 @xref{Q2.1.1}, for more info on how to download and install the packages.
|
|
|
2321
|
|
|
2322 @node Q1.7.2, Q1.7.3, Q1.7.1, Introduction
|
|
|
2323 @unnumberedsubsec Q1.7.2: Which external packages are there?
|
|
2537
|
2324
|
|
|
2325 @subheading Normal Packages
|
|
|
2326
|
|
|
2327 A very broad collection of elisp packages.
|
|
2417
|
2328
|
|
|
2329 @table @asis
|
|
2537
|
2330 @item Sun
|
|
|
2331 Support for Sparcworks.
|
|
|
2332
|
|
|
2333 @item ada
|
|
|
2334 Ada language support.
|
|
|
2335
|
|
|
2336 @item apel
|
|
|
2337 A Portable Emacs Library. Used by XEmacs MIME support.
|
|
|
2338
|
|
|
2339 @item auctex
|
|
|
2340 Basic TeX/LaTeX support.
|
|
|
2341
|
|
|
2342 @item bbdb
|
|
|
2343 The Big Brother Data Base: a rolodex-like database program.
|
|
|
2344
|
|
|
2345 @item build
|
|
|
2346 Build XEmacs from within (UNIX, Windows).
|
|
|
2347
|
|
|
2348 @item c-support
|
|
|
2349 Basic single-file add-ons for editing C code.
|
|
|
2350
|
|
|
2351 @item calc
|
|
|
2352 Emacs calculator.
|
|
|
2353
|
|
|
2354 @item calendar
|
|
|
2355 Calendar and diary support.
|
|
|
2356
|
|
|
2357 @item cc-mode
|
|
|
2358 C, C++, Objective-C, Java, CORBA IDL, Pike and AWK language support.
|
|
|
2359
|
|
|
2360 @item clearcase
|
|
|
2361 New Clearcase Version Control for XEmacs (UNIX, Windows).
|
|
|
2362
|
|
|
2363 @item clearcase
|
|
|
2364 Support for the Clearcase version control system.
|
|
|
2365
|
|
|
2366 @item cookie
|
|
|
2367 "Fortune cookie"-style messages. Includes Spook (suspicious phrases)
|
|
|
2368 and Yow (Zippy quotes).
|
|
|
2369
|
|
|
2370 @item crisp
|
|
|
2371 Crisp/Brief emulation.
|
|
|
2372
|
|
|
2373 @item debug
|
|
|
2374 GUD, gdb, dbx debugging support.
|
|
|
2375
|
|
|
2376 @item dictionary
|
|
|
2377 Interface to RFC2229 dictionary servers.
|
|
|
2378
|
|
|
2379 @item dired
|
|
|
2380 The DIRectory EDitor is for manipulating, and running commands on
|
|
|
2381 files in a directory.
|
|
|
2382
|
|
|
2383 @item docbookide
|
|
|
2384 DocBook editing support.
|
|
|
2385
|
|
|
2386 @item ecb
|
|
|
2387 Emacs source code browser.
|
|
|
2388
|
|
|
2389 @item ecrypto
|
|
|
2390 Crypto functionality in Emacs Lisp.
|
|
|
2391
|
|
|
2392 @item edebug
|
|
|
2393 An Emacs Lisp debugger.
|
|
|
2394
|
|
|
2395 @item ediff
|
|
|
2396 Interface over GNU patch.
|
|
|
2397
|
|
|
2398 @item edit-utils
|
|
|
2399 Miscellaneous editor extensions, you probably need this.
|
|
|
2400
|
|
|
2401 @item edt
|
|
|
2402 DEC EDIT/EDT emulation.
|
|
|
2403
|
|
|
2404 @item efs
|
|
|
2405 Treat files on remote systems the same as local files.
|
|
|
2406
|
|
|
2407 @item eieio
|
|
|
2408 Enhanced Implementation of Emacs Interpreted Objects.
|
|
|
2409
|
|
|
2410 @item elib
|
|
|
2411 Portable Emacs Lisp utilities library.
|
|
|
2412
|
|
|
2413 @item emerge
|
|
|
2414 Another interface over GNU patch.
|
|
|
2415
|
|
|
2416 @item erc
|
|
|
2417 ERC is an Emacs InternetRelayChat client.
|
|
|
2418
|
|
|
2419 @item escreen
|
|
|
2420 Multiple editing sessions withing a single frame (like screen).
|
|
|
2421
|
|
|
2422 @item eshell
|
|
|
2423 Command shell implemented entirely in Emacs Lisp.
|
|
|
2424
|
|
|
2425 @item ess
|
|
|
2426 ESS: Emacs Speaks Statistics.
|
|
|
2427
|
|
|
2428 @item eterm
|
|
|
2429 Terminal emulation.
|
|
|
2430
|
|
|
2431 @item eudc
|
|
|
2432 Emacs Unified Directory Client (LDAP, PH).
|
|
|
2433
|
|
|
2434 @item footnote
|
|
|
2435 Footnoting in mail message editing modes.
|
|
|
2436
|
|
|
2437 @item forms
|
|
|
2438 Forms editing support (obsolete, use Widget instead).
|
|
|
2439
|
|
|
2440 @item fortran-modes
|
|
|
2441 Fortran support.
|
|
|
2442
|
|
|
2443 @item fortran-modes
|
|
|
2444 Fortran language support.
|
|
|
2445
|
|
|
2446 @item frame-icon
|
|
|
2447 Set up mode-specific icons for each frame under XEmacs.
|
|
|
2448
|
|
|
2449 @item fsf-compat
|
|
|
2450 GNU Emacs compatibility files.
|
|
|
2451
|
|
|
2452 @item games
|
|
|
2453 Tetris, Sokoban, and Snake.
|
|
|
2454
|
|
|
2455 @item general-docs
|
|
|
2456 General documentation. Presently, empty.
|
|
|
2457
|
|
|
2458 @item gnats
|
|
|
2459 XEmacs bug reports.
|
|
|
2460
|
|
|
2461 @item gnus
|
|
|
2462 The Gnus Newsreader and Mailreader.
|
|
|
2463
|
|
|
2464 @item haskell-mode
|
|
|
2465 Haskell editing support.
|
|
|
2466
|
|
|
2467 @item hm--html-menus
|
|
|
2468 HTML editing.
|
|
|
2469
|
|
|
2470 @item hyperbole
|
|
|
2471 Hyperbole: The Everyday Info Manager.
|
|
|
2472
|
|
|
2473 @item ibuffer
|
|
|
2474 Advanced replacement for buffer-menu.
|
|
|
2475
|
|
|
2476 @item idlwave
|
|
|
2477 Editing and Shell mode for the Interactive Data Language.
|
|
|
2478
|
|
|
2479 @item igrep
|
|
|
2480 Enhanced front-end for Grep.
|
|
|
2481
|
|
|
2482 @item ilisp
|
|
|
2483 Front-end for interacting with Inferior Lisp (external lisps).
|
|
|
2484
|
|
|
2485 @item ispell
|
|
|
2486 Spell-checking with GNU ispell.
|
|
|
2487
|
|
|
2488 @item jde
|
|
|
2489 Integrated Development Environment for Java.
|
|
|
2490
|
|
|
2491 @item liece
|
|
|
2492 IRC (Internet Relay Chat) client for Emacs. Note, this package is
|
|
|
2493 deprecated and will be removed, use riece instead.
|
|
|
2494
|
|
|
2495 @item mail-lib
|
|
|
2496 Fundamental lisp files for providing email support.
|
|
|
2497
|
|
|
2498 @item mailcrypt
|
|
|
2499 Support for messaging encryption with PGP.
|
|
|
2500
|
|
|
2501 @item mew
|
|
|
2502 Messaging in an Emacs World; a MIME-based email program.
|
|
|
2503
|
|
|
2504 @item mh-e
|
|
|
2505 The XEmacs Interface to the MH Mail System.
|
|
|
2506
|
|
|
2507 @item mine
|
|
|
2508 Elisp implementation of the game 'Minehunt'.
|
|
|
2509
|
|
|
2510 @item misc-games
|
|
|
2511 Other amusements and diversions.
|
|
|
2512
|
|
|
2513 @item mmm-mode
|
|
|
2514 Support for Multiple Major Modes within a single buffer.
|
|
|
2515
|
|
|
2516 @item net-utils
|
|
|
2517 Miscellaneous Networking Utilities.
|
|
|
2518
|
|
|
2519 @item ocaml
|
|
|
2520 Objective Caml editing support.
|
|
|
2521
|
|
|
2522 @item oo-browser
|
|
|
2523 OO-Browser: The Multi-Language Object-Oriented Code Browser.
|
|
|
2524
|
|
|
2525 @item ocaml
|
|
|
2526 Objective Caml editing support.
|
|
|
2527
|
|
|
2528 @item os-utils
|
|
|
2529 Miscellaneous single-file O/S utilities, for printing, archiving,
|
|
|
2530 compression, remote shells, etc.
|
|
|
2531
|
|
|
2532 @item pc
|
|
|
2533 PC style interface emulation.
|
|
|
2534
|
|
|
2535 @item pcl-cvs
|
|
|
2536 CVS frontend.
|
|
|
2537
|
|
|
2538 @item pcomplete
|
|
|
2539 Provides programmatic completion.
|
|
|
2540
|
|
|
2541 @item perl-modes
|
|
|
2542 Perl support.
|
|
|
2543
|
|
|
2544 @item pgg
|
|
|
2545 Emacs interface to various PGP implementations.
|
|
|
2546
|
|
|
2547 @item prog-modes
|
|
|
2548 Support for various programming languages.
|
|
|
2549
|
|
|
2550 @item ps-print
|
|
|
2551 Printing functions and utilities.
|
|
|
2552
|
|
|
2553 @item psgml
|
|
|
2554 Validated HTML/SGML editing.
|
|
|
2555
|
|
|
2556 @item psgml-dtds
|
|
|
2557 A collection of DTDs for psgml. Note that this package is deprecated
|
|
|
2558 and will be removed in the future, most likely Q2/2003. Instead of using
|
|
|
2559 this, you should install needed DTDs yourself.
|
|
|
2560
|
|
|
2561 @item python-modes
|
|
|
2562 Python language support.
|
|
|
2563
|
|
|
2564 @item reftex
|
|
|
2565 Emacs support for LaTeX cross-references, citations.
|
|
|
2566
|
|
|
2567 @item riece
|
|
|
2568 IRC (Internet Relay Chat) client for Emacs.
|
|
|
2569
|
|
|
2570 @item rmail
|
|
|
2571 An obsolete Emacs mailer. If you do not already use it don't start.
|
|
|
2572
|
|
|
2573 @item ruby-modes
|
|
|
2574 Ruby support.
|
|
|
2575
|
|
|
2576 @item sasl
|
|
|
2577 Simple Authentication and Security Layer (SASL) library.
|
|
|
2578
|
|
|
2579 @item scheme
|
|
|
2580 Front-end support for Inferior Scheme.
|
|
|
2581
|
|
|
2582 @item semantic
|
|
|
2583 Semantic bovinator (Yacc/Lex for XEmacs). Includes Senator.
|
|
|
2584
|
|
|
2585 @item sgml
|
|
|
2586 SGML/Linuxdoc-SGML editing.
|
|
|
2587
|
|
|
2588 @item sh-script
|
|
|
2589 Support for editing shell scripts.
|
|
|
2590
|
|
|
2591 @item sieve
|
|
|
2592 Manage Sieve email filtering scripts.
|
|
|
2593
|
|
|
2594 @item slider
|
|
|
2595 User interface tool.
|
|
|
2596
|
|
|
2597 @item sml-mode
|
|
|
2598 SML editing support.
|
|
|
2599
|
|
|
2600 @item sounds-au
|
|
|
2601 XEmacs Sun sound files.
|
|
|
2602
|
|
|
2603 @item sounds-wav
|
|
|
2604 XEmacs Microsoft sound files.
|
|
|
2605
|
|
|
2606 @item speedbar
|
|
|
2607 Provides a separate frame with convenient references.
|
|
|
2608
|
|
|
2609 @item strokes
|
|
|
2610 Mouse enhancement utility.
|
|
|
2611
|
|
|
2612 @item supercite
|
|
|
2613 An Emacs citation tool for News & Mail messages.
|
|
|
2614
|
|
|
2615 @item texinfo
|
|
|
2616 XEmacs TeXinfo support.
|
|
|
2617
|
|
|
2618 @item text-modes
|
|
|
2619 Miscellaneous support for editing text files.
|
|
|
2620
|
|
|
2621 @item textools
|
|
|
2622 Miscellaneous TeX support.
|
|
|
2623
|
|
|
2624 @item time
|
|
|
2625 Display time & date on the modeline.
|
|
|
2626
|
|
|
2627 @item tm
|
|
|
2628 Emacs MIME support. Not needed for gnus >= 5.8.0.
|
|
|
2629
|
|
|
2630 @item tooltalk
|
|
|
2631 Support for building with Tooltalk.
|
|
|
2632
|
|
|
2633 @item tpu
|
|
|
2634 DEC EDIT/TPU support.
|
|
|
2635
|
|
|
2636 @item tramp
|
|
|
2637 Remote shell-based file editing. This is similar to EFS or Ange-FTP,
|
|
|
2638 but works with rsh/ssh and rcp/scp.
|
|
|
2639
|
|
|
2640 @item vc
|
|
|
2641 Version Control for Free systems.
|
|
|
2642
|
|
|
2643 @item vc-cc
|
|
|
2644 Version Control for ClearCase (UnFree) systems.
|
|
|
2645
|
|
|
2646 @item vhdl
|
|
|
2647 Support for VHDL.
|
|
|
2648
|
|
|
2649 @item view-process
|
|
|
2650 A Unix process browsing tool.
|
|
|
2651
|
|
|
2652 @item viper
|
|
|
2653 VI emulation support.
|
|
|
2654
|
|
|
2655 @item vm
|
|
|
2656 An Emacs mailer.
|
|
|
2657
|
|
|
2658 @item w3
|
|
|
2659 A Web browser.
|
|
|
2660
|
|
|
2661 @item x-symbol
|
|
|
2662 Semi WYSIWYG for LaTeX, HTML, etc, using additional fonts.
|
|
|
2663
|
|
|
2664 @item xemacs-base
|
|
|
2665 Fundamental XEmacs support, you almost certainly need this.
|
|
|
2666
|
|
|
2667 @item xemacs-devel
|
|
|
2668 XEmacs Lisp developer support. This package contains utilities for
|
|
|
2669 supporting Lisp development. It is a single-file package so it may be
|
|
|
2670 tailored.
|
|
|
2671
|
|
|
2672 @item xlib
|
|
|
2673 Emacs interface to X server.
|
|
|
2674
|
|
|
2675 @item xslide
|
|
|
2676 XSL editing support.
|
|
|
2677
|
|
|
2678 @item xslt-process
|
|
|
2679 A minor mode for (X)Emacs which allows running an XSLT processor on a
|
|
|
2680 buffer.
|
|
|
2681
|
|
|
2682 @item xwem
|
|
|
2683 X Emacs Window Manager.
|
|
|
2684
|
|
|
2685 @item zenirc
|
|
|
2686 ZENIRC IRC Client.
|
|
2417
|
2687 @end table
|
|
|
2688
|
|
2537
|
2689 @subheading Mule Support (mule)
|
|
|
2690
|
|
|
2691 MULti-lingual Enhancement. Support for world scripts such as
|
|
|
2692 Latin, Arabic, Cyrillic, Chinese, Japanese, Greek, Hebrew etc.
|
|
|
2693 To use these packages your XEmacs must be compiled with Mule
|
|
|
2694 support.
|
|
|
2695
|
|
|
2696 @table @asis
|
|
|
2697 @item edict
|
|
|
2698 MULE: Lisp Interface to EDICT, Kanji Dictionary.
|
|
|
2699
|
|
|
2700 @item egg-its
|
|
|
2701 MULE: Wnn (4.2 and 6) support. SJ3 support.
|
|
|
2702
|
|
|
2703 @item latin-unity
|
|
|
2704 MULE: find single ISO 8859 character set to encode a buffer.
|
|
|
2705
|
|
|
2706 @item latin-unity
|
|
|
2707 Unify character sets in a buffer. When characters belong to disjoint
|
|
|
2708 character sets, this attempts to translate the characters so
|
|
|
2709 that they belong to one character set. If the buffer coding system is
|
|
|
2710 not sufficient, this suggests different coding systems.
|
|
|
2711
|
|
|
2712 @item leim
|
|
|
2713 MULE: Quail. All non-English and non-Japanese language support.
|
|
|
2714
|
|
|
2715 @item locale
|
|
|
2716 MULE: Localized menubars and localized splash screens.
|
|
|
2717
|
|
|
2718 @item lookup
|
|
|
2719 Dictionary support. (This isn't an English dictionary program)
|
|
|
2720
|
|
|
2721 @item mule-base
|
|
|
2722 MULE: Basic Mule support, required for building with Mule.
|
|
|
2723
|
|
|
2724 @item mule-ucs
|
|
|
2725 MULE: Extended coding systems (including Unicode) for XEmacs.
|
|
|
2726
|
|
|
2727 @item mule-ucs
|
|
|
2728 Extended coding systems (including Unicode) for XEmacs.
|
|
|
2729
|
|
|
2730 @item skk
|
|
|
2731 Another Japanese Language Input Method. Can be used without a
|
|
|
2732 separate process running as a dictionary server.
|
|
|
2733 @end table
|
|
|
2734
|
|
2559
|
2735 @node Q1.7.3, Q1.7.4, Q1.7.2, Introduction
|
|
|
2736 @unnumberedsubsec Q1.7.3: Do I need to have the packages to run XEmacs?
|
|
|
2737
|
|
|
2738 Strictly speaking, no. XEmacs will build and install just fine without
|
|
|
2739 any packages installed. However, only the most basic editing functions
|
|
|
2740 will be available with no packages installed, so installing packages is
|
|
|
2741 an essential part of making your installed XEmacs _useful_.
|
|
|
2742
|
|
|
2743 @node Q1.7.4, Q1.8.1, Q1.7.3, Introduction
|
|
|
2744 @unnumberedsubsec Q1.7.4: Is there a way to find which package has particular functionality?
|
|
|
2745
|
|
|
2746 If you want to find out which package contains the functionality you
|
|
|
2747 are looking for, use @kbd{M-x package-get-package-provider}, and give it a
|
|
|
2748 symbol that is likely to be in that package.
|
|
|
2749
|
|
|
2750 For example, if some code you want to use has a @code{(require 'thingatpt)}
|
|
|
2751 in it:
|
|
|
2752
|
|
|
2753 @example
|
|
|
2754 M-x package-get-package-provider RET thingatpt RET
|
|
|
2755 @end example
|
|
|
2756
|
|
|
2757 which will return something like: @samp{(fsf-compat "1.08").}
|
|
|
2758
|
|
2537
|
2759 @unnumberedsec 1.8: Internationalization
|
|
|
2760
|
|
2559
|
2761 @node Q1.8.1, Q1.8.2, Q1.7.4, Introduction
|
|
2537
|
2762 @unnumberedsubsec Q1.8.1: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
442
|
2763
|
|
|
2764 Both the stable and development versions of XEmacs include
|
|
1135
|
2765 internationalization support (aka MULE). MULE currently (21.4) works on
|
|
|
2766 UNIX and Linux systems. It is possible to build with MULE on Windows
|
|
|
2767 systems, but if you really need MULE on Windows, it is recommended that
|
|
|
2768 you build and use the development (21.5) version, and deal with the
|
|
|
2769 instability of the development tree. Binaries compiled without MULE
|
|
|
2770 support run faster than MULE capable XEmacsen.
|
|
428
|
2771
|
|
2537
|
2772 @node Q1.8.2, Q1.8.3, Q1.8.1, Introduction
|
|
|
2773 @unnumberedsubsec Q1.8.2: How can I help with internationalization?
|
|
430
|
2774
|
|
|
2775 If you would like to help, you may want to join the
|
|
|
2776 @email{xemacs-mule@@xemacs.org} mailing list. Especially needed are
|
|
|
2777 people who speak/write languages other than English, who are willing to
|
|
|
2778 use XEmacs/MULE regularly, and have some experience with Elisp.
|
|
428
|
2779
|
|
1135
|
2780 Translations of the TUTORIAL and man page are welcome, and XEmacs does
|
|
|
2781 support multilingual menus, but we have few current translations.
|
|
|
2782
|
|
2537
|
2783 @xref{Q1.5.2, How do I become a Beta Tester?}.
|
|
|
2784
|
|
|
2785 @node Q1.8.3, Q1.8.4, Q1.8.2, Introduction
|
|
|
2786 @unnumberedsubsec Q1.8.3: How do I type non-ASCII characters?
|
|
2417
|
2787
|
|
2459
|
2788 @xref{Q3.0.6, How can you type in special characters in XEmacs?}, in
|
|
2417
|
2789 part 3 of this FAQ, for some simple methods that also work in non-MULE
|
|
|
2790 builds of XEmacs (but only for one-octet coded character sets, and
|
|
|
2791 mostly for ISO 8859/1). Many of the methods available for Cyrillic
|
|
2537
|
2792 (@pxref{Q1.8.7, How about Cyrillic modes?}) work without MULE. MULE
|
|
|
2793 has more general capabilities. @xref{Q1.8.5, Please explain the
|
|
2417
|
2794 various input methods in MULE/XEmacs}.
|
|
|
2795
|
|
2459
|
2796 @xref{Q4.0.8, How do I display non-ASCII characters?}, which covers
|
|
2417
|
2797 display of non-ASCII characters.
|
|
|
2798
|
|
2537
|
2799 @node Q1.8.4, Q1.8.5, Q1.8.3, Introduction
|
|
|
2800 @unnumberedsubsec Q1.8.4: Can XEmacs messages come out in a different language?
|
|
428
|
2801
|
|
1135
|
2802 The message-catalog support was written but is badly bit-rotted. XEmacs
|
|
|
2803 20 and 21 did @emph{not} support it, and early releases of XEmacs 22
|
|
|
2804 will not either.
|
|
|
2805
|
|
|
2806 However, menubar localization @emph{does} work. To enable it, add to
|
|
|
2807 your @file{Emacs} file entries like this:
|
|
428
|
2808
|
|
|
2809 @example
|
|
440
|
2810 Emacs*XlwMenu.resourceLabels: True
|
|
|
2811 Emacs*XlwMenu.file.labelString: Fichier
|
|
442
|
2812 Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster oeffnen
|
|
428
|
2813 @end example
|
|
|
2814
|
|
|
2815 The name of the resource is derived from the non-localized entry by
|
|
|
2816 removing punctuation and capitalizing as above.
|
|
|
2817
|
|
2537
|
2818 @node Q1.8.5, Q1.8.6, Q1.8.4, Introduction
|
|
|
2819 @unnumberedsubsec Q1.8.5: Please explain the various input methods in MULE/XEmacs
|
|
428
|
2820
|
|
1135
|
2821 Mule supports a wide variety of input methods. There are three basic
|
|
|
2822 classes: Lisp implementations, generic platform support, and library
|
|
|
2823 interfaces.
|
|
|
2824
|
|
|
2825 @emph{Lisp implementations} include Quail, which provides table-driven input
|
|
|
2826 methods for almost all the character sets that Mule supports (including
|
|
|
2827 all of the ISO 8859 family, the Indic languages, Thai, and so on), and
|
|
|
2828 SKK, for Japanese. (SKK also supports an interface to an external
|
|
|
2829 "dictionary server" process.) Quail supports both typical "dead-key"
|
|
|
2830 methods (eg, in the "latin-1-prefix" method, @kbd{" a} produces ä, LATIN
|
|
|
2831 SMALL LETTER A WITH DIAERESIS), and the complex dictionary-based phonetic
|
|
|
2832 methods used for Asian ideographic languages like Chinese.
|
|
|
2833
|
|
|
2834 Lisp implementations can be less powerful (but they are not perceptibly
|
|
|
2835 inefficient), and of course are not portable to non-Emacs applications.
|
|
|
2836 The incompatibility can be very annoying. On the other hand, they
|
|
|
2837 require no special platform support or external libraries, so if you can
|
|
|
2838 display the characters, Mule can input them for you and you can edit,
|
|
|
2839 anywhere.
|
|
|
2840
|
|
|
2841 @emph{Generic platform support} is currently limited to the X Input
|
|
|
2842 Method (XIM) framework, although support for MSIME (for MS Windows) is
|
|
|
2843 planned, and IIIMF (Sun's Internet-Intranet Input Method Framework)
|
|
|
2844 support is extremely desirable. XIM is enabled at build time by use of
|
|
|
2845 the @samp{--with-xim} flag to @code{configure}. For use of XIM, see
|
|
|
2846 your platform documentation. However, normally the input method you use
|
|
|
2847 is specified via the @samp{LANG} and @samp{XMODIFIERS} environment
|
|
|
2848 variables.
|
|
|
2849
|
|
|
2850 Of course, input skills are portable across most applications. However,
|
|
|
2851 especially in modern GUI systems the habit of using bucky bits has
|
|
|
2852 fallen into sad disuse, and many XIM systems are poorly configured for
|
|
|
2853 use with Emacs. For example, the kinput2 input manager (a separate
|
|
|
2854 process providing an interface between Japanese dictionary servers such
|
|
|
2855 as Canna and Wnn, and the application) tends to gobble up keystrokes
|
|
|
2856 generating Meta characters. This means that to edit while using an XIM
|
|
|
2857 input method, you must toggle the input method off every time you want
|
|
|
2858 to use @kbd{M-f}. Your mileage may vary.
|
|
|
2859
|
|
|
2860 @emph{Library interfaces} are most common for Japanese, although Wnn
|
|
|
2861 supports Chinese (traditional and simplified) and Korean. There are
|
|
|
2862 Chinese and Korean input servers available, but we do not know of any
|
|
|
2863 patches for XEmacs to use them directly. You can use them via
|
|
|
2864 IM-enabled terminals, by manipulating the terminal coding systems. We
|
|
|
2865 describe only the Japanese-oriented systems here. The advantage of
|
|
|
2866 these systems is that they are very powerful, and on platforms where
|
|
|
2867 they are available there is typically a wide range of applications that
|
|
|
2868 support them. Thus your input skills are portable across applications.
|
|
|
2869
|
|
|
2870 Mule provides built-in interfaces to the following input methods: Wnn4,
|
|
|
2871 Wnn6, Canna, and SJ3. These can be configured at build time. There are
|
|
|
2872 patches available (no URL, sorry) to support the SKK server, as well.
|
|
|
2873 Wnn and SJ3 use the @code{egg} user interface. The interface for Canna
|
|
|
2874 is specialized to Canna.
|
|
428
|
2875
|
|
|
2876 Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
|
|
1135
|
2877 University. It is a powerful and complex system. Wnn4 is free and Wnn6
|
|
|
2878 is not. Wnn uses grammatical hints and probability of word association,
|
|
|
2879 so in principle Wnn can be cleverer than other methods.
|
|
|
2880
|
|
|
2881 Canna, made by NEC, supports only Japanese. It is a simple and powerful
|
|
|
2882 system. Canna uses only grammar, but its grammar and dictionary are
|
|
|
2883 quite sophisticated. So for standard modern Japanese, Canna seems
|
|
|
2884 cleverer than Wnn4. In addition, the UNIX version of Canna is free (now
|
|
|
2885 there is a Microsoft Windows version).
|
|
|
2886
|
|
|
2887 SJ3, by Sony, supports only Japanese.
|
|
428
|
2888
|
|
|
2889 Egg consists of following parts:
|
|
|
2890
|
|
|
2891 @enumerate
|
|
|
2892 @item
|
|
|
2893 Input character Translation System (ITS) layer.
|
|
|
2894 It translates ASCII inputs to Kana/PinYin/Hangul characters.
|
|
|
2895
|
|
|
2896 @item
|
|
|
2897 Kana/PinYin/Hangul to Kanji transfer layer.
|
|
1135
|
2898 The interface layer to network Kana-Kanji server (Wnn and Sj3).
|
|
428
|
2899 @end enumerate
|
|
|
2900
|
|
1135
|
2901 These input methods are modal. They have a raw (alphabet) mode, a
|
|
|
2902 phonetic input mode, and Kana-Kanji transfer mode. However there are
|
|
|
2903 mode-less input methods for Egg and Canna. @samp{boiled-egg} is a
|
|
|
2904 mode-less input method running on Egg. For Canna, @samp{canna.el} has a
|
|
|
2905 tiny boiled-egg-like command, @code{(canna-boil)}, and there are some
|
|
|
2906 boiled-egg-like utilities.
|
|
|
2907
|
|
|
2908 Much of this information was provided by @email{morioka@@jaist.ac.jp,
|
|
|
2909 MORIOKA Tomohiko}.
|
|
428
|
2910
|
|
2537
|
2911 @node Q1.8.6, Q1.8.7, Q1.8.5, Introduction
|
|
|
2912 @unnumberedsubsec Q1.8.6: How do I portably code for MULE/XEmacs?
|
|
428
|
2913
|
|
1135
|
2914 MULE has evolved rapidly over the last few years, and the original third
|
|
|
2915 party patch (for GNU Emacs 19), GNU Emacs 20+, and XEmacs 20+ have quite
|
|
|
2916 different implementations. The APIs also vary although recent versions
|
|
|
2917 of XEmacs have tended to converge to the GNU Emacs standard.
|
|
|
2918
|
|
|
2919 MULE implementations are going to continue to evolve. Both GNU Emacs
|
|
|
2920 and XEmacs are working hard on Unicode support, which will involve new
|
|
|
2921 APIs and probably variations on old ones. For XEmacs 22, the old ISO
|
|
|
2922 2022-based system for recognizing encodings will be replaced by a much
|
|
|
2923 more flexible system, which should improve accuracy of automatic coding
|
|
|
2924 detections, but will also involve new APIs.
|
|
|
2925
|
|
428
|
2926 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
|
|
|
2927
|
|
|
2928 @quotation
|
|
1135
|
2929 The application implementor must write separate code for these mule
|
|
|
2930 variants. [Please don't hesitate to report these variants to us; they
|
|
|
2931 are not, strictly speaking, bugs, but they give third-party developers
|
|
|
2932 the same kind of creepy-crawly feeling. We'll do what we can. -- Ed.]
|
|
428
|
2933
|
|
|
2934 MULE and the next version of Emacs are similar but the symbols are very
|
|
|
2935 different---requiring separate code as well.
|
|
|
2936
|
|
|
2937 Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of
|
|
|
2938 emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called
|
|
1135
|
2939 @code{emu} to provide a common interface. [There is an XEmacs package
|
|
|
2940 of APEL which provides much more comprehensive coverage. Be careful,
|
|
|
2941 however; APEL has problems of its own. -- Ed.]
|
|
428
|
2942
|
|
|
2943 I have the following suggestions about dealing with mule variants:
|
|
|
2944
|
|
|
2945 @itemize @bullet
|
|
|
2946 @item
|
|
|
2947 @code{(featurep 'mule)} @code{t} on all mule variants
|
|
|
2948
|
|
|
2949 @item
|
|
|
2950 @code{(boundp 'MULE)} is @code{t} on only MULE. Maybe the next version
|
|
|
2951 of Emacs will not have this symbol.
|
|
|
2952
|
|
|
2953 @item
|
|
|
2954 MULE has a variable @code{mule-version}. Perhaps the next version of
|
|
|
2955 Emacs will have this variable as well.
|
|
|
2956 @end itemize
|
|
|
2957
|
|
|
2958 Following is a sample to distinguish mule variants:
|
|
|
2959
|
|
|
2960 @lisp
|
|
|
2961 (if (featurep 'mule)
|
|
|
2962 (cond ((boundp 'MULE)
|
|
|
2963 ;; for original Mule
|
|
|
2964 )
|
|
440
|
2965 ((string-match "XEmacs" emacs-version)
|
|
|
2966 ;; for XEmacs with Mule
|
|
|
2967 )
|
|
|
2968 (t
|
|
|
2969 ;; for next version of Emacs
|
|
|
2970 ))
|
|
428
|
2971 ;; for old emacs variants
|
|
|
2972 )
|
|
|
2973 @end lisp
|
|
|
2974 @end quotation
|
|
|
2975
|
|
2537
|
2976 @node Q1.8.7, Q1.8.8, Q1.8.6, Introduction
|
|
|
2977 @unnumberedsubsec Q1.8.7: How about Cyrillic modes?
|
|
428
|
2978
|
|
|
2979 @email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes:
|
|
|
2980
|
|
|
2981 @quotation
|
|
|
2982 There is a cyrillic mode in the file @file{mysetup.zip} in
|
|
|
2983 @iftex
|
|
|
2984 @*
|
|
|
2985 @end iftex
|
|
|
2986 @uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}. This is a
|
|
|
2987 modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el}
|
|
|
2988 which can be obtained from
|
|
|
2989 @end quotation
|
|
|
2990
|
|
871
|
2991 @uref{http://www.math.uga.edu/~valery/russian.el}.
|
|
428
|
2992
|
|
|
2993 @email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes:
|
|
|
2994
|
|
|
2995 @quotation
|
|
|
2996 There is another cyrillic mode for both GNU Emacs and XEmacs by
|
|
|
2997 @email{manin@@camelot.mssm.edu, Dmitrii
|
|
|
2998 (Mitya) Manin} at
|
|
|
2999 @iftex
|
|
|
3000
|
|
|
3001 @end iftex
|
|
|
3002 @uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}.
|
|
|
3003 @c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead.
|
|
|
3004 @c Changed to russian host instead
|
|
|
3005 @end quotation
|
|
|
3006
|
|
|
3007 @email{rebecca.ore@@op.net, Rebecca Ore} writes:
|
|
|
3008
|
|
|
3009 @quotation
|
|
|
3010 The fullest resource I found on Russian language use (in and out of
|
|
661
|
3011 XEmacs) is @uref{http://www.ibiblio.org/sergei/Software/Software.html}
|
|
428
|
3012 @end quotation
|
|
|
3013
|
|
2537
|
3014 @node Q1.8.8, Q1.8.9, Q1.8.7, Introduction
|
|
|
3015 @unnumberedsubsec Q1.8.8: Does XEmacs support Unicode?
|
|
2417
|
3016
|
|
|
3017 To get Unicode support, you need a Mule-enabled XEmacs.
|
|
|
3018
|
|
|
3019 21.5 has internal support for Unicode and supports it fully, although we
|
|
|
3020 don't yet use it as the internal encoding.
|
|
|
3021
|
|
|
3022 21.4 supports Unicode partially -- as an external encoding for files,
|
|
2537
|
3023 processes, and terminals, but without font support. @xref{Q1.8.9, How
|
|
2417
|
3024 does XEmacs display Unicode?}. To get Unicode support in 21.4,
|
|
|
3025 install Mule-UCS from packages in the usual way, and put
|
|
745
|
3026
|
|
1616
|
3027 @example
|
|
745
|
3028 (require 'un-define)
|
|
|
3029 (set-coding-priority-list '(utf-8))
|
|
1616
|
3030 (set-coding-category-system 'utf-8 'utf-8)
|
|
|
3031 @end example
|
|
|
3032
|
|
|
3033 in your init file to enable the UTF-8 coding system. You may wish to
|
|
|
3034 view the documentation of @code{set-coding-priority-list} if you find
|
|
|
3035 that files that are not UTF-8 are being mis-recognized as UTF-8.
|
|
745
|
3036
|
|
2417
|
3037 Install standard national fonts (not Unicode fonts) for all character
|
|
2537
|
3038 sets you use. @xref{Q1.8.9, How does XEmacs display Unicode??}.
|
|
745
|
3039
|
|
|
3040 Mule-UCS also supports 16-bit forms of Unicode (UTF-16). It does not
|
|
|
3041 support 31-bit forms of Unicode (UTF-32 or UCS-4).
|
|
|
3042
|
|
2537
|
3043 @node Q1.8.9, , Q1.8.8, Introduction
|
|
|
3044 @unnumberedsubsec Q1.8.9: How does XEmacs display Unicode?
|
|
745
|
3045
|
|
|
3046 Mule doesn't have a Unicode charset internally, so there's nothing to
|
|
|
3047 bind a Unicode registry to. It would not be straightforward to create,
|
|
|
3048 either, because Unicode is not ISO 2022-compatible. You'd have to
|
|
|
3049 translate it to multiple 96x96 pages.
|
|
|
3050
|
|
|
3051 This means that Mule-UCS uses ordinary national fonts for display. This
|
|
|
3052 is not really a problem, except for those languages that use the Unified
|
|
|
3053 Han characters. The problem here is that Mule-UCS maps from Unicode
|
|
|
3054 code points to national character sets in a deterministic way. By
|
|
|
3055 default, this means that Japanese fonts are tried first, then Chinese,
|
|
|
3056 then Korean. To change the priority ordering, use the command
|
|
|
3057 `un-define-change-charset-order'.
|
|
|
3058
|
|
|
3059 It also means you can't use Unicode fonts directly, at least not without
|
|
|
3060 extreme hackery. You can run -nw with (set-terminal-coding-system
|
|
|
3061 'utf-8) if you really want a Unicode font for some reason.
|
|
|
3062
|
|
|
3063 Real Unicode support will be introduced in XEmacs 22.0.
|
|
|
3064
|
|
2459
|
3065 @node Installation, Editing, Introduction, Top
|
|
2417
|
3066 @unnumbered 2 Installation and Troubleshooting
|
|
428
|
3067
|
|
|
3068 This is part 2 of the XEmacs Frequently Asked Questions list. This
|
|
2417
|
3069 section is devoted to Installation, Maintenance and Troubleshooting.
|
|
428
|
3070
|
|
|
3071 @menu
|
|
2559
|
3072 2.0: Installation (General)
|
|
|
3073 * Q2.0.1:: How do I build and install XEmacs?
|
|
|
3074 * Q2.0.2:: Where do I find external libraries?
|
|
|
3075 * Q2.0.3:: How do I specify the paths that XEmacs uses for finding files?
|
|
|
3076 * Q2.0.4:: Running XEmacs without installing
|
|
|
3077 * Q2.0.5:: XEmacs is too big
|
|
|
3078
|
|
|
3079 2.1: Package Installation
|
|
|
3080 * Q2.1.1:: How do I install the packages?
|
|
|
3081 * Q2.1.2:: Can I install the packages individually?
|
|
|
3082 * Q2.1.3:: Can I install the packages automatically?
|
|
|
3083 * Q2.1.4:: Can I upgrade or remove packages?
|
|
|
3084 * Q2.1.5:: Which packages to install?
|
|
|
3085 * Q2.1.6:: Can you describe the package location process in more detail?
|
|
|
3086 * Q2.1.7:: EFS fails with "500 AUTH not understood"
|
|
|
3087
|
|
|
3088 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
|
3089 * Q2.2.1:: Libraries in non-standard locations
|
|
|
3090 * Q2.2.2:: Why can't I strip XEmacs?
|
|
|
3091
|
|
|
3092 2.3: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
3093 * Q2.3.1:: What exactly are all the different ways to build XEmacs under Windows?
|
|
|
3094 * Q2.3.2:: What compiler/libraries do I need to compile XEmacs?
|
|
|
3095 * Q2.3.3:: How do I compile the native port?
|
|
|
3096 * Q2.3.4:: What do I need for Cygwin?
|
|
|
3097 * Q2.3.5:: How do I compile under Cygwin?
|
|
|
3098 * Q2.3.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
|
3099 * Q2.3.7:: How do I compile with X support?
|
|
|
3100 * Q2.3.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
|
3101
|
|
|
3102 2.4: General Troubleshooting
|
|
|
3103 * Q2.4.1:: How do I deal with bugs or with problems building, installing, or running?
|
|
|
3104 * Q2.4.2:: Help! XEmacs just crashed on me!
|
|
|
3105 * Q2.4.3:: XEmacs crashes and I compiled it myself.
|
|
|
3106 * Q2.4.4:: How to debug an XEmacs problem with a debugger
|
|
|
3107 * Q2.4.5:: I get a cryptic error message when trying to do something.
|
|
|
3108 * Q2.4.6:: XEmacs hangs when I try to do something.
|
|
|
3109 * Q2.4.7:: I get an error message when XEmacs is running in batch mode.
|
|
|
3110 * Q2.4.8:: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
|
3111 * Q2.4.9:: @kbd{C-g} doesn't work for me. Is it broken?
|
|
|
3112 * Q2.4.10:: How do I debug process-related problems?
|
|
|
3113 * Q2.4.11:: XEmacs is outputting lots of X errors.
|
|
|
3114 * Q2.4.12:: After upgrading, XEmacs won't do `foo' any more!
|
|
|
3115
|
|
|
3116 2.5: Startup-Related Problems
|
|
|
3117 * Q2.5.1:: XEmacs cannot connect to my X Terminal!
|
|
|
3118 * Q2.5.2:: Startup problems related to paths or package locations.
|
|
|
3119 * Q2.5.3:: XEmacs won't start without network.
|
|
|
3120 * Q2.5.4:: Startup warnings about deducing proper fonts?
|
|
|
3121 * Q2.5.5:: Warnings from incorrect key modifiers.
|
|
|
3122 * Q2.5.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
428
|
3123 @end menu
|
|
|
3124
|
|
2559
|
3125 @unnumberedsec 2.0: Installation (General)
|
|
2417
|
3126
|
|
428
|
3127 @node Q2.0.1, Q2.0.2, Installation, Installation
|
|
2559
|
3128 @unnumberedsubsec Q2.0.1: How do I build and install XEmacs?
|
|
|
3129
|
|
|
3130 See the file @file{etc/NEWS} for information on new features and other
|
|
|
3131 user-visible changes since the last version of XEmacs.
|
|
|
3132
|
|
|
3133 The file @file{INSTALL} in the top-level directory says how to bring
|
|
|
3134 up XEmacs on Unix and Cygwin, once you have loaded the entire subtree
|
|
|
3135 of this directory.
|
|
|
3136
|
|
|
3137 See the file @file{nt/README} for instructions on building XEmacs for
|
|
|
3138 Microsoft Windows.
|
|
|
3139
|
|
|
3140 @xref{Q2.1.1}, for the installation of (essential) add on packages.
|
|
2417
|
3141
|
|
|
3142 @node Q2.0.2, Q2.0.3, Q2.0.1, Installation
|
|
2559
|
3143 @unnumberedsubsec Q2.0.2: Where do I find external libraries?
|
|
2417
|
3144
|
|
2459
|
3145 All external libraries used by XEmacs can be found on the XEmacs web
|
|
2417
|
3146 site
|
|
|
3147 @iftex
|
|
|
3148 @*
|
|
|
3149 @end iftex
|
|
2459
|
3150 @uref{http://www.xemacs.org/Download/optLibs.html}.
|
|
2417
|
3151
|
|
|
3152 The library versions available here are known to work with XEmacs.
|
|
|
3153 (Newer versions will probably work as well but we can't guarantee it.)
|
|
|
3154 We try to keep the libraries up-to-date but may not always succeed.
|
|
2459
|
3155 Check the above page for the canonical locations of the external libraries,
|
|
|
3156 allowing you to download the latest, bleeding-edge versions.
|
|
2417
|
3157
|
|
2559
|
3158 @node Q2.0.3, Q2.0.4, Q2.0.2, Installation
|
|
|
3159 @unnumberedsubsec Q2.0.3: How do I specify the paths that XEmacs uses for finding files?
|
|
2417
|
3160
|
|
|
3161 You can specify what paths to use by using a number of different flags
|
|
|
3162 when running configure. See the section MAKE VARIABLES in the top-level
|
|
|
3163 file INSTALL in the XEmacs distribution for a listing of those flags.
|
|
|
3164
|
|
|
3165 Most of the time, however, the simplest fix is: @strong{do not} specify
|
|
|
3166 paths as you might for GNU Emacs. XEmacs can generally determine the
|
|
|
3167 necessary paths dynamically at run time. The only path that generally
|
|
|
3168 needs to be specified is the root directory to install into. That can
|
|
|
3169 be specified by passing the @code{--prefix} flag to configure. For a
|
|
|
3170 description of the XEmacs install tree, please consult the @file{NEWS}
|
|
|
3171 file.
|
|
|
3172
|
|
2559
|
3173 @node Q2.0.4, Q2.0.5, Q2.0.3, Installation
|
|
|
3174 @unnumberedsubsec Q2.0.4: Running XEmacs without installing
|
|
442
|
3175
|
|
|
3176 How can I just try XEmacs without installing it?
|
|
428
|
3177
|
|
|
3178 XEmacs will run in place without requiring installation and copying of
|
|
|
3179 the Lisp directories, and without having to specify a special build-time
|
|
|
3180 flag. It's the copying of the Lisp directories that requires so much
|
|
|
3181 space. XEmacs is largely written in Lisp.
|
|
|
3182
|
|
|
3183 A good method is to make a shell alias for xemacs:
|
|
|
3184
|
|
|
3185 @example
|
|
2459
|
3186 alias xemacs=/src/xemacs-21.5/src/xemacs
|
|
428
|
3187 @end example
|
|
|
3188
|
|
|
3189 (You will obviously use whatever directory you downloaded the source
|
|
2459
|
3190 tree to instead of @file{/src/xemacs-21.5}).
|
|
428
|
3191
|
|
|
3192 This will let you run XEmacs without massive copying.
|
|
|
3193
|
|
2559
|
3194 @node Q2.0.5, Q2.1.1, Q2.0.4, Installation
|
|
|
3195 @unnumberedsubsec Q2.0.5: XEmacs is too big
|
|
428
|
3196
|
|
442
|
3197 The space required by the installation directories can be
|
|
428
|
3198 reduced dramatically if desired. Gzip all the .el files. Remove all
|
|
442
|
3199 the packages you'll never want to use. Remove the TexInfo manuals.
|
|
428
|
3200 Remove the Info (and use just hardcopy versions of the manual). Remove
|
|
|
3201 most of the stuff in etc. Remove or gzip all the source code. Gzip or
|
|
|
3202 remove the C source code. Configure it so that copies are not made of
|
|
1138
|
3203 the support lisp.
|
|
428
|
3204
|
|
|
3205 These are all Emacs Lisp source code and bytecompiled object code. You
|
|
|
3206 may safely gzip everything named *.el here. You may remove any package
|
|
|
3207 you don't use. @emph{Nothing bad will happen if you delete a package
|
|
|
3208 that you do not use}. You must be sure you do not use it though, so be
|
|
|
3209 conservative at first.
|
|
|
3210
|
|
1648
|
3211 Any package with the possible exceptions of xemacs-base, and EFS are
|
|
|
3212 candidates for removal. Ask yourself, @emph{Do I ever want to use this
|
|
|
3213 package?} If the answer is no, then it is a candidate for removal.
|
|
428
|
3214
|
|
|
3215 First, gzip all the .el files. Then go about package by package and
|
|
|
3216 start gzipping the .elc files. Then run XEmacs and do whatever it is
|
|
1648
|
3217 you normally do. If nothing bad happens, then remove the package. You
|
|
|
3218 can remove a package via the PUI interface
|
|
|
3219 (@code{M-x pui-list-packages}, then press @kbd{d} to mark the packages
|
|
|
3220 you wish to delete, and then @kbd{x} to delete them.
|
|
|
3221
|
|
|
3222 Another method is to do @code{M-x package-get-delete-package}.
|
|
428
|
3223
|
|
2559
|
3224 @unnumberedsec 2.1: Package Installation
|
|
|
3225
|
|
|
3226 @node Q2.1.1, Q2.1.2, Q2.0.5, Installation
|
|
|
3227 @unnumberedsubsec Q2.1.1: How do I install the packages?
|
|
|
3228
|
|
|
3229 There are three ways to install the packages.
|
|
|
3230
|
|
|
3231 @enumerate
|
|
|
3232 @item
|
|
|
3233 Manually, all at once, using the 'Sumo Tarball'.
|
|
|
3234 @item
|
|
|
3235 Manually, using individual package tarballs.
|
|
|
3236 @item
|
|
|
3237 Automatically, using the package tools from XEmacs.
|
|
|
3238 @end enumerate
|
|
|
3239
|
|
|
3240 If you don't want to mess with the packages, it is easiest to just
|
|
|
3241 grab them manually, all at once. (For the other two ways,
|
|
|
3242 @xref{Q2.1.2}, and @xref{Q2.1.3}.) Download the file
|
|
|
3243
|
|
|
3244 @file{xemacs-sumo.tar.gz}
|
|
|
3245
|
|
|
3246 For an XEmacs compiled with Mule you also need
|
|
|
3247
|
|
|
3248 @file{xemacs-mule-sumo.tar.gz}
|
|
|
3249
|
|
|
3250 These are in the @file{packages} directory on your XEmacs mirror
|
|
|
3251 archive: @uref{ftp://ftp.xemacs.org/pub/xemacs/packages} or its
|
|
|
3252 mirrors. N.B. They are called 'Sumo Tarballs' for good reason. They
|
|
|
3253 are currently about 19MB and 4.5MB (gzipped) respectively.
|
|
|
3254
|
|
|
3255 Install them on Unix and Mac OS X using the shell/Terminal command
|
|
|
3256
|
|
|
3257 @code{cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xf -}
|
|
|
3258
|
|
|
3259 Where @samp{$prefix} is what you gave to the @samp{--prefix} flag to
|
|
|
3260 @file{configure}, and defaults to @file{/usr/local}.
|
|
|
3261
|
|
|
3262 If you have GNU tar you can use:
|
|
|
3263
|
|
|
3264 @code{cd $prefix/lib/xemacs ; tar zxvf <tarballname>}
|
|
|
3265
|
|
|
3266 If you have the packages somewhere nonstandard and don't want to
|
|
|
3267 bother with @samp{$prefix} (for example, you're a developer and are
|
|
|
3268 compiling the packages yourself, and want your own private copy of
|
|
|
3269 everything), you can also directly specify this using @file{configure}.
|
|
|
3270 To do this under 21.5 and above use the @samp{--package-prefix} parameter
|
|
|
3271 to specify the directory under which you untarred the above tarballs.
|
|
|
3272 Under 21.4 and previous you need to use @samp{--package-path},
|
|
|
3273 something like this:
|
|
|
3274
|
|
|
3275 @example
|
|
|
3276 configure --package-path="~/.xemacs::/src/xemacs/site-packages:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages" ...
|
|
|
3277 @end example
|
|
|
3278
|
|
|
3279 Under Windows, you need to place the above @samp{tar.gz} files in the
|
|
|
3280 directory specified using the @samp{PACKAGE_PREFIX} value in
|
|
|
3281 @file{nt/config.inc} and by default is @file{\Program Files\XEmacs}.
|
|
|
3282 (To untar a @samp{tar.gz} file you will need to use a utility such as
|
|
|
3283 WinZip, unless you have Cygwin or a similar environment installed, in
|
|
|
3284 which case the above Unix shell command should work fine.) If you want
|
|
|
3285 the packages somewhere else, just change @samp{PACKAGE_PREFIX}.
|
|
|
3286
|
|
|
3287 Note that XEmacs finds the packages automatically anywhere underneath
|
|
|
3288 the directory tree where it expects to find the packages. All you
|
|
|
3289 need to do is put stuff there; you don't need to run any program to
|
|
|
3290 tell XEmacs to find the packges, or do anything of that sort.
|
|
|
3291
|
|
|
3292 However, XEmacs will only notice newly installed packages when it
|
|
|
3293 starts up, so you will have to restart if you are already running
|
|
|
3294 XEmacs.
|
|
|
3295
|
|
|
3296 For more details, @xref{Startup Paths,,,xemacs, the XEmacs User's
|
|
|
3297 Manual}, and @xref{Packages,,,xemacs, the XEmacs User's Manual}.
|
|
|
3298
|
|
|
3299 As the Sumo tarballs are not regenerated as often as the individual
|
|
|
3300 packages, it is recommended that you use the automatic package tools
|
|
|
3301 afterwards to pick up any recent updates.
|
|
|
3302
|
|
|
3303 @emph{NOTE}: For detailed information about how the package
|
|
|
3304 hierarchies work, @xref{Package Overview,,,lispref, the XEmacs Lisp
|
|
|
3305 Reference Manual}.
|
|
|
3306
|
|
|
3307 @node Q2.1.2, Q2.1.3, Q2.1.1, Installation
|
|
|
3308 @unnumberedsubsec Q2.1.2: Can I install the packages individually?
|
|
|
3309
|
|
|
3310 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.
|
|
|
3311
|
|
|
3312 Note: If you are upgrading packages already installed, it's best to
|
|
|
3313 remove the old package first (@pxref{Q2.1.4}).
|
|
|
3314
|
|
|
3315 For example if we are installing the @samp{xemacs-base}
|
|
|
3316 package (version 1.48):
|
|
|
3317
|
|
|
3318 @example
|
|
|
3319 mkdir $prefix/lib/xemacs/xemacs-packages RET # if it does not exist yet
|
|
|
3320 cd $prefix/lib/xemacs/xemacs-packages RET
|
|
|
3321 gunzip -c /path/to/xemacs-base-1.48-pkg.tar.gz | tar xvf - RET
|
|
|
3322 @end example
|
|
|
3323
|
|
|
3324 Or if you have GNU tar, the last step can be:
|
|
|
3325
|
|
|
3326 @example
|
|
|
3327 tar zxvf /path/to/xemacs-base-1.48-pkg.tar.gz RET
|
|
|
3328 @end example
|
|
|
3329
|
|
|
3330 For MULE related packages, it is best to untar into the @samp{mule-packages}
|
|
|
3331 hierarchy, i.e. for the @samp{mule-base} package, version 1.37:
|
|
|
3332
|
|
|
3333 @example
|
|
|
3334 mkdir $prefix/lib/xemacs/mule-packages RET # if it does not exist yet
|
|
|
3335 cd $prefix/lib/xemacs/mule-packages RET
|
|
|
3336 gunzip -c /path/to/mule-base-1.37-pkg.tar.gz | tar xvf - RET
|
|
|
3337 @end example
|
|
|
3338
|
|
|
3339 Or if you have GNU tar, the last step can be:
|
|
|
3340
|
|
|
3341 @example
|
|
|
3342 tar zxvf /path/to/mule-base-1.37-pkg.tar.gz RET
|
|
|
3343 @end example
|
|
|
3344
|
|
|
3345 @node Q2.1.3, Q2.1.4, Q2.1.2, Installation
|
|
|
3346 @unnumberedsubsec Q2.1.3: Can I install the packages automatically?
|
|
|
3347
|
|
|
3348 XEmacs comes with some tools to make the periodic updating and
|
|
|
3349 installing easier. It will notice if new packages or versions are
|
|
|
3350 available and will fetch them from the FTP site.
|
|
|
3351
|
|
|
3352 Unfortunately this requires that a few packages are already in place.
|
|
|
3353 You will have to install them by hand as above or use a SUMO tarball.
|
|
|
3354 This requirement will hopefully go away in the future. The packages
|
|
|
3355 you need are:
|
|
|
3356
|
|
|
3357 @example
|
|
|
3358 efs - To fetch the files from the FTP site or mirrors.
|
|
|
3359 xemacs-base - Needed by efs.
|
|
|
3360 @end example
|
|
|
3361
|
|
|
3362 and optionally:
|
|
|
3363
|
|
|
3364 @example
|
|
|
3365 mailcrypt - For PGP verification of the package-index file.
|
|
|
3366 @end example
|
|
|
3367
|
|
|
3368 After installing these by hand, fire up XEmacs and follow these
|
|
|
3369 steps.
|
|
|
3370
|
|
|
3371 @enumerate
|
|
|
3372 @item
|
|
|
3373 Choose a download site.
|
|
|
3374 @itemize @bullet
|
|
|
3375 @item
|
|
|
3376 via menu: Tools -> Packages -> Set Download Site
|
|
|
3377 @item
|
|
|
3378 via keyb: M-x customize-variable RET package-get-remote RET
|
|
|
3379 (put in the details of remote host and directory)
|
|
|
3380 @end itemize
|
|
|
3381
|
|
|
3382 If the package tarballs _AND_ the package-index file are in a
|
|
|
3383 local directory, you can: M-x pui-set-local-package-get-directory RET
|
|
|
3384
|
|
|
3385 @item
|
|
|
3386 Obtain a list of packages and display the list in a buffer named
|
|
|
3387 "*Packages*".
|
|
|
3388 @itemize @bullet
|
|
|
3389 @item
|
|
|
3390 menu: Tools -> Packages -> List & Install
|
|
|
3391 @item
|
|
|
3392 keyb: M-x pui-list-packages RET
|
|
|
3393 @end itemize
|
|
|
3394
|
|
|
3395 XEmacs will now connect to the remote site and download the
|
|
|
3396 latest package-index file.
|
|
|
3397
|
|
|
3398 The resulting buffer, "*Packages*" has brief instructions at the
|
|
|
3399 end of the buffer.
|
|
|
3400
|
|
|
3401 @item
|
|
|
3402 Choose the packages you wish to install.
|
|
|
3403 @itemize @bullet
|
|
|
3404 @item
|
|
|
3405 mouse: Click button 2 on the package name.
|
|
|
3406 @item
|
|
|
3407 keyb: RET on the package name
|
|
|
3408 @end itemize
|
|
|
3409
|
|
|
3410 @item
|
|
|
3411 Make sure you have everything you need.
|
|
|
3412 @itemize @bullet
|
|
|
3413 @item
|
|
|
3414 menu: Packages -> Add Required
|
|
|
3415 @item
|
|
|
3416 keyb: r
|
|
|
3417 @end itemize
|
|
|
3418
|
|
|
3419 XEmacs will now search for packages that are required by the
|
|
|
3420 ones that you have chosen to install and offer to select
|
|
|
3421 those packages also.
|
|
|
3422
|
|
|
3423 For novices and gurus alike, this step can save your bacon.
|
|
|
3424 It's easy to forget to install a critical package.
|
|
|
3425
|
|
|
3426 @item
|
|
|
3427 Download and install the packages.
|
|
|
3428 @itemize @bullet
|
|
|
3429 @item
|
|
|
3430 menu: Packages -> Install/Remove Selected
|
|
|
3431 @item
|
|
|
3432 keyb: x
|
|
|
3433 @end itemize
|
|
|
3434 @end enumerate
|
|
|
3435
|
|
|
3436 @node Q2.1.4, Q2.1.5, Q2.1.3, Installation
|
|
|
3437 @unnumberedsubsec Q2.1.4: Can I upgrade or remove packages?
|
|
|
3438
|
|
|
3439 As the exact files and their locations contained in a package may
|
|
|
3440 change it is recommended to remove a package first before installing a
|
|
|
3441 new version. In order to facilitate removal each package contains an
|
|
|
3442 pgkinfo/MANIFEST.pkgname file which list all the files belong to the
|
|
|
3443 package. M-x package-admin-delete-binary-package RET can be used to
|
|
|
3444 remove a package using this file.
|
|
|
3445
|
|
|
3446 Note that the interactive package tools included with XEmacs already do
|
|
|
3447 this for you.
|
|
|
3448
|
|
|
3449 @node Q2.1.5, Q2.1.6, Q2.1.4, Installation
|
|
|
3450 @unnumberedsubsec Q2.1.5: Which packages to install?
|
|
|
3451
|
|
|
3452 Unless you are an advanced user, just install everything.
|
|
|
3453
|
|
|
3454 If you really want to install only what's absolutely needed, a good
|
|
|
3455 minimal set of packages for XEmacs-latin1 would be
|
|
|
3456
|
|
|
3457 @example
|
|
|
3458 xemacs-base, xemacs-devel, c-support, cc-mode, debug, dired, efs,
|
|
|
3459 edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes,
|
|
|
3460 text-modes, time, mailcrypt
|
|
|
3461 @end example
|
|
|
3462
|
|
|
3463 If you are using the XEmacs package tools, don't forget to do:
|
|
|
3464
|
|
|
3465 @example
|
|
|
3466 Packages -> Add Required
|
|
|
3467 @end example
|
|
|
3468
|
|
|
3469 To make sure you have everything that the packages you have chosen to
|
|
|
3470 install need.
|
|
|
3471
|
|
|
3472 @xref{Q1.7.2}, for a description of the various packages.
|
|
|
3473
|
|
|
3474 @node Q2.1.6, Q2.1.7, Q2.1.5, Installation
|
|
|
3475 @unnumberedsubsec Q2.1.6: Can you describe the package location process in more detail?
|
|
|
3476
|
|
|
3477 On startup XEmacs looks for packages in so-called package hierarchies.
|
|
|
3478 Normally, there are three system wide hierarchies, like this:
|
|
|
3479
|
|
|
3480 @example
|
|
|
3481 $prefix/lib/xemacs/xemacs-packages/
|
|
|
3482 Normal packages go here.
|
|
|
3483
|
|
|
3484 $prefix/lib/xemacs/mule-packages/
|
|
|
3485 Mule packages go here and are only searched by MULE-enabled XEmacsen.
|
|
|
3486
|
|
|
3487 $prefix/lib/xemacs/site-packages/
|
|
|
3488 Local and 3rd party packages go here.
|
|
|
3489 @end example
|
|
|
3490
|
|
|
3491 This is what you get when you untar the SUMO tarballs under
|
|
|
3492 @file{$prefix/lib/xemacs}.
|
|
|
3493
|
|
|
3494 @file{$prefix} is specified using the @samp{--prefix} parameter to
|
|
|
3495 @file{configure}, and defaults to @file{usr/local}.
|
|
|
3496
|
|
|
3497 If the package path is not explicitly specified, XEmacs looks for the
|
|
|
3498 package directory @file{xemacs-packages} (and @file{mule-packages} and
|
|
|
3499 @file{site-packages}) first under @samp{~/.xemacs}, then for a sister
|
|
|
3500 directory @file{lib/xemacs-VERSION} of the directory in which the
|
|
|
3501 XEmacs executable is located, then for a sister directory
|
|
|
3502 @file{lib/xemacs}. The XEmacs executable (under Unix at least) is
|
|
|
3503 installed by default in @file{/usr/local/bin}; this explains why
|
|
|
3504 XEmacs in its default installation will find packages that you put
|
|
|
3505 under @file{/usr/local/lib/xemacs}.
|
|
|
3506
|
|
|
3507 You can specify where exactly XEmacs looks for packages by using the
|
|
|
3508 @samp{--package-prefix} or @samp{--package-path} parameters to
|
|
|
3509 @file{configure} (or the equivalent settings in @file{config.inc},
|
|
|
3510 under Windows), or setting the @samp{EMACSPACKAGEPATH} environment
|
|
|
3511 variable (which has the same format as @samp{--package-path}).
|
|
|
3512 @xref{Q2.1.1}.
|
|
|
3513
|
|
|
3514 See @file{configure.usage} for more info about the format of these
|
|
|
3515 @file{configure} parameters.
|
|
|
3516
|
|
|
3517 In addition to the system wide packages, each user can have his own
|
|
|
3518 packages installed under @file{~/.xemacs/}. If you want to install
|
|
|
3519 packages there using the interactive tools, you need to set
|
|
|
3520 @code{package-get-install-to-user-init-directory} to @code{t}.
|
|
|
3521
|
|
|
3522 The site-packages hierarchy replaces the old @file{site-lisp}
|
|
|
3523 directory. XEmacs no longer looks into a @file{site-lisp} directly by
|
|
|
3524 default. A good place to put @file{site-start.el} would be in
|
|
|
3525 @file{$prefix/lib/xemacs/site-packages/lisp/}.
|
|
|
3526
|
|
|
3527 @node Q2.1.7, Q2.2.1, Q2.1.6, Installation
|
|
|
3528 @unnumberedsubsec Q2.1.7: EFS fails with "500 AUTH not understood" (NEW)
|
|
2417
|
3529
|
|
|
3530 A typical error: FTP Error: USER request failed; 500 AUTH not understood.
|
|
|
3531
|
|
|
3532 Thanks to giacomo boffi @email{giacomo.boffi@@polimi.it} who recommends
|
|
|
3533 on comp.emacs.xemacs:
|
|
|
3534
|
|
|
3535 tell your ftp client to not attempt AUTH authentication (or do not
|
|
|
3536 use FTP servers that don't understand AUTH)
|
|
|
3537
|
|
|
3538 and notes that you need to add an element (often "-u") to
|
|
|
3539 `efs-ftp-program-args'. Use M-x customize-variable, and verify the
|
|
|
3540 needed flag with `man ftp' or other local documentation.
|
|
|
3541
|
|
2559
|
3542 @unnumberedsec 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
|
3543
|
|
|
3544 @node Q2.2.1, Q2.2.2, Q2.1.7, Installation
|
|
|
3545 @unnumberedsubsec Q2.2.1: Libraries in non-standard locations
|
|
428
|
3546
|
|
2459
|
3547 If your libraries are in a non-standard location, you can specify the location
|
|
|
3548 using the following flags to @file{configure}:
|
|
|
3549
|
|
|
3550 @example
|
|
|
3551 --site-libraries=WHATEVER
|
|
|
3552 --site-includes=WHATEVER
|
|
|
3553 @end example
|
|
|
3554
|
|
|
3555 If you have multiple paths to specify, use the following syntax:
|
|
428
|
3556
|
|
|
3557 @example
|
|
|
3558 --site-libraries='/path/one /path/two /path/etc'
|
|
|
3559 @end example
|
|
|
3560
|
|
2559
|
3561 @node Q2.2.2, Q2.3.1, Q2.2.1, Installation
|
|
|
3562 @unnumberedsubsec Q2.2.2: Why can't I strip XEmacs?
|
|
428
|
3563
|
|
|
3564 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:
|
|
|
3565
|
|
|
3566 @quotation
|
|
|
3567 Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The
|
|
|
3568 link gives you a bare-boned emacs (called temacs). temacs is then run,
|
|
|
3569 preloading some of the lisp files. The result is then dumped into a new
|
|
|
3570 executable, named xemacs, which will contain all of the preloaded lisp
|
|
|
3571 functions and data.
|
|
|
3572
|
|
|
3573 Now, during the dump itself, the executable (code+data+symbols) is
|
|
|
3574 written on disk using a special unexec() function. This function is
|
|
|
3575 obviously heavily system dependent. And on some systems, it leads to an
|
|
|
3576 executable which, although valid, cannot be stripped without damage. If
|
|
|
3577 memory serves, this is especially the case for AIX binaries. On other
|
|
462
|
3578 architectures it might work OK.
|
|
428
|
3579
|
|
|
3580 The Right Way to strip the emacs binary is to strip temacs prior to
|
|
|
3581 dumping xemacs. This will always work, although you can do that only if
|
|
|
3582 you install from sources (as temacs is @file{not} part of the binary
|
|
|
3583 kits).
|
|
|
3584 @end quotation
|
|
|
3585
|
|
|
3586 @email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes:
|
|
|
3587
|
|
|
3588 @quotation
|
|
|
3589 Here is the trick:
|
|
|
3590
|
|
|
3591 @enumerate
|
|
|
3592 @item
|
|
|
3593 [ ./configure; make ]
|
|
|
3594
|
|
|
3595 @item
|
|
|
3596 rm src/xemacs
|
|
|
3597
|
|
|
3598 @item
|
|
|
3599 strip src/temacs
|
|
|
3600
|
|
|
3601 @item
|
|
|
3602 make
|
|
|
3603
|
|
|
3604 @item
|
|
|
3605 cp src/xemacs /usr/local/bin/xemacs
|
|
|
3606
|
|
|
3607 @item
|
|
|
3608 cp lib-src/DOC-19.16-XEmacs
|
|
|
3609 @iftex
|
|
|
3610 \ @*
|
|
|
3611 @end iftex
|
|
|
3612 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
|
|
|
3613 @end enumerate
|
|
|
3614 @end quotation
|
|
|
3615
|
|
2559
|
3616 @unnumberedsec 2.3: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
3617
|
|
|
3618 @node Q2.3.1, Q2.3.2, Q2.2.2, Installation
|
|
|
3619 @unnumberedsubsec Q2.3.1: What exactly are all the different ways to build XEmacs under Windows?
|
|
2417
|
3620
|
|
|
3621 XEmacs can be built in several ways in the MS Windows environment.
|
|
|
3622
|
|
|
3623 The standard way is what we call the "native" port. It uses the Win32
|
|
|
3624 API and has no connection with X whatsoever -- it does not require X
|
|
|
3625 libraries to build, nor does it require an X server to run. The native
|
|
|
3626 port is the most reliable version and provides the best graphical
|
|
|
3627 support. Almost all development is geared towards this version, and
|
|
|
3628 there is little reason not to use it.
|
|
|
3629
|
|
|
3630 The second way to build is the Cygwin port. It takes advantage of
|
|
2537
|
3631 Cygnus emulation library under Win32. @xref{Q1.2.5, What are Cygwin
|
|
2417
|
3632 and MinGW, and do I need them to run XEmacs?}, for more information.
|
|
|
3633
|
|
|
3634 A third way is the MinGW port. It uses the Cygwin environment to
|
|
2537
|
3635 build but does not require it at runtime. @xref{Q1.2.5, What are
|
|
2417
|
3636 Cygwin and MinGW, and do I need them to run XEmacs?}, for more
|
|
|
3637 information.
|
|
|
3638
|
|
|
3639 Finally, you might also be able to build the non-Cygwin, non-MinGW "X"
|
|
|
3640 port. This was actually the first version of XEmacs that ran under MS
|
|
|
3641 Windows, and although the code is still in XEmacs, it's essentially
|
|
|
3642 orphaned and it's unlikely it will compile without a lot of work. If
|
|
|
3643 you want an MS Windows versin of XEmacs that supports X, use the Cygwin
|
|
|
3644 version. (The X support there is actively maintained, so that Windows
|
|
|
3645 developers can test the X support in XEmacs.)
|
|
|
3646
|
|
2559
|
3647 @node Q2.3.2, Q2.3.3, Q2.3.1, Installation
|
|
|
3648 @unnumberedsubsec Q2.3.2: What compiler/libraries do I need to compile XEmacs?
|
|
2417
|
3649
|
|
|
3650 You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have
|
|
|
3651 some beta testers currently trying to compile with VC.NET, aka version
|
|
|
3652 7.0, but we can't yet report complete success.) For the Cygwin and
|
|
|
3653 MinGW versions, you need the Cygwin environment, which comes with GCC,
|
|
2537
|
3654 the compiler used for those versions. @xref{Q1.2.5, What are Cygwin
|
|
2417
|
3655 and MinGW, and do I need them to run XEmacs?}, for more information on
|
|
|
3656 Cygwin and MinGW.
|
|
|
3657
|
|
2559
|
3658 @node Q2.3.3, Q2.3.4, Q2.3.2, Installation
|
|
|
3659 @unnumberedsubsec Q2.3.3: How do I compile the native port?
|
|
2417
|
3660
|
|
|
3661 Please read the file @file{nt/README} in the XEmacs distribution, which
|
|
|
3662 contains the full description.
|
|
|
3663
|
|
2559
|
3664 @node Q2.3.4, Q2.3.5, Q2.3.3, Installation
|
|
|
3665 @unnumberedsubsec Q2.3.4: What do I need for Cygwin?
|
|
2417
|
3666
|
|
|
3667 You can find the Cygwin tools and compiler at:
|
|
|
3668
|
|
|
3669 @uref{http://www.cygwin.com/}
|
|
|
3670
|
|
|
3671 Click on the @samp{Install or update now!} link, which will download a
|
|
|
3672 file @file{setup.exe}, which you can use to download everything
|
|
|
3673 else. (You will need to pick a mirror site; @samp{mirrors.rcn.net} is
|
|
|
3674 probably the best.) You should go ahead and install everything --
|
|
|
3675 you'll get various ancillary libraries that XEmacs needs or likes,
|
|
|
3676 e.g. XPM, PNG, JPEG, TIFF, etc. You can also get X Windows here, if you
|
|
|
3677 want to compile under X.
|
|
|
3678
|
|
|
3679 If you want to compile without X, you will need the @file{xpm-nox}
|
|
|
3680 library, which must be specifically selected in the Cygwin netinstaller;
|
|
|
3681 it is not selected by default. The package has had various names.
|
|
|
3682 Currently it is called @file{cygXpm-noX4.dll}.
|
|
|
3683
|
|
2559
|
3684 @node Q2.3.5, Q2.3.6, Q2.3.4, Installation
|
|
|
3685 @unnumberedsubsec Q2.3.5: How do I compile under Cygwin?
|
|
2417
|
3686
|
|
|
3687 Similar as on Unix; use the usual `configure' and `make' process.
|
|
|
3688 Some problems to watch out for:
|
|
|
3689
|
|
|
3690 @itemize @bullet
|
|
|
3691 @item
|
|
|
3692 make sure HOME is set. This controls where you
|
|
|
3693 @file{init.el} file comes from;
|
|
|
3694
|
|
|
3695 @item
|
|
|
3696 @samp{CYGWIN} needs to be set to @samp{tty} for process support to work;
|
|
|
3697
|
|
|
3698 @item
|
|
|
3699 picking up some other grep or other UNIX-like tools can kill configure;
|
|
|
3700
|
|
|
3701 @item
|
|
|
3702 static heap too small, adjust @file{src/sheap-adjust.h} to a more positive
|
|
|
3703 number;
|
|
|
3704
|
|
|
3705 @item
|
|
|
3706 (Unconfirmed) The Cygwin version doesn't understand
|
|
|
3707 @file{//machine/path} type paths so you will need to manually mount a
|
|
|
3708 directory of this form under a unix style directory for a build to work
|
|
|
3709 on the directory;
|
|
|
3710
|
|
|
3711 @item
|
|
|
3712 If you're building @strong{WITHOUT} X11, don't forget to change symlinks
|
|
|
3713 @file{/usr/lib/libXpm.a} and @file{/usr/lib/libXpm.dll.a} to point to
|
|
|
3714 the non-X versions of these libraries. By default they point to the X
|
|
|
3715 versions. So:
|
|
|
3716
|
|
|
3717 @example
|
|
|
3718 /usr/lib/libXpm.a -> /usr/lib/libXpm-noX.a
|
|
|
3719 /usr/lib/libXpm.dll.a -> /usr/lib/libXpm-noX.dll.a
|
|
|
3720 @end example
|
|
|
3721
|
|
|
3722 (This advice may now be obsolete because of the availability of the
|
|
|
3723 cygXpm-noX4.dll package from Cygwin. Send confirmation to
|
|
|
3724 @email{faq@@xemacs.org}.)
|
|
|
3725
|
|
|
3726 @item
|
|
|
3727 Other problems are listed in the @file{PROBLEMS} file, in the top-level
|
|
|
3728 directory of the XEmacs sources.
|
|
|
3729
|
|
|
3730 @end itemize
|
|
|
3731
|
|
|
3732
|
|
2559
|
3733 @node Q2.3.6, Q2.3.7, Q2.3.5, Installation
|
|
|
3734 @unnumberedsubsec Q2.3.6: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
2417
|
3735
|
|
|
3736 Similar to the method for Unix. Things to remember:
|
|
|
3737
|
|
|
3738 @itemize @bullet
|
|
|
3739 @item
|
|
|
3740 Specify the target host on the command line for @file{./configure}, e.g.
|
|
|
3741 @samp{./configure i586-pc-mingw32}.
|
|
|
3742
|
|
|
3743 @item
|
|
|
3744 Be sure that your build directory is mounted such that it has the
|
|
|
3745 same path either as a cygwin path (@file{/build/xemacs}) or as a Windows
|
|
|
3746 path (@file{c:\build\xemacs}).
|
|
|
3747
|
|
|
3748 @item
|
|
|
3749 Build @samp{gcc -mno-cygwin} versions of the extra libs, i.e. @file{libpng},
|
|
|
3750 @file{compface}, etc.
|
|
|
3751
|
|
|
3752 @item
|
|
|
3753 Specify the target location of the extra libs on the command line
|
|
|
3754 to @file{configure}, e.g.
|
|
|
3755 @samp{./configure --site-prefixes=/build/libs i586-pc-mingw32}.
|
|
|
3756 @end itemize
|
|
|
3757
|
|
2559
|
3758 @node Q2.3.7, Q2.3.8, Q2.3.6, Installation
|
|
|
3759 @unnumberedsubsec Q2.3.7: How do I compile with X support?
|
|
2417
|
3760
|
|
|
3761 To compile under Cygwin, all you need to do is install XFree86, which
|
|
|
3762 is available as part of the standard Cygwin installation.
|
|
|
3763 @uref{http://www.cygwin.com/}. Once installed, @file{configure}
|
|
|
3764 should automatically find the X libraries and compile with X support.
|
|
|
3765
|
|
|
3766 As noted above, the non-Cygwin X support is basically orphaned, and
|
|
|
3767 probably won't work. But if it want to try, it's described in
|
|
|
3768 @file{nt/README} in some detail. Basically, you need to get X11
|
|
2459
|
3769 libraries from @uref{http://ftp.x.org}, and compile them. If the
|
|
2417
|
3770 precompiled versions are available somewhere, we don't know of it.
|
|
|
3771
|
|
2559
|
3772 @node Q2.3.8, Q2.4.1, Q2.3.7, Installation
|
|
|
3773 @unnumberedsubsec Q2.3.8: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
1058
|
3774
|
|
|
3775 The Cygwin binary distributed with the netinstaller uses an external DLL
|
|
|
3776 to handle XPM images (such as toolbar buttons). You may get an error like
|
|
|
3777
|
|
2559
|
3778 @example
|
|
|
3779 This application has failed to start because cygXpm-noX4.dll was not found.
|
|
|
3780 Re-installing the application may fix this problem.
|
|
|
3781 @end example
|
|
1058
|
3782
|
|
|
3783 Andy Piper <andy@@xemacs.org> sez:
|
|
|
3784
|
|
2559
|
3785 @example
|
|
|
3786 cygXpm-noX4 is part of the cygwin distribution under libraries or
|
|
|
3787 graphics, but is not installed by default. You need to run the
|
|
|
3788 cygwin setup again and select this package.
|
|
|
3789 @end example
|
|
1058
|
3790
|
|
|
3791 Ie, reinstalling XEmacs won't help because it is not part of the XEmacs
|
|
|
3792 distribution.
|
|
|
3793
|
|
2559
|
3794 @unnumberedsec 2.4: General Troubleshooting
|
|
|
3795
|
|
|
3796 @node Q2.4.1, Q2.4.2, Q2.3.8, Installation
|
|
|
3797 @unnumberedsubsec Q2.4.1: How do I deal with bugs or with problems building, installing, or running?
|
|
|
3798
|
|
|
3799 The file @file{PROBLEMS} contains information on many common problems that
|
|
|
3800 occur in building, installing and running XEmacs.
|
|
|
3801
|
|
|
3802 Reports of bugs in XEmacs should be sent to
|
|
|
3803 @email{xemacs-beta@@xemacs.org}. You can also post to the newsgroup
|
|
|
3804 comp.emacs.xemacs (or equivalentlt, send to the mailing list
|
|
|
3805 @email{xemacs@@xemacs.org}), but it is less likely that the developers
|
|
|
3806 will see it in a timely fashion. @xref{Bugs,,, xemacs, the XEmacs
|
|
|
3807 User's Manual}, for more information on how to report bugs.
|
|
|
3808 @xref{Q1.4.2}, for more information on mailing lists relating to
|
|
|
3809 XEmacs.
|
|
|
3810
|
|
|
3811 There are three ways to read the Bugs section.
|
|
|
3812
|
|
|
3813 @enumerate
|
|
|
3814 @item
|
|
|
3815 In a printed copy of the XEmacs manual.
|
|
|
3816
|
|
|
3817 @item
|
|
|
3818 With Info. First, start XEmacs. From the menu, select
|
|
|
3819 @samp{Help->Info (Online Docs)->Info Contents} to enter Info, then
|
|
|
3820 click on @samp{XEmacs}, then on @samp{Bugs}. Or, use the keyboard: do
|
|
|
3821 @kbd{C-h i} to enter Info, then @kbd{m XEmacs RET} to get to the Emacs
|
|
|
3822 manual, then @kbd{m Bugs RET} to get to the section on bugs. Or use
|
|
|
3823 standalone Info in a like manner. (Standalone Info is part of the
|
|
|
3824 Texinfo distribution, not part of the XEmacs distribution.)
|
|
|
3825
|
|
|
3826 @item
|
|
|
3827 By hand. Do
|
|
|
3828 @example
|
|
|
3829 cat info/xemacs* | more "+/^File: xemacs.info, Node: Bugs,"
|
|
|
3830 @end example
|
|
|
3831 @end enumerate
|
|
|
3832
|
|
|
3833 @node Q2.4.2, Q2.4.3, Q2.4.1, Installation
|
|
|
3834 @unnumberedsubsec Q2.4.2: Help! XEmacs just crashed on me!
|
|
428
|
3835
|
|
|
3836 First of all, don't panic. Whenever XEmacs crashes, it tries extremely
|
|
|
3837 hard to auto-save all of your files before dying. (The main time that
|
|
|
3838 this will not happen is if the machine physically lost power or if you
|
|
|
3839 killed the XEmacs process using @code{kill -9}). The next time you try
|
|
|
3840 to edit those files, you will be informed that a more recent auto-save
|
|
|
3841 file exists. You can use @kbd{M-x recover-file} to retrieve the
|
|
|
3842 auto-saved version of the file.
|
|
|
3843
|
|
462
|
3844 You can use the command @kbd{M-x recover-session} after a crash to pick
|
|
|
3845 up where you left off.
|
|
428
|
3846
|
|
|
3847 Now, XEmacs is not perfect, and there may occasionally be times, or
|
|
|
3848 particular sequences of actions, that cause it to crash. If you can
|
|
|
3849 come up with a reproducible way of doing this (or even if you have a
|
|
|
3850 pretty good memory of exactly what you were doing at the time), the
|
|
2417
|
3851 maintainers would be very interested in knowing about it. The best
|
|
|
3852 way to report a bug is using @kbd{M-x report-emacs-bug} (or by
|
|
|
3853 selecting @samp{Send Bug Report...} from the Help menu). If that
|
|
|
3854 won't work (e.g. you can't get XEmacs working at all), send ordinary
|
|
|
3855 mail to @email{xemacs-beta@@xemacs.org}. @emph{MAKE SURE} to include
|
|
|
3856 the output from the crash, especially including the Lisp backtrace, as
|
|
|
3857 well as the XEmacs configuration from @kbd{M-x describe-installation}
|
|
|
3858 (or equivalently, the file @file{Installation} in the top of the build
|
|
|
3859 tree). Note that the developers do @emph{not} usually follow
|
|
|
3860 @samp{comp.emacs.xemacs} on a regular basis; thus, this is better for
|
|
|
3861 general questions about XEmacs than bug reports.
|
|
428
|
3862
|
|
1183
|
3863 If at all possible, include a C stack backtrace of the core dump that
|
|
2417
|
3864 was produced. This shows where exactly things went wrong, and makes
|
|
|
3865 it much easier to diagnose problems. To do this under Unix and Mac OS
|
|
|
3866 X, you need to locate the core file (it's called @file{core}, and is
|
|
|
3867 usually sitting in the directory that you started XEmacs from, or your
|
|
|
3868 home directory if that other directory was not writable). Then, go to
|
|
|
3869 that directory and execute a command like:
|
|
428
|
3870
|
|
|
3871 @example
|
|
|
3872 gdb `which xemacs` core
|
|
|
3873 @end example
|
|
|
3874
|
|
|
3875 and then issue the command @samp{where} to get the stack backtrace. You
|
|
|
3876 might have to use @code{dbx} or some similar debugger in place of
|
|
|
3877 @code{gdb}. If you don't have any such debugger available, complain to
|
|
|
3878 your system administrator.
|
|
|
3879
|
|
2417
|
3880 It's possible that a core file didn't get produced or the stack trace
|
|
|
3881 from gdb is garbage, in which case you're out of luck unless you can
|
|
|
3882 reproduce the bug. A nonexistent core file can happen in some
|
|
|
3883 circumstances on some operating systems, depending on what exactly
|
|
|
3884 triggered the crash. It's also possible, however, that your limits
|
|
|
3885 are set to turn them off. You may be able to reenable them using a
|
|
|
3886 command like @samp{unlimit coredumpsize} or @samp{ulimit -c}. (To find
|
|
|
3887 out how your limits are set, use the command @samp{limit}.) However, if
|
|
|
3888 you didn't explicitly set your limits this way, go complain to your
|
|
|
3889 system administrator and tell him not to disable core files by
|
|
|
3890 default.
|
|
|
3891
|
|
|
3892 A garbaged stack trace can happen for various reasons. Some versions
|
|
|
3893 of gdb are broken on certain operating systems and aren't able to read
|
|
|
3894 the core file. It's also possible that the stack got overwritten
|
|
|
3895 during the crash. A very simple reason, however, is that your version
|
|
|
3896 of XEmacs was compiled without debugging information or had the
|
|
|
3897 debugging information stripped. A compilation with optimization can
|
|
|
3898 also result in partly or completely garbaged stack trace. In such
|
|
|
3899 cases, you will need to recompile XEmacs with debugging information
|
|
2559
|
3900 and without optimization; @xref{Q2.4.4, How to debug an XEmacs problem
|
|
2417
|
3901 with a debugger}. Note also that core files currently don't work at
|
|
|
3902 all under Cygwin, and the only way to get a backtrace is to run XEmacs
|
|
|
3903 from gdb.
|
|
|
3904
|
|
|
3905 If you cannot get a backtrace from the core dump, but can reproduce
|
|
|
3906 the problem, try running XEmacs under gdb. The goal is to get clean C
|
|
|
3907 and Lisp backtraces and submit a bug report including full
|
|
|
3908 configuration information as described above, as this will greatly
|
|
|
3909 assist in the process of tracking down the bug. However, even partial
|
|
|
3910 information is better than none. The process of getting backtraces
|
|
2559
|
3911 from gdb is described in detail in @ref{Q2.4.4, How to debug an XEmacs
|
|
2417
|
3912 problem with a debugger}.
|
|
428
|
3913
|
|
1183
|
3914 If you're under Microsoft Windows, you're out of luck unless you happen
|
|
|
3915 to have a debugging aid installed on your system, for example Visual
|
|
|
3916 C++. In this case, the crash will result in a message giving you the
|
|
|
3917 option to enter a debugger (for example, by pressing @samp{Cancel}). Do
|
|
|
3918 this and locate the stack-trace window. (If your XEmacs was built
|
|
|
3919 without debugging information, the stack trace may not be very useful.)
|
|
|
3920
|
|
428
|
3921 When making a problem report make sure that:
|
|
|
3922
|
|
|
3923 @enumerate
|
|
|
3924 @item
|
|
|
3925 Report @strong{all} of the information output by XEmacs during the
|
|
|
3926 crash.
|
|
|
3927
|
|
|
3928 @item
|
|
2417
|
3929 You mention what O/S and Hardware you are running XEmacs on.
|
|
428
|
3930
|
|
|
3931 @item
|
|
|
3932 What version of XEmacs you are running.
|
|
|
3933
|
|
|
3934 @item
|
|
|
3935 What build options you are using.
|
|
|
3936
|
|
|
3937 @item
|
|
2417
|
3938 If the problem is related to graphics and you are running Unix or Mac
|
|
|
3939 OS X, we will also need to know what version of the X Window System
|
|
|
3940 you are running, and what window manager you are using.
|
|
1183
|
3941
|
|
|
3942 @item
|
|
|
3943 If the problem happened on a TTY, please include the terminal type.
|
|
2417
|
3944
|
|
|
3945 @item
|
|
|
3946 Try very hard to get both C and Lisp backtraces, as described above.
|
|
428
|
3947 @end enumerate
|
|
|
3948
|
|
1135
|
3949 Much of the information above is automatically generated by @kbd{M-x
|
|
|
3950 report-emacs-bug}. Even more, and often useful, information can be
|
|
|
3951 generated by redirecting the output of @code{make} and @code{make check}
|
|
|
3952 to a file (@file{beta.err} is the default used by @code{build-report}),
|
|
|
3953 and executing @kbd{M-x build-report}.
|
|
|
3954
|
|
2417
|
3955
|
|
2559
|
3956 @node Q2.4.3, Q2.4.4, Q2.4.2, Installation
|
|
|
3957 @unnumberedsubsec Q2.4.3: XEmacs crashes and I compiled it myself.
|
|
2417
|
3958
|
|
|
3959 There have been a variety of reports of crashes due to compilers with
|
|
|
3960 buggy optimizers. If you are compiling with optimization, consider
|
|
2559
|
3961 turning it off (@pxref{Q2.4.4, How to debug an XEmacs problem with a
|
|
2417
|
3962 debugger}) and recompiling.
|
|
|
3963
|
|
|
3964 Please see the @file{PROBLEMS} file that comes with XEmacs (it's in
|
|
|
3965 the top-level source directory) to read what it says about your
|
|
|
3966 platform.
|
|
|
3967
|
|
|
3968 If you compiled XEmacs using @samp{--use-union-type} (or the option
|
|
|
3969 @samp{USE_UNION_TYPE} in @file{config.inc} under Windows), try
|
|
|
3970 recompiling again without it. The union type has been known to trigger
|
|
|
3971 compiler errors in a number of cases.
|
|
|
3972
|
|
2559
|
3973 @node Q2.4.4, Q2.4.5, Q2.4.3, Installation
|
|
|
3974 @unnumberedsubsec Q2.4.4: How to debug an XEmacs problem with a debugger
|
|
428
|
3975
|
|
|
3976 If XEmacs does crash on you, one of the most productive things you can
|
|
|
3977 do to help get the bug fixed is to poke around a bit with the debugger.
|
|
|
3978 Here are some hints:
|
|
|
3979
|
|
|
3980 @itemize @bullet
|
|
|
3981 @item
|
|
|
3982 First of all, if the crash is at all reproducible, consider very
|
|
563
|
3983 strongly recompiling your XEmacs with debugging symbols and with no
|
|
|
3984 optimization (e.g. with GCC use the compiler flags @samp{-g -O0} --
|
|
|
3985 that's an "oh" followed by a zero), and with the configure options
|
|
2417
|
3986 @samp{--debug=yes} and @samp{--error-checking=all}. This will make
|
|
|
3987 your XEmacs run somewhat slower, but you are a lot more likely to
|
|
|
3988 catch the problem earlier (closer to its source). It makes it a lot
|
|
|
3989 easier to determine what's going on with a debugger. The way to
|
|
|
3990 control the compiler flags is with the configuration option
|
|
|
3991 @samp{--cflags}. If you have a recent version of 21.5, you should use
|
|
|
3992 @samp{--without-optimization} in preference to directly setting
|
|
|
3993 @samp{--cflags}.
|
|
1258
|
3994
|
|
|
3995 @item
|
|
|
3996 If it's not a true crash (@emph{i.e.}, XEmacs is hung, or a zombie
|
|
|
3997 process), or it's inconvenient to run XEmacs again because XEmacs is
|
|
|
3998 already running or is running in batch mode as part of a bunch of
|
|
|
3999 scripts, you may be able to attach to the existing process with your
|
|
2417
|
4000 debugger. Under Unix and Mac OS X, the typical way to do this is to
|
|
|
4001 first use some variant of the @samp{ps} command to figure out the
|
|
|
4002 process ID of XEmacs, for example @samp{ps -auxww | grep xemacs} under
|
|
|
4003 a BSD variant, @samp{ps -elf | grep xemacs} under Linux or System V,
|
|
|
4004 or @samp{ps -aW | grep xemacs} under Cygwin. Then run
|
|
|
4005
|
|
|
4006 @example
|
|
|
4007 gdb /path/to/xemacs/xemacs ####
|
|
|
4008 @end example
|
|
|
4009
|
|
|
4010 Where @code{####} is the process id of your XEmacs. (If you're not
|
|
|
4011 sure, try using @samp{which xemacs}.) When gdb attaches, the xemacs
|
|
|
4012 will stop and you can type @samp{where} in gdb to get a stack trace as
|
|
|
4013 usual. To get things moving again, you can just type @samp{quit} in
|
|
|
4014 gdb. It'll tell you the program is running and ask if you want to
|
|
|
4015 quit anyways. Say @samp{y} and it'll quit and have your emacs
|
|
|
4016 continue from where it was at.
|
|
|
4017
|
|
|
4018 If you're running another debugger, a similar method may work, or you
|
|
|
4019 may have to run the debugger first and then use the @code{attach}
|
|
|
4020 command or something similar.
|
|
|
4021
|
|
|
4022 Under Microsoft Windows, use the menu item @samp{Build->Start
|
|
|
4023 Debug->Attach to Process...} and select the XEmacs process from the list
|
|
|
4024 given.
|
|
1258
|
4025
|
|
|
4026 @item
|
|
|
4027 If you're able to run XEmacs under a debugger and reproduce the crash,
|
|
|
4028 here are some things you can do:
|
|
428
|
4029
|
|
|
4030 @item
|
|
|
4031 If XEmacs is hitting an assertion failure, put a breakpoint on
|
|
|
4032 @code{assert_failed()}.
|
|
|
4033
|
|
|
4034 @item
|
|
|
4035 If XEmacs is hitting some weird Lisp error that's causing it to crash
|
|
|
4036 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is
|
|
2417
|
4037 declared static in @file{eval.c}.
|
|
428
|
4038
|
|
|
4039 @item
|
|
563
|
4040 If XEmacs is outputting lots of X errors, put a breakpoint on
|
|
2417
|
4041 @code{x_error_handler()}; that will tell you which call is causing
|
|
|
4042 them. Note that the result may not be very useful by default because
|
|
|
4043 X Windows normally operates asynchronously: A bunch of commands are
|
|
|
4044 buffered up and then sent to the server all at once. This greatly
|
|
|
4045 improves performance over a network but means that an error may not be
|
|
|
4046 reported until the server receives the commands, which can be long
|
|
|
4047 after XEmacs made the erroneous calls. For best results, you need to
|
|
|
4048 make the X server synchronous before getting the backtrace. This can
|
|
|
4049 be done by starting XEmacs with the @samp{-sync} option or executing
|
|
|
4050 the Lisp code @code{(x-debug-mode t)}.
|
|
563
|
4051
|
|
|
4052 @item
|
|
428
|
4053 Internally, you will probably see lots of variables that hold objects of
|
|
1258
|
4054 type @code{Lisp_Object}. These are references to Lisp objects.
|
|
|
4055 Printing them out with the debugger probably won't be too
|
|
|
4056 useful---you'll likely just see a number. To decode them, do this:
|
|
428
|
4057
|
|
|
4058 @example
|
|
2417
|
4059 call debug_print (OBJECT)
|
|
428
|
4060 @end example
|
|
|
4061
|
|
|
4062 where @var{OBJECT} is whatever you want to decode (it can be a variable,
|
|
1258
|
4063 a function call, etc.). This uses the Lisp printing routines to out a
|
|
|
4064 readable representation on the TTY from which the xemacs process was
|
|
|
4065 invoked.
|
|
428
|
4066
|
|
2417
|
4067 Under 21.5 and later, @code{dp} is defined as an easier-to-type equivalent
|
|
|
4068 of @code{debug_print}. You can also try @code{dpa} if you can't see
|
|
|
4069 the output from @code{debug_print} (this will return a string containing
|
|
|
4070 the output), or use @code{debug_p3} if @code{debug_print} itself triggers
|
|
|
4071 a crash (this is a less comprehensive but super-safe way to print out
|
|
|
4072 a Lisp object).
|
|
|
4073
|
|
428
|
4074 @item
|
|
|
4075 If you want to get a Lisp backtrace showing the Lisp call
|
|
|
4076 stack, do this:
|
|
|
4077
|
|
|
4078 @example
|
|
2417
|
4079 call debug_backtrace ()
|
|
428
|
4080 @end example
|
|
|
4081
|
|
2417
|
4082 Under 21.5 and later, @code{db} is defined as an easier-to-type equivalent
|
|
|
4083 of @code{debug_backtrace}.
|
|
|
4084
|
|
|
4085 @item
|
|
|
4086 Using @code{debug_print} and @code{debug_backtrace} has two
|
|
|
4087 disadvantages - they can only be used with a running (including hung
|
|
|
4088 or zombie) xemacs process, and they do not display the internal C
|
|
|
4089 structure of a Lisp Object. Even if all you've got is a core dump,
|
|
|
4090 all is not lost.
|
|
428
|
4091
|
|
|
4092 If you're using GDB, there are some macros in the file
|
|
438
|
4093 @file{src/.gdbinit} in the XEmacs source distribution that should make
|
|
|
4094 it easier for you to decode Lisp objects. This file is automatically
|
|
|
4095 read by gdb if gdb is run in the directory where xemacs was built, and
|
|
|
4096 contains these useful macros to inspect the state of xemacs:
|
|
|
4097
|
|
|
4098 @table @code
|
|
|
4099 @item pobj
|
|
|
4100 Usage: pobj lisp_object @*
|
|
|
4101 Print the internal C representation of a lisp object.
|
|
|
4102
|
|
|
4103 @item xtype
|
|
|
4104 Usage: xtype lisp_object @*
|
|
|
4105 Print the Lisp type of a lisp object.
|
|
|
4106
|
|
|
4107 @item lbt
|
|
|
4108 Usage: lbt @*
|
|
|
4109 Print the current Lisp stack trace.
|
|
1258
|
4110 Requires a running xemacs process. (It works by calling the db
|
|
|
4111 routine described above.)
|
|
438
|
4112
|
|
|
4113 @item ldp
|
|
|
4114 Usage: ldp lisp_object @*
|
|
|
4115 Print a Lisp Object value using the Lisp printer.
|
|
1258
|
4116 Requires a running xemacs process. (It works by calling the dp
|
|
|
4117 routine described above.)
|
|
438
|
4118
|
|
|
4119 @item run-temacs
|
|
|
4120 Usage: run-temacs @*
|
|
|
4121 Run temacs interactively, like xemacs.
|
|
|
4122 Use this with debugging tools (like purify) that cannot deal with dumping,
|
|
|
4123 or when temacs builds successfully, but xemacs does not.
|
|
|
4124
|
|
|
4125 @item dump-temacs
|
|
|
4126 Usage: dump-temacs @*
|
|
|
4127 Run the dumping part of the build procedure.
|
|
|
4128 Use when debugging temacs, not xemacs!
|
|
|
4129 Use this when temacs builds successfully, but xemacs does not.
|
|
|
4130
|
|
|
4131 @item check-xemacs
|
|
|
4132 Usage: check-xemacs @*
|
|
|
4133 Run the test suite. Equivalent to 'make check'.
|
|
|
4134
|
|
|
4135 @item check-temacs
|
|
|
4136 Usage: check-temacs @*
|
|
|
4137 Run the test suite on temacs. Equivalent to 'make check-temacs'.
|
|
|
4138 Use this with debugging tools (like purify) that cannot deal with dumping,
|
|
|
4139 or when temacs builds successfully, but xemacs does not.
|
|
|
4140 @end table
|
|
428
|
4141
|
|
|
4142 If you are using Sun's @file{dbx} debugger, there is an equivalent file
|
|
438
|
4143 @file{src/.dbxrc}, which defines the same commands for dbx.
|
|
428
|
4144
|
|
|
4145 @item
|
|
|
4146 If you're using a debugger to get a C stack backtrace and you're seeing
|
|
|
4147 stack traces with some of the innermost frames mangled, it may be due to
|
|
|
4148 dynamic linking. (This happens especially under Linux.) Consider
|
|
|
4149 reconfiguring with @samp{--dynamic=no}. Also, sometimes (again under
|
|
|
4150 Linux), stack backtraces of core dumps will have the frame where the
|
|
|
4151 fatal signal occurred mangled; if you can obtain a stack trace while
|
|
|
4152 running the XEmacs process under a debugger, the stack trace should be
|
|
|
4153 clean.
|
|
|
4154
|
|
1183
|
4155 @email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so
|
|
|
4156 version 1.8 if dynamic linking and debugging is a problem on Linux.
|
|
428
|
4157
|
|
|
4158 @item
|
|
|
4159 If you're using a debugger to get a C stack backtrace and you're
|
|
|
4160 getting a completely mangled and bogus stack trace, it's probably due to
|
|
|
4161 one of the following:
|
|
|
4162
|
|
|
4163 @enumerate a
|
|
|
4164 @item
|
|
|
4165 Your executable has been stripped. Bad news. Tell your sysadmin not to
|
|
|
4166 do this---it doesn't accomplish anything except to save a bit of disk
|
|
|
4167 space, and makes debugging much much harder.
|
|
|
4168
|
|
|
4169 @item
|
|
|
4170 Your stack is getting trashed. Debugging this is hard; you have to do a
|
|
|
4171 binary-search type of narrowing down where the crash occurs, until you
|
|
|
4172 figure out exactly which line is causing the problem. Of course, this
|
|
1258
|
4173 only works if the bug is highly reproducible. Also, in many cases if
|
|
|
4174 you run XEmacs from the debugger, the debugger can protect the stack
|
|
|
4175 somewhat. However, if the stack is being smashed, it is typically the
|
|
|
4176 case that there is a wild pointer somewhere in the program, often quite
|
|
|
4177 far from where the crash occurs.
|
|
428
|
4178
|
|
|
4179 @item
|
|
|
4180 If your stack trace has exactly one frame in it, with address 0x0, this
|
|
|
4181 could simply mean that XEmacs attempted to execute code at that address,
|
|
|
4182 e.g. through jumping to a null function pointer. Unfortunately, under
|
|
|
4183 those circumstances, GDB under Linux doesn't know how to get a stack
|
|
1183
|
4184 trace. (Yes, this is the fourth Linux-related problem I've mentioned. I
|
|
428
|
4185 have no idea why GDB under Linux is so bogus. Complain to the GDB
|
|
1183
|
4186 authors, or to comp.os.linux.development.system.) Again, you'll have to
|
|
428
|
4187 use the narrowing-down process described above.
|
|
|
4188
|
|
|
4189 @item
|
|
462
|
4190 You will get a Lisp backtrace output when XEmacs crashes, so you'll have
|
|
|
4191 something useful.
|
|
428
|
4192
|
|
|
4193 @end enumerate
|
|
|
4194
|
|
|
4195 @item
|
|
|
4196 If you compile with the newer gcc variants gcc-2.8 or egcs, you will
|
|
438
|
4197 also need gdb 4.17 or above. Earlier releases of gdb can't handle the
|
|
|
4198 debug information generated by the newer compilers.
|
|
428
|
4199
|
|
|
4200 @item
|
|
438
|
4201 In versions of XEmacs before 21.2.27, @file{src/.gdbinit} was named
|
|
|
4202 @file{src/gdbinit}. This had the disadvantage of not being sourced
|
|
|
4203 automatically by gdb, so you had to set that up yourself.
|
|
428
|
4204
|
|
1183
|
4205 @item
|
|
|
4206 If you are running Microsoft Windows, the the file @file{nt/README} for
|
|
|
4207 further information about debugging XEmacs.
|
|
|
4208
|
|
428
|
4209 @end itemize
|
|
|
4210
|
|
2559
|
4211 @node Q2.4.5, Q2.4.6, Q2.4.4, Installation
|
|
|
4212 @unnumberedsubsec Q2.4.5: I get a cryptic error message when trying to do something.
|
|
2417
|
4213
|
|
|
4214 When I try to use some particular option of some particular package, I
|
|
|
4215 get a cryptic error message in the minibuffer.
|
|
|
4216
|
|
|
4217 If the message went by too quickly, use @samp{Help->Recent Messages}
|
|
|
4218 from the menubar (or type @kbd{C-h l}) to see recent messages.
|
|
|
4219
|
|
|
4220 If you can't figure out what's going on, select
|
|
|
4221 @samp{Options->Troubleshooting->Debug on Error} from the menubar (or
|
|
|
4222 type @kbd{M-:} then @kbd{(setq debug-on-error t)}) then try and make
|
|
|
4223 the error happen again. This will put in the debugger (you can get
|
|
|
4224 out of this and continue what you were doing before by typing @kbd{c})
|
|
|
4225 and give you a backtrace that may be enlightening. If not, try
|
|
|
4226 reading through this FAQ; if that fails, you could try posting to
|
|
|
4227 @samp{comp.emacs.xemacs} (making sure to include the backtrace) and
|
|
|
4228 someone may be able to help. If you can identify which XEmacs Lisp
|
|
|
4229 source file the error is coming from you can get a more detailed stack
|
|
|
4230 backtrace by doing the following:
|
|
428
|
4231
|
|
|
4232 @enumerate
|
|
|
4233 @item
|
|
2417
|
4234 Visit the .el file in an XEmacs buffer.
|
|
|
4235
|
|
|
4236 @item
|
|
|
4237 Issue the command @kbd{M-x eval-current-buffer}.
|
|
|
4238
|
|
|
4239 @item
|
|
|
4240 Reproduce the error.
|
|
428
|
4241 @end enumerate
|
|
|
4242
|
|
2417
|
4243 For more information on debugging Lisp code, @xref{Debugging,,,
|
|
|
4244 lispref, XEmacs Lisp Reference Manual}.
|
|
|
4245
|
|
2559
|
4246 @node Q2.4.6, Q2.4.7, Q2.4.5, Installation
|
|
|
4247 @unnumberedsubsec Q2.4.6: XEmacs hangs when I try to do something.
|
|
2417
|
4248
|
|
|
4249 XEmacs might just be slow; some operations take a long time. XEmacs
|
|
|
4250 may also be waiting on a response from the network, for example when
|
|
|
4251 you are trying to send mail.
|
|
|
4252
|
|
|
4253 You can usually interrupt XEmacs by typing @kbd{C-g}. If not (for
|
|
|
4254 example, Lisp code explicitly disabled this by setting
|
|
|
4255 @code{inhibit-quit}), you can use the "critical quit" mechanism by
|
|
|
4256 typing @kbd{Control-Shift-G}. This should also pop you into the
|
|
|
4257 debugger and give you a backtrace, which can tell you where the
|
|
2559
|
4258 problem is (@pxref{Q2.4.4, How to debug an XEmacs problem with a
|
|
2417
|
4259 debugger}). (Note that setting @code{debug-on-quit} or selecting
|
|
|
4260 @samp{Options->Troubleshooting->Debug on Quit} will also cause regular
|
|
|
4261 @kbd{C-g} to enter the debugger and give you a backtrace.)
|
|
|
4262
|
|
|
4263 If you can't interrupt XEmacs this way, or for some reason XEmacs is
|
|
|
4264 not talking to the keyboard, you can try sending the @samp{SIGINT}
|
|
|
4265 signal using the @samp{kill} command.
|
|
|
4266
|
|
|
4267 If the Lisp backtrace isn't enlightening, or if XEmacs is so hung that
|
|
|
4268 you can't interrupt it at all, you could try attaching to the process
|
|
2559
|
4269 and getting a C stack backtrace. @xref{Q2.4.4, How to debug an XEmacs
|
|
2417
|
4270 problem with a debugger}.
|
|
|
4271
|
|
2559
|
4272 @node Q2.4.7, Q2.4.8, Q2.4.6, Installation
|
|
|
4273 @unnumberedsubsec Q2.4.7: I get an error message when XEmacs is running in batch mode.
|
|
2417
|
4274
|
|
|
4275 Typically this happens when you are trying to compile some Elisp code.
|
|
|
4276 If you are doing this as part of XEmacs or the XEmacs packages, you
|
|
|
4277 should automatically get a backtrace, which can help you determine the
|
|
|
4278 source of the problem. In other cases, you can get equivalent results
|
|
|
4279 by setting the environment variable @samp{XEMACSDEBUG} to @samp{(setq
|
|
|
4280 stack-trace-on-error t load-always-display-messages t
|
|
|
4281 load-ignore-out-of-date-elc-files t load-show-full-path-in-messages
|
|
|
4282 t)} (this needs to be all on one line; to set an environment variable,
|
|
|
4283 use @samp{export XEMACSDEBUG='FOO'} under @samp{bash}, @samp{zsh},
|
|
|
4284 etc. or @samp{setenv XEMACSDEBUG 'FOO'} under @samp{csh} and
|
|
|
4285 @samp{tcsh}). @samp{XEMACSDEBUG} specifies Lisp code that will be
|
|
|
4286 executed at startup time.
|
|
|
4287
|
|
|
4288 If the backtrace is not sufficiently useful in helping you diagnose
|
|
|
4289 the problem, you should consider using a debugger such as GDB.
|
|
2559
|
4290 @xref{Q2.4.4, How to debug an XEmacs problem with a debugger}. You
|
|
2417
|
4291 probably want to set a breakpoint on @code{signal_1}. Since such
|
|
|
4292 errors often occur during compiling, which is often triggered by a
|
|
|
4293 complex command run from a make suite, it may be easier to attach to
|
|
|
4294 the process once it's running.
|
|
|
4295
|
|
|
4296 Under Microsoft Windows (and perhaps other operating systems), there
|
|
|
4297 is another useful trick you can do if you have configured with
|
|
|
4298 debugging support (configure option @samp{--debug} or setting
|
|
|
4299 @samp{DEBUG_XEMACS} in @file{nt/config.inc}). Set the environment
|
|
|
4300 variable @samp{XEMACSDEBUG} (as described above) to @samp{(setq
|
|
|
4301 debug-on-error t)}. Then, when an error occurs noninteractively,
|
|
|
4302 instead of trying to invoke the Lisp debugger (which obviously won't
|
|
|
4303 work), XEmacs will break out to a C debugger using
|
|
|
4304 @code{(force-debugging-signal t)}. @emph{NOTE}: This runs
|
|
|
4305 @code{abort()}!!! (As well as and after executing INT 3 under MS
|
|
|
4306 Windows, which should invoke a debugger if it's active.) This is
|
|
|
4307 guaranteed to kill XEmacs! (But in this situation, XEmacs is about to
|
|
|
4308 die anyway, and if no debugger is present, this will usefully dump
|
|
|
4309 core.)
|
|
|
4310
|
|
2559
|
4311 @node Q2.4.8, Q2.4.9, Q2.4.7, Installation
|
|
|
4312 @unnumberedsubsec Q2.4.8: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
2417
|
4313
|
|
|
4314 XEmacs has various facilities for debugging event handling.
|
|
|
4315
|
|
|
4316 First, try setting the variable @code{debug-emacs-events} to non-zero.
|
|
|
4317 This will output various information showing which events are being
|
|
|
4318 received and how they are being translated. This may show you, for
|
|
|
4319 example, that a key command is getting intercepted using
|
|
|
4320 @code{key-translation-map}; this problem can otherwise be very tricky
|
|
|
4321 to debug.
|
|
|
4322
|
|
|
4323 Under X, you can see exactly which events are being received from the
|
|
|
4324 window system by setting @code{x-debug-events} to non-zero. (The value
|
|
|
4325 @samp{1} gives you regular output, and @samp{2} gives you verbose
|
|
|
4326 output, including all parameters.)
|
|
|
4327
|
|
|
4328 A similar facility exists under MS Windows: Set
|
|
|
4329 @code{debug-mswindows-events} to non-zero. (The value @samp{1} gives
|
|
|
4330 you regular output. The value @samp{2} gives you verbose output,
|
|
|
4331 including all parameters. The value @samp{3} gives you
|
|
|
4332 super-gorily-detailed output.)
|
|
|
4333
|
|
2559
|
4334 @node Q2.4.9, Q2.4.10, Q2.4.8, Installation
|
|
|
4335 @unnumberedsubsec Q2.4.9: @kbd{C-g} doesn't work for me. Is it broken?
|
|
2417
|
4336
|
|
|
4337 @kbd{C-g} does work for most people in most circumstances. If it
|
|
|
4338 doesn't, there are two possible explanations:
|
|
|
4339
|
|
|
4340 @enumerate
|
|
|
4341 @item
|
|
|
4342 XEmacs is hung in a way that prevents @kbd{C-g} from working. This
|
|
|
4343 can happen when code is wrapped with a binding of @code{inhibit-quit}
|
|
|
4344 to @code{t}; you should still be able interrupt XEmacs using "critical
|
|
|
4345 quit". On the other hand, XEmacs may be seriously wedged. (If you're
|
|
|
4346 lucky, sending @samp{SIGINT} to the XEmacs process will interrupt it.)
|
|
2559
|
4347 @xref{Q2.4.6, XEmacs hangs when I try to do something.}.
|
|
2417
|
4348
|
|
|
4349 @item
|
|
|
4350 @kbd{C-g} is indeed broken on your system. To test, try executing
|
|
|
4351 @code{(while t)} from the @samp{*scratch*} buffer. If @kbd{C-g}
|
|
|
4352 doesn't interrupt, then it's broken. This used to happen with systems
|
|
|
4353 where @samp{SIGIO} was broken, but @samp{BROKEN_SIGIO} wasn't defined.
|
|
|
4354 However, there may not be very many such systems nowadays.
|
|
|
4355 @end enumerate
|
|
|
4356
|
|
2559
|
4357 @node Q2.4.10, Q2.4.11, Q2.4.9, Installation
|
|
|
4358 @unnumberedsubsec Q2.4.10: How do I debug process-related problems?
|
|
2417
|
4359
|
|
|
4360 Under MS Windows, you can set the variable
|
|
|
4361 @code{debug-mswindows-process-command-lines} to non-@samp{nil} to get
|
|
|
4362 information on exactly what is getting passed to a process. This can
|
|
|
4363 be useful in determining problems with quoting. (Under Unix, a process
|
|
|
4364 receives each argument separately, but under MS Windows a single
|
|
|
4365 command line is received, and arguments with spaces or other special
|
|
|
4366 characters in them must be quoted. Unfortunately this means that each
|
|
|
4367 process, potentially at least, has its own quoting conventions, and
|
|
|
4368 the code to process quoting conventions in @file{cmd.exe}, the Visual
|
|
|
4369 C++ startup code and the like is baroque and poorly documented.
|
|
|
4370 XEmacs uses the variable
|
|
|
4371 @code{mswindows-construct-process-command-line-alist} to construct a
|
|
|
4372 command line from a list of arguments based on the command to be run,
|
|
|
4373 but it is (and cannot be) a perfect solution.)
|
|
|
4374
|
|
2559
|
4375 @node Q2.4.11, Q2.4.12, Q2.4.10, Installation
|
|
|
4376 @unnumberedsubsec Q2.4.11: XEmacs is outputting lots of X errors.
|
|
563
|
4377
|
|
|
4378 If this is happening, we would very much like to know what's causing
|
|
2559
|
4379 them. To find this out, see @ref{Q2.4.4, How to debug an XEmacs
|
|
2417
|
4380 problem with a debugger}. Try to get both a C and Lisp backtrace, and
|
|
|
4381 send them along with the full error output to
|
|
|
4382 @email{xemacs-beta@@xemacs.org}.
|
|
|
4383
|
|
2559
|
4384 @node Q2.4.12, Q2.5.1, Q2.4.11, Installation
|
|
|
4385 @unnumberedsubsec Q2.4.12: After upgrading, XEmacs won't do `foo' any more!
|
|
2417
|
4386
|
|
|
4387 You have been used to doing `foo', but now when you invoke it (or
|
|
|
4388 click the toolbar button or select the menu item), nothing (or an
|
|
|
4389 error) happens. The simplest explanation is that you are missing a
|
|
|
4390 package that is essential to you. You can either track it down and
|
|
|
4391 install it (there is a list of packages and brief descriptions of
|
|
|
4392 their contents in @file{etc/PACKAGES}), or install the `Sumo Tarball'
|
|
2559
|
4393 (@pxref{Q2.1.2, How do I figure out which packages to install?}).
|
|
2417
|
4394
|
|
|
4395 @c #### should xref to XEmacs manual here
|
|
|
4396
|
|
2559
|
4397 @unnumberedsec 2.5: Startup-Related Problems
|
|
|
4398
|
|
|
4399 @node Q2.5.1, Q2.5.2, Q2.4.12, Installation
|
|
|
4400 @unnumberedsubsec Q2.5.1: XEmacs cannot connect to my X Terminal!
|
|
2417
|
4401
|
|
|
4402 Help! I can not get XEmacs to display on my Envizex X-terminal!
|
|
|
4403
|
|
|
4404 Try setting the @code{DISPLAY} variable using the numeric IP address of
|
|
|
4405 the host you are running XEmacs from.
|
|
|
4406
|
|
2559
|
4407 @node Q2.5.2, Q2.5.3, Q2.5.1, Installation
|
|
|
4408 @unnumberedsubsec Q2.5.2 Startup problems related to paths or package locations.
|
|
|
4409
|
|
|
4410 First of all, if XEmacs can't find the packages, check to make sure
|
|
|
4411 that you put the packages in the right place, or that you told XEmacs
|
|
|
4412 where to look for the packages when you compiled it. @xref{Q2.1.1}.
|
|
|
4413
|
|
|
4414 If something is still going wrong, or you get a startup warning about
|
|
|
4415 not being able to deduce some paths, you can get detailed information
|
|
|
4416 on the path-searching process at startup by setting the environment
|
|
|
4417 variable @samp{EMACSDEBUGPATHS} to a non-null value. One thing to
|
|
|
4418 look for if you're having package problems is the value of
|
|
|
4419 @samp{configure-package-path}. This corresponds to what was compiled
|
|
|
4420 into XEmacs using the @samp{--package-prefix} or @samp{--package-path}
|
|
|
4421 parameter (@pxref{Q2.1.1}). If this has the value of @samp{nil},
|
|
|
4422 this means that no value was compiled into XEmacs using these parameters.
|
|
|
4423
|
|
|
4424 @node Q2.5.3, Q2.5.4, Q2.5.2, Installation
|
|
|
4425 @unnumberedsubsec Q2.5.3: XEmacs won't start without network.
|
|
434
|
4426
|
|
|
4427 If XEmacs starts when you're on the network, but fails when you're not
|
|
|
4428 on the network, you may be missing a "localhost" entry in your
|
|
|
4429 @file{/etc/hosts} file. The file should contain an entry like:
|
|
|
4430
|
|
|
4431 @example
|
|
|
4432 127.0.0.1 localhost
|
|
|
4433 @end example
|
|
|
4434
|
|
|
4435 Add that line, and XEmacs will be happy.
|
|
|
4436
|
|
2559
|
4437 @node Q2.5.4, Q2.5.5, Q2.5.3, Installation
|
|
|
4438 @unnumberedsubsec Q2.5.4: Startup warnings about deducing proper fonts?
|
|
2417
|
4439
|
|
|
4440 How can I avoid the startup warnings about deducing proper fonts?
|
|
|
4441
|
|
|
4442 This is highly dependent on your installation, but try with the
|
|
|
4443 following font as your base font for XEmacs and see what it does:
|
|
|
4444
|
|
|
4445 @format
|
|
|
4446 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
|
|
|
4447 @end format
|
|
|
4448
|
|
|
4449 More precisely, do the following in your resource file:
|
|
|
4450
|
|
|
4451 @format
|
|
|
4452 Emacs.default.attributeFont: \
|
|
|
4453 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
|
|
|
4454 @end format
|
|
|
4455
|
|
|
4456 If you just don't want to see the @samp{*Warnings*} buffer at startup
|
|
|
4457 time, you can set this:
|
|
428
|
4458
|
|
|
4459 @lisp
|
|
2417
|
4460 (setq display-warning-minimum-level 'error)
|
|
428
|
4461 @end lisp
|
|
|
4462
|
|
2417
|
4463 The buffer still exists; it just isn't in your face.
|
|
|
4464
|
|
2559
|
4465 @node Q2.5.5, Q2.5.6, Q2.5.4, Installation
|
|
|
4466 @unnumberedsubsec Q2.5.5: Warnings from incorrect key modifiers.
|
|
2417
|
4467
|
|
|
4468 The following information comes from the @file{PROBLEMS} file that comes
|
|
|
4469 with XEmacs.
|
|
|
4470
|
|
|
4471 If you're having troubles with HP/UX it is because HP/UX defines the
|
|
|
4472 modifiers wrong in X. Here is a shell script to fix the problem; be
|
|
|
4473 sure that it is run after VUE configures the X server.
|
|
428
|
4474
|
|
|
4475 @example
|
|
2417
|
4476 #! /bin/sh
|
|
|
4477 xmodmap 2> /dev/null - << EOF
|
|
|
4478 keysym Alt_L = Meta_L
|
|
|
4479 keysym Alt_R = Meta_R
|
|
|
4480 EOF
|
|
|
4481
|
|
|
4482 xmodmap - << EOF
|
|
|
4483 clear mod1
|
|
|
4484 keysym Mode_switch = NoSymbol
|
|
|
4485 add mod1 = Meta_L
|
|
|
4486 keysym Meta_R = Mode_switch
|
|
|
4487 add mod2 = Mode_switch
|
|
|
4488 EOF
|
|
428
|
4489 @end example
|
|
|
4490
|
|
2559
|
4491 @node Q2.5.6, , Q2.5.5, Installation
|
|
|
4492 @unnumberedsubsec Q2.5.6: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
2417
|
4493
|
|
|
4494 Yes.
|
|
|
4495
|
|
|
4496 The console was there because @file{temacs} (and in turn, @file{xemacs})
|
|
|
4497 was a console application, and Windows typically creates a new
|
|
|
4498 console for a console process unless the creating process requests that
|
|
|
4499 one isn't created. This used to be fixed with @file{runemacs}, a small
|
|
|
4500 Windows application that existed merely to start @file{xemacs}, stating
|
|
|
4501 that it didn't want a console.
|
|
|
4502
|
|
|
4503 XEmacs 21.4 fixes this cleanly by the virtue of being a true "GUI"
|
|
|
4504 application. The explanation of what that means is included for
|
|
|
4505 educational value.
|
|
|
4506
|
|
|
4507 When building an application to be run in a Win32 environment, you must
|
|
|
4508 state which sub-system it is to run in. Valid subsystems include
|
|
|
4509 "console" and "gui". The subsystem you use affects the run time
|
|
|
4510 libraries linked into your application, the start up function that is
|
|
|
4511 run before control is handed over to your application, the entry point
|
|
|
4512 to your program, and how Windows normally invokes your program. (Console
|
|
|
4513 programs automatically get a console created for them at startup if
|
|
|
4514 their stdin/stdout don't point anywhere useful, which is the case when
|
|
|
4515 run from the GUI. This is a stupid design, of course -- instead, the
|
|
|
4516 console should get created only when the first I/O actually occurs!
|
|
|
4517 GUI programs have an equally stupid design: When called from
|
|
|
4518 @file{CMD.EXE}/@file{COMMAND.COM}, their stdin/stdout will be set to
|
|
|
4519 point nowhere useful, even though the command shell has its own
|
|
|
4520 stdin/stdout. It's as if someone who had learned a bit about stdio but
|
|
|
4521 had no actual knowledge of interprocess communication designed the
|
|
|
4522 scheme; unfortunately, the whole process-communication aspect of the
|
|
|
4523 Win32 API is equally badly designed.) For example, the entry point for a
|
|
|
4524 console app is "main" (which is what you'd expect for a C/C++ program),
|
|
|
4525 but the entry point for a "gui" app is "WinMain". This confuses and
|
|
|
4526 annoys a lot of programmers who've grown up on Unix systems, where the
|
|
|
4527 kernel doesn't really care whether your application is a gui program or
|
|
|
4528 not.
|
|
|
4529
|
|
|
4530 For reasons not altogether clear, and are lost in the mists of time and
|
|
|
4531 tradition, XEmacs on Win32 started out as a console application, and
|
|
|
4532 therefore a console was automatically created for it. (It may have been
|
|
|
4533 made a console application partly because a console is needed in some
|
|
|
4534 circumstances, especially under Win95, to interrupt, terminate, or send
|
|
|
4535 signals to a child process, and because of the bogosity mentioned above
|
|
|
4536 with GUI programs and the standard command shell. Currently, XEmacs
|
|
|
4537 just creates and immediately hides a console when necessary, and
|
|
|
4538 works around the "no useful stdio" problem by creating its own console
|
|
|
4539 window as necessary to display messages in.)
|
|
|
4540
|
|
2459
|
4541 @node Editing, Display, Installation, Top
|
|
|
4542 @unnumbered 3 Editing Functions
|
|
2417
|
4543
|
|
|
4544 This is part 3 of the XEmacs Frequently Asked Questions list. This
|
|
2459
|
4545 section is devoted to the editing-related capabilities of XEmacs (the
|
|
|
4546 keyboard, mouse, buffers, text selections, etc.) and how to customize
|
|
|
4547 them.
|
|
2417
|
4548
|
|
|
4549 @menu
|
|
|
4550 3.0: The Keyboard
|
|
2459
|
4551 * Q3.0.1:: How can I customize the keyboard?
|
|
|
4552 * Q3.0.2:: How can I bind complex functions (or macros) to keys?
|
|
|
4553 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down?
|
|
|
4554 * Q3.0.4:: Globally binding @kbd{Delete}?
|
|
|
4555 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
|
4556 * Q3.0.6:: How can you type in special characters in XEmacs?
|
|
|
4557 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys?
|
|
|
4558 * Q3.0.8:: How do I map the arrow keys?
|
|
|
4559 * Q3.0.9:: HP Alt key as Meta.
|
|
|
4560 * Q3.0.10:: Why does edt emulation not work?
|
|
|
4561 * Q3.0.11:: How can I emulate VI and use it as my default mode?
|
|
2417
|
4562
|
|
|
4563 3.1: The Mouse
|
|
|
4564 * Q3.1.1:: How can I turn off Mouse pasting?
|
|
|
4565 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons?
|
|
|
4566 * Q3.1.3:: Clicking the left button does not do anything in buffer list.
|
|
|
4567 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3?
|
|
2459
|
4568 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
|
4569
|
|
|
4570 3.2: Buffers, Text Editing
|
|
|
4571 * Q3.2.1:: Can I have the end of the buffer delimited in some way?
|
|
|
4572 * Q3.2.2:: How do I insert today's date into a buffer?
|
|
|
4573 * Q3.2.3:: How do I get a single minibuffer frame?
|
|
|
4574 * Q3.2.4:: How can I enable auto-indent and/or Filladapt?
|
|
|
4575 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
4576
|
|
|
4577 3.3: Text Selections
|
|
|
4578 * Q3.3.1:: How do I select a rectangular region?
|
|
|
4579 * Q3.3.2:: How can I turn off or change highlighted selections?
|
|
|
4580 * Q3.3.3:: How do I cause typing on an active region to remove it?
|
|
|
4581 * Q3.3.4:: Can I turn off the highlight during isearch?
|
|
|
4582 * Q3.3.5:: Why is killing so slow?
|
|
|
4583 * Q3.3.6:: Why does @kbd{M-w} take so long?
|
|
|
4584
|
|
|
4585 3.4: Editing Source Code
|
|
|
4586 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode?
|
|
|
4587 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly?
|
|
2417
|
4588 @end menu
|
|
|
4589
|
|
|
4590 @unnumberedsec 3.0: The Keyboard
|
|
|
4591
|
|
2459
|
4592 @node Q3.0.1, Q3.0.2, Editing, Editing
|
|
|
4593 @unnumberedsubsec Q3.0.1: How can I customize the keyboard?
|
|
|
4594
|
|
|
4595 #### Write me.
|
|
|
4596
|
|
|
4597 @node Q3.0.2, Q3.0.3, Q3.0.1, Editing
|
|
|
4598 @unnumberedsubsec Q3.0.2: How can I bind complex functions (or macros) to keys?
|
|
428
|
4599
|
|
|
4600 As an example, say you want the @kbd{paste} key on a Sun keyboard to
|
|
|
4601 insert the current Primary X selection at point. You can accomplish this
|
|
|
4602 with:
|
|
|
4603
|
|
|
4604 @lisp
|
|
|
4605 (define-key global-map [f18] 'x-insert-selection)
|
|
|
4606 @end lisp
|
|
|
4607
|
|
|
4608 However, this only works if there is a current X selection (the
|
|
|
4609 selection will be highlighted). The functionality I like is for the
|
|
|
4610 @kbd{paste} key to insert the current X selection if there is one,
|
|
|
4611 otherwise insert the contents of the clipboard. To do this you need to
|
|
|
4612 pass arguments to @code{x-insert-selection}. This is done by wrapping
|
|
|
4613 the call in a 'lambda form:
|
|
|
4614
|
|
|
4615 @lisp
|
|
|
4616 (global-set-key [f18]
|
|
|
4617 (lambda () (interactive) (x-insert-selection t nil)))
|
|
|
4618 @end lisp
|
|
|
4619
|
|
|
4620 This binds the f18 key to a @dfn{generic} functional object. The
|
|
|
4621 interactive spec is required because only interactive functions can be
|
|
|
4622 bound to keys.
|
|
|
4623
|
|
|
4624 For the FAQ example you could use:
|
|
|
4625
|
|
|
4626 @lisp
|
|
|
4627 (global-set-key [(control ?.)]
|
|
|
4628 (lambda () (interactive) (scroll-up 1)))
|
|
440
|
4629 (global-set-key [(control ?;)]
|
|
|
4630 (lambda () (interactive) (scroll-up -1)))
|
|
428
|
4631 @end lisp
|
|
|
4632
|
|
|
4633 This is fine if you only need a few functions within the lambda body.
|
|
2417
|
4634 If you're doing more it's cleaner to define a separate function.
|
|
2459
|
4635 @xref{Q3.0.3, How do I bind C-. and C-; to scroll one line up and
|
|
2417
|
4636 down?}.
|
|
|
4637
|
|
2459
|
4638 @node Q3.0.3, Q3.0.4, Q3.0.2, Editing
|
|
|
4639 @unnumberedsubsec Q3.0.3: How do I bind C-. and C-; to scroll one line up and down?
|
|
428
|
4640
|
|
|
4641 Add the following (Thanks to @email{mly@@adoc.xerox.com, Richard Mlynarik} and
|
|
|
4642 @email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}:
|
|
|
4643
|
|
|
4644 @lisp
|
|
|
4645 (defun scroll-up-one-line ()
|
|
|
4646 (interactive)
|
|
|
4647 (scroll-up 1))
|
|
|
4648
|
|
|
4649 (defun scroll-down-one-line ()
|
|
|
4650 (interactive)
|
|
|
4651 (scroll-down 1))
|
|
|
4652
|
|
|
4653 (global-set-key [(control ?.)] 'scroll-up-one-line) ; C-.
|
|
440
|
4654 (global-set-key [(control ?;)] 'scroll-down-one-line) ; C-;
|
|
428
|
4655 @end lisp
|
|
|
4656
|
|
|
4657 The key point is that you can only bind simple functions to keys; you
|
|
2417
|
4658 can not bind a key to a function that you're also passing arguments
|
|
2459
|
4659 to. (@pxref{Q3.0.2, How can I bind complex functions (or macros) to
|
|
2417
|
4660 keys?} for a better answer).
|
|
|
4661
|
|
2459
|
4662 @node Q3.0.4, Q3.0.5, Q3.0.3, Editing
|
|
|
4663 @unnumberedsubsec Q3.0.4: Globally binding @kbd{Delete}?
|
|
428
|
4664
|
|
|
4665 I cannot manage to globally bind my @kbd{Delete} key to something other
|
|
|
4666 than the default. How does one do this?
|
|
|
4667
|
|
462
|
4668 Answer: The problem is that many modes explicitly bind @kbd{Delete}. To
|
|
|
4669 get around this, try the following:
|
|
|
4670
|
|
428
|
4671 @lisp
|
|
|
4672 (defun foo ()
|
|
|
4673 (interactive)
|
|
|
4674 (message "You hit DELETE"))
|
|
|
4675
|
|
462
|
4676 (define-key key-translation-map 'delete 'redirected-delete)
|
|
|
4677 (global-set-key 'redirected-delete 'foo)
|
|
428
|
4678 @end lisp
|
|
|
4679
|
|
2459
|
4680 @node Q3.0.5, Q3.0.6, Q3.0.4, Editing
|
|
|
4681 @unnumberedsubsec Q3.0.5: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
428
|
4682
|
|
|
4683 The following works in GNU Emacs 19:
|
|
|
4684
|
|
|
4685 @lisp
|
|
|
4686 (global-set-key [help] 'help-command);; Help
|
|
|
4687 @end lisp
|
|
|
4688
|
|
462
|
4689 The following works in XEmacs with the addition of shift:
|
|
428
|
4690
|
|
|
4691 @lisp
|
|
|
4692 (global-set-key [(shift help)] 'help-command);; Help
|
|
|
4693 @end lisp
|
|
|
4694
|
|
|
4695 But it doesn't work alone. This is in the file @file{PROBLEMS} which
|
|
|
4696 should have come with your XEmacs installation: @emph{Emacs ignores the
|
|
|
4697 @kbd{help} key when running OLWM}.
|
|
|
4698
|
|
|
4699 OLWM grabs the @kbd{help} key, and retransmits it to the appropriate
|
|
|
4700 client using
|
|
|
4701 @iftex
|
|
|
4702 @*
|
|
|
4703 @end iftex
|
|
|
4704 @code{XSendEvent}. Allowing Emacs to react to synthetic
|
|
|
4705 events is a security hole, so this is turned off by default. You can
|
|
|
4706 enable it by setting the variable @code{x-allow-sendevents} to t. You
|
|
|
4707 can also cause fix this by telling OLWM to not grab the help key, with
|
|
|
4708 the null binding @code{OpenWindows.KeyboardCommand.Help:}.
|
|
|
4709
|
|
2459
|
4710 @node Q3.0.6, Q3.0.7, Q3.0.5, Editing
|
|
|
4711 @unnumberedsubsec Q3.0.6: How can you type in special characters in XEmacs?
|
|
428
|
4712 One way is to use the package @code{x-compose}. Then you can use
|
|
|
4713 sequences like @kbd{Compose " a} to get ä, etc.
|
|
|
4714
|
|
462
|
4715 Another way is to use the @code{iso-insert} package. Then you can use
|
|
|
4716 sequences like @kbd{C-x 8 " a} to get ä, etc.
|
|
428
|
4717
|
|
|
4718 @email{glynn@@sensei.co.uk, Glynn Clements} writes:
|
|
|
4719
|
|
|
4720 @quotation
|
|
|
4721 It depends upon your X server.
|
|
|
4722
|
|
|
4723 Generally, the simplest way is to define a key as Multi_key with
|
|
|
4724 xmodmap, e.g.
|
|
|
4725 @c hey, show some respect, willya -- there's xkeycaps, isn't there? --
|
|
|
4726 @c chr ;)
|
|
|
4727 @example
|
|
440
|
4728 xmodmap -e 'keycode 0xff20 = Multi_key'
|
|
428
|
4729 @end example
|
|
|
4730
|
|
|
4731 You will need to pick an appropriate keycode. Use xev to find out the
|
|
|
4732 keycodes for each key.
|
|
|
4733
|
|
|
4734 [NB: On a `Windows' keyboard, recent versions of XFree86 automatically
|
|
|
4735 define the right `Windows' key as Multi_key'.]
|
|
|
4736
|
|
|
4737 Once you have Multi_key defined, you can use e.g.
|
|
|
4738 @example
|
|
440
|
4739 Multi a ' => á
|
|
|
4740 Multi e " => ë
|
|
|
4741 Multi c , => ç
|
|
428
|
4742 @end example
|
|
|
4743
|
|
|
4744 etc.
|
|
|
4745
|
|
|
4746 Also, recent versions of XFree86 define various AltGr-<key>
|
|
|
4747 combinations as dead keys, i.e.
|
|
|
4748 @example
|
|
440
|
4749 AltGr [ => dead_diaeresis
|
|
|
4750 AltGr ] => dead_tilde
|
|
|
4751 AltGr ; => dead_acute
|
|
428
|
4752 @end example
|
|
|
4753 etc.
|
|
|
4754
|
|
|
4755 Running @samp{xmodmap -pk} will list all of the defined keysyms.
|
|
|
4756 @end quotation
|
|
|
4757
|
|
1135
|
4758 For the related problem of @emph{displaying} non-ASCII characters in a
|
|
2459
|
4759 non-Mule XEmacs, @xref{Q4.0.8, How do I display non-ASCII characters?}.
|
|
|
4760
|
|
|
4761 @node Q3.0.7, Q3.0.8, Q3.0.6, Editing
|
|
|
4762 @unnumberedsubsec Q3.0.7: Can I turn on @dfn{sticky} modifier keys?
|
|
428
|
4763
|
|
|
4764 Yes, with @code{(setq modifier-keys-are-sticky t)}. This will give the
|
|
|
4765 effect of being able to press and release Shift and have the next
|
|
|
4766 character typed come out in upper case. This will affect all the other
|
|
|
4767 modifier keys like Control and Meta as well.
|
|
|
4768
|
|
|
4769 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
|
4770
|
|
|
4771 @quotation
|
|
|
4772 One thing about the sticky modifiers is that if you move the mouse out
|
|
|
4773 of the frame and back in, it cancels all currently ``stuck'' modifiers.
|
|
|
4774 @end quotation
|
|
|
4775
|
|
2459
|
4776 @node Q3.0.8, Q3.0.9, Q3.0.7, Editing
|
|
|
4777 @unnumberedsubsec Q3.0.8: How do I map the arrow keys?
|
|
428
|
4778 @c New
|
|
|
4779 Say you want to map @kbd{C-@key{right}} to forward-word:
|
|
|
4780
|
|
|
4781 @email{sds@@usa.net, Sam Steingold} writes:
|
|
|
4782
|
|
|
4783 @quotation
|
|
|
4784 @lisp
|
|
|
4785 ; both XEmacs and Emacs
|
|
|
4786 (define-key global-map [(control right)] 'forward-word)
|
|
|
4787 @end lisp
|
|
|
4788 or
|
|
|
4789 @lisp
|
|
|
4790 ; Emacs only
|
|
|
4791 (define-key global-map [C-right] 'forward-word)
|
|
|
4792 @end lisp
|
|
|
4793 or
|
|
|
4794 @lisp
|
|
|
4795 ; ver > 20, both
|
|
|
4796 (define-key global-map (kbd "C-<right>") 'forward-word)
|
|
|
4797 @end lisp
|
|
|
4798 @end quotation
|
|
|
4799
|
|
2459
|
4800 @node Q3.0.9, Q3.0.10, Q3.0.8, Editing
|
|
|
4801 @unnumberedsubsec Q3.0.9: HP Alt key as Meta.
|
|
2417
|
4802
|
|
|
4803 How can I make XEmacs recognize the Alt key of my HP workstation as a
|
|
|
4804 Meta key?
|
|
|
4805
|
|
|
4806 Put the following line into a file and load it with xmodmap(1) before
|
|
|
4807 starting XEmacs:
|
|
428
|
4808
|
|
|
4809 @example
|
|
2417
|
4810 remove Mod1 = Mode_switch
|
|
428
|
4811 @end example
|
|
|
4812
|
|
2459
|
4813 @node Q3.0.10, Q3.0.11, Q3.0.9, Editing
|
|
|
4814 @unnumberedsubsec Q3.0.10: Why does edt emulation not work?
|
|
2417
|
4815
|
|
|
4816 We don't know, but you can use tpu-edt emulation instead, which works
|
|
|
4817 fine and is a little fancier than the standard edt emulation. To do
|
|
|
4818 this, add the following line to your @file{init.el}:
|
|
|
4819
|
|
|
4820 @lisp
|
|
|
4821 (tpu-edt)
|
|
|
4822 @end lisp
|
|
|
4823
|
|
|
4824 If you don't want it to replace @kbd{C-h} with an edt-style help menu
|
|
|
4825 add this as well:
|
|
428
|
4826
|
|
|
4827 @lisp
|
|
2417
|
4828 (global-set-key [(control h)] 'help-for-help)
|
|
428
|
4829 @end lisp
|
|
|
4830
|
|
2459
|
4831 @node Q3.0.11, Q3.1.1, Q3.0.10, Editing
|
|
|
4832 @unnumberedsubsec Q3.0.11: How can I emulate VI and use it as my default mode?
|
|
2417
|
4833
|
|
|
4834 Our recommended VI emulator is viper. To make viper-mode the default,
|
|
|
4835 add this to your @file{init.el}:
|
|
428
|
4836
|
|
|
4837 @lisp
|
|
2417
|
4838 (viper-mode)
|
|
428
|
4839 @end lisp
|
|
|
4840
|
|
2417
|
4841 @email{kifer@@CS.SunySB.EDU, Michael Kifer} writes:
|
|
|
4842
|
|
|
4843 @quotation
|
|
|
4844 This should be added as close to the top of @file{init.el} as you can get
|
|
|
4845 it, otherwise some minor modes may not get viper-ized.
|
|
|
4846 @end quotation
|
|
|
4847
|
|
|
4848 @unnumberedsec 3.1: The Mouse
|
|
|
4849
|
|
2459
|
4850 @node Q3.1.1, Q3.1.2, Q3.0.11, Editing
|
|
2417
|
4851 @unnumberedsubsec Q3.1.1: How can I turn off Mouse pasting?
|
|
428
|
4852
|
|
|
4853 I keep hitting the middle mouse button by accident and getting stuff
|
|
|
4854 pasted into my buffer so how can I turn this off?
|
|
|
4855
|
|
|
4856 Here is an alternative binding, whereby the middle mouse button selects
|
|
|
4857 (but does not cut) the expression under the mouse. Clicking middle on a
|
|
|
4858 left or right paren will select to the matching one. Note that you can
|
|
|
4859 use @code{define-key} or @code{global-set-key}.
|
|
|
4860
|
|
|
4861 @lisp
|
|
|
4862 (defun mouse-set-point-and-select (event)
|
|
|
4863 "Sets the point at the mouse location, then marks following form"
|
|
|
4864 (interactive "@@e")
|
|
|
4865 (mouse-set-point event)
|
|
|
4866 (mark-sexp 1))
|
|
|
4867 (define-key global-map [button2] 'mouse-set-point-and-select)
|
|
|
4868 @end lisp
|
|
|
4869
|
|
2459
|
4870 @node Q3.1.2, Q3.1.3, Q3.1.1, Editing
|
|
2417
|
4871 @unnumberedsubsec Q3.1.2: How do I set control/meta/etc modifiers on mouse buttons?
|
|
428
|
4872
|
|
|
4873 Use, for instance, @code{[(meta button1)]}. For example, here is a common
|
|
|
4874 setting for Common Lisp programmers who use the bundled @code{ilisp}
|
|
|
4875 package, whereby meta-button1 on a function name will find the file where
|
|
|
4876 the function name was defined, and put you at that location in the source
|
|
|
4877 file.
|
|
|
4878
|
|
|
4879 [Inside a function that gets called by the lisp-mode-hook and
|
|
|
4880 ilisp-mode-hook]
|
|
|
4881
|
|
|
4882 @lisp
|
|
|
4883 (local-set-key [(meta button1)] 'edit-definitions-lisp)
|
|
|
4884 @end lisp
|
|
|
4885
|
|
2459
|
4886 @node Q3.1.3, Q3.1.4, Q3.1.2, Editing
|
|
2417
|
4887 @unnumberedsubsec Q3.1.3: Clicking the left button does not do anything in buffer list.
|
|
428
|
4888
|
|
|
4889 I do @kbd{C-x C-b} to get a list of buffers and the entries get
|
|
|
4890 highlighted when I move the mouse over them but clicking the left mouse
|
|
|
4891 does not do anything.
|
|
|
4892
|
|
|
4893 Use the middle mouse button.
|
|
|
4894
|
|
2459
|
4895 @node Q3.1.4, Q3.1.5, Q3.1.3, Editing
|
|
2417
|
4896 @unnumberedsubsec Q3.1.4: How can I get a list of buffers when I hit mouse button 3?
|
|
428
|
4897
|
|
|
4898 The following code will replace the default popup on button3:
|
|
|
4899
|
|
|
4900 @lisp
|
|
|
4901 (global-set-key [button3] 'popup-buffer-menu)
|
|
|
4902 @end lisp
|
|
|
4903
|
|
2459
|
4904 @node Q3.1.5, Q3.2.1, Q3.1.4, Editing
|
|
|
4905 @unnumberedsubsec Q3.1.5: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
428
|
4906
|
|
|
4907 By default XEmacs pastes X selections where the mouse pointer is. How
|
|
|
4908 do I disable this?
|
|
|
4909
|
|
|
4910 Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank
|
|
|
4911 @key{RET}}.
|
|
|
4912
|
|
2417
|
4913 To get XEmacs to paste at the text cursor, add this your @file{init.el}:
|
|
428
|
4914
|
|
|
4915 @lisp
|
|
|
4916 (setq mouse-yank-at-point t)
|
|
|
4917 @end lisp
|
|
|
4918
|
|
2459
|
4919 You can also change this with Customize. Select from the
|
|
|
4920 @code{Options} menu @code{Advanced
|
|
|
4921 (Customize)->Emacs->Editing->Mouse->Yank At Point...} or type @kbd{M-x
|
|
|
4922 customize @key{RET} mouse @key{RET}}.
|
|
|
4923
|
|
|
4924 @unnumberedsec 3.2: Buffers, Text Editing
|
|
|
4925
|
|
|
4926 @node Q3.2.1, Q3.2.2, Q3.1.5, Editing
|
|
|
4927 @unnumberedsubsec Q3.2.1: Can I have the end of the buffer delimited in some way?
|
|
|
4928
|
|
|
4929 Say, with: @samp{[END]}?
|
|
|
4930
|
|
|
4931 Try this:
|
|
|
4932
|
|
|
4933 @lisp
|
|
|
4934 (let ((ext (make-extent (point-min) (point-max))))
|
|
|
4935 (set-extent-property ext 'start-closed t)
|
|
|
4936 (set-extent-property ext 'end-closed t)
|
|
|
4937 (set-extent-property ext 'detachable nil)
|
|
|
4938 (set-extent-end-glyph ext (make-glyph [string :data "[END]"])))
|
|
|
4939 @end lisp
|
|
|
4940
|
|
|
4941 Since this is XEmacs, you can specify an icon to be shown on
|
|
|
4942 window-system devices. To do so, change the @code{make-glyph} call to
|
|
|
4943 something like this:
|
|
|
4944
|
|
|
4945 @lisp
|
|
|
4946 (make-glyph '([xpm :file "~/something.xpm"]
|
|
|
4947 [string :data "[END]"]))
|
|
|
4948 @end lisp
|
|
|
4949
|
|
|
4950 You can inline the @sc{xpm} definition yourself by specifying
|
|
|
4951 @code{:data} instead of @code{:file}. Here is such a full-featured
|
|
|
4952 version that works on both X and TTY devices:
|
|
|
4953
|
|
|
4954 @lisp
|
|
|
4955 (let ((ext (make-extent (point-min) (point-max))))
|
|
|
4956 (set-extent-property ext 'start-closed t)
|
|
|
4957 (set-extent-property ext 'end-closed t)
|
|
|
4958 (set-extent-property ext 'detachable nil)
|
|
|
4959 (set-extent-end-glyph ext (make-glyph '([xpm :data "\
|
|
|
4960 /* XPM */
|
|
|
4961 static char* eye = @{
|
|
|
4962 \"20 11 7 2\",
|
|
|
4963 \"__ c None\"
|
|
|
4964 \"_` c #7f7f7f\",
|
|
|
4965 \"_a c #fefefe\",
|
|
|
4966 \"_b c #7f0000\",
|
|
|
4967 \"_c c #fefe00\",
|
|
|
4968 \"_d c #fe0000\",
|
|
|
4969 \"_e c #bfbfbf\",
|
|
|
4970 \"___________`_`_`___b_b_b_b_________`____\",
|
|
|
4971 \"_________`_`_`___b_c_c_c_b_b____________\",
|
|
|
4972 \"_____`_`_`_e___b_b_c_c_c___b___b_______`\",
|
|
|
4973 \"___`_`_e_a___b_b_d___b___b___b___b______\",
|
|
|
4974 \"_`_`_e_a_e___b_b_d_b___b___b___b___b____\",
|
|
|
4975 \"_`_`_a_e_a___b_b_d___b___b___b___b___b__\",
|
|
|
4976 \"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\",
|
|
|
4977 \"___`_`_e_a___b_b_b_d_c___b___b___d_b____\",
|
|
|
4978 \"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\",
|
|
|
4979 \"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\",
|
|
|
4980 \"___`_____`_`_`_`___b_b_b_b_b_b__________\",
|
|
|
4981 @} ;"]
|
|
|
4982 [string :data "[END]"]))))
|
|
|
4983 @end lisp
|
|
|
4984
|
|
|
4985 Note that you might want to make this a function, and put it to a hook.
|
|
|
4986 We leave that as an exercise for the reader.
|
|
|
4987
|
|
|
4988 @node Q3.2.2, Q3.2.3, Q3.2.1, Editing
|
|
|
4989 @unnumberedsubsec Q3.2.2: How do I insert today's date into a buffer?
|
|
2417
|
4990
|
|
|
4991 Like this:
|
|
428
|
4992
|
|
|
4993 @lisp
|
|
2459
|
4994 (insert (current-time-string))
|
|
2417
|
4995 @end lisp
|
|
|
4996
|
|
2459
|
4997 @node Q3.2.3, Q3.2.4, Q3.2.2, Editing
|
|
|
4998 @unnumberedsubsec Q3.2.3: How do I get a single minibuffer frame?
|
|
|
4999
|
|
|
5000 @email{acs@@acm.org, Vin Shelton} writes:
|
|
2417
|
5001
|
|
|
5002 @lisp
|
|
2459
|
5003 (setq initial-frame-plist '(minibuffer nil))
|
|
|
5004 (setq default-frame-plist '(minibuffer nil))
|
|
|
5005 (setq default-minibuffer-frame
|
|
|
5006 (make-frame
|
|
|
5007 '(minibuffer only
|
|
|
5008 width 86
|
|
|
5009 height 1
|
|
|
5010 menubar-visible-p nil
|
|
|
5011 default-toolbar-visible-p nil
|
|
|
5012 name "minibuffer"
|
|
|
5013 top -2
|
|
|
5014 left -2
|
|
|
5015 has-modeline-p nil)))
|
|
|
5016 (frame-notice-user-settings)
|
|
2417
|
5017 @end lisp
|
|
|
5018
|
|
2459
|
5019 @strong{Please note:} The single minibuffer frame may not be to everyone's
|
|
|
5020 taste, and there any number of other XEmacs options settings that may
|
|
|
5021 make it difficult or inconvenient to use.
|
|
|
5022
|
|
|
5023 @node Q3.2.4, Q3.2.5, Q3.2.3, Editing
|
|
|
5024 @unnumberedsubsec Q3.2.4: How can I enable auto-indent and/or Filladapt?
|
|
|
5025
|
|
|
5026 Put the following line in your @file{init.el}:
|
|
428
|
5027
|
|
|
5028 @lisp
|
|
2459
|
5029 (setq indent-line-function 'indent-relative-maybe)
|
|
428
|
5030 @end lisp
|
|
|
5031
|
|
2459
|
5032 If you want to get fancy, try the @code{filladapt} package available
|
|
|
5033 standard with XEmacs. Put this into your @file{init.el}:
|
|
428
|
5034
|
|
|
5035 @lisp
|
|
2459
|
5036 (require 'filladapt)
|
|
|
5037 (setq-default filladapt-mode t)
|
|
|
5038 (add-hook 'c-mode-hook 'turn-off-filladapt-mode)
|
|
428
|
5039 @end lisp
|
|
|
5040
|
|
2459
|
5041 This will enable Filladapt for all modes except C mode, where it doesn't
|
|
|
5042 work well. To turn Filladapt on only in particular major modes, remove
|
|
|
5043 the @code{(setq-default ...)} line and use
|
|
|
5044 @code{turn-on-filladapt-mode}, like this:
|
|
428
|
5045
|
|
|
5046 @lisp
|
|
2459
|
5047 (add-hook 'text-mode-hook 'turn-on-filladapt-mode)
|
|
428
|
5048 @end lisp
|
|
2417
|
5049
|
|
2459
|
5050 You can customize filling and adaptive filling with Customize.
|
|
|
5051 Select from the @code{Options} menu
|
|
|
5052 @code{Advanced (Customize)->Emacs->Editing->Fill->Fill...}
|
|
|
5053 or type @kbd{M-x customize @key{RET} fill @key{RET}}.
|
|
|
5054
|
|
|
5055 Note that well-behaving text-lookalike modes will run
|
|
|
5056 @code{text-mode-hook} by default (e.g. that's what Message does). For
|
|
|
5057 the nasty ones, you'll have to provide the @code{add-hook}s yourself.
|
|
|
5058
|
|
|
5059 Please note that the @code{fa-extras} package is no longer useful.
|
|
|
5060
|
|
|
5061 @node Q3.2.5, Q3.3.1, Q3.2.4, Editing
|
|
|
5062 @unnumberedsubsec Q3.2.5: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
5063
|
|
|
5064 Try the following lisp in your @file{init.el}:
|
|
2417
|
5065
|
|
|
5066 @lisp
|
|
2459
|
5067 (setq default-major-mode 'text-mode)
|
|
2769
|
5068 (add-hook 'text-mode-hook 'turn-on-auto-fill)
|
|
2417
|
5069 @end lisp
|
|
|
5070
|
|
2459
|
5071 @strong{WARNING}: note that changing the value of
|
|
|
5072 @code{default-major-mode} from @code{fundamental-mode} can break a large
|
|
|
5073 amount of built-in code that expects newly created buffers to be in
|
|
|
5074 @code{fundamental-mode}. (Changing from @code{fundamental-mode} to
|
|
|
5075 @code{text-mode} might not wreak too much havoc, but changing to
|
|
|
5076 something more exotic like a lisp-mode would break many Emacs packages).
|
|
|
5077
|
|
|
5078 Note that Emacs by default starts up in buffer @code{*scratch*} in
|
|
|
5079 @code{initial-major-mode}, which defaults to
|
|
|
5080 @code{lisp-interaction-mode}. Thus adding the following form to your
|
|
|
5081 Emacs init file will cause the initial @code{*scratch*} buffer to be put
|
|
|
5082 into auto-fill'ed @code{text-mode}:
|
|
2417
|
5083
|
|
|
5084 @lisp
|
|
2459
|
5085 (setq initial-major-mode
|
|
|
5086 (lambda ()
|
|
|
5087 (text-mode)
|
|
|
5088 (turn-on-auto-fill)))
|
|
2417
|
5089 @end lisp
|
|
|
5090
|
|
2459
|
5091 Note that after your init file is loaded, if
|
|
|
5092 @code{inhibit-startup-message} is @code{nil} (the default) and the
|
|
|
5093 startup buffer is @code{*scratch*} then the startup message will be
|
|
|
5094 inserted into @code{*scratch*}; it will be removed after a timeout by
|
|
|
5095 erasing the entire @code{*scratch*} buffer. Keep in mind this default
|
|
|
5096 usage of @code{*scratch*} if you desire any prior manipulation of
|
|
|
5097 @code{*scratch*} from within your Emacs init file. In particular,
|
|
|
5098 anything you insert into @code{*scratch*} from your init file will be
|
|
|
5099 later erased. Also, if you change the mode of the @code{*scratch*}
|
|
|
5100 buffer, be sure that this will not interfere with possible later
|
|
|
5101 insertion of the startup message (e.g. if you put @code{*scratch*} into
|
|
|
5102 a nonstandard mode that has automatic font lock rules, then the startup
|
|
|
5103 message might get fontified in a strange foreign manner, e.g. as code in
|
|
|
5104 some programming language).
|
|
|
5105
|
|
|
5106 @unnumberedsec 3.3: Text Selections
|
|
|
5107
|
|
|
5108 @node Q3.3.1, Q3.3.2, Q3.2.5, Editing
|
|
|
5109 @unnumberedsubsec Q3.3.1: How do I select a rectangular region?
|
|
2417
|
5110
|
|
|
5111 Just select the region normally, then use the rectangle commands (e.g.
|
|
|
5112 @code{kill-rectangle} on it. The region does not highlight as a
|
|
|
5113 rectangle, but the commands work just fine.
|
|
|
5114
|
|
|
5115 To actually sweep out rectangular regions with the mouse you can use
|
|
|
5116 @code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}.
|
|
|
5117 Then use rectangle commands.
|
|
|
5118
|
|
|
5119 You can also do the following to change default behavior to sweep out
|
|
|
5120 rectangular regions:
|
|
|
5121
|
|
|
5122 @lisp
|
|
|
5123 (setq mouse-track-rectangle-p t)
|
|
|
5124 @end lisp
|
|
|
5125
|
|
2459
|
5126 You can also change this with Customize.
|
|
2417
|
5127 Select from the @code{Options} menu
|
|
|
5128 @code{Advanced (Customize)->Emacs->Editing->Mouse->Track Rectangle...} or type
|
|
|
5129 @kbd{M-x customize @key{RET} mouse @key{RET}}.
|
|
|
5130
|
|
|
5131
|
|
|
5132 @example
|
|
|
5133 mouse-track-do-rectangle: (event)
|
|
|
5134 -- an interactive compiled Lisp function.
|
|
|
5135 Like `mouse-track' but selects rectangles instead of regions.
|
|
|
5136 @end example
|
|
|
5137
|
|
2459
|
5138 @node Q3.3.2, Q3.3.3, Q3.3.1, Editing
|
|
|
5139 @unnumberedsubsec Q3.3.2: How can I turn off or change highlighted selections?
|
|
428
|
5140
|
|
|
5141 The @code{zmacs} mode allows for what some might call gratuitous
|
|
|
5142 highlighting for selected regions (either by setting mark or by using
|
|
|
5143 the mouse). This is the default behavior. To turn off, add the
|
|
2417
|
5144 following line to your @file{init.el} file:
|
|
428
|
5145
|
|
|
5146 @lisp
|
|
|
5147 (setq zmacs-regions nil)
|
|
|
5148 @end lisp
|
|
|
5149
|
|
2417
|
5150 You can also change this with Customize. Select from the
|
|
|
5151 @code{Options} menu
|
|
|
5152 @code{Advanced (Customize)->Emacs->Editing->Basics->Zmacs Regions}
|
|
|
5153 or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
|
|
|
5154
|
|
|
5155 To change the face for selection, look at @code{Options->Advanced (Customize)}
|
|
|
5156 on the menubar.
|
|
|
5157
|
|
2459
|
5158 @node Q3.3.3, Q3.3.4, Q3.3.2, Editing
|
|
|
5159 @unnumberedsubsec Q3.3.3: How do I cause typing on an active region to remove it?
|
|
428
|
5160
|
|
|
5161 I want to change things so that if I select some text and start typing,
|
|
|
5162 the typed text replaces the selected text, similar to Motif.
|
|
|
5163
|
|
|
5164 You want to use something called @dfn{pending delete}. Pending delete
|
|
|
5165 is what happens when you select a region (with the mouse or keyboard)
|
|
|
5166 and you press a key to replace the selected region by the key you typed.
|
|
|
5167 Usually backspace kills the selected region.
|
|
|
5168
|
|
2164
|
5169 To get this behavior, ensure that you have the @file{pc} package
|
|
|
5170 installed, and add the following lines to your
|
|
2417
|
5171 @file{init.el}:
|
|
428
|
5172
|
|
|
5173 @lisp
|
|
438
|
5174 (cond
|
|
|
5175 ((fboundp 'turn-on-pending-delete)
|
|
|
5176 (turn-on-pending-delete))
|
|
|
5177 ((fboundp 'pending-delete-on)
|
|
|
5178 (pending-delete-on t)))
|
|
428
|
5179 @end lisp
|
|
|
5180
|
|
1138
|
5181 Note that this will work with both Backspace and Delete. This code is a
|
|
438
|
5182 tad more complicated than it has to be for XEmacs in order to make it
|
|
|
5183 more portable.
|
|
428
|
5184
|
|
2459
|
5185 @node Q3.3.4, Q3.3.5, Q3.3.3, Editing
|
|
|
5186 @unnumberedsubsec Q3.3.4: Can I turn off the highlight during isearch?
|
|
428
|
5187
|
|
|
5188 I do not like my text highlighted while I am doing isearch as I am not
|
|
|
5189 able to see what's underneath. How do I turn it off?
|
|
|
5190
|
|
2417
|
5191 Put the following in your @file{init.el}:
|
|
428
|
5192
|
|
|
5193 @lisp
|
|
|
5194 (setq isearch-highlight nil)
|
|
|
5195 @end lisp
|
|
|
5196
|
|
2459
|
5197 You can also change this with Customize. Type
|
|
428
|
5198 @kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}.
|
|
|
5199
|
|
|
5200 Note also that isearch-highlight affects query-replace and ispell.
|
|
|
5201 Instead of disabling isearch-highlight you may find that a better
|
|
|
5202 solution consists of customizing the @code{isearch} face.
|
|
|
5203
|
|
2459
|
5204 @node Q3.3.5, Q3.3.6, Q3.3.4, Editing
|
|
|
5205 @unnumberedsubsec Q3.3.5: Why is killing so slow?
|
|
892
|
5206
|
|
|
5207 This actually is an X Windows question, although you'll notice it with
|
|
|
5208 keyboard operations as well as while using the GUI. Basically, there
|
|
|
5209 are four ways to communicate interprogram via the X server:
|
|
|
5210
|
|
|
5211 @table @strong
|
|
|
5212 @item Primary selection
|
|
|
5213 a transient selection that gets replaced every time a new selection is made
|
|
|
5214
|
|
|
5215 @item Secondary selection
|
|
|
5216 for "exchanging" with the primary selection
|
|
|
5217
|
|
|
5218 @item Cut buffers
|
|
|
5219 a clipboard internal to the X server (deprecated)
|
|
|
5220
|
|
|
5221 @item Clipboard selection
|
|
|
5222 a selection with a notification protocol that allows a separate app to
|
|
|
5223 manage the clipboard
|
|
|
5224 @end table
|
|
|
5225
|
|
|
5226 The cut buffers are deprecated because managing them is even more
|
|
|
5227 inefficient than the clipboard notification protocol. The primary
|
|
|
5228 selection works fine for many users and applications, but is not very
|
|
|
5229 robust under intensive or sophisticated use.
|
|
|
5230
|
|
|
5231 In Motif and MS Windows, a clipboard has become the primary means for
|
|
|
5232 managing cut and paste. These means that "modern" applications tend to
|
|
|
5233 be oriented toward a true clipboard, rather than the primary selection.
|
|
|
5234 (On Windows, there is nothing equivalent to the primary selection.)
|
|
|
5235 It's not that XEmacs doesn't support the simple primary selection
|
|
|
5236 method, it's that more and more other applications don't.
|
|
|
5237
|
|
|
5238 So the slowdown occurs because XEmacs now engages in the clipboard
|
|
|
5239 notification protocol on @emph{every} kill. This is especially slow on
|
|
|
5240 Motif.
|
|
|
5241
|
|
|
5242 With most people running most clients and server on the same host, and
|
|
|
5243 many of the rest working over very fast communication, you may expect
|
|
|
5244 that the situation is not going to improve.
|
|
|
5245
|
|
|
5246 There are a number of workarounds. The most effective is to use a
|
|
|
5247 special command to do selection ownership only when you intend to paste
|
|
|
5248 to another application. Useful commands are @code{kill-primary-selection}
|
|
|
5249 and @code{copy-primary-selection}. These work only on text selected
|
|
|
5250 with the mouse (probably; experiment), and are bound by default to the
|
|
|
5251 @kbd{Cut} and @kbd{Copy}, respectively, buttons on the toolbar.
|
|
|
5252 @code{copy-primary-selection} is also bound to @kbd{C-Insert}. You can
|
|
|
5253 yank the clipboard contents with @code{yank-primary-selection}, bound to
|
|
|
5254 the @kbd{Paste} toolbar button and @kbd{Sh-Insert}.
|
|
|
5255
|
|
|
5256 If you are communicating by cut and paste with applications that use the
|
|
|
5257 primary selection, then you can customize
|
|
|
5258 @code{interprogram-cut-function} to @code{nil}, restoring the XEmacs
|
|
|
5259 version 20 behavior. How can you tell if a program will support this?
|
|
|
5260 Motifly-correct programs require the clipboard; you lose. For others,
|
|
|
5261 only by trying it. You also need to customize the complementary
|
|
|
5262 @code{interprogram-paste-function} to @code{nil}. (Otherwise
|
|
|
5263 XEmacs-to-XEmacs pastes will not work correctly.)
|
|
|
5264
|
|
|
5265 You may get some relief on Motif by setting
|
|
|
5266 @code{x-selection-strict-motif-ownership} to nil, but this means you will
|
|
|
5267 only intermittently be able to paste XEmacs kills to Motif applications.
|
|
|
5268
|
|
|
5269 Thanks to Jeff Mincy and Glynn Clements for corrections.
|
|
|
5270
|
|
2459
|
5271 @node Q3.3.6, Q3.4.1, Q3.3.5, Editing
|
|
|
5272 @unnumberedsubsec Q3.3.6: Why does @kbd{M-w} take so long?
|
|
2417
|
5273
|
|
|
5274 It actually doesn't. It leaves the region visible for a second so that
|
|
|
5275 you can see what area is being yanked. If you start working, though, it
|
|
|
5276 will immediately complete its operation. In other words, it will only
|
|
|
5277 delay for a second if you let it.
|
|
|
5278
|
|
2459
|
5279 @unnumberedsec 3.4: Editing Source Code
|
|
|
5280
|
|
|
5281 @node Q3.4.1, Q3.4.2, Q3.3.6, Editing
|
|
|
5282 @unnumberedsubsec Q3.4.1: I do not like cc-mode. How do I use the old c-mode?
|
|
2417
|
5283
|
|
|
5284 Well, first off, consider if you really want to do this. cc-mode is
|
|
|
5285 much more powerful than the old c-mode. If you're having trouble
|
|
|
5286 getting your old offsets to work, try using @code{c-set-offset} instead.
|
|
|
5287 You might also consider using the package @code{cc-compat}.
|
|
|
5288
|
|
|
5289 But, if you still insist, add the following lines to your @file{init.el}:
|
|
|
5290
|
|
|
5291 @lisp
|
|
|
5292 (fmakunbound 'c-mode)
|
|
|
5293 (makunbound 'c-mode-map)
|
|
|
5294 (fmakunbound 'c++-mode)
|
|
|
5295 (makunbound 'c++-mode-map)
|
|
|
5296 (makunbound 'c-style-alist)
|
|
|
5297 (load-library "old-c-mode")
|
|
|
5298 (load-library "old-c++-mode")
|
|
|
5299 @end lisp
|
|
|
5300
|
|
|
5301 This must be done before any other reference is made to either c-mode or
|
|
|
5302 c++-mode.
|
|
|
5303
|
|
2459
|
5304 @node Q3.4.2, , Q3.4.1, Editing
|
|
|
5305 @unnumberedsubsec Q3.4.2: How do you make XEmacs indent CL if-clauses correctly?
|
|
2417
|
5306
|
|
|
5307 I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the
|
|
|
5308 same amount instead of indenting the 3rd clause differently from the
|
|
|
5309 first two.
|
|
|
5310
|
|
2459
|
5311 The package @code{cl-indent} that comes with XEmacs sets up this kind
|
|
|
5312 of indentation by default. @code{cl-indent} also knows about many
|
|
|
5313 other CL-specific forms. To use @code{cl-indent}, one can do this:
|
|
2417
|
5314
|
|
|
5315 @lisp
|
|
2459
|
5316 (setq lisp-indent-function 'common-lisp-indent-function)
|
|
2417
|
5317 @end lisp
|
|
|
5318
|
|
|
5319 One can also customize @file{cl-indent.el} so it mimics the default
|
|
|
5320 @code{if} indentation @code{then} indented more than the @code{else}.
|
|
|
5321 Here's how:
|
|
|
5322
|
|
|
5323 @lisp
|
|
|
5324 (put 'if 'common-lisp-indent-function '(nil nil &body))
|
|
|
5325 @end lisp
|
|
|
5326
|
|
2459
|
5327 @node Display, External Subsystems, Editing, Top
|
|
|
5328 @unnumbered 4 Display Functions
|
|
428
|
5329
|
|
|
5330 This is part 4 of the XEmacs Frequently Asked Questions list. This
|
|
2459
|
5331 section is devoted to the display-related capabilities of XEmacs
|
|
|
5332 (fonts, colors, modeline, menubar, toolbar, scrollbar, etc.) and how
|
|
|
5333 to customize them.
|
|
|
5334
|
|
|
5335 @menu
|
|
|
5336 4.0: Textual Fonts and Colors
|
|
|
5337 * Q4.0.1:: How do I specify a font?
|
|
|
5338 * Q4.0.2:: How do I set the text, menu and modeline fonts?
|
|
|
5339 * Q4.0.3:: How can I set color options from @file{init.el}?
|
|
|
5340 * Q4.0.4:: How can I set the colors when highlighting a region?
|
|
|
5341 * Q4.0.5:: How can I limit color map usage?
|
|
|
5342 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them.
|
|
|
5343 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs?
|
|
|
5344 * Q4.0.8:: How do I display non-ASCII characters?
|
|
|
5345 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}.
|
|
|
5346
|
|
|
5347 4.1: Syntax Highlighting (Font Lock)
|
|
|
5348 * Q4.1.1:: How can I do source code highlighting using font-lock?
|
|
|
5349 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
5350
|
|
|
5351 4.2: The Modeline
|
|
|
5352 * Q4.2.1:: How can I make the modeline go away?
|
|
|
5353 * Q4.2.2:: How do you have XEmacs display the line number in the modeline?
|
|
|
5354 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline?
|
|
|
5355 * Q4.2.4:: How can I change the modeline color based on the mode used?
|
|
|
5356
|
|
|
5357 4.3: The Cursor
|
|
|
5358 * Q4.3.1:: Is there a way to make the bar cursor thicker?
|
|
|
5359 * Q4.3.2:: Is there a way to get back the block cursor?
|
|
|
5360 * Q4.3.3:: Can I make the cursor blink?
|
|
|
5361
|
|
|
5362 4.4: The Menubar
|
|
|
5363 * Q4.4.1:: How do I get rid of the menubar?
|
|
|
5364 * Q4.4.2:: How can I customize the menubar?
|
|
|
5365 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
5366 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
5367 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
5368
|
|
|
5369 4.5: The Toolbar
|
|
|
5370 * Q4.5.1:: How do I get rid of the toolbar?
|
|
|
5371 * Q4.5.2:: How can I customize the toolbar?
|
|
|
5372 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar?
|
|
|
5373 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar
|
|
|
5374
|
|
|
5375 4.6: Scrollbars and Scrolling
|
|
|
5376 * Q4.6.1:: How can I disable the scrollbar?
|
|
|
5377 * Q4.6.2:: How can I change the scrollbar width?
|
|
|
5378 * Q4.6.3:: How can I use resources to change scrollbar colors?
|
|
|
5379 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this?
|
|
|
5380 * Q4.6.5:: Scrolling one line at a time.
|
|
|
5381 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
5382 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
5383
|
|
|
5384 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
5385 * Q4.7.1:: How can I disable the gutter tabs?
|
|
|
5386 * Q4.7.2:: How can I disable the progress bar?
|
|
|
5387 * Q4.7.3:: There are bugs in the gutter or widgets.
|
|
|
5388 * Q4.7.4:: How can I customize the gutter or gutter tabs?
|
|
|
5389 @end menu
|
|
|
5390
|
|
|
5391 @unnumberedsec 4.0: Textual Fonts and Colors
|
|
|
5392
|
|
|
5393 @node Q4.0.1, Q4.0.2, Display, Display
|
|
|
5394 @unnumberedsubsec Q4.0.1: How do I specify a font?
|
|
|
5395
|
|
|
5396 #### Update me.
|
|
|
5397
|
|
|
5398 In 21.4 and above, you can use the @samp{Options} menu to change the font.
|
|
|
5399 You can also do it in your init file, e.g. like this (for MS Windows):
|
|
|
5400
|
|
|
5401 @display
|
|
|
5402 (set-face-font 'default "Lucida Console:Regular:10")
|
|
|
5403 (set-face-font 'modeline "MS Sans Serif:Regular:10")
|
|
|
5404 @end display
|
|
|
5405
|
|
|
5406 @node Q4.0.2, Q4.0.3, Q4.0.1, Display
|
|
|
5407 @unnumberedsubsec Q4.0.2: How do I set the text, menu and modeline fonts?
|
|
|
5408
|
|
|
5409 #### Update me.
|
|
|
5410
|
|
|
5411 Note that you should use @samp{Emacs.} and not @samp{Emacs*} when
|
|
|
5412 setting face values.
|
|
|
5413
|
|
|
5414 In @file{.Xresources}:
|
|
|
5415
|
|
|
5416 @example
|
|
|
5417 Emacs.default.attributeFont: -*-*-medium-r-*-*-*-120-*-*-m-*-*-*
|
|
|
5418 Emacs*menubar*font: fixed
|
|
|
5419 Emacs.modeline.attributeFont: fixed
|
|
|
5420 @end example
|
|
|
5421
|
|
|
5422 This is confusing because @samp{default} and @samp{modeline} are face
|
|
|
5423 names, and can be found listed with all faces in the current mode by
|
|
|
5424 using @kbd{M-x set-face-font (enter) ?}. They use the face-specific
|
|
|
5425 resource @samp{attributeFont}.
|
|
|
5426
|
|
|
5427 On the other hand, @samp{menubar} is a normal X thing that uses the
|
|
|
5428 resource @samp{font}. With Motif it @emph{may be} necessary to use
|
|
|
5429 @samp{fontList} @emph{instead of} @samp{font}. In @emph{non-Motif}
|
|
|
5430 configurations with Mule it @emph{is} necessary to use @samp{fontSet}
|
|
|
5431 instead of @samp{font}. (Sorry, there just is no simple recipe here.)
|
|
|
5432
|
|
|
5433 @node Q4.0.3, Q4.0.4, Q4.0.2, Display
|
|
|
5434 @unnumberedsubsec Q4.0.3: How can I set color options from @file{init.el}?
|
|
|
5435
|
|
|
5436 How can I set the most commonly used color options from my
|
|
|
5437 @file{init.el} instead of from my @file{.Xresources}?
|
|
|
5438
|
|
|
5439 Like this:
|
|
|
5440
|
|
|
5441 @lisp
|
|
|
5442 (set-face-background 'default "bisque") ; frame background
|
|
|
5443 (set-face-foreground 'default "black") ; normal text
|
|
|
5444 (set-face-background 'zmacs-region "red") ; When selecting w/
|
|
|
5445 ; mouse
|
|
|
5446 (set-face-foreground 'zmacs-region "yellow")
|
|
|
5447 (set-face-font 'default "*courier-bold-r*120-100-100*")
|
|
|
5448 (set-face-background 'highlight "blue") ; Ie when selecting
|
|
|
5449 ; buffers
|
|
|
5450 (set-face-foreground 'highlight "yellow")
|
|
|
5451 (set-face-background 'modeline "blue") ; Line at bottom
|
|
|
5452 ; of buffer
|
|
|
5453 (set-face-foreground 'modeline "white")
|
|
|
5454 (set-face-font 'modeline "*bold-r-normal*140-100-100*")
|
|
|
5455 (set-face-background 'isearch "yellow") ; When highlighting
|
|
|
5456 ; while searching
|
|
|
5457 (set-face-foreground 'isearch "red")
|
|
|
5458 (setq x-pointer-foreground-color "black") ; Adds to bg color,
|
|
|
5459 ; so keep black
|
|
|
5460 (setq x-pointer-background-color "blue") ; This is color
|
|
|
5461 ; you really
|
|
|
5462 ; want ptr/crsr
|
|
|
5463 @end lisp
|
|
|
5464
|
|
|
5465 @node Q4.0.4, Q4.0.5, Q4.0.3, Display
|
|
|
5466 @unnumberedsubsec Q4.0.4: How can I set the colors when highlighting a region?
|
|
|
5467
|
|
|
5468 How can I set the background/foreground colors when highlighting a
|
|
|
5469 region?
|
|
|
5470
|
|
|
5471 You can change the face @code{zmacs-region} either in your
|
|
|
5472 @file{.Xresources}:
|
|
|
5473
|
|
|
5474 @example
|
|
|
5475 Emacs.zmacs-region.attributeForeground: firebrick
|
|
|
5476 Emacs.zmacs-region.attributeBackground: lightseagreen
|
|
|
5477 @end example
|
|
|
5478
|
|
|
5479 or in your @file{init.el}:
|
|
|
5480
|
|
|
5481 @lisp
|
|
|
5482 (set-face-background 'zmacs-region "red")
|
|
|
5483 (set-face-foreground 'zmacs-region "yellow")
|
|
|
5484 @end lisp
|
|
|
5485
|
|
|
5486 @node Q4.0.5, Q4.0.6, Q4.0.4, Display
|
|
|
5487 @unnumberedsubsec Q4.0.5: How can I limit color map usage?
|
|
|
5488
|
|
|
5489 I'm using Netscape (or another color grabber like XEmacs);
|
|
|
5490 is there any way to limit the number of available colors in the color map?
|
|
|
5491
|
|
|
5492 Answer: No, but you can start Netscape before XEmacs, and it will use
|
|
|
5493 the closest available color if the colormap is full. You can also limit
|
|
|
5494 the number of colors Netscape uses, using the flags -mono, -ncols <#> or
|
|
|
5495 -install (for mono, limiting to <#> colors, or for using a private color
|
|
|
5496 map).
|
|
|
5497
|
|
|
5498 If you have the money, another solution would be to use a truecolor or
|
|
|
5499 direct color video.
|
|
|
5500
|
|
|
5501 @node Q4.0.6, Q4.0.7, Q4.0.5, Display
|
|
|
5502 @unnumberedsubsec Q4.0.6: My tty supports color, but XEmacs doesn't use them.
|
|
|
5503
|
|
|
5504 XEmacs tries to automatically determine whether your tty supports color,
|
|
|
5505 but sometimes guesses wrong. In that case, you can make XEmacs Do The
|
|
|
5506 Right Thing using this Lisp code:
|
|
|
5507
|
|
|
5508 @lisp
|
|
|
5509 (if (eq 'tty (device-type))
|
|
|
5510 (set-device-class nil 'color))
|
|
|
5511 @end lisp
|
|
|
5512
|
|
|
5513 @node Q4.0.7, Q4.0.8, Q4.0.6, Display
|
|
|
5514 @unnumberedsubsec Q4.0.7: Can I have pixmap backgrounds in XEmacs?
|
|
|
5515 @c New
|
|
|
5516 @email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes:
|
|
|
5517
|
|
|
5518 @quotation
|
|
|
5519 There are several ways to do it. For example, you could specify a
|
|
|
5520 default pixmap image to use in your @file{~/.Xresources}, e.g.,
|
|
|
5521
|
|
|
5522
|
|
|
5523 @example
|
|
|
5524 Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm
|
|
|
5525 @end example
|
|
|
5526
|
|
|
5527
|
|
|
5528 and then reload ~/.Xresources and restart XEmacs. Alternatively,
|
|
|
5529 since each face can have its own pixmap background, a better way
|
|
|
5530 would be to set a face's pixmap within your XEmacs init file, e.g.,
|
|
|
5531
|
|
|
5532 @lisp
|
|
|
5533 (set-face-background-pixmap 'default "/path/to/image.xpm")
|
|
|
5534 (set-face-background-pixmap 'bold "/path/to/another_image.xpm")
|
|
|
5535 @end lisp
|
|
|
5536
|
|
|
5537 and so on. You can also do this interactively via @kbd{M-x edit-faces}.
|
|
|
5538
|
|
|
5539 @end quotation
|
|
|
5540
|
|
|
5541 @node Q4.0.8, Q4.0.9, Q4.0.7, Display
|
|
|
5542 @unnumberedsubsec Q4.0.8: How do I display non-ASCII characters?
|
|
|
5543 @c New
|
|
|
5544
|
|
|
5545 If you're using a Mule-enabled XEmacs, then display is automatic. If
|
|
|
5546 you're not seeing the characters you expect, either (1) you don't have
|
|
|
5547 appropriate fonts available or (2) XEmacs did not correctly detect the
|
|
|
5548 coding system (@pxref{Recognize Coding, , , xemacs}). In case (1),
|
|
|
5549 install fonts as is customary for your platform. In case (2), you
|
|
|
5550 need to tell XEmacs explicitly what coding systems you're using.
|
|
|
5551 @ref{Specify Coding, , , xemacs}.
|
|
|
5552
|
|
|
5553 If your XEmacs is not Mule-enabled, and for some reason getting a
|
|
|
5554 Mule-enabled XEmacs seems like the wrong thing to do, all is not lost.
|
|
|
5555 You can arrange it by brute force. In @file{event-Xt.c} (suppress the
|
|
|
5556 urge to look in this file---play Doom instead, because you'll survive
|
|
|
5557 longer), it is written:
|
|
|
5558
|
|
|
5559 @quotation
|
|
|
5560 In a non-Mule world, a user can still have a multi-lingual editor, by
|
|
|
5561 doing @code{(set-face-font "-*-iso8859-2" (current-buffer))} for all
|
|
|
5562 their Latin-2 buffers, etc.
|
|
|
5563 @end quotation
|
|
|
5564
|
|
|
5565 For the related problem of @emph{inputting} non-ASCII characters in a
|
|
|
5566 non-Mule XEmacs, @xref{Q3.0.6, How can you type in special characters
|
|
|
5567 in XEmacs?}.
|
|
|
5568
|
|
|
5569 @node Q4.0.9, Q4.1.1, Q4.0.8, Display
|
|
|
5570 @unnumberedsubsec Q4.0.9: Font selections in don't get saved after @code{Save Options}.
|
|
|
5571
|
|
|
5572 @email{mannj@@ll.mit.edu, John Mann} writes:
|
|
|
5573
|
|
|
5574 @quotation
|
|
|
5575 You have to go to @samp{Options->Menubars} and unselect
|
|
|
5576 @samp{Frame-Local Font Menu}. If this option is selected, font changes
|
|
|
5577 are only applied to the @emph{current} frame and do @emph{not} get saved
|
|
|
5578 when you save options.
|
|
|
5579 @end quotation
|
|
|
5580
|
|
|
5581 Also, set the following in your @file{init.el}:
|
|
|
5582
|
|
|
5583 @lisp
|
|
|
5584 (setq options-save-faces t)
|
|
|
5585 @end lisp
|
|
|
5586
|
|
|
5587 @unnumberedsec 4.1: Syntax Highlighting (Font Lock)
|
|
|
5588
|
|
|
5589 @node Q4.1.1, Q4.1.2, Q4.0.9, Display
|
|
|
5590 @unnumberedsubsec Q4.1.1: How can I do source code highlighting using font-lock?
|
|
|
5591
|
|
|
5592 For most modes, font-lock is already set up and just needs to be turned
|
|
|
5593 on. This can be done by adding the line:
|
|
|
5594
|
|
|
5595 @lisp
|
|
|
5596 (require 'font-lock)
|
|
|
5597 @end lisp
|
|
|
5598
|
|
|
5599 to your @file{init.el}. (You can turn it on for the
|
|
|
5600 current buffer and session only by @kbd{M-x font-lock-mode}.) See the
|
|
|
5601 file @file{etc/sample.init.el} (@file{etc/sample.emacs} in XEmacs
|
|
|
5602 versions prior to 21.4) for more information.
|
|
|
5603
|
|
|
5604 @c the old way:
|
|
|
5605 @c (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
|
|
|
5606 @c (add-hook 'dired-mode-hook 'turn-on-font-lock)
|
|
|
5607
|
|
|
5608 See also @code{Syntax Highlighting} from the @code{Options} menu.
|
|
|
5609 Remember to save options.
|
|
|
5610
|
|
|
5611 @node Q4.1.2, Q4.2.1, Q4.1.1, Display
|
|
|
5612 @unnumberedsubsec Q4.1.2: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
5613
|
|
|
5614 Use the following code in your @file{init.el}:
|
|
|
5615
|
|
|
5616 @lisp
|
|
|
5617 (setq-default font-lock-maximum-decoration t)
|
|
|
5618 @end lisp
|
|
|
5619
|
|
|
5620 See also @code{Syntax Highlighting} from the @code{Options} menu.
|
|
|
5621 Remember to save options.
|
|
|
5622
|
|
|
5623 @unnumberedsec 4.2: The Modeline
|
|
|
5624
|
|
|
5625 @node Q4.2.1, Q4.2.2, Q4.1.2, Display
|
|
|
5626 @unnumberedsubsec Q4.2.1: How can I make the modeline go away?
|
|
|
5627
|
|
|
5628 @lisp
|
|
|
5629 (set-specifier has-modeline-p nil)
|
|
|
5630 @end lisp
|
|
|
5631
|
|
|
5632 @node Q4.2.2, Q4.2.3, Q4.2.1, Display
|
|
|
5633 @unnumberedsubsec Q4.2.2: How do you have XEmacs display the line number in the modeline?
|
|
|
5634
|
|
|
5635 Add the following line to your @file{init.el} file to
|
|
|
5636 display the line number:
|
|
|
5637
|
|
|
5638 @lisp
|
|
|
5639 (line-number-mode 1)
|
|
|
5640 @end lisp
|
|
|
5641
|
|
|
5642 Use the following to display the column number:
|
|
|
5643
|
|
|
5644 @lisp
|
|
|
5645 (column-number-mode 1)
|
|
|
5646 @end lisp
|
|
|
5647
|
|
|
5648 Or select from the @code{Options} menu
|
|
|
5649 @iftex
|
|
|
5650 @*
|
|
|
5651 @end iftex
|
|
|
5652 @code{Advanced (Customize)->Emacs->Editing->Basics->Line Number Mode}
|
|
|
5653 and/or
|
|
|
5654 @iftex
|
|
|
5655 @*
|
|
|
5656 @end iftex
|
|
|
5657 @code{Advanced (Customize)->Emacs->Editing->Basics->Column Number Mode}
|
|
|
5658
|
|
|
5659 Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
|
|
|
5660
|
|
|
5661 @node Q4.2.3, Q4.2.4, Q4.2.2, Display
|
|
|
5662 @unnumberedsubsec Q4.2.3: How do I get XEmacs to put the time of day on the modeline?
|
|
|
5663
|
|
|
5664 Add the following line to your @file{init.el} file to
|
|
|
5665 display the time:
|
|
|
5666
|
|
|
5667 @lisp
|
|
|
5668 (display-time)
|
|
|
5669 @end lisp
|
|
|
5670
|
|
|
5671 See @code{Customize} from the @code{Options} menu for customization.
|
|
|
5672
|
|
|
5673 @node Q4.2.4, Q4.3.1, Q4.2.3, Display
|
|
|
5674 @unnumberedsubsec Q4.2.4: How can I change the modeline color based on the mode used?
|
|
|
5675
|
|
|
5676 You can use something like the following:
|
|
|
5677
|
|
|
5678 @lisp
|
|
|
5679 (add-hook 'lisp-mode-hook
|
|
|
5680 (lambda ()
|
|
|
5681 (set-face-background 'modeline "red" (current-buffer))))
|
|
|
5682 @end lisp
|
|
|
5683
|
|
|
5684 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
|
|
|
5685 colors change from the default set in your @file{init.el}.
|
|
|
5686 The change will only be made in the buffer you just entered (which
|
|
|
5687 contains the Lisp file you are editing) and will not affect the modeline
|
|
|
5688 colors anywhere else.
|
|
|
5689
|
|
|
5690 Notes:
|
|
|
5691
|
|
|
5692 @itemize @bullet
|
|
|
5693
|
|
|
5694 @item The hook is the mode name plus @code{-hook}. eg. c-mode-hook,
|
|
|
5695 c++-mode-hook, emacs-lisp-mode-hook (used for your
|
|
|
5696 @file{init.el} or a @file{xx.el} file),
|
|
|
5697 lisp-interaction-mode-hook (the @samp{*scratch*} buffer),
|
|
|
5698 text-mode-hook, etc.
|
|
|
5699
|
|
|
5700 @item
|
|
|
5701 Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)},
|
|
|
5702 otherwise you will erase anything that anybody has already put on the
|
|
|
5703 hook.
|
|
|
5704
|
|
|
5705 @item
|
|
|
5706 You can also do @code{(set-face-font 'modeline @var{font})},
|
|
|
5707 eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*"
|
|
|
5708 (current-buffer))} if you wish the modeline font to vary based on the
|
|
|
5709 current mode.
|
|
|
5710 @end itemize
|
|
|
5711
|
|
|
5712 There are additional modeline faces, @code{modeline-buffer-id},
|
|
|
5713 @code{modeline-mousable}, and @code{modeline-mousable-minor-mode}, which
|
|
|
5714 you may want to customize.
|
|
|
5715
|
|
|
5716 @unnumberedsec 4.3: The Cursor
|
|
|
5717
|
|
|
5718 @node Q4.3.1, Q4.3.2, Q4.2.4, Display
|
|
|
5719 @unnumberedsubsec Q4.3.1: Is there a way to make the bar cursor thicker?
|
|
|
5720
|
|
|
5721 I'd like to have the bar cursor a little thicker, as I tend to "lose" it
|
|
|
5722 often.
|
|
|
5723
|
|
|
5724 For a 1 pixel bar cursor, use:
|
|
|
5725
|
|
|
5726 @lisp
|
|
|
5727 (setq bar-cursor t)
|
|
|
5728 @end lisp
|
|
|
5729
|
|
|
5730 For a 2 pixel bar cursor, use:
|
|
|
5731
|
|
|
5732 @lisp
|
|
|
5733 (setq bar-cursor 'anything-else)
|
|
|
5734 @end lisp
|
|
|
5735
|
|
|
5736 You can also change these with Customize.
|
|
|
5737 Select from the @code{Options} menu
|
|
|
5738 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
|
|
|
5739 @kbd{M-x customize @key{RET} display @key{RET}}.
|
|
|
5740
|
|
|
5741 You can use a color to make it stand out better:
|
|
|
5742
|
|
|
5743 @example
|
|
|
5744 Emacs*cursorColor: Red
|
|
|
5745 @end example
|
|
|
5746
|
|
|
5747 @node Q4.3.2, Q4.3.3, Q4.3.1, Display
|
|
|
5748 @unnumberedsubsec Q4.3.2: Is there a way to get back the block cursor?
|
|
|
5749
|
|
|
5750 @lisp
|
|
|
5751 (setq bar-cursor nil)
|
|
|
5752 @end lisp
|
|
|
5753
|
|
|
5754 You can also change this with Customize.
|
|
|
5755 Select from the @code{Options} menu
|
|
|
5756 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
|
|
|
5757 @kbd{M-x customize @key{RET} display @key{RET}}.
|
|
|
5758
|
|
|
5759 @node Q4.3.3, Q4.4.1, Q4.3.2, Display
|
|
|
5760 @unnumberedsubsec Q4.3.3: Can I make the cursor blink?
|
|
|
5761
|
|
|
5762 Yes, like this:
|
|
|
5763
|
|
|
5764 @lisp
|
|
|
5765 (blink-cursor-mode)
|
|
|
5766 @end lisp
|
|
|
5767
|
|
|
5768 This function toggles between a steady cursor and a blinking cursor.
|
|
|
5769 You may also set this mode from the menu bar by selecting
|
|
|
5770 @samp{Options->Display->Blinking Cursor}. Remember to save options.
|
|
|
5771
|
|
|
5772 @unnumberedsec 4.4: The Menubar
|
|
|
5773
|
|
|
5774 @node Q4.4.1, Q4.4.2, Q4.3.3, Display
|
|
|
5775 @unnumberedsubsec Q4.4.1: How do I get rid of the menubar?
|
|
|
5776
|
|
|
5777 @lisp
|
|
|
5778 (set-specifier menubar-visible-p nil)
|
|
|
5779 @end lisp
|
|
|
5780
|
|
|
5781 @node Q4.4.2, Q4.4.3, Q4.4.1, Display
|
|
|
5782 @unnumberedsubsec Q4.4.2: How can I customize the menubar?
|
|
|
5783
|
|
|
5784 For an extensive menubar, add this line to your @file{init.el}:
|
|
|
5785
|
|
|
5786 @lisp
|
|
|
5787 (load "big-menubar")
|
|
|
5788 @end lisp
|
|
|
5789
|
|
|
5790 If you'd like to write your own, this file provides as good a set of
|
|
|
5791 examples as any to start from. The file is located in edit-utils
|
|
|
5792 package.
|
|
|
5793
|
|
|
5794 @node Q4.4.3, Q4.4.4, Q4.4.2, Display
|
|
|
5795 @unnumberedsubsec Q4.4.3: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
5796
|
|
|
5797 #### Write me.
|
|
|
5798
|
|
|
5799 @node Q4.4.4, Q4.4.5, Q4.4.3, Display
|
|
|
5800 @unnumberedsubsec Q4.4.4: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
5801
|
|
|
5802 Add the following to your @file{init.el} (suit to fit):
|
|
|
5803
|
|
|
5804 @lisp
|
|
|
5805 (setq buffers-menu-max-size 20)
|
|
|
5806 @end lisp
|
|
|
5807
|
|
|
5808 For no limit, use an argument of @samp{nil}.
|
|
|
5809
|
|
|
5810 You can also change this with Customize. Select from the
|
|
|
5811 @code{Options} menu
|
|
|
5812 @code{Advanced (Customize)->Emacs->Environment->Menu->Buffers Menu->Max Size...}
|
|
|
5813 or type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}.
|
|
|
5814
|
|
|
5815 @node Q4.4.5, Q4.5.1, Q4.4.4, Display
|
|
|
5816 @unnumberedsubsec Q4.4.5: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
5817
|
|
|
5818 I am trying to use a resource like @code{Emacs*menubar*font} to set the
|
|
|
5819 font of the menubar but it's not working.
|
|
|
5820
|
|
|
5821 In Motif, the use of @samp{font} resources is obsoleted in order to
|
|
|
5822 support internationalization. If you are using the real Motif menubar,
|
|
|
5823 this resource is not recognized at all; you have to say:
|
|
|
5824
|
|
|
5825 @example
|
|
|
5826 Emacs*menubar*fontList: FONT
|
|
|
5827 @end example
|
|
|
5828
|
|
|
5829 If you are using the Lucid menubar, for backward compatibility with
|
|
|
5830 existing user configurations, the @samp{font} resource is recognized.
|
|
|
5831 Since this is not supported by Motif itself, the code is a kludge and
|
|
|
5832 the @samp{font} resource will be recognized only if the @samp{fontList}
|
|
|
5833 resource resource is unset. This means that the resource
|
|
|
5834
|
|
|
5835 @example
|
|
|
5836 *fontList: FONT
|
|
|
5837 @end example
|
|
|
5838
|
|
|
5839 will override
|
|
|
5840
|
|
|
5841 @example
|
|
|
5842 Emacs*menubar*font: FONT
|
|
|
5843 @end example
|
|
|
5844
|
|
|
5845 even though the latter is more specific.
|
|
|
5846
|
|
|
5847 In non-Motif configurations using @samp{--with-mule} and
|
|
|
5848 @samp{--with-xfs} it @emph{is} necessary to use the @code{fontSet}
|
|
|
5849 resource @emph{instead of} the @code{font} resource. The backward
|
|
|
5850 compatibility kludge was never implemented for non-Motif builds.
|
|
|
5851 Example:
|
|
|
5852
|
|
|
5853 @example
|
|
|
5854 *fontSet: FONT
|
|
|
5855 @end example
|
|
|
5856
|
|
|
5857 @unnumberedsec 4.5: The Toolbar
|
|
|
5858
|
|
|
5859 @node Q4.5.1, Q4.5.2, Q4.4.5, Display
|
|
|
5860 @unnumberedsubsec Q4.5.1: How do I get rid of the toolbar?
|
|
|
5861
|
|
|
5862 #### Write me.
|
|
|
5863
|
|
|
5864 @node Q4.5.2, Q4.5.3, Q4.5.1, Display
|
|
|
5865 @unnumberedsubsec Q4.5.2: How can I customize the toolbar?
|
|
|
5866
|
|
|
5867 #### Write me.
|
|
|
5868
|
|
|
5869 @node Q4.5.3, Q4.5.4, Q4.5.2, Display
|
|
|
5870 @unnumberedsubsec Q4.5.3: How can I bind a key to a function to toggle the toolbar?
|
|
|
5871
|
|
|
5872 Try something like:
|
|
|
5873
|
|
|
5874 @lisp
|
|
|
5875 (defun my-toggle-toolbar ()
|
|
|
5876 (interactive)
|
|
|
5877 (set-specifier default-toolbar-visible-p
|
|
|
5878 (not (specifier-instance default-toolbar-visible-p))))
|
|
|
5879 (global-set-key "\C-xT" 'my-toggle-toolbar)
|
|
|
5880 @end lisp
|
|
|
5881
|
|
|
5882 @ignore
|
|
|
5883 @c Probably not relevant any more
|
|
|
5884 There are redisplay bugs in 19.14 that may make the preceding result in
|
|
|
5885 a messed-up display, especially for frames with multiple windows. You
|
|
|
5886 may need to resize the frame before XEmacs completely realizes the
|
|
|
5887 toolbar is really gone.
|
|
|
5888 @end ignore
|
|
|
5889
|
|
|
5890 Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct
|
|
|
5891 code.
|
|
|
5892
|
|
|
5893 @node Q4.5.4, Q4.6.1, Q4.5.3, Display
|
|
|
5894 @unnumberedsubsec Q4.5.4: @samp{Can't instantiate image error...} in toolbar
|
|
|
5895
|
|
|
5896 @email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes:
|
|
|
5897
|
|
|
5898 I just installed the XEmacs (20.4-2) RPMS that I downloaded from
|
|
|
5899 @uref{http://www.xemacs.org/}. Everything works fine, except that when
|
|
|
5900 I place my mouse over the toolbar, it beeps and gives me this message:
|
|
|
5901
|
|
|
5902 @example
|
|
|
5903 Can't instantiate image (probably cached):
|
|
|
5904 [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data
|
|
|
5905 (16 16 <strange control characters> ...
|
|
|
5906 @end example
|
|
|
5907
|
|
|
5908 @email{kyle_jones@@wonderworks.com, Kyle Jones} writes:
|
|
|
5909 @quotation
|
|
|
5910 This is problem specific to some Chips and Technologies video
|
|
|
5911 chips, when running XFree86. Putting
|
|
|
5912
|
|
|
5913 @code{Option "sw_cursor"}
|
|
|
5914
|
|
|
5915 in @file{XF86Config} gets rid of the problem.
|
|
|
5916 @end quotation
|
|
|
5917
|
|
|
5918 @unnumberedsec 4.6: Scrollbars and Scrolling
|
|
|
5919
|
|
|
5920 @node Q4.6.1, Q4.6.2, Q4.5.4, Display
|
|
|
5921 @unnumberedsubsec Q4.6.1: How can I disable the scrollbar?
|
|
|
5922
|
|
|
5923 To disable them for all frames, add the following line to
|
|
|
5924 your @file{.Xresources}:
|
|
|
5925
|
|
|
5926 @example
|
|
|
5927 Emacs.scrollBarWidth: 0
|
|
|
5928 @end example
|
|
|
5929
|
|
|
5930 Or select @samp{Options->Display->Scrollbars}.
|
|
|
5931 Remember to save options.
|
|
|
5932
|
|
|
5933 To turn the scrollbar off on a per-frame basis, use the following
|
|
|
5934 function:
|
|
|
5935
|
|
|
5936 @lisp
|
|
|
5937 (set-specifier scrollbar-width 0 (selected-frame))
|
|
|
5938 @end lisp
|
|
|
5939
|
|
|
5940 You can actually turn the scrollbars on at any level you want by
|
|
|
5941 substituting for (selected-frame) in the above command. For example, to
|
|
|
5942 turn the scrollbars off only in a single buffer:
|
|
|
5943
|
|
|
5944 @lisp
|
|
|
5945 (set-specifier scrollbar-width 0 (current-buffer))
|
|
|
5946 @end lisp
|
|
|
5947
|
|
|
5948 @node Q4.6.2, Q4.6.3, Q4.6.1, Display
|
|
|
5949 @unnumberedsubsec Q4.6.2: How can I change the scrollbar width?
|
|
|
5950
|
|
|
5951 #### Write me.
|
|
|
5952
|
|
|
5953 @node Q4.6.3, Q4.6.4, Q4.6.2, Display
|
|
|
5954 @unnumberedsubsec Q4.6.3: How can I use resources to change scrollbar colors?
|
|
|
5955
|
|
|
5956 Here's a recap of how to use resources to change your scrollbar colors:
|
|
|
5957
|
|
|
5958 @example
|
|
|
5959 ! Motif scrollbars
|
|
|
5960
|
|
|
5961 Emacs*XmScrollBar.Background: skyblue
|
|
|
5962 Emacs*XmScrollBar.troughColor: lightgray
|
|
|
5963
|
|
|
5964 ! Athena scrollbars
|
|
|
5965
|
|
|
5966 Emacs*Scrollbar.Foreground: skyblue
|
|
|
5967 Emacs*Scrollbar.Background: lightgray
|
|
|
5968 @end example
|
|
|
5969
|
|
|
5970 Note the capitalization of @code{Scrollbar} for the Athena widget.
|
|
|
5971
|
|
|
5972 @node Q4.6.4, Q4.6.5, Q4.6.3, Display
|
|
|
5973 @unnumberedsubsec Q4.6.4: Moving the scrollbar can move the point; can I disable this?
|
|
|
5974
|
|
|
5975 When I move the scrollbar in an XEmacs window, it moves the point as
|
|
|
5976 well, which should not be the default behavior. Is this a bug or a
|
|
|
5977 feature? Can I disable it?
|
|
|
5978
|
|
|
5979 The current behavior is a feature, not a bug. Point remains at the same
|
|
|
5980 buffer position as long as that position does not scroll off the screen.
|
|
|
5981 In that event, point will end up in either the upper-left or lower-left
|
|
|
5982 hand corner.
|
|
|
5983
|
|
|
5984 This cannot be changed.
|
|
|
5985
|
|
|
5986 @node Q4.6.5, Q4.6.6, Q4.6.4, Display
|
|
|
5987 @unnumberedsubsec Q4.6.5: Scrolling one line at a time.
|
|
|
5988
|
|
|
5989 Can the cursor keys scroll the screen a line at a time, rather than the
|
|
|
5990 default half page jump? I tend it to find it disorienting.
|
|
|
5991
|
|
|
5992 Use the following:
|
|
|
5993
|
|
|
5994 @lisp
|
|
|
5995 (setq scroll-step 1)
|
|
|
5996 @end lisp
|
|
|
5997
|
|
|
5998 You can also change this with Customize. Select from the
|
|
|
5999 @code{Options} menu
|
|
|
6000 @code{Advanced (Customize)->Emacs->Environment->Windows->Scroll Step...}
|
|
|
6001 or type @kbd{M-x customize @key{RET} windows @key{RET}}.
|
|
|
6002
|
|
|
6003 @node Q4.6.6, Q4.6.7, Q4.6.5, Display
|
|
|
6004 @unnumberedsubsec Q4.6.6: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
6005
|
|
|
6006 Do @code{(setq truncate-lines t)} in the mode-hooks for any modes
|
|
|
6007 in which you want lines truncated.
|
|
|
6008
|
|
|
6009 More precisely: If @code{truncate-lines} is nil, horizontal scrollbars
|
|
|
6010 will never appear. Otherwise, they will appear only if the value of
|
|
|
6011 @code{scrollbar-height} for that buffer/window/etc. is non-zero. If you
|
|
|
6012 do
|
|
|
6013
|
|
|
6014 @lisp
|
|
|
6015 (set-specifier scrollbar-height 0)
|
|
|
6016 @end lisp
|
|
|
6017
|
|
|
6018 then horizontal scrollbars will not appear in truncated buffers unless
|
|
|
6019 the package specifically asked for them.
|
|
|
6020
|
|
|
6021 @node Q4.6.7, Q4.7.1, Q4.6.6, Display
|
|
|
6022 @unnumberedsubsec Q4.6.7: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
6023
|
|
|
6024 @code{auto-show-mode} controls whether or not a horizontal scrollbar
|
|
|
6025 magically appears when a line is too long to be displayed. This is
|
|
|
6026 enabled by default. To turn it off, put the following in your
|
|
|
6027 @file{init.el}:
|
|
|
6028
|
|
|
6029 @lisp
|
|
|
6030 (setq auto-show-mode nil)
|
|
|
6031 (setq-default auto-show-mode nil)
|
|
|
6032 @end lisp
|
|
|
6033
|
|
|
6034 @unnumberedsec 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
6035
|
|
|
6036 @node Q4.7.1, Q4.7.2, Q4.6.7, Display
|
|
|
6037 @unnumberedsubsec Q4.7.1: How can I disable the gutter tabs?
|
|
|
6038
|
|
|
6039 #### Write me.
|
|
|
6040
|
|
|
6041 @node Q4.7.2, Q4.7.3, Q4.7.1, Display
|
|
|
6042 @unnumberedsubsec Q4.7.2: How can I disable the progress bar?
|
|
|
6043
|
|
|
6044 #### Write me.
|
|
|
6045
|
|
|
6046 @node Q4.7.3, Q4.7.4, Q4.7.2, Display
|
|
|
6047 @unnumberedsubsec Q4.7.3: There are bugs in the gutter or widgets.
|
|
|
6048
|
|
|
6049 #### Write me.
|
|
|
6050
|
|
|
6051 @node Q4.7.4, , Q4.7.3, Display
|
|
|
6052 @unnumberedsubsec Q4.7.4: How can I customize the gutter or gutter tabs?
|
|
|
6053
|
|
|
6054 #### Write me.
|
|
|
6055
|
|
|
6056 @node External Subsystems, Internet, Display, Top
|
|
|
6057 @unnumbered 5 Interfacing with the Operating System and External Devices
|
|
|
6058
|
|
|
6059 This is part 5 of the XEmacs Frequently Asked Questions list. This
|
|
2417
|
6060 section is devoted to the various ways that XEmacs interfaces with the
|
|
|
6061 operating system, with other processes and with external devices such
|
|
|
6062 as speakers and the printer.
|
|
428
|
6063
|
|
|
6064 @menu
|
|
2459
|
6065 5.0: X Window System and Resources
|
|
|
6066 * Q5.0.1:: Where is a list of X resources?
|
|
|
6067 * Q5.0.2:: How can I detect a color display?
|
|
|
6068 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}?
|
|
|
6069 * Q5.0.4:: How can I have the window title area display the full path?
|
|
|
6070 * Q5.0.5:: @samp{xemacs -name junk} doesn't work?
|
|
|
6071 * Q5.0.6:: @samp{-iconic} doesn't work.
|
|
|
6072
|
|
|
6073 5.1: Microsoft Windows
|
|
|
6074 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
|
6075 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
|
6076
|
|
|
6077 5.2: Printing
|
|
|
6078 * Q5.2.1:: What do I need to change to make printing work?
|
|
|
6079 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer?
|
|
|
6080 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
|
6081 * Q5.2.4:: Can you print under MS Windows?
|
|
|
6082
|
|
|
6083 5.3: Sound
|
|
|
6084 * Q5.3.1:: How do I turn off the sound?
|
|
|
6085 * Q5.3.2:: How do I get funky sounds instead of a boring beep?
|
|
|
6086 * Q5.3.3:: What are NAS and ESD (EsounD)?
|
|
|
6087 * Q5.3.4:: Sunsite sounds don't play.
|
|
|
6088
|
|
|
6089 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
6090 * Q5.4.1:: What is an interior shell?
|
|
|
6091 * Q5.4.2:: How do I start up a second shell buffer?
|
|
|
6092 * Q5.4.3:: Telnet from shell filters too much
|
|
|
6093 * Q5.4.4:: Strange things are happening in Shell Mode.
|
|
|
6094 * Q5.4.5:: XEmacs complains "No such file or directory, diff"
|
|
2995
|
6095 * Q5.4.6:: Cygwin error "fork_copy: linked dll/bss pass 0 failed"
|
|
2459
|
6096
|
|
|
6097 5.5: Multiple Device Support
|
|
|
6098 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display?
|
|
|
6099 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
6100 * Q5.5.3:: How do I disable gnuserv from opening a new frame?
|
|
|
6101 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
|
6102 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
428
|
6103 @end menu
|
|
|
6104
|
|
2459
|
6105 @unnumberedsec 5.0: X Window System and Resources
|
|
|
6106
|
|
|
6107 @node Q5.0.1, Q5.0.2, External Subsystems, External Subsystems
|
|
|
6108 @unnumberedsubsec Q5.0.1: Where is a list of X resources?
|
|
2417
|
6109
|
|
|
6110 Search through the @file{NEWS} file for @samp{X Resources}. A fairly
|
|
|
6111 comprehensive list is given after it.
|
|
|
6112
|
|
|
6113 In addition, an @file{app-defaults} file @file{etc/Emacs.ad} is
|
|
|
6114 supplied, listing the defaults. The file @file{etc/sample.Xresources}
|
|
|
6115 gives a different set of defaults that you might consider for
|
|
|
6116 installation in your @file{~/.Xresources} file. It is nearly the same
|
|
|
6117 as @file{etc/Emacs.ad}, but a few entries are altered. Be careful about
|
|
|
6118 installing the contents of this file into your @file{.Xresources} (or
|
|
|
6119 legacy @file{.Xdefaults}) file if you use GNU Emacs under X11 as well.
|
|
|
6120
|
|
2459
|
6121 @node Q5.0.2, Q5.0.3, Q5.0.1, External Subsystems
|
|
|
6122 @unnumberedsubsec Q5.0.2: How can I detect a color display?
|
|
2417
|
6123
|
|
|
6124 You can test the return value of the function @code{(device-class)}, as
|
|
|
6125 in:
|
|
|
6126
|
|
|
6127 @lisp
|
|
|
6128 (when (eq (device-class) 'color)
|
|
|
6129 (set-face-foreground 'font-lock-comment-face "Grey")
|
|
|
6130 (set-face-foreground 'font-lock-string-face "Red")
|
|
|
6131 ....
|
|
|
6132 )
|
|
|
6133 @end lisp
|
|
|
6134
|
|
2459
|
6135 @node Q5.0.3, Q5.0.4, Q5.0.2, External Subsystems
|
|
|
6136 @unnumberedsubsec Q5.0.3: How can I get the icon to just say @samp{XEmacs}?
|
|
2417
|
6137
|
|
|
6138 I'd like the icon to just say @samp{XEmacs}, and not include the name of
|
|
|
6139 the current file in it.
|
|
|
6140
|
|
|
6141 Add the following line to your @file{init.el}:
|
|
|
6142
|
|
|
6143 @lisp
|
|
|
6144 (setq frame-icon-title-format "XEmacs")
|
|
|
6145 @end lisp
|
|
|
6146
|
|
2459
|
6147 @node Q5.0.4, Q5.0.5, Q5.0.3, External Subsystems
|
|
|
6148 @unnumberedsubsec Q5.0.4: How can I have the window title area display the full path?
|
|
2417
|
6149
|
|
|
6150 I'd like to have the window title area display the full directory/name
|
|
|
6151 of the current buffer file and not just the name.
|
|
|
6152
|
|
|
6153 Add the following line to your @file{init.el}:
|
|
|
6154
|
|
|
6155 @lisp
|
|
|
6156 (setq frame-title-format "%S: %f")
|
|
|
6157 @end lisp
|
|
|
6158
|
|
|
6159 A more sophisticated title might be:
|
|
|
6160
|
|
|
6161 @lisp
|
|
|
6162 (setq frame-title-format
|
|
|
6163 '("%S: " (buffer-file-name "%f"
|
|
|
6164 (dired-directory dired-directory "%b"))))
|
|
|
6165 @end lisp
|
|
|
6166
|
|
|
6167 That is, use the file name, or the dired-directory, or the buffer name.
|
|
|
6168
|
|
2459
|
6169 @node Q5.0.5, Q5.0.6, Q5.0.4, External Subsystems
|
|
|
6170 @unnumberedsubsec Q5.0.5: @samp{xemacs -name junk} doesn't work?
|
|
2417
|
6171
|
|
|
6172 When I run @samp{xterm -name junk}, I get an xterm whose class name
|
|
|
6173 according to xprop, is @samp{junk}. This is the way it's supposed to
|
|
|
6174 work, I think. When I run @samp{xemacs -name junk} the class name is
|
|
|
6175 not set to @samp{junk}. It's still @samp{emacs}. What does
|
|
|
6176 @samp{xemacs -name} really do? The reason I ask is that my window
|
|
|
6177 manager (fvwm) will make a window sticky and I use XEmacs to read my
|
|
|
6178 mail. I want that XEmacs window to be sticky, without having to use the
|
|
|
6179 window manager's function to set the window sticky. What gives?
|
|
|
6180
|
|
|
6181 @samp{xemacs -name} sets the application name for the program (that is,
|
|
|
6182 the thing which normally comes from @samp{argv[0]}). Using @samp{-name}
|
|
|
6183 is the same as making a copy of the executable with that new name. The
|
|
|
6184 @code{WM_CLASS} property on each frame is set to the frame-name, and the
|
|
|
6185 application-class. So, if you did @samp{xemacs -name FOO} and then
|
|
|
6186 created a frame named @var{BAR}, you'd get an X window with WM_CLASS =
|
|
|
6187 @code{( "BAR", "Emacs")}. However, the resource hierarchy for this
|
|
|
6188 widget would be:
|
|
|
6189
|
|
|
6190 @example
|
|
|
6191 Name: FOO .shell .container .BAR
|
|
|
6192 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
|
|
|
6193 @end example
|
|
|
6194
|
|
|
6195 instead of the default
|
|
|
6196
|
|
|
6197 @example
|
|
|
6198 Name: xemacs.shell .container .emacs
|
|
|
6199 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
|
|
|
6200 @end example
|
|
|
6201
|
|
|
6202
|
|
|
6203 It is arguable that the first element of WM_CLASS should be set to the
|
|
|
6204 application-name instead of the frame-name, but I think that's less
|
|
|
6205 flexible, since it does not give you the ability to have multiple frames
|
|
|
6206 with different WM_CLASS properties. Another possibility would be for
|
|
|
6207 the default frame name to come from the application name instead of
|
|
|
6208 simply being @samp{emacs}. However, at this point, making that change
|
|
|
6209 would be troublesome: it would mean that many users would have to make
|
|
|
6210 yet another change to their resource files (since the default frame name
|
|
|
6211 would suddenly change from @samp{emacs} to @samp{xemacs}, or whatever
|
|
|
6212 the executable happened to be named), so we'd rather avoid it.
|
|
|
6213
|
|
|
6214 To make a frame with a particular name use:
|
|
|
6215
|
|
|
6216 @lisp
|
|
|
6217 (make-frame '((name . "the-name")))
|
|
|
6218 @end lisp
|
|
|
6219
|
|
2459
|
6220 @node Q5.0.6, Q5.1.1, Q5.0.5, External Subsystems
|
|
|
6221 @unnumberedsubsec Q5.0.6: @samp{-iconic} doesn't work.
|
|
2417
|
6222
|
|
|
6223 When I start up XEmacs using @samp{-iconic} it doesn't work right.
|
|
|
6224 Using @samp{-unmapped} on the command line, and setting the
|
|
|
6225 @code{initiallyUnmapped} X Resource don't seem to help much either...
|
|
|
6226
|
|
|
6227 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
|
6228
|
|
|
6229 @quotation
|
|
|
6230 Ugh, this stuff is such an incredible mess that I've about given up
|
|
|
6231 getting it to work. The principal problem is numerous window-manager
|
|
|
6232 bugs...
|
|
|
6233 @end quotation
|
|
|
6234
|
|
2459
|
6235 @unnumberedsec 5.1: Microsoft Windows
|
|
|
6236
|
|
|
6237 @node Q5.1.1, Q5.1.2, Q5.0.6, External Subsystems
|
|
|
6238 @unnumberedsubsec Q5.1.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
2417
|
6239
|
|
|
6240 In his flavor of Emacs 20, Richard Stallman has renamed all the @samp{win32-*}
|
|
|
6241 symbols to @samp{w32-*}. Does XEmacs do the same?
|
|
|
6242
|
|
|
6243 We consider such a move counter-productive, thus we do not use the
|
|
|
6244 @samp{w32} prefix. (His rather questionable justification was that he
|
|
|
6245 did not consider Windows to be a "winning" platform.) However, the name
|
|
|
6246 @samp{Win32} is not particularly descriptive outside the Windows world,
|
|
|
6247 and using just @samp{windows-} would be too generic. So we chose a
|
|
|
6248 compromise, the prefix @samp{mswindows-} for Windows-related variables
|
|
|
6249 and functions.
|
|
|
6250
|
|
|
6251 Thus all the XEmacs variables and functions directly related to either
|
|
|
6252 the Windows GUI or OS are prefixed @samp{mswindows-} (except for a
|
|
|
6253 couple of debugging variables, prefixed @samp{debug-mswindows-}). From
|
|
|
6254 an architectural perspective, however, we believe that this is mostly a
|
|
|
6255 non-issue because there should be a very small number of
|
|
|
6256 window-systems-specific variables anyway. Whenever possible, we try to
|
|
|
6257 provide generic interfaces that apply to all window systems.
|
|
|
6258
|
|
|
6259 @c not true:
|
|
|
6260 @c The user variables
|
|
|
6261 @c that share functionality with existing NT Emacs variables are be named
|
|
|
6262 @c with our convention, but we provide the GNU Emacs names as
|
|
|
6263 @c compatibility aliases.
|
|
|
6264
|
|
2459
|
6265 @node Q5.1.2, Q5.2.1, Q5.1.1, External Subsystems
|
|
|
6266 @unnumberedsubsec Q5.1.2: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
2417
|
6267
|
|
|
6268 @unnumberedsubsubsec Associating a new file type with XEmacs.
|
|
|
6269
|
|
|
6270 In Explorer select @samp{View->Options->File Types}, press @samp{[New
|
|
|
6271 Type...]} and fill in the dialog box, e.g.:
|
|
|
6272
|
|
|
6273 @example
|
|
|
6274 Description of type: Emacs Lisp source
|
|
|
6275 Associated extension: el
|
|
|
6276 Content Type (MIME): text/plain
|
|
|
6277 @end example
|
|
|
6278
|
|
|
6279 then press @samp{[New...]} and fill in the @samp{Action} dialog box as
|
|
|
6280 follows:
|
|
|
6281
|
|
|
6282 @example
|
|
|
6283 Action:
|
|
|
6284 Open
|
|
|
6285
|
|
|
6286 Application used to perform action:
|
|
|
6287 D:\Full\path\for\xemacs.exe "%1"
|
|
|
6288
|
|
|
6289 [x] Use DDE
|
|
|
6290
|
|
|
6291 DDE Message:
|
|
|
6292 open("%1")
|
|
|
6293
|
|
|
6294 Application:
|
|
|
6295 <leave blank>
|
|
|
6296
|
|
|
6297 DDE Application Not Running:
|
|
|
6298 <leave blank>
|
|
|
6299
|
|
|
6300 Topic:
|
|
|
6301 <leave blank>
|
|
|
6302 @end example
|
|
|
6303
|
|
|
6304 @unnumberedsubsubsec Associating an existing file type with XEmacs.
|
|
|
6305
|
|
|
6306 In Explorer select @samp{View->Options->File Types}. Click on the file
|
|
|
6307 type in the list and press @samp{[Edit...]}. If the file type already
|
|
|
6308 has an @samp{Open} action, double click on it and fill in the
|
|
|
6309 @samp{Action} dialog box as described above; otherwise create a new
|
|
|
6310 action.
|
|
|
6311
|
|
|
6312 If the file type has more than one action listed, you probably want to
|
|
|
6313 make the @samp{Open} action that you just edited the default by clicking on
|
|
|
6314 it and pressing @samp{Set Default}.
|
|
|
6315
|
|
|
6316 Note for Windows 2000 users: Under Windows 2000, get to @samp{File Types}
|
|
|
6317 using @samp{Control Panel->Folder Options->File Types}.
|
|
|
6318
|
|
2459
|
6319 @unnumberedsec 5.2: Printing
|
|
|
6320
|
|
|
6321 @node Q5.2.1, Q5.2.2, Q5.1.2, External Subsystems
|
|
|
6322 @unnumberedsubsec Q5.2.1: What do I need to change to make printing work?
|
|
2417
|
6323
|
|
|
6324 For regular printing there are two variables that can be customized.
|
|
|
6325
|
|
|
6326 @table @code
|
|
|
6327 @item lpr-command
|
|
|
6328 This should be set to a command that takes standard input and sends
|
|
|
6329 it to a printer. Something like:
|
|
|
6330
|
|
|
6331 @lisp
|
|
|
6332 (setq lpr-command "lp")
|
|
|
6333 @end lisp
|
|
|
6334
|
|
|
6335 @item lpr-switches
|
|
|
6336 This should be set to a list that contains whatever the print command
|
|
|
6337 requires to do its job. Something like:
|
|
|
6338
|
|
|
6339 @lisp
|
|
|
6340 (setq lpr-switches '("-depson"))
|
|
|
6341 @end lisp
|
|
|
6342 @end table
|
|
|
6343
|
|
|
6344 For postscript printing there are three analogous variables to
|
|
|
6345 customize.
|
|
|
6346
|
|
|
6347 @table @code
|
|
|
6348 @item ps-lpr-command
|
|
|
6349 This should be set to a command that takes postscript on standard input
|
|
|
6350 and directs it to a postscript printer.
|
|
|
6351
|
|
|
6352 @item ps-lpr-switches
|
|
|
6353 This should be set to a list of switches required for
|
|
|
6354 @code{ps-lpr-command} to do its job.
|
|
|
6355
|
|
|
6356 @item ps-print-color-p
|
|
|
6357 This boolean variable should be set @code{t} if printing will be done in
|
|
|
6358 color, otherwise it should be set to @code{nil}.
|
|
|
6359 @end table
|
|
|
6360
|
|
|
6361 NOTE: It is an undocumented limitation in XEmacs that postscript
|
|
|
6362 printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a
|
|
|
6363 window system environment. It cannot be used outside of X11.
|
|
|
6364
|
|
2459
|
6365 @node Q5.2.2, Q5.2.3, Q5.2.1, External Subsystems
|
|
|
6366 @unnumberedsubsec Q5.2.2: How can I print WYSIWYG a font-locked buffer?
|
|
2417
|
6367
|
|
|
6368 Font-lock looks nice. How can I print (WYSIWYG) the highlighted
|
|
|
6369 document?
|
|
|
6370
|
|
|
6371 The package @code{ps-print}, which is now included with XEmacs, provides
|
|
|
6372 the ability to do this. The source code contains complete instructions
|
|
|
6373 on its use, in
|
|
|
6374 @file{$prefix/lib/xemacs/xemacs-packages/lisp/ps-print/ps-print.el},
|
|
|
6375 being the default location of an installed ps-print package.
|
|
|
6376
|
|
2459
|
6377 @node Q5.2.3, Q5.2.4, Q5.2.2, External Subsystems
|
|
|
6378 @unnumberedsubsec Q5.2.3: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
2417
|
6379
|
|
|
6380 My printer is a Postscript printer and @code{lpr} only works for
|
|
|
6381 Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x
|
|
|
6382 lpr-buffer} to work?
|
|
|
6383
|
|
|
6384 Put something like this in your @file{init.el}:
|
|
428
|
6385
|
|
|
6386 @lisp
|
|
2417
|
6387 (setq lpr-command "a2ps")
|
|
|
6388 (setq lpr-switches '("-p" "-1"))
|
|
|
6389 @end lisp
|
|
|
6390
|
|
|
6391 If you don't use a2ps to convert ASCII to postscript (why not, it's
|
|
|
6392 free?), replace with the command you do use. Note also that some
|
|
|
6393 versions of a2ps require a @samp{-Pprinter} to ensure spooling.
|
|
|
6394
|
|
2459
|
6395 @node Q5.2.4, Q5.3.1, Q5.2.3, External Subsystems
|
|
|
6396 @unnumberedsubsec Q5.2.4: Can you print under MS Windows?
|
|
2417
|
6397
|
|
|
6398 As of 21.4, printing works on Windows, using simply
|
|
|
6399 @samp{File->Print BUFFER...}, and can be configured with
|
|
|
6400 @samp{File->Page Setup...}.
|
|
|
6401
|
|
|
6402 Prior to 21.4, there is no built-in support, but there are some clever
|
|
|
6403 hacks out there. If you know how, please let us know and we'll put it
|
|
|
6404 here.
|
|
|
6405
|
|
2459
|
6406 @unnumberedsec 5.3: Sound
|
|
|
6407
|
|
|
6408 @node Q5.3.1, Q5.3.2, Q5.2.4, External Subsystems
|
|
|
6409 @unnumberedsubsec Q5.3.1: How do I turn off the sound?
|
|
2417
|
6410
|
|
|
6411 Add the following line to your @file{init.el}:
|
|
|
6412
|
|
|
6413 @lisp
|
|
|
6414 (setq bell-volume 0)
|
|
|
6415 (setq sound-alist nil)
|
|
|
6416 @end lisp
|
|
|
6417
|
|
|
6418 That will make your XEmacs totally silent---even the default ding sound
|
|
|
6419 (TTY beep on TTY-s) will be gone.
|
|
|
6420
|
|
|
6421 You can also change these with Customize. Select from the
|
|
|
6422 @code{Options} menu @code{Advanced
|
|
|
6423 (Customize)->Emacs->Environment->Sound->Sound...} or type @kbd{M-x
|
|
|
6424 customize @key{RET} sound @key{RET}}.
|
|
|
6425
|
|
|
6426
|
|
2459
|
6427 @node Q5.3.2, Q5.3.3, Q5.3.1, External Subsystems
|
|
|
6428 @unnumberedsubsec Q5.3.2: How do I get funky sounds instead of a boring beep?
|
|
2417
|
6429
|
|
|
6430 Make sure your XEmacs was compiled with sound support, and then put this
|
|
|
6431 in your @file{init.el}:
|
|
|
6432
|
|
|
6433 @lisp
|
|
|
6434 (load-default-sounds)
|
|
|
6435 @end lisp
|
|
|
6436
|
|
2459
|
6437 @node Q5.3.3, Q5.3.4, Q5.3.2, External Subsystems
|
|
|
6438 @unnumberedsubsec Q5.3.3: What are NAS and ESD (EsounD)?
|
|
|
6439
|
|
|
6440 @dfn{Network Audio System} (NAS) is a client-server sound library for X.
|
|
|
6441
|
|
|
6442 @uref{http://radscan.com/nas.html}.
|
|
|
6443
|
|
|
6444 To build XEmacs with it, use the @file{configure} flag @samp{--with-sound=nas}.
|
|
|
6445
|
|
|
6446 @dfn{Enlightened Sound Daemon} (ESD or EsounD) is yet another sound system.
|
|
|
6447
|
|
|
6448 @uref{http://www.tux.org/~ricdude/EsounD.html}.
|
|
|
6449
|
|
|
6450 To build XEmacs with it, use the @file{configure} flag @samp{--with-sound=esd}.
|
|
|
6451
|
|
|
6452 You can specify support for both with a flag like @samp{--with-sound=nas,esd}.
|
|
|
6453
|
|
|
6454 @node Q5.3.4, Q5.4.1, Q5.3.3, External Subsystems
|
|
|
6455 @unnumberedsubsec Q5.3.4: Sunsite sounds don't play.
|
|
2417
|
6456
|
|
|
6457 I'm having some trouble with sounds I've downloaded from sunsite. They
|
|
|
6458 play when I run them through @code{showaudio} or cat them directly to
|
|
|
6459 @file{/dev/audio}, but XEmacs refuses to play them.
|
|
|
6460
|
|
|
6461 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
|
|
|
6462
|
|
|
6463 @quotation
|
|
|
6464 [Many of] These files have an (erroneous) 24byte header that tells about
|
|
|
6465 the format that they have been recorded in. If you cat them to
|
|
|
6466 @file{/dev/audio}, the header will be ignored and the default behavior
|
|
|
6467 for /dev/audio will be used. This happens to be 8kHz uLaw. It is
|
|
|
6468 probably possible to fix the header by piping through @code{sox} and
|
|
|
6469 passing explicit parameters for specifying the sampling format; you then
|
|
|
6470 need to perform a 'null' conversion from SunAudio to SunAudio.
|
|
|
6471 @end quotation
|
|
|
6472
|
|
2459
|
6473 @unnumberedsec 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
6474
|
|
|
6475 @node Q5.4.1, Q5.4.2, Q5.3.4, External Subsystems
|
|
|
6476 @unnumberedsubsec Q5.4.1: What is an interior shell?
|
|
2417
|
6477
|
|
|
6478 #### Write me.
|
|
|
6479
|
|
2459
|
6480 @node Q5.4.2, Q5.4.3, Q5.4.1, External Subsystems
|
|
|
6481 @unnumberedsubsec Q5.4.2: How do I start up a second shell buffer?
|
|
2417
|
6482
|
|
|
6483 In the @code{*shell*} buffer:
|
|
|
6484
|
|
|
6485 @lisp
|
|
|
6486 M-x rename-buffer @key{RET} *shell-1* @key{RET}
|
|
|
6487 M-x shell RET
|
|
|
6488 @end lisp
|
|
|
6489
|
|
|
6490 This will then start a second shell. The key is that no buffer named
|
|
|
6491 @samp{*shell*} can exist. It might be preferable to use @kbd{M-x
|
|
|
6492 rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x
|
|
|
6493 rename-buffer}.
|
|
|
6494
|
|
|
6495 Alternately, you can set the variable @code{shell-multiple-shells}.
|
|
|
6496 If the value of this variable is non-nil, each time shell mode is invoked,
|
|
|
6497 a new shell is made
|
|
|
6498
|
|
2459
|
6499 @node Q5.4.3, Q5.4.4, Q5.4.2, External Subsystems
|
|
|
6500 @unnumberedsubsec Q5.4.3: Telnet from shell filters too much
|
|
2417
|
6501
|
|
|
6502 I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke
|
|
|
6503 and use a telnet session within it. Everything works fine except that
|
|
|
6504 now all @samp{^M}'s are filtered out by Emacs. Fixes?
|
|
|
6505
|
|
|
6506 Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather
|
|
|
6507 than doing rsh or telnet within the local shell buffer. You can also
|
|
|
6508 use @kbd{M-x ssh} to open secure remote session if you have @code{ssh}
|
|
|
6509 installed.
|
|
|
6510
|
|
2459
|
6511 @node Q5.4.4, Q5.4.5, Q5.4.3, External Subsystems
|
|
|
6512 @unnumberedsubsec Q5.4.4: Strange things are happening in Shell Mode.
|
|
2417
|
6513
|
|
|
6514 Sometimes (i.e. it's not repeatable, and I can't work out why it
|
|
|
6515 happens) when I'm typing into shell mode, I hit return and only a
|
|
|
6516 portion of the command is given to the shell, and a blank prompt is
|
|
|
6517 returned. If I hit return again, the rest of the previous command is
|
|
|
6518 given to the shell.
|
|
|
6519
|
|
|
6520 @email{martin@@xemacs.org, Martin Buchholz} writes:
|
|
|
6521
|
|
|
6522 @quotation
|
|
|
6523 There is a known problem with interaction between @code{csh} and the
|
|
|
6524 @code{filec} option and XEmacs. You should add the following to your
|
|
|
6525 @file{.cshrc}:
|
|
|
6526
|
|
|
6527 @example
|
|
|
6528 if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec
|
|
|
6529 @end example
|
|
|
6530 @end quotation
|
|
|
6531
|
|
2995
|
6532 @node Q5.4.5, Q5.4.6, Q5.4.4, External Subsystems
|
|
2459
|
6533 @unnumberedsubsec Q5.4.5: XEmacs complains "No such file or directory, diff"
|
|
2417
|
6534
|
|
|
6535 or "ispell" or other commands that seem related to whatever you just
|
|
|
6536 tried to do (M-x ediff or M-$, for example).
|
|
|
6537
|
|
|
6538 There are a large number of common (in the sense that "everyone has
|
|
|
6539 these, they really do") Unix utilities that are not provided with
|
|
|
6540 XEmacs. The GNU Project's implementations are available for Windows in
|
|
|
6541 the the Cygwin distribution (@uref{http://www.cygwin.com/}), which also
|
|
|
6542 provides a complete Unix emulation environment (and thus makes ports of
|
|
|
6543 Unix utilities nearly trivial). Another implementation is that from
|
|
|
6544 MinGW (@uref{http://www.mingw.org/msys.shtml}). If you know of others,
|
|
|
6545 please let us know!
|
|
|
6546
|
|
2995
|
6547 @node Q5.4.6, Q5.5.1, Q5.4.5, External Subsystems
|
|
|
6548 @unnumberedsubsec Q5.4.6: Cygwin error "fork_copy: linked dll/bss pass 0 failed"
|
|
|
6549
|
|
|
6550 If you are getting an error like
|
|
|
6551
|
|
|
6552 @example
|
|
|
6553 17797832 [main] bash 3468 fork_copy: linked dll/bss pass 0 failed,
|
|
|
6554 0x675000..0x6756A0, done 0, windows pid 2708, Win 32 error 487
|
|
|
6555 bash: fork: resource temporarily unavailable
|
|
|
6556 @end example
|
|
|
6557
|
|
|
6558 when trying to run bash using @kbd{M-x shell}, then you need to rebase
|
|
|
6559 your Cygwin DLL's. This is a known problem with Cygwin. To fix:
|
|
|
6560
|
|
|
6561 @enumerate
|
|
|
6562 @item
|
|
|
6563 Download the @file{rebase} utility from Cygwin setup (it's under
|
|
|
6564 @samp{System}).
|
|
|
6565 @item
|
|
|
6566 Kill @strong{all} of your Cygwin processes, including all of your
|
|
|
6567 shells and all background processes. Use @code{ps -a} to list all the
|
|
|
6568 processes you need to kill.
|
|
|
6569 @item
|
|
|
6570 From a DOS prompt, run @file{ash} (@strong{not} @file{bash},
|
|
|
6571 @file{tcsh} or @file{zsh}). Do not try to be clever and @code{exec
|
|
|
6572 /bin/ash} from your last shell; it won't work.
|
|
|
6573 @item
|
|
|
6574 Type @code{/bin/rebaseall -v}.
|
|
|
6575 @end enumerate
|
|
|
6576
|
|
|
6577 The problem should now be fixed -- at least, until you install another
|
|
|
6578 Cygwin package with DLL's, in which case you may have to repeat the
|
|
|
6579 procedure.
|
|
|
6580
|
|
2459
|
6581 @unnumberedsec 5.5: Multiple Device Support
|
|
|
6582
|
|
2995
|
6583 @node Q5.5.1, Q5.5.2, Q5.4.6, External Subsystems
|
|
2459
|
6584 @unnumberedsubsec Q5.5.1: How do I open a frame on another screen of my multi-headed display?
|
|
2417
|
6585
|
|
|
6586 Use the command @kbd{M-x make-frame-on-display}. This command is also
|
|
|
6587 on the File menu in the menubar.
|
|
|
6588
|
|
|
6589 The command @code{make-frame-on-tty} also exists, which will establish a
|
|
|
6590 connection to any tty-like device. Opening the TTY devices should be
|
|
|
6591 left to @code{gnuclient}, though.
|
|
|
6592
|
|
2459
|
6593 @node Q5.5.2, Q5.5.3, Q5.5.1, External Subsystems
|
|
|
6594 @unnumberedsubsec Q5.5.2: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
6595
|
|
|
6596 Yes. Use @code{gnuclient -nw}.
|
|
|
6597
|
|
|
6598 Also see @ref{Q5.5.3, How do I disable gnuserv from opening a new frame?}.
|
|
|
6599
|
|
|
6600 @node Q5.5.3, Q5.5.4, Q5.5.2, External Subsystems
|
|
|
6601 @unnumberedsubsec Q5.5.3: How do I disable gnuserv from opening a new frame?
|
|
2417
|
6602
|
|
|
6603 If you set the @code{gnuserv-frame} variable to the frame that should be
|
|
|
6604 used to display buffers that are pulled up, a new frame will not be
|
|
|
6605 created. For example, you could put
|
|
|
6606
|
|
|
6607 @lisp
|
|
|
6608 (setq gnuserv-frame (selected-frame))
|
|
428
|
6609 @end lisp
|
|
|
6610
|
|
2417
|
6611 early on in your @file{init.el}, to ensure that the first frame created
|
|
|
6612 is the one used for your gnuserv buffers.
|
|
|
6613
|
|
|
6614 There is an option to set the gnuserv target to the current frame. See
|
|
|
6615 @code{Options->Display->"Other Window" Location->Make Current Frame Gnuserv Target}
|
|
|
6616
|
|
|
6617 You can also change this with Customize. Select from the
|
|
|
6618 @code{Options} menu @code{Advanced
|
|
|
6619 (Customize)->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type
|
|
|
6620 @kbd{M-x customize @key{RET} gnuserv @key{RET}}.
|
|
|
6621
|
|
|
6622
|
|
2459
|
6623 @node Q5.5.4, Q5.5.5, Q5.5.3, External Subsystems
|
|
|
6624 @unnumberedsubsec Q5.5.4: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
2417
|
6625
|
|
|
6626 Put the following in your @file{init.el} file to start the server:
|
|
|
6627
|
|
|
6628 @lisp
|
|
|
6629 (gnuserv-start)
|
|
|
6630 @end lisp
|
|
|
6631
|
|
|
6632 Start your first XEmacs as usual. After that, you can do:
|
|
|
6633
|
|
|
6634 @example
|
|
|
6635 gnuclient randomfilename
|
|
|
6636 @end example
|
|
|
6637
|
|
|
6638 from the command line to get your existing XEmacs process to open a new
|
|
|
6639 frame and visit randomfilename in that window. When you're done editing
|
|
|
6640 randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the
|
|
|
6641 frame.
|
|
|
6642
|
|
|
6643 See also man page of gnuclient.
|
|
|
6644
|
|
2459
|
6645 @node Q5.5.5, , Q5.5.4, External Subsystems
|
|
|
6646 @unnumberedsubsec Q5.5.5: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
2417
|
6647
|
|
|
6648 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
|
|
|
6649 @quotation
|
|
|
6650 Here is one of the solutions, we have this in a script called
|
|
|
6651 @file{etc/editclient.sh}.
|
|
|
6652 @example
|
|
|
6653 #!/bin/sh
|
|
|
6654 if gnuclient -batch -eval t >/dev/null 2>&1
|
|
|
6655 then
|
|
|
6656 exec gnuclient $@{1+"$@@"@}
|
|
|
6657 else
|
|
|
6658 xemacs -unmapped -f gnuserv-start &
|
|
|
6659 until gnuclient -batch -eval t >/dev/null 2>&1
|
|
|
6660 do
|
|
|
6661 sleep 1
|
|
|
6662 done
|
|
|
6663 exec gnuclient $@{1+"$@@"@}
|
|
|
6664 fi
|
|
|
6665 @end example
|
|
|
6666
|
|
|
6667 Note that there is a known problem when running XEmacs and 'gnuclient
|
|
|
6668 -nw' on the same TTY.
|
|
|
6669 @end quotation
|
|
|
6670
|
|
2459
|
6671 @node Internet, Advanced, External Subsystems, Top
|
|
|
6672 @unnumbered 6 Connecting to the Internet
|
|
|
6673
|
|
|
6674 This is part 6 of the XEmacs Frequently Asked Questions list. This
|
|
|
6675 section is devoted connecting to the Internet.
|
|
|
6676
|
|
|
6677 @menu
|
|
|
6678 6.0: General Mail and News
|
|
|
6679 * Q6.0.1:: What are the various packages for reading mail?
|
|
|
6680 * Q6.0.2:: How can I send mail?
|
|
|
6681 * Q6.0.3:: How do I get my outgoing mail archived?
|
|
|
6682 * Q6.0.4:: How can I read and/or compose MIME messages?
|
|
|
6683 * Q6.0.5:: How do I customize the From line?
|
|
|
6684 * Q6.0.6:: How do I get my MUA to filter mail for me?
|
|
|
6685 * Q6.0.7:: Remote mail reading with an MUA.
|
|
|
6686 * Q6.0.8:: An MUA gets an error incorporating new mail.
|
|
|
6687 * Q6.0.9:: Why isn't @file{movemail} working?
|
|
|
6688 * Q6.0.10:: How do I make my MUA display graphical smilies?
|
|
|
6689 * Q6.0.11:: How can I get those oh-so-neat X-Face lines?
|
|
|
6690
|
|
|
6691 6.1: Reading Mail with VM
|
|
|
6692 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
6693 * Q6.1.2:: How can I get VM to automatically check for new mail?
|
|
|
6694 * 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"?
|
|
|
6695 * Q6.1.4:: Is there a mailing list or FAQ for VM?
|
|
|
6696 * Q6.1.5:: How do I make VM stay in a single frame?
|
|
|
6697 * Q6.1.6:: Customization of VM not covered in the manual, or here.
|
|
|
6698
|
|
|
6699 6.2: Reading Netnews and Mail with Gnus
|
|
|
6700 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
6701 * Q6.2.2:: How do I make Gnus stay within a single frame?
|
|
|
6702
|
|
|
6703 6.3: FTP Access
|
|
|
6704 * Q6.3.1:: Can I edit files on other hosts?
|
|
|
6705 * Q6.3.2:: What is EFS?
|
|
|
6706
|
|
|
6707 6.4: Web Browsing with W3
|
|
|
6708 * Q6.4.1:: What is W3?
|
|
|
6709 * Q6.4.2:: How do I run W3 from behind a firewall?
|
|
|
6710 * Q6.4.3:: Is it true that W3 supports style sheets and tables?
|
|
|
6711 @end menu
|
|
|
6712
|
|
|
6713 @unnumberedsec 6.0: General Mail and News
|
|
|
6714
|
|
|
6715 @node Q6.0.1, Q6.0.2, Internet, Internet
|
|
|
6716 @unnumberedsubsec Q6.0.1: What are the various packages for reading mail?
|
|
|
6717
|
|
|
6718 #### Write me.
|
|
|
6719
|
|
|
6720 @node Q6.0.2, Q6.0.3, Q6.0.1, Internet
|
|
|
6721 @unnumberedsubsec Q6.0.2: How can I send mail?
|
|
|
6722
|
|
|
6723 Under Unix and Mac OS X, the @samp{sendmail} package is normally used
|
|
|
6724 for this.
|
|
|
6725 #### Write me.
|
|
|
6726
|
|
|
6727 Under Windows, you need to use @samp{smtpmail}, which communicates
|
|
|
6728 directly with the mail server, as there is no @file{sendmail} program
|
|
|
6729 running. To get it working, use code like the following in your
|
|
|
6730 @file{init.el} file:
|
|
|
6731
|
|
|
6732 @lisp
|
|
|
6733 ;; Get mail working under Windows.
|
|
|
6734 (setq message-send-mail-function 'smtpmail-send-it) ; for message/Gnus
|
|
|
6735 (setq send-mail-function 'smtpmail-send-it) ; for C-x m, etc.
|
|
|
6736 ;; the following ensures that mail problems can be debugged: it logs a trace
|
|
|
6737 ;; of the SMTP conversation to *trace of SMTP session to <somewhere>*.
|
|
|
6738 (setq smtpmail-debug-info t)
|
|
|
6739 ;; Substitute your info here.
|
|
|
6740 ;(setq user-mail-address "ben@@xemacs.org")
|
|
|
6741 ;(setq user-full-name "Ben Wing")
|
|
|
6742 ;(setq smtpmail-default-smtp-server "smtp.myserver.myisp.com")
|
|
|
6743 ;; The following two aren't completely necessary but may help.
|
|
|
6744 ;(setq smtpmail-local-domain "666.com")
|
|
|
6745 ;(setq smtpmail-sendto-domain "666.com")
|
|
|
6746 ;; If your SMTP server requires a username/password to authenticate, as
|
|
|
6747 ;; many do nowadays, set them like this:
|
|
|
6748 ;(setq smtpmail-auth-credentials ; or use ~/.authinfo
|
|
|
6749 ; '(("smtp.myserver.myisp.com" 25 "USER@@SOMEWHERE" "PASSWORD")))
|
|
|
6750
|
|
|
6751 ;; Other possibilities for getting smtpmail to work:
|
|
|
6752 ;;
|
|
|
6753 ;; If for some reason you need to authenticate using the STARTTLS protocol
|
|
|
6754 ;; (don't look into this unless you know what it is), use
|
|
|
6755 ;; (setq smtpmail-starttls-credentials
|
|
|
6756 ;; '(("YOUR SMTP HOST" 25 "~/.my_smtp_tls.key" "~/.my_smtp_tls.cert")))
|
|
|
6757 ;; Requires external program
|
|
|
6758 ;; ftp://ftp.opaopa.org/pub/elisp/starttls-*.tar.gz.
|
|
|
6759 ;; See http://www.ietf.org/rfc/rfc2246.txt,
|
|
|
6760 ;; http://www.ietf.org/rfc/rfc2487.txt
|
|
|
6761 @end lisp
|
|
|
6762
|
|
|
6763 The lines you need to care about are those that set
|
|
|
6764 @code{user-mail-address}, @code{user-full-name},
|
|
|
6765 @code{smtpmail-default-smtp-server}, and
|
|
|
6766 @code{smtpmail-auth-credentials}. You need to set these with,
|
|
|
6767 respectively, your email address, your full name, the SMTP server you
|
|
|
6768 use for outgoing mail, and the username and password you need to log
|
|
|
6769 in to your SMTP server. (If for some reason your SMTP server doesn't
|
|
|
6770 require logging in to send mail, don't uncomment this last line.)
|
|
|
6771
|
|
|
6772 The other settings may be useful in specific cases, but you should know what
|
|
|
6773 you're doing before enabling them.
|
|
|
6774
|
|
|
6775 @node Q6.0.3, Q6.0.4, Q6.0.2, Internet
|
|
|
6776 @unnumberedsubsec Q6.0.3: How do I get my outgoing mail archived?
|
|
|
6777
|
|
|
6778 @lisp
|
|
|
6779 (setq mail-archive-file-name "~/outbox")
|
|
|
6780 @end lisp
|
|
|
6781
|
|
|
6782 @node Q6.0.4, Q6.0.5, Q6.0.3, Internet
|
|
|
6783 @unnumberedsubsec Q6.0.4: How can I read and/or compose MIME messages?
|
|
|
6784
|
|
|
6785 VM, MH-E and GNUS support MIME natively. Other MUAs may or may not
|
|
|
6786 have MIME support; refer to their documentation and other resources,
|
|
|
6787 such as web pages and mailing lists. Packages like SEMI/WEMI may be
|
|
|
6788 useful in connection with MUAs like mew and Wanderlust.
|
|
|
6789
|
|
|
6790 @node Q6.0.5, Q6.0.6, Q6.0.4, Internet
|
|
|
6791 @unnumberedsubsec Q6.0.5: How do I customize the From line?
|
|
|
6792
|
|
|
6793 How do I change the @samp{From:} line? I have set gnus-user-from-line
|
|
|
6794 to
|
|
|
6795 @example
|
|
|
6796 Gail Gurman <gail.gurman@@sybase.com>
|
|
|
6797 @end example
|
|
|
6798 @noindent , but XEmacs Gnus doesn't use
|
|
|
6799 it. [This should apply to all MUA's. --ed] Instead it uses
|
|
|
6800 @example
|
|
|
6801 Gail Mara Gurman @email{gailg@@deall}
|
|
|
6802 @end example
|
|
|
6803 @noindent and then complains
|
|
|
6804 that it's incorrect. Also, as you perhaps can see, my Message-ID is
|
|
|
6805 screwy. How can I change that?
|
|
|
6806
|
|
|
6807 @email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes:
|
|
|
6808
|
|
|
6809 @quotation
|
|
|
6810 Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or
|
|
|
6811 @code{mail-host-address} to @samp{sybase.com}.
|
|
|
6812 @end quotation
|
|
|
6813
|
|
|
6814 @node Q6.0.6, Q6.0.7, Q6.0.5, Internet
|
|
|
6815 @unnumberedsubsec Q6.0.6: How do I get my MUA to filter mail for me?
|
|
|
6816
|
|
|
6817 One possibility is to use procmail to split your mail before it gets to
|
|
|
6818 the MUA. I prefer this personally, since there are many strange and
|
|
|
6819 wonderful things one can do with procmail. Procmail may be found at
|
|
|
6820 @uref{http://www.procmail.org/}.
|
|
|
6821
|
|
|
6822 Also see the Mail Filtering FAQ at:
|
|
|
6823 @iftex
|
|
|
6824 @*
|
|
|
6825 @end iftex
|
|
|
6826 @uref{http://www.faqs.org/faqs/mail/filtering-faq/}.
|
|
|
6827
|
|
|
6828 @node Q6.0.7, Q6.0.8, Q6.0.6, Internet
|
|
|
6829 @unnumberedsubsec Q6.0.7: Remote mail reading with an MUA.
|
|
|
6830
|
|
|
6831 My mailbox lives at the office on a big honkin server. My regular INBOX
|
|
|
6832 lives on my honkin desktop machine. I now can PPP to the office from
|
|
|
6833 home which is far from honking... I'd like to be able to read mail at
|
|
|
6834 home without storing it here and I'd like to use xemacs and the MUA at
|
|
|
6835 home... Is there a recommended setup?
|
|
|
6836
|
|
|
6837 @email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes:
|
|
|
6838
|
|
|
6839 @quotation
|
|
|
6840 There are several ways to do this.
|
|
|
6841
|
|
|
6842 @enumerate
|
|
|
6843 @item
|
|
|
6844 Set your display to your home machine and run dxpc or one of the other X
|
|
|
6845 compressors.
|
|
|
6846
|
|
|
6847 @item
|
|
|
6848 NFS mount your desktop machine on your home machine and modify your pop
|
|
|
6849 command on your home machine to rsh to your desktop machine and actually
|
|
|
6850 do the pop get's.
|
|
|
6851
|
|
|
6852 @item
|
|
|
6853 Run a POP server on your desktop machine as well and do a sort of two
|
|
|
6854 tiered POP get.
|
|
|
6855 @end enumerate
|
|
|
6856 @end quotation
|
|
|
6857
|
|
|
6858 @email{wmperry@@monolith.spry.com, William Perry} adds:
|
|
|
6859
|
|
|
6860 @quotation
|
|
|
6861 Or you could run a pop script periodically on your desktop machine, and
|
|
|
6862 just use ange-ftp or NFS to get to your mailbox. I used to do this all
|
|
|
6863 the time back at IU.
|
|
|
6864 @end quotation
|
|
|
6865
|
|
|
6866 @node Q6.0.8, Q6.0.9, Q6.0.7, Internet
|
|
|
6867 @unnumberedsubsec Q6.0.8: An MUA gets an error incorporating new mail.
|
|
|
6868
|
|
|
6869 rmail and VM, and probably other MUA's as well, get new mail from
|
|
|
6870 your mailbox (called @file{/var/mail/$USER} or @file{/var/spool/mail/$USER}
|
|
|
6871 or something similar) using a program called @code{movemail}.
|
|
|
6872 This program interlocks with @code{/bin/mail} using the protocol
|
|
|
6873 defined by @code{/bin/mail}.
|
|
|
6874
|
|
|
6875 There are various different protocols in general use, which you need to
|
|
|
6876 specify using the @samp{--mail-locking} option to @file{configure}:
|
|
|
6877
|
|
|
6878 @table @samp
|
|
|
6879 @item lockf
|
|
|
6880 POSIX file locking with @code{lockf()}
|
|
|
6881 @item flock
|
|
|
6882 BSD file locking with @code{flock()}
|
|
|
6883 @item dot
|
|
|
6884 To manipulate mail file @file{foo}, first create file @file{foo.lock}
|
|
|
6885 @item locking
|
|
|
6886 Use @code{locking()}, Microsoft's renamed @code{flock()}
|
|
|
6887 @item mmdf
|
|
|
6888 Use @code{lk_open()} and @code{lk_close()} as defined by the Multi-channel
|
|
|
6889 Memo Distribution Facility
|
|
|
6890 @item pop
|
|
|
6891 Retrieve mail using POP (the Post Office Protocol). This is the
|
|
|
6892 default for Cygwin/MinGW.
|
|
|
6893 @end table
|
|
|
6894
|
|
|
6895 @strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
|
|
|
6896 SYSTEM, YOU CAN LOSE MAIL!}
|
|
|
6897
|
|
|
6898 Usually the value is correctly determined automatically:
|
|
|
6899 @file{configure} tries to detect the method in use, and defaults exist
|
|
|
6900 on systems for which this doesn't work.
|
|
|
6901
|
|
|
6902 However, if you run into problems incorporating new mail, it may be
|
|
|
6903 because an incorrect method is being used.
|
|
|
6904
|
|
|
6905 If your system uses the lock file protocol, and permissions are set
|
|
|
6906 so that ordinary users cannot write lock files in the mail spool
|
|
|
6907 directory, you may need to make @file{movemail} setgid to a
|
|
|
6908 suitable group such as @samp{mail}. You can use these commands (as
|
|
|
6909 root):
|
|
|
6910
|
|
|
6911 @example
|
|
|
6912 chgrp mail movemail
|
|
|
6913 chmod 2755 movemail
|
|
|
6914 @end example
|
|
|
6915
|
|
|
6916 If you are using the @samp{pop} locking method, @file{movemail} must
|
|
|
6917 be setuid root.
|
|
|
6918
|
|
|
6919 Installation normally copies movemail from the build directory to an
|
|
|
6920 installation directory which is usually under @file{/usr/local/lib}.
|
|
|
6921 The installed copy of @file{movemail} is usually in the directory
|
|
|
6922 @file{/usr/local/lib/xemacs-VERSION/TARGET} (for example,
|
|
|
6923 @file{/usr/local/lib/xemacs-21.4.15/i686-pc-cygwin}). You must change
|
|
|
6924 the group and mode of the installed copy; changing the group and mode
|
|
|
6925 of the build directory copy is ineffective.
|
|
|
6926
|
|
|
6927 @node Q6.0.9, Q6.0.10, Q6.0.8, Internet
|
|
|
6928 @unnumberedsubsec Q6.0.9: Why isn't @file{movemail} working?
|
|
|
6929
|
|
|
6930 @xref{Q6.0.8}.
|
|
|
6931
|
|
|
6932 Note also that older versions of Mozilla came with a @file{movemail}
|
|
|
6933 program that is @strong{not} compatible with XEmacs. Do not use it.
|
|
|
6934 Always use the @file{movemail} installed with your XEmacs. Failure to
|
|
|
6935 do so can result in lost mail.
|
|
|
6936
|
|
|
6937 @node Q6.0.10, Q6.0.11, Q6.0.9, Internet
|
|
|
6938 @unnumberedsubsec Q6.0.10: How do I make my MUA display graphical smilies?
|
|
|
6939 For mh-e use the following:
|
|
|
6940
|
|
|
6941 @lisp
|
|
|
6942 (add-hook 'mh-show-mode-hook '(lambda ()
|
|
|
6943 (smiley-region (point-min)
|
|
|
6944 (point-max))))
|
|
|
6945 @end lisp
|
|
|
6946
|
|
|
6947 @email{bill@@carpenter.ORG, WJCarpenter} writes:
|
|
|
6948 For VM use the following:
|
|
|
6949 @lisp
|
|
|
6950 (autoload 'smiley-region "smiley" nil t)
|
|
|
6951 (add-hook 'vm-select-message-hook
|
|
|
6952 '(lambda ()
|
|
|
6953 (smiley-region (point-min)
|
|
|
6954 (point-max))))
|
|
|
6955 @end lisp
|
|
|
6956
|
|
|
6957 For tm use the following:
|
|
|
6958 @lisp
|
|
|
6959 (autoload 'smiley-buffer "smiley" nil t)
|
|
|
6960 (add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer)
|
|
|
6961 @end lisp
|
|
|
6962
|
|
|
6963 @node Q6.0.11, Q6.1.1, Q6.0.10, Internet
|
|
|
6964 @unnumberedsubsec Q6.0.11: How can I get those oh-so-neat X-Face lines?
|
|
|
6965
|
|
|
6966 Firstly there is an ftp site which describes X-faces and has the
|
|
|
6967 associated tools mentioned below, at
|
|
|
6968 @uref{http://ftp.cs.indiana.edu/pub/faces/}.
|
|
|
6969
|
|
|
6970 Then the steps are
|
|
|
6971
|
|
|
6972 @enumerate
|
|
|
6973 @item
|
|
|
6974 Create 48x48x1 bitmap with your favorite tool
|
|
|
6975
|
|
|
6976 @item
|
|
|
6977 Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc.,
|
|
|
6978 and then compile the face.
|
|
|
6979
|
|
|
6980 @item
|
|
|
6981 @example
|
|
|
6982 cat file.xbm | xbm2ikon |compface > file.face
|
|
|
6983 @end example
|
|
|
6984
|
|
|
6985 @item
|
|
|
6986 Then be sure to quote things that are necessary for emacs strings:
|
|
|
6987
|
|
|
6988 @example
|
|
|
6989 cat ./file.face | sed 's/\\/\\\\/g'
|
|
|
6990 @iftex
|
|
|
6991 \ @*
|
|
|
6992 @end iftex
|
|
|
6993 | sed 's/\"/\\\"/g' > ./file.face.quoted
|
|
|
6994 @end example
|
|
|
6995
|
|
|
6996 @item
|
|
|
6997 Then set up emacs to include the file as a mail header - there were a
|
|
|
6998 couple of suggestions here---either something like:
|
|
|
6999
|
|
|
7000 @lisp
|
|
|
7001 (setq mail-default-headers
|
|
|
7002 "X-Face: @email{Ugly looking text string here}")
|
|
|
7003 @end lisp
|
|
|
7004
|
|
|
7005 Or, alternatively, as:
|
|
|
7006
|
|
|
7007 @lisp
|
|
|
7008 (defun mail-insert-x-face ()
|
|
|
7009 (save-excursion
|
|
|
7010 (goto-char (point-min))
|
|
|
7011 (search-forward mail-header-separator)
|
|
|
7012 (beginning-of-line)
|
|
|
7013 (insert "X-Face:")
|
|
|
7014 (insert-file-contents "~/.face")))
|
|
|
7015
|
|
|
7016 (add-hook 'mail-setup-hook 'mail-insert-x-face)
|
|
|
7017 @end lisp
|
|
|
7018 @end enumerate
|
|
|
7019
|
|
|
7020 However, 2 things might be wrong:
|
|
|
7021
|
|
|
7022 Some versions of pbmtoicon produces some header lines that is not
|
|
|
7023 expected by the version of compface that I grabbed. So I found I had to
|
|
|
7024 include a @code{tail +3} in the pipeline like this:
|
|
|
7025
|
|
|
7026 @example
|
|
|
7027 cat file.xbm | xbm2ikon | tail +3 |compface > file.face
|
|
|
7028 @end example
|
|
|
7029
|
|
|
7030 Some people have also found that if one uses the @code{(insert-file)}
|
|
|
7031 method, one should NOT quote the face string using the sed script .
|
|
|
7032
|
|
|
7033 It might also be helpful to use @email{stig@@hackvan.com, Stig's} script
|
|
|
7034 xbm2face (included in the compface distribution at XEmacs.org) to do the
|
|
|
7035 conversion.
|
|
|
7036
|
|
|
7037 Contributors for this item:
|
|
|
7038
|
|
|
7039 Paul Emsley,
|
|
|
7040 Ricardo Marek,
|
|
|
7041 Amir J. Katz,
|
|
|
7042 Glen McCort,
|
|
|
7043 Heinz Uphoff,
|
|
|
7044 Peter Arius,
|
|
|
7045 Paul Harrison, and
|
|
|
7046 Vegard Vesterheim
|
|
|
7047
|
|
|
7048 @unnumberedsec 6.1: Reading Mail with VM
|
|
|
7049
|
|
|
7050 @node Q6.1.1, Q6.1.2, Q6.0.11, Internet
|
|
|
7051 @unnumberedsubsec Q6.1.1: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
7052
|
|
|
7053 Use @code{vm-spool-files}, like this for example:
|
|
|
7054
|
|
|
7055 @lisp
|
|
|
7056 (setq vm-spool-files '("/var/spool/mail/wing"
|
|
|
7057 "netcom23.netcom.com:110:pass:wing:MYPASS"))
|
|
|
7058 @end lisp
|
|
|
7059
|
|
|
7060 Of course substitute your actual password for MYPASS.
|
|
|
7061
|
|
|
7062 @node Q6.1.2, Q6.1.3, Q6.1.1, Internet
|
|
|
7063 @unnumberedsubsec Q6.1.2: How can I get VM to automatically check for new mail?
|
|
|
7064
|
|
|
7065 @email{turner@@lanl.gov, John Turner} writes:
|
|
|
7066
|
|
|
7067 @quotation
|
|
|
7068 Use the following:
|
|
|
7069
|
|
|
7070 @lisp
|
|
|
7071 (setq vm-auto-get-new-mail 60)
|
|
|
7072 @end lisp
|
|
|
7073 @end quotation
|
|
|
7074
|
|
|
7075 @node Q6.1.3, Q6.1.4, Q6.1.2, Internet
|
|
|
7076 @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"?
|
|
|
7077
|
|
|
7078 Set @code{vm-reply-ignored-addresses} to a list, like
|
|
|
7079
|
|
|
7080 @lisp
|
|
|
7081 (setq vm-reply-ignored-addresses
|
|
|
7082 '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com"
|
|
|
7083 "wing@@netcom.com" "wing@@xemacs.org"))
|
|
|
7084 @end lisp
|
|
|
7085
|
|
|
7086 Note that each string is a regular expression.
|
|
|
7087
|
|
|
7088 @node Q6.1.4, Q6.1.5, Q6.1.3, Internet
|
|
|
7089 @unnumberedsubsec Q6.1.4: Is there a mailing list or FAQ for VM?
|
|
|
7090
|
|
|
7091 A FAQ for VM exists at @uref{http://www.wonderworks.com/vm/FAQ.html}.
|
|
|
7092
|
|
|
7093 VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug.
|
|
|
7094
|
|
|
7095 @node Q6.1.5, Q6.1.6, Q6.1.4, Internet
|
|
|
7096 @unnumberedsubsec Q6.1.5: How do I make VM stay in a single frame?
|
|
|
7097
|
|
|
7098 John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes:
|
|
|
7099
|
|
|
7100 @quotation
|
|
|
7101 @lisp
|
|
|
7102 ; Don't use multiple frames
|
|
|
7103 (setq vm-frame-per-composition nil)
|
|
|
7104 (setq vm-frame-per-folder nil)
|
|
|
7105 (setq vm-frame-per-edit nil)
|
|
|
7106 (setq vm-frame-per-summary nil)
|
|
|
7107 @end lisp
|
|
|
7108 @end quotation
|
|
|
7109
|
|
|
7110 @node Q6.1.6, Q6.2.1, Q6.1.5, Internet
|
|
|
7111 @unnumberedsubsec Q6.1.6: Customization of VM not covered in the manual, or here.
|
|
|
7112
|
|
|
7113 @email{boffi@@hp735.stru.polimi.it, giacomo boffi} writes:
|
|
|
7114
|
|
|
7115 @quotation
|
|
|
7116 The meta-answer is to look into the file @file{vm-vars.el}, in the vm
|
|
|
7117 directory of the lisp library.
|
|
|
7118
|
|
|
7119 @file{vm-vars.el} contains, initializes and carefully describes, with
|
|
|
7120 examples of usage, the plethora of user options that @emph{fully}
|
|
|
7121 control VM's behavior.
|
|
|
7122
|
|
|
7123 Enter vm-vars, @code{forward-search} for toolbar, find the variables
|
|
|
7124 that control the toolbar placement, appearance, existence, copy to your
|
|
|
7125 @file{init.el} or @file{.vm} and modify according to the
|
|
|
7126 detailed instructions.
|
|
|
7127
|
|
|
7128 The above also applies to all the various features of VM: search for
|
|
|
7129 some keywords, maybe the first you conjure isn't appropriate, find the
|
|
|
7130 appropriate variables, copy and experiment.
|
|
|
7131 @end quotation
|
|
|
7132
|
|
|
7133 @unnumberedsec 6.2: Reading Netnews and Mail with Gnus
|
|
|
7134
|
|
|
7135 @node Q6.2.1, Q6.2.2, Q6.1.6, Internet
|
|
|
7136 @unnumberedsubsec Q6.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
7137
|
|
|
7138 The Gnus numbering issues are not meant for mere mortals to know them.
|
|
|
7139 If you feel you @emph{must} enter the muddy waters of Gnus, visit the
|
|
|
7140 excellent FAQ, maintained by Justin Sheehy, at:
|
|
|
7141
|
|
|
7142 @example
|
|
|
7143 @uref{http://my.gnus.org/FAQ/}
|
|
|
7144 @end example
|
|
|
7145
|
|
|
7146 See also Gnus home page
|
|
|
7147 @example
|
|
|
7148 @uref{http://www.gnus.org/}
|
|
|
7149 @end example
|
|
|
7150
|
|
|
7151 @node Q6.2.2, Q6.3.1, Q6.2.1, Internet
|
|
|
7152 @unnumberedsubsec Q6.2.2: How do I make Gnus stay within a single frame?
|
|
|
7153
|
|
|
7154 The toolbar code to start Gnus opens the new frame---and it's a feature
|
|
|
7155 rather than a bug. If you don't like it, but would still like to click
|
|
|
7156 on the seemly icon, use the following code:
|
|
|
7157
|
|
|
7158 @lisp
|
|
|
7159 (defun toolbar-news ()
|
|
|
7160 (gnus))
|
|
|
7161 @end lisp
|
|
|
7162
|
|
|
7163 It will redefine the callback function of the icon to just call
|
|
|
7164 @code{gnus}, without all the fancy frame stuff.
|
|
|
7165
|
|
|
7166 @unnumberedsec 6.3: FTP Access
|
|
|
7167
|
|
|
7168 @node Q6.3.1, Q6.3.2, Q6.2.2, Internet
|
|
|
7169 @unnumberedsubsec Q6.3.1: Can I edit files on other hosts?
|
|
|
7170
|
|
|
7171 Yes. Of course XEmacs can use any network file system (such as NFS or
|
|
|
7172 Windows file sharing) you have available, and includes some
|
|
|
7173 optimizations and safety features appropriate to those environments.
|
|
|
7174
|
|
|
7175 It is also possible to transparently edit files via FTP, ssh, or rsh. That
|
|
|
7176 is, XEmacs makes a local copy using the transport in the background, and
|
|
|
7177 automatically refreshes the remote original from that copy when you save
|
|
|
7178 it. XEmacs also is capable of doing file system manipulations like
|
|
|
7179 creating and removing directories and files. The FTP interface is
|
|
|
7180 provided by the standard @samp{efs} package @ref{Top, EFS, , efs}. The
|
|
|
7181 ssh/rsh interface is provided by the optional @samp{tramp} package
|
|
|
7182 @ref{Top, TRAMP, , tramp}.
|
|
|
7183
|
|
|
7184 @node Q6.3.2, Q6.4.1, Q6.3.1, Internet
|
|
|
7185 @unnumberedsubsec Q6.3.2: What is EFS?
|
|
|
7186
|
|
|
7187 #### Write me.
|
|
|
7188
|
|
|
7189 @unnumberedsec 6.4: Web Browsing with W3
|
|
|
7190
|
|
|
7191 @node Q6.4.1, Q6.4.2, Q6.3.2, Internet
|
|
|
7192 @unnumberedsubsec Q6.4.1: What is W3?
|
|
|
7193
|
|
|
7194 W3 is an advanced graphical browser written in Emacs lisp that runs on
|
|
|
7195 XEmacs. It has full support for cascaded style sheets, and more...
|
|
|
7196
|
|
|
7197 It has a home web page at
|
|
|
7198 @uref{http://www.cs.indiana.edu/elisp/w3/docs.html}.
|
|
|
7199
|
|
|
7200 @node Q6.4.2, Q6.4.3, Q6.4.1, Internet
|
|
|
7201 @unnumberedsubsec Q6.4.2: How do I run W3 from behind a firewall?
|
|
|
7202
|
|
|
7203 There is a long, well-written, detailed section in the W3 manual that
|
|
|
7204 describes how to do this. Look in the section entitled "Firewalls".
|
|
|
7205
|
|
|
7206 @node Q6.4.3, , Q6.4.2, Internet
|
|
|
7207 @unnumberedsubsec Q6.4.3: Is it true that W3 supports style sheets and tables?
|
|
|
7208
|
|
|
7209 Yes, and much more. W3, as distributed with the latest XEmacs is a
|
|
|
7210 full-featured web browser.
|
|
|
7211
|
|
|
7212 @node Advanced, Other Packages, Internet, Top
|
|
|
7213 @unnumbered 7 Advanced Customization Using XEmacs Lisp
|
|
|
7214
|
|
|
7215 This is part 7 of the XEmacs Frequently Asked Questions list. This
|
|
|
7216 section is devoted to advanced customization using XEmacs Lisp.
|
|
|
7217
|
|
|
7218 @menu
|
|
2537
|
7219 7.0: Emacs Lisp and @file{init.el}
|
|
|
7220 * Q7.0.1:: What version of Emacs am I running?
|
|
|
7221 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions?
|
|
|
7222 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly.
|
|
|
7223 * Q7.0.4:: How can I add directories to the @code{load-path}?
|
|
|
7224 * Q7.0.5:: How to check if a lisp function is defined?
|
|
|
7225 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer?
|
|
|
7226
|
|
|
7227 7.1: Emacs Lisp Programming Techniques
|
|
|
7228 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
|
7229 * Q7.1.2:: Can I generate "fake" keyboard events?
|
|
|
7230 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail?
|
|
|
7231 * Q7.1.4:: What is the performance hit of @code{let}?
|
|
|
7232 * Q7.1.5:: What is the recommended use of @code{setq}?
|
|
|
7233 * Q7.1.6:: What is the typical misuse of @code{setq}?
|
|
|
7234 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down?
|
|
|
7235 * Q7.1.8:: I like recursion, does it slow things down?
|
|
|
7236 * Q7.1.9:: How do I put a glyph as annotation in a buffer?
|
|
|
7237 * Q7.1.10:: @code{map-extents} won't traverse all of my extents!
|
|
|
7238 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
|
7239
|
|
|
7240 7.2: Mathematics
|
|
|
7241 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp?
|
|
|
7242 * Q7.2.2:: XEmacs segfaults when I use very big numbers!
|
|
|
7243 * Q7.2.3:: Bignums are really slow!
|
|
|
7244 * Q7.2.4:: Equal bignums don't compare as equal! What gives?
|
|
2459
|
7245 @end menu
|
|
|
7246
|
|
2537
|
7247 @unnumberedsec 7.0: Emacs Lisp and @file{init.el}
|
|
2459
|
7248
|
|
|
7249 @node Q7.0.1, Q7.0.2, Advanced, Advanced
|
|
2537
|
7250 @unnumberedsubsec Q7.0.1: What version of Emacs am I running?
|
|
2459
|
7251
|
|
|
7252 How can @file{init.el} determine which of the family of
|
|
|
7253 Emacsen I am using?
|
|
|
7254
|
|
|
7255 To determine if you are currently running GNU Emacs 18, GNU Emacs 19,
|
|
|
7256 XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the
|
|
|
7257 example given in @file{etc/sample.init.el} (@file{etc/sample.emacs} in
|
|
|
7258 XEmacs versions prior to 21.4). There are other nifty things in there
|
|
|
7259 as well!
|
|
|
7260
|
|
|
7261 For all new code, all you really need to do is:
|
|
|
7262
|
|
|
7263 @lisp
|
|
|
7264 (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
|
|
|
7265 @end lisp
|
|
|
7266
|
|
2537
|
7267 @node Q7.0.2, Q7.0.3, Q7.0.1, Advanced
|
|
|
7268 @unnumberedsubsec Q7.0.2: How can I evaluate Emacs-Lisp expressions?
|
|
2459
|
7269
|
|
|
7270 I know I can evaluate Elisp expressions from @code{*scratch*} buffer
|
|
|
7271 with @kbd{C-j} after the expression. How do I do it from another
|
|
|
7272 buffer?
|
|
|
7273
|
|
|
7274 Press @kbd{M-:} (the default binding of @code{eval-expression}), and
|
|
|
7275 enter the expression to the minibuffer.
|
|
|
7276
|
|
2537
|
7277 @node Q7.0.3, Q7.0.4, Q7.0.2, Advanced
|
|
|
7278 @unnumberedsubsec Q7.0.3: @code{(setq tab-width 6)} behaves oddly.
|
|
2459
|
7279
|
|
|
7280 If you put @code{(setq tab-width 6)} in your
|
|
|
7281 @file{init.el} file it does not work! Is there a reason
|
|
|
7282 for this? If you do it at the EVAL prompt it works fine!! How strange.
|
|
|
7283
|
|
|
7284 Use @code{setq-default} instead, since @code{tab-width} is
|
|
|
7285 all-buffer-local.
|
|
|
7286
|
|
2537
|
7287 @node Q7.0.4, Q7.0.5, Q7.0.3, Advanced
|
|
|
7288 @unnumberedsubsec Q7.0.4: How can I add directories to the @code{load-path}?
|
|
2459
|
7289
|
|
|
7290 Here are two ways to do that, one that puts your directories at the
|
|
|
7291 front of the load-path, the other at the end:
|
|
|
7292
|
|
|
7293 @lisp
|
|
|
7294 ;;; Add things at the beginning of the load-path, do not add
|
|
|
7295 ;;; duplicate directories:
|
|
|
7296 (pushnew "bar" load-path :test 'equal)
|
|
|
7297
|
|
|
7298 (pushnew "foo" load-path :test 'equal)
|
|
|
7299
|
|
|
7300 ;;; Add things at the end, unconditionally
|
|
|
7301 (setq load-path (nconc load-path '("foo" "bar")))
|
|
|
7302 @end lisp
|
|
|
7303
|
|
|
7304 @email{keithh@@nortel.ca, keith (k.p.) hanlan} writes:
|
|
|
7305
|
|
|
7306 @quotation
|
|
|
7307 To add directories using Unix shell metacharacters use
|
|
|
7308 @file{expand-file-name} like this:
|
|
|
7309
|
|
|
7310 @lisp
|
|
|
7311 (push (expand-file-name "~keithh/.emacsdir") load-path)
|
|
|
7312 @end lisp
|
|
|
7313 @end quotation
|
|
|
7314
|
|
2537
|
7315 @node Q7.0.5, Q7.0.6, Q7.0.4, Advanced
|
|
|
7316 @unnumberedsubsec Q7.0.5: How to check if a lisp function is defined?
|
|
2459
|
7317
|
|
|
7318 Use the following elisp:
|
|
|
7319
|
|
|
7320 @lisp
|
|
|
7321 (fboundp 'foo)
|
|
|
7322 @end lisp
|
|
|
7323
|
|
|
7324 It's almost always a mistake to test @code{emacs-version} or any similar
|
|
|
7325 variables.
|
|
|
7326
|
|
|
7327 Instead, use feature-tests, such as @code{featurep}, @code{boundp},
|
|
|
7328 @code{fboundp}, or even simple behavioral tests, eg.:
|
|
|
7329
|
|
|
7330 @lisp
|
|
|
7331 (defvar foo-old-losing-code-p
|
|
|
7332 (condition-case nil (progn (losing-code t) nil)
|
|
|
7333 (wrong-number-of-arguments t)))
|
|
|
7334 @end lisp
|
|
|
7335
|
|
|
7336 There is an incredible amount of broken code out there which could work
|
|
|
7337 much better more often in more places if it did the above instead of
|
|
|
7338 trying to divine its environment from the value of one variable.
|
|
|
7339
|
|
2537
|
7340 @node Q7.0.6, Q7.1.1, Q7.0.5, Advanced
|
|
|
7341 @unnumberedsubsec Q7.0.6: Can I force the output of @code{(face-list)} to a buffer?
|
|
2459
|
7342
|
|
|
7343 It would be good having it in a buffer, as the output of
|
|
|
7344 @code{(face-list)} is too wide to fit to a minibuffer.
|
|
|
7345
|
|
|
7346 Evaluate the expression in the @samp{*scratch*} buffer with point after
|
|
|
7347 the rightmost paren and typing @kbd{C-j}.
|
|
|
7348
|
|
|
7349 If the minibuffer smallness is the only problem you encounter, you can
|
|
|
7350 simply press @kbd{C-h l} to get the former minibuffer contents in a
|
|
|
7351 buffer.
|
|
|
7352
|
|
2537
|
7353 @unnumberedsec 7.1: Emacs Lisp Programming Techniques
|
|
|
7354
|
|
|
7355 @node Q7.1.1, Q7.1.2, Q7.0.6, Advanced
|
|
|
7356 @unnumberedsubsec Q7.1.1: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
2459
|
7357
|
|
|
7358 @email{clerik@@naggum.no, Erik Naggum} writes;
|
|
|
7359
|
|
|
7360 @quotation
|
|
|
7361 Emacs has a legacy of keyboards that produced characters with modifier
|
|
|
7362 bits, and therefore map a variety of input systems into this scheme even
|
|
|
7363 today. XEmacs is instead optimized for X events. This causes an
|
|
|
7364 incompatibility in the way key sequences are specified, but both Emacs
|
|
|
7365 and XEmacs will accept a key sequence as a vector of lists of modifiers
|
|
|
7366 that ends with a key, e.g., to bind @kbd{M-C-a}, you would say
|
|
|
7367 @code{[(meta control a)]} in both Emacsen. XEmacs has an abbreviated
|
|
|
7368 form for a single key, just (meta control a). Emacs has an abbreviated
|
|
|
7369 form for the Control and the Meta modifiers to string-characters (the
|
|
|
7370 ASCII characters), as in @samp{\M-\C-a}. XEmacs users need to be aware
|
|
|
7371 that the abbreviated form works only for one-character key sequences,
|
|
|
7372 while Emacs users need to be aware that the string-character is rather
|
|
|
7373 limited. Specifically, the string-character can accommodate only 256
|
|
|
7374 different values, 128 of which have the Meta modifier and 128 of which
|
|
|
7375 have not. In each of these blocks, only 32 characters have the Control
|
|
|
7376 modifier. Whereas @code{[(meta control A)]} differs from @code{[(meta
|
|
|
7377 control a)]} because the case differs, @samp{\M-\C-a} and @samp{\M-\C-A}
|
|
|
7378 do not. Programmers are advised to use the full common form, both
|
|
|
7379 because it is more readable and less error-prone, and because it is
|
|
|
7380 supported by both Emacsen.
|
|
|
7381 @end quotation
|
|
|
7382
|
|
|
7383 Another (even safer) way to be sure of the key-sequences is to use the
|
|
|
7384 @code{read-kbd-macro} function, which takes a string like @samp{C-c
|
|
|
7385 <up>}, and converts it to the internal key representation of the Emacs
|
|
|
7386 you use. The function is available both on XEmacs and GNU Emacs.
|
|
|
7387
|
|
2537
|
7388 @node Q7.1.2, Q7.1.3, Q7.1.1, Advanced
|
|
|
7389 @unnumberedsubsec Q7.1.2: Can I generate "fake" keyboard events?
|
|
2459
|
7390
|
|
|
7391 I wonder if there is an interactive function that can generate
|
|
|
7392 @dfn{fake} keyboard events. This way, I could simply map them inside
|
|
|
7393 XEmacs.
|
|
|
7394
|
|
|
7395 This seems to work:
|
|
|
7396
|
|
|
7397 @lisp
|
|
|
7398 (defun cg--generate-char-event (ch)
|
|
|
7399 "Generate an event, as if ch has been typed"
|
|
|
7400 (dispatch-event (character-to-event ch)))
|
|
|
7401
|
|
|
7402 ;; Backspace and Delete stuff
|
|
|
7403 (global-set-key [backspace]
|
|
|
7404 (lambda () (interactive) (cg--generate-char-event 127)))
|
|
|
7405 (global-set-key [unknown_keysym_0x4]
|
|
|
7406 (lambda () (interactive) (cg--generate-char-event 4)))
|
|
|
7407 @end lisp
|
|
|
7408
|
|
2537
|
7409 @node Q7.1.3, Q7.1.4, Q7.1.2, Advanced
|
|
|
7410 @unnumberedsubsec Q7.1.3: Could you explain @code{read-kbd-macro} in more detail?
|
|
2459
|
7411
|
|
|
7412 The @code{read-kbd-macro} function returns the internal Emacs
|
|
|
7413 representation of a human-readable string (which is its argument).
|
|
|
7414 Thus:
|
|
|
7415
|
|
|
7416 @lisp
|
|
|
7417 (read-kbd-macro "C-c C-a")
|
|
|
7418 @result{} [(control ?c) (control ?a)]
|
|
|
7419
|
|
|
7420 (read-kbd-macro "C-c C-. <up>")
|
|
|
7421 @result{} [(control ?c) (control ?.) up]
|
|
|
7422 @end lisp
|
|
|
7423
|
|
|
7424 In GNU Emacs the same forms will be evaluated to what GNU Emacs
|
|
|
7425 understands internally---the sequences @code{"\C-x\C-c"} and @code{[3
|
|
|
7426 67108910 up]}, respectively.
|
|
|
7427
|
|
|
7428 The exact @dfn{human-readable} syntax is defined in the docstring of
|
|
|
7429 @code{edmacro-mode}. I'll repeat it here, for completeness.
|
|
|
7430
|
|
|
7431 @quotation
|
|
|
7432 Format of keyboard macros during editing:
|
|
|
7433
|
|
|
7434 Text is divided into @dfn{words} separated by whitespace. Except for
|
|
|
7435 the words described below, the characters of each word go directly as
|
|
|
7436 characters of the macro. The whitespace that separates words is
|
|
|
7437 ignored. Whitespace in the macro must be written explicitly, as in
|
|
|
7438 @kbd{foo @key{SPC} bar @key{RET}}.
|
|
|
7439
|
|
|
7440 @itemize @bullet
|
|
|
7441 @item
|
|
|
7442 The special words @kbd{RET}, @kbd{SPC}, @kbd{TAB}, @kbd{DEL}, @kbd{LFD},
|
|
|
7443 @kbd{ESC}, and @kbd{NUL} represent special control characters. The
|
|
|
7444 words must be written in uppercase.
|
|
|
7445
|
|
|
7446 @item
|
|
|
7447 A word in angle brackets, e.g., @code{<return>}, @code{<down>}, or
|
|
|
7448 @code{<f1>}, represents a function key. (Note that in the standard
|
|
|
7449 configuration, the function key @code{<return>} and the control key
|
|
|
7450 @key{RET} are synonymous.) You can use angle brackets on the words
|
|
|
7451 @key{RET}, @key{SPC}, etc., but they are not required there.
|
|
|
7452
|
|
|
7453 @item
|
|
|
7454 Keys can be written by their @sc{ascii} code, using a backslash followed
|
|
|
7455 by up to six octal digits. This is the only way to represent keys with
|
|
|
7456 codes above \377.
|
|
|
7457
|
|
|
7458 @item
|
|
|
7459 One or more prefixes @kbd{M-} (meta), @kbd{C-} (control), @kbd{S-}
|
|
|
7460 (shift), @kbd{A-} (alt), @kbd{H-} (hyper), and @kbd{s-} (super) may
|
|
|
7461 precede a character or key notation. For function keys, the prefixes
|
|
|
7462 may go inside or outside of the brackets: @code{C-<down>} @equiv{}
|
|
|
7463 @code{<C-down>}. The prefixes may be written in any order: @kbd{M-C-x}
|
|
|
7464 @equiv{} @kbd{C-M-x}.
|
|
|
7465
|
|
|
7466 Prefixes are not allowed on multi-key words, e.g., @kbd{C-abc}, except
|
|
|
7467 that the Meta prefix is allowed on a sequence of digits and optional
|
|
|
7468 minus sign: @kbd{M--123} @equiv{} @kbd{M-- M-1 M-2 M-3}.
|
|
|
7469
|
|
|
7470 @item
|
|
|
7471 The @code{^} notation for control characters also works: @kbd{^M}
|
|
|
7472 @equiv{} @kbd{C-m}.
|
|
|
7473
|
|
|
7474 @item
|
|
|
7475 Double angle brackets enclose command names: @code{<<next-line>>} is
|
|
|
7476 shorthand for @kbd{M-x next-line @key{RET}}.
|
|
|
7477
|
|
|
7478 @item
|
|
|
7479 Finally, @code{REM} or @code{;;} causes the rest of the line to be
|
|
|
7480 ignored as a comment.
|
|
|
7481 @end itemize
|
|
|
7482
|
|
|
7483 Any word may be prefixed by a multiplier in the form of a decimal number
|
|
|
7484 and @code{*}: @code{3*<right>} @equiv{} @code{<right> <right> <right>},
|
|
|
7485 and @code{10*foo} @equiv{}
|
|
|
7486 @iftex
|
|
|
7487 @*
|
|
|
7488 @end iftex
|
|
|
7489 @code{foofoofoofoofoofoofoofoofoofoo}.
|
|
|
7490
|
|
|
7491 Multiple text keys can normally be strung together to form a word, but
|
|
|
7492 you may need to add whitespace if the word would look like one of the
|
|
|
7493 above notations: @code{; ; ;} is a keyboard macro with three semicolons,
|
|
|
7494 but @code{;;;} is a comment. Likewise, @code{\ 1 2 3} is four keys but
|
|
|
7495 @code{\123} is a single key written in octal, and @code{< right >} is
|
|
|
7496 seven keys but @code{<right>} is a single function key. When in doubt,
|
|
|
7497 use whitespace.
|
|
|
7498 @end quotation
|
|
|
7499
|
|
2537
|
7500 @node Q7.1.4, Q7.1.5, Q7.1.3, Advanced
|
|
|
7501 @unnumberedsubsec Q7.1.4: What is the performance hit of @code{let}?
|
|
2459
|
7502
|
|
|
7503 In most cases, not noticeable. Besides, there's no avoiding
|
|
|
7504 @code{let}---you have to bind your local variables, after all. Some
|
|
|
7505 pose a question whether to nest @code{let}s, or use one @code{let} per
|
|
|
7506 function. I think because of clarity and maintenance (and possible
|
|
|
7507 future implementation), @code{let}-s should be used (nested) in a way to
|
|
|
7508 provide the clearest code.
|
|
|
7509
|
|
2537
|
7510 @node Q7.1.5, Q7.1.6, Q7.1.4, Advanced
|
|
|
7511 @unnumberedsubsec Q7.1.5: What is the recommended use of @code{setq}?
|
|
2459
|
7512
|
|
|
7513 @itemize @bullet
|
|
|
7514 @item Global variables
|
|
|
7515
|
|
|
7516 You will typically @code{defvar} your global variable to a default
|
|
|
7517 value, and use @code{setq} to set it later.
|
|
|
7518
|
|
|
7519 It is never a good practice to @code{setq} user variables (like
|
|
|
7520 @code{case-fold-search}, etc.), as it ignores the user's choice
|
|
|
7521 unconditionally. Note that @code{defvar} doesn't change the value of a
|
|
|
7522 variable if it was bound previously. If you wish to change a
|
|
|
7523 user-variable temporarily, use @code{let}:
|
|
|
7524
|
|
|
7525 @lisp
|
|
|
7526 (let ((case-fold-search nil))
|
|
|
7527 ... ; code with searches that must be case-sensitive
|
|
|
7528 ...)
|
|
|
7529 @end lisp
|
|
|
7530
|
|
|
7531 You will notice the user-variables by their docstrings beginning with an
|
|
|
7532 asterisk (a convention).
|
|
|
7533
|
|
|
7534 @item Local variables
|
|
|
7535
|
|
|
7536 Bind them with @code{let}, which will unbind them (or restore their
|
|
|
7537 previous value, if they were bound) after exiting from the @code{let}
|
|
|
7538 form. Change the value of local variables with @code{setq} or whatever
|
|
|
7539 you like (e.g. @code{incf}, @code{setf} and such). The @code{let} form
|
|
|
7540 can even return one of its local variables.
|
|
|
7541
|
|
|
7542 Typical usage:
|
|
|
7543
|
|
|
7544 @lisp
|
|
|
7545 ;; iterate through the elements of the list returned by
|
|
|
7546 ;; `hairy-function-that-returns-list'
|
|
|
7547 (let ((l (hairy-function-that-returns-list)))
|
|
|
7548 (while l
|
|
|
7549 ... do something with (car l) ...
|
|
|
7550 (setq l (cdr l))))
|
|
|
7551 @end lisp
|
|
|
7552
|
|
|
7553 Another typical usage includes building a value simply to work with it.
|
|
|
7554
|
|
|
7555 @lisp
|
|
|
7556 ;; Build the mode keymap out of the key-translation-alist
|
|
|
7557 (let ((inbox (file-truename (expand-file-name box)))
|
|
|
7558 (i 0))
|
|
|
7559 ... code dealing with inbox ...
|
|
|
7560 inbox)
|
|
|
7561 @end lisp
|
|
|
7562
|
|
|
7563 This piece of code uses the local variable @code{inbox}, which becomes
|
|
|
7564 unbound (or regains old value) after exiting the form. The form also
|
|
|
7565 returns the value of @code{inbox}, which can be reused, for instance:
|
|
|
7566
|
|
|
7567 @lisp
|
|
|
7568 (setq foo-processed-inbox
|
|
|
7569 (let .....))
|
|
|
7570 @end lisp
|
|
|
7571 @end itemize
|
|
|
7572
|
|
2537
|
7573 @node Q7.1.6, Q7.1.7, Q7.1.5, Advanced
|
|
|
7574 @unnumberedsubsec Q7.1.6: What is the typical misuse of @code{setq}?
|
|
2459
|
7575
|
|
|
7576 A typical misuse is probably @code{setq}ing a variable that was meant to
|
|
|
7577 be local. Such a variable will remain bound forever, never to be
|
|
|
7578 garbage-collected. For example, the code doing:
|
|
|
7579
|
|
|
7580 @lisp
|
|
|
7581 (defun my-function (whatever)
|
|
|
7582 (setq a nil)
|
|
|
7583 ... build a large list ...
|
|
|
7584 ... and exit ...)
|
|
|
7585 @end lisp
|
|
|
7586
|
|
|
7587 does a bad thing, as @code{a} will keep consuming memory, never to be
|
|
|
7588 unbound. The correct thing is to do it like this:
|
|
|
7589
|
|
|
7590 @lisp
|
|
|
7591 (defun my-function (whatever)
|
|
|
7592 (let (a) ; default initialization is to nil
|
|
|
7593 ... build a large list ...
|
|
|
7594 ... and exit, unbinding `a' in the process ...)
|
|
|
7595 @end lisp
|
|
|
7596
|
|
|
7597 Not only is this prettier syntactically, but it makes it possible for
|
|
|
7598 Emacs to garbage-collect the objects which @code{a} used to reference.
|
|
|
7599
|
|
|
7600 Note that even global variables should not be @code{setq}ed without
|
|
|
7601 @code{defvar}ing them first, because the byte-compiler issues warnings.
|
|
|
7602 The reason for the warning is the following:
|
|
|
7603
|
|
|
7604 @lisp
|
|
|
7605 (defun flurgoze nil) ; ok, global internal variable
|
|
|
7606 ...
|
|
|
7607
|
|
|
7608 (setq flurghoze t) ; ops! a typo, but semantically correct.
|
|
|
7609 ; however, the byte-compiler warns.
|
|
|
7610
|
|
|
7611 While compiling toplevel forms:
|
|
|
7612 ** assignment to free variable flurghoze
|
|
|
7613 @end lisp
|
|
|
7614
|
|
2537
|
7615 @node Q7.1.7, Q7.1.8, Q7.1.6, Advanced
|
|
|
7616 @unnumberedsubsec Q7.1.7: I like the @code{do} form of cl, does it slow things down?
|
|
2459
|
7617
|
|
|
7618 It shouldn't. Here is what Dave Gillespie has to say about cl.el
|
|
|
7619 performance:
|
|
|
7620
|
|
|
7621 @quotation
|
|
|
7622 Many of the advanced features of this package, such as @code{defun*},
|
|
|
7623 @code{loop}, and @code{setf}, are implemented as Lisp macros. In
|
|
|
7624 byte-compiled code, these complex notations will be expanded into
|
|
|
7625 equivalent Lisp code which is simple and efficient. For example, the
|
|
|
7626 forms
|
|
|
7627
|
|
|
7628 @lisp
|
|
|
7629 (incf i n)
|
|
|
7630 (push x (car p))
|
|
|
7631 @end lisp
|
|
|
7632
|
|
|
7633 are expanded at compile-time to the Lisp forms
|
|
|
7634
|
|
|
7635 @lisp
|
|
|
7636 (setq i (+ i n))
|
|
|
7637 (setcar p (cons x (car p)))
|
|
|
7638 @end lisp
|
|
|
7639
|
|
|
7640 which are the most efficient ways of doing these respective operations
|
|
|
7641 in Lisp. Thus, there is no performance penalty for using the more
|
|
|
7642 readable @code{incf} and @code{push} forms in your compiled code.
|
|
|
7643
|
|
|
7644 @emph{Interpreted} code, on the other hand, must expand these macros
|
|
|
7645 every time they are executed. For this reason it is strongly
|
|
|
7646 recommended that code making heavy use of macros be compiled. (The
|
|
|
7647 features labelled @dfn{Special Form} instead of @dfn{Function} in this
|
|
|
7648 manual are macros.) A loop using @code{incf} a hundred times will
|
|
|
7649 execute considerably faster if compiled, and will also garbage-collect
|
|
|
7650 less because the macro expansion will not have to be generated, used,
|
|
|
7651 and thrown away a hundred times.
|
|
|
7652
|
|
|
7653 You can find out how a macro expands by using the @code{cl-prettyexpand}
|
|
|
7654 function.
|
|
|
7655 @end quotation
|
|
|
7656
|
|
2537
|
7657 @node Q7.1.8, Q7.1.9, Q7.1.7, Advanced
|
|
|
7658 @unnumberedsubsec Q7.1.8: I like recursion, does it slow things down?
|
|
2459
|
7659
|
|
|
7660 Yes. The Emacs byte-compiler cannot do much to optimize recursion. But
|
|
|
7661 think well whether this is a real concern in Emacs. Much of the Emacs
|
|
|
7662 slowness comes from internal mechanisms such as redisplay, or from the
|
|
|
7663 fact that it is an interpreter.
|
|
|
7664
|
|
|
7665 Please try not to make your code much uglier to gain a very small speed
|
|
|
7666 gain. It's not usually worth it.
|
|
|
7667
|
|
2537
|
7668 @node Q7.1.9, Q7.1.10, Q7.1.8, Advanced
|
|
|
7669 @unnumberedsubsec Q7.1.9: How do I put a glyph as annotation in a buffer?
|
|
2459
|
7670
|
|
|
7671 Here is a solution that will insert the glyph annotation at the
|
|
|
7672 beginning of buffer:
|
|
|
7673
|
|
|
7674 @lisp
|
|
|
7675 (make-annotation (make-glyph '([FORMAT :file FILE]
|
|
|
7676 [string :data "fallback-text"]))
|
|
|
7677 (point-min)
|
|
|
7678 'text
|
|
|
7679 (current-buffer))
|
|
|
7680 @end lisp
|
|
|
7681
|
|
|
7682 Replace @samp{FORMAT} with an unquoted symbol representing the format of
|
|
|
7683 the image (e.g. @code{xpm}, @code{xbm}, @code{gif}, @code{jpeg}, etc.)
|
|
|
7684 Instead of @samp{FILE}, use the image file name
|
|
|
7685 (e.g.
|
|
|
7686 @iftex
|
|
|
7687 @*
|
|
|
7688 @end iftex
|
|
|
7689 @file{/usr/local/lib/xemacs-21.4/etc/recycle.xpm}).
|
|
|
7690
|
|
|
7691 You can turn this to a function (that optionally prompts you for a file
|
|
|
7692 name), and inserts the glyph at @code{(point)} instead of
|
|
|
7693 @code{(point-min)}.
|
|
|
7694
|
|
2537
|
7695 @node Q7.1.10, Q7.1.11, Q7.1.9, Advanced
|
|
|
7696 @unnumberedsubsec Q7.1.10: @code{map-extents} won't traverse all of my extents!
|
|
2459
|
7697
|
|
|
7698 I tried to use @code{map-extents} to do an operation on all the extents
|
|
|
7699 in a region. However, it seems to quit after processing a random number
|
|
|
7700 of extents. Is it buggy?
|
|
|
7701
|
|
|
7702 No. The documentation of @code{map-extents} states that it will iterate
|
|
|
7703 across the extents as long as @var{function} returns @code{nil}.
|
|
|
7704 Unexperienced programmers often forget to return @code{nil} explicitly,
|
|
|
7705 which results in buggy code. For instance, the following code is
|
|
|
7706 supposed to delete all the extents in a buffer, and issue as many
|
|
|
7707 @samp{fubar!} messages.
|
|
|
7708
|
|
|
7709 @lisp
|
|
|
7710 (map-extents (lambda (ext ignore)
|
|
|
7711 (delete-extent ext)
|
|
|
7712 (message "fubar!")))
|
|
|
7713 @end lisp
|
|
|
7714
|
|
|
7715 Instead, it will delete only the first extent, and stop right there --
|
|
|
7716 because @code{message} will return a non-nil value. The correct code
|
|
|
7717 is:
|
|
|
7718
|
|
|
7719 @lisp
|
|
|
7720 (map-extents (lambda (ext ignore)
|
|
|
7721 (delete-extent ext)
|
|
|
7722 (message "fubar!")
|
|
|
7723 nil))
|
|
|
7724 @end lisp
|
|
|
7725
|
|
2537
|
7726 @node Q7.1.11, Q7.2.1, Q7.1.10, Advanced
|
|
|
7727 @unnumberedsubsec Q7.1.11: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
2459
|
7728 @c New
|
|
|
7729
|
|
|
7730 @email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
|
|
|
7731 @quotation
|
|
|
7732 Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence},
|
|
|
7733 press a key (say @key{RET} in the Gnus Group buffer), and get the
|
|
|
7734 results using @kbd{M-x profile-results}. It should give you an idea of
|
|
|
7735 where the time is being spent.
|
|
|
7736 @end quotation
|
|
|
7737
|
|
2537
|
7738 @unnumberedsec 7.2: Mathematics
|
|
|
7739
|
|
|
7740 @node Q7.2.1, Q7.2.2, Q7.1.11, Advanced
|
|
|
7741 @unnumberedsubsec Q7.2.1: What are bignums, ratios, and bigfloats in Lisp?
|
|
2459
|
7742
|
|
|
7743 Thanks to @email{james@@xemacs.org, Jerry James}, XEmacs 21.5.18 and
|
|
|
7744 later can use the capabilities of multiple-precision libraries that may
|
|
|
7745 be available for your platform. The GNU Multiple Precision (GMP) and
|
|
|
7746 BSD Multiple Precision (MP) libraries are partially supported. GMP
|
|
|
7747 gives you @dfn{bignums} (arbitrary precision integers), @dfn{ratios}
|
|
|
7748 (arbitrary precision fractions), and @dfn{bigfloats} (arbitrary
|
|
|
7749 precision floating point numbers). GNU MP is better-supported by XEmacs
|
|
|
7750 at the time of writing (2004-04-06). BSD MP support does not include
|
|
|
7751 ratios or bigfloats, and it throws errors that aren't understood.
|
|
|
7752
|
|
|
7753 In most cases, bignum support should be transparent to users and Lisp
|
|
|
7754 programmers. A bignum-enabled XEmacs will automatically convert from
|
|
|
7755 fixnums to bignums and back in pure integer arithmetic, and for GNU MP,
|
|
|
7756 from floats to bigfloats. (Bigfloats must be explicitly coerced to
|
|
|
7757 other types, even if they are exactly representable by less precise
|
|
|
7758 types.) The Lisp reader and printer have been enhanced to handle
|
|
|
7759 bignums, as have the mathematical functions. Rationals (fixnums,
|
|
|
7760 bignums, and ratios) are printed using the @samp{%d}, @samp{%o},
|
|
|
7761 @samp{%x}, and @samp{%u} format conversions. The read syntax for ratios
|
|
|
7762 is @samp{3/5}.
|
|
|
7763
|
|
|
7764 User-visible changes in behavior include (in probable order of annoyance)
|
|
|
7765
|
|
|
7766 @itemize
|
|
|
7767 @item
|
|
|
7768 Arithmetic can cause a segfault, depending on your MP library
|
|
2537
|
7769 @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}.
|
|
2459
|
7770
|
|
|
7771 @item
|
|
|
7772 Terminology is not Common-Lisp-conforming. For example, ``integer'' for
|
|
|
7773 Emacs Lisp means what Common Lisp calls ``fixnum''. This issue is being
|
|
|
7774 investigated, but the use of ``integer'' for fixnum is pervasive and may
|
|
|
7775 cause backward-compatibility and GNU-Emacs-compatibility problems.
|
|
|
7776
|
|
|
7777 @item
|
|
|
7778 Many operations that used to cause a range error now succeed, with
|
|
|
7779 intermediate results and return values coerced to bignums as needed.
|
|
|
7780
|
|
|
7781 @item
|
|
|
7782 An atom with ratio read syntax now returns a number, not a symbol.
|
|
|
7783
|
|
|
7784 @item
|
|
|
7785 The @samp{%u} format conversion will now give an error if its argument
|
|
|
7786 is negative. (Without MP, it prints a number which Lisp can't read.)
|
|
|
7787 @end itemize
|
|
|
7788
|
|
|
7789 @emph{Surgeon General's Warning}: The automatic conversions cannot be
|
|
|
7790 disabled at runtime. New functions have been added which produce
|
|
|
7791 ratios, so there should be few surprises with type conflicts, but they
|
|
|
7792 can't be ruled out. ``Arbitrary'' precision means precisely what it
|
|
|
7793 says. If you work with extremely large numbers, your machine may
|
|
|
7794 arbitrarily decide to hand you an unpleasant surprise rather than a
|
|
2537
|
7795 bignum @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}.
|
|
2459
|
7796
|
|
|
7797 To configure with GNU MP, add
|
|
|
7798 @samp{--use-number-lib=gmp}
|
|
|
7799 to your invocation of @file{configure}. For BSD MP, use
|
|
|
7800 @samp{--use-number-lib=mp}.
|
|
|
7801
|
|
|
7802 If you would like to help with bignum support, especially on BSD MP,
|
|
|
7803 please subscribe to the @uref{http://www.xemacs.org/Lists/#xemacs-beta,
|
|
|
7804 XEmacs Beta mailing list}, and book up on @file{number-gmp.h} and
|
|
|
7805 @file{number-mp.h}. Jerry has promised to write internals documentation
|
|
|
7806 eventually, but if your skills run more to analysis and documentation
|
|
|
7807 than to writing new code, feel free to fill in the gap!
|
|
|
7808
|
|
|
7809
|
|
2537
|
7810 @node Q7.2.2, Q7.2.3, Q7.2.1, Advanced
|
|
|
7811 @unnumberedsubsec Q7.2.2: XEmacs segfaults when I use very big numbers!
|
|
2459
|
7812
|
|
|
7813 GMP by default allocates temporaries on the stack. If you run out of
|
|
|
7814 stack space, you're dead; there is no way that we know of to reliably
|
|
|
7815 detect this condition, because @samp{alloca} is typically implemented to
|
|
|
7816 be @emph{fast} rather than robust. If you just need a little more
|
|
|
7817 oomph, use a bigger stack (@emph{e.g.}, the @file{ulimit -s} command in
|
|
|
7818 bash(1)). If you want robustness at the cost of speed, configure GMP
|
|
|
7819 with @samp{--disable-alloca} and rebuild the GMP library.
|
|
|
7820
|
|
|
7821 We do not know whether BSD MP uses @samp{alloca} or not. Please send
|
|
|
7822 any information you have as a bug report (@kbd{M-x report-xemacs-bug
|
|
|
7823 @key{RET}}), which will give us platform information. (We do know that
|
|
|
7824 BSD MP implementations vary across vendors, but how much, we do not know
|
|
|
7825 yet.)
|
|
|
7826
|
|
|
7827
|
|
2537
|
7828 @node Q7.2.3, Q7.2.4, Q7.2.2, Advanced
|
|
|
7829 @unnumberedsubsec Q7.2.3: Bignums are really slow!
|
|
2459
|
7830
|
|
|
7831 Many Linux distributions compile all their packages for the i386, and
|
|
|
7832 this is costly. An optimized version can give you two or three orders
|
|
|
7833 of magnitude better performance for a Pentium III or IV. (Yes, really.
|
|
|
7834 See @uref{http://www.swox.com/gmp/gmp-speed.html}.)
|
|
|
7835
|
|
|
7836
|
|
2537
|
7837 @node Q7.2.4, , Q7.2.3, Advanced
|
|
|
7838 @unnumberedsubsec Q7.2.4: Equal bignums don't compare as equal! What gives?
|
|
2459
|
7839
|
|
|
7840 Ah, Grasshopper, I see you are using @code{(eq x y)}. The Bodhisattva
|
|
|
7841 CLTL2 warned of the illusion that equal numbers would be @samp{eq}!
|
|
|
7842 Meditate on the deeper truths of @samp{eql}, in which numbers of the same
|
|
|
7843 type which have equal values compare equal, and @samp{=}, which does any
|
|
|
7844 necessary type coercions before comparing for equality.
|
|
|
7845
|
|
|
7846 Yeah, yeah, it has always worked for integer types, because fixnums and
|
|
|
7847 characters have an immediate representation. Sorry about that;
|
|
|
7848 arbitrary precision obviously requires consing new objects because the
|
|
|
7849 objects are ``large'' and of variable size, and the definition of
|
|
|
7850 @samp{eq} does not permit different objects to compare as equal.
|
|
|
7851
|
|
|
7852 @node Other Packages, Current Events, Advanced, Top
|
|
|
7853 @unnumbered 8 Other External Packages
|
|
|
7854
|
|
|
7855 This is part 8 of the XEmacs Frequently Asked Questions list. This
|
|
|
7856 section is devoted to miscellaneous external packages not covered
|
|
|
7857 elsewhere in XEmacs.
|
|
|
7858
|
|
|
7859 @menu
|
|
2537
|
7860 8.0: TeX
|
|
2459
|
7861 * Q8.0.1:: Is there something better than LaTeX mode?
|
|
|
7862 * Q8.0.2:: What is AUCTeX? Where do you get it?
|
|
|
7863 * Q8.0.3:: Problems installing AUCTeX.
|
|
|
7864 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline?
|
|
|
7865
|
|
|
7866 8.1: Other Unbundled Packages
|
|
|
7867 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
|
7868 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets?
|
|
|
7869 * Q8.1.3:: Is there a MatLab mode?
|
|
|
7870
|
|
|
7871 8.2: Environments Built Around XEmacs
|
|
|
7872 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop?
|
|
|
7873 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21?
|
|
|
7874 * Q8.2.3:: What is/was Energize?
|
|
|
7875 * Q8.2.4:: What is Infodock?
|
|
|
7876 @end menu
|
|
|
7877
|
|
|
7878 @unnumberedsec 8.0: TeX
|
|
|
7879
|
|
|
7880 @node Q8.0.1, Q8.0.2, Other Packages, Other Packages
|
|
|
7881 @unnumberedsubsec Q8.0.1: Is there something better than LaTeX mode?
|
|
2417
|
7882
|
|
|
7883 @email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes:
|
|
|
7884
|
|
|
7885 @quotation
|
|
|
7886 The standard TeX modes leave much to be desired, and are somewhat
|
|
2459
|
7887 leniently maintained. Serious TeX users use AUCTeX (@pxref{Q8.0.2,
|
|
2417
|
7888 What is AUCTeX? Where do you get it?}).
|
|
|
7889 @end quotation
|
|
|
7890
|
|
2459
|
7891 @node Q8.0.2, Q8.0.3, Q8.0.1, Other Packages
|
|
|
7892 @unnumberedsubsec Q8.0.2: What is AUCTeX? Where do you get it?
|
|
2417
|
7893
|
|
|
7894 AUCTeX is a complex and sophisticated editing package dedicated to TeX
|
|
|
7895 and related text formatting languages, including LaTeX and Texinfo.
|
|
|
7896 It provides support for running TeX on a file or part of a file,
|
|
|
7897 include files, and of course shortcuts for entering common TeX macros,
|
|
|
7898 LaTeX environments, etc, and for fontlock.
|
|
|
7899
|
|
|
7900 AUCTeX is a standard package provided by XEmacs. You can get it as
|
|
|
7901 usual through the @kbd{M-x list-packages} interface. It is also
|
|
|
7902 included in the (non-Mule) SUMO package. The AUCTeX XEmacs package is
|
|
|
7903 maintained by Uwe Brauer <GET MAIL ADDRESS>.
|
|
|
7904
|
|
|
7905 AUCTeX is extremely complicated, and its developers primarily
|
|
|
7906 use GNU Emacs. Not all features of the bleeding edge version
|
|
|
7907 of AUCTeX are immediately ported to XEmacs; if you need
|
|
|
7908 these, you may be better off getting the most recent versions
|
|
|
7909 from the GNU AUCTeX project on @uref{http://savannah.gnu.org}.
|
|
|
7910
|
|
2459
|
7911 @node Q8.0.3, Q8.0.4, Q8.0.2, Other Packages
|
|
|
7912 @unnumberedsubsec Q8.0.3: Problems installing AUCTeX.
|
|
2417
|
7913
|
|
|
7914 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
|
|
|
7915
|
|
|
7916 @quotation
|
|
|
7917 AUCTeX works fine on both stock Emacs and XEmacs has been doing so for
|
|
|
7918 a very very long time. This is mostly due to the work of
|
|
|
7919 @email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu}
|
|
|
7920 package. Which leads to what is probably the problem...
|
|
|
7921 @end quotation
|
|
|
7922
|
|
|
7923 Most problems with AUCTeX are one of two things:
|
|
|
7924
|
|
|
7925 @itemize @bullet
|
|
|
7926 @item
|
|
|
7927 The TeX-lisp-directory in @file{tex-site.el} and the makefile don't
|
|
|
7928 match.
|
|
|
7929
|
|
|
7930 Fix: make sure you configure AUCTeX properly @strong{before} installing.
|
|
|
7931
|
|
|
7932 @item
|
|
|
7933 You have an old version of easymenu.el in your path.
|
|
|
7934
|
|
|
7935 Fix: use @code{locate-library} and remove old versions to make sure it
|
|
|
7936 @strong{only} finds the one that came with XEmacs.
|
|
|
7937 @end itemize
|
|
|
7938
|
|
2459
|
7939 @node Q8.0.4, Q8.1.1, Q8.0.3, Other Packages
|
|
|
7940 @unnumberedsubsec Q8.0.4: How do I turn off current chapter from AUCTeX modeline?
|
|
2417
|
7941
|
|
|
7942 With AUCTeX, fast typing is hard because the current chapter, section
|
|
|
7943 etc. are given in the modeline. How can I turn this off?
|
|
|
7944
|
|
|
7945 It's not AUCTeX, it comes from @code{func-menu} in @file{func-menu.el}.
|
|
|
7946
|
|
|
7947 @c Add this code to your @file{init.el} to turn it off:
|
|
|
7948 @c
|
|
|
7949 @c @lisp
|
|
|
7950 @c (setq fume-display-in-modeline-p nil)
|
|
|
7951 @c @end lisp
|
|
|
7952 @c
|
|
|
7953 @c Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
|
|
|
7954 @c mode:
|
|
|
7955 @c
|
|
|
7956 @c @lisp
|
|
|
7957 @c (add-hook 'TeX-mode-hook
|
|
|
7958 @c '(lambda () (setq fume-display-in-modeline-p nil)))
|
|
|
7959 @c @end lisp
|
|
|
7960 @c
|
|
|
7961 @email{dhughes@@origin-at.co.uk, David Hughes} writes:
|
|
|
7962
|
|
|
7963 @quotation
|
|
|
7964 Try this; you'll still get the function name displayed in the modeline,
|
|
|
7965 but it won't attempt to keep track when you modify the file. To refresh
|
|
|
7966 when it gets out of synch, you simply need click on the @samp{Rescan
|
|
|
7967 Buffer} option in the function-menu.
|
|
|
7968
|
|
|
7969 @lisp
|
|
|
7970 (setq-default fume-auto-rescan-buffer-p nil)
|
|
|
7971 @end lisp
|
|
|
7972 @end quotation
|
|
|
7973
|
|
2459
|
7974 @unnumberedsec 8.1: Other Unbundled Packages
|
|
|
7975
|
|
|
7976 @node Q8.1.1, Q8.1.2, Q8.0.4, Other Packages
|
|
|
7977 @unnumberedsubsec Q8.1.1: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
2417
|
7978
|
|
|
7979 The reason for an Emacs package not to be included in XEmacs is
|
|
|
7980 usually one or more of the following:
|
|
|
7981
|
|
|
7982 @enumerate
|
|
|
7983 @item
|
|
|
7984 The package has not been ported to XEmacs. This will typically happen
|
|
|
7985 when it uses GNU-Emacs-specific features, which make it fail under
|
|
|
7986 XEmacs.
|
|
|
7987
|
|
|
7988 Porting a package to XEmacs can range from a trivial amount of change to
|
|
|
7989 a partial or full rewrite. Fortunately, the authors of modern packages
|
|
|
7990 usually choose to support both Emacsen themselves.
|
|
|
7991
|
|
|
7992 @item
|
|
|
7993 The package has been decided not to be appropriate for XEmacs. It may
|
|
|
7994 have an equivalent or better replacement within XEmacs, in which case
|
|
|
7995 the developers may choose not to burden themselves with supporting an
|
|
|
7996 additional package.
|
|
|
7997
|
|
|
7998 Each package bundled with XEmacs means more work for the maintainers,
|
|
|
7999 whether they want it or not. If you are ready to take over the
|
|
|
8000 maintenance responsibilities for the package you port, be sure to say
|
|
|
8001 so---we will more likely include it.
|
|
|
8002
|
|
|
8003 @item
|
|
|
8004 The package simply hasn't been noted by the XEmacs development. If
|
|
|
8005 that's the case, the messages like yours are very useful for attracting
|
|
|
8006 our attention.
|
|
|
8007
|
|
|
8008 @item
|
|
|
8009 The package was noted by the developers, but they simply haven't yet
|
|
|
8010 gotten around to including/porting it. Wait for the next release or,
|
|
|
8011 even better, offer your help. It will be gladly accepted and
|
|
|
8012 appreciated.
|
|
|
8013 @end enumerate
|
|
|
8014
|
|
2459
|
8015 @node Q8.1.2, Q8.1.3, Q8.1.1, Other Packages
|
|
|
8016 @unnumberedsubsec Q8.1.2: Are there any Emacs Lisp Spreadsheets?
|
|
2417
|
8017
|
|
|
8018 Yes. Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at
|
|
428
|
8019 @iftex
|
|
|
8020 @*
|
|
|
8021 @end iftex
|
|
2459
|
8022 @uref{http://acs.ist.psu.edu/dismal/dismal.html}.
|
|
|
8023
|
|
|
8024 @node Q8.1.3, Q8.2.1, Q8.1.2, Other Packages
|
|
|
8025 @unnumberedsubsec Q8.1.3: Is there a MatLab mode?
|
|
2417
|
8026
|
|
|
8027 Yes, a matlab mode and other items are available at the
|
|
2459
|
8028 @uref{http://www.mathworks.com/matlabcentral/files/104/matlab.el}.
|
|
|
8029
|
|
|
8030 @unnumberedsec 8.2: Environments Built Around XEmacs
|
|
|
8031
|
|
|
8032 @node Q8.2.1, Q8.2.2, Q8.1.3, Other Packages
|
|
|
8033 @unnumberedsubsec Q8.2.1: What are SPARCworks, EOS, and WorkShop?
|
|
2417
|
8034
|
|
|
8035 SPARCworks was a development environment from Sun (circa 1993-1996)
|
|
|
8036 and consisted of compilers (C, C++, FORTRAN 77, Fortran 90, Ada, and
|
|
|
8037 Pascal), a debugger, and other tools such as TeamWare (for
|
|
|
8038 configuration management), MakeTool, etc.
|
|
428
|
8039
|
|
|
8040 EOS is the integration of XEmacs with the SPARCworks debugger. It
|
|
|
8041 allows one to use an XEmacs frame to view code (complete with
|
|
|
8042 fontification, etc.), set breakpoints, print variables, etc., while
|
|
2417
|
8043 using the SPARCworks debugger.
|
|
|
8044
|
|
|
8045 EOS stands for "Era on SPARCworks"; Era stood for "Emacs Rewritten
|
|
|
8046 Again" and was the name used by Sun for its modified version of Lucid
|
|
|
8047 Emacs (later XEmacs) in the early-mid 90's. This is documented in
|
|
|
8048 more detail in the history section of the XEmacs About page.
|
|
|
8049
|
|
|
8050 EOS was replaced around 1996 with a newer graphical development
|
|
|
8051 environment called Sun WorkShop. The current status of this is
|
|
|
8052 unknown.
|
|
|
8053
|
|
2459
|
8054 @node Q8.2.2, Q8.2.3, Q8.2.1, Other Packages
|
|
|
8055 @unnumberedsubsec Q8.2.2: How do I start the Sun Workshop support in XEmacs 21?
|
|
428
|
8056
|
|
|
8057 Add the switch ---with-workshop to the configure command when building
|
|
|
8058 XEmacs and put the following in one of your startup files
|
|
|
8059 (e.g. site-start.el or .emacs):
|
|
|
8060
|
|
|
8061 @lisp
|
|
|
8062 (when (featurep 'tooltalk)
|
|
|
8063 (load "tooltalk-macros")
|
|
|
8064 (load "tooltalk-util")
|
|
|
8065 (load "tooltalk-init"))
|
|
|
8066 (when (featurep 'sparcworks)
|
|
|
8067 (load "sunpro-init")
|
|
|
8068 (load "ring")
|
|
|
8069 (load "comint")
|
|
|
8070 (load "annotations")
|
|
|
8071 (sunpro-startup))
|
|
|
8072 @end lisp
|
|
|
8073
|
|
|
8074 If you are not using the latest Workshop (5.0) you have to apply the
|
|
|
8075 following patch:
|
|
|
8076
|
|
|
8077 @format
|
|
|
8078 --- /opt/SUNWspro/lib/eserve.el.ORIG Fri May 14 15:23:26 1999
|
|
|
8079 +++ /opt/SUNWspro/lib/eserve.el Fri May 14 15:24:54 1999
|
|
|
8080 @@@@ -42,7 +42,7 @@@@
|
|
|
8081 (defvar running-xemacs nil "t if we're running XEmacs")
|
|
|
8082 (defvar running-emacs nil "t if we're running GNU Emacs 19")
|
|
438
|
8083
|
|
428
|
8084 -(if (string-match "^\\(19\\|20\\)\..*\\(XEmacs\\|Lucid\\)" emacs-version)
|
|
|
8085 +(if (string-match "\\(XEmacs\\|Lucid\\)" emacs-version)
|
|
|
8086 (setq running-xemacs t)
|
|
|
8087 (setq running-emacs t))
|
|
438
|
8088 @end format
|
|
428
|
8089
|
|
2459
|
8090 @node Q8.2.3, Q8.2.4, Q8.2.2, Other Packages
|
|
|
8091 @unnumberedsubsec Q8.2.3: What is/was Energize?
|
|
2417
|
8092
|
|
|
8093 The "Energize Programming System" was a C and C++ development environment
|
|
|
8094 sold by Lucid, Inc. It was the reason why Lucid Emacs, now XEmacs, was
|
|
|
8095 created in the first place. Unfortunately, Lucid went out of business in
|
|
|
8096 1994. The rights to sell it in Japan were purchased by INS
|
|
|
8097 Engineering (which briefly employed Stig Hackvan aka Jonathan
|
|
|
8098 Stigelman to work on Japanese support for XEmacs, in late 1994 and
|
|
|
8099 early 1995) and Tartan bought the rights to sell it in the rest of the
|
|
|
8100 world. However, INS is not selling Energize at this point and may or
|
|
|
8101 may not have ever done so; Tartan certainly never did.
|
|
|
8102
|
|
2459
|
8103 @node Q8.2.4, , Q8.2.3, Other Packages
|
|
|
8104 @unnumberedsubsec Q8.2.4: What is Infodock?
|
|
428
|
8105
|
|
660
|
8106 @uref{http://sourceforge.net/projects/infodock/, InfoDock} is an
|
|
|
8107 integrated productivity toolset, mainly aimed at technical people,
|
|
|
8108 hosted at SourceForge.
|
|
428
|
8109
|
|
|
8110 InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of
|
|
|
8111 the power of Emacs, but with an easier to use and more comprehensive
|
|
|
8112 menu-based user interface. The bottom portion of this text describes
|
|
|
8113 how it differs from XEmacs and GNU Emacs from the Free Software
|
|
|
8114 Foundation.
|
|
|
8115
|
|
|
8116 InfoDock is aimed at people who want a free, turn-key productivity
|
|
|
8117 environment. Although InfoDock is customizable, it is not intended for
|
|
|
8118 people who like basic versions of Emacs which need to be customized
|
|
|
8119 extensively for local use; standard Emacs distributions are better for
|
|
|
8120 such uses. InfoDock is for those people who want a complete,
|
|
|
8121 pre-customized environment in one package, which they need not touch
|
|
|
8122 more than once or twice a year to update to new revisions.
|
|
|
8123
|
|
|
8124 InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX,
|
|
|
8125 and Intel Linux systems. It is intended for use on a color display,
|
|
|
8126 although most features will work on monochrome monitors. Simply unpack
|
|
|
8127 InfoDock according to the instructions in the ID-INSTALL file and you
|
|
|
8128 are ready to run.
|
|
|
8129
|
|
|
8130 The InfoDock Manual is concise, yet sufficient as a user guide for users
|
|
|
8131 who have never used an Emacs-type editor before. For users who are
|
|
|
8132 already familiar with Emacs, it supplements the information in the GNU
|
|
|
8133 Emacs Manual.
|
|
|
8134
|
|
|
8135 InfoDock menus are much more extensive and more mature than standard
|
|
|
8136 Emacs menus. Each menu offers a @samp{Manual} item which displays
|
|
|
8137 documentation associated with the menu's functions.
|
|
|
8138
|
|
|
8139 @noindent
|
|
|
8140 Four types of menubars are provided:
|
|
|
8141 @enumerate
|
|
|
8142 @item
|
|
|
8143 An extensive menubar providing access to global InfoDock commands.
|
|
|
8144 @item
|
|
|
8145 Mode-specific menubars tailored to the current major mode.
|
|
|
8146 @item
|
|
|
8147 A simple menubar for basic editing to help novices get started with InfoDock.
|
|
|
8148 @item
|
|
|
8149 The standard XEmacs menubar.
|
|
|
8150 @end enumerate
|
|
|
8151
|
|
|
8152 Most modes also include mode-specific popup menus. Additionally, region and
|
|
|
8153 rectangle popup menus are included.
|
|
|
8154
|
|
|
8155 @samp{Hyperbole}, the everyday information manager, is a core part of
|
|
|
8156 InfoDock. This provides context-sensitive mouse keys, a rolodex-type
|
|
|
8157 contact manager, programmable hypertext buttons, and an autonumbered
|
|
|
8158 outliner with embedded hyperlink anchors.
|
|
|
8159
|
|
|
8160 The @samp{OO-Browser}, a multi-language object-oriented code browser, is a
|
|
|
8161 standard part of InfoDock.
|
|
|
8162
|
|
|
8163 InfoDock saves a more extensive set of user options than other Emacs
|
|
|
8164 versions.
|
|
|
8165
|
|
|
8166 InfoDock inserts a useful file header in many file types, showing the
|
|
|
8167 author, summary, and last modification time of each file. A summary
|
|
|
8168 program can then be used to summarize all of the files in a directory,
|
|
|
8169 for easy MANIFEST file creation.
|
|
|
8170
|
|
|
8171 Your working set of buffers is automatically saved and restored (if you
|
|
|
8172 answer yes to a prompt) between InfoDock sessions.
|
|
|
8173
|
|
|
8174 Refined color choices for code highlighting are provided for both dark and
|
|
|
8175 light background display frames.
|
|
|
8176
|
|
|
8177 The @kbd{C-z} key prefix performs frame-based commands which parallel the
|
|
|
8178 @kbd{C-x} key prefix for window-based commands.
|
|
|
8179
|
|
|
8180 The Smart Menu system is included for producing command menus on dumb
|
|
|
8181 terminals.
|
|
|
8182
|
|
|
8183 Lisp libraries are better categorized according to function.
|
|
|
8184
|
|
|
8185 Extensions and improvements to many areas of Emacs are included, such as:
|
|
|
8186 paragraph filling, mail reading with Rmail, shell handling, outlining, code
|
|
|
8187 highlighting and browsing, and man page browsing.
|
|
|
8188
|
|
|
8189 InfoDock questions, answers and discussion should go to the mail list
|
|
|
8190 @iftex
|
|
|
8191 @*
|
|
|
8192 @end iftex
|
|
|
8193 @email{infodock@@infodock.com}. Use
|
|
|
8194 @email{infodock-request@@infodock.com} to be added or removed from the
|
|
|
8195 list. Always include your InfoDock version number when sending help
|
|
|
8196 requests.
|
|
|
8197
|
|
2459
|
8198 @node Current Events, Legacy Versions, Other Packages, Top
|
|
|
8199 @unnumbered 9 What the Future Holds
|
|
|
8200
|
|
|
8201 This is part 9 of the XEmacs Frequently Asked Questions list. This
|
|
611
|
8202 section will change frequently, and (in theory) should contain any
|
|
|
8203 interesting items that have transpired recently. (But in practice it's
|
|
|
8204 not getting updated like this.)
|
|
|
8205
|
|
|
8206 This section also contains descriptions of the new features in all the
|
|
|
8207 recent releases of XEmacs. For the most part, the information below is
|
|
|
8208 a synopsis of the more complete information that can be found in the
|
|
|
8209 file @file{NEWS} in the @file{etc} directory of the XEmacs distribution.
|
|
|
8210 You can view this file in XEmacs using @kbd{C-h n} or the @samp{Help}
|
|
|
8211 menu.
|
|
|
8212
|
|
|
8213 Information on older versions of XEmacs can be find in @file{ONEWS} in
|
|
|
8214 the same directory, or @file{OONEWS} for really old versions.
|
|
|
8215
|
|
428
|
8216 @menu
|
|
2537
|
8217 9.0: Changes
|
|
2459
|
8218 * Q9.0.1:: What new features will be in XEmacs soon?
|
|
|
8219 * Q9.0.2:: What's new in XEmacs 21.4?
|
|
|
8220 * Q9.0.3:: What's new in XEmacs 21.1?
|
|
|
8221 * Q9.0.4:: What's new in XEmacs 20.4?
|
|
|
8222 * Q9.0.5:: What's new in XEmacs 20.3?
|
|
|
8223 * Q9.0.6:: What's new in XEmacs 20.2?
|
|
428
|
8224 @end menu
|
|
|
8225
|
|
2459
|
8226 @unnumberedsec 9.0: Changes
|
|
|
8227
|
|
|
8228 @node Q9.0.1, Q9.0.2, Current Events, Current Events
|
|
|
8229 @unnumberedsubsec Q9.0.1: What new features will be in XEmacs soon?
|
|
611
|
8230
|
|
2417
|
8231 #### Write me.
|
|
428
|
8232
|
|
2459
|
8233 @node Q9.0.2, Q9.0.3, Q9.0.1, Current Events
|
|
|
8234 @unnumberedsubsec Q9.0.2: What's new in XEmacs 21.4?
|
|
611
|
8235
|
|
|
8236 21.4 was the "stable" version of the 21.2 series, which was considered
|
|
|
8237 "experimental" throughout its life; thus there were no "official"
|
|
|
8238 releases at all. In essence, XEmacs is now following the "alternating"
|
|
|
8239 scheme of Linux, where at any point there are at least two different
|
|
|
8240 development branches, one "stable" and one "experimental". Periodic
|
|
|
8241 releases happen in both branches, but those in the experimental branch
|
|
|
8242 are not tested as well, and there's no guarantee they will work at all.
|
|
|
8243 The experiemental branch is open to any and all code that's acceptable
|
|
|
8244 to the developers; the stable branch, however, is in general limited
|
|
|
8245 only to bug fixes, and all contributions are carefully reviewed to make
|
|
|
8246 sure they will increase and not decrease stability.
|
|
|
8247
|
|
|
8248 21.3 never existed at all; it was decided to follow the Linux scheme
|
|
|
8249 exactly, where odd-numbered series are experimental and even-numbered
|
|
|
8250 ones stable.
|
|
|
8251
|
|
|
8252 The following lists summarizes the essential changes made in this
|
|
|
8253 version. For a fuller list, see the @file{NEWS} in the @file{etc}
|
|
|
8254 directory of the XEmacs distribution, or use @kbd{C-h n} or the
|
|
|
8255 @samp{Help} menu to view this file inside of XEmacs.
|
|
|
8256
|
|
676
|
8257 @unnumberedsubsubsec User-visible changes in XEmacs 21.4
|
|
611
|
8258
|
|
|
8259 @itemize @bullet
|
|
|
8260
|
|
|
8261 @item
|
|
|
8262 The delete key now deletes forward by default.
|
|
|
8263 @item
|
|
|
8264 Shifted motion keys now select text by default.
|
|
|
8265 @item
|
|
|
8266 You can now build XEmacs with support for GTK+ widget set.
|
|
|
8267 @item
|
|
|
8268 ~/.xemacs/init.el is now the preferred location for the init
|
|
|
8269 file. (XEmacs now supports a `~/.xemacs/init.el' startup file. Custom
|
|
|
8270 file will move to ~/.xemacs/custom.el.)
|
|
|
8271 @item
|
|
|
8272 Much-improved sample init.el, showing how to use many useful features.
|
|
|
8273 @item
|
|
|
8274 XEmacs support for menu accelerators has been much improved.
|
|
|
8275 @item
|
|
|
8276 Default menubar improvements. (Default menubar has many new commands and
|
|
|
8277 better organization. The font-menu is now available under MS Windows.)
|
|
|
8278 @item
|
|
2417
|
8279 Dialog box improvements, including a real file dialog box. (XEmacs now
|
|
|
8280 has a proper file dialog box under MS Windows (and GTK)! The old
|
|
|
8281 clunky file dialog box is improved. Keyboard traversal now works
|
|
|
8282 correctly in MS Windows dialog boxes. There is a Search dialog box
|
|
|
8283 available from @samp{Edit->Find...})
|
|
611
|
8284 @item
|
|
|
8285 New buffer tabs.
|
|
|
8286 @item
|
|
|
8287 There is a new MS Windows installer, netinstall, ported from Cygwin.
|
|
|
8288 @item
|
|
|
8289 The subprocess quote-handling mechanism under Windows is much improved.
|
|
|
8290 @item
|
|
|
8291 Printing support now available under MS Windows.
|
|
|
8292 @item
|
|
|
8293 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).)
|
|
|
8294 @item
|
|
|
8295 Mail spool locking now works correctly.
|
|
|
8296 @item
|
|
|
8297 International support changes. (The default coding-priority-list is now
|
|
|
8298 safer. International keysyms are now supported under X. MS Windows
|
|
|
8299 1251 code page now supported. Czech, Thai, Cyrillic-KOI8, Vietnamese,
|
|
|
8300 Ethiopic now supported. Proper support for words in Latin 3 and Latin
|
|
|
8301 4.)
|
|
|
8302 @item
|
|
|
8303 Help buffers contain hyperlinks, and other changes.
|
|
|
8304 @item
|
|
|
8305 The modeline's text is now scrollable.
|
|
|
8306 @item
|
|
|
8307 The mouse wheel under MS Windows now functions correctly.
|
|
|
8308 @item
|
|
|
8309 Interactive searching and matching case improvements. (Incremental search will now highlight all visible matches. Interactive searches always respect uppercase characters.)
|
|
|
8310 @item
|
|
|
8311 Rectangle functions rewritten to avoid inserting extra spaces.
|
|
|
8312 @item
|
|
|
8313 New command `kill-entire-line' that always kills the entire line.
|
|
|
8314 @item
|
|
|
8315 Default values correctly stored in minibuffer histories.
|
|
|
8316 @item
|
|
|
8317 You can now create "indirect buffers", like in GNU Emacs.
|
|
|
8318 @item
|
|
|
8319 Pixel-based scrolling has been implemented.
|
|
|
8320 @item
|
|
|
8321 Operation progress can be displayed using graphical widgets.
|
|
|
8322 @item
|
|
|
8323 User names following a tilde can now be completed at file name prompts.
|
|
|
8324 @item
|
|
|
8325 XEmacs can now play sound using Enlightenment Sound Daemon (ESD).
|
|
|
8326 @item
|
|
|
8327 X-Face support is now available under MS Windows.
|
|
|
8328 @item
|
|
|
8329 The PostgreSQL Relational Database Management System is now supported.
|
|
|
8330 @item
|
|
|
8331 Indentation no longer indents comments that begin at column zero.
|
|
|
8332 @item
|
|
|
8333 Face and variable settings can have comments in Customize.
|
|
|
8334 @item
|
|
|
8335 New locations for early package hierarchies.
|
|
|
8336 @item
|
|
|
8337 The `auto-save' library has been greatly improved.
|
|
|
8338 @item
|
|
|
8339 New variable `mswindows-alt-by-itself-activates-menu'.
|
|
|
8340 @item
|
|
|
8341 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.)
|
|
|
8342 @item
|
|
|
8343 Etags changes. See @file{NEWS} for full details.
|
|
|
8344 @end itemize
|
|
|
8345
|
|
676
|
8346 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.4
|
|
611
|
8347
|
|
|
8348 Not yet written.
|
|
|
8349
|
|
661
|
8350 @c APA: Texi2html produces invalid HTML from an empty list of bullets!
|
|
|
8351 @c Please uncomment following list when it does contain bullets.
|
|
|
8352 @c @itemize @bullet
|
|
|
8353 @c @end itemize
|
|
611
|
8354
|
|
2459
|
8355 @node Q9.0.3, Q9.0.4, Q9.0.2, Current Events
|
|
|
8356 @unnumberedsubsec Q9.0.3: What's new in XEmacs 21.1?
|
|
611
|
8357
|
|
|
8358 21.1 was the "stable" version of "experimental" 21.0 series.
|
|
2459
|
8359 @xref{Q9.0.2, What's new in XEmacs 21.4?}.
|
|
611
|
8360
|
|
|
8361 The following lists summarizes the essential changes made in this
|
|
|
8362 version. For a fuller list, see the @file{NEWS} in the @file{etc}
|
|
|
8363 directory of the XEmacs distribution, or use @kbd{C-h n} or the
|
|
|
8364 @samp{Help} menu to view this file inside of XEmacs.
|
|
|
8365
|
|
676
|
8366 @unnumberedsubsubsec User-visible changes in XEmacs 21.1
|
|
611
|
8367
|
|
|
8368 @itemize @bullet
|
|
|
8369
|
|
|
8370 @item
|
|
2459
|
8371 XEmacs is now supported under Microsoft Windows 95/98 and Windows
|
|
2417
|
8372 NT/2000/XP operating systems. To discuss Windows-specific issues,
|
|
|
8373 subscribe to the mailing list at
|
|
|
8374 @email{xemacs-winnt-request@@xemacs.org}.
|
|
611
|
8375
|
|
|
8376 @item
|
|
|
8377 XEmacs has been unbundled into constituent installable packages.
|
|
|
8378
|
|
|
8379 @item
|
|
|
8380 @strong{Other notable changes}: The @samp{Options} menu has been ported to
|
|
|
8381 Custom; XEmacs now is able to choose X visuals and use private
|
|
|
8382 colormaps; You can drag the vertical divider of "horizontally"
|
|
|
8383 (side-by-side) split windows.
|
|
|
8384
|
|
|
8385 @item
|
|
|
8386 @strong{Building changes}: XEmacs can be built with support for 31-bit Lisp
|
|
|
8387 integers and 32-bit pointers (previously, it was 28-bit integers and
|
|
|
8388 pointers); XEmacs can be built with LDAP support; @file{dir} files can be
|
|
|
8389 removed in the Info subsystem, and will be regenerated on-the-fly.
|
|
|
8390
|
|
|
8391 @item
|
|
|
8392 @strong{New packages}: @file{imenu}, @file{popper}, @file{gdb-highlight}
|
|
|
8393
|
|
|
8394 @item
|
|
|
8395 @strong{Package changes}: Many changes to @file{cc-mode}, @file{gnus},
|
|
|
8396 @file{gnuclient}. See @file{NEWS} for full details.
|
|
|
8397
|
|
|
8398 @item
|
|
|
8399 @strong{New commands, variables and functions}:
|
|
|
8400 @code{center-to-window-line} (like @code{recenter} but doesn't force a
|
|
|
8401 redisplay); variable @code{user-full-name} (customize what your full
|
|
|
8402 name looks like in mail); @kbd{M-x customize-changed-options} (customize
|
|
|
8403 options whose default values changes because you upgraded your XEmacs);
|
|
|
8404 @kbd{M-x add-log-convert} (converts an old-style ChangeLog buffer to
|
|
|
8405 new-style); @kbd{M-x zap-up-to-char} (like @code{zap-to-char} but
|
|
|
8406 doesn't delete the char searched for); commands to store, retrieve and
|
|
|
8407 increment numbers in registers, useful for macros.
|
|
|
8408
|
|
|
8409 @item
|
|
|
8410 @strong{Changes to commands, variables, and functions}: @kbd{M-x
|
|
|
8411 query-replace} and friends operate only on the region when it's active;
|
|
|
8412 @code{echo-keystrokes} can now be a floating-point number; @kbd{M-.}
|
|
|
8413 searches exact tag matches before inexact ones; function
|
|
|
8414 @code{user-full-name} with no arguments returns the var
|
|
|
8415 @code{user-full-name}; a prefix arg to @kbd{M-:} and @kbd{C-h c} inserts
|
|
|
8416 the result in the current buffer.
|
|
1138
|
8417
|
|
611
|
8418 @item
|
|
|
8419 @strong{Other changes}: Under X, new application class @samp{XEmacs};
|
|
|
8420 byte-compilation of user-specs now works.
|
|
|
8421
|
|
|
8422 @item
|
|
|
8423 @strong{XEmacs/Mule (internationalization) changes}: Mule support now
|
|
|
8424 works on TTY's; Egg/SJ3 input method now officially supported (Quail and
|
|
|
8425 Egg/Skk already available through LEIM since 20.3); localized Japanese
|
|
|
8426 menubars if XEmacs is built with the right support.
|
|
|
8427
|
|
|
8428 @end itemize
|
|
|
8429
|
|
676
|
8430 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.1
|
|
611
|
8431
|
|
|
8432 @itemize @bullet
|
|
|
8433
|
|
|
8434 @item
|
|
|
8435 @strong{Specifier changes}: The window locale now has a higher
|
|
|
8436 precedence than the buffer locale when instantiating; new macro
|
|
|
8437 @code{let-specifier}; new specifiers
|
|
|
8438 @code{vertical-scrollbar-visible-p}, horizontal-scrollbar-visible-p',
|
|
|
8439 @code{scrollbar-on-left-p}, @code{scrollbar-on-top-p},
|
|
|
8440 @code{vertical-divider-always-visible-p},
|
|
|
8441 @code{vertical-divider-shadow-thickness},
|
|
|
8442 @code{vertical-divider-line-width}, @code{vertical-divider-spacing};
|
|
|
8443 specifiers and symbols whose value is a specifier allowed as modeline
|
|
|
8444 specifications.
|
|
|
8445
|
|
|
8446 @item
|
|
|
8447 @strong{Frame focus changes}: @code{focus-follows-mouse} works like FSF,
|
|
|
8448 prevents any attempt to permanently change the selected frame; new
|
|
|
8449 function @code{focus-frame} sets the window system focus a frame; new
|
|
|
8450 special forms @code{save-selected-frame} and @code{with-selected-frame}.
|
|
|
8451
|
|
|
8452 @item
|
|
|
8453 @strong{Window function changes}: @code{select-window} now has optional
|
|
|
8454 argument @var{NORECORD} to inhibit recording a buffer change;
|
|
|
8455 @code{vertical-motion} now correctly handles optional @var{WINDOW}
|
|
|
8456 argument and has new optional argument @var{PIXELS}, to have the
|
|
|
8457 returned values be in pixels; new function
|
|
|
8458 @code{vertical-motion-pixels}; new functions
|
|
|
8459 @code{window-text-area-pixel-@{width,height,edges@}}; new functions
|
|
|
8460 @code{shrink-window-pixels} and @code{enlarge-window-pixels}; new
|
|
|
8461 function @code{window-displayed-text-pixel-height}.
|
|
|
8462
|
|
|
8463 @item
|
|
|
8464 @strong{Other function changes}: Arithmetic comparison functions
|
|
|
8465 @code{<}, @code{>}, @code{=}, @code{/=} now accept a variable number of
|
|
|
8466 arguments; hashtables now have a consistent read/print syntax; keyword
|
|
|
8467 symbols cannot be set to a value other than themselves; @code{concat} no
|
|
|
8468 longer accepts integer arguments; new function @code{string}, like
|
|
|
8469 @code{list}, @code{vector}, etc.; new function @code{temp-directory}
|
|
|
8470 (OS-independent way to get a temp directory); @code{load-average} has
|
|
|
8471 optional argument @var{USE-FLOATS}; @code{make-event} implemented
|
|
|
8472 completely; new function @code{function-interactive} (returns a
|
|
|
8473 function's interactive spec); new functions @code{lmessage},
|
|
|
8474 @code{lwarn} (printf-like versions of @code{display-wessage},
|
|
|
8475 @code{display-warning}); new keyword @code{:version} to
|
|
|
8476 @code{defcustom}.
|
|
|
8477
|
|
|
8478 @item
|
|
|
8479 @strong{Performance}: when the new GNU Malloc aka Doug Lea Malloc is
|
|
|
8480 available, it will be used (better performance on libc6 Linux systems);
|
|
|
8481 tracking line-numbers in modeline is now efficient; profiling records a
|
|
|
8482 call-count of all called functions, retrievable through
|
|
|
8483 @code{profile-call-count-results}.
|
|
|
8484
|
|
|
8485 @item
|
|
|
8486 @strong{Startup and path searching}: code to assemble paths at startup
|
|
|
8487 rewritten for new package system; new function @code{split-path} (splits
|
|
|
8488 by @code{path-separator}); @code{Info-default-directory-list} obsolete,
|
|
|
8489 use @code{Info-directory-list} instead; site-lisp is deprecated and no
|
|
|
8490 longer on the load-path by default.
|
|
|
8491
|
|
|
8492 @end itemize
|
|
|
8493
|
|
2459
|
8494 @node Q9.0.4, Q9.0.5, Q9.0.3, Current Events
|
|
|
8495 @unnumberedsubsec Q9.0.4: What's new in XEmacs 20.4?
|
|
611
|
8496
|
|
|
8497 XEmacs 20.4 is a bugfix release with no user-visible changes.
|
|
|
8498 @c Filled in from NEWS file of 20.5-b33
|
|
|
8499
|
|
2459
|
8500 @node Q9.0.5, Q9.0.6, Q9.0.4, Current Events
|
|
|
8501 @unnumberedsubsec Q9.0.5: What's new in XEmacs 20.3?
|
|
428
|
8502
|
|
|
8503 XEmacs 20.3 was released in November 1997. It contains many bugfixes,
|
|
|
8504 and a number of new features, including Autoconf 2 based configuration,
|
|
|
8505 additional support for Mule (Multi-language extensions to Emacs), many
|
|
|
8506 more customizations, multiple frames on TTY-s, support for multiple info
|
|
|
8507 directories, an enhanced gnuclient, improvements to regexp matching,
|
|
|
8508 increased MIME support, and many, many synches with GNU Emacs 20.
|
|
|
8509
|
|
|
8510 The XEmacs/Mule support has been only seriously tested in a Japanese
|
|
|
8511 locale, and no doubt many problems still remain. The support for
|
|
|
8512 ISO-Latin-1 and Japanese is fairly strong. MULE support comes at a
|
|
440
|
8513 price---about a 30% slowdown from 19.16. We're making progress on
|
|
428
|
8514 improving performance and XEmacs 20.3 compiled without Mule (which is
|
|
|
8515 the default) is definitely faster than XEmacs 19.16.
|
|
|
8516
|
|
|
8517 XEmacs 20.3 is the first non-beta v20 release, and will be the
|
|
|
8518 basis for all further development.
|
|
|
8519
|
|
2459
|
8520 @node Q9.0.6, , Q9.0.5, Current Events
|
|
|
8521 @unnumberedsubsec Q9.0.6: What's new in XEmacs 20.2?
|
|
611
|
8522
|
|
|
8523 The biggest changes in 20.2 include integration of EFS (the next
|
|
|
8524 generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a
|
|
|
8525 major mode for editing Tex and LaTeX, and a lot of other stuff). Many
|
|
|
8526 bugs from 20.0 have been fixed for this release. 20.2 also contains a
|
|
|
8527 new system for customizing XEmacs options, invoked via @kbd{M-x
|
|
|
8528 customize}.
|
|
|
8529
|
|
|
8530 XEmacs 20.2 is the development release (20.0 was beta), and is no longer
|
|
|
8531 considered unstable.
|
|
|
8532
|
|
|
8533 For older news, see the file @file{ONEWS} in the @file{etc} directory of
|
|
|
8534 the XEmacs distribution.
|
|
428
|
8535
|
|
2417
|
8536 @node Legacy Versions, , Current Events, Top
|
|
2459
|
8537 @unnumbered 10 New information about old XEmacsen
|
|
|
8538
|
|
|
8539 This is part 10 of the XEmacs Frequently Asked Questions list. It will
|
|
1495
|
8540 occasionally be updated to reflect new information about versions which
|
|
|
8541 are no longer being revised by the XEmacs Project. The primary purpose
|
|
|
8542 is advice on compatibility of older XEmacsen with new packages and
|
|
|
8543 updated versions of packages, but bug fixes (which will not be applied
|
|
|
8544 to released XEmacsen, but users can apply themselves) are also accepted.
|
|
|
8545
|
|
|
8546 @menu
|
|
2537
|
8547 10.0: XEmacs 21.1
|
|
2459
|
8548 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
2559
|
8549 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1.
|
|
1495
|
8550 @end menu
|
|
|
8551
|
|
2459
|
8552 @unnumberedsec 10.0: XEmacs 21.1
|
|
|
8553
|
|
2559
|
8554 @node Q10.0.1, Q10.0.2, Legacy Versions, Legacy Versions
|
|
2459
|
8555 @unnumberedsubsec Q10.0.1: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
1495
|
8556
|
|
|
8557 @email{eeide@@cs.utah.edu, Eric Eide} wrote:
|
|
|
8558
|
|
|
8559 @quotation
|
|
|
8560 Previously I wrote:
|
|
|
8561
|
|
|
8562 Eric> Summary: with Gnus 5.10.1 in XEmacs 21.1.14, I don't see
|
|
|
8563 Eric> any smileys :-(.
|
|
|
8564
|
|
|
8565 After a bit of sleuthing, I discovered the essence of the problem.
|
|
|
8566 For me, the form:
|
|
|
8567
|
|
|
8568 @lisp
|
|
|
8569 (with-temp-buffer
|
|
|
8570 (insert-file-contents "foo.xpm")
|
|
|
8571 (buffer-string))
|
|
|
8572 @end lisp
|
|
|
8573
|
|
|
8574 returns the empty string. This is because something somewhere
|
|
|
8575 replaces the XPM data with a glyph --- I haven't figured out where
|
|
|
8576 this occurs.
|
|
|
8577 @end quotation
|
|
|
8578
|
|
|
8579 @email{kyle_jones@@wonderworks.com, Kyle Jones} replies:
|
|
|
8580
|
|
|
8581 @quotation
|
|
|
8582 Do this:
|
|
|
8583
|
|
|
8584 @lisp
|
|
|
8585 (setq format-alist nil)
|
|
|
8586 @end lisp
|
|
|
8587
|
|
|
8588 The image-mode stuff is gone from format-alist in the 21.4
|
|
|
8589 branch, praise be.
|
|
|
8590 @end quotation
|
|
|
8591
|
|
2559
|
8592 @node Q10.0.2, , Q10.0.1, Legacy Versions
|
|
|
8593 @unnumberedsubsec Q10.0.2: XEmacs won't start on Windows in XEmacs 21.1.
|
|
|
8594
|
|
|
8595 XEmacs relies on a process called "dumping" to generate a working
|
|
|
8596 executable. Under MS-Windows this process effectively fixes the memory
|
|
|
8597 addresses of information in the executable. When XEmacs starts up it tries
|
|
|
8598 to reserve these memory addresses so that the dumping process can be
|
|
|
8599 reversed -- putting the information back at the correct addresses.
|
|
|
8600 Unfortunately some .DLLs (for instance the soundblaster driver) occupy
|
|
|
8601 memory addresses that can conflict with those needed by the dumped XEmacs
|
|
|
8602 executable. In this instance XEmacs will fail to start without any
|
|
|
8603 explanation. Note that this is extremely machine specific.
|
|
|
8604
|
|
|
8605 21.1.10 includes a fix for this that makes more intelligent guesses
|
|
|
8606 about which memory addresses will be free, and this should cure the
|
|
|
8607 problem for most people. 21.4 implements "portable dumping", which
|
|
|
8608 eliminates the problem altogether. We recommend you use the 21.4
|
|
|
8609 binaries, but you can use the 21.1 binaries if you are very paranoid
|
|
|
8610 about stability. @xref{Q1.1.2, Are binaries available?}.
|
|
|
8611
|
|
428
|
8612 @bye
|
