|
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
|
|
3404
|
10 @subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2006/05/16 15:36:16 $
|
|
428
|
11 @sp 1
|
|
2417
|
12 @author Ben Wing <ben@@xemacs.org>
|
|
1869
|
13 @author Tony Rossini <rossini@@u.washington.edu>
|
|
428
|
14 @author Chuck Thompson <cthomp@@xemacs.org>
|
|
|
15 @author Steve Baur <steve@@xemacs.org>
|
|
|
16 @author Andreas Kaempf <andreas@@sccon.com>
|
|
|
17 @author Christian Nyb@o{} <chr@@mediascience.no>
|
|
434
|
18 @author Sandra Wambold <wambold@@xemacs.org>
|
|
428
|
19 @page
|
|
|
20 @end titlepage
|
|
|
21
|
|
|
22 @ifinfo
|
|
|
23 @dircategory XEmacs Editor
|
|
|
24 @direntry
|
|
440
|
25 * FAQ: (xemacs-faq). XEmacs FAQ.
|
|
428
|
26 @end direntry
|
|
|
27 @end ifinfo
|
|
|
28
|
|
2417
|
29 @ignore
|
|
|
30 *****************************************
|
|
|
31 ***** To update the menus and nodes *****
|
|
|
32 *****************************************
|
|
|
33
|
|
|
34 First, the first argument to @node (the name itself) needs to be correct.
|
|
|
35 Use a macro if necessary to update the @node names from the
|
|
|
36 @unnumberedsubsec commands. Also note that the command we're about to
|
|
|
37 run will not correctly fix up the part of the menu to the right of a ::.
|
|
|
38 It will leave existing text in place but not change anything. If you
|
|
|
39 make a lot of changes and want to update this semi-automatically, use
|
|
|
40 M-x occur to pick out all @unnumberedsubsec lines then do some editing
|
|
|
41 magic to coerce them into the right format and cut and paste as necessary:
|
|
|
42
|
|
|
43 1. M-x occur @unnumberedsubsec
|
|
|
44 2. <select a rectangle including all text before the Q#.#.#>
|
|
|
45 3. C-x r t *<space>
|
|
|
46 4. go to the top and use the following macro to get the indentation right.
|
|
|
47
|
|
|
48 (setq last-kbd-macro (read-kbd-macro
|
|
|
49 "C-s : RET : <right> M-x indent- to- column RET 14 RET <home> <down>"))
|
|
|
50
|
|
|
51 5. Cut and paste the menus into the detailmenu at the top and
|
|
|
52 individual menus at the top of the appropriate chapters. (#### I
|
|
|
53 wonder, does texinfo-master-menu generate the detailmenu from the
|
|
|
54 individual menus or vice-versa or neither?)
|
|
|
55
|
|
|
56 Then,
|
|
|
57
|
|
2559
|
58 6. C-u C-c C-u m (C-u M-x texinfo-master-menu) will update the menus
|
|
2417
|
59 and nodes. However, it appears that even though it tries to
|
|
|
60 preserve the existing menu structure as much as possible, it
|
|
|
61 doesn't do a perfect job. It messes up in at least two ways: The
|
|
|
62 indentation in the part of the main menu above the detailmenu will
|
|
|
63 be screwed up, and the #.0 titles will be removed from both the
|
|
|
64 detailmenu and the individual chapter menus. In addition,
|
|
|
65 sometimes random things get screwed up in individual parts of the
|
|
|
66 menus. Therefore:
|
|
|
67
|
|
2559
|
68 1. Use the Lisp line below to get the spacing correct for the Q#.#.#
|
|
|
69 menu entries.
|
|
|
70
|
|
|
71 (set (make-local-variable 'texinfo-column-for-description) 14)
|
|
|
72
|
|
|
73 2. Copy the whole detailmenu beforehand.
|
|
|
74 3. Run C-u C-c C-u m to fix up the nodes.
|
|
|
75 4. Run `fix-main-menu' and `fix-omitted-menu-lines'.
|
|
|
76 5. Check the new detailmenu carefully to see if anything is screwed up
|
|
2417
|
77 compared to the old detailmenu you copied.
|
|
2559
|
78 6. If so, paste back the appropriate sections and fix up the corresponding
|
|
2417
|
79 part of the chapter-specific menu.
|
|
|
80
|
|
|
81 (defun fix-main-menu ()
|
|
|
82 (interactive)
|
|
|
83 (save-restriction
|
|
|
84 (let (p q)
|
|
2559
|
85 (goto-char (point-min))
|
|
|
86 (re-search-forward "^@menu")
|
|
2417
|
87 (setq p (match-beginning 0))
|
|
|
88 (re-search-forward "^$")
|
|
|
89 (setq q (match-end 0))
|
|
|
90 (narrow-to-region p q)
|
|
|
91 (goto-char p)
|
|
|
92 (while (search-forward ":: " nil t)
|
|
|
93 (indent-to-column 26)))))
|
|
|
94
|
|
|
95 (defun fix-omitted-menu-lines ()
|
|
|
96 (interactive)
|
|
|
97 (save-excursion
|
|
2559
|
98 (loop for x from 1 to 10 do
|
|
2417
|
99 (goto-char (point-min))
|
|
|
100 (re-search-forward (format "@unnumberedsec \\(%d.0: .*\\)" x))
|
|
|
101 (let ((line (match-string 1)))
|
|
2559
|
102 (re-search-backward "^@menu")
|
|
2417
|
103 (forward-line 1)
|
|
2559
|
104 (unless (looking-at "[0-9]+.0:")
|
|
2417
|
105 (insert line)
|
|
|
106 (insert "\n"))
|
|
|
107 (goto-char (point-min))
|
|
2559
|
108 (re-search-forward "^@menu")
|
|
2417
|
109 (search-forward (format "Q%d.0.1:" x))
|
|
|
110 (forward-line -1)
|
|
2559
|
111 (unless (looking-at "[0-9]+.0:")
|
|
|
112 (insert "\n")
|
|
|
113 (insert line))))))
|
|
2417
|
114
|
|
|
115 *****************************************
|
|
|
116 ***** Other work *****
|
|
|
117 *****************************************
|
|
|
118
|
|
|
119 When you've rearranged and renumbered a bunch of nodes, you can get
|
|
|
120 the numbers agreeing again. The macro below assumes that the
|
|
|
121 unnumberedsubsec number is correct, and fixes up the node to agree.
|
|
|
122 Only the first part of the node is fixed and the other parts may still
|
|
|
123 be wrong; but they will be fixed as part of
|
|
|
124 @code{texinfo-master-menu}.
|
|
|
125
|
|
|
126 (setq last-kbd-macro (read-kbd-macro
|
|
|
127 "<f1> unnumberedsubsec SPC RET C-s : RET <left> C-x C-x <f3> <home> <up> <C-right> <right> C-s , RET <left> C-x C-x <f4> <home> 2*<down>"))
|
|
|
128 @end ignore
|
|
|
129
|
|
|
130
|
|
428
|
131 @node Top, Introduction, (dir), (dir)
|
|
|
132 @top XEmacs FAQ
|
|
|
133
|
|
|
134 This is the guide to the XEmacs Frequently Asked Questions list---a
|
|
|
135 compendium of questions and answers pertaining to one of the finest
|
|
442
|
136 programs ever written. XEmacs is much more than just a Text Editor.
|
|
|
137
|
|
|
138 This FAQ is freely redistributable. This FAQ is distributed in the hope
|
|
|
139 that it will be useful, but WITHOUT ANY WARRANTY; without even the
|
|
|
140 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
|
428
|
141
|
|
|
142 If you have a Web browser, the official hypertext version is at
|
|
|
143 @iftex
|
|
|
144 @*
|
|
|
145 @end iftex
|
|
1143
|
146 @uref{http://www.xemacs.org/FAQ/xemacs-faq.html}
|
|
428
|
147
|
|
|
148 @ifset CANONICAL
|
|
|
149 @html
|
|
|
150 This document is available in several different formats:
|
|
|
151 @itemize @bullet
|
|
|
152 @item
|
|
|
153 @uref{xemacs-faq.txt, As a single ASCII file}, produced by
|
|
|
154 @code{makeinfo --no-headers}
|
|
|
155 @item
|
|
|
156 @uref{xemacs-faq.dvi, As a .dvi file}, as used with
|
|
|
157 @uref{http://www.tug.org, TeX.}
|
|
|
158 @item
|
|
|
159 As a PostScript file @uref{xemacs-faq-a4.ps, in A4 format},
|
|
|
160 as well as in @uref{xemacs-faq-letter.ps, letter format}
|
|
|
161 @item
|
|
|
162 In html format, @uref{xemacs-faq_1.html, split by chapter}, or in
|
|
|
163 @uref{xemacs-faq.html, one monolithic} document.
|
|
|
164 @item
|
|
|
165 The canonical version of the FAQ is the texinfo document
|
|
|
166 @uref{xemacs-faq.texi, man/xemacs-faq.texi}.
|
|
|
167 @item
|
|
|
168 If you do not have makeinfo installed, you may @uref{xemacs-faq.info,
|
|
|
169 download the faq} in info format, and install it in @file{<XEmacs
|
|
|
170 library directory>/info/}. For example in
|
|
462
|
171 @file{/usr/local/lib/xemacs-21.4/info/}.
|
|
428
|
172
|
|
|
173 @end itemize
|
|
|
174
|
|
|
175 @end html
|
|
|
176
|
|
|
177 @end ifset
|
|
|
178
|
|
|
179 @c end ifset points to CANONICAL
|
|
|
180
|
|
|
181 @menu
|
|
2417
|
182 * Introduction:: Introduction, Policy, Credits.
|
|
|
183 * Installation:: Installation and Troubleshooting.
|
|
2459
|
184 * Editing:: Editing Functions.
|
|
|
185 * Display:: Display Functions.
|
|
2417
|
186 * External Subsystems:: Interfacing with the OS and External Devices.
|
|
|
187 * Internet:: Connecting to the Internet.
|
|
|
188 * Advanced:: Advanced Customization Using XEmacs Lisp.
|
|
2459
|
189 * Other Packages:: Other External Packages.
|
|
2417
|
190 * Current Events:: What the Future Holds.
|
|
|
191 * Legacy Versions:: New information about old XEmacsen.
|
|
428
|
192
|
|
|
193 @detailmenu
|
|
|
194 --- The Detailed Node Listing ---
|
|
|
195
|
|
2417
|
196 1 Introduction, Policy, Credits
|
|
|
197
|
|
2537
|
198 1.0: What is XEmacs?
|
|
2417
|
199 * Q1.0.1:: What is XEmacs?
|
|
|
200 * Q1.0.2:: What is the current version of XEmacs?
|
|
2537
|
201 * Q1.0.3:: How do you pronounce XEmacs?
|
|
|
202 * Q1.0.4:: What does XEmacs look like?
|
|
|
203 * Q1.0.5:: Who wrote XEmacs?
|
|
|
204 * Q1.0.6:: Who wrote the FAQ?
|
|
|
205
|
|
|
206 1.1: Getting XEmacs
|
|
|
207 * Q1.1.1:: Where can I find XEmacs?
|
|
|
208 * Q1.1.2:: Are binaries available?
|
|
|
209 * Q1.1.3:: How do I get the bleeding-edge sources?
|
|
|
210 * Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual?
|
|
|
211
|
|
|
212 1.2: Versions for Different Operating Systems
|
|
|
213 * Q1.2.1:: Do I need X11 to run XEmacs?
|
|
|
214 * Q1.2.2:: What versions of Unix does XEmacs run on?
|
|
|
215 * Q1.2.3:: Is there a port of XEmacs to Microsoft Windows?
|
|
|
216 * Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
217 * Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
218 * Q1.2.6:: What are the differences between the various MS Windows emacsen?
|
|
|
219 * Q1.2.7:: How does the port cope with differences in the Windows user interface?
|
|
|
220 * Q1.2.8:: Is there a port of XEmacs to the Macintosh?
|
|
|
221 * Q1.2.9:: Is there a port of XEmacs to MS-DOS?
|
|
|
222 * Q1.2.10:: Is there a port of XEmacs to OS/2?
|
|
|
223 * Q1.2.11:: Is there a port of XEmacs to NextStep?
|
|
|
224 * Q1.2.12:: Is there a port of XEmacs to VMS?
|
|
|
225
|
|
|
226 1.3: Getting Started
|
|
|
227 * Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
|
228 * Q1.3.2:: Where do I put my @file{init.el} file?
|
|
|
229 * Q1.3.3:: Can I use the same @file{init.el} with the other Emacs?
|
|
|
230 * Q1.3.4:: Any good XEmacs tutorials around?
|
|
|
231 * Q1.3.5:: May I see an example of a useful XEmacs Lisp function?
|
|
|
232 * Q1.3.6:: And how do I bind it to a key?
|
|
|
233 * Q1.3.7:: What's the difference between a macro and a function?
|
|
|
234 * Q1.3.8:: What is @code{Custom}?
|
|
|
235
|
|
|
236 1.4: Getting Help
|
|
|
237 * Q1.4.1:: Where can I get help?
|
|
|
238 * Q1.4.2:: Which mailing lists are there?
|
|
2559
|
239 * Q1.4.3:: Where are the mailing lists archived?
|
|
|
240 * Q1.4.4:: How can I get two instances of info?
|
|
|
241 * Q1.4.5:: How do I add new Info directories?
|
|
2537
|
242
|
|
|
243 1.5: Contributing to XEmacs
|
|
|
244 * Q1.5.1:: How do I submit changes to the FAQ?
|
|
|
245 * Q1.5.2:: How do I become a beta tester?
|
|
|
246 * Q1.5.3:: How do I contribute to XEmacs itself?
|
|
2559
|
247 * Q1.5.4:: How do I get started developing XEmacs?
|
|
|
248 * Q1.5.5:: What's the basic layout of the code?
|
|
2537
|
249
|
|
|
250 1.6: Politics (XEmacs vs. GNU Emacs)
|
|
|
251 * Q1.6.1:: What is GNU Emacs?
|
|
|
252 * Q1.6.2:: How does XEmacs differ from GNU Emacs?
|
|
|
253 * Q1.6.3:: How much does XEmacs differ?
|
|
|
254 * Q1.6.4:: Is XEmacs "GNU"?
|
|
|
255 * Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
|
256 * Q1.6.6:: Why haven't XEmacs and GNU Emacs merged?
|
|
|
257
|
|
|
258 1.7: External Packages
|
|
2559
|
259 * Q1.7.1:: What is the package system?
|
|
|
260 * Q1.7.2:: Which external packages are there?
|
|
|
261 * Q1.7.3:: Do I need to have the packages to run XEmacs?
|
|
|
262 * Q1.7.4:: Is there a way to find which package has particular functionality?
|
|
2537
|
263
|
|
|
264 1.8: Internationalization
|
|
|
265 * Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
|
266 * Q1.8.2:: How can I help with internationalization?
|
|
|
267 * Q1.8.3:: How do I type non-ASCII characters?
|
|
|
268 * Q1.8.4:: Can XEmacs messages come out in a different language?
|
|
|
269 * Q1.8.5:: Please explain the various input methods in MULE/XEmacs
|
|
|
270 * Q1.8.6:: How do I portably code for MULE/XEmacs?
|
|
|
271 * Q1.8.7:: How about Cyrillic modes?
|
|
|
272 * Q1.8.8:: Does XEmacs support Unicode?
|
|
|
273 * Q1.8.9:: How does XEmacs display Unicode?
|
|
2417
|
274
|
|
|
275 2 Installation and Troubleshooting
|
|
|
276
|
|
2559
|
277 2.0: Installation (General)
|
|
|
278 * Q2.0.1:: How do I build and install XEmacs?
|
|
|
279 * Q2.0.2:: Where do I find external libraries?
|
|
|
280 * Q2.0.3:: How do I specify the paths that XEmacs uses for finding files?
|
|
|
281 * Q2.0.4:: Running XEmacs without installing
|
|
|
282 * Q2.0.5:: XEmacs is too big
|
|
|
283
|
|
|
284 2.1: Package Installation
|
|
|
285 * Q2.1.1:: How do I install the packages?
|
|
|
286 * Q2.1.2:: Can I install the packages individually?
|
|
|
287 * Q2.1.3:: Can I install the packages automatically?
|
|
|
288 * Q2.1.4:: Can I upgrade or remove packages?
|
|
|
289 * Q2.1.5:: Which packages to install?
|
|
|
290 * Q2.1.6:: Can you describe the package location process in more detail?
|
|
|
291 * Q2.1.7:: EFS fails with "500 AUTH not understood"
|
|
|
292
|
|
|
293 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
|
294 * Q2.2.1:: Libraries in non-standard locations
|
|
|
295 * Q2.2.2:: Why can't I strip XEmacs?
|
|
3404
|
296 * Q2.2.3:: X11/bitmaps/gray (or other X11-related file) not found.
|
|
2559
|
297
|
|
|
298 2.3: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
299 * Q2.3.1:: What exactly are all the different ways to build XEmacs under Windows?
|
|
|
300 * Q2.3.2:: What compiler/libraries do I need to compile XEmacs?
|
|
|
301 * Q2.3.3:: How do I compile the native port?
|
|
|
302 * Q2.3.4:: What do I need for Cygwin?
|
|
|
303 * Q2.3.5:: How do I compile under Cygwin?
|
|
|
304 * Q2.3.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
|
305 * Q2.3.7:: How do I compile with X support?
|
|
|
306 * Q2.3.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
|
307
|
|
|
308 2.4: General Troubleshooting
|
|
|
309 * Q2.4.1:: How do I deal with bugs or with problems building, installing, or running?
|
|
|
310 * Q2.4.2:: Help! XEmacs just crashed on me!
|
|
|
311 * Q2.4.3:: XEmacs crashes and I compiled it myself.
|
|
|
312 * Q2.4.4:: How to debug an XEmacs problem with a debugger
|
|
|
313 * Q2.4.5:: I get a cryptic error message when trying to do something.
|
|
|
314 * Q2.4.6:: XEmacs hangs when I try to do something.
|
|
|
315 * Q2.4.7:: I get an error message when XEmacs is running in batch mode.
|
|
|
316 * Q2.4.8:: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
|
317 * Q2.4.9:: @kbd{C-g} doesn't work for me. Is it broken?
|
|
|
318 * Q2.4.10:: How do I debug process-related problems?
|
|
|
319 * Q2.4.11:: XEmacs is outputting lots of X errors.
|
|
|
320 * Q2.4.12:: After upgrading, XEmacs won't do `foo' any more!
|
|
|
321
|
|
|
322 2.5: Startup-Related Problems
|
|
|
323 * Q2.5.1:: XEmacs cannot connect to my X Terminal!
|
|
|
324 * Q2.5.2:: Startup problems related to paths or package locations.
|
|
|
325 * Q2.5.3:: XEmacs won't start without network.
|
|
|
326 * Q2.5.4:: Startup warnings about deducing proper fonts?
|
|
|
327 * Q2.5.5:: Warnings from incorrect key modifiers.
|
|
|
328 * Q2.5.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
2417
|
329
|
|
2459
|
330 3 Editing Functions
|
|
2417
|
331
|
|
|
332 3.0: The Keyboard
|
|
2459
|
333 * Q3.0.1:: How can I customize the keyboard?
|
|
|
334 * Q3.0.2:: How can I bind complex functions (or macros) to keys?
|
|
|
335 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down?
|
|
|
336 * Q3.0.4:: Globally binding @kbd{Delete}?
|
|
|
337 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
|
338 * Q3.0.6:: How can you type in special characters in XEmacs?
|
|
|
339 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys?
|
|
|
340 * Q3.0.8:: How do I map the arrow keys?
|
|
|
341 * Q3.0.9:: HP Alt key as Meta.
|
|
|
342 * Q3.0.10:: Why does edt emulation not work?
|
|
|
343 * Q3.0.11:: How can I emulate VI and use it as my default mode?
|
|
2417
|
344
|
|
|
345 3.1: The Mouse
|
|
|
346 * Q3.1.1:: How can I turn off Mouse pasting?
|
|
|
347 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons?
|
|
|
348 * Q3.1.3:: Clicking the left button does not do anything in buffer list.
|
|
|
349 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3?
|
|
2459
|
350 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
|
351
|
|
|
352 3.2: Buffers, Text Editing
|
|
|
353 * Q3.2.1:: Can I have the end of the buffer delimited in some way?
|
|
|
354 * Q3.2.2:: How do I insert today's date into a buffer?
|
|
|
355 * Q3.2.3:: How do I get a single minibuffer frame?
|
|
|
356 * Q3.2.4:: How can I enable auto-indent and/or Filladapt?
|
|
|
357 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
358
|
|
|
359 3.3: Text Selections
|
|
|
360 * Q3.3.1:: How do I select a rectangular region?
|
|
|
361 * Q3.3.2:: How can I turn off or change highlighted selections?
|
|
|
362 * Q3.3.3:: How do I cause typing on an active region to remove it?
|
|
|
363 * Q3.3.4:: Can I turn off the highlight during isearch?
|
|
|
364 * Q3.3.5:: Why is killing so slow?
|
|
|
365 * Q3.3.6:: Why does @kbd{M-w} take so long?
|
|
|
366
|
|
|
367 3.4: Editing Source Code
|
|
|
368 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode?
|
|
|
369 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly?
|
|
|
370
|
|
|
371 4 Display Functions
|
|
|
372
|
|
|
373 4.0: Textual Fonts and Colors
|
|
|
374 * Q4.0.1:: How do I specify a font?
|
|
|
375 * Q4.0.2:: How do I set the text, menu and modeline fonts?
|
|
|
376 * Q4.0.3:: How can I set color options from @file{init.el}?
|
|
|
377 * Q4.0.4:: How can I set the colors when highlighting a region?
|
|
|
378 * Q4.0.5:: How can I limit color map usage?
|
|
|
379 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them.
|
|
|
380 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs?
|
|
|
381 * Q4.0.8:: How do I display non-ASCII characters?
|
|
|
382 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}.
|
|
|
383
|
|
|
384 4.1: Syntax Highlighting (Font Lock)
|
|
|
385 * Q4.1.1:: How can I do source code highlighting using font-lock?
|
|
|
386 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
387
|
|
|
388 4.2: The Modeline
|
|
|
389 * Q4.2.1:: How can I make the modeline go away?
|
|
|
390 * Q4.2.2:: How do you have XEmacs display the line number in the modeline?
|
|
|
391 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline?
|
|
|
392 * Q4.2.4:: How can I change the modeline color based on the mode used?
|
|
|
393
|
|
|
394 4.3: The Cursor
|
|
|
395 * Q4.3.1:: Is there a way to make the bar cursor thicker?
|
|
|
396 * Q4.3.2:: Is there a way to get back the block cursor?
|
|
|
397 * Q4.3.3:: Can I make the cursor blink?
|
|
|
398
|
|
|
399 4.4: The Menubar
|
|
|
400 * Q4.4.1:: How do I get rid of the menubar?
|
|
|
401 * Q4.4.2:: How can I customize the menubar?
|
|
|
402 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
403 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
404 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
405
|
|
|
406 4.5: The Toolbar
|
|
|
407 * Q4.5.1:: How do I get rid of the toolbar?
|
|
|
408 * Q4.5.2:: How can I customize the toolbar?
|
|
|
409 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar?
|
|
|
410 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar
|
|
|
411
|
|
|
412 4.6: Scrollbars and Scrolling
|
|
|
413 * Q4.6.1:: How can I disable the scrollbar?
|
|
|
414 * Q4.6.2:: How can I change the scrollbar width?
|
|
|
415 * Q4.6.3:: How can I use resources to change scrollbar colors?
|
|
|
416 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this?
|
|
|
417 * Q4.6.5:: Scrolling one line at a time.
|
|
|
418 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
419 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
420
|
|
|
421 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
422 * Q4.7.1:: How can I disable the gutter tabs?
|
|
|
423 * Q4.7.2:: How can I disable the progress bar?
|
|
|
424 * Q4.7.3:: There are bugs in the gutter or widgets.
|
|
|
425 * Q4.7.4:: How can I customize the gutter or gutter tabs?
|
|
|
426
|
|
|
427 5 Interfacing with the Operating System and External Devices
|
|
|
428
|
|
|
429 5.0: X Window System and Resources
|
|
|
430 * Q5.0.1:: Where is a list of X resources?
|
|
|
431 * Q5.0.2:: How can I detect a color display?
|
|
|
432 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}?
|
|
|
433 * Q5.0.4:: How can I have the window title area display the full path?
|
|
|
434 * Q5.0.5:: @samp{xemacs -name junk} doesn't work?
|
|
|
435 * Q5.0.6:: @samp{-iconic} doesn't work.
|
|
|
436
|
|
|
437 5.1: Microsoft Windows
|
|
|
438 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
|
439 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
|
440
|
|
|
441 5.2: Printing
|
|
|
442 * Q5.2.1:: What do I need to change to make printing work?
|
|
|
443 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer?
|
|
|
444 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
|
445 * Q5.2.4:: Can you print under MS Windows?
|
|
|
446
|
|
|
447 5.3: Sound
|
|
|
448 * Q5.3.1:: How do I turn off the sound?
|
|
|
449 * Q5.3.2:: How do I get funky sounds instead of a boring beep?
|
|
|
450 * Q5.3.3:: What are NAS and ESD (EsounD)?
|
|
|
451 * Q5.3.4:: Sunsite sounds don't play.
|
|
|
452
|
|
|
453 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
454 * Q5.4.1:: What is an interior shell?
|
|
|
455 * Q5.4.2:: How do I start up a second shell buffer?
|
|
|
456 * Q5.4.3:: Telnet from shell filters too much
|
|
|
457 * Q5.4.4:: Strange things are happening in Shell Mode.
|
|
|
458 * Q5.4.5:: XEmacs complains "No such file or directory, diff"
|
|
2995
|
459 * Q5.4.6:: Cygwin error "fork_copy: linked dll/bss pass 0 failed"
|
|
2459
|
460
|
|
|
461 5.5: Multiple Device Support
|
|
|
462 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display?
|
|
|
463 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
464 * Q5.5.3:: How do I disable gnuserv from opening a new frame?
|
|
|
465 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
|
466 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
|
467
|
|
|
468 6 Connecting to the Internet
|
|
|
469
|
|
|
470 6.0: General Mail and News
|
|
|
471 * Q6.0.1:: What are the various packages for reading mail?
|
|
|
472 * Q6.0.2:: How can I send mail?
|
|
|
473 * Q6.0.3:: How do I get my outgoing mail archived?
|
|
|
474 * Q6.0.4:: How can I read and/or compose MIME messages?
|
|
|
475 * Q6.0.5:: How do I customize the From line?
|
|
|
476 * Q6.0.6:: How do I get my MUA to filter mail for me?
|
|
|
477 * Q6.0.7:: Remote mail reading with an MUA.
|
|
|
478 * Q6.0.8:: An MUA gets an error incorporating new mail.
|
|
|
479 * Q6.0.9:: Why isn't @file{movemail} working?
|
|
|
480 * Q6.0.10:: How do I make my MUA display graphical smilies?
|
|
|
481 * Q6.0.11:: How can I get those oh-so-neat X-Face lines?
|
|
|
482
|
|
|
483 6.1: Reading Mail with VM
|
|
|
484 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
485 * Q6.1.2:: How can I get VM to automatically check for new mail?
|
|
|
486 * Q6.1.3:: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"?
|
|
|
487 * Q6.1.4:: Is there a mailing list or FAQ for VM?
|
|
|
488 * Q6.1.5:: How do I make VM stay in a single frame?
|
|
|
489 * Q6.1.6:: Customization of VM not covered in the manual, or here.
|
|
|
490
|
|
|
491 6.2: Reading Netnews and Mail with Gnus
|
|
|
492 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
493 * Q6.2.2:: How do I make Gnus stay within a single frame?
|
|
|
494
|
|
|
495 6.3: FTP Access
|
|
|
496 * Q6.3.1:: Can I edit files on other hosts?
|
|
|
497 * Q6.3.2:: What is EFS?
|
|
|
498
|
|
|
499 6.4: Web Browsing with W3
|
|
|
500 * Q6.4.1:: What is W3?
|
|
|
501 * Q6.4.2:: How do I run W3 from behind a firewall?
|
|
|
502 * Q6.4.3:: Is it true that W3 supports style sheets and tables?
|
|
|
503
|
|
|
504 7 Advanced Customization Using XEmacs Lisp
|
|
|
505
|
|
2537
|
506 7.0: Emacs Lisp and @file{init.el}
|
|
|
507 * Q7.0.1:: What version of Emacs am I running?
|
|
|
508 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions?
|
|
|
509 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly.
|
|
|
510 * Q7.0.4:: How can I add directories to the @code{load-path}?
|
|
|
511 * Q7.0.5:: How to check if a lisp function is defined?
|
|
|
512 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer?
|
|
|
513
|
|
|
514 7.1: Emacs Lisp Programming Techniques
|
|
|
515 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
|
516 * Q7.1.2:: Can I generate "fake" keyboard events?
|
|
|
517 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail?
|
|
|
518 * Q7.1.4:: What is the performance hit of @code{let}?
|
|
|
519 * Q7.1.5:: What is the recommended use of @code{setq}?
|
|
|
520 * Q7.1.6:: What is the typical misuse of @code{setq}?
|
|
|
521 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down?
|
|
|
522 * Q7.1.8:: I like recursion, does it slow things down?
|
|
|
523 * Q7.1.9:: How do I put a glyph as annotation in a buffer?
|
|
|
524 * Q7.1.10:: @code{map-extents} won't traverse all of my extents!
|
|
|
525 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
|
526
|
|
|
527 7.2: Mathematics
|
|
2559
|
528 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp?
|
|
|
529 * Q7.2.2:: XEmacs segfaults when I use very big numbers!
|
|
|
530 * Q7.2.3:: Bignums are really slow!
|
|
|
531 * Q7.2.4:: Equal bignums don't compare as equal! What gives?
|
|
2459
|
532
|
|
|
533 8 Other External Packages
|
|
|
534
|
|
|
535 8.0: TeX
|
|
|
536 * Q8.0.1:: Is there something better than LaTeX mode?
|
|
|
537 * Q8.0.2:: What is AUCTeX? Where do you get it?
|
|
|
538 * Q8.0.3:: Problems installing AUCTeX.
|
|
|
539 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline?
|
|
|
540
|
|
|
541 8.1: Other Unbundled Packages
|
|
|
542 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
|
543 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets?
|
|
|
544 * Q8.1.3:: Is there a MatLab mode?
|
|
|
545
|
|
|
546 8.2: Environments Built Around XEmacs
|
|
|
547 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop?
|
|
|
548 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21?
|
|
|
549 * Q8.2.3:: What is/was Energize?
|
|
|
550 * Q8.2.4:: What is Infodock?
|
|
|
551
|
|
|
552 9 What the Future Holds
|
|
|
553
|
|
|
554 9.0: Changes
|
|
|
555 * Q9.0.1:: What new features will be in XEmacs soon?
|
|
|
556 * Q9.0.2:: What's new in XEmacs 21.4?
|
|
|
557 * Q9.0.3:: What's new in XEmacs 21.1?
|
|
|
558 * Q9.0.4:: What's new in XEmacs 20.4?
|
|
|
559 * Q9.0.5:: What's new in XEmacs 20.3?
|
|
|
560 * Q9.0.6:: What's new in XEmacs 20.2?
|
|
|
561
|
|
|
562 10 New information about old XEmacsen
|
|
|
563
|
|
|
564 10.0: XEmacs 21.1
|
|
|
565 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
2559
|
566 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1.
|
|
|
567
|
|
428
|
568 @end detailmenu
|
|
|
569 @end menu
|
|
|
570
|
|
|
571 @node Introduction, Installation, Top, Top
|
|
|
572 @unnumbered 1 Introduction, Policy, Credits
|
|
|
573
|
|
|
574 Learning XEmacs is a lifelong activity. Even people who have used Emacs
|
|
|
575 for years keep discovering new features. Therefore this document cannot
|
|
|
576 be complete. Instead it is aimed at the person who is either
|
|
|
577 considering XEmacs for their own use, or has just obtained it and is
|
|
|
578 wondering what to do next. It is also useful as a reference to
|
|
|
579 available resources.
|
|
|
580
|
|
2417
|
581 The previous maintainer of the FAQ was
|
|
|
582 @email{rossini@@biostat.washington.edu, Anthony Rossini}, who started
|
|
|
583 it, after getting tired of hearing JWZ complain about repeatedly
|
|
|
584 having to answer questions. @email{ben@@xemacs.org, Ben Wing} then
|
|
|
585 took over and did a massive update reorganizing the whole thing. At
|
|
|
586 this point Anthony took back over, but then had to give it up again.
|
|
|
587 Some of the other contributors to this FAQ are listed later in this
|
|
|
588 document.
|
|
428
|
589
|
|
|
590 The previous version was converted to hypertext format, and edited by
|
|
|
591 @email{steve@@xemacs.org, Steven L. Baur}. It was converted back to
|
|
434
|
592 texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}. The FAQ was then
|
|
|
593 maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it
|
|
2417
|
594 on to ChristianNyb@o{}, and then to @email{wambold@@xemacs.org,Sandra Wambold}.
|
|
|
595
|
|
|
596 The current version of the FAQ has been heavily redone by
|
|
|
597 @email{ben@@xemacs.org, Ben Wing}.
|
|
428
|
598
|
|
|
599 If you notice any errors or items which should be added or amended to
|
|
2417
|
600 this FAQ please send email to @email{xemacs-beta@@xemacs.org}.
|
|
|
601 Include @samp{XEmacs FAQ} on the Subject: line.
|
|
428
|
602
|
|
|
603 @menu
|
|
2537
|
604 1.0: What is XEmacs?
|
|
2417
|
605 * Q1.0.1:: What is XEmacs?
|
|
|
606 * Q1.0.2:: What is the current version of XEmacs?
|
|
2537
|
607 * Q1.0.3:: How do you pronounce XEmacs?
|
|
|
608 * Q1.0.4:: What does XEmacs look like?
|
|
|
609 * Q1.0.5:: Who wrote XEmacs?
|
|
|
610 * Q1.0.6:: Who wrote the FAQ?
|
|
|
611
|
|
|
612 1.1: Getting XEmacs
|
|
|
613 * Q1.1.1:: Where can I find XEmacs?
|
|
|
614 * Q1.1.2:: Are binaries available?
|
|
|
615 * Q1.1.3:: How do I get the bleeding-edge sources?
|
|
|
616 * Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual?
|
|
|
617
|
|
|
618 1.2: Versions for Different Operating Systems
|
|
|
619 * Q1.2.1:: Do I need X11 to run XEmacs?
|
|
|
620 * Q1.2.2:: What versions of Unix does XEmacs run on?
|
|
|
621 * Q1.2.3:: Is there a port of XEmacs to Microsoft Windows?
|
|
|
622 * Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
623 * Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
624 * Q1.2.6:: What are the differences between the various MS Windows emacsen?
|
|
|
625 * Q1.2.7:: How does the port cope with differences in the Windows user interface?
|
|
|
626 * Q1.2.8:: Is there a port of XEmacs to the Macintosh?
|
|
|
627 * Q1.2.9:: Is there a port of XEmacs to MS-DOS?
|
|
|
628 * Q1.2.10:: Is there a port of XEmacs to OS/2?
|
|
|
629 * Q1.2.11:: Is there a port of XEmacs to NextStep?
|
|
|
630 * Q1.2.12:: Is there a port of XEmacs to VMS?
|
|
|
631
|
|
|
632 1.3: Getting Started
|
|
|
633 * Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
|
634 * Q1.3.2:: Where do I put my @file{init.el} file?
|
|
|
635 * Q1.3.3:: Can I use the same @file{init.el} with the other Emacs?
|
|
|
636 * Q1.3.4:: Any good XEmacs tutorials around?
|
|
|
637 * Q1.3.5:: May I see an example of a useful XEmacs Lisp function?
|
|
|
638 * Q1.3.6:: And how do I bind it to a key?
|
|
|
639 * Q1.3.7:: What's the difference between a macro and a function?
|
|
|
640 * Q1.3.8:: What is @code{Custom}?
|
|
|
641
|
|
|
642 1.4: Getting Help
|
|
|
643 * Q1.4.1:: Where can I get help?
|
|
|
644 * Q1.4.2:: Which mailing lists are there?
|
|
2559
|
645 * Q1.4.3:: Where are the mailing lists archived?
|
|
|
646 * Q1.4.4:: How can I get two instances of info?
|
|
|
647 * Q1.4.5:: How do I add new Info directories?
|
|
2537
|
648
|
|
|
649 1.5: Contributing to XEmacs
|
|
|
650 * Q1.5.1:: How do I submit changes to the FAQ?
|
|
|
651 * Q1.5.2:: How do I become a beta tester?
|
|
|
652 * Q1.5.3:: How do I contribute to XEmacs itself?
|
|
2559
|
653 * Q1.5.4:: How do I get started developing XEmacs?
|
|
|
654 * Q1.5.5:: What's the basic layout of the code?
|
|
2537
|
655
|
|
|
656 1.6: Politics (XEmacs vs. GNU Emacs)
|
|
|
657 * Q1.6.1:: What is GNU Emacs?
|
|
|
658 * Q1.6.2:: How does XEmacs differ from GNU Emacs?
|
|
|
659 * Q1.6.3:: How much does XEmacs differ?
|
|
|
660 * Q1.6.4:: Is XEmacs "GNU"?
|
|
|
661 * Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
|
662 * Q1.6.6:: Why haven't XEmacs and GNU Emacs merged?
|
|
|
663
|
|
|
664 1.7: External Packages
|
|
2559
|
665 * Q1.7.1:: What is the package system?
|
|
|
666 * Q1.7.2:: Which external packages are there?
|
|
|
667 * Q1.7.3:: Do I need to have the packages to run XEmacs?
|
|
|
668 * Q1.7.4:: Is there a way to find which package has particular functionality?
|
|
2537
|
669
|
|
|
670 1.8: Internationalization
|
|
|
671 * Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
|
672 * Q1.8.2:: How can I help with internationalization?
|
|
|
673 * Q1.8.3:: How do I type non-ASCII characters?
|
|
|
674 * Q1.8.4:: Can XEmacs messages come out in a different language?
|
|
|
675 * Q1.8.5:: Please explain the various input methods in MULE/XEmacs
|
|
|
676 * Q1.8.6:: How do I portably code for MULE/XEmacs?
|
|
|
677 * Q1.8.7:: How about Cyrillic modes?
|
|
|
678 * Q1.8.8:: Does XEmacs support Unicode?
|
|
|
679 * Q1.8.9:: How does XEmacs display Unicode?
|
|
428
|
680 @end menu
|
|
|
681
|
|
2537
|
682 @unnumberedsec 1.0: What is XEmacs?
|
|
2417
|
683
|
|
428
|
684 @node Q1.0.1, Q1.0.2, Introduction, Introduction
|
|
|
685 @unnumberedsubsec Q1.0.1: What is XEmacs?
|
|
|
686
|
|
479
|
687 XEmacs is a powerful, highly customizable open source text editor and
|
|
2417
|
688 application development system, with full GUI support. It is
|
|
|
689 protected under the GNU Public License and related to other versions
|
|
|
690 of Emacs, in particular GNU Emacs. Its emphasis is on modern
|
|
|
691 graphical user interface support and an open software development
|
|
|
692 model, similar to Linux. XEmacs has an active development community
|
|
|
693 numbering in the hundreds (and thousands of active beta testers on top
|
|
|
694 of this), and runs on all versions of MS Windows, on Mac OS X, on
|
|
|
695 Linux, and on nearly every other version of Unix in existence.
|
|
|
696 Support for XEmacs has been supplied by Sun Microsystems, University
|
|
|
697 of Illinois, Lucid, ETL/Electrotechnical Laboratory, Amdahl
|
|
|
698 Corporation, BeOpen, and others, as well as the unpaid time of a great
|
|
|
699 number of individual developers.
|
|
428
|
700
|
|
|
701 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction
|
|
|
702 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs?
|
|
|
703
|
|
2417
|
704 XEmacs versions 21.4.* are releases made from the current stable
|
|
|
705 sources. XEmacs versions 21.5.* (which will be released as 22.0) are
|
|
|
706 releases made from the development sources. Check at
|
|
|
707 @uref{http://www.xemacs.org} for the current minor version. XEmacs
|
|
|
708 versions 21.1.* were the previous stable releases, now retired.
|
|
|
709
|
|
|
710 XEmacs 20.4, released in February 1998, was the last release of v20.
|
|
|
711
|
|
|
712 XEmacs 19.16, released in November, 1997. was the last release of v19,
|
|
|
713 and was also the last version without international language support.
|
|
428
|
714
|
|
|
715 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction
|
|
2537
|
716 @unnumberedsubsec Q1.0.3: How do you pronounce XEmacs?
|
|
|
717
|
|
|
718 The most common pronounciation is @samp{Eks eemax}.
|
|
428
|
719
|
|
|
720 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction
|
|
2537
|
721 @unnumberedsubsec Q1.0.4: What does XEmacs look like?
|
|
|
722
|
|
|
723 Screen snapshots are available at
|
|
|
724 @uref{http://www.xemacs.org/About/Screenshots/index.html}
|
|
|
725 as part of the XEmacs website.
|
|
|
726
|
|
|
727 @node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
|
|
|
728 @unnumberedsubsec Q1.0.5: Who wrote XEmacs?
|
|
|
729
|
|
|
730 XEmacs is the result of the time and effort of many people, and the
|
|
|
731 active developers have changed over time. There are two major
|
|
|
732 components of the XEmacs effort -- writing the code itself and providing
|
|
|
733 all the support work (testing the code, releasing beta and final
|
|
|
734 versions, handling patches, reading bug reports, maintaining the web
|
|
|
735 site, managing the mailing lists, etc. etc.). Neither component would
|
|
|
736 work without the other.
|
|
|
737
|
|
|
738 @subheading CODING
|
|
|
739
|
|
|
740 The primary code contributor over the years has been Ben Wing (active
|
|
|
741 since late 1992). Between 1991 and 1995, large amounts of coding was
|
|
|
742 contributed by Jamie Zawinski and Chuck Thompson. Many other people
|
|
|
743 have authored major subsystems or otherwise contributed large amounts of
|
|
|
744 code, including Andy Piper, Hrvoje Niksic, Jerry James, Jonathan Harris,
|
|
|
745 Kyle Jones, Martin Buchholz, Michael Sperber, Olivier Galibert, Richard
|
|
|
746 Mlynarik, Stig, William Perry and plenty of others.
|
|
|
747
|
|
|
748 Primary XEmacs-specific subsystems and their authors:
|
|
|
749
|
|
|
750 @table @asis
|
|
|
751 @item Objects
|
|
|
752 @itemize @minus
|
|
|
753 @item
|
|
|
754 Conversion from 26-bit to 28-bit pointers and integers, lrecords, lcrecords: Richard Mlynarik, 1994
|
|
|
755 @item
|
|
|
756 Conversion to 32-bit pointers and 31-bit integers: Kyle Jones, Martin Buchholz
|
|
|
757 @item
|
|
|
758 Portable dumper, object descriptions: Olivier Galibert
|
|
|
759 @item
|
|
|
760 KKCC (new garbage collector), ephemerons, weak boxes: Michael Sperber and students
|
|
|
761 @item
|
|
|
762 Random object work (object equal and hash methods, weak lists, lcrecord lists, bit vectors, dynarr, blocktype, opaque, string resizing): Ben Wing
|
|
|
763 @item
|
|
|
764 Profiling: Ben Wing
|
|
|
765 @item
|
|
|
766 Some byte-compilation and hash-table improvements: Martin Buchholz
|
|
|
767 @item
|
|
|
768 Bignum: Jerry James
|
|
|
769 @end itemize
|
|
|
770
|
|
|
771 @item Internationalization/Mule
|
|
|
772 @itemize @minus
|
|
|
773 @item
|
|
|
774 mostly Ben Wing; many ideas for future work, Stephen Turnbull
|
|
|
775 @end itemize
|
|
|
776
|
|
|
777 @item I/O
|
|
|
778 @itemize @minus
|
|
|
779 @item
|
|
|
780 Basic event/event-stream implementation: Jamie Zawinski
|
|
|
781 @item
|
|
|
782 Most event work since 1994: Ben Wing
|
|
|
783 @item
|
|
|
784 Asynchronous stuff (async timeouts, signals, quit-checking): Ben Wing
|
|
|
785 @item
|
|
|
786 Process method abstraction, Windows process work: Kirill Katsnelson
|
|
|
787 @item
|
|
|
788 Misc-user events, async timeouts, most quit-checking and signal code, most other work since 1994: Ben Wing
|
|
|
789 @item
|
|
|
790 Lstreams: Ben Wing
|
|
|
791 @end itemize
|
|
|
792
|
|
|
793 @item Display
|
|
|
794 @itemize @minus
|
|
|
795 @item
|
|
|
796 Redisplay mechanism: implementation, Chuck Thompson; additional work, lots of people
|
|
|
797 @item
|
|
|
798 Glyphs: mostly Ben Wing
|
|
|
799 @item
|
|
|
800 Specifiers: Ben Wing
|
|
|
801 @item
|
|
|
802 Extents: initial implementation, someone at Lucid; rewrite, 1994, Ben Wing
|
|
|
803 @item
|
|
|
804 Widgets: Andy Piper
|
|
|
805 @item
|
|
|
806 JPEG/PNG/TIFF image converters: Ben Wing, William Perry, Jareth Hein, others (see comment in @file{glyphs-eimage.c})
|
|
|
807 @item
|
|
|
808 Menus: Jamie Zawinski, someone at Lucid (Lucid menus)
|
|
|
809 @item
|
|
|
810 Scrollbars: Chuck Thompson, ??? (Lucid scrollbar)
|
|
|
811 @item
|
|
|
812 Multi-device/device-independence work (console/device/etc methods): Ben Wing, prototype by chuck thompson
|
|
|
813 @item
|
|
|
814 Faces: first implementation, Jamie Zawinski; second, chuck; third, Ben Wing
|
|
|
815 @item
|
|
|
816 Fonts/colors: first implementation, Jamie Zawinski; further work, Ben Wing
|
|
|
817 @item
|
|
|
818 Toolbars: implementation, chuck, much interface work, Ben Wing
|
|
|
819 @item
|
|
|
820 Gutters, tabs: andy piper
|
|
|
821 @end itemize
|
|
|
822
|
|
|
823 @item Device subsystems
|
|
|
824 @itemize @minus
|
|
|
825 @item
|
|
4311
|
826 X Windows: Jamie Zawinski, Ben Wing, others
|
|
2537
|
827 @item
|
|
|
828 GTK: William Perry, Malcolm Purvis
|
|
|
829 @item
|
|
|
830 MS Windows: initial implementation, Jonathan Harris; some more work, Andy Piper, Ben Wing
|
|
|
831 @item
|
|
|
832 TTY: Chuck Thompson, Ben Wing
|
|
|
833 @item
|
|
|
834 Cygwin: Andy Piper
|
|
|
835 @end itemize
|
|
|
836
|
|
|
837 @item Misc
|
|
|
838 @itemize @minus
|
|
|
839 @item
|
|
|
840 Configure: initial porting from fsf, Chuck Thompson; conversion to autoconf 2, much rewriting, Martin Buchholz
|
|
|
841 @item
|
|
|
842 Most initialization-related code: Ben Wing
|
|
|
843 @item
|
|
|
844 Internals manual, much of Lisp manual: Ben Wing
|
|
|
845 @item
|
|
|
846 FSF synching: initial sync with FSF 19, Richard Mlynarik, further work, Ben Wing
|
|
|
847 @end itemize
|
|
|
848 @end table
|
|
|
849
|
|
|
850 @subheading SUPPORT
|
|
|
851
|
|
|
852 Currently, support duties are handled by many different people.
|
|
|
853
|
|
|
854 Release managers have been
|
|
|
855
|
|
|
856 @itemize @minus
|
|
|
857 @item
|
|
|
858 Stephen Turnbull (April 2001 - January 2003, March 2004 - present, 21.2.47 - 21.4.12, 21.5.2 - 21.5.7, 21.5.17 - present)
|
|
|
859 @item
|
|
|
860 Vin Shelton (May 2003 - present, 21.4.13 - present)
|
|
|
861 @item
|
|
|
862 Steve Youngs (July 2002 - September 2003, 21.5.8 - 21.5.16)
|
|
|
863 @item
|
|
|
864 Martin Buchholz (December 1998, November 1999 - May 2001, 21.2.7 - 21.2.8, 21.2.21 - 21.2.46, 21.5.0 - 21.5.1)
|
|
|
865 @item
|
|
|
866 Steve Baur (early 1997 - December 1998, February 1999 - November 1999, 19.15 - 21.2.5, 21.2.9 - 21.2.20)
|
|
|
867 @item
|
|
|
868 Andy Piper (December 1998, 21.2.6)
|
|
|
869 @item
|
|
|
870 Chuck Thompson (June 1994 - September 1996, 19.11 - 19.14)
|
|
|
871 @item
|
|
|
872 Jamie Zawinski (April 1991 - June 1994, 19.0 - 19.10)
|
|
|
873 @end itemize
|
|
|
874
|
|
|
875 The recent overlapping dates are intentional, since two or three trees
|
|
|
876 are maintained simultaneously at any point.
|
|
|
877
|
|
|
878 Other major support work:
|
|
|
879
|
|
|
880 @itemize @minus
|
|
|
881 @item
|
|
|
882 Adrian Aichner wrote and maintains the web site.
|
|
|
883 @item
|
|
|
884 Stephen Turnbull has produced many of the beta and semi-stable releases
|
|
|
885 and has attempted to be the "face" of XEmacs on the newsgroups and
|
|
|
886 mailing lists.
|
|
|
887 @item
|
|
|
888 Steve Youngs currently produces the beta releases (???).
|
|
|
889 @item
|
|
4311
|
890 Steve Youngs, Ville Skyttä, and now Norbert Koch have taken turns
|
|
2537
|
891 maintaining the packages.
|
|
|
892 @item
|
|
|
893 Vin Shelton maintains the stable releases.
|
|
|
894 @item
|
|
|
895 Testing - #### Norbert, Adrian, ???
|
|
|
896 @end itemize
|
|
|
897
|
|
|
898 Portraits and email of some of the major developers:
|
|
|
899
|
|
|
900 @itemize @bullet
|
|
|
901 @item @email{andy@@xemacs.org, Andy Piper}
|
|
|
902 @html
|
|
|
903 <br><img src="piper.png" alt="Portrait of Andy Piper"><br>
|
|
|
904 @end html
|
|
|
905
|
|
|
906 @item @email{ben@@xemacs.org, Ben Wing}
|
|
|
907 @html
|
|
|
908 <br><img src="ben.png" alt="Portrait of Ben Wing"><br>
|
|
|
909 @end html
|
|
|
910
|
|
|
911 @item @email{cthomp@@xemacs.org, Chuck Thompson}
|
|
|
912 @html
|
|
|
913 <br><img src="cthomp.png" alt="Portrait of Chuck Thompson"><br>
|
|
|
914 @end html
|
|
|
915
|
|
|
916 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
|
|
|
917
|
|
|
918 @html
|
|
|
919 <br><img src="hniksic.png" alt="Portrait of Hrvoje Niksic"><br>
|
|
|
920 @end html
|
|
|
921
|
|
|
922 @item @email{jwz@@jwz.org, Jamie Zawinski}
|
|
|
923 @html
|
|
|
924 <br><img src="jwz.png" alt="Portrait of Jamie Zawinski"><br>
|
|
|
925 @end html
|
|
|
926
|
|
|
927 @item @email{martin@@xemacs.org, Martin Buchholz}
|
|
|
928 @html
|
|
|
929 <br><img src="martin.png" alt="Portrait of Martin Buchholz"><br>
|
|
|
930 @end html
|
|
|
931
|
|
|
932 @item @email{mly@@adoc.xerox.com, Richard Mlynarik}
|
|
|
933 @html
|
|
|
934 <br><img src="mly.png" alt="Portrait of Richard Mlynarik"><br>
|
|
|
935 @end html
|
|
|
936
|
|
|
937 @item @email{stephen@@xemacs.org, Stephen Turnbull}
|
|
|
938
|
|
|
939 @item @email{steve@@xemacs.org, Steve Baur}
|
|
|
940 @html
|
|
|
941 <br><img src="slb.png" alt="Portrait of Steve Baur"><br>
|
|
|
942 @end html
|
|
|
943 @end itemize
|
|
|
944
|
|
|
945 Many other people have contributed to XEmacs; this is partially
|
|
|
946 enumerated in the @samp{About XEmacs} option in the Help menu.
|
|
|
947
|
|
|
948 @node Q1.0.6, Q1.1.1, Q1.0.5, Introduction
|
|
|
949 @unnumberedsubsec Q1.0.6: Who wrote the FAQ?
|
|
|
950
|
|
|
951 The current version of this FAQ was created by @email{ben@@xemacs.org,
|
|
|
952 Ben Wing}.
|
|
|
953
|
|
|
954 Previous contributors to the FAQ include
|
|
|
955
|
|
|
956 @itemize @bullet
|
|
|
957 @item @email{steve@@xemacs.org, SL Baur}
|
|
|
958
|
|
|
959 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
|
|
|
960
|
|
|
961 @item @email{binge@@aloft.att.com, Curtis.N.Bingham}
|
|
|
962
|
|
|
963 @item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan}
|
|
|
964
|
|
|
965 @item @email{rjc@@cogsci.ed.ac.uk, Richard Caley}
|
|
|
966
|
|
|
967 @item @email{cognot@@ensg.u-nancy.fr, Richard Cognot}
|
|
|
968
|
|
|
969 @item @email{daku@@nortel.ca, Mark Daku}
|
|
|
970
|
|
|
971 @item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque}
|
|
|
972
|
|
|
973 @item @email{eeide@@cs.utah.edu, Eric Eide}
|
|
|
974
|
|
|
975 @item @email{af@@biomath.jussieu.fr, Alain Fauconnet}
|
|
|
976
|
|
|
977 @item @email{cflatter@@nrao.edu, Chris Flatters}
|
|
|
978
|
|
|
979 @item @email{ginsparg@@adra.com, Evelyn Ginsparg}
|
|
|
980
|
|
|
981 @item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall}
|
|
|
982
|
|
|
983 @item @email{dkindred@@cmu.edu, Darrell Kindred}
|
|
|
984
|
|
|
985 @item @email{dmoore@@ucsd.edu, David Moore}
|
|
|
986
|
|
|
987 @item @email{arup+@@cmu.edu, Arup Mukherjee}
|
|
|
988
|
|
|
989 @item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen}
|
|
|
990
|
|
|
991 @item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell}
|
|
|
992
|
|
|
993 @item @email{dworkin@@ccs.neu.edu, Justin Sheehy}
|
|
|
994
|
|
|
995 @item @email{stig@@hackvan.com, Stig}
|
|
|
996
|
|
|
997 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
|
|
|
998 @end itemize
|
|
|
999
|
|
|
1000 @unnumberedsec 1.1: Getting XEmacs
|
|
|
1001
|
|
|
1002 @node Q1.1.1, Q1.1.2, Q1.0.6, Introduction
|
|
|
1003 @unnumberedsubsec Q1.1.1: Where can I find XEmacs?
|
|
|
1004
|
|
|
1005 To download XEmacs, visit the XEmacs WWW page at
|
|
|
1006 @uref{http://www.xemacs.org/Download/}. The most up-to-date list of
|
|
|
1007 distribution sites can always be found there. Try to pick a site that
|
|
|
1008 is networkologically close to you. If you know of other mirrors of
|
|
|
1009 the XEmacs archives, please send e-mail to
|
|
|
1010 @uref{mailto:webmaster@@xemacs.org} and we will list them here as well.
|
|
|
1011
|
|
|
1012 The canonical distribution point is ftp.xemacs.org, available either
|
|
|
1013 through HTTP (@uref{http://ftp.xemacs.org/}) or anonymous FTP
|
|
|
1014 (@uref{ftp://ftp.xemacs.org/pub/xemacs/}).
|
|
|
1015
|
|
|
1016 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
|
|
|
1017 @unnumberedsubsec Q1.1.2: Are binaries available?
|
|
2417
|
1018
|
|
|
1019 MS Windows binaries are available at
|
|
|
1020 @uref{http://www.xemacs.org/Download/win32/} for the native versions
|
|
|
1021 of 21.4 and 21.1. Cygwin binaries are now available as part of the
|
|
|
1022 standard Cygwin installation process. XEmacs also comes pre-built as
|
|
|
1023 part of many Linux distributions, such as Red Hat and SuSE.
|
|
|
1024
|
|
|
1025 Otherwise, you will need to build XEmacs yourself or get your system
|
|
|
1026 administrator to do it. Generally, this is not a difficult process
|
|
|
1027 under Unix and Mac OS X, as XEmacs has been tested under all of the
|
|
|
1028 common Unix versions and under Mac OS X and comes with an extensive
|
|
|
1029 configure script that is able to automatically detect most aspects of
|
|
|
1030 the configuration of your particular system.
|
|
|
1031
|
|
2537
|
1032 @node Q1.1.3, Q1.1.4, Q1.1.2, Introduction
|
|
|
1033 @unnumberedsubsec Q1.1.3: How do I get the bleeding-edge sources?
|
|
|
1034
|
|
|
1035 If you are interested in developing XEmacs, or getting the absolutely most
|
|
|
1036 recent, up-to-the-moment, bleeding-edge source code, you can directly
|
|
|
1037 access the master CVS source tree (read-only, of course, until you ask for
|
|
|
1038 and are granted permission to directly modify portions of the source tree)
|
|
|
1039 at cvs.xemacs.org. Directions on how to access the source tree are located
|
|
|
1040 at @uref{http://www.xemacs.org/Develop/cvsaccess.html}.
|
|
|
1041
|
|
|
1042 Nightly CVS snapshots are available at
|
|
|
1043 @uref{http://www.dk.xemacs.org/Download/CVS-snapshots/}.
|
|
|
1044
|
|
|
1045 @node Q1.1.4, Q1.2.1, Q1.1.3, Introduction
|
|
|
1046 @unnumberedsubsec Q1.1.4: 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.2: Versions for Different Operating Systems
|
|
|
1056
|
|
|
1057 @node Q1.2.1, Q1.2.2, Q1.1.4, Introduction
|
|
|
1058 @unnumberedsubsec Q1.2.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.2.2, Q1.2.3, Q1.2.1, Introduction
|
|
|
1065 @unnumberedsubsec Q1.2.2: What versions of Unix does XEmacs run on?
|
|
|
1066
|
|
2559
|
1067 XEmacs is regularly tested on Linux, Solaris, SunOS, HP/UX, FreeBSD,
|
|
|
1068 OpenBSD, BSD/OS aka BSDI, Tru64 aka DEC/OSF, SCO5, and probably
|
|
|
1069 others. It should work on all versions of Unix created in the last 10
|
|
|
1070 years or so, perhaps with a bit of work on more obscure platforms to
|
|
|
1071 correct bit-rot. It uses a sophisticated configuration system to
|
|
|
1072 auto-detect zillions of features that are implemented differently in
|
|
|
1073 different versions of Unix, so it will probably work on your vendor's
|
|
|
1074 version, possibly with a bit of tweaking, even if we've never heard of
|
|
|
1075 it.
|
|
|
1076
|
|
2537
|
1077 For problems with particular machines and versions of Unix, see the
|
|
|
1078 @file{PROBLEMS} file.
|
|
|
1079
|
|
|
1080 Much effort has gone into making XEmacs work on as many different
|
|
|
1081 machines, configurations, and compilers as possible.
|
|
|
1082
|
|
|
1083 Much effort has gone into making XEmacs 64-bit clean.
|
|
|
1084
|
|
|
1085 Much effort has gone into removing system-specific code, and replacing
|
|
|
1086 such code with autodetection at configure time.
|
|
|
1087
|
|
|
1088 The XEmacs core should build "out of the box" on most Unix-like systems.
|
|
|
1089
|
|
|
1090 XEmacs 21.2 was tested and @samp{make check} succeeded on these Unix
|
|
|
1091 configurations as of 2001-02-10:
|
|
|
1092
|
|
|
1093 @example
|
|
|
1094 alphaev56-dec-osf4.0e (both Compaq C and gcc)
|
|
|
1095 i386-unknown-freebsd4.2
|
|
|
1096 i386-unknown-netbsdelf1.5
|
|
|
1097 i586-sco-sysv5uw7.0.1 (both SCO's cc and gcc)
|
|
|
1098 i686-pc-linux-gnu
|
|
|
1099 hppa2.0-hp-hpux10.20 (both HP's ANSI cc and gcc)
|
|
|
1100 mips-sgi-irix6.5 (both MIPSpro cc and gcc)
|
|
|
1101 rs6000-ibm-aix4.3.0.0 (both IBM's xlc and gcc)
|
|
|
1102 sparc-sun-solaris2.6 (both Sun's Forte C and gcc)
|
|
|
1103 sparc-sun-solaris2.7 (both Sun's Forte C and gcc)
|
|
|
1104 sparc-sun-sunos4.1.4 (gcc)
|
|
|
1105 @end example
|
|
|
1106
|
|
3018
|
1107 Some systems have a dual mode 32-bit/64-bit compiler. On most of these,
|
|
|
1108 XEmacs requires the @samp{--pdump} (in XEmacs 21.5,
|
|
|
1109 @samp{--enable-pdump}) configure option to build correctly with the
|
|
|
1110 64-bit version of the compiler.
|
|
2537
|
1111
|
|
|
1112 @example
|
|
|
1113 mips-sgi-irix6.5, CC="gcc -mabi=64"
|
|
|
1114 mips-sgi-irix6.5, CC="cc -64"
|
|
|
1115 rs6000-ibm-aix4.3.0.0, CC="cc -q64"
|
|
|
1116 @end example
|
|
|
1117
|
|
|
1118 On most of these systems, XEmacs also builds with a C++ compiler,
|
|
|
1119 but not "out of the box". This feature is only for use by the
|
|
|
1120 maintainers.
|
|
|
1121
|
|
|
1122 XEmacs 21.2 is known @emph{not} to work on any machines with m680x0
|
|
|
1123 processors. Sorry, all you sun3 and Unix PC nostalgia buffs out there.
|
|
|
1124
|
|
|
1125 VMS has never been supported by XEmacs. In fact, all the old VMS code
|
|
|
1126 inherited from Emacs has been removed. Sorry, all you VMS fans out there.
|
|
|
1127
|
|
|
1128 @node Q1.2.3, Q1.2.4, Q1.2.2, Introduction
|
|
|
1129 @unnumberedsubsec Q1.2.3: Is there a port of XEmacs to Microsoft Windows?
|
|
|
1130
|
|
|
1131 Yes. Beginning with release 21.0, XEmacs has worked under MS Windows
|
|
|
1132 and is fully-featured and actively developed. A group of dedicated
|
|
|
1133 developers actively maintains and improves the Windows-specific
|
|
|
1134 portions of the code. Some of the core developers, in fact, use
|
|
|
1135 Windows as their only development environment, and some features, such
|
|
|
1136 as printing, actually work better on Windows than native Unix and Mac
|
|
|
1137 OS X. The mailing list at @email{xemacs-winnt@@xemacs.org} is dedicated
|
|
|
1138 to that effort (please use the -request address to
|
|
|
1139 subscribe). (Despite its name, XEmacs actually works on all versions
|
|
|
1140 of Windows.)
|
|
|
1141
|
|
|
1142 The list name is misleading, as XEmacs supports and has been compiled on
|
|
|
1143 Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows
|
|
|
1144 XP, and all newer versions of Windows. The MS Windows-specific code is
|
|
|
1145 based on Microsoft Win32 API, and will not work on MS Windows 3.x or on
|
|
|
1146 MS-DOS.
|
|
|
1147
|
|
|
1148 XEmacs also supports the Cygwin and MinGW development and runtime
|
|
|
1149 environments, where it also uses native Windows code for graphical
|
|
|
1150 features. In addition, under Cygwin it is possible to compile XEmacs
|
|
|
1151 to use an X server (and XFree86 is available as part of the standard
|
|
|
1152 Cygwin installation).
|
|
|
1153
|
|
|
1154 @node Q1.2.4, Q1.2.5, Q1.2.3, Introduction
|
|
|
1155 @unnumberedsubsec Q1.2.4: Can I build XEmacs on MS Windows with X support? Do I need to?
|
|
|
1156
|
|
|
1157 Yes, you can, but no you do not need to. In fact, we recommend that you
|
|
|
1158 use a native-GUI version unless you have a specific need for an X
|
|
|
1159 version.
|
|
|
1160
|
|
|
1161 @node Q1.2.5, Q1.2.6, Q1.2.4, Introduction
|
|
|
1162 @unnumberedsubsec Q1.2.5: What are Cygwin and MinGW, and do I need them to run XEmacs?
|
|
|
1163
|
|
|
1164 To answer the second part of the question: No, you, you don't need
|
|
|
1165 Cygwin or MinGW to build or to run XEmacs. But if you have them and
|
|
|
1166 want to use them, XEmacs supports these environments.
|
|
|
1167
|
|
|
1168 (One important reason to support Cygwin is that it lets the MS Windows
|
|
|
1169 developers test out their code in a Unix environment without actually
|
|
|
1170 having to have a Unix machine around. For this reason alone, Cygwin
|
|
|
1171 support is likely to remain supported for a long time in XEmacs. Same
|
|
|
1172 goes for the X support under Cygwin, for the same reasons. MinGW
|
|
|
1173 support, on the other hand, depends on volunteers to keep it up to date;
|
|
|
1174 but this is generally not hard.)
|
|
|
1175
|
|
|
1176 Cygwin is a set of tools providing Unix-like API on top of Win32.
|
|
|
1177 It makes it easy to port large Unix programs without significant
|
|
|
1178 changes to their source code. It is a development environment as well
|
|
|
1179 as a runtime environment.
|
|
|
1180
|
|
|
1181 When built with Cygwin, XEmacs supports all display types -- TTY, X &
|
|
|
1182 Win32 GUI, and can be built with support for all three simultaneously.
|
|
|
1183 If you build with Win32 GUI support then the Cygwin version uses the
|
|
|
1184 majority of the Windows-specific code, which is mostly related to
|
|
|
1185 display. If you want to build with X support you need X libraries (and
|
|
2559
|
1186 an X server to display XEmacs on); see @ref{Q2.3.7}. TTY and Win32 GUI
|
|
2537
|
1187 require no additional libraries beyond what comes standard with Cygwin.
|
|
|
1188
|
|
|
1189 The advantages of the Cygwin version are that it integrates well with
|
|
|
1190 the Cygwin environment for existing Cygwin users; uses configure so
|
|
|
1191 building with different features is very easy; and actively supports X &
|
|
|
1192 TTY. Furthermore, the entire Cygwin environment and compiler are free,
|
|
|
1193 whereas Visual C++ costs money.
|
|
|
1194
|
|
|
1195 The disadvantage is that it requires the whole Cygwin environment,
|
|
|
1196 whereas the native port requires only a suitable MS Windows compiler.
|
|
|
1197 Also, it follows the Unix filesystem and process model very closely
|
|
|
1198 (some will undoubtedly view this as an advantage).
|
|
|
1199
|
|
|
1200 See @uref{http://www.cygwin.com/} for more information on
|
|
|
1201 Cygwin.
|
|
|
1202
|
|
|
1203 MinGW is a collection of header files and import libraries that allow
|
|
|
1204 one to use GCC under the Cygwin environment to compile and produce
|
|
|
1205 exactly the same native Win32 programs that you can using Visual C++.
|
|
|
1206 Programs compiled with MinGW make use of the standard Microsoft runtime
|
|
|
1207 library @file{MSVCRT.DLL}, present on all Windows systems, and look,
|
|
|
1208 feel, and act like a standard Visual-C-produced application. (The only
|
|
|
1209 difference is the compiler.) This means that, unlike a
|
|
|
1210 standardly-compiled Cygwin application, no extra runtime support
|
|
|
1211 (e.g. Cygwin's @file{cygwin1.dll}) is required. This, along with the
|
|
|
1212 fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y
|
|
|
1213 environment, for those die-hard Unix hackers out there), is the main
|
|
|
1214 advantage of MinGW. It is also potentially faster than Cygwin because
|
|
|
1215 it has less overhead when calling Windows, but you lose the POSIX
|
|
|
1216 emulation layer, which makes Unix programs harder to port. (But this is
|
|
|
1217 irrelevant for XEmacs since it's already ported to Win32.)
|
|
|
1218
|
|
|
1219 See @uref{http://www.mingw.org/} for more information on MinGW.
|
|
|
1220
|
|
|
1221 @node Q1.2.6, Q1.2.7, Q1.2.5, Introduction
|
|
|
1222 @unnumberedsubsec Q1.2.6: What are the differences between the various MS Windows emacsen?
|
|
|
1223
|
|
|
1224 XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing.
|
|
|
1225 Could you briefly explain the differences between them?
|
|
|
1226
|
|
|
1227 Here is a recount of various Emacs versions running on MS Windows:
|
|
|
1228
|
|
|
1229 @itemize @bullet
|
|
|
1230
|
|
|
1231 @item
|
|
|
1232 XEmacs
|
|
|
1233
|
|
|
1234 @itemize @minus
|
|
|
1235
|
|
|
1236 @item
|
|
|
1237 Beginning with XEmacs 19.12, XEmacs' architecture was redesigned
|
|
|
1238 in such a way to allow clean support of multiple window systems. At
|
|
|
1239 this time the TTY support was added, making X and TTY the first two
|
|
|
1240 "window systems" supported by XEmacs. The 19.12 design is the basis for
|
|
|
1241 the current native MS Windows code.
|
|
|
1242
|
|
|
1243 @item
|
|
|
1244 Some time during 1997, David Hobley (soon joined by Marc Paquette)
|
|
|
1245 imported some of the NT-specific portions of GNU Emacs, making XEmacs
|
|
|
1246 with X support compile under Windows NT, and creating the "X" port.
|
|
|
1247
|
|
|
1248 @item
|
|
|
1249 Several months later, Jonathan Harris sent out initial patches to use
|
|
|
1250 the Win32 API, thus creating the native port. Since then, various
|
|
|
1251 people have contributed, including Kirill M. Katsnelson (contributed
|
|
|
1252 support for menubars, subprocesses and network, as well as loads of
|
|
|
1253 other code), Andy Piper (ported XEmacs to Cygwin environment,
|
|
|
1254 contributed Windows unexec, Windows-specific glyphs and toolbars code,
|
|
|
1255 and more), Ben Wing (loads of improvements; primary MS Windows developer
|
|
|
1256 since 2000), Jeff Sparkes (contributed scrollbars support) and many
|
|
|
1257 others.
|
|
|
1258 @end itemize
|
|
|
1259
|
|
|
1260 @item
|
|
|
1261 NT Emacs
|
|
|
1262
|
|
|
1263 @itemize @minus
|
|
|
1264
|
|
|
1265 @item
|
|
|
1266 NT Emacs was an early version of GNU Emacs 19 modified to compile and
|
|
|
1267 run under MS Windows 95 and NT using the native Win32 API. It was
|
|
|
1268 written by Geoff Voelker, and has long since been incorporated into
|
|
|
1269 the mainline GNU Emacs distribution.
|
|
|
1270 @end itemize
|
|
|
1271
|
|
|
1272 @item
|
|
|
1273 Win-Emacs
|
|
|
1274
|
|
|
1275 @itemize @minus
|
|
|
1276
|
|
|
1277 @item
|
|
|
1278 Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X
|
|
|
1279 compatibility libraries. Win-Emacs was written by Ben Wing. The MS
|
|
|
1280 Windows code never made it back to Lucid Emacs, and its creator (Pearl
|
|
|
1281 Software) has long since gone out of business.
|
|
|
1282 @end itemize
|
|
|
1283
|
|
|
1284 @item
|
|
|
1285 GNU Emacs for DOS
|
|
|
1286
|
|
|
1287 @itemize @minus
|
|
|
1288
|
|
|
1289 @item
|
|
|
1290 GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
|
|
|
1291 port of GCC). Such an Emacs is heavily underfeatured, because it does
|
|
|
1292 not support long file names, lacks proper subprocesses support, and
|
|
|
1293 is far too big compared with typical DOS editors.
|
|
|
1294 @end itemize
|
|
|
1295
|
|
|
1296 @item
|
|
|
1297 GNU Emacs compiled with Win32
|
|
|
1298
|
|
|
1299 @itemize @minus
|
|
|
1300
|
|
|
1301 @item
|
|
|
1302 Starting with GNU Emacs 19.30, it has been possible to compile GNU Emacs
|
|
|
1303 under MS Windows using the DJGPP compiler and X libraries. The result
|
|
|
1304 is very similar to GNU Emacs compiled under MS DOS, only it works
|
|
|
1305 somewhat better because it runs in 32-bit mode, makes use of all the
|
|
|
1306 system memory, supports long file names, etc.
|
|
|
1307 @end itemize
|
|
|
1308
|
|
|
1309 @end itemize
|
|
|
1310
|
|
|
1311 @node Q1.2.7, Q1.2.8, Q1.2.6, Introduction
|
|
|
1312 @unnumberedsubsec Q1.2.7: How does the port cope with differences in the Windows user interface?
|
|
|
1313
|
|
|
1314 The XEmacs (and Emacs in general) user interface is pretty different
|
|
|
1315 from what is expected of a typical MS Windows program. How does the MS
|
|
|
1316 Windows port cope with it?
|
|
|
1317
|
|
|
1318 As a general rule, we follow native MS Windows conventions as much as
|
|
|
1319 possible. 21.4 is a fairly complete Windows application, supporting
|
|
|
1320 native printing, system file dialog boxes, tool tips, etc. In cases
|
|
|
1321 where there's a clear UI conflict, we currently use normal Unix XEmacs
|
|
|
1322 behavior by default, but make sure the MS Windows "look and feel" (mark
|
|
|
1323 via shift-arrow, self-inserting deletes region, Alt selects menu items,
|
|
|
1324 etc.) is easily configurable (respectively: using the variable
|
|
|
1325 @code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact
|
|
|
1326 the default in these versions], or the @file{pc-select} package; using
|
|
|
1327 the @file{pending-del} package; and setting the variable
|
|
|
1328 @code{menu-accelerator-enabled} to @code{menu-force} in 21.4 and above).
|
|
|
1329 In fact, if you use the sample @file{init.el} file as your init file,
|
|
|
1330 you will get all these behaviors automatically turned on.
|
|
|
1331
|
|
|
1332 In future versions, some of these features might be turned on by
|
|
|
1333 default in the MS Windows environment.
|
|
|
1334
|
|
|
1335 @node Q1.2.8, Q1.2.9, Q1.2.7, Introduction
|
|
|
1336 @unnumberedsubsec Q1.2.8: Is there a port of XEmacs to the Macintosh?
|
|
|
1337
|
|
|
1338 Yes.
|
|
|
1339
|
|
|
1340 XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly
|
|
|
1341 will not feel very much like a Mac application as it has no Mac-specific
|
|
|
1342 code in it.
|
|
|
1343
|
|
|
1344 There is also a port of XEmacs 19.14 that works on all recent versions
|
|
|
1345 of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com,
|
|
|
1346 Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY
|
|
|
1347 mode only (one single Macintosh window, 25 colors), but has a large
|
|
|
1348 number of Mac-specific additions. It's available at
|
|
|
1349 @uref{http://homepage.mac.com/pjarvis/xemacs.html}.
|
|
|
1350
|
|
|
1351 @node Q1.2.9, Q1.2.10, Q1.2.8, Introduction
|
|
2559
|
1352 @unnumberedsubsec Q1.2.9: Is there a port of XEmacs to MS-DOS?
|
|
|
1353
|
|
|
1354 No. We have never supported running on MS-DOS or Windows 3.1, and in
|
|
|
1355 fact have long since deleted all MS-DOS-related code. We're not
|
|
|
1356 particularly interested in patches for these platforms, as they would
|
|
|
1357 introduce huge amounts of code clutter due to the woefully
|
|
|
1358 underfeatured nature of these systems. (See GNU Emacs for a port to
|
|
|
1359 MS-DOS.)
|
|
2537
|
1360
|
|
|
1361 @node Q1.2.10, Q1.2.11, Q1.2.9, Introduction
|
|
2559
|
1362 @unnumberedsubsec Q1.2.10: Is there a port of XEmacs to OS/2?
|
|
2537
|
1363
|
|
|
1364 No, but Alexander Nikolaev <avn_1251@@mail.ru> was at one point
|
|
|
1365 working on it.
|
|
|
1366
|
|
2559
|
1367 @node Q1.2.11, Q1.2.12, Q1.2.10, Introduction
|
|
|
1368 @unnumberedsubsec Q1.2.11: Is there a port of XEmacs to NextStep?
|
|
2537
|
1369
|
|
|
1370 Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did
|
|
|
1371 the port of GNU Emacs to NeXTstep and expressed interest in doing the
|
|
|
1372 XEmacs port, but never went any farther.
|
|
|
1373
|
|
2559
|
1374 @node Q1.2.12, Q1.3.1, Q1.2.11, Introduction
|
|
|
1375 @unnumberedsubsec Q1.2.12: Is there a port of XEmacs to VMS?
|
|
2537
|
1376
|
|
|
1377 VMS has never been supported by XEmacs. In fact, all the old VMS code
|
|
|
1378 inherited from GNU Emacs has been removed. Sorry, all you VMS fans
|
|
|
1379 out there.
|
|
|
1380
|
|
|
1381 @unnumberedsec 1.3: Getting Started
|
|
|
1382
|
|
2559
|
1383 @node Q1.3.1, Q1.3.2, Q1.2.12, Introduction
|
|
2537
|
1384 @unnumberedsubsec Q1.3.1: What is an @file{init.el} or @file{.emacs} and is there a sample one?
|
|
|
1385
|
|
|
1386 The @file{init.el} or @file{.emacs} file is used to customize XEmacs to
|
|
|
1387 your tastes. Starting in 21.4, the preferred location for the init file
|
|
|
1388 is @file{~/.xemacs/init.el}; in previous versions, it was
|
|
|
1389 @file{~/.emacs}. 21.4 still accepts the old location, but the first
|
|
|
1390 time you run it, it will ask to migrate your file to the new location.
|
|
|
1391 If you answer yes, the file will be moved, and a "compatibility"
|
|
|
1392 @file{.emacs} file will be placed in the old location so that you can
|
|
|
1393 still run older versions of XEmacs, and versions of GNU Emacs, which
|
|
|
1394 expect the old location. The @file{.emacs} file present is just a stub
|
|
|
1395 that loads the real file in @file{~/.xemacs/init.el}.
|
|
|
1396
|
|
|
1397 No two init files are alike, nor are they expected to be alike, but
|
|
|
1398 that's the point. The XEmacs distribution contains an excellent starter
|
|
|
1399 example in the @file{etc/} directory called @file{sample.init.el}
|
|
|
1400 (starting in 21.4) or @file{sample.emacs} in older versions. Copy this
|
|
|
1401 file from there to @file{~/.xemacs/init.el} (starting in 21.4) or
|
|
|
1402 @file{~/.emacs} in older versions, where @samp{~} means your home
|
|
|
1403 directory, of course. Then edit it to suit.
|
|
|
1404
|
|
|
1405 You may bring the @file{sample.init.el} or @file{sample.emacs} file into
|
|
|
1406 an XEmacs buffer from the menubar. (The menu entry for it is always
|
|
|
1407 under the @samp{Help} menu, but its location under that has changed in
|
|
|
1408 various versions. Recently, look under the @samp{Samples} submenu.) To
|
|
|
1409 determine the location of the @file{etc/} directory type the command
|
|
|
1410 @kbd{C-h v data-directory @key{RET}}.
|
|
|
1411
|
|
|
1412 @node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
|
|
|
1413 @unnumberedsubsec Q1.3.2: Where do I put my @file{init.el} file?
|
|
|
1414
|
|
|
1415 @file{init.el} is the name of the init file starting with 21.4, and is
|
|
|
1416 located in the subdirectory @file{.xemacs/} of your home directory. In
|
|
|
1417 prior versions, the init file is called @file{.emacs} and is located in
|
|
|
1418 your home directory.
|
|
|
1419
|
|
|
1420 Your home directory under Windows is determined by the @samp{HOME}
|
|
|
1421 environment variable. If this is not set, it defaults to @samp{C:\}.
|
|
|
1422 To set this variable, modify @file{AUTOEXEC.BAT} under Windows 95/98, or
|
|
|
1423 select @samp{Control Panel->System->Advanced->Environment Variables...}
|
|
|
1424 under Windows NT/2000.
|
|
|
1425
|
|
|
1426 @node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
|
|
|
1427 @unnumberedsubsec Q1.3.3: Can I use the same @file{init.el} with the other Emacs?
|
|
|
1428
|
|
|
1429 Yes. The sample @file{init.el} included in the XEmacs
|
|
|
1430 distribution will show you how to handle different versions and flavors
|
|
|
1431 of Emacs.
|
|
|
1432
|
|
|
1433 @node Q1.3.4, Q1.3.5, Q1.3.3, Introduction
|
|
|
1434 @unnumberedsubsec Q1.3.4: Any good XEmacs tutorials around?
|
|
|
1435
|
|
|
1436 There's the XEmacs tutorial available from the Help Menu under
|
|
|
1437 @samp{Help->Tutorials}, or by typing @kbd{C-h t}. To check whether
|
|
|
1438 it's available in a non-english language, type @kbd{C-u C-h t TAB}, type
|
|
|
1439 the first letters of your preferred language, then type @key{RET}.
|
|
|
1440
|
|
|
1441 @comment There's an Emacs Lisp tutorial at
|
|
|
1442 @comment
|
|
|
1443 @comment @example
|
|
|
1444 @comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
|
|
|
1445 @comment @end example
|
|
|
1446 @comment
|
|
|
1447 @comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
|
|
|
1448 @comment page at
|
|
|
1449 @comment @iftex
|
|
|
1450 @comment @*
|
|
|
1451 @comment @end iftex
|
|
|
1452 @comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}.
|
|
|
1453
|
|
|
1454 @node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
|
|
|
1455 @unnumberedsubsec Q1.3.5: May I see an example of a useful XEmacs Lisp function?
|
|
|
1456
|
|
|
1457 The following function does a little bit of everything useful. It does
|
|
|
1458 something with the prefix argument, it examines the text around the
|
|
|
1459 cursor, and it's interactive so it may be bound to a key. It inserts
|
|
|
1460 copies of the current word the cursor is sitting on at the cursor. If
|
|
|
1461 you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will
|
|
|
1462 insert 3 copies.
|
|
|
1463
|
|
|
1464 @lisp
|
|
|
1465 (defun double-word (count)
|
|
|
1466 "Insert a copy of the current word underneath the cursor"
|
|
|
1467 (interactive "*p")
|
|
|
1468 (let (here there string)
|
|
|
1469 (save-excursion
|
|
|
1470 (forward-word -1)
|
|
|
1471 (setq here (point))
|
|
|
1472 (forward-word 1)
|
|
|
1473 (setq there (point))
|
|
|
1474 (setq string (buffer-substring here there)))
|
|
|
1475 (while (>= count 1)
|
|
|
1476 (insert string)
|
|
|
1477 (decf count))))
|
|
|
1478 @end lisp
|
|
|
1479
|
|
|
1480 The best way to see what is going on here is to let XEmacs tell you.
|
|
|
1481 Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor
|
|
|
1482 sitting just to the right of the function you want explained. Eg. move
|
|
|
1483 the cursor to the SPACE between @code{interactive} and @samp{"*p"} and
|
|
|
1484 hit @kbd{C-h f} to see what the function @code{interactive} does. Doing
|
|
|
1485 this will tell you that the @code{*} requires a writable buffer, and
|
|
|
1486 @code{p} converts the prefix argument to a number, and
|
|
|
1487 @code{interactive} allows you to execute the command with @kbd{M-x}.
|
|
|
1488
|
|
|
1489 @node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
|
|
|
1490 @unnumberedsubsec Q1.3.6: And how do I bind it to a key?
|
|
|
1491
|
|
|
1492 To bind to a key do:
|
|
|
1493
|
|
|
1494 @lisp
|
|
|
1495 (global-set-key "\C-cd" 'double-word)
|
|
|
1496 @end lisp
|
|
|
1497
|
|
|
1498 Or interactively, @kbd{M-x global-set-key} and follow the prompts.
|
|
|
1499
|
|
|
1500 @node Q1.3.7, Q1.3.8, Q1.3.6, Introduction
|
|
|
1501 @unnumberedsubsec Q1.3.7: What's the difference between a macro and a function?
|
|
|
1502
|
|
|
1503 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual:
|
|
|
1504
|
|
|
1505 @dfn{Macros} enable you to define new control constructs and other
|
|
|
1506 language features. A macro is defined much like a function, but instead
|
|
|
1507 of telling how to compute a value, it tells how to compute another Lisp
|
|
|
1508 expression which will in turn compute the value. We call this
|
|
|
1509 expression the @dfn{expansion} of the macro.
|
|
|
1510
|
|
|
1511 Macros can do this because they operate on the unevaluated expressions
|
|
|
1512 for the arguments, not on the argument values as functions do. They can
|
|
|
1513 therefore construct an expansion containing these argument expressions
|
|
|
1514 or parts of them.
|
|
|
1515
|
|
|
1516 Do not confuse the two terms with @dfn{keyboard macros}, which are
|
|
|
1517 another matter, entirely. A keyboard macro is a key bound to several
|
|
|
1518 other keys. Refer to manual for details.
|
|
|
1519
|
|
|
1520 @node Q1.3.8, Q1.4.1, Q1.3.7, Introduction
|
|
|
1521 @unnumberedsubsec Q1.3.8: What is @code{Custom}?
|
|
|
1522
|
|
|
1523 @code{Custom} is a system for customizing XEmacs options.
|
|
|
1524
|
|
|
1525 You can access @code{Advanced (Customize)} from the @code{Options} menu
|
|
|
1526 or invoking one of customize commands by typing eg.
|
|
|
1527 @kbd{M-x customize}, @kbd{M-x customize-face},
|
|
|
1528 @kbd{M-x customize-variable} or @kbd{M-x customize-apropos}.
|
|
|
1529
|
|
|
1530 There is also new @samp{browser} mode for Customize.
|
|
|
1531 Try it out with @kbd{M-x customize-browse}
|
|
|
1532
|
|
|
1533 @unnumberedsec 1.4: Getting Help
|
|
|
1534
|
|
|
1535 @node Q1.4.1, Q1.4.2, Q1.3.8, Introduction
|
|
|
1536 @unnumberedsubsec Q1.4.1: Where can I get help?
|
|
|
1537
|
|
|
1538 Probably the easiest way, if everything is installed, is to use Info, by
|
|
|
1539 pressing @kbd{C-h i}, or looking for an Info item on the
|
|
|
1540 Help Menu. @kbd{M-x apropos} can be used to look for particular commands.
|
|
|
1541
|
|
|
1542 For items not found in the manual, try reading this FAQ
|
|
|
1543 and reading the Usenet group comp.emacs.xemacs.
|
|
|
1544
|
|
|
1545 If you choose to post to a newsgroup, @strong{please use
|
|
|
1546 comp.emacs.xemacs}. Please do not post XEmacs related questions to
|
|
|
1547 gnu.emacs.help.
|
|
|
1548
|
|
|
1549 If you cannot post or read Usenet news, there is a corresponding mailing
|
|
|
1550 list @email{xemacs-news@@xemacs.org} which is available. It can be
|
|
|
1551 subscribed to via the Mailman Web interface or by sending mail to to
|
|
|
1552 @email{xemacs-news-request@@xemacs.org} with @samp{subscribe} in the
|
|
|
1553 body of the message. See also
|
|
|
1554 @uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a
|
|
|
1555 subscription, you may use the @email{xemacs-news-request@@xemacs.org}
|
|
|
1556 address or the Web interface. Send a message with a subject of
|
|
|
1557 @samp{unsubscribe} to be removed.
|
|
|
1558
|
|
|
1559 @node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
|
|
|
1560 @unnumberedsubsec Q1.4.2: Which mailing lists are there?
|
|
|
1561
|
|
|
1562 For complete, up-to-date info on the lists and how to subscribe, see
|
|
|
1563 @uref{http://www.xemacs.org/Lists/}.
|
|
|
1564
|
|
|
1565 @table @samp
|
|
|
1566
|
|
|
1567 @item comp.emacs.xemacs
|
|
|
1568 is a Usenet newsgroup
|
|
|
1569 for XEmacs users to discuss problems and issues that arise
|
|
|
1570 for them. It's not generally an appropriate place to ask
|
|
|
1571 about apparent bugs (use @samp{xemacs-beta}), or future plans
|
|
|
1572 (use @samp{xemacs-design}).
|
|
|
1573
|
|
|
1574 @item xemacs-announce
|
|
|
1575 is a read-only, low
|
|
|
1576 volume list for announcements concerning the XEmacs project
|
|
|
1577 and new releases of the XEmacs software.
|
|
|
1578
|
|
|
1579 @item xemacs-beta
|
|
2559
|
1580 is an open list for bug reports about beta versions of XEmacs. This
|
|
|
1581 includes the bug reports themselves, by both users and developers, as
|
|
|
1582 well as queries, follow-ups, and discussions further determining their
|
|
|
1583 nature and status. This is the primary channel for this kind of
|
|
|
1584 discussion; related code changes will usually not be applied until
|
|
|
1585 they have been discussed here. When such discussions touch on
|
|
|
1586 significant changes to the code (in particular, structural changes),
|
|
|
1587 or on changes to API's or external functionality, they should be moved
|
|
|
1588 to @samp{xemacs-design}. Requests and proposals for non-bug-related
|
|
|
1589 changes do not belong on @samp{xemacs-beta}, and should be sent to
|
|
|
1590 @samp{xemacs-design} instead.
|
|
2537
|
1591
|
|
|
1592 @item xemacs-beta-ja
|
|
|
1593 is an open list for bug
|
|
|
1594 reports and design discussion related to Mule features,
|
|
|
1595 including Japanese handling, in beta versions of XEmacs.
|
|
|
1596 Japanese is the preferred language of discussion. For most
|
|
|
1597 timely presentation to reviewers, please consider sending
|
|
|
1598 appropriate discussion to @samp{xemacs-mule} or
|
|
|
1599 @samp{xemacs-design} in English when convenient for
|
|
|
1600 the participants in discussion. When possible, bug reports
|
|
|
1601 not related to Mule (including Japanese) should be reported on
|
|
|
1602 @samp{xemacs-beta} in English.
|
|
|
1603
|
|
|
1604 @item xemacs-buildreports
|
|
|
1605 is an open list for
|
|
|
1606 submission of build-reports on beta versions of XEmacs. For
|
|
|
1607 information on what the build-reports should contain, please
|
|
|
1608 see the `etc/BETA' file which is included in each beta
|
|
|
1609 distribution.
|
|
|
1610
|
|
|
1611 @item xemacs-cvs
|
|
|
1612 is a read-only list for notices
|
|
|
1613 and information on what has been committed to the XEmacs CVS
|
|
|
1614 trees, by whom, and for what.
|
|
|
1615
|
|
|
1616 @item xemacs-design
|
|
|
1617 is an open list for
|
|
|
1618 discussing the design of XEmacs. This includes discussion
|
|
|
1619 about planned and ongoing changes to functionality and API
|
|
|
1620 changes and additions as well as requests for them. This is
|
|
|
1621 the primary channel for this kind of discussion; related code
|
|
|
1622 changes will usually not be applied until they have been
|
|
|
1623 discussed here. This does not include bug reports, which go
|
|
|
1624 to @samp{xemacs-beta}.
|
|
|
1625
|
|
|
1626 @item xemacs-mule
|
|
|
1627 is an open mailing list for
|
|
|
1628 discussion of International extensions to XEmacs including
|
|
|
1629 Mule, XIM, I18n issues, etc, and is not confined to
|
|
|
1630 developmental issues. This list is not restricted to
|
|
|
1631 English, postings in all languages are welcome.
|
|
|
1632
|
|
|
1633 @item xemacs-news
|
|
|
1634 is an open list for discussion
|
|
|
1635 and bug reporting for XEmacs. This mailing list is
|
|
|
1636 bi-directionally gatewayed with the USENET newsgroup
|
|
|
1637 comp.emacs.xemacs.
|
|
|
1638
|
|
|
1639 @item xemacs-nt
|
|
|
1640 is a developers-only mailing
|
|
|
1641 list and is intended for people who wish to work actively on
|
|
|
1642 the porting of XEmacs to Microsoft Windows NT and Microsoft
|
|
|
1643 Windows '95.
|
|
|
1644
|
|
|
1645 @item xemacs-patches
|
|
|
1646 is an open, moderated
|
|
|
1647 list for submission of patches to the XEmacs distribution
|
|
|
1648 and its packages. Anyone may subscribe or submit to
|
|
|
1649 xemacs-patches, but all submissions are reviewed by the list
|
|
|
1650 moderator before they are distributed to the
|
|
|
1651 list. Discussion is not appropriate on xemacs-patches.
|
|
|
1652
|
|
|
1653 @item xemacs-users-ja
|
|
|
1654 is an open list for
|
|
|
1655 discussion and bug reporting for XEmacs. Japanese is the
|
|
|
1656 preferred language of discussion. It is not gated to
|
|
|
1657 comp.emacs.xemacs or the @samp{xemacs} list. For
|
|
|
1658 fastest response, bugs not specifically related to Japanese
|
|
|
1659 or Mule features should be reported on
|
|
|
1660 @samp{xemacs-beta} (in English).
|
|
|
1661
|
|
|
1662 @item xemacs-users-ru
|
|
|
1663 is an open list for
|
|
|
1664 discussion and bug reporting for XEmacs. Russian is the
|
|
|
1665 preferred language of discussion. It is not gated to
|
|
|
1666 comp.emacs.xemacs or the @samp{xemacs} list. For
|
|
|
1667 fastest response, bugs not specifically related to Russian
|
|
|
1668 or Mule features should be reported on
|
|
|
1669 @samp{xemacs-beta} (in English).
|
|
|
1670 @end table
|
|
|
1671
|
|
|
1672 @node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
|
|
|
1673 @unnumberedsubsec Q1.4.3: Where are the mailing lists archived?
|
|
|
1674
|
|
|
1675 The archives can be found at @uref{http://list-archive.xemacs.org}
|
|
|
1676
|
|
|
1677 @node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
|
|
|
1678 @unnumberedsubsec Q1.4.4: How can I get two instances of info?
|
|
|
1679
|
|
|
1680 Before 21.4, you can't. The @code{info} package does not provide for
|
|
|
1681 multiple info buffers. In 21.4, this should be fixed. #### how?
|
|
|
1682
|
|
|
1683 @node Q1.4.5, Q1.5.1, Q1.4.4, Introduction
|
|
|
1684 @unnumberedsubsec Q1.4.5: How do I add new Info directories?
|
|
|
1685
|
|
|
1686 You use something like:
|
|
|
1687
|
|
|
1688 @lisp
|
|
|
1689 (setq Info-directory-list (cons
|
|
|
1690 (expand-file-name "~/info")
|
|
|
1691 Info-default-directory-list))
|
|
|
1692 @end lisp
|
|
|
1693
|
|
|
1694 @email{davidm@@prism.kla.com, David Masterson} writes:
|
|
|
1695
|
|
|
1696 @quotation
|
|
|
1697 Emacs Info and XEmacs Info do many things differently. If you're trying to
|
|
|
1698 support a number of versions of Emacs, here are some notes to remember:
|
|
|
1699
|
|
|
1700 @enumerate
|
|
|
1701 @item
|
|
|
1702 Emacs Info scans @code{Info-directory-list} from right-to-left while
|
|
|
1703 XEmacs Info reads it from left-to-right, so append to the @emph{correct}
|
|
|
1704 end of the list.
|
|
|
1705
|
|
|
1706 @item
|
|
|
1707 Use @code{Info-default-directory-list} to initialize
|
|
|
1708 @code{Info-directory-list} @emph{if} it is available at startup, but not
|
|
|
1709 all Emacsen define it.
|
|
|
1710
|
|
|
1711 @item
|
|
|
1712 Emacs Info looks for a standard @file{dir} file in each of the
|
|
|
1713 directories scanned from #1 and magically concatenates them together.
|
|
|
1714
|
|
|
1715 @item
|
|
|
1716 XEmacs Info looks for a @file{localdir} file (which consists of just the
|
|
|
1717 menu entries from a @file{dir} file) in each of the directories scanned
|
|
|
1718 from #1 (except the first), does a simple concatenation of them, and
|
|
|
1719 magically attaches the resulting list to the end of the menu in the
|
|
|
1720 @file{dir} file in the first directory.
|
|
|
1721 @end enumerate
|
|
|
1722
|
|
|
1723 Another alternative is to convert the documentation to HTML with
|
|
|
1724 texi2html and read it from a web browser like Lynx or W3.
|
|
|
1725 @end quotation
|
|
|
1726
|
|
|
1727 @unnumberedsec 1.5: Contributing to XEmacs
|
|
|
1728
|
|
|
1729 @node Q1.5.1, Q1.5.2, Q1.4.5, Introduction
|
|
|
1730 @unnumberedsubsec Q1.5.1: How do I submit changes to the FAQ?
|
|
|
1731
|
|
|
1732 The FAQ is actively maintained and modified regularly. All links should
|
|
|
1733 be up to date. Unfortunately, some of the information is out of date --
|
|
|
1734 a situation which the FAQ maintainer is working on. All submissions are
|
|
|
1735 welcome, please e-mail submissions to @email{faq@@xemacs.org, XEmacs FAQ
|
|
|
1736 maintainers}.
|
|
|
1737
|
|
|
1738 Please make sure that @samp{XEmacs FAQ} appears on the Subject: line.
|
|
|
1739 If you think you have a better way of answering a question, or think a
|
|
|
1740 question should be included, we'd like to hear about it. Questions and
|
|
|
1741 answers included into the FAQ will be edited for spelling and grammar
|
|
|
1742 and will be attributed. Answers appearing without attribution are
|
|
|
1743 either from versions of the FAQ dated before May 1996 or are from
|
|
|
1744 previous FAQ maintainers. Answers quoted from Usenet news articles will
|
|
|
1745 always be attributed, regardless of the author.
|
|
|
1746
|
|
|
1747 @node Q1.5.2, Q1.5.3, Q1.5.1, Introduction
|
|
|
1748 @unnumberedsubsec Q1.5.2: How do I become a beta tester?
|
|
|
1749
|
|
|
1750 Send an email message to @email{xemacs-beta-request@@xemacs.org} with
|
|
|
1751 the line @samp{subscribe} in the body of the message.
|
|
|
1752
|
|
|
1753 Be prepared to get your hands dirty, as beta testers are expected to
|
|
|
1754 identify problems as best they can.
|
|
|
1755
|
|
2559
|
1756 @node Q1.5.3, Q1.5.4, Q1.5.2, Introduction
|
|
2537
|
1757 @unnumberedsubsec Q1.5.3: How do I contribute to XEmacs itself?
|
|
|
1758
|
|
|
1759 It depends on the knowledge and time you possess. If you are able, by
|
|
|
1760 all means become a beta tester (@pxref{Q1.5.2}). If you are a
|
|
|
1761 programmer, try to build XEmacs and see if you can improve it.
|
|
|
1762
|
|
|
1763 Otherwise, you can still help by using XEmacs as your everyday editor
|
|
|
1764 (for pre-built binary versions, @pxref{Q1.1.2}) and reporting bugs you
|
|
|
1765 find to the mailing list.
|
|
|
1766
|
|
|
1767 Another area where we need help is the documentation: We need good
|
|
|
1768 documentation for building XEmacs and for using it. This FAQ is a
|
|
|
1769 small step in that direction.
|
|
|
1770
|
|
|
1771 Ben Wing @email{ben@@xemacs.org} writes:
|
|
|
1772
|
|
|
1773 @quotation
|
|
|
1774 BTW if you have a wish list of things that you want added, you have to
|
|
|
1775 speak up about it! More specifically, you can do the following if you
|
|
|
1776 want a feature added (in increasing order of usefulness):
|
|
|
1777
|
|
|
1778 @itemize @bullet
|
|
|
1779 @item
|
|
|
1780 Make a posting about a feature you want added.
|
|
|
1781
|
|
|
1782 @item
|
|
|
1783 Become a beta tester and make more postings about those same features.
|
|
|
1784
|
|
|
1785 @item
|
|
|
1786 Convince us that you're going to use the features in some cool and
|
|
|
1787 useful way.
|
|
|
1788
|
|
|
1789 @item
|
|
|
1790 Come up with a clear and well-thought-out API concerning the features.
|
|
|
1791
|
|
|
1792 @item
|
|
|
1793 Write the code to implement a feature and send us a patch.
|
|
|
1794 @end itemize
|
|
|
1795
|
|
|
1796 (not that we're necessarily requiring you to write the code, but we can
|
|
|
1797 always hope :)
|
|
|
1798 @end quotation
|
|
|
1799
|
|
2559
|
1800 @node Q1.5.4, Q1.5.5, Q1.5.3, Introduction
|
|
|
1801 @unnumberedsubsec Q1.5.4: How do I get started developing XEmacs?
|
|
|
1802
|
|
|
1803 First, get yourself set up under CVS so that you can access the CVS
|
|
|
1804 repositories containing the XEmacs sources and the XEmacs packages.
|
|
|
1805
|
|
|
1806 Next, set up your layout. This is important, as a good layout will
|
|
|
1807 facilitate getting things done efficiently, while a bad layout will could
|
|
|
1808 lead to disaster, as you can't figure out which code is the most recent,
|
|
|
1809 which can be thrown away, etc. We suggest the following layout: (feel free
|
|
|
1810 to make changes)
|
|
|
1811
|
|
|
1812 @itemize @bullet
|
|
|
1813 @item
|
|
|
1814 Everything goes under @file{/src/xemacs} (use a different directory if
|
|
|
1815 you want). From now, instead of saying @file{/src/xemacs}, we use
|
|
|
1816 @file{<xsrc-top>}, to make it easier in case someone picked a
|
|
|
1817 different directory.
|
|
|
1818
|
|
|
1819 @item
|
|
|
1820 Package source is in @file{<xsrc-top>/package-src}.
|
|
|
1821
|
|
|
1822 @item
|
|
|
1823 Installed packages go under @file{<xsrc-top>/xemacs-packages}, and
|
|
|
1824 @file{<xsrc-top>/mule-packages}.
|
|
|
1825
|
|
|
1826 @item
|
|
|
1827 A "workspace" is a complete copy of the sources, in which you do work of
|
|
|
1828 a particular kind. Workspaces can be differentiated by which branch of
|
|
|
1829 the source tree they extend off of -- usually either the stable or
|
|
|
1830 experimental, unless other branches have been created (for example, Ben
|
|
|
1831 created a branch for his Mule work because (1) the project was long-term
|
|
|
1832 and involved an enormous number of changes, (2) people wanted to be able
|
|
|
1833 to look at what his work in progress, and (3) he wanted to be able to
|
|
|
1834 check things in and in general use source-code control, since it was a
|
|
|
1835 long-term project). Workspaces are also differentiated in what their
|
|
|
1836 purpose is -- general working workspace, workspace for particular
|
|
|
1837 projects, workspace keeping the latest copy of the code in one of the
|
|
|
1838 branches without mods, etc.
|
|
|
1839
|
|
|
1840 @item
|
|
|
1841 Various workspaces are subdirectories under @file{<xsrc-top>}, e.g.:
|
|
|
1842
|
|
|
1843 @itemize @bullet
|
|
|
1844 @item
|
|
|
1845 @file{<xsrc-top>/working} (the workspace you're actively working on,
|
|
|
1846 periodically synched up with the latest trunk)
|
|
|
1847
|
|
|
1848 @item
|
|
|
1849 @file{<xsrc-top>/stable} (for making changes to the stable version of
|
|
|
1850 XEmacs, which sits on a branch)
|
|
|
1851
|
|
|
1852 @item
|
|
|
1853 @file{<xsrc-top>/unsigned-removal} (a workspace for a specific, difficult
|
|
|
1854 task that's going to affect lots of source and take a long time, and
|
|
|
1855 so best done in its own workspace without the interference of other
|
|
|
1856 work you're doing. Also, you can commit just this one large change,
|
|
|
1857 separate from all the other changes).
|
|
|
1858
|
|
|
1859 @item
|
|
|
1860 @file{<xsrc-top>/latest} (a copy of the latest sources on the trunk,
|
|
|
1861 i.e. the experimental version of XEmacs, with no patches in it;
|
|
|
1862 either update it periodically, by hand, or set up a cron job to do it
|
|
|
1863 automatically). Set it up so it can be built, and build it so you
|
|
|
1864 have a working XEmacs. (Building it might also go into the cron job.)
|
|
|
1865
|
|
|
1866 This workspace serves a number of purposes:
|
|
|
1867 @enumerate
|
|
|
1868 @item
|
|
|
1869 You always have a recent version of XEmacs you can compare
|
|
|
1870 against when something you're working on breaks. It's true
|
|
|
1871 that you can do this with cvs diff, but when you need to do
|
|
|
1872 some serious investigation, this method just fails.
|
|
|
1873 @item
|
|
|
1874 You (almost) always have a working, up-to-date executable that
|
|
|
1875 can be used when your executable is crashing and you need to
|
|
|
1876 keep developing it, or when you need an `xemacs' to build
|
|
|
1877 packages, etc.
|
|
|
1878 @item
|
|
|
1879 When creating new workspaces, you can just copy the `latest'
|
|
|
1880 workspace using GNU @code{cp -a}. You have all the .elc's built,
|
|
|
1881 everything else probably configured, any spare files in place
|
|
|
1882 (e.g. some annoying xpm.dll under Windows, etc.).
|
|
|
1883 @end enumerate
|
|
|
1884
|
|
|
1885 @item
|
|
|
1886 @file{<xsrc-top>/latest-stable/} (equivalent to @file{<xsrc-top>/latest/}, but
|
|
|
1887 for the Stable branch of XEmacs, rather than the Experimental branch
|
|
|
1888 of XEmacs). This may or may not be necessary depending on how much
|
|
|
1889 development you do of the stable branch.
|
|
|
1890 @end itemize
|
|
|
1891
|
|
|
1892 @item
|
|
|
1893 @file{<xsrc-top>/xemacsweb} is a workspace for working on the XEmacs
|
|
|
1894 web site.
|
|
|
1895
|
|
|
1896 @item
|
|
|
1897 @file{<xsrc-top>/in-patches} for patches received from email and saved
|
|
|
1898 to files.
|
|
|
1899
|
|
|
1900 @item
|
|
|
1901 @file{<xsrc-top>/out-patches} for locally-generated patches to be sent
|
|
|
1902 to @email{xemacs-patches@@xemacs.org}. Less useful now that the
|
|
|
1903 patcher util has been developed.
|
|
|
1904
|
|
|
1905 @item
|
|
|
1906 @file{<xsrc-top>/build}, for build trees when compiling and testing XEmacs with
|
|
|
1907 various configuration options turned off and on. The scripts in
|
|
|
1908 xemacs-builds/ben (see below) can be used to automate building XEmacs
|
|
|
1909 workspaces with many different configuration options and automatically
|
|
|
1910 filtering out the normal output so that you see only the abnormal
|
|
|
1911 output.
|
|
|
1912
|
|
|
1913 @item
|
|
|
1914 @file{<xsrc-top>/xemacs-builds}, for the xemacs-builds module, which you need
|
|
|
1915 to check out separately in CVS. This contains scripts used for building
|
|
|
1916 XEmacs, automating and simplifying using CVS, etc. Under various
|
|
|
1917 people's directories are their own build and other scripts. The
|
|
|
1918 currently most-maintained scripts are under ben/, where there are easily
|
|
|
1919 configurable scripts that can be used to easily build any workspace
|
|
|
1920 (esp. if you've more or less followed the layout presented above)
|
|
|
1921 unattended, with one or more configuration states (there's a
|
|
|
1922 pre-determined list of the most useful, but it's easy to change). The
|
|
|
1923 output is filtered and split up in various ways so that you can identify
|
|
|
1924 which output came from where, and you can see the output either full or
|
|
|
1925 with all "normal" output except occasional status messages filtered so
|
|
|
1926 that you only see the abnormal ones.
|
|
|
1927 @end itemize
|
|
|
1928
|
|
|
1929 @node Q1.5.5, Q1.6.1, Q1.5.4, Introduction
|
|
|
1930 @unnumberedsubsec Q1.5.5: What's the basic layout of the code?
|
|
|
1931
|
|
|
1932 The file @file{configure} is a shell script to acclimate XEmacs to the
|
|
|
1933 oddities of your processor and operating system. It will create a
|
|
|
1934 file named @file{Makefile} (a script for the @file{make} program), which helps
|
|
|
1935 automate the process of building and installing emacs. See INSTALL
|
|
|
1936 for more detailed information.
|
|
|
1937
|
|
|
1938 The file @file{configure.in} is the input used by the autoconf program to
|
|
|
1939 construct the @file{configure} script. Since XEmacs has configuration
|
|
|
1940 requirements that autoconf can't meet, @file{configure.in} uses an unholy
|
|
|
1941 marriage of custom-baked configuration code and autoconf macros; it
|
|
|
1942 may be wise to avoid rebuilding @file{configure} from @file{configure.in} when
|
|
|
1943 possible.
|
|
|
1944
|
|
|
1945 The file @file{Makefile.in} is a template used by @file{configure} to create
|
|
|
1946 @file{Makefile}.
|
|
|
1947
|
|
|
1948 There are several subdirectories:
|
|
|
1949
|
|
|
1950 @enumerate
|
|
|
1951 @item
|
|
|
1952 @file{src} holds the C code for XEmacs (the XEmacs Lisp interpreter and its
|
|
|
1953 primitives, the redisplay code, and some basic editing functions).
|
|
|
1954 @item
|
|
|
1955 @file{lisp} holds the XEmacs Lisp code for XEmacs (most everything else).
|
|
|
1956 @item
|
|
|
1957 @file{lib-src} holds the source code for some utility programs for use by
|
|
|
1958 or with XEmacs, like movemail and etags.
|
|
|
1959 @item
|
|
|
1960 @file{etc} holds miscellaneous architecture-independent data files
|
|
|
1961 XEmacs uses, like the tutorial text. The contents of the @file{lisp},
|
|
|
1962 @file{info} and @file{man} subdirectories are architecture-independent too.
|
|
|
1963 @item
|
|
|
1964 @file{lwlib} holds the C code for the X toolkit objects used by XEmacs.
|
|
|
1965 @item
|
|
|
1966 @file{info} holds the Info documentation tree for XEmacs.
|
|
|
1967 @item
|
|
|
1968 @file{man} holds the source code for the XEmacs online documentation.
|
|
|
1969 @item
|
|
|
1970 @file{nt} holds files used compiling XEmacs under Microsoft Windows.
|
|
|
1971 @end enumerate
|
|
|
1972
|
|
2537
|
1973 @unnumberedsec 1.6: Politics (XEmacs vs. GNU Emacs)
|
|
|
1974
|
|
2559
|
1975 @node Q1.6.1, Q1.6.2, Q1.5.5, Introduction
|
|
2537
|
1976 @unnumberedsubsec Q1.6.1: What is GNU Emacs?
|
|
|
1977
|
|
|
1978 GNU Emacs and XEmacs are related open-source text editors. Both
|
|
|
1979 derive from GNU Emacs version 18; the split between the two happened
|
|
|
1980 in 1991 (for comparison, the oldest versions of GNU Emacs date from
|
|
|
1981 1984). For information on GNU Emacs, see
|
|
|
1982 @uref{http://www.gnu.org/software/emacs/emacs.html}.
|
|
|
1983
|
|
|
1984 @node Q1.6.2, Q1.6.3, Q1.6.1, Introduction
|
|
|
1985 @unnumberedsubsec Q1.6.2: How does XEmacs differ from GNU Emacs?
|
|
428
|
1986
|
|
|
1987 For a detailed description of the differences between GNU Emacs and
|
|
|
1988 XEmacs and a detailed history of XEmacs, check out the
|
|
|
1989 @example
|
|
430
|
1990 @uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file}
|
|
428
|
1991 @end example
|
|
|
1992
|
|
2417
|
1993 @table @strong
|
|
|
1994 @item User-Visible Editing Features
|
|
|
1995 XEmacs in general tries hard to conform to exist user-interface
|
|
|
1996 standards, and to work "out-of-the-box" without the need for obscure
|
|
|
1997 customization changes. GNU Emacs, particularly version 21, has gotten
|
|
|
1998 better about this (in many cases by copying the XEmacs behavior!), but
|
|
|
1999 still has some weirdnesses. For example, the standard method of
|
|
|
2000 selecting text using the Shift key works out-of-the-box in XEmacs.
|
|
|
2001
|
|
|
2002 XEmacs has a built-in toolbar. Four toolbars can actually be configured
|
|
|
2003 simultaneously: top, bottom, left, and right toolbars.
|
|
|
2004
|
|
|
2005 XEmacs has vertical and horizontal scrollbars. Unlike in GNU Emacs 19
|
|
|
2006 (which provides a primitive form of vertical scrollbar), these are true
|
|
|
2007 toolkit scrollbars. A look-alike Motif scrollbar is provided for those
|
|
|
2008 who don't have Motif. (Even for those who do, the look-alike may be
|
|
|
2009 preferable as it is faster.)
|
|
|
2010
|
|
|
2011 XEmacs has buffer tabs along the top of the frame (although the
|
|
|
2012 position can be changed) that make it very easy to switch buffers.
|
|
|
2013
|
|
|
2014 The menubar under XEmacs is better-designed, with more thought put into
|
|
|
2015 it.
|
|
|
2016
|
|
|
2017 XEmacs can ask questions using popup dialog boxes. Any command executed
|
|
|
2018 from a menu will ask yes/no questions with dialog boxes, while commands
|
|
|
2019 executed via the keyboard will use the minibuffer.
|
|
|
2020
|
|
|
2021 XEmacs under MS Windows provides uses the standard file-dialog box for
|
|
|
2022 opening and saving files. Standard menu-accelerator behavior can easily
|
|
|
2023 be enabled using the Options menu, and integrates well into the existing
|
|
|
2024 keymap.
|
|
|
2025
|
|
|
2026 XEmacs has (still experimental) support for widgets of various sorts --
|
|
|
2027 buttons, text boxes, sliders, progress bars, etc. A progress bar is
|
|
|
2028 used in font lock to show the progress.
|
|
|
2029
|
|
|
2030 Experimental support for drag-and-drop protocols is provided from
|
|
|
2031 XEmacs 21.
|
|
|
2032
|
|
|
2033 @item General Platform Support
|
|
|
2034 If you're running on a machine with audio hardware, you can specify
|
|
|
2035 sound files for XEmacs to play instead of the default X beep. See the
|
|
|
2036 documentation of the function load-sound-file and the variable
|
|
|
2037 sound-alist. XEmacs also supports the network sound protocols NAS and
|
|
|
2038 EsounD.
|
|
|
2039
|
|
|
2040 XEmacs 21 supports database protocols with LISP bindings, currently
|
|
|
2041 including Berkeley DB, LDAP, and PostgreSQL (21.2 only).
|
|
|
2042
|
|
|
2043 XEmacs 20 and 21 support the Canna, Wnn, and SJ3 Japanese input method
|
|
|
2044 servers directly, as well as through the X Input Method (XIM)
|
|
|
2045 protocol. GNU Emacs 20 supports only the XIM protocol. Both Emacsen
|
|
|
2046 support the Quail family of input methods (implemented in LISP) for many
|
|
|
2047 languages.
|
|
|
2048
|
|
|
2049 XEmacs provides support for ToolTalk on systems that have
|
|
|
2050 it.
|
|
|
2051
|
|
|
2052 @item Packaged LISP Libraries
|
|
|
2053 Many more packages are provided standard with XEmacs than with GNU Emacs
|
|
|
2054 19 or 20.
|
|
|
2055
|
|
|
2056 XEmacs 21 supports an integrated package management system which uses
|
|
|
2057 EFS to download, then automatically install prebuilt LISP
|
|
|
2058 libraries. This allows XEmacs users much more straightforward access to
|
|
|
2059 the "latest and greatest" version of any given library.
|
|
|
2060
|
|
|
2061 We are working on a standard method for enabling, disabling and
|
|
|
2062 otherwise controlling packages, which should make them very easy to use.
|
|
|
2063
|
|
|
2064 @item LISP Programming
|
|
|
2065 From XEmacs 20 on, characters are a separate type. Characters can be
|
|
|
2066 converted to integers (and many integers can be converted to
|
|
|
2067 characters), but characters are not integers. GNU Emacs 19, XEmacs 19,
|
|
|
2068 Mule 2.3 (an extensive patch to GNU Emacs 18.55 and 19.x), and GNU Emacs
|
|
|
2069 20 (incorporating Mule 3 and later Mule 4) represent them as integers.
|
|
|
2070
|
|
|
2071 From XEmacs 20 on, the buffer is treated as an array of characters, and
|
|
|
2072 the representation of buffer text is not exposed to LISP. The GNU Emacs
|
|
|
2073 20 functions like buffer-as-multibyte are not supported.
|
|
|
2074
|
|
|
2075 In XEmacs, events are first-class objects. GNU Emacs 19 represents them
|
|
|
2076 as integers, which obscures the differences between a key gesture and
|
|
|
2077 the ancient ASCII code used to represent a particular overlapping subset
|
|
|
2078 of them.
|
|
|
2079
|
|
|
2080 In XEmacs, keymaps are first-class opaque objects. GNU Emacs 19
|
|
|
2081 represents them as complicated combinations of association lists and
|
|
|
2082 vectors. If you use the advertised functional interface to manipulation
|
|
|
2083 of keymaps, the same code will work in XEmacs, GNU Emacs 18, and GNU
|
|
|
2084 Emacs 19; if your code depends on the underlying implementation of
|
|
|
2085 keymaps, it will not.
|
|
|
2086
|
|
|
2087 XEmacs uses "extents" to represent all non-textual aspects of buffers;
|
|
|
2088 GNU Emacs 19 uses two distinct objects, "text properties" and
|
|
|
2089 "overlays", which divide up the functionality between them. Extents are
|
|
|
2090 a superset of the union of the functionality of the two GNU Emacs data
|
|
|
2091 types. The full GNU Emacs 19 interface to text properties and overlays
|
|
|
2092 is supported in XEmacs (with extents being the underlying
|
|
|
2093 representation).
|
|
|
2094
|
|
|
2095 Extents can be made to be copied into strings, and then restored, by
|
|
|
2096 kill and yank. Thus, one can specify this behavior on either "extents"
|
|
|
2097 or "text properties", whereas in GNU Emacs 19 text properties always
|
|
|
2098 have this behavior and overlays never do.
|
|
|
2099
|
|
|
2100 @item Window System Programming Interface
|
|
|
2101 XEmacs uses the MIT "Xt" toolkit instead of raw Xlib calls, which makes
|
|
|
2102 it be a more well-behaved X citizen (and also improves portability). A
|
|
|
2103 result of this is that it is possible to include other Xt "Widgets" in
|
|
|
2104 the XEmacs window. Also, XEmacs understands the standard Xt command-line
|
|
|
2105 arguments.
|
|
|
2106
|
|
|
2107 XEmacs supports Motif applications, generic Xt (e.g. Athena)
|
|
|
2108 applications, and raw Xlib applications. An XEmacs variant which
|
|
|
2109 supports GTK+ is available (integration as an option in the XEmacs
|
|
|
2110 mainline is planned for XEmacs 22), although code to take advantage of
|
|
|
2111 the support is as yet scarce.
|
|
|
2112
|
|
|
2113 An XEmacs frame can be placed within an "external client widget" managed
|
|
|
2114 by another application. This allows an application to use an XEmacs
|
|
|
2115 frame as its text pane rather than the standard Text widget that is
|
|
|
2116 provided with Motif or Athena.
|
|
|
2117
|
|
|
2118 @item Community Participation
|
|
2459
|
2119 Joining the XEmacs development team is simple. Mail to
|
|
|
2120 @email{xemacs-beta@@xemacs.org, XEmacs Developers}, and you're in! (If
|
|
|
2121 you want to be, of course. You're also welcome to just post
|
|
|
2122 development-related questions and bug reports.) The GNU Emacs
|
|
2417
|
2123 development team and internal mailing lists are still by invitation
|
|
|
2124 only.
|
|
|
2125
|
|
|
2126 The "bleeding edge" of mainline XEmacs development is available by
|
|
|
2127 anonymous CVS as are some subsidiary branches (check out the xemacs-gtk
|
|
|
2128 module for the latest in GUI features!)
|
|
|
2129
|
|
|
2130 Development and maintenance of Lisp libraries is separated from the core
|
|
|
2131 editor development at a fairly low level. This provides better
|
|
|
2132 modularization and a better division of responsibility between external
|
|
|
2133 library maintainers and the XEmacs core development team. Even for
|
|
|
2134 packages the size of Gnus, XEmacs users normally have access to a
|
|
|
2135 pre-built version within a few weeks of a major release, and minor
|
|
|
2136 updates often within days.
|
|
|
2137
|
|
|
2138 CVS commit authority is broadly dispersed. Recognized maintainers of
|
|
|
2139 LISP libraries who are willing to maintain XEmacs packaged versions
|
|
|
2140 automatically qualify for CVS accounts for their packages.
|
|
|
2141 @end table
|
|
|
2142
|
|
2537
|
2143 @node Q1.6.3, Q1.6.4, Q1.6.2, Introduction
|
|
|
2144 @unnumberedsubsec Q1.6.3: How much does XEmacs differ?
|
|
2417
|
2145
|
|
|
2146 RMS has asserted at times that XEmacs is merely a "patch" on top of
|
|
2537
|
2147 GNU Emacs (@pxref{Q1.6.4}). In fact, probably not more than 5% of the
|
|
2417
|
2148 code, if that, remains unchanged, and nearly 14 years of work has gone
|
|
|
2149 into XEmacs at this point. (GNU Emacs itself is only than 20 years
|
|
|
2150 old, and thus XEmacs has existed as a separate product for over 2/3 of
|
|
|
2151 the lifespan of GNU Emacs.) As a point of comparison, XEmacs 21.5 has
|
|
|
2152 perhaps 65,000 more lines of C code than GNU Emacs 21.2.
|
|
|
2153
|
|
|
2154 However, the XEmacs developers strive to keep their code compatible with
|
|
|
2155 GNU Emacs, especially on the Lisp level. Much effort goes into
|
|
|
2156 "synching" the XEmacs Elisp code with recent GNU Emacs releases so as to
|
|
|
2157 benefit from GNU Emacs development work. (In contrast, almost no code
|
|
|
2158 from XEmacs has made it into GNU Emacs, and in fact the GNU Emacs
|
|
|
2159 developers are instructed by RMS not to even look at XEmacs source code!
|
|
|
2160 This stems from self-imposed licensing restrictions on the part of GNU
|
|
|
2161 Emacs -- and almost certainly out of hostility, as well.)
|
|
|
2162
|
|
2537
|
2163 @node Q1.6.4, Q1.6.5, Q1.6.3, Introduction
|
|
|
2164 @unnumberedsubsec Q1.6.4: Is XEmacs "GNU"?
|
|
2417
|
2165
|
|
|
2166 RMS insists on the term "GNU XEmacs" and maintains that
|
|
|
2167
|
|
|
2168 @quotation
|
|
|
2169 XEmacs is GNU software because it's a modified version of a
|
|
|
2170 GNU program. And it is GNU software because the FSF is the copyright
|
|
|
2171 holder for most of it, and therefore the legal responsibility for
|
|
|
2172 protecting its free status falls on us whether we want it or not. This
|
|
|
2173 is why the term "GNU XEmacs" is legitimate.
|
|
|
2174 @end quotation
|
|
|
2175
|
|
|
2176 In fact, FSF is @emph{not} the copyright holder for most of the code,
|
|
2537
|
2177 as very little unmodified FSF code remains (@pxref{Q1.6.3}).
|
|
2417
|
2178
|
|
|
2179 Furthermore, RMS's assertion that XEmacs is "GNU" seems rather bizarre
|
|
|
2180 to the XEmacs developers given RMS's hostility and general lack of
|
|
|
2181 interest in cooperation. "GNU" software in general is part of the GNU
|
|
|
2182 Project, is distributed by it on their FTP site, and receives support
|
|
|
2183 (or at least cooperation), as well as implicit endorsement, from it.
|
|
|
2184 The GNU Project, however, has never supported XEmacs and never
|
|
|
2185 distributed XEmacs, and RMS's hostility is the farthest thing possible
|
|
|
2186 from an endorsement. In fact, the GNU Project distributes a number of
|
|
|
2187 non-GNU software projects on the FSF web site, but again XEmacs is not
|
|
|
2188 one of them.
|
|
|
2189
|
|
2537
|
2190 @node Q1.6.5, Q1.6.6, Q1.6.4, Introduction
|
|
|
2191 @unnumberedsubsec Q1.6.5: What is the correct way to refer to XEmacs and GNU Emacs?
|
|
2417
|
2192
|
|
|
2193 Unfortunately even the naming of these two applications has become
|
|
|
2194 politicized. Much of this stems from RMS, who has a history of
|
|
|
2195 politicizing similar issues. (Compare the controversy over "Lignux"
|
|
|
2196 and "GNU/Linux".) We would prefer that the terms "XEmacs" and "GNU
|
|
|
2197 Emacs" be used, which are neutral and acceptable to most people. RMS,
|
|
|
2198 however, is not willing to accept these terms. He insists that, if
|
|
|
2199 his product is called "GNU Emacs", then ours must be called "GNU
|
|
2537
|
2200 XEmacs". (For our opinion of this term, @xref{Q1.6.4}.) On the other
|
|
2417
|
2201 hand, if our product is to be called "XEmacs", as we prefer, then his
|
|
|
2202 product must simply be called "Emacs". The intent of this seems
|
|
|
2203 clear: RMS wants to make sure the names reflect his view that his
|
|
|
2204 version is the "real" Emacs and ours is merely a derivative,
|
|
2537
|
2205 second-class product (@pxref{Q1.6.3}).
|
|
2417
|
2206
|
|
|
2207 The XEmacs developers hope that you will use the neutral terms
|
|
|
2208 "XEmacs" and "GNU Emacs" for these two specific products. "Emacs", on
|
|
|
2209 the other hand, is a generic term for a class of programmable text
|
|
|
2210 editors with a similar look-and-feel, and usually a Lisp-based
|
|
|
2211 extension language. These trace themselves back to early editors such
|
|
|
2212 as EINE, ZWEI, ZMACS and Multics Emacs. @xref{A History of Emacs,,,
|
|
|
2213 internals, XEmacs Internals Manual}.
|
|
|
2214
|
|
|
2215 We also call upon RMS, in the spirit of furthering cooperation, to
|
|
|
2216 stop politicizing this issue and use the neutral terms "XEmacs" and
|
|
|
2217 "GNU Emacs". We have already acceded to RMS' wishes in this respect,
|
|
|
2218 and we expect him to do the same. (In the past, the XEmacs developers
|
|
|
2219 often used the terms "FSF Emacs" or "FSFmacs" or "RMSmacs" in
|
|
|
2220 reference to GNU Emacs; these terms were apparently modeled after RMS'
|
|
|
2221 own usage of "Gosmacs" and "Gosling Emacs" in reference to Unipress
|
|
|
2222 Emacs, produced by James Gosling. RMS, however, considers such terms
|
|
|
2223 to be insulting, so we refrain from using them as much as possible in
|
|
|
2224 preference to GNU Emacs.)
|
|
|
2225
|
|
2537
|
2226 @node Q1.6.6, Q1.7.1, Q1.6.5, Introduction
|
|
|
2227 @unnumberedsubsec Q1.6.6: Why haven't XEmacs and GNU Emacs merged?
|
|
2417
|
2228
|
|
|
2229 There are currently irreconcilable differences in the views about
|
|
|
2230 technical, programming, design, organizational and legal matters
|
|
|
2231 between Richard Stallman (RMS), the author and leader of the GNU Emacs
|
|
|
2232 project, and the XEmacs development team which provide little hope for
|
|
|
2233 a merge to take place in the short-term future. There have been
|
|
|
2234 repeated attempts at merging by all of the major XEmacs developers,
|
|
|
2235 starting from the early days of Lucid Emacs (in 1991), but they have
|
|
|
2236 all failed. RMS has very strong views about how GNU Emacs should be
|
|
|
2237 structured and how his project should be run, and during the repeated
|
|
|
2238 merge efforts has never demonstrated any realistic interest in
|
|
|
2239 sufficiently compromising or ceding control to allow a middle ground
|
|
|
2240 to be found. The basic problem seems to be the very different goals
|
|
|
2241 of RMS and the XEmacs project. The primary goals of the XEmacs
|
|
|
2242 project are technical and organizational -- we want to create the best
|
|
|
2243 editor possible, and to make it as easy as possible for people around
|
|
|
2244 the world to contribute. The primary goals of RMS, on the other hand,
|
|
|
2245 are political, and GNU Emacs, and any potential merge efforts with
|
|
|
2246 XEmacs, are strictly subservient to these goals. In fact, in many
|
|
|
2247 ways RMS sees GNU Emacs as the "poster child" of his aims, the one
|
|
|
2248 program in the GNU project that above all others must set an example
|
|
|
2249 to the world. (This has to do with the fact that GNU Emacs was the
|
|
|
2250 first program in the GNU project, and the only one that he is still
|
|
|
2251 personally involved with on a day-to-day basis.) Given his goals, his
|
|
|
2252 position is completely reasonable -- but unfortunately, makes any
|
|
|
2253 merge impossible.
|
|
|
2254
|
|
|
2255 From the XEmacs perspective, the most intractable issues appear to be
|
|
|
2256 legal and organizational, specifically:
|
|
428
|
2257
|
|
|
2258 @itemize @bullet
|
|
|
2259 @item
|
|
2417
|
2260 RMS requires "legal papers" to be signed for all contributions of code
|
|
|
2261 to GNU Emacs over 10 lines or so, transferring the copyright and all
|
|
|
2262 legal rights to the code to the Free Software Foundation. XEmacs does
|
|
|
2263 not and has never required this, since it has the practical effect of
|
|
|
2264 discouraging individual and in particular corporate contributions --
|
|
|
2265 corporations will almost never sign away their legal rights to code
|
|
|
2266 since it makes it impossible to reuse the code in any product that
|
|
|
2267 whose license is not compatible with the GNU General Public License.
|
|
|
2268 Since RMS has shown no inclination to compromise on this issue, a
|
|
|
2269 merge would require that most of the existing XEmacs code would need
|
|
|
2270 to be thrown away and rewritten -- something the XEmacs developers are
|
|
|
2271 understandably reluctant to do.
|
|
|
2272
|
|
|
2273 @item
|
|
|
2274 A repeated stumbling block in the merge talks has been the issue of
|
|
|
2275 organizational control over the resulting product. RMS has made it
|
|
|
2276 clear that he intends to have final say over design issues in a merged
|
|
|
2277 Emacs. Unfortunately, RMS and the XEmacs developers have repeatedly
|
|
|
2278 clashed over design decisions, and RMS' insistence on getting his way
|
|
|
2279 in such disagreements was the very reason for the split in the first
|
|
|
2280 place. This same issue has come up again and again in merge talks and
|
|
|
2281 we have never been able to come to a satisfactory resolution. To the
|
|
|
2282 extent that RMS is willing to compromise at all, it appears to be of a
|
|
|
2283 purely political rather than technical nature -- "If we support this
|
|
|
2284 feature of yours, we also get to support this other feature of mine."
|
|
|
2285 The XEmacs developers cannot see how such a process would lead to
|
|
|
2286 anything but a mess of incompatible things hodgepodged together.
|
|
|
2287
|
|
|
2288 @item
|
|
|
2289 Because of the years of separate development, distinct and
|
|
|
2290 incompatible interfaces have developed and merging would be extremely
|
|
|
2291 difficult even with the above non-technical issues resolved. The
|
|
|
2292 problem has been exacerbated by the issue of legal papers -- because
|
|
|
2293 XEmacs code is not "kosher" from RMS' perspective, he discourages
|
|
|
2294 developers from even looking at it out of legal concerns. Although it
|
|
|
2295 is still possible to read the XEmacs documentation and run the
|
|
|
2296 program, the practical effect of this prohibition has been to strongly
|
|
|
2297 discourage code-sharing and cooperative development -- although a
|
|
|
2298 great deal of GNU Emacs code has been incorporated into XEmacs,
|
|
|
2299 practically none has gone the other direction.
|
|
428
|
2300 @end itemize
|
|
|
2301
|
|
|
2302 If you have a comment to add regarding the merge, it is a good idea to
|
|
2417
|
2303 avoid posting to the newsgroups, because of the very heated flamewars
|
|
|
2304 that often result. Mail your questions to
|
|
|
2305 @email{xemacs-beta@@xemacs.org} and @email{emacs-devel@@gnu.org}.
|
|
|
2306
|
|
2537
|
2307 @unnumberedsec 1.7: External Packages
|
|
|
2308
|
|
2559
|
2309 @node Q1.7.1, Q1.7.2, Q1.6.6, Introduction
|
|
|
2310 @unnumberedsubsec Q1.7.1: What is the package system?
|
|
|
2311
|
|
|
2312 In order to reduce the size and increase the maintainability of
|
|
|
2313 XEmacs, the majority of the Elisp packages that came with previous
|
|
|
2314 releases have been unbundled. They have been replaced by the package
|
|
|
2315 system. Each elisp add-on (or groups of them when they are small) now
|
|
|
2316 comes in its own tarball that contains a small search hierarchy.
|
|
|
2317
|
|
|
2318 You select just the ones you need. Install them by untarring them into
|
|
|
2319 the right place. On startup XEmacs will find them, set up the load
|
|
|
2320 path correctly, install autoloads, etc, etc.
|
|
|
2321
|
|
|
2322 @xref{Q2.1.1}, for more info on how to download and install the packages.
|
|
|
2323
|
|
|
2324 @node Q1.7.2, Q1.7.3, Q1.7.1, Introduction
|
|
|
2325 @unnumberedsubsec Q1.7.2: Which external packages are there?
|
|
2537
|
2326
|
|
|
2327 @subheading Normal Packages
|
|
|
2328
|
|
|
2329 A very broad collection of elisp packages.
|
|
2417
|
2330
|
|
|
2331 @table @asis
|
|
2537
|
2332 @item Sun
|
|
|
2333 Support for Sparcworks.
|
|
|
2334
|
|
|
2335 @item ada
|
|
|
2336 Ada language support.
|
|
|
2337
|
|
|
2338 @item apel
|
|
|
2339 A Portable Emacs Library. Used by XEmacs MIME support.
|
|
|
2340
|
|
|
2341 @item auctex
|
|
|
2342 Basic TeX/LaTeX support.
|
|
|
2343
|
|
|
2344 @item bbdb
|
|
|
2345 The Big Brother Data Base: a rolodex-like database program.
|
|
|
2346
|
|
|
2347 @item build
|
|
|
2348 Build XEmacs from within (UNIX, Windows).
|
|
|
2349
|
|
|
2350 @item c-support
|
|
|
2351 Basic single-file add-ons for editing C code.
|
|
|
2352
|
|
|
2353 @item calc
|
|
|
2354 Emacs calculator.
|
|
|
2355
|
|
|
2356 @item calendar
|
|
|
2357 Calendar and diary support.
|
|
|
2358
|
|
|
2359 @item cc-mode
|
|
|
2360 C, C++, Objective-C, Java, CORBA IDL, Pike and AWK language support.
|
|
|
2361
|
|
|
2362 @item clearcase
|
|
|
2363 New Clearcase Version Control for XEmacs (UNIX, Windows).
|
|
|
2364
|
|
|
2365 @item clearcase
|
|
|
2366 Support for the Clearcase version control system.
|
|
|
2367
|
|
|
2368 @item cookie
|
|
|
2369 "Fortune cookie"-style messages. Includes Spook (suspicious phrases)
|
|
|
2370 and Yow (Zippy quotes).
|
|
|
2371
|
|
|
2372 @item crisp
|
|
|
2373 Crisp/Brief emulation.
|
|
|
2374
|
|
|
2375 @item debug
|
|
|
2376 GUD, gdb, dbx debugging support.
|
|
|
2377
|
|
|
2378 @item dictionary
|
|
|
2379 Interface to RFC2229 dictionary servers.
|
|
|
2380
|
|
|
2381 @item dired
|
|
|
2382 The DIRectory EDitor is for manipulating, and running commands on
|
|
|
2383 files in a directory.
|
|
|
2384
|
|
|
2385 @item docbookide
|
|
|
2386 DocBook editing support.
|
|
|
2387
|
|
|
2388 @item ecb
|
|
|
2389 Emacs source code browser.
|
|
|
2390
|
|
|
2391 @item ecrypto
|
|
|
2392 Crypto functionality in Emacs Lisp.
|
|
|
2393
|
|
|
2394 @item edebug
|
|
|
2395 An Emacs Lisp debugger.
|
|
|
2396
|
|
|
2397 @item ediff
|
|
|
2398 Interface over GNU patch.
|
|
|
2399
|
|
|
2400 @item edit-utils
|
|
|
2401 Miscellaneous editor extensions, you probably need this.
|
|
|
2402
|
|
|
2403 @item edt
|
|
|
2404 DEC EDIT/EDT emulation.
|
|
|
2405
|
|
|
2406 @item efs
|
|
|
2407 Treat files on remote systems the same as local files.
|
|
|
2408
|
|
|
2409 @item eieio
|
|
|
2410 Enhanced Implementation of Emacs Interpreted Objects.
|
|
|
2411
|
|
|
2412 @item elib
|
|
|
2413 Portable Emacs Lisp utilities library.
|
|
|
2414
|
|
|
2415 @item emerge
|
|
|
2416 Another interface over GNU patch.
|
|
|
2417
|
|
|
2418 @item erc
|
|
|
2419 ERC is an Emacs InternetRelayChat client.
|
|
|
2420
|
|
|
2421 @item escreen
|
|
|
2422 Multiple editing sessions withing a single frame (like screen).
|
|
|
2423
|
|
|
2424 @item eshell
|
|
|
2425 Command shell implemented entirely in Emacs Lisp.
|
|
|
2426
|
|
|
2427 @item ess
|
|
|
2428 ESS: Emacs Speaks Statistics.
|
|
|
2429
|
|
|
2430 @item eterm
|
|
|
2431 Terminal emulation.
|
|
|
2432
|
|
|
2433 @item eudc
|
|
|
2434 Emacs Unified Directory Client (LDAP, PH).
|
|
|
2435
|
|
|
2436 @item footnote
|
|
|
2437 Footnoting in mail message editing modes.
|
|
|
2438
|
|
|
2439 @item forms
|
|
|
2440 Forms editing support (obsolete, use Widget instead).
|
|
|
2441
|
|
|
2442 @item fortran-modes
|
|
|
2443 Fortran support.
|
|
|
2444
|
|
|
2445 @item fortran-modes
|
|
|
2446 Fortran language support.
|
|
|
2447
|
|
|
2448 @item frame-icon
|
|
|
2449 Set up mode-specific icons for each frame under XEmacs.
|
|
|
2450
|
|
|
2451 @item fsf-compat
|
|
|
2452 GNU Emacs compatibility files.
|
|
|
2453
|
|
|
2454 @item games
|
|
|
2455 Tetris, Sokoban, and Snake.
|
|
|
2456
|
|
|
2457 @item general-docs
|
|
|
2458 General documentation. Presently, empty.
|
|
|
2459
|
|
|
2460 @item gnats
|
|
|
2461 XEmacs bug reports.
|
|
|
2462
|
|
|
2463 @item gnus
|
|
|
2464 The Gnus Newsreader and Mailreader.
|
|
|
2465
|
|
|
2466 @item haskell-mode
|
|
|
2467 Haskell editing support.
|
|
|
2468
|
|
|
2469 @item hm--html-menus
|
|
|
2470 HTML editing.
|
|
|
2471
|
|
|
2472 @item hyperbole
|
|
|
2473 Hyperbole: The Everyday Info Manager.
|
|
|
2474
|
|
|
2475 @item ibuffer
|
|
|
2476 Advanced replacement for buffer-menu.
|
|
|
2477
|
|
|
2478 @item idlwave
|
|
|
2479 Editing and Shell mode for the Interactive Data Language.
|
|
|
2480
|
|
|
2481 @item igrep
|
|
|
2482 Enhanced front-end for Grep.
|
|
|
2483
|
|
|
2484 @item ilisp
|
|
|
2485 Front-end for interacting with Inferior Lisp (external lisps).
|
|
|
2486
|
|
|
2487 @item ispell
|
|
|
2488 Spell-checking with GNU ispell.
|
|
|
2489
|
|
|
2490 @item jde
|
|
|
2491 Integrated Development Environment for Java.
|
|
|
2492
|
|
|
2493 @item liece
|
|
|
2494 IRC (Internet Relay Chat) client for Emacs. Note, this package is
|
|
|
2495 deprecated and will be removed, use riece instead.
|
|
|
2496
|
|
|
2497 @item mail-lib
|
|
|
2498 Fundamental lisp files for providing email support.
|
|
|
2499
|
|
|
2500 @item mailcrypt
|
|
|
2501 Support for messaging encryption with PGP.
|
|
|
2502
|
|
|
2503 @item mew
|
|
|
2504 Messaging in an Emacs World; a MIME-based email program.
|
|
|
2505
|
|
|
2506 @item mh-e
|
|
|
2507 The XEmacs Interface to the MH Mail System.
|
|
|
2508
|
|
|
2509 @item mine
|
|
|
2510 Elisp implementation of the game 'Minehunt'.
|
|
|
2511
|
|
|
2512 @item misc-games
|
|
|
2513 Other amusements and diversions.
|
|
|
2514
|
|
|
2515 @item mmm-mode
|
|
|
2516 Support for Multiple Major Modes within a single buffer.
|
|
|
2517
|
|
|
2518 @item net-utils
|
|
|
2519 Miscellaneous Networking Utilities.
|
|
|
2520
|
|
|
2521 @item ocaml
|
|
|
2522 Objective Caml editing support.
|
|
|
2523
|
|
|
2524 @item oo-browser
|
|
|
2525 OO-Browser: The Multi-Language Object-Oriented Code Browser.
|
|
|
2526
|
|
|
2527 @item ocaml
|
|
|
2528 Objective Caml editing support.
|
|
|
2529
|
|
|
2530 @item os-utils
|
|
|
2531 Miscellaneous single-file O/S utilities, for printing, archiving,
|
|
|
2532 compression, remote shells, etc.
|
|
|
2533
|
|
|
2534 @item pc
|
|
|
2535 PC style interface emulation.
|
|
|
2536
|
|
|
2537 @item pcl-cvs
|
|
|
2538 CVS frontend.
|
|
|
2539
|
|
|
2540 @item pcomplete
|
|
|
2541 Provides programmatic completion.
|
|
|
2542
|
|
|
2543 @item perl-modes
|
|
|
2544 Perl support.
|
|
|
2545
|
|
|
2546 @item pgg
|
|
|
2547 Emacs interface to various PGP implementations.
|
|
|
2548
|
|
|
2549 @item prog-modes
|
|
|
2550 Support for various programming languages.
|
|
|
2551
|
|
|
2552 @item ps-print
|
|
|
2553 Printing functions and utilities.
|
|
|
2554
|
|
|
2555 @item psgml
|
|
|
2556 Validated HTML/SGML editing.
|
|
|
2557
|
|
|
2558 @item psgml-dtds
|
|
|
2559 A collection of DTDs for psgml. Note that this package is deprecated
|
|
|
2560 and will be removed in the future, most likely Q2/2003. Instead of using
|
|
|
2561 this, you should install needed DTDs yourself.
|
|
|
2562
|
|
|
2563 @item python-modes
|
|
|
2564 Python language support.
|
|
|
2565
|
|
|
2566 @item reftex
|
|
|
2567 Emacs support for LaTeX cross-references, citations.
|
|
|
2568
|
|
|
2569 @item riece
|
|
|
2570 IRC (Internet Relay Chat) client for Emacs.
|
|
|
2571
|
|
|
2572 @item rmail
|
|
|
2573 An obsolete Emacs mailer. If you do not already use it don't start.
|
|
|
2574
|
|
|
2575 @item ruby-modes
|
|
|
2576 Ruby support.
|
|
|
2577
|
|
|
2578 @item sasl
|
|
|
2579 Simple Authentication and Security Layer (SASL) library.
|
|
|
2580
|
|
|
2581 @item scheme
|
|
|
2582 Front-end support for Inferior Scheme.
|
|
|
2583
|
|
|
2584 @item semantic
|
|
|
2585 Semantic bovinator (Yacc/Lex for XEmacs). Includes Senator.
|
|
|
2586
|
|
|
2587 @item sgml
|
|
|
2588 SGML/Linuxdoc-SGML editing.
|
|
|
2589
|
|
|
2590 @item sh-script
|
|
|
2591 Support for editing shell scripts.
|
|
|
2592
|
|
|
2593 @item sieve
|
|
|
2594 Manage Sieve email filtering scripts.
|
|
|
2595
|
|
|
2596 @item slider
|
|
|
2597 User interface tool.
|
|
|
2598
|
|
|
2599 @item sml-mode
|
|
|
2600 SML editing support.
|
|
|
2601
|
|
|
2602 @item sounds-au
|
|
|
2603 XEmacs Sun sound files.
|
|
|
2604
|
|
|
2605 @item sounds-wav
|
|
|
2606 XEmacs Microsoft sound files.
|
|
|
2607
|
|
|
2608 @item speedbar
|
|
|
2609 Provides a separate frame with convenient references.
|
|
|
2610
|
|
|
2611 @item strokes
|
|
|
2612 Mouse enhancement utility.
|
|
|
2613
|
|
|
2614 @item supercite
|
|
|
2615 An Emacs citation tool for News & Mail messages.
|
|
|
2616
|
|
|
2617 @item texinfo
|
|
|
2618 XEmacs TeXinfo support.
|
|
|
2619
|
|
|
2620 @item text-modes
|
|
|
2621 Miscellaneous support for editing text files.
|
|
|
2622
|
|
|
2623 @item textools
|
|
|
2624 Miscellaneous TeX support.
|
|
|
2625
|
|
|
2626 @item time
|
|
|
2627 Display time & date on the modeline.
|
|
|
2628
|
|
|
2629 @item tm
|
|
|
2630 Emacs MIME support. Not needed for gnus >= 5.8.0.
|
|
|
2631
|
|
|
2632 @item tooltalk
|
|
|
2633 Support for building with Tooltalk.
|
|
|
2634
|
|
|
2635 @item tpu
|
|
|
2636 DEC EDIT/TPU support.
|
|
|
2637
|
|
|
2638 @item tramp
|
|
|
2639 Remote shell-based file editing. This is similar to EFS or Ange-FTP,
|
|
|
2640 but works with rsh/ssh and rcp/scp.
|
|
|
2641
|
|
|
2642 @item vc
|
|
|
2643 Version Control for Free systems.
|
|
|
2644
|
|
|
2645 @item vc-cc
|
|
|
2646 Version Control for ClearCase (UnFree) systems.
|
|
|
2647
|
|
|
2648 @item vhdl
|
|
|
2649 Support for VHDL.
|
|
|
2650
|
|
|
2651 @item view-process
|
|
|
2652 A Unix process browsing tool.
|
|
|
2653
|
|
|
2654 @item viper
|
|
|
2655 VI emulation support.
|
|
|
2656
|
|
|
2657 @item vm
|
|
|
2658 An Emacs mailer.
|
|
|
2659
|
|
|
2660 @item w3
|
|
|
2661 A Web browser.
|
|
|
2662
|
|
|
2663 @item x-symbol
|
|
|
2664 Semi WYSIWYG for LaTeX, HTML, etc, using additional fonts.
|
|
|
2665
|
|
|
2666 @item xemacs-base
|
|
|
2667 Fundamental XEmacs support, you almost certainly need this.
|
|
|
2668
|
|
|
2669 @item xemacs-devel
|
|
|
2670 XEmacs Lisp developer support. This package contains utilities for
|
|
|
2671 supporting Lisp development. It is a single-file package so it may be
|
|
|
2672 tailored.
|
|
|
2673
|
|
|
2674 @item xlib
|
|
|
2675 Emacs interface to X server.
|
|
|
2676
|
|
|
2677 @item xslide
|
|
|
2678 XSL editing support.
|
|
|
2679
|
|
|
2680 @item xslt-process
|
|
|
2681 A minor mode for (X)Emacs which allows running an XSLT processor on a
|
|
|
2682 buffer.
|
|
|
2683
|
|
|
2684 @item xwem
|
|
|
2685 X Emacs Window Manager.
|
|
|
2686
|
|
|
2687 @item zenirc
|
|
|
2688 ZENIRC IRC Client.
|
|
2417
|
2689 @end table
|
|
|
2690
|
|
2537
|
2691 @subheading Mule Support (mule)
|
|
|
2692
|
|
|
2693 MULti-lingual Enhancement. Support for world scripts such as
|
|
|
2694 Latin, Arabic, Cyrillic, Chinese, Japanese, Greek, Hebrew etc.
|
|
|
2695 To use these packages your XEmacs must be compiled with Mule
|
|
|
2696 support.
|
|
|
2697
|
|
|
2698 @table @asis
|
|
|
2699 @item edict
|
|
|
2700 MULE: Lisp Interface to EDICT, Kanji Dictionary.
|
|
|
2701
|
|
|
2702 @item egg-its
|
|
|
2703 MULE: Wnn (4.2 and 6) support. SJ3 support.
|
|
|
2704
|
|
|
2705 @item latin-unity
|
|
|
2706 MULE: find single ISO 8859 character set to encode a buffer.
|
|
|
2707
|
|
|
2708 @item latin-unity
|
|
|
2709 Unify character sets in a buffer. When characters belong to disjoint
|
|
|
2710 character sets, this attempts to translate the characters so
|
|
|
2711 that they belong to one character set. If the buffer coding system is
|
|
|
2712 not sufficient, this suggests different coding systems.
|
|
|
2713
|
|
|
2714 @item leim
|
|
|
2715 MULE: Quail. All non-English and non-Japanese language support.
|
|
|
2716
|
|
|
2717 @item locale
|
|
|
2718 MULE: Localized menubars and localized splash screens.
|
|
|
2719
|
|
|
2720 @item lookup
|
|
|
2721 Dictionary support. (This isn't an English dictionary program)
|
|
|
2722
|
|
|
2723 @item mule-base
|
|
|
2724 MULE: Basic Mule support, required for building with Mule.
|
|
|
2725
|
|
|
2726 @item mule-ucs
|
|
|
2727 MULE: Extended coding systems (including Unicode) for XEmacs.
|
|
|
2728
|
|
|
2729 @item mule-ucs
|
|
|
2730 Extended coding systems (including Unicode) for XEmacs.
|
|
|
2731
|
|
|
2732 @item skk
|
|
|
2733 Another Japanese Language Input Method. Can be used without a
|
|
|
2734 separate process running as a dictionary server.
|
|
|
2735 @end table
|
|
|
2736
|
|
2559
|
2737 @node Q1.7.3, Q1.7.4, Q1.7.2, Introduction
|
|
|
2738 @unnumberedsubsec Q1.7.3: Do I need to have the packages to run XEmacs?
|
|
|
2739
|
|
|
2740 Strictly speaking, no. XEmacs will build and install just fine without
|
|
|
2741 any packages installed. However, only the most basic editing functions
|
|
|
2742 will be available with no packages installed, so installing packages is
|
|
|
2743 an essential part of making your installed XEmacs _useful_.
|
|
|
2744
|
|
|
2745 @node Q1.7.4, Q1.8.1, Q1.7.3, Introduction
|
|
|
2746 @unnumberedsubsec Q1.7.4: Is there a way to find which package has particular functionality?
|
|
|
2747
|
|
|
2748 If you want to find out which package contains the functionality you
|
|
|
2749 are looking for, use @kbd{M-x package-get-package-provider}, and give it a
|
|
|
2750 symbol that is likely to be in that package.
|
|
|
2751
|
|
|
2752 For example, if some code you want to use has a @code{(require 'thingatpt)}
|
|
|
2753 in it:
|
|
|
2754
|
|
|
2755 @example
|
|
|
2756 M-x package-get-package-provider RET thingatpt RET
|
|
|
2757 @end example
|
|
|
2758
|
|
|
2759 which will return something like: @samp{(fsf-compat "1.08").}
|
|
|
2760
|
|
2537
|
2761 @unnumberedsec 1.8: Internationalization
|
|
|
2762
|
|
2559
|
2763 @node Q1.8.1, Q1.8.2, Q1.7.4, Introduction
|
|
2537
|
2764 @unnumberedsubsec Q1.8.1: What is the status of internationalization support aka MULE (including Asian language support)?
|
|
442
|
2765
|
|
|
2766 Both the stable and development versions of XEmacs include
|
|
1135
|
2767 internationalization support (aka MULE). MULE currently (21.4) works on
|
|
|
2768 UNIX and Linux systems. It is possible to build with MULE on Windows
|
|
|
2769 systems, but if you really need MULE on Windows, it is recommended that
|
|
|
2770 you build and use the development (21.5) version, and deal with the
|
|
|
2771 instability of the development tree. Binaries compiled without MULE
|
|
|
2772 support run faster than MULE capable XEmacsen.
|
|
428
|
2773
|
|
2537
|
2774 @node Q1.8.2, Q1.8.3, Q1.8.1, Introduction
|
|
|
2775 @unnumberedsubsec Q1.8.2: How can I help with internationalization?
|
|
430
|
2776
|
|
|
2777 If you would like to help, you may want to join the
|
|
|
2778 @email{xemacs-mule@@xemacs.org} mailing list. Especially needed are
|
|
|
2779 people who speak/write languages other than English, who are willing to
|
|
|
2780 use XEmacs/MULE regularly, and have some experience with Elisp.
|
|
428
|
2781
|
|
1135
|
2782 Translations of the TUTORIAL and man page are welcome, and XEmacs does
|
|
|
2783 support multilingual menus, but we have few current translations.
|
|
|
2784
|
|
2537
|
2785 @xref{Q1.5.2, How do I become a Beta Tester?}.
|
|
|
2786
|
|
|
2787 @node Q1.8.3, Q1.8.4, Q1.8.2, Introduction
|
|
|
2788 @unnumberedsubsec Q1.8.3: How do I type non-ASCII characters?
|
|
2417
|
2789
|
|
2459
|
2790 @xref{Q3.0.6, How can you type in special characters in XEmacs?}, in
|
|
2417
|
2791 part 3 of this FAQ, for some simple methods that also work in non-MULE
|
|
|
2792 builds of XEmacs (but only for one-octet coded character sets, and
|
|
|
2793 mostly for ISO 8859/1). Many of the methods available for Cyrillic
|
|
2537
|
2794 (@pxref{Q1.8.7, How about Cyrillic modes?}) work without MULE. MULE
|
|
|
2795 has more general capabilities. @xref{Q1.8.5, Please explain the
|
|
2417
|
2796 various input methods in MULE/XEmacs}.
|
|
|
2797
|
|
2459
|
2798 @xref{Q4.0.8, How do I display non-ASCII characters?}, which covers
|
|
2417
|
2799 display of non-ASCII characters.
|
|
|
2800
|
|
2537
|
2801 @node Q1.8.4, Q1.8.5, Q1.8.3, Introduction
|
|
|
2802 @unnumberedsubsec Q1.8.4: Can XEmacs messages come out in a different language?
|
|
428
|
2803
|
|
1135
|
2804 The message-catalog support was written but is badly bit-rotted. XEmacs
|
|
|
2805 20 and 21 did @emph{not} support it, and early releases of XEmacs 22
|
|
|
2806 will not either.
|
|
|
2807
|
|
|
2808 However, menubar localization @emph{does} work. To enable it, add to
|
|
|
2809 your @file{Emacs} file entries like this:
|
|
428
|
2810
|
|
|
2811 @example
|
|
440
|
2812 Emacs*XlwMenu.resourceLabels: True
|
|
|
2813 Emacs*XlwMenu.file.labelString: Fichier
|
|
442
|
2814 Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster oeffnen
|
|
428
|
2815 @end example
|
|
|
2816
|
|
|
2817 The name of the resource is derived from the non-localized entry by
|
|
|
2818 removing punctuation and capitalizing as above.
|
|
|
2819
|
|
2537
|
2820 @node Q1.8.5, Q1.8.6, Q1.8.4, Introduction
|
|
|
2821 @unnumberedsubsec Q1.8.5: Please explain the various input methods in MULE/XEmacs
|
|
428
|
2822
|
|
1135
|
2823 Mule supports a wide variety of input methods. There are three basic
|
|
|
2824 classes: Lisp implementations, generic platform support, and library
|
|
|
2825 interfaces.
|
|
|
2826
|
|
|
2827 @emph{Lisp implementations} include Quail, which provides table-driven input
|
|
|
2828 methods for almost all the character sets that Mule supports (including
|
|
|
2829 all of the ISO 8859 family, the Indic languages, Thai, and so on), and
|
|
|
2830 SKK, for Japanese. (SKK also supports an interface to an external
|
|
|
2831 "dictionary server" process.) Quail supports both typical "dead-key"
|
|
|
2832 methods (eg, in the "latin-1-prefix" method, @kbd{" a} produces ä, LATIN
|
|
|
2833 SMALL LETTER A WITH DIAERESIS), and the complex dictionary-based phonetic
|
|
|
2834 methods used for Asian ideographic languages like Chinese.
|
|
|
2835
|
|
|
2836 Lisp implementations can be less powerful (but they are not perceptibly
|
|
|
2837 inefficient), and of course are not portable to non-Emacs applications.
|
|
|
2838 The incompatibility can be very annoying. On the other hand, they
|
|
|
2839 require no special platform support or external libraries, so if you can
|
|
|
2840 display the characters, Mule can input them for you and you can edit,
|
|
|
2841 anywhere.
|
|
|
2842
|
|
|
2843 @emph{Generic platform support} is currently limited to the X Input
|
|
|
2844 Method (XIM) framework, although support for MSIME (for MS Windows) is
|
|
|
2845 planned, and IIIMF (Sun's Internet-Intranet Input Method Framework)
|
|
|
2846 support is extremely desirable. XIM is enabled at build time by use of
|
|
|
2847 the @samp{--with-xim} flag to @code{configure}. For use of XIM, see
|
|
|
2848 your platform documentation. However, normally the input method you use
|
|
|
2849 is specified via the @samp{LANG} and @samp{XMODIFIERS} environment
|
|
|
2850 variables.
|
|
|
2851
|
|
|
2852 Of course, input skills are portable across most applications. However,
|
|
|
2853 especially in modern GUI systems the habit of using bucky bits has
|
|
|
2854 fallen into sad disuse, and many XIM systems are poorly configured for
|
|
|
2855 use with Emacs. For example, the kinput2 input manager (a separate
|
|
|
2856 process providing an interface between Japanese dictionary servers such
|
|
|
2857 as Canna and Wnn, and the application) tends to gobble up keystrokes
|
|
|
2858 generating Meta characters. This means that to edit while using an XIM
|
|
|
2859 input method, you must toggle the input method off every time you want
|
|
|
2860 to use @kbd{M-f}. Your mileage may vary.
|
|
|
2861
|
|
|
2862 @emph{Library interfaces} are most common for Japanese, although Wnn
|
|
|
2863 supports Chinese (traditional and simplified) and Korean. There are
|
|
|
2864 Chinese and Korean input servers available, but we do not know of any
|
|
|
2865 patches for XEmacs to use them directly. You can use them via
|
|
|
2866 IM-enabled terminals, by manipulating the terminal coding systems. We
|
|
|
2867 describe only the Japanese-oriented systems here. The advantage of
|
|
|
2868 these systems is that they are very powerful, and on platforms where
|
|
|
2869 they are available there is typically a wide range of applications that
|
|
|
2870 support them. Thus your input skills are portable across applications.
|
|
|
2871
|
|
|
2872 Mule provides built-in interfaces to the following input methods: Wnn4,
|
|
|
2873 Wnn6, Canna, and SJ3. These can be configured at build time. There are
|
|
|
2874 patches available (no URL, sorry) to support the SKK server, as well.
|
|
|
2875 Wnn and SJ3 use the @code{egg} user interface. The interface for Canna
|
|
|
2876 is specialized to Canna.
|
|
428
|
2877
|
|
|
2878 Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
|
|
1135
|
2879 University. It is a powerful and complex system. Wnn4 is free and Wnn6
|
|
|
2880 is not. Wnn uses grammatical hints and probability of word association,
|
|
|
2881 so in principle Wnn can be cleverer than other methods.
|
|
|
2882
|
|
|
2883 Canna, made by NEC, supports only Japanese. It is a simple and powerful
|
|
|
2884 system. Canna uses only grammar, but its grammar and dictionary are
|
|
|
2885 quite sophisticated. So for standard modern Japanese, Canna seems
|
|
|
2886 cleverer than Wnn4. In addition, the UNIX version of Canna is free (now
|
|
|
2887 there is a Microsoft Windows version).
|
|
|
2888
|
|
|
2889 SJ3, by Sony, supports only Japanese.
|
|
428
|
2890
|
|
|
2891 Egg consists of following parts:
|
|
|
2892
|
|
|
2893 @enumerate
|
|
|
2894 @item
|
|
|
2895 Input character Translation System (ITS) layer.
|
|
|
2896 It translates ASCII inputs to Kana/PinYin/Hangul characters.
|
|
|
2897
|
|
|
2898 @item
|
|
|
2899 Kana/PinYin/Hangul to Kanji transfer layer.
|
|
1135
|
2900 The interface layer to network Kana-Kanji server (Wnn and Sj3).
|
|
428
|
2901 @end enumerate
|
|
|
2902
|
|
1135
|
2903 These input methods are modal. They have a raw (alphabet) mode, a
|
|
|
2904 phonetic input mode, and Kana-Kanji transfer mode. However there are
|
|
|
2905 mode-less input methods for Egg and Canna. @samp{boiled-egg} is a
|
|
|
2906 mode-less input method running on Egg. For Canna, @samp{canna.el} has a
|
|
|
2907 tiny boiled-egg-like command, @code{(canna-boil)}, and there are some
|
|
|
2908 boiled-egg-like utilities.
|
|
|
2909
|
|
|
2910 Much of this information was provided by @email{morioka@@jaist.ac.jp,
|
|
|
2911 MORIOKA Tomohiko}.
|
|
428
|
2912
|
|
2537
|
2913 @node Q1.8.6, Q1.8.7, Q1.8.5, Introduction
|
|
|
2914 @unnumberedsubsec Q1.8.6: How do I portably code for MULE/XEmacs?
|
|
428
|
2915
|
|
1135
|
2916 MULE has evolved rapidly over the last few years, and the original third
|
|
|
2917 party patch (for GNU Emacs 19), GNU Emacs 20+, and XEmacs 20+ have quite
|
|
|
2918 different implementations. The APIs also vary although recent versions
|
|
|
2919 of XEmacs have tended to converge to the GNU Emacs standard.
|
|
|
2920
|
|
|
2921 MULE implementations are going to continue to evolve. Both GNU Emacs
|
|
|
2922 and XEmacs are working hard on Unicode support, which will involve new
|
|
|
2923 APIs and probably variations on old ones. For XEmacs 22, the old ISO
|
|
|
2924 2022-based system for recognizing encodings will be replaced by a much
|
|
|
2925 more flexible system, which should improve accuracy of automatic coding
|
|
|
2926 detections, but will also involve new APIs.
|
|
|
2927
|
|
428
|
2928 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
|
|
|
2929
|
|
|
2930 @quotation
|
|
1135
|
2931 The application implementor must write separate code for these mule
|
|
|
2932 variants. [Please don't hesitate to report these variants to us; they
|
|
|
2933 are not, strictly speaking, bugs, but they give third-party developers
|
|
|
2934 the same kind of creepy-crawly feeling. We'll do what we can. -- Ed.]
|
|
428
|
2935
|
|
|
2936 MULE and the next version of Emacs are similar but the symbols are very
|
|
|
2937 different---requiring separate code as well.
|
|
|
2938
|
|
|
2939 Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of
|
|
|
2940 emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called
|
|
1135
|
2941 @code{emu} to provide a common interface. [There is an XEmacs package
|
|
|
2942 of APEL which provides much more comprehensive coverage. Be careful,
|
|
|
2943 however; APEL has problems of its own. -- Ed.]
|
|
428
|
2944
|
|
|
2945 I have the following suggestions about dealing with mule variants:
|
|
|
2946
|
|
|
2947 @itemize @bullet
|
|
|
2948 @item
|
|
|
2949 @code{(featurep 'mule)} @code{t} on all mule variants
|
|
|
2950
|
|
|
2951 @item
|
|
|
2952 @code{(boundp 'MULE)} is @code{t} on only MULE. Maybe the next version
|
|
|
2953 of Emacs will not have this symbol.
|
|
|
2954
|
|
|
2955 @item
|
|
|
2956 MULE has a variable @code{mule-version}. Perhaps the next version of
|
|
|
2957 Emacs will have this variable as well.
|
|
|
2958 @end itemize
|
|
|
2959
|
|
|
2960 Following is a sample to distinguish mule variants:
|
|
|
2961
|
|
|
2962 @lisp
|
|
|
2963 (if (featurep 'mule)
|
|
|
2964 (cond ((boundp 'MULE)
|
|
|
2965 ;; for original Mule
|
|
|
2966 )
|
|
440
|
2967 ((string-match "XEmacs" emacs-version)
|
|
|
2968 ;; for XEmacs with Mule
|
|
|
2969 )
|
|
|
2970 (t
|
|
|
2971 ;; for next version of Emacs
|
|
|
2972 ))
|
|
428
|
2973 ;; for old emacs variants
|
|
|
2974 )
|
|
|
2975 @end lisp
|
|
|
2976 @end quotation
|
|
|
2977
|
|
2537
|
2978 @node Q1.8.7, Q1.8.8, Q1.8.6, Introduction
|
|
|
2979 @unnumberedsubsec Q1.8.7: How about Cyrillic modes?
|
|
428
|
2980
|
|
|
2981 @email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes:
|
|
|
2982
|
|
|
2983 @quotation
|
|
|
2984 There is a cyrillic mode in the file @file{mysetup.zip} in
|
|
|
2985 @iftex
|
|
|
2986 @*
|
|
|
2987 @end iftex
|
|
|
2988 @uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}. This is a
|
|
|
2989 modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el}
|
|
|
2990 which can be obtained from
|
|
|
2991 @end quotation
|
|
|
2992
|
|
871
|
2993 @uref{http://www.math.uga.edu/~valery/russian.el}.
|
|
428
|
2994
|
|
|
2995 @email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes:
|
|
|
2996
|
|
|
2997 @quotation
|
|
|
2998 There is another cyrillic mode for both GNU Emacs and XEmacs by
|
|
|
2999 @email{manin@@camelot.mssm.edu, Dmitrii
|
|
|
3000 (Mitya) Manin} at
|
|
|
3001 @iftex
|
|
|
3002
|
|
|
3003 @end iftex
|
|
|
3004 @uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}.
|
|
|
3005 @c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead.
|
|
|
3006 @c Changed to russian host instead
|
|
|
3007 @end quotation
|
|
|
3008
|
|
|
3009 @email{rebecca.ore@@op.net, Rebecca Ore} writes:
|
|
|
3010
|
|
|
3011 @quotation
|
|
|
3012 The fullest resource I found on Russian language use (in and out of
|
|
661
|
3013 XEmacs) is @uref{http://www.ibiblio.org/sergei/Software/Software.html}
|
|
428
|
3014 @end quotation
|
|
|
3015
|
|
2537
|
3016 @node Q1.8.8, Q1.8.9, Q1.8.7, Introduction
|
|
|
3017 @unnumberedsubsec Q1.8.8: Does XEmacs support Unicode?
|
|
2417
|
3018
|
|
|
3019 To get Unicode support, you need a Mule-enabled XEmacs.
|
|
|
3020
|
|
|
3021 21.5 has internal support for Unicode and supports it fully, although we
|
|
|
3022 don't yet use it as the internal encoding.
|
|
|
3023
|
|
|
3024 21.4 supports Unicode partially -- as an external encoding for files,
|
|
2537
|
3025 processes, and terminals, but without font support. @xref{Q1.8.9, How
|
|
2417
|
3026 does XEmacs display Unicode?}. To get Unicode support in 21.4,
|
|
|
3027 install Mule-UCS from packages in the usual way, and put
|
|
745
|
3028
|
|
1616
|
3029 @example
|
|
745
|
3030 (require 'un-define)
|
|
|
3031 (set-coding-priority-list '(utf-8))
|
|
1616
|
3032 (set-coding-category-system 'utf-8 'utf-8)
|
|
|
3033 @end example
|
|
|
3034
|
|
|
3035 in your init file to enable the UTF-8 coding system. You may wish to
|
|
|
3036 view the documentation of @code{set-coding-priority-list} if you find
|
|
|
3037 that files that are not UTF-8 are being mis-recognized as UTF-8.
|
|
745
|
3038
|
|
2417
|
3039 Install standard national fonts (not Unicode fonts) for all character
|
|
2537
|
3040 sets you use. @xref{Q1.8.9, How does XEmacs display Unicode??}.
|
|
745
|
3041
|
|
|
3042 Mule-UCS also supports 16-bit forms of Unicode (UTF-16). It does not
|
|
|
3043 support 31-bit forms of Unicode (UTF-32 or UCS-4).
|
|
|
3044
|
|
2537
|
3045 @node Q1.8.9, , Q1.8.8, Introduction
|
|
|
3046 @unnumberedsubsec Q1.8.9: How does XEmacs display Unicode?
|
|
745
|
3047
|
|
|
3048 Mule doesn't have a Unicode charset internally, so there's nothing to
|
|
|
3049 bind a Unicode registry to. It would not be straightforward to create,
|
|
|
3050 either, because Unicode is not ISO 2022-compatible. You'd have to
|
|
|
3051 translate it to multiple 96x96 pages.
|
|
|
3052
|
|
|
3053 This means that Mule-UCS uses ordinary national fonts for display. This
|
|
|
3054 is not really a problem, except for those languages that use the Unified
|
|
|
3055 Han characters. The problem here is that Mule-UCS maps from Unicode
|
|
|
3056 code points to national character sets in a deterministic way. By
|
|
|
3057 default, this means that Japanese fonts are tried first, then Chinese,
|
|
|
3058 then Korean. To change the priority ordering, use the command
|
|
|
3059 `un-define-change-charset-order'.
|
|
|
3060
|
|
|
3061 It also means you can't use Unicode fonts directly, at least not without
|
|
|
3062 extreme hackery. You can run -nw with (set-terminal-coding-system
|
|
|
3063 'utf-8) if you really want a Unicode font for some reason.
|
|
|
3064
|
|
|
3065 Real Unicode support will be introduced in XEmacs 22.0.
|
|
|
3066
|
|
2459
|
3067 @node Installation, Editing, Introduction, Top
|
|
2417
|
3068 @unnumbered 2 Installation and Troubleshooting
|
|
428
|
3069
|
|
|
3070 This is part 2 of the XEmacs Frequently Asked Questions list. This
|
|
2417
|
3071 section is devoted to Installation, Maintenance and Troubleshooting.
|
|
428
|
3072
|
|
|
3073 @menu
|
|
2559
|
3074 2.0: Installation (General)
|
|
|
3075 * Q2.0.1:: How do I build and install XEmacs?
|
|
|
3076 * Q2.0.2:: Where do I find external libraries?
|
|
|
3077 * Q2.0.3:: How do I specify the paths that XEmacs uses for finding files?
|
|
|
3078 * Q2.0.4:: Running XEmacs without installing
|
|
|
3079 * Q2.0.5:: XEmacs is too big
|
|
|
3080
|
|
|
3081 2.1: Package Installation
|
|
|
3082 * Q2.1.1:: How do I install the packages?
|
|
|
3083 * Q2.1.2:: Can I install the packages individually?
|
|
|
3084 * Q2.1.3:: Can I install the packages automatically?
|
|
|
3085 * Q2.1.4:: Can I upgrade or remove packages?
|
|
|
3086 * Q2.1.5:: Which packages to install?
|
|
|
3087 * Q2.1.6:: Can you describe the package location process in more detail?
|
|
|
3088 * Q2.1.7:: EFS fails with "500 AUTH not understood"
|
|
|
3089
|
|
|
3090 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
|
3091 * Q2.2.1:: Libraries in non-standard locations
|
|
|
3092 * Q2.2.2:: Why can't I strip XEmacs?
|
|
3404
|
3093 * Q2.2.3:: X11/bitmaps/gray (or other X11-related file) not found.
|
|
2559
|
3094
|
|
|
3095 2.3: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
3096 * Q2.3.1:: What exactly are all the different ways to build XEmacs under Windows?
|
|
|
3097 * Q2.3.2:: What compiler/libraries do I need to compile XEmacs?
|
|
|
3098 * Q2.3.3:: How do I compile the native port?
|
|
|
3099 * Q2.3.4:: What do I need for Cygwin?
|
|
|
3100 * Q2.3.5:: How do I compile under Cygwin?
|
|
|
3101 * Q2.3.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
|
3102 * Q2.3.7:: How do I compile with X support?
|
|
|
3103 * Q2.3.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
|
3104
|
|
|
3105 2.4: General Troubleshooting
|
|
|
3106 * Q2.4.1:: How do I deal with bugs or with problems building, installing, or running?
|
|
|
3107 * Q2.4.2:: Help! XEmacs just crashed on me!
|
|
|
3108 * Q2.4.3:: XEmacs crashes and I compiled it myself.
|
|
|
3109 * Q2.4.4:: How to debug an XEmacs problem with a debugger
|
|
|
3110 * Q2.4.5:: I get a cryptic error message when trying to do something.
|
|
|
3111 * Q2.4.6:: XEmacs hangs when I try to do something.
|
|
|
3112 * Q2.4.7:: I get an error message when XEmacs is running in batch mode.
|
|
|
3113 * Q2.4.8:: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
|
3114 * Q2.4.9:: @kbd{C-g} doesn't work for me. Is it broken?
|
|
|
3115 * Q2.4.10:: How do I debug process-related problems?
|
|
|
3116 * Q2.4.11:: XEmacs is outputting lots of X errors.
|
|
|
3117 * Q2.4.12:: After upgrading, XEmacs won't do `foo' any more!
|
|
|
3118
|
|
|
3119 2.5: Startup-Related Problems
|
|
|
3120 * Q2.5.1:: XEmacs cannot connect to my X Terminal!
|
|
|
3121 * Q2.5.2:: Startup problems related to paths or package locations.
|
|
|
3122 * Q2.5.3:: XEmacs won't start without network.
|
|
|
3123 * Q2.5.4:: Startup warnings about deducing proper fonts?
|
|
|
3124 * Q2.5.5:: Warnings from incorrect key modifiers.
|
|
|
3125 * Q2.5.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
428
|
3126 @end menu
|
|
|
3127
|
|
2559
|
3128 @unnumberedsec 2.0: Installation (General)
|
|
2417
|
3129
|
|
428
|
3130 @node Q2.0.1, Q2.0.2, Installation, Installation
|
|
2559
|
3131 @unnumberedsubsec Q2.0.1: How do I build and install XEmacs?
|
|
|
3132
|
|
|
3133 See the file @file{etc/NEWS} for information on new features and other
|
|
|
3134 user-visible changes since the last version of XEmacs.
|
|
|
3135
|
|
|
3136 The file @file{INSTALL} in the top-level directory says how to bring
|
|
|
3137 up XEmacs on Unix and Cygwin, once you have loaded the entire subtree
|
|
|
3138 of this directory.
|
|
|
3139
|
|
|
3140 See the file @file{nt/README} for instructions on building XEmacs for
|
|
|
3141 Microsoft Windows.
|
|
|
3142
|
|
|
3143 @xref{Q2.1.1}, for the installation of (essential) add on packages.
|
|
2417
|
3144
|
|
|
3145 @node Q2.0.2, Q2.0.3, Q2.0.1, Installation
|
|
2559
|
3146 @unnumberedsubsec Q2.0.2: Where do I find external libraries?
|
|
2417
|
3147
|
|
2459
|
3148 All external libraries used by XEmacs can be found on the XEmacs web
|
|
2417
|
3149 site
|
|
|
3150 @iftex
|
|
|
3151 @*
|
|
|
3152 @end iftex
|
|
2459
|
3153 @uref{http://www.xemacs.org/Download/optLibs.html}.
|
|
2417
|
3154
|
|
|
3155 The library versions available here are known to work with XEmacs.
|
|
|
3156 (Newer versions will probably work as well but we can't guarantee it.)
|
|
|
3157 We try to keep the libraries up-to-date but may not always succeed.
|
|
2459
|
3158 Check the above page for the canonical locations of the external libraries,
|
|
|
3159 allowing you to download the latest, bleeding-edge versions.
|
|
2417
|
3160
|
|
2559
|
3161 @node Q2.0.3, Q2.0.4, Q2.0.2, Installation
|
|
|
3162 @unnumberedsubsec Q2.0.3: How do I specify the paths that XEmacs uses for finding files?
|
|
2417
|
3163
|
|
|
3164 You can specify what paths to use by using a number of different flags
|
|
|
3165 when running configure. See the section MAKE VARIABLES in the top-level
|
|
|
3166 file INSTALL in the XEmacs distribution for a listing of those flags.
|
|
|
3167
|
|
|
3168 Most of the time, however, the simplest fix is: @strong{do not} specify
|
|
|
3169 paths as you might for GNU Emacs. XEmacs can generally determine the
|
|
|
3170 necessary paths dynamically at run time. The only path that generally
|
|
|
3171 needs to be specified is the root directory to install into. That can
|
|
|
3172 be specified by passing the @code{--prefix} flag to configure. For a
|
|
|
3173 description of the XEmacs install tree, please consult the @file{NEWS}
|
|
|
3174 file.
|
|
|
3175
|
|
2559
|
3176 @node Q2.0.4, Q2.0.5, Q2.0.3, Installation
|
|
|
3177 @unnumberedsubsec Q2.0.4: Running XEmacs without installing
|
|
442
|
3178
|
|
|
3179 How can I just try XEmacs without installing it?
|
|
428
|
3180
|
|
|
3181 XEmacs will run in place without requiring installation and copying of
|
|
|
3182 the Lisp directories, and without having to specify a special build-time
|
|
|
3183 flag. It's the copying of the Lisp directories that requires so much
|
|
|
3184 space. XEmacs is largely written in Lisp.
|
|
|
3185
|
|
|
3186 A good method is to make a shell alias for xemacs:
|
|
|
3187
|
|
|
3188 @example
|
|
2459
|
3189 alias xemacs=/src/xemacs-21.5/src/xemacs
|
|
428
|
3190 @end example
|
|
|
3191
|
|
|
3192 (You will obviously use whatever directory you downloaded the source
|
|
2459
|
3193 tree to instead of @file{/src/xemacs-21.5}).
|
|
428
|
3194
|
|
|
3195 This will let you run XEmacs without massive copying.
|
|
|
3196
|
|
2559
|
3197 @node Q2.0.5, Q2.1.1, Q2.0.4, Installation
|
|
|
3198 @unnumberedsubsec Q2.0.5: XEmacs is too big
|
|
428
|
3199
|
|
442
|
3200 The space required by the installation directories can be
|
|
428
|
3201 reduced dramatically if desired. Gzip all the .el files. Remove all
|
|
442
|
3202 the packages you'll never want to use. Remove the TexInfo manuals.
|
|
428
|
3203 Remove the Info (and use just hardcopy versions of the manual). Remove
|
|
|
3204 most of the stuff in etc. Remove or gzip all the source code. Gzip or
|
|
|
3205 remove the C source code. Configure it so that copies are not made of
|
|
1138
|
3206 the support lisp.
|
|
428
|
3207
|
|
|
3208 These are all Emacs Lisp source code and bytecompiled object code. You
|
|
|
3209 may safely gzip everything named *.el here. You may remove any package
|
|
|
3210 you don't use. @emph{Nothing bad will happen if you delete a package
|
|
|
3211 that you do not use}. You must be sure you do not use it though, so be
|
|
|
3212 conservative at first.
|
|
|
3213
|
|
1648
|
3214 Any package with the possible exceptions of xemacs-base, and EFS are
|
|
|
3215 candidates for removal. Ask yourself, @emph{Do I ever want to use this
|
|
|
3216 package?} If the answer is no, then it is a candidate for removal.
|
|
428
|
3217
|
|
|
3218 First, gzip all the .el files. Then go about package by package and
|
|
|
3219 start gzipping the .elc files. Then run XEmacs and do whatever it is
|
|
1648
|
3220 you normally do. If nothing bad happens, then remove the package. You
|
|
|
3221 can remove a package via the PUI interface
|
|
|
3222 (@code{M-x pui-list-packages}, then press @kbd{d} to mark the packages
|
|
|
3223 you wish to delete, and then @kbd{x} to delete them.
|
|
|
3224
|
|
|
3225 Another method is to do @code{M-x package-get-delete-package}.
|
|
428
|
3226
|
|
2559
|
3227 @unnumberedsec 2.1: Package Installation
|
|
|
3228
|
|
|
3229 @node Q2.1.1, Q2.1.2, Q2.0.5, Installation
|
|
|
3230 @unnumberedsubsec Q2.1.1: How do I install the packages?
|
|
|
3231
|
|
|
3232 There are three ways to install the packages.
|
|
|
3233
|
|
|
3234 @enumerate
|
|
|
3235 @item
|
|
|
3236 Manually, all at once, using the 'Sumo Tarball'.
|
|
|
3237 @item
|
|
|
3238 Manually, using individual package tarballs.
|
|
|
3239 @item
|
|
|
3240 Automatically, using the package tools from XEmacs.
|
|
|
3241 @end enumerate
|
|
|
3242
|
|
|
3243 If you don't want to mess with the packages, it is easiest to just
|
|
|
3244 grab them manually, all at once. (For the other two ways,
|
|
|
3245 @xref{Q2.1.2}, and @xref{Q2.1.3}.) Download the file
|
|
|
3246
|
|
|
3247 @file{xemacs-sumo.tar.gz}
|
|
|
3248
|
|
|
3249 For an XEmacs compiled with Mule you also need
|
|
|
3250
|
|
|
3251 @file{xemacs-mule-sumo.tar.gz}
|
|
|
3252
|
|
|
3253 These are in the @file{packages} directory on your XEmacs mirror
|
|
|
3254 archive: @uref{ftp://ftp.xemacs.org/pub/xemacs/packages} or its
|
|
|
3255 mirrors. N.B. They are called 'Sumo Tarballs' for good reason. They
|
|
|
3256 are currently about 19MB and 4.5MB (gzipped) respectively.
|
|
|
3257
|
|
|
3258 Install them on Unix and Mac OS X using the shell/Terminal command
|
|
|
3259
|
|
|
3260 @code{cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xf -}
|
|
|
3261
|
|
|
3262 Where @samp{$prefix} is what you gave to the @samp{--prefix} flag to
|
|
|
3263 @file{configure}, and defaults to @file{/usr/local}.
|
|
|
3264
|
|
|
3265 If you have GNU tar you can use:
|
|
|
3266
|
|
|
3267 @code{cd $prefix/lib/xemacs ; tar zxvf <tarballname>}
|
|
|
3268
|
|
3018
|
3269 If you have the packages somewhere nonstandard and don't want to bother
|
|
|
3270 with @samp{$prefix} (for example, you're a developer and are compiling
|
|
|
3271 the packages yourself, and want your own private copy of everything),
|
|
|
3272 you can also directly specify this using @file{configure}. To do this
|
|
3179
|
3273 with 21.5 and above use the @samp{--with-late-packages} parameter to
|
|
3018
|
3274 specify the directory under which you untarred the above tarballs.
|
|
|
3275 Under 21.4 and previous you need to use @samp{--package-path}. Using
|
|
|
3276 these options looks something like this:
|
|
2559
|
3277
|
|
|
3278 @example
|
|
|
3279 configure --package-path="~/.xemacs::/src/xemacs/site-packages:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages" ...
|
|
|
3280 @end example
|
|
|
3281
|
|
|
3282 Under Windows, you need to place the above @samp{tar.gz} files in the
|
|
|
3283 directory specified using the @samp{PACKAGE_PREFIX} value in
|
|
|
3284 @file{nt/config.inc} and by default is @file{\Program Files\XEmacs}.
|
|
|
3285 (To untar a @samp{tar.gz} file you will need to use a utility such as
|
|
|
3286 WinZip, unless you have Cygwin or a similar environment installed, in
|
|
|
3287 which case the above Unix shell command should work fine.) If you want
|
|
|
3288 the packages somewhere else, just change @samp{PACKAGE_PREFIX}.
|
|
|
3289
|
|
|
3290 Note that XEmacs finds the packages automatically anywhere underneath
|
|
|
3291 the directory tree where it expects to find the packages. All you
|
|
|
3292 need to do is put stuff there; you don't need to run any program to
|
|
4311
|
3293 tell XEmacs to find the packages, or do anything of that sort.
|
|
2559
|
3294
|
|
|
3295 However, XEmacs will only notice newly installed packages when it
|
|
|
3296 starts up, so you will have to restart if you are already running
|
|
|
3297 XEmacs.
|
|
|
3298
|
|
|
3299 For more details, @xref{Startup Paths,,,xemacs, the XEmacs User's
|
|
|
3300 Manual}, and @xref{Packages,,,xemacs, the XEmacs User's Manual}.
|
|
|
3301
|
|
|
3302 As the Sumo tarballs are not regenerated as often as the individual
|
|
|
3303 packages, it is recommended that you use the automatic package tools
|
|
|
3304 afterwards to pick up any recent updates.
|
|
|
3305
|
|
|
3306 @emph{NOTE}: For detailed information about how the package
|
|
|
3307 hierarchies work, @xref{Package Overview,,,lispref, the XEmacs Lisp
|
|
|
3308 Reference Manual}.
|
|
|
3309
|
|
|
3310 @node Q2.1.2, Q2.1.3, Q2.1.1, Installation
|
|
|
3311 @unnumberedsubsec Q2.1.2: Can I install the packages individually?
|
|
|
3312
|
|
|
3313 Yes, you can download individual packages from the FTP site (@pxref{Q2.1.1}). Since packages are automatically noticed at startup, you just have to put them in the right place.
|
|
|
3314
|
|
|
3315 Note: If you are upgrading packages already installed, it's best to
|
|
|
3316 remove the old package first (@pxref{Q2.1.4}).
|
|
|
3317
|
|
|
3318 For example if we are installing the @samp{xemacs-base}
|
|
|
3319 package (version 1.48):
|
|
|
3320
|
|
|
3321 @example
|
|
|
3322 mkdir $prefix/lib/xemacs/xemacs-packages RET # if it does not exist yet
|
|
|
3323 cd $prefix/lib/xemacs/xemacs-packages RET
|
|
|
3324 gunzip -c /path/to/xemacs-base-1.48-pkg.tar.gz | tar xvf - RET
|
|
|
3325 @end example
|
|
|
3326
|
|
|
3327 Or if you have GNU tar, the last step can be:
|
|
|
3328
|
|
|
3329 @example
|
|
|
3330 tar zxvf /path/to/xemacs-base-1.48-pkg.tar.gz RET
|
|
|
3331 @end example
|
|
|
3332
|
|
|
3333 For MULE related packages, it is best to untar into the @samp{mule-packages}
|
|
|
3334 hierarchy, i.e. for the @samp{mule-base} package, version 1.37:
|
|
|
3335
|
|
|
3336 @example
|
|
|
3337 mkdir $prefix/lib/xemacs/mule-packages RET # if it does not exist yet
|
|
|
3338 cd $prefix/lib/xemacs/mule-packages RET
|
|
|
3339 gunzip -c /path/to/mule-base-1.37-pkg.tar.gz | tar xvf - RET
|
|
|
3340 @end example
|
|
|
3341
|
|
|
3342 Or if you have GNU tar, the last step can be:
|
|
|
3343
|
|
|
3344 @example
|
|
|
3345 tar zxvf /path/to/mule-base-1.37-pkg.tar.gz RET
|
|
|
3346 @end example
|
|
|
3347
|
|
|
3348 @node Q2.1.3, Q2.1.4, Q2.1.2, Installation
|
|
|
3349 @unnumberedsubsec Q2.1.3: Can I install the packages automatically?
|
|
|
3350
|
|
|
3351 XEmacs comes with some tools to make the periodic updating and
|
|
|
3352 installing easier. It will notice if new packages or versions are
|
|
|
3353 available and will fetch them from the FTP site.
|
|
|
3354
|
|
|
3355 Unfortunately this requires that a few packages are already in place.
|
|
|
3356 You will have to install them by hand as above or use a SUMO tarball.
|
|
|
3357 This requirement will hopefully go away in the future. The packages
|
|
|
3358 you need are:
|
|
|
3359
|
|
|
3360 @example
|
|
|
3361 efs - To fetch the files from the FTP site or mirrors.
|
|
|
3362 xemacs-base - Needed by efs.
|
|
|
3363 @end example
|
|
|
3364
|
|
|
3365 and optionally:
|
|
|
3366
|
|
|
3367 @example
|
|
|
3368 mailcrypt - For PGP verification of the package-index file.
|
|
|
3369 @end example
|
|
|
3370
|
|
|
3371 After installing these by hand, fire up XEmacs and follow these
|
|
|
3372 steps.
|
|
|
3373
|
|
|
3374 @enumerate
|
|
|
3375 @item
|
|
|
3376 Choose a download site.
|
|
|
3377 @itemize @bullet
|
|
|
3378 @item
|
|
|
3379 via menu: Tools -> Packages -> Set Download Site
|
|
|
3380 @item
|
|
|
3381 via keyb: M-x customize-variable RET package-get-remote RET
|
|
|
3382 (put in the details of remote host and directory)
|
|
|
3383 @end itemize
|
|
|
3384
|
|
|
3385 If the package tarballs _AND_ the package-index file are in a
|
|
|
3386 local directory, you can: M-x pui-set-local-package-get-directory RET
|
|
|
3387
|
|
|
3388 @item
|
|
|
3389 Obtain a list of packages and display the list in a buffer named
|
|
|
3390 "*Packages*".
|
|
|
3391 @itemize @bullet
|
|
|
3392 @item
|
|
|
3393 menu: Tools -> Packages -> List & Install
|
|
|
3394 @item
|
|
|
3395 keyb: M-x pui-list-packages RET
|
|
|
3396 @end itemize
|
|
|
3397
|
|
|
3398 XEmacs will now connect to the remote site and download the
|
|
|
3399 latest package-index file.
|
|
|
3400
|
|
|
3401 The resulting buffer, "*Packages*" has brief instructions at the
|
|
|
3402 end of the buffer.
|
|
|
3403
|
|
|
3404 @item
|
|
|
3405 Choose the packages you wish to install.
|
|
|
3406 @itemize @bullet
|
|
|
3407 @item
|
|
|
3408 mouse: Click button 2 on the package name.
|
|
|
3409 @item
|
|
|
3410 keyb: RET on the package name
|
|
|
3411 @end itemize
|
|
|
3412
|
|
|
3413 @item
|
|
|
3414 Make sure you have everything you need.
|
|
|
3415 @itemize @bullet
|
|
|
3416 @item
|
|
|
3417 menu: Packages -> Add Required
|
|
|
3418 @item
|
|
|
3419 keyb: r
|
|
|
3420 @end itemize
|
|
|
3421
|
|
|
3422 XEmacs will now search for packages that are required by the
|
|
|
3423 ones that you have chosen to install and offer to select
|
|
|
3424 those packages also.
|
|
|
3425
|
|
|
3426 For novices and gurus alike, this step can save your bacon.
|
|
|
3427 It's easy to forget to install a critical package.
|
|
|
3428
|
|
|
3429 @item
|
|
|
3430 Download and install the packages.
|
|
|
3431 @itemize @bullet
|
|
|
3432 @item
|
|
|
3433 menu: Packages -> Install/Remove Selected
|
|
|
3434 @item
|
|
|
3435 keyb: x
|
|
|
3436 @end itemize
|
|
|
3437 @end enumerate
|
|
|
3438
|
|
|
3439 @node Q2.1.4, Q2.1.5, Q2.1.3, Installation
|
|
|
3440 @unnumberedsubsec Q2.1.4: Can I upgrade or remove packages?
|
|
|
3441
|
|
|
3442 As the exact files and their locations contained in a package may
|
|
|
3443 change it is recommended to remove a package first before installing a
|
|
4311
|
3444 new version. In order to facilitate removal each package contains a
|
|
|
3445 pkginfo/MANIFEST.pkgname file which lists all the files belonging to
|
|
|
3446 the package. M-x package-admin-delete-binary-package RET can be used
|
|
|
3447 to remove a package using this file.
|
|
2559
|
3448
|
|
|
3449 Note that the interactive package tools included with XEmacs already do
|
|
|
3450 this for you.
|
|
|
3451
|
|
|
3452 @node Q2.1.5, Q2.1.6, Q2.1.4, Installation
|
|
|
3453 @unnumberedsubsec Q2.1.5: Which packages to install?
|
|
|
3454
|
|
|
3455 Unless you are an advanced user, just install everything.
|
|
|
3456
|
|
|
3457 If you really want to install only what's absolutely needed, a good
|
|
|
3458 minimal set of packages for XEmacs-latin1 would be
|
|
|
3459
|
|
|
3460 @example
|
|
|
3461 xemacs-base, xemacs-devel, c-support, cc-mode, debug, dired, efs,
|
|
|
3462 edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes,
|
|
|
3463 text-modes, time, mailcrypt
|
|
|
3464 @end example
|
|
|
3465
|
|
|
3466 If you are using the XEmacs package tools, don't forget to do:
|
|
|
3467
|
|
|
3468 @example
|
|
|
3469 Packages -> Add Required
|
|
|
3470 @end example
|
|
|
3471
|
|
|
3472 To make sure you have everything that the packages you have chosen to
|
|
|
3473 install need.
|
|
|
3474
|
|
|
3475 @xref{Q1.7.2}, for a description of the various packages.
|
|
|
3476
|
|
|
3477 @node Q2.1.6, Q2.1.7, Q2.1.5, Installation
|
|
|
3478 @unnumberedsubsec Q2.1.6: Can you describe the package location process in more detail?
|
|
|
3479
|
|
|
3480 On startup XEmacs looks for packages in so-called package hierarchies.
|
|
|
3481 Normally, there are three system wide hierarchies, like this:
|
|
|
3482
|
|
|
3483 @example
|
|
|
3484 $prefix/lib/xemacs/xemacs-packages/
|
|
|
3485 Normal packages go here.
|
|
|
3486
|
|
|
3487 $prefix/lib/xemacs/mule-packages/
|
|
|
3488 Mule packages go here and are only searched by MULE-enabled XEmacsen.
|
|
|
3489
|
|
|
3490 $prefix/lib/xemacs/site-packages/
|
|
|
3491 Local and 3rd party packages go here.
|
|
|
3492 @end example
|
|
|
3493
|
|
|
3494 This is what you get when you untar the SUMO tarballs under
|
|
|
3495 @file{$prefix/lib/xemacs}.
|
|
|
3496
|
|
|
3497 @file{$prefix} is specified using the @samp{--prefix} parameter to
|
|
|
3498 @file{configure}, and defaults to @file{usr/local}.
|
|
|
3499
|
|
|
3500 If the package path is not explicitly specified, XEmacs looks for the
|
|
|
3501 package directory @file{xemacs-packages} (and @file{mule-packages} and
|
|
|
3502 @file{site-packages}) first under @samp{~/.xemacs}, then for a sister
|
|
|
3503 directory @file{lib/xemacs-VERSION} of the directory in which the
|
|
|
3504 XEmacs executable is located, then for a sister directory
|
|
|
3505 @file{lib/xemacs}. The XEmacs executable (under Unix at least) is
|
|
|
3506 installed by default in @file{/usr/local/bin}; this explains why
|
|
|
3507 XEmacs in its default installation will find packages that you put
|
|
|
3508 under @file{/usr/local/lib/xemacs}.
|
|
|
3509
|
|
|
3510 You can specify where exactly XEmacs looks for packages by using the
|
|
3179
|
3511 @samp{--with-user-packages} (an alias for @samp{--with-early-packages})
|
|
|
3512 or @samp{--with-system-packages} (an alias for
|
|
|
3513 @samp{--with-late-packages}) or @samp{--with-legacy-packages}
|
|
|
3514 (an alias for @samp{--with-last-packages})
|
|
|
3515 parameters to @file{configure} (or the equivalent settings in
|
|
|
3516 @file{config.inc}, under Windows), or setting the
|
|
|
3517 @samp{EMACSEARLYPACKAGES}, @samp{EMACSLATEPACKAGES}, and
|
|
|
3518 @samp{EMACSLASTPACKAGES} environment variables (which have the same
|
|
|
3519 format as the configure options). @xref{Q2.1.1}.
|
|
2559
|
3520
|
|
|
3521 See @file{configure.usage} for more info about the format of these
|
|
|
3522 @file{configure} parameters.
|
|
|
3523
|
|
|
3524 In addition to the system wide packages, each user can have his own
|
|
|
3525 packages installed under @file{~/.xemacs/}. If you want to install
|
|
|
3526 packages there using the interactive tools, you need to set
|
|
|
3527 @code{package-get-install-to-user-init-directory} to @code{t}.
|
|
|
3528
|
|
|
3529 The site-packages hierarchy replaces the old @file{site-lisp}
|
|
|
3530 directory. XEmacs no longer looks into a @file{site-lisp} directly by
|
|
|
3531 default. A good place to put @file{site-start.el} would be in
|
|
|
3532 @file{$prefix/lib/xemacs/site-packages/lisp/}.
|
|
|
3533
|
|
|
3534 @node Q2.1.7, Q2.2.1, Q2.1.6, Installation
|
|
|
3535 @unnumberedsubsec Q2.1.7: EFS fails with "500 AUTH not understood" (NEW)
|
|
2417
|
3536
|
|
|
3537 A typical error: FTP Error: USER request failed; 500 AUTH not understood.
|
|
|
3538
|
|
4311
|
3539 Thanks to Giacomo Boffi @email{giacomo.boffi@@polimi.it} who recommends
|
|
2417
|
3540 on comp.emacs.xemacs:
|
|
|
3541
|
|
|
3542 tell your ftp client to not attempt AUTH authentication (or do not
|
|
|
3543 use FTP servers that don't understand AUTH)
|
|
|
3544
|
|
|
3545 and notes that you need to add an element (often "-u") to
|
|
|
3546 `efs-ftp-program-args'. Use M-x customize-variable, and verify the
|
|
|
3547 needed flag with `man ftp' or other local documentation.
|
|
|
3548
|
|
2559
|
3549 @unnumberedsec 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW)
|
|
|
3550
|
|
|
3551 @node Q2.2.1, Q2.2.2, Q2.1.7, Installation
|
|
|
3552 @unnumberedsubsec Q2.2.1: Libraries in non-standard locations
|
|
428
|
3553
|
|
2459
|
3554 If your libraries are in a non-standard location, you can specify the location
|
|
3018
|
3555 using the following flags to @file{configure}. Under 21.4 or earlier:
|
|
2459
|
3556
|
|
|
3557 @example
|
|
|
3558 --site-libraries=WHATEVER
|
|
|
3559 --site-includes=WHATEVER
|
|
|
3560 @end example
|
|
|
3561
|
|
3018
|
3562 Under 21.5 or later:
|
|
|
3563
|
|
|
3564 @example
|
|
|
3565 --with-site-libraries=WHATEVER
|
|
|
3566 --with-site-includes=WHATEVER
|
|
|
3567 @end example
|
|
|
3568
|
|
2459
|
3569 If you have multiple paths to specify, use the following syntax:
|
|
428
|
3570
|
|
|
3571 @example
|
|
|
3572 --site-libraries='/path/one /path/two /path/etc'
|
|
|
3573 @end example
|
|
|
3574
|
|
3018
|
3575 If the libraries and headers reside in the directories @samp{lib} and
|
|
|
3576 @samp{include} of a common root (say @samp{/sw}) then both can be
|
|
|
3577 specified with a single option:
|
|
|
3578
|
|
|
3579 @example
|
|
|
3580 --site-prefixes=WHATEVER
|
|
|
3581 @end example
|
|
|
3582
|
|
|
3583 or for 21.5:
|
|
|
3584
|
|
|
3585 @example
|
|
|
3586 --with-site-prefixes=WHATEVER
|
|
|
3587 @end example
|
|
|
3588
|
|
3404
|
3589 @node Q2.2.2, Q2.2.3, Q2.2.1, Installation
|
|
2559
|
3590 @unnumberedsubsec Q2.2.2: Why can't I strip XEmacs?
|
|
428
|
3591
|
|
|
3592 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:
|
|
|
3593
|
|
|
3594 @quotation
|
|
|
3595 Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The
|
|
|
3596 link gives you a bare-boned emacs (called temacs). temacs is then run,
|
|
|
3597 preloading some of the lisp files. The result is then dumped into a new
|
|
|
3598 executable, named xemacs, which will contain all of the preloaded lisp
|
|
|
3599 functions and data.
|
|
|
3600
|
|
|
3601 Now, during the dump itself, the executable (code+data+symbols) is
|
|
|
3602 written on disk using a special unexec() function. This function is
|
|
|
3603 obviously heavily system dependent. And on some systems, it leads to an
|
|
|
3604 executable which, although valid, cannot be stripped without damage. If
|
|
|
3605 memory serves, this is especially the case for AIX binaries. On other
|
|
462
|
3606 architectures it might work OK.
|
|
428
|
3607
|
|
|
3608 The Right Way to strip the emacs binary is to strip temacs prior to
|
|
|
3609 dumping xemacs. This will always work, although you can do that only if
|
|
|
3610 you install from sources (as temacs is @file{not} part of the binary
|
|
|
3611 kits).
|
|
|
3612 @end quotation
|
|
|
3613
|
|
|
3614 @email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes:
|
|
|
3615
|
|
|
3616 @quotation
|
|
|
3617 Here is the trick:
|
|
|
3618
|
|
|
3619 @enumerate
|
|
|
3620 @item
|
|
|
3621 [ ./configure; make ]
|
|
|
3622
|
|
|
3623 @item
|
|
|
3624 rm src/xemacs
|
|
|
3625
|
|
|
3626 @item
|
|
|
3627 strip src/temacs
|
|
|
3628
|
|
|
3629 @item
|
|
|
3630 make
|
|
|
3631
|
|
|
3632 @item
|
|
|
3633 cp src/xemacs /usr/local/bin/xemacs
|
|
|
3634
|
|
|
3635 @item
|
|
|
3636 cp lib-src/DOC-19.16-XEmacs
|
|
|
3637 @iftex
|
|
|
3638 \ @*
|
|
|
3639 @end iftex
|
|
|
3640 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
|
|
|
3641 @end enumerate
|
|
|
3642 @end quotation
|
|
|
3643
|
|
3404
|
3644 @node Q2.2.3, Q2.3.1, Q2.2.2, Installation
|
|
|
3645 @unnumberedsubsec Q2.2.3: X11/bitmaps/gray (or other X11-related file) not found.
|
|
|
3646
|
|
|
3647 The X11R6 distribution was monolithic, but the X11R7 distribution is
|
|
|
3648 much more modular. Many OS distributions omit these bitmaps (assuming
|
|
|
3649 nobody uses them, evidently). Your OS distribution should have a
|
|
|
3650 developer's package containing these files, probably with a name
|
|
|
3651 containing the string "bitmap". Known package names (you may need to
|
|
|
3652 add an extension such as .deb or .rpm) include x11/xbitmaps (Ubuntu)
|
|
|
3653 and xorg-x11-xbitmaps (Fedora Core 5).
|
|
|
3654
|
|
2559
|
3655 @unnumberedsec 2.3: Windows Installation (Windows, Cygwin, MinGW)
|
|
|
3656
|
|
3404
|
3657 @node Q2.3.1, Q2.3.2, Q2.2.3, Installation
|
|
2559
|
3658 @unnumberedsubsec Q2.3.1: What exactly are all the different ways to build XEmacs under Windows?
|
|
2417
|
3659
|
|
|
3660 XEmacs can be built in several ways in the MS Windows environment.
|
|
|
3661
|
|
|
3662 The standard way is what we call the "native" port. It uses the Win32
|
|
|
3663 API and has no connection with X whatsoever -- it does not require X
|
|
|
3664 libraries to build, nor does it require an X server to run. The native
|
|
|
3665 port is the most reliable version and provides the best graphical
|
|
|
3666 support. Almost all development is geared towards this version, and
|
|
|
3667 there is little reason not to use it.
|
|
|
3668
|
|
|
3669 The second way to build is the Cygwin port. It takes advantage of
|
|
2537
|
3670 Cygnus emulation library under Win32. @xref{Q1.2.5, What are Cygwin
|
|
2417
|
3671 and MinGW, and do I need them to run XEmacs?}, for more information.
|
|
|
3672
|
|
|
3673 A third way is the MinGW port. It uses the Cygwin environment to
|
|
2537
|
3674 build but does not require it at runtime. @xref{Q1.2.5, What are
|
|
2417
|
3675 Cygwin and MinGW, and do I need them to run XEmacs?}, for more
|
|
|
3676 information.
|
|
|
3677
|
|
|
3678 Finally, you might also be able to build the non-Cygwin, non-MinGW "X"
|
|
|
3679 port. This was actually the first version of XEmacs that ran under MS
|
|
|
3680 Windows, and although the code is still in XEmacs, it's essentially
|
|
|
3681 orphaned and it's unlikely it will compile without a lot of work. If
|
|
|
3682 you want an MS Windows versin of XEmacs that supports X, use the Cygwin
|
|
|
3683 version. (The X support there is actively maintained, so that Windows
|
|
|
3684 developers can test the X support in XEmacs.)
|
|
|
3685
|
|
2559
|
3686 @node Q2.3.2, Q2.3.3, Q2.3.1, Installation
|
|
|
3687 @unnumberedsubsec Q2.3.2: What compiler/libraries do I need to compile XEmacs?
|
|
2417
|
3688
|
|
|
3689 You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have
|
|
|
3690 some beta testers currently trying to compile with VC.NET, aka version
|
|
|
3691 7.0, but we can't yet report complete success.) For the Cygwin and
|
|
|
3692 MinGW versions, you need the Cygwin environment, which comes with GCC,
|
|
2537
|
3693 the compiler used for those versions. @xref{Q1.2.5, What are Cygwin
|
|
2417
|
3694 and MinGW, and do I need them to run XEmacs?}, for more information on
|
|
|
3695 Cygwin and MinGW.
|
|
|
3696
|
|
2559
|
3697 @node Q2.3.3, Q2.3.4, Q2.3.2, Installation
|
|
|
3698 @unnumberedsubsec Q2.3.3: How do I compile the native port?
|
|
2417
|
3699
|
|
|
3700 Please read the file @file{nt/README} in the XEmacs distribution, which
|
|
|
3701 contains the full description.
|
|
|
3702
|
|
2559
|
3703 @node Q2.3.4, Q2.3.5, Q2.3.3, Installation
|
|
|
3704 @unnumberedsubsec Q2.3.4: What do I need for Cygwin?
|
|
2417
|
3705
|
|
|
3706 You can find the Cygwin tools and compiler at:
|
|
|
3707
|
|
|
3708 @uref{http://www.cygwin.com/}
|
|
|
3709
|
|
|
3710 Click on the @samp{Install or update now!} link, which will download a
|
|
|
3711 file @file{setup.exe}, which you can use to download everything
|
|
|
3712 else. (You will need to pick a mirror site; @samp{mirrors.rcn.net} is
|
|
|
3713 probably the best.) You should go ahead and install everything --
|
|
|
3714 you'll get various ancillary libraries that XEmacs needs or likes,
|
|
|
3715 e.g. XPM, PNG, JPEG, TIFF, etc. You can also get X Windows here, if you
|
|
|
3716 want to compile under X.
|
|
|
3717
|
|
|
3718 If you want to compile without X, you will need the @file{xpm-nox}
|
|
|
3719 library, which must be specifically selected in the Cygwin netinstaller;
|
|
|
3720 it is not selected by default. The package has had various names.
|
|
|
3721 Currently it is called @file{cygXpm-noX4.dll}.
|
|
|
3722
|
|
2559
|
3723 @node Q2.3.5, Q2.3.6, Q2.3.4, Installation
|
|
|
3724 @unnumberedsubsec Q2.3.5: How do I compile under Cygwin?
|
|
2417
|
3725
|
|
|
3726 Similar as on Unix; use the usual `configure' and `make' process.
|
|
|
3727 Some problems to watch out for:
|
|
|
3728
|
|
|
3729 @itemize @bullet
|
|
|
3730 @item
|
|
|
3731 make sure HOME is set. This controls where you
|
|
|
3732 @file{init.el} file comes from;
|
|
|
3733
|
|
|
3734 @item
|
|
|
3735 @samp{CYGWIN} needs to be set to @samp{tty} for process support to work;
|
|
|
3736
|
|
|
3737 @item
|
|
|
3738 picking up some other grep or other UNIX-like tools can kill configure;
|
|
|
3739
|
|
|
3740 @item
|
|
|
3741 static heap too small, adjust @file{src/sheap-adjust.h} to a more positive
|
|
|
3742 number;
|
|
|
3743
|
|
|
3744 @item
|
|
|
3745 (Unconfirmed) The Cygwin version doesn't understand
|
|
|
3746 @file{//machine/path} type paths so you will need to manually mount a
|
|
|
3747 directory of this form under a unix style directory for a build to work
|
|
|
3748 on the directory;
|
|
|
3749
|
|
|
3750 @item
|
|
|
3751 If you're building @strong{WITHOUT} X11, don't forget to change symlinks
|
|
|
3752 @file{/usr/lib/libXpm.a} and @file{/usr/lib/libXpm.dll.a} to point to
|
|
|
3753 the non-X versions of these libraries. By default they point to the X
|
|
|
3754 versions. So:
|
|
|
3755
|
|
|
3756 @example
|
|
|
3757 /usr/lib/libXpm.a -> /usr/lib/libXpm-noX.a
|
|
|
3758 /usr/lib/libXpm.dll.a -> /usr/lib/libXpm-noX.dll.a
|
|
|
3759 @end example
|
|
|
3760
|
|
|
3761 (This advice may now be obsolete because of the availability of the
|
|
|
3762 cygXpm-noX4.dll package from Cygwin. Send confirmation to
|
|
|
3763 @email{faq@@xemacs.org}.)
|
|
|
3764
|
|
|
3765 @item
|
|
|
3766 Other problems are listed in the @file{PROBLEMS} file, in the top-level
|
|
|
3767 directory of the XEmacs sources.
|
|
|
3768
|
|
|
3769 @end itemize
|
|
|
3770
|
|
|
3771
|
|
2559
|
3772 @node Q2.3.6, Q2.3.7, Q2.3.5, Installation
|
|
|
3773 @unnumberedsubsec Q2.3.6: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
|
|
2417
|
3774
|
|
|
3775 Similar to the method for Unix. Things to remember:
|
|
|
3776
|
|
|
3777 @itemize @bullet
|
|
|
3778 @item
|
|
|
3779 Specify the target host on the command line for @file{./configure}, e.g.
|
|
|
3780 @samp{./configure i586-pc-mingw32}.
|
|
|
3781
|
|
|
3782 @item
|
|
|
3783 Be sure that your build directory is mounted such that it has the
|
|
|
3784 same path either as a cygwin path (@file{/build/xemacs}) or as a Windows
|
|
|
3785 path (@file{c:\build\xemacs}).
|
|
|
3786
|
|
|
3787 @item
|
|
|
3788 Build @samp{gcc -mno-cygwin} versions of the extra libs, i.e. @file{libpng},
|
|
|
3789 @file{compface}, etc.
|
|
|
3790
|
|
|
3791 @item
|
|
|
3792 Specify the target location of the extra libs on the command line
|
|
3018
|
3793 to @file{configure}, e.g.for 21.4 or earlier
|
|
|
3794 @samp{./configure --site-prefixes=/build/libs i586-pc-mingw32} and for
|
|
|
3795 21.5 or later
|
|
|
3796 @samp{./configure --with-site-prefixes=/build/libs i586-pc-mingw32}.
|
|
2417
|
3797 @end itemize
|
|
|
3798
|
|
2559
|
3799 @node Q2.3.7, Q2.3.8, Q2.3.6, Installation
|
|
|
3800 @unnumberedsubsec Q2.3.7: How do I compile with X support?
|
|
2417
|
3801
|
|
|
3802 To compile under Cygwin, all you need to do is install XFree86, which
|
|
|
3803 is available as part of the standard Cygwin installation.
|
|
|
3804 @uref{http://www.cygwin.com/}. Once installed, @file{configure}
|
|
|
3805 should automatically find the X libraries and compile with X support.
|
|
|
3806
|
|
|
3807 As noted above, the non-Cygwin X support is basically orphaned, and
|
|
|
3808 probably won't work. But if it want to try, it's described in
|
|
|
3809 @file{nt/README} in some detail. Basically, you need to get X11
|
|
2459
|
3810 libraries from @uref{http://ftp.x.org}, and compile them. If the
|
|
2417
|
3811 precompiled versions are available somewhere, we don't know of it.
|
|
|
3812
|
|
2559
|
3813 @node Q2.3.8, Q2.4.1, Q2.3.7, Installation
|
|
|
3814 @unnumberedsubsec Q2.3.8: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW)
|
|
1058
|
3815
|
|
|
3816 The Cygwin binary distributed with the netinstaller uses an external DLL
|
|
|
3817 to handle XPM images (such as toolbar buttons). You may get an error like
|
|
|
3818
|
|
2559
|
3819 @example
|
|
|
3820 This application has failed to start because cygXpm-noX4.dll was not found.
|
|
|
3821 Re-installing the application may fix this problem.
|
|
|
3822 @end example
|
|
1058
|
3823
|
|
|
3824 Andy Piper <andy@@xemacs.org> sez:
|
|
|
3825
|
|
2559
|
3826 @example
|
|
|
3827 cygXpm-noX4 is part of the cygwin distribution under libraries or
|
|
|
3828 graphics, but is not installed by default. You need to run the
|
|
|
3829 cygwin setup again and select this package.
|
|
|
3830 @end example
|
|
1058
|
3831
|
|
|
3832 Ie, reinstalling XEmacs won't help because it is not part of the XEmacs
|
|
|
3833 distribution.
|
|
|
3834
|
|
2559
|
3835 @unnumberedsec 2.4: General Troubleshooting
|
|
|
3836
|
|
|
3837 @node Q2.4.1, Q2.4.2, Q2.3.8, Installation
|
|
|
3838 @unnumberedsubsec Q2.4.1: How do I deal with bugs or with problems building, installing, or running?
|
|
|
3839
|
|
|
3840 The file @file{PROBLEMS} contains information on many common problems that
|
|
|
3841 occur in building, installing and running XEmacs.
|
|
|
3842
|
|
|
3843 Reports of bugs in XEmacs should be sent to
|
|
|
3844 @email{xemacs-beta@@xemacs.org}. You can also post to the newsgroup
|
|
|
3845 comp.emacs.xemacs (or equivalentlt, send to the mailing list
|
|
|
3846 @email{xemacs@@xemacs.org}), but it is less likely that the developers
|
|
|
3847 will see it in a timely fashion. @xref{Bugs,,, xemacs, the XEmacs
|
|
|
3848 User's Manual}, for more information on how to report bugs.
|
|
|
3849 @xref{Q1.4.2}, for more information on mailing lists relating to
|
|
|
3850 XEmacs.
|
|
|
3851
|
|
|
3852 There are three ways to read the Bugs section.
|
|
|
3853
|
|
|
3854 @enumerate
|
|
|
3855 @item
|
|
|
3856 In a printed copy of the XEmacs manual.
|
|
|
3857
|
|
|
3858 @item
|
|
|
3859 With Info. First, start XEmacs. From the menu, select
|
|
|
3860 @samp{Help->Info (Online Docs)->Info Contents} to enter Info, then
|
|
|
3861 click on @samp{XEmacs}, then on @samp{Bugs}. Or, use the keyboard: do
|
|
|
3862 @kbd{C-h i} to enter Info, then @kbd{m XEmacs RET} to get to the Emacs
|
|
|
3863 manual, then @kbd{m Bugs RET} to get to the section on bugs. Or use
|
|
|
3864 standalone Info in a like manner. (Standalone Info is part of the
|
|
|
3865 Texinfo distribution, not part of the XEmacs distribution.)
|
|
|
3866
|
|
|
3867 @item
|
|
|
3868 By hand. Do
|
|
|
3869 @example
|
|
|
3870 cat info/xemacs* | more "+/^File: xemacs.info, Node: Bugs,"
|
|
|
3871 @end example
|
|
|
3872 @end enumerate
|
|
|
3873
|
|
|
3874 @node Q2.4.2, Q2.4.3, Q2.4.1, Installation
|
|
|
3875 @unnumberedsubsec Q2.4.2: Help! XEmacs just crashed on me!
|
|
428
|
3876
|
|
|
3877 First of all, don't panic. Whenever XEmacs crashes, it tries extremely
|
|
|
3878 hard to auto-save all of your files before dying. (The main time that
|
|
|
3879 this will not happen is if the machine physically lost power or if you
|
|
|
3880 killed the XEmacs process using @code{kill -9}). The next time you try
|
|
|
3881 to edit those files, you will be informed that a more recent auto-save
|
|
|
3882 file exists. You can use @kbd{M-x recover-file} to retrieve the
|
|
|
3883 auto-saved version of the file.
|
|
|
3884
|
|
462
|
3885 You can use the command @kbd{M-x recover-session} after a crash to pick
|
|
|
3886 up where you left off.
|
|
428
|
3887
|
|
|
3888 Now, XEmacs is not perfect, and there may occasionally be times, or
|
|
|
3889 particular sequences of actions, that cause it to crash. If you can
|
|
|
3890 come up with a reproducible way of doing this (or even if you have a
|
|
|
3891 pretty good memory of exactly what you were doing at the time), the
|
|
2417
|
3892 maintainers would be very interested in knowing about it. The best
|
|
|
3893 way to report a bug is using @kbd{M-x report-emacs-bug} (or by
|
|
|
3894 selecting @samp{Send Bug Report...} from the Help menu). If that
|
|
|
3895 won't work (e.g. you can't get XEmacs working at all), send ordinary
|
|
|
3896 mail to @email{xemacs-beta@@xemacs.org}. @emph{MAKE SURE} to include
|
|
|
3897 the output from the crash, especially including the Lisp backtrace, as
|
|
|
3898 well as the XEmacs configuration from @kbd{M-x describe-installation}
|
|
|
3899 (or equivalently, the file @file{Installation} in the top of the build
|
|
|
3900 tree). Note that the developers do @emph{not} usually follow
|
|
|
3901 @samp{comp.emacs.xemacs} on a regular basis; thus, this is better for
|
|
|
3902 general questions about XEmacs than bug reports.
|
|
428
|
3903
|
|
1183
|
3904 If at all possible, include a C stack backtrace of the core dump that
|
|
2417
|
3905 was produced. This shows where exactly things went wrong, and makes
|
|
|
3906 it much easier to diagnose problems. To do this under Unix and Mac OS
|
|
|
3907 X, you need to locate the core file (it's called @file{core}, and is
|
|
|
3908 usually sitting in the directory that you started XEmacs from, or your
|
|
|
3909 home directory if that other directory was not writable). Then, go to
|
|
|
3910 that directory and execute a command like:
|
|
428
|
3911
|
|
|
3912 @example
|
|
|
3913 gdb `which xemacs` core
|
|
|
3914 @end example
|
|
|
3915
|
|
|
3916 and then issue the command @samp{where} to get the stack backtrace. You
|
|
|
3917 might have to use @code{dbx} or some similar debugger in place of
|
|
|
3918 @code{gdb}. If you don't have any such debugger available, complain to
|
|
|
3919 your system administrator.
|
|
|
3920
|
|
2417
|
3921 It's possible that a core file didn't get produced or the stack trace
|
|
|
3922 from gdb is garbage, in which case you're out of luck unless you can
|
|
|
3923 reproduce the bug. A nonexistent core file can happen in some
|
|
|
3924 circumstances on some operating systems, depending on what exactly
|
|
|
3925 triggered the crash. It's also possible, however, that your limits
|
|
|
3926 are set to turn them off. You may be able to reenable them using a
|
|
|
3927 command like @samp{unlimit coredumpsize} or @samp{ulimit -c}. (To find
|
|
|
3928 out how your limits are set, use the command @samp{limit}.) However, if
|
|
|
3929 you didn't explicitly set your limits this way, go complain to your
|
|
|
3930 system administrator and tell him not to disable core files by
|
|
|
3931 default.
|
|
|
3932
|
|
|
3933 A garbaged stack trace can happen for various reasons. Some versions
|
|
|
3934 of gdb are broken on certain operating systems and aren't able to read
|
|
|
3935 the core file. It's also possible that the stack got overwritten
|
|
|
3936 during the crash. A very simple reason, however, is that your version
|
|
|
3937 of XEmacs was compiled without debugging information or had the
|
|
|
3938 debugging information stripped. A compilation with optimization can
|
|
|
3939 also result in partly or completely garbaged stack trace. In such
|
|
|
3940 cases, you will need to recompile XEmacs with debugging information
|
|
2559
|
3941 and without optimization; @xref{Q2.4.4, How to debug an XEmacs problem
|
|
2417
|
3942 with a debugger}. Note also that core files currently don't work at
|
|
|
3943 all under Cygwin, and the only way to get a backtrace is to run XEmacs
|
|
|
3944 from gdb.
|
|
|
3945
|
|
|
3946 If you cannot get a backtrace from the core dump, but can reproduce
|
|
|
3947 the problem, try running XEmacs under gdb. The goal is to get clean C
|
|
|
3948 and Lisp backtraces and submit a bug report including full
|
|
|
3949 configuration information as described above, as this will greatly
|
|
|
3950 assist in the process of tracking down the bug. However, even partial
|
|
|
3951 information is better than none. The process of getting backtraces
|
|
2559
|
3952 from gdb is described in detail in @ref{Q2.4.4, How to debug an XEmacs
|
|
2417
|
3953 problem with a debugger}.
|
|
428
|
3954
|
|
1183
|
3955 If you're under Microsoft Windows, you're out of luck unless you happen
|
|
|
3956 to have a debugging aid installed on your system, for example Visual
|
|
|
3957 C++. In this case, the crash will result in a message giving you the
|
|
|
3958 option to enter a debugger (for example, by pressing @samp{Cancel}). Do
|
|
|
3959 this and locate the stack-trace window. (If your XEmacs was built
|
|
|
3960 without debugging information, the stack trace may not be very useful.)
|
|
|
3961
|
|
428
|
3962 When making a problem report make sure that:
|
|
|
3963
|
|
|
3964 @enumerate
|
|
|
3965 @item
|
|
|
3966 Report @strong{all} of the information output by XEmacs during the
|
|
|
3967 crash.
|
|
|
3968
|
|
|
3969 @item
|
|
2417
|
3970 You mention what O/S and Hardware you are running XEmacs on.
|
|
428
|
3971
|
|
|
3972 @item
|
|
|
3973 What version of XEmacs you are running.
|
|
|
3974
|
|
|
3975 @item
|
|
|
3976 What build options you are using.
|
|
|
3977
|
|
|
3978 @item
|
|
2417
|
3979 If the problem is related to graphics and you are running Unix or Mac
|
|
|
3980 OS X, we will also need to know what version of the X Window System
|
|
|
3981 you are running, and what window manager you are using.
|
|
1183
|
3982
|
|
|
3983 @item
|
|
|
3984 If the problem happened on a TTY, please include the terminal type.
|
|
2417
|
3985
|
|
|
3986 @item
|
|
|
3987 Try very hard to get both C and Lisp backtraces, as described above.
|
|
428
|
3988 @end enumerate
|
|
|
3989
|
|
1135
|
3990 Much of the information above is automatically generated by @kbd{M-x
|
|
|
3991 report-emacs-bug}. Even more, and often useful, information can be
|
|
|
3992 generated by redirecting the output of @code{make} and @code{make check}
|
|
|
3993 to a file (@file{beta.err} is the default used by @code{build-report}),
|
|
|
3994 and executing @kbd{M-x build-report}.
|
|
|
3995
|
|
2417
|
3996
|
|
2559
|
3997 @node Q2.4.3, Q2.4.4, Q2.4.2, Installation
|
|
|
3998 @unnumberedsubsec Q2.4.3: XEmacs crashes and I compiled it myself.
|
|
2417
|
3999
|
|
|
4000 There have been a variety of reports of crashes due to compilers with
|
|
|
4001 buggy optimizers. If you are compiling with optimization, consider
|
|
2559
|
4002 turning it off (@pxref{Q2.4.4, How to debug an XEmacs problem with a
|
|
2417
|
4003 debugger}) and recompiling.
|
|
|
4004
|
|
|
4005 Please see the @file{PROBLEMS} file that comes with XEmacs (it's in
|
|
|
4006 the top-level source directory) to read what it says about your
|
|
|
4007 platform.
|
|
|
4008
|
|
3018
|
4009 If you compiled XEmacs 21.4 or ealier using @samp{--use-union-type}, or
|
|
|
4010 21.5 or later using @samp{--enable-union-type} (or in either case used
|
|
|
4011 the option @samp{USE_UNION_TYPE} in @file{config.inc} under Windows),
|
|
|
4012 try recompiling again without it. The union type has been known to
|
|
|
4013 trigger compiler errors in a number of cases.
|
|
2417
|
4014
|
|
2559
|
4015 @node Q2.4.4, Q2.4.5, Q2.4.3, Installation
|
|
|
4016 @unnumberedsubsec Q2.4.4: How to debug an XEmacs problem with a debugger
|
|
428
|
4017
|
|
|
4018 If XEmacs does crash on you, one of the most productive things you can
|
|
|
4019 do to help get the bug fixed is to poke around a bit with the debugger.
|
|
|
4020 Here are some hints:
|
|
|
4021
|
|
|
4022 @itemize @bullet
|
|
|
4023 @item
|
|
|
4024 First of all, if the crash is at all reproducible, consider very
|
|
563
|
4025 strongly recompiling your XEmacs with debugging symbols and with no
|
|
|
4026 optimization (e.g. with GCC use the compiler flags @samp{-g -O0} --
|
|
|
4027 that's an "oh" followed by a zero), and with the configure options
|
|
3018
|
4028 @samp{--debug=yes} and @samp{--error-checking=all}
|
|
|
4029 (@samp{--enable-debug=yes} and @samp{--enable-error-checking=all} on
|
|
|
4030 XEmacs 21.5 or later). This will make your XEmacs run somewhat slower,
|
|
|
4031 but you are a lot more likely to catch the problem earlier (closer to
|
|
|
4032 its source). It makes it a lot easier to determine what's going on with
|
|
|
4033 a debugger. The way to control the compiler flags is with the
|
|
|
4034 configuration option @samp{--cflags} (@samp{--with-cflags} in 21.5). If
|
|
|
4035 you have a recent version of 21.5, you should use
|
|
2417
|
4036 @samp{--without-optimization} in preference to directly setting
|
|
|
4037 @samp{--cflags}.
|
|
1258
|
4038
|
|
|
4039 @item
|
|
|
4040 If it's not a true crash (@emph{i.e.}, XEmacs is hung, or a zombie
|
|
|
4041 process), or it's inconvenient to run XEmacs again because XEmacs is
|
|
|
4042 already running or is running in batch mode as part of a bunch of
|
|
|
4043 scripts, you may be able to attach to the existing process with your
|
|
2417
|
4044 debugger. Under Unix and Mac OS X, the typical way to do this is to
|
|
|
4045 first use some variant of the @samp{ps} command to figure out the
|
|
|
4046 process ID of XEmacs, for example @samp{ps -auxww | grep xemacs} under
|
|
|
4047 a BSD variant, @samp{ps -elf | grep xemacs} under Linux or System V,
|
|
|
4048 or @samp{ps -aW | grep xemacs} under Cygwin. Then run
|
|
|
4049
|
|
|
4050 @example
|
|
|
4051 gdb /path/to/xemacs/xemacs ####
|
|
|
4052 @end example
|
|
|
4053
|
|
|
4054 Where @code{####} is the process id of your XEmacs. (If you're not
|
|
|
4055 sure, try using @samp{which xemacs}.) When gdb attaches, the xemacs
|
|
|
4056 will stop and you can type @samp{where} in gdb to get a stack trace as
|
|
|
4057 usual. To get things moving again, you can just type @samp{quit} in
|
|
|
4058 gdb. It'll tell you the program is running and ask if you want to
|
|
|
4059 quit anyways. Say @samp{y} and it'll quit and have your emacs
|
|
|
4060 continue from where it was at.
|
|
|
4061
|
|
|
4062 If you're running another debugger, a similar method may work, or you
|
|
|
4063 may have to run the debugger first and then use the @code{attach}
|
|
|
4064 command or something similar.
|
|
|
4065
|
|
|
4066 Under Microsoft Windows, use the menu item @samp{Build->Start
|
|
|
4067 Debug->Attach to Process...} and select the XEmacs process from the list
|
|
|
4068 given.
|
|
1258
|
4069
|
|
|
4070 @item
|
|
|
4071 If you're able to run XEmacs under a debugger and reproduce the crash,
|
|
|
4072 here are some things you can do:
|
|
428
|
4073
|
|
|
4074 @item
|
|
|
4075 If XEmacs is hitting an assertion failure, put a breakpoint on
|
|
|
4076 @code{assert_failed()}.
|
|
|
4077
|
|
|
4078 @item
|
|
|
4079 If XEmacs is hitting some weird Lisp error that's causing it to crash
|
|
|
4080 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is
|
|
2417
|
4081 declared static in @file{eval.c}.
|
|
428
|
4082
|
|
|
4083 @item
|
|
563
|
4084 If XEmacs is outputting lots of X errors, put a breakpoint on
|
|
2417
|
4085 @code{x_error_handler()}; that will tell you which call is causing
|
|
|
4086 them. Note that the result may not be very useful by default because
|
|
|
4087 X Windows normally operates asynchronously: A bunch of commands are
|
|
|
4088 buffered up and then sent to the server all at once. This greatly
|
|
|
4089 improves performance over a network but means that an error may not be
|
|
|
4090 reported until the server receives the commands, which can be long
|
|
|
4091 after XEmacs made the erroneous calls. For best results, you need to
|
|
|
4092 make the X server synchronous before getting the backtrace. This can
|
|
|
4093 be done by starting XEmacs with the @samp{-sync} option or executing
|
|
|
4094 the Lisp code @code{(x-debug-mode t)}.
|
|
563
|
4095
|
|
|
4096 @item
|
|
428
|
4097 Internally, you will probably see lots of variables that hold objects of
|
|
1258
|
4098 type @code{Lisp_Object}. These are references to Lisp objects.
|
|
|
4099 Printing them out with the debugger probably won't be too
|
|
|
4100 useful---you'll likely just see a number. To decode them, do this:
|
|
428
|
4101
|
|
|
4102 @example
|
|
2417
|
4103 call debug_print (OBJECT)
|
|
428
|
4104 @end example
|
|
|
4105
|
|
|
4106 where @var{OBJECT} is whatever you want to decode (it can be a variable,
|
|
1258
|
4107 a function call, etc.). This uses the Lisp printing routines to out a
|
|
|
4108 readable representation on the TTY from which the xemacs process was
|
|
|
4109 invoked.
|
|
428
|
4110
|
|
2417
|
4111 Under 21.5 and later, @code{dp} is defined as an easier-to-type equivalent
|
|
|
4112 of @code{debug_print}. You can also try @code{dpa} if you can't see
|
|
|
4113 the output from @code{debug_print} (this will return a string containing
|
|
|
4114 the output), or use @code{debug_p3} if @code{debug_print} itself triggers
|
|
|
4115 a crash (this is a less comprehensive but super-safe way to print out
|
|
|
4116 a Lisp object).
|
|
|
4117
|
|
428
|
4118 @item
|
|
|
4119 If you want to get a Lisp backtrace showing the Lisp call
|
|
|
4120 stack, do this:
|
|
|
4121
|
|
|
4122 @example
|
|
2417
|
4123 call debug_backtrace ()
|
|
428
|
4124 @end example
|
|
|
4125
|
|
2417
|
4126 Under 21.5 and later, @code{db} is defined as an easier-to-type equivalent
|
|
|
4127 of @code{debug_backtrace}.
|
|
|
4128
|
|
|
4129 @item
|
|
|
4130 Using @code{debug_print} and @code{debug_backtrace} has two
|
|
|
4131 disadvantages - they can only be used with a running (including hung
|
|
|
4132 or zombie) xemacs process, and they do not display the internal C
|
|
|
4133 structure of a Lisp Object. Even if all you've got is a core dump,
|
|
|
4134 all is not lost.
|
|
428
|
4135
|
|
|
4136 If you're using GDB, there are some macros in the file
|
|
438
|
4137 @file{src/.gdbinit} in the XEmacs source distribution that should make
|
|
|
4138 it easier for you to decode Lisp objects. This file is automatically
|
|
|
4139 read by gdb if gdb is run in the directory where xemacs was built, and
|
|
|
4140 contains these useful macros to inspect the state of xemacs:
|
|
|
4141
|
|
|
4142 @table @code
|
|
|
4143 @item pobj
|
|
|
4144 Usage: pobj lisp_object @*
|
|
|
4145 Print the internal C representation of a lisp object.
|
|
|
4146
|
|
|
4147 @item xtype
|
|
|
4148 Usage: xtype lisp_object @*
|
|
|
4149 Print the Lisp type of a lisp object.
|
|
|
4150
|
|
|
4151 @item lbt
|
|
|
4152 Usage: lbt @*
|
|
|
4153 Print the current Lisp stack trace.
|
|
1258
|
4154 Requires a running xemacs process. (It works by calling the db
|
|
|
4155 routine described above.)
|
|
438
|
4156
|
|
|
4157 @item ldp
|
|
|
4158 Usage: ldp lisp_object @*
|
|
|
4159 Print a Lisp Object value using the Lisp printer.
|
|
1258
|
4160 Requires a running xemacs process. (It works by calling the dp
|
|
|
4161 routine described above.)
|
|
438
|
4162
|
|
|
4163 @item run-temacs
|
|
|
4164 Usage: run-temacs @*
|
|
|
4165 Run temacs interactively, like xemacs.
|
|
|
4166 Use this with debugging tools (like purify) that cannot deal with dumping,
|
|
|
4167 or when temacs builds successfully, but xemacs does not.
|
|
|
4168
|
|
|
4169 @item dump-temacs
|
|
|
4170 Usage: dump-temacs @*
|
|
|
4171 Run the dumping part of the build procedure.
|
|
|
4172 Use when debugging temacs, not xemacs!
|
|
|
4173 Use this when temacs builds successfully, but xemacs does not.
|
|
|
4174
|
|
|
4175 @item check-xemacs
|
|
|
4176 Usage: check-xemacs @*
|
|
|
4177 Run the test suite. Equivalent to 'make check'.
|
|
|
4178
|
|
|
4179 @item check-temacs
|
|
|
4180 Usage: check-temacs @*
|
|
|
4181 Run the test suite on temacs. Equivalent to 'make check-temacs'.
|
|
|
4182 Use this with debugging tools (like purify) that cannot deal with dumping,
|
|
|
4183 or when temacs builds successfully, but xemacs does not.
|
|
|
4184 @end table
|
|
428
|
4185
|
|
|
4186 If you are using Sun's @file{dbx} debugger, there is an equivalent file
|
|
438
|
4187 @file{src/.dbxrc}, which defines the same commands for dbx.
|
|
428
|
4188
|
|
|
4189 @item
|
|
|
4190 If you're using a debugger to get a C stack backtrace and you're seeing
|
|
|
4191 stack traces with some of the innermost frames mangled, it may be due to
|
|
|
4192 dynamic linking. (This happens especially under Linux.) Consider
|
|
3018
|
4193 reconfiguring with @samp{--dynamic=no} (@samp{--with-dynamic=no} in 21.5
|
|
|
4194 or later). Also, sometimes (again under Linux), stack backtraces of
|
|
|
4195 core dumps will have the frame where the fatal signal occurred mangled;
|
|
|
4196 if you can obtain a stack trace while running the XEmacs process under a
|
|
|
4197 debugger, the stack trace should be clean.
|
|
428
|
4198
|
|
1183
|
4199 @email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so
|
|
|
4200 version 1.8 if dynamic linking and debugging is a problem on Linux.
|
|
428
|
4201
|
|
|
4202 @item
|
|
|
4203 If you're using a debugger to get a C stack backtrace and you're
|
|
|
4204 getting a completely mangled and bogus stack trace, it's probably due to
|
|
|
4205 one of the following:
|
|
|
4206
|
|
|
4207 @enumerate a
|
|
|
4208 @item
|
|
|
4209 Your executable has been stripped. Bad news. Tell your sysadmin not to
|
|
|
4210 do this---it doesn't accomplish anything except to save a bit of disk
|
|
|
4211 space, and makes debugging much much harder.
|
|
|
4212
|
|
|
4213 @item
|
|
|
4214 Your stack is getting trashed. Debugging this is hard; you have to do a
|
|
|
4215 binary-search type of narrowing down where the crash occurs, until you
|
|
|
4216 figure out exactly which line is causing the problem. Of course, this
|
|
1258
|
4217 only works if the bug is highly reproducible. Also, in many cases if
|
|
|
4218 you run XEmacs from the debugger, the debugger can protect the stack
|
|
|
4219 somewhat. However, if the stack is being smashed, it is typically the
|
|
|
4220 case that there is a wild pointer somewhere in the program, often quite
|
|
|
4221 far from where the crash occurs.
|
|
428
|
4222
|
|
|
4223 @item
|
|
|
4224 If your stack trace has exactly one frame in it, with address 0x0, this
|
|
|
4225 could simply mean that XEmacs attempted to execute code at that address,
|
|
|
4226 e.g. through jumping to a null function pointer. Unfortunately, under
|
|
|
4227 those circumstances, GDB under Linux doesn't know how to get a stack
|
|
1183
|
4228 trace. (Yes, this is the fourth Linux-related problem I've mentioned. I
|
|
428
|
4229 have no idea why GDB under Linux is so bogus. Complain to the GDB
|
|
1183
|
4230 authors, or to comp.os.linux.development.system.) Again, you'll have to
|
|
428
|
4231 use the narrowing-down process described above.
|
|
|
4232
|
|
|
4233 @item
|
|
462
|
4234 You will get a Lisp backtrace output when XEmacs crashes, so you'll have
|
|
|
4235 something useful.
|
|
428
|
4236
|
|
|
4237 @end enumerate
|
|
|
4238
|
|
|
4239 @item
|
|
|
4240 If you compile with the newer gcc variants gcc-2.8 or egcs, you will
|
|
438
|
4241 also need gdb 4.17 or above. Earlier releases of gdb can't handle the
|
|
|
4242 debug information generated by the newer compilers.
|
|
428
|
4243
|
|
|
4244 @item
|
|
438
|
4245 In versions of XEmacs before 21.2.27, @file{src/.gdbinit} was named
|
|
|
4246 @file{src/gdbinit}. This had the disadvantage of not being sourced
|
|
|
4247 automatically by gdb, so you had to set that up yourself.
|
|
428
|
4248
|
|
1183
|
4249 @item
|
|
|
4250 If you are running Microsoft Windows, the the file @file{nt/README} for
|
|
|
4251 further information about debugging XEmacs.
|
|
|
4252
|
|
428
|
4253 @end itemize
|
|
|
4254
|
|
2559
|
4255 @node Q2.4.5, Q2.4.6, Q2.4.4, Installation
|
|
|
4256 @unnumberedsubsec Q2.4.5: I get a cryptic error message when trying to do something.
|
|
2417
|
4257
|
|
|
4258 When I try to use some particular option of some particular package, I
|
|
|
4259 get a cryptic error message in the minibuffer.
|
|
|
4260
|
|
|
4261 If the message went by too quickly, use @samp{Help->Recent Messages}
|
|
|
4262 from the menubar (or type @kbd{C-h l}) to see recent messages.
|
|
|
4263
|
|
|
4264 If you can't figure out what's going on, select
|
|
|
4265 @samp{Options->Troubleshooting->Debug on Error} from the menubar (or
|
|
|
4266 type @kbd{M-:} then @kbd{(setq debug-on-error t)}) then try and make
|
|
|
4267 the error happen again. This will put in the debugger (you can get
|
|
|
4268 out of this and continue what you were doing before by typing @kbd{c})
|
|
|
4269 and give you a backtrace that may be enlightening. If not, try
|
|
|
4270 reading through this FAQ; if that fails, you could try posting to
|
|
|
4271 @samp{comp.emacs.xemacs} (making sure to include the backtrace) and
|
|
|
4272 someone may be able to help. If you can identify which XEmacs Lisp
|
|
|
4273 source file the error is coming from you can get a more detailed stack
|
|
|
4274 backtrace by doing the following:
|
|
428
|
4275
|
|
|
4276 @enumerate
|
|
|
4277 @item
|
|
2417
|
4278 Visit the .el file in an XEmacs buffer.
|
|
|
4279
|
|
|
4280 @item
|
|
|
4281 Issue the command @kbd{M-x eval-current-buffer}.
|
|
|
4282
|
|
|
4283 @item
|
|
|
4284 Reproduce the error.
|
|
428
|
4285 @end enumerate
|
|
|
4286
|
|
2417
|
4287 For more information on debugging Lisp code, @xref{Debugging,,,
|
|
|
4288 lispref, XEmacs Lisp Reference Manual}.
|
|
|
4289
|
|
2559
|
4290 @node Q2.4.6, Q2.4.7, Q2.4.5, Installation
|
|
|
4291 @unnumberedsubsec Q2.4.6: XEmacs hangs when I try to do something.
|
|
2417
|
4292
|
|
|
4293 XEmacs might just be slow; some operations take a long time. XEmacs
|
|
|
4294 may also be waiting on a response from the network, for example when
|
|
|
4295 you are trying to send mail.
|
|
|
4296
|
|
|
4297 You can usually interrupt XEmacs by typing @kbd{C-g}. If not (for
|
|
|
4298 example, Lisp code explicitly disabled this by setting
|
|
|
4299 @code{inhibit-quit}), you can use the "critical quit" mechanism by
|
|
|
4300 typing @kbd{Control-Shift-G}. This should also pop you into the
|
|
|
4301 debugger and give you a backtrace, which can tell you where the
|
|
2559
|
4302 problem is (@pxref{Q2.4.4, How to debug an XEmacs problem with a
|
|
2417
|
4303 debugger}). (Note that setting @code{debug-on-quit} or selecting
|
|
|
4304 @samp{Options->Troubleshooting->Debug on Quit} will also cause regular
|
|
|
4305 @kbd{C-g} to enter the debugger and give you a backtrace.)
|
|
|
4306
|
|
|
4307 If you can't interrupt XEmacs this way, or for some reason XEmacs is
|
|
|
4308 not talking to the keyboard, you can try sending the @samp{SIGINT}
|
|
|
4309 signal using the @samp{kill} command.
|
|
|
4310
|
|
|
4311 If the Lisp backtrace isn't enlightening, or if XEmacs is so hung that
|
|
|
4312 you can't interrupt it at all, you could try attaching to the process
|
|
2559
|
4313 and getting a C stack backtrace. @xref{Q2.4.4, How to debug an XEmacs
|
|
2417
|
4314 problem with a debugger}.
|
|
|
4315
|
|
2559
|
4316 @node Q2.4.7, Q2.4.8, Q2.4.6, Installation
|
|
|
4317 @unnumberedsubsec Q2.4.7: I get an error message when XEmacs is running in batch mode.
|
|
2417
|
4318
|
|
|
4319 Typically this happens when you are trying to compile some Elisp code.
|
|
|
4320 If you are doing this as part of XEmacs or the XEmacs packages, you
|
|
|
4321 should automatically get a backtrace, which can help you determine the
|
|
|
4322 source of the problem. In other cases, you can get equivalent results
|
|
|
4323 by setting the environment variable @samp{XEMACSDEBUG} to @samp{(setq
|
|
|
4324 stack-trace-on-error t load-always-display-messages t
|
|
|
4325 load-ignore-out-of-date-elc-files t load-show-full-path-in-messages
|
|
|
4326 t)} (this needs to be all on one line; to set an environment variable,
|
|
|
4327 use @samp{export XEMACSDEBUG='FOO'} under @samp{bash}, @samp{zsh},
|
|
|
4328 etc. or @samp{setenv XEMACSDEBUG 'FOO'} under @samp{csh} and
|
|
|
4329 @samp{tcsh}). @samp{XEMACSDEBUG} specifies Lisp code that will be
|
|
|
4330 executed at startup time.
|
|
|
4331
|
|
|
4332 If the backtrace is not sufficiently useful in helping you diagnose
|
|
|
4333 the problem, you should consider using a debugger such as GDB.
|
|
2559
|
4334 @xref{Q2.4.4, How to debug an XEmacs problem with a debugger}. You
|
|
2417
|
4335 probably want to set a breakpoint on @code{signal_1}. Since such
|
|
|
4336 errors often occur during compiling, which is often triggered by a
|
|
|
4337 complex command run from a make suite, it may be easier to attach to
|
|
|
4338 the process once it's running.
|
|
|
4339
|
|
3018
|
4340 Under Microsoft Windows (and perhaps other operating systems), there is
|
|
|
4341 another useful trick you can do if you have configured with debugging
|
|
|
4342 support (configure option @samp{--debug} (@samp{--with-debug} in 21.5)
|
|
|
4343 or setting @samp{DEBUG_XEMACS} in @file{nt/config.inc}). Set the
|
|
|
4344 environment variable @samp{XEMACSDEBUG} (as described above) to
|
|
|
4345 @samp{(setq debug-on-error t)}. Then, when an error occurs
|
|
|
4346 noninteractively, instead of trying to invoke the Lisp debugger (which
|
|
|
4347 obviously won't work), XEmacs will break out to a C debugger using
|
|
2417
|
4348 @code{(force-debugging-signal t)}. @emph{NOTE}: This runs
|
|
|
4349 @code{abort()}!!! (As well as and after executing INT 3 under MS
|
|
|
4350 Windows, which should invoke a debugger if it's active.) This is
|
|
|
4351 guaranteed to kill XEmacs! (But in this situation, XEmacs is about to
|
|
|
4352 die anyway, and if no debugger is present, this will usefully dump
|
|
|
4353 core.)
|
|
|
4354
|
|
2559
|
4355 @node Q2.4.8, Q2.4.9, Q2.4.7, Installation
|
|
|
4356 @unnumberedsubsec Q2.4.8: The keyboard or mouse is not working properly, or I have some other event-related problem.
|
|
2417
|
4357
|
|
|
4358 XEmacs has various facilities for debugging event handling.
|
|
|
4359
|
|
|
4360 First, try setting the variable @code{debug-emacs-events} to non-zero.
|
|
|
4361 This will output various information showing which events are being
|
|
|
4362 received and how they are being translated. This may show you, for
|
|
|
4363 example, that a key command is getting intercepted using
|
|
|
4364 @code{key-translation-map}; this problem can otherwise be very tricky
|
|
|
4365 to debug.
|
|
|
4366
|
|
|
4367 Under X, you can see exactly which events are being received from the
|
|
|
4368 window system by setting @code{x-debug-events} to non-zero. (The value
|
|
|
4369 @samp{1} gives you regular output, and @samp{2} gives you verbose
|
|
|
4370 output, including all parameters.)
|
|
|
4371
|
|
|
4372 A similar facility exists under MS Windows: Set
|
|
|
4373 @code{debug-mswindows-events} to non-zero. (The value @samp{1} gives
|
|
|
4374 you regular output. The value @samp{2} gives you verbose output,
|
|
|
4375 including all parameters. The value @samp{3} gives you
|
|
|
4376 super-gorily-detailed output.)
|
|
|
4377
|
|
2559
|
4378 @node Q2.4.9, Q2.4.10, Q2.4.8, Installation
|
|
|
4379 @unnumberedsubsec Q2.4.9: @kbd{C-g} doesn't work for me. Is it broken?
|
|
2417
|
4380
|
|
|
4381 @kbd{C-g} does work for most people in most circumstances. If it
|
|
|
4382 doesn't, there are two possible explanations:
|
|
|
4383
|
|
|
4384 @enumerate
|
|
|
4385 @item
|
|
|
4386 XEmacs is hung in a way that prevents @kbd{C-g} from working. This
|
|
|
4387 can happen when code is wrapped with a binding of @code{inhibit-quit}
|
|
|
4388 to @code{t}; you should still be able interrupt XEmacs using "critical
|
|
|
4389 quit". On the other hand, XEmacs may be seriously wedged. (If you're
|
|
|
4390 lucky, sending @samp{SIGINT} to the XEmacs process will interrupt it.)
|
|
2559
|
4391 @xref{Q2.4.6, XEmacs hangs when I try to do something.}.
|
|
2417
|
4392
|
|
|
4393 @item
|
|
|
4394 @kbd{C-g} is indeed broken on your system. To test, try executing
|
|
|
4395 @code{(while t)} from the @samp{*scratch*} buffer. If @kbd{C-g}
|
|
|
4396 doesn't interrupt, then it's broken. This used to happen with systems
|
|
|
4397 where @samp{SIGIO} was broken, but @samp{BROKEN_SIGIO} wasn't defined.
|
|
|
4398 However, there may not be very many such systems nowadays.
|
|
|
4399 @end enumerate
|
|
|
4400
|
|
2559
|
4401 @node Q2.4.10, Q2.4.11, Q2.4.9, Installation
|
|
|
4402 @unnumberedsubsec Q2.4.10: How do I debug process-related problems?
|
|
2417
|
4403
|
|
|
4404 Under MS Windows, you can set the variable
|
|
|
4405 @code{debug-mswindows-process-command-lines} to non-@samp{nil} to get
|
|
|
4406 information on exactly what is getting passed to a process. This can
|
|
|
4407 be useful in determining problems with quoting. (Under Unix, a process
|
|
|
4408 receives each argument separately, but under MS Windows a single
|
|
|
4409 command line is received, and arguments with spaces or other special
|
|
|
4410 characters in them must be quoted. Unfortunately this means that each
|
|
|
4411 process, potentially at least, has its own quoting conventions, and
|
|
|
4412 the code to process quoting conventions in @file{cmd.exe}, the Visual
|
|
|
4413 C++ startup code and the like is baroque and poorly documented.
|
|
|
4414 XEmacs uses the variable
|
|
|
4415 @code{mswindows-construct-process-command-line-alist} to construct a
|
|
|
4416 command line from a list of arguments based on the command to be run,
|
|
|
4417 but it is (and cannot be) a perfect solution.)
|
|
|
4418
|
|
2559
|
4419 @node Q2.4.11, Q2.4.12, Q2.4.10, Installation
|
|
|
4420 @unnumberedsubsec Q2.4.11: XEmacs is outputting lots of X errors.
|
|
563
|
4421
|
|
|
4422 If this is happening, we would very much like to know what's causing
|
|
2559
|
4423 them. To find this out, see @ref{Q2.4.4, How to debug an XEmacs
|
|
2417
|
4424 problem with a debugger}. Try to get both a C and Lisp backtrace, and
|
|
|
4425 send them along with the full error output to
|
|
|
4426 @email{xemacs-beta@@xemacs.org}.
|
|
|
4427
|
|
2559
|
4428 @node Q2.4.12, Q2.5.1, Q2.4.11, Installation
|
|
|
4429 @unnumberedsubsec Q2.4.12: After upgrading, XEmacs won't do `foo' any more!
|
|
2417
|
4430
|
|
|
4431 You have been used to doing `foo', but now when you invoke it (or
|
|
|
4432 click the toolbar button or select the menu item), nothing (or an
|
|
|
4433 error) happens. The simplest explanation is that you are missing a
|
|
|
4434 package that is essential to you. You can either track it down and
|
|
|
4435 install it (there is a list of packages and brief descriptions of
|
|
|
4436 their contents in @file{etc/PACKAGES}), or install the `Sumo Tarball'
|
|
2559
|
4437 (@pxref{Q2.1.2, How do I figure out which packages to install?}).
|
|
2417
|
4438
|
|
|
4439 @c #### should xref to XEmacs manual here
|
|
|
4440
|
|
2559
|
4441 @unnumberedsec 2.5: Startup-Related Problems
|
|
|
4442
|
|
|
4443 @node Q2.5.1, Q2.5.2, Q2.4.12, Installation
|
|
|
4444 @unnumberedsubsec Q2.5.1: XEmacs cannot connect to my X Terminal!
|
|
2417
|
4445
|
|
|
4446 Help! I can not get XEmacs to display on my Envizex X-terminal!
|
|
|
4447
|
|
|
4448 Try setting the @code{DISPLAY} variable using the numeric IP address of
|
|
|
4449 the host you are running XEmacs from.
|
|
|
4450
|
|
2559
|
4451 @node Q2.5.2, Q2.5.3, Q2.5.1, Installation
|
|
|
4452 @unnumberedsubsec Q2.5.2 Startup problems related to paths or package locations.
|
|
|
4453
|
|
|
4454 First of all, if XEmacs can't find the packages, check to make sure
|
|
|
4455 that you put the packages in the right place, or that you told XEmacs
|
|
|
4456 where to look for the packages when you compiled it. @xref{Q2.1.1}.
|
|
|
4457
|
|
|
4458 If something is still going wrong, or you get a startup warning about
|
|
|
4459 not being able to deduce some paths, you can get detailed information
|
|
|
4460 on the path-searching process at startup by setting the environment
|
|
|
4461 variable @samp{EMACSDEBUGPATHS} to a non-null value. One thing to
|
|
|
4462 look for if you're having package problems is the value of
|
|
|
4463 @samp{configure-package-path}. This corresponds to what was compiled
|
|
|
4464 into XEmacs using the @samp{--package-prefix} or @samp{--package-path}
|
|
|
4465 parameter (@pxref{Q2.1.1}). If this has the value of @samp{nil},
|
|
|
4466 this means that no value was compiled into XEmacs using these parameters.
|
|
|
4467
|
|
|
4468 @node Q2.5.3, Q2.5.4, Q2.5.2, Installation
|
|
|
4469 @unnumberedsubsec Q2.5.3: XEmacs won't start without network.
|
|
434
|
4470
|
|
|
4471 If XEmacs starts when you're on the network, but fails when you're not
|
|
|
4472 on the network, you may be missing a "localhost" entry in your
|
|
|
4473 @file{/etc/hosts} file. The file should contain an entry like:
|
|
|
4474
|
|
|
4475 @example
|
|
|
4476 127.0.0.1 localhost
|
|
|
4477 @end example
|
|
|
4478
|
|
|
4479 Add that line, and XEmacs will be happy.
|
|
|
4480
|
|
2559
|
4481 @node Q2.5.4, Q2.5.5, Q2.5.3, Installation
|
|
|
4482 @unnumberedsubsec Q2.5.4: Startup warnings about deducing proper fonts?
|
|
2417
|
4483
|
|
|
4484 How can I avoid the startup warnings about deducing proper fonts?
|
|
|
4485
|
|
|
4486 This is highly dependent on your installation, but try with the
|
|
|
4487 following font as your base font for XEmacs and see what it does:
|
|
|
4488
|
|
|
4489 @format
|
|
|
4490 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
|
|
|
4491 @end format
|
|
|
4492
|
|
|
4493 More precisely, do the following in your resource file:
|
|
|
4494
|
|
|
4495 @format
|
|
|
4496 Emacs.default.attributeFont: \
|
|
|
4497 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
|
|
|
4498 @end format
|
|
|
4499
|
|
|
4500 If you just don't want to see the @samp{*Warnings*} buffer at startup
|
|
|
4501 time, you can set this:
|
|
428
|
4502
|
|
|
4503 @lisp
|
|
2417
|
4504 (setq display-warning-minimum-level 'error)
|
|
428
|
4505 @end lisp
|
|
|
4506
|
|
2417
|
4507 The buffer still exists; it just isn't in your face.
|
|
|
4508
|
|
2559
|
4509 @node Q2.5.5, Q2.5.6, Q2.5.4, Installation
|
|
|
4510 @unnumberedsubsec Q2.5.5: Warnings from incorrect key modifiers.
|
|
2417
|
4511
|
|
|
4512 The following information comes from the @file{PROBLEMS} file that comes
|
|
|
4513 with XEmacs.
|
|
|
4514
|
|
|
4515 If you're having troubles with HP/UX it is because HP/UX defines the
|
|
|
4516 modifiers wrong in X. Here is a shell script to fix the problem; be
|
|
|
4517 sure that it is run after VUE configures the X server.
|
|
428
|
4518
|
|
|
4519 @example
|
|
2417
|
4520 #! /bin/sh
|
|
|
4521 xmodmap 2> /dev/null - << EOF
|
|
|
4522 keysym Alt_L = Meta_L
|
|
|
4523 keysym Alt_R = Meta_R
|
|
|
4524 EOF
|
|
|
4525
|
|
|
4526 xmodmap - << EOF
|
|
|
4527 clear mod1
|
|
|
4528 keysym Mode_switch = NoSymbol
|
|
|
4529 add mod1 = Meta_L
|
|
|
4530 keysym Meta_R = Mode_switch
|
|
|
4531 add mod2 = Mode_switch
|
|
|
4532 EOF
|
|
428
|
4533 @end example
|
|
|
4534
|
|
2559
|
4535 @node Q2.5.6, , Q2.5.5, Installation
|
|
|
4536 @unnumberedsubsec Q2.5.6: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
|
|
2417
|
4537
|
|
|
4538 Yes.
|
|
|
4539
|
|
|
4540 The console was there because @file{temacs} (and in turn, @file{xemacs})
|
|
|
4541 was a console application, and Windows typically creates a new
|
|
|
4542 console for a console process unless the creating process requests that
|
|
|
4543 one isn't created. This used to be fixed with @file{runemacs}, a small
|
|
|
4544 Windows application that existed merely to start @file{xemacs}, stating
|
|
|
4545 that it didn't want a console.
|
|
|
4546
|
|
|
4547 XEmacs 21.4 fixes this cleanly by the virtue of being a true "GUI"
|
|
|
4548 application. The explanation of what that means is included for
|
|
|
4549 educational value.
|
|
|
4550
|
|
|
4551 When building an application to be run in a Win32 environment, you must
|
|
|
4552 state which sub-system it is to run in. Valid subsystems include
|
|
|
4553 "console" and "gui". The subsystem you use affects the run time
|
|
|
4554 libraries linked into your application, the start up function that is
|
|
|
4555 run before control is handed over to your application, the entry point
|
|
|
4556 to your program, and how Windows normally invokes your program. (Console
|
|
|
4557 programs automatically get a console created for them at startup if
|
|
|
4558 their stdin/stdout don't point anywhere useful, which is the case when
|
|
|
4559 run from the GUI. This is a stupid design, of course -- instead, the
|
|
|
4560 console should get created only when the first I/O actually occurs!
|
|
|
4561 GUI programs have an equally stupid design: When called from
|
|
|
4562 @file{CMD.EXE}/@file{COMMAND.COM}, their stdin/stdout will be set to
|
|
|
4563 point nowhere useful, even though the command shell has its own
|
|
|
4564 stdin/stdout. It's as if someone who had learned a bit about stdio but
|
|
|
4565 had no actual knowledge of interprocess communication designed the
|
|
|
4566 scheme; unfortunately, the whole process-communication aspect of the
|
|
|
4567 Win32 API is equally badly designed.) For example, the entry point for a
|
|
|
4568 console app is "main" (which is what you'd expect for a C/C++ program),
|
|
|
4569 but the entry point for a "gui" app is "WinMain". This confuses and
|
|
|
4570 annoys a lot of programmers who've grown up on Unix systems, where the
|
|
|
4571 kernel doesn't really care whether your application is a gui program or
|
|
|
4572 not.
|
|
|
4573
|
|
|
4574 For reasons not altogether clear, and are lost in the mists of time and
|
|
|
4575 tradition, XEmacs on Win32 started out as a console application, and
|
|
|
4576 therefore a console was automatically created for it. (It may have been
|
|
|
4577 made a console application partly because a console is needed in some
|
|
|
4578 circumstances, especially under Win95, to interrupt, terminate, or send
|
|
|
4579 signals to a child process, and because of the bogosity mentioned above
|
|
|
4580 with GUI programs and the standard command shell. Currently, XEmacs
|
|
|
4581 just creates and immediately hides a console when necessary, and
|
|
|
4582 works around the "no useful stdio" problem by creating its own console
|
|
|
4583 window as necessary to display messages in.)
|
|
|
4584
|
|
2459
|
4585 @node Editing, Display, Installation, Top
|
|
|
4586 @unnumbered 3 Editing Functions
|
|
2417
|
4587
|
|
|
4588 This is part 3 of the XEmacs Frequently Asked Questions list. This
|
|
2459
|
4589 section is devoted to the editing-related capabilities of XEmacs (the
|
|
|
4590 keyboard, mouse, buffers, text selections, etc.) and how to customize
|
|
|
4591 them.
|
|
2417
|
4592
|
|
|
4593 @menu
|
|
|
4594 3.0: The Keyboard
|
|
2459
|
4595 * Q3.0.1:: How can I customize the keyboard?
|
|
|
4596 * Q3.0.2:: How can I bind complex functions (or macros) to keys?
|
|
|
4597 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down?
|
|
|
4598 * Q3.0.4:: Globally binding @kbd{Delete}?
|
|
|
4599 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
|
4600 * Q3.0.6:: How can you type in special characters in XEmacs?
|
|
|
4601 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys?
|
|
|
4602 * Q3.0.8:: How do I map the arrow keys?
|
|
|
4603 * Q3.0.9:: HP Alt key as Meta.
|
|
|
4604 * Q3.0.10:: Why does edt emulation not work?
|
|
|
4605 * Q3.0.11:: How can I emulate VI and use it as my default mode?
|
|
2417
|
4606
|
|
|
4607 3.1: The Mouse
|
|
|
4608 * Q3.1.1:: How can I turn off Mouse pasting?
|
|
|
4609 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons?
|
|
|
4610 * Q3.1.3:: Clicking the left button does not do anything in buffer list.
|
|
|
4611 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3?
|
|
2459
|
4612 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
|
4613
|
|
|
4614 3.2: Buffers, Text Editing
|
|
|
4615 * Q3.2.1:: Can I have the end of the buffer delimited in some way?
|
|
|
4616 * Q3.2.2:: How do I insert today's date into a buffer?
|
|
|
4617 * Q3.2.3:: How do I get a single minibuffer frame?
|
|
|
4618 * Q3.2.4:: How can I enable auto-indent and/or Filladapt?
|
|
|
4619 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
4620
|
|
|
4621 3.3: Text Selections
|
|
|
4622 * Q3.3.1:: How do I select a rectangular region?
|
|
|
4623 * Q3.3.2:: How can I turn off or change highlighted selections?
|
|
|
4624 * Q3.3.3:: How do I cause typing on an active region to remove it?
|
|
|
4625 * Q3.3.4:: Can I turn off the highlight during isearch?
|
|
|
4626 * Q3.3.5:: Why is killing so slow?
|
|
|
4627 * Q3.3.6:: Why does @kbd{M-w} take so long?
|
|
|
4628
|
|
|
4629 3.4: Editing Source Code
|
|
|
4630 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode?
|
|
|
4631 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly?
|
|
2417
|
4632 @end menu
|
|
|
4633
|
|
|
4634 @unnumberedsec 3.0: The Keyboard
|
|
|
4635
|
|
2459
|
4636 @node Q3.0.1, Q3.0.2, Editing, Editing
|
|
|
4637 @unnumberedsubsec Q3.0.1: How can I customize the keyboard?
|
|
|
4638
|
|
|
4639 #### Write me.
|
|
|
4640
|
|
|
4641 @node Q3.0.2, Q3.0.3, Q3.0.1, Editing
|
|
|
4642 @unnumberedsubsec Q3.0.2: How can I bind complex functions (or macros) to keys?
|
|
428
|
4643
|
|
|
4644 As an example, say you want the @kbd{paste} key on a Sun keyboard to
|
|
|
4645 insert the current Primary X selection at point. You can accomplish this
|
|
|
4646 with:
|
|
|
4647
|
|
|
4648 @lisp
|
|
|
4649 (define-key global-map [f18] 'x-insert-selection)
|
|
|
4650 @end lisp
|
|
|
4651
|
|
|
4652 However, this only works if there is a current X selection (the
|
|
|
4653 selection will be highlighted). The functionality I like is for the
|
|
|
4654 @kbd{paste} key to insert the current X selection if there is one,
|
|
|
4655 otherwise insert the contents of the clipboard. To do this you need to
|
|
|
4656 pass arguments to @code{x-insert-selection}. This is done by wrapping
|
|
|
4657 the call in a 'lambda form:
|
|
|
4658
|
|
|
4659 @lisp
|
|
|
4660 (global-set-key [f18]
|
|
|
4661 (lambda () (interactive) (x-insert-selection t nil)))
|
|
|
4662 @end lisp
|
|
|
4663
|
|
|
4664 This binds the f18 key to a @dfn{generic} functional object. The
|
|
|
4665 interactive spec is required because only interactive functions can be
|
|
|
4666 bound to keys.
|
|
|
4667
|
|
|
4668 For the FAQ example you could use:
|
|
|
4669
|
|
|
4670 @lisp
|
|
|
4671 (global-set-key [(control ?.)]
|
|
|
4672 (lambda () (interactive) (scroll-up 1)))
|
|
440
|
4673 (global-set-key [(control ?;)]
|
|
|
4674 (lambda () (interactive) (scroll-up -1)))
|
|
428
|
4675 @end lisp
|
|
|
4676
|
|
|
4677 This is fine if you only need a few functions within the lambda body.
|
|
2417
|
4678 If you're doing more it's cleaner to define a separate function.
|
|
2459
|
4679 @xref{Q3.0.3, How do I bind C-. and C-; to scroll one line up and
|
|
2417
|
4680 down?}.
|
|
|
4681
|
|
2459
|
4682 @node Q3.0.3, Q3.0.4, Q3.0.2, Editing
|
|
|
4683 @unnumberedsubsec Q3.0.3: How do I bind C-. and C-; to scroll one line up and down?
|
|
428
|
4684
|
|
|
4685 Add the following (Thanks to @email{mly@@adoc.xerox.com, Richard Mlynarik} and
|
|
|
4686 @email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}:
|
|
|
4687
|
|
|
4688 @lisp
|
|
|
4689 (defun scroll-up-one-line ()
|
|
|
4690 (interactive)
|
|
|
4691 (scroll-up 1))
|
|
|
4692
|
|
|
4693 (defun scroll-down-one-line ()
|
|
|
4694 (interactive)
|
|
|
4695 (scroll-down 1))
|
|
|
4696
|
|
|
4697 (global-set-key [(control ?.)] 'scroll-up-one-line) ; C-.
|
|
440
|
4698 (global-set-key [(control ?;)] 'scroll-down-one-line) ; C-;
|
|
428
|
4699 @end lisp
|
|
|
4700
|
|
|
4701 The key point is that you can only bind simple functions to keys; you
|
|
2417
|
4702 can not bind a key to a function that you're also passing arguments
|
|
2459
|
4703 to. (@pxref{Q3.0.2, How can I bind complex functions (or macros) to
|
|
2417
|
4704 keys?} for a better answer).
|
|
|
4705
|
|
2459
|
4706 @node Q3.0.4, Q3.0.5, Q3.0.3, Editing
|
|
|
4707 @unnumberedsubsec Q3.0.4: Globally binding @kbd{Delete}?
|
|
428
|
4708
|
|
|
4709 I cannot manage to globally bind my @kbd{Delete} key to something other
|
|
|
4710 than the default. How does one do this?
|
|
|
4711
|
|
462
|
4712 Answer: The problem is that many modes explicitly bind @kbd{Delete}. To
|
|
|
4713 get around this, try the following:
|
|
|
4714
|
|
428
|
4715 @lisp
|
|
|
4716 (defun foo ()
|
|
|
4717 (interactive)
|
|
|
4718 (message "You hit DELETE"))
|
|
|
4719
|
|
462
|
4720 (define-key key-translation-map 'delete 'redirected-delete)
|
|
|
4721 (global-set-key 'redirected-delete 'foo)
|
|
428
|
4722 @end lisp
|
|
|
4723
|
|
2459
|
4724 @node Q3.0.5, Q3.0.6, Q3.0.4, Editing
|
|
|
4725 @unnumberedsubsec Q3.0.5: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
428
|
4726
|
|
|
4727 The following works in GNU Emacs 19:
|
|
|
4728
|
|
|
4729 @lisp
|
|
|
4730 (global-set-key [help] 'help-command);; Help
|
|
|
4731 @end lisp
|
|
|
4732
|
|
462
|
4733 The following works in XEmacs with the addition of shift:
|
|
428
|
4734
|
|
|
4735 @lisp
|
|
|
4736 (global-set-key [(shift help)] 'help-command);; Help
|
|
|
4737 @end lisp
|
|
|
4738
|
|
|
4739 But it doesn't work alone. This is in the file @file{PROBLEMS} which
|
|
|
4740 should have come with your XEmacs installation: @emph{Emacs ignores the
|
|
|
4741 @kbd{help} key when running OLWM}.
|
|
|
4742
|
|
|
4743 OLWM grabs the @kbd{help} key, and retransmits it to the appropriate
|
|
|
4744 client using
|
|
|
4745 @iftex
|
|
|
4746 @*
|
|
|
4747 @end iftex
|
|
|
4748 @code{XSendEvent}. Allowing Emacs to react to synthetic
|
|
|
4749 events is a security hole, so this is turned off by default. You can
|
|
|
4750 enable it by setting the variable @code{x-allow-sendevents} to t. You
|
|
|
4751 can also cause fix this by telling OLWM to not grab the help key, with
|
|
|
4752 the null binding @code{OpenWindows.KeyboardCommand.Help:}.
|
|
|
4753
|
|
2459
|
4754 @node Q3.0.6, Q3.0.7, Q3.0.5, Editing
|
|
|
4755 @unnumberedsubsec Q3.0.6: How can you type in special characters in XEmacs?
|
|
428
|
4756 One way is to use the package @code{x-compose}. Then you can use
|
|
|
4757 sequences like @kbd{Compose " a} to get ä, etc.
|
|
|
4758
|
|
462
|
4759 Another way is to use the @code{iso-insert} package. Then you can use
|
|
|
4760 sequences like @kbd{C-x 8 " a} to get ä, etc.
|
|
428
|
4761
|
|
|
4762 @email{glynn@@sensei.co.uk, Glynn Clements} writes:
|
|
|
4763
|
|
|
4764 @quotation
|
|
|
4765 It depends upon your X server.
|
|
|
4766
|
|
|
4767 Generally, the simplest way is to define a key as Multi_key with
|
|
|
4768 xmodmap, e.g.
|
|
|
4769 @c hey, show some respect, willya -- there's xkeycaps, isn't there? --
|
|
|
4770 @c chr ;)
|
|
|
4771 @example
|
|
440
|
4772 xmodmap -e 'keycode 0xff20 = Multi_key'
|
|
428
|
4773 @end example
|
|
|
4774
|
|
|
4775 You will need to pick an appropriate keycode. Use xev to find out the
|
|
|
4776 keycodes for each key.
|
|
|
4777
|
|
|
4778 [NB: On a `Windows' keyboard, recent versions of XFree86 automatically
|
|
|
4779 define the right `Windows' key as Multi_key'.]
|
|
|
4780
|
|
|
4781 Once you have Multi_key defined, you can use e.g.
|
|
|
4782 @example
|
|
440
|
4783 Multi a ' => á
|
|
|
4784 Multi e " => ë
|
|
|
4785 Multi c , => ç
|
|
428
|
4786 @end example
|
|
|
4787
|
|
|
4788 etc.
|
|
|
4789
|
|
|
4790 Also, recent versions of XFree86 define various AltGr-<key>
|
|
|
4791 combinations as dead keys, i.e.
|
|
|
4792 @example
|
|
440
|
4793 AltGr [ => dead_diaeresis
|
|
|
4794 AltGr ] => dead_tilde
|
|
|
4795 AltGr ; => dead_acute
|
|
428
|
4796 @end example
|
|
|
4797 etc.
|
|
|
4798
|
|
|
4799 Running @samp{xmodmap -pk} will list all of the defined keysyms.
|
|
|
4800 @end quotation
|
|
|
4801
|
|
1135
|
4802 For the related problem of @emph{displaying} non-ASCII characters in a
|
|
2459
|
4803 non-Mule XEmacs, @xref{Q4.0.8, How do I display non-ASCII characters?}.
|
|
|
4804
|
|
|
4805 @node Q3.0.7, Q3.0.8, Q3.0.6, Editing
|
|
|
4806 @unnumberedsubsec Q3.0.7: Can I turn on @dfn{sticky} modifier keys?
|
|
428
|
4807
|
|
|
4808 Yes, with @code{(setq modifier-keys-are-sticky t)}. This will give the
|
|
|
4809 effect of being able to press and release Shift and have the next
|
|
|
4810 character typed come out in upper case. This will affect all the other
|
|
|
4811 modifier keys like Control and Meta as well.
|
|
|
4812
|
|
|
4813 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
|
4814
|
|
|
4815 @quotation
|
|
|
4816 One thing about the sticky modifiers is that if you move the mouse out
|
|
|
4817 of the frame and back in, it cancels all currently ``stuck'' modifiers.
|
|
|
4818 @end quotation
|
|
|
4819
|
|
2459
|
4820 @node Q3.0.8, Q3.0.9, Q3.0.7, Editing
|
|
|
4821 @unnumberedsubsec Q3.0.8: How do I map the arrow keys?
|
|
428
|
4822 @c New
|
|
|
4823 Say you want to map @kbd{C-@key{right}} to forward-word:
|
|
|
4824
|
|
|
4825 @email{sds@@usa.net, Sam Steingold} writes:
|
|
|
4826
|
|
|
4827 @quotation
|
|
|
4828 @lisp
|
|
|
4829 ; both XEmacs and Emacs
|
|
|
4830 (define-key global-map [(control right)] 'forward-word)
|
|
|
4831 @end lisp
|
|
|
4832 or
|
|
|
4833 @lisp
|
|
|
4834 ; Emacs only
|
|
|
4835 (define-key global-map [C-right] 'forward-word)
|
|
|
4836 @end lisp
|
|
|
4837 or
|
|
|
4838 @lisp
|
|
|
4839 ; ver > 20, both
|
|
|
4840 (define-key global-map (kbd "C-<right>") 'forward-word)
|
|
|
4841 @end lisp
|
|
|
4842 @end quotation
|
|
|
4843
|
|
2459
|
4844 @node Q3.0.9, Q3.0.10, Q3.0.8, Editing
|
|
|
4845 @unnumberedsubsec Q3.0.9: HP Alt key as Meta.
|
|
2417
|
4846
|
|
|
4847 How can I make XEmacs recognize the Alt key of my HP workstation as a
|
|
|
4848 Meta key?
|
|
|
4849
|
|
|
4850 Put the following line into a file and load it with xmodmap(1) before
|
|
|
4851 starting XEmacs:
|
|
428
|
4852
|
|
|
4853 @example
|
|
2417
|
4854 remove Mod1 = Mode_switch
|
|
428
|
4855 @end example
|
|
|
4856
|
|
2459
|
4857 @node Q3.0.10, Q3.0.11, Q3.0.9, Editing
|
|
|
4858 @unnumberedsubsec Q3.0.10: Why does edt emulation not work?
|
|
2417
|
4859
|
|
|
4860 We don't know, but you can use tpu-edt emulation instead, which works
|
|
|
4861 fine and is a little fancier than the standard edt emulation. To do
|
|
|
4862 this, add the following line to your @file{init.el}:
|
|
|
4863
|
|
|
4864 @lisp
|
|
|
4865 (tpu-edt)
|
|
|
4866 @end lisp
|
|
|
4867
|
|
|
4868 If you don't want it to replace @kbd{C-h} with an edt-style help menu
|
|
|
4869 add this as well:
|
|
428
|
4870
|
|
|
4871 @lisp
|
|
2417
|
4872 (global-set-key [(control h)] 'help-for-help)
|
|
428
|
4873 @end lisp
|
|
|
4874
|
|
2459
|
4875 @node Q3.0.11, Q3.1.1, Q3.0.10, Editing
|
|
|
4876 @unnumberedsubsec Q3.0.11: How can I emulate VI and use it as my default mode?
|
|
2417
|
4877
|
|
|
4878 Our recommended VI emulator is viper. To make viper-mode the default,
|
|
|
4879 add this to your @file{init.el}:
|
|
428
|
4880
|
|
|
4881 @lisp
|
|
2417
|
4882 (viper-mode)
|
|
428
|
4883 @end lisp
|
|
|
4884
|
|
2417
|
4885 @email{kifer@@CS.SunySB.EDU, Michael Kifer} writes:
|
|
|
4886
|
|
|
4887 @quotation
|
|
|
4888 This should be added as close to the top of @file{init.el} as you can get
|
|
|
4889 it, otherwise some minor modes may not get viper-ized.
|
|
|
4890 @end quotation
|
|
|
4891
|
|
|
4892 @unnumberedsec 3.1: The Mouse
|
|
|
4893
|
|
2459
|
4894 @node Q3.1.1, Q3.1.2, Q3.0.11, Editing
|
|
2417
|
4895 @unnumberedsubsec Q3.1.1: How can I turn off Mouse pasting?
|
|
428
|
4896
|
|
|
4897 I keep hitting the middle mouse button by accident and getting stuff
|
|
|
4898 pasted into my buffer so how can I turn this off?
|
|
|
4899
|
|
|
4900 Here is an alternative binding, whereby the middle mouse button selects
|
|
|
4901 (but does not cut) the expression under the mouse. Clicking middle on a
|
|
|
4902 left or right paren will select to the matching one. Note that you can
|
|
|
4903 use @code{define-key} or @code{global-set-key}.
|
|
|
4904
|
|
|
4905 @lisp
|
|
|
4906 (defun mouse-set-point-and-select (event)
|
|
|
4907 "Sets the point at the mouse location, then marks following form"
|
|
|
4908 (interactive "@@e")
|
|
|
4909 (mouse-set-point event)
|
|
|
4910 (mark-sexp 1))
|
|
|
4911 (define-key global-map [button2] 'mouse-set-point-and-select)
|
|
|
4912 @end lisp
|
|
|
4913
|
|
2459
|
4914 @node Q3.1.2, Q3.1.3, Q3.1.1, Editing
|
|
2417
|
4915 @unnumberedsubsec Q3.1.2: How do I set control/meta/etc modifiers on mouse buttons?
|
|
428
|
4916
|
|
|
4917 Use, for instance, @code{[(meta button1)]}. For example, here is a common
|
|
|
4918 setting for Common Lisp programmers who use the bundled @code{ilisp}
|
|
|
4919 package, whereby meta-button1 on a function name will find the file where
|
|
|
4920 the function name was defined, and put you at that location in the source
|
|
|
4921 file.
|
|
|
4922
|
|
|
4923 [Inside a function that gets called by the lisp-mode-hook and
|
|
|
4924 ilisp-mode-hook]
|
|
|
4925
|
|
|
4926 @lisp
|
|
|
4927 (local-set-key [(meta button1)] 'edit-definitions-lisp)
|
|
|
4928 @end lisp
|
|
|
4929
|
|
2459
|
4930 @node Q3.1.3, Q3.1.4, Q3.1.2, Editing
|
|
2417
|
4931 @unnumberedsubsec Q3.1.3: Clicking the left button does not do anything in buffer list.
|
|
428
|
4932
|
|
|
4933 I do @kbd{C-x C-b} to get a list of buffers and the entries get
|
|
|
4934 highlighted when I move the mouse over them but clicking the left mouse
|
|
|
4935 does not do anything.
|
|
|
4936
|
|
|
4937 Use the middle mouse button.
|
|
|
4938
|
|
2459
|
4939 @node Q3.1.4, Q3.1.5, Q3.1.3, Editing
|
|
2417
|
4940 @unnumberedsubsec Q3.1.4: How can I get a list of buffers when I hit mouse button 3?
|
|
428
|
4941
|
|
|
4942 The following code will replace the default popup on button3:
|
|
|
4943
|
|
|
4944 @lisp
|
|
|
4945 (global-set-key [button3] 'popup-buffer-menu)
|
|
|
4946 @end lisp
|
|
|
4947
|
|
2459
|
4948 @node Q3.1.5, Q3.2.1, Q3.1.4, Editing
|
|
|
4949 @unnumberedsubsec Q3.1.5: How can I set XEmacs up so that it pastes where the text cursor is?
|
|
428
|
4950
|
|
|
4951 By default XEmacs pastes X selections where the mouse pointer is. How
|
|
|
4952 do I disable this?
|
|
|
4953
|
|
|
4954 Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank
|
|
|
4955 @key{RET}}.
|
|
|
4956
|
|
2417
|
4957 To get XEmacs to paste at the text cursor, add this your @file{init.el}:
|
|
428
|
4958
|
|
|
4959 @lisp
|
|
|
4960 (setq mouse-yank-at-point t)
|
|
|
4961 @end lisp
|
|
|
4962
|
|
2459
|
4963 You can also change this with Customize. Select from the
|
|
|
4964 @code{Options} menu @code{Advanced
|
|
|
4965 (Customize)->Emacs->Editing->Mouse->Yank At Point...} or type @kbd{M-x
|
|
|
4966 customize @key{RET} mouse @key{RET}}.
|
|
|
4967
|
|
|
4968 @unnumberedsec 3.2: Buffers, Text Editing
|
|
|
4969
|
|
|
4970 @node Q3.2.1, Q3.2.2, Q3.1.5, Editing
|
|
|
4971 @unnumberedsubsec Q3.2.1: Can I have the end of the buffer delimited in some way?
|
|
|
4972
|
|
|
4973 Say, with: @samp{[END]}?
|
|
|
4974
|
|
|
4975 Try this:
|
|
|
4976
|
|
|
4977 @lisp
|
|
|
4978 (let ((ext (make-extent (point-min) (point-max))))
|
|
|
4979 (set-extent-property ext 'start-closed t)
|
|
|
4980 (set-extent-property ext 'end-closed t)
|
|
|
4981 (set-extent-property ext 'detachable nil)
|
|
|
4982 (set-extent-end-glyph ext (make-glyph [string :data "[END]"])))
|
|
|
4983 @end lisp
|
|
|
4984
|
|
|
4985 Since this is XEmacs, you can specify an icon to be shown on
|
|
|
4986 window-system devices. To do so, change the @code{make-glyph} call to
|
|
|
4987 something like this:
|
|
|
4988
|
|
|
4989 @lisp
|
|
|
4990 (make-glyph '([xpm :file "~/something.xpm"]
|
|
|
4991 [string :data "[END]"]))
|
|
|
4992 @end lisp
|
|
|
4993
|
|
|
4994 You can inline the @sc{xpm} definition yourself by specifying
|
|
|
4995 @code{:data} instead of @code{:file}. Here is such a full-featured
|
|
|
4996 version that works on both X and TTY devices:
|
|
|
4997
|
|
|
4998 @lisp
|
|
|
4999 (let ((ext (make-extent (point-min) (point-max))))
|
|
|
5000 (set-extent-property ext 'start-closed t)
|
|
|
5001 (set-extent-property ext 'end-closed t)
|
|
|
5002 (set-extent-property ext 'detachable nil)
|
|
|
5003 (set-extent-end-glyph ext (make-glyph '([xpm :data "\
|
|
|
5004 /* XPM */
|
|
|
5005 static char* eye = @{
|
|
|
5006 \"20 11 7 2\",
|
|
|
5007 \"__ c None\"
|
|
|
5008 \"_` c #7f7f7f\",
|
|
|
5009 \"_a c #fefefe\",
|
|
|
5010 \"_b c #7f0000\",
|
|
|
5011 \"_c c #fefe00\",
|
|
|
5012 \"_d c #fe0000\",
|
|
|
5013 \"_e c #bfbfbf\",
|
|
|
5014 \"___________`_`_`___b_b_b_b_________`____\",
|
|
|
5015 \"_________`_`_`___b_c_c_c_b_b____________\",
|
|
|
5016 \"_____`_`_`_e___b_b_c_c_c___b___b_______`\",
|
|
|
5017 \"___`_`_e_a___b_b_d___b___b___b___b______\",
|
|
|
5018 \"_`_`_e_a_e___b_b_d_b___b___b___b___b____\",
|
|
|
5019 \"_`_`_a_e_a___b_b_d___b___b___b___b___b__\",
|
|
|
5020 \"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\",
|
|
|
5021 \"___`_`_e_a___b_b_b_d_c___b___b___d_b____\",
|
|
|
5022 \"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\",
|
|
|
5023 \"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\",
|
|
|
5024 \"___`_____`_`_`_`___b_b_b_b_b_b__________\",
|
|
|
5025 @} ;"]
|
|
|
5026 [string :data "[END]"]))))
|
|
|
5027 @end lisp
|
|
|
5028
|
|
|
5029 Note that you might want to make this a function, and put it to a hook.
|
|
|
5030 We leave that as an exercise for the reader.
|
|
|
5031
|
|
|
5032 @node Q3.2.2, Q3.2.3, Q3.2.1, Editing
|
|
|
5033 @unnumberedsubsec Q3.2.2: How do I insert today's date into a buffer?
|
|
2417
|
5034
|
|
|
5035 Like this:
|
|
428
|
5036
|
|
|
5037 @lisp
|
|
2459
|
5038 (insert (current-time-string))
|
|
2417
|
5039 @end lisp
|
|
|
5040
|
|
2459
|
5041 @node Q3.2.3, Q3.2.4, Q3.2.2, Editing
|
|
|
5042 @unnumberedsubsec Q3.2.3: How do I get a single minibuffer frame?
|
|
|
5043
|
|
|
5044 @email{acs@@acm.org, Vin Shelton} writes:
|
|
2417
|
5045
|
|
|
5046 @lisp
|
|
2459
|
5047 (setq initial-frame-plist '(minibuffer nil))
|
|
|
5048 (setq default-frame-plist '(minibuffer nil))
|
|
|
5049 (setq default-minibuffer-frame
|
|
|
5050 (make-frame
|
|
|
5051 '(minibuffer only
|
|
|
5052 width 86
|
|
|
5053 height 1
|
|
|
5054 menubar-visible-p nil
|
|
|
5055 default-toolbar-visible-p nil
|
|
|
5056 name "minibuffer"
|
|
|
5057 top -2
|
|
|
5058 left -2
|
|
|
5059 has-modeline-p nil)))
|
|
|
5060 (frame-notice-user-settings)
|
|
2417
|
5061 @end lisp
|
|
|
5062
|
|
2459
|
5063 @strong{Please note:} The single minibuffer frame may not be to everyone's
|
|
|
5064 taste, and there any number of other XEmacs options settings that may
|
|
|
5065 make it difficult or inconvenient to use.
|
|
|
5066
|
|
|
5067 @node Q3.2.4, Q3.2.5, Q3.2.3, Editing
|
|
|
5068 @unnumberedsubsec Q3.2.4: How can I enable auto-indent and/or Filladapt?
|
|
|
5069
|
|
|
5070 Put the following line in your @file{init.el}:
|
|
428
|
5071
|
|
|
5072 @lisp
|
|
2459
|
5073 (setq indent-line-function 'indent-relative-maybe)
|
|
428
|
5074 @end lisp
|
|
|
5075
|
|
2459
|
5076 If you want to get fancy, try the @code{filladapt} package available
|
|
|
5077 standard with XEmacs. Put this into your @file{init.el}:
|
|
428
|
5078
|
|
|
5079 @lisp
|
|
2459
|
5080 (require 'filladapt)
|
|
|
5081 (setq-default filladapt-mode t)
|
|
|
5082 (add-hook 'c-mode-hook 'turn-off-filladapt-mode)
|
|
428
|
5083 @end lisp
|
|
|
5084
|
|
2459
|
5085 This will enable Filladapt for all modes except C mode, where it doesn't
|
|
|
5086 work well. To turn Filladapt on only in particular major modes, remove
|
|
|
5087 the @code{(setq-default ...)} line and use
|
|
|
5088 @code{turn-on-filladapt-mode}, like this:
|
|
428
|
5089
|
|
|
5090 @lisp
|
|
2459
|
5091 (add-hook 'text-mode-hook 'turn-on-filladapt-mode)
|
|
428
|
5092 @end lisp
|
|
2417
|
5093
|
|
2459
|
5094 You can customize filling and adaptive filling with Customize.
|
|
|
5095 Select from the @code{Options} menu
|
|
|
5096 @code{Advanced (Customize)->Emacs->Editing->Fill->Fill...}
|
|
|
5097 or type @kbd{M-x customize @key{RET} fill @key{RET}}.
|
|
|
5098
|
|
|
5099 Note that well-behaving text-lookalike modes will run
|
|
|
5100 @code{text-mode-hook} by default (e.g. that's what Message does). For
|
|
|
5101 the nasty ones, you'll have to provide the @code{add-hook}s yourself.
|
|
|
5102
|
|
|
5103 Please note that the @code{fa-extras} package is no longer useful.
|
|
|
5104
|
|
|
5105 @node Q3.2.5, Q3.3.1, Q3.2.4, Editing
|
|
|
5106 @unnumberedsubsec Q3.2.5: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
5107
|
|
|
5108 Try the following lisp in your @file{init.el}:
|
|
2417
|
5109
|
|
|
5110 @lisp
|
|
2459
|
5111 (setq default-major-mode 'text-mode)
|
|
2769
|
5112 (add-hook 'text-mode-hook 'turn-on-auto-fill)
|
|
2417
|
5113 @end lisp
|
|
|
5114
|
|
2459
|
5115 @strong{WARNING}: note that changing the value of
|
|
|
5116 @code{default-major-mode} from @code{fundamental-mode} can break a large
|
|
|
5117 amount of built-in code that expects newly created buffers to be in
|
|
|
5118 @code{fundamental-mode}. (Changing from @code{fundamental-mode} to
|
|
|
5119 @code{text-mode} might not wreak too much havoc, but changing to
|
|
|
5120 something more exotic like a lisp-mode would break many Emacs packages).
|
|
|
5121
|
|
|
5122 Note that Emacs by default starts up in buffer @code{*scratch*} in
|
|
|
5123 @code{initial-major-mode}, which defaults to
|
|
|
5124 @code{lisp-interaction-mode}. Thus adding the following form to your
|
|
|
5125 Emacs init file will cause the initial @code{*scratch*} buffer to be put
|
|
|
5126 into auto-fill'ed @code{text-mode}:
|
|
2417
|
5127
|
|
|
5128 @lisp
|
|
2459
|
5129 (setq initial-major-mode
|
|
|
5130 (lambda ()
|
|
|
5131 (text-mode)
|
|
|
5132 (turn-on-auto-fill)))
|
|
2417
|
5133 @end lisp
|
|
|
5134
|
|
2459
|
5135 Note that after your init file is loaded, if
|
|
|
5136 @code{inhibit-startup-message} is @code{nil} (the default) and the
|
|
|
5137 startup buffer is @code{*scratch*} then the startup message will be
|
|
|
5138 inserted into @code{*scratch*}; it will be removed after a timeout by
|
|
|
5139 erasing the entire @code{*scratch*} buffer. Keep in mind this default
|
|
|
5140 usage of @code{*scratch*} if you desire any prior manipulation of
|
|
|
5141 @code{*scratch*} from within your Emacs init file. In particular,
|
|
|
5142 anything you insert into @code{*scratch*} from your init file will be
|
|
|
5143 later erased. Also, if you change the mode of the @code{*scratch*}
|
|
|
5144 buffer, be sure that this will not interfere with possible later
|
|
|
5145 insertion of the startup message (e.g. if you put @code{*scratch*} into
|
|
|
5146 a nonstandard mode that has automatic font lock rules, then the startup
|
|
|
5147 message might get fontified in a strange foreign manner, e.g. as code in
|
|
|
5148 some programming language).
|
|
|
5149
|
|
|
5150 @unnumberedsec 3.3: Text Selections
|
|
|
5151
|
|
|
5152 @node Q3.3.1, Q3.3.2, Q3.2.5, Editing
|
|
|
5153 @unnumberedsubsec Q3.3.1: How do I select a rectangular region?
|
|
2417
|
5154
|
|
|
5155 Just select the region normally, then use the rectangle commands (e.g.
|
|
|
5156 @code{kill-rectangle} on it. The region does not highlight as a
|
|
|
5157 rectangle, but the commands work just fine.
|
|
|
5158
|
|
|
5159 To actually sweep out rectangular regions with the mouse you can use
|
|
|
5160 @code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}.
|
|
|
5161 Then use rectangle commands.
|
|
|
5162
|
|
|
5163 You can also do the following to change default behavior to sweep out
|
|
|
5164 rectangular regions:
|
|
|
5165
|
|
|
5166 @lisp
|
|
|
5167 (setq mouse-track-rectangle-p t)
|
|
|
5168 @end lisp
|
|
|
5169
|
|
2459
|
5170 You can also change this with Customize.
|
|
2417
|
5171 Select from the @code{Options} menu
|
|
|
5172 @code{Advanced (Customize)->Emacs->Editing->Mouse->Track Rectangle...} or type
|
|
|
5173 @kbd{M-x customize @key{RET} mouse @key{RET}}.
|
|
|
5174
|
|
|
5175
|
|
|
5176 @example
|
|
|
5177 mouse-track-do-rectangle: (event)
|
|
|
5178 -- an interactive compiled Lisp function.
|
|
|
5179 Like `mouse-track' but selects rectangles instead of regions.
|
|
|
5180 @end example
|
|
|
5181
|
|
2459
|
5182 @node Q3.3.2, Q3.3.3, Q3.3.1, Editing
|
|
|
5183 @unnumberedsubsec Q3.3.2: How can I turn off or change highlighted selections?
|
|
428
|
5184
|
|
|
5185 The @code{zmacs} mode allows for what some might call gratuitous
|
|
|
5186 highlighting for selected regions (either by setting mark or by using
|
|
|
5187 the mouse). This is the default behavior. To turn off, add the
|
|
2417
|
5188 following line to your @file{init.el} file:
|
|
428
|
5189
|
|
|
5190 @lisp
|
|
|
5191 (setq zmacs-regions nil)
|
|
|
5192 @end lisp
|
|
|
5193
|
|
2417
|
5194 You can also change this with Customize. Select from the
|
|
|
5195 @code{Options} menu
|
|
|
5196 @code{Advanced (Customize)->Emacs->Editing->Basics->Zmacs Regions}
|
|
|
5197 or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
|
|
|
5198
|
|
|
5199 To change the face for selection, look at @code{Options->Advanced (Customize)}
|
|
|
5200 on the menubar.
|
|
|
5201
|
|
2459
|
5202 @node Q3.3.3, Q3.3.4, Q3.3.2, Editing
|
|
|
5203 @unnumberedsubsec Q3.3.3: How do I cause typing on an active region to remove it?
|
|
428
|
5204
|
|
|
5205 I want to change things so that if I select some text and start typing,
|
|
|
5206 the typed text replaces the selected text, similar to Motif.
|
|
|
5207
|
|
|
5208 You want to use something called @dfn{pending delete}. Pending delete
|
|
|
5209 is what happens when you select a region (with the mouse or keyboard)
|
|
|
5210 and you press a key to replace the selected region by the key you typed.
|
|
|
5211 Usually backspace kills the selected region.
|
|
|
5212
|
|
2164
|
5213 To get this behavior, ensure that you have the @file{pc} package
|
|
|
5214 installed, and add the following lines to your
|
|
2417
|
5215 @file{init.el}:
|
|
428
|
5216
|
|
|
5217 @lisp
|
|
438
|
5218 (cond
|
|
|
5219 ((fboundp 'turn-on-pending-delete)
|
|
|
5220 (turn-on-pending-delete))
|
|
|
5221 ((fboundp 'pending-delete-on)
|
|
|
5222 (pending-delete-on t)))
|
|
428
|
5223 @end lisp
|
|
|
5224
|
|
1138
|
5225 Note that this will work with both Backspace and Delete. This code is a
|
|
438
|
5226 tad more complicated than it has to be for XEmacs in order to make it
|
|
|
5227 more portable.
|
|
428
|
5228
|
|
2459
|
5229 @node Q3.3.4, Q3.3.5, Q3.3.3, Editing
|
|
|
5230 @unnumberedsubsec Q3.3.4: Can I turn off the highlight during isearch?
|
|
428
|
5231
|
|
|
5232 I do not like my text highlighted while I am doing isearch as I am not
|
|
|
5233 able to see what's underneath. How do I turn it off?
|
|
|
5234
|
|
2417
|
5235 Put the following in your @file{init.el}:
|
|
428
|
5236
|
|
|
5237 @lisp
|
|
|
5238 (setq isearch-highlight nil)
|
|
|
5239 @end lisp
|
|
|
5240
|
|
2459
|
5241 You can also change this with Customize. Type
|
|
428
|
5242 @kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}.
|
|
|
5243
|
|
|
5244 Note also that isearch-highlight affects query-replace and ispell.
|
|
|
5245 Instead of disabling isearch-highlight you may find that a better
|
|
|
5246 solution consists of customizing the @code{isearch} face.
|
|
|
5247
|
|
2459
|
5248 @node Q3.3.5, Q3.3.6, Q3.3.4, Editing
|
|
|
5249 @unnumberedsubsec Q3.3.5: Why is killing so slow?
|
|
892
|
5250
|
|
|
5251 This actually is an X Windows question, although you'll notice it with
|
|
|
5252 keyboard operations as well as while using the GUI. Basically, there
|
|
|
5253 are four ways to communicate interprogram via the X server:
|
|
|
5254
|
|
|
5255 @table @strong
|
|
|
5256 @item Primary selection
|
|
|
5257 a transient selection that gets replaced every time a new selection is made
|
|
|
5258
|
|
|
5259 @item Secondary selection
|
|
|
5260 for "exchanging" with the primary selection
|
|
|
5261
|
|
|
5262 @item Cut buffers
|
|
|
5263 a clipboard internal to the X server (deprecated)
|
|
|
5264
|
|
|
5265 @item Clipboard selection
|
|
|
5266 a selection with a notification protocol that allows a separate app to
|
|
|
5267 manage the clipboard
|
|
|
5268 @end table
|
|
|
5269
|
|
|
5270 The cut buffers are deprecated because managing them is even more
|
|
|
5271 inefficient than the clipboard notification protocol. The primary
|
|
|
5272 selection works fine for many users and applications, but is not very
|
|
|
5273 robust under intensive or sophisticated use.
|
|
|
5274
|
|
|
5275 In Motif and MS Windows, a clipboard has become the primary means for
|
|
|
5276 managing cut and paste. These means that "modern" applications tend to
|
|
|
5277 be oriented toward a true clipboard, rather than the primary selection.
|
|
|
5278 (On Windows, there is nothing equivalent to the primary selection.)
|
|
|
5279 It's not that XEmacs doesn't support the simple primary selection
|
|
|
5280 method, it's that more and more other applications don't.
|
|
|
5281
|
|
|
5282 So the slowdown occurs because XEmacs now engages in the clipboard
|
|
|
5283 notification protocol on @emph{every} kill. This is especially slow on
|
|
|
5284 Motif.
|
|
|
5285
|
|
|
5286 With most people running most clients and server on the same host, and
|
|
|
5287 many of the rest working over very fast communication, you may expect
|
|
|
5288 that the situation is not going to improve.
|
|
|
5289
|
|
|
5290 There are a number of workarounds. The most effective is to use a
|
|
|
5291 special command to do selection ownership only when you intend to paste
|
|
|
5292 to another application. Useful commands are @code{kill-primary-selection}
|
|
|
5293 and @code{copy-primary-selection}. These work only on text selected
|
|
|
5294 with the mouse (probably; experiment), and are bound by default to the
|
|
|
5295 @kbd{Cut} and @kbd{Copy}, respectively, buttons on the toolbar.
|
|
|
5296 @code{copy-primary-selection} is also bound to @kbd{C-Insert}. You can
|
|
|
5297 yank the clipboard contents with @code{yank-primary-selection}, bound to
|
|
|
5298 the @kbd{Paste} toolbar button and @kbd{Sh-Insert}.
|
|
|
5299
|
|
|
5300 If you are communicating by cut and paste with applications that use the
|
|
|
5301 primary selection, then you can customize
|
|
|
5302 @code{interprogram-cut-function} to @code{nil}, restoring the XEmacs
|
|
|
5303 version 20 behavior. How can you tell if a program will support this?
|
|
|
5304 Motifly-correct programs require the clipboard; you lose. For others,
|
|
|
5305 only by trying it. You also need to customize the complementary
|
|
|
5306 @code{interprogram-paste-function} to @code{nil}. (Otherwise
|
|
|
5307 XEmacs-to-XEmacs pastes will not work correctly.)
|
|
|
5308
|
|
|
5309 You may get some relief on Motif by setting
|
|
|
5310 @code{x-selection-strict-motif-ownership} to nil, but this means you will
|
|
|
5311 only intermittently be able to paste XEmacs kills to Motif applications.
|
|
|
5312
|
|
|
5313 Thanks to Jeff Mincy and Glynn Clements for corrections.
|
|
|
5314
|
|
2459
|
5315 @node Q3.3.6, Q3.4.1, Q3.3.5, Editing
|
|
|
5316 @unnumberedsubsec Q3.3.6: Why does @kbd{M-w} take so long?
|
|
2417
|
5317
|
|
|
5318 It actually doesn't. It leaves the region visible for a second so that
|
|
|
5319 you can see what area is being yanked. If you start working, though, it
|
|
|
5320 will immediately complete its operation. In other words, it will only
|
|
|
5321 delay for a second if you let it.
|
|
|
5322
|
|
2459
|
5323 @unnumberedsec 3.4: Editing Source Code
|
|
|
5324
|
|
|
5325 @node Q3.4.1, Q3.4.2, Q3.3.6, Editing
|
|
|
5326 @unnumberedsubsec Q3.4.1: I do not like cc-mode. How do I use the old c-mode?
|
|
2417
|
5327
|
|
|
5328 Well, first off, consider if you really want to do this. cc-mode is
|
|
|
5329 much more powerful than the old c-mode. If you're having trouble
|
|
|
5330 getting your old offsets to work, try using @code{c-set-offset} instead.
|
|
|
5331 You might also consider using the package @code{cc-compat}.
|
|
|
5332
|
|
|
5333 But, if you still insist, add the following lines to your @file{init.el}:
|
|
|
5334
|
|
|
5335 @lisp
|
|
|
5336 (fmakunbound 'c-mode)
|
|
|
5337 (makunbound 'c-mode-map)
|
|
|
5338 (fmakunbound 'c++-mode)
|
|
|
5339 (makunbound 'c++-mode-map)
|
|
|
5340 (makunbound 'c-style-alist)
|
|
|
5341 (load-library "old-c-mode")
|
|
|
5342 (load-library "old-c++-mode")
|
|
|
5343 @end lisp
|
|
|
5344
|
|
|
5345 This must be done before any other reference is made to either c-mode or
|
|
|
5346 c++-mode.
|
|
|
5347
|
|
2459
|
5348 @node Q3.4.2, , Q3.4.1, Editing
|
|
|
5349 @unnumberedsubsec Q3.4.2: How do you make XEmacs indent CL if-clauses correctly?
|
|
2417
|
5350
|
|
|
5351 I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the
|
|
|
5352 same amount instead of indenting the 3rd clause differently from the
|
|
|
5353 first two.
|
|
|
5354
|
|
2459
|
5355 The package @code{cl-indent} that comes with XEmacs sets up this kind
|
|
|
5356 of indentation by default. @code{cl-indent} also knows about many
|
|
|
5357 other CL-specific forms. To use @code{cl-indent}, one can do this:
|
|
2417
|
5358
|
|
|
5359 @lisp
|
|
2459
|
5360 (setq lisp-indent-function 'common-lisp-indent-function)
|
|
2417
|
5361 @end lisp
|
|
|
5362
|
|
|
5363 One can also customize @file{cl-indent.el} so it mimics the default
|
|
|
5364 @code{if} indentation @code{then} indented more than the @code{else}.
|
|
|
5365 Here's how:
|
|
|
5366
|
|
|
5367 @lisp
|
|
|
5368 (put 'if 'common-lisp-indent-function '(nil nil &body))
|
|
|
5369 @end lisp
|
|
|
5370
|
|
2459
|
5371 @node Display, External Subsystems, Editing, Top
|
|
|
5372 @unnumbered 4 Display Functions
|
|
428
|
5373
|
|
|
5374 This is part 4 of the XEmacs Frequently Asked Questions list. This
|
|
2459
|
5375 section is devoted to the display-related capabilities of XEmacs
|
|
|
5376 (fonts, colors, modeline, menubar, toolbar, scrollbar, etc.) and how
|
|
|
5377 to customize them.
|
|
|
5378
|
|
|
5379 @menu
|
|
|
5380 4.0: Textual Fonts and Colors
|
|
|
5381 * Q4.0.1:: How do I specify a font?
|
|
|
5382 * Q4.0.2:: How do I set the text, menu and modeline fonts?
|
|
|
5383 * Q4.0.3:: How can I set color options from @file{init.el}?
|
|
|
5384 * Q4.0.4:: How can I set the colors when highlighting a region?
|
|
|
5385 * Q4.0.5:: How can I limit color map usage?
|
|
|
5386 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them.
|
|
|
5387 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs?
|
|
|
5388 * Q4.0.8:: How do I display non-ASCII characters?
|
|
|
5389 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}.
|
|
|
5390
|
|
|
5391 4.1: Syntax Highlighting (Font Lock)
|
|
|
5392 * Q4.1.1:: How can I do source code highlighting using font-lock?
|
|
|
5393 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
5394
|
|
|
5395 4.2: The Modeline
|
|
|
5396 * Q4.2.1:: How can I make the modeline go away?
|
|
|
5397 * Q4.2.2:: How do you have XEmacs display the line number in the modeline?
|
|
|
5398 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline?
|
|
|
5399 * Q4.2.4:: How can I change the modeline color based on the mode used?
|
|
|
5400
|
|
|
5401 4.3: The Cursor
|
|
|
5402 * Q4.3.1:: Is there a way to make the bar cursor thicker?
|
|
|
5403 * Q4.3.2:: Is there a way to get back the block cursor?
|
|
|
5404 * Q4.3.3:: Can I make the cursor blink?
|
|
|
5405
|
|
|
5406 4.4: The Menubar
|
|
|
5407 * Q4.4.1:: How do I get rid of the menubar?
|
|
|
5408 * Q4.4.2:: How can I customize the menubar?
|
|
|
5409 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
5410 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
5411 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
5412
|
|
|
5413 4.5: The Toolbar
|
|
|
5414 * Q4.5.1:: How do I get rid of the toolbar?
|
|
|
5415 * Q4.5.2:: How can I customize the toolbar?
|
|
|
5416 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar?
|
|
|
5417 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar
|
|
|
5418
|
|
|
5419 4.6: Scrollbars and Scrolling
|
|
|
5420 * Q4.6.1:: How can I disable the scrollbar?
|
|
|
5421 * Q4.6.2:: How can I change the scrollbar width?
|
|
|
5422 * Q4.6.3:: How can I use resources to change scrollbar colors?
|
|
|
5423 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this?
|
|
|
5424 * Q4.6.5:: Scrolling one line at a time.
|
|
|
5425 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
5426 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
5427
|
|
|
5428 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
5429 * Q4.7.1:: How can I disable the gutter tabs?
|
|
|
5430 * Q4.7.2:: How can I disable the progress bar?
|
|
|
5431 * Q4.7.3:: There are bugs in the gutter or widgets.
|
|
|
5432 * Q4.7.4:: How can I customize the gutter or gutter tabs?
|
|
|
5433 @end menu
|
|
|
5434
|
|
|
5435 @unnumberedsec 4.0: Textual Fonts and Colors
|
|
|
5436
|
|
|
5437 @node Q4.0.1, Q4.0.2, Display, Display
|
|
|
5438 @unnumberedsubsec Q4.0.1: How do I specify a font?
|
|
|
5439
|
|
|
5440 #### Update me.
|
|
|
5441
|
|
|
5442 In 21.4 and above, you can use the @samp{Options} menu to change the font.
|
|
|
5443 You can also do it in your init file, e.g. like this (for MS Windows):
|
|
|
5444
|
|
|
5445 @display
|
|
|
5446 (set-face-font 'default "Lucida Console:Regular:10")
|
|
|
5447 (set-face-font 'modeline "MS Sans Serif:Regular:10")
|
|
|
5448 @end display
|
|
|
5449
|
|
|
5450 @node Q4.0.2, Q4.0.3, Q4.0.1, Display
|
|
|
5451 @unnumberedsubsec Q4.0.2: How do I set the text, menu and modeline fonts?
|
|
|
5452
|
|
|
5453 #### Update me.
|
|
|
5454
|
|
|
5455 Note that you should use @samp{Emacs.} and not @samp{Emacs*} when
|
|
|
5456 setting face values.
|
|
|
5457
|
|
|
5458 In @file{.Xresources}:
|
|
|
5459
|
|
|
5460 @example
|
|
|
5461 Emacs.default.attributeFont: -*-*-medium-r-*-*-*-120-*-*-m-*-*-*
|
|
|
5462 Emacs*menubar*font: fixed
|
|
|
5463 Emacs.modeline.attributeFont: fixed
|
|
|
5464 @end example
|
|
|
5465
|
|
|
5466 This is confusing because @samp{default} and @samp{modeline} are face
|
|
|
5467 names, and can be found listed with all faces in the current mode by
|
|
|
5468 using @kbd{M-x set-face-font (enter) ?}. They use the face-specific
|
|
|
5469 resource @samp{attributeFont}.
|
|
|
5470
|
|
|
5471 On the other hand, @samp{menubar} is a normal X thing that uses the
|
|
|
5472 resource @samp{font}. With Motif it @emph{may be} necessary to use
|
|
|
5473 @samp{fontList} @emph{instead of} @samp{font}. In @emph{non-Motif}
|
|
|
5474 configurations with Mule it @emph{is} necessary to use @samp{fontSet}
|
|
|
5475 instead of @samp{font}. (Sorry, there just is no simple recipe here.)
|
|
|
5476
|
|
|
5477 @node Q4.0.3, Q4.0.4, Q4.0.2, Display
|
|
|
5478 @unnumberedsubsec Q4.0.3: How can I set color options from @file{init.el}?
|
|
|
5479
|
|
|
5480 How can I set the most commonly used color options from my
|
|
|
5481 @file{init.el} instead of from my @file{.Xresources}?
|
|
|
5482
|
|
|
5483 Like this:
|
|
|
5484
|
|
|
5485 @lisp
|
|
|
5486 (set-face-background 'default "bisque") ; frame background
|
|
|
5487 (set-face-foreground 'default "black") ; normal text
|
|
|
5488 (set-face-background 'zmacs-region "red") ; When selecting w/
|
|
|
5489 ; mouse
|
|
|
5490 (set-face-foreground 'zmacs-region "yellow")
|
|
|
5491 (set-face-font 'default "*courier-bold-r*120-100-100*")
|
|
|
5492 (set-face-background 'highlight "blue") ; Ie when selecting
|
|
|
5493 ; buffers
|
|
|
5494 (set-face-foreground 'highlight "yellow")
|
|
|
5495 (set-face-background 'modeline "blue") ; Line at bottom
|
|
|
5496 ; of buffer
|
|
|
5497 (set-face-foreground 'modeline "white")
|
|
|
5498 (set-face-font 'modeline "*bold-r-normal*140-100-100*")
|
|
|
5499 (set-face-background 'isearch "yellow") ; When highlighting
|
|
|
5500 ; while searching
|
|
|
5501 (set-face-foreground 'isearch "red")
|
|
|
5502 (setq x-pointer-foreground-color "black") ; Adds to bg color,
|
|
|
5503 ; so keep black
|
|
|
5504 (setq x-pointer-background-color "blue") ; This is color
|
|
|
5505 ; you really
|
|
|
5506 ; want ptr/crsr
|
|
|
5507 @end lisp
|
|
|
5508
|
|
|
5509 @node Q4.0.4, Q4.0.5, Q4.0.3, Display
|
|
|
5510 @unnumberedsubsec Q4.0.4: How can I set the colors when highlighting a region?
|
|
|
5511
|
|
|
5512 How can I set the background/foreground colors when highlighting a
|
|
|
5513 region?
|
|
|
5514
|
|
|
5515 You can change the face @code{zmacs-region} either in your
|
|
|
5516 @file{.Xresources}:
|
|
|
5517
|
|
|
5518 @example
|
|
|
5519 Emacs.zmacs-region.attributeForeground: firebrick
|
|
|
5520 Emacs.zmacs-region.attributeBackground: lightseagreen
|
|
|
5521 @end example
|
|
|
5522
|
|
|
5523 or in your @file{init.el}:
|
|
|
5524
|
|
|
5525 @lisp
|
|
|
5526 (set-face-background 'zmacs-region "red")
|
|
|
5527 (set-face-foreground 'zmacs-region "yellow")
|
|
|
5528 @end lisp
|
|
|
5529
|
|
|
5530 @node Q4.0.5, Q4.0.6, Q4.0.4, Display
|
|
|
5531 @unnumberedsubsec Q4.0.5: How can I limit color map usage?
|
|
|
5532
|
|
|
5533 I'm using Netscape (or another color grabber like XEmacs);
|
|
|
5534 is there any way to limit the number of available colors in the color map?
|
|
|
5535
|
|
|
5536 Answer: No, but you can start Netscape before XEmacs, and it will use
|
|
|
5537 the closest available color if the colormap is full. You can also limit
|
|
|
5538 the number of colors Netscape uses, using the flags -mono, -ncols <#> or
|
|
|
5539 -install (for mono, limiting to <#> colors, or for using a private color
|
|
|
5540 map).
|
|
|
5541
|
|
|
5542 If you have the money, another solution would be to use a truecolor or
|
|
|
5543 direct color video.
|
|
|
5544
|
|
|
5545 @node Q4.0.6, Q4.0.7, Q4.0.5, Display
|
|
|
5546 @unnumberedsubsec Q4.0.6: My tty supports color, but XEmacs doesn't use them.
|
|
|
5547
|
|
|
5548 XEmacs tries to automatically determine whether your tty supports color,
|
|
|
5549 but sometimes guesses wrong. In that case, you can make XEmacs Do The
|
|
|
5550 Right Thing using this Lisp code:
|
|
|
5551
|
|
|
5552 @lisp
|
|
|
5553 (if (eq 'tty (device-type))
|
|
|
5554 (set-device-class nil 'color))
|
|
|
5555 @end lisp
|
|
|
5556
|
|
|
5557 @node Q4.0.7, Q4.0.8, Q4.0.6, Display
|
|
|
5558 @unnumberedsubsec Q4.0.7: Can I have pixmap backgrounds in XEmacs?
|
|
|
5559 @c New
|
|
|
5560 @email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes:
|
|
|
5561
|
|
|
5562 @quotation
|
|
|
5563 There are several ways to do it. For example, you could specify a
|
|
|
5564 default pixmap image to use in your @file{~/.Xresources}, e.g.,
|
|
|
5565
|
|
|
5566
|
|
|
5567 @example
|
|
|
5568 Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm
|
|
|
5569 @end example
|
|
|
5570
|
|
|
5571
|
|
|
5572 and then reload ~/.Xresources and restart XEmacs. Alternatively,
|
|
|
5573 since each face can have its own pixmap background, a better way
|
|
|
5574 would be to set a face's pixmap within your XEmacs init file, e.g.,
|
|
|
5575
|
|
|
5576 @lisp
|
|
|
5577 (set-face-background-pixmap 'default "/path/to/image.xpm")
|
|
|
5578 (set-face-background-pixmap 'bold "/path/to/another_image.xpm")
|
|
|
5579 @end lisp
|
|
|
5580
|
|
|
5581 and so on. You can also do this interactively via @kbd{M-x edit-faces}.
|
|
|
5582
|
|
|
5583 @end quotation
|
|
|
5584
|
|
|
5585 @node Q4.0.8, Q4.0.9, Q4.0.7, Display
|
|
|
5586 @unnumberedsubsec Q4.0.8: How do I display non-ASCII characters?
|
|
|
5587 @c New
|
|
|
5588
|
|
|
5589 If you're using a Mule-enabled XEmacs, then display is automatic. If
|
|
|
5590 you're not seeing the characters you expect, either (1) you don't have
|
|
|
5591 appropriate fonts available or (2) XEmacs did not correctly detect the
|
|
|
5592 coding system (@pxref{Recognize Coding, , , xemacs}). In case (1),
|
|
|
5593 install fonts as is customary for your platform. In case (2), you
|
|
|
5594 need to tell XEmacs explicitly what coding systems you're using.
|
|
|
5595 @ref{Specify Coding, , , xemacs}.
|
|
|
5596
|
|
|
5597 If your XEmacs is not Mule-enabled, and for some reason getting a
|
|
|
5598 Mule-enabled XEmacs seems like the wrong thing to do, all is not lost.
|
|
|
5599 You can arrange it by brute force. In @file{event-Xt.c} (suppress the
|
|
|
5600 urge to look in this file---play Doom instead, because you'll survive
|
|
|
5601 longer), it is written:
|
|
|
5602
|
|
|
5603 @quotation
|
|
|
5604 In a non-Mule world, a user can still have a multi-lingual editor, by
|
|
|
5605 doing @code{(set-face-font "-*-iso8859-2" (current-buffer))} for all
|
|
|
5606 their Latin-2 buffers, etc.
|
|
|
5607 @end quotation
|
|
|
5608
|
|
|
5609 For the related problem of @emph{inputting} non-ASCII characters in a
|
|
|
5610 non-Mule XEmacs, @xref{Q3.0.6, How can you type in special characters
|
|
|
5611 in XEmacs?}.
|
|
|
5612
|
|
|
5613 @node Q4.0.9, Q4.1.1, Q4.0.8, Display
|
|
|
5614 @unnumberedsubsec Q4.0.9: Font selections in don't get saved after @code{Save Options}.
|
|
|
5615
|
|
|
5616 @email{mannj@@ll.mit.edu, John Mann} writes:
|
|
|
5617
|
|
|
5618 @quotation
|
|
|
5619 You have to go to @samp{Options->Menubars} and unselect
|
|
|
5620 @samp{Frame-Local Font Menu}. If this option is selected, font changes
|
|
|
5621 are only applied to the @emph{current} frame and do @emph{not} get saved
|
|
|
5622 when you save options.
|
|
|
5623 @end quotation
|
|
|
5624
|
|
|
5625 Also, set the following in your @file{init.el}:
|
|
|
5626
|
|
|
5627 @lisp
|
|
|
5628 (setq options-save-faces t)
|
|
|
5629 @end lisp
|
|
|
5630
|
|
|
5631 @unnumberedsec 4.1: Syntax Highlighting (Font Lock)
|
|
|
5632
|
|
|
5633 @node Q4.1.1, Q4.1.2, Q4.0.9, Display
|
|
|
5634 @unnumberedsubsec Q4.1.1: How can I do source code highlighting using font-lock?
|
|
|
5635
|
|
|
5636 For most modes, font-lock is already set up and just needs to be turned
|
|
|
5637 on. This can be done by adding the line:
|
|
|
5638
|
|
|
5639 @lisp
|
|
|
5640 (require 'font-lock)
|
|
|
5641 @end lisp
|
|
|
5642
|
|
|
5643 to your @file{init.el}. (You can turn it on for the
|
|
|
5644 current buffer and session only by @kbd{M-x font-lock-mode}.) See the
|
|
|
5645 file @file{etc/sample.init.el} (@file{etc/sample.emacs} in XEmacs
|
|
|
5646 versions prior to 21.4) for more information.
|
|
|
5647
|
|
|
5648 @c the old way:
|
|
|
5649 @c (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
|
|
|
5650 @c (add-hook 'dired-mode-hook 'turn-on-font-lock)
|
|
|
5651
|
|
|
5652 See also @code{Syntax Highlighting} from the @code{Options} menu.
|
|
|
5653 Remember to save options.
|
|
|
5654
|
|
|
5655 @node Q4.1.2, Q4.2.1, Q4.1.1, Display
|
|
|
5656 @unnumberedsubsec Q4.1.2: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
5657
|
|
|
5658 Use the following code in your @file{init.el}:
|
|
|
5659
|
|
|
5660 @lisp
|
|
|
5661 (setq-default font-lock-maximum-decoration t)
|
|
|
5662 @end lisp
|
|
|
5663
|
|
|
5664 See also @code{Syntax Highlighting} from the @code{Options} menu.
|
|
|
5665 Remember to save options.
|
|
|
5666
|
|
|
5667 @unnumberedsec 4.2: The Modeline
|
|
|
5668
|
|
|
5669 @node Q4.2.1, Q4.2.2, Q4.1.2, Display
|
|
|
5670 @unnumberedsubsec Q4.2.1: How can I make the modeline go away?
|
|
|
5671
|
|
|
5672 @lisp
|
|
|
5673 (set-specifier has-modeline-p nil)
|
|
|
5674 @end lisp
|
|
|
5675
|
|
|
5676 @node Q4.2.2, Q4.2.3, Q4.2.1, Display
|
|
|
5677 @unnumberedsubsec Q4.2.2: How do you have XEmacs display the line number in the modeline?
|
|
|
5678
|
|
|
5679 Add the following line to your @file{init.el} file to
|
|
|
5680 display the line number:
|
|
|
5681
|
|
|
5682 @lisp
|
|
|
5683 (line-number-mode 1)
|
|
|
5684 @end lisp
|
|
|
5685
|
|
|
5686 Use the following to display the column number:
|
|
|
5687
|
|
|
5688 @lisp
|
|
|
5689 (column-number-mode 1)
|
|
|
5690 @end lisp
|
|
|
5691
|
|
|
5692 Or select from the @code{Options} menu
|
|
|
5693 @iftex
|
|
|
5694 @*
|
|
|
5695 @end iftex
|
|
|
5696 @code{Advanced (Customize)->Emacs->Editing->Basics->Line Number Mode}
|
|
|
5697 and/or
|
|
|
5698 @iftex
|
|
|
5699 @*
|
|
|
5700 @end iftex
|
|
|
5701 @code{Advanced (Customize)->Emacs->Editing->Basics->Column Number Mode}
|
|
|
5702
|
|
|
5703 Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
|
|
|
5704
|
|
|
5705 @node Q4.2.3, Q4.2.4, Q4.2.2, Display
|
|
|
5706 @unnumberedsubsec Q4.2.3: How do I get XEmacs to put the time of day on the modeline?
|
|
|
5707
|
|
|
5708 Add the following line to your @file{init.el} file to
|
|
|
5709 display the time:
|
|
|
5710
|
|
|
5711 @lisp
|
|
|
5712 (display-time)
|
|
|
5713 @end lisp
|
|
|
5714
|
|
|
5715 See @code{Customize} from the @code{Options} menu for customization.
|
|
|
5716
|
|
|
5717 @node Q4.2.4, Q4.3.1, Q4.2.3, Display
|
|
|
5718 @unnumberedsubsec Q4.2.4: How can I change the modeline color based on the mode used?
|
|
|
5719
|
|
|
5720 You can use something like the following:
|
|
|
5721
|
|
|
5722 @lisp
|
|
|
5723 (add-hook 'lisp-mode-hook
|
|
|
5724 (lambda ()
|
|
|
5725 (set-face-background 'modeline "red" (current-buffer))))
|
|
|
5726 @end lisp
|
|
|
5727
|
|
|
5728 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
|
|
|
5729 colors change from the default set in your @file{init.el}.
|
|
|
5730 The change will only be made in the buffer you just entered (which
|
|
|
5731 contains the Lisp file you are editing) and will not affect the modeline
|
|
|
5732 colors anywhere else.
|
|
|
5733
|
|
|
5734 Notes:
|
|
|
5735
|
|
|
5736 @itemize @bullet
|
|
|
5737
|
|
|
5738 @item The hook is the mode name plus @code{-hook}. eg. c-mode-hook,
|
|
|
5739 c++-mode-hook, emacs-lisp-mode-hook (used for your
|
|
|
5740 @file{init.el} or a @file{xx.el} file),
|
|
|
5741 lisp-interaction-mode-hook (the @samp{*scratch*} buffer),
|
|
|
5742 text-mode-hook, etc.
|
|
|
5743
|
|
|
5744 @item
|
|
|
5745 Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)},
|
|
|
5746 otherwise you will erase anything that anybody has already put on the
|
|
|
5747 hook.
|
|
|
5748
|
|
|
5749 @item
|
|
|
5750 You can also do @code{(set-face-font 'modeline @var{font})},
|
|
|
5751 eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*"
|
|
|
5752 (current-buffer))} if you wish the modeline font to vary based on the
|
|
|
5753 current mode.
|
|
|
5754 @end itemize
|
|
|
5755
|
|
|
5756 There are additional modeline faces, @code{modeline-buffer-id},
|
|
|
5757 @code{modeline-mousable}, and @code{modeline-mousable-minor-mode}, which
|
|
|
5758 you may want to customize.
|
|
|
5759
|
|
|
5760 @unnumberedsec 4.3: The Cursor
|
|
|
5761
|
|
|
5762 @node Q4.3.1, Q4.3.2, Q4.2.4, Display
|
|
|
5763 @unnumberedsubsec Q4.3.1: Is there a way to make the bar cursor thicker?
|
|
|
5764
|
|
|
5765 I'd like to have the bar cursor a little thicker, as I tend to "lose" it
|
|
|
5766 often.
|
|
|
5767
|
|
|
5768 For a 1 pixel bar cursor, use:
|
|
|
5769
|
|
|
5770 @lisp
|
|
|
5771 (setq bar-cursor t)
|
|
|
5772 @end lisp
|
|
|
5773
|
|
|
5774 For a 2 pixel bar cursor, use:
|
|
|
5775
|
|
|
5776 @lisp
|
|
|
5777 (setq bar-cursor 'anything-else)
|
|
|
5778 @end lisp
|
|
|
5779
|
|
|
5780 You can also change these with Customize.
|
|
|
5781 Select from the @code{Options} menu
|
|
|
5782 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
|
|
|
5783 @kbd{M-x customize @key{RET} display @key{RET}}.
|
|
|
5784
|
|
|
5785 You can use a color to make it stand out better:
|
|
|
5786
|
|
|
5787 @example
|
|
|
5788 Emacs*cursorColor: Red
|
|
|
5789 @end example
|
|
|
5790
|
|
|
5791 @node Q4.3.2, Q4.3.3, Q4.3.1, Display
|
|
|
5792 @unnumberedsubsec Q4.3.2: Is there a way to get back the block cursor?
|
|
|
5793
|
|
|
5794 @lisp
|
|
|
5795 (setq bar-cursor nil)
|
|
|
5796 @end lisp
|
|
|
5797
|
|
|
5798 You can also change this with Customize.
|
|
|
5799 Select from the @code{Options} menu
|
|
|
5800 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
|
|
|
5801 @kbd{M-x customize @key{RET} display @key{RET}}.
|
|
|
5802
|
|
|
5803 @node Q4.3.3, Q4.4.1, Q4.3.2, Display
|
|
|
5804 @unnumberedsubsec Q4.3.3: Can I make the cursor blink?
|
|
|
5805
|
|
|
5806 Yes, like this:
|
|
|
5807
|
|
|
5808 @lisp
|
|
|
5809 (blink-cursor-mode)
|
|
|
5810 @end lisp
|
|
|
5811
|
|
|
5812 This function toggles between a steady cursor and a blinking cursor.
|
|
|
5813 You may also set this mode from the menu bar by selecting
|
|
|
5814 @samp{Options->Display->Blinking Cursor}. Remember to save options.
|
|
|
5815
|
|
|
5816 @unnumberedsec 4.4: The Menubar
|
|
|
5817
|
|
|
5818 @node Q4.4.1, Q4.4.2, Q4.3.3, Display
|
|
|
5819 @unnumberedsubsec Q4.4.1: How do I get rid of the menubar?
|
|
|
5820
|
|
|
5821 @lisp
|
|
|
5822 (set-specifier menubar-visible-p nil)
|
|
|
5823 @end lisp
|
|
|
5824
|
|
|
5825 @node Q4.4.2, Q4.4.3, Q4.4.1, Display
|
|
|
5826 @unnumberedsubsec Q4.4.2: How can I customize the menubar?
|
|
|
5827
|
|
|
5828 For an extensive menubar, add this line to your @file{init.el}:
|
|
|
5829
|
|
|
5830 @lisp
|
|
|
5831 (load "big-menubar")
|
|
|
5832 @end lisp
|
|
|
5833
|
|
|
5834 If you'd like to write your own, this file provides as good a set of
|
|
|
5835 examples as any to start from. The file is located in edit-utils
|
|
|
5836 package.
|
|
|
5837
|
|
|
5838 @node Q4.4.3, Q4.4.4, Q4.4.2, Display
|
|
|
5839 @unnumberedsubsec Q4.4.3: How do I enable use of the keyboard (@kbd{Alt}) to access menu items?
|
|
|
5840
|
|
|
5841 #### Write me.
|
|
|
5842
|
|
|
5843 @node Q4.4.4, Q4.4.5, Q4.4.3, Display
|
|
|
5844 @unnumberedsubsec Q4.4.4: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
|
5845
|
|
|
5846 Add the following to your @file{init.el} (suit to fit):
|
|
|
5847
|
|
|
5848 @lisp
|
|
|
5849 (setq buffers-menu-max-size 20)
|
|
|
5850 @end lisp
|
|
|
5851
|
|
|
5852 For no limit, use an argument of @samp{nil}.
|
|
|
5853
|
|
|
5854 You can also change this with Customize. Select from the
|
|
|
5855 @code{Options} menu
|
|
|
5856 @code{Advanced (Customize)->Emacs->Environment->Menu->Buffers Menu->Max Size...}
|
|
|
5857 or type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}.
|
|
|
5858
|
|
|
5859 @node Q4.4.5, Q4.5.1, Q4.4.4, Display
|
|
|
5860 @unnumberedsubsec Q4.4.5: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
5861
|
|
|
5862 I am trying to use a resource like @code{Emacs*menubar*font} to set the
|
|
|
5863 font of the menubar but it's not working.
|
|
|
5864
|
|
|
5865 In Motif, the use of @samp{font} resources is obsoleted in order to
|
|
|
5866 support internationalization. If you are using the real Motif menubar,
|
|
|
5867 this resource is not recognized at all; you have to say:
|
|
|
5868
|
|
|
5869 @example
|
|
|
5870 Emacs*menubar*fontList: FONT
|
|
|
5871 @end example
|
|
|
5872
|
|
|
5873 If you are using the Lucid menubar, for backward compatibility with
|
|
|
5874 existing user configurations, the @samp{font} resource is recognized.
|
|
|
5875 Since this is not supported by Motif itself, the code is a kludge and
|
|
|
5876 the @samp{font} resource will be recognized only if the @samp{fontList}
|
|
|
5877 resource resource is unset. This means that the resource
|
|
|
5878
|
|
|
5879 @example
|
|
|
5880 *fontList: FONT
|
|
|
5881 @end example
|
|
|
5882
|
|
|
5883 will override
|
|
|
5884
|
|
|
5885 @example
|
|
|
5886 Emacs*menubar*font: FONT
|
|
|
5887 @end example
|
|
|
5888
|
|
|
5889 even though the latter is more specific.
|
|
|
5890
|
|
|
5891 In non-Motif configurations using @samp{--with-mule} and
|
|
|
5892 @samp{--with-xfs} it @emph{is} necessary to use the @code{fontSet}
|
|
|
5893 resource @emph{instead of} the @code{font} resource. The backward
|
|
|
5894 compatibility kludge was never implemented for non-Motif builds.
|
|
|
5895 Example:
|
|
|
5896
|
|
|
5897 @example
|
|
|
5898 *fontSet: FONT
|
|
|
5899 @end example
|
|
|
5900
|
|
|
5901 @unnumberedsec 4.5: The Toolbar
|
|
|
5902
|
|
|
5903 @node Q4.5.1, Q4.5.2, Q4.4.5, Display
|
|
|
5904 @unnumberedsubsec Q4.5.1: How do I get rid of the toolbar?
|
|
|
5905
|
|
|
5906 #### Write me.
|
|
|
5907
|
|
|
5908 @node Q4.5.2, Q4.5.3, Q4.5.1, Display
|
|
|
5909 @unnumberedsubsec Q4.5.2: How can I customize the toolbar?
|
|
|
5910
|
|
|
5911 #### Write me.
|
|
|
5912
|
|
|
5913 @node Q4.5.3, Q4.5.4, Q4.5.2, Display
|
|
|
5914 @unnumberedsubsec Q4.5.3: How can I bind a key to a function to toggle the toolbar?
|
|
|
5915
|
|
|
5916 Try something like:
|
|
|
5917
|
|
|
5918 @lisp
|
|
|
5919 (defun my-toggle-toolbar ()
|
|
|
5920 (interactive)
|
|
|
5921 (set-specifier default-toolbar-visible-p
|
|
|
5922 (not (specifier-instance default-toolbar-visible-p))))
|
|
|
5923 (global-set-key "\C-xT" 'my-toggle-toolbar)
|
|
|
5924 @end lisp
|
|
|
5925
|
|
|
5926 @ignore
|
|
|
5927 @c Probably not relevant any more
|
|
|
5928 There are redisplay bugs in 19.14 that may make the preceding result in
|
|
|
5929 a messed-up display, especially for frames with multiple windows. You
|
|
|
5930 may need to resize the frame before XEmacs completely realizes the
|
|
|
5931 toolbar is really gone.
|
|
|
5932 @end ignore
|
|
|
5933
|
|
|
5934 Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct
|
|
|
5935 code.
|
|
|
5936
|
|
|
5937 @node Q4.5.4, Q4.6.1, Q4.5.3, Display
|
|
|
5938 @unnumberedsubsec Q4.5.4: @samp{Can't instantiate image error...} in toolbar
|
|
|
5939
|
|
|
5940 @email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes:
|
|
|
5941
|
|
|
5942 I just installed the XEmacs (20.4-2) RPMS that I downloaded from
|
|
|
5943 @uref{http://www.xemacs.org/}. Everything works fine, except that when
|
|
|
5944 I place my mouse over the toolbar, it beeps and gives me this message:
|
|
|
5945
|
|
|
5946 @example
|
|
|
5947 Can't instantiate image (probably cached):
|
|
|
5948 [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data
|
|
|
5949 (16 16 <strange control characters> ...
|
|
|
5950 @end example
|
|
|
5951
|
|
|
5952 @email{kyle_jones@@wonderworks.com, Kyle Jones} writes:
|
|
|
5953 @quotation
|
|
|
5954 This is problem specific to some Chips and Technologies video
|
|
|
5955 chips, when running XFree86. Putting
|
|
|
5956
|
|
|
5957 @code{Option "sw_cursor"}
|
|
|
5958
|
|
|
5959 in @file{XF86Config} gets rid of the problem.
|
|
|
5960 @end quotation
|
|
|
5961
|
|
|
5962 @unnumberedsec 4.6: Scrollbars and Scrolling
|
|
|
5963
|
|
|
5964 @node Q4.6.1, Q4.6.2, Q4.5.4, Display
|
|
|
5965 @unnumberedsubsec Q4.6.1: How can I disable the scrollbar?
|
|
|
5966
|
|
|
5967 To disable them for all frames, add the following line to
|
|
|
5968 your @file{.Xresources}:
|
|
|
5969
|
|
|
5970 @example
|
|
|
5971 Emacs.scrollBarWidth: 0
|
|
|
5972 @end example
|
|
|
5973
|
|
|
5974 Or select @samp{Options->Display->Scrollbars}.
|
|
|
5975 Remember to save options.
|
|
|
5976
|
|
|
5977 To turn the scrollbar off on a per-frame basis, use the following
|
|
|
5978 function:
|
|
|
5979
|
|
|
5980 @lisp
|
|
|
5981 (set-specifier scrollbar-width 0 (selected-frame))
|
|
|
5982 @end lisp
|
|
|
5983
|
|
|
5984 You can actually turn the scrollbars on at any level you want by
|
|
|
5985 substituting for (selected-frame) in the above command. For example, to
|
|
|
5986 turn the scrollbars off only in a single buffer:
|
|
|
5987
|
|
|
5988 @lisp
|
|
|
5989 (set-specifier scrollbar-width 0 (current-buffer))
|
|
|
5990 @end lisp
|
|
|
5991
|
|
|
5992 @node Q4.6.2, Q4.6.3, Q4.6.1, Display
|
|
|
5993 @unnumberedsubsec Q4.6.2: How can I change the scrollbar width?
|
|
|
5994
|
|
|
5995 #### Write me.
|
|
|
5996
|
|
|
5997 @node Q4.6.3, Q4.6.4, Q4.6.2, Display
|
|
|
5998 @unnumberedsubsec Q4.6.3: How can I use resources to change scrollbar colors?
|
|
|
5999
|
|
|
6000 Here's a recap of how to use resources to change your scrollbar colors:
|
|
|
6001
|
|
|
6002 @example
|
|
|
6003 ! Motif scrollbars
|
|
|
6004
|
|
|
6005 Emacs*XmScrollBar.Background: skyblue
|
|
|
6006 Emacs*XmScrollBar.troughColor: lightgray
|
|
|
6007
|
|
|
6008 ! Athena scrollbars
|
|
|
6009
|
|
|
6010 Emacs*Scrollbar.Foreground: skyblue
|
|
|
6011 Emacs*Scrollbar.Background: lightgray
|
|
|
6012 @end example
|
|
|
6013
|
|
|
6014 Note the capitalization of @code{Scrollbar} for the Athena widget.
|
|
|
6015
|
|
|
6016 @node Q4.6.4, Q4.6.5, Q4.6.3, Display
|
|
|
6017 @unnumberedsubsec Q4.6.4: Moving the scrollbar can move the point; can I disable this?
|
|
|
6018
|
|
|
6019 When I move the scrollbar in an XEmacs window, it moves the point as
|
|
|
6020 well, which should not be the default behavior. Is this a bug or a
|
|
|
6021 feature? Can I disable it?
|
|
|
6022
|
|
|
6023 The current behavior is a feature, not a bug. Point remains at the same
|
|
|
6024 buffer position as long as that position does not scroll off the screen.
|
|
|
6025 In that event, point will end up in either the upper-left or lower-left
|
|
|
6026 hand corner.
|
|
|
6027
|
|
|
6028 This cannot be changed.
|
|
|
6029
|
|
|
6030 @node Q4.6.5, Q4.6.6, Q4.6.4, Display
|
|
|
6031 @unnumberedsubsec Q4.6.5: Scrolling one line at a time.
|
|
|
6032
|
|
|
6033 Can the cursor keys scroll the screen a line at a time, rather than the
|
|
|
6034 default half page jump? I tend it to find it disorienting.
|
|
|
6035
|
|
|
6036 Use the following:
|
|
|
6037
|
|
|
6038 @lisp
|
|
|
6039 (setq scroll-step 1)
|
|
|
6040 @end lisp
|
|
|
6041
|
|
|
6042 You can also change this with Customize. Select from the
|
|
|
6043 @code{Options} menu
|
|
|
6044 @code{Advanced (Customize)->Emacs->Environment->Windows->Scroll Step...}
|
|
|
6045 or type @kbd{M-x customize @key{RET} windows @key{RET}}.
|
|
|
6046
|
|
|
6047 @node Q4.6.6, Q4.6.7, Q4.6.5, Display
|
|
|
6048 @unnumberedsubsec Q4.6.6: How can I turn off automatic horizontal scrolling in specific modes?
|
|
|
6049
|
|
|
6050 Do @code{(setq truncate-lines t)} in the mode-hooks for any modes
|
|
|
6051 in which you want lines truncated.
|
|
|
6052
|
|
|
6053 More precisely: If @code{truncate-lines} is nil, horizontal scrollbars
|
|
|
6054 will never appear. Otherwise, they will appear only if the value of
|
|
|
6055 @code{scrollbar-height} for that buffer/window/etc. is non-zero. If you
|
|
|
6056 do
|
|
|
6057
|
|
|
6058 @lisp
|
|
|
6059 (set-specifier scrollbar-height 0)
|
|
|
6060 @end lisp
|
|
|
6061
|
|
|
6062 then horizontal scrollbars will not appear in truncated buffers unless
|
|
|
6063 the package specifically asked for them.
|
|
|
6064
|
|
|
6065 @node Q4.6.7, Q4.7.1, Q4.6.6, Display
|
|
|
6066 @unnumberedsubsec Q4.6.7: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
6067
|
|
|
6068 @code{auto-show-mode} controls whether or not a horizontal scrollbar
|
|
|
6069 magically appears when a line is too long to be displayed. This is
|
|
|
6070 enabled by default. To turn it off, put the following in your
|
|
|
6071 @file{init.el}:
|
|
|
6072
|
|
|
6073 @lisp
|
|
|
6074 (setq auto-show-mode nil)
|
|
|
6075 (setq-default auto-show-mode nil)
|
|
|
6076 @end lisp
|
|
|
6077
|
|
|
6078 @unnumberedsec 4.7: The Gutter Tabs, The Progress Bar, Widgets
|
|
|
6079
|
|
|
6080 @node Q4.7.1, Q4.7.2, Q4.6.7, Display
|
|
|
6081 @unnumberedsubsec Q4.7.1: How can I disable the gutter tabs?
|
|
|
6082
|
|
|
6083 #### Write me.
|
|
|
6084
|
|
|
6085 @node Q4.7.2, Q4.7.3, Q4.7.1, Display
|
|
|
6086 @unnumberedsubsec Q4.7.2: How can I disable the progress bar?
|
|
|
6087
|
|
|
6088 #### Write me.
|
|
|
6089
|
|
|
6090 @node Q4.7.3, Q4.7.4, Q4.7.2, Display
|
|
|
6091 @unnumberedsubsec Q4.7.3: There are bugs in the gutter or widgets.
|
|
|
6092
|
|
|
6093 #### Write me.
|
|
|
6094
|
|
|
6095 @node Q4.7.4, , Q4.7.3, Display
|
|
|
6096 @unnumberedsubsec Q4.7.4: How can I customize the gutter or gutter tabs?
|
|
|
6097
|
|
|
6098 #### Write me.
|
|
|
6099
|
|
|
6100 @node External Subsystems, Internet, Display, Top
|
|
|
6101 @unnumbered 5 Interfacing with the Operating System and External Devices
|
|
|
6102
|
|
|
6103 This is part 5 of the XEmacs Frequently Asked Questions list. This
|
|
2417
|
6104 section is devoted to the various ways that XEmacs interfaces with the
|
|
|
6105 operating system, with other processes and with external devices such
|
|
|
6106 as speakers and the printer.
|
|
428
|
6107
|
|
|
6108 @menu
|
|
2459
|
6109 5.0: X Window System and Resources
|
|
|
6110 * Q5.0.1:: Where is a list of X resources?
|
|
|
6111 * Q5.0.2:: How can I detect a color display?
|
|
|
6112 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}?
|
|
|
6113 * Q5.0.4:: How can I have the window title area display the full path?
|
|
|
6114 * Q5.0.5:: @samp{xemacs -name junk} doesn't work?
|
|
|
6115 * Q5.0.6:: @samp{-iconic} doesn't work.
|
|
|
6116
|
|
|
6117 5.1: Microsoft Windows
|
|
|
6118 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
|
6119 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
|
6120
|
|
|
6121 5.2: Printing
|
|
|
6122 * Q5.2.1:: What do I need to change to make printing work?
|
|
|
6123 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer?
|
|
|
6124 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
|
6125 * Q5.2.4:: Can you print under MS Windows?
|
|
|
6126
|
|
|
6127 5.3: Sound
|
|
|
6128 * Q5.3.1:: How do I turn off the sound?
|
|
|
6129 * Q5.3.2:: How do I get funky sounds instead of a boring beep?
|
|
|
6130 * Q5.3.3:: What are NAS and ESD (EsounD)?
|
|
|
6131 * Q5.3.4:: Sunsite sounds don't play.
|
|
|
6132
|
|
|
6133 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
6134 * Q5.4.1:: What is an interior shell?
|
|
|
6135 * Q5.4.2:: How do I start up a second shell buffer?
|
|
|
6136 * Q5.4.3:: Telnet from shell filters too much
|
|
|
6137 * Q5.4.4:: Strange things are happening in Shell Mode.
|
|
|
6138 * Q5.4.5:: XEmacs complains "No such file or directory, diff"
|
|
2995
|
6139 * Q5.4.6:: Cygwin error "fork_copy: linked dll/bss pass 0 failed"
|
|
2459
|
6140
|
|
|
6141 5.5: Multiple Device Support
|
|
|
6142 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display?
|
|
|
6143 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
6144 * Q5.5.3:: How do I disable gnuserv from opening a new frame?
|
|
|
6145 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
|
6146 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
428
|
6147 @end menu
|
|
|
6148
|
|
2459
|
6149 @unnumberedsec 5.0: X Window System and Resources
|
|
|
6150
|
|
|
6151 @node Q5.0.1, Q5.0.2, External Subsystems, External Subsystems
|
|
|
6152 @unnumberedsubsec Q5.0.1: Where is a list of X resources?
|
|
2417
|
6153
|
|
|
6154 Search through the @file{NEWS} file for @samp{X Resources}. A fairly
|
|
|
6155 comprehensive list is given after it.
|
|
|
6156
|
|
|
6157 In addition, an @file{app-defaults} file @file{etc/Emacs.ad} is
|
|
|
6158 supplied, listing the defaults. The file @file{etc/sample.Xresources}
|
|
|
6159 gives a different set of defaults that you might consider for
|
|
|
6160 installation in your @file{~/.Xresources} file. It is nearly the same
|
|
|
6161 as @file{etc/Emacs.ad}, but a few entries are altered. Be careful about
|
|
|
6162 installing the contents of this file into your @file{.Xresources} (or
|
|
|
6163 legacy @file{.Xdefaults}) file if you use GNU Emacs under X11 as well.
|
|
|
6164
|
|
2459
|
6165 @node Q5.0.2, Q5.0.3, Q5.0.1, External Subsystems
|
|
|
6166 @unnumberedsubsec Q5.0.2: How can I detect a color display?
|
|
2417
|
6167
|
|
|
6168 You can test the return value of the function @code{(device-class)}, as
|
|
|
6169 in:
|
|
|
6170
|
|
|
6171 @lisp
|
|
|
6172 (when (eq (device-class) 'color)
|
|
|
6173 (set-face-foreground 'font-lock-comment-face "Grey")
|
|
|
6174 (set-face-foreground 'font-lock-string-face "Red")
|
|
|
6175 ....
|
|
|
6176 )
|
|
|
6177 @end lisp
|
|
|
6178
|
|
2459
|
6179 @node Q5.0.3, Q5.0.4, Q5.0.2, External Subsystems
|
|
|
6180 @unnumberedsubsec Q5.0.3: How can I get the icon to just say @samp{XEmacs}?
|
|
2417
|
6181
|
|
|
6182 I'd like the icon to just say @samp{XEmacs}, and not include the name of
|
|
|
6183 the current file in it.
|
|
|
6184
|
|
|
6185 Add the following line to your @file{init.el}:
|
|
|
6186
|
|
|
6187 @lisp
|
|
|
6188 (setq frame-icon-title-format "XEmacs")
|
|
|
6189 @end lisp
|
|
|
6190
|
|
2459
|
6191 @node Q5.0.4, Q5.0.5, Q5.0.3, External Subsystems
|
|
|
6192 @unnumberedsubsec Q5.0.4: How can I have the window title area display the full path?
|
|
2417
|
6193
|
|
|
6194 I'd like to have the window title area display the full directory/name
|
|
|
6195 of the current buffer file and not just the name.
|
|
|
6196
|
|
|
6197 Add the following line to your @file{init.el}:
|
|
|
6198
|
|
|
6199 @lisp
|
|
|
6200 (setq frame-title-format "%S: %f")
|
|
|
6201 @end lisp
|
|
|
6202
|
|
|
6203 A more sophisticated title might be:
|
|
|
6204
|
|
|
6205 @lisp
|
|
|
6206 (setq frame-title-format
|
|
|
6207 '("%S: " (buffer-file-name "%f"
|
|
|
6208 (dired-directory dired-directory "%b"))))
|
|
|
6209 @end lisp
|
|
|
6210
|
|
|
6211 That is, use the file name, or the dired-directory, or the buffer name.
|
|
|
6212
|
|
2459
|
6213 @node Q5.0.5, Q5.0.6, Q5.0.4, External Subsystems
|
|
|
6214 @unnumberedsubsec Q5.0.5: @samp{xemacs -name junk} doesn't work?
|
|
2417
|
6215
|
|
|
6216 When I run @samp{xterm -name junk}, I get an xterm whose class name
|
|
|
6217 according to xprop, is @samp{junk}. This is the way it's supposed to
|
|
|
6218 work, I think. When I run @samp{xemacs -name junk} the class name is
|
|
|
6219 not set to @samp{junk}. It's still @samp{emacs}. What does
|
|
|
6220 @samp{xemacs -name} really do? The reason I ask is that my window
|
|
|
6221 manager (fvwm) will make a window sticky and I use XEmacs to read my
|
|
|
6222 mail. I want that XEmacs window to be sticky, without having to use the
|
|
|
6223 window manager's function to set the window sticky. What gives?
|
|
|
6224
|
|
|
6225 @samp{xemacs -name} sets the application name for the program (that is,
|
|
|
6226 the thing which normally comes from @samp{argv[0]}). Using @samp{-name}
|
|
|
6227 is the same as making a copy of the executable with that new name. The
|
|
|
6228 @code{WM_CLASS} property on each frame is set to the frame-name, and the
|
|
|
6229 application-class. So, if you did @samp{xemacs -name FOO} and then
|
|
|
6230 created a frame named @var{BAR}, you'd get an X window with WM_CLASS =
|
|
|
6231 @code{( "BAR", "Emacs")}. However, the resource hierarchy for this
|
|
|
6232 widget would be:
|
|
|
6233
|
|
|
6234 @example
|
|
|
6235 Name: FOO .shell .container .BAR
|
|
|
6236 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
|
|
|
6237 @end example
|
|
|
6238
|
|
|
6239 instead of the default
|
|
|
6240
|
|
|
6241 @example
|
|
|
6242 Name: xemacs.shell .container .emacs
|
|
|
6243 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
|
|
|
6244 @end example
|
|
|
6245
|
|
|
6246
|
|
|
6247 It is arguable that the first element of WM_CLASS should be set to the
|
|
|
6248 application-name instead of the frame-name, but I think that's less
|
|
|
6249 flexible, since it does not give you the ability to have multiple frames
|
|
|
6250 with different WM_CLASS properties. Another possibility would be for
|
|
|
6251 the default frame name to come from the application name instead of
|
|
|
6252 simply being @samp{emacs}. However, at this point, making that change
|
|
|
6253 would be troublesome: it would mean that many users would have to make
|
|
|
6254 yet another change to their resource files (since the default frame name
|
|
|
6255 would suddenly change from @samp{emacs} to @samp{xemacs}, or whatever
|
|
|
6256 the executable happened to be named), so we'd rather avoid it.
|
|
|
6257
|
|
|
6258 To make a frame with a particular name use:
|
|
|
6259
|
|
|
6260 @lisp
|
|
|
6261 (make-frame '((name . "the-name")))
|
|
|
6262 @end lisp
|
|
|
6263
|
|
2459
|
6264 @node Q5.0.6, Q5.1.1, Q5.0.5, External Subsystems
|
|
|
6265 @unnumberedsubsec Q5.0.6: @samp{-iconic} doesn't work.
|
|
2417
|
6266
|
|
|
6267 When I start up XEmacs using @samp{-iconic} it doesn't work right.
|
|
|
6268 Using @samp{-unmapped} on the command line, and setting the
|
|
|
6269 @code{initiallyUnmapped} X Resource don't seem to help much either...
|
|
|
6270
|
|
|
6271 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
|
6272
|
|
|
6273 @quotation
|
|
|
6274 Ugh, this stuff is such an incredible mess that I've about given up
|
|
|
6275 getting it to work. The principal problem is numerous window-manager
|
|
|
6276 bugs...
|
|
|
6277 @end quotation
|
|
|
6278
|
|
2459
|
6279 @unnumberedsec 5.1: Microsoft Windows
|
|
|
6280
|
|
|
6281 @node Q5.1.1, Q5.1.2, Q5.0.6, External Subsystems
|
|
|
6282 @unnumberedsubsec Q5.1.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
|
|
2417
|
6283
|
|
|
6284 In his flavor of Emacs 20, Richard Stallman has renamed all the @samp{win32-*}
|
|
|
6285 symbols to @samp{w32-*}. Does XEmacs do the same?
|
|
|
6286
|
|
|
6287 We consider such a move counter-productive, thus we do not use the
|
|
|
6288 @samp{w32} prefix. (His rather questionable justification was that he
|
|
|
6289 did not consider Windows to be a "winning" platform.) However, the name
|
|
|
6290 @samp{Win32} is not particularly descriptive outside the Windows world,
|
|
|
6291 and using just @samp{windows-} would be too generic. So we chose a
|
|
|
6292 compromise, the prefix @samp{mswindows-} for Windows-related variables
|
|
|
6293 and functions.
|
|
|
6294
|
|
|
6295 Thus all the XEmacs variables and functions directly related to either
|
|
|
6296 the Windows GUI or OS are prefixed @samp{mswindows-} (except for a
|
|
|
6297 couple of debugging variables, prefixed @samp{debug-mswindows-}). From
|
|
|
6298 an architectural perspective, however, we believe that this is mostly a
|
|
|
6299 non-issue because there should be a very small number of
|
|
|
6300 window-systems-specific variables anyway. Whenever possible, we try to
|
|
|
6301 provide generic interfaces that apply to all window systems.
|
|
|
6302
|
|
|
6303 @c not true:
|
|
|
6304 @c The user variables
|
|
|
6305 @c that share functionality with existing NT Emacs variables are be named
|
|
|
6306 @c with our convention, but we provide the GNU Emacs names as
|
|
|
6307 @c compatibility aliases.
|
|
|
6308
|
|
2459
|
6309 @node Q5.1.2, Q5.2.1, Q5.1.1, External Subsystems
|
|
|
6310 @unnumberedsubsec Q5.1.2: How do I get Windows Explorer to associate a file type with XEmacs?
|
|
2417
|
6311
|
|
|
6312 @unnumberedsubsubsec Associating a new file type with XEmacs.
|
|
|
6313
|
|
|
6314 In Explorer select @samp{View->Options->File Types}, press @samp{[New
|
|
|
6315 Type...]} and fill in the dialog box, e.g.:
|
|
|
6316
|
|
|
6317 @example
|
|
|
6318 Description of type: Emacs Lisp source
|
|
|
6319 Associated extension: el
|
|
|
6320 Content Type (MIME): text/plain
|
|
|
6321 @end example
|
|
|
6322
|
|
|
6323 then press @samp{[New...]} and fill in the @samp{Action} dialog box as
|
|
|
6324 follows:
|
|
|
6325
|
|
|
6326 @example
|
|
|
6327 Action:
|
|
|
6328 Open
|
|
|
6329
|
|
|
6330 Application used to perform action:
|
|
|
6331 D:\Full\path\for\xemacs.exe "%1"
|
|
|
6332
|
|
|
6333 [x] Use DDE
|
|
|
6334
|
|
|
6335 DDE Message:
|
|
|
6336 open("%1")
|
|
|
6337
|
|
|
6338 Application:
|
|
|
6339 <leave blank>
|
|
|
6340
|
|
|
6341 DDE Application Not Running:
|
|
|
6342 <leave blank>
|
|
|
6343
|
|
|
6344 Topic:
|
|
|
6345 <leave blank>
|
|
|
6346 @end example
|
|
|
6347
|
|
|
6348 @unnumberedsubsubsec Associating an existing file type with XEmacs.
|
|
|
6349
|
|
|
6350 In Explorer select @samp{View->Options->File Types}. Click on the file
|
|
|
6351 type in the list and press @samp{[Edit...]}. If the file type already
|
|
|
6352 has an @samp{Open} action, double click on it and fill in the
|
|
|
6353 @samp{Action} dialog box as described above; otherwise create a new
|
|
|
6354 action.
|
|
|
6355
|
|
|
6356 If the file type has more than one action listed, you probably want to
|
|
|
6357 make the @samp{Open} action that you just edited the default by clicking on
|
|
|
6358 it and pressing @samp{Set Default}.
|
|
|
6359
|
|
|
6360 Note for Windows 2000 users: Under Windows 2000, get to @samp{File Types}
|
|
|
6361 using @samp{Control Panel->Folder Options->File Types}.
|
|
|
6362
|
|
2459
|
6363 @unnumberedsec 5.2: Printing
|
|
|
6364
|
|
|
6365 @node Q5.2.1, Q5.2.2, Q5.1.2, External Subsystems
|
|
|
6366 @unnumberedsubsec Q5.2.1: What do I need to change to make printing work?
|
|
2417
|
6367
|
|
|
6368 For regular printing there are two variables that can be customized.
|
|
|
6369
|
|
|
6370 @table @code
|
|
|
6371 @item lpr-command
|
|
|
6372 This should be set to a command that takes standard input and sends
|
|
|
6373 it to a printer. Something like:
|
|
|
6374
|
|
|
6375 @lisp
|
|
|
6376 (setq lpr-command "lp")
|
|
|
6377 @end lisp
|
|
|
6378
|
|
|
6379 @item lpr-switches
|
|
|
6380 This should be set to a list that contains whatever the print command
|
|
|
6381 requires to do its job. Something like:
|
|
|
6382
|
|
|
6383 @lisp
|
|
|
6384 (setq lpr-switches '("-depson"))
|
|
|
6385 @end lisp
|
|
|
6386 @end table
|
|
|
6387
|
|
|
6388 For postscript printing there are three analogous variables to
|
|
|
6389 customize.
|
|
|
6390
|
|
|
6391 @table @code
|
|
|
6392 @item ps-lpr-command
|
|
|
6393 This should be set to a command that takes postscript on standard input
|
|
|
6394 and directs it to a postscript printer.
|
|
|
6395
|
|
|
6396 @item ps-lpr-switches
|
|
|
6397 This should be set to a list of switches required for
|
|
|
6398 @code{ps-lpr-command} to do its job.
|
|
|
6399
|
|
|
6400 @item ps-print-color-p
|
|
|
6401 This boolean variable should be set @code{t} if printing will be done in
|
|
|
6402 color, otherwise it should be set to @code{nil}.
|
|
|
6403 @end table
|
|
|
6404
|
|
|
6405 NOTE: It is an undocumented limitation in XEmacs that postscript
|
|
|
6406 printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a
|
|
|
6407 window system environment. It cannot be used outside of X11.
|
|
|
6408
|
|
2459
|
6409 @node Q5.2.2, Q5.2.3, Q5.2.1, External Subsystems
|
|
|
6410 @unnumberedsubsec Q5.2.2: How can I print WYSIWYG a font-locked buffer?
|
|
2417
|
6411
|
|
|
6412 Font-lock looks nice. How can I print (WYSIWYG) the highlighted
|
|
|
6413 document?
|
|
|
6414
|
|
|
6415 The package @code{ps-print}, which is now included with XEmacs, provides
|
|
|
6416 the ability to do this. The source code contains complete instructions
|
|
|
6417 on its use, in
|
|
|
6418 @file{$prefix/lib/xemacs/xemacs-packages/lisp/ps-print/ps-print.el},
|
|
|
6419 being the default location of an installed ps-print package.
|
|
|
6420
|
|
2459
|
6421 @node Q5.2.3, Q5.2.4, Q5.2.2, External Subsystems
|
|
|
6422 @unnumberedsubsec Q5.2.3: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
2417
|
6423
|
|
|
6424 My printer is a Postscript printer and @code{lpr} only works for
|
|
|
6425 Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x
|
|
|
6426 lpr-buffer} to work?
|
|
|
6427
|
|
|
6428 Put something like this in your @file{init.el}:
|
|
428
|
6429
|
|
|
6430 @lisp
|
|
2417
|
6431 (setq lpr-command "a2ps")
|
|
|
6432 (setq lpr-switches '("-p" "-1"))
|
|
|
6433 @end lisp
|
|
|
6434
|
|
|
6435 If you don't use a2ps to convert ASCII to postscript (why not, it's
|
|
|
6436 free?), replace with the command you do use. Note also that some
|
|
|
6437 versions of a2ps require a @samp{-Pprinter} to ensure spooling.
|
|
|
6438
|
|
2459
|
6439 @node Q5.2.4, Q5.3.1, Q5.2.3, External Subsystems
|
|
|
6440 @unnumberedsubsec Q5.2.4: Can you print under MS Windows?
|
|
2417
|
6441
|
|
|
6442 As of 21.4, printing works on Windows, using simply
|
|
|
6443 @samp{File->Print BUFFER...}, and can be configured with
|
|
|
6444 @samp{File->Page Setup...}.
|
|
|
6445
|
|
|
6446 Prior to 21.4, there is no built-in support, but there are some clever
|
|
|
6447 hacks out there. If you know how, please let us know and we'll put it
|
|
|
6448 here.
|
|
|
6449
|
|
2459
|
6450 @unnumberedsec 5.3: Sound
|
|
|
6451
|
|
|
6452 @node Q5.3.1, Q5.3.2, Q5.2.4, External Subsystems
|
|
|
6453 @unnumberedsubsec Q5.3.1: How do I turn off the sound?
|
|
2417
|
6454
|
|
|
6455 Add the following line to your @file{init.el}:
|
|
|
6456
|
|
|
6457 @lisp
|
|
|
6458 (setq bell-volume 0)
|
|
|
6459 (setq sound-alist nil)
|
|
|
6460 @end lisp
|
|
|
6461
|
|
|
6462 That will make your XEmacs totally silent---even the default ding sound
|
|
|
6463 (TTY beep on TTY-s) will be gone.
|
|
|
6464
|
|
|
6465 You can also change these with Customize. Select from the
|
|
|
6466 @code{Options} menu @code{Advanced
|
|
|
6467 (Customize)->Emacs->Environment->Sound->Sound...} or type @kbd{M-x
|
|
|
6468 customize @key{RET} sound @key{RET}}.
|
|
|
6469
|
|
|
6470
|
|
2459
|
6471 @node Q5.3.2, Q5.3.3, Q5.3.1, External Subsystems
|
|
|
6472 @unnumberedsubsec Q5.3.2: How do I get funky sounds instead of a boring beep?
|
|
2417
|
6473
|
|
|
6474 Make sure your XEmacs was compiled with sound support, and then put this
|
|
|
6475 in your @file{init.el}:
|
|
|
6476
|
|
|
6477 @lisp
|
|
|
6478 (load-default-sounds)
|
|
|
6479 @end lisp
|
|
|
6480
|
|
2459
|
6481 @node Q5.3.3, Q5.3.4, Q5.3.2, External Subsystems
|
|
|
6482 @unnumberedsubsec Q5.3.3: What are NAS and ESD (EsounD)?
|
|
|
6483
|
|
|
6484 @dfn{Network Audio System} (NAS) is a client-server sound library for X.
|
|
|
6485
|
|
|
6486 @uref{http://radscan.com/nas.html}.
|
|
|
6487
|
|
3018
|
6488 To build XEmacs with it, use the @file{configure} flag
|
|
|
6489 @samp{--with-sound=nas} (@samp{--enable-sound=nas} in 21.5 or later).
|
|
2459
|
6490
|
|
|
6491 @dfn{Enlightened Sound Daemon} (ESD or EsounD) is yet another sound system.
|
|
|
6492
|
|
|
6493 @uref{http://www.tux.org/~ricdude/EsounD.html}.
|
|
|
6494
|
|
3018
|
6495 To build XEmacs with it, use the @file{configure} flag
|
|
|
6496 @samp{--with-sound=esd} (@samp{--enable-sound=esd} in 21.5 or later).
|
|
|
6497
|
|
|
6498 You can specify support for both with a flag like
|
|
|
6499 @samp{--with-sound=nas,esd} (@samp{--enable-sound=nas,esd} in 21.5 or
|
|
|
6500 later).
|
|
2459
|
6501
|
|
|
6502 @node Q5.3.4, Q5.4.1, Q5.3.3, External Subsystems
|
|
|
6503 @unnumberedsubsec Q5.3.4: Sunsite sounds don't play.
|
|
2417
|
6504
|
|
|
6505 I'm having some trouble with sounds I've downloaded from sunsite. They
|
|
|
6506 play when I run them through @code{showaudio} or cat them directly to
|
|
|
6507 @file{/dev/audio}, but XEmacs refuses to play them.
|
|
|
6508
|
|
|
6509 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
|
|
|
6510
|
|
|
6511 @quotation
|
|
|
6512 [Many of] These files have an (erroneous) 24byte header that tells about
|
|
|
6513 the format that they have been recorded in. If you cat them to
|
|
|
6514 @file{/dev/audio}, the header will be ignored and the default behavior
|
|
|
6515 for /dev/audio will be used. This happens to be 8kHz uLaw. It is
|
|
|
6516 probably possible to fix the header by piping through @code{sox} and
|
|
|
6517 passing explicit parameters for specifying the sampling format; you then
|
|
|
6518 need to perform a 'null' conversion from SunAudio to SunAudio.
|
|
|
6519 @end quotation
|
|
|
6520
|
|
2459
|
6521 @unnumberedsec 5.4: Running an Interior Shell, Invoking Subprocesses
|
|
|
6522
|
|
|
6523 @node Q5.4.1, Q5.4.2, Q5.3.4, External Subsystems
|
|
|
6524 @unnumberedsubsec Q5.4.1: What is an interior shell?
|
|
2417
|
6525
|
|
|
6526 #### Write me.
|
|
|
6527
|
|
2459
|
6528 @node Q5.4.2, Q5.4.3, Q5.4.1, External Subsystems
|
|
|
6529 @unnumberedsubsec Q5.4.2: How do I start up a second shell buffer?
|
|
2417
|
6530
|
|
|
6531 In the @code{*shell*} buffer:
|
|
|
6532
|
|
|
6533 @lisp
|
|
|
6534 M-x rename-buffer @key{RET} *shell-1* @key{RET}
|
|
|
6535 M-x shell RET
|
|
|
6536 @end lisp
|
|
|
6537
|
|
|
6538 This will then start a second shell. The key is that no buffer named
|
|
|
6539 @samp{*shell*} can exist. It might be preferable to use @kbd{M-x
|
|
|
6540 rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x
|
|
|
6541 rename-buffer}.
|
|
|
6542
|
|
|
6543 Alternately, you can set the variable @code{shell-multiple-shells}.
|
|
|
6544 If the value of this variable is non-nil, each time shell mode is invoked,
|
|
|
6545 a new shell is made
|
|
|
6546
|
|
2459
|
6547 @node Q5.4.3, Q5.4.4, Q5.4.2, External Subsystems
|
|
|
6548 @unnumberedsubsec Q5.4.3: Telnet from shell filters too much
|
|
2417
|
6549
|
|
|
6550 I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke
|
|
|
6551 and use a telnet session within it. Everything works fine except that
|
|
|
6552 now all @samp{^M}'s are filtered out by Emacs. Fixes?
|
|
|
6553
|
|
|
6554 Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather
|
|
|
6555 than doing rsh or telnet within the local shell buffer. You can also
|
|
|
6556 use @kbd{M-x ssh} to open secure remote session if you have @code{ssh}
|
|
|
6557 installed.
|
|
|
6558
|
|
2459
|
6559 @node Q5.4.4, Q5.4.5, Q5.4.3, External Subsystems
|
|
|
6560 @unnumberedsubsec Q5.4.4: Strange things are happening in Shell Mode.
|
|
2417
|
6561
|
|
|
6562 Sometimes (i.e. it's not repeatable, and I can't work out why it
|
|
|
6563 happens) when I'm typing into shell mode, I hit return and only a
|
|
|
6564 portion of the command is given to the shell, and a blank prompt is
|
|
|
6565 returned. If I hit return again, the rest of the previous command is
|
|
|
6566 given to the shell.
|
|
|
6567
|
|
|
6568 @email{martin@@xemacs.org, Martin Buchholz} writes:
|
|
|
6569
|
|
|
6570 @quotation
|
|
|
6571 There is a known problem with interaction between @code{csh} and the
|
|
|
6572 @code{filec} option and XEmacs. You should add the following to your
|
|
|
6573 @file{.cshrc}:
|
|
|
6574
|
|
|
6575 @example
|
|
|
6576 if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec
|
|
|
6577 @end example
|
|
|
6578 @end quotation
|
|
|
6579
|
|
2995
|
6580 @node Q5.4.5, Q5.4.6, Q5.4.4, External Subsystems
|
|
2459
|
6581 @unnumberedsubsec Q5.4.5: XEmacs complains "No such file or directory, diff"
|
|
2417
|
6582
|
|
|
6583 or "ispell" or other commands that seem related to whatever you just
|
|
|
6584 tried to do (M-x ediff or M-$, for example).
|
|
|
6585
|
|
|
6586 There are a large number of common (in the sense that "everyone has
|
|
|
6587 these, they really do") Unix utilities that are not provided with
|
|
|
6588 XEmacs. The GNU Project's implementations are available for Windows in
|
|
|
6589 the the Cygwin distribution (@uref{http://www.cygwin.com/}), which also
|
|
|
6590 provides a complete Unix emulation environment (and thus makes ports of
|
|
|
6591 Unix utilities nearly trivial). Another implementation is that from
|
|
|
6592 MinGW (@uref{http://www.mingw.org/msys.shtml}). If you know of others,
|
|
|
6593 please let us know!
|
|
|
6594
|
|
2995
|
6595 @node Q5.4.6, Q5.5.1, Q5.4.5, External Subsystems
|
|
|
6596 @unnumberedsubsec Q5.4.6: Cygwin error "fork_copy: linked dll/bss pass 0 failed"
|
|
|
6597
|
|
|
6598 If you are getting an error like
|
|
|
6599
|
|
|
6600 @example
|
|
|
6601 17797832 [main] bash 3468 fork_copy: linked dll/bss pass 0 failed,
|
|
|
6602 0x675000..0x6756A0, done 0, windows pid 2708, Win 32 error 487
|
|
|
6603 bash: fork: resource temporarily unavailable
|
|
|
6604 @end example
|
|
|
6605
|
|
|
6606 when trying to run bash using @kbd{M-x shell}, then you need to rebase
|
|
|
6607 your Cygwin DLL's. This is a known problem with Cygwin. To fix:
|
|
|
6608
|
|
|
6609 @enumerate
|
|
|
6610 @item
|
|
|
6611 Download the @file{rebase} utility from Cygwin setup (it's under
|
|
|
6612 @samp{System}).
|
|
|
6613 @item
|
|
|
6614 Kill @strong{all} of your Cygwin processes, including all of your
|
|
|
6615 shells and all background processes. Use @code{ps -a} to list all the
|
|
|
6616 processes you need to kill.
|
|
|
6617 @item
|
|
|
6618 From a DOS prompt, run @file{ash} (@strong{not} @file{bash},
|
|
|
6619 @file{tcsh} or @file{zsh}). Do not try to be clever and @code{exec
|
|
|
6620 /bin/ash} from your last shell; it won't work.
|
|
|
6621 @item
|
|
|
6622 Type @code{/bin/rebaseall -v}.
|
|
|
6623 @end enumerate
|
|
|
6624
|
|
|
6625 The problem should now be fixed -- at least, until you install another
|
|
|
6626 Cygwin package with DLL's, in which case you may have to repeat the
|
|
|
6627 procedure.
|
|
|
6628
|
|
2459
|
6629 @unnumberedsec 5.5: Multiple Device Support
|
|
|
6630
|
|
2995
|
6631 @node Q5.5.1, Q5.5.2, Q5.4.6, External Subsystems
|
|
2459
|
6632 @unnumberedsubsec Q5.5.1: How do I open a frame on another screen of my multi-headed display?
|
|
2417
|
6633
|
|
|
6634 Use the command @kbd{M-x make-frame-on-display}. This command is also
|
|
|
6635 on the File menu in the menubar.
|
|
|
6636
|
|
|
6637 The command @code{make-frame-on-tty} also exists, which will establish a
|
|
|
6638 connection to any tty-like device. Opening the TTY devices should be
|
|
|
6639 left to @code{gnuclient}, though.
|
|
|
6640
|
|
2459
|
6641 @node Q5.5.2, Q5.5.3, Q5.5.1, External Subsystems
|
|
|
6642 @unnumberedsubsec Q5.5.2: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
6643
|
|
|
6644 Yes. Use @code{gnuclient -nw}.
|
|
|
6645
|
|
|
6646 Also see @ref{Q5.5.3, How do I disable gnuserv from opening a new frame?}.
|
|
|
6647
|
|
|
6648 @node Q5.5.3, Q5.5.4, Q5.5.2, External Subsystems
|
|
|
6649 @unnumberedsubsec Q5.5.3: How do I disable gnuserv from opening a new frame?
|
|
2417
|
6650
|
|
|
6651 If you set the @code{gnuserv-frame} variable to the frame that should be
|
|
|
6652 used to display buffers that are pulled up, a new frame will not be
|
|
|
6653 created. For example, you could put
|
|
|
6654
|
|
|
6655 @lisp
|
|
|
6656 (setq gnuserv-frame (selected-frame))
|
|
428
|
6657 @end lisp
|
|
|
6658
|
|
2417
|
6659 early on in your @file{init.el}, to ensure that the first frame created
|
|
|
6660 is the one used for your gnuserv buffers.
|
|
|
6661
|
|
|
6662 There is an option to set the gnuserv target to the current frame. See
|
|
|
6663 @code{Options->Display->"Other Window" Location->Make Current Frame Gnuserv Target}
|
|
|
6664
|
|
|
6665 You can also change this with Customize. Select from the
|
|
|
6666 @code{Options} menu @code{Advanced
|
|
|
6667 (Customize)->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type
|
|
|
6668 @kbd{M-x customize @key{RET} gnuserv @key{RET}}.
|
|
|
6669
|
|
|
6670
|
|
2459
|
6671 @node Q5.5.4, Q5.5.5, Q5.5.3, External Subsystems
|
|
|
6672 @unnumberedsubsec Q5.5.4: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
2417
|
6673
|
|
|
6674 Put the following in your @file{init.el} file to start the server:
|
|
|
6675
|
|
|
6676 @lisp
|
|
|
6677 (gnuserv-start)
|
|
|
6678 @end lisp
|
|
|
6679
|
|
|
6680 Start your first XEmacs as usual. After that, you can do:
|
|
|
6681
|
|
|
6682 @example
|
|
|
6683 gnuclient randomfilename
|
|
|
6684 @end example
|
|
|
6685
|
|
|
6686 from the command line to get your existing XEmacs process to open a new
|
|
|
6687 frame and visit randomfilename in that window. When you're done editing
|
|
|
6688 randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the
|
|
|
6689 frame.
|
|
|
6690
|
|
|
6691 See also man page of gnuclient.
|
|
|
6692
|
|
2459
|
6693 @node Q5.5.5, , Q5.5.4, External Subsystems
|
|
|
6694 @unnumberedsubsec Q5.5.5: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
2417
|
6695
|
|
|
6696 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
|
|
|
6697 @quotation
|
|
|
6698 Here is one of the solutions, we have this in a script called
|
|
|
6699 @file{etc/editclient.sh}.
|
|
|
6700 @example
|
|
|
6701 #!/bin/sh
|
|
|
6702 if gnuclient -batch -eval t >/dev/null 2>&1
|
|
|
6703 then
|
|
|
6704 exec gnuclient $@{1+"$@@"@}
|
|
|
6705 else
|
|
|
6706 xemacs -unmapped -f gnuserv-start &
|
|
|
6707 until gnuclient -batch -eval t >/dev/null 2>&1
|
|
|
6708 do
|
|
|
6709 sleep 1
|
|
|
6710 done
|
|
|
6711 exec gnuclient $@{1+"$@@"@}
|
|
|
6712 fi
|
|
|
6713 @end example
|
|
|
6714
|
|
|
6715 Note that there is a known problem when running XEmacs and 'gnuclient
|
|
|
6716 -nw' on the same TTY.
|
|
|
6717 @end quotation
|
|
|
6718
|
|
2459
|
6719 @node Internet, Advanced, External Subsystems, Top
|
|
|
6720 @unnumbered 6 Connecting to the Internet
|
|
|
6721
|
|
|
6722 This is part 6 of the XEmacs Frequently Asked Questions list. This
|
|
|
6723 section is devoted connecting to the Internet.
|
|
|
6724
|
|
|
6725 @menu
|
|
|
6726 6.0: General Mail and News
|
|
|
6727 * Q6.0.1:: What are the various packages for reading mail?
|
|
|
6728 * Q6.0.2:: How can I send mail?
|
|
|
6729 * Q6.0.3:: How do I get my outgoing mail archived?
|
|
|
6730 * Q6.0.4:: How can I read and/or compose MIME messages?
|
|
|
6731 * Q6.0.5:: How do I customize the From line?
|
|
|
6732 * Q6.0.6:: How do I get my MUA to filter mail for me?
|
|
|
6733 * Q6.0.7:: Remote mail reading with an MUA.
|
|
|
6734 * Q6.0.8:: An MUA gets an error incorporating new mail.
|
|
|
6735 * Q6.0.9:: Why isn't @file{movemail} working?
|
|
|
6736 * Q6.0.10:: How do I make my MUA display graphical smilies?
|
|
|
6737 * Q6.0.11:: How can I get those oh-so-neat X-Face lines?
|
|
|
6738
|
|
|
6739 6.1: Reading Mail with VM
|
|
|
6740 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
6741 * Q6.1.2:: How can I get VM to automatically check for new mail?
|
|
|
6742 * Q6.1.3:: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"?
|
|
|
6743 * Q6.1.4:: Is there a mailing list or FAQ for VM?
|
|
|
6744 * Q6.1.5:: How do I make VM stay in a single frame?
|
|
|
6745 * Q6.1.6:: Customization of VM not covered in the manual, or here.
|
|
|
6746
|
|
|
6747 6.2: Reading Netnews and Mail with Gnus
|
|
|
6748 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
6749 * Q6.2.2:: How do I make Gnus stay within a single frame?
|
|
|
6750
|
|
|
6751 6.3: FTP Access
|
|
|
6752 * Q6.3.1:: Can I edit files on other hosts?
|
|
|
6753 * Q6.3.2:: What is EFS?
|
|
|
6754
|
|
|
6755 6.4: Web Browsing with W3
|
|
|
6756 * Q6.4.1:: What is W3?
|
|
|
6757 * Q6.4.2:: How do I run W3 from behind a firewall?
|
|
|
6758 * Q6.4.3:: Is it true that W3 supports style sheets and tables?
|
|
|
6759 @end menu
|
|
|
6760
|
|
|
6761 @unnumberedsec 6.0: General Mail and News
|
|
|
6762
|
|
|
6763 @node Q6.0.1, Q6.0.2, Internet, Internet
|
|
|
6764 @unnumberedsubsec Q6.0.1: What are the various packages for reading mail?
|
|
|
6765
|
|
|
6766 #### Write me.
|
|
|
6767
|
|
|
6768 @node Q6.0.2, Q6.0.3, Q6.0.1, Internet
|
|
|
6769 @unnumberedsubsec Q6.0.2: How can I send mail?
|
|
|
6770
|
|
|
6771 Under Unix and Mac OS X, the @samp{sendmail} package is normally used
|
|
|
6772 for this.
|
|
|
6773 #### Write me.
|
|
|
6774
|
|
|
6775 Under Windows, you need to use @samp{smtpmail}, which communicates
|
|
|
6776 directly with the mail server, as there is no @file{sendmail} program
|
|
|
6777 running. To get it working, use code like the following in your
|
|
|
6778 @file{init.el} file:
|
|
|
6779
|
|
|
6780 @lisp
|
|
|
6781 ;; Get mail working under Windows.
|
|
|
6782 (setq message-send-mail-function 'smtpmail-send-it) ; for message/Gnus
|
|
|
6783 (setq send-mail-function 'smtpmail-send-it) ; for C-x m, etc.
|
|
|
6784 ;; the following ensures that mail problems can be debugged: it logs a trace
|
|
|
6785 ;; of the SMTP conversation to *trace of SMTP session to <somewhere>*.
|
|
|
6786 (setq smtpmail-debug-info t)
|
|
|
6787 ;; Substitute your info here.
|
|
|
6788 ;(setq user-mail-address "ben@@xemacs.org")
|
|
|
6789 ;(setq user-full-name "Ben Wing")
|
|
|
6790 ;(setq smtpmail-default-smtp-server "smtp.myserver.myisp.com")
|
|
|
6791 ;; The following two aren't completely necessary but may help.
|
|
|
6792 ;(setq smtpmail-local-domain "666.com")
|
|
|
6793 ;(setq smtpmail-sendto-domain "666.com")
|
|
|
6794 ;; If your SMTP server requires a username/password to authenticate, as
|
|
|
6795 ;; many do nowadays, set them like this:
|
|
|
6796 ;(setq smtpmail-auth-credentials ; or use ~/.authinfo
|
|
|
6797 ; '(("smtp.myserver.myisp.com" 25 "USER@@SOMEWHERE" "PASSWORD")))
|
|
|
6798
|
|
|
6799 ;; Other possibilities for getting smtpmail to work:
|
|
|
6800 ;;
|
|
|
6801 ;; If for some reason you need to authenticate using the STARTTLS protocol
|
|
|
6802 ;; (don't look into this unless you know what it is), use
|
|
|
6803 ;; (setq smtpmail-starttls-credentials
|
|
|
6804 ;; '(("YOUR SMTP HOST" 25 "~/.my_smtp_tls.key" "~/.my_smtp_tls.cert")))
|
|
|
6805 ;; Requires external program
|
|
|
6806 ;; ftp://ftp.opaopa.org/pub/elisp/starttls-*.tar.gz.
|
|
|
6807 ;; See http://www.ietf.org/rfc/rfc2246.txt,
|
|
|
6808 ;; http://www.ietf.org/rfc/rfc2487.txt
|
|
|
6809 @end lisp
|
|
|
6810
|
|
|
6811 The lines you need to care about are those that set
|
|
|
6812 @code{user-mail-address}, @code{user-full-name},
|
|
|
6813 @code{smtpmail-default-smtp-server}, and
|
|
|
6814 @code{smtpmail-auth-credentials}. You need to set these with,
|
|
|
6815 respectively, your email address, your full name, the SMTP server you
|
|
|
6816 use for outgoing mail, and the username and password you need to log
|
|
|
6817 in to your SMTP server. (If for some reason your SMTP server doesn't
|
|
|
6818 require logging in to send mail, don't uncomment this last line.)
|
|
|
6819
|
|
|
6820 The other settings may be useful in specific cases, but you should know what
|
|
|
6821 you're doing before enabling them.
|
|
|
6822
|
|
|
6823 @node Q6.0.3, Q6.0.4, Q6.0.2, Internet
|
|
|
6824 @unnumberedsubsec Q6.0.3: How do I get my outgoing mail archived?
|
|
|
6825
|
|
|
6826 @lisp
|
|
|
6827 (setq mail-archive-file-name "~/outbox")
|
|
|
6828 @end lisp
|
|
|
6829
|
|
|
6830 @node Q6.0.4, Q6.0.5, Q6.0.3, Internet
|
|
|
6831 @unnumberedsubsec Q6.0.4: How can I read and/or compose MIME messages?
|
|
|
6832
|
|
|
6833 VM, MH-E and GNUS support MIME natively. Other MUAs may or may not
|
|
|
6834 have MIME support; refer to their documentation and other resources,
|
|
|
6835 such as web pages and mailing lists. Packages like SEMI/WEMI may be
|
|
|
6836 useful in connection with MUAs like mew and Wanderlust.
|
|
|
6837
|
|
|
6838 @node Q6.0.5, Q6.0.6, Q6.0.4, Internet
|
|
|
6839 @unnumberedsubsec Q6.0.5: How do I customize the From line?
|
|
|
6840
|
|
|
6841 How do I change the @samp{From:} line? I have set gnus-user-from-line
|
|
|
6842 to
|
|
|
6843 @example
|
|
|
6844 Gail Gurman <gail.gurman@@sybase.com>
|
|
|
6845 @end example
|
|
|
6846 @noindent , but XEmacs Gnus doesn't use
|
|
|
6847 it. [This should apply to all MUA's. --ed] Instead it uses
|
|
|
6848 @example
|
|
|
6849 Gail Mara Gurman @email{gailg@@deall}
|
|
|
6850 @end example
|
|
|
6851 @noindent and then complains
|
|
|
6852 that it's incorrect. Also, as you perhaps can see, my Message-ID is
|
|
|
6853 screwy. How can I change that?
|
|
|
6854
|
|
|
6855 @email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes:
|
|
|
6856
|
|
|
6857 @quotation
|
|
|
6858 Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or
|
|
|
6859 @code{mail-host-address} to @samp{sybase.com}.
|
|
|
6860 @end quotation
|
|
|
6861
|
|
|
6862 @node Q6.0.6, Q6.0.7, Q6.0.5, Internet
|
|
|
6863 @unnumberedsubsec Q6.0.6: How do I get my MUA to filter mail for me?
|
|
|
6864
|
|
|
6865 One possibility is to use procmail to split your mail before it gets to
|
|
|
6866 the MUA. I prefer this personally, since there are many strange and
|
|
|
6867 wonderful things one can do with procmail. Procmail may be found at
|
|
|
6868 @uref{http://www.procmail.org/}.
|
|
|
6869
|
|
|
6870 Also see the Mail Filtering FAQ at:
|
|
|
6871 @iftex
|
|
|
6872 @*
|
|
|
6873 @end iftex
|
|
|
6874 @uref{http://www.faqs.org/faqs/mail/filtering-faq/}.
|
|
|
6875
|
|
|
6876 @node Q6.0.7, Q6.0.8, Q6.0.6, Internet
|
|
|
6877 @unnumberedsubsec Q6.0.7: Remote mail reading with an MUA.
|
|
|
6878
|
|
|
6879 My mailbox lives at the office on a big honkin server. My regular INBOX
|
|
|
6880 lives on my honkin desktop machine. I now can PPP to the office from
|
|
|
6881 home which is far from honking... I'd like to be able to read mail at
|
|
|
6882 home without storing it here and I'd like to use xemacs and the MUA at
|
|
|
6883 home... Is there a recommended setup?
|
|
|
6884
|
|
|
6885 @email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes:
|
|
|
6886
|
|
|
6887 @quotation
|
|
|
6888 There are several ways to do this.
|
|
|
6889
|
|
|
6890 @enumerate
|
|
|
6891 @item
|
|
|
6892 Set your display to your home machine and run dxpc or one of the other X
|
|
|
6893 compressors.
|
|
|
6894
|
|
|
6895 @item
|
|
|
6896 NFS mount your desktop machine on your home machine and modify your pop
|
|
|
6897 command on your home machine to rsh to your desktop machine and actually
|
|
|
6898 do the pop get's.
|
|
|
6899
|
|
|
6900 @item
|
|
|
6901 Run a POP server on your desktop machine as well and do a sort of two
|
|
|
6902 tiered POP get.
|
|
|
6903 @end enumerate
|
|
|
6904 @end quotation
|
|
|
6905
|
|
|
6906 @email{wmperry@@monolith.spry.com, William Perry} adds:
|
|
|
6907
|
|
|
6908 @quotation
|
|
|
6909 Or you could run a pop script periodically on your desktop machine, and
|
|
|
6910 just use ange-ftp or NFS to get to your mailbox. I used to do this all
|
|
|
6911 the time back at IU.
|
|
|
6912 @end quotation
|
|
|
6913
|
|
|
6914 @node Q6.0.8, Q6.0.9, Q6.0.7, Internet
|
|
|
6915 @unnumberedsubsec Q6.0.8: An MUA gets an error incorporating new mail.
|
|
|
6916
|
|
|
6917 rmail and VM, and probably other MUA's as well, get new mail from
|
|
|
6918 your mailbox (called @file{/var/mail/$USER} or @file{/var/spool/mail/$USER}
|
|
|
6919 or something similar) using a program called @code{movemail}.
|
|
|
6920 This program interlocks with @code{/bin/mail} using the protocol
|
|
|
6921 defined by @code{/bin/mail}.
|
|
|
6922
|
|
|
6923 There are various different protocols in general use, which you need to
|
|
3018
|
6924 specify using the @samp{--mail-locking} option
|
|
|
6925 (@samp{--with-mail-locking} in 21.5 or later) to @file{configure}:
|
|
2459
|
6926
|
|
|
6927 @table @samp
|
|
|
6928 @item lockf
|
|
|
6929 POSIX file locking with @code{lockf()}
|
|
|
6930 @item flock
|
|
|
6931 BSD file locking with @code{flock()}
|
|
|
6932 @item dot
|
|
|
6933 To manipulate mail file @file{foo}, first create file @file{foo.lock}
|
|
|
6934 @item locking
|
|
|
6935 Use @code{locking()}, Microsoft's renamed @code{flock()}
|
|
|
6936 @item mmdf
|
|
|
6937 Use @code{lk_open()} and @code{lk_close()} as defined by the Multi-channel
|
|
|
6938 Memo Distribution Facility
|
|
|
6939 @item pop
|
|
|
6940 Retrieve mail using POP (the Post Office Protocol). This is the
|
|
|
6941 default for Cygwin/MinGW.
|
|
|
6942 @end table
|
|
|
6943
|
|
|
6944 @strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
|
|
|
6945 SYSTEM, YOU CAN LOSE MAIL!}
|
|
|
6946
|
|
|
6947 Usually the value is correctly determined automatically:
|
|
|
6948 @file{configure} tries to detect the method in use, and defaults exist
|
|
|
6949 on systems for which this doesn't work.
|
|
|
6950
|
|
|
6951 However, if you run into problems incorporating new mail, it may be
|
|
|
6952 because an incorrect method is being used.
|
|
|
6953
|
|
|
6954 If your system uses the lock file protocol, and permissions are set
|
|
|
6955 so that ordinary users cannot write lock files in the mail spool
|
|
|
6956 directory, you may need to make @file{movemail} setgid to a
|
|
|
6957 suitable group such as @samp{mail}. You can use these commands (as
|
|
|
6958 root):
|
|
|
6959
|
|
|
6960 @example
|
|
|
6961 chgrp mail movemail
|
|
|
6962 chmod 2755 movemail
|
|
|
6963 @end example
|
|
|
6964
|
|
|
6965 If you are using the @samp{pop} locking method, @file{movemail} must
|
|
|
6966 be setuid root.
|
|
|
6967
|
|
|
6968 Installation normally copies movemail from the build directory to an
|
|
|
6969 installation directory which is usually under @file{/usr/local/lib}.
|
|
|
6970 The installed copy of @file{movemail} is usually in the directory
|
|
|
6971 @file{/usr/local/lib/xemacs-VERSION/TARGET} (for example,
|
|
|
6972 @file{/usr/local/lib/xemacs-21.4.15/i686-pc-cygwin}). You must change
|
|
|
6973 the group and mode of the installed copy; changing the group and mode
|
|
|
6974 of the build directory copy is ineffective.
|
|
|
6975
|
|
|
6976 @node Q6.0.9, Q6.0.10, Q6.0.8, Internet
|
|
|
6977 @unnumberedsubsec Q6.0.9: Why isn't @file{movemail} working?
|
|
|
6978
|
|
|
6979 @xref{Q6.0.8}.
|
|
|
6980
|
|
|
6981 Note also that older versions of Mozilla came with a @file{movemail}
|
|
|
6982 program that is @strong{not} compatible with XEmacs. Do not use it.
|
|
|
6983 Always use the @file{movemail} installed with your XEmacs. Failure to
|
|
|
6984 do so can result in lost mail.
|
|
|
6985
|
|
|
6986 @node Q6.0.10, Q6.0.11, Q6.0.9, Internet
|
|
|
6987 @unnumberedsubsec Q6.0.10: How do I make my MUA display graphical smilies?
|
|
|
6988 For mh-e use the following:
|
|
|
6989
|
|
|
6990 @lisp
|
|
|
6991 (add-hook 'mh-show-mode-hook '(lambda ()
|
|
|
6992 (smiley-region (point-min)
|
|
|
6993 (point-max))))
|
|
|
6994 @end lisp
|
|
|
6995
|
|
|
6996 @email{bill@@carpenter.ORG, WJCarpenter} writes:
|
|
|
6997 For VM use the following:
|
|
|
6998 @lisp
|
|
|
6999 (autoload 'smiley-region "smiley" nil t)
|
|
|
7000 (add-hook 'vm-select-message-hook
|
|
|
7001 '(lambda ()
|
|
|
7002 (smiley-region (point-min)
|
|
|
7003 (point-max))))
|
|
|
7004 @end lisp
|
|
|
7005
|
|
|
7006 For tm use the following:
|
|
|
7007 @lisp
|
|
|
7008 (autoload 'smiley-buffer "smiley" nil t)
|
|
|
7009 (add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer)
|
|
|
7010 @end lisp
|
|
|
7011
|
|
|
7012 @node Q6.0.11, Q6.1.1, Q6.0.10, Internet
|
|
|
7013 @unnumberedsubsec Q6.0.11: How can I get those oh-so-neat X-Face lines?
|
|
|
7014
|
|
|
7015 Firstly there is an ftp site which describes X-faces and has the
|
|
|
7016 associated tools mentioned below, at
|
|
|
7017 @uref{http://ftp.cs.indiana.edu/pub/faces/}.
|
|
|
7018
|
|
|
7019 Then the steps are
|
|
|
7020
|
|
|
7021 @enumerate
|
|
|
7022 @item
|
|
|
7023 Create 48x48x1 bitmap with your favorite tool
|
|
|
7024
|
|
|
7025 @item
|
|
|
7026 Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc.,
|
|
|
7027 and then compile the face.
|
|
|
7028
|
|
|
7029 @item
|
|
|
7030 @example
|
|
|
7031 cat file.xbm | xbm2ikon |compface > file.face
|
|
|
7032 @end example
|
|
|
7033
|
|
|
7034 @item
|
|
|
7035 Then be sure to quote things that are necessary for emacs strings:
|
|
|
7036
|
|
|
7037 @example
|
|
|
7038 cat ./file.face | sed 's/\\/\\\\/g'
|
|
|
7039 @iftex
|
|
|
7040 \ @*
|
|
|
7041 @end iftex
|
|
|
7042 | sed 's/\"/\\\"/g' > ./file.face.quoted
|
|
|
7043 @end example
|
|
|
7044
|
|
|
7045 @item
|
|
|
7046 Then set up emacs to include the file as a mail header - there were a
|
|
|
7047 couple of suggestions here---either something like:
|
|
|
7048
|
|
|
7049 @lisp
|
|
|
7050 (setq mail-default-headers
|
|
|
7051 "X-Face: @email{Ugly looking text string here}")
|
|
|
7052 @end lisp
|
|
|
7053
|
|
|
7054 Or, alternatively, as:
|
|
|
7055
|
|
|
7056 @lisp
|
|
|
7057 (defun mail-insert-x-face ()
|
|
|
7058 (save-excursion
|
|
|
7059 (goto-char (point-min))
|
|
|
7060 (search-forward mail-header-separator)
|
|
|
7061 (beginning-of-line)
|
|
|
7062 (insert "X-Face:")
|
|
|
7063 (insert-file-contents "~/.face")))
|
|
|
7064
|
|
|
7065 (add-hook 'mail-setup-hook 'mail-insert-x-face)
|
|
|
7066 @end lisp
|
|
|
7067 @end enumerate
|
|
|
7068
|
|
|
7069 However, 2 things might be wrong:
|
|
|
7070
|
|
|
7071 Some versions of pbmtoicon produces some header lines that is not
|
|
|
7072 expected by the version of compface that I grabbed. So I found I had to
|
|
|
7073 include a @code{tail +3} in the pipeline like this:
|
|
|
7074
|
|
|
7075 @example
|
|
|
7076 cat file.xbm | xbm2ikon | tail +3 |compface > file.face
|
|
|
7077 @end example
|
|
|
7078
|
|
|
7079 Some people have also found that if one uses the @code{(insert-file)}
|
|
|
7080 method, one should NOT quote the face string using the sed script .
|
|
|
7081
|
|
|
7082 It might also be helpful to use @email{stig@@hackvan.com, Stig's} script
|
|
|
7083 xbm2face (included in the compface distribution at XEmacs.org) to do the
|
|
|
7084 conversion.
|
|
|
7085
|
|
|
7086 Contributors for this item:
|
|
|
7087
|
|
|
7088 Paul Emsley,
|
|
|
7089 Ricardo Marek,
|
|
|
7090 Amir J. Katz,
|
|
|
7091 Glen McCort,
|
|
|
7092 Heinz Uphoff,
|
|
|
7093 Peter Arius,
|
|
|
7094 Paul Harrison, and
|
|
|
7095 Vegard Vesterheim
|
|
|
7096
|
|
|
7097 @unnumberedsec 6.1: Reading Mail with VM
|
|
|
7098
|
|
|
7099 @node Q6.1.1, Q6.1.2, Q6.0.11, Internet
|
|
|
7100 @unnumberedsubsec Q6.1.1: How do I set up VM to retrieve mail from a remote site using POP?
|
|
|
7101
|
|
|
7102 Use @code{vm-spool-files}, like this for example:
|
|
|
7103
|
|
|
7104 @lisp
|
|
|
7105 (setq vm-spool-files '("/var/spool/mail/wing"
|
|
|
7106 "netcom23.netcom.com:110:pass:wing:MYPASS"))
|
|
|
7107 @end lisp
|
|
|
7108
|
|
|
7109 Of course substitute your actual password for MYPASS.
|
|
|
7110
|
|
|
7111 @node Q6.1.2, Q6.1.3, Q6.1.1, Internet
|
|
|
7112 @unnumberedsubsec Q6.1.2: How can I get VM to automatically check for new mail?
|
|
|
7113
|
|
|
7114 @email{turner@@lanl.gov, John Turner} writes:
|
|
|
7115
|
|
|
7116 @quotation
|
|
|
7117 Use the following:
|
|
|
7118
|
|
|
7119 @lisp
|
|
|
7120 (setq vm-auto-get-new-mail 60)
|
|
|
7121 @end lisp
|
|
|
7122 @end quotation
|
|
|
7123
|
|
|
7124 @node Q6.1.3, Q6.1.4, Q6.1.2, Internet
|
|
|
7125 @unnumberedsubsec Q6.1.3: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"?
|
|
|
7126
|
|
|
7127 Set @code{vm-reply-ignored-addresses} to a list, like
|
|
|
7128
|
|
|
7129 @lisp
|
|
|
7130 (setq vm-reply-ignored-addresses
|
|
|
7131 '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com"
|
|
|
7132 "wing@@netcom.com" "wing@@xemacs.org"))
|
|
|
7133 @end lisp
|
|
|
7134
|
|
|
7135 Note that each string is a regular expression.
|
|
|
7136
|
|
|
7137 @node Q6.1.4, Q6.1.5, Q6.1.3, Internet
|
|
|
7138 @unnumberedsubsec Q6.1.4: Is there a mailing list or FAQ for VM?
|
|
|
7139
|
|
|
7140 A FAQ for VM exists at @uref{http://www.wonderworks.com/vm/FAQ.html}.
|
|
|
7141
|
|
|
7142 VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug.
|
|
|
7143
|
|
|
7144 @node Q6.1.5, Q6.1.6, Q6.1.4, Internet
|
|
|
7145 @unnumberedsubsec Q6.1.5: How do I make VM stay in a single frame?
|
|
|
7146
|
|
|
7147 John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes:
|
|
|
7148
|
|
|
7149 @quotation
|
|
|
7150 @lisp
|
|
|
7151 ; Don't use multiple frames
|
|
|
7152 (setq vm-frame-per-composition nil)
|
|
|
7153 (setq vm-frame-per-folder nil)
|
|
|
7154 (setq vm-frame-per-edit nil)
|
|
|
7155 (setq vm-frame-per-summary nil)
|
|
|
7156 @end lisp
|
|
|
7157 @end quotation
|
|
|
7158
|
|
|
7159 @node Q6.1.6, Q6.2.1, Q6.1.5, Internet
|
|
|
7160 @unnumberedsubsec Q6.1.6: Customization of VM not covered in the manual, or here.
|
|
|
7161
|
|
4311
|
7162 @email{boffi@@hp735.stru.polimi.it, Giacomo Boffi} writes:
|
|
2459
|
7163
|
|
|
7164 @quotation
|
|
|
7165 The meta-answer is to look into the file @file{vm-vars.el}, in the vm
|
|
|
7166 directory of the lisp library.
|
|
|
7167
|
|
|
7168 @file{vm-vars.el} contains, initializes and carefully describes, with
|
|
|
7169 examples of usage, the plethora of user options that @emph{fully}
|
|
|
7170 control VM's behavior.
|
|
|
7171
|
|
|
7172 Enter vm-vars, @code{forward-search} for toolbar, find the variables
|
|
|
7173 that control the toolbar placement, appearance, existence, copy to your
|
|
|
7174 @file{init.el} or @file{.vm} and modify according to the
|
|
|
7175 detailed instructions.
|
|
|
7176
|
|
|
7177 The above also applies to all the various features of VM: search for
|
|
|
7178 some keywords, maybe the first you conjure isn't appropriate, find the
|
|
|
7179 appropriate variables, copy and experiment.
|
|
|
7180 @end quotation
|
|
|
7181
|
|
|
7182 @unnumberedsec 6.2: Reading Netnews and Mail with Gnus
|
|
|
7183
|
|
|
7184 @node Q6.2.1, Q6.2.2, Q6.1.6, Internet
|
|
|
7185 @unnumberedsubsec Q6.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
|
7186
|
|
|
7187 The Gnus numbering issues are not meant for mere mortals to know them.
|
|
|
7188 If you feel you @emph{must} enter the muddy waters of Gnus, visit the
|
|
|
7189 excellent FAQ, maintained by Justin Sheehy, at:
|
|
|
7190
|
|
|
7191 @example
|
|
|
7192 @uref{http://my.gnus.org/FAQ/}
|
|
|
7193 @end example
|
|
|
7194
|
|
|
7195 See also Gnus home page
|
|
|
7196 @example
|
|
|
7197 @uref{http://www.gnus.org/}
|
|
|
7198 @end example
|
|
|
7199
|
|
|
7200 @node Q6.2.2, Q6.3.1, Q6.2.1, Internet
|
|
|
7201 @unnumberedsubsec Q6.2.2: How do I make Gnus stay within a single frame?
|
|
|
7202
|
|
|
7203 The toolbar code to start Gnus opens the new frame---and it's a feature
|
|
|
7204 rather than a bug. If you don't like it, but would still like to click
|
|
|
7205 on the seemly icon, use the following code:
|
|
|
7206
|
|
|
7207 @lisp
|
|
|
7208 (defun toolbar-news ()
|
|
|
7209 (gnus))
|
|
|
7210 @end lisp
|
|
|
7211
|
|
|
7212 It will redefine the callback function of the icon to just call
|
|
|
7213 @code{gnus}, without all the fancy frame stuff.
|
|
|
7214
|
|
|
7215 @unnumberedsec 6.3: FTP Access
|
|
|
7216
|
|
|
7217 @node Q6.3.1, Q6.3.2, Q6.2.2, Internet
|
|
|
7218 @unnumberedsubsec Q6.3.1: Can I edit files on other hosts?
|
|
|
7219
|
|
|
7220 Yes. Of course XEmacs can use any network file system (such as NFS or
|
|
|
7221 Windows file sharing) you have available, and includes some
|
|
|
7222 optimizations and safety features appropriate to those environments.
|
|
|
7223
|
|
|
7224 It is also possible to transparently edit files via FTP, ssh, or rsh. That
|
|
|
7225 is, XEmacs makes a local copy using the transport in the background, and
|
|
|
7226 automatically refreshes the remote original from that copy when you save
|
|
|
7227 it. XEmacs also is capable of doing file system manipulations like
|
|
|
7228 creating and removing directories and files. The FTP interface is
|
|
|
7229 provided by the standard @samp{efs} package @ref{Top, EFS, , efs}. The
|
|
|
7230 ssh/rsh interface is provided by the optional @samp{tramp} package
|
|
|
7231 @ref{Top, TRAMP, , tramp}.
|
|
|
7232
|
|
|
7233 @node Q6.3.2, Q6.4.1, Q6.3.1, Internet
|
|
|
7234 @unnumberedsubsec Q6.3.2: What is EFS?
|
|
|
7235
|
|
|
7236 #### Write me.
|
|
|
7237
|
|
|
7238 @unnumberedsec 6.4: Web Browsing with W3
|
|
|
7239
|
|
|
7240 @node Q6.4.1, Q6.4.2, Q6.3.2, Internet
|
|
|
7241 @unnumberedsubsec Q6.4.1: What is W3?
|
|
|
7242
|
|
|
7243 W3 is an advanced graphical browser written in Emacs lisp that runs on
|
|
|
7244 XEmacs. It has full support for cascaded style sheets, and more...
|
|
|
7245
|
|
|
7246 It has a home web page at
|
|
|
7247 @uref{http://www.cs.indiana.edu/elisp/w3/docs.html}.
|
|
|
7248
|
|
|
7249 @node Q6.4.2, Q6.4.3, Q6.4.1, Internet
|
|
|
7250 @unnumberedsubsec Q6.4.2: How do I run W3 from behind a firewall?
|
|
|
7251
|
|
|
7252 There is a long, well-written, detailed section in the W3 manual that
|
|
|
7253 describes how to do this. Look in the section entitled "Firewalls".
|
|
|
7254
|
|
|
7255 @node Q6.4.3, , Q6.4.2, Internet
|
|
|
7256 @unnumberedsubsec Q6.4.3: Is it true that W3 supports style sheets and tables?
|
|
|
7257
|
|
|
7258 Yes, and much more. W3, as distributed with the latest XEmacs is a
|
|
|
7259 full-featured web browser.
|
|
|
7260
|
|
|
7261 @node Advanced, Other Packages, Internet, Top
|
|
|
7262 @unnumbered 7 Advanced Customization Using XEmacs Lisp
|
|
|
7263
|
|
|
7264 This is part 7 of the XEmacs Frequently Asked Questions list. This
|
|
|
7265 section is devoted to advanced customization using XEmacs Lisp.
|
|
|
7266
|
|
|
7267 @menu
|
|
2537
|
7268 7.0: Emacs Lisp and @file{init.el}
|
|
|
7269 * Q7.0.1:: What version of Emacs am I running?
|
|
|
7270 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions?
|
|
|
7271 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly.
|
|
|
7272 * Q7.0.4:: How can I add directories to the @code{load-path}?
|
|
|
7273 * Q7.0.5:: How to check if a lisp function is defined?
|
|
|
7274 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer?
|
|
|
7275
|
|
|
7276 7.1: Emacs Lisp Programming Techniques
|
|
|
7277 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
|
7278 * Q7.1.2:: Can I generate "fake" keyboard events?
|
|
|
7279 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail?
|
|
|
7280 * Q7.1.4:: What is the performance hit of @code{let}?
|
|
|
7281 * Q7.1.5:: What is the recommended use of @code{setq}?
|
|
|
7282 * Q7.1.6:: What is the typical misuse of @code{setq}?
|
|
|
7283 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down?
|
|
|
7284 * Q7.1.8:: I like recursion, does it slow things down?
|
|
|
7285 * Q7.1.9:: How do I put a glyph as annotation in a buffer?
|
|
|
7286 * Q7.1.10:: @code{map-extents} won't traverse all of my extents!
|
|
|
7287 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
|
7288
|
|
|
7289 7.2: Mathematics
|
|
|
7290 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp?
|
|
|
7291 * Q7.2.2:: XEmacs segfaults when I use very big numbers!
|
|
|
7292 * Q7.2.3:: Bignums are really slow!
|
|
|
7293 * Q7.2.4:: Equal bignums don't compare as equal! What gives?
|
|
2459
|
7294 @end menu
|
|
|
7295
|
|
2537
|
7296 @unnumberedsec 7.0: Emacs Lisp and @file{init.el}
|
|
2459
|
7297
|
|
|
7298 @node Q7.0.1, Q7.0.2, Advanced, Advanced
|
|
2537
|
7299 @unnumberedsubsec Q7.0.1: What version of Emacs am I running?
|
|
2459
|
7300
|
|
|
7301 How can @file{init.el} determine which of the family of
|
|
|
7302 Emacsen I am using?
|
|
|
7303
|
|
|
7304 To determine if you are currently running GNU Emacs 18, GNU Emacs 19,
|
|
|
7305 XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the
|
|
|
7306 example given in @file{etc/sample.init.el} (@file{etc/sample.emacs} in
|
|
|
7307 XEmacs versions prior to 21.4). There are other nifty things in there
|
|
|
7308 as well!
|
|
|
7309
|
|
|
7310 For all new code, all you really need to do is:
|
|
|
7311
|
|
|
7312 @lisp
|
|
|
7313 (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
|
|
|
7314 @end lisp
|
|
|
7315
|
|
2537
|
7316 @node Q7.0.2, Q7.0.3, Q7.0.1, Advanced
|
|
|
7317 @unnumberedsubsec Q7.0.2: How can I evaluate Emacs-Lisp expressions?
|
|
2459
|
7318
|
|
|
7319 I know I can evaluate Elisp expressions from @code{*scratch*} buffer
|
|
|
7320 with @kbd{C-j} after the expression. How do I do it from another
|
|
|
7321 buffer?
|
|
|
7322
|
|
|
7323 Press @kbd{M-:} (the default binding of @code{eval-expression}), and
|
|
|
7324 enter the expression to the minibuffer.
|
|
|
7325
|
|
2537
|
7326 @node Q7.0.3, Q7.0.4, Q7.0.2, Advanced
|
|
|
7327 @unnumberedsubsec Q7.0.3: @code{(setq tab-width 6)} behaves oddly.
|
|
2459
|
7328
|
|
|
7329 If you put @code{(setq tab-width 6)} in your
|
|
|
7330 @file{init.el} file it does not work! Is there a reason
|
|
|
7331 for this? If you do it at the EVAL prompt it works fine!! How strange.
|
|
|
7332
|
|
|
7333 Use @code{setq-default} instead, since @code{tab-width} is
|
|
|
7334 all-buffer-local.
|
|
|
7335
|
|
2537
|
7336 @node Q7.0.4, Q7.0.5, Q7.0.3, Advanced
|
|
|
7337 @unnumberedsubsec Q7.0.4: How can I add directories to the @code{load-path}?
|
|
2459
|
7338
|
|
|
7339 Here are two ways to do that, one that puts your directories at the
|
|
|
7340 front of the load-path, the other at the end:
|
|
|
7341
|
|
|
7342 @lisp
|
|
|
7343 ;;; Add things at the beginning of the load-path, do not add
|
|
|
7344 ;;; duplicate directories:
|
|
|
7345 (pushnew "bar" load-path :test 'equal)
|
|
|
7346
|
|
|
7347 (pushnew "foo" load-path :test 'equal)
|
|
|
7348
|
|
|
7349 ;;; Add things at the end, unconditionally
|
|
|
7350 (setq load-path (nconc load-path '("foo" "bar")))
|
|
|
7351 @end lisp
|
|
|
7352
|
|
4311
|
7353 @email{keithh@@nortel.ca, Keith (k.p.) Hanlan} writes:
|
|
2459
|
7354
|
|
|
7355 @quotation
|
|
|
7356 To add directories using Unix shell metacharacters use
|
|
|
7357 @file{expand-file-name} like this:
|
|
|
7358
|
|
|
7359 @lisp
|
|
|
7360 (push (expand-file-name "~keithh/.emacsdir") load-path)
|
|
|
7361 @end lisp
|
|
|
7362 @end quotation
|
|
|
7363
|
|
2537
|
7364 @node Q7.0.5, Q7.0.6, Q7.0.4, Advanced
|
|
|
7365 @unnumberedsubsec Q7.0.5: How to check if a lisp function is defined?
|
|
2459
|
7366
|
|
|
7367 Use the following elisp:
|
|
|
7368
|
|
|
7369 @lisp
|
|
|
7370 (fboundp 'foo)
|
|
|
7371 @end lisp
|
|
|
7372
|
|
|
7373 It's almost always a mistake to test @code{emacs-version} or any similar
|
|
|
7374 variables.
|
|
|
7375
|
|
|
7376 Instead, use feature-tests, such as @code{featurep}, @code{boundp},
|
|
|
7377 @code{fboundp}, or even simple behavioral tests, eg.:
|
|
|
7378
|
|
|
7379 @lisp
|
|
|
7380 (defvar foo-old-losing-code-p
|
|
|
7381 (condition-case nil (progn (losing-code t) nil)
|
|
|
7382 (wrong-number-of-arguments t)))
|
|
|
7383 @end lisp
|
|
|
7384
|
|
|
7385 There is an incredible amount of broken code out there which could work
|
|
|
7386 much better more often in more places if it did the above instead of
|
|
|
7387 trying to divine its environment from the value of one variable.
|
|
|
7388
|
|
2537
|
7389 @node Q7.0.6, Q7.1.1, Q7.0.5, Advanced
|
|
|
7390 @unnumberedsubsec Q7.0.6: Can I force the output of @code{(face-list)} to a buffer?
|
|
2459
|
7391
|
|
|
7392 It would be good having it in a buffer, as the output of
|
|
|
7393 @code{(face-list)} is too wide to fit to a minibuffer.
|
|
|
7394
|
|
|
7395 Evaluate the expression in the @samp{*scratch*} buffer with point after
|
|
|
7396 the rightmost paren and typing @kbd{C-j}.
|
|
|
7397
|
|
|
7398 If the minibuffer smallness is the only problem you encounter, you can
|
|
|
7399 simply press @kbd{C-h l} to get the former minibuffer contents in a
|
|
|
7400 buffer.
|
|
|
7401
|
|
2537
|
7402 @unnumberedsec 7.1: Emacs Lisp Programming Techniques
|
|
|
7403
|
|
|
7404 @node Q7.1.1, Q7.1.2, Q7.0.6, Advanced
|
|
|
7405 @unnumberedsubsec Q7.1.1: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
2459
|
7406
|
|
|
7407 @email{clerik@@naggum.no, Erik Naggum} writes;
|
|
|
7408
|
|
|
7409 @quotation
|
|
|
7410 Emacs has a legacy of keyboards that produced characters with modifier
|
|
|
7411 bits, and therefore map a variety of input systems into this scheme even
|
|
|
7412 today. XEmacs is instead optimized for X events. This causes an
|
|
|
7413 incompatibility in the way key sequences are specified, but both Emacs
|
|
|
7414 and XEmacs will accept a key sequence as a vector of lists of modifiers
|
|
|
7415 that ends with a key, e.g., to bind @kbd{M-C-a}, you would say
|
|
|
7416 @code{[(meta control a)]} in both Emacsen. XEmacs has an abbreviated
|
|
|
7417 form for a single key, just (meta control a). Emacs has an abbreviated
|
|
|
7418 form for the Control and the Meta modifiers to string-characters (the
|
|
|
7419 ASCII characters), as in @samp{\M-\C-a}. XEmacs users need to be aware
|
|
|
7420 that the abbreviated form works only for one-character key sequences,
|
|
|
7421 while Emacs users need to be aware that the string-character is rather
|
|
|
7422 limited. Specifically, the string-character can accommodate only 256
|
|
|
7423 different values, 128 of which have the Meta modifier and 128 of which
|
|
|
7424 have not. In each of these blocks, only 32 characters have the Control
|
|
|
7425 modifier. Whereas @code{[(meta control A)]} differs from @code{[(meta
|
|
|
7426 control a)]} because the case differs, @samp{\M-\C-a} and @samp{\M-\C-A}
|
|
|
7427 do not. Programmers are advised to use the full common form, both
|
|
|
7428 because it is more readable and less error-prone, and because it is
|
|
|
7429 supported by both Emacsen.
|
|
|
7430 @end quotation
|
|
|
7431
|
|
|
7432 Another (even safer) way to be sure of the key-sequences is to use the
|
|
|
7433 @code{read-kbd-macro} function, which takes a string like @samp{C-c
|
|
|
7434 <up>}, and converts it to the internal key representation of the Emacs
|
|
|
7435 you use. The function is available both on XEmacs and GNU Emacs.
|
|
|
7436
|
|
2537
|
7437 @node Q7.1.2, Q7.1.3, Q7.1.1, Advanced
|
|
|
7438 @unnumberedsubsec Q7.1.2: Can I generate "fake" keyboard events?
|
|
2459
|
7439
|
|
|
7440 I wonder if there is an interactive function that can generate
|
|
|
7441 @dfn{fake} keyboard events. This way, I could simply map them inside
|
|
|
7442 XEmacs.
|
|
|
7443
|
|
|
7444 This seems to work:
|
|
|
7445
|
|
|
7446 @lisp
|
|
|
7447 (defun cg--generate-char-event (ch)
|
|
|
7448 "Generate an event, as if ch has been typed"
|
|
|
7449 (dispatch-event (character-to-event ch)))
|
|
|
7450
|
|
|
7451 ;; Backspace and Delete stuff
|
|
|
7452 (global-set-key [backspace]
|
|
|
7453 (lambda () (interactive) (cg--generate-char-event 127)))
|
|
|
7454 (global-set-key [unknown_keysym_0x4]
|
|
|
7455 (lambda () (interactive) (cg--generate-char-event 4)))
|
|
|
7456 @end lisp
|
|
|
7457
|
|
2537
|
7458 @node Q7.1.3, Q7.1.4, Q7.1.2, Advanced
|
|
|
7459 @unnumberedsubsec Q7.1.3: Could you explain @code{read-kbd-macro} in more detail?
|
|
2459
|
7460
|
|
|
7461 The @code{read-kbd-macro} function returns the internal Emacs
|
|
|
7462 representation of a human-readable string (which is its argument).
|
|
|
7463 Thus:
|
|
|
7464
|
|
|
7465 @lisp
|
|
|
7466 (read-kbd-macro "C-c C-a")
|
|
|
7467 @result{} [(control ?c) (control ?a)]
|
|
|
7468
|
|
|
7469 (read-kbd-macro "C-c C-. <up>")
|
|
|
7470 @result{} [(control ?c) (control ?.) up]
|
|
|
7471 @end lisp
|
|
|
7472
|
|
|
7473 In GNU Emacs the same forms will be evaluated to what GNU Emacs
|
|
|
7474 understands internally---the sequences @code{"\C-x\C-c"} and @code{[3
|
|
|
7475 67108910 up]}, respectively.
|
|
|
7476
|
|
|
7477 The exact @dfn{human-readable} syntax is defined in the docstring of
|
|
|
7478 @code{edmacro-mode}. I'll repeat it here, for completeness.
|
|
|
7479
|
|
|
7480 @quotation
|
|
|
7481 Format of keyboard macros during editing:
|
|
|
7482
|
|
|
7483 Text is divided into @dfn{words} separated by whitespace. Except for
|
|
|
7484 the words described below, the characters of each word go directly as
|
|
|
7485 characters of the macro. The whitespace that separates words is
|
|
|
7486 ignored. Whitespace in the macro must be written explicitly, as in
|
|
|
7487 @kbd{foo @key{SPC} bar @key{RET}}.
|
|
|
7488
|
|
|
7489 @itemize @bullet
|
|
|
7490 @item
|
|
|
7491 The special words @kbd{RET}, @kbd{SPC}, @kbd{TAB}, @kbd{DEL}, @kbd{LFD},
|
|
|
7492 @kbd{ESC}, and @kbd{NUL} represent special control characters. The
|
|
|
7493 words must be written in uppercase.
|
|
|
7494
|
|
|
7495 @item
|
|
|
7496 A word in angle brackets, e.g., @code{<return>}, @code{<down>}, or
|
|
|
7497 @code{<f1>}, represents a function key. (Note that in the standard
|
|
|
7498 configuration, the function key @code{<return>} and the control key
|
|
|
7499 @key{RET} are synonymous.) You can use angle brackets on the words
|
|
|
7500 @key{RET}, @key{SPC}, etc., but they are not required there.
|
|
|
7501
|
|
|
7502 @item
|
|
|
7503 Keys can be written by their @sc{ascii} code, using a backslash followed
|
|
|
7504 by up to six octal digits. This is the only way to represent keys with
|
|
|
7505 codes above \377.
|
|
|
7506
|
|
|
7507 @item
|
|
|
7508 One or more prefixes @kbd{M-} (meta), @kbd{C-} (control), @kbd{S-}
|
|
|
7509 (shift), @kbd{A-} (alt), @kbd{H-} (hyper), and @kbd{s-} (super) may
|
|
|
7510 precede a character or key notation. For function keys, the prefixes
|
|
|
7511 may go inside or outside of the brackets: @code{C-<down>} @equiv{}
|
|
|
7512 @code{<C-down>}. The prefixes may be written in any order: @kbd{M-C-x}
|
|
|
7513 @equiv{} @kbd{C-M-x}.
|
|
|
7514
|
|
|
7515 Prefixes are not allowed on multi-key words, e.g., @kbd{C-abc}, except
|
|
|
7516 that the Meta prefix is allowed on a sequence of digits and optional
|
|
|
7517 minus sign: @kbd{M--123} @equiv{} @kbd{M-- M-1 M-2 M-3}.
|
|
|
7518
|
|
|
7519 @item
|
|
|
7520 The @code{^} notation for control characters also works: @kbd{^M}
|
|
|
7521 @equiv{} @kbd{C-m}.
|
|
|
7522
|
|
|
7523 @item
|
|
|
7524 Double angle brackets enclose command names: @code{<<next-line>>} is
|
|
|
7525 shorthand for @kbd{M-x next-line @key{RET}}.
|
|
|
7526
|
|
|
7527 @item
|
|
|
7528 Finally, @code{REM} or @code{;;} causes the rest of the line to be
|
|
|
7529 ignored as a comment.
|
|
|
7530 @end itemize
|
|
|
7531
|
|
|
7532 Any word may be prefixed by a multiplier in the form of a decimal number
|
|
|
7533 and @code{*}: @code{3*<right>} @equiv{} @code{<right> <right> <right>},
|
|
|
7534 and @code{10*foo} @equiv{}
|
|
|
7535 @iftex
|
|
|
7536 @*
|
|
|
7537 @end iftex
|
|
|
7538 @code{foofoofoofoofoofoofoofoofoofoo}.
|
|
|
7539
|
|
|
7540 Multiple text keys can normally be strung together to form a word, but
|
|
|
7541 you may need to add whitespace if the word would look like one of the
|
|
|
7542 above notations: @code{; ; ;} is a keyboard macro with three semicolons,
|
|
|
7543 but @code{;;;} is a comment. Likewise, @code{\ 1 2 3} is four keys but
|
|
|
7544 @code{\123} is a single key written in octal, and @code{< right >} is
|
|
|
7545 seven keys but @code{<right>} is a single function key. When in doubt,
|
|
|
7546 use whitespace.
|
|
|
7547 @end quotation
|
|
|
7548
|
|
2537
|
7549 @node Q7.1.4, Q7.1.5, Q7.1.3, Advanced
|
|
|
7550 @unnumberedsubsec Q7.1.4: What is the performance hit of @code{let}?
|
|
2459
|
7551
|
|
|
7552 In most cases, not noticeable. Besides, there's no avoiding
|
|
|
7553 @code{let}---you have to bind your local variables, after all. Some
|
|
|
7554 pose a question whether to nest @code{let}s, or use one @code{let} per
|
|
|
7555 function. I think because of clarity and maintenance (and possible
|
|
|
7556 future implementation), @code{let}-s should be used (nested) in a way to
|
|
|
7557 provide the clearest code.
|
|
|
7558
|
|
2537
|
7559 @node Q7.1.5, Q7.1.6, Q7.1.4, Advanced
|
|
|
7560 @unnumberedsubsec Q7.1.5: What is the recommended use of @code{setq}?
|
|
2459
|
7561
|
|
|
7562 @itemize @bullet
|
|
|
7563 @item Global variables
|
|
|
7564
|
|
|
7565 You will typically @code{defvar} your global variable to a default
|
|
|
7566 value, and use @code{setq} to set it later.
|
|
|
7567
|
|
|
7568 It is never a good practice to @code{setq} user variables (like
|
|
|
7569 @code{case-fold-search}, etc.), as it ignores the user's choice
|
|
|
7570 unconditionally. Note that @code{defvar} doesn't change the value of a
|
|
|
7571 variable if it was bound previously. If you wish to change a
|
|
|
7572 user-variable temporarily, use @code{let}:
|
|
|
7573
|
|
|
7574 @lisp
|
|
|
7575 (let ((case-fold-search nil))
|
|
|
7576 ... ; code with searches that must be case-sensitive
|
|
|
7577 ...)
|
|
|
7578 @end lisp
|
|
|
7579
|
|
|
7580 You will notice the user-variables by their docstrings beginning with an
|
|
|
7581 asterisk (a convention).
|
|
|
7582
|
|
|
7583 @item Local variables
|
|
|
7584
|
|
|
7585 Bind them with @code{let}, which will unbind them (or restore their
|
|
|
7586 previous value, if they were bound) after exiting from the @code{let}
|
|
|
7587 form. Change the value of local variables with @code{setq} or whatever
|
|
|
7588 you like (e.g. @code{incf}, @code{setf} and such). The @code{let} form
|
|
|
7589 can even return one of its local variables.
|
|
|
7590
|
|
|
7591 Typical usage:
|
|
|
7592
|
|
|
7593 @lisp
|
|
|
7594 ;; iterate through the elements of the list returned by
|
|
|
7595 ;; `hairy-function-that-returns-list'
|
|
|
7596 (let ((l (hairy-function-that-returns-list)))
|
|
|
7597 (while l
|
|
|
7598 ... do something with (car l) ...
|
|
|
7599 (setq l (cdr l))))
|
|
|
7600 @end lisp
|
|
|
7601
|
|
|
7602 Another typical usage includes building a value simply to work with it.
|
|
|
7603
|
|
|
7604 @lisp
|
|
|
7605 ;; Build the mode keymap out of the key-translation-alist
|
|
|
7606 (let ((inbox (file-truename (expand-file-name box)))
|
|
|
7607 (i 0))
|
|
|
7608 ... code dealing with inbox ...
|
|
|
7609 inbox)
|
|
|
7610 @end lisp
|
|
|
7611
|
|
|
7612 This piece of code uses the local variable @code{inbox}, which becomes
|
|
|
7613 unbound (or regains old value) after exiting the form. The form also
|
|
|
7614 returns the value of @code{inbox}, which can be reused, for instance:
|
|
|
7615
|
|
|
7616 @lisp
|
|
|
7617 (setq foo-processed-inbox
|
|
|
7618 (let .....))
|
|
|
7619 @end lisp
|
|
|
7620 @end itemize
|
|
|
7621
|
|
2537
|
7622 @node Q7.1.6, Q7.1.7, Q7.1.5, Advanced
|
|
|
7623 @unnumberedsubsec Q7.1.6: What is the typical misuse of @code{setq}?
|
|
2459
|
7624
|
|
|
7625 A typical misuse is probably @code{setq}ing a variable that was meant to
|
|
|
7626 be local. Such a variable will remain bound forever, never to be
|
|
|
7627 garbage-collected. For example, the code doing:
|
|
|
7628
|
|
|
7629 @lisp
|
|
|
7630 (defun my-function (whatever)
|
|
|
7631 (setq a nil)
|
|
|
7632 ... build a large list ...
|
|
|
7633 ... and exit ...)
|
|
|
7634 @end lisp
|
|
|
7635
|
|
|
7636 does a bad thing, as @code{a} will keep consuming memory, never to be
|
|
|
7637 unbound. The correct thing is to do it like this:
|
|
|
7638
|
|
|
7639 @lisp
|
|
|
7640 (defun my-function (whatever)
|
|
|
7641 (let (a) ; default initialization is to nil
|
|
|
7642 ... build a large list ...
|
|
|
7643 ... and exit, unbinding `a' in the process ...)
|
|
|
7644 @end lisp
|
|
|
7645
|
|
|
7646 Not only is this prettier syntactically, but it makes it possible for
|
|
|
7647 Emacs to garbage-collect the objects which @code{a} used to reference.
|
|
|
7648
|
|
|
7649 Note that even global variables should not be @code{setq}ed without
|
|
|
7650 @code{defvar}ing them first, because the byte-compiler issues warnings.
|
|
|
7651 The reason for the warning is the following:
|
|
|
7652
|
|
|
7653 @lisp
|
|
|
7654 (defun flurgoze nil) ; ok, global internal variable
|
|
|
7655 ...
|
|
|
7656
|
|
|
7657 (setq flurghoze t) ; ops! a typo, but semantically correct.
|
|
|
7658 ; however, the byte-compiler warns.
|
|
|
7659
|
|
|
7660 While compiling toplevel forms:
|
|
|
7661 ** assignment to free variable flurghoze
|
|
|
7662 @end lisp
|
|
|
7663
|
|
2537
|
7664 @node Q7.1.7, Q7.1.8, Q7.1.6, Advanced
|
|
|
7665 @unnumberedsubsec Q7.1.7: I like the @code{do} form of cl, does it slow things down?
|
|
2459
|
7666
|
|
|
7667 It shouldn't. Here is what Dave Gillespie has to say about cl.el
|
|
|
7668 performance:
|
|
|
7669
|
|
|
7670 @quotation
|
|
|
7671 Many of the advanced features of this package, such as @code{defun*},
|
|
|
7672 @code{loop}, and @code{setf}, are implemented as Lisp macros. In
|
|
|
7673 byte-compiled code, these complex notations will be expanded into
|
|
|
7674 equivalent Lisp code which is simple and efficient. For example, the
|
|
|
7675 forms
|
|
|
7676
|
|
|
7677 @lisp
|
|
|
7678 (incf i n)
|
|
|
7679 (push x (car p))
|
|
|
7680 @end lisp
|
|
|
7681
|
|
|
7682 are expanded at compile-time to the Lisp forms
|
|
|
7683
|
|
|
7684 @lisp
|
|
|
7685 (setq i (+ i n))
|
|
|
7686 (setcar p (cons x (car p)))
|
|
|
7687 @end lisp
|
|
|
7688
|
|
|
7689 which are the most efficient ways of doing these respective operations
|
|
|
7690 in Lisp. Thus, there is no performance penalty for using the more
|
|
|
7691 readable @code{incf} and @code{push} forms in your compiled code.
|
|
|
7692
|
|
|
7693 @emph{Interpreted} code, on the other hand, must expand these macros
|
|
|
7694 every time they are executed. For this reason it is strongly
|
|
|
7695 recommended that code making heavy use of macros be compiled. (The
|
|
|
7696 features labelled @dfn{Special Form} instead of @dfn{Function} in this
|
|
|
7697 manual are macros.) A loop using @code{incf} a hundred times will
|
|
|
7698 execute considerably faster if compiled, and will also garbage-collect
|
|
|
7699 less because the macro expansion will not have to be generated, used,
|
|
|
7700 and thrown away a hundred times.
|
|
|
7701
|
|
|
7702 You can find out how a macro expands by using the @code{cl-prettyexpand}
|
|
|
7703 function.
|
|
|
7704 @end quotation
|
|
|
7705
|
|
2537
|
7706 @node Q7.1.8, Q7.1.9, Q7.1.7, Advanced
|
|
|
7707 @unnumberedsubsec Q7.1.8: I like recursion, does it slow things down?
|
|
2459
|
7708
|
|
|
7709 Yes. The Emacs byte-compiler cannot do much to optimize recursion. But
|
|
|
7710 think well whether this is a real concern in Emacs. Much of the Emacs
|
|
|
7711 slowness comes from internal mechanisms such as redisplay, or from the
|
|
|
7712 fact that it is an interpreter.
|
|
|
7713
|
|
|
7714 Please try not to make your code much uglier to gain a very small speed
|
|
|
7715 gain. It's not usually worth it.
|
|
|
7716
|
|
2537
|
7717 @node Q7.1.9, Q7.1.10, Q7.1.8, Advanced
|
|
|
7718 @unnumberedsubsec Q7.1.9: How do I put a glyph as annotation in a buffer?
|
|
2459
|
7719
|
|
|
7720 Here is a solution that will insert the glyph annotation at the
|
|
|
7721 beginning of buffer:
|
|
|
7722
|
|
|
7723 @lisp
|
|
|
7724 (make-annotation (make-glyph '([FORMAT :file FILE]
|
|
|
7725 [string :data "fallback-text"]))
|
|
|
7726 (point-min)
|
|
|
7727 'text
|
|
|
7728 (current-buffer))
|
|
|
7729 @end lisp
|
|
|
7730
|
|
|
7731 Replace @samp{FORMAT} with an unquoted symbol representing the format of
|
|
|
7732 the image (e.g. @code{xpm}, @code{xbm}, @code{gif}, @code{jpeg}, etc.)
|
|
|
7733 Instead of @samp{FILE}, use the image file name
|
|
|
7734 (e.g.
|
|
|
7735 @iftex
|
|
|
7736 @*
|
|
|
7737 @end iftex
|
|
|
7738 @file{/usr/local/lib/xemacs-21.4/etc/recycle.xpm}).
|
|
|
7739
|
|
|
7740 You can turn this to a function (that optionally prompts you for a file
|
|
|
7741 name), and inserts the glyph at @code{(point)} instead of
|
|
|
7742 @code{(point-min)}.
|
|
|
7743
|
|
2537
|
7744 @node Q7.1.10, Q7.1.11, Q7.1.9, Advanced
|
|
|
7745 @unnumberedsubsec Q7.1.10: @code{map-extents} won't traverse all of my extents!
|
|
2459
|
7746
|
|
|
7747 I tried to use @code{map-extents} to do an operation on all the extents
|
|
|
7748 in a region. However, it seems to quit after processing a random number
|
|
|
7749 of extents. Is it buggy?
|
|
|
7750
|
|
|
7751 No. The documentation of @code{map-extents} states that it will iterate
|
|
|
7752 across the extents as long as @var{function} returns @code{nil}.
|
|
|
7753 Unexperienced programmers often forget to return @code{nil} explicitly,
|
|
|
7754 which results in buggy code. For instance, the following code is
|
|
|
7755 supposed to delete all the extents in a buffer, and issue as many
|
|
|
7756 @samp{fubar!} messages.
|
|
|
7757
|
|
|
7758 @lisp
|
|
|
7759 (map-extents (lambda (ext ignore)
|
|
|
7760 (delete-extent ext)
|
|
|
7761 (message "fubar!")))
|
|
|
7762 @end lisp
|
|
|
7763
|
|
|
7764 Instead, it will delete only the first extent, and stop right there --
|
|
|
7765 because @code{message} will return a non-nil value. The correct code
|
|
|
7766 is:
|
|
|
7767
|
|
|
7768 @lisp
|
|
|
7769 (map-extents (lambda (ext ignore)
|
|
|
7770 (delete-extent ext)
|
|
|
7771 (message "fubar!")
|
|
|
7772 nil))
|
|
|
7773 @end lisp
|
|
|
7774
|
|
2537
|
7775 @node Q7.1.11, Q7.2.1, Q7.1.10, Advanced
|
|
|
7776 @unnumberedsubsec Q7.1.11: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
2459
|
7777 @c New
|
|
|
7778
|
|
|
7779 @email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
|
|
|
7780 @quotation
|
|
|
7781 Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence},
|
|
|
7782 press a key (say @key{RET} in the Gnus Group buffer), and get the
|
|
|
7783 results using @kbd{M-x profile-results}. It should give you an idea of
|
|
|
7784 where the time is being spent.
|
|
|
7785 @end quotation
|
|
|
7786
|
|
2537
|
7787 @unnumberedsec 7.2: Mathematics
|
|
|
7788
|
|
|
7789 @node Q7.2.1, Q7.2.2, Q7.1.11, Advanced
|
|
|
7790 @unnumberedsubsec Q7.2.1: What are bignums, ratios, and bigfloats in Lisp?
|
|
2459
|
7791
|
|
|
7792 Thanks to @email{james@@xemacs.org, Jerry James}, XEmacs 21.5.18 and
|
|
|
7793 later can use the capabilities of multiple-precision libraries that may
|
|
|
7794 be available for your platform. The GNU Multiple Precision (GMP) and
|
|
|
7795 BSD Multiple Precision (MP) libraries are partially supported. GMP
|
|
|
7796 gives you @dfn{bignums} (arbitrary precision integers), @dfn{ratios}
|
|
|
7797 (arbitrary precision fractions), and @dfn{bigfloats} (arbitrary
|
|
|
7798 precision floating point numbers). GNU MP is better-supported by XEmacs
|
|
|
7799 at the time of writing (2004-04-06). BSD MP support does not include
|
|
|
7800 ratios or bigfloats, and it throws errors that aren't understood.
|
|
|
7801
|
|
|
7802 In most cases, bignum support should be transparent to users and Lisp
|
|
|
7803 programmers. A bignum-enabled XEmacs will automatically convert from
|
|
|
7804 fixnums to bignums and back in pure integer arithmetic, and for GNU MP,
|
|
|
7805 from floats to bigfloats. (Bigfloats must be explicitly coerced to
|
|
|
7806 other types, even if they are exactly representable by less precise
|
|
|
7807 types.) The Lisp reader and printer have been enhanced to handle
|
|
|
7808 bignums, as have the mathematical functions. Rationals (fixnums,
|
|
|
7809 bignums, and ratios) are printed using the @samp{%d}, @samp{%o},
|
|
|
7810 @samp{%x}, and @samp{%u} format conversions. The read syntax for ratios
|
|
|
7811 is @samp{3/5}.
|
|
|
7812
|
|
|
7813 User-visible changes in behavior include (in probable order of annoyance)
|
|
|
7814
|
|
|
7815 @itemize
|
|
|
7816 @item
|
|
|
7817 Arithmetic can cause a segfault, depending on your MP library
|
|
2537
|
7818 @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}.
|
|
2459
|
7819
|
|
|
7820 @item
|
|
|
7821 Terminology is not Common-Lisp-conforming. For example, ``integer'' for
|
|
|
7822 Emacs Lisp means what Common Lisp calls ``fixnum''. This issue is being
|
|
|
7823 investigated, but the use of ``integer'' for fixnum is pervasive and may
|
|
|
7824 cause backward-compatibility and GNU-Emacs-compatibility problems.
|
|
|
7825
|
|
|
7826 @item
|
|
|
7827 Many operations that used to cause a range error now succeed, with
|
|
|
7828 intermediate results and return values coerced to bignums as needed.
|
|
|
7829
|
|
|
7830 @item
|
|
|
7831 An atom with ratio read syntax now returns a number, not a symbol.
|
|
|
7832
|
|
|
7833 @item
|
|
|
7834 The @samp{%u} format conversion will now give an error if its argument
|
|
|
7835 is negative. (Without MP, it prints a number which Lisp can't read.)
|
|
|
7836 @end itemize
|
|
|
7837
|
|
|
7838 @emph{Surgeon General's Warning}: The automatic conversions cannot be
|
|
|
7839 disabled at runtime. New functions have been added which produce
|
|
|
7840 ratios, so there should be few surprises with type conflicts, but they
|
|
|
7841 can't be ruled out. ``Arbitrary'' precision means precisely what it
|
|
|
7842 says. If you work with extremely large numbers, your machine may
|
|
|
7843 arbitrarily decide to hand you an unpleasant surprise rather than a
|
|
2537
|
7844 bignum @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}.
|
|
2459
|
7845
|
|
3018
|
7846 To configure with GNU MP, add @samp{--use-number-lib=gmp}
|
|
|
7847 (@samp{--enable-bignum=gmp} in 21.5 or later) to your invocation of
|
|
|
7848 @file{configure}. For BSD MP, use @samp{--use-number-lib=mp}
|
|
|
7849 (@samp{--enable-bignum=mp} for 21.5).
|
|
2459
|
7850
|
|
|
7851 If you would like to help with bignum support, especially on BSD MP,
|
|
|
7852 please subscribe to the @uref{http://www.xemacs.org/Lists/#xemacs-beta,
|
|
|
7853 XEmacs Beta mailing list}, and book up on @file{number-gmp.h} and
|
|
|
7854 @file{number-mp.h}. Jerry has promised to write internals documentation
|
|
|
7855 eventually, but if your skills run more to analysis and documentation
|
|
|
7856 than to writing new code, feel free to fill in the gap!
|
|
|
7857
|
|
|
7858
|
|
2537
|
7859 @node Q7.2.2, Q7.2.3, Q7.2.1, Advanced
|
|
|
7860 @unnumberedsubsec Q7.2.2: XEmacs segfaults when I use very big numbers!
|
|
2459
|
7861
|
|
|
7862 GMP by default allocates temporaries on the stack. If you run out of
|
|
|
7863 stack space, you're dead; there is no way that we know of to reliably
|
|
|
7864 detect this condition, because @samp{alloca} is typically implemented to
|
|
|
7865 be @emph{fast} rather than robust. If you just need a little more
|
|
|
7866 oomph, use a bigger stack (@emph{e.g.}, the @file{ulimit -s} command in
|
|
|
7867 bash(1)). If you want robustness at the cost of speed, configure GMP
|
|
|
7868 with @samp{--disable-alloca} and rebuild the GMP library.
|
|
|
7869
|
|
|
7870 We do not know whether BSD MP uses @samp{alloca} or not. Please send
|
|
|
7871 any information you have as a bug report (@kbd{M-x report-xemacs-bug
|
|
|
7872 @key{RET}}), which will give us platform information. (We do know that
|
|
|
7873 BSD MP implementations vary across vendors, but how much, we do not know
|
|
|
7874 yet.)
|
|
|
7875
|
|
|
7876
|
|
2537
|
7877 @node Q7.2.3, Q7.2.4, Q7.2.2, Advanced
|
|
|
7878 @unnumberedsubsec Q7.2.3: Bignums are really slow!
|
|
2459
|
7879
|
|
|
7880 Many Linux distributions compile all their packages for the i386, and
|
|
|
7881 this is costly. An optimized version can give you two or three orders
|
|
|
7882 of magnitude better performance for a Pentium III or IV. (Yes, really.
|
|
|
7883 See @uref{http://www.swox.com/gmp/gmp-speed.html}.)
|
|
|
7884
|
|
|
7885
|
|
2537
|
7886 @node Q7.2.4, , Q7.2.3, Advanced
|
|
|
7887 @unnumberedsubsec Q7.2.4: Equal bignums don't compare as equal! What gives?
|
|
2459
|
7888
|
|
|
7889 Ah, Grasshopper, I see you are using @code{(eq x y)}. The Bodhisattva
|
|
|
7890 CLTL2 warned of the illusion that equal numbers would be @samp{eq}!
|
|
|
7891 Meditate on the deeper truths of @samp{eql}, in which numbers of the same
|
|
|
7892 type which have equal values compare equal, and @samp{=}, which does any
|
|
|
7893 necessary type coercions before comparing for equality.
|
|
|
7894
|
|
|
7895 Yeah, yeah, it has always worked for integer types, because fixnums and
|
|
|
7896 characters have an immediate representation. Sorry about that;
|
|
|
7897 arbitrary precision obviously requires consing new objects because the
|
|
|
7898 objects are ``large'' and of variable size, and the definition of
|
|
|
7899 @samp{eq} does not permit different objects to compare as equal.
|
|
|
7900
|
|
|
7901 @node Other Packages, Current Events, Advanced, Top
|
|
|
7902 @unnumbered 8 Other External Packages
|
|
|
7903
|
|
|
7904 This is part 8 of the XEmacs Frequently Asked Questions list. This
|
|
|
7905 section is devoted to miscellaneous external packages not covered
|
|
|
7906 elsewhere in XEmacs.
|
|
|
7907
|
|
|
7908 @menu
|
|
2537
|
7909 8.0: TeX
|
|
2459
|
7910 * Q8.0.1:: Is there something better than LaTeX mode?
|
|
|
7911 * Q8.0.2:: What is AUCTeX? Where do you get it?
|
|
|
7912 * Q8.0.3:: Problems installing AUCTeX.
|
|
|
7913 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline?
|
|
|
7914
|
|
|
7915 8.1: Other Unbundled Packages
|
|
|
7916 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
|
7917 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets?
|
|
|
7918 * Q8.1.3:: Is there a MatLab mode?
|
|
|
7919
|
|
|
7920 8.2: Environments Built Around XEmacs
|
|
|
7921 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop?
|
|
|
7922 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21?
|
|
|
7923 * Q8.2.3:: What is/was Energize?
|
|
|
7924 * Q8.2.4:: What is Infodock?
|
|
|
7925 @end menu
|
|
|
7926
|
|
|
7927 @unnumberedsec 8.0: TeX
|
|
|
7928
|
|
|
7929 @node Q8.0.1, Q8.0.2, Other Packages, Other Packages
|
|
|
7930 @unnumberedsubsec Q8.0.1: Is there something better than LaTeX mode?
|
|
2417
|
7931
|
|
|
7932 @email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes:
|
|
|
7933
|
|
|
7934 @quotation
|
|
|
7935 The standard TeX modes leave much to be desired, and are somewhat
|
|
2459
|
7936 leniently maintained. Serious TeX users use AUCTeX (@pxref{Q8.0.2,
|
|
2417
|
7937 What is AUCTeX? Where do you get it?}).
|
|
|
7938 @end quotation
|
|
|
7939
|
|
2459
|
7940 @node Q8.0.2, Q8.0.3, Q8.0.1, Other Packages
|
|
|
7941 @unnumberedsubsec Q8.0.2: What is AUCTeX? Where do you get it?
|
|
2417
|
7942
|
|
|
7943 AUCTeX is a complex and sophisticated editing package dedicated to TeX
|
|
|
7944 and related text formatting languages, including LaTeX and Texinfo.
|
|
|
7945 It provides support for running TeX on a file or part of a file,
|
|
|
7946 include files, and of course shortcuts for entering common TeX macros,
|
|
|
7947 LaTeX environments, etc, and for fontlock.
|
|
|
7948
|
|
|
7949 AUCTeX is a standard package provided by XEmacs. You can get it as
|
|
|
7950 usual through the @kbd{M-x list-packages} interface. It is also
|
|
|
7951 included in the (non-Mule) SUMO package. The AUCTeX XEmacs package is
|
|
|
7952 maintained by Uwe Brauer <GET MAIL ADDRESS>.
|
|
|
7953
|
|
|
7954 AUCTeX is extremely complicated, and its developers primarily
|
|
|
7955 use GNU Emacs. Not all features of the bleeding edge version
|
|
|
7956 of AUCTeX are immediately ported to XEmacs; if you need
|
|
|
7957 these, you may be better off getting the most recent versions
|
|
|
7958 from the GNU AUCTeX project on @uref{http://savannah.gnu.org}.
|
|
|
7959
|
|
2459
|
7960 @node Q8.0.3, Q8.0.4, Q8.0.2, Other Packages
|
|
|
7961 @unnumberedsubsec Q8.0.3: Problems installing AUCTeX.
|
|
2417
|
7962
|
|
|
7963 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
|
|
|
7964
|
|
|
7965 @quotation
|
|
|
7966 AUCTeX works fine on both stock Emacs and XEmacs has been doing so for
|
|
|
7967 a very very long time. This is mostly due to the work of
|
|
|
7968 @email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu}
|
|
|
7969 package. Which leads to what is probably the problem...
|
|
|
7970 @end quotation
|
|
|
7971
|
|
|
7972 Most problems with AUCTeX are one of two things:
|
|
|
7973
|
|
|
7974 @itemize @bullet
|
|
|
7975 @item
|
|
|
7976 The TeX-lisp-directory in @file{tex-site.el} and the makefile don't
|
|
|
7977 match.
|
|
|
7978
|
|
|
7979 Fix: make sure you configure AUCTeX properly @strong{before} installing.
|
|
|
7980
|
|
|
7981 @item
|
|
|
7982 You have an old version of easymenu.el in your path.
|
|
|
7983
|
|
|
7984 Fix: use @code{locate-library} and remove old versions to make sure it
|
|
|
7985 @strong{only} finds the one that came with XEmacs.
|
|
|
7986 @end itemize
|
|
|
7987
|
|
2459
|
7988 @node Q8.0.4, Q8.1.1, Q8.0.3, Other Packages
|
|
|
7989 @unnumberedsubsec Q8.0.4: How do I turn off current chapter from AUCTeX modeline?
|
|
2417
|
7990
|
|
|
7991 With AUCTeX, fast typing is hard because the current chapter, section
|
|
|
7992 etc. are given in the modeline. How can I turn this off?
|
|
|
7993
|
|
|
7994 It's not AUCTeX, it comes from @code{func-menu} in @file{func-menu.el}.
|
|
|
7995
|
|
|
7996 @c Add this code to your @file{init.el} to turn it off:
|
|
|
7997 @c
|
|
|
7998 @c @lisp
|
|
|
7999 @c (setq fume-display-in-modeline-p nil)
|
|
|
8000 @c @end lisp
|
|
|
8001 @c
|
|
|
8002 @c Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
|
|
|
8003 @c mode:
|
|
|
8004 @c
|
|
|
8005 @c @lisp
|
|
|
8006 @c (add-hook 'TeX-mode-hook
|
|
|
8007 @c '(lambda () (setq fume-display-in-modeline-p nil)))
|
|
|
8008 @c @end lisp
|
|
|
8009 @c
|
|
|
8010 @email{dhughes@@origin-at.co.uk, David Hughes} writes:
|
|
|
8011
|
|
|
8012 @quotation
|
|
|
8013 Try this; you'll still get the function name displayed in the modeline,
|
|
|
8014 but it won't attempt to keep track when you modify the file. To refresh
|
|
|
8015 when it gets out of synch, you simply need click on the @samp{Rescan
|
|
|
8016 Buffer} option in the function-menu.
|
|
|
8017
|
|
|
8018 @lisp
|
|
|
8019 (setq-default fume-auto-rescan-buffer-p nil)
|
|
|
8020 @end lisp
|
|
|
8021 @end quotation
|
|
|
8022
|
|
2459
|
8023 @unnumberedsec 8.1: Other Unbundled Packages
|
|
|
8024
|
|
|
8025 @node Q8.1.1, Q8.1.2, Q8.0.4, Other Packages
|
|
|
8026 @unnumberedsubsec Q8.1.1: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
2417
|
8027
|
|
|
8028 The reason for an Emacs package not to be included in XEmacs is
|
|
|
8029 usually one or more of the following:
|
|
|
8030
|
|
|
8031 @enumerate
|
|
|
8032 @item
|
|
|
8033 The package has not been ported to XEmacs. This will typically happen
|
|
|
8034 when it uses GNU-Emacs-specific features, which make it fail under
|
|
|
8035 XEmacs.
|
|
|
8036
|
|
|
8037 Porting a package to XEmacs can range from a trivial amount of change to
|
|
|
8038 a partial or full rewrite. Fortunately, the authors of modern packages
|
|
|
8039 usually choose to support both Emacsen themselves.
|
|
|
8040
|
|
|
8041 @item
|
|
|
8042 The package has been decided not to be appropriate for XEmacs. It may
|
|
|
8043 have an equivalent or better replacement within XEmacs, in which case
|
|
|
8044 the developers may choose not to burden themselves with supporting an
|
|
|
8045 additional package.
|
|
|
8046
|
|
|
8047 Each package bundled with XEmacs means more work for the maintainers,
|
|
|
8048 whether they want it or not. If you are ready to take over the
|
|
|
8049 maintenance responsibilities for the package you port, be sure to say
|
|
|
8050 so---we will more likely include it.
|
|
|
8051
|
|
|
8052 @item
|
|
|
8053 The package simply hasn't been noted by the XEmacs development. If
|
|
|
8054 that's the case, the messages like yours are very useful for attracting
|
|
|
8055 our attention.
|
|
|
8056
|
|
|
8057 @item
|
|
|
8058 The package was noted by the developers, but they simply haven't yet
|
|
|
8059 gotten around to including/porting it. Wait for the next release or,
|
|
|
8060 even better, offer your help. It will be gladly accepted and
|
|
|
8061 appreciated.
|
|
|
8062 @end enumerate
|
|
|
8063
|
|
2459
|
8064 @node Q8.1.2, Q8.1.3, Q8.1.1, Other Packages
|
|
|
8065 @unnumberedsubsec Q8.1.2: Are there any Emacs Lisp Spreadsheets?
|
|
2417
|
8066
|
|
|
8067 Yes. Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at
|
|
428
|
8068 @iftex
|
|
|
8069 @*
|
|
|
8070 @end iftex
|
|
2459
|
8071 @uref{http://acs.ist.psu.edu/dismal/dismal.html}.
|
|
|
8072
|
|
|
8073 @node Q8.1.3, Q8.2.1, Q8.1.2, Other Packages
|
|
|
8074 @unnumberedsubsec Q8.1.3: Is there a MatLab mode?
|
|
2417
|
8075
|
|
|
8076 Yes, a matlab mode and other items are available at the
|
|
2459
|
8077 @uref{http://www.mathworks.com/matlabcentral/files/104/matlab.el}.
|
|
|
8078
|
|
|
8079 @unnumberedsec 8.2: Environments Built Around XEmacs
|
|
|
8080
|
|
|
8081 @node Q8.2.1, Q8.2.2, Q8.1.3, Other Packages
|
|
|
8082 @unnumberedsubsec Q8.2.1: What are SPARCworks, EOS, and WorkShop?
|
|
2417
|
8083
|
|
|
8084 SPARCworks was a development environment from Sun (circa 1993-1996)
|
|
|
8085 and consisted of compilers (C, C++, FORTRAN 77, Fortran 90, Ada, and
|
|
|
8086 Pascal), a debugger, and other tools such as TeamWare (for
|
|
|
8087 configuration management), MakeTool, etc.
|
|
428
|
8088
|
|
|
8089 EOS is the integration of XEmacs with the SPARCworks debugger. It
|
|
|
8090 allows one to use an XEmacs frame to view code (complete with
|
|
|
8091 fontification, etc.), set breakpoints, print variables, etc., while
|
|
2417
|
8092 using the SPARCworks debugger.
|
|
|
8093
|
|
|
8094 EOS stands for "Era on SPARCworks"; Era stood for "Emacs Rewritten
|
|
|
8095 Again" and was the name used by Sun for its modified version of Lucid
|
|
|
8096 Emacs (later XEmacs) in the early-mid 90's. This is documented in
|
|
|
8097 more detail in the history section of the XEmacs About page.
|
|
|
8098
|
|
|
8099 EOS was replaced around 1996 with a newer graphical development
|
|
|
8100 environment called Sun WorkShop. The current status of this is
|
|
|
8101 unknown.
|
|
|
8102
|
|
2459
|
8103 @node Q8.2.2, Q8.2.3, Q8.2.1, Other Packages
|
|
|
8104 @unnumberedsubsec Q8.2.2: How do I start the Sun Workshop support in XEmacs 21?
|
|
428
|
8105
|
|
|
8106 Add the switch ---with-workshop to the configure command when building
|
|
|
8107 XEmacs and put the following in one of your startup files
|
|
|
8108 (e.g. site-start.el or .emacs):
|
|
|
8109
|
|
|
8110 @lisp
|
|
|
8111 (when (featurep 'tooltalk)
|
|
|
8112 (load "tooltalk-macros")
|
|
|
8113 (load "tooltalk-util")
|
|
|
8114 (load "tooltalk-init"))
|
|
|
8115 (when (featurep 'sparcworks)
|
|
|
8116 (load "sunpro-init")
|
|
|
8117 (load "ring")
|
|
|
8118 (load "comint")
|
|
|
8119 (load "annotations")
|
|
|
8120 (sunpro-startup))
|
|
|
8121 @end lisp
|
|
|
8122
|
|
|
8123 If you are not using the latest Workshop (5.0) you have to apply the
|
|
|
8124 following patch:
|
|
|
8125
|
|
|
8126 @format
|
|
|
8127 --- /opt/SUNWspro/lib/eserve.el.ORIG Fri May 14 15:23:26 1999
|
|
|
8128 +++ /opt/SUNWspro/lib/eserve.el Fri May 14 15:24:54 1999
|
|
|
8129 @@@@ -42,7 +42,7 @@@@
|
|
|
8130 (defvar running-xemacs nil "t if we're running XEmacs")
|
|
|
8131 (defvar running-emacs nil "t if we're running GNU Emacs 19")
|
|
438
|
8132
|
|
428
|
8133 -(if (string-match "^\\(19\\|20\\)\..*\\(XEmacs\\|Lucid\\)" emacs-version)
|
|
|
8134 +(if (string-match "\\(XEmacs\\|Lucid\\)" emacs-version)
|
|
|
8135 (setq running-xemacs t)
|
|
|
8136 (setq running-emacs t))
|
|
438
|
8137 @end format
|
|
428
|
8138
|
|
2459
|
8139 @node Q8.2.3, Q8.2.4, Q8.2.2, Other Packages
|
|
|
8140 @unnumberedsubsec Q8.2.3: What is/was Energize?
|
|
2417
|
8141
|
|
|
8142 The "Energize Programming System" was a C and C++ development environment
|
|
|
8143 sold by Lucid, Inc. It was the reason why Lucid Emacs, now XEmacs, was
|
|
|
8144 created in the first place. Unfortunately, Lucid went out of business in
|
|
|
8145 1994. The rights to sell it in Japan were purchased by INS
|
|
|
8146 Engineering (which briefly employed Stig Hackvan aka Jonathan
|
|
|
8147 Stigelman to work on Japanese support for XEmacs, in late 1994 and
|
|
|
8148 early 1995) and Tartan bought the rights to sell it in the rest of the
|
|
|
8149 world. However, INS is not selling Energize at this point and may or
|
|
|
8150 may not have ever done so; Tartan certainly never did.
|
|
|
8151
|
|
2459
|
8152 @node Q8.2.4, , Q8.2.3, Other Packages
|
|
|
8153 @unnumberedsubsec Q8.2.4: What is Infodock?
|
|
428
|
8154
|
|
660
|
8155 @uref{http://sourceforge.net/projects/infodock/, InfoDock} is an
|
|
|
8156 integrated productivity toolset, mainly aimed at technical people,
|
|
|
8157 hosted at SourceForge.
|
|
428
|
8158
|
|
|
8159 InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of
|
|
|
8160 the power of Emacs, but with an easier to use and more comprehensive
|
|
|
8161 menu-based user interface. The bottom portion of this text describes
|
|
|
8162 how it differs from XEmacs and GNU Emacs from the Free Software
|
|
|
8163 Foundation.
|
|
|
8164
|
|
|
8165 InfoDock is aimed at people who want a free, turn-key productivity
|
|
|
8166 environment. Although InfoDock is customizable, it is not intended for
|
|
|
8167 people who like basic versions of Emacs which need to be customized
|
|
|
8168 extensively for local use; standard Emacs distributions are better for
|
|
|
8169 such uses. InfoDock is for those people who want a complete,
|
|
|
8170 pre-customized environment in one package, which they need not touch
|
|
|
8171 more than once or twice a year to update to new revisions.
|
|
|
8172
|
|
|
8173 InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX,
|
|
|
8174 and Intel Linux systems. It is intended for use on a color display,
|
|
|
8175 although most features will work on monochrome monitors. Simply unpack
|
|
|
8176 InfoDock according to the instructions in the ID-INSTALL file and you
|
|
|
8177 are ready to run.
|
|
|
8178
|
|
|
8179 The InfoDock Manual is concise, yet sufficient as a user guide for users
|
|
|
8180 who have never used an Emacs-type editor before. For users who are
|
|
|
8181 already familiar with Emacs, it supplements the information in the GNU
|
|
|
8182 Emacs Manual.
|
|
|
8183
|
|
|
8184 InfoDock menus are much more extensive and more mature than standard
|
|
|
8185 Emacs menus. Each menu offers a @samp{Manual} item which displays
|
|
|
8186 documentation associated with the menu's functions.
|
|
|
8187
|
|
|
8188 @noindent
|
|
|
8189 Four types of menubars are provided:
|
|
|
8190 @enumerate
|
|
|
8191 @item
|
|
|
8192 An extensive menubar providing access to global InfoDock commands.
|
|
|
8193 @item
|
|
|
8194 Mode-specific menubars tailored to the current major mode.
|
|
|
8195 @item
|
|
|
8196 A simple menubar for basic editing to help novices get started with InfoDock.
|
|
|
8197 @item
|
|
|
8198 The standard XEmacs menubar.
|
|
|
8199 @end enumerate
|
|
|
8200
|
|
|
8201 Most modes also include mode-specific popup menus. Additionally, region and
|
|
|
8202 rectangle popup menus are included.
|
|
|
8203
|
|
|
8204 @samp{Hyperbole}, the everyday information manager, is a core part of
|
|
|
8205 InfoDock. This provides context-sensitive mouse keys, a rolodex-type
|
|
|
8206 contact manager, programmable hypertext buttons, and an autonumbered
|
|
|
8207 outliner with embedded hyperlink anchors.
|
|
|
8208
|
|
|
8209 The @samp{OO-Browser}, a multi-language object-oriented code browser, is a
|
|
|
8210 standard part of InfoDock.
|
|
|
8211
|
|
|
8212 InfoDock saves a more extensive set of user options than other Emacs
|
|
|
8213 versions.
|
|
|
8214
|
|
|
8215 InfoDock inserts a useful file header in many file types, showing the
|
|
|
8216 author, summary, and last modification time of each file. A summary
|
|
|
8217 program can then be used to summarize all of the files in a directory,
|
|
|
8218 for easy MANIFEST file creation.
|
|
|
8219
|
|
|
8220 Your working set of buffers is automatically saved and restored (if you
|
|
|
8221 answer yes to a prompt) between InfoDock sessions.
|
|
|
8222
|
|
|
8223 Refined color choices for code highlighting are provided for both dark and
|
|
|
8224 light background display frames.
|
|
|
8225
|
|
|
8226 The @kbd{C-z} key prefix performs frame-based commands which parallel the
|
|
|
8227 @kbd{C-x} key prefix for window-based commands.
|
|
|
8228
|
|
|
8229 The Smart Menu system is included for producing command menus on dumb
|
|
|
8230 terminals.
|
|
|
8231
|
|
|
8232 Lisp libraries are better categorized according to function.
|
|
|
8233
|
|
|
8234 Extensions and improvements to many areas of Emacs are included, such as:
|
|
|
8235 paragraph filling, mail reading with Rmail, shell handling, outlining, code
|
|
|
8236 highlighting and browsing, and man page browsing.
|
|
|
8237
|
|
|
8238 InfoDock questions, answers and discussion should go to the mail list
|
|
|
8239 @iftex
|
|
|
8240 @*
|
|
|
8241 @end iftex
|
|
|
8242 @email{infodock@@infodock.com}. Use
|
|
|
8243 @email{infodock-request@@infodock.com} to be added or removed from the
|
|
|
8244 list. Always include your InfoDock version number when sending help
|
|
|
8245 requests.
|
|
|
8246
|
|
2459
|
8247 @node Current Events, Legacy Versions, Other Packages, Top
|
|
|
8248 @unnumbered 9 What the Future Holds
|
|
|
8249
|
|
|
8250 This is part 9 of the XEmacs Frequently Asked Questions list. This
|
|
611
|
8251 section will change frequently, and (in theory) should contain any
|
|
|
8252 interesting items that have transpired recently. (But in practice it's
|
|
|
8253 not getting updated like this.)
|
|
|
8254
|
|
|
8255 This section also contains descriptions of the new features in all the
|
|
|
8256 recent releases of XEmacs. For the most part, the information below is
|
|
|
8257 a synopsis of the more complete information that can be found in the
|
|
|
8258 file @file{NEWS} in the @file{etc} directory of the XEmacs distribution.
|
|
|
8259 You can view this file in XEmacs using @kbd{C-h n} or the @samp{Help}
|
|
|
8260 menu.
|
|
|
8261
|
|
|
8262 Information on older versions of XEmacs can be find in @file{ONEWS} in
|
|
|
8263 the same directory, or @file{OONEWS} for really old versions.
|
|
|
8264
|
|
428
|
8265 @menu
|
|
2537
|
8266 9.0: Changes
|
|
2459
|
8267 * Q9.0.1:: What new features will be in XEmacs soon?
|
|
|
8268 * Q9.0.2:: What's new in XEmacs 21.4?
|
|
|
8269 * Q9.0.3:: What's new in XEmacs 21.1?
|
|
|
8270 * Q9.0.4:: What's new in XEmacs 20.4?
|
|
|
8271 * Q9.0.5:: What's new in XEmacs 20.3?
|
|
|
8272 * Q9.0.6:: What's new in XEmacs 20.2?
|
|
428
|
8273 @end menu
|
|
|
8274
|
|
2459
|
8275 @unnumberedsec 9.0: Changes
|
|
|
8276
|
|
|
8277 @node Q9.0.1, Q9.0.2, Current Events, Current Events
|
|
|
8278 @unnumberedsubsec Q9.0.1: What new features will be in XEmacs soon?
|
|
611
|
8279
|
|
2417
|
8280 #### Write me.
|
|
428
|
8281
|
|
2459
|
8282 @node Q9.0.2, Q9.0.3, Q9.0.1, Current Events
|
|
|
8283 @unnumberedsubsec Q9.0.2: What's new in XEmacs 21.4?
|
|
611
|
8284
|
|
|
8285 21.4 was the "stable" version of the 21.2 series, which was considered
|
|
|
8286 "experimental" throughout its life; thus there were no "official"
|
|
|
8287 releases at all. In essence, XEmacs is now following the "alternating"
|
|
|
8288 scheme of Linux, where at any point there are at least two different
|
|
|
8289 development branches, one "stable" and one "experimental". Periodic
|
|
|
8290 releases happen in both branches, but those in the experimental branch
|
|
|
8291 are not tested as well, and there's no guarantee they will work at all.
|
|
4311
|
8292 The experimental branch is open to any and all code that's acceptable
|
|
611
|
8293 to the developers; the stable branch, however, is in general limited
|
|
|
8294 only to bug fixes, and all contributions are carefully reviewed to make
|
|
|
8295 sure they will increase and not decrease stability.
|
|
|
8296
|
|
|
8297 21.3 never existed at all; it was decided to follow the Linux scheme
|
|
|
8298 exactly, where odd-numbered series are experimental and even-numbered
|
|
|
8299 ones stable.
|
|
|
8300
|
|
|
8301 The following lists summarizes the essential changes made in this
|
|
|
8302 version. For a fuller list, see the @file{NEWS} in the @file{etc}
|
|
|
8303 directory of the XEmacs distribution, or use @kbd{C-h n} or the
|
|
|
8304 @samp{Help} menu to view this file inside of XEmacs.
|
|
|
8305
|
|
676
|
8306 @unnumberedsubsubsec User-visible changes in XEmacs 21.4
|
|
611
|
8307
|
|
|
8308 @itemize @bullet
|
|
|
8309
|
|
|
8310 @item
|
|
|
8311 The delete key now deletes forward by default.
|
|
|
8312 @item
|
|
|
8313 Shifted motion keys now select text by default.
|
|
|
8314 @item
|
|
|
8315 You can now build XEmacs with support for GTK+ widget set.
|
|
|
8316 @item
|
|
|
8317 ~/.xemacs/init.el is now the preferred location for the init
|
|
|
8318 file. (XEmacs now supports a `~/.xemacs/init.el' startup file. Custom
|
|
|
8319 file will move to ~/.xemacs/custom.el.)
|
|
|
8320 @item
|
|
|
8321 Much-improved sample init.el, showing how to use many useful features.
|
|
|
8322 @item
|
|
|
8323 XEmacs support for menu accelerators has been much improved.
|
|
|
8324 @item
|
|
|
8325 Default menubar improvements. (Default menubar has many new commands and
|
|
|
8326 better organization. The font-menu is now available under MS Windows.)
|
|
|
8327 @item
|
|
2417
|
8328 Dialog box improvements, including a real file dialog box. (XEmacs now
|
|
|
8329 has a proper file dialog box under MS Windows (and GTK)! The old
|
|
|
8330 clunky file dialog box is improved. Keyboard traversal now works
|
|
|
8331 correctly in MS Windows dialog boxes. There is a Search dialog box
|
|
|
8332 available from @samp{Edit->Find...})
|
|
611
|
8333 @item
|
|
|
8334 New buffer tabs.
|
|
|
8335 @item
|
|
|
8336 There is a new MS Windows installer, netinstall, ported from Cygwin.
|
|
|
8337 @item
|
|
|
8338 The subprocess quote-handling mechanism under Windows is much improved.
|
|
|
8339 @item
|
|
|
8340 Printing support now available under MS Windows.
|
|
|
8341 @item
|
|
|
8342 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).)
|
|
|
8343 @item
|
|
|
8344 Mail spool locking now works correctly.
|
|
|
8345 @item
|
|
|
8346 International support changes. (The default coding-priority-list is now
|
|
|
8347 safer. International keysyms are now supported under X. MS Windows
|
|
|
8348 1251 code page now supported. Czech, Thai, Cyrillic-KOI8, Vietnamese,
|
|
|
8349 Ethiopic now supported. Proper support for words in Latin 3 and Latin
|
|
|
8350 4.)
|
|
|
8351 @item
|
|
|
8352 Help buffers contain hyperlinks, and other changes.
|
|
|
8353 @item
|
|
|
8354 The modeline's text is now scrollable.
|
|
|
8355 @item
|
|
|
8356 The mouse wheel under MS Windows now functions correctly.
|
|
|
8357 @item
|
|
|
8358 Interactive searching and matching case improvements. (Incremental search will now highlight all visible matches. Interactive searches always respect uppercase characters.)
|
|
|
8359 @item
|
|
|
8360 Rectangle functions rewritten to avoid inserting extra spaces.
|
|
|
8361 @item
|
|
|
8362 New command `kill-entire-line' that always kills the entire line.
|
|
|
8363 @item
|
|
|
8364 Default values correctly stored in minibuffer histories.
|
|
|
8365 @item
|
|
|
8366 You can now create "indirect buffers", like in GNU Emacs.
|
|
|
8367 @item
|
|
|
8368 Pixel-based scrolling has been implemented.
|
|
|
8369 @item
|
|
|
8370 Operation progress can be displayed using graphical widgets.
|
|
|
8371 @item
|
|
|
8372 User names following a tilde can now be completed at file name prompts.
|
|
|
8373 @item
|
|
|
8374 XEmacs can now play sound using Enlightenment Sound Daemon (ESD).
|
|
|
8375 @item
|
|
|
8376 X-Face support is now available under MS Windows.
|
|
|
8377 @item
|
|
|
8378 The PostgreSQL Relational Database Management System is now supported.
|
|
|
8379 @item
|
|
|
8380 Indentation no longer indents comments that begin at column zero.
|
|
|
8381 @item
|
|
|
8382 Face and variable settings can have comments in Customize.
|
|
|
8383 @item
|
|
|
8384 New locations for early package hierarchies.
|
|
|
8385 @item
|
|
|
8386 The `auto-save' library has been greatly improved.
|
|
|
8387 @item
|
|
|
8388 New variable `mswindows-alt-by-itself-activates-menu'.
|
|
|
8389 @item
|
|
|
8390 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.)
|
|
|
8391 @item
|
|
|
8392 Etags changes. See @file{NEWS} for full details.
|
|
|
8393 @end itemize
|
|
|
8394
|
|
676
|
8395 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.4
|
|
611
|
8396
|
|
|
8397 Not yet written.
|
|
|
8398
|
|
661
|
8399 @c APA: Texi2html produces invalid HTML from an empty list of bullets!
|
|
|
8400 @c Please uncomment following list when it does contain bullets.
|
|
|
8401 @c @itemize @bullet
|
|
|
8402 @c @end itemize
|
|
611
|
8403
|
|
2459
|
8404 @node Q9.0.3, Q9.0.4, Q9.0.2, Current Events
|
|
|
8405 @unnumberedsubsec Q9.0.3: What's new in XEmacs 21.1?
|
|
611
|
8406
|
|
|
8407 21.1 was the "stable" version of "experimental" 21.0 series.
|
|
2459
|
8408 @xref{Q9.0.2, What's new in XEmacs 21.4?}.
|
|
611
|
8409
|
|
|
8410 The following lists summarizes the essential changes made in this
|
|
|
8411 version. For a fuller list, see the @file{NEWS} in the @file{etc}
|
|
|
8412 directory of the XEmacs distribution, or use @kbd{C-h n} or the
|
|
|
8413 @samp{Help} menu to view this file inside of XEmacs.
|
|
|
8414
|
|
676
|
8415 @unnumberedsubsubsec User-visible changes in XEmacs 21.1
|
|
611
|
8416
|
|
|
8417 @itemize @bullet
|
|
|
8418
|
|
|
8419 @item
|
|
2459
|
8420 XEmacs is now supported under Microsoft Windows 95/98 and Windows
|
|
2417
|
8421 NT/2000/XP operating systems. To discuss Windows-specific issues,
|
|
|
8422 subscribe to the mailing list at
|
|
|
8423 @email{xemacs-winnt-request@@xemacs.org}.
|
|
611
|
8424
|
|
|
8425 @item
|
|
|
8426 XEmacs has been unbundled into constituent installable packages.
|
|
|
8427
|
|
|
8428 @item
|
|
|
8429 @strong{Other notable changes}: The @samp{Options} menu has been ported to
|
|
|
8430 Custom; XEmacs now is able to choose X visuals and use private
|
|
|
8431 colormaps; You can drag the vertical divider of "horizontally"
|
|
|
8432 (side-by-side) split windows.
|
|
|
8433
|
|
|
8434 @item
|
|
|
8435 @strong{Building changes}: XEmacs can be built with support for 31-bit Lisp
|
|
|
8436 integers and 32-bit pointers (previously, it was 28-bit integers and
|
|
|
8437 pointers); XEmacs can be built with LDAP support; @file{dir} files can be
|
|
|
8438 removed in the Info subsystem, and will be regenerated on-the-fly.
|
|
|
8439
|
|
|
8440 @item
|
|
|
8441 @strong{New packages}: @file{imenu}, @file{popper}, @file{gdb-highlight}
|
|
|
8442
|
|
|
8443 @item
|
|
|
8444 @strong{Package changes}: Many changes to @file{cc-mode}, @file{gnus},
|
|
|
8445 @file{gnuclient}. See @file{NEWS} for full details.
|
|
|
8446
|
|
|
8447 @item
|
|
|
8448 @strong{New commands, variables and functions}:
|
|
|
8449 @code{center-to-window-line} (like @code{recenter} but doesn't force a
|
|
|
8450 redisplay); variable @code{user-full-name} (customize what your full
|
|
|
8451 name looks like in mail); @kbd{M-x customize-changed-options} (customize
|
|
|
8452 options whose default values changes because you upgraded your XEmacs);
|
|
|
8453 @kbd{M-x add-log-convert} (converts an old-style ChangeLog buffer to
|
|
|
8454 new-style); @kbd{M-x zap-up-to-char} (like @code{zap-to-char} but
|
|
|
8455 doesn't delete the char searched for); commands to store, retrieve and
|
|
|
8456 increment numbers in registers, useful for macros.
|
|
|
8457
|
|
|
8458 @item
|
|
|
8459 @strong{Changes to commands, variables, and functions}: @kbd{M-x
|
|
|
8460 query-replace} and friends operate only on the region when it's active;
|
|
|
8461 @code{echo-keystrokes} can now be a floating-point number; @kbd{M-.}
|
|
|
8462 searches exact tag matches before inexact ones; function
|
|
|
8463 @code{user-full-name} with no arguments returns the var
|
|
|
8464 @code{user-full-name}; a prefix arg to @kbd{M-:} and @kbd{C-h c} inserts
|
|
|
8465 the result in the current buffer.
|
|
1138
|
8466
|
|
611
|
8467 @item
|
|
|
8468 @strong{Other changes}: Under X, new application class @samp{XEmacs};
|
|
|
8469 byte-compilation of user-specs now works.
|
|
|
8470
|
|
|
8471 @item
|
|
|
8472 @strong{XEmacs/Mule (internationalization) changes}: Mule support now
|
|
|
8473 works on TTY's; Egg/SJ3 input method now officially supported (Quail and
|
|
|
8474 Egg/Skk already available through LEIM since 20.3); localized Japanese
|
|
|
8475 menubars if XEmacs is built with the right support.
|
|
|
8476
|
|
|
8477 @end itemize
|
|
|
8478
|
|
676
|
8479 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.1
|
|
611
|
8480
|
|
|
8481 @itemize @bullet
|
|
|
8482
|
|
|
8483 @item
|
|
|
8484 @strong{Specifier changes}: The window locale now has a higher
|
|
|
8485 precedence than the buffer locale when instantiating; new macro
|
|
|
8486 @code{let-specifier}; new specifiers
|
|
|
8487 @code{vertical-scrollbar-visible-p}, horizontal-scrollbar-visible-p',
|
|
|
8488 @code{scrollbar-on-left-p}, @code{scrollbar-on-top-p},
|
|
|
8489 @code{vertical-divider-always-visible-p},
|
|
|
8490 @code{vertical-divider-shadow-thickness},
|
|
|
8491 @code{vertical-divider-line-width}, @code{vertical-divider-spacing};
|
|
|
8492 specifiers and symbols whose value is a specifier allowed as modeline
|
|
|
8493 specifications.
|
|
|
8494
|
|
|
8495 @item
|
|
|
8496 @strong{Frame focus changes}: @code{focus-follows-mouse} works like FSF,
|
|
|
8497 prevents any attempt to permanently change the selected frame; new
|
|
|
8498 function @code{focus-frame} sets the window system focus a frame; new
|
|
|
8499 special forms @code{save-selected-frame} and @code{with-selected-frame}.
|
|
|
8500
|
|
|
8501 @item
|
|
|
8502 @strong{Window function changes}: @code{select-window} now has optional
|
|
|
8503 argument @var{NORECORD} to inhibit recording a buffer change;
|
|
|
8504 @code{vertical-motion} now correctly handles optional @var{WINDOW}
|
|
|
8505 argument and has new optional argument @var{PIXELS}, to have the
|
|
|
8506 returned values be in pixels; new function
|
|
|
8507 @code{vertical-motion-pixels}; new functions
|
|
|
8508 @code{window-text-area-pixel-@{width,height,edges@}}; new functions
|
|
|
8509 @code{shrink-window-pixels} and @code{enlarge-window-pixels}; new
|
|
|
8510 function @code{window-displayed-text-pixel-height}.
|
|
|
8511
|
|
|
8512 @item
|
|
|
8513 @strong{Other function changes}: Arithmetic comparison functions
|
|
|
8514 @code{<}, @code{>}, @code{=}, @code{/=} now accept a variable number of
|
|
|
8515 arguments; hashtables now have a consistent read/print syntax; keyword
|
|
|
8516 symbols cannot be set to a value other than themselves; @code{concat} no
|
|
|
8517 longer accepts integer arguments; new function @code{string}, like
|
|
|
8518 @code{list}, @code{vector}, etc.; new function @code{temp-directory}
|
|
|
8519 (OS-independent way to get a temp directory); @code{load-average} has
|
|
|
8520 optional argument @var{USE-FLOATS}; @code{make-event} implemented
|
|
|
8521 completely; new function @code{function-interactive} (returns a
|
|
|
8522 function's interactive spec); new functions @code{lmessage},
|
|
|
8523 @code{lwarn} (printf-like versions of @code{display-wessage},
|
|
|
8524 @code{display-warning}); new keyword @code{:version} to
|
|
|
8525 @code{defcustom}.
|
|
|
8526
|
|
|
8527 @item
|
|
|
8528 @strong{Performance}: when the new GNU Malloc aka Doug Lea Malloc is
|
|
|
8529 available, it will be used (better performance on libc6 Linux systems);
|
|
|
8530 tracking line-numbers in modeline is now efficient; profiling records a
|
|
|
8531 call-count of all called functions, retrievable through
|
|
|
8532 @code{profile-call-count-results}.
|
|
|
8533
|
|
|
8534 @item
|
|
|
8535 @strong{Startup and path searching}: code to assemble paths at startup
|
|
|
8536 rewritten for new package system; new function @code{split-path} (splits
|
|
|
8537 by @code{path-separator}); @code{Info-default-directory-list} obsolete,
|
|
|
8538 use @code{Info-directory-list} instead; site-lisp is deprecated and no
|
|
|
8539 longer on the load-path by default.
|
|
|
8540
|
|
|
8541 @end itemize
|
|
|
8542
|
|
2459
|
8543 @node Q9.0.4, Q9.0.5, Q9.0.3, Current Events
|
|
|
8544 @unnumberedsubsec Q9.0.4: What's new in XEmacs 20.4?
|
|
611
|
8545
|
|
|
8546 XEmacs 20.4 is a bugfix release with no user-visible changes.
|
|
|
8547 @c Filled in from NEWS file of 20.5-b33
|
|
|
8548
|
|
2459
|
8549 @node Q9.0.5, Q9.0.6, Q9.0.4, Current Events
|
|
|
8550 @unnumberedsubsec Q9.0.5: What's new in XEmacs 20.3?
|
|
428
|
8551
|
|
|
8552 XEmacs 20.3 was released in November 1997. It contains many bugfixes,
|
|
|
8553 and a number of new features, including Autoconf 2 based configuration,
|
|
|
8554 additional support for Mule (Multi-language extensions to Emacs), many
|
|
|
8555 more customizations, multiple frames on TTY-s, support for multiple info
|
|
|
8556 directories, an enhanced gnuclient, improvements to regexp matching,
|
|
|
8557 increased MIME support, and many, many synches with GNU Emacs 20.
|
|
|
8558
|
|
|
8559 The XEmacs/Mule support has been only seriously tested in a Japanese
|
|
|
8560 locale, and no doubt many problems still remain. The support for
|
|
|
8561 ISO-Latin-1 and Japanese is fairly strong. MULE support comes at a
|
|
440
|
8562 price---about a 30% slowdown from 19.16. We're making progress on
|
|
428
|
8563 improving performance and XEmacs 20.3 compiled without Mule (which is
|
|
|
8564 the default) is definitely faster than XEmacs 19.16.
|
|
|
8565
|
|
|
8566 XEmacs 20.3 is the first non-beta v20 release, and will be the
|
|
|
8567 basis for all further development.
|
|
|
8568
|
|
2459
|
8569 @node Q9.0.6, , Q9.0.5, Current Events
|
|
|
8570 @unnumberedsubsec Q9.0.6: What's new in XEmacs 20.2?
|
|
611
|
8571
|
|
|
8572 The biggest changes in 20.2 include integration of EFS (the next
|
|
|
8573 generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a
|
|
|
8574 major mode for editing Tex and LaTeX, and a lot of other stuff). Many
|
|
|
8575 bugs from 20.0 have been fixed for this release. 20.2 also contains a
|
|
|
8576 new system for customizing XEmacs options, invoked via @kbd{M-x
|
|
|
8577 customize}.
|
|
|
8578
|
|
|
8579 XEmacs 20.2 is the development release (20.0 was beta), and is no longer
|
|
|
8580 considered unstable.
|
|
|
8581
|
|
|
8582 For older news, see the file @file{ONEWS} in the @file{etc} directory of
|
|
|
8583 the XEmacs distribution.
|
|
428
|
8584
|
|
2417
|
8585 @node Legacy Versions, , Current Events, Top
|
|
2459
|
8586 @unnumbered 10 New information about old XEmacsen
|
|
|
8587
|
|
|
8588 This is part 10 of the XEmacs Frequently Asked Questions list. It will
|
|
1495
|
8589 occasionally be updated to reflect new information about versions which
|
|
|
8590 are no longer being revised by the XEmacs Project. The primary purpose
|
|
|
8591 is advice on compatibility of older XEmacsen with new packages and
|
|
|
8592 updated versions of packages, but bug fixes (which will not be applied
|
|
|
8593 to released XEmacsen, but users can apply themselves) are also accepted.
|
|
|
8594
|
|
|
8595 @menu
|
|
2537
|
8596 10.0: XEmacs 21.1
|
|
2459
|
8597 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
2559
|
8598 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1.
|
|
1495
|
8599 @end menu
|
|
|
8600
|
|
2459
|
8601 @unnumberedsec 10.0: XEmacs 21.1
|
|
|
8602
|
|
2559
|
8603 @node Q10.0.1, Q10.0.2, Legacy Versions, Legacy Versions
|
|
2459
|
8604 @unnumberedsubsec Q10.0.1: Gnus 5.10 won't display smileys in XEmacs 21.1.
|
|
1495
|
8605
|
|
|
8606 @email{eeide@@cs.utah.edu, Eric Eide} wrote:
|
|
|
8607
|
|
|
8608 @quotation
|
|
|
8609 Previously I wrote:
|
|
|
8610
|
|
|
8611 Eric> Summary: with Gnus 5.10.1 in XEmacs 21.1.14, I don't see
|
|
|
8612 Eric> any smileys :-(.
|
|
|
8613
|
|
|
8614 After a bit of sleuthing, I discovered the essence of the problem.
|
|
|
8615 For me, the form:
|
|
|
8616
|
|
|
8617 @lisp
|
|
|
8618 (with-temp-buffer
|
|
|
8619 (insert-file-contents "foo.xpm")
|
|
|
8620 (buffer-string))
|
|
|
8621 @end lisp
|
|
|
8622
|
|
|
8623 returns the empty string. This is because something somewhere
|
|
|
8624 replaces the XPM data with a glyph --- I haven't figured out where
|
|
|
8625 this occurs.
|
|
|
8626 @end quotation
|
|
|
8627
|
|
|
8628 @email{kyle_jones@@wonderworks.com, Kyle Jones} replies:
|
|
|
8629
|
|
|
8630 @quotation
|
|
|
8631 Do this:
|
|
|
8632
|
|
|
8633 @lisp
|
|
|
8634 (setq format-alist nil)
|
|
|
8635 @end lisp
|
|
|
8636
|
|
|
8637 The image-mode stuff is gone from format-alist in the 21.4
|
|
|
8638 branch, praise be.
|
|
|
8639 @end quotation
|
|
|
8640
|
|
2559
|
8641 @node Q10.0.2, , Q10.0.1, Legacy Versions
|
|
|
8642 @unnumberedsubsec Q10.0.2: XEmacs won't start on Windows in XEmacs 21.1.
|
|
|
8643
|
|
|
8644 XEmacs relies on a process called "dumping" to generate a working
|
|
|
8645 executable. Under MS-Windows this process effectively fixes the memory
|
|
|
8646 addresses of information in the executable. When XEmacs starts up it tries
|
|
|
8647 to reserve these memory addresses so that the dumping process can be
|
|
|
8648 reversed -- putting the information back at the correct addresses.
|
|
|
8649 Unfortunately some .DLLs (for instance the soundblaster driver) occupy
|
|
|
8650 memory addresses that can conflict with those needed by the dumped XEmacs
|
|
|
8651 executable. In this instance XEmacs will fail to start without any
|
|
|
8652 explanation. Note that this is extremely machine specific.
|
|
|
8653
|
|
|
8654 21.1.10 includes a fix for this that makes more intelligent guesses
|
|
|
8655 about which memory addresses will be free, and this should cure the
|
|
|
8656 problem for most people. 21.4 implements "portable dumping", which
|
|
|
8657 eliminates the problem altogether. We recommend you use the 21.4
|
|
|
8658 binaries, but you can use the 21.1 binaries if you are very paranoid
|
|
|
8659 about stability. @xref{Q1.1.2, Are binaries available?}.
|
|
|
8660
|
|
428
|
8661 @bye
|
