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