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