|
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
|
|
2459
|
10 @subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2004/12/29 05:08:26 $
|
|
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
|
|
|
58 1. Use the Lisp line below to get the spacing correct for the Q#.#.#
|
|
|
59 menu entries.
|
|
|
60
|
|
|
61 (set (make-local-variable 'texinfo-column-for-description) 14)
|
|
|
62
|
|
|
63 2. C-u C-c C-u m (C-u M-x texinfo-master-menu) will update the menus
|
|
|
64 and nodes. However, it appears that even though it tries to
|
|
|
65 preserve the existing menu structure as much as possible, it
|
|
|
66 doesn't do a perfect job. It messes up in at least two ways: The
|
|
|
67 indentation in the part of the main menu above the detailmenu will
|
|
|
68 be screwed up, and the #.0 titles will be removed from both the
|
|
|
69 detailmenu and the individual chapter menus. In addition,
|
|
|
70 sometimes random things get screwed up in individual parts of the
|
|
|
71 menus. Therefore:
|
|
|
72
|
|
|
73 1. Copy the whole detailmenu beforehand.
|
|
|
74 2. Run C-u C-C C-u m to fix up the nodes.
|
|
|
75 3. Run `fix-main-menu' and `fix-omitted-menu-lines'.
|
|
|
76 4. Check the new detailmenu carefully to see if anything is screwed up
|
|
|
77 compared to the old detailmenu you copied.
|
|
|
78 5. If so, paste back the appropriate sections and fix up the corresponding
|
|
|
79 part of the chapter-specific menu.
|
|
|
80
|
|
|
81 (defun fix-main-menu ()
|
|
|
82 (interactive)
|
|
|
83 (save-restriction
|
|
|
84 (let (p q)
|
|
|
85 (search-forward "@menu")
|
|
|
86 (setq p (match-beginning 0))
|
|
|
87 (re-search-forward "^$")
|
|
|
88 (setq q (match-end 0))
|
|
|
89 (narrow-to-region p q)
|
|
|
90 (goto-char p)
|
|
|
91 (while (search-forward ":: " nil t)
|
|
|
92 (indent-to-column 26)))))
|
|
|
93
|
|
|
94 (defun fix-omitted-menu-lines ()
|
|
|
95 (interactive)
|
|
|
96 (save-excursion
|
|
|
97 (loop for x from 1 to 7 do
|
|
|
98 (goto-char (point-min))
|
|
|
99 (re-search-forward (format "@unnumberedsec \\(%d.0: .*\\)" x))
|
|
|
100 (let ((line (match-string 1)))
|
|
|
101 (search-backward "@menu")
|
|
|
102 (forward-line 1)
|
|
|
103 (unless (looking-at "[0-9].0:")
|
|
|
104 (insert line)
|
|
|
105 (insert "\n"))
|
|
|
106 (goto-char (point-min))
|
|
|
107 (search-forward "@menu")
|
|
|
108 (search-forward (format "Q%d.0.1:" x))
|
|
|
109 (forward-line -1)
|
|
|
110 (unless (looking-at "[0-9].0:")
|
|
|
111 (insert line)
|
|
|
112 (insert "\n"))))))
|
|
|
113
|
|
|
114 *****************************************
|
|
|
115 ***** Other work *****
|
|
|
116 *****************************************
|
|
|
117
|
|
|
118 When you've rearranged and renumbered a bunch of nodes, you can get
|
|
|
119 the numbers agreeing again. The macro below assumes that the
|
|
|
120 unnumberedsubsec number is correct, and fixes up the node to agree.
|
|
|
121 Only the first part of the node is fixed and the other parts may still
|
|
|
122 be wrong; but they will be fixed as part of
|
|
|
123 @code{texinfo-master-menu}.
|
|
|
124
|
|
|
125 (setq last-kbd-macro (read-kbd-macro
|
|
|
126 "<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>"))
|
|
|
127 @end ignore
|
|
|
128
|
|
|
129
|
|
428
|
130 @node Top, Introduction, (dir), (dir)
|
|
|
131 @top XEmacs FAQ
|
|
|
132
|
|
|
133 This is the guide to the XEmacs Frequently Asked Questions list---a
|
|
|
134 compendium of questions and answers pertaining to one of the finest
|
|
442
|
135 programs ever written. XEmacs is much more than just a Text Editor.
|
|
|
136
|
|
|
137 This FAQ is freely redistributable. This FAQ is distributed in the hope
|
|
|
138 that it will be useful, but WITHOUT ANY WARRANTY; without even the
|
|
|
139 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
|
428
|
140
|
|
|
141 If you have a Web browser, the official hypertext version is at
|
|
|
142 @iftex
|
|
|
143 @*
|
|
|
144 @end iftex
|
|
1143
|
145 @uref{http://www.xemacs.org/FAQ/xemacs-faq.html}
|
|
428
|
146
|
|
|
147 @ifset CANONICAL
|
|
|
148 @html
|
|
|
149 This document is available in several different formats:
|
|
|
150 @itemize @bullet
|
|
|
151 @item
|
|
|
152 @uref{xemacs-faq.txt, As a single ASCII file}, produced by
|
|
|
153 @code{makeinfo --no-headers}
|
|
|
154 @item
|
|
|
155 @uref{xemacs-faq.dvi, As a .dvi file}, as used with
|
|
|
156 @uref{http://www.tug.org, TeX.}
|
|
|
157 @item
|
|
|
158 As a PostScript file @uref{xemacs-faq-a4.ps, in A4 format},
|
|
|
159 as well as in @uref{xemacs-faq-letter.ps, letter format}
|
|
|
160 @item
|
|
|
161 In html format, @uref{xemacs-faq_1.html, split by chapter}, or in
|
|
|
162 @uref{xemacs-faq.html, one monolithic} document.
|
|
|
163 @item
|
|
|
164 The canonical version of the FAQ is the texinfo document
|
|
|
165 @uref{xemacs-faq.texi, man/xemacs-faq.texi}.
|
|
|
166 @item
|
|
|
167 If you do not have makeinfo installed, you may @uref{xemacs-faq.info,
|
|
|
168 download the faq} in info format, and install it in @file{<XEmacs
|
|
|
169 library directory>/info/}. For example in
|
|
462
|
170 @file{/usr/local/lib/xemacs-21.4/info/}.
|
|
428
|
171
|
|
|
172 @end itemize
|
|
|
173
|
|
|
174 @end html
|
|
|
175
|
|
|
176 @end ifset
|
|
|
177
|
|
|
178 @c end ifset points to CANONICAL
|
|
|
179
|
|
|
180 @menu
|
|
2417
|
181 * Introduction:: Introduction, Policy, Credits.
|
|
|
182 * Installation:: Installation and Troubleshooting.
|
|
2459
|
183 * Editing:: Editing Functions.
|
|
|
184 * Display:: Display Functions.
|
|
2417
|
185 * External Subsystems:: Interfacing with the OS and External Devices.
|
|
|
186 * Internet:: Connecting to the Internet.
|
|
|
187 * Advanced:: Advanced Customization Using XEmacs Lisp.
|
|
2459
|
188 * Other Packages:: Other External Packages.
|
|
2417
|
189 * Current Events:: What the Future Holds.
|
|
|
190 * Legacy Versions:: New information about old XEmacsen.
|
|
428
|
191
|
|
|
192 @detailmenu
|
|
|
193 --- The Detailed Node Listing ---
|
|
|
194
|
|
2417
|
195 1 Introduction, Policy, Credits
|
|
|
196
|
|
|
197 1.0: Introduction
|
|
|
198 * Q1.0.1:: What is XEmacs?
|
|
|
199 * Q1.0.2:: What is the current version of XEmacs?
|
|
|
200 * Q1.0.3:: Where can I find it?
|
|
|
201 * Q1.0.4:: Are binaries available?
|
|
|
202 * Q1.0.5:: How does XEmacs differ from GNU Emacs?
|
|
|
203 * Q1.0.6:: How much does XEmacs differ?
|
|
|
204 * Q1.0.7:: Is XEmacs "GNU"?
|
|
|
205 * Q1.0.8:: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
|
206 * Q1.0.9:: Why haven't XEmacs and GNU Emacs merged?
|
|
|
207 * Q1.0.10:: Where can I get help?
|
|
|
208 * Q1.0.11:: Where are the mailing lists archived?
|
|
|
209 * Q1.0.12:: How do you pronounce XEmacs?
|
|
|
210 * Q1.0.13:: What does XEmacs look like?
|
|
|
211 * Q1.0.14:: Where can I obtain a printed copy of the XEmacs User's Manual?
|
|
|
212
|
|
|
213 1.1: Versions for Different Operating Systems
|
|
|
214 * Q1.1.1:: Do I need X11 to run XEmacs?
|
|
|
215 * Q1.1.2:: Is there a port of XEmacs to Microsoft Windows?
|
|
|
216 * Q1.1.3:: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
217 * Q1.1.4:: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
218 * Q1.1.5:: What are the differences between the various MS Windows emacsen?
|
|
|
219 * Q1.1.6:: Is there a port of XEmacs to the Macintosh?
|
|
|
220 * Q1.1.7:: Is there a port of XEmacs to NextStep?
|
|
|
221 * Q1.1.8:: Is there a port of XEmacs to OS/2?
|
|
|
222 * Q1.1.9:: How does the port cope with differences in the Windows user interface?
|
|
|
223
|
|
|
224 1.2: Policies
|
|
|
225 * Q1.2.1:: What is the FAQ editorial policy?
|
|
|
226 * Q1.2.2:: How do I become a beta tester?
|
|
|
227 * Q1.2.3:: How do I contribute to XEmacs itself?
|
|
|
228
|
|
|
229 1.3: Credits
|
|
|
230 * Q1.3.1:: Who wrote XEmacs?
|
|
|
231 * Q1.3.2:: Who contributed to this version of the FAQ?
|
|
|
232 * Q1.3.3:: Who contributed to the FAQ in the past?
|
|
|
233
|
|
|
234 1.4: Internationalization
|
|
2459
|
235 * Q1.4.1:: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
2417
|
236 * Q1.4.2:: How can I help with internationalization?
|
|
|
237 * Q1.4.3:: How do I type non-ASCII characters?
|
|
|
238 * Q1.4.4:: Can XEmacs messages come out in a different language?
|
|
|
239 * Q1.4.5:: Please explain the various input methods in MULE/XEmacs
|
|
|
240 * Q1.4.6:: How do I portably code for MULE/XEmacs?
|
|
|
241 * Q1.4.7:: How about Cyrillic modes?
|
|
|
242 * Q1.4.8:: Does XEmacs support Unicode?
|
|
|
243 * Q1.4.9:: How does XEmacs display Unicode?
|
|
|
244
|
|
|
245 1.5: Getting Started
|
|
|
246 * Q1.5.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
|
247 * Q1.5.2:: Where do I put my @file{init.el} file?
|
|
|
248 * Q1.5.3:: Can I use the same @file{init.el} with the other Emacs?
|
|
|
249 * Q1.5.4:: Any good XEmacs tutorials around?
|
|
|
250 * Q1.5.5:: May I see an example of a useful XEmacs Lisp function?
|
|
|
251 * Q1.5.6:: And how do I bind it to a key?
|
|
|
252 * Q1.5.7:: What's the difference between a macro and a function?
|
|
|
253 * Q1.5.8:: What is @code{Custom}?
|
|
|
254
|
|
|
255 2 Installation and Troubleshooting
|
|
|
256
|
|
|
257 2.0: Installation (General), Packages
|
|
|
258 * Q2.0.1:: How do I install the packages?
|
|
|
259 * Q2.0.2:: I don't need no steenkin' packages. Do I?
|
|
|
260 * Q2.0.3:: Where do I find external libraries?
|
|
|
261 * Q2.0.4:: How do I specify the paths that XEmacs uses for finding files?
|
|
|
262 * Q2.0.5:: Running XEmacs without installing
|
|
|
263 * Q2.0.6:: XEmacs is too big
|
|
|
264 * Q2.0.7:: EFS fails with "500 AUTH not understood" (NEW)
|
|
|
265
|
|
2459
|
266 2.1: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
2417
|
267 * Q2.1.1:: Libraries in non-standard locations
|
|
|
268 * Q2.1.2:: Why can't I strip XEmacs?
|
|
|
269
|
|
|
270 2.2: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
271 * Q2.2.1:: What exactly are all the different ways to build XEmacs under Windows?
|
|
|
272 * Q2.2.2:: What compiler/libraries do I need to compile XEmacs?
|
|
|
273 * Q2.2.3:: How do I compile the native port?
|
|
|
274 * Q2.2.4:: What do I need for Cygwin?
|
|
|
275 * Q2.2.5:: How do I compile under Cygwin?
|
|
|
276 * Q2.2.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
|
277 * Q2.2.7:: How do I compile with X support?
|
|
|
278 * Q2.2.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
|
279
|
|
|
280 2.3: General Troubleshooting
|
|
|
281 * Q2.3.1:: Help! XEmacs just crashed on me!
|
|
|
282 * Q2.3.2:: XEmacs crashes and I compiled it myself.
|
|
|
283 * Q2.3.3:: How to debug an XEmacs problem with a debugger
|
|
|
284 * Q2.3.4:: I get a cryptic error message when trying to do something.
|
|
|
285 * Q2.3.5:: XEmacs hangs when I try to do something.
|
|
|
286 * Q2.3.6:: I get an error message when XEmacs is running in batch mode.
|
|
|
287 * Q2.3.7:: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
|
288 * Q2.3.8:: @kbd{C-g} doesn't work for me. Is it broken?
|
|
|
289 * Q2.3.9:: How do I debug process-related problems?
|
|
|
290 * Q2.3.10:: XEmacs is outputting lots of X errors.
|
|
|
291 * Q2.3.11:: After upgrading, XEmacs won't do `foo' any more!
|
|
|
292
|
|
|
293 2.4: Startup-Related Problems
|
|
|
294 * Q2.4.1:: XEmacs cannot connect to my X Terminal!
|
|
|
295 * Q2.4.2:: XEmacs won't start on Windows.
|
|
|
296 * Q2.4.3:: XEmacs won't start without network.
|
|
|
297 * Q2.4.4:: Startup warnings about deducing proper fonts?
|
|
|
298 * Q2.4.5:: Warnings from incorrect key modifiers.
|
|
|
299 * Q2.4.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
|
300
|
|
2459
|
301 3 Editing Functions
|
|
2417
|
302
|
|
|
303 3.0: The Keyboard
|
|
2459
|
304 * Q3.0.1:: How can I customize the keyboard?
|
|
|
305 * Q3.0.2:: How can I bind complex functions (or macros) to keys?
|
|
|
306 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down?
|
|
|
307 * Q3.0.4:: Globally binding @kbd{Delete}?
|
|
|
308 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
|
309 * Q3.0.6:: How can you type in special characters in XEmacs?
|
|
|
310 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys?
|
|
|
311 * Q3.0.8:: How do I map the arrow keys?
|
|
|
312 * Q3.0.9:: HP Alt key as Meta.
|
|
|
313 * Q3.0.10:: Why does edt emulation not work?
|
|
|
314 * Q3.0.11:: How can I emulate VI and use it as my default mode?
|
|
2417
|
315
|
|
|
316 3.1: The Mouse
|
|
|
317 * Q3.1.1:: How can I turn off Mouse pasting?
|
|
|
318 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons?
|
|
|
319 * Q3.1.3:: Clicking the left button does not do anything in buffer list.
|
|
|
320 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3?
|
|
2459
|
321 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
|
322
|
|
|
323 3.2: Buffers, Text Editing
|
|
|
324 * Q3.2.1:: Can I have the end of the buffer delimited in some way?
|
|
|
325 * Q3.2.2:: How do I insert today's date into a buffer?
|
|
|
326 * Q3.2.3:: How do I get a single minibuffer frame?
|
|
|
327 * Q3.2.4:: How can I enable auto-indent and/or Filladapt?
|
|
|
328 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
329
|
|
|
330 3.3: Text Selections
|
|
|
331 * Q3.3.1:: How do I select a rectangular region?
|
|
|
332 * Q3.3.2:: How can I turn off or change highlighted selections?
|
|
|
333 * Q3.3.3:: How do I cause typing on an active region to remove it?
|
|
|
334 * Q3.3.4:: Can I turn off the highlight during isearch?
|
|
|
335 * Q3.3.5:: Why is killing so slow?
|
|
|
336 * Q3.3.6:: Why does @kbd{M-w} take so long?
|
|
|
337
|
|
|
338 3.4: Editing Source Code
|
|
|
339 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode?
|
|
|
340 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly?
|
|
|
341
|
|
|
342 4 Display Functions
|
|
|
343
|
|
|
344 4.0: Textual Fonts and Colors
|
|
|
345 * Q4.0.1:: How do I specify a font?
|
|
|
346 * Q4.0.2:: How do I set the text, menu and modeline fonts?
|
|
|
347 * Q4.0.3:: How can I set color options from @file{init.el}?
|
|
|
348 * Q4.0.4:: How can I set the colors when highlighting a region?
|
|
|
349 * Q4.0.5:: How can I limit color map usage?
|
|
|
350 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them.
|
|
|
351 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs?
|
|
|
352 * Q4.0.8:: How do I display non-ASCII characters?
|
|
|
353 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}.
|
|
|
354
|
|
|
355 4.1: Syntax Highlighting (Font Lock)
|
|
|
356 * Q4.1.1:: How can I do source code highlighting using font-lock?
|
|
|
357 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
358
|
|
|
359 4.2: The Modeline
|
|
|
360 * Q4.2.1:: How can I make the modeline go away?
|
|
|
361 * Q4.2.2:: How do you have XEmacs display the line number in the modeline?
|
|
|
362 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline?
|
|
|
363 * Q4.2.4:: How can I change the modeline color based on the mode used?
|
|
|
364
|
|
|
365 4.3: The Cursor
|
|
|
366 * Q4.3.1:: Is there a way to make the bar cursor thicker?
|
|
|
367 * Q4.3.2:: Is there a way to get back the block cursor?
|
|
|
368 * Q4.3.3:: Can I make the cursor blink?
|
|
|
369
|
|
|
370 4.4: The Menubar
|
|
|
371 * Q4.4.1:: How do I get rid of the menubar?
|
|
|
372 * Q4.4.2:: How can I customize the menubar?
|
|
|
373 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
374 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
375 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
376
|
|
|
377 4.5: The Toolbar
|
|
|
378 * Q4.5.1:: How do I get rid of the toolbar?
|
|
|
379 * Q4.5.2:: How can I customize the toolbar?
|
|
|
380 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar?
|
|
|
381 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar
|
|
|
382
|
|
|
383 4.6: Scrollbars and Scrolling
|
|
|
384 * Q4.6.1:: How can I disable the scrollbar?
|
|
|
385 * Q4.6.2:: How can I change the scrollbar width?
|
|
|
386 * Q4.6.3:: How can I use resources to change scrollbar colors?
|
|
|
387 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this?
|
|
|
388 * Q4.6.5:: Scrolling one line at a time.
|
|
|
389 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
390 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
391
|
|
|
392 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
393 * Q4.7.1:: How can I disable the gutter tabs?
|
|
|
394 * Q4.7.2:: How can I disable the progress bar?
|
|
|
395 * Q4.7.3:: There are bugs in the gutter or widgets.
|
|
|
396 * Q4.7.4:: How can I customize the gutter or gutter tabs?
|
|
|
397
|
|
|
398 5 Interfacing with the Operating System and External Devices
|
|
|
399
|
|
|
400 5.0: X Window System and Resources
|
|
|
401 * Q5.0.1:: Where is a list of X resources?
|
|
|
402 * Q5.0.2:: How can I detect a color display?
|
|
|
403 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}?
|
|
|
404 * Q5.0.4:: How can I have the window title area display the full path?
|
|
|
405 * Q5.0.5:: @samp{xemacs -name junk} doesn't work?
|
|
|
406 * Q5.0.6:: @samp{-iconic} doesn't work.
|
|
|
407
|
|
|
408 5.1: Microsoft Windows
|
|
|
409 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
|
410 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
|
411
|
|
|
412 5.2: Printing
|
|
|
413 * Q5.2.1:: What do I need to change to make printing work?
|
|
|
414 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer?
|
|
|
415 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
|
416 * Q5.2.4:: Can you print under MS Windows?
|
|
|
417
|
|
|
418 5.3: Sound
|
|
|
419 * Q5.3.1:: How do I turn off the sound?
|
|
|
420 * Q5.3.2:: How do I get funky sounds instead of a boring beep?
|
|
|
421 * Q5.3.3:: What are NAS and ESD (EsounD)?
|
|
|
422 * Q5.3.4:: Sunsite sounds don't play.
|
|
|
423
|
|
|
424 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
425 * Q5.4.1:: What is an interior shell?
|
|
|
426 * Q5.4.2:: How do I start up a second shell buffer?
|
|
|
427 * Q5.4.3:: Telnet from shell filters too much
|
|
|
428 * Q5.4.4:: Strange things are happening in Shell Mode.
|
|
|
429 * Q5.4.5:: XEmacs complains "No such file or directory, diff"
|
|
|
430
|
|
|
431 5.5: Multiple Device Support
|
|
|
432 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display?
|
|
|
433 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
434 * Q5.5.3:: How do I disable gnuserv from opening a new frame?
|
|
|
435 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
|
436 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
|
437
|
|
|
438 6 Connecting to the Internet
|
|
|
439
|
|
|
440 6.0: General Mail and News
|
|
|
441 * Q6.0.1:: What are the various packages for reading mail?
|
|
|
442 * Q6.0.2:: How can I send mail?
|
|
|
443 * Q6.0.3:: How do I get my outgoing mail archived?
|
|
|
444 * Q6.0.4:: How can I read and/or compose MIME messages?
|
|
|
445 * Q6.0.5:: How do I customize the From line?
|
|
|
446 * Q6.0.6:: How do I get my MUA to filter mail for me?
|
|
|
447 * Q6.0.7:: Remote mail reading with an MUA.
|
|
|
448 * Q6.0.8:: An MUA gets an error incorporating new mail.
|
|
|
449 * Q6.0.9:: Why isn't @file{movemail} working?
|
|
|
450 * Q6.0.10:: How do I make my MUA display graphical smilies?
|
|
|
451 * Q6.0.11:: How can I get those oh-so-neat X-Face lines?
|
|
|
452
|
|
|
453 6.1: Reading Mail with VM
|
|
|
454 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
455 * Q6.1.2:: How can I get VM to automatically check for new mail?
|
|
|
456 * 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"?
|
|
|
457 * Q6.1.4:: Is there a mailing list or FAQ for VM?
|
|
|
458 * Q6.1.5:: How do I make VM stay in a single frame?
|
|
|
459 * Q6.1.6:: Customization of VM not covered in the manual, or here.
|
|
|
460
|
|
|
461 6.2: Reading Netnews and Mail with Gnus
|
|
|
462 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
463 * Q6.2.2:: How do I make Gnus stay within a single frame?
|
|
|
464
|
|
|
465 6.3: FTP Access
|
|
|
466 * Q6.3.1:: Can I edit files on other hosts?
|
|
|
467 * Q6.3.2:: What is EFS?
|
|
|
468
|
|
|
469 6.4: Web Browsing with W3
|
|
|
470 * Q6.4.1:: What is W3?
|
|
|
471 * Q6.4.2:: How do I run W3 from behind a firewall?
|
|
|
472 * Q6.4.3:: Is it true that W3 supports style sheets and tables?
|
|
|
473
|
|
|
474 7 Advanced Customization Using XEmacs Lisp
|
|
|
475
|
|
|
476 7.0: Online Help
|
|
|
477 * Q7.0.1:: How can I get two instances of info?
|
|
|
478 * Q7.0.2:: How do I add new Info directories?
|
|
|
479
|
|
|
480 7.1: Emacs Lisp and @file{init.el}
|
|
|
481 * Q7.1.1:: What version of Emacs am I running?
|
|
|
482 * Q7.1.2:: How can I evaluate Emacs-Lisp expressions?
|
|
|
483 * Q7.1.3:: @code{(setq tab-width 6)} behaves oddly.
|
|
|
484 * Q7.1.4:: How can I add directories to the @code{load-path}?
|
|
|
485 * Q7.1.5:: How to check if a lisp function is defined?
|
|
|
486 * Q7.1.6:: Can I force the output of @code{(face-list)} to a buffer?
|
|
|
487
|
|
|
488 7.2: Emacs Lisp Programming Techniques
|
|
|
489 * Q7.2.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
|
490 * Q7.2.2:: Can I generate "fake" keyboard events?
|
|
|
491 * Q7.2.3:: Could you explain @code{read-kbd-macro} in more detail?
|
|
|
492 * Q7.2.4:: What is the performance hit of @code{let}?
|
|
|
493 * Q7.2.5:: What is the recommended use of @code{setq}?
|
|
|
494 * Q7.2.6:: What is the typical misuse of @code{setq}?
|
|
|
495 * Q7.2.7:: I like the @code{do} form of cl, does it slow things down?
|
|
|
496 * Q7.2.8:: I like recursion, does it slow things down?
|
|
|
497 * Q7.2.9:: How do I put a glyph as annotation in a buffer?
|
|
|
498 * Q7.2.10:: @code{map-extents} won't traverse all of my extents!
|
|
|
499 * Q7.2.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
|
500
|
|
|
501 7.3: Mathematics
|
|
|
502 * Q7.3.1:: What are bignums, ratios, and bigfloats in Lisp?
|
|
|
503 * Q7.3.2:: XEmacs segfaults when I use very big numbers!
|
|
|
504 * Q7.3.3:: Bignums are really slow!
|
|
|
505 * Q7.3.4:: Equal bignums don't compare as equal! What gives?
|
|
|
506
|
|
|
507 8 Other External Packages
|
|
|
508
|
|
|
509 8.0: TeX
|
|
|
510 * Q8.0.1:: Is there something better than LaTeX mode?
|
|
|
511 * Q8.0.2:: What is AUCTeX? Where do you get it?
|
|
|
512 * Q8.0.3:: Problems installing AUCTeX.
|
|
|
513 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline?
|
|
|
514
|
|
|
515 8.1: Other Unbundled Packages
|
|
|
516 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
|
517 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets?
|
|
|
518 * Q8.1.3:: Is there a MatLab mode?
|
|
|
519
|
|
|
520 8.2: Environments Built Around XEmacs
|
|
|
521 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop?
|
|
|
522 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21?
|
|
|
523 * Q8.2.3:: What is/was Energize?
|
|
|
524 * Q8.2.4:: What is Infodock?
|
|
|
525
|
|
|
526 9 What the Future Holds
|
|
|
527
|
|
|
528 9.0: Changes
|
|
|
529 * Q9.0.1:: What new features will be in XEmacs soon?
|
|
|
530 * Q9.0.2:: What's new in XEmacs 21.4?
|
|
|
531 * Q9.0.3:: What's new in XEmacs 21.1?
|
|
|
532 * Q9.0.4:: What's new in XEmacs 20.4?
|
|
|
533 * Q9.0.5:: What's new in XEmacs 20.3?
|
|
|
534 * Q9.0.6:: What's new in XEmacs 20.2?
|
|
|
535
|
|
|
536 10 New information about old XEmacsen
|
|
|
537
|
|
|
538 10.0: XEmacs 21.1
|
|
|
539 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
1495
|
540
|
|
428
|
541 @end detailmenu
|
|
|
542 @end menu
|
|
|
543
|
|
|
544 @node Introduction, Installation, Top, Top
|
|
|
545 @unnumbered 1 Introduction, Policy, Credits
|
|
|
546
|
|
|
547 Learning XEmacs is a lifelong activity. Even people who have used Emacs
|
|
|
548 for years keep discovering new features. Therefore this document cannot
|
|
|
549 be complete. Instead it is aimed at the person who is either
|
|
|
550 considering XEmacs for their own use, or has just obtained it and is
|
|
|
551 wondering what to do next. It is also useful as a reference to
|
|
|
552 available resources.
|
|
|
553
|
|
2417
|
554 The previous maintainer of the FAQ was
|
|
|
555 @email{rossini@@biostat.washington.edu, Anthony Rossini}, who started
|
|
|
556 it, after getting tired of hearing JWZ complain about repeatedly
|
|
|
557 having to answer questions. @email{ben@@xemacs.org, Ben Wing} then
|
|
|
558 took over and did a massive update reorganizing the whole thing. At
|
|
|
559 this point Anthony took back over, but then had to give it up again.
|
|
|
560 Some of the other contributors to this FAQ are listed later in this
|
|
|
561 document.
|
|
428
|
562
|
|
|
563 The previous version was converted to hypertext format, and edited by
|
|
|
564 @email{steve@@xemacs.org, Steven L. Baur}. It was converted back to
|
|
434
|
565 texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}. The FAQ was then
|
|
|
566 maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it
|
|
2417
|
567 on to ChristianNyb@o{}, and then to @email{wambold@@xemacs.org,Sandra Wambold}.
|
|
|
568
|
|
|
569 The current version of the FAQ has been heavily redone by
|
|
|
570 @email{ben@@xemacs.org, Ben Wing}.
|
|
428
|
571
|
|
|
572 If you notice any errors or items which should be added or amended to
|
|
2417
|
573 this FAQ please send email to @email{xemacs-beta@@xemacs.org}.
|
|
|
574 Include @samp{XEmacs FAQ} on the Subject: line.
|
|
428
|
575
|
|
|
576 @menu
|
|
2417
|
577 1.0: Introduction
|
|
|
578 * Q1.0.1:: What is XEmacs?
|
|
|
579 * Q1.0.2:: What is the current version of XEmacs?
|
|
|
580 * Q1.0.3:: Where can I find it?
|
|
|
581 * Q1.0.4:: Are binaries available?
|
|
|
582 * Q1.0.5:: How does XEmacs differ from GNU Emacs?
|
|
|
583 * Q1.0.6:: How much does XEmacs differ?
|
|
|
584 * Q1.0.7:: Is XEmacs "GNU"?
|
|
|
585 * Q1.0.8:: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
|
586 * Q1.0.9:: Why haven't XEmacs and GNU Emacs merged?
|
|
|
587 * Q1.0.10:: Where can I get help?
|
|
|
588 * Q1.0.11:: Where are the mailing lists archived?
|
|
|
589 * Q1.0.12:: How do you pronounce XEmacs?
|
|
|
590 * Q1.0.13:: What does XEmacs look like?
|
|
|
591 * Q1.0.14:: Where can I obtain a printed copy of the XEmacs User's Manual?
|
|
|
592
|
|
|
593 1.1: Versions for Different Operating Systems
|
|
|
594 * Q1.1.1:: Do I need X11 to run XEmacs?
|
|
|
595 * Q1.1.2:: Is there a port of XEmacs to Microsoft Windows?
|
|
|
596 * Q1.1.3:: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
597 * Q1.1.4:: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
598 * Q1.1.5:: What are the differences between the various MS Windows emacsen?
|
|
|
599 * Q1.1.6:: Is there a port of XEmacs to the Macintosh?
|
|
|
600 * Q1.1.7:: Is there a port of XEmacs to NextStep?
|
|
|
601 * Q1.1.8:: Is there a port of XEmacs to OS/2?
|
|
|
602 * Q1.1.9:: How does the port cope with differences in the Windows user interface?
|
|
|
603
|
|
|
604 1.2: Policies
|
|
|
605 * Q1.2.1:: What is the FAQ editorial policy?
|
|
|
606 * Q1.2.2:: How do I become a beta tester?
|
|
|
607 * Q1.2.3:: How do I contribute to XEmacs itself?
|
|
|
608
|
|
|
609 1.3: Credits
|
|
|
610 * Q1.3.1:: Who wrote XEmacs?
|
|
|
611 * Q1.3.2:: Who contributed to this version of the FAQ?
|
|
|
612 * Q1.3.3:: Who contributed to the FAQ in the past?
|
|
|
613
|
|
|
614 1.4: Internationalization
|
|
2459
|
615 * Q1.4.1:: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
2417
|
616 * Q1.4.2:: How can I help with internationalization?
|
|
|
617 * Q1.4.3:: How do I type non-ASCII characters?
|
|
|
618 * Q1.4.4:: Can XEmacs messages come out in a different language?
|
|
|
619 * Q1.4.5:: Please explain the various input methods in MULE/XEmacs
|
|
|
620 * Q1.4.6:: How do I portably code for MULE/XEmacs?
|
|
|
621 * Q1.4.7:: How about Cyrillic modes?
|
|
|
622 * Q1.4.8:: Does XEmacs support Unicode?
|
|
|
623 * Q1.4.9:: How does XEmacs display Unicode?
|
|
|
624
|
|
|
625 1.5: Getting Started
|
|
|
626 * Q1.5.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
|
627 * Q1.5.2:: Where do I put my @file{init.el} file?
|
|
|
628 * Q1.5.3:: Can I use the same @file{init.el} with the other Emacs?
|
|
|
629 * Q1.5.4:: Any good XEmacs tutorials around?
|
|
|
630 * Q1.5.5:: May I see an example of a useful XEmacs Lisp function?
|
|
|
631 * Q1.5.6:: And how do I bind it to a key?
|
|
|
632 * Q1.5.7:: What's the difference between a macro and a function?
|
|
|
633 * Q1.5.8:: What is @code{Custom}?
|
|
428
|
634 @end menu
|
|
|
635
|
|
2417
|
636 @unnumberedsec 1.0: Introduction
|
|
|
637
|
|
428
|
638 @node Q1.0.1, Q1.0.2, Introduction, Introduction
|
|
|
639 @unnumberedsubsec Q1.0.1: What is XEmacs?
|
|
|
640
|
|
479
|
641 XEmacs is a powerful, highly customizable open source text editor and
|
|
2417
|
642 application development system, with full GUI support. It is
|
|
|
643 protected under the GNU Public License and related to other versions
|
|
|
644 of Emacs, in particular GNU Emacs. Its emphasis is on modern
|
|
|
645 graphical user interface support and an open software development
|
|
|
646 model, similar to Linux. XEmacs has an active development community
|
|
|
647 numbering in the hundreds (and thousands of active beta testers on top
|
|
|
648 of this), and runs on all versions of MS Windows, on Mac OS X, on
|
|
|
649 Linux, and on nearly every other version of Unix in existence.
|
|
|
650 Support for XEmacs has been supplied by Sun Microsystems, University
|
|
|
651 of Illinois, Lucid, ETL/Electrotechnical Laboratory, Amdahl
|
|
|
652 Corporation, BeOpen, and others, as well as the unpaid time of a great
|
|
|
653 number of individual developers.
|
|
428
|
654
|
|
|
655 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction
|
|
|
656 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs?
|
|
|
657
|
|
2417
|
658 XEmacs versions 21.4.* are releases made from the current stable
|
|
|
659 sources. XEmacs versions 21.5.* (which will be released as 22.0) are
|
|
|
660 releases made from the development sources. Check at
|
|
|
661 @uref{http://www.xemacs.org} for the current minor version. XEmacs
|
|
|
662 versions 21.1.* were the previous stable releases, now retired.
|
|
|
663
|
|
|
664 XEmacs 20.4, released in February 1998, was the last release of v20.
|
|
|
665
|
|
|
666 XEmacs 19.16, released in November, 1997. was the last release of v19,
|
|
|
667 and was also the last version without international language support.
|
|
428
|
668
|
|
|
669 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction
|
|
|
670 @unnumberedsubsec Q1.0.3: Where can I find it?
|
|
|
671
|
|
2459
|
672 The canonical source and binaries can be found at:
|
|
428
|
673
|
|
|
674 @example
|
|
2459
|
675 @uref{http://ftp.xemacs.org/pub/xemacs/}
|
|
428
|
676 @end example
|
|
|
677
|
|
|
678 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction
|
|
2417
|
679 @unnumberedsubsec Q1.0.4: Are binaries available?
|
|
|
680
|
|
|
681 MS Windows binaries are available at
|
|
|
682 @uref{http://www.xemacs.org/Download/win32/} for the native versions
|
|
|
683 of 21.4 and 21.1. Cygwin binaries are now available as part of the
|
|
|
684 standard Cygwin installation process. XEmacs also comes pre-built as
|
|
|
685 part of many Linux distributions, such as Red Hat and SuSE.
|
|
|
686
|
|
|
687 Otherwise, you will need to build XEmacs yourself or get your system
|
|
|
688 administrator to do it. Generally, this is not a difficult process
|
|
|
689 under Unix and Mac OS X, as XEmacs has been tested under all of the
|
|
|
690 common Unix versions and under Mac OS X and comes with an extensive
|
|
|
691 configure script that is able to automatically detect most aspects of
|
|
|
692 the configuration of your particular system.
|
|
|
693
|
|
|
694 @node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
|
|
|
695 @unnumberedsubsec Q1.0.5: How does XEmacs differ from GNU Emacs?
|
|
428
|
696
|
|
|
697 For a detailed description of the differences between GNU Emacs and
|
|
|
698 XEmacs and a detailed history of XEmacs, check out the
|
|
|
699 @example
|
|
430
|
700 @uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file}
|
|
428
|
701 @end example
|
|
|
702
|
|
2417
|
703 @table @strong
|
|
|
704 @item User-Visible Editing Features
|
|
|
705 XEmacs in general tries hard to conform to exist user-interface
|
|
|
706 standards, and to work "out-of-the-box" without the need for obscure
|
|
|
707 customization changes. GNU Emacs, particularly version 21, has gotten
|
|
|
708 better about this (in many cases by copying the XEmacs behavior!), but
|
|
|
709 still has some weirdnesses. For example, the standard method of
|
|
|
710 selecting text using the Shift key works out-of-the-box in XEmacs.
|
|
|
711
|
|
|
712 XEmacs has a built-in toolbar. Four toolbars can actually be configured
|
|
|
713 simultaneously: top, bottom, left, and right toolbars.
|
|
|
714
|
|
|
715 XEmacs has vertical and horizontal scrollbars. Unlike in GNU Emacs 19
|
|
|
716 (which provides a primitive form of vertical scrollbar), these are true
|
|
|
717 toolkit scrollbars. A look-alike Motif scrollbar is provided for those
|
|
|
718 who don't have Motif. (Even for those who do, the look-alike may be
|
|
|
719 preferable as it is faster.)
|
|
|
720
|
|
|
721 XEmacs has buffer tabs along the top of the frame (although the
|
|
|
722 position can be changed) that make it very easy to switch buffers.
|
|
|
723
|
|
|
724 The menubar under XEmacs is better-designed, with more thought put into
|
|
|
725 it.
|
|
|
726
|
|
|
727 XEmacs can ask questions using popup dialog boxes. Any command executed
|
|
|
728 from a menu will ask yes/no questions with dialog boxes, while commands
|
|
|
729 executed via the keyboard will use the minibuffer.
|
|
|
730
|
|
|
731 XEmacs under MS Windows provides uses the standard file-dialog box for
|
|
|
732 opening and saving files. Standard menu-accelerator behavior can easily
|
|
|
733 be enabled using the Options menu, and integrates well into the existing
|
|
|
734 keymap.
|
|
|
735
|
|
|
736 XEmacs has (still experimental) support for widgets of various sorts --
|
|
|
737 buttons, text boxes, sliders, progress bars, etc. A progress bar is
|
|
|
738 used in font lock to show the progress.
|
|
|
739
|
|
|
740 Experimental support for drag-and-drop protocols is provided from
|
|
|
741 XEmacs 21.
|
|
|
742
|
|
|
743 @item General Platform Support
|
|
|
744 If you're running on a machine with audio hardware, you can specify
|
|
|
745 sound files for XEmacs to play instead of the default X beep. See the
|
|
|
746 documentation of the function load-sound-file and the variable
|
|
|
747 sound-alist. XEmacs also supports the network sound protocols NAS and
|
|
|
748 EsounD.
|
|
|
749
|
|
|
750 XEmacs 21 supports database protocols with LISP bindings, currently
|
|
|
751 including Berkeley DB, LDAP, and PostgreSQL (21.2 only).
|
|
|
752
|
|
|
753 XEmacs 20 and 21 support the Canna, Wnn, and SJ3 Japanese input method
|
|
|
754 servers directly, as well as through the X Input Method (XIM)
|
|
|
755 protocol. GNU Emacs 20 supports only the XIM protocol. Both Emacsen
|
|
|
756 support the Quail family of input methods (implemented in LISP) for many
|
|
|
757 languages.
|
|
|
758
|
|
|
759 XEmacs provides support for ToolTalk on systems that have
|
|
|
760 it.
|
|
|
761
|
|
|
762 @item Packaged LISP Libraries
|
|
|
763 Many more packages are provided standard with XEmacs than with GNU Emacs
|
|
|
764 19 or 20.
|
|
|
765
|
|
|
766 XEmacs 21 supports an integrated package management system which uses
|
|
|
767 EFS to download, then automatically install prebuilt LISP
|
|
|
768 libraries. This allows XEmacs users much more straightforward access to
|
|
|
769 the "latest and greatest" version of any given library.
|
|
|
770
|
|
|
771 We are working on a standard method for enabling, disabling and
|
|
|
772 otherwise controlling packages, which should make them very easy to use.
|
|
|
773
|
|
|
774 @item LISP Programming
|
|
|
775 From XEmacs 20 on, characters are a separate type. Characters can be
|
|
|
776 converted to integers (and many integers can be converted to
|
|
|
777 characters), but characters are not integers. GNU Emacs 19, XEmacs 19,
|
|
|
778 Mule 2.3 (an extensive patch to GNU Emacs 18.55 and 19.x), and GNU Emacs
|
|
|
779 20 (incorporating Mule 3 and later Mule 4) represent them as integers.
|
|
|
780
|
|
|
781 From XEmacs 20 on, the buffer is treated as an array of characters, and
|
|
|
782 the representation of buffer text is not exposed to LISP. The GNU Emacs
|
|
|
783 20 functions like buffer-as-multibyte are not supported.
|
|
|
784
|
|
|
785 In XEmacs, events are first-class objects. GNU Emacs 19 represents them
|
|
|
786 as integers, which obscures the differences between a key gesture and
|
|
|
787 the ancient ASCII code used to represent a particular overlapping subset
|
|
|
788 of them.
|
|
|
789
|
|
|
790 In XEmacs, keymaps are first-class opaque objects. GNU Emacs 19
|
|
|
791 represents them as complicated combinations of association lists and
|
|
|
792 vectors. If you use the advertised functional interface to manipulation
|
|
|
793 of keymaps, the same code will work in XEmacs, GNU Emacs 18, and GNU
|
|
|
794 Emacs 19; if your code depends on the underlying implementation of
|
|
|
795 keymaps, it will not.
|
|
|
796
|
|
|
797 XEmacs uses "extents" to represent all non-textual aspects of buffers;
|
|
|
798 GNU Emacs 19 uses two distinct objects, "text properties" and
|
|
|
799 "overlays", which divide up the functionality between them. Extents are
|
|
|
800 a superset of the union of the functionality of the two GNU Emacs data
|
|
|
801 types. The full GNU Emacs 19 interface to text properties and overlays
|
|
|
802 is supported in XEmacs (with extents being the underlying
|
|
|
803 representation).
|
|
|
804
|
|
|
805 Extents can be made to be copied into strings, and then restored, by
|
|
|
806 kill and yank. Thus, one can specify this behavior on either "extents"
|
|
|
807 or "text properties", whereas in GNU Emacs 19 text properties always
|
|
|
808 have this behavior and overlays never do.
|
|
|
809
|
|
|
810 @item Window System Programming Interface
|
|
|
811 XEmacs uses the MIT "Xt" toolkit instead of raw Xlib calls, which makes
|
|
|
812 it be a more well-behaved X citizen (and also improves portability). A
|
|
|
813 result of this is that it is possible to include other Xt "Widgets" in
|
|
|
814 the XEmacs window. Also, XEmacs understands the standard Xt command-line
|
|
|
815 arguments.
|
|
|
816
|
|
|
817 XEmacs supports Motif applications, generic Xt (e.g. Athena)
|
|
|
818 applications, and raw Xlib applications. An XEmacs variant which
|
|
|
819 supports GTK+ is available (integration as an option in the XEmacs
|
|
|
820 mainline is planned for XEmacs 22), although code to take advantage of
|
|
|
821 the support is as yet scarce.
|
|
|
822
|
|
|
823 An XEmacs frame can be placed within an "external client widget" managed
|
|
|
824 by another application. This allows an application to use an XEmacs
|
|
|
825 frame as its text pane rather than the standard Text widget that is
|
|
|
826 provided with Motif or Athena.
|
|
|
827
|
|
|
828 @item Community Participation
|
|
2459
|
829 Joining the XEmacs development team is simple. Mail to
|
|
|
830 @email{xemacs-beta@@xemacs.org, XEmacs Developers}, and you're in! (If
|
|
|
831 you want to be, of course. You're also welcome to just post
|
|
|
832 development-related questions and bug reports.) The GNU Emacs
|
|
2417
|
833 development team and internal mailing lists are still by invitation
|
|
|
834 only.
|
|
|
835
|
|
|
836 The "bleeding edge" of mainline XEmacs development is available by
|
|
|
837 anonymous CVS as are some subsidiary branches (check out the xemacs-gtk
|
|
|
838 module for the latest in GUI features!)
|
|
|
839
|
|
|
840 Development and maintenance of Lisp libraries is separated from the core
|
|
|
841 editor development at a fairly low level. This provides better
|
|
|
842 modularization and a better division of responsibility between external
|
|
|
843 library maintainers and the XEmacs core development team. Even for
|
|
|
844 packages the size of Gnus, XEmacs users normally have access to a
|
|
|
845 pre-built version within a few weeks of a major release, and minor
|
|
|
846 updates often within days.
|
|
|
847
|
|
|
848 CVS commit authority is broadly dispersed. Recognized maintainers of
|
|
|
849 LISP libraries who are willing to maintain XEmacs packaged versions
|
|
|
850 automatically qualify for CVS accounts for their packages.
|
|
|
851 @end table
|
|
|
852
|
|
|
853 @node Q1.0.6, Q1.0.7, Q1.0.5, Introduction
|
|
|
854 @unnumberedsubsec Q1.0.6: How much does XEmacs differ?
|
|
|
855
|
|
|
856 RMS has asserted at times that XEmacs is merely a "patch" on top of
|
|
|
857 GNU Emacs (@pxref{Q1.0.7}). In fact, probably not more than 5% of the
|
|
|
858 code, if that, remains unchanged, and nearly 14 years of work has gone
|
|
|
859 into XEmacs at this point. (GNU Emacs itself is only than 20 years
|
|
|
860 old, and thus XEmacs has existed as a separate product for over 2/3 of
|
|
|
861 the lifespan of GNU Emacs.) As a point of comparison, XEmacs 21.5 has
|
|
|
862 perhaps 65,000 more lines of C code than GNU Emacs 21.2.
|
|
|
863
|
|
|
864 However, the XEmacs developers strive to keep their code compatible with
|
|
|
865 GNU Emacs, especially on the Lisp level. Much effort goes into
|
|
|
866 "synching" the XEmacs Elisp code with recent GNU Emacs releases so as to
|
|
|
867 benefit from GNU Emacs development work. (In contrast, almost no code
|
|
|
868 from XEmacs has made it into GNU Emacs, and in fact the GNU Emacs
|
|
|
869 developers are instructed by RMS not to even look at XEmacs source code!
|
|
|
870 This stems from self-imposed licensing restrictions on the part of GNU
|
|
|
871 Emacs -- and almost certainly out of hostility, as well.)
|
|
|
872
|
|
|
873 @node Q1.0.7, Q1.0.8, Q1.0.6, Introduction
|
|
|
874 @unnumberedsubsec Q1.0.7: Is XEmacs "GNU"?
|
|
|
875
|
|
|
876 RMS insists on the term "GNU XEmacs" and maintains that
|
|
|
877
|
|
|
878 @quotation
|
|
|
879 XEmacs is GNU software because it's a modified version of a
|
|
|
880 GNU program. And it is GNU software because the FSF is the copyright
|
|
|
881 holder for most of it, and therefore the legal responsibility for
|
|
|
882 protecting its free status falls on us whether we want it or not. This
|
|
|
883 is why the term "GNU XEmacs" is legitimate.
|
|
|
884 @end quotation
|
|
|
885
|
|
|
886 In fact, FSF is @emph{not} the copyright holder for most of the code,
|
|
|
887 as very little unmodified FSF code remains (@pxref{Q1.0.6}).
|
|
|
888
|
|
|
889 Furthermore, RMS's assertion that XEmacs is "GNU" seems rather bizarre
|
|
|
890 to the XEmacs developers given RMS's hostility and general lack of
|
|
|
891 interest in cooperation. "GNU" software in general is part of the GNU
|
|
|
892 Project, is distributed by it on their FTP site, and receives support
|
|
|
893 (or at least cooperation), as well as implicit endorsement, from it.
|
|
|
894 The GNU Project, however, has never supported XEmacs and never
|
|
|
895 distributed XEmacs, and RMS's hostility is the farthest thing possible
|
|
|
896 from an endorsement. In fact, the GNU Project distributes a number of
|
|
|
897 non-GNU software projects on the FSF web site, but again XEmacs is not
|
|
|
898 one of them.
|
|
|
899
|
|
|
900 @node Q1.0.8, Q1.0.9, Q1.0.7, Introduction
|
|
|
901 @unnumberedsubsec Q1.0.8: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
|
902
|
|
|
903 Unfortunately even the naming of these two applications has become
|
|
|
904 politicized. Much of this stems from RMS, who has a history of
|
|
|
905 politicizing similar issues. (Compare the controversy over "Lignux"
|
|
|
906 and "GNU/Linux".) We would prefer that the terms "XEmacs" and "GNU
|
|
|
907 Emacs" be used, which are neutral and acceptable to most people. RMS,
|
|
|
908 however, is not willing to accept these terms. He insists that, if
|
|
|
909 his product is called "GNU Emacs", then ours must be called "GNU
|
|
|
910 XEmacs". (For our opinion of this term, @xref{Q1.0.7}.) On the other
|
|
|
911 hand, if our product is to be called "XEmacs", as we prefer, then his
|
|
|
912 product must simply be called "Emacs". The intent of this seems
|
|
|
913 clear: RMS wants to make sure the names reflect his view that his
|
|
|
914 version is the "real" Emacs and ours is merely a derivative,
|
|
|
915 second-class product (@pxref{Q1.0.6}).
|
|
|
916
|
|
|
917 The XEmacs developers hope that you will use the neutral terms
|
|
|
918 "XEmacs" and "GNU Emacs" for these two specific products. "Emacs", on
|
|
|
919 the other hand, is a generic term for a class of programmable text
|
|
|
920 editors with a similar look-and-feel, and usually a Lisp-based
|
|
|
921 extension language. These trace themselves back to early editors such
|
|
|
922 as EINE, ZWEI, ZMACS and Multics Emacs. @xref{A History of Emacs,,,
|
|
|
923 internals, XEmacs Internals Manual}.
|
|
|
924
|
|
|
925 We also call upon RMS, in the spirit of furthering cooperation, to
|
|
|
926 stop politicizing this issue and use the neutral terms "XEmacs" and
|
|
|
927 "GNU Emacs". We have already acceded to RMS' wishes in this respect,
|
|
|
928 and we expect him to do the same. (In the past, the XEmacs developers
|
|
|
929 often used the terms "FSF Emacs" or "FSFmacs" or "RMSmacs" in
|
|
|
930 reference to GNU Emacs; these terms were apparently modeled after RMS'
|
|
|
931 own usage of "Gosmacs" and "Gosling Emacs" in reference to Unipress
|
|
|
932 Emacs, produced by James Gosling. RMS, however, considers such terms
|
|
|
933 to be insulting, so we refrain from using them as much as possible in
|
|
|
934 preference to GNU Emacs.)
|
|
|
935
|
|
|
936 @node Q1.0.9, Q1.0.10, Q1.0.8, Introduction
|
|
|
937 @unnumberedsubsec Q1.0.9: Why haven't XEmacs and GNU Emacs merged?
|
|
|
938
|
|
|
939 There are currently irreconcilable differences in the views about
|
|
|
940 technical, programming, design, organizational and legal matters
|
|
|
941 between Richard Stallman (RMS), the author and leader of the GNU Emacs
|
|
|
942 project, and the XEmacs development team which provide little hope for
|
|
|
943 a merge to take place in the short-term future. There have been
|
|
|
944 repeated attempts at merging by all of the major XEmacs developers,
|
|
|
945 starting from the early days of Lucid Emacs (in 1991), but they have
|
|
|
946 all failed. RMS has very strong views about how GNU Emacs should be
|
|
|
947 structured and how his project should be run, and during the repeated
|
|
|
948 merge efforts has never demonstrated any realistic interest in
|
|
|
949 sufficiently compromising or ceding control to allow a middle ground
|
|
|
950 to be found. The basic problem seems to be the very different goals
|
|
|
951 of RMS and the XEmacs project. The primary goals of the XEmacs
|
|
|
952 project are technical and organizational -- we want to create the best
|
|
|
953 editor possible, and to make it as easy as possible for people around
|
|
|
954 the world to contribute. The primary goals of RMS, on the other hand,
|
|
|
955 are political, and GNU Emacs, and any potential merge efforts with
|
|
|
956 XEmacs, are strictly subservient to these goals. In fact, in many
|
|
|
957 ways RMS sees GNU Emacs as the "poster child" of his aims, the one
|
|
|
958 program in the GNU project that above all others must set an example
|
|
|
959 to the world. (This has to do with the fact that GNU Emacs was the
|
|
|
960 first program in the GNU project, and the only one that he is still
|
|
|
961 personally involved with on a day-to-day basis.) Given his goals, his
|
|
|
962 position is completely reasonable -- but unfortunately, makes any
|
|
|
963 merge impossible.
|
|
|
964
|
|
|
965 From the XEmacs perspective, the most intractable issues appear to be
|
|
|
966 legal and organizational, specifically:
|
|
428
|
967
|
|
|
968 @itemize @bullet
|
|
|
969 @item
|
|
2417
|
970 RMS requires "legal papers" to be signed for all contributions of code
|
|
|
971 to GNU Emacs over 10 lines or so, transferring the copyright and all
|
|
|
972 legal rights to the code to the Free Software Foundation. XEmacs does
|
|
|
973 not and has never required this, since it has the practical effect of
|
|
|
974 discouraging individual and in particular corporate contributions --
|
|
|
975 corporations will almost never sign away their legal rights to code
|
|
|
976 since it makes it impossible to reuse the code in any product that
|
|
|
977 whose license is not compatible with the GNU General Public License.
|
|
|
978 Since RMS has shown no inclination to compromise on this issue, a
|
|
|
979 merge would require that most of the existing XEmacs code would need
|
|
|
980 to be thrown away and rewritten -- something the XEmacs developers are
|
|
|
981 understandably reluctant to do.
|
|
|
982
|
|
|
983 @item
|
|
|
984 A repeated stumbling block in the merge talks has been the issue of
|
|
|
985 organizational control over the resulting product. RMS has made it
|
|
|
986 clear that he intends to have final say over design issues in a merged
|
|
|
987 Emacs. Unfortunately, RMS and the XEmacs developers have repeatedly
|
|
|
988 clashed over design decisions, and RMS' insistence on getting his way
|
|
|
989 in such disagreements was the very reason for the split in the first
|
|
|
990 place. This same issue has come up again and again in merge talks and
|
|
|
991 we have never been able to come to a satisfactory resolution. To the
|
|
|
992 extent that RMS is willing to compromise at all, it appears to be of a
|
|
|
993 purely political rather than technical nature -- "If we support this
|
|
|
994 feature of yours, we also get to support this other feature of mine."
|
|
|
995 The XEmacs developers cannot see how such a process would lead to
|
|
|
996 anything but a mess of incompatible things hodgepodged together.
|
|
|
997
|
|
|
998 @item
|
|
|
999 Because of the years of separate development, distinct and
|
|
|
1000 incompatible interfaces have developed and merging would be extremely
|
|
|
1001 difficult even with the above non-technical issues resolved. The
|
|
|
1002 problem has been exacerbated by the issue of legal papers -- because
|
|
|
1003 XEmacs code is not "kosher" from RMS' perspective, he discourages
|
|
|
1004 developers from even looking at it out of legal concerns. Although it
|
|
|
1005 is still possible to read the XEmacs documentation and run the
|
|
|
1006 program, the practical effect of this prohibition has been to strongly
|
|
|
1007 discourage code-sharing and cooperative development -- although a
|
|
|
1008 great deal of GNU Emacs code has been incorporated into XEmacs,
|
|
|
1009 practically none has gone the other direction.
|
|
428
|
1010 @end itemize
|
|
|
1011
|
|
|
1012 If you have a comment to add regarding the merge, it is a good idea to
|
|
2417
|
1013 avoid posting to the newsgroups, because of the very heated flamewars
|
|
|
1014 that often result. Mail your questions to
|
|
|
1015 @email{xemacs-beta@@xemacs.org} and @email{emacs-devel@@gnu.org}.
|
|
|
1016
|
|
|
1017 @node Q1.0.10, Q1.0.11, Q1.0.9, Introduction
|
|
|
1018 @unnumberedsubsec Q1.0.10: Where can I get help?
|
|
428
|
1019
|
|
430
|
1020 Probably the easiest way, if everything is installed, is to use Info, by
|
|
462
|
1021 pressing @kbd{C-h i}, or looking for an Info item on the
|
|
430
|
1022 Help Menu. @kbd{M-x apropos} can be used to look for particular commands.
|
|
|
1023
|
|
|
1024 For items not found in the manual, try reading this FAQ
|
|
|
1025 and reading the Usenet group comp.emacs.xemacs.
|
|
|
1026
|
|
|
1027 If you choose to post to a newsgroup, @strong{please use
|
|
|
1028 comp.emacs.xemacs}. Please do not post XEmacs related questions to
|
|
|
1029 gnu.emacs.help.
|
|
428
|
1030
|
|
|
1031 If you cannot post or read Usenet news, there is a corresponding mailing
|
|
741
|
1032 list @email{xemacs-news@@xemacs.org} which is available. It can be
|
|
742
|
1033 subscribed to via the Mailman Web interface or by sending mail to to
|
|
741
|
1034 @email{xemacs-news-request@@xemacs.org} with @samp{subscribe} in the
|
|
742
|
1035 body of the message. See also
|
|
|
1036 @uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a
|
|
|
1037 subscription, you may use the @email{xemacs-news-request@@xemacs.org}
|
|
|
1038 address or the Web interface. Send a message with a subject of
|
|
|
1039 @samp{unsubscribe} to be removed.
|
|
428
|
1040
|
|
2417
|
1041 @node Q1.0.11, Q1.0.12, Q1.0.10, Introduction
|
|
|
1042 @unnumberedsubsec Q1.0.11: Where are the mailing lists archived?
|
|
428
|
1043
|
|
462
|
1044 The archives can be found at @uref{http://list-archive.xemacs.org}
|
|
428
|
1045
|
|
2417
|
1046 @node Q1.0.12, Q1.0.13, Q1.0.11, Introduction
|
|
|
1047 @unnumberedsubsec Q1.0.12: How do you pronounce XEmacs?
|
|
428
|
1048
|
|
430
|
1049 The most common pronounciation is @samp{Eks eemax}.
|
|
428
|
1050
|
|
2417
|
1051 @node Q1.0.13, Q1.0.14, Q1.0.12, Introduction
|
|
|
1052 @unnumberedsubsec Q1.0.13: What does XEmacs look like?
|
|
428
|
1053
|
|
658
|
1054 Screen snapshots are available at
|
|
|
1055 @uref{http://www.xemacs.org/About/Screenshots/index.html}
|
|
|
1056 as part of the XEmacs website.
|
|
428
|
1057
|
|
2417
|
1058 @node Q1.0.14, Q1.1.1, Q1.0.13, Introduction
|
|
|
1059 @unnumberedsubsec Q1.0.14: Where can I obtain a printed copy of the XEmacs User's Manual?
|
|
|
1060
|
|
|
1061 Pre-printed manuals are not available. If you are familiar with
|
|
|
1062 TeX, you can generate your own manual from the XEmacs sources.
|
|
|
1063
|
|
|
1064 HTML and Postscript versions of XEmacs manuals are available from the
|
|
|
1065 XEmacs web site at
|
|
|
1066 @uref{http://www.xemacs.org/Documentation/index.html}.
|
|
|
1067
|
|
|
1068 @unnumberedsec 1.1: Versions for Different Operating Systems
|
|
|
1069
|
|
|
1070 @node Q1.1.1, Q1.1.2, Q1.0.14, Introduction
|
|
|
1071 @unnumberedsubsec Q1.1.1: Do I need X11 to run XEmacs?
|
|
|
1072
|
|
|
1073 No. The name @dfn{XEmacs} is unfortunate in the sense that it is
|
|
|
1074 @strong{not} an X Window System-only version of Emacs. XEmacs has
|
|
|
1075 full color support on a color-capable character terminal.
|
|
|
1076
|
|
|
1077 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
|
|
|
1078 @unnumberedsubsec Q1.1.2: Is there a port of XEmacs to Microsoft Windows?
|
|
|
1079
|
|
|
1080 Yes. Beginning with release 21.0, XEmacs has worked under MS Windows
|
|
|
1081 and is fully-featured and actively developed. A group of dedicated
|
|
|
1082 developers actively maintains and improves the Windows-specific
|
|
|
1083 portions of the code. Some of the core developers, in fact, use
|
|
|
1084 Windows as their only development environment, and some features, such
|
|
|
1085 as printing, actually work better on Windows than native Unix and Mac
|
|
|
1086 OS X. The mailing list at @email{xemacs-winnt@@xemacs.org} is dedicated
|
|
|
1087 to that effort (please use the -request address to
|
|
|
1088 subscribe). (Despite its name, XEmacs actually works on all versions
|
|
|
1089 of Windows.)
|
|
|
1090
|
|
|
1091 The list name is misleading, as XEmacs supports and has been compiled on
|
|
|
1092 Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows
|
|
|
1093 XP, and all newer versions of Windows. The MS Windows-specific code is
|
|
|
1094 based on Microsoft Win32 API, and will not work on MS Windows 3.x or on
|
|
|
1095 MS-DOS.
|
|
|
1096
|
|
|
1097 XEmacs also supports the Cygwin and MinGW development and runtime
|
|
|
1098 environments, where it also uses native Windows code for graphical
|
|
|
1099 features. In addition, under Cygwin it is possible to compile XEmacs
|
|
|
1100 to use an X server (and XFree86 is available as part of the standard
|
|
|
1101 Cygwin installation).
|
|
|
1102
|
|
|
1103 @node Q1.1.3, Q1.1.4, Q1.1.2, Introduction
|
|
|
1104 @unnumberedsubsec Q1.1.3: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
1105
|
|
|
1106 Yes, you can, but no you do not need to. In fact, we recommend that you
|
|
|
1107 use a native-GUI version unless you have a specific need for an X
|
|
|
1108 version.
|
|
|
1109
|
|
|
1110 @node Q1.1.4, Q1.1.5, Q1.1.3, Introduction
|
|
|
1111 @unnumberedsubsec Q1.1.4: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
1112
|
|
|
1113 To answer the second part of the question: No, you, you don't need
|
|
|
1114 Cygwin or MinGW to build or to run XEmacs. But if you have them and
|
|
|
1115 want to use them, XEmacs supports these environments.
|
|
|
1116
|
|
|
1117 (One important reason to support Cygwin is that it lets the MS Windows
|
|
|
1118 developers test out their code in a Unix environment without actually
|
|
|
1119 having to have a Unix machine around. For this reason alone, Cygwin
|
|
|
1120 support is likely to remain supported for a long time in XEmacs. Same
|
|
|
1121 goes for the X support under Cygwin, for the same reasons. MinGW
|
|
|
1122 support, on the other hand, depends on volunteers to keep it up to date;
|
|
|
1123 but this is generally not hard.)
|
|
|
1124
|
|
|
1125 Cygwin is a set of tools providing Unix-like API on top of Win32.
|
|
|
1126 It makes it easy to port large Unix programs without significant
|
|
|
1127 changes to their source code. It is a development environment as well
|
|
|
1128 as a runtime environment.
|
|
|
1129
|
|
|
1130 When built with Cygwin, XEmacs supports all display types -- TTY, X &
|
|
|
1131 Win32 GUI, and can be built with support for all three simultaneously.
|
|
|
1132 If you build with Win32 GUI support then the Cygwin version uses the
|
|
|
1133 majority of the Windows-specific code, which is mostly related to
|
|
|
1134 display. If you want to build with X support you need X libraries (and
|
|
|
1135 an X server to display XEmacs on); see @ref{Q2.2.7}. TTY and Win32 GUI
|
|
|
1136 require no additional libraries beyond what comes standard with Cygwin.
|
|
|
1137
|
|
|
1138 The advantages of the Cygwin version are that it integrates well with
|
|
|
1139 the Cygwin environment for existing Cygwin users; uses configure so
|
|
|
1140 building with different features is very easy; and actively supports X &
|
|
|
1141 TTY. Furthermore, the entire Cygwin environment and compiler are free,
|
|
|
1142 whereas Visual C++ costs money.
|
|
|
1143
|
|
|
1144 The disadvantage is that it requires the whole Cygwin environment,
|
|
|
1145 whereas the native port requires only a suitable MS Windows compiler.
|
|
|
1146 Also, it follows the Unix filesystem and process model very closely
|
|
|
1147 (some will undoubtedly view this as an advantage).
|
|
|
1148
|
|
2459
|
1149 See @uref{http://www.cygwin.com/} for more information on
|
|
2417
|
1150 Cygwin.
|
|
|
1151
|
|
|
1152 MinGW is a collection of header files and import libraries that allow
|
|
|
1153 one to use GCC under the Cygwin environment to compile and produce
|
|
|
1154 exactly the same native Win32 programs that you can using Visual C++.
|
|
|
1155 Programs compiled with MinGW make use of the standard Microsoft runtime
|
|
|
1156 library @file{MSVCRT.DLL}, present on all Windows systems, and look,
|
|
|
1157 feel, and act like a standard Visual-C-produced application. (The only
|
|
|
1158 difference is the compiler.) This means that, unlike a
|
|
|
1159 standardly-compiled Cygwin application, no extra runtime support
|
|
|
1160 (e.g. Cygwin's @file{cygwin1.dll}) is required. This, along with the
|
|
|
1161 fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y
|
|
|
1162 environment, for those die-hard Unix hackers out there), is the main
|
|
|
1163 advantage of MinGW. It is also potentially faster than Cygwin because
|
|
|
1164 it has less overhead when calling Windows, but you lose the POSIX
|
|
|
1165 emulation layer, which makes Unix programs harder to port. (But this is
|
|
|
1166 irrelevant for XEmacs since it's already ported to Win32.)
|
|
|
1167
|
|
|
1168 See @uref{http://www.mingw.org/} for more information on MinGW.
|
|
|
1169
|
|
|
1170 @node Q1.1.5, Q1.1.6, Q1.1.4, Introduction
|
|
|
1171 @unnumberedsubsec Q1.1.5: What are the differences between the various MS Windows emacsen?
|
|
|
1172
|
|
|
1173 XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing.
|
|
|
1174 Could you briefly explain the differences between them?
|
|
|
1175
|
|
|
1176 Here is a recount of various Emacs versions running on MS Windows:
|
|
|
1177
|
|
|
1178 @itemize @bullet
|
|
|
1179
|
|
|
1180 @item
|
|
|
1181 XEmacs
|
|
|
1182
|
|
|
1183 @itemize @minus
|
|
|
1184
|
|
|
1185 @item
|
|
|
1186 Beginning with XEmacs 19.12, XEmacs' architecture was redesigned
|
|
|
1187 in such a way to allow clean support of multiple window systems. At
|
|
|
1188 this time the TTY support was added, making X and TTY the first two
|
|
|
1189 "window systems" supported by XEmacs. The 19.12 design is the basis for
|
|
|
1190 the current native MS Windows code.
|
|
|
1191
|
|
|
1192 @item
|
|
|
1193 Some time during 1997, David Hobley (soon joined by Marc Paquette)
|
|
|
1194 imported some of the NT-specific portions of GNU Emacs, making XEmacs
|
|
|
1195 with X support compile under Windows NT, and creating the "X" port.
|
|
|
1196
|
|
|
1197 @item
|
|
|
1198 Several months later, Jonathan Harris sent out initial patches to use
|
|
|
1199 the Win32 API, thus creating the native port. Since then, various
|
|
|
1200 people have contributed, including Kirill M. Katsnelson (contributed
|
|
|
1201 support for menubars, subprocesses and network, as well as loads of
|
|
|
1202 other code), Andy Piper (ported XEmacs to Cygwin environment,
|
|
|
1203 contributed Windows unexec, Windows-specific glyphs and toolbars code,
|
|
|
1204 and more), Ben Wing (loads of improvements; primary MS Windows developer
|
|
|
1205 since 2000), Jeff Sparkes (contributed scrollbars support) and many
|
|
|
1206 others.
|
|
|
1207 @end itemize
|
|
|
1208
|
|
|
1209 @item
|
|
|
1210 NT Emacs
|
|
|
1211
|
|
|
1212 @itemize @minus
|
|
|
1213
|
|
|
1214 @item
|
|
|
1215 NT Emacs was an early version of GNU Emacs 19 modified to compile and
|
|
|
1216 run under MS Windows 95 and NT using the native Win32 API. It was
|
|
|
1217 written by Geoff Voelker, and has long since been incorporated into
|
|
|
1218 the mainline GNU Emacs distribution.
|
|
|
1219 @end itemize
|
|
|
1220
|
|
|
1221 @item
|
|
|
1222 Win-Emacs
|
|
|
1223
|
|
|
1224 @itemize @minus
|
|
|
1225
|
|
|
1226 @item
|
|
|
1227 Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X
|
|
|
1228 compatibility libraries. Win-Emacs was written by Ben Wing. The MS
|
|
|
1229 Windows code never made it back to Lucid Emacs, and its creator (Pearl
|
|
|
1230 Software) has long since gone out of business.
|
|
|
1231 @end itemize
|
|
|
1232
|
|
|
1233 @item
|
|
|
1234 GNU Emacs for DOS
|
|
|
1235
|
|
|
1236 @itemize @minus
|
|
|
1237
|
|
|
1238 @item
|
|
|
1239 GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
|
|
|
1240 port of GCC). Such an Emacs is heavily underfeatured, because it does
|
|
|
1241 not support long file names, lacks proper subprocesses support, and
|
|
|
1242 is far too big compared with typical DOS editors.
|
|
|
1243 @end itemize
|
|
|
1244
|
|
|
1245 @item
|
|
|
1246 GNU Emacs compiled with Win32
|
|
|
1247
|
|
|
1248 @itemize @minus
|
|
|
1249
|
|
|
1250 @item
|
|
2459
|
1251 Starting with GNU Emacs 19.30, it has been possible to compile GNU Emacs
|
|
2417
|
1252 under MS Windows using the DJGPP compiler and X libraries. The result
|
|
|
1253 is very similar to GNU Emacs compiled under MS DOS, only it works
|
|
|
1254 somewhat better because it runs in 32-bit mode, makes use of all the
|
|
|
1255 system memory, supports long file names, etc.
|
|
|
1256 @end itemize
|
|
|
1257
|
|
|
1258 @end itemize
|
|
|
1259
|
|
|
1260 @node Q1.1.6, Q1.1.7, Q1.1.5, Introduction
|
|
|
1261 @unnumberedsubsec Q1.1.6: Is there a port of XEmacs to the Macintosh?
|
|
438
|
1262
|
|
613
|
1263 Yes.
|
|
|
1264
|
|
|
1265 XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly
|
|
|
1266 will not feel very much like a Mac application as it has no Mac-specific
|
|
|
1267 code in it.
|
|
|
1268
|
|
|
1269 There is also a port of XEmacs 19.14 that works on all recent versions
|
|
|
1270 of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com,
|
|
2421
|
1271 Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY
|
|
|
1272 mode only (one single Macintosh window, 25 colors), but has a large
|
|
|
1273 number of Mac-specific additions. It's available at
|
|
613
|
1274 @uref{http://homepage.mac.com/pjarvis/xemacs.html}.
|
|
428
|
1275
|
|
2417
|
1276 @node Q1.1.7, Q1.1.8, Q1.1.6, Introduction
|
|
|
1277 @unnumberedsubsec Q1.1.7: Is there a port of XEmacs to NextStep?
|
|
428
|
1278
|
|
|
1279 Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did
|
|
|
1280 the port of GNU Emacs to NeXTstep and expressed interest in doing the
|
|
|
1281 XEmacs port, but never went any farther.
|
|
|
1282
|
|
2417
|
1283 @node Q1.1.8, Q1.1.9, Q1.1.7, Introduction
|
|
|
1284 @unnumberedsubsec Q1.1.8: Is there a port of XEmacs to OS/2?
|
|
428
|
1285
|
|
438
|
1286 No, but Alexander Nikolaev <avn_1251@@mail.ru> is working on it.
|
|
428
|
1287
|
|
2417
|
1288 @node Q1.1.9, Q1.2.1, Q1.1.8, Introduction
|
|
|
1289 @unnumberedsubsec Q1.1.9: How does the port cope with differences in the Windows user interface?
|
|
|
1290
|
|
|
1291 The XEmacs (and Emacs in general) user interface is pretty different
|
|
|
1292 from what is expected of a typical MS Windows program. How does the MS
|
|
|
1293 Windows port cope with it?
|
|
|
1294
|
|
|
1295 As a general rule, we follow native MS Windows conventions as much as
|
|
|
1296 possible. 21.4 is a fairly complete Windows application, supporting
|
|
|
1297 native printing, system file dialog boxes, tool tips, etc. In cases
|
|
|
1298 where there's a clear UI conflict, we currently use normal Unix XEmacs
|
|
|
1299 behavior by default, but make sure the MS Windows "look and feel" (mark
|
|
|
1300 via shift-arrow, self-inserting deletes region, Alt selects menu items,
|
|
|
1301 etc.) is easily configurable (respectively: using the variable
|
|
|
1302 @code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact
|
|
|
1303 the default in these versions], or the @file{pc-select} package; using
|
|
|
1304 the @file{pending-del} package; and setting the variable
|
|
|
1305 @code{menu-accelerator-enabled} to @code{menu-force} in 21.4 and above).
|
|
|
1306 In fact, if you use the sample @file{init.el} file as your init file,
|
|
|
1307 you will get all these behaviors automatically turned on.
|
|
|
1308
|
|
|
1309 In future versions, some of these features might be turned on by
|
|
|
1310 default in the MS Windows environment.
|
|
|
1311
|
|
|
1312 @unnumberedsec 1.2: Policies
|
|
|
1313
|
|
|
1314 @node Q1.2.1, Q1.2.2, Q1.1.9, Introduction
|
|
|
1315 @unnumberedsubsec Q1.2.1: What is the FAQ editorial policy?
|
|
428
|
1316
|
|
|
1317 The FAQ is actively maintained and modified regularly. All links should
|
|
434
|
1318 be up to date. Unfortunately, some of the information is out of date --
|
|
|
1319 a situation which the FAQ maintainer is working on. All submissions are
|
|
|
1320 welcome, please e-mail submissions to @email{faq@@xemacs.org, XEmacs FAQ
|
|
|
1321 maintainers}.
|
|
428
|
1322
|
|
|
1323 Please make sure that @samp{XEmacs FAQ} appears on the Subject: line.
|
|
|
1324 If you think you have a better way of answering a question, or think a
|
|
430
|
1325 question should be included, we'd like to hear about it. Questions and
|
|
442
|
1326 answers included into the FAQ will be edited for spelling and grammar
|
|
428
|
1327 and will be attributed. Answers appearing without attribution are
|
|
442
|
1328 either from versions of the FAQ dated before May 1996 or are from
|
|
|
1329 previous FAQ maintainers. Answers quoted from Usenet news articles will
|
|
|
1330 always be attributed, regardless of the author.
|
|
428
|
1331
|
|
2417
|
1332 @node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
|
|
|
1333 @unnumberedsubsec Q1.2.2: How do I become a beta tester?
|
|
428
|
1334
|
|
430
|
1335 Send an email message to @email{xemacs-beta-request@@xemacs.org} with
|
|
|
1336 the line @samp{subscribe} in the body of the message.
|
|
428
|
1337
|
|
|
1338 Be prepared to get your hands dirty, as beta testers are expected to
|
|
|
1339 identify problems as best they can.
|
|
|
1340
|
|
2417
|
1341 @node Q1.2.3, Q1.3.1, Q1.2.2, Introduction
|
|
|
1342 @unnumberedsubsec Q1.2.3: How do I contribute to XEmacs itself?
|
|
|
1343
|
|
|
1344 It depends on the knowledge and time you possess. If you are able, by
|
|
|
1345 all means become a beta tester (@pxref{Q1.2.2}). If you are a
|
|
|
1346 programmer, try to build XEmacs and see if you can improve it.
|
|
|
1347
|
|
|
1348 Otherwise, you can still help by using XEmacs as your everyday editor
|
|
|
1349 (for pre-built binary versions, @pxref{Q1.0.4}) and reporting bugs you
|
|
|
1350 find to the mailing list.
|
|
|
1351
|
|
|
1352 Another area where we need help is the documentation: We need good
|
|
|
1353 documentation for building XEmacs and for using it. This FAQ is a
|
|
|
1354 small step in that direction.
|
|
428
|
1355
|
|
|
1356 Ben Wing @email{ben@@xemacs.org} writes:
|
|
|
1357
|
|
|
1358 @quotation
|
|
|
1359 BTW if you have a wish list of things that you want added, you have to
|
|
|
1360 speak up about it! More specifically, you can do the following if you
|
|
|
1361 want a feature added (in increasing order of usefulness):
|
|
|
1362
|
|
|
1363 @itemize @bullet
|
|
|
1364 @item
|
|
|
1365 Make a posting about a feature you want added.
|
|
|
1366
|
|
|
1367 @item
|
|
|
1368 Become a beta tester and make more postings about those same features.
|
|
|
1369
|
|
|
1370 @item
|
|
|
1371 Convince us that you're going to use the features in some cool and
|
|
|
1372 useful way.
|
|
|
1373
|
|
|
1374 @item
|
|
|
1375 Come up with a clear and well-thought-out API concerning the features.
|
|
|
1376
|
|
|
1377 @item
|
|
|
1378 Write the code to implement a feature and send us a patch.
|
|
|
1379 @end itemize
|
|
|
1380
|
|
|
1381 (not that we're necessarily requiring you to write the code, but we can
|
|
|
1382 always hope :)
|
|
|
1383 @end quotation
|
|
|
1384
|
|
2417
|
1385 @unnumberedsec 1.3: Credits
|
|
|
1386
|
|
|
1387 @node Q1.3.1, Q1.3.2, Q1.2.3, Introduction
|
|
|
1388 @unnumberedsubsec Q1.3.1: Who wrote XEmacs?
|
|
|
1389
|
|
|
1390 XEmacs is the result of the time and effort of many people, and the
|
|
|
1391 active developers have changed over time. There are two major
|
|
|
1392 components of the XEmacs effort -- writing the code itself and providing
|
|
|
1393 all the support work (testing the code, releasing beta and final
|
|
|
1394 versions, handling patches, reading bug reports, maintaining the web
|
|
|
1395 site, managing the mailing lists, etc. etc.). Neither component would
|
|
|
1396 work without the other.
|
|
|
1397
|
|
|
1398 @subheading CODING
|
|
|
1399
|
|
|
1400 The primary code contributor over the years has been Ben Wing (active
|
|
|
1401 since late 1992). Between 1991 and 1995, large amounts of coding was
|
|
|
1402 contributed by Jamie Zawinski and Chuck Thompson. Many other people
|
|
|
1403 have authored major subsystems or otherwise contributed large amounts of
|
|
|
1404 code, including Andy Piper, Hrvoje Niksic, Jerry James, Jonathan Harris,
|
|
|
1405 Kyle Jones, Martin Buchholz, Michael Sperber, Olivier Galibert, Richard
|
|
|
1406 Mlynarik, Stig, William Perry and plenty of others.
|
|
|
1407
|
|
|
1408 Primary XEmacs-specific subsystems and their authors:
|
|
|
1409
|
|
|
1410 @table @asis
|
|
|
1411 @item Objects
|
|
|
1412 @itemize @minus
|
|
|
1413 @item
|
|
|
1414 Conversion from 26-bit to 28-bit pointers and integers, lrecords, lcrecords: Richard Mlynarik, 1994
|
|
|
1415 @item
|
|
|
1416 Conversion to 32-bit pointers and 31-bit integers: Kyle Jones, Martin Buchholz
|
|
|
1417 @item
|
|
|
1418 Portable dumper, object descriptions: Olivier Galibert
|
|
|
1419 @item
|
|
|
1420 KKCC (new garbage collector), ephemerons, weak boxes: Michael Sperber and students
|
|
|
1421 @item
|
|
|
1422 Random object work (object equal and hash methods, weak lists, lcrecord lists, bit vectors, dynarr, blocktype, opaque, string resizing): Ben Wing
|
|
|
1423 @item
|
|
|
1424 Profiling: Ben Wing
|
|
|
1425 @item
|
|
|
1426 Some byte-compilation and hash-table improvements: Martin Buchholz
|
|
|
1427 @item
|
|
|
1428 Bignum: Jerry James
|
|
|
1429 @end itemize
|
|
|
1430
|
|
|
1431 @item Internationalization/Mule
|
|
|
1432 @itemize @minus
|
|
|
1433 @item
|
|
|
1434 mostly Ben Wing; many ideas for future work, Stephen Turnbull
|
|
|
1435 @end itemize
|
|
|
1436
|
|
|
1437 @item I/O
|
|
|
1438 @itemize @minus
|
|
|
1439 @item
|
|
|
1440 Basic event/event-stream implementation: Jamie Zawinski
|
|
|
1441 @item
|
|
|
1442 Most event work since 1994: Ben Wing
|
|
|
1443 @item
|
|
|
1444 Asynchronous stuff (async timeouts, signals, quit-checking): Ben Wing
|
|
|
1445 @item
|
|
|
1446 Process method abstraction, Windows process work: Kirill Katsnelson
|
|
|
1447 @item
|
|
|
1448 Misc-user events, async timeouts, most quit-checking and signal code, most other work since 1994: Ben Wing
|
|
|
1449 @item
|
|
|
1450 Lstreams: Ben Wing
|
|
|
1451 @end itemize
|
|
|
1452
|
|
|
1453 @item Display
|
|
|
1454 @itemize @minus
|
|
|
1455 @item
|
|
|
1456 Redisplay mechanism: implementation, Chuck Thompson; additional work, lots of people
|
|
|
1457 @item
|
|
|
1458 Glyphs: mostly Ben Wing
|
|
|
1459 @item
|
|
|
1460 Specifiers: Ben Wing
|
|
|
1461 @item
|
|
|
1462 Extents: initial implementation, someone at Lucid; rewrite, 1994, Ben Wing
|
|
|
1463 @item
|
|
|
1464 Widgets: Andy Piper
|
|
|
1465 @item
|
|
|
1466 JPEG/PNG/TIFF image converters: Ben Wing, William Perry, Jareth Hein, others (see comment in @file{glyphs-eimage.c})
|
|
|
1467 @item
|
|
|
1468 Menus: Jamie Zawinski, someone at Lucid (Lucid menus)
|
|
|
1469 @item
|
|
|
1470 Scrollbars: Chuck Thompson, ??? (Lucid scrollbar)
|
|
|
1471 @item
|
|
|
1472 Multi-device/device-independence work (console/device/etc methods): Ben Wing, prototype by chuck thompson
|
|
|
1473 @item
|
|
|
1474 Faces: first implementation, Jamie Zawinski; second, chuck; third, Ben Wing
|
|
|
1475 @item
|
|
|
1476 Fonts/colors: first implementation, Jamie Zawinski; further work, Ben Wing
|
|
|
1477 @item
|
|
|
1478 Toolbars: implementation, chuck, much interface work, Ben Wing
|
|
|
1479 @item
|
|
|
1480 Gutters, tabs: andy piper
|
|
|
1481 @end itemize
|
|
|
1482
|
|
|
1483 @item Device subsystems
|
|
|
1484 @itemize @minus
|
|
|
1485 @item
|
|
|
1486 X Windows: Jamie Zawinksi, Ben Wing, others
|
|
|
1487 @item
|
|
|
1488 GTK: William Perry, Malcolm Purvis
|
|
|
1489 @item
|
|
|
1490 MS Windows: initial implementation, Jonathan Harris; some more work, Andy Piper, Ben Wing
|
|
|
1491 @item
|
|
|
1492 TTY: Chuck Thompson, Ben Wing
|
|
|
1493 @item
|
|
|
1494 Cygwin: Andy Piper
|
|
|
1495 @end itemize
|
|
|
1496
|
|
|
1497 @item Misc
|
|
|
1498 @itemize @minus
|
|
|
1499 @item
|
|
|
1500 Configure: initial porting from fsf, Chuck Thompson; conversion to autoconf 2, much rewriting, Martin Buchholz
|
|
|
1501 @item
|
|
|
1502 Most initialization-related code: Ben Wing
|
|
|
1503 @item
|
|
|
1504 Internals manual, much of Lisp manual: Ben Wing
|
|
|
1505 @item
|
|
|
1506 FSF synching: initial sync with FSF 19, Richard Mlynarik, further work, Ben Wing
|
|
|
1507 @end itemize
|
|
|
1508 @end table
|
|
|
1509
|
|
|
1510 @subheading SUPPORT
|
|
|
1511
|
|
|
1512 Currently, support duties are handled by many different people.
|
|
|
1513
|
|
|
1514 Release managers have been
|
|
|
1515
|
|
|
1516 @itemize @minus
|
|
|
1517 @item
|
|
|
1518 Stephen Turnbull (April 2001 - present, 21.x - 21.x?)
|
|
|
1519 @item
|
|
|
1520 Vin Shelton?
|
|
|
1521 @item
|
|
|
1522 Steve Youngs (July 2002 - present??, 21.x - 21.x?)
|
|
|
1523 @item
|
|
|
1524 Martin Buchholz (December 1998 - May 2001, 21.x - 21.x?)
|
|
|
1525 @item
|
|
|
1526 Steve Baur (early 1997 - November 1998, 19.15 - 21.0)
|
|
|
1527 @item
|
|
|
1528 Chuck Thompson (June 1994 - September 1996, 19.11 - 19.14)
|
|
|
1529 @item
|
|
|
1530 Jamie Zawinski (April 1991 - June 1994, 19.0 - 19.10)
|
|
|
1531 @end itemize
|
|
|
1532
|
|
|
1533 The recent overlapping dates are intentional, since two or three trees
|
|
|
1534 are maintained simultaneously at any point.
|
|
|
1535
|
|
|
1536 Other major support work:
|
|
|
1537
|
|
|
1538 @itemize @minus
|
|
|
1539 @item
|
|
|
1540 Adrian Aichner wrote and maintains the web site.
|
|
|
1541 @item
|
|
|
1542 Stephen Turnbull has produced many of the beta and semi-stable releases
|
|
|
1543 and has attempted to be the "face" of XEmacs on the newsgroups and
|
|
|
1544 mailing lists.
|
|
|
1545 @item
|
|
|
1546 Steve Youngs currently produces the beta releases (???).
|
|
|
1547 @item
|
|
|
1548 Steve Youngs, Ville Skytta, and now Norbert Koch have taken turns
|
|
|
1549 maintaining the packages.
|
|
|
1550 @item
|
|
|
1551 Vin Shelton maintains the stable releases.
|
|
|
1552 @item
|
|
|
1553 Testing - #### Norbert, Adrian, ???
|
|
|
1554 @end itemize
|
|
|
1555
|
|
|
1556 Portraits and email of some of the major developers:
|
|
428
|
1557
|
|
|
1558 @itemize @bullet
|
|
2417
|
1559 @item @email{andy@@xemacs.org, Andy Piper}
|
|
444
|
1560 @html
|
|
2418
|
1561 <br><img src="piper.png" alt="Portrait of Andy Piper"><br>
|
|
444
|
1562 @end html
|
|
428
|
1563
|
|
462
|
1564 @item @email{ben@@xemacs.org, Ben Wing}
|
|
444
|
1565 @html
|
|
2418
|
1566 <br><img src="ben.png" alt="Portrait of Ben Wing"><br>
|
|
444
|
1567 @end html
|
|
428
|
1568
|
|
|
1569 @item @email{cthomp@@xemacs.org, Chuck Thompson}
|
|
444
|
1570 @html
|
|
2418
|
1571 <br><img src="cthomp.png" alt="Portrait of Chuck Thompson"><br>
|
|
444
|
1572 @end html
|
|
428
|
1573
|
|
2417
|
1574 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
|
|
|
1575
|
|
|
1576 @html
|
|
2418
|
1577 <br><img src="hniksic.png" alt="Portrait of Hrvoje Niksic"><br>
|
|
2417
|
1578 @end html
|
|
|
1579
|
|
428
|
1580 @item @email{jwz@@jwz.org, Jamie Zawinski}
|
|
444
|
1581 @html
|
|
2418
|
1582 <br><img src="jwz.png" alt="Portrait of Jamie Zawinski"><br>
|
|
444
|
1583 @end html
|
|
428
|
1584
|
|
2417
|
1585 @item @email{martin@@xemacs.org, Martin Buchholz}
|
|
|
1586 @html
|
|
2418
|
1587 <br><img src="martin.png" alt="Portrait of Martin Buchholz"><br>
|
|
2417
|
1588 @end html
|
|
|
1589
|
|
428
|
1590 @item @email{mly@@adoc.xerox.com, Richard Mlynarik}
|
|
2418
|
1591 @html
|
|
|
1592 <br><img src="mly.png" alt="Portrait of Richard Mlynarik"><br>
|
|
|
1593 @end html
|
|
462
|
1594
|
|
2417
|
1595 @item @email{stephen@@xemacs.org, Stephen Turnbull}
|
|
|
1596
|
|
|
1597 @item @email{steve@@xemacs.org, Steve Baur}
|
|
|
1598 @html
|
|
2418
|
1599 <br><img src="slb.png" alt="Portrait of Steve Baur"><br>
|
|
2417
|
1600 @end html
|
|
428
|
1601 @end itemize
|
|
|
1602
|
|
2417
|
1603 Many other people have contributed to XEmacs; this is partially
|
|
|
1604 enumerated in the @samp{About XEmacs} option in the Help menu.
|
|
|
1605
|
|
|
1606 @node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
|
|
|
1607 @unnumberedsubsec Q1.3.2: Who contributed to this version of the FAQ?
|
|
|
1608
|
|
|
1609 The current version of this FAQ was created by @email{ben@@xemacs.org,
|
|
|
1610 Ben Wing}.
|
|
|
1611
|
|
|
1612 @node Q1.3.3, Q1.4.1, Q1.3.2, Introduction
|
|
|
1613 @unnumberedsubsec Q1.3.3: Who contributed to the FAQ in the past?
|
|
|
1614
|
|
|
1615 This is only a partial list, as many names were lost in a hard disk
|
|
|
1616 crash some time ago.
|
|
428
|
1617
|
|
|
1618 @itemize @bullet
|
|
|
1619 @item @email{steve@@xemacs.org, SL Baur}
|
|
|
1620
|
|
|
1621 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
|
|
|
1622
|
|
|
1623 @item @email{binge@@aloft.att.com, Curtis.N.Bingham}
|
|
|
1624
|
|
438
|
1625 @item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan}
|
|
|
1626
|
|
428
|
1627 @item @email{rjc@@cogsci.ed.ac.uk, Richard Caley}
|
|
|
1628
|
|
|
1629 @item @email{cognot@@ensg.u-nancy.fr, Richard Cognot}
|
|
|
1630
|
|
438
|
1631 @item @email{daku@@nortel.ca, Mark Daku}
|
|
|
1632
|
|
428
|
1633 @item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque}
|
|
|
1634
|
|
|
1635 @item @email{eeide@@cs.utah.edu, Eric Eide}
|
|
|
1636
|
|
438
|
1637 @item @email{af@@biomath.jussieu.fr, Alain Fauconnet}
|
|
|
1638
|
|
428
|
1639 @item @email{cflatter@@nrao.edu, Chris Flatters}
|
|
|
1640
|
|
|
1641 @item @email{ginsparg@@adra.com, Evelyn Ginsparg}
|
|
|
1642
|
|
|
1643 @item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall}
|
|
|
1644
|
|
|
1645 @item @email{dkindred@@cmu.edu, Darrell Kindred}
|
|
|
1646
|
|
|
1647 @item @email{dmoore@@ucsd.edu, David Moore}
|
|
|
1648
|
|
|
1649 @item @email{arup+@@cmu.edu, Arup Mukherjee}
|
|
|
1650
|
|
|
1651 @item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen}
|
|
|
1652
|
|
|
1653 @item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell}
|
|
|
1654
|
|
|
1655 @item @email{dworkin@@ccs.neu.edu, Justin Sheehy}
|
|
|
1656
|
|
|
1657 @item @email{stig@@hackvan.com, Stig}
|
|
|
1658
|
|
|
1659 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
|
|
|
1660 @end itemize
|
|
|
1661
|
|
2417
|
1662 @unnumberedsec 1.4: Internationalization
|
|
|
1663
|
|
|
1664 @node Q1.4.1, Q1.4.2, Q1.3.3, Introduction
|
|
2459
|
1665 @unnumberedsubsec Q1.4.1: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
442
|
1666
|
|
|
1667 Both the stable and development versions of XEmacs include
|
|
1135
|
1668 internationalization support (aka MULE). MULE currently (21.4) works on
|
|
|
1669 UNIX and Linux systems. It is possible to build with MULE on Windows
|
|
|
1670 systems, but if you really need MULE on Windows, it is recommended that
|
|
|
1671 you build and use the development (21.5) version, and deal with the
|
|
|
1672 instability of the development tree. Binaries compiled without MULE
|
|
|
1673 support run faster than MULE capable XEmacsen.
|
|
428
|
1674
|
|
2417
|
1675 @node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
|
|
|
1676 @unnumberedsubsec Q1.4.2: How can I help with internationalization?
|
|
430
|
1677
|
|
|
1678 If you would like to help, you may want to join the
|
|
|
1679 @email{xemacs-mule@@xemacs.org} mailing list. Especially needed are
|
|
|
1680 people who speak/write languages other than English, who are willing to
|
|
|
1681 use XEmacs/MULE regularly, and have some experience with Elisp.
|
|
428
|
1682
|
|
1135
|
1683 Translations of the TUTORIAL and man page are welcome, and XEmacs does
|
|
|
1684 support multilingual menus, but we have few current translations.
|
|
|
1685
|
|
2417
|
1686 @xref{Q1.2.2, How do I become a Beta Tester?}.
|
|
|
1687
|
|
|
1688 @node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
|
|
|
1689 @unnumberedsubsec Q1.4.3: How do I type non-ASCII characters?
|
|
|
1690
|
|
2459
|
1691 @xref{Q3.0.6, How can you type in special characters in XEmacs?}, in
|
|
2417
|
1692 part 3 of this FAQ, for some simple methods that also work in non-MULE
|
|
|
1693 builds of XEmacs (but only for one-octet coded character sets, and
|
|
|
1694 mostly for ISO 8859/1). Many of the methods available for Cyrillic
|
|
|
1695 (@pxref{Q1.4.7, How about Cyrillic modes?}) work without MULE. MULE
|
|
|
1696 has more general capabilities. @xref{Q1.4.5, Please explain the
|
|
|
1697 various input methods in MULE/XEmacs}.
|
|
|
1698
|
|
2459
|
1699 @xref{Q4.0.8, How do I display non-ASCII characters?}, which covers
|
|
2417
|
1700 display of non-ASCII characters.
|
|
|
1701
|
|
|
1702 @node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
|
|
|
1703 @unnumberedsubsec Q1.4.4: Can XEmacs messages come out in a different language?
|
|
428
|
1704
|
|
1135
|
1705 The message-catalog support was written but is badly bit-rotted. XEmacs
|
|
|
1706 20 and 21 did @emph{not} support it, and early releases of XEmacs 22
|
|
|
1707 will not either.
|
|
|
1708
|
|
|
1709 However, menubar localization @emph{does} work. To enable it, add to
|
|
|
1710 your @file{Emacs} file entries like this:
|
|
428
|
1711
|
|
|
1712 @example
|
|
440
|
1713 Emacs*XlwMenu.resourceLabels: True
|
|
|
1714 Emacs*XlwMenu.file.labelString: Fichier
|
|
442
|
1715 Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster oeffnen
|
|
428
|
1716 @end example
|
|
|
1717
|
|
|
1718 The name of the resource is derived from the non-localized entry by
|
|
|
1719 removing punctuation and capitalizing as above.
|
|
|
1720
|
|
2417
|
1721 @node Q1.4.5, Q1.4.6, Q1.4.4, Introduction
|
|
|
1722 @unnumberedsubsec Q1.4.5: Please explain the various input methods in MULE/XEmacs
|
|
428
|
1723
|
|
1135
|
1724 Mule supports a wide variety of input methods. There are three basic
|
|
|
1725 classes: Lisp implementations, generic platform support, and library
|
|
|
1726 interfaces.
|
|
|
1727
|
|
|
1728 @emph{Lisp implementations} include Quail, which provides table-driven input
|
|
|
1729 methods for almost all the character sets that Mule supports (including
|
|
|
1730 all of the ISO 8859 family, the Indic languages, Thai, and so on), and
|
|
|
1731 SKK, for Japanese. (SKK also supports an interface to an external
|
|
|
1732 "dictionary server" process.) Quail supports both typical "dead-key"
|
|
|
1733 methods (eg, in the "latin-1-prefix" method, @kbd{" a} produces ä, LATIN
|
|
|
1734 SMALL LETTER A WITH DIAERESIS), and the complex dictionary-based phonetic
|
|
|
1735 methods used for Asian ideographic languages like Chinese.
|
|
|
1736
|
|
|
1737 Lisp implementations can be less powerful (but they are not perceptibly
|
|
|
1738 inefficient), and of course are not portable to non-Emacs applications.
|
|
|
1739 The incompatibility can be very annoying. On the other hand, they
|
|
|
1740 require no special platform support or external libraries, so if you can
|
|
|
1741 display the characters, Mule can input them for you and you can edit,
|
|
|
1742 anywhere.
|
|
|
1743
|
|
|
1744 @emph{Generic platform support} is currently limited to the X Input
|
|
|
1745 Method (XIM) framework, although support for MSIME (for MS Windows) is
|
|
|
1746 planned, and IIIMF (Sun's Internet-Intranet Input Method Framework)
|
|
|
1747 support is extremely desirable. XIM is enabled at build time by use of
|
|
|
1748 the @samp{--with-xim} flag to @code{configure}. For use of XIM, see
|
|
|
1749 your platform documentation. However, normally the input method you use
|
|
|
1750 is specified via the @samp{LANG} and @samp{XMODIFIERS} environment
|
|
|
1751 variables.
|
|
|
1752
|
|
|
1753 Of course, input skills are portable across most applications. However,
|
|
|
1754 especially in modern GUI systems the habit of using bucky bits has
|
|
|
1755 fallen into sad disuse, and many XIM systems are poorly configured for
|
|
|
1756 use with Emacs. For example, the kinput2 input manager (a separate
|
|
|
1757 process providing an interface between Japanese dictionary servers such
|
|
|
1758 as Canna and Wnn, and the application) tends to gobble up keystrokes
|
|
|
1759 generating Meta characters. This means that to edit while using an XIM
|
|
|
1760 input method, you must toggle the input method off every time you want
|
|
|
1761 to use @kbd{M-f}. Your mileage may vary.
|
|
|
1762
|
|
|
1763 @emph{Library interfaces} are most common for Japanese, although Wnn
|
|
|
1764 supports Chinese (traditional and simplified) and Korean. There are
|
|
|
1765 Chinese and Korean input servers available, but we do not know of any
|
|
|
1766 patches for XEmacs to use them directly. You can use them via
|
|
|
1767 IM-enabled terminals, by manipulating the terminal coding systems. We
|
|
|
1768 describe only the Japanese-oriented systems here. The advantage of
|
|
|
1769 these systems is that they are very powerful, and on platforms where
|
|
|
1770 they are available there is typically a wide range of applications that
|
|
|
1771 support them. Thus your input skills are portable across applications.
|
|
|
1772
|
|
|
1773 Mule provides built-in interfaces to the following input methods: Wnn4,
|
|
|
1774 Wnn6, Canna, and SJ3. These can be configured at build time. There are
|
|
|
1775 patches available (no URL, sorry) to support the SKK server, as well.
|
|
|
1776 Wnn and SJ3 use the @code{egg} user interface. The interface for Canna
|
|
|
1777 is specialized to Canna.
|
|
428
|
1778
|
|
|
1779 Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
|
|
1135
|
1780 University. It is a powerful and complex system. Wnn4 is free and Wnn6
|
|
|
1781 is not. Wnn uses grammatical hints and probability of word association,
|
|
|
1782 so in principle Wnn can be cleverer than other methods.
|
|
|
1783
|
|
|
1784 Canna, made by NEC, supports only Japanese. It is a simple and powerful
|
|
|
1785 system. Canna uses only grammar, but its grammar and dictionary are
|
|
|
1786 quite sophisticated. So for standard modern Japanese, Canna seems
|
|
|
1787 cleverer than Wnn4. In addition, the UNIX version of Canna is free (now
|
|
|
1788 there is a Microsoft Windows version).
|
|
|
1789
|
|
|
1790 SJ3, by Sony, supports only Japanese.
|
|
428
|
1791
|
|
|
1792 Egg consists of following parts:
|
|
|
1793
|
|
|
1794 @enumerate
|
|
|
1795 @item
|
|
|
1796 Input character Translation System (ITS) layer.
|
|
|
1797 It translates ASCII inputs to Kana/PinYin/Hangul characters.
|
|
|
1798
|
|
|
1799 @item
|
|
|
1800 Kana/PinYin/Hangul to Kanji transfer layer.
|
|
1135
|
1801 The interface layer to network Kana-Kanji server (Wnn and Sj3).
|
|
428
|
1802 @end enumerate
|
|
|
1803
|
|
1135
|
1804 These input methods are modal. They have a raw (alphabet) mode, a
|
|
|
1805 phonetic input mode, and Kana-Kanji transfer mode. However there are
|
|
|
1806 mode-less input methods for Egg and Canna. @samp{boiled-egg} is a
|
|
|
1807 mode-less input method running on Egg. For Canna, @samp{canna.el} has a
|
|
|
1808 tiny boiled-egg-like command, @code{(canna-boil)}, and there are some
|
|
|
1809 boiled-egg-like utilities.
|
|
|
1810
|
|
|
1811 Much of this information was provided by @email{morioka@@jaist.ac.jp,
|
|
|
1812 MORIOKA Tomohiko}.
|
|
428
|
1813
|
|
2417
|
1814 @node Q1.4.6, Q1.4.7, Q1.4.5, Introduction
|
|
|
1815 @unnumberedsubsec Q1.4.6: How do I portably code for MULE/XEmacs?
|
|
428
|
1816
|
|
1135
|
1817 MULE has evolved rapidly over the last few years, and the original third
|
|
|
1818 party patch (for GNU Emacs 19), GNU Emacs 20+, and XEmacs 20+ have quite
|
|
|
1819 different implementations. The APIs also vary although recent versions
|
|
|
1820 of XEmacs have tended to converge to the GNU Emacs standard.
|
|
|
1821
|
|
|
1822 MULE implementations are going to continue to evolve. Both GNU Emacs
|
|
|
1823 and XEmacs are working hard on Unicode support, which will involve new
|
|
|
1824 APIs and probably variations on old ones. For XEmacs 22, the old ISO
|
|
|
1825 2022-based system for recognizing encodings will be replaced by a much
|
|
|
1826 more flexible system, which should improve accuracy of automatic coding
|
|
|
1827 detections, but will also involve new APIs.
|
|
|
1828
|
|
428
|
1829 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
|
|
|
1830
|
|
|
1831 @quotation
|
|
1135
|
1832 The application implementor must write separate code for these mule
|
|
|
1833 variants. [Please don't hesitate to report these variants to us; they
|
|
|
1834 are not, strictly speaking, bugs, but they give third-party developers
|
|
|
1835 the same kind of creepy-crawly feeling. We'll do what we can. -- Ed.]
|
|
428
|
1836
|
|
|
1837 MULE and the next version of Emacs are similar but the symbols are very
|
|
|
1838 different---requiring separate code as well.
|
|
|
1839
|
|
|
1840 Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of
|
|
|
1841 emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called
|
|
1135
|
1842 @code{emu} to provide a common interface. [There is an XEmacs package
|
|
|
1843 of APEL which provides much more comprehensive coverage. Be careful,
|
|
|
1844 however; APEL has problems of its own. -- Ed.]
|
|
428
|
1845
|
|
|
1846 I have the following suggestions about dealing with mule variants:
|
|
|
1847
|
|
|
1848 @itemize @bullet
|
|
|
1849 @item
|
|
|
1850 @code{(featurep 'mule)} @code{t} on all mule variants
|
|
|
1851
|
|
|
1852 @item
|
|
|
1853 @code{(boundp 'MULE)} is @code{t} on only MULE. Maybe the next version
|
|
|
1854 of Emacs will not have this symbol.
|
|
|
1855
|
|
|
1856 @item
|
|
|
1857 MULE has a variable @code{mule-version}. Perhaps the next version of
|
|
|
1858 Emacs will have this variable as well.
|
|
|
1859 @end itemize
|
|
|
1860
|
|
|
1861 Following is a sample to distinguish mule variants:
|
|
|
1862
|
|
|
1863 @lisp
|
|
|
1864 (if (featurep 'mule)
|
|
|
1865 (cond ((boundp 'MULE)
|
|
|
1866 ;; for original Mule
|
|
|
1867 )
|
|
440
|
1868 ((string-match "XEmacs" emacs-version)
|
|
|
1869 ;; for XEmacs with Mule
|
|
|
1870 )
|
|
|
1871 (t
|
|
|
1872 ;; for next version of Emacs
|
|
|
1873 ))
|
|
428
|
1874 ;; for old emacs variants
|
|
|
1875 )
|
|
|
1876 @end lisp
|
|
|
1877 @end quotation
|
|
|
1878
|
|
2417
|
1879 @node Q1.4.7, Q1.4.8, Q1.4.6, Introduction
|
|
|
1880 @unnumberedsubsec Q1.4.7: How about Cyrillic modes?
|
|
428
|
1881
|
|
|
1882 @email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes:
|
|
|
1883
|
|
|
1884 @quotation
|
|
|
1885 There is a cyrillic mode in the file @file{mysetup.zip} in
|
|
|
1886 @iftex
|
|
|
1887 @*
|
|
|
1888 @end iftex
|
|
|
1889 @uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}. This is a
|
|
|
1890 modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el}
|
|
|
1891 which can be obtained from
|
|
|
1892 @end quotation
|
|
|
1893
|
|
871
|
1894 @uref{http://www.math.uga.edu/~valery/russian.el}.
|
|
428
|
1895
|
|
|
1896 @email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes:
|
|
|
1897
|
|
|
1898 @quotation
|
|
|
1899 There is another cyrillic mode for both GNU Emacs and XEmacs by
|
|
|
1900 @email{manin@@camelot.mssm.edu, Dmitrii
|
|
|
1901 (Mitya) Manin} at
|
|
|
1902 @iftex
|
|
|
1903
|
|
|
1904 @end iftex
|
|
|
1905 @uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}.
|
|
|
1906 @c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead.
|
|
|
1907 @c Changed to russian host instead
|
|
|
1908 @end quotation
|
|
|
1909
|
|
|
1910 @email{rebecca.ore@@op.net, Rebecca Ore} writes:
|
|
|
1911
|
|
|
1912 @quotation
|
|
|
1913 The fullest resource I found on Russian language use (in and out of
|
|
661
|
1914 XEmacs) is @uref{http://www.ibiblio.org/sergei/Software/Software.html}
|
|
428
|
1915 @end quotation
|
|
|
1916
|
|
2417
|
1917 @node Q1.4.8, Q1.4.9, Q1.4.7, Introduction
|
|
|
1918 @unnumberedsubsec Q1.4.8: Does XEmacs support Unicode?
|
|
|
1919
|
|
|
1920 To get Unicode support, you need a Mule-enabled XEmacs.
|
|
|
1921
|
|
|
1922 21.5 has internal support for Unicode and supports it fully, although we
|
|
|
1923 don't yet use it as the internal encoding.
|
|
|
1924
|
|
|
1925 21.4 supports Unicode partially -- as an external encoding for files,
|
|
|
1926 processes, and terminals, but without font support. @xref{Q1.4.9, How
|
|
|
1927 does XEmacs display Unicode?}. To get Unicode support in 21.4,
|
|
|
1928 install Mule-UCS from packages in the usual way, and put
|
|
745
|
1929
|
|
1616
|
1930 @example
|
|
745
|
1931 (require 'un-define)
|
|
|
1932 (set-coding-priority-list '(utf-8))
|
|
1616
|
1933 (set-coding-category-system 'utf-8 'utf-8)
|
|
|
1934 @end example
|
|
|
1935
|
|
|
1936 in your init file to enable the UTF-8 coding system. You may wish to
|
|
|
1937 view the documentation of @code{set-coding-priority-list} if you find
|
|
|
1938 that files that are not UTF-8 are being mis-recognized as UTF-8.
|
|
745
|
1939
|
|
2417
|
1940 Install standard national fonts (not Unicode fonts) for all character
|
|
|
1941 sets you use. @xref{Q1.4.9, How does XEmacs display Unicode??}.
|
|
745
|
1942
|
|
|
1943 Mule-UCS also supports 16-bit forms of Unicode (UTF-16). It does not
|
|
|
1944 support 31-bit forms of Unicode (UTF-32 or UCS-4).
|
|
|
1945
|
|
2417
|
1946 @node Q1.4.9, Q1.5.1, Q1.4.8, Introduction
|
|
|
1947 @unnumberedsubsec Q1.4.9: How does XEmacs display Unicode?
|
|
745
|
1948
|
|
|
1949 Mule doesn't have a Unicode charset internally, so there's nothing to
|
|
|
1950 bind a Unicode registry to. It would not be straightforward to create,
|
|
|
1951 either, because Unicode is not ISO 2022-compatible. You'd have to
|
|
|
1952 translate it to multiple 96x96 pages.
|
|
|
1953
|
|
|
1954 This means that Mule-UCS uses ordinary national fonts for display. This
|
|
|
1955 is not really a problem, except for those languages that use the Unified
|
|
|
1956 Han characters. The problem here is that Mule-UCS maps from Unicode
|
|
|
1957 code points to national character sets in a deterministic way. By
|
|
|
1958 default, this means that Japanese fonts are tried first, then Chinese,
|
|
|
1959 then Korean. To change the priority ordering, use the command
|
|
|
1960 `un-define-change-charset-order'.
|
|
|
1961
|
|
|
1962 It also means you can't use Unicode fonts directly, at least not without
|
|
|
1963 extreme hackery. You can run -nw with (set-terminal-coding-system
|
|
|
1964 'utf-8) if you really want a Unicode font for some reason.
|
|
|
1965
|
|
|
1966 Real Unicode support will be introduced in XEmacs 22.0.
|
|
|
1967
|
|
2417
|
1968 @unnumberedsec 1.5: Getting Started
|
|
|
1969
|
|
|
1970 @node Q1.5.1, Q1.5.2, Q1.4.9, Introduction
|
|
|
1971 @unnumberedsubsec Q1.5.1: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
462
|
1972
|
|
|
1973 The @file{init.el} or @file{.emacs} file is used to customize XEmacs to
|
|
|
1974 your tastes. Starting in 21.4, the preferred location for the init file
|
|
|
1975 is @file{~/.xemacs/init.el}; in previous versions, it was
|
|
|
1976 @file{~/.emacs}. 21.4 still accepts the old location, but the first
|
|
|
1977 time you run it, it will ask to migrate your file to the new location.
|
|
|
1978 If you answer yes, the file will be moved, and a "compatibility"
|
|
|
1979 @file{.emacs} file will be placed in the old location so that you can
|
|
|
1980 still run older versions of XEmacs, and versions of GNU Emacs, which
|
|
|
1981 expect the old location. The @file{.emacs} file present is just a stub
|
|
|
1982 that loads the real file in @file{~/.xemacs/init.el}.
|
|
|
1983
|
|
|
1984 No two init files are alike, nor are they expected to be alike, but
|
|
|
1985 that's the point. The XEmacs distribution contains an excellent starter
|
|
|
1986 example in the @file{etc/} directory called @file{sample.init.el}
|
|
|
1987 (starting in 21.4) or @file{sample.emacs} in older versions. Copy this
|
|
|
1988 file from there to @file{~/.xemacs/init.el} (starting in 21.4) or
|
|
|
1989 @file{~/.emacs} in older versions, where @samp{~} means your home
|
|
|
1990 directory, of course. Then edit it to suit.
|
|
|
1991
|
|
|
1992 You may bring the @file{sample.init.el} or @file{sample.emacs} file into
|
|
|
1993 an XEmacs buffer from the menubar. (The menu entry for it is always
|
|
|
1994 under the @samp{Help} menu, but its location under that has changed in
|
|
|
1995 various versions. Recently, look under the @samp{Samples} submenu.) To
|
|
|
1996 determine the location of the @file{etc/} directory type the command
|
|
428
|
1997 @kbd{C-h v data-directory @key{RET}}.
|
|
|
1998
|
|
2417
|
1999 @node Q1.5.2, Q1.5.3, Q1.5.1, Introduction
|
|
|
2000 @unnumberedsubsec Q1.5.2: Where do I put my @file{init.el} file?
|
|
|
2001
|
|
|
2002 @file{init.el} is the name of the init file starting with 21.4, and is
|
|
|
2003 located in the subdirectory @file{.xemacs/} of your home directory. In
|
|
|
2004 prior versions, the init file is called @file{.emacs} and is located in
|
|
|
2005 your home directory.
|
|
|
2006
|
|
|
2007 Your home directory under Windows is determined by the @samp{HOME}
|
|
|
2008 environment variable. If this is not set, it defaults to @samp{C:\}.
|
|
|
2009 To set this variable, modify @file{AUTOEXEC.BAT} under Windows 95/98, or
|
|
|
2010 select @samp{Control Panel->System->Advanced->Environment Variables...}
|
|
|
2011 under Windows NT/2000.
|
|
|
2012
|
|
|
2013 @node Q1.5.3, Q1.5.4, Q1.5.2, Introduction
|
|
|
2014 @unnumberedsubsec Q1.5.3: Can I use the same @file{init.el} with the other Emacs?
|
|
|
2015
|
|
|
2016 Yes. The sample @file{init.el} included in the XEmacs
|
|
462
|
2017 distribution will show you how to handle different versions and flavors
|
|
|
2018 of Emacs.
|
|
428
|
2019
|
|
2417
|
2020 @node Q1.5.4, Q1.5.5, Q1.5.3, Introduction
|
|
|
2021 @unnumberedsubsec Q1.5.4: Any good XEmacs tutorials around?
|
|
428
|
2022
|
|
|
2023 There's the XEmacs tutorial available from the Help Menu under
|
|
2417
|
2024 @samp{Help->Tutorials}, or by typing @kbd{C-h t}. To check whether
|
|
428
|
2025 it's available in a non-english language, type @kbd{C-u C-h t TAB}, type
|
|
|
2026 the first letters of your preferred language, then type @key{RET}.
|
|
|
2027
|
|
430
|
2028 @comment There's an Emacs Lisp tutorial at
|
|
438
|
2029 @comment
|
|
430
|
2030 @comment @example
|
|
|
2031 @comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
|
|
|
2032 @comment @end example
|
|
438
|
2033 @comment
|
|
430
|
2034 @comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
|
|
|
2035 @comment page at
|
|
|
2036 @comment @iftex
|
|
|
2037 @comment @*
|
|
|
2038 @comment @end iftex
|
|
|
2039 @comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}.
|
|
428
|
2040
|
|
2417
|
2041 @node Q1.5.5, Q1.5.6, Q1.5.4, Introduction
|
|
|
2042 @unnumberedsubsec Q1.5.5: May I see an example of a useful XEmacs Lisp function?
|
|
428
|
2043
|
|
|
2044 The following function does a little bit of everything useful. It does
|
|
|
2045 something with the prefix argument, it examines the text around the
|
|
|
2046 cursor, and it's interactive so it may be bound to a key. It inserts
|
|
|
2047 copies of the current word the cursor is sitting on at the cursor. If
|
|
|
2048 you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will
|
|
|
2049 insert 3 copies.
|
|
|
2050
|
|
|
2051 @lisp
|
|
|
2052 (defun double-word (count)
|
|
|
2053 "Insert a copy of the current word underneath the cursor"
|
|
|
2054 (interactive "*p")
|
|
|
2055 (let (here there string)
|
|
|
2056 (save-excursion
|
|
|
2057 (forward-word -1)
|
|
|
2058 (setq here (point))
|
|
|
2059 (forward-word 1)
|
|
|
2060 (setq there (point))
|
|
|
2061 (setq string (buffer-substring here there)))
|
|
|
2062 (while (>= count 1)
|
|
|
2063 (insert string)
|
|
|
2064 (decf count))))
|
|
|
2065 @end lisp
|
|
|
2066
|
|
|
2067 The best way to see what is going on here is to let XEmacs tell you.
|
|
|
2068 Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor
|
|
|
2069 sitting just to the right of the function you want explained. Eg. move
|
|
|
2070 the cursor to the SPACE between @code{interactive} and @samp{"*p"} and
|
|
|
2071 hit @kbd{C-h f} to see what the function @code{interactive} does. Doing
|
|
|
2072 this will tell you that the @code{*} requires a writable buffer, and
|
|
|
2073 @code{p} converts the prefix argument to a number, and
|
|
|
2074 @code{interactive} allows you to execute the command with @kbd{M-x}.
|
|
|
2075
|
|
2417
|
2076 @node Q1.5.6, Q1.5.7, Q1.5.5, Introduction
|
|
|
2077 @unnumberedsubsec Q1.5.6: And how do I bind it to a key?
|
|
428
|
2078
|
|
|
2079 To bind to a key do:
|
|
|
2080
|
|
|
2081 @lisp
|
|
|
2082 (global-set-key "\C-cd" 'double-word)
|
|
|
2083 @end lisp
|
|
|
2084
|
|
|
2085 Or interactively, @kbd{M-x global-set-key} and follow the prompts.
|
|
|
2086
|
|
2417
|
2087 @node Q1.5.7, Q1.5.8, Q1.5.6, Introduction
|
|
|
2088 @unnumberedsubsec Q1.5.7: What's the difference between a macro and a function?
|
|
428
|
2089
|
|
|
2090 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual:
|
|
|
2091
|
|
|
2092 @dfn{Macros} enable you to define new control constructs and other
|
|
|
2093 language features. A macro is defined much like a function, but instead
|
|
|
2094 of telling how to compute a value, it tells how to compute another Lisp
|
|
|
2095 expression which will in turn compute the value. We call this
|
|
|
2096 expression the @dfn{expansion} of the macro.
|
|
|
2097
|
|
|
2098 Macros can do this because they operate on the unevaluated expressions
|
|
|
2099 for the arguments, not on the argument values as functions do. They can
|
|
|
2100 therefore construct an expansion containing these argument expressions
|
|
|
2101 or parts of them.
|
|
|
2102
|
|
|
2103 Do not confuse the two terms with @dfn{keyboard macros}, which are
|
|
|
2104 another matter, entirely. A keyboard macro is a key bound to several
|
|
|
2105 other keys. Refer to manual for details.
|
|
|
2106
|
|
2417
|
2107 @node Q1.5.8, , Q1.5.7, Introduction
|
|
|
2108 @unnumberedsubsec Q1.5.8: What is @code{Custom}?
|
|
|
2109
|
|
|
2110 @code{Custom} is a system for customizing XEmacs options.
|
|
|
2111
|
|
|
2112 You can access @code{Advanced (Customize)} from the @code{Options} menu
|
|
|
2113 or invoking one of customize commands by typing eg.
|
|
|
2114 @kbd{M-x customize}, @kbd{M-x customize-face},
|
|
|
2115 @kbd{M-x customize-variable} or @kbd{M-x customize-apropos}.
|
|
|
2116
|
|
|
2117 There is also new @samp{browser} mode for Customize.
|
|
|
2118 Try it out with @kbd{M-x customize-browse}
|
|
|
2119
|
|
2459
|
2120 @node Installation, Editing, Introduction, Top
|
|
2417
|
2121 @unnumbered 2 Installation and Troubleshooting
|
|
428
|
2122
|
|
|
2123 This is part 2 of the XEmacs Frequently Asked Questions list. This
|
|
2417
|
2124 section is devoted to Installation, Maintenance and Troubleshooting.
|
|
428
|
2125
|
|
|
2126 @menu
|
|
2417
|
2127 2.0: Installation (General), Packages
|
|
|
2128 * Q2.0.1:: How do I install the packages?
|
|
|
2129 * Q2.0.2:: I don't need no steenkin' packages. Do I?
|
|
|
2130 * Q2.0.3:: Where do I find external libraries?
|
|
|
2131 * Q2.0.4:: How do I specify the paths that XEmacs uses for finding files?
|
|
|
2132 * Q2.0.5:: Running XEmacs without installing
|
|
|
2133 * Q2.0.6:: XEmacs is too big
|
|
|
2134 * Q2.0.7:: EFS fails with "500 AUTH not understood" (NEW)
|
|
|
2135
|
|
|
2136 2.1: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
|
2137 * Q2.1.1:: Libraries in non-standard locations
|
|
|
2138 * Q2.1.2:: Why can't I strip XEmacs?
|
|
|
2139
|
|
|
2140 2.2: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
2141 * Q2.2.1:: What exactly are all the different ways to build XEmacs under Windows?
|
|
|
2142 * Q2.2.2:: What compiler/libraries do I need to compile XEmacs?
|
|
|
2143 * Q2.2.3:: How do I compile the native port?
|
|
|
2144 * Q2.2.4:: What do I need for Cygwin?
|
|
|
2145 * Q2.2.5:: How do I compile under Cygwin?
|
|
|
2146 * Q2.2.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
|
2147 * Q2.2.7:: How do I compile with X support?
|
|
|
2148 * Q2.2.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
|
2149
|
|
|
2150 2.3: General Troubleshooting
|
|
|
2151 * Q2.3.1:: Help! XEmacs just crashed on me!
|
|
|
2152 * Q2.3.2:: XEmacs crashes and I compiled it myself.
|
|
|
2153 * Q2.3.3:: How to debug an XEmacs problem with a debugger
|
|
|
2154 * Q2.3.4:: I get a cryptic error message when trying to do something.
|
|
|
2155 * Q2.3.5:: XEmacs hangs when I try to do something.
|
|
|
2156 * Q2.3.6:: I get an error message when XEmacs is running in batch mode.
|
|
|
2157 * Q2.3.7:: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
|
2158 * Q2.3.8:: @kbd{C-g} doesn't work for me. Is it broken?
|
|
|
2159 * Q2.3.9:: How do I debug process-related problems?
|
|
|
2160 * Q2.3.10:: XEmacs is outputting lots of X errors.
|
|
|
2161 * Q2.3.11:: After upgrading, XEmacs won't do `foo' any more!
|
|
|
2162
|
|
|
2163 2.4: Startup-Related Problems
|
|
|
2164 * Q2.4.1:: XEmacs cannot connect to my X Terminal!
|
|
|
2165 * Q2.4.2:: XEmacs won't start on Windows.
|
|
|
2166 * Q2.4.3:: XEmacs won't start without network.
|
|
|
2167 * Q2.4.4:: Startup warnings about deducing proper fonts?
|
|
|
2168 * Q2.4.5:: Warnings from incorrect key modifiers.
|
|
|
2169 * Q2.4.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
428
|
2170 @end menu
|
|
|
2171
|
|
2417
|
2172 @unnumberedsec 2.0: Installation (General), Packages
|
|
|
2173
|
|
428
|
2174 @node Q2.0.1, Q2.0.2, Installation, Installation
|
|
2417
|
2175 @unnumberedsubsec Q2.0.1: How do I install the packages?
|
|
|
2176
|
|
|
2177 Many people really liked the old way that packages were bundled and do
|
|
|
2178 not want to mess with packages at all. You can grab all the packages at
|
|
|
2179 once like you used to with old XEmacs versions. Download the file
|
|
|
2180
|
|
|
2181 @file{xemacs-sumo.tar.gz}
|
|
|
2182
|
|
|
2183 For an XEmacs compiled with Mule you also need
|
|
|
2184
|
|
|
2185 @file{xemacs-mule-sumo.tar.gz}
|
|
|
2186
|
|
|
2187 These are in the @file{packages} directory on your XEmacs mirror
|
|
|
2188 archive. N.B. They are called 'Sumo Tarballs' for good reason. They
|
|
|
2189 are currently about 15MB and 2.3MB (gzipped) respectively.
|
|
|
2190
|
|
|
2191 Install them on Unix and Mac OS X using the shell/Terminal command
|
|
|
2192
|
|
|
2193 @code{cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xf -}
|
|
|
2194
|
|
|
2195 Where @samp{$prefix} is what you gave to the @samp{--prefix} flag to
|
|
|
2196 @file{configure}, and defaults to @file{/usr/local}.
|
|
|
2197
|
|
|
2198 If you have the packages somewhere nonstandard and don't want to
|
|
|
2199 bother with @samp{$prefix} (for example, you're a developer and are
|
|
|
2200 compiling the packages yourself, and want your own private copy of
|
|
|
2201 everything), you can also directly specify this using @file{configure}.
|
|
|
2202 To do this under 21.5 and above use the @samp{--package-prefix} parameter
|
|
|
2203 to specify the directory under which you untarred the above tarballs.
|
|
|
2204 Under 21.4 and previous you need to use @samp{--package-path},
|
|
|
2205 something like this:
|
|
|
2206
|
|
|
2207 @example
|
|
|
2208 configure --package-path="~/.xemacs::/src/xemacs/site-packages:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages" ...
|
|
|
2209 @end example
|
|
|
2210
|
|
|
2211 Under Windows, you need to place the above @samp{tar.gz} files in the
|
|
|
2212 directory specified using the @samp{PACKAGE_PREFIX} value in
|
|
|
2213 @file{nt/config.inc} and by default is @file{\Program Files\XEmacs}.
|
|
|
2214 (To untar a @samp{tar.gz} file you will need to use a utility such as
|
|
|
2215 WinZip, unless you have Cygwin or a similar environment installed, in
|
|
|
2216 which case the above Unix shell command should work fine.) If you want
|
|
|
2217 the packages somewhere else, just change @samp{PACKAGE_PREFIX}.
|
|
|
2218
|
|
|
2219 Note that XEmacs finds the packages automatically anywhere underneath
|
|
|
2220 the directory tree where it expects to find the packages. All you
|
|
|
2221 need to do is put stuff there; you don't need to run any program to
|
|
|
2222 tell XEmacs to find the packges, or do anything of that sort.
|
|
|
2223
|
|
|
2224 See @file{README.packages} in the top-level source directory for more
|
|
|
2225 detailed installation instructions.
|
|
|
2226
|
|
|
2227 As the Sumo tarballs are not regenerated as often as the individual
|
|
|
2228 packages, it is recommended that you use the automatic package tools
|
|
|
2229 afterwards to pick up any recent updates.
|
|
|
2230
|
|
|
2231 @emph{More detailed info}: If the package path is not explicitly
|
|
|
2232 specified, XEmacs looks for the package directory
|
|
|
2233 @file{xemacs-packages} (and @file{mule-packages}, etc.) first under
|
|
|
2234 @samp{~/.xemacs}, then for a sister directory
|
|
|
2235 @file{lib/xemacs-VERSION} of the directory in which the XEmacs
|
|
|
2236 executable is located, then for a sister directory @file{lib/xemacs}.
|
|
|
2237 The XEmacs executable (under Unix at least) is installed by default in
|
|
|
2238 @file{/usr/local/bin}; this explains why XEmacs in its default
|
|
|
2239 installation will find packages that you put under
|
|
|
2240 @file{/usr/local/lib/xemacs}.
|
|
|
2241
|
|
|
2242 #### I'm not sure what exactly happens when the package path is
|
|
|
2243 specifically given, as is the case when the @samp{--package-prefix} or
|
|
|
2244 @samp{--package-path} options are given to @file{configure}, and
|
|
|
2245 always under Microsoft Windows.
|
|
|
2246
|
|
|
2247 @emph{NOTE}: For detailed information about how the package
|
|
|
2248 hierarchies work, @xref{Package Overview,,,lispref, the XEmacs Lisp
|
|
|
2249 Reference Manual}.
|
|
|
2250
|
|
|
2251 @node Q2.0.2, Q2.0.3, Q2.0.1, Installation
|
|
|
2252 @unnumberedsubsec Q2.0.2: I don't need no steenkin' packages. Do I?
|
|
|
2253
|
|
|
2254 Strictly speaking, no. XEmacs will build and install just fine without
|
|
|
2255 any packages installed. However, only the most basic editing functions
|
|
|
2256 will be available with no packages installed, so installing packages is
|
|
|
2257 an essential part of making your installed XEmacs _useful_.
|
|
|
2258
|
|
|
2259 @node Q2.0.3, Q2.0.4, Q2.0.2, Installation
|
|
|
2260 @unnumberedsubsec Q2.0.3: Where do I find external libraries?
|
|
|
2261
|
|
2459
|
2262 All external libraries used by XEmacs can be found on the XEmacs web
|
|
2417
|
2263 site
|
|
|
2264 @iftex
|
|
|
2265 @*
|
|
|
2266 @end iftex
|
|
2459
|
2267 @uref{http://www.xemacs.org/Download/optLibs.html}.
|
|
2417
|
2268
|
|
|
2269 The library versions available here are known to work with XEmacs.
|
|
|
2270 (Newer versions will probably work as well but we can't guarantee it.)
|
|
|
2271 We try to keep the libraries up-to-date but may not always succeed.
|
|
2459
|
2272 Check the above page for the canonical locations of the external libraries,
|
|
|
2273 allowing you to download the latest, bleeding-edge versions.
|
|
2417
|
2274
|
|
|
2275 @node Q2.0.4, Q2.0.5, Q2.0.3, Installation
|
|
|
2276 @unnumberedsubsec Q2.0.4: How do I specify the paths that XEmacs uses for finding files?
|
|
|
2277
|
|
|
2278 You can specify what paths to use by using a number of different flags
|
|
|
2279 when running configure. See the section MAKE VARIABLES in the top-level
|
|
|
2280 file INSTALL in the XEmacs distribution for a listing of those flags.
|
|
|
2281
|
|
|
2282 Most of the time, however, the simplest fix is: @strong{do not} specify
|
|
|
2283 paths as you might for GNU Emacs. XEmacs can generally determine the
|
|
|
2284 necessary paths dynamically at run time. The only path that generally
|
|
|
2285 needs to be specified is the root directory to install into. That can
|
|
|
2286 be specified by passing the @code{--prefix} flag to configure. For a
|
|
|
2287 description of the XEmacs install tree, please consult the @file{NEWS}
|
|
|
2288 file.
|
|
|
2289
|
|
|
2290 @node Q2.0.5, Q2.0.6, Q2.0.4, Installation
|
|
|
2291 @unnumberedsubsec Q2.0.5: Running XEmacs without installing
|
|
442
|
2292
|
|
|
2293 How can I just try XEmacs without installing it?
|
|
428
|
2294
|
|
|
2295 XEmacs will run in place without requiring installation and copying of
|
|
|
2296 the Lisp directories, and without having to specify a special build-time
|
|
|
2297 flag. It's the copying of the Lisp directories that requires so much
|
|
|
2298 space. XEmacs is largely written in Lisp.
|
|
|
2299
|
|
|
2300 A good method is to make a shell alias for xemacs:
|
|
|
2301
|
|
|
2302 @example
|
|
2459
|
2303 alias xemacs=/src/xemacs-21.5/src/xemacs
|
|
428
|
2304 @end example
|
|
|
2305
|
|
|
2306 (You will obviously use whatever directory you downloaded the source
|
|
2459
|
2307 tree to instead of @file{/src/xemacs-21.5}).
|
|
428
|
2308
|
|
|
2309 This will let you run XEmacs without massive copying.
|
|
|
2310
|
|
2417
|
2311 @node Q2.0.6, Q2.0.7, Q2.0.5, Installation
|
|
|
2312 @unnumberedsubsec Q2.0.6: XEmacs is too big
|
|
428
|
2313
|
|
442
|
2314 The space required by the installation directories can be
|
|
428
|
2315 reduced dramatically if desired. Gzip all the .el files. Remove all
|
|
442
|
2316 the packages you'll never want to use. Remove the TexInfo manuals.
|
|
428
|
2317 Remove the Info (and use just hardcopy versions of the manual). Remove
|
|
|
2318 most of the stuff in etc. Remove or gzip all the source code. Gzip or
|
|
|
2319 remove the C source code. Configure it so that copies are not made of
|
|
1138
|
2320 the support lisp.
|
|
428
|
2321
|
|
|
2322 These are all Emacs Lisp source code and bytecompiled object code. You
|
|
|
2323 may safely gzip everything named *.el here. You may remove any package
|
|
|
2324 you don't use. @emph{Nothing bad will happen if you delete a package
|
|
|
2325 that you do not use}. You must be sure you do not use it though, so be
|
|
|
2326 conservative at first.
|
|
|
2327
|
|
1648
|
2328 Any package with the possible exceptions of xemacs-base, and EFS are
|
|
|
2329 candidates for removal. Ask yourself, @emph{Do I ever want to use this
|
|
|
2330 package?} If the answer is no, then it is a candidate for removal.
|
|
428
|
2331
|
|
|
2332 First, gzip all the .el files. Then go about package by package and
|
|
|
2333 start gzipping the .elc files. Then run XEmacs and do whatever it is
|
|
1648
|
2334 you normally do. If nothing bad happens, then remove the package. You
|
|
|
2335 can remove a package via the PUI interface
|
|
|
2336 (@code{M-x pui-list-packages}, then press @kbd{d} to mark the packages
|
|
|
2337 you wish to delete, and then @kbd{x} to delete them.
|
|
|
2338
|
|
|
2339 Another method is to do @code{M-x package-get-delete-package}.
|
|
428
|
2340
|
|
2417
|
2341 @node Q2.0.7, Q2.1.1, Q2.0.6, Installation
|
|
|
2342 @unnumberedsubsec Q2.0.7: EFS fails with "500 AUTH not understood" (NEW)
|
|
|
2343
|
|
|
2344 A typical error: FTP Error: USER request failed; 500 AUTH not understood.
|
|
|
2345
|
|
|
2346 Thanks to giacomo boffi @email{giacomo.boffi@@polimi.it} who recommends
|
|
|
2347 on comp.emacs.xemacs:
|
|
|
2348
|
|
|
2349 tell your ftp client to not attempt AUTH authentication (or do not
|
|
|
2350 use FTP servers that don't understand AUTH)
|
|
|
2351
|
|
|
2352 and notes that you need to add an element (often "-u") to
|
|
|
2353 `efs-ftp-program-args'. Use M-x customize-variable, and verify the
|
|
|
2354 needed flag with `man ftp' or other local documentation.
|
|
|
2355
|
|
|
2356 @unnumberedsec 2.1: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
|
2357
|
|
|
2358 @node Q2.1.1, Q2.1.2, Q2.0.7, Installation
|
|
|
2359 @unnumberedsubsec Q2.1.1: Libraries in non-standard locations
|
|
428
|
2360
|
|
2459
|
2361 If your libraries are in a non-standard location, you can specify the location
|
|
|
2362 using the following flags to @file{configure}:
|
|
|
2363
|
|
|
2364 @example
|
|
|
2365 --site-libraries=WHATEVER
|
|
|
2366 --site-includes=WHATEVER
|
|
|
2367 @end example
|
|
|
2368
|
|
|
2369 If you have multiple paths to specify, use the following syntax:
|
|
428
|
2370
|
|
|
2371 @example
|
|
|
2372 --site-libraries='/path/one /path/two /path/etc'
|
|
|
2373 @end example
|
|
|
2374
|
|
2459
|
2375 @node Q2.1.2, Q2.2.1, Q2.1.1, Installation
|
|
2417
|
2376 @unnumberedsubsec Q2.1.2: Why can't I strip XEmacs?
|
|
428
|
2377
|
|
|
2378 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:
|
|
|
2379
|
|
|
2380 @quotation
|
|
|
2381 Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The
|
|
|
2382 link gives you a bare-boned emacs (called temacs). temacs is then run,
|
|
|
2383 preloading some of the lisp files. The result is then dumped into a new
|
|
|
2384 executable, named xemacs, which will contain all of the preloaded lisp
|
|
|
2385 functions and data.
|
|
|
2386
|
|
|
2387 Now, during the dump itself, the executable (code+data+symbols) is
|
|
|
2388 written on disk using a special unexec() function. This function is
|
|
|
2389 obviously heavily system dependent. And on some systems, it leads to an
|
|
|
2390 executable which, although valid, cannot be stripped without damage. If
|
|
|
2391 memory serves, this is especially the case for AIX binaries. On other
|
|
462
|
2392 architectures it might work OK.
|
|
428
|
2393
|
|
|
2394 The Right Way to strip the emacs binary is to strip temacs prior to
|
|
|
2395 dumping xemacs. This will always work, although you can do that only if
|
|
|
2396 you install from sources (as temacs is @file{not} part of the binary
|
|
|
2397 kits).
|
|
|
2398 @end quotation
|
|
|
2399
|
|
|
2400 @email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes:
|
|
|
2401
|
|
|
2402 @quotation
|
|
|
2403 Here is the trick:
|
|
|
2404
|
|
|
2405 @enumerate
|
|
|
2406 @item
|
|
|
2407 [ ./configure; make ]
|
|
|
2408
|
|
|
2409 @item
|
|
|
2410 rm src/xemacs
|
|
|
2411
|
|
|
2412 @item
|
|
|
2413 strip src/temacs
|
|
|
2414
|
|
|
2415 @item
|
|
|
2416 make
|
|
|
2417
|
|
|
2418 @item
|
|
|
2419 cp src/xemacs /usr/local/bin/xemacs
|
|
|
2420
|
|
|
2421 @item
|
|
|
2422 cp lib-src/DOC-19.16-XEmacs
|
|
|
2423 @iftex
|
|
|
2424 \ @*
|
|
|
2425 @end iftex
|
|
|
2426 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
|
|
|
2427 @end enumerate
|
|
|
2428 @end quotation
|
|
|
2429
|
|
2417
|
2430 @unnumberedsec 2.2: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
2431
|
|
2459
|
2432 @node Q2.2.1, Q2.2.2, Q2.1.2, Installation
|
|
2417
|
2433 @unnumberedsubsec Q2.2.1: What exactly are all the different ways to build XEmacs under Windows?
|
|
|
2434
|
|
|
2435 XEmacs can be built in several ways in the MS Windows environment.
|
|
|
2436
|
|
|
2437 The standard way is what we call the "native" port. It uses the Win32
|
|
|
2438 API and has no connection with X whatsoever -- it does not require X
|
|
|
2439 libraries to build, nor does it require an X server to run. The native
|
|
|
2440 port is the most reliable version and provides the best graphical
|
|
|
2441 support. Almost all development is geared towards this version, and
|
|
|
2442 there is little reason not to use it.
|
|
|
2443
|
|
|
2444 The second way to build is the Cygwin port. It takes advantage of
|
|
|
2445 Cygnus emulation library under Win32. @xref{Q1.1.4, What are Cygwin
|
|
|
2446 and MinGW, and do I need them to run XEmacs?}, for more information.
|
|
|
2447
|
|
|
2448 A third way is the MinGW port. It uses the Cygwin environment to
|
|
|
2449 build but does not require it at runtime. @xref{Q1.1.4, What are
|
|
|
2450 Cygwin and MinGW, and do I need them to run XEmacs?}, for more
|
|
|
2451 information.
|
|
|
2452
|
|
|
2453 Finally, you might also be able to build the non-Cygwin, non-MinGW "X"
|
|
|
2454 port. This was actually the first version of XEmacs that ran under MS
|
|
|
2455 Windows, and although the code is still in XEmacs, it's essentially
|
|
|
2456 orphaned and it's unlikely it will compile without a lot of work. If
|
|
|
2457 you want an MS Windows versin of XEmacs that supports X, use the Cygwin
|
|
|
2458 version. (The X support there is actively maintained, so that Windows
|
|
|
2459 developers can test the X support in XEmacs.)
|
|
|
2460
|
|
|
2461 @node Q2.2.2, Q2.2.3, Q2.2.1, Installation
|
|
|
2462 @unnumberedsubsec Q2.2.2: What compiler/libraries do I need to compile XEmacs?
|
|
|
2463
|
|
|
2464 You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have
|
|
|
2465 some beta testers currently trying to compile with VC.NET, aka version
|
|
|
2466 7.0, but we can't yet report complete success.) For the Cygwin and
|
|
|
2467 MinGW versions, you need the Cygwin environment, which comes with GCC,
|
|
|
2468 the compiler used for those versions. @xref{Q1.1.4, What are Cygwin
|
|
|
2469 and MinGW, and do I need them to run XEmacs?}, for more information on
|
|
|
2470 Cygwin and MinGW.
|
|
|
2471
|
|
|
2472 @node Q2.2.3, Q2.2.4, Q2.2.2, Installation
|
|
|
2473 @unnumberedsubsec Q2.2.3: How do I compile the native port?
|
|
|
2474
|
|
|
2475 Please read the file @file{nt/README} in the XEmacs distribution, which
|
|
|
2476 contains the full description.
|
|
|
2477
|
|
|
2478 @node Q2.2.4, Q2.2.5, Q2.2.3, Installation
|
|
|
2479 @unnumberedsubsec Q2.2.4: What do I need for Cygwin?
|
|
|
2480
|
|
|
2481 You can find the Cygwin tools and compiler at:
|
|
|
2482
|
|
|
2483 @uref{http://www.cygwin.com/}
|
|
|
2484
|
|
|
2485 Click on the @samp{Install or update now!} link, which will download a
|
|
|
2486 file @file{setup.exe}, which you can use to download everything
|
|
|
2487 else. (You will need to pick a mirror site; @samp{mirrors.rcn.net} is
|
|
|
2488 probably the best.) You should go ahead and install everything --
|
|
|
2489 you'll get various ancillary libraries that XEmacs needs or likes,
|
|
|
2490 e.g. XPM, PNG, JPEG, TIFF, etc. You can also get X Windows here, if you
|
|
|
2491 want to compile under X.
|
|
|
2492
|
|
|
2493 If you want to compile without X, you will need the @file{xpm-nox}
|
|
|
2494 library, which must be specifically selected in the Cygwin netinstaller;
|
|
|
2495 it is not selected by default. The package has had various names.
|
|
|
2496 Currently it is called @file{cygXpm-noX4.dll}.
|
|
|
2497
|
|
|
2498 @node Q2.2.5, Q2.2.6, Q2.2.4, Installation
|
|
|
2499 @unnumberedsubsec Q2.2.5: How do I compile under Cygwin?
|
|
|
2500
|
|
|
2501 Similar as on Unix; use the usual `configure' and `make' process.
|
|
|
2502 Some problems to watch out for:
|
|
|
2503
|
|
|
2504 @itemize @bullet
|
|
|
2505 @item
|
|
|
2506 make sure HOME is set. This controls where you
|
|
|
2507 @file{init.el} file comes from;
|
|
|
2508
|
|
|
2509 @item
|
|
|
2510 @samp{CYGWIN} needs to be set to @samp{tty} for process support to work;
|
|
|
2511
|
|
|
2512 @item
|
|
|
2513 picking up some other grep or other UNIX-like tools can kill configure;
|
|
|
2514
|
|
|
2515 @item
|
|
|
2516 static heap too small, adjust @file{src/sheap-adjust.h} to a more positive
|
|
|
2517 number;
|
|
|
2518
|
|
|
2519 @item
|
|
|
2520 (Unconfirmed) The Cygwin version doesn't understand
|
|
|
2521 @file{//machine/path} type paths so you will need to manually mount a
|
|
|
2522 directory of this form under a unix style directory for a build to work
|
|
|
2523 on the directory;
|
|
|
2524
|
|
|
2525 @item
|
|
|
2526 If you're building @strong{WITHOUT} X11, don't forget to change symlinks
|
|
|
2527 @file{/usr/lib/libXpm.a} and @file{/usr/lib/libXpm.dll.a} to point to
|
|
|
2528 the non-X versions of these libraries. By default they point to the X
|
|
|
2529 versions. So:
|
|
|
2530
|
|
|
2531 @example
|
|
|
2532 /usr/lib/libXpm.a -> /usr/lib/libXpm-noX.a
|
|
|
2533 /usr/lib/libXpm.dll.a -> /usr/lib/libXpm-noX.dll.a
|
|
|
2534 @end example
|
|
|
2535
|
|
|
2536 (This advice may now be obsolete because of the availability of the
|
|
|
2537 cygXpm-noX4.dll package from Cygwin. Send confirmation to
|
|
|
2538 @email{faq@@xemacs.org}.)
|
|
|
2539
|
|
|
2540 @item
|
|
|
2541 Other problems are listed in the @file{PROBLEMS} file, in the top-level
|
|
|
2542 directory of the XEmacs sources.
|
|
|
2543
|
|
|
2544 @end itemize
|
|
|
2545
|
|
|
2546
|
|
|
2547 @node Q2.2.6, Q2.2.7, Q2.2.5, Installation
|
|
|
2548 @unnumberedsubsec Q2.2.6: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
|
2549
|
|
|
2550 Similar to the method for Unix. Things to remember:
|
|
|
2551
|
|
|
2552 @itemize @bullet
|
|
|
2553 @item
|
|
|
2554 Specify the target host on the command line for @file{./configure}, e.g.
|
|
|
2555 @samp{./configure i586-pc-mingw32}.
|
|
|
2556
|
|
|
2557 @item
|
|
|
2558 Be sure that your build directory is mounted such that it has the
|
|
|
2559 same path either as a cygwin path (@file{/build/xemacs}) or as a Windows
|
|
|
2560 path (@file{c:\build\xemacs}).
|
|
|
2561
|
|
|
2562 @item
|
|
|
2563 Build @samp{gcc -mno-cygwin} versions of the extra libs, i.e. @file{libpng},
|
|
|
2564 @file{compface}, etc.
|
|
|
2565
|
|
|
2566 @item
|
|
|
2567 Specify the target location of the extra libs on the command line
|
|
|
2568 to @file{configure}, e.g.
|
|
|
2569 @samp{./configure --site-prefixes=/build/libs i586-pc-mingw32}.
|
|
|
2570 @end itemize
|
|
|
2571
|
|
|
2572 @node Q2.2.7, Q2.2.8, Q2.2.6, Installation
|
|
|
2573 @unnumberedsubsec Q2.2.7: How do I compile with X support?
|
|
|
2574
|
|
|
2575 To compile under Cygwin, all you need to do is install XFree86, which
|
|
|
2576 is available as part of the standard Cygwin installation.
|
|
|
2577 @uref{http://www.cygwin.com/}. Once installed, @file{configure}
|
|
|
2578 should automatically find the X libraries and compile with X support.
|
|
|
2579
|
|
|
2580 As noted above, the non-Cygwin X support is basically orphaned, and
|
|
|
2581 probably won't work. But if it want to try, it's described in
|
|
|
2582 @file{nt/README} in some detail. Basically, you need to get X11
|
|
2459
|
2583 libraries from @uref{http://ftp.x.org}, and compile them. If the
|
|
2417
|
2584 precompiled versions are available somewhere, we don't know of it.
|
|
|
2585
|
|
|
2586 @node Q2.2.8, Q2.3.1, Q2.2.7, Installation
|
|
|
2587 @unnumberedsubsec Q2.2.8: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
1058
|
2588
|
|
|
2589 The Cygwin binary distributed with the netinstaller uses an external DLL
|
|
|
2590 to handle XPM images (such as toolbar buttons). You may get an error like
|
|
|
2591
|
|
|
2592 This application has failed to start because cygXpm-noX4.dll was not found.
|
|
|
2593 Re-installing the application may fix this problem.
|
|
|
2594
|
|
|
2595 Andy Piper <andy@@xemacs.org> sez:
|
|
|
2596
|
|
|
2597 cygXpm-noX4 is part of the cygwin distribution under libraries or
|
|
|
2598 graphics, but is not installed by default. You need to run the
|
|
|
2599 cygwin setup again and select this package.
|
|
|
2600
|
|
|
2601 Ie, reinstalling XEmacs won't help because it is not part of the XEmacs
|
|
|
2602 distribution.
|
|
|
2603
|
|
2417
|
2604 @unnumberedsec 2.3: General Troubleshooting
|
|
|
2605
|
|
|
2606 @node Q2.3.1, Q2.3.2, Q2.2.8, Installation
|
|
|
2607 @unnumberedsubsec Q2.3.1: Help! XEmacs just crashed on me!
|
|
428
|
2608
|
|
|
2609 First of all, don't panic. Whenever XEmacs crashes, it tries extremely
|
|
|
2610 hard to auto-save all of your files before dying. (The main time that
|
|
|
2611 this will not happen is if the machine physically lost power or if you
|
|
|
2612 killed the XEmacs process using @code{kill -9}). The next time you try
|
|
|
2613 to edit those files, you will be informed that a more recent auto-save
|
|
|
2614 file exists. You can use @kbd{M-x recover-file} to retrieve the
|
|
|
2615 auto-saved version of the file.
|
|
|
2616
|
|
462
|
2617 You can use the command @kbd{M-x recover-session} after a crash to pick
|
|
|
2618 up where you left off.
|
|
428
|
2619
|
|
|
2620 Now, XEmacs is not perfect, and there may occasionally be times, or
|
|
|
2621 particular sequences of actions, that cause it to crash. If you can
|
|
|
2622 come up with a reproducible way of doing this (or even if you have a
|
|
|
2623 pretty good memory of exactly what you were doing at the time), the
|
|
2417
|
2624 maintainers would be very interested in knowing about it. The best
|
|
|
2625 way to report a bug is using @kbd{M-x report-emacs-bug} (or by
|
|
|
2626 selecting @samp{Send Bug Report...} from the Help menu). If that
|
|
|
2627 won't work (e.g. you can't get XEmacs working at all), send ordinary
|
|
|
2628 mail to @email{xemacs-beta@@xemacs.org}. @emph{MAKE SURE} to include
|
|
|
2629 the output from the crash, especially including the Lisp backtrace, as
|
|
|
2630 well as the XEmacs configuration from @kbd{M-x describe-installation}
|
|
|
2631 (or equivalently, the file @file{Installation} in the top of the build
|
|
|
2632 tree). Note that the developers do @emph{not} usually follow
|
|
|
2633 @samp{comp.emacs.xemacs} on a regular basis; thus, this is better for
|
|
|
2634 general questions about XEmacs than bug reports.
|
|
428
|
2635
|
|
1183
|
2636 If at all possible, include a C stack backtrace of the core dump that
|
|
2417
|
2637 was produced. This shows where exactly things went wrong, and makes
|
|
|
2638 it much easier to diagnose problems. To do this under Unix and Mac OS
|
|
|
2639 X, you need to locate the core file (it's called @file{core}, and is
|
|
|
2640 usually sitting in the directory that you started XEmacs from, or your
|
|
|
2641 home directory if that other directory was not writable). Then, go to
|
|
|
2642 that directory and execute a command like:
|
|
428
|
2643
|
|
|
2644 @example
|
|
|
2645 gdb `which xemacs` core
|
|
|
2646 @end example
|
|
|
2647
|
|
|
2648 and then issue the command @samp{where} to get the stack backtrace. You
|
|
|
2649 might have to use @code{dbx} or some similar debugger in place of
|
|
|
2650 @code{gdb}. If you don't have any such debugger available, complain to
|
|
|
2651 your system administrator.
|
|
|
2652
|
|
2417
|
2653 It's possible that a core file didn't get produced or the stack trace
|
|
|
2654 from gdb is garbage, in which case you're out of luck unless you can
|
|
|
2655 reproduce the bug. A nonexistent core file can happen in some
|
|
|
2656 circumstances on some operating systems, depending on what exactly
|
|
|
2657 triggered the crash. It's also possible, however, that your limits
|
|
|
2658 are set to turn them off. You may be able to reenable them using a
|
|
|
2659 command like @samp{unlimit coredumpsize} or @samp{ulimit -c}. (To find
|
|
|
2660 out how your limits are set, use the command @samp{limit}.) However, if
|
|
|
2661 you didn't explicitly set your limits this way, go complain to your
|
|
|
2662 system administrator and tell him not to disable core files by
|
|
|
2663 default.
|
|
|
2664
|
|
|
2665 A garbaged stack trace can happen for various reasons. Some versions
|
|
|
2666 of gdb are broken on certain operating systems and aren't able to read
|
|
|
2667 the core file. It's also possible that the stack got overwritten
|
|
|
2668 during the crash. A very simple reason, however, is that your version
|
|
|
2669 of XEmacs was compiled without debugging information or had the
|
|
|
2670 debugging information stripped. A compilation with optimization can
|
|
|
2671 also result in partly or completely garbaged stack trace. In such
|
|
|
2672 cases, you will need to recompile XEmacs with debugging information
|
|
|
2673 and without optimization; @xref{Q2.3.3, How to debug an XEmacs problem
|
|
|
2674 with a debugger}. Note also that core files currently don't work at
|
|
|
2675 all under Cygwin, and the only way to get a backtrace is to run XEmacs
|
|
|
2676 from gdb.
|
|
|
2677
|
|
|
2678 If you cannot get a backtrace from the core dump, but can reproduce
|
|
|
2679 the problem, try running XEmacs under gdb. The goal is to get clean C
|
|
|
2680 and Lisp backtraces and submit a bug report including full
|
|
|
2681 configuration information as described above, as this will greatly
|
|
|
2682 assist in the process of tracking down the bug. However, even partial
|
|
|
2683 information is better than none. The process of getting backtraces
|
|
|
2684 from gdb is described in detail in @ref{Q2.3.3, How to debug an XEmacs
|
|
|
2685 problem with a debugger}.
|
|
428
|
2686
|
|
1183
|
2687 If you're under Microsoft Windows, you're out of luck unless you happen
|
|
|
2688 to have a debugging aid installed on your system, for example Visual
|
|
|
2689 C++. In this case, the crash will result in a message giving you the
|
|
|
2690 option to enter a debugger (for example, by pressing @samp{Cancel}). Do
|
|
|
2691 this and locate the stack-trace window. (If your XEmacs was built
|
|
|
2692 without debugging information, the stack trace may not be very useful.)
|
|
|
2693
|
|
428
|
2694 When making a problem report make sure that:
|
|
|
2695
|
|
|
2696 @enumerate
|
|
|
2697 @item
|
|
|
2698 Report @strong{all} of the information output by XEmacs during the
|
|
|
2699 crash.
|
|
|
2700
|
|
|
2701 @item
|
|
2417
|
2702 You mention what O/S and Hardware you are running XEmacs on.
|
|
428
|
2703
|
|
|
2704 @item
|
|
|
2705 What version of XEmacs you are running.
|
|
|
2706
|
|
|
2707 @item
|
|
|
2708 What build options you are using.
|
|
|
2709
|
|
|
2710 @item
|
|
2417
|
2711 If the problem is related to graphics and you are running Unix or Mac
|
|
|
2712 OS X, we will also need to know what version of the X Window System
|
|
|
2713 you are running, and what window manager you are using.
|
|
1183
|
2714
|
|
|
2715 @item
|
|
|
2716 If the problem happened on a TTY, please include the terminal type.
|
|
2417
|
2717
|
|
|
2718 @item
|
|
|
2719 Try very hard to get both C and Lisp backtraces, as described above.
|
|
428
|
2720 @end enumerate
|
|
|
2721
|
|
1135
|
2722 Much of the information above is automatically generated by @kbd{M-x
|
|
|
2723 report-emacs-bug}. Even more, and often useful, information can be
|
|
|
2724 generated by redirecting the output of @code{make} and @code{make check}
|
|
|
2725 to a file (@file{beta.err} is the default used by @code{build-report}),
|
|
|
2726 and executing @kbd{M-x build-report}.
|
|
|
2727
|
|
2417
|
2728
|
|
|
2729 @node Q2.3.2, Q2.3.3, Q2.3.1, Installation
|
|
|
2730 @unnumberedsubsec Q2.3.2: XEmacs crashes and I compiled it myself.
|
|
|
2731
|
|
|
2732 There have been a variety of reports of crashes due to compilers with
|
|
|
2733 buggy optimizers. If you are compiling with optimization, consider
|
|
|
2734 turning it off (@pxref{Q2.3.3, How to debug an XEmacs problem with a
|
|
|
2735 debugger}) and recompiling.
|
|
|
2736
|
|
|
2737 Please see the @file{PROBLEMS} file that comes with XEmacs (it's in
|
|
|
2738 the top-level source directory) to read what it says about your
|
|
|
2739 platform.
|
|
|
2740
|
|
|
2741 If you compiled XEmacs using @samp{--use-union-type} (or the option
|
|
|
2742 @samp{USE_UNION_TYPE} in @file{config.inc} under Windows), try
|
|
|
2743 recompiling again without it. The union type has been known to trigger
|
|
|
2744 compiler errors in a number of cases.
|
|
|
2745
|
|
|
2746 @node Q2.3.3, Q2.3.4, Q2.3.2, Installation
|
|
|
2747 @unnumberedsubsec Q2.3.3: How to debug an XEmacs problem with a debugger
|
|
428
|
2748
|
|
|
2749 If XEmacs does crash on you, one of the most productive things you can
|
|
|
2750 do to help get the bug fixed is to poke around a bit with the debugger.
|
|
|
2751 Here are some hints:
|
|
|
2752
|
|
|
2753 @itemize @bullet
|
|
|
2754 @item
|
|
|
2755 First of all, if the crash is at all reproducible, consider very
|
|
563
|
2756 strongly recompiling your XEmacs with debugging symbols and with no
|
|
|
2757 optimization (e.g. with GCC use the compiler flags @samp{-g -O0} --
|
|
|
2758 that's an "oh" followed by a zero), and with the configure options
|
|
2417
|
2759 @samp{--debug=yes} and @samp{--error-checking=all}. This will make
|
|
|
2760 your XEmacs run somewhat slower, but you are a lot more likely to
|
|
|
2761 catch the problem earlier (closer to its source). It makes it a lot
|
|
|
2762 easier to determine what's going on with a debugger. The way to
|
|
|
2763 control the compiler flags is with the configuration option
|
|
|
2764 @samp{--cflags}. If you have a recent version of 21.5, you should use
|
|
|
2765 @samp{--without-optimization} in preference to directly setting
|
|
|
2766 @samp{--cflags}.
|
|
1258
|
2767
|
|
|
2768 @item
|
|
|
2769 If it's not a true crash (@emph{i.e.}, XEmacs is hung, or a zombie
|
|
|
2770 process), or it's inconvenient to run XEmacs again because XEmacs is
|
|
|
2771 already running or is running in batch mode as part of a bunch of
|
|
|
2772 scripts, you may be able to attach to the existing process with your
|
|
2417
|
2773 debugger. Under Unix and Mac OS X, the typical way to do this is to
|
|
|
2774 first use some variant of the @samp{ps} command to figure out the
|
|
|
2775 process ID of XEmacs, for example @samp{ps -auxww | grep xemacs} under
|
|
|
2776 a BSD variant, @samp{ps -elf | grep xemacs} under Linux or System V,
|
|
|
2777 or @samp{ps -aW | grep xemacs} under Cygwin. Then run
|
|
|
2778
|
|
|
2779 @example
|
|
|
2780 gdb /path/to/xemacs/xemacs ####
|
|
|
2781 @end example
|
|
|
2782
|
|
|
2783 Where @code{####} is the process id of your XEmacs. (If you're not
|
|
|
2784 sure, try using @samp{which xemacs}.) When gdb attaches, the xemacs
|
|
|
2785 will stop and you can type @samp{where} in gdb to get a stack trace as
|
|
|
2786 usual. To get things moving again, you can just type @samp{quit} in
|
|
|
2787 gdb. It'll tell you the program is running and ask if you want to
|
|
|
2788 quit anyways. Say @samp{y} and it'll quit and have your emacs
|
|
|
2789 continue from where it was at.
|
|
|
2790
|
|
|
2791 If you're running another debugger, a similar method may work, or you
|
|
|
2792 may have to run the debugger first and then use the @code{attach}
|
|
|
2793 command or something similar.
|
|
|
2794
|
|
|
2795 Under Microsoft Windows, use the menu item @samp{Build->Start
|
|
|
2796 Debug->Attach to Process...} and select the XEmacs process from the list
|
|
|
2797 given.
|
|
1258
|
2798
|
|
|
2799 @item
|
|
|
2800 If you're able to run XEmacs under a debugger and reproduce the crash,
|
|
|
2801 here are some things you can do:
|
|
428
|
2802
|
|
|
2803 @item
|
|
|
2804 If XEmacs is hitting an assertion failure, put a breakpoint on
|
|
|
2805 @code{assert_failed()}.
|
|
|
2806
|
|
|
2807 @item
|
|
|
2808 If XEmacs is hitting some weird Lisp error that's causing it to crash
|
|
|
2809 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is
|
|
2417
|
2810 declared static in @file{eval.c}.
|
|
428
|
2811
|
|
|
2812 @item
|
|
563
|
2813 If XEmacs is outputting lots of X errors, put a breakpoint on
|
|
2417
|
2814 @code{x_error_handler()}; that will tell you which call is causing
|
|
|
2815 them. Note that the result may not be very useful by default because
|
|
|
2816 X Windows normally operates asynchronously: A bunch of commands are
|
|
|
2817 buffered up and then sent to the server all at once. This greatly
|
|
|
2818 improves performance over a network but means that an error may not be
|
|
|
2819 reported until the server receives the commands, which can be long
|
|
|
2820 after XEmacs made the erroneous calls. For best results, you need to
|
|
|
2821 make the X server synchronous before getting the backtrace. This can
|
|
|
2822 be done by starting XEmacs with the @samp{-sync} option or executing
|
|
|
2823 the Lisp code @code{(x-debug-mode t)}.
|
|
563
|
2824
|
|
|
2825 @item
|
|
428
|
2826 Internally, you will probably see lots of variables that hold objects of
|
|
1258
|
2827 type @code{Lisp_Object}. These are references to Lisp objects.
|
|
|
2828 Printing them out with the debugger probably won't be too
|
|
|
2829 useful---you'll likely just see a number. To decode them, do this:
|
|
428
|
2830
|
|
|
2831 @example
|
|
2417
|
2832 call debug_print (OBJECT)
|
|
428
|
2833 @end example
|
|
|
2834
|
|
|
2835 where @var{OBJECT} is whatever you want to decode (it can be a variable,
|
|
1258
|
2836 a function call, etc.). This uses the Lisp printing routines to out a
|
|
|
2837 readable representation on the TTY from which the xemacs process was
|
|
|
2838 invoked.
|
|
428
|
2839
|
|
2417
|
2840 Under 21.5 and later, @code{dp} is defined as an easier-to-type equivalent
|
|
|
2841 of @code{debug_print}. You can also try @code{dpa} if you can't see
|
|
|
2842 the output from @code{debug_print} (this will return a string containing
|
|
|
2843 the output), or use @code{debug_p3} if @code{debug_print} itself triggers
|
|
|
2844 a crash (this is a less comprehensive but super-safe way to print out
|
|
|
2845 a Lisp object).
|
|
|
2846
|
|
428
|
2847 @item
|
|
|
2848 If you want to get a Lisp backtrace showing the Lisp call
|
|
|
2849 stack, do this:
|
|
|
2850
|
|
|
2851 @example
|
|
2417
|
2852 call debug_backtrace ()
|
|
428
|
2853 @end example
|
|
|
2854
|
|
2417
|
2855 Under 21.5 and later, @code{db} is defined as an easier-to-type equivalent
|
|
|
2856 of @code{debug_backtrace}.
|
|
|
2857
|
|
|
2858 @item
|
|
|
2859 Using @code{debug_print} and @code{debug_backtrace} has two
|
|
|
2860 disadvantages - they can only be used with a running (including hung
|
|
|
2861 or zombie) xemacs process, and they do not display the internal C
|
|
|
2862 structure of a Lisp Object. Even if all you've got is a core dump,
|
|
|
2863 all is not lost.
|
|
428
|
2864
|
|
|
2865 If you're using GDB, there are some macros in the file
|
|
438
|
2866 @file{src/.gdbinit} in the XEmacs source distribution that should make
|
|
|
2867 it easier for you to decode Lisp objects. This file is automatically
|
|
|
2868 read by gdb if gdb is run in the directory where xemacs was built, and
|
|
|
2869 contains these useful macros to inspect the state of xemacs:
|
|
|
2870
|
|
|
2871 @table @code
|
|
|
2872 @item pobj
|
|
|
2873 Usage: pobj lisp_object @*
|
|
|
2874 Print the internal C representation of a lisp object.
|
|
|
2875
|
|
|
2876 @item xtype
|
|
|
2877 Usage: xtype lisp_object @*
|
|
|
2878 Print the Lisp type of a lisp object.
|
|
|
2879
|
|
|
2880 @item lbt
|
|
|
2881 Usage: lbt @*
|
|
|
2882 Print the current Lisp stack trace.
|
|
1258
|
2883 Requires a running xemacs process. (It works by calling the db
|
|
|
2884 routine described above.)
|
|
438
|
2885
|
|
|
2886 @item ldp
|
|
|
2887 Usage: ldp lisp_object @*
|
|
|
2888 Print a Lisp Object value using the Lisp printer.
|
|
1258
|
2889 Requires a running xemacs process. (It works by calling the dp
|
|
|
2890 routine described above.)
|
|
438
|
2891
|
|
|
2892 @item run-temacs
|
|
|
2893 Usage: run-temacs @*
|
|
|
2894 Run temacs interactively, like xemacs.
|
|
|
2895 Use this with debugging tools (like purify) that cannot deal with dumping,
|
|
|
2896 or when temacs builds successfully, but xemacs does not.
|
|
|
2897
|
|
|
2898 @item dump-temacs
|
|
|
2899 Usage: dump-temacs @*
|
|
|
2900 Run the dumping part of the build procedure.
|
|
|
2901 Use when debugging temacs, not xemacs!
|
|
|
2902 Use this when temacs builds successfully, but xemacs does not.
|
|
|
2903
|
|
|
2904 @item check-xemacs
|
|
|
2905 Usage: check-xemacs @*
|
|
|
2906 Run the test suite. Equivalent to 'make check'.
|
|
|
2907
|
|
|
2908 @item check-temacs
|
|
|
2909 Usage: check-temacs @*
|
|
|
2910 Run the test suite on temacs. Equivalent to 'make check-temacs'.
|
|
|
2911 Use this with debugging tools (like purify) that cannot deal with dumping,
|
|
|
2912 or when temacs builds successfully, but xemacs does not.
|
|
|
2913 @end table
|
|
428
|
2914
|
|
|
2915 If you are using Sun's @file{dbx} debugger, there is an equivalent file
|
|
438
|
2916 @file{src/.dbxrc}, which defines the same commands for dbx.
|
|
428
|
2917
|
|
|
2918 @item
|
|
|
2919 If you're using a debugger to get a C stack backtrace and you're seeing
|
|
|
2920 stack traces with some of the innermost frames mangled, it may be due to
|
|
|
2921 dynamic linking. (This happens especially under Linux.) Consider
|
|
|
2922 reconfiguring with @samp{--dynamic=no}. Also, sometimes (again under
|
|
|
2923 Linux), stack backtraces of core dumps will have the frame where the
|
|
|
2924 fatal signal occurred mangled; if you can obtain a stack trace while
|
|
|
2925 running the XEmacs process under a debugger, the stack trace should be
|
|
|
2926 clean.
|
|
|
2927
|
|
1183
|
2928 @email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so
|
|
|
2929 version 1.8 if dynamic linking and debugging is a problem on Linux.
|
|
428
|
2930
|
|
|
2931 @item
|
|
|
2932 If you're using a debugger to get a C stack backtrace and you're
|
|
|
2933 getting a completely mangled and bogus stack trace, it's probably due to
|
|
|
2934 one of the following:
|
|
|
2935
|
|
|
2936 @enumerate a
|
|
|
2937 @item
|
|
|
2938 Your executable has been stripped. Bad news. Tell your sysadmin not to
|
|
|
2939 do this---it doesn't accomplish anything except to save a bit of disk
|
|
|
2940 space, and makes debugging much much harder.
|
|
|
2941
|
|
|
2942 @item
|
|
|
2943 Your stack is getting trashed. Debugging this is hard; you have to do a
|
|
|
2944 binary-search type of narrowing down where the crash occurs, until you
|
|
|
2945 figure out exactly which line is causing the problem. Of course, this
|
|
1258
|
2946 only works if the bug is highly reproducible. Also, in many cases if
|
|
|
2947 you run XEmacs from the debugger, the debugger can protect the stack
|
|
|
2948 somewhat. However, if the stack is being smashed, it is typically the
|
|
|
2949 case that there is a wild pointer somewhere in the program, often quite
|
|
|
2950 far from where the crash occurs.
|
|
428
|
2951
|
|
|
2952 @item
|
|
|
2953 If your stack trace has exactly one frame in it, with address 0x0, this
|
|
|
2954 could simply mean that XEmacs attempted to execute code at that address,
|
|
|
2955 e.g. through jumping to a null function pointer. Unfortunately, under
|
|
|
2956 those circumstances, GDB under Linux doesn't know how to get a stack
|
|
1183
|
2957 trace. (Yes, this is the fourth Linux-related problem I've mentioned. I
|
|
428
|
2958 have no idea why GDB under Linux is so bogus. Complain to the GDB
|
|
1183
|
2959 authors, or to comp.os.linux.development.system.) Again, you'll have to
|
|
428
|
2960 use the narrowing-down process described above.
|
|
|
2961
|
|
|
2962 @item
|
|
462
|
2963 You will get a Lisp backtrace output when XEmacs crashes, so you'll have
|
|
|
2964 something useful.
|
|
428
|
2965
|
|
|
2966 @end enumerate
|
|
|
2967
|
|
|
2968 @item
|
|
|
2969 If you compile with the newer gcc variants gcc-2.8 or egcs, you will
|
|
438
|
2970 also need gdb 4.17 or above. Earlier releases of gdb can't handle the
|
|
|
2971 debug information generated by the newer compilers.
|
|
428
|
2972
|
|
|
2973 @item
|
|
438
|
2974 In versions of XEmacs before 21.2.27, @file{src/.gdbinit} was named
|
|
|
2975 @file{src/gdbinit}. This had the disadvantage of not being sourced
|
|
|
2976 automatically by gdb, so you had to set that up yourself.
|
|
428
|
2977
|
|
1183
|
2978 @item
|
|
|
2979 If you are running Microsoft Windows, the the file @file{nt/README} for
|
|
|
2980 further information about debugging XEmacs.
|
|
|
2981
|
|
428
|
2982 @end itemize
|
|
|
2983
|
|
2417
|
2984 @node Q2.3.4, Q2.3.5, Q2.3.3, Installation
|
|
|
2985 @unnumberedsubsec Q2.3.4: I get a cryptic error message when trying to do something.
|
|
|
2986
|
|
|
2987 When I try to use some particular option of some particular package, I
|
|
|
2988 get a cryptic error message in the minibuffer.
|
|
|
2989
|
|
|
2990 If the message went by too quickly, use @samp{Help->Recent Messages}
|
|
|
2991 from the menubar (or type @kbd{C-h l}) to see recent messages.
|
|
|
2992
|
|
|
2993 If you can't figure out what's going on, select
|
|
|
2994 @samp{Options->Troubleshooting->Debug on Error} from the menubar (or
|
|
|
2995 type @kbd{M-:} then @kbd{(setq debug-on-error t)}) then try and make
|
|
|
2996 the error happen again. This will put in the debugger (you can get
|
|
|
2997 out of this and continue what you were doing before by typing @kbd{c})
|
|
|
2998 and give you a backtrace that may be enlightening. If not, try
|
|
|
2999 reading through this FAQ; if that fails, you could try posting to
|
|
|
3000 @samp{comp.emacs.xemacs} (making sure to include the backtrace) and
|
|
|
3001 someone may be able to help. If you can identify which XEmacs Lisp
|
|
|
3002 source file the error is coming from you can get a more detailed stack
|
|
|
3003 backtrace by doing the following:
|
|
428
|
3004
|
|
|
3005 @enumerate
|
|
|
3006 @item
|
|
2417
|
3007 Visit the .el file in an XEmacs buffer.
|
|
|
3008
|
|
|
3009 @item
|
|
|
3010 Issue the command @kbd{M-x eval-current-buffer}.
|
|
|
3011
|
|
|
3012 @item
|
|
|
3013 Reproduce the error.
|
|
428
|
3014 @end enumerate
|
|
|
3015
|
|
2417
|
3016 For more information on debugging Lisp code, @xref{Debugging,,,
|
|
|
3017 lispref, XEmacs Lisp Reference Manual}.
|
|
|
3018
|
|
|
3019 @node Q2.3.5, Q2.3.6, Q2.3.4, Installation
|
|
|
3020 @unnumberedsubsec Q2.3.5: XEmacs hangs when I try to do something.
|
|
|
3021
|
|
|
3022 XEmacs might just be slow; some operations take a long time. XEmacs
|
|
|
3023 may also be waiting on a response from the network, for example when
|
|
|
3024 you are trying to send mail.
|
|
|
3025
|
|
|
3026 You can usually interrupt XEmacs by typing @kbd{C-g}. If not (for
|
|
|
3027 example, Lisp code explicitly disabled this by setting
|
|
|
3028 @code{inhibit-quit}), you can use the "critical quit" mechanism by
|
|
|
3029 typing @kbd{Control-Shift-G}. This should also pop you into the
|
|
|
3030 debugger and give you a backtrace, which can tell you where the
|
|
|
3031 problem is (@pxref{Q2.3.3, How to debug an XEmacs problem with a
|
|
|
3032 debugger}). (Note that setting @code{debug-on-quit} or selecting
|
|
|
3033 @samp{Options->Troubleshooting->Debug on Quit} will also cause regular
|
|
|
3034 @kbd{C-g} to enter the debugger and give you a backtrace.)
|
|
|
3035
|
|
|
3036 If you can't interrupt XEmacs this way, or for some reason XEmacs is
|
|
|
3037 not talking to the keyboard, you can try sending the @samp{SIGINT}
|
|
|
3038 signal using the @samp{kill} command.
|
|
|
3039
|
|
|
3040 If the Lisp backtrace isn't enlightening, or if XEmacs is so hung that
|
|
|
3041 you can't interrupt it at all, you could try attaching to the process
|
|
|
3042 and getting a C stack backtrace. @xref{Q2.3.3, How to debug an XEmacs
|
|
|
3043 problem with a debugger}.
|
|
|
3044
|
|
|
3045 @node Q2.3.6, Q2.3.7, Q2.3.5, Installation
|
|
|
3046 @unnumberedsubsec Q2.3.6: I get an error message when XEmacs is running in batch mode.
|
|
|
3047
|
|
|
3048 Typically this happens when you are trying to compile some Elisp code.
|
|
|
3049 If you are doing this as part of XEmacs or the XEmacs packages, you
|
|
|
3050 should automatically get a backtrace, which can help you determine the
|
|
|
3051 source of the problem. In other cases, you can get equivalent results
|
|
|
3052 by setting the environment variable @samp{XEMACSDEBUG} to @samp{(setq
|
|
|
3053 stack-trace-on-error t load-always-display-messages t
|
|
|
3054 load-ignore-out-of-date-elc-files t load-show-full-path-in-messages
|
|
|
3055 t)} (this needs to be all on one line; to set an environment variable,
|
|
|
3056 use @samp{export XEMACSDEBUG='FOO'} under @samp{bash}, @samp{zsh},
|
|
|
3057 etc. or @samp{setenv XEMACSDEBUG 'FOO'} under @samp{csh} and
|
|
|
3058 @samp{tcsh}). @samp{XEMACSDEBUG} specifies Lisp code that will be
|
|
|
3059 executed at startup time.
|
|
|
3060
|
|
|
3061 If the backtrace is not sufficiently useful in helping you diagnose
|
|
|
3062 the problem, you should consider using a debugger such as GDB.
|
|
|
3063 @xref{Q2.3.3, How to debug an XEmacs problem with a debugger}. You
|
|
|
3064 probably want to set a breakpoint on @code{signal_1}. Since such
|
|
|
3065 errors often occur during compiling, which is often triggered by a
|
|
|
3066 complex command run from a make suite, it may be easier to attach to
|
|
|
3067 the process once it's running.
|
|
|
3068
|
|
|
3069 Under Microsoft Windows (and perhaps other operating systems), there
|
|
|
3070 is another useful trick you can do if you have configured with
|
|
|
3071 debugging support (configure option @samp{--debug} or setting
|
|
|
3072 @samp{DEBUG_XEMACS} in @file{nt/config.inc}). Set the environment
|
|
|
3073 variable @samp{XEMACSDEBUG} (as described above) to @samp{(setq
|
|
|
3074 debug-on-error t)}. Then, when an error occurs noninteractively,
|
|
|
3075 instead of trying to invoke the Lisp debugger (which obviously won't
|
|
|
3076 work), XEmacs will break out to a C debugger using
|
|
|
3077 @code{(force-debugging-signal t)}. @emph{NOTE}: This runs
|
|
|
3078 @code{abort()}!!! (As well as and after executing INT 3 under MS
|
|
|
3079 Windows, which should invoke a debugger if it's active.) This is
|
|
|
3080 guaranteed to kill XEmacs! (But in this situation, XEmacs is about to
|
|
|
3081 die anyway, and if no debugger is present, this will usefully dump
|
|
|
3082 core.)
|
|
|
3083
|
|
|
3084 @node Q2.3.7, Q2.3.8, Q2.3.6, Installation
|
|
|
3085 @unnumberedsubsec Q2.3.7: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
|
3086
|
|
|
3087 XEmacs has various facilities for debugging event handling.
|
|
|
3088
|
|
|
3089 First, try setting the variable @code{debug-emacs-events} to non-zero.
|
|
|
3090 This will output various information showing which events are being
|
|
|
3091 received and how they are being translated. This may show you, for
|
|
|
3092 example, that a key command is getting intercepted using
|
|
|
3093 @code{key-translation-map}; this problem can otherwise be very tricky
|
|
|
3094 to debug.
|
|
|
3095
|
|
|
3096 Under X, you can see exactly which events are being received from the
|
|
|
3097 window system by setting @code{x-debug-events} to non-zero. (The value
|
|
|
3098 @samp{1} gives you regular output, and @samp{2} gives you verbose
|
|
|
3099 output, including all parameters.)
|
|
|
3100
|
|
|
3101 A similar facility exists under MS Windows: Set
|
|
|
3102 @code{debug-mswindows-events} to non-zero. (The value @samp{1} gives
|
|
|
3103 you regular output. The value @samp{2} gives you verbose output,
|
|
|
3104 including all parameters. The value @samp{3} gives you
|
|
|
3105 super-gorily-detailed output.)
|
|
|
3106
|
|
|
3107 @node Q2.3.8, Q2.3.9, Q2.3.7, Installation
|
|
|
3108 @unnumberedsubsec Q2.3.8: @kbd{C-g} doesn't work for me. Is it broken?
|
|
|
3109
|
|
|
3110 @kbd{C-g} does work for most people in most circumstances. If it
|
|
|
3111 doesn't, there are two possible explanations:
|
|
|
3112
|
|
|
3113 @enumerate
|
|
|
3114 @item
|
|
|
3115 XEmacs is hung in a way that prevents @kbd{C-g} from working. This
|
|
|
3116 can happen when code is wrapped with a binding of @code{inhibit-quit}
|
|
|
3117 to @code{t}; you should still be able interrupt XEmacs using "critical
|
|
|
3118 quit". On the other hand, XEmacs may be seriously wedged. (If you're
|
|
|
3119 lucky, sending @samp{SIGINT} to the XEmacs process will interrupt it.)
|
|
|
3120 @xref{Q2.3.5, XEmacs hangs when I try to do something.}.
|
|
|
3121
|
|
|
3122 @item
|
|
|
3123 @kbd{C-g} is indeed broken on your system. To test, try executing
|
|
|
3124 @code{(while t)} from the @samp{*scratch*} buffer. If @kbd{C-g}
|
|
|
3125 doesn't interrupt, then it's broken. This used to happen with systems
|
|
|
3126 where @samp{SIGIO} was broken, but @samp{BROKEN_SIGIO} wasn't defined.
|
|
|
3127 However, there may not be very many such systems nowadays.
|
|
|
3128 @end enumerate
|
|
|
3129
|
|
|
3130 @node Q2.3.9, Q2.3.10, Q2.3.8, Installation
|
|
|
3131 @unnumberedsubsec Q2.3.9: How do I debug process-related problems?
|
|
|
3132
|
|
|
3133 Under MS Windows, you can set the variable
|
|
|
3134 @code{debug-mswindows-process-command-lines} to non-@samp{nil} to get
|
|
|
3135 information on exactly what is getting passed to a process. This can
|
|
|
3136 be useful in determining problems with quoting. (Under Unix, a process
|
|
|
3137 receives each argument separately, but under MS Windows a single
|
|
|
3138 command line is received, and arguments with spaces or other special
|
|
|
3139 characters in them must be quoted. Unfortunately this means that each
|
|
|
3140 process, potentially at least, has its own quoting conventions, and
|
|
|
3141 the code to process quoting conventions in @file{cmd.exe}, the Visual
|
|
|
3142 C++ startup code and the like is baroque and poorly documented.
|
|
|
3143 XEmacs uses the variable
|
|
|
3144 @code{mswindows-construct-process-command-line-alist} to construct a
|
|
|
3145 command line from a list of arguments based on the command to be run,
|
|
|
3146 but it is (and cannot be) a perfect solution.)
|
|
|
3147
|
|
|
3148 @node Q2.3.10, Q2.3.11, Q2.3.9, Installation
|
|
|
3149 @unnumberedsubsec Q2.3.10: XEmacs is outputting lots of X errors.
|
|
563
|
3150
|
|
|
3151 If this is happening, we would very much like to know what's causing
|
|
2417
|
3152 them. To find this out, see @ref{Q2.3.3, How to debug an XEmacs
|
|
|
3153 problem with a debugger}. Try to get both a C and Lisp backtrace, and
|
|
|
3154 send them along with the full error output to
|
|
|
3155 @email{xemacs-beta@@xemacs.org}.
|
|
|
3156
|
|
|
3157 @node Q2.3.11, Q2.4.1, Q2.3.10, Installation
|
|
|
3158 @unnumberedsubsec Q2.3.11: After upgrading, XEmacs won't do `foo' any more!
|
|
|
3159
|
|
|
3160 You have been used to doing `foo', but now when you invoke it (or
|
|
|
3161 click the toolbar button or select the menu item), nothing (or an
|
|
|
3162 error) happens. The simplest explanation is that you are missing a
|
|
|
3163 package that is essential to you. You can either track it down and
|
|
|
3164 install it (there is a list of packages and brief descriptions of
|
|
|
3165 their contents in @file{etc/PACKAGES}), or install the `Sumo Tarball'
|
|
|
3166 (@pxref{Q2.0.2, How do I figure out which packages to install?}).
|
|
|
3167
|
|
|
3168 @c #### should xref to XEmacs manual here
|
|
|
3169
|
|
|
3170 @unnumberedsec 2.4: Startup-Related Problems
|
|
|
3171
|
|
|
3172 @node Q2.4.1, Q2.4.2, Q2.3.11, Installation
|
|
|
3173 @unnumberedsubsec Q2.4.1: XEmacs cannot connect to my X Terminal!
|
|
|
3174
|
|
|
3175 Help! I can not get XEmacs to display on my Envizex X-terminal!
|
|
|
3176
|
|
|
3177 Try setting the @code{DISPLAY} variable using the numeric IP address of
|
|
|
3178 the host you are running XEmacs from.
|
|
|
3179
|
|
|
3180 @node Q2.4.2, Q2.4.3, Q2.4.1, Installation
|
|
|
3181 @unnumberedsubsec Q2.4.2: XEmacs won't start on Windows.
|
|
|
3182
|
|
|
3183 XEmacs relies on a process called "dumping" to generate a working
|
|
|
3184 executable. Under MS-Windows this process effectively fixes the memory
|
|
|
3185 addresses of information in the executable. When XEmacs starts up it tries
|
|
|
3186 to reserve these memory addresses so that the dumping process can be
|
|
|
3187 reversed -- putting the information back at the correct addresses.
|
|
|
3188 Unfortunately some .DLLs (for instance the soundblaster driver) occupy
|
|
|
3189 memory addresses that can conflict with those needed by the dumped XEmacs
|
|
|
3190 executable. In this instance XEmacs will fail to start without any
|
|
|
3191 explanation. Note that this is extremely machine specific.
|
|
|
3192
|
|
|
3193 21.1.10 includes a fix for this that makes more intelligent guesses
|
|
|
3194 about which memory addresses will be free, and this should cure the
|
|
|
3195 problem for most people. 21.4 implements "portable dumping", which
|
|
|
3196 eliminates the problem altogether. We recommend you use the 21.4
|
|
|
3197 binaries, but you can use the 21.1 binaries if you are very paranoid
|
|
|
3198 about stability. @xref{Q1.0.4, Are binaries available?}.
|
|
|
3199
|
|
|
3200 @node Q2.4.3, Q2.4.4, Q2.4.2, Installation
|
|
|
3201 @unnumberedsubsec Q2.4.3: XEmacs won't start without network.
|
|
434
|
3202
|
|
|
3203 If XEmacs starts when you're on the network, but fails when you're not
|
|
|
3204 on the network, you may be missing a "localhost" entry in your
|
|
|
3205 @file{/etc/hosts} file. The file should contain an entry like:
|
|
|
3206
|
|
|
3207 @example
|
|
|
3208 127.0.0.1 localhost
|
|
|
3209 @end example
|
|
|
3210
|
|
|
3211 Add that line, and XEmacs will be happy.
|
|
|
3212
|
|
2417
|
3213 @node Q2.4.4, Q2.4.5, Q2.4.3, Installation
|
|
|
3214 @unnumberedsubsec Q2.4.4: Startup warnings about deducing proper fonts?
|
|
|
3215
|
|
|
3216 How can I avoid the startup warnings about deducing proper fonts?
|
|
|
3217
|
|
|
3218 This is highly dependent on your installation, but try with the
|
|
|
3219 following font as your base font for XEmacs and see what it does:
|
|
|
3220
|
|
|
3221 @format
|
|
|
3222 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
|
|
|
3223 @end format
|
|
|
3224
|
|
|
3225 More precisely, do the following in your resource file:
|
|
|
3226
|
|
|
3227 @format
|
|
|
3228 Emacs.default.attributeFont: \
|
|
|
3229 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
|
|
|
3230 @end format
|
|
|
3231
|
|
|
3232 If you just don't want to see the @samp{*Warnings*} buffer at startup
|
|
|
3233 time, you can set this:
|
|
428
|
3234
|
|
|
3235 @lisp
|
|
2417
|
3236 (setq display-warning-minimum-level 'error)
|
|
428
|
3237 @end lisp
|
|
|
3238
|
|
2417
|
3239 The buffer still exists; it just isn't in your face.
|
|
|
3240
|
|
|
3241 @node Q2.4.5, Q2.4.6, Q2.4.4, Installation
|
|
|
3242 @unnumberedsubsec Q2.4.5: Warnings from incorrect key modifiers.
|
|
|
3243
|
|
|
3244 The following information comes from the @file{PROBLEMS} file that comes
|
|
|
3245 with XEmacs.
|
|
|
3246
|
|
|
3247 If you're having troubles with HP/UX it is because HP/UX defines the
|
|
|
3248 modifiers wrong in X. Here is a shell script to fix the problem; be
|
|
|
3249 sure that it is run after VUE configures the X server.
|
|
428
|
3250
|
|
|
3251 @example
|
|
2417
|
3252 #! /bin/sh
|
|
|
3253 xmodmap 2> /dev/null - << EOF
|
|
|
3254 keysym Alt_L = Meta_L
|
|
|
3255 keysym Alt_R = Meta_R
|
|
|
3256 EOF
|
|
|
3257
|
|
|
3258 xmodmap - << EOF
|
|
|
3259 clear mod1
|
|
|
3260 keysym Mode_switch = NoSymbol
|
|
|
3261 add mod1 = Meta_L
|
|
|
3262 keysym Meta_R = Mode_switch
|
|
|
3263 add mod2 = Mode_switch
|
|
|
3264 EOF
|
|
428
|
3265 @end example
|
|
|
3266
|
|
2417
|
3267 @node Q2.4.6, , Q2.4.5, Installation
|
|
|
3268 @unnumberedsubsec Q2.4.6: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
|
3269
|
|
|
3270 Yes.
|
|
|
3271
|
|
|
3272 The console was there because @file{temacs} (and in turn, @file{xemacs})
|
|
|
3273 was a console application, and Windows typically creates a new
|
|
|
3274 console for a console process unless the creating process requests that
|
|
|
3275 one isn't created. This used to be fixed with @file{runemacs}, a small
|
|
|
3276 Windows application that existed merely to start @file{xemacs}, stating
|
|
|
3277 that it didn't want a console.
|
|
|
3278
|
|
|
3279 XEmacs 21.4 fixes this cleanly by the virtue of being a true "GUI"
|
|
|
3280 application. The explanation of what that means is included for
|
|
|
3281 educational value.
|
|
|
3282
|
|
|
3283 When building an application to be run in a Win32 environment, you must
|
|
|
3284 state which sub-system it is to run in. Valid subsystems include
|
|
|
3285 "console" and "gui". The subsystem you use affects the run time
|
|
|
3286 libraries linked into your application, the start up function that is
|
|
|
3287 run before control is handed over to your application, the entry point
|
|
|
3288 to your program, and how Windows normally invokes your program. (Console
|
|
|
3289 programs automatically get a console created for them at startup if
|
|
|
3290 their stdin/stdout don't point anywhere useful, which is the case when
|
|
|
3291 run from the GUI. This is a stupid design, of course -- instead, the
|
|
|
3292 console should get created only when the first I/O actually occurs!
|
|
|
3293 GUI programs have an equally stupid design: When called from
|
|
|
3294 @file{CMD.EXE}/@file{COMMAND.COM}, their stdin/stdout will be set to
|
|
|
3295 point nowhere useful, even though the command shell has its own
|
|
|
3296 stdin/stdout. It's as if someone who had learned a bit about stdio but
|
|
|
3297 had no actual knowledge of interprocess communication designed the
|
|
|
3298 scheme; unfortunately, the whole process-communication aspect of the
|
|
|
3299 Win32 API is equally badly designed.) For example, the entry point for a
|
|
|
3300 console app is "main" (which is what you'd expect for a C/C++ program),
|
|
|
3301 but the entry point for a "gui" app is "WinMain". This confuses and
|
|
|
3302 annoys a lot of programmers who've grown up on Unix systems, where the
|
|
|
3303 kernel doesn't really care whether your application is a gui program or
|
|
|
3304 not.
|
|
|
3305
|
|
|
3306 For reasons not altogether clear, and are lost in the mists of time and
|
|
|
3307 tradition, XEmacs on Win32 started out as a console application, and
|
|
|
3308 therefore a console was automatically created for it. (It may have been
|
|
|
3309 made a console application partly because a console is needed in some
|
|
|
3310 circumstances, especially under Win95, to interrupt, terminate, or send
|
|
|
3311 signals to a child process, and because of the bogosity mentioned above
|
|
|
3312 with GUI programs and the standard command shell. Currently, XEmacs
|
|
|
3313 just creates and immediately hides a console when necessary, and
|
|
|
3314 works around the "no useful stdio" problem by creating its own console
|
|
|
3315 window as necessary to display messages in.)
|
|
|
3316
|
|
2459
|
3317 @node Editing, Display, Installation, Top
|
|
|
3318 @unnumbered 3 Editing Functions
|
|
2417
|
3319
|
|
|
3320 This is part 3 of the XEmacs Frequently Asked Questions list. This
|
|
2459
|
3321 section is devoted to the editing-related capabilities of XEmacs (the
|
|
|
3322 keyboard, mouse, buffers, text selections, etc.) and how to customize
|
|
|
3323 them.
|
|
2417
|
3324
|
|
|
3325 @menu
|
|
|
3326 3.0: The Keyboard
|
|
2459
|
3327 * Q3.0.1:: How can I customize the keyboard?
|
|
|
3328 * Q3.0.2:: How can I bind complex functions (or macros) to keys?
|
|
|
3329 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down?
|
|
|
3330 * Q3.0.4:: Globally binding @kbd{Delete}?
|
|
|
3331 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
|
3332 * Q3.0.6:: How can you type in special characters in XEmacs?
|
|
|
3333 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys?
|
|
|
3334 * Q3.0.8:: How do I map the arrow keys?
|
|
|
3335 * Q3.0.9:: HP Alt key as Meta.
|
|
|
3336 * Q3.0.10:: Why does edt emulation not work?
|
|
|
3337 * Q3.0.11:: How can I emulate VI and use it as my default mode?
|
|
2417
|
3338
|
|
|
3339 3.1: The Mouse
|
|
|
3340 * Q3.1.1:: How can I turn off Mouse pasting?
|
|
|
3341 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons?
|
|
|
3342 * Q3.1.3:: Clicking the left button does not do anything in buffer list.
|
|
|
3343 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3?
|
|
2459
|
3344 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
|
3345
|
|
|
3346 3.2: Buffers, Text Editing
|
|
|
3347 * Q3.2.1:: Can I have the end of the buffer delimited in some way?
|
|
|
3348 * Q3.2.2:: How do I insert today's date into a buffer?
|
|
|
3349 * Q3.2.3:: How do I get a single minibuffer frame?
|
|
|
3350 * Q3.2.4:: How can I enable auto-indent and/or Filladapt?
|
|
|
3351 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
3352
|
|
|
3353 3.3: Text Selections
|
|
|
3354 * Q3.3.1:: How do I select a rectangular region?
|
|
|
3355 * Q3.3.2:: How can I turn off or change highlighted selections?
|
|
|
3356 * Q3.3.3:: How do I cause typing on an active region to remove it?
|
|
|
3357 * Q3.3.4:: Can I turn off the highlight during isearch?
|
|
|
3358 * Q3.3.5:: Why is killing so slow?
|
|
|
3359 * Q3.3.6:: Why does @kbd{M-w} take so long?
|
|
|
3360
|
|
|
3361 3.4: Editing Source Code
|
|
|
3362 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode?
|
|
|
3363 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly?
|
|
2417
|
3364 @end menu
|
|
|
3365
|
|
|
3366 @unnumberedsec 3.0: The Keyboard
|
|
|
3367
|
|
2459
|
3368 @node Q3.0.1, Q3.0.2, Editing, Editing
|
|
|
3369 @unnumberedsubsec Q3.0.1: How can I customize the keyboard?
|
|
|
3370
|
|
|
3371 #### Write me.
|
|
|
3372
|
|
|
3373 @node Q3.0.2, Q3.0.3, Q3.0.1, Editing
|
|
|
3374 @unnumberedsubsec Q3.0.2: How can I bind complex functions (or macros) to keys?
|
|
428
|
3375
|
|
|
3376 As an example, say you want the @kbd{paste} key on a Sun keyboard to
|
|
|
3377 insert the current Primary X selection at point. You can accomplish this
|
|
|
3378 with:
|
|
|
3379
|
|
|
3380 @lisp
|
|
|
3381 (define-key global-map [f18] 'x-insert-selection)
|
|
|
3382 @end lisp
|
|
|
3383
|
|
|
3384 However, this only works if there is a current X selection (the
|
|
|
3385 selection will be highlighted). The functionality I like is for the
|
|
|
3386 @kbd{paste} key to insert the current X selection if there is one,
|
|
|
3387 otherwise insert the contents of the clipboard. To do this you need to
|
|
|
3388 pass arguments to @code{x-insert-selection}. This is done by wrapping
|
|
|
3389 the call in a 'lambda form:
|
|
|
3390
|
|
|
3391 @lisp
|
|
|
3392 (global-set-key [f18]
|
|
|
3393 (lambda () (interactive) (x-insert-selection t nil)))
|
|
|
3394 @end lisp
|
|
|
3395
|
|
|
3396 This binds the f18 key to a @dfn{generic} functional object. The
|
|
|
3397 interactive spec is required because only interactive functions can be
|
|
|
3398 bound to keys.
|
|
|
3399
|
|
|
3400 For the FAQ example you could use:
|
|
|
3401
|
|
|
3402 @lisp
|
|
|
3403 (global-set-key [(control ?.)]
|
|
|
3404 (lambda () (interactive) (scroll-up 1)))
|
|
440
|
3405 (global-set-key [(control ?;)]
|
|
|
3406 (lambda () (interactive) (scroll-up -1)))
|
|
428
|
3407 @end lisp
|
|
|
3408
|
|
|
3409 This is fine if you only need a few functions within the lambda body.
|
|
2417
|
3410 If you're doing more it's cleaner to define a separate function.
|
|
2459
|
3411 @xref{Q3.0.3, How do I bind C-. and C-; to scroll one line up and
|
|
2417
|
3412 down?}.
|
|
|
3413
|
|
2459
|
3414 @node Q3.0.3, Q3.0.4, Q3.0.2, Editing
|
|
|
3415 @unnumberedsubsec Q3.0.3: How do I bind C-. and C-; to scroll one line up and down?
|
|
428
|
3416
|
|
|
3417 Add the following (Thanks to @email{mly@@adoc.xerox.com, Richard Mlynarik} and
|
|
|
3418 @email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}:
|
|
|
3419
|
|
|
3420 @lisp
|
|
|
3421 (defun scroll-up-one-line ()
|
|
|
3422 (interactive)
|
|
|
3423 (scroll-up 1))
|
|
|
3424
|
|
|
3425 (defun scroll-down-one-line ()
|
|
|
3426 (interactive)
|
|
|
3427 (scroll-down 1))
|
|
|
3428
|
|
|
3429 (global-set-key [(control ?.)] 'scroll-up-one-line) ; C-.
|
|
440
|
3430 (global-set-key [(control ?;)] 'scroll-down-one-line) ; C-;
|
|
428
|
3431 @end lisp
|
|
|
3432
|
|
|
3433 The key point is that you can only bind simple functions to keys; you
|
|
2417
|
3434 can not bind a key to a function that you're also passing arguments
|
|
2459
|
3435 to. (@pxref{Q3.0.2, How can I bind complex functions (or macros) to
|
|
2417
|
3436 keys?} for a better answer).
|
|
|
3437
|
|
2459
|
3438 @node Q3.0.4, Q3.0.5, Q3.0.3, Editing
|
|
|
3439 @unnumberedsubsec Q3.0.4: Globally binding @kbd{Delete}?
|
|
428
|
3440
|
|
|
3441 I cannot manage to globally bind my @kbd{Delete} key to something other
|
|
|
3442 than the default. How does one do this?
|
|
|
3443
|
|
462
|
3444 Answer: The problem is that many modes explicitly bind @kbd{Delete}. To
|
|
|
3445 get around this, try the following:
|
|
|
3446
|
|
428
|
3447 @lisp
|
|
|
3448 (defun foo ()
|
|
|
3449 (interactive)
|
|
|
3450 (message "You hit DELETE"))
|
|
|
3451
|
|
462
|
3452 (define-key key-translation-map 'delete 'redirected-delete)
|
|
|
3453 (global-set-key 'redirected-delete 'foo)
|
|
428
|
3454 @end lisp
|
|
|
3455
|
|
2459
|
3456 @node Q3.0.5, Q3.0.6, Q3.0.4, Editing
|
|
|
3457 @unnumberedsubsec Q3.0.5: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
428
|
3458
|
|
|
3459 The following works in GNU Emacs 19:
|
|
|
3460
|
|
|
3461 @lisp
|
|
|
3462 (global-set-key [help] 'help-command);; Help
|
|
|
3463 @end lisp
|
|
|
3464
|
|
462
|
3465 The following works in XEmacs with the addition of shift:
|
|
428
|
3466
|
|
|
3467 @lisp
|
|
|
3468 (global-set-key [(shift help)] 'help-command);; Help
|
|
|
3469 @end lisp
|
|
|
3470
|
|
|
3471 But it doesn't work alone. This is in the file @file{PROBLEMS} which
|
|
|
3472 should have come with your XEmacs installation: @emph{Emacs ignores the
|
|
|
3473 @kbd{help} key when running OLWM}.
|
|
|
3474
|
|
|
3475 OLWM grabs the @kbd{help} key, and retransmits it to the appropriate
|
|
|
3476 client using
|
|
|
3477 @iftex
|
|
|
3478 @*
|
|
|
3479 @end iftex
|
|
|
3480 @code{XSendEvent}. Allowing Emacs to react to synthetic
|
|
|
3481 events is a security hole, so this is turned off by default. You can
|
|
|
3482 enable it by setting the variable @code{x-allow-sendevents} to t. You
|
|
|
3483 can also cause fix this by telling OLWM to not grab the help key, with
|
|
|
3484 the null binding @code{OpenWindows.KeyboardCommand.Help:}.
|
|
|
3485
|
|
2459
|
3486 @node Q3.0.6, Q3.0.7, Q3.0.5, Editing
|
|
|
3487 @unnumberedsubsec Q3.0.6: How can you type in special characters in XEmacs?
|
|
428
|
3488 One way is to use the package @code{x-compose}. Then you can use
|
|
|
3489 sequences like @kbd{Compose " a} to get ä, etc.
|
|
|
3490
|
|
462
|
3491 Another way is to use the @code{iso-insert} package. Then you can use
|
|
|
3492 sequences like @kbd{C-x 8 " a} to get ä, etc.
|
|
428
|
3493
|
|
|
3494 @email{glynn@@sensei.co.uk, Glynn Clements} writes:
|
|
|
3495
|
|
|
3496 @quotation
|
|
|
3497 It depends upon your X server.
|
|
|
3498
|
|
|
3499 Generally, the simplest way is to define a key as Multi_key with
|
|
|
3500 xmodmap, e.g.
|
|
|
3501 @c hey, show some respect, willya -- there's xkeycaps, isn't there? --
|
|
|
3502 @c chr ;)
|
|
|
3503 @example
|
|
440
|
3504 xmodmap -e 'keycode 0xff20 = Multi_key'
|
|
428
|
3505 @end example
|
|
|
3506
|
|
|
3507 You will need to pick an appropriate keycode. Use xev to find out the
|
|
|
3508 keycodes for each key.
|
|
|
3509
|
|
|
3510 [NB: On a `Windows' keyboard, recent versions of XFree86 automatically
|
|
|
3511 define the right `Windows' key as Multi_key'.]
|
|
|
3512
|
|
|
3513 Once you have Multi_key defined, you can use e.g.
|
|
|
3514 @example
|
|
440
|
3515 Multi a ' => á
|
|
|
3516 Multi e " => ë
|
|
|
3517 Multi c , => ç
|
|
428
|
3518 @end example
|
|
|
3519
|
|
|
3520 etc.
|
|
|
3521
|
|
|
3522 Also, recent versions of XFree86 define various AltGr-<key>
|
|
|
3523 combinations as dead keys, i.e.
|
|
|
3524 @example
|
|
440
|
3525 AltGr [ => dead_diaeresis
|
|
|
3526 AltGr ] => dead_tilde
|
|
|
3527 AltGr ; => dead_acute
|
|
428
|
3528 @end example
|
|
|
3529 etc.
|
|
|
3530
|
|
|
3531 Running @samp{xmodmap -pk} will list all of the defined keysyms.
|
|
|
3532 @end quotation
|
|
|
3533
|
|
1135
|
3534 For the related problem of @emph{displaying} non-ASCII characters in a
|
|
2459
|
3535 non-Mule XEmacs, @xref{Q4.0.8, How do I display non-ASCII characters?}.
|
|
|
3536
|
|
|
3537 @node Q3.0.7, Q3.0.8, Q3.0.6, Editing
|
|
|
3538 @unnumberedsubsec Q3.0.7: Can I turn on @dfn{sticky} modifier keys?
|
|
428
|
3539
|
|
|
3540 Yes, with @code{(setq modifier-keys-are-sticky t)}. This will give the
|
|
|
3541 effect of being able to press and release Shift and have the next
|
|
|
3542 character typed come out in upper case. This will affect all the other
|
|
|
3543 modifier keys like Control and Meta as well.
|
|
|
3544
|
|
|
3545 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
|
3546
|
|
|
3547 @quotation
|
|
|
3548 One thing about the sticky modifiers is that if you move the mouse out
|
|
|
3549 of the frame and back in, it cancels all currently ``stuck'' modifiers.
|
|
|
3550 @end quotation
|
|
|
3551
|
|
2459
|
3552 @node Q3.0.8, Q3.0.9, Q3.0.7, Editing
|
|
|
3553 @unnumberedsubsec Q3.0.8: How do I map the arrow keys?
|
|
428
|
3554 @c New
|
|
|
3555 Say you want to map @kbd{C-@key{right}} to forward-word:
|
|
|
3556
|
|
|
3557 @email{sds@@usa.net, Sam Steingold} writes:
|
|
|
3558
|
|
|
3559 @quotation
|
|
|
3560 @lisp
|
|
|
3561 ; both XEmacs and Emacs
|
|
|
3562 (define-key global-map [(control right)] 'forward-word)
|
|
|
3563 @end lisp
|
|
|
3564 or
|
|
|
3565 @lisp
|
|
|
3566 ; Emacs only
|
|
|
3567 (define-key global-map [C-right] 'forward-word)
|
|
|
3568 @end lisp
|
|
|
3569 or
|
|
|
3570 @lisp
|
|
|
3571 ; ver > 20, both
|
|
|
3572 (define-key global-map (kbd "C-<right>") 'forward-word)
|
|
|
3573 @end lisp
|
|
|
3574 @end quotation
|
|
|
3575
|
|
2459
|
3576 @node Q3.0.9, Q3.0.10, Q3.0.8, Editing
|
|
|
3577 @unnumberedsubsec Q3.0.9: HP Alt key as Meta.
|
|
2417
|
3578
|
|
|
3579 How can I make XEmacs recognize the Alt key of my HP workstation as a
|
|
|
3580 Meta key?
|
|
|
3581
|
|
|
3582 Put the following line into a file and load it with xmodmap(1) before
|
|
|
3583 starting XEmacs:
|
|
428
|
3584
|
|
|
3585 @example
|
|
2417
|
3586 remove Mod1 = Mode_switch
|
|
428
|
3587 @end example
|
|
|
3588
|
|
2459
|
3589 @node Q3.0.10, Q3.0.11, Q3.0.9, Editing
|
|
|
3590 @unnumberedsubsec Q3.0.10: Why does edt emulation not work?
|
|
2417
|
3591
|
|
|
3592 We don't know, but you can use tpu-edt emulation instead, which works
|
|
|
3593 fine and is a little fancier than the standard edt emulation. To do
|
|
|
3594 this, add the following line to your @file{init.el}:
|
|
|
3595
|
|
|
3596 @lisp
|
|
|
3597 (tpu-edt)
|
|
|
3598 @end lisp
|
|
|
3599
|
|
|
3600 If you don't want it to replace @kbd{C-h} with an edt-style help menu
|
|
|
3601 add this as well:
|
|
428
|
3602
|
|
|
3603 @lisp
|
|
2417
|
3604 (global-set-key [(control h)] 'help-for-help)
|
|
428
|
3605 @end lisp
|
|
|
3606
|
|
2459
|
3607 @node Q3.0.11, Q3.1.1, Q3.0.10, Editing
|
|
|
3608 @unnumberedsubsec Q3.0.11: How can I emulate VI and use it as my default mode?
|
|
2417
|
3609
|
|
|
3610 Our recommended VI emulator is viper. To make viper-mode the default,
|
|
|
3611 add this to your @file{init.el}:
|
|
428
|
3612
|
|
|
3613 @lisp
|
|
2417
|
3614 (viper-mode)
|
|
428
|
3615 @end lisp
|
|
|
3616
|
|
2417
|
3617 @email{kifer@@CS.SunySB.EDU, Michael Kifer} writes:
|
|
|
3618
|
|
|
3619 @quotation
|
|
|
3620 This should be added as close to the top of @file{init.el} as you can get
|
|
|
3621 it, otherwise some minor modes may not get viper-ized.
|
|
|
3622 @end quotation
|
|
|
3623
|
|
|
3624 @unnumberedsec 3.1: The Mouse
|
|
|
3625
|
|
2459
|
3626 @node Q3.1.1, Q3.1.2, Q3.0.11, Editing
|
|
2417
|
3627 @unnumberedsubsec Q3.1.1: How can I turn off Mouse pasting?
|
|
428
|
3628
|
|
|
3629 I keep hitting the middle mouse button by accident and getting stuff
|
|
|
3630 pasted into my buffer so how can I turn this off?
|
|
|
3631
|
|
|
3632 Here is an alternative binding, whereby the middle mouse button selects
|
|
|
3633 (but does not cut) the expression under the mouse. Clicking middle on a
|
|
|
3634 left or right paren will select to the matching one. Note that you can
|
|
|
3635 use @code{define-key} or @code{global-set-key}.
|
|
|
3636
|
|
|
3637 @lisp
|
|
|
3638 (defun mouse-set-point-and-select (event)
|
|
|
3639 "Sets the point at the mouse location, then marks following form"
|
|
|
3640 (interactive "@@e")
|
|
|
3641 (mouse-set-point event)
|
|
|
3642 (mark-sexp 1))
|
|
|
3643 (define-key global-map [button2] 'mouse-set-point-and-select)
|
|
|
3644 @end lisp
|
|
|
3645
|
|
2459
|
3646 @node Q3.1.2, Q3.1.3, Q3.1.1, Editing
|
|
2417
|
3647 @unnumberedsubsec Q3.1.2: How do I set control/meta/etc modifiers on mouse buttons?
|
|
428
|
3648
|
|
|
3649 Use, for instance, @code{[(meta button1)]}. For example, here is a common
|
|
|
3650 setting for Common Lisp programmers who use the bundled @code{ilisp}
|
|
|
3651 package, whereby meta-button1 on a function name will find the file where
|
|
|
3652 the function name was defined, and put you at that location in the source
|
|
|
3653 file.
|
|
|
3654
|
|
|
3655 [Inside a function that gets called by the lisp-mode-hook and
|
|
|
3656 ilisp-mode-hook]
|
|
|
3657
|
|
|
3658 @lisp
|
|
|
3659 (local-set-key [(meta button1)] 'edit-definitions-lisp)
|
|
|
3660 @end lisp
|
|
|
3661
|
|
2459
|
3662 @node Q3.1.3, Q3.1.4, Q3.1.2, Editing
|
|
2417
|
3663 @unnumberedsubsec Q3.1.3: Clicking the left button does not do anything in buffer list.
|
|
428
|
3664
|
|
|
3665 I do @kbd{C-x C-b} to get a list of buffers and the entries get
|
|
|
3666 highlighted when I move the mouse over them but clicking the left mouse
|
|
|
3667 does not do anything.
|
|
|
3668
|
|
|
3669 Use the middle mouse button.
|
|
|
3670
|
|
2459
|
3671 @node Q3.1.4, Q3.1.5, Q3.1.3, Editing
|
|
2417
|
3672 @unnumberedsubsec Q3.1.4: How can I get a list of buffers when I hit mouse button 3?
|
|
428
|
3673
|
|
|
3674 The following code will replace the default popup on button3:
|
|
|
3675
|
|
|
3676 @lisp
|
|
|
3677 (global-set-key [button3] 'popup-buffer-menu)
|
|
|
3678 @end lisp
|
|
|
3679
|
|
2459
|
3680 @node Q3.1.5, Q3.2.1, Q3.1.4, Editing
|
|
|
3681 @unnumberedsubsec Q3.1.5: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
428
|
3682
|
|
|
3683 By default XEmacs pastes X selections where the mouse pointer is. How
|
|
|
3684 do I disable this?
|
|
|
3685
|
|
|
3686 Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank
|
|
|
3687 @key{RET}}.
|
|
|
3688
|
|
2417
|
3689 To get XEmacs to paste at the text cursor, add this your @file{init.el}:
|
|
428
|
3690
|
|
|
3691 @lisp
|
|
|
3692 (setq mouse-yank-at-point t)
|
|
|
3693 @end lisp
|
|
|
3694
|
|
2459
|
3695 You can also change this with Customize. Select from the
|
|
|
3696 @code{Options} menu @code{Advanced
|
|
|
3697 (Customize)->Emacs->Editing->Mouse->Yank At Point...} or type @kbd{M-x
|
|
|
3698 customize @key{RET} mouse @key{RET}}.
|
|
|
3699
|
|
|
3700 @unnumberedsec 3.2: Buffers, Text Editing
|
|
|
3701
|
|
|
3702 @node Q3.2.1, Q3.2.2, Q3.1.5, Editing
|
|
|
3703 @unnumberedsubsec Q3.2.1: Can I have the end of the buffer delimited in some way?
|
|
|
3704
|
|
|
3705 Say, with: @samp{[END]}?
|
|
|
3706
|
|
|
3707 Try this:
|
|
|
3708
|
|
|
3709 @lisp
|
|
|
3710 (let ((ext (make-extent (point-min) (point-max))))
|
|
|
3711 (set-extent-property ext 'start-closed t)
|
|
|
3712 (set-extent-property ext 'end-closed t)
|
|
|
3713 (set-extent-property ext 'detachable nil)
|
|
|
3714 (set-extent-end-glyph ext (make-glyph [string :data "[END]"])))
|
|
|
3715 @end lisp
|
|
|
3716
|
|
|
3717 Since this is XEmacs, you can specify an icon to be shown on
|
|
|
3718 window-system devices. To do so, change the @code{make-glyph} call to
|
|
|
3719 something like this:
|
|
|
3720
|
|
|
3721 @lisp
|
|
|
3722 (make-glyph '([xpm :file "~/something.xpm"]
|
|
|
3723 [string :data "[END]"]))
|
|
|
3724 @end lisp
|
|
|
3725
|
|
|
3726 You can inline the @sc{xpm} definition yourself by specifying
|
|
|
3727 @code{:data} instead of @code{:file}. Here is such a full-featured
|
|
|
3728 version that works on both X and TTY devices:
|
|
|
3729
|
|
|
3730 @lisp
|
|
|
3731 (let ((ext (make-extent (point-min) (point-max))))
|
|
|
3732 (set-extent-property ext 'start-closed t)
|
|
|
3733 (set-extent-property ext 'end-closed t)
|
|
|
3734 (set-extent-property ext 'detachable nil)
|
|
|
3735 (set-extent-end-glyph ext (make-glyph '([xpm :data "\
|
|
|
3736 /* XPM */
|
|
|
3737 static char* eye = @{
|
|
|
3738 \"20 11 7 2\",
|
|
|
3739 \"__ c None\"
|
|
|
3740 \"_` c #7f7f7f\",
|
|
|
3741 \"_a c #fefefe\",
|
|
|
3742 \"_b c #7f0000\",
|
|
|
3743 \"_c c #fefe00\",
|
|
|
3744 \"_d c #fe0000\",
|
|
|
3745 \"_e c #bfbfbf\",
|
|
|
3746 \"___________`_`_`___b_b_b_b_________`____\",
|
|
|
3747 \"_________`_`_`___b_c_c_c_b_b____________\",
|
|
|
3748 \"_____`_`_`_e___b_b_c_c_c___b___b_______`\",
|
|
|
3749 \"___`_`_e_a___b_b_d___b___b___b___b______\",
|
|
|
3750 \"_`_`_e_a_e___b_b_d_b___b___b___b___b____\",
|
|
|
3751 \"_`_`_a_e_a___b_b_d___b___b___b___b___b__\",
|
|
|
3752 \"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\",
|
|
|
3753 \"___`_`_e_a___b_b_b_d_c___b___b___d_b____\",
|
|
|
3754 \"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\",
|
|
|
3755 \"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\",
|
|
|
3756 \"___`_____`_`_`_`___b_b_b_b_b_b__________\",
|
|
|
3757 @} ;"]
|
|
|
3758 [string :data "[END]"]))))
|
|
|
3759 @end lisp
|
|
|
3760
|
|
|
3761 Note that you might want to make this a function, and put it to a hook.
|
|
|
3762 We leave that as an exercise for the reader.
|
|
|
3763
|
|
|
3764 @node Q3.2.2, Q3.2.3, Q3.2.1, Editing
|
|
|
3765 @unnumberedsubsec Q3.2.2: How do I insert today's date into a buffer?
|
|
2417
|
3766
|
|
|
3767 Like this:
|
|
428
|
3768
|
|
|
3769 @lisp
|
|
2459
|
3770 (insert (current-time-string))
|
|
2417
|
3771 @end lisp
|
|
|
3772
|
|
2459
|
3773 @node Q3.2.3, Q3.2.4, Q3.2.2, Editing
|
|
|
3774 @unnumberedsubsec Q3.2.3: How do I get a single minibuffer frame?
|
|
|
3775
|
|
|
3776 @email{acs@@acm.org, Vin Shelton} writes:
|
|
2417
|
3777
|
|
|
3778 @lisp
|
|
2459
|
3779 (setq initial-frame-plist '(minibuffer nil))
|
|
|
3780 (setq default-frame-plist '(minibuffer nil))
|
|
|
3781 (setq default-minibuffer-frame
|
|
|
3782 (make-frame
|
|
|
3783 '(minibuffer only
|
|
|
3784 width 86
|
|
|
3785 height 1
|
|
|
3786 menubar-visible-p nil
|
|
|
3787 default-toolbar-visible-p nil
|
|
|
3788 name "minibuffer"
|
|
|
3789 top -2
|
|
|
3790 left -2
|
|
|
3791 has-modeline-p nil)))
|
|
|
3792 (frame-notice-user-settings)
|
|
2417
|
3793 @end lisp
|
|
|
3794
|
|
2459
|
3795 @strong{Please note:} The single minibuffer frame may not be to everyone's
|
|
|
3796 taste, and there any number of other XEmacs options settings that may
|
|
|
3797 make it difficult or inconvenient to use.
|
|
|
3798
|
|
|
3799 @node Q3.2.4, Q3.2.5, Q3.2.3, Editing
|
|
|
3800 @unnumberedsubsec Q3.2.4: How can I enable auto-indent and/or Filladapt?
|
|
|
3801
|
|
|
3802 Put the following line in your @file{init.el}:
|
|
428
|
3803
|
|
|
3804 @lisp
|
|
2459
|
3805 (setq indent-line-function 'indent-relative-maybe)
|
|
428
|
3806 @end lisp
|
|
|
3807
|
|
2459
|
3808 If you want to get fancy, try the @code{filladapt} package available
|
|
|
3809 standard with XEmacs. Put this into your @file{init.el}:
|
|
428
|
3810
|
|
|
3811 @lisp
|
|
2459
|
3812 (require 'filladapt)
|
|
|
3813 (setq-default filladapt-mode t)
|
|
|
3814 (add-hook 'c-mode-hook 'turn-off-filladapt-mode)
|
|
428
|
3815 @end lisp
|
|
|
3816
|
|
2459
|
3817 This will enable Filladapt for all modes except C mode, where it doesn't
|
|
|
3818 work well. To turn Filladapt on only in particular major modes, remove
|
|
|
3819 the @code{(setq-default ...)} line and use
|
|
|
3820 @code{turn-on-filladapt-mode}, like this:
|
|
428
|
3821
|
|
|
3822 @lisp
|
|
2459
|
3823 (add-hook 'text-mode-hook 'turn-on-filladapt-mode)
|
|
428
|
3824 @end lisp
|
|
2417
|
3825
|
|
2459
|
3826 You can customize filling and adaptive filling with Customize.
|
|
|
3827 Select from the @code{Options} menu
|
|
|
3828 @code{Advanced (Customize)->Emacs->Editing->Fill->Fill...}
|
|
|
3829 or type @kbd{M-x customize @key{RET} fill @key{RET}}.
|
|
|
3830
|
|
|
3831 Note that well-behaving text-lookalike modes will run
|
|
|
3832 @code{text-mode-hook} by default (e.g. that's what Message does). For
|
|
|
3833 the nasty ones, you'll have to provide the @code{add-hook}s yourself.
|
|
|
3834
|
|
|
3835 Please note that the @code{fa-extras} package is no longer useful.
|
|
|
3836
|
|
|
3837 @node Q3.2.5, Q3.3.1, Q3.2.4, Editing
|
|
|
3838 @unnumberedsubsec Q3.2.5: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
3839
|
|
|
3840 Try the following lisp in your @file{init.el}:
|
|
2417
|
3841
|
|
|
3842 @lisp
|
|
2459
|
3843 (setq default-major-mode 'text-mode)
|
|
|
3844 (setq text-mode-hook 'turn-on-auto-fill)
|
|
2417
|
3845 @end lisp
|
|
|
3846
|
|
2459
|
3847 @strong{WARNING}: note that changing the value of
|
|
|
3848 @code{default-major-mode} from @code{fundamental-mode} can break a large
|
|
|
3849 amount of built-in code that expects newly created buffers to be in
|
|
|
3850 @code{fundamental-mode}. (Changing from @code{fundamental-mode} to
|
|
|
3851 @code{text-mode} might not wreak too much havoc, but changing to
|
|
|
3852 something more exotic like a lisp-mode would break many Emacs packages).
|
|
|
3853
|
|
|
3854 Note that Emacs by default starts up in buffer @code{*scratch*} in
|
|
|
3855 @code{initial-major-mode}, which defaults to
|
|
|
3856 @code{lisp-interaction-mode}. Thus adding the following form to your
|
|
|
3857 Emacs init file will cause the initial @code{*scratch*} buffer to be put
|
|
|
3858 into auto-fill'ed @code{text-mode}:
|
|
2417
|
3859
|
|
|
3860 @lisp
|
|
2459
|
3861 (setq initial-major-mode
|
|
|
3862 (lambda ()
|
|
|
3863 (text-mode)
|
|
|
3864 (turn-on-auto-fill)))
|
|
2417
|
3865 @end lisp
|
|
|
3866
|
|
2459
|
3867 Note that after your init file is loaded, if
|
|
|
3868 @code{inhibit-startup-message} is @code{nil} (the default) and the
|
|
|
3869 startup buffer is @code{*scratch*} then the startup message will be
|
|
|
3870 inserted into @code{*scratch*}; it will be removed after a timeout by
|
|
|
3871 erasing the entire @code{*scratch*} buffer. Keep in mind this default
|
|
|
3872 usage of @code{*scratch*} if you desire any prior manipulation of
|
|
|
3873 @code{*scratch*} from within your Emacs init file. In particular,
|
|
|
3874 anything you insert into @code{*scratch*} from your init file will be
|
|
|
3875 later erased. Also, if you change the mode of the @code{*scratch*}
|
|
|
3876 buffer, be sure that this will not interfere with possible later
|
|
|
3877 insertion of the startup message (e.g. if you put @code{*scratch*} into
|
|
|
3878 a nonstandard mode that has automatic font lock rules, then the startup
|
|
|
3879 message might get fontified in a strange foreign manner, e.g. as code in
|
|
|
3880 some programming language).
|
|
|
3881
|
|
|
3882 @unnumberedsec 3.3: Text Selections
|
|
|
3883
|
|
|
3884 @node Q3.3.1, Q3.3.2, Q3.2.5, Editing
|
|
|
3885 @unnumberedsubsec Q3.3.1: How do I select a rectangular region?
|
|
2417
|
3886
|
|
|
3887 Just select the region normally, then use the rectangle commands (e.g.
|
|
|
3888 @code{kill-rectangle} on it. The region does not highlight as a
|
|
|
3889 rectangle, but the commands work just fine.
|
|
|
3890
|
|
|
3891 To actually sweep out rectangular regions with the mouse you can use
|
|
|
3892 @code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}.
|
|
|
3893 Then use rectangle commands.
|
|
|
3894
|
|
|
3895 You can also do the following to change default behavior to sweep out
|
|
|
3896 rectangular regions:
|
|
|
3897
|
|
|
3898 @lisp
|
|
|
3899 (setq mouse-track-rectangle-p t)
|
|
|
3900 @end lisp
|
|
|
3901
|
|
2459
|
3902 You can also change this with Customize.
|
|
2417
|
3903 Select from the @code{Options} menu
|
|
|
3904 @code{Advanced (Customize)->Emacs->Editing->Mouse->Track Rectangle...} or type
|
|
|
3905 @kbd{M-x customize @key{RET} mouse @key{RET}}.
|
|
|
3906
|
|
|
3907
|
|
|
3908 @example
|
|
|
3909 mouse-track-do-rectangle: (event)
|
|
|
3910 -- an interactive compiled Lisp function.
|
|
|
3911 Like `mouse-track' but selects rectangles instead of regions.
|
|
|
3912 @end example
|
|
|
3913
|
|
2459
|
3914 @node Q3.3.2, Q3.3.3, Q3.3.1, Editing
|
|
|
3915 @unnumberedsubsec Q3.3.2: How can I turn off or change highlighted selections?
|
|
428
|
3916
|
|
|
3917 The @code{zmacs} mode allows for what some might call gratuitous
|
|
|
3918 highlighting for selected regions (either by setting mark or by using
|
|
|
3919 the mouse). This is the default behavior. To turn off, add the
|
|
2417
|
3920 following line to your @file{init.el} file:
|
|
428
|
3921
|
|
|
3922 @lisp
|
|
|
3923 (setq zmacs-regions nil)
|
|
|
3924 @end lisp
|
|
|
3925
|
|
2417
|
3926 You can also change this with Customize. Select from the
|
|
|
3927 @code{Options} menu
|
|
|
3928 @code{Advanced (Customize)->Emacs->Editing->Basics->Zmacs Regions}
|
|
|
3929 or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
|
|
|
3930
|
|
|
3931 To change the face for selection, look at @code{Options->Advanced (Customize)}
|
|
|
3932 on the menubar.
|
|
|
3933
|
|
2459
|
3934 @node Q3.3.3, Q3.3.4, Q3.3.2, Editing
|
|
|
3935 @unnumberedsubsec Q3.3.3: How do I cause typing on an active region to remove it?
|
|
428
|
3936
|
|
|
3937 I want to change things so that if I select some text and start typing,
|
|
|
3938 the typed text replaces the selected text, similar to Motif.
|
|
|
3939
|
|
|
3940 You want to use something called @dfn{pending delete}. Pending delete
|
|
|
3941 is what happens when you select a region (with the mouse or keyboard)
|
|
|
3942 and you press a key to replace the selected region by the key you typed.
|
|
|
3943 Usually backspace kills the selected region.
|
|
|
3944
|
|
2164
|
3945 To get this behavior, ensure that you have the @file{pc} package
|
|
|
3946 installed, and add the following lines to your
|
|
2417
|
3947 @file{init.el}:
|
|
428
|
3948
|
|
|
3949 @lisp
|
|
438
|
3950 (cond
|
|
|
3951 ((fboundp 'turn-on-pending-delete)
|
|
|
3952 (turn-on-pending-delete))
|
|
|
3953 ((fboundp 'pending-delete-on)
|
|
|
3954 (pending-delete-on t)))
|
|
428
|
3955 @end lisp
|
|
|
3956
|
|
1138
|
3957 Note that this will work with both Backspace and Delete. This code is a
|
|
438
|
3958 tad more complicated than it has to be for XEmacs in order to make it
|
|
|
3959 more portable.
|
|
428
|
3960
|
|
2459
|
3961 @node Q3.3.4, Q3.3.5, Q3.3.3, Editing
|
|
|
3962 @unnumberedsubsec Q3.3.4: Can I turn off the highlight during isearch?
|
|
428
|
3963
|
|
|
3964 I do not like my text highlighted while I am doing isearch as I am not
|
|
|
3965 able to see what's underneath. How do I turn it off?
|
|
|
3966
|
|
2417
|
3967 Put the following in your @file{init.el}:
|
|
428
|
3968
|
|
|
3969 @lisp
|
|
|
3970 (setq isearch-highlight nil)
|
|
|
3971 @end lisp
|
|
|
3972
|
|
2459
|
3973 You can also change this with Customize. Type
|
|
428
|
3974 @kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}.
|
|
|
3975
|
|
|
3976 Note also that isearch-highlight affects query-replace and ispell.
|
|
|
3977 Instead of disabling isearch-highlight you may find that a better
|
|
|
3978 solution consists of customizing the @code{isearch} face.
|
|
|
3979
|
|
2459
|
3980 @node Q3.3.5, Q3.3.6, Q3.3.4, Editing
|
|
|
3981 @unnumberedsubsec Q3.3.5: Why is killing so slow?
|
|
892
|
3982
|
|
|
3983 This actually is an X Windows question, although you'll notice it with
|
|
|
3984 keyboard operations as well as while using the GUI. Basically, there
|
|
|
3985 are four ways to communicate interprogram via the X server:
|
|
|
3986
|
|
|
3987 @table @strong
|
|
|
3988 @item Primary selection
|
|
|
3989 a transient selection that gets replaced every time a new selection is made
|
|
|
3990
|
|
|
3991 @item Secondary selection
|
|
|
3992 for "exchanging" with the primary selection
|
|
|
3993
|
|
|
3994 @item Cut buffers
|
|
|
3995 a clipboard internal to the X server (deprecated)
|
|
|
3996
|
|
|
3997 @item Clipboard selection
|
|
|
3998 a selection with a notification protocol that allows a separate app to
|
|
|
3999 manage the clipboard
|
|
|
4000 @end table
|
|
|
4001
|
|
|
4002 The cut buffers are deprecated because managing them is even more
|
|
|
4003 inefficient than the clipboard notification protocol. The primary
|
|
|
4004 selection works fine for many users and applications, but is not very
|
|
|
4005 robust under intensive or sophisticated use.
|
|
|
4006
|
|
|
4007 In Motif and MS Windows, a clipboard has become the primary means for
|
|
|
4008 managing cut and paste. These means that "modern" applications tend to
|
|
|
4009 be oriented toward a true clipboard, rather than the primary selection.
|
|
|
4010 (On Windows, there is nothing equivalent to the primary selection.)
|
|
|
4011 It's not that XEmacs doesn't support the simple primary selection
|
|
|
4012 method, it's that more and more other applications don't.
|
|
|
4013
|
|
|
4014 So the slowdown occurs because XEmacs now engages in the clipboard
|
|
|
4015 notification protocol on @emph{every} kill. This is especially slow on
|
|
|
4016 Motif.
|
|
|
4017
|
|
|
4018 With most people running most clients and server on the same host, and
|
|
|
4019 many of the rest working over very fast communication, you may expect
|
|
|
4020 that the situation is not going to improve.
|
|
|
4021
|
|
|
4022 There are a number of workarounds. The most effective is to use a
|
|
|
4023 special command to do selection ownership only when you intend to paste
|
|
|
4024 to another application. Useful commands are @code{kill-primary-selection}
|
|
|
4025 and @code{copy-primary-selection}. These work only on text selected
|
|
|
4026 with the mouse (probably; experiment), and are bound by default to the
|
|
|
4027 @kbd{Cut} and @kbd{Copy}, respectively, buttons on the toolbar.
|
|
|
4028 @code{copy-primary-selection} is also bound to @kbd{C-Insert}. You can
|
|
|
4029 yank the clipboard contents with @code{yank-primary-selection}, bound to
|
|
|
4030 the @kbd{Paste} toolbar button and @kbd{Sh-Insert}.
|
|
|
4031
|
|
|
4032 If you are communicating by cut and paste with applications that use the
|
|
|
4033 primary selection, then you can customize
|
|
|
4034 @code{interprogram-cut-function} to @code{nil}, restoring the XEmacs
|
|
|
4035 version 20 behavior. How can you tell if a program will support this?
|
|
|
4036 Motifly-correct programs require the clipboard; you lose. For others,
|
|
|
4037 only by trying it. You also need to customize the complementary
|
|
|
4038 @code{interprogram-paste-function} to @code{nil}. (Otherwise
|
|
|
4039 XEmacs-to-XEmacs pastes will not work correctly.)
|
|
|
4040
|
|
|
4041 You may get some relief on Motif by setting
|
|
|
4042 @code{x-selection-strict-motif-ownership} to nil, but this means you will
|
|
|
4043 only intermittently be able to paste XEmacs kills to Motif applications.
|
|
|
4044
|
|
|
4045 Thanks to Jeff Mincy and Glynn Clements for corrections.
|
|
|
4046
|
|
2459
|
4047 @node Q3.3.6, Q3.4.1, Q3.3.5, Editing
|
|
|
4048 @unnumberedsubsec Q3.3.6: Why does @kbd{M-w} take so long?
|
|
2417
|
4049
|
|
|
4050 It actually doesn't. It leaves the region visible for a second so that
|
|
|
4051 you can see what area is being yanked. If you start working, though, it
|
|
|
4052 will immediately complete its operation. In other words, it will only
|
|
|
4053 delay for a second if you let it.
|
|
|
4054
|
|
2459
|
4055 @unnumberedsec 3.4: Editing Source Code
|
|
|
4056
|
|
|
4057 @node Q3.4.1, Q3.4.2, Q3.3.6, Editing
|
|
|
4058 @unnumberedsubsec Q3.4.1: I do not like cc-mode. How do I use the old c-mode?
|
|
2417
|
4059
|
|
|
4060 Well, first off, consider if you really want to do this. cc-mode is
|
|
|
4061 much more powerful than the old c-mode. If you're having trouble
|
|
|
4062 getting your old offsets to work, try using @code{c-set-offset} instead.
|
|
|
4063 You might also consider using the package @code{cc-compat}.
|
|
|
4064
|
|
|
4065 But, if you still insist, add the following lines to your @file{init.el}:
|
|
|
4066
|
|
|
4067 @lisp
|
|
|
4068 (fmakunbound 'c-mode)
|
|
|
4069 (makunbound 'c-mode-map)
|
|
|
4070 (fmakunbound 'c++-mode)
|
|
|
4071 (makunbound 'c++-mode-map)
|
|
|
4072 (makunbound 'c-style-alist)
|
|
|
4073 (load-library "old-c-mode")
|
|
|
4074 (load-library "old-c++-mode")
|
|
|
4075 @end lisp
|
|
|
4076
|
|
|
4077 This must be done before any other reference is made to either c-mode or
|
|
|
4078 c++-mode.
|
|
|
4079
|
|
2459
|
4080 @node Q3.4.2, , Q3.4.1, Editing
|
|
|
4081 @unnumberedsubsec Q3.4.2: How do you make XEmacs indent CL if-clauses correctly?
|
|
2417
|
4082
|
|
|
4083 I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the
|
|
|
4084 same amount instead of indenting the 3rd clause differently from the
|
|
|
4085 first two.
|
|
|
4086
|
|
2459
|
4087 The package @code{cl-indent} that comes with XEmacs sets up this kind
|
|
|
4088 of indentation by default. @code{cl-indent} also knows about many
|
|
|
4089 other CL-specific forms. To use @code{cl-indent}, one can do this:
|
|
2417
|
4090
|
|
|
4091 @lisp
|
|
2459
|
4092 (setq lisp-indent-function 'common-lisp-indent-function)
|
|
2417
|
4093 @end lisp
|
|
|
4094
|
|
|
4095 One can also customize @file{cl-indent.el} so it mimics the default
|
|
|
4096 @code{if} indentation @code{then} indented more than the @code{else}.
|
|
|
4097 Here's how:
|
|
|
4098
|
|
|
4099 @lisp
|
|
|
4100 (put 'if 'common-lisp-indent-function '(nil nil &body))
|
|
|
4101 @end lisp
|
|
|
4102
|
|
2459
|
4103 @node Display, External Subsystems, Editing, Top
|
|
|
4104 @unnumbered 4 Display Functions
|
|
428
|
4105
|
|
|
4106 This is part 4 of the XEmacs Frequently Asked Questions list. This
|
|
2459
|
4107 section is devoted to the display-related capabilities of XEmacs
|
|
|
4108 (fonts, colors, modeline, menubar, toolbar, scrollbar, etc.) and how
|
|
|
4109 to customize them.
|
|
|
4110
|
|
|
4111 @menu
|
|
|
4112 4.0: Textual Fonts and Colors
|
|
|
4113 * Q4.0.1:: How do I specify a font?
|
|
|
4114 * Q4.0.2:: How do I set the text, menu and modeline fonts?
|
|
|
4115 * Q4.0.3:: How can I set color options from @file{init.el}?
|
|
|
4116 * Q4.0.4:: How can I set the colors when highlighting a region?
|
|
|
4117 * Q4.0.5:: How can I limit color map usage?
|
|
|
4118 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them.
|
|
|
4119 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs?
|
|
|
4120 * Q4.0.8:: How do I display non-ASCII characters?
|
|
|
4121 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}.
|
|
|
4122
|
|
|
4123 4.1: Syntax Highlighting (Font Lock)
|
|
|
4124 * Q4.1.1:: How can I do source code highlighting using font-lock?
|
|
|
4125 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
4126
|
|
|
4127 4.2: The Modeline
|
|
|
4128 * Q4.2.1:: How can I make the modeline go away?
|
|
|
4129 * Q4.2.2:: How do you have XEmacs display the line number in the modeline?
|
|
|
4130 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline?
|
|
|
4131 * Q4.2.4:: How can I change the modeline color based on the mode used?
|
|
|
4132
|
|
|
4133 4.3: The Cursor
|
|
|
4134 * Q4.3.1:: Is there a way to make the bar cursor thicker?
|
|
|
4135 * Q4.3.2:: Is there a way to get back the block cursor?
|
|
|
4136 * Q4.3.3:: Can I make the cursor blink?
|
|
|
4137
|
|
|
4138 4.4: The Menubar
|
|
|
4139 * Q4.4.1:: How do I get rid of the menubar?
|
|
|
4140 * Q4.4.2:: How can I customize the menubar?
|
|
|
4141 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
4142 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
4143 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
4144
|
|
|
4145 4.5: The Toolbar
|
|
|
4146 * Q4.5.1:: How do I get rid of the toolbar?
|
|
|
4147 * Q4.5.2:: How can I customize the toolbar?
|
|
|
4148 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar?
|
|
|
4149 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar
|
|
|
4150
|
|
|
4151 4.6: Scrollbars and Scrolling
|
|
|
4152 * Q4.6.1:: How can I disable the scrollbar?
|
|
|
4153 * Q4.6.2:: How can I change the scrollbar width?
|
|
|
4154 * Q4.6.3:: How can I use resources to change scrollbar colors?
|
|
|
4155 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this?
|
|
|
4156 * Q4.6.5:: Scrolling one line at a time.
|
|
|
4157 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
4158 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
4159
|
|
|
4160 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
4161 * Q4.7.1:: How can I disable the gutter tabs?
|
|
|
4162 * Q4.7.2:: How can I disable the progress bar?
|
|
|
4163 * Q4.7.3:: There are bugs in the gutter or widgets.
|
|
|
4164 * Q4.7.4:: How can I customize the gutter or gutter tabs?
|
|
|
4165 @end menu
|
|
|
4166
|
|
|
4167 @unnumberedsec 4.0: Textual Fonts and Colors
|
|
|
4168
|
|
|
4169 @node Q4.0.1, Q4.0.2, Display, Display
|
|
|
4170 @unnumberedsubsec Q4.0.1: How do I specify a font?
|
|
|
4171
|
|
|
4172 #### Update me.
|
|
|
4173
|
|
|
4174 In 21.4 and above, you can use the @samp{Options} menu to change the font.
|
|
|
4175 You can also do it in your init file, e.g. like this (for MS Windows):
|
|
|
4176
|
|
|
4177 @display
|
|
|
4178 (set-face-font 'default "Lucida Console:Regular:10")
|
|
|
4179 (set-face-font 'modeline "MS Sans Serif:Regular:10")
|
|
|
4180 @end display
|
|
|
4181
|
|
|
4182 @node Q4.0.2, Q4.0.3, Q4.0.1, Display
|
|
|
4183 @unnumberedsubsec Q4.0.2: How do I set the text, menu and modeline fonts?
|
|
|
4184
|
|
|
4185 #### Update me.
|
|
|
4186
|
|
|
4187 Note that you should use @samp{Emacs.} and not @samp{Emacs*} when
|
|
|
4188 setting face values.
|
|
|
4189
|
|
|
4190 In @file{.Xresources}:
|
|
|
4191
|
|
|
4192 @example
|
|
|
4193 Emacs.default.attributeFont: -*-*-medium-r-*-*-*-120-*-*-m-*-*-*
|
|
|
4194 Emacs*menubar*font: fixed
|
|
|
4195 Emacs.modeline.attributeFont: fixed
|
|
|
4196 @end example
|
|
|
4197
|
|
|
4198 This is confusing because @samp{default} and @samp{modeline} are face
|
|
|
4199 names, and can be found listed with all faces in the current mode by
|
|
|
4200 using @kbd{M-x set-face-font (enter) ?}. They use the face-specific
|
|
|
4201 resource @samp{attributeFont}.
|
|
|
4202
|
|
|
4203 On the other hand, @samp{menubar} is a normal X thing that uses the
|
|
|
4204 resource @samp{font}. With Motif it @emph{may be} necessary to use
|
|
|
4205 @samp{fontList} @emph{instead of} @samp{font}. In @emph{non-Motif}
|
|
|
4206 configurations with Mule it @emph{is} necessary to use @samp{fontSet}
|
|
|
4207 instead of @samp{font}. (Sorry, there just is no simple recipe here.)
|
|
|
4208
|
|
|
4209 @node Q4.0.3, Q4.0.4, Q4.0.2, Display
|
|
|
4210 @unnumberedsubsec Q4.0.3: How can I set color options from @file{init.el}?
|
|
|
4211
|
|
|
4212 How can I set the most commonly used color options from my
|
|
|
4213 @file{init.el} instead of from my @file{.Xresources}?
|
|
|
4214
|
|
|
4215 Like this:
|
|
|
4216
|
|
|
4217 @lisp
|
|
|
4218 (set-face-background 'default "bisque") ; frame background
|
|
|
4219 (set-face-foreground 'default "black") ; normal text
|
|
|
4220 (set-face-background 'zmacs-region "red") ; When selecting w/
|
|
|
4221 ; mouse
|
|
|
4222 (set-face-foreground 'zmacs-region "yellow")
|
|
|
4223 (set-face-font 'default "*courier-bold-r*120-100-100*")
|
|
|
4224 (set-face-background 'highlight "blue") ; Ie when selecting
|
|
|
4225 ; buffers
|
|
|
4226 (set-face-foreground 'highlight "yellow")
|
|
|
4227 (set-face-background 'modeline "blue") ; Line at bottom
|
|
|
4228 ; of buffer
|
|
|
4229 (set-face-foreground 'modeline "white")
|
|
|
4230 (set-face-font 'modeline "*bold-r-normal*140-100-100*")
|
|
|
4231 (set-face-background 'isearch "yellow") ; When highlighting
|
|
|
4232 ; while searching
|
|
|
4233 (set-face-foreground 'isearch "red")
|
|
|
4234 (setq x-pointer-foreground-color "black") ; Adds to bg color,
|
|
|
4235 ; so keep black
|
|
|
4236 (setq x-pointer-background-color "blue") ; This is color
|
|
|
4237 ; you really
|
|
|
4238 ; want ptr/crsr
|
|
|
4239 @end lisp
|
|
|
4240
|
|
|
4241 @node Q4.0.4, Q4.0.5, Q4.0.3, Display
|
|
|
4242 @unnumberedsubsec Q4.0.4: How can I set the colors when highlighting a region?
|
|
|
4243
|
|
|
4244 How can I set the background/foreground colors when highlighting a
|
|
|
4245 region?
|
|
|
4246
|
|
|
4247 You can change the face @code{zmacs-region} either in your
|
|
|
4248 @file{.Xresources}:
|
|
|
4249
|
|
|
4250 @example
|
|
|
4251 Emacs.zmacs-region.attributeForeground: firebrick
|
|
|
4252 Emacs.zmacs-region.attributeBackground: lightseagreen
|
|
|
4253 @end example
|
|
|
4254
|
|
|
4255 or in your @file{init.el}:
|
|
|
4256
|
|
|
4257 @lisp
|
|
|
4258 (set-face-background 'zmacs-region "red")
|
|
|
4259 (set-face-foreground 'zmacs-region "yellow")
|
|
|
4260 @end lisp
|
|
|
4261
|
|
|
4262 @node Q4.0.5, Q4.0.6, Q4.0.4, Display
|
|
|
4263 @unnumberedsubsec Q4.0.5: How can I limit color map usage?
|
|
|
4264
|
|
|
4265 I'm using Netscape (or another color grabber like XEmacs);
|
|
|
4266 is there any way to limit the number of available colors in the color map?
|
|
|
4267
|
|
|
4268 Answer: No, but you can start Netscape before XEmacs, and it will use
|
|
|
4269 the closest available color if the colormap is full. You can also limit
|
|
|
4270 the number of colors Netscape uses, using the flags -mono, -ncols <#> or
|
|
|
4271 -install (for mono, limiting to <#> colors, or for using a private color
|
|
|
4272 map).
|
|
|
4273
|
|
|
4274 If you have the money, another solution would be to use a truecolor or
|
|
|
4275 direct color video.
|
|
|
4276
|
|
|
4277 @node Q4.0.6, Q4.0.7, Q4.0.5, Display
|
|
|
4278 @unnumberedsubsec Q4.0.6: My tty supports color, but XEmacs doesn't use them.
|
|
|
4279
|
|
|
4280 XEmacs tries to automatically determine whether your tty supports color,
|
|
|
4281 but sometimes guesses wrong. In that case, you can make XEmacs Do The
|
|
|
4282 Right Thing using this Lisp code:
|
|
|
4283
|
|
|
4284 @lisp
|
|
|
4285 (if (eq 'tty (device-type))
|
|
|
4286 (set-device-class nil 'color))
|
|
|
4287 @end lisp
|
|
|
4288
|
|
|
4289 @node Q4.0.7, Q4.0.8, Q4.0.6, Display
|
|
|
4290 @unnumberedsubsec Q4.0.7: Can I have pixmap backgrounds in XEmacs?
|
|
|
4291 @c New
|
|
|
4292 @email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes:
|
|
|
4293
|
|
|
4294 @quotation
|
|
|
4295 There are several ways to do it. For example, you could specify a
|
|
|
4296 default pixmap image to use in your @file{~/.Xresources}, e.g.,
|
|
|
4297
|
|
|
4298
|
|
|
4299 @example
|
|
|
4300 Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm
|
|
|
4301 @end example
|
|
|
4302
|
|
|
4303
|
|
|
4304 and then reload ~/.Xresources and restart XEmacs. Alternatively,
|
|
|
4305 since each face can have its own pixmap background, a better way
|
|
|
4306 would be to set a face's pixmap within your XEmacs init file, e.g.,
|
|
|
4307
|
|
|
4308 @lisp
|
|
|
4309 (set-face-background-pixmap 'default "/path/to/image.xpm")
|
|
|
4310 (set-face-background-pixmap 'bold "/path/to/another_image.xpm")
|
|
|
4311 @end lisp
|
|
|
4312
|
|
|
4313 and so on. You can also do this interactively via @kbd{M-x edit-faces}.
|
|
|
4314
|
|
|
4315 @end quotation
|
|
|
4316
|
|
|
4317 @node Q4.0.8, Q4.0.9, Q4.0.7, Display
|
|
|
4318 @unnumberedsubsec Q4.0.8: How do I display non-ASCII characters?
|
|
|
4319 @c New
|
|
|
4320
|
|
|
4321 If you're using a Mule-enabled XEmacs, then display is automatic. If
|
|
|
4322 you're not seeing the characters you expect, either (1) you don't have
|
|
|
4323 appropriate fonts available or (2) XEmacs did not correctly detect the
|
|
|
4324 coding system (@pxref{Recognize Coding, , , xemacs}). In case (1),
|
|
|
4325 install fonts as is customary for your platform. In case (2), you
|
|
|
4326 need to tell XEmacs explicitly what coding systems you're using.
|
|
|
4327 @ref{Specify Coding, , , xemacs}.
|
|
|
4328
|
|
|
4329 If your XEmacs is not Mule-enabled, and for some reason getting a
|
|
|
4330 Mule-enabled XEmacs seems like the wrong thing to do, all is not lost.
|
|
|
4331 You can arrange it by brute force. In @file{event-Xt.c} (suppress the
|
|
|
4332 urge to look in this file---play Doom instead, because you'll survive
|
|
|
4333 longer), it is written:
|
|
|
4334
|
|
|
4335 @quotation
|
|
|
4336 In a non-Mule world, a user can still have a multi-lingual editor, by
|
|
|
4337 doing @code{(set-face-font "-*-iso8859-2" (current-buffer))} for all
|
|
|
4338 their Latin-2 buffers, etc.
|
|
|
4339 @end quotation
|
|
|
4340
|
|
|
4341 For the related problem of @emph{inputting} non-ASCII characters in a
|
|
|
4342 non-Mule XEmacs, @xref{Q3.0.6, How can you type in special characters
|
|
|
4343 in XEmacs?}.
|
|
|
4344
|
|
|
4345 @node Q4.0.9, Q4.1.1, Q4.0.8, Display
|
|
|
4346 @unnumberedsubsec Q4.0.9: Font selections in don't get saved after @code{Save Options}.
|
|
|
4347
|
|
|
4348 @email{mannj@@ll.mit.edu, John Mann} writes:
|
|
|
4349
|
|
|
4350 @quotation
|
|
|
4351 You have to go to @samp{Options->Menubars} and unselect
|
|
|
4352 @samp{Frame-Local Font Menu}. If this option is selected, font changes
|
|
|
4353 are only applied to the @emph{current} frame and do @emph{not} get saved
|
|
|
4354 when you save options.
|
|
|
4355 @end quotation
|
|
|
4356
|
|
|
4357 Also, set the following in your @file{init.el}:
|
|
|
4358
|
|
|
4359 @lisp
|
|
|
4360 (setq options-save-faces t)
|
|
|
4361 @end lisp
|
|
|
4362
|
|
|
4363 @unnumberedsec 4.1: Syntax Highlighting (Font Lock)
|
|
|
4364
|
|
|
4365 @node Q4.1.1, Q4.1.2, Q4.0.9, Display
|
|
|
4366 @unnumberedsubsec Q4.1.1: How can I do source code highlighting using font-lock?
|
|
|
4367
|
|
|
4368 For most modes, font-lock is already set up and just needs to be turned
|
|
|
4369 on. This can be done by adding the line:
|
|
|
4370
|
|
|
4371 @lisp
|
|
|
4372 (require 'font-lock)
|
|
|
4373 @end lisp
|
|
|
4374
|
|
|
4375 to your @file{init.el}. (You can turn it on for the
|
|
|
4376 current buffer and session only by @kbd{M-x font-lock-mode}.) See the
|
|
|
4377 file @file{etc/sample.init.el} (@file{etc/sample.emacs} in XEmacs
|
|
|
4378 versions prior to 21.4) for more information.
|
|
|
4379
|
|
|
4380 @c the old way:
|
|
|
4381 @c (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
|
|
|
4382 @c (add-hook 'dired-mode-hook 'turn-on-font-lock)
|
|
|
4383
|
|
|
4384 See also @code{Syntax Highlighting} from the @code{Options} menu.
|
|
|
4385 Remember to save options.
|
|
|
4386
|
|
|
4387 @node Q4.1.2, Q4.2.1, Q4.1.1, Display
|
|
|
4388 @unnumberedsubsec Q4.1.2: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
4389
|
|
|
4390 Use the following code in your @file{init.el}:
|
|
|
4391
|
|
|
4392 @lisp
|
|
|
4393 (setq-default font-lock-maximum-decoration t)
|
|
|
4394 @end lisp
|
|
|
4395
|
|
|
4396 See also @code{Syntax Highlighting} from the @code{Options} menu.
|
|
|
4397 Remember to save options.
|
|
|
4398
|
|
|
4399 @unnumberedsec 4.2: The Modeline
|
|
|
4400
|
|
|
4401 @node Q4.2.1, Q4.2.2, Q4.1.2, Display
|
|
|
4402 @unnumberedsubsec Q4.2.1: How can I make the modeline go away?
|
|
|
4403
|
|
|
4404 @lisp
|
|
|
4405 (set-specifier has-modeline-p nil)
|
|
|
4406 @end lisp
|
|
|
4407
|
|
|
4408 @node Q4.2.2, Q4.2.3, Q4.2.1, Display
|
|
|
4409 @unnumberedsubsec Q4.2.2: How do you have XEmacs display the line number in the modeline?
|
|
|
4410
|
|
|
4411 Add the following line to your @file{init.el} file to
|
|
|
4412 display the line number:
|
|
|
4413
|
|
|
4414 @lisp
|
|
|
4415 (line-number-mode 1)
|
|
|
4416 @end lisp
|
|
|
4417
|
|
|
4418 Use the following to display the column number:
|
|
|
4419
|
|
|
4420 @lisp
|
|
|
4421 (column-number-mode 1)
|
|
|
4422 @end lisp
|
|
|
4423
|
|
|
4424 Or select from the @code{Options} menu
|
|
|
4425 @iftex
|
|
|
4426 @*
|
|
|
4427 @end iftex
|
|
|
4428 @code{Advanced (Customize)->Emacs->Editing->Basics->Line Number Mode}
|
|
|
4429 and/or
|
|
|
4430 @iftex
|
|
|
4431 @*
|
|
|
4432 @end iftex
|
|
|
4433 @code{Advanced (Customize)->Emacs->Editing->Basics->Column Number Mode}
|
|
|
4434
|
|
|
4435 Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
|
|
|
4436
|
|
|
4437 @node Q4.2.3, Q4.2.4, Q4.2.2, Display
|
|
|
4438 @unnumberedsubsec Q4.2.3: How do I get XEmacs to put the time of day on the modeline?
|
|
|
4439
|
|
|
4440 Add the following line to your @file{init.el} file to
|
|
|
4441 display the time:
|
|
|
4442
|
|
|
4443 @lisp
|
|
|
4444 (display-time)
|
|
|
4445 @end lisp
|
|
|
4446
|
|
|
4447 See @code{Customize} from the @code{Options} menu for customization.
|
|
|
4448
|
|
|
4449 @node Q4.2.4, Q4.3.1, Q4.2.3, Display
|
|
|
4450 @unnumberedsubsec Q4.2.4: How can I change the modeline color based on the mode used?
|
|
|
4451
|
|
|
4452 You can use something like the following:
|
|
|
4453
|
|
|
4454 @lisp
|
|
|
4455 (add-hook 'lisp-mode-hook
|
|
|
4456 (lambda ()
|
|
|
4457 (set-face-background 'modeline "red" (current-buffer))))
|
|
|
4458 @end lisp
|
|
|
4459
|
|
|
4460 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
|
|
|
4461 colors change from the default set in your @file{init.el}.
|
|
|
4462 The change will only be made in the buffer you just entered (which
|
|
|
4463 contains the Lisp file you are editing) and will not affect the modeline
|
|
|
4464 colors anywhere else.
|
|
|
4465
|
|
|
4466 Notes:
|
|
|
4467
|
|
|
4468 @itemize @bullet
|
|
|
4469
|
|
|
4470 @item The hook is the mode name plus @code{-hook}. eg. c-mode-hook,
|
|
|
4471 c++-mode-hook, emacs-lisp-mode-hook (used for your
|
|
|
4472 @file{init.el} or a @file{xx.el} file),
|
|
|
4473 lisp-interaction-mode-hook (the @samp{*scratch*} buffer),
|
|
|
4474 text-mode-hook, etc.
|
|
|
4475
|
|
|
4476 @item
|
|
|
4477 Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)},
|
|
|
4478 otherwise you will erase anything that anybody has already put on the
|
|
|
4479 hook.
|
|
|
4480
|
|
|
4481 @item
|
|
|
4482 You can also do @code{(set-face-font 'modeline @var{font})},
|
|
|
4483 eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*"
|
|
|
4484 (current-buffer))} if you wish the modeline font to vary based on the
|
|
|
4485 current mode.
|
|
|
4486 @end itemize
|
|
|
4487
|
|
|
4488 There are additional modeline faces, @code{modeline-buffer-id},
|
|
|
4489 @code{modeline-mousable}, and @code{modeline-mousable-minor-mode}, which
|
|
|
4490 you may want to customize.
|
|
|
4491
|
|
|
4492 @unnumberedsec 4.3: The Cursor
|
|
|
4493
|
|
|
4494 @node Q4.3.1, Q4.3.2, Q4.2.4, Display
|
|
|
4495 @unnumberedsubsec Q4.3.1: Is there a way to make the bar cursor thicker?
|
|
|
4496
|
|
|
4497 I'd like to have the bar cursor a little thicker, as I tend to "lose" it
|
|
|
4498 often.
|
|
|
4499
|
|
|
4500 For a 1 pixel bar cursor, use:
|
|
|
4501
|
|
|
4502 @lisp
|
|
|
4503 (setq bar-cursor t)
|
|
|
4504 @end lisp
|
|
|
4505
|
|
|
4506 For a 2 pixel bar cursor, use:
|
|
|
4507
|
|
|
4508 @lisp
|
|
|
4509 (setq bar-cursor 'anything-else)
|
|
|
4510 @end lisp
|
|
|
4511
|
|
|
4512 You can also change these with Customize.
|
|
|
4513 Select from the @code{Options} menu
|
|
|
4514 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
|
|
|
4515 @kbd{M-x customize @key{RET} display @key{RET}}.
|
|
|
4516
|
|
|
4517 You can use a color to make it stand out better:
|
|
|
4518
|
|
|
4519 @example
|
|
|
4520 Emacs*cursorColor: Red
|
|
|
4521 @end example
|
|
|
4522
|
|
|
4523 @node Q4.3.2, Q4.3.3, Q4.3.1, Display
|
|
|
4524 @unnumberedsubsec Q4.3.2: Is there a way to get back the block cursor?
|
|
|
4525
|
|
|
4526 @lisp
|
|
|
4527 (setq bar-cursor nil)
|
|
|
4528 @end lisp
|
|
|
4529
|
|
|
4530 You can also change this with Customize.
|
|
|
4531 Select from the @code{Options} menu
|
|
|
4532 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
|
|
|
4533 @kbd{M-x customize @key{RET} display @key{RET}}.
|
|
|
4534
|
|
|
4535 @node Q4.3.3, Q4.4.1, Q4.3.2, Display
|
|
|
4536 @unnumberedsubsec Q4.3.3: Can I make the cursor blink?
|
|
|
4537
|
|
|
4538 Yes, like this:
|
|
|
4539
|
|
|
4540 @lisp
|
|
|
4541 (blink-cursor-mode)
|
|
|
4542 @end lisp
|
|
|
4543
|
|
|
4544 This function toggles between a steady cursor and a blinking cursor.
|
|
|
4545 You may also set this mode from the menu bar by selecting
|
|
|
4546 @samp{Options->Display->Blinking Cursor}. Remember to save options.
|
|
|
4547
|
|
|
4548 @unnumberedsec 4.4: The Menubar
|
|
|
4549
|
|
|
4550 @node Q4.4.1, Q4.4.2, Q4.3.3, Display
|
|
|
4551 @unnumberedsubsec Q4.4.1: How do I get rid of the menubar?
|
|
|
4552
|
|
|
4553 @lisp
|
|
|
4554 (set-specifier menubar-visible-p nil)
|
|
|
4555 @end lisp
|
|
|
4556
|
|
|
4557 @node Q4.4.2, Q4.4.3, Q4.4.1, Display
|
|
|
4558 @unnumberedsubsec Q4.4.2: How can I customize the menubar?
|
|
|
4559
|
|
|
4560 For an extensive menubar, add this line to your @file{init.el}:
|
|
|
4561
|
|
|
4562 @lisp
|
|
|
4563 (load "big-menubar")
|
|
|
4564 @end lisp
|
|
|
4565
|
|
|
4566 If you'd like to write your own, this file provides as good a set of
|
|
|
4567 examples as any to start from. The file is located in edit-utils
|
|
|
4568 package.
|
|
|
4569
|
|
|
4570 @node Q4.4.3, Q4.4.4, Q4.4.2, Display
|
|
|
4571 @unnumberedsubsec Q4.4.3: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
4572
|
|
|
4573 #### Write me.
|
|
|
4574
|
|
|
4575 @node Q4.4.4, Q4.4.5, Q4.4.3, Display
|
|
|
4576 @unnumberedsubsec Q4.4.4: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
4577
|
|
|
4578 Add the following to your @file{init.el} (suit to fit):
|
|
|
4579
|
|
|
4580 @lisp
|
|
|
4581 (setq buffers-menu-max-size 20)
|
|
|
4582 @end lisp
|
|
|
4583
|
|
|
4584 For no limit, use an argument of @samp{nil}.
|
|
|
4585
|
|
|
4586 You can also change this with Customize. Select from the
|
|
|
4587 @code{Options} menu
|
|
|
4588 @code{Advanced (Customize)->Emacs->Environment->Menu->Buffers Menu->Max Size...}
|
|
|
4589 or type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}.
|
|
|
4590
|
|
|
4591 @node Q4.4.5, Q4.5.1, Q4.4.4, Display
|
|
|
4592 @unnumberedsubsec Q4.4.5: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
4593
|
|
|
4594 I am trying to use a resource like @code{Emacs*menubar*font} to set the
|
|
|
4595 font of the menubar but it's not working.
|
|
|
4596
|
|
|
4597 In Motif, the use of @samp{font} resources is obsoleted in order to
|
|
|
4598 support internationalization. If you are using the real Motif menubar,
|
|
|
4599 this resource is not recognized at all; you have to say:
|
|
|
4600
|
|
|
4601 @example
|
|
|
4602 Emacs*menubar*fontList: FONT
|
|
|
4603 @end example
|
|
|
4604
|
|
|
4605 If you are using the Lucid menubar, for backward compatibility with
|
|
|
4606 existing user configurations, the @samp{font} resource is recognized.
|
|
|
4607 Since this is not supported by Motif itself, the code is a kludge and
|
|
|
4608 the @samp{font} resource will be recognized only if the @samp{fontList}
|
|
|
4609 resource resource is unset. This means that the resource
|
|
|
4610
|
|
|
4611 @example
|
|
|
4612 *fontList: FONT
|
|
|
4613 @end example
|
|
|
4614
|
|
|
4615 will override
|
|
|
4616
|
|
|
4617 @example
|
|
|
4618 Emacs*menubar*font: FONT
|
|
|
4619 @end example
|
|
|
4620
|
|
|
4621 even though the latter is more specific.
|
|
|
4622
|
|
|
4623 In non-Motif configurations using @samp{--with-mule} and
|
|
|
4624 @samp{--with-xfs} it @emph{is} necessary to use the @code{fontSet}
|
|
|
4625 resource @emph{instead of} the @code{font} resource. The backward
|
|
|
4626 compatibility kludge was never implemented for non-Motif builds.
|
|
|
4627 Example:
|
|
|
4628
|
|
|
4629 @example
|
|
|
4630 *fontSet: FONT
|
|
|
4631 @end example
|
|
|
4632
|
|
|
4633 @unnumberedsec 4.5: The Toolbar
|
|
|
4634
|
|
|
4635 @node Q4.5.1, Q4.5.2, Q4.4.5, Display
|
|
|
4636 @unnumberedsubsec Q4.5.1: How do I get rid of the toolbar?
|
|
|
4637
|
|
|
4638 #### Write me.
|
|
|
4639
|
|
|
4640 @node Q4.5.2, Q4.5.3, Q4.5.1, Display
|
|
|
4641 @unnumberedsubsec Q4.5.2: How can I customize the toolbar?
|
|
|
4642
|
|
|
4643 #### Write me.
|
|
|
4644
|
|
|
4645 @node Q4.5.3, Q4.5.4, Q4.5.2, Display
|
|
|
4646 @unnumberedsubsec Q4.5.3: How can I bind a key to a function to toggle the toolbar?
|
|
|
4647
|
|
|
4648 Try something like:
|
|
|
4649
|
|
|
4650 @lisp
|
|
|
4651 (defun my-toggle-toolbar ()
|
|
|
4652 (interactive)
|
|
|
4653 (set-specifier default-toolbar-visible-p
|
|
|
4654 (not (specifier-instance default-toolbar-visible-p))))
|
|
|
4655 (global-set-key "\C-xT" 'my-toggle-toolbar)
|
|
|
4656 @end lisp
|
|
|
4657
|
|
|
4658 @ignore
|
|
|
4659 @c Probably not relevant any more
|
|
|
4660 There are redisplay bugs in 19.14 that may make the preceding result in
|
|
|
4661 a messed-up display, especially for frames with multiple windows. You
|
|
|
4662 may need to resize the frame before XEmacs completely realizes the
|
|
|
4663 toolbar is really gone.
|
|
|
4664 @end ignore
|
|
|
4665
|
|
|
4666 Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct
|
|
|
4667 code.
|
|
|
4668
|
|
|
4669 @node Q4.5.4, Q4.6.1, Q4.5.3, Display
|
|
|
4670 @unnumberedsubsec Q4.5.4: @samp{Can't instantiate image error...} in toolbar
|
|
|
4671
|
|
|
4672 @email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes:
|
|
|
4673
|
|
|
4674 I just installed the XEmacs (20.4-2) RPMS that I downloaded from
|
|
|
4675 @uref{http://www.xemacs.org/}. Everything works fine, except that when
|
|
|
4676 I place my mouse over the toolbar, it beeps and gives me this message:
|
|
|
4677
|
|
|
4678 @example
|
|
|
4679 Can't instantiate image (probably cached):
|
|
|
4680 [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data
|
|
|
4681 (16 16 <strange control characters> ...
|
|
|
4682 @end example
|
|
|
4683
|
|
|
4684 @email{kyle_jones@@wonderworks.com, Kyle Jones} writes:
|
|
|
4685 @quotation
|
|
|
4686 This is problem specific to some Chips and Technologies video
|
|
|
4687 chips, when running XFree86. Putting
|
|
|
4688
|
|
|
4689 @code{Option "sw_cursor"}
|
|
|
4690
|
|
|
4691 in @file{XF86Config} gets rid of the problem.
|
|
|
4692 @end quotation
|
|
|
4693
|
|
|
4694 @unnumberedsec 4.6: Scrollbars and Scrolling
|
|
|
4695
|
|
|
4696 @node Q4.6.1, Q4.6.2, Q4.5.4, Display
|
|
|
4697 @unnumberedsubsec Q4.6.1: How can I disable the scrollbar?
|
|
|
4698
|
|
|
4699 To disable them for all frames, add the following line to
|
|
|
4700 your @file{.Xresources}:
|
|
|
4701
|
|
|
4702 @example
|
|
|
4703 Emacs.scrollBarWidth: 0
|
|
|
4704 @end example
|
|
|
4705
|
|
|
4706 Or select @samp{Options->Display->Scrollbars}.
|
|
|
4707 Remember to save options.
|
|
|
4708
|
|
|
4709 To turn the scrollbar off on a per-frame basis, use the following
|
|
|
4710 function:
|
|
|
4711
|
|
|
4712 @lisp
|
|
|
4713 (set-specifier scrollbar-width 0 (selected-frame))
|
|
|
4714 @end lisp
|
|
|
4715
|
|
|
4716 You can actually turn the scrollbars on at any level you want by
|
|
|
4717 substituting for (selected-frame) in the above command. For example, to
|
|
|
4718 turn the scrollbars off only in a single buffer:
|
|
|
4719
|
|
|
4720 @lisp
|
|
|
4721 (set-specifier scrollbar-width 0 (current-buffer))
|
|
|
4722 @end lisp
|
|
|
4723
|
|
|
4724 @node Q4.6.2, Q4.6.3, Q4.6.1, Display
|
|
|
4725 @unnumberedsubsec Q4.6.2: How can I change the scrollbar width?
|
|
|
4726
|
|
|
4727 #### Write me.
|
|
|
4728
|
|
|
4729 @node Q4.6.3, Q4.6.4, Q4.6.2, Display
|
|
|
4730 @unnumberedsubsec Q4.6.3: How can I use resources to change scrollbar colors?
|
|
|
4731
|
|
|
4732 Here's a recap of how to use resources to change your scrollbar colors:
|
|
|
4733
|
|
|
4734 @example
|
|
|
4735 ! Motif scrollbars
|
|
|
4736
|
|
|
4737 Emacs*XmScrollBar.Background: skyblue
|
|
|
4738 Emacs*XmScrollBar.troughColor: lightgray
|
|
|
4739
|
|
|
4740 ! Athena scrollbars
|
|
|
4741
|
|
|
4742 Emacs*Scrollbar.Foreground: skyblue
|
|
|
4743 Emacs*Scrollbar.Background: lightgray
|
|
|
4744 @end example
|
|
|
4745
|
|
|
4746 Note the capitalization of @code{Scrollbar} for the Athena widget.
|
|
|
4747
|
|
|
4748 @node Q4.6.4, Q4.6.5, Q4.6.3, Display
|
|
|
4749 @unnumberedsubsec Q4.6.4: Moving the scrollbar can move the point; can I disable this?
|
|
|
4750
|
|
|
4751 When I move the scrollbar in an XEmacs window, it moves the point as
|
|
|
4752 well, which should not be the default behavior. Is this a bug or a
|
|
|
4753 feature? Can I disable it?
|
|
|
4754
|
|
|
4755 The current behavior is a feature, not a bug. Point remains at the same
|
|
|
4756 buffer position as long as that position does not scroll off the screen.
|
|
|
4757 In that event, point will end up in either the upper-left or lower-left
|
|
|
4758 hand corner.
|
|
|
4759
|
|
|
4760 This cannot be changed.
|
|
|
4761
|
|
|
4762 @node Q4.6.5, Q4.6.6, Q4.6.4, Display
|
|
|
4763 @unnumberedsubsec Q4.6.5: Scrolling one line at a time.
|
|
|
4764
|
|
|
4765 Can the cursor keys scroll the screen a line at a time, rather than the
|
|
|
4766 default half page jump? I tend it to find it disorienting.
|
|
|
4767
|
|
|
4768 Use the following:
|
|
|
4769
|
|
|
4770 @lisp
|
|
|
4771 (setq scroll-step 1)
|
|
|
4772 @end lisp
|
|
|
4773
|
|
|
4774 You can also change this with Customize. Select from the
|
|
|
4775 @code{Options} menu
|
|
|
4776 @code{Advanced (Customize)->Emacs->Environment->Windows->Scroll Step...}
|
|
|
4777 or type @kbd{M-x customize @key{RET} windows @key{RET}}.
|
|
|
4778
|
|
|
4779 @node Q4.6.6, Q4.6.7, Q4.6.5, Display
|
|
|
4780 @unnumberedsubsec Q4.6.6: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
4781
|
|
|
4782 Do @code{(setq truncate-lines t)} in the mode-hooks for any modes
|
|
|
4783 in which you want lines truncated.
|
|
|
4784
|
|
|
4785 More precisely: If @code{truncate-lines} is nil, horizontal scrollbars
|
|
|
4786 will never appear. Otherwise, they will appear only if the value of
|
|
|
4787 @code{scrollbar-height} for that buffer/window/etc. is non-zero. If you
|
|
|
4788 do
|
|
|
4789
|
|
|
4790 @lisp
|
|
|
4791 (set-specifier scrollbar-height 0)
|
|
|
4792 @end lisp
|
|
|
4793
|
|
|
4794 then horizontal scrollbars will not appear in truncated buffers unless
|
|
|
4795 the package specifically asked for them.
|
|
|
4796
|
|
|
4797 @node Q4.6.7, Q4.7.1, Q4.6.6, Display
|
|
|
4798 @unnumberedsubsec Q4.6.7: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
4799
|
|
|
4800 @code{auto-show-mode} controls whether or not a horizontal scrollbar
|
|
|
4801 magically appears when a line is too long to be displayed. This is
|
|
|
4802 enabled by default. To turn it off, put the following in your
|
|
|
4803 @file{init.el}:
|
|
|
4804
|
|
|
4805 @lisp
|
|
|
4806 (setq auto-show-mode nil)
|
|
|
4807 (setq-default auto-show-mode nil)
|
|
|
4808 @end lisp
|
|
|
4809
|
|
|
4810 @unnumberedsec 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
4811
|
|
|
4812 @node Q4.7.1, Q4.7.2, Q4.6.7, Display
|
|
|
4813 @unnumberedsubsec Q4.7.1: How can I disable the gutter tabs?
|
|
|
4814
|
|
|
4815 #### Write me.
|
|
|
4816
|
|
|
4817 @node Q4.7.2, Q4.7.3, Q4.7.1, Display
|
|
|
4818 @unnumberedsubsec Q4.7.2: How can I disable the progress bar?
|
|
|
4819
|
|
|
4820 #### Write me.
|
|
|
4821
|
|
|
4822 @node Q4.7.3, Q4.7.4, Q4.7.2, Display
|
|
|
4823 @unnumberedsubsec Q4.7.3: There are bugs in the gutter or widgets.
|
|
|
4824
|
|
|
4825 #### Write me.
|
|
|
4826
|
|
|
4827 @node Q4.7.4, , Q4.7.3, Display
|
|
|
4828 @unnumberedsubsec Q4.7.4: How can I customize the gutter or gutter tabs?
|
|
|
4829
|
|
|
4830 #### Write me.
|
|
|
4831
|
|
|
4832 @node External Subsystems, Internet, Display, Top
|
|
|
4833 @unnumbered 5 Interfacing with the Operating System and External Devices
|
|
|
4834
|
|
|
4835 This is part 5 of the XEmacs Frequently Asked Questions list. This
|
|
2417
|
4836 section is devoted to the various ways that XEmacs interfaces with the
|
|
|
4837 operating system, with other processes and with external devices such
|
|
|
4838 as speakers and the printer.
|
|
428
|
4839
|
|
|
4840 @menu
|
|
2459
|
4841 5.0: X Window System and Resources
|
|
|
4842 * Q5.0.1:: Where is a list of X resources?
|
|
|
4843 * Q5.0.2:: How can I detect a color display?
|
|
|
4844 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}?
|
|
|
4845 * Q5.0.4:: How can I have the window title area display the full path?
|
|
|
4846 * Q5.0.5:: @samp{xemacs -name junk} doesn't work?
|
|
|
4847 * Q5.0.6:: @samp{-iconic} doesn't work.
|
|
|
4848
|
|
|
4849 5.1: Microsoft Windows
|
|
|
4850 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
|
4851 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
|
4852
|
|
|
4853 5.2: Printing
|
|
|
4854 * Q5.2.1:: What do I need to change to make printing work?
|
|
|
4855 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer?
|
|
|
4856 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
|
4857 * Q5.2.4:: Can you print under MS Windows?
|
|
|
4858
|
|
|
4859 5.3: Sound
|
|
|
4860 * Q5.3.1:: How do I turn off the sound?
|
|
|
4861 * Q5.3.2:: How do I get funky sounds instead of a boring beep?
|
|
|
4862 * Q5.3.3:: What are NAS and ESD (EsounD)?
|
|
|
4863 * Q5.3.4:: Sunsite sounds don't play.
|
|
|
4864
|
|
|
4865 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
4866 * Q5.4.1:: What is an interior shell?
|
|
|
4867 * Q5.4.2:: How do I start up a second shell buffer?
|
|
|
4868 * Q5.4.3:: Telnet from shell filters too much
|
|
|
4869 * Q5.4.4:: Strange things are happening in Shell Mode.
|
|
|
4870 * Q5.4.5:: XEmacs complains "No such file or directory, diff"
|
|
|
4871
|
|
|
4872 5.5: Multiple Device Support
|
|
|
4873 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display?
|
|
|
4874 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
4875 * Q5.5.3:: How do I disable gnuserv from opening a new frame?
|
|
|
4876 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
|
4877 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
428
|
4878 @end menu
|
|
|
4879
|
|
2459
|
4880 @unnumberedsec 5.0: X Window System and Resources
|
|
|
4881
|
|
|
4882 @node Q5.0.1, Q5.0.2, External Subsystems, External Subsystems
|
|
|
4883 @unnumberedsubsec Q5.0.1: Where is a list of X resources?
|
|
2417
|
4884
|
|
|
4885 Search through the @file{NEWS} file for @samp{X Resources}. A fairly
|
|
|
4886 comprehensive list is given after it.
|
|
|
4887
|
|
|
4888 In addition, an @file{app-defaults} file @file{etc/Emacs.ad} is
|
|
|
4889 supplied, listing the defaults. The file @file{etc/sample.Xresources}
|
|
|
4890 gives a different set of defaults that you might consider for
|
|
|
4891 installation in your @file{~/.Xresources} file. It is nearly the same
|
|
|
4892 as @file{etc/Emacs.ad}, but a few entries are altered. Be careful about
|
|
|
4893 installing the contents of this file into your @file{.Xresources} (or
|
|
|
4894 legacy @file{.Xdefaults}) file if you use GNU Emacs under X11 as well.
|
|
|
4895
|
|
2459
|
4896 @node Q5.0.2, Q5.0.3, Q5.0.1, External Subsystems
|
|
|
4897 @unnumberedsubsec Q5.0.2: How can I detect a color display?
|
|
2417
|
4898
|
|
|
4899 You can test the return value of the function @code{(device-class)}, as
|
|
|
4900 in:
|
|
|
4901
|
|
|
4902 @lisp
|
|
|
4903 (when (eq (device-class) 'color)
|
|
|
4904 (set-face-foreground 'font-lock-comment-face "Grey")
|
|
|
4905 (set-face-foreground 'font-lock-string-face "Red")
|
|
|
4906 ....
|
|
|
4907 )
|
|
|
4908 @end lisp
|
|
|
4909
|
|
2459
|
4910 @node Q5.0.3, Q5.0.4, Q5.0.2, External Subsystems
|
|
|
4911 @unnumberedsubsec Q5.0.3: How can I get the icon to just say @samp{XEmacs}?
|
|
2417
|
4912
|
|
|
4913 I'd like the icon to just say @samp{XEmacs}, and not include the name of
|
|
|
4914 the current file in it.
|
|
|
4915
|
|
|
4916 Add the following line to your @file{init.el}:
|
|
|
4917
|
|
|
4918 @lisp
|
|
|
4919 (setq frame-icon-title-format "XEmacs")
|
|
|
4920 @end lisp
|
|
|
4921
|
|
2459
|
4922 @node Q5.0.4, Q5.0.5, Q5.0.3, External Subsystems
|
|
|
4923 @unnumberedsubsec Q5.0.4: How can I have the window title area display the full path?
|
|
2417
|
4924
|
|
|
4925 I'd like to have the window title area display the full directory/name
|
|
|
4926 of the current buffer file and not just the name.
|
|
|
4927
|
|
|
4928 Add the following line to your @file{init.el}:
|
|
|
4929
|
|
|
4930 @lisp
|
|
|
4931 (setq frame-title-format "%S: %f")
|
|
|
4932 @end lisp
|
|
|
4933
|
|
|
4934 A more sophisticated title might be:
|
|
|
4935
|
|
|
4936 @lisp
|
|
|
4937 (setq frame-title-format
|
|
|
4938 '("%S: " (buffer-file-name "%f"
|
|
|
4939 (dired-directory dired-directory "%b"))))
|
|
|
4940 @end lisp
|
|
|
4941
|
|
|
4942 That is, use the file name, or the dired-directory, or the buffer name.
|
|
|
4943
|
|
2459
|
4944 @node Q5.0.5, Q5.0.6, Q5.0.4, External Subsystems
|
|
|
4945 @unnumberedsubsec Q5.0.5: @samp{xemacs -name junk} doesn't work?
|
|
2417
|
4946
|
|
|
4947 When I run @samp{xterm -name junk}, I get an xterm whose class name
|
|
|
4948 according to xprop, is @samp{junk}. This is the way it's supposed to
|
|
|
4949 work, I think. When I run @samp{xemacs -name junk} the class name is
|
|
|
4950 not set to @samp{junk}. It's still @samp{emacs}. What does
|
|
|
4951 @samp{xemacs -name} really do? The reason I ask is that my window
|
|
|
4952 manager (fvwm) will make a window sticky and I use XEmacs to read my
|
|
|
4953 mail. I want that XEmacs window to be sticky, without having to use the
|
|
|
4954 window manager's function to set the window sticky. What gives?
|
|
|
4955
|
|
|
4956 @samp{xemacs -name} sets the application name for the program (that is,
|
|
|
4957 the thing which normally comes from @samp{argv[0]}). Using @samp{-name}
|
|
|
4958 is the same as making a copy of the executable with that new name. The
|
|
|
4959 @code{WM_CLASS} property on each frame is set to the frame-name, and the
|
|
|
4960 application-class. So, if you did @samp{xemacs -name FOO} and then
|
|
|
4961 created a frame named @var{BAR}, you'd get an X window with WM_CLASS =
|
|
|
4962 @code{( "BAR", "Emacs")}. However, the resource hierarchy for this
|
|
|
4963 widget would be:
|
|
|
4964
|
|
|
4965 @example
|
|
|
4966 Name: FOO .shell .container .BAR
|
|
|
4967 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
|
|
|
4968 @end example
|
|
|
4969
|
|
|
4970 instead of the default
|
|
|
4971
|
|
|
4972 @example
|
|
|
4973 Name: xemacs.shell .container .emacs
|
|
|
4974 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
|
|
|
4975 @end example
|
|
|
4976
|
|
|
4977
|
|
|
4978 It is arguable that the first element of WM_CLASS should be set to the
|
|
|
4979 application-name instead of the frame-name, but I think that's less
|
|
|
4980 flexible, since it does not give you the ability to have multiple frames
|
|
|
4981 with different WM_CLASS properties. Another possibility would be for
|
|
|
4982 the default frame name to come from the application name instead of
|
|
|
4983 simply being @samp{emacs}. However, at this point, making that change
|
|
|
4984 would be troublesome: it would mean that many users would have to make
|
|
|
4985 yet another change to their resource files (since the default frame name
|
|
|
4986 would suddenly change from @samp{emacs} to @samp{xemacs}, or whatever
|
|
|
4987 the executable happened to be named), so we'd rather avoid it.
|
|
|
4988
|
|
|
4989 To make a frame with a particular name use:
|
|
|
4990
|
|
|
4991 @lisp
|
|
|
4992 (make-frame '((name . "the-name")))
|
|
|
4993 @end lisp
|
|
|
4994
|
|
2459
|
4995 @node Q5.0.6, Q5.1.1, Q5.0.5, External Subsystems
|
|
|
4996 @unnumberedsubsec Q5.0.6: @samp{-iconic} doesn't work.
|
|
2417
|
4997
|
|
|
4998 When I start up XEmacs using @samp{-iconic} it doesn't work right.
|
|
|
4999 Using @samp{-unmapped} on the command line, and setting the
|
|
|
5000 @code{initiallyUnmapped} X Resource don't seem to help much either...
|
|
|
5001
|
|
|
5002 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
|
5003
|
|
|
5004 @quotation
|
|
|
5005 Ugh, this stuff is such an incredible mess that I've about given up
|
|
|
5006 getting it to work. The principal problem is numerous window-manager
|
|
|
5007 bugs...
|
|
|
5008 @end quotation
|
|
|
5009
|
|
2459
|
5010 @unnumberedsec 5.1: Microsoft Windows
|
|
|
5011
|
|
|
5012 @node Q5.1.1, Q5.1.2, Q5.0.6, External Subsystems
|
|
|
5013 @unnumberedsubsec Q5.1.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
2417
|
5014
|
|
|
5015 In his flavor of Emacs 20, Richard Stallman has renamed all the @samp{win32-*}
|
|
|
5016 symbols to @samp{w32-*}. Does XEmacs do the same?
|
|
|
5017
|
|
|
5018 We consider such a move counter-productive, thus we do not use the
|
|
|
5019 @samp{w32} prefix. (His rather questionable justification was that he
|
|
|
5020 did not consider Windows to be a "winning" platform.) However, the name
|
|
|
5021 @samp{Win32} is not particularly descriptive outside the Windows world,
|
|
|
5022 and using just @samp{windows-} would be too generic. So we chose a
|
|
|
5023 compromise, the prefix @samp{mswindows-} for Windows-related variables
|
|
|
5024 and functions.
|
|
|
5025
|
|
|
5026 Thus all the XEmacs variables and functions directly related to either
|
|
|
5027 the Windows GUI or OS are prefixed @samp{mswindows-} (except for a
|
|
|
5028 couple of debugging variables, prefixed @samp{debug-mswindows-}). From
|
|
|
5029 an architectural perspective, however, we believe that this is mostly a
|
|
|
5030 non-issue because there should be a very small number of
|
|
|
5031 window-systems-specific variables anyway. Whenever possible, we try to
|
|
|
5032 provide generic interfaces that apply to all window systems.
|
|
|
5033
|
|
|
5034 @c not true:
|
|
|
5035 @c The user variables
|
|
|
5036 @c that share functionality with existing NT Emacs variables are be named
|
|
|
5037 @c with our convention, but we provide the GNU Emacs names as
|
|
|
5038 @c compatibility aliases.
|
|
|
5039
|
|
2459
|
5040 @node Q5.1.2, Q5.2.1, Q5.1.1, External Subsystems
|
|
|
5041 @unnumberedsubsec Q5.1.2: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
2417
|
5042
|
|
|
5043 @unnumberedsubsubsec Associating a new file type with XEmacs.
|
|
|
5044
|
|
|
5045 In Explorer select @samp{View->Options->File Types}, press @samp{[New
|
|
|
5046 Type...]} and fill in the dialog box, e.g.:
|
|
|
5047
|
|
|
5048 @example
|
|
|
5049 Description of type: Emacs Lisp source
|
|
|
5050 Associated extension: el
|
|
|
5051 Content Type (MIME): text/plain
|
|
|
5052 @end example
|
|
|
5053
|
|
|
5054 then press @samp{[New...]} and fill in the @samp{Action} dialog box as
|
|
|
5055 follows:
|
|
|
5056
|
|
|
5057 @example
|
|
|
5058 Action:
|
|
|
5059 Open
|
|
|
5060
|
|
|
5061 Application used to perform action:
|
|
|
5062 D:\Full\path\for\xemacs.exe "%1"
|
|
|
5063
|
|
|
5064 [x] Use DDE
|
|
|
5065
|
|
|
5066 DDE Message:
|
|
|
5067 open("%1")
|
|
|
5068
|
|
|
5069 Application:
|
|
|
5070 <leave blank>
|
|
|
5071
|
|
|
5072 DDE Application Not Running:
|
|
|
5073 <leave blank>
|
|
|
5074
|
|
|
5075 Topic:
|
|
|
5076 <leave blank>
|
|
|
5077 @end example
|
|
|
5078
|
|
|
5079 @unnumberedsubsubsec Associating an existing file type with XEmacs.
|
|
|
5080
|
|
|
5081 In Explorer select @samp{View->Options->File Types}. Click on the file
|
|
|
5082 type in the list and press @samp{[Edit...]}. If the file type already
|
|
|
5083 has an @samp{Open} action, double click on it and fill in the
|
|
|
5084 @samp{Action} dialog box as described above; otherwise create a new
|
|
|
5085 action.
|
|
|
5086
|
|
|
5087 If the file type has more than one action listed, you probably want to
|
|
|
5088 make the @samp{Open} action that you just edited the default by clicking on
|
|
|
5089 it and pressing @samp{Set Default}.
|
|
|
5090
|
|
|
5091 Note for Windows 2000 users: Under Windows 2000, get to @samp{File Types}
|
|
|
5092 using @samp{Control Panel->Folder Options->File Types}.
|
|
|
5093
|
|
2459
|
5094 @unnumberedsec 5.2: Printing
|
|
|
5095
|
|
|
5096 @node Q5.2.1, Q5.2.2, Q5.1.2, External Subsystems
|
|
|
5097 @unnumberedsubsec Q5.2.1: What do I need to change to make printing work?
|
|
2417
|
5098
|
|
|
5099 For regular printing there are two variables that can be customized.
|
|
|
5100
|
|
|
5101 @table @code
|
|
|
5102 @item lpr-command
|
|
|
5103 This should be set to a command that takes standard input and sends
|
|
|
5104 it to a printer. Something like:
|
|
|
5105
|
|
|
5106 @lisp
|
|
|
5107 (setq lpr-command "lp")
|
|
|
5108 @end lisp
|
|
|
5109
|
|
|
5110 @item lpr-switches
|
|
|
5111 This should be set to a list that contains whatever the print command
|
|
|
5112 requires to do its job. Something like:
|
|
|
5113
|
|
|
5114 @lisp
|
|
|
5115 (setq lpr-switches '("-depson"))
|
|
|
5116 @end lisp
|
|
|
5117 @end table
|
|
|
5118
|
|
|
5119 For postscript printing there are three analogous variables to
|
|
|
5120 customize.
|
|
|
5121
|
|
|
5122 @table @code
|
|
|
5123 @item ps-lpr-command
|
|
|
5124 This should be set to a command that takes postscript on standard input
|
|
|
5125 and directs it to a postscript printer.
|
|
|
5126
|
|
|
5127 @item ps-lpr-switches
|
|
|
5128 This should be set to a list of switches required for
|
|
|
5129 @code{ps-lpr-command} to do its job.
|
|
|
5130
|
|
|
5131 @item ps-print-color-p
|
|
|
5132 This boolean variable should be set @code{t} if printing will be done in
|
|
|
5133 color, otherwise it should be set to @code{nil}.
|
|
|
5134 @end table
|
|
|
5135
|
|
|
5136 NOTE: It is an undocumented limitation in XEmacs that postscript
|
|
|
5137 printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a
|
|
|
5138 window system environment. It cannot be used outside of X11.
|
|
|
5139
|
|
2459
|
5140 @node Q5.2.2, Q5.2.3, Q5.2.1, External Subsystems
|
|
|
5141 @unnumberedsubsec Q5.2.2: How can I print WYSIWYG a font-locked buffer?
|
|
2417
|
5142
|
|
|
5143 Font-lock looks nice. How can I print (WYSIWYG) the highlighted
|
|
|
5144 document?
|
|
|
5145
|
|
|
5146 The package @code{ps-print}, which is now included with XEmacs, provides
|
|
|
5147 the ability to do this. The source code contains complete instructions
|
|
|
5148 on its use, in
|
|
|
5149 @file{$prefix/lib/xemacs/xemacs-packages/lisp/ps-print/ps-print.el},
|
|
|
5150 being the default location of an installed ps-print package.
|
|
|
5151
|
|
2459
|
5152 @node Q5.2.3, Q5.2.4, Q5.2.2, External Subsystems
|
|
|
5153 @unnumberedsubsec Q5.2.3: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
2417
|
5154
|
|
|
5155 My printer is a Postscript printer and @code{lpr} only works for
|
|
|
5156 Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x
|
|
|
5157 lpr-buffer} to work?
|
|
|
5158
|
|
|
5159 Put something like this in your @file{init.el}:
|
|
428
|
5160
|
|
|
5161 @lisp
|
|
2417
|
5162 (setq lpr-command "a2ps")
|
|
|
5163 (setq lpr-switches '("-p" "-1"))
|
|
|
5164 @end lisp
|
|
|
5165
|
|
|
5166 If you don't use a2ps to convert ASCII to postscript (why not, it's
|
|
|
5167 free?), replace with the command you do use. Note also that some
|
|
|
5168 versions of a2ps require a @samp{-Pprinter} to ensure spooling.
|
|
|
5169
|
|
2459
|
5170 @node Q5.2.4, Q5.3.1, Q5.2.3, External Subsystems
|
|
|
5171 @unnumberedsubsec Q5.2.4: Can you print under MS Windows?
|
|
2417
|
5172
|
|
|
5173 As of 21.4, printing works on Windows, using simply
|
|
|
5174 @samp{File->Print BUFFER...}, and can be configured with
|
|
|
5175 @samp{File->Page Setup...}.
|
|
|
5176
|
|
|
5177 Prior to 21.4, there is no built-in support, but there are some clever
|
|
|
5178 hacks out there. If you know how, please let us know and we'll put it
|
|
|
5179 here.
|
|
|
5180
|
|
2459
|
5181 @unnumberedsec 5.3: Sound
|
|
|
5182
|
|
|
5183 @node Q5.3.1, Q5.3.2, Q5.2.4, External Subsystems
|
|
|
5184 @unnumberedsubsec Q5.3.1: How do I turn off the sound?
|
|
2417
|
5185
|
|
|
5186 Add the following line to your @file{init.el}:
|
|
|
5187
|
|
|
5188 @lisp
|
|
|
5189 (setq bell-volume 0)
|
|
|
5190 (setq sound-alist nil)
|
|
|
5191 @end lisp
|
|
|
5192
|
|
|
5193 That will make your XEmacs totally silent---even the default ding sound
|
|
|
5194 (TTY beep on TTY-s) will be gone.
|
|
|
5195
|
|
|
5196 You can also change these with Customize. Select from the
|
|
|
5197 @code{Options} menu @code{Advanced
|
|
|
5198 (Customize)->Emacs->Environment->Sound->Sound...} or type @kbd{M-x
|
|
|
5199 customize @key{RET} sound @key{RET}}.
|
|
|
5200
|
|
|
5201
|
|
2459
|
5202 @node Q5.3.2, Q5.3.3, Q5.3.1, External Subsystems
|
|
|
5203 @unnumberedsubsec Q5.3.2: How do I get funky sounds instead of a boring beep?
|
|
2417
|
5204
|
|
|
5205 Make sure your XEmacs was compiled with sound support, and then put this
|
|
|
5206 in your @file{init.el}:
|
|
|
5207
|
|
|
5208 @lisp
|
|
|
5209 (load-default-sounds)
|
|
|
5210 @end lisp
|
|
|
5211
|
|
2459
|
5212 @node Q5.3.3, Q5.3.4, Q5.3.2, External Subsystems
|
|
|
5213 @unnumberedsubsec Q5.3.3: What are NAS and ESD (EsounD)?
|
|
|
5214
|
|
|
5215 @dfn{Network Audio System} (NAS) is a client-server sound library for X.
|
|
|
5216
|
|
|
5217 @uref{http://radscan.com/nas.html}.
|
|
|
5218
|
|
|
5219 To build XEmacs with it, use the @file{configure} flag @samp{--with-sound=nas}.
|
|
|
5220
|
|
|
5221 @dfn{Enlightened Sound Daemon} (ESD or EsounD) is yet another sound system.
|
|
|
5222
|
|
|
5223 @uref{http://www.tux.org/~ricdude/EsounD.html}.
|
|
|
5224
|
|
|
5225 To build XEmacs with it, use the @file{configure} flag @samp{--with-sound=esd}.
|
|
|
5226
|
|
|
5227 You can specify support for both with a flag like @samp{--with-sound=nas,esd}.
|
|
|
5228
|
|
|
5229 @node Q5.3.4, Q5.4.1, Q5.3.3, External Subsystems
|
|
|
5230 @unnumberedsubsec Q5.3.4: Sunsite sounds don't play.
|
|
2417
|
5231
|
|
|
5232 I'm having some trouble with sounds I've downloaded from sunsite. They
|
|
|
5233 play when I run them through @code{showaudio} or cat them directly to
|
|
|
5234 @file{/dev/audio}, but XEmacs refuses to play them.
|
|
|
5235
|
|
|
5236 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
|
|
|
5237
|
|
|
5238 @quotation
|
|
|
5239 [Many of] These files have an (erroneous) 24byte header that tells about
|
|
|
5240 the format that they have been recorded in. If you cat them to
|
|
|
5241 @file{/dev/audio}, the header will be ignored and the default behavior
|
|
|
5242 for /dev/audio will be used. This happens to be 8kHz uLaw. It is
|
|
|
5243 probably possible to fix the header by piping through @code{sox} and
|
|
|
5244 passing explicit parameters for specifying the sampling format; you then
|
|
|
5245 need to perform a 'null' conversion from SunAudio to SunAudio.
|
|
|
5246 @end quotation
|
|
|
5247
|
|
2459
|
5248 @unnumberedsec 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
5249
|
|
|
5250 @node Q5.4.1, Q5.4.2, Q5.3.4, External Subsystems
|
|
|
5251 @unnumberedsubsec Q5.4.1: What is an interior shell?
|
|
2417
|
5252
|
|
|
5253 #### Write me.
|
|
|
5254
|
|
2459
|
5255 @node Q5.4.2, Q5.4.3, Q5.4.1, External Subsystems
|
|
|
5256 @unnumberedsubsec Q5.4.2: How do I start up a second shell buffer?
|
|
2417
|
5257
|
|
|
5258 In the @code{*shell*} buffer:
|
|
|
5259
|
|
|
5260 @lisp
|
|
|
5261 M-x rename-buffer @key{RET} *shell-1* @key{RET}
|
|
|
5262 M-x shell RET
|
|
|
5263 @end lisp
|
|
|
5264
|
|
|
5265 This will then start a second shell. The key is that no buffer named
|
|
|
5266 @samp{*shell*} can exist. It might be preferable to use @kbd{M-x
|
|
|
5267 rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x
|
|
|
5268 rename-buffer}.
|
|
|
5269
|
|
|
5270 Alternately, you can set the variable @code{shell-multiple-shells}.
|
|
|
5271 If the value of this variable is non-nil, each time shell mode is invoked,
|
|
|
5272 a new shell is made
|
|
|
5273
|
|
2459
|
5274 @node Q5.4.3, Q5.4.4, Q5.4.2, External Subsystems
|
|
|
5275 @unnumberedsubsec Q5.4.3: Telnet from shell filters too much
|
|
2417
|
5276
|
|
|
5277 I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke
|
|
|
5278 and use a telnet session within it. Everything works fine except that
|
|
|
5279 now all @samp{^M}'s are filtered out by Emacs. Fixes?
|
|
|
5280
|
|
|
5281 Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather
|
|
|
5282 than doing rsh or telnet within the local shell buffer. You can also
|
|
|
5283 use @kbd{M-x ssh} to open secure remote session if you have @code{ssh}
|
|
|
5284 installed.
|
|
|
5285
|
|
2459
|
5286 @node Q5.4.4, Q5.4.5, Q5.4.3, External Subsystems
|
|
|
5287 @unnumberedsubsec Q5.4.4: Strange things are happening in Shell Mode.
|
|
2417
|
5288
|
|
|
5289 Sometimes (i.e. it's not repeatable, and I can't work out why it
|
|
|
5290 happens) when I'm typing into shell mode, I hit return and only a
|
|
|
5291 portion of the command is given to the shell, and a blank prompt is
|
|
|
5292 returned. If I hit return again, the rest of the previous command is
|
|
|
5293 given to the shell.
|
|
|
5294
|
|
|
5295 @email{martin@@xemacs.org, Martin Buchholz} writes:
|
|
|
5296
|
|
|
5297 @quotation
|
|
|
5298 There is a known problem with interaction between @code{csh} and the
|
|
|
5299 @code{filec} option and XEmacs. You should add the following to your
|
|
|
5300 @file{.cshrc}:
|
|
|
5301
|
|
|
5302 @example
|
|
|
5303 if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec
|
|
|
5304 @end example
|
|
|
5305 @end quotation
|
|
|
5306
|
|
2459
|
5307 @node Q5.4.5, Q5.5.1, Q5.4.4, External Subsystems
|
|
|
5308 @unnumberedsubsec Q5.4.5: XEmacs complains "No such file or directory, diff"
|
|
2417
|
5309
|
|
|
5310 or "ispell" or other commands that seem related to whatever you just
|
|
|
5311 tried to do (M-x ediff or M-$, for example).
|
|
|
5312
|
|
|
5313 There are a large number of common (in the sense that "everyone has
|
|
|
5314 these, they really do") Unix utilities that are not provided with
|
|
|
5315 XEmacs. The GNU Project's implementations are available for Windows in
|
|
|
5316 the the Cygwin distribution (@uref{http://www.cygwin.com/}), which also
|
|
|
5317 provides a complete Unix emulation environment (and thus makes ports of
|
|
|
5318 Unix utilities nearly trivial). Another implementation is that from
|
|
|
5319 MinGW (@uref{http://www.mingw.org/msys.shtml}). If you know of others,
|
|
|
5320 please let us know!
|
|
|
5321
|
|
2459
|
5322 @unnumberedsec 5.5: Multiple Device Support
|
|
|
5323
|
|
|
5324 @node Q5.5.1, Q5.5.2, Q5.4.5, External Subsystems
|
|
|
5325 @unnumberedsubsec Q5.5.1: How do I open a frame on another screen of my multi-headed display?
|
|
2417
|
5326
|
|
|
5327 Use the command @kbd{M-x make-frame-on-display}. This command is also
|
|
|
5328 on the File menu in the menubar.
|
|
|
5329
|
|
|
5330 The command @code{make-frame-on-tty} also exists, which will establish a
|
|
|
5331 connection to any tty-like device. Opening the TTY devices should be
|
|
|
5332 left to @code{gnuclient}, though.
|
|
|
5333
|
|
2459
|
5334 @node Q5.5.2, Q5.5.3, Q5.5.1, External Subsystems
|
|
|
5335 @unnumberedsubsec Q5.5.2: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
5336
|
|
|
5337 Yes. Use @code{gnuclient -nw}.
|
|
|
5338
|
|
|
5339 Also see @ref{Q5.5.3, How do I disable gnuserv from opening a new frame?}.
|
|
|
5340
|
|
|
5341 @node Q5.5.3, Q5.5.4, Q5.5.2, External Subsystems
|
|
|
5342 @unnumberedsubsec Q5.5.3: How do I disable gnuserv from opening a new frame?
|
|
2417
|
5343
|
|
|
5344 If you set the @code{gnuserv-frame} variable to the frame that should be
|
|
|
5345 used to display buffers that are pulled up, a new frame will not be
|
|
|
5346 created. For example, you could put
|
|
|
5347
|
|
|
5348 @lisp
|
|
|
5349 (setq gnuserv-frame (selected-frame))
|
|
428
|
5350 @end lisp
|
|
|
5351
|
|
2417
|
5352 early on in your @file{init.el}, to ensure that the first frame created
|
|
|
5353 is the one used for your gnuserv buffers.
|
|
|
5354
|
|
|
5355 There is an option to set the gnuserv target to the current frame. See
|
|
|
5356 @code{Options->Display->"Other Window" Location->Make Current Frame Gnuserv Target}
|
|
|
5357
|
|
|
5358 You can also change this with Customize. Select from the
|
|
|
5359 @code{Options} menu @code{Advanced
|
|
|
5360 (Customize)->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type
|
|
|
5361 @kbd{M-x customize @key{RET} gnuserv @key{RET}}.
|
|
|
5362
|
|
|
5363
|
|
2459
|
5364 @node Q5.5.4, Q5.5.5, Q5.5.3, External Subsystems
|
|
|
5365 @unnumberedsubsec Q5.5.4: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
2417
|
5366
|
|
|
5367 Put the following in your @file{init.el} file to start the server:
|
|
|
5368
|
|
|
5369 @lisp
|
|
|
5370 (gnuserv-start)
|
|
|
5371 @end lisp
|
|
|
5372
|
|
|
5373 Start your first XEmacs as usual. After that, you can do:
|
|
|
5374
|
|
|
5375 @example
|
|
|
5376 gnuclient randomfilename
|
|
|
5377 @end example
|
|
|
5378
|
|
|
5379 from the command line to get your existing XEmacs process to open a new
|
|
|
5380 frame and visit randomfilename in that window. When you're done editing
|
|
|
5381 randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the
|
|
|
5382 frame.
|
|
|
5383
|
|
|
5384 See also man page of gnuclient.
|
|
|
5385
|
|
2459
|
5386 @node Q5.5.5, , Q5.5.4, External Subsystems
|
|
|
5387 @unnumberedsubsec Q5.5.5: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
2417
|
5388
|
|
|
5389 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
|
|
|
5390 @quotation
|
|
|
5391 Here is one of the solutions, we have this in a script called
|
|
|
5392 @file{etc/editclient.sh}.
|
|
|
5393 @example
|
|
|
5394 #!/bin/sh
|
|
|
5395 if gnuclient -batch -eval t >/dev/null 2>&1
|
|
|
5396 then
|
|
|
5397 exec gnuclient $@{1+"$@@"@}
|
|
|
5398 else
|
|
|
5399 xemacs -unmapped -f gnuserv-start &
|
|
|
5400 until gnuclient -batch -eval t >/dev/null 2>&1
|
|
|
5401 do
|
|
|
5402 sleep 1
|
|
|
5403 done
|
|
|
5404 exec gnuclient $@{1+"$@@"@}
|
|
|
5405 fi
|
|
|
5406 @end example
|
|
|
5407
|
|
|
5408 Note that there is a known problem when running XEmacs and 'gnuclient
|
|
|
5409 -nw' on the same TTY.
|
|
|
5410 @end quotation
|
|
|
5411
|
|
2459
|
5412 @node Internet, Advanced, External Subsystems, Top
|
|
|
5413 @unnumbered 6 Connecting to the Internet
|
|
|
5414
|
|
|
5415 This is part 6 of the XEmacs Frequently Asked Questions list. This
|
|
|
5416 section is devoted connecting to the Internet.
|
|
|
5417
|
|
|
5418 @menu
|
|
|
5419 6.0: General Mail and News
|
|
|
5420 * Q6.0.1:: What are the various packages for reading mail?
|
|
|
5421 * Q6.0.2:: How can I send mail?
|
|
|
5422 * Q6.0.3:: How do I get my outgoing mail archived?
|
|
|
5423 * Q6.0.4:: How can I read and/or compose MIME messages?
|
|
|
5424 * Q6.0.5:: How do I customize the From line?
|
|
|
5425 * Q6.0.6:: How do I get my MUA to filter mail for me?
|
|
|
5426 * Q6.0.7:: Remote mail reading with an MUA.
|
|
|
5427 * Q6.0.8:: An MUA gets an error incorporating new mail.
|
|
|
5428 * Q6.0.9:: Why isn't @file{movemail} working?
|
|
|
5429 * Q6.0.10:: How do I make my MUA display graphical smilies?
|
|
|
5430 * Q6.0.11:: How can I get those oh-so-neat X-Face lines?
|
|
|
5431
|
|
|
5432 6.1: Reading Mail with VM
|
|
|
5433 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
5434 * Q6.1.2:: How can I get VM to automatically check for new mail?
|
|
|
5435 * 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"?
|
|
|
5436 * Q6.1.4:: Is there a mailing list or FAQ for VM?
|
|
|
5437 * Q6.1.5:: How do I make VM stay in a single frame?
|
|
|
5438 * Q6.1.6:: Customization of VM not covered in the manual, or here.
|
|
|
5439
|
|
|
5440 6.2: Reading Netnews and Mail with Gnus
|
|
|
5441 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
5442 * Q6.2.2:: How do I make Gnus stay within a single frame?
|
|
|
5443
|
|
|
5444 6.3: FTP Access
|
|
|
5445 * Q6.3.1:: Can I edit files on other hosts?
|
|
|
5446 * Q6.3.2:: What is EFS?
|
|
|
5447
|
|
|
5448 6.4: Web Browsing with W3
|
|
|
5449 * Q6.4.1:: What is W3?
|
|
|
5450 * Q6.4.2:: How do I run W3 from behind a firewall?
|
|
|
5451 * Q6.4.3:: Is it true that W3 supports style sheets and tables?
|
|
|
5452 @end menu
|
|
|
5453
|
|
|
5454 @unnumberedsec 6.0: General Mail and News
|
|
|
5455
|
|
|
5456 @node Q6.0.1, Q6.0.2, Internet, Internet
|
|
|
5457 @unnumberedsubsec Q6.0.1: What are the various packages for reading mail?
|
|
|
5458
|
|
|
5459 #### Write me.
|
|
|
5460
|
|
|
5461 @node Q6.0.2, Q6.0.3, Q6.0.1, Internet
|
|
|
5462 @unnumberedsubsec Q6.0.2: How can I send mail?
|
|
|
5463
|
|
|
5464 Under Unix and Mac OS X, the @samp{sendmail} package is normally used
|
|
|
5465 for this.
|
|
|
5466 #### Write me.
|
|
|
5467
|
|
|
5468 Under Windows, you need to use @samp{smtpmail}, which communicates
|
|
|
5469 directly with the mail server, as there is no @file{sendmail} program
|
|
|
5470 running. To get it working, use code like the following in your
|
|
|
5471 @file{init.el} file:
|
|
|
5472
|
|
|
5473 @lisp
|
|
|
5474 ;; Get mail working under Windows.
|
|
|
5475 (setq message-send-mail-function 'smtpmail-send-it) ; for message/Gnus
|
|
|
5476 (setq send-mail-function 'smtpmail-send-it) ; for C-x m, etc.
|
|
|
5477 ;; the following ensures that mail problems can be debugged: it logs a trace
|
|
|
5478 ;; of the SMTP conversation to *trace of SMTP session to <somewhere>*.
|
|
|
5479 (setq smtpmail-debug-info t)
|
|
|
5480 ;; Substitute your info here.
|
|
|
5481 ;(setq user-mail-address "ben@@xemacs.org")
|
|
|
5482 ;(setq user-full-name "Ben Wing")
|
|
|
5483 ;(setq smtpmail-default-smtp-server "smtp.myserver.myisp.com")
|
|
|
5484 ;; The following two aren't completely necessary but may help.
|
|
|
5485 ;(setq smtpmail-local-domain "666.com")
|
|
|
5486 ;(setq smtpmail-sendto-domain "666.com")
|
|
|
5487 ;; If your SMTP server requires a username/password to authenticate, as
|
|
|
5488 ;; many do nowadays, set them like this:
|
|
|
5489 ;(setq smtpmail-auth-credentials ; or use ~/.authinfo
|
|
|
5490 ; '(("smtp.myserver.myisp.com" 25 "USER@@SOMEWHERE" "PASSWORD")))
|
|
|
5491
|
|
|
5492 ;; Other possibilities for getting smtpmail to work:
|
|
|
5493 ;;
|
|
|
5494 ;; If for some reason you need to authenticate using the STARTTLS protocol
|
|
|
5495 ;; (don't look into this unless you know what it is), use
|
|
|
5496 ;; (setq smtpmail-starttls-credentials
|
|
|
5497 ;; '(("YOUR SMTP HOST" 25 "~/.my_smtp_tls.key" "~/.my_smtp_tls.cert")))
|
|
|
5498 ;; Requires external program
|
|
|
5499 ;; ftp://ftp.opaopa.org/pub/elisp/starttls-*.tar.gz.
|
|
|
5500 ;; See http://www.ietf.org/rfc/rfc2246.txt,
|
|
|
5501 ;; http://www.ietf.org/rfc/rfc2487.txt
|
|
|
5502 @end lisp
|
|
|
5503
|
|
|
5504 The lines you need to care about are those that set
|
|
|
5505 @code{user-mail-address}, @code{user-full-name},
|
|
|
5506 @code{smtpmail-default-smtp-server}, and
|
|
|
5507 @code{smtpmail-auth-credentials}. You need to set these with,
|
|
|
5508 respectively, your email address, your full name, the SMTP server you
|
|
|
5509 use for outgoing mail, and the username and password you need to log
|
|
|
5510 in to your SMTP server. (If for some reason your SMTP server doesn't
|
|
|
5511 require logging in to send mail, don't uncomment this last line.)
|
|
|
5512
|
|
|
5513 The other settings may be useful in specific cases, but you should know what
|
|
|
5514 you're doing before enabling them.
|
|
|
5515
|
|
|
5516 @node Q6.0.3, Q6.0.4, Q6.0.2, Internet
|
|
|
5517 @unnumberedsubsec Q6.0.3: How do I get my outgoing mail archived?
|
|
|
5518
|
|
|
5519 @lisp
|
|
|
5520 (setq mail-archive-file-name "~/outbox")
|
|
|
5521 @end lisp
|
|
|
5522
|
|
|
5523 @node Q6.0.4, Q6.0.5, Q6.0.3, Internet
|
|
|
5524 @unnumberedsubsec Q6.0.4: How can I read and/or compose MIME messages?
|
|
|
5525
|
|
|
5526 VM, MH-E and GNUS support MIME natively. Other MUAs may or may not
|
|
|
5527 have MIME support; refer to their documentation and other resources,
|
|
|
5528 such as web pages and mailing lists. Packages like SEMI/WEMI may be
|
|
|
5529 useful in connection with MUAs like mew and Wanderlust.
|
|
|
5530
|
|
|
5531 @node Q6.0.5, Q6.0.6, Q6.0.4, Internet
|
|
|
5532 @unnumberedsubsec Q6.0.5: How do I customize the From line?
|
|
|
5533
|
|
|
5534 How do I change the @samp{From:} line? I have set gnus-user-from-line
|
|
|
5535 to
|
|
|
5536 @example
|
|
|
5537 Gail Gurman <gail.gurman@@sybase.com>
|
|
|
5538 @end example
|
|
|
5539 @noindent , but XEmacs Gnus doesn't use
|
|
|
5540 it. [This should apply to all MUA's. --ed] Instead it uses
|
|
|
5541 @example
|
|
|
5542 Gail Mara Gurman @email{gailg@@deall}
|
|
|
5543 @end example
|
|
|
5544 @noindent and then complains
|
|
|
5545 that it's incorrect. Also, as you perhaps can see, my Message-ID is
|
|
|
5546 screwy. How can I change that?
|
|
|
5547
|
|
|
5548 @email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes:
|
|
|
5549
|
|
|
5550 @quotation
|
|
|
5551 Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or
|
|
|
5552 @code{mail-host-address} to @samp{sybase.com}.
|
|
|
5553 @end quotation
|
|
|
5554
|
|
|
5555 @node Q6.0.6, Q6.0.7, Q6.0.5, Internet
|
|
|
5556 @unnumberedsubsec Q6.0.6: How do I get my MUA to filter mail for me?
|
|
|
5557
|
|
|
5558 One possibility is to use procmail to split your mail before it gets to
|
|
|
5559 the MUA. I prefer this personally, since there are many strange and
|
|
|
5560 wonderful things one can do with procmail. Procmail may be found at
|
|
|
5561 @uref{http://www.procmail.org/}.
|
|
|
5562
|
|
|
5563 Also see the Mail Filtering FAQ at:
|
|
|
5564 @iftex
|
|
|
5565 @*
|
|
|
5566 @end iftex
|
|
|
5567 @uref{http://www.faqs.org/faqs/mail/filtering-faq/}.
|
|
|
5568
|
|
|
5569 @node Q6.0.7, Q6.0.8, Q6.0.6, Internet
|
|
|
5570 @unnumberedsubsec Q6.0.7: Remote mail reading with an MUA.
|
|
|
5571
|
|
|
5572 My mailbox lives at the office on a big honkin server. My regular INBOX
|
|
|
5573 lives on my honkin desktop machine. I now can PPP to the office from
|
|
|
5574 home which is far from honking... I'd like to be able to read mail at
|
|
|
5575 home without storing it here and I'd like to use xemacs and the MUA at
|
|
|
5576 home... Is there a recommended setup?
|
|
|
5577
|
|
|
5578 @email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes:
|
|
|
5579
|
|
|
5580 @quotation
|
|
|
5581 There are several ways to do this.
|
|
|
5582
|
|
|
5583 @enumerate
|
|
|
5584 @item
|
|
|
5585 Set your display to your home machine and run dxpc or one of the other X
|
|
|
5586 compressors.
|
|
|
5587
|
|
|
5588 @item
|
|
|
5589 NFS mount your desktop machine on your home machine and modify your pop
|
|
|
5590 command on your home machine to rsh to your desktop machine and actually
|
|
|
5591 do the pop get's.
|
|
|
5592
|
|
|
5593 @item
|
|
|
5594 Run a POP server on your desktop machine as well and do a sort of two
|
|
|
5595 tiered POP get.
|
|
|
5596 @end enumerate
|
|
|
5597 @end quotation
|
|
|
5598
|
|
|
5599 @email{wmperry@@monolith.spry.com, William Perry} adds:
|
|
|
5600
|
|
|
5601 @quotation
|
|
|
5602 Or you could run a pop script periodically on your desktop machine, and
|
|
|
5603 just use ange-ftp or NFS to get to your mailbox. I used to do this all
|
|
|
5604 the time back at IU.
|
|
|
5605 @end quotation
|
|
|
5606
|
|
|
5607 @node Q6.0.8, Q6.0.9, Q6.0.7, Internet
|
|
|
5608 @unnumberedsubsec Q6.0.8: An MUA gets an error incorporating new mail.
|
|
|
5609
|
|
|
5610 rmail and VM, and probably other MUA's as well, get new mail from
|
|
|
5611 your mailbox (called @file{/var/mail/$USER} or @file{/var/spool/mail/$USER}
|
|
|
5612 or something similar) using a program called @code{movemail}.
|
|
|
5613 This program interlocks with @code{/bin/mail} using the protocol
|
|
|
5614 defined by @code{/bin/mail}.
|
|
|
5615
|
|
|
5616 There are various different protocols in general use, which you need to
|
|
|
5617 specify using the @samp{--mail-locking} option to @file{configure}:
|
|
|
5618
|
|
|
5619 @table @samp
|
|
|
5620 @item lockf
|
|
|
5621 POSIX file locking with @code{lockf()}
|
|
|
5622 @item flock
|
|
|
5623 BSD file locking with @code{flock()}
|
|
|
5624 @item dot
|
|
|
5625 To manipulate mail file @file{foo}, first create file @file{foo.lock}
|
|
|
5626 @item locking
|
|
|
5627 Use @code{locking()}, Microsoft's renamed @code{flock()}
|
|
|
5628 @item mmdf
|
|
|
5629 Use @code{lk_open()} and @code{lk_close()} as defined by the Multi-channel
|
|
|
5630 Memo Distribution Facility
|
|
|
5631 @item pop
|
|
|
5632 Retrieve mail using POP (the Post Office Protocol). This is the
|
|
|
5633 default for Cygwin/MinGW.
|
|
|
5634 @end table
|
|
|
5635
|
|
|
5636 @strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
|
|
|
5637 SYSTEM, YOU CAN LOSE MAIL!}
|
|
|
5638
|
|
|
5639 Usually the value is correctly determined automatically:
|
|
|
5640 @file{configure} tries to detect the method in use, and defaults exist
|
|
|
5641 on systems for which this doesn't work.
|
|
|
5642
|
|
|
5643 However, if you run into problems incorporating new mail, it may be
|
|
|
5644 because an incorrect method is being used.
|
|
|
5645
|
|
|
5646 If your system uses the lock file protocol, and permissions are set
|
|
|
5647 so that ordinary users cannot write lock files in the mail spool
|
|
|
5648 directory, you may need to make @file{movemail} setgid to a
|
|
|
5649 suitable group such as @samp{mail}. You can use these commands (as
|
|
|
5650 root):
|
|
|
5651
|
|
|
5652 @example
|
|
|
5653 chgrp mail movemail
|
|
|
5654 chmod 2755 movemail
|
|
|
5655 @end example
|
|
|
5656
|
|
|
5657 If you are using the @samp{pop} locking method, @file{movemail} must
|
|
|
5658 be setuid root.
|
|
|
5659
|
|
|
5660 Installation normally copies movemail from the build directory to an
|
|
|
5661 installation directory which is usually under @file{/usr/local/lib}.
|
|
|
5662 The installed copy of @file{movemail} is usually in the directory
|
|
|
5663 @file{/usr/local/lib/xemacs-VERSION/TARGET} (for example,
|
|
|
5664 @file{/usr/local/lib/xemacs-21.4.15/i686-pc-cygwin}). You must change
|
|
|
5665 the group and mode of the installed copy; changing the group and mode
|
|
|
5666 of the build directory copy is ineffective.
|
|
|
5667
|
|
|
5668 @node Q6.0.9, Q6.0.10, Q6.0.8, Internet
|
|
|
5669 @unnumberedsubsec Q6.0.9: Why isn't @file{movemail} working?
|
|
|
5670
|
|
|
5671 @xref{Q6.0.8}.
|
|
|
5672
|
|
|
5673 Note also that older versions of Mozilla came with a @file{movemail}
|
|
|
5674 program that is @strong{not} compatible with XEmacs. Do not use it.
|
|
|
5675 Always use the @file{movemail} installed with your XEmacs. Failure to
|
|
|
5676 do so can result in lost mail.
|
|
|
5677
|
|
|
5678 @node Q6.0.10, Q6.0.11, Q6.0.9, Internet
|
|
|
5679 @unnumberedsubsec Q6.0.10: How do I make my MUA display graphical smilies?
|
|
|
5680 For mh-e use the following:
|
|
|
5681
|
|
|
5682 @lisp
|
|
|
5683 (add-hook 'mh-show-mode-hook '(lambda ()
|
|
|
5684 (smiley-region (point-min)
|
|
|
5685 (point-max))))
|
|
|
5686 @end lisp
|
|
|
5687
|
|
|
5688 @email{bill@@carpenter.ORG, WJCarpenter} writes:
|
|
|
5689 For VM use the following:
|
|
|
5690 @lisp
|
|
|
5691 (autoload 'smiley-region "smiley" nil t)
|
|
|
5692 (add-hook 'vm-select-message-hook
|
|
|
5693 '(lambda ()
|
|
|
5694 (smiley-region (point-min)
|
|
|
5695 (point-max))))
|
|
|
5696 @end lisp
|
|
|
5697
|
|
|
5698 For tm use the following:
|
|
|
5699 @lisp
|
|
|
5700 (autoload 'smiley-buffer "smiley" nil t)
|
|
|
5701 (add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer)
|
|
|
5702 @end lisp
|
|
|
5703
|
|
|
5704 @node Q6.0.11, Q6.1.1, Q6.0.10, Internet
|
|
|
5705 @unnumberedsubsec Q6.0.11: How can I get those oh-so-neat X-Face lines?
|
|
|
5706
|
|
|
5707 Firstly there is an ftp site which describes X-faces and has the
|
|
|
5708 associated tools mentioned below, at
|
|
|
5709 @uref{http://ftp.cs.indiana.edu/pub/faces/}.
|
|
|
5710
|
|
|
5711 Then the steps are
|
|
|
5712
|
|
|
5713 @enumerate
|
|
|
5714 @item
|
|
|
5715 Create 48x48x1 bitmap with your favorite tool
|
|
|
5716
|
|
|
5717 @item
|
|
|
5718 Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc.,
|
|
|
5719 and then compile the face.
|
|
|
5720
|
|
|
5721 @item
|
|
|
5722 @example
|
|
|
5723 cat file.xbm | xbm2ikon |compface > file.face
|
|
|
5724 @end example
|
|
|
5725
|
|
|
5726 @item
|
|
|
5727 Then be sure to quote things that are necessary for emacs strings:
|
|
|
5728
|
|
|
5729 @example
|
|
|
5730 cat ./file.face | sed 's/\\/\\\\/g'
|
|
|
5731 @iftex
|
|
|
5732 \ @*
|
|
|
5733 @end iftex
|
|
|
5734 | sed 's/\"/\\\"/g' > ./file.face.quoted
|
|
|
5735 @end example
|
|
|
5736
|
|
|
5737 @item
|
|
|
5738 Then set up emacs to include the file as a mail header - there were a
|
|
|
5739 couple of suggestions here---either something like:
|
|
|
5740
|
|
|
5741 @lisp
|
|
|
5742 (setq mail-default-headers
|
|
|
5743 "X-Face: @email{Ugly looking text string here}")
|
|
|
5744 @end lisp
|
|
|
5745
|
|
|
5746 Or, alternatively, as:
|
|
|
5747
|
|
|
5748 @lisp
|
|
|
5749 (defun mail-insert-x-face ()
|
|
|
5750 (save-excursion
|
|
|
5751 (goto-char (point-min))
|
|
|
5752 (search-forward mail-header-separator)
|
|
|
5753 (beginning-of-line)
|
|
|
5754 (insert "X-Face:")
|
|
|
5755 (insert-file-contents "~/.face")))
|
|
|
5756
|
|
|
5757 (add-hook 'mail-setup-hook 'mail-insert-x-face)
|
|
|
5758 @end lisp
|
|
|
5759 @end enumerate
|
|
|
5760
|
|
|
5761 However, 2 things might be wrong:
|
|
|
5762
|
|
|
5763 Some versions of pbmtoicon produces some header lines that is not
|
|
|
5764 expected by the version of compface that I grabbed. So I found I had to
|
|
|
5765 include a @code{tail +3} in the pipeline like this:
|
|
|
5766
|
|
|
5767 @example
|
|
|
5768 cat file.xbm | xbm2ikon | tail +3 |compface > file.face
|
|
|
5769 @end example
|
|
|
5770
|
|
|
5771 Some people have also found that if one uses the @code{(insert-file)}
|
|
|
5772 method, one should NOT quote the face string using the sed script .
|
|
|
5773
|
|
|
5774 It might also be helpful to use @email{stig@@hackvan.com, Stig's} script
|
|
|
5775 xbm2face (included in the compface distribution at XEmacs.org) to do the
|
|
|
5776 conversion.
|
|
|
5777
|
|
|
5778 Contributors for this item:
|
|
|
5779
|
|
|
5780 Paul Emsley,
|
|
|
5781 Ricardo Marek,
|
|
|
5782 Amir J. Katz,
|
|
|
5783 Glen McCort,
|
|
|
5784 Heinz Uphoff,
|
|
|
5785 Peter Arius,
|
|
|
5786 Paul Harrison, and
|
|
|
5787 Vegard Vesterheim
|
|
|
5788
|
|
|
5789 @unnumberedsec 6.1: Reading Mail with VM
|
|
|
5790
|
|
|
5791 @node Q6.1.1, Q6.1.2, Q6.0.11, Internet
|
|
|
5792 @unnumberedsubsec Q6.1.1: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
5793
|
|
|
5794 Use @code{vm-spool-files}, like this for example:
|
|
|
5795
|
|
|
5796 @lisp
|
|
|
5797 (setq vm-spool-files '("/var/spool/mail/wing"
|
|
|
5798 "netcom23.netcom.com:110:pass:wing:MYPASS"))
|
|
|
5799 @end lisp
|
|
|
5800
|
|
|
5801 Of course substitute your actual password for MYPASS.
|
|
|
5802
|
|
|
5803 @node Q6.1.2, Q6.1.3, Q6.1.1, Internet
|
|
|
5804 @unnumberedsubsec Q6.1.2: How can I get VM to automatically check for new mail?
|
|
|
5805
|
|
|
5806 @email{turner@@lanl.gov, John Turner} writes:
|
|
|
5807
|
|
|
5808 @quotation
|
|
|
5809 Use the following:
|
|
|
5810
|
|
|
5811 @lisp
|
|
|
5812 (setq vm-auto-get-new-mail 60)
|
|
|
5813 @end lisp
|
|
|
5814 @end quotation
|
|
|
5815
|
|
|
5816 @node Q6.1.3, Q6.1.4, Q6.1.2, Internet
|
|
|
5817 @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"?
|
|
|
5818
|
|
|
5819 Set @code{vm-reply-ignored-addresses} to a list, like
|
|
|
5820
|
|
|
5821 @lisp
|
|
|
5822 (setq vm-reply-ignored-addresses
|
|
|
5823 '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com"
|
|
|
5824 "wing@@netcom.com" "wing@@xemacs.org"))
|
|
|
5825 @end lisp
|
|
|
5826
|
|
|
5827 Note that each string is a regular expression.
|
|
|
5828
|
|
|
5829 @node Q6.1.4, Q6.1.5, Q6.1.3, Internet
|
|
|
5830 @unnumberedsubsec Q6.1.4: Is there a mailing list or FAQ for VM?
|
|
|
5831
|
|
|
5832 A FAQ for VM exists at @uref{http://www.wonderworks.com/vm/FAQ.html}.
|
|
|
5833
|
|
|
5834 VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug.
|
|
|
5835
|
|
|
5836 @node Q6.1.5, Q6.1.6, Q6.1.4, Internet
|
|
|
5837 @unnumberedsubsec Q6.1.5: How do I make VM stay in a single frame?
|
|
|
5838
|
|
|
5839 John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes:
|
|
|
5840
|
|
|
5841 @quotation
|
|
|
5842 @lisp
|
|
|
5843 ; Don't use multiple frames
|
|
|
5844 (setq vm-frame-per-composition nil)
|
|
|
5845 (setq vm-frame-per-folder nil)
|
|
|
5846 (setq vm-frame-per-edit nil)
|
|
|
5847 (setq vm-frame-per-summary nil)
|
|
|
5848 @end lisp
|
|
|
5849 @end quotation
|
|
|
5850
|
|
|
5851 @node Q6.1.6, Q6.2.1, Q6.1.5, Internet
|
|
|
5852 @unnumberedsubsec Q6.1.6: Customization of VM not covered in the manual, or here.
|
|
|
5853
|
|
|
5854 @email{boffi@@hp735.stru.polimi.it, giacomo boffi} writes:
|
|
|
5855
|
|
|
5856 @quotation
|
|
|
5857 The meta-answer is to look into the file @file{vm-vars.el}, in the vm
|
|
|
5858 directory of the lisp library.
|
|
|
5859
|
|
|
5860 @file{vm-vars.el} contains, initializes and carefully describes, with
|
|
|
5861 examples of usage, the plethora of user options that @emph{fully}
|
|
|
5862 control VM's behavior.
|
|
|
5863
|
|
|
5864 Enter vm-vars, @code{forward-search} for toolbar, find the variables
|
|
|
5865 that control the toolbar placement, appearance, existence, copy to your
|
|
|
5866 @file{init.el} or @file{.vm} and modify according to the
|
|
|
5867 detailed instructions.
|
|
|
5868
|
|
|
5869 The above also applies to all the various features of VM: search for
|
|
|
5870 some keywords, maybe the first you conjure isn't appropriate, find the
|
|
|
5871 appropriate variables, copy and experiment.
|
|
|
5872 @end quotation
|
|
|
5873
|
|
|
5874 @unnumberedsec 6.2: Reading Netnews and Mail with Gnus
|
|
|
5875
|
|
|
5876 @node Q6.2.1, Q6.2.2, Q6.1.6, Internet
|
|
|
5877 @unnumberedsubsec Q6.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
5878
|
|
|
5879 The Gnus numbering issues are not meant for mere mortals to know them.
|
|
|
5880 If you feel you @emph{must} enter the muddy waters of Gnus, visit the
|
|
|
5881 excellent FAQ, maintained by Justin Sheehy, at:
|
|
|
5882
|
|
|
5883 @example
|
|
|
5884 @uref{http://my.gnus.org/FAQ/}
|
|
|
5885 @end example
|
|
|
5886
|
|
|
5887 See also Gnus home page
|
|
|
5888 @example
|
|
|
5889 @uref{http://www.gnus.org/}
|
|
|
5890 @end example
|
|
|
5891
|
|
|
5892 @node Q6.2.2, Q6.3.1, Q6.2.1, Internet
|
|
|
5893 @unnumberedsubsec Q6.2.2: How do I make Gnus stay within a single frame?
|
|
|
5894
|
|
|
5895 The toolbar code to start Gnus opens the new frame---and it's a feature
|
|
|
5896 rather than a bug. If you don't like it, but would still like to click
|
|
|
5897 on the seemly icon, use the following code:
|
|
|
5898
|
|
|
5899 @lisp
|
|
|
5900 (defun toolbar-news ()
|
|
|
5901 (gnus))
|
|
|
5902 @end lisp
|
|
|
5903
|
|
|
5904 It will redefine the callback function of the icon to just call
|
|
|
5905 @code{gnus}, without all the fancy frame stuff.
|
|
|
5906
|
|
|
5907 @unnumberedsec 6.3: FTP Access
|
|
|
5908
|
|
|
5909 @node Q6.3.1, Q6.3.2, Q6.2.2, Internet
|
|
|
5910 @unnumberedsubsec Q6.3.1: Can I edit files on other hosts?
|
|
|
5911
|
|
|
5912 Yes. Of course XEmacs can use any network file system (such as NFS or
|
|
|
5913 Windows file sharing) you have available, and includes some
|
|
|
5914 optimizations and safety features appropriate to those environments.
|
|
|
5915
|
|
|
5916 It is also possible to transparently edit files via FTP, ssh, or rsh. That
|
|
|
5917 is, XEmacs makes a local copy using the transport in the background, and
|
|
|
5918 automatically refreshes the remote original from that copy when you save
|
|
|
5919 it. XEmacs also is capable of doing file system manipulations like
|
|
|
5920 creating and removing directories and files. The FTP interface is
|
|
|
5921 provided by the standard @samp{efs} package @ref{Top, EFS, , efs}. The
|
|
|
5922 ssh/rsh interface is provided by the optional @samp{tramp} package
|
|
|
5923 @ref{Top, TRAMP, , tramp}.
|
|
|
5924
|
|
|
5925 @node Q6.3.2, Q6.4.1, Q6.3.1, Internet
|
|
|
5926 @unnumberedsubsec Q6.3.2: What is EFS?
|
|
|
5927
|
|
|
5928 #### Write me.
|
|
|
5929
|
|
|
5930 @unnumberedsec 6.4: Web Browsing with W3
|
|
|
5931
|
|
|
5932 @node Q6.4.1, Q6.4.2, Q6.3.2, Internet
|
|
|
5933 @unnumberedsubsec Q6.4.1: What is W3?
|
|
|
5934
|
|
|
5935 W3 is an advanced graphical browser written in Emacs lisp that runs on
|
|
|
5936 XEmacs. It has full support for cascaded style sheets, and more...
|
|
|
5937
|
|
|
5938 It has a home web page at
|
|
|
5939 @uref{http://www.cs.indiana.edu/elisp/w3/docs.html}.
|
|
|
5940
|
|
|
5941 @node Q6.4.2, Q6.4.3, Q6.4.1, Internet
|
|
|
5942 @unnumberedsubsec Q6.4.2: How do I run W3 from behind a firewall?
|
|
|
5943
|
|
|
5944 There is a long, well-written, detailed section in the W3 manual that
|
|
|
5945 describes how to do this. Look in the section entitled "Firewalls".
|
|
|
5946
|
|
|
5947 @node Q6.4.3, , Q6.4.2, Internet
|
|
|
5948 @unnumberedsubsec Q6.4.3: Is it true that W3 supports style sheets and tables?
|
|
|
5949
|
|
|
5950 Yes, and much more. W3, as distributed with the latest XEmacs is a
|
|
|
5951 full-featured web browser.
|
|
|
5952
|
|
|
5953 @node Advanced, Other Packages, Internet, Top
|
|
|
5954 @unnumbered 7 Advanced Customization Using XEmacs Lisp
|
|
|
5955
|
|
|
5956 This is part 7 of the XEmacs Frequently Asked Questions list. This
|
|
|
5957 section is devoted to advanced customization using XEmacs Lisp.
|
|
|
5958
|
|
|
5959 @menu
|
|
|
5960 7.0: Online Help
|
|
|
5961 * Q7.0.1:: How can I get two instances of info?
|
|
|
5962 * Q7.0.2:: How do I add new Info directories?
|
|
|
5963
|
|
|
5964 7.1: Emacs Lisp and @file{init.el}
|
|
|
5965 * Q7.1.1:: What version of Emacs am I running?
|
|
|
5966 * Q7.1.2:: How can I evaluate Emacs-Lisp expressions?
|
|
|
5967 * Q7.1.3:: @code{(setq tab-width 6)} behaves oddly.
|
|
|
5968 * Q7.1.4:: How can I add directories to the @code{load-path}?
|
|
|
5969 * Q7.1.5:: How to check if a lisp function is defined?
|
|
|
5970 * Q7.1.6:: Can I force the output of @code{(face-list)} to a buffer?
|
|
|
5971
|
|
|
5972 7.2: Emacs Lisp Programming Techniques
|
|
|
5973 * Q7.2.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
|
5974 * Q7.2.2:: Can I generate "fake" keyboard events?
|
|
|
5975 * Q7.2.3:: Could you explain @code{read-kbd-macro} in more detail?
|
|
|
5976 * Q7.2.4:: What is the performance hit of @code{let}?
|
|
|
5977 * Q7.2.5:: What is the recommended use of @code{setq}?
|
|
|
5978 * Q7.2.6:: What is the typical misuse of @code{setq}?
|
|
|
5979 * Q7.2.7:: I like the @code{do} form of cl, does it slow things down?
|
|
|
5980 * Q7.2.8:: I like recursion, does it slow things down?
|
|
|
5981 * Q7.2.9:: How do I put a glyph as annotation in a buffer?
|
|
|
5982 * Q7.2.10:: @code{map-extents} won't traverse all of my extents!
|
|
|
5983 * Q7.2.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
|
5984
|
|
|
5985 7.3: Mathematics
|
|
|
5986 * Q7.3.1:: What are bignums, ratios, and bigfloats in Lisp?
|
|
|
5987 * Q7.3.2:: XEmacs segfaults when I use very big numbers!
|
|
|
5988 * Q7.3.3:: Bignums are really slow!
|
|
|
5989 * Q7.3.4:: Equal bignums don't compare as equal! What gives?
|
|
|
5990 @end menu
|
|
|
5991
|
|
|
5992 @unnumberedsec 7.0: Online Help
|
|
|
5993
|
|
|
5994 @node Q7.0.1, Q7.0.2, Advanced, Advanced
|
|
|
5995 @unnumberedsubsec Q7.0.1: How can I get two instances of info?
|
|
|
5996
|
|
|
5997 Before 21.4, you can't. The @code{info} package does not provide for
|
|
|
5998 multiple info buffers. In 21.4, this should be fixed. #### how?
|
|
|
5999
|
|
|
6000 @node Q7.0.2, Q7.1.1, Q7.0.1, Advanced
|
|
|
6001 @unnumberedsubsec Q7.0.2: How do I add new Info directories?
|
|
|
6002
|
|
|
6003 You use something like:
|
|
|
6004
|
|
|
6005 @lisp
|
|
|
6006 (setq Info-directory-list (cons
|
|
|
6007 (expand-file-name "~/info")
|
|
|
6008 Info-default-directory-list))
|
|
|
6009 @end lisp
|
|
|
6010
|
|
|
6011 @email{davidm@@prism.kla.com, David Masterson} writes:
|
|
|
6012
|
|
|
6013 @quotation
|
|
|
6014 Emacs Info and XEmacs Info do many things differently. If you're trying to
|
|
|
6015 support a number of versions of Emacs, here are some notes to remember:
|
|
|
6016
|
|
|
6017 @enumerate
|
|
|
6018 @item
|
|
|
6019 Emacs Info scans @code{Info-directory-list} from right-to-left while
|
|
|
6020 XEmacs Info reads it from left-to-right, so append to the @emph{correct}
|
|
|
6021 end of the list.
|
|
|
6022
|
|
|
6023 @item
|
|
|
6024 Use @code{Info-default-directory-list} to initialize
|
|
|
6025 @code{Info-directory-list} @emph{if} it is available at startup, but not
|
|
|
6026 all Emacsen define it.
|
|
|
6027
|
|
|
6028 @item
|
|
|
6029 Emacs Info looks for a standard @file{dir} file in each of the
|
|
|
6030 directories scanned from #1 and magically concatenates them together.
|
|
|
6031
|
|
|
6032 @item
|
|
|
6033 XEmacs Info looks for a @file{localdir} file (which consists of just the
|
|
|
6034 menu entries from a @file{dir} file) in each of the directories scanned
|
|
|
6035 from #1 (except the first), does a simple concatenation of them, and
|
|
|
6036 magically attaches the resulting list to the end of the menu in the
|
|
|
6037 @file{dir} file in the first directory.
|
|
|
6038 @end enumerate
|
|
|
6039
|
|
|
6040 Another alternative is to convert the documentation to HTML with
|
|
|
6041 texi2html and read it from a web browser like Lynx or W3.
|
|
|
6042 @end quotation
|
|
|
6043
|
|
|
6044 @unnumberedsec 7.1: Emacs Lisp and @file{init.el}
|
|
|
6045
|
|
|
6046 @node Q7.1.1, Q7.1.2, Q7.0.2, Advanced
|
|
|
6047 @unnumberedsubsec Q7.1.1: What version of Emacs am I running?
|
|
|
6048
|
|
|
6049 How can @file{init.el} determine which of the family of
|
|
|
6050 Emacsen I am using?
|
|
|
6051
|
|
|
6052 To determine if you are currently running GNU Emacs 18, GNU Emacs 19,
|
|
|
6053 XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the
|
|
|
6054 example given in @file{etc/sample.init.el} (@file{etc/sample.emacs} in
|
|
|
6055 XEmacs versions prior to 21.4). There are other nifty things in there
|
|
|
6056 as well!
|
|
|
6057
|
|
|
6058 For all new code, all you really need to do is:
|
|
|
6059
|
|
|
6060 @lisp
|
|
|
6061 (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
|
|
|
6062 @end lisp
|
|
|
6063
|
|
|
6064 @node Q7.1.2, Q7.1.3, Q7.1.1, Advanced
|
|
|
6065 @unnumberedsubsec Q7.1.2: How can I evaluate Emacs-Lisp expressions?
|
|
|
6066
|
|
|
6067 I know I can evaluate Elisp expressions from @code{*scratch*} buffer
|
|
|
6068 with @kbd{C-j} after the expression. How do I do it from another
|
|
|
6069 buffer?
|
|
|
6070
|
|
|
6071 Press @kbd{M-:} (the default binding of @code{eval-expression}), and
|
|
|
6072 enter the expression to the minibuffer.
|
|
|
6073
|
|
|
6074 @node Q7.1.3, Q7.1.4, Q7.1.2, Advanced
|
|
|
6075 @unnumberedsubsec Q7.1.3: @code{(setq tab-width 6)} behaves oddly.
|
|
|
6076
|
|
|
6077 If you put @code{(setq tab-width 6)} in your
|
|
|
6078 @file{init.el} file it does not work! Is there a reason
|
|
|
6079 for this? If you do it at the EVAL prompt it works fine!! How strange.
|
|
|
6080
|
|
|
6081 Use @code{setq-default} instead, since @code{tab-width} is
|
|
|
6082 all-buffer-local.
|
|
|
6083
|
|
|
6084 @node Q7.1.4, Q7.1.5, Q7.1.3, Advanced
|
|
|
6085 @unnumberedsubsec Q7.1.4: How can I add directories to the @code{load-path}?
|
|
|
6086
|
|
|
6087 Here are two ways to do that, one that puts your directories at the
|
|
|
6088 front of the load-path, the other at the end:
|
|
|
6089
|
|
|
6090 @lisp
|
|
|
6091 ;;; Add things at the beginning of the load-path, do not add
|
|
|
6092 ;;; duplicate directories:
|
|
|
6093 (pushnew "bar" load-path :test 'equal)
|
|
|
6094
|
|
|
6095 (pushnew "foo" load-path :test 'equal)
|
|
|
6096
|
|
|
6097 ;;; Add things at the end, unconditionally
|
|
|
6098 (setq load-path (nconc load-path '("foo" "bar")))
|
|
|
6099 @end lisp
|
|
|
6100
|
|
|
6101 @email{keithh@@nortel.ca, keith (k.p.) hanlan} writes:
|
|
|
6102
|
|
|
6103 @quotation
|
|
|
6104 To add directories using Unix shell metacharacters use
|
|
|
6105 @file{expand-file-name} like this:
|
|
|
6106
|
|
|
6107 @lisp
|
|
|
6108 (push (expand-file-name "~keithh/.emacsdir") load-path)
|
|
|
6109 @end lisp
|
|
|
6110 @end quotation
|
|
|
6111
|
|
|
6112 @node Q7.1.5, Q7.1.6, Q7.1.4, Advanced
|
|
|
6113 @unnumberedsubsec Q7.1.5: How to check if a lisp function is defined?
|
|
|
6114
|
|
|
6115 Use the following elisp:
|
|
|
6116
|
|
|
6117 @lisp
|
|
|
6118 (fboundp 'foo)
|
|
|
6119 @end lisp
|
|
|
6120
|
|
|
6121 It's almost always a mistake to test @code{emacs-version} or any similar
|
|
|
6122 variables.
|
|
|
6123
|
|
|
6124 Instead, use feature-tests, such as @code{featurep}, @code{boundp},
|
|
|
6125 @code{fboundp}, or even simple behavioral tests, eg.:
|
|
|
6126
|
|
|
6127 @lisp
|
|
|
6128 (defvar foo-old-losing-code-p
|
|
|
6129 (condition-case nil (progn (losing-code t) nil)
|
|
|
6130 (wrong-number-of-arguments t)))
|
|
|
6131 @end lisp
|
|
|
6132
|
|
|
6133 There is an incredible amount of broken code out there which could work
|
|
|
6134 much better more often in more places if it did the above instead of
|
|
|
6135 trying to divine its environment from the value of one variable.
|
|
|
6136
|
|
|
6137 @node Q7.1.6, Q7.2.1, Q7.1.5, Advanced
|
|
|
6138 @unnumberedsubsec Q7.1.6: Can I force the output of @code{(face-list)} to a buffer?
|
|
|
6139
|
|
|
6140 It would be good having it in a buffer, as the output of
|
|
|
6141 @code{(face-list)} is too wide to fit to a minibuffer.
|
|
|
6142
|
|
|
6143 Evaluate the expression in the @samp{*scratch*} buffer with point after
|
|
|
6144 the rightmost paren and typing @kbd{C-j}.
|
|
|
6145
|
|
|
6146 If the minibuffer smallness is the only problem you encounter, you can
|
|
|
6147 simply press @kbd{C-h l} to get the former minibuffer contents in a
|
|
|
6148 buffer.
|
|
|
6149
|
|
|
6150 @unnumberedsec 7.2: Emacs Lisp Programming Techniques
|
|
|
6151
|
|
|
6152 @node Q7.2.1, Q7.2.2, Q7.1.6, Advanced
|
|
|
6153 @unnumberedsubsec Q7.2.1: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
|
6154
|
|
|
6155 @email{clerik@@naggum.no, Erik Naggum} writes;
|
|
|
6156
|
|
|
6157 @quotation
|
|
|
6158 Emacs has a legacy of keyboards that produced characters with modifier
|
|
|
6159 bits, and therefore map a variety of input systems into this scheme even
|
|
|
6160 today. XEmacs is instead optimized for X events. This causes an
|
|
|
6161 incompatibility in the way key sequences are specified, but both Emacs
|
|
|
6162 and XEmacs will accept a key sequence as a vector of lists of modifiers
|
|
|
6163 that ends with a key, e.g., to bind @kbd{M-C-a}, you would say
|
|
|
6164 @code{[(meta control a)]} in both Emacsen. XEmacs has an abbreviated
|
|
|
6165 form for a single key, just (meta control a). Emacs has an abbreviated
|
|
|
6166 form for the Control and the Meta modifiers to string-characters (the
|
|
|
6167 ASCII characters), as in @samp{\M-\C-a}. XEmacs users need to be aware
|
|
|
6168 that the abbreviated form works only for one-character key sequences,
|
|
|
6169 while Emacs users need to be aware that the string-character is rather
|
|
|
6170 limited. Specifically, the string-character can accommodate only 256
|
|
|
6171 different values, 128 of which have the Meta modifier and 128 of which
|
|
|
6172 have not. In each of these blocks, only 32 characters have the Control
|
|
|
6173 modifier. Whereas @code{[(meta control A)]} differs from @code{[(meta
|
|
|
6174 control a)]} because the case differs, @samp{\M-\C-a} and @samp{\M-\C-A}
|
|
|
6175 do not. Programmers are advised to use the full common form, both
|
|
|
6176 because it is more readable and less error-prone, and because it is
|
|
|
6177 supported by both Emacsen.
|
|
|
6178 @end quotation
|
|
|
6179
|
|
|
6180 Another (even safer) way to be sure of the key-sequences is to use the
|
|
|
6181 @code{read-kbd-macro} function, which takes a string like @samp{C-c
|
|
|
6182 <up>}, and converts it to the internal key representation of the Emacs
|
|
|
6183 you use. The function is available both on XEmacs and GNU Emacs.
|
|
|
6184
|
|
|
6185 @node Q7.2.2, Q7.2.3, Q7.2.1, Advanced
|
|
|
6186 @unnumberedsubsec Q7.2.2: Can I generate "fake" keyboard events?
|
|
|
6187
|
|
|
6188 I wonder if there is an interactive function that can generate
|
|
|
6189 @dfn{fake} keyboard events. This way, I could simply map them inside
|
|
|
6190 XEmacs.
|
|
|
6191
|
|
|
6192 This seems to work:
|
|
|
6193
|
|
|
6194 @lisp
|
|
|
6195 (defun cg--generate-char-event (ch)
|
|
|
6196 "Generate an event, as if ch has been typed"
|
|
|
6197 (dispatch-event (character-to-event ch)))
|
|
|
6198
|
|
|
6199 ;; Backspace and Delete stuff
|
|
|
6200 (global-set-key [backspace]
|
|
|
6201 (lambda () (interactive) (cg--generate-char-event 127)))
|
|
|
6202 (global-set-key [unknown_keysym_0x4]
|
|
|
6203 (lambda () (interactive) (cg--generate-char-event 4)))
|
|
|
6204 @end lisp
|
|
|
6205
|
|
|
6206 @node Q7.2.3, Q7.2.4, Q7.2.2, Advanced
|
|
|
6207 @unnumberedsubsec Q7.2.3: Could you explain @code{read-kbd-macro} in more detail?
|
|
|
6208
|
|
|
6209 The @code{read-kbd-macro} function returns the internal Emacs
|
|
|
6210 representation of a human-readable string (which is its argument).
|
|
|
6211 Thus:
|
|
|
6212
|
|
|
6213 @lisp
|
|
|
6214 (read-kbd-macro "C-c C-a")
|
|
|
6215 @result{} [(control ?c) (control ?a)]
|
|
|
6216
|
|
|
6217 (read-kbd-macro "C-c C-. <up>")
|
|
|
6218 @result{} [(control ?c) (control ?.) up]
|
|
|
6219 @end lisp
|
|
|
6220
|
|
|
6221 In GNU Emacs the same forms will be evaluated to what GNU Emacs
|
|
|
6222 understands internally---the sequences @code{"\C-x\C-c"} and @code{[3
|
|
|
6223 67108910 up]}, respectively.
|
|
|
6224
|
|
|
6225 The exact @dfn{human-readable} syntax is defined in the docstring of
|
|
|
6226 @code{edmacro-mode}. I'll repeat it here, for completeness.
|
|
|
6227
|
|
|
6228 @quotation
|
|
|
6229 Format of keyboard macros during editing:
|
|
|
6230
|
|
|
6231 Text is divided into @dfn{words} separated by whitespace. Except for
|
|
|
6232 the words described below, the characters of each word go directly as
|
|
|
6233 characters of the macro. The whitespace that separates words is
|
|
|
6234 ignored. Whitespace in the macro must be written explicitly, as in
|
|
|
6235 @kbd{foo @key{SPC} bar @key{RET}}.
|
|
|
6236
|
|
|
6237 @itemize @bullet
|
|
|
6238 @item
|
|
|
6239 The special words @kbd{RET}, @kbd{SPC}, @kbd{TAB}, @kbd{DEL}, @kbd{LFD},
|
|
|
6240 @kbd{ESC}, and @kbd{NUL} represent special control characters. The
|
|
|
6241 words must be written in uppercase.
|
|
|
6242
|
|
|
6243 @item
|
|
|
6244 A word in angle brackets, e.g., @code{<return>}, @code{<down>}, or
|
|
|
6245 @code{<f1>}, represents a function key. (Note that in the standard
|
|
|
6246 configuration, the function key @code{<return>} and the control key
|
|
|
6247 @key{RET} are synonymous.) You can use angle brackets on the words
|
|
|
6248 @key{RET}, @key{SPC}, etc., but they are not required there.
|
|
|
6249
|
|
|
6250 @item
|
|
|
6251 Keys can be written by their @sc{ascii} code, using a backslash followed
|
|
|
6252 by up to six octal digits. This is the only way to represent keys with
|
|
|
6253 codes above \377.
|
|
|
6254
|
|
|
6255 @item
|
|
|
6256 One or more prefixes @kbd{M-} (meta), @kbd{C-} (control), @kbd{S-}
|
|
|
6257 (shift), @kbd{A-} (alt), @kbd{H-} (hyper), and @kbd{s-} (super) may
|
|
|
6258 precede a character or key notation. For function keys, the prefixes
|
|
|
6259 may go inside or outside of the brackets: @code{C-<down>} @equiv{}
|
|
|
6260 @code{<C-down>}. The prefixes may be written in any order: @kbd{M-C-x}
|
|
|
6261 @equiv{} @kbd{C-M-x}.
|
|
|
6262
|
|
|
6263 Prefixes are not allowed on multi-key words, e.g., @kbd{C-abc}, except
|
|
|
6264 that the Meta prefix is allowed on a sequence of digits and optional
|
|
|
6265 minus sign: @kbd{M--123} @equiv{} @kbd{M-- M-1 M-2 M-3}.
|
|
|
6266
|
|
|
6267 @item
|
|
|
6268 The @code{^} notation for control characters also works: @kbd{^M}
|
|
|
6269 @equiv{} @kbd{C-m}.
|
|
|
6270
|
|
|
6271 @item
|
|
|
6272 Double angle brackets enclose command names: @code{<<next-line>>} is
|
|
|
6273 shorthand for @kbd{M-x next-line @key{RET}}.
|
|
|
6274
|
|
|
6275 @item
|
|
|
6276 Finally, @code{REM} or @code{;;} causes the rest of the line to be
|
|
|
6277 ignored as a comment.
|
|
|
6278 @end itemize
|
|
|
6279
|
|
|
6280 Any word may be prefixed by a multiplier in the form of a decimal number
|
|
|
6281 and @code{*}: @code{3*<right>} @equiv{} @code{<right> <right> <right>},
|
|
|
6282 and @code{10*foo} @equiv{}
|
|
|
6283 @iftex
|
|
|
6284 @*
|
|
|
6285 @end iftex
|
|
|
6286 @code{foofoofoofoofoofoofoofoofoofoo}.
|
|
|
6287
|
|
|
6288 Multiple text keys can normally be strung together to form a word, but
|
|
|
6289 you may need to add whitespace if the word would look like one of the
|
|
|
6290 above notations: @code{; ; ;} is a keyboard macro with three semicolons,
|
|
|
6291 but @code{;;;} is a comment. Likewise, @code{\ 1 2 3} is four keys but
|
|
|
6292 @code{\123} is a single key written in octal, and @code{< right >} is
|
|
|
6293 seven keys but @code{<right>} is a single function key. When in doubt,
|
|
|
6294 use whitespace.
|
|
|
6295 @end quotation
|
|
|
6296
|
|
|
6297 @node Q7.2.4, Q7.2.5, Q7.2.3, Advanced
|
|
|
6298 @unnumberedsubsec Q7.2.4: What is the performance hit of @code{let}?
|
|
|
6299
|
|
|
6300 In most cases, not noticeable. Besides, there's no avoiding
|
|
|
6301 @code{let}---you have to bind your local variables, after all. Some
|
|
|
6302 pose a question whether to nest @code{let}s, or use one @code{let} per
|
|
|
6303 function. I think because of clarity and maintenance (and possible
|
|
|
6304 future implementation), @code{let}-s should be used (nested) in a way to
|
|
|
6305 provide the clearest code.
|
|
|
6306
|
|
|
6307 @node Q7.2.5, Q7.2.6, Q7.2.4, Advanced
|
|
|
6308 @unnumberedsubsec Q7.2.5: What is the recommended use of @code{setq}?
|
|
|
6309
|
|
|
6310 @itemize @bullet
|
|
|
6311 @item Global variables
|
|
|
6312
|
|
|
6313 You will typically @code{defvar} your global variable to a default
|
|
|
6314 value, and use @code{setq} to set it later.
|
|
|
6315
|
|
|
6316 It is never a good practice to @code{setq} user variables (like
|
|
|
6317 @code{case-fold-search}, etc.), as it ignores the user's choice
|
|
|
6318 unconditionally. Note that @code{defvar} doesn't change the value of a
|
|
|
6319 variable if it was bound previously. If you wish to change a
|
|
|
6320 user-variable temporarily, use @code{let}:
|
|
|
6321
|
|
|
6322 @lisp
|
|
|
6323 (let ((case-fold-search nil))
|
|
|
6324 ... ; code with searches that must be case-sensitive
|
|
|
6325 ...)
|
|
|
6326 @end lisp
|
|
|
6327
|
|
|
6328 You will notice the user-variables by their docstrings beginning with an
|
|
|
6329 asterisk (a convention).
|
|
|
6330
|
|
|
6331 @item Local variables
|
|
|
6332
|
|
|
6333 Bind them with @code{let}, which will unbind them (or restore their
|
|
|
6334 previous value, if they were bound) after exiting from the @code{let}
|
|
|
6335 form. Change the value of local variables with @code{setq} or whatever
|
|
|
6336 you like (e.g. @code{incf}, @code{setf} and such). The @code{let} form
|
|
|
6337 can even return one of its local variables.
|
|
|
6338
|
|
|
6339 Typical usage:
|
|
|
6340
|
|
|
6341 @lisp
|
|
|
6342 ;; iterate through the elements of the list returned by
|
|
|
6343 ;; `hairy-function-that-returns-list'
|
|
|
6344 (let ((l (hairy-function-that-returns-list)))
|
|
|
6345 (while l
|
|
|
6346 ... do something with (car l) ...
|
|
|
6347 (setq l (cdr l))))
|
|
|
6348 @end lisp
|
|
|
6349
|
|
|
6350 Another typical usage includes building a value simply to work with it.
|
|
|
6351
|
|
|
6352 @lisp
|
|
|
6353 ;; Build the mode keymap out of the key-translation-alist
|
|
|
6354 (let ((inbox (file-truename (expand-file-name box)))
|
|
|
6355 (i 0))
|
|
|
6356 ... code dealing with inbox ...
|
|
|
6357 inbox)
|
|
|
6358 @end lisp
|
|
|
6359
|
|
|
6360 This piece of code uses the local variable @code{inbox}, which becomes
|
|
|
6361 unbound (or regains old value) after exiting the form. The form also
|
|
|
6362 returns the value of @code{inbox}, which can be reused, for instance:
|
|
|
6363
|
|
|
6364 @lisp
|
|
|
6365 (setq foo-processed-inbox
|
|
|
6366 (let .....))
|
|
|
6367 @end lisp
|
|
|
6368 @end itemize
|
|
|
6369
|
|
|
6370 @node Q7.2.6, Q7.2.7, Q7.2.5, Advanced
|
|
|
6371 @unnumberedsubsec Q7.2.6: What is the typical misuse of @code{setq}?
|
|
|
6372
|
|
|
6373 A typical misuse is probably @code{setq}ing a variable that was meant to
|
|
|
6374 be local. Such a variable will remain bound forever, never to be
|
|
|
6375 garbage-collected. For example, the code doing:
|
|
|
6376
|
|
|
6377 @lisp
|
|
|
6378 (defun my-function (whatever)
|
|
|
6379 (setq a nil)
|
|
|
6380 ... build a large list ...
|
|
|
6381 ... and exit ...)
|
|
|
6382 @end lisp
|
|
|
6383
|
|
|
6384 does a bad thing, as @code{a} will keep consuming memory, never to be
|
|
|
6385 unbound. The correct thing is to do it like this:
|
|
|
6386
|
|
|
6387 @lisp
|
|
|
6388 (defun my-function (whatever)
|
|
|
6389 (let (a) ; default initialization is to nil
|
|
|
6390 ... build a large list ...
|
|
|
6391 ... and exit, unbinding `a' in the process ...)
|
|
|
6392 @end lisp
|
|
|
6393
|
|
|
6394 Not only is this prettier syntactically, but it makes it possible for
|
|
|
6395 Emacs to garbage-collect the objects which @code{a} used to reference.
|
|
|
6396
|
|
|
6397 Note that even global variables should not be @code{setq}ed without
|
|
|
6398 @code{defvar}ing them first, because the byte-compiler issues warnings.
|
|
|
6399 The reason for the warning is the following:
|
|
|
6400
|
|
|
6401 @lisp
|
|
|
6402 (defun flurgoze nil) ; ok, global internal variable
|
|
|
6403 ...
|
|
|
6404
|
|
|
6405 (setq flurghoze t) ; ops! a typo, but semantically correct.
|
|
|
6406 ; however, the byte-compiler warns.
|
|
|
6407
|
|
|
6408 While compiling toplevel forms:
|
|
|
6409 ** assignment to free variable flurghoze
|
|
|
6410 @end lisp
|
|
|
6411
|
|
|
6412 @node Q7.2.7, Q7.2.8, Q7.2.6, Advanced
|
|
|
6413 @unnumberedsubsec Q7.2.7: I like the @code{do} form of cl, does it slow things down?
|
|
|
6414
|
|
|
6415 It shouldn't. Here is what Dave Gillespie has to say about cl.el
|
|
|
6416 performance:
|
|
|
6417
|
|
|
6418 @quotation
|
|
|
6419 Many of the advanced features of this package, such as @code{defun*},
|
|
|
6420 @code{loop}, and @code{setf}, are implemented as Lisp macros. In
|
|
|
6421 byte-compiled code, these complex notations will be expanded into
|
|
|
6422 equivalent Lisp code which is simple and efficient. For example, the
|
|
|
6423 forms
|
|
|
6424
|
|
|
6425 @lisp
|
|
|
6426 (incf i n)
|
|
|
6427 (push x (car p))
|
|
|
6428 @end lisp
|
|
|
6429
|
|
|
6430 are expanded at compile-time to the Lisp forms
|
|
|
6431
|
|
|
6432 @lisp
|
|
|
6433 (setq i (+ i n))
|
|
|
6434 (setcar p (cons x (car p)))
|
|
|
6435 @end lisp
|
|
|
6436
|
|
|
6437 which are the most efficient ways of doing these respective operations
|
|
|
6438 in Lisp. Thus, there is no performance penalty for using the more
|
|
|
6439 readable @code{incf} and @code{push} forms in your compiled code.
|
|
|
6440
|
|
|
6441 @emph{Interpreted} code, on the other hand, must expand these macros
|
|
|
6442 every time they are executed. For this reason it is strongly
|
|
|
6443 recommended that code making heavy use of macros be compiled. (The
|
|
|
6444 features labelled @dfn{Special Form} instead of @dfn{Function} in this
|
|
|
6445 manual are macros.) A loop using @code{incf} a hundred times will
|
|
|
6446 execute considerably faster if compiled, and will also garbage-collect
|
|
|
6447 less because the macro expansion will not have to be generated, used,
|
|
|
6448 and thrown away a hundred times.
|
|
|
6449
|
|
|
6450 You can find out how a macro expands by using the @code{cl-prettyexpand}
|
|
|
6451 function.
|
|
|
6452 @end quotation
|
|
|
6453
|
|
|
6454 @node Q7.2.8, Q7.2.9, Q7.2.7, Advanced
|
|
|
6455 @unnumberedsubsec Q7.2.8: I like recursion, does it slow things down?
|
|
|
6456
|
|
|
6457 Yes. The Emacs byte-compiler cannot do much to optimize recursion. But
|
|
|
6458 think well whether this is a real concern in Emacs. Much of the Emacs
|
|
|
6459 slowness comes from internal mechanisms such as redisplay, or from the
|
|
|
6460 fact that it is an interpreter.
|
|
|
6461
|
|
|
6462 Please try not to make your code much uglier to gain a very small speed
|
|
|
6463 gain. It's not usually worth it.
|
|
|
6464
|
|
|
6465 @node Q7.2.9, Q7.2.10, Q7.2.8, Advanced
|
|
|
6466 @unnumberedsubsec Q7.2.9: How do I put a glyph as annotation in a buffer?
|
|
|
6467
|
|
|
6468 Here is a solution that will insert the glyph annotation at the
|
|
|
6469 beginning of buffer:
|
|
|
6470
|
|
|
6471 @lisp
|
|
|
6472 (make-annotation (make-glyph '([FORMAT :file FILE]
|
|
|
6473 [string :data "fallback-text"]))
|
|
|
6474 (point-min)
|
|
|
6475 'text
|
|
|
6476 (current-buffer))
|
|
|
6477 @end lisp
|
|
|
6478
|
|
|
6479 Replace @samp{FORMAT} with an unquoted symbol representing the format of
|
|
|
6480 the image (e.g. @code{xpm}, @code{xbm}, @code{gif}, @code{jpeg}, etc.)
|
|
|
6481 Instead of @samp{FILE}, use the image file name
|
|
|
6482 (e.g.
|
|
|
6483 @iftex
|
|
|
6484 @*
|
|
|
6485 @end iftex
|
|
|
6486 @file{/usr/local/lib/xemacs-21.4/etc/recycle.xpm}).
|
|
|
6487
|
|
|
6488 You can turn this to a function (that optionally prompts you for a file
|
|
|
6489 name), and inserts the glyph at @code{(point)} instead of
|
|
|
6490 @code{(point-min)}.
|
|
|
6491
|
|
|
6492 @node Q7.2.10, Q7.2.11, Q7.2.9, Advanced
|
|
|
6493 @unnumberedsubsec Q7.2.10: @code{map-extents} won't traverse all of my extents!
|
|
|
6494
|
|
|
6495 I tried to use @code{map-extents} to do an operation on all the extents
|
|
|
6496 in a region. However, it seems to quit after processing a random number
|
|
|
6497 of extents. Is it buggy?
|
|
|
6498
|
|
|
6499 No. The documentation of @code{map-extents} states that it will iterate
|
|
|
6500 across the extents as long as @var{function} returns @code{nil}.
|
|
|
6501 Unexperienced programmers often forget to return @code{nil} explicitly,
|
|
|
6502 which results in buggy code. For instance, the following code is
|
|
|
6503 supposed to delete all the extents in a buffer, and issue as many
|
|
|
6504 @samp{fubar!} messages.
|
|
|
6505
|
|
|
6506 @lisp
|
|
|
6507 (map-extents (lambda (ext ignore)
|
|
|
6508 (delete-extent ext)
|
|
|
6509 (message "fubar!")))
|
|
|
6510 @end lisp
|
|
|
6511
|
|
|
6512 Instead, it will delete only the first extent, and stop right there --
|
|
|
6513 because @code{message} will return a non-nil value. The correct code
|
|
|
6514 is:
|
|
|
6515
|
|
|
6516 @lisp
|
|
|
6517 (map-extents (lambda (ext ignore)
|
|
|
6518 (delete-extent ext)
|
|
|
6519 (message "fubar!")
|
|
|
6520 nil))
|
|
|
6521 @end lisp
|
|
|
6522
|
|
|
6523 @node Q7.2.11, Q7.3.1, Q7.2.10, Advanced
|
|
|
6524 @unnumberedsubsec Q7.2.11: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
|
6525 @c New
|
|
|
6526
|
|
|
6527 @email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
|
|
|
6528 @quotation
|
|
|
6529 Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence},
|
|
|
6530 press a key (say @key{RET} in the Gnus Group buffer), and get the
|
|
|
6531 results using @kbd{M-x profile-results}. It should give you an idea of
|
|
|
6532 where the time is being spent.
|
|
|
6533 @end quotation
|
|
|
6534
|
|
|
6535 @unnumberedsec 7.3: Mathematics
|
|
|
6536
|
|
|
6537 @node Q7.3.1, Q7.3.2, Q7.2.11, Advanced
|
|
|
6538 @unnumberedsubsec Q7.3.1: What are bignums, ratios, and bigfloats in Lisp?
|
|
|
6539
|
|
|
6540 Thanks to @email{james@@xemacs.org, Jerry James}, XEmacs 21.5.18 and
|
|
|
6541 later can use the capabilities of multiple-precision libraries that may
|
|
|
6542 be available for your platform. The GNU Multiple Precision (GMP) and
|
|
|
6543 BSD Multiple Precision (MP) libraries are partially supported. GMP
|
|
|
6544 gives you @dfn{bignums} (arbitrary precision integers), @dfn{ratios}
|
|
|
6545 (arbitrary precision fractions), and @dfn{bigfloats} (arbitrary
|
|
|
6546 precision floating point numbers). GNU MP is better-supported by XEmacs
|
|
|
6547 at the time of writing (2004-04-06). BSD MP support does not include
|
|
|
6548 ratios or bigfloats, and it throws errors that aren't understood.
|
|
|
6549
|
|
|
6550 In most cases, bignum support should be transparent to users and Lisp
|
|
|
6551 programmers. A bignum-enabled XEmacs will automatically convert from
|
|
|
6552 fixnums to bignums and back in pure integer arithmetic, and for GNU MP,
|
|
|
6553 from floats to bigfloats. (Bigfloats must be explicitly coerced to
|
|
|
6554 other types, even if they are exactly representable by less precise
|
|
|
6555 types.) The Lisp reader and printer have been enhanced to handle
|
|
|
6556 bignums, as have the mathematical functions. Rationals (fixnums,
|
|
|
6557 bignums, and ratios) are printed using the @samp{%d}, @samp{%o},
|
|
|
6558 @samp{%x}, and @samp{%u} format conversions. The read syntax for ratios
|
|
|
6559 is @samp{3/5}.
|
|
|
6560
|
|
|
6561 User-visible changes in behavior include (in probable order of annoyance)
|
|
|
6562
|
|
|
6563 @itemize
|
|
|
6564 @item
|
|
|
6565 Arithmetic can cause a segfault, depending on your MP library
|
|
|
6566 @ref{Q7.3.2, XEmacs segfaults when I use very big numbers!}.
|
|
|
6567
|
|
|
6568 @item
|
|
|
6569 Terminology is not Common-Lisp-conforming. For example, ``integer'' for
|
|
|
6570 Emacs Lisp means what Common Lisp calls ``fixnum''. This issue is being
|
|
|
6571 investigated, but the use of ``integer'' for fixnum is pervasive and may
|
|
|
6572 cause backward-compatibility and GNU-Emacs-compatibility problems.
|
|
|
6573
|
|
|
6574 @item
|
|
|
6575 Many operations that used to cause a range error now succeed, with
|
|
|
6576 intermediate results and return values coerced to bignums as needed.
|
|
|
6577
|
|
|
6578 @item
|
|
|
6579 An atom with ratio read syntax now returns a number, not a symbol.
|
|
|
6580
|
|
|
6581 @item
|
|
|
6582 The @samp{%u} format conversion will now give an error if its argument
|
|
|
6583 is negative. (Without MP, it prints a number which Lisp can't read.)
|
|
|
6584 @end itemize
|
|
|
6585
|
|
|
6586 @emph{Surgeon General's Warning}: The automatic conversions cannot be
|
|
|
6587 disabled at runtime. New functions have been added which produce
|
|
|
6588 ratios, so there should be few surprises with type conflicts, but they
|
|
|
6589 can't be ruled out. ``Arbitrary'' precision means precisely what it
|
|
|
6590 says. If you work with extremely large numbers, your machine may
|
|
|
6591 arbitrarily decide to hand you an unpleasant surprise rather than a
|
|
|
6592 bignum @ref{Q7.3.2, XEmacs segfaults when I use very big numbers!}.
|
|
|
6593
|
|
|
6594 To configure with GNU MP, add
|
|
|
6595 @samp{--use-number-lib=gmp}
|
|
|
6596 to your invocation of @file{configure}. For BSD MP, use
|
|
|
6597 @samp{--use-number-lib=mp}.
|
|
|
6598
|
|
|
6599 If you would like to help with bignum support, especially on BSD MP,
|
|
|
6600 please subscribe to the @uref{http://www.xemacs.org/Lists/#xemacs-beta,
|
|
|
6601 XEmacs Beta mailing list}, and book up on @file{number-gmp.h} and
|
|
|
6602 @file{number-mp.h}. Jerry has promised to write internals documentation
|
|
|
6603 eventually, but if your skills run more to analysis and documentation
|
|
|
6604 than to writing new code, feel free to fill in the gap!
|
|
|
6605
|
|
|
6606
|
|
|
6607 @node Q7.3.2, Q7.3.3, Q7.3.1, Advanced
|
|
|
6608 @unnumberedsubsec Q7.3.2: XEmacs segfaults when I use very big numbers!
|
|
|
6609
|
|
|
6610 GMP by default allocates temporaries on the stack. If you run out of
|
|
|
6611 stack space, you're dead; there is no way that we know of to reliably
|
|
|
6612 detect this condition, because @samp{alloca} is typically implemented to
|
|
|
6613 be @emph{fast} rather than robust. If you just need a little more
|
|
|
6614 oomph, use a bigger stack (@emph{e.g.}, the @file{ulimit -s} command in
|
|
|
6615 bash(1)). If you want robustness at the cost of speed, configure GMP
|
|
|
6616 with @samp{--disable-alloca} and rebuild the GMP library.
|
|
|
6617
|
|
|
6618 We do not know whether BSD MP uses @samp{alloca} or not. Please send
|
|
|
6619 any information you have as a bug report (@kbd{M-x report-xemacs-bug
|
|
|
6620 @key{RET}}), which will give us platform information. (We do know that
|
|
|
6621 BSD MP implementations vary across vendors, but how much, we do not know
|
|
|
6622 yet.)
|
|
|
6623
|
|
|
6624
|
|
|
6625 @node Q7.3.3, Q7.3.4, Q7.3.2, Advanced
|
|
|
6626 @unnumberedsubsec Q7.3.3: Bignums are really slow!
|
|
|
6627
|
|
|
6628 Many Linux distributions compile all their packages for the i386, and
|
|
|
6629 this is costly. An optimized version can give you two or three orders
|
|
|
6630 of magnitude better performance for a Pentium III or IV. (Yes, really.
|
|
|
6631 See @uref{http://www.swox.com/gmp/gmp-speed.html}.)
|
|
|
6632
|
|
|
6633
|
|
|
6634 @node Q7.3.4, , Q7.3.3, Advanced
|
|
|
6635 @unnumberedsubsec Q7.3.4: Equal bignums don't compare as equal! What gives?
|
|
|
6636
|
|
|
6637 Ah, Grasshopper, I see you are using @code{(eq x y)}. The Bodhisattva
|
|
|
6638 CLTL2 warned of the illusion that equal numbers would be @samp{eq}!
|
|
|
6639 Meditate on the deeper truths of @samp{eql}, in which numbers of the same
|
|
|
6640 type which have equal values compare equal, and @samp{=}, which does any
|
|
|
6641 necessary type coercions before comparing for equality.
|
|
|
6642
|
|
|
6643 Yeah, yeah, it has always worked for integer types, because fixnums and
|
|
|
6644 characters have an immediate representation. Sorry about that;
|
|
|
6645 arbitrary precision obviously requires consing new objects because the
|
|
|
6646 objects are ``large'' and of variable size, and the definition of
|
|
|
6647 @samp{eq} does not permit different objects to compare as equal.
|
|
|
6648
|
|
|
6649 @node Other Packages, Current Events, Advanced, Top
|
|
|
6650 @unnumbered 8 Other External Packages
|
|
|
6651
|
|
|
6652 This is part 8 of the XEmacs Frequently Asked Questions list. This
|
|
|
6653 section is devoted to miscellaneous external packages not covered
|
|
|
6654 elsewhere in XEmacs.
|
|
|
6655
|
|
|
6656 @menu
|
|
|
6657 * Q8.0.1:: Is there something better than LaTeX mode?
|
|
|
6658 * Q8.0.2:: What is AUCTeX? Where do you get it?
|
|
|
6659 * Q8.0.3:: Problems installing AUCTeX.
|
|
|
6660 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline?
|
|
|
6661
|
|
|
6662 8.1: Other Unbundled Packages
|
|
|
6663 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
|
6664 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets?
|
|
|
6665 * Q8.1.3:: Is there a MatLab mode?
|
|
|
6666
|
|
|
6667 8.2: Environments Built Around XEmacs
|
|
|
6668 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop?
|
|
|
6669 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21?
|
|
|
6670 * Q8.2.3:: What is/was Energize?
|
|
|
6671 * Q8.2.4:: What is Infodock?
|
|
|
6672 @end menu
|
|
|
6673
|
|
|
6674 @unnumberedsec 8.0: TeX
|
|
|
6675
|
|
|
6676 @node Q8.0.1, Q8.0.2, Other Packages, Other Packages
|
|
|
6677 @unnumberedsubsec Q8.0.1: Is there something better than LaTeX mode?
|
|
2417
|
6678
|
|
|
6679 @email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes:
|
|
|
6680
|
|
|
6681 @quotation
|
|
|
6682 The standard TeX modes leave much to be desired, and are somewhat
|
|
2459
|
6683 leniently maintained. Serious TeX users use AUCTeX (@pxref{Q8.0.2,
|
|
2417
|
6684 What is AUCTeX? Where do you get it?}).
|
|
|
6685 @end quotation
|
|
|
6686
|
|
2459
|
6687 @node Q8.0.2, Q8.0.3, Q8.0.1, Other Packages
|
|
|
6688 @unnumberedsubsec Q8.0.2: What is AUCTeX? Where do you get it?
|
|
2417
|
6689
|
|
|
6690 AUCTeX is a complex and sophisticated editing package dedicated to TeX
|
|
|
6691 and related text formatting languages, including LaTeX and Texinfo.
|
|
|
6692 It provides support for running TeX on a file or part of a file,
|
|
|
6693 include files, and of course shortcuts for entering common TeX macros,
|
|
|
6694 LaTeX environments, etc, and for fontlock.
|
|
|
6695
|
|
|
6696 AUCTeX is a standard package provided by XEmacs. You can get it as
|
|
|
6697 usual through the @kbd{M-x list-packages} interface. It is also
|
|
|
6698 included in the (non-Mule) SUMO package. The AUCTeX XEmacs package is
|
|
|
6699 maintained by Uwe Brauer <GET MAIL ADDRESS>.
|
|
|
6700
|
|
|
6701 AUCTeX is extremely complicated, and its developers primarily
|
|
|
6702 use GNU Emacs. Not all features of the bleeding edge version
|
|
|
6703 of AUCTeX are immediately ported to XEmacs; if you need
|
|
|
6704 these, you may be better off getting the most recent versions
|
|
|
6705 from the GNU AUCTeX project on @uref{http://savannah.gnu.org}.
|
|
|
6706
|
|
2459
|
6707 @node Q8.0.3, Q8.0.4, Q8.0.2, Other Packages
|
|
|
6708 @unnumberedsubsec Q8.0.3: Problems installing AUCTeX.
|
|
2417
|
6709
|
|
|
6710 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
|
|
|
6711
|
|
|
6712 @quotation
|
|
|
6713 AUCTeX works fine on both stock Emacs and XEmacs has been doing so for
|
|
|
6714 a very very long time. This is mostly due to the work of
|
|
|
6715 @email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu}
|
|
|
6716 package. Which leads to what is probably the problem...
|
|
|
6717 @end quotation
|
|
|
6718
|
|
|
6719 Most problems with AUCTeX are one of two things:
|
|
|
6720
|
|
|
6721 @itemize @bullet
|
|
|
6722 @item
|
|
|
6723 The TeX-lisp-directory in @file{tex-site.el} and the makefile don't
|
|
|
6724 match.
|
|
|
6725
|
|
|
6726 Fix: make sure you configure AUCTeX properly @strong{before} installing.
|
|
|
6727
|
|
|
6728 @item
|
|
|
6729 You have an old version of easymenu.el in your path.
|
|
|
6730
|
|
|
6731 Fix: use @code{locate-library} and remove old versions to make sure it
|
|
|
6732 @strong{only} finds the one that came with XEmacs.
|
|
|
6733 @end itemize
|
|
|
6734
|
|
2459
|
6735 @node Q8.0.4, Q8.1.1, Q8.0.3, Other Packages
|
|
|
6736 @unnumberedsubsec Q8.0.4: How do I turn off current chapter from AUCTeX modeline?
|
|
2417
|
6737
|
|
|
6738 With AUCTeX, fast typing is hard because the current chapter, section
|
|
|
6739 etc. are given in the modeline. How can I turn this off?
|
|
|
6740
|
|
|
6741 It's not AUCTeX, it comes from @code{func-menu} in @file{func-menu.el}.
|
|
|
6742
|
|
|
6743 @c Add this code to your @file{init.el} to turn it off:
|
|
|
6744 @c
|
|
|
6745 @c @lisp
|
|
|
6746 @c (setq fume-display-in-modeline-p nil)
|
|
|
6747 @c @end lisp
|
|
|
6748 @c
|
|
|
6749 @c Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
|
|
|
6750 @c mode:
|
|
|
6751 @c
|
|
|
6752 @c @lisp
|
|
|
6753 @c (add-hook 'TeX-mode-hook
|
|
|
6754 @c '(lambda () (setq fume-display-in-modeline-p nil)))
|
|
|
6755 @c @end lisp
|
|
|
6756 @c
|
|
|
6757 @email{dhughes@@origin-at.co.uk, David Hughes} writes:
|
|
|
6758
|
|
|
6759 @quotation
|
|
|
6760 Try this; you'll still get the function name displayed in the modeline,
|
|
|
6761 but it won't attempt to keep track when you modify the file. To refresh
|
|
|
6762 when it gets out of synch, you simply need click on the @samp{Rescan
|
|
|
6763 Buffer} option in the function-menu.
|
|
|
6764
|
|
|
6765 @lisp
|
|
|
6766 (setq-default fume-auto-rescan-buffer-p nil)
|
|
|
6767 @end lisp
|
|
|
6768 @end quotation
|
|
|
6769
|
|
2459
|
6770 @unnumberedsec 8.1: Other Unbundled Packages
|
|
|
6771
|
|
|
6772 @node Q8.1.1, Q8.1.2, Q8.0.4, Other Packages
|
|
|
6773 @unnumberedsubsec Q8.1.1: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
2417
|
6774
|
|
|
6775 The reason for an Emacs package not to be included in XEmacs is
|
|
|
6776 usually one or more of the following:
|
|
|
6777
|
|
|
6778 @enumerate
|
|
|
6779 @item
|
|
|
6780 The package has not been ported to XEmacs. This will typically happen
|
|
|
6781 when it uses GNU-Emacs-specific features, which make it fail under
|
|
|
6782 XEmacs.
|
|
|
6783
|
|
|
6784 Porting a package to XEmacs can range from a trivial amount of change to
|
|
|
6785 a partial or full rewrite. Fortunately, the authors of modern packages
|
|
|
6786 usually choose to support both Emacsen themselves.
|
|
|
6787
|
|
|
6788 @item
|
|
|
6789 The package has been decided not to be appropriate for XEmacs. It may
|
|
|
6790 have an equivalent or better replacement within XEmacs, in which case
|
|
|
6791 the developers may choose not to burden themselves with supporting an
|
|
|
6792 additional package.
|
|
|
6793
|
|
|
6794 Each package bundled with XEmacs means more work for the maintainers,
|
|
|
6795 whether they want it or not. If you are ready to take over the
|
|
|
6796 maintenance responsibilities for the package you port, be sure to say
|
|
|
6797 so---we will more likely include it.
|
|
|
6798
|
|
|
6799 @item
|
|
|
6800 The package simply hasn't been noted by the XEmacs development. If
|
|
|
6801 that's the case, the messages like yours are very useful for attracting
|
|
|
6802 our attention.
|
|
|
6803
|
|
|
6804 @item
|
|
|
6805 The package was noted by the developers, but they simply haven't yet
|
|
|
6806 gotten around to including/porting it. Wait for the next release or,
|
|
|
6807 even better, offer your help. It will be gladly accepted and
|
|
|
6808 appreciated.
|
|
|
6809 @end enumerate
|
|
|
6810
|
|
2459
|
6811 @node Q8.1.2, Q8.1.3, Q8.1.1, Other Packages
|
|
|
6812 @unnumberedsubsec Q8.1.2: Are there any Emacs Lisp Spreadsheets?
|
|
2417
|
6813
|
|
|
6814 Yes. Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at
|
|
428
|
6815 @iftex
|
|
|
6816 @*
|
|
|
6817 @end iftex
|
|
2459
|
6818 @uref{http://acs.ist.psu.edu/dismal/dismal.html}.
|
|
|
6819
|
|
|
6820 @node Q8.1.3, Q8.2.1, Q8.1.2, Other Packages
|
|
|
6821 @unnumberedsubsec Q8.1.3: Is there a MatLab mode?
|
|
2417
|
6822
|
|
|
6823 Yes, a matlab mode and other items are available at the
|
|
2459
|
6824 @uref{http://www.mathworks.com/matlabcentral/files/104/matlab.el}.
|
|
|
6825
|
|
|
6826 @unnumberedsec 8.2: Environments Built Around XEmacs
|
|
|
6827
|
|
|
6828 @node Q8.2.1, Q8.2.2, Q8.1.3, Other Packages
|
|
|
6829 @unnumberedsubsec Q8.2.1: What are SPARCworks, EOS, and WorkShop?
|
|
2417
|
6830
|
|
|
6831 SPARCworks was a development environment from Sun (circa 1993-1996)
|
|
|
6832 and consisted of compilers (C, C++, FORTRAN 77, Fortran 90, Ada, and
|
|
|
6833 Pascal), a debugger, and other tools such as TeamWare (for
|
|
|
6834 configuration management), MakeTool, etc.
|
|
428
|
6835
|
|
|
6836 EOS is the integration of XEmacs with the SPARCworks debugger. It
|
|
|
6837 allows one to use an XEmacs frame to view code (complete with
|
|
|
6838 fontification, etc.), set breakpoints, print variables, etc., while
|
|
2417
|
6839 using the SPARCworks debugger.
|
|
|
6840
|
|
|
6841 EOS stands for "Era on SPARCworks"; Era stood for "Emacs Rewritten
|
|
|
6842 Again" and was the name used by Sun for its modified version of Lucid
|
|
|
6843 Emacs (later XEmacs) in the early-mid 90's. This is documented in
|
|
|
6844 more detail in the history section of the XEmacs About page.
|
|
|
6845
|
|
|
6846 EOS was replaced around 1996 with a newer graphical development
|
|
|
6847 environment called Sun WorkShop. The current status of this is
|
|
|
6848 unknown.
|
|
|
6849
|
|
2459
|
6850 @node Q8.2.2, Q8.2.3, Q8.2.1, Other Packages
|
|
|
6851 @unnumberedsubsec Q8.2.2: How do I start the Sun Workshop support in XEmacs 21?
|
|
428
|
6852
|
|
|
6853 Add the switch ---with-workshop to the configure command when building
|
|
|
6854 XEmacs and put the following in one of your startup files
|
|
|
6855 (e.g. site-start.el or .emacs):
|
|
|
6856
|
|
|
6857 @lisp
|
|
|
6858 (when (featurep 'tooltalk)
|
|
|
6859 (load "tooltalk-macros")
|
|
|
6860 (load "tooltalk-util")
|
|
|
6861 (load "tooltalk-init"))
|
|
|
6862 (when (featurep 'sparcworks)
|
|
|
6863 (load "sunpro-init")
|
|
|
6864 (load "ring")
|
|
|
6865 (load "comint")
|
|
|
6866 (load "annotations")
|
|
|
6867 (sunpro-startup))
|
|
|
6868 @end lisp
|
|
|
6869
|
|
|
6870 If you are not using the latest Workshop (5.0) you have to apply the
|
|
|
6871 following patch:
|
|
|
6872
|
|
|
6873 @format
|
|
|
6874 --- /opt/SUNWspro/lib/eserve.el.ORIG Fri May 14 15:23:26 1999
|
|
|
6875 +++ /opt/SUNWspro/lib/eserve.el Fri May 14 15:24:54 1999
|
|
|
6876 @@@@ -42,7 +42,7 @@@@
|
|
|
6877 (defvar running-xemacs nil "t if we're running XEmacs")
|
|
|
6878 (defvar running-emacs nil "t if we're running GNU Emacs 19")
|
|
438
|
6879
|
|
428
|
6880 -(if (string-match "^\\(19\\|20\\)\..*\\(XEmacs\\|Lucid\\)" emacs-version)
|
|
|
6881 +(if (string-match "\\(XEmacs\\|Lucid\\)" emacs-version)
|
|
|
6882 (setq running-xemacs t)
|
|
|
6883 (setq running-emacs t))
|
|
438
|
6884 @end format
|
|
428
|
6885
|
|
2459
|
6886 @node Q8.2.3, Q8.2.4, Q8.2.2, Other Packages
|
|
|
6887 @unnumberedsubsec Q8.2.3: What is/was Energize?
|
|
2417
|
6888
|
|
|
6889 The "Energize Programming System" was a C and C++ development environment
|
|
|
6890 sold by Lucid, Inc. It was the reason why Lucid Emacs, now XEmacs, was
|
|
|
6891 created in the first place. Unfortunately, Lucid went out of business in
|
|
|
6892 1994. The rights to sell it in Japan were purchased by INS
|
|
|
6893 Engineering (which briefly employed Stig Hackvan aka Jonathan
|
|
|
6894 Stigelman to work on Japanese support for XEmacs, in late 1994 and
|
|
|
6895 early 1995) and Tartan bought the rights to sell it in the rest of the
|
|
|
6896 world. However, INS is not selling Energize at this point and may or
|
|
|
6897 may not have ever done so; Tartan certainly never did.
|
|
|
6898
|
|
2459
|
6899 @node Q8.2.4, , Q8.2.3, Other Packages
|
|
|
6900 @unnumberedsubsec Q8.2.4: What is Infodock?
|
|
428
|
6901
|
|
660
|
6902 @uref{http://sourceforge.net/projects/infodock/, InfoDock} is an
|
|
|
6903 integrated productivity toolset, mainly aimed at technical people,
|
|
|
6904 hosted at SourceForge.
|
|
428
|
6905
|
|
|
6906 InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of
|
|
|
6907 the power of Emacs, but with an easier to use and more comprehensive
|
|
|
6908 menu-based user interface. The bottom portion of this text describes
|
|
|
6909 how it differs from XEmacs and GNU Emacs from the Free Software
|
|
|
6910 Foundation.
|
|
|
6911
|
|
|
6912 InfoDock is aimed at people who want a free, turn-key productivity
|
|
|
6913 environment. Although InfoDock is customizable, it is not intended for
|
|
|
6914 people who like basic versions of Emacs which need to be customized
|
|
|
6915 extensively for local use; standard Emacs distributions are better for
|
|
|
6916 such uses. InfoDock is for those people who want a complete,
|
|
|
6917 pre-customized environment in one package, which they need not touch
|
|
|
6918 more than once or twice a year to update to new revisions.
|
|
|
6919
|
|
|
6920 InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX,
|
|
|
6921 and Intel Linux systems. It is intended for use on a color display,
|
|
|
6922 although most features will work on monochrome monitors. Simply unpack
|
|
|
6923 InfoDock according to the instructions in the ID-INSTALL file and you
|
|
|
6924 are ready to run.
|
|
|
6925
|
|
|
6926 The InfoDock Manual is concise, yet sufficient as a user guide for users
|
|
|
6927 who have never used an Emacs-type editor before. For users who are
|
|
|
6928 already familiar with Emacs, it supplements the information in the GNU
|
|
|
6929 Emacs Manual.
|
|
|
6930
|
|
|
6931 InfoDock menus are much more extensive and more mature than standard
|
|
|
6932 Emacs menus. Each menu offers a @samp{Manual} item which displays
|
|
|
6933 documentation associated with the menu's functions.
|
|
|
6934
|
|
|
6935 @noindent
|
|
|
6936 Four types of menubars are provided:
|
|
|
6937 @enumerate
|
|
|
6938 @item
|
|
|
6939 An extensive menubar providing access to global InfoDock commands.
|
|
|
6940 @item
|
|
|
6941 Mode-specific menubars tailored to the current major mode.
|
|
|
6942 @item
|
|
|
6943 A simple menubar for basic editing to help novices get started with InfoDock.
|
|
|
6944 @item
|
|
|
6945 The standard XEmacs menubar.
|
|
|
6946 @end enumerate
|
|
|
6947
|
|
|
6948 Most modes also include mode-specific popup menus. Additionally, region and
|
|
|
6949 rectangle popup menus are included.
|
|
|
6950
|
|
|
6951 @samp{Hyperbole}, the everyday information manager, is a core part of
|
|
|
6952 InfoDock. This provides context-sensitive mouse keys, a rolodex-type
|
|
|
6953 contact manager, programmable hypertext buttons, and an autonumbered
|
|
|
6954 outliner with embedded hyperlink anchors.
|
|
|
6955
|
|
|
6956 The @samp{OO-Browser}, a multi-language object-oriented code browser, is a
|
|
|
6957 standard part of InfoDock.
|
|
|
6958
|
|
|
6959 InfoDock saves a more extensive set of user options than other Emacs
|
|
|
6960 versions.
|
|
|
6961
|
|
|
6962 InfoDock inserts a useful file header in many file types, showing the
|
|
|
6963 author, summary, and last modification time of each file. A summary
|
|
|
6964 program can then be used to summarize all of the files in a directory,
|
|
|
6965 for easy MANIFEST file creation.
|
|
|
6966
|
|
|
6967 Your working set of buffers is automatically saved and restored (if you
|
|
|
6968 answer yes to a prompt) between InfoDock sessions.
|
|
|
6969
|
|
|
6970 Refined color choices for code highlighting are provided for both dark and
|
|
|
6971 light background display frames.
|
|
|
6972
|
|
|
6973 The @kbd{C-z} key prefix performs frame-based commands which parallel the
|
|
|
6974 @kbd{C-x} key prefix for window-based commands.
|
|
|
6975
|
|
|
6976 The Smart Menu system is included for producing command menus on dumb
|
|
|
6977 terminals.
|
|
|
6978
|
|
|
6979 Lisp libraries are better categorized according to function.
|
|
|
6980
|
|
|
6981 Extensions and improvements to many areas of Emacs are included, such as:
|
|
|
6982 paragraph filling, mail reading with Rmail, shell handling, outlining, code
|
|
|
6983 highlighting and browsing, and man page browsing.
|
|
|
6984
|
|
|
6985 InfoDock questions, answers and discussion should go to the mail list
|
|
|
6986 @iftex
|
|
|
6987 @*
|
|
|
6988 @end iftex
|
|
|
6989 @email{infodock@@infodock.com}. Use
|
|
|
6990 @email{infodock-request@@infodock.com} to be added or removed from the
|
|
|
6991 list. Always include your InfoDock version number when sending help
|
|
|
6992 requests.
|
|
|
6993
|
|
2459
|
6994 @node Current Events, Legacy Versions, Other Packages, Top
|
|
|
6995 @unnumbered 9 What the Future Holds
|
|
|
6996
|
|
|
6997 This is part 9 of the XEmacs Frequently Asked Questions list. This
|
|
611
|
6998 section will change frequently, and (in theory) should contain any
|
|
|
6999 interesting items that have transpired recently. (But in practice it's
|
|
|
7000 not getting updated like this.)
|
|
|
7001
|
|
|
7002 This section also contains descriptions of the new features in all the
|
|
|
7003 recent releases of XEmacs. For the most part, the information below is
|
|
|
7004 a synopsis of the more complete information that can be found in the
|
|
|
7005 file @file{NEWS} in the @file{etc} directory of the XEmacs distribution.
|
|
|
7006 You can view this file in XEmacs using @kbd{C-h n} or the @samp{Help}
|
|
|
7007 menu.
|
|
|
7008
|
|
|
7009 Information on older versions of XEmacs can be find in @file{ONEWS} in
|
|
|
7010 the same directory, or @file{OONEWS} for really old versions.
|
|
|
7011
|
|
428
|
7012 @menu
|
|
2459
|
7013 * Q9.0.1:: What new features will be in XEmacs soon?
|
|
|
7014 * Q9.0.2:: What's new in XEmacs 21.4?
|
|
|
7015 * Q9.0.3:: What's new in XEmacs 21.1?
|
|
|
7016 * Q9.0.4:: What's new in XEmacs 20.4?
|
|
|
7017 * Q9.0.5:: What's new in XEmacs 20.3?
|
|
|
7018 * Q9.0.6:: What's new in XEmacs 20.2?
|
|
428
|
7019 @end menu
|
|
|
7020
|
|
2459
|
7021 @unnumberedsec 9.0: Changes
|
|
|
7022
|
|
|
7023 @node Q9.0.1, Q9.0.2, Current Events, Current Events
|
|
|
7024 @unnumberedsubsec Q9.0.1: What new features will be in XEmacs soon?
|
|
611
|
7025
|
|
2417
|
7026 #### Write me.
|
|
428
|
7027
|
|
2459
|
7028 @node Q9.0.2, Q9.0.3, Q9.0.1, Current Events
|
|
|
7029 @unnumberedsubsec Q9.0.2: What's new in XEmacs 21.4?
|
|
611
|
7030
|
|
|
7031 21.4 was the "stable" version of the 21.2 series, which was considered
|
|
|
7032 "experimental" throughout its life; thus there were no "official"
|
|
|
7033 releases at all. In essence, XEmacs is now following the "alternating"
|
|
|
7034 scheme of Linux, where at any point there are at least two different
|
|
|
7035 development branches, one "stable" and one "experimental". Periodic
|
|
|
7036 releases happen in both branches, but those in the experimental branch
|
|
|
7037 are not tested as well, and there's no guarantee they will work at all.
|
|
|
7038 The experiemental branch is open to any and all code that's acceptable
|
|
|
7039 to the developers; the stable branch, however, is in general limited
|
|
|
7040 only to bug fixes, and all contributions are carefully reviewed to make
|
|
|
7041 sure they will increase and not decrease stability.
|
|
|
7042
|
|
|
7043 21.3 never existed at all; it was decided to follow the Linux scheme
|
|
|
7044 exactly, where odd-numbered series are experimental and even-numbered
|
|
|
7045 ones stable.
|
|
|
7046
|
|
|
7047 The following lists summarizes the essential changes made in this
|
|
|
7048 version. For a fuller list, see the @file{NEWS} in the @file{etc}
|
|
|
7049 directory of the XEmacs distribution, or use @kbd{C-h n} or the
|
|
|
7050 @samp{Help} menu to view this file inside of XEmacs.
|
|
|
7051
|
|
676
|
7052 @unnumberedsubsubsec User-visible changes in XEmacs 21.4
|
|
611
|
7053
|
|
|
7054 @itemize @bullet
|
|
|
7055
|
|
|
7056 @item
|
|
|
7057 The delete key now deletes forward by default.
|
|
|
7058 @item
|
|
|
7059 Shifted motion keys now select text by default.
|
|
|
7060 @item
|
|
|
7061 You can now build XEmacs with support for GTK+ widget set.
|
|
|
7062 @item
|
|
|
7063 ~/.xemacs/init.el is now the preferred location for the init
|
|
|
7064 file. (XEmacs now supports a `~/.xemacs/init.el' startup file. Custom
|
|
|
7065 file will move to ~/.xemacs/custom.el.)
|
|
|
7066 @item
|
|
|
7067 Much-improved sample init.el, showing how to use many useful features.
|
|
|
7068 @item
|
|
|
7069 XEmacs support for menu accelerators has been much improved.
|
|
|
7070 @item
|
|
|
7071 Default menubar improvements. (Default menubar has many new commands and
|
|
|
7072 better organization. The font-menu is now available under MS Windows.)
|
|
|
7073 @item
|
|
2417
|
7074 Dialog box improvements, including a real file dialog box. (XEmacs now
|
|
|
7075 has a proper file dialog box under MS Windows (and GTK)! The old
|
|
|
7076 clunky file dialog box is improved. Keyboard traversal now works
|
|
|
7077 correctly in MS Windows dialog boxes. There is a Search dialog box
|
|
|
7078 available from @samp{Edit->Find...})
|
|
611
|
7079 @item
|
|
|
7080 New buffer tabs.
|
|
|
7081 @item
|
|
|
7082 There is a new MS Windows installer, netinstall, ported from Cygwin.
|
|
|
7083 @item
|
|
|
7084 The subprocess quote-handling mechanism under Windows is much improved.
|
|
|
7085 @item
|
|
|
7086 Printing support now available under MS Windows.
|
|
|
7087 @item
|
|
|
7088 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).)
|
|
|
7089 @item
|
|
|
7090 Mail spool locking now works correctly.
|
|
|
7091 @item
|
|
|
7092 International support changes. (The default coding-priority-list is now
|
|
|
7093 safer. International keysyms are now supported under X. MS Windows
|
|
|
7094 1251 code page now supported. Czech, Thai, Cyrillic-KOI8, Vietnamese,
|
|
|
7095 Ethiopic now supported. Proper support for words in Latin 3 and Latin
|
|
|
7096 4.)
|
|
|
7097 @item
|
|
|
7098 Help buffers contain hyperlinks, and other changes.
|
|
|
7099 @item
|
|
|
7100 The modeline's text is now scrollable.
|
|
|
7101 @item
|
|
|
7102 The mouse wheel under MS Windows now functions correctly.
|
|
|
7103 @item
|
|
|
7104 Interactive searching and matching case improvements. (Incremental search will now highlight all visible matches. Interactive searches always respect uppercase characters.)
|
|
|
7105 @item
|
|
|
7106 Rectangle functions rewritten to avoid inserting extra spaces.
|
|
|
7107 @item
|
|
|
7108 New command `kill-entire-line' that always kills the entire line.
|
|
|
7109 @item
|
|
|
7110 Default values correctly stored in minibuffer histories.
|
|
|
7111 @item
|
|
|
7112 You can now create "indirect buffers", like in GNU Emacs.
|
|
|
7113 @item
|
|
|
7114 Pixel-based scrolling has been implemented.
|
|
|
7115 @item
|
|
|
7116 Operation progress can be displayed using graphical widgets.
|
|
|
7117 @item
|
|
|
7118 User names following a tilde can now be completed at file name prompts.
|
|
|
7119 @item
|
|
|
7120 XEmacs can now play sound using Enlightenment Sound Daemon (ESD).
|
|
|
7121 @item
|
|
|
7122 X-Face support is now available under MS Windows.
|
|
|
7123 @item
|
|
|
7124 The PostgreSQL Relational Database Management System is now supported.
|
|
|
7125 @item
|
|
|
7126 Indentation no longer indents comments that begin at column zero.
|
|
|
7127 @item
|
|
|
7128 Face and variable settings can have comments in Customize.
|
|
|
7129 @item
|
|
|
7130 New locations for early package hierarchies.
|
|
|
7131 @item
|
|
|
7132 The `auto-save' library has been greatly improved.
|
|
|
7133 @item
|
|
|
7134 New variable `mswindows-alt-by-itself-activates-menu'.
|
|
|
7135 @item
|
|
|
7136 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.)
|
|
|
7137 @item
|
|
|
7138 Etags changes. See @file{NEWS} for full details.
|
|
|
7139 @end itemize
|
|
|
7140
|
|
676
|
7141 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.4
|
|
611
|
7142
|
|
|
7143 Not yet written.
|
|
|
7144
|
|
661
|
7145 @c APA: Texi2html produces invalid HTML from an empty list of bullets!
|
|
|
7146 @c Please uncomment following list when it does contain bullets.
|
|
|
7147 @c @itemize @bullet
|
|
|
7148 @c @end itemize
|
|
611
|
7149
|
|
2459
|
7150 @node Q9.0.3, Q9.0.4, Q9.0.2, Current Events
|
|
|
7151 @unnumberedsubsec Q9.0.3: What's new in XEmacs 21.1?
|
|
611
|
7152
|
|
|
7153 21.1 was the "stable" version of "experimental" 21.0 series.
|
|
2459
|
7154 @xref{Q9.0.2, What's new in XEmacs 21.4?}.
|
|
611
|
7155
|
|
|
7156 The following lists summarizes the essential changes made in this
|
|
|
7157 version. For a fuller list, see the @file{NEWS} in the @file{etc}
|
|
|
7158 directory of the XEmacs distribution, or use @kbd{C-h n} or the
|
|
|
7159 @samp{Help} menu to view this file inside of XEmacs.
|
|
|
7160
|
|
676
|
7161 @unnumberedsubsubsec User-visible changes in XEmacs 21.1
|
|
611
|
7162
|
|
|
7163 @itemize @bullet
|
|
|
7164
|
|
|
7165 @item
|
|
2459
|
7166 XEmacs is now supported under Microsoft Windows 95/98 and Windows
|
|
2417
|
7167 NT/2000/XP operating systems. To discuss Windows-specific issues,
|
|
|
7168 subscribe to the mailing list at
|
|
|
7169 @email{xemacs-winnt-request@@xemacs.org}.
|
|
611
|
7170
|
|
|
7171 @item
|
|
|
7172 XEmacs has been unbundled into constituent installable packages.
|
|
|
7173
|
|
|
7174 @item
|
|
|
7175 @strong{Other notable changes}: The @samp{Options} menu has been ported to
|
|
|
7176 Custom; XEmacs now is able to choose X visuals and use private
|
|
|
7177 colormaps; You can drag the vertical divider of "horizontally"
|
|
|
7178 (side-by-side) split windows.
|
|
|
7179
|
|
|
7180 @item
|
|
|
7181 @strong{Building changes}: XEmacs can be built with support for 31-bit Lisp
|
|
|
7182 integers and 32-bit pointers (previously, it was 28-bit integers and
|
|
|
7183 pointers); XEmacs can be built with LDAP support; @file{dir} files can be
|
|
|
7184 removed in the Info subsystem, and will be regenerated on-the-fly.
|
|
|
7185
|
|
|
7186 @item
|
|
|
7187 @strong{New packages}: @file{imenu}, @file{popper}, @file{gdb-highlight}
|
|
|
7188
|
|
|
7189 @item
|
|
|
7190 @strong{Package changes}: Many changes to @file{cc-mode}, @file{gnus},
|
|
|
7191 @file{gnuclient}. See @file{NEWS} for full details.
|
|
|
7192
|
|
|
7193 @item
|
|
|
7194 @strong{New commands, variables and functions}:
|
|
|
7195 @code{center-to-window-line} (like @code{recenter} but doesn't force a
|
|
|
7196 redisplay); variable @code{user-full-name} (customize what your full
|
|
|
7197 name looks like in mail); @kbd{M-x customize-changed-options} (customize
|
|
|
7198 options whose default values changes because you upgraded your XEmacs);
|
|
|
7199 @kbd{M-x add-log-convert} (converts an old-style ChangeLog buffer to
|
|
|
7200 new-style); @kbd{M-x zap-up-to-char} (like @code{zap-to-char} but
|
|
|
7201 doesn't delete the char searched for); commands to store, retrieve and
|
|
|
7202 increment numbers in registers, useful for macros.
|
|
|
7203
|
|
|
7204 @item
|
|
|
7205 @strong{Changes to commands, variables, and functions}: @kbd{M-x
|
|
|
7206 query-replace} and friends operate only on the region when it's active;
|
|
|
7207 @code{echo-keystrokes} can now be a floating-point number; @kbd{M-.}
|
|
|
7208 searches exact tag matches before inexact ones; function
|
|
|
7209 @code{user-full-name} with no arguments returns the var
|
|
|
7210 @code{user-full-name}; a prefix arg to @kbd{M-:} and @kbd{C-h c} inserts
|
|
|
7211 the result in the current buffer.
|
|
1138
|
7212
|
|
611
|
7213 @item
|
|
|
7214 @strong{Other changes}: Under X, new application class @samp{XEmacs};
|
|
|
7215 byte-compilation of user-specs now works.
|
|
|
7216
|
|
|
7217 @item
|
|
|
7218 @strong{XEmacs/Mule (internationalization) changes}: Mule support now
|
|
|
7219 works on TTY's; Egg/SJ3 input method now officially supported (Quail and
|
|
|
7220 Egg/Skk already available through LEIM since 20.3); localized Japanese
|
|
|
7221 menubars if XEmacs is built with the right support.
|
|
|
7222
|
|
|
7223 @end itemize
|
|
|
7224
|
|
676
|
7225 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.1
|
|
611
|
7226
|
|
|
7227 @itemize @bullet
|
|
|
7228
|
|
|
7229 @item
|
|
|
7230 @strong{Specifier changes}: The window locale now has a higher
|
|
|
7231 precedence than the buffer locale when instantiating; new macro
|
|
|
7232 @code{let-specifier}; new specifiers
|
|
|
7233 @code{vertical-scrollbar-visible-p}, horizontal-scrollbar-visible-p',
|
|
|
7234 @code{scrollbar-on-left-p}, @code{scrollbar-on-top-p},
|
|
|
7235 @code{vertical-divider-always-visible-p},
|
|
|
7236 @code{vertical-divider-shadow-thickness},
|
|
|
7237 @code{vertical-divider-line-width}, @code{vertical-divider-spacing};
|
|
|
7238 specifiers and symbols whose value is a specifier allowed as modeline
|
|
|
7239 specifications.
|
|
|
7240
|
|
|
7241 @item
|
|
|
7242 @strong{Frame focus changes}: @code{focus-follows-mouse} works like FSF,
|
|
|
7243 prevents any attempt to permanently change the selected frame; new
|
|
|
7244 function @code{focus-frame} sets the window system focus a frame; new
|
|
|
7245 special forms @code{save-selected-frame} and @code{with-selected-frame}.
|
|
|
7246
|
|
|
7247 @item
|
|
|
7248 @strong{Window function changes}: @code{select-window} now has optional
|
|
|
7249 argument @var{NORECORD} to inhibit recording a buffer change;
|
|
|
7250 @code{vertical-motion} now correctly handles optional @var{WINDOW}
|
|
|
7251 argument and has new optional argument @var{PIXELS}, to have the
|
|
|
7252 returned values be in pixels; new function
|
|
|
7253 @code{vertical-motion-pixels}; new functions
|
|
|
7254 @code{window-text-area-pixel-@{width,height,edges@}}; new functions
|
|
|
7255 @code{shrink-window-pixels} and @code{enlarge-window-pixels}; new
|
|
|
7256 function @code{window-displayed-text-pixel-height}.
|
|
|
7257
|
|
|
7258 @item
|
|
|
7259 @strong{Other function changes}: Arithmetic comparison functions
|
|
|
7260 @code{<}, @code{>}, @code{=}, @code{/=} now accept a variable number of
|
|
|
7261 arguments; hashtables now have a consistent read/print syntax; keyword
|
|
|
7262 symbols cannot be set to a value other than themselves; @code{concat} no
|
|
|
7263 longer accepts integer arguments; new function @code{string}, like
|
|
|
7264 @code{list}, @code{vector}, etc.; new function @code{temp-directory}
|
|
|
7265 (OS-independent way to get a temp directory); @code{load-average} has
|
|
|
7266 optional argument @var{USE-FLOATS}; @code{make-event} implemented
|
|
|
7267 completely; new function @code{function-interactive} (returns a
|
|
|
7268 function's interactive spec); new functions @code{lmessage},
|
|
|
7269 @code{lwarn} (printf-like versions of @code{display-wessage},
|
|
|
7270 @code{display-warning}); new keyword @code{:version} to
|
|
|
7271 @code{defcustom}.
|
|
|
7272
|
|
|
7273 @item
|
|
|
7274 @strong{Performance}: when the new GNU Malloc aka Doug Lea Malloc is
|
|
|
7275 available, it will be used (better performance on libc6 Linux systems);
|
|
|
7276 tracking line-numbers in modeline is now efficient; profiling records a
|
|
|
7277 call-count of all called functions, retrievable through
|
|
|
7278 @code{profile-call-count-results}.
|
|
|
7279
|
|
|
7280 @item
|
|
|
7281 @strong{Startup and path searching}: code to assemble paths at startup
|
|
|
7282 rewritten for new package system; new function @code{split-path} (splits
|
|
|
7283 by @code{path-separator}); @code{Info-default-directory-list} obsolete,
|
|
|
7284 use @code{Info-directory-list} instead; site-lisp is deprecated and no
|
|
|
7285 longer on the load-path by default.
|
|
|
7286
|
|
|
7287 @end itemize
|
|
|
7288
|
|
2459
|
7289 @node Q9.0.4, Q9.0.5, Q9.0.3, Current Events
|
|
|
7290 @unnumberedsubsec Q9.0.4: What's new in XEmacs 20.4?
|
|
611
|
7291
|
|
|
7292 XEmacs 20.4 is a bugfix release with no user-visible changes.
|
|
|
7293 @c Filled in from NEWS file of 20.5-b33
|
|
|
7294
|
|
2459
|
7295 @node Q9.0.5, Q9.0.6, Q9.0.4, Current Events
|
|
|
7296 @unnumberedsubsec Q9.0.5: What's new in XEmacs 20.3?
|
|
428
|
7297
|
|
|
7298 XEmacs 20.3 was released in November 1997. It contains many bugfixes,
|
|
|
7299 and a number of new features, including Autoconf 2 based configuration,
|
|
|
7300 additional support for Mule (Multi-language extensions to Emacs), many
|
|
|
7301 more customizations, multiple frames on TTY-s, support for multiple info
|
|
|
7302 directories, an enhanced gnuclient, improvements to regexp matching,
|
|
|
7303 increased MIME support, and many, many synches with GNU Emacs 20.
|
|
|
7304
|
|
|
7305 The XEmacs/Mule support has been only seriously tested in a Japanese
|
|
|
7306 locale, and no doubt many problems still remain. The support for
|
|
|
7307 ISO-Latin-1 and Japanese is fairly strong. MULE support comes at a
|
|
440
|
7308 price---about a 30% slowdown from 19.16. We're making progress on
|
|
428
|
7309 improving performance and XEmacs 20.3 compiled without Mule (which is
|
|
|
7310 the default) is definitely faster than XEmacs 19.16.
|
|
|
7311
|
|
|
7312 XEmacs 20.3 is the first non-beta v20 release, and will be the
|
|
|
7313 basis for all further development.
|
|
|
7314
|
|
2459
|
7315 @node Q9.0.6, , Q9.0.5, Current Events
|
|
|
7316 @unnumberedsubsec Q9.0.6: What's new in XEmacs 20.2?
|
|
611
|
7317
|
|
|
7318 The biggest changes in 20.2 include integration of EFS (the next
|
|
|
7319 generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a
|
|
|
7320 major mode for editing Tex and LaTeX, and a lot of other stuff). Many
|
|
|
7321 bugs from 20.0 have been fixed for this release. 20.2 also contains a
|
|
|
7322 new system for customizing XEmacs options, invoked via @kbd{M-x
|
|
|
7323 customize}.
|
|
|
7324
|
|
|
7325 XEmacs 20.2 is the development release (20.0 was beta), and is no longer
|
|
|
7326 considered unstable.
|
|
|
7327
|
|
|
7328 For older news, see the file @file{ONEWS} in the @file{etc} directory of
|
|
|
7329 the XEmacs distribution.
|
|
428
|
7330
|
|
2417
|
7331 @node Legacy Versions, , Current Events, Top
|
|
2459
|
7332 @unnumbered 10 New information about old XEmacsen
|
|
|
7333
|
|
|
7334 This is part 10 of the XEmacs Frequently Asked Questions list. It will
|
|
1495
|
7335 occasionally be updated to reflect new information about versions which
|
|
|
7336 are no longer being revised by the XEmacs Project. The primary purpose
|
|
|
7337 is advice on compatibility of older XEmacsen with new packages and
|
|
|
7338 updated versions of packages, but bug fixes (which will not be applied
|
|
|
7339 to released XEmacsen, but users can apply themselves) are also accepted.
|
|
|
7340
|
|
|
7341 @menu
|
|
2459
|
7342 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
1495
|
7343 @end menu
|
|
|
7344
|
|
2459
|
7345 @unnumberedsec 10.0: XEmacs 21.1
|
|
|
7346
|
|
|
7347 @node Q10.0.1, , Legacy Versions, Legacy Versions
|
|
|
7348 @unnumberedsubsec Q10.0.1: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
1495
|
7349
|
|
|
7350 @email{eeide@@cs.utah.edu, Eric Eide} wrote:
|
|
|
7351
|
|
|
7352 @quotation
|
|
|
7353 Previously I wrote:
|
|
|
7354
|
|
|
7355 Eric> Summary: with Gnus 5.10.1 in XEmacs 21.1.14, I don't see
|
|
|
7356 Eric> any smileys :-(.
|
|
|
7357
|
|
|
7358 After a bit of sleuthing, I discovered the essence of the problem.
|
|
|
7359 For me, the form:
|
|
|
7360
|
|
|
7361 @lisp
|
|
|
7362 (with-temp-buffer
|
|
|
7363 (insert-file-contents "foo.xpm")
|
|
|
7364 (buffer-string))
|
|
|
7365 @end lisp
|
|
|
7366
|
|
|
7367 returns the empty string. This is because something somewhere
|
|
|
7368 replaces the XPM data with a glyph --- I haven't figured out where
|
|
|
7369 this occurs.
|
|
|
7370 @end quotation
|
|
|
7371
|
|
|
7372 @email{kyle_jones@@wonderworks.com, Kyle Jones} replies:
|
|
|
7373
|
|
|
7374 @quotation
|
|
|
7375 Do this:
|
|
|
7376
|
|
|
7377 @lisp
|
|
|
7378 (setq format-alist nil)
|
|
|
7379 @end lisp
|
|
|
7380
|
|
|
7381 The image-mode stuff is gone from format-alist in the 21.4
|
|
|
7382 branch, praise be.
|
|
|
7383 @end quotation
|
|
|
7384
|
|
428
|
7385 @bye
|
