1 \input texinfo.tex @c -*- mode: texinfo; coding: iso-2022-8 -*-
3 @setfilename ../info/xemacs-faq.info
4 @settitle Frequently asked questions about XEmacs
10 @subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2002/04/30 16:06:09 $
12 @author Tony Rossini <rossini@@biostat.washington.edu>
13 @author Ben Wing <ben@@xemacs.org>
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>
18 @author Sandra Wambold <wambold@@xemacs.org>
23 @dircategory XEmacs Editor
25 * FAQ: (xemacs-faq). XEmacs FAQ.
29 @node Top, Introduction, (dir), (dir)
32 This is the guide to the XEmacs Frequently Asked Questions list---a
33 compendium of questions and answers pertaining to one of the finest
34 programs ever written. XEmacs is much more than just a Text Editor.
36 This FAQ is freely redistributable. This FAQ is distributed in the hope
37 that it will be useful, but WITHOUT ANY WARRANTY; without even the
38 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
40 If you have a Web browser, the official hypertext version is at
44 @uref{http://www.xemacs.org/faq/xemacs-faq.html}
48 This document is available in several different formats:
51 @uref{xemacs-faq.txt, As a single ASCII file}, produced by
52 @code{makeinfo --no-headers}
54 @uref{xemacs-faq.dvi, As a .dvi file}, as used with
55 @uref{http://www.tug.org, TeX.}
57 As a PostScript file @uref{xemacs-faq-a4.ps, in A4 format},
58 as well as in @uref{xemacs-faq-letter.ps, letter format}
60 In html format, @uref{xemacs-faq_1.html, split by chapter}, or in
61 @uref{xemacs-faq.html, one monolithic} document.
63 The canonical version of the FAQ is the texinfo document
64 @uref{xemacs-faq.texi, man/xemacs-faq.texi}.
66 If you do not have makeinfo installed, you may @uref{xemacs-faq.info,
67 download the faq} in info format, and install it in @file{<XEmacs
68 library directory>/info/}. For example in
69 @file{/usr/local/lib/xemacs-21.4/info/}.
77 @c end ifset points to CANONICAL
80 * Introduction:: Introduction, Policy, Credits.
81 * Installation:: Installation and Trouble Shooting.
82 * Customization:: Customization and Options.
83 * Subsystems:: Major Subsystems.
84 * Miscellaneous:: The Miscellaneous Stuff.
85 * MS Windows:: XEmacs on Microsoft Windows.
86 * Current Events:: What the Future Holds.
90 --- The Detailed Node Listing ---
92 Introduction, Policy, Credits
94 * Q1.0.1:: What is XEmacs?
95 * Q1.0.2:: What is the current version of XEmacs?
96 * Q1.0.3:: Where can I find it?
97 * Q1.0.4:: Why Another Version of Emacs?
98 * Q1.0.5:: Why Haven't XEmacs and GNU Emacs Merged?
99 * Q1.0.6:: Where can I get help?
100 * Q1.0.7:: Where are the mailing lists archived?
101 * Q1.0.8:: How do you pronounce XEmacs?
102 * Q1.0.9:: What does XEmacs look like?
103 * Q1.0.10:: Is there a port of XEmacs to Microsoft ('95 or NT)?
104 * Q1.0.11:: Is there a port of XEmacs to the Macintosh?
105 * Q1.0.12:: Is there a port of XEmacs to NextStep?
106 * Q1.0.13:: Is there a port of XEmacs to OS/2?
107 * Q1.0.14:: Where can I get a printed copy of the XEmacs users manual?
110 * Q1.1.1:: What is the FAQ editorial policy?
111 * Q1.1.2:: How do I become a Beta Tester?
112 * Q1.1.3:: How do I contribute to XEmacs itself?
115 * Q1.2.1:: Who wrote XEmacs?
116 * Q1.2.2:: Who contributed to this version of the FAQ?
117 * Q1.2.3:: Who contributed to the FAQ in the past?
119 Internationalization:
120 * Q1.3.1:: What is the status of internationalization support aka MULE (including Asian language support?
121 * Q1.3.2:: How can I help with internationalization?
122 * Q1.3.3:: How do I type non-ASCII characters?
123 * Q1.3.4:: Can XEmacs messages come out in a different language?
124 * Q1.3.5:: Please explain the various input methods in MULE/XEmacs
125 * Q1.3.6:: How do I portably code for MULE/XEmacs?
126 * Q1.3.7:: How about Cyrillic Modes?
127 * Q1.3.8:: Does XEmacs support Unicode?
128 * Q1.3.9:: How does XEmacs display Unicode?
131 * Q1.4.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one?
132 * Q1.4.2:: Can I use the same @file{init.el}/@file{.emacs} with the other Emacs?
133 * Q1.4.3:: Any good XEmacs tutorials around?
134 * Q1.4.4:: May I see an example of a useful XEmacs Lisp function?
135 * Q1.4.5:: And how do I bind it to a key?
136 * Q1.4.6:: What's the difference between a macro and a function?
138 Installation and Trouble Shooting
140 * Q2.0.1:: Running XEmacs without installing.
141 * Q2.0.2:: XEmacs is too big.
142 * Q2.0.3:: Compiling XEmacs with Netaudio.
143 * Q2.0.4:: Problems with Linux and ncurses.
144 * Q2.0.5:: Do I need X11 to run XEmacs?
145 * Q2.0.6:: I'm having strange crashes. What do I do?
146 * Q2.0.7:: Libraries in non-standard locations.
147 * Q2.0.8:: can't resolve symbol _h_errno
148 * Q2.0.9:: Where do I find external libraries?
149 * Q2.0.10:: After I run configure I find a coredump, is something wrong?
150 * Q2.0.11:: XEmacs can't resolve host names.
151 * Q2.0.12:: Why can't I strip XEmacs?
152 * Q2.0.13:: I don't need no steenkin' packages. Do I? (NEW)
153 * Q2.0.14:: How do I figure out which packages to install? (NEW)
156 * Q2.1.1:: XEmacs just crashed on me!
157 * Q2.1.2:: Cryptic Minibuffer messages.
158 * Q2.1.3:: Translation Table Syntax messages at Startup.
159 * Q2.1.4:: Startup warnings about deducing proper fonts?
160 * Q2.1.5:: XEmacs cannot connect to my X Terminal.
161 * Q2.1.6:: XEmacs just locked up my Linux X server.
162 * Q2.1.7:: HP Alt key as Meta.
163 * Q2.1.8:: got (wrong-type-argument color-instance-p nil)!
164 * Q2.1.9:: XEmacs causes my OpenWindows 3.0 server to crash.
165 * Q2.1.10:: Warnings from incorrect key modifiers.
166 * Q2.1.11:: Can't instantiate image error... in toolbar
167 * Q2.1.12:: Regular Expression Problems on DEC OSF1.
168 * Q2.1.13:: HP/UX 10.10 and @code{create_process} failure
169 * Q2.1.14:: @kbd{C-g} doesn't work for me. Is it broken?
170 * Q2.1.15:: How to debug an XEmacs problem with a debugger.
171 * Q2.1.16:: XEmacs crashes in @code{strcat} on HP/UX 10.
172 * Q2.1.17:: @samp{Marker does not point anywhere}.
173 * Q2.1.18:: XEmacs is outputting lots of X errors.
174 * Q2.1.19:: XEmacs does not follow the local timezone.
175 * Q2.1.20:: @samp{Symbol's function definition is void: hkey-help-show.}
176 * Q2.1.21:: [This question intentionally left blank]
177 * Q2.1.22:: XEmacs seems to take a really long time to do some things.
178 * Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
179 * Q2.1.24:: XEmacs won't start without network. (NEW)
180 * Q2.1.25:: After upgrading, XEmacs won't do `foo' any more! (NEW)
182 Customization and Options
184 * Q3.0.1:: What version of Emacs am I running?
185 * Q3.0.2:: How do I evaluate Elisp expressions?
186 * Q3.0.3:: @code{(setq tab-width 6)} behaves oddly.
187 * Q3.0.4:: How can I add directories to the @code{load-path}?
188 * Q3.0.5:: How to check if a lisp function is defined?
189 * Q3.0.6:: Can I force the output of @code{(face-list)} to a buffer?
190 * Q3.0.7:: Font selections don't get saved after @code{Save Options}.
191 * Q3.0.8:: How do I make a single minibuffer frame?
192 * Q3.0.9:: What is @code{Customize}?
194 X Window System & Resources:
195 * Q3.1.1:: Where is a list of X resources?
196 * Q3.1.2:: How can I detect a color display?
197 * Q3.1.3:: [This question intentionally left blank]
198 * Q3.1.4:: [This question intentionally left blank]
199 * Q3.1.5:: How can I get the icon to just say @samp{XEmacs}?
200 * Q3.1.6:: How can I have the window title area display the full path?
201 * Q3.1.7:: @samp{xemacs -name junk} doesn't work?
202 * Q3.1.8:: @samp{-iconic} doesn't work.
204 Textual Fonts & Colors:
205 * Q3.2.1:: How can I set color options from @file{init.el}/@file{.emacs}?
206 * Q3.2.2:: How do I set the text, menu and modeline fonts?
207 * Q3.2.3:: How can I set the colors when highlighting a region?
208 * Q3.2.4:: How can I limit color map usage?
209 * Q3.2.5:: My tty supports color, but XEmacs doesn't use them.
210 * Q3.2.6:: Can I have pixmap backgrounds in XEmacs?
213 * Q3.3.1:: How can I make the modeline go away?
214 * Q3.3.2:: How do you have XEmacs display the line number in the modeline?
215 * Q3.3.3:: How do I get XEmacs to put the time of day on the modeline?
216 * Q3.3.4:: How do I turn off current chapter from AUC TeX modeline?
217 * Q3.3.5:: How can one change the modeline color based on the mode used?
219 Multiple Device Support:
220 * Q3.4.1:: How do I open a frame on another screen of my multi-headed display?
221 * Q3.4.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
224 * Q3.5.1:: How can I bind complex functions (or macros) to keys?
225 * Q3.5.2:: How can I stop down-arrow from adding empty lines to the bottom of my buffers?
226 * Q3.5.3:: How do I bind C-. and C-; to scroll one line up and down?
227 * Q3.5.4:: Globally binding @kbd{Delete}?
228 * Q3.5.5:: Scrolling one line at a time.
229 * Q3.5.6:: How to map @kbd{Help} key alone on Sun type4 keyboard?
230 * Q3.5.7:: How can you type in special characters in XEmacs?
231 * Q3.5.8:: [This question intentionally left blank]
232 * Q3.5.9:: How do I make the Delete key delete forward?
233 * Q3.5.10:: Can I turn on @dfn{sticky} modifier keys?
234 * Q3.5.11:: How do I map the arrow keys?
237 * Q3.6.1:: Is there a way to make the bar cursor thicker?
238 * Q3.6.2:: Is there a way to get back the old block cursor where the cursor covers the character in front of the point?
239 * Q3.6.3:: Can I make the cursor blink?
241 The Mouse and Highlighting:
242 * Q3.7.1:: How can I turn off Mouse pasting?
243 * Q3.7.2:: How do I set control/meta/etc modifiers on mouse buttons?
244 * Q3.7.3:: Clicking the left button does not do anything in buffer list.
245 * Q3.7.4:: How can I get a list of buffers when I hit mouse button 3?
246 * Q3.7.5:: Why does cut-and-paste not work between XEmacs and a cmdtool?
247 * Q3.7.6:: How I can set XEmacs up so that it pastes where the text cursor is?
248 * Q3.7.7:: How do I select a rectangular region?
249 * Q3.7.8:: Why does @kbd{M-w} take so long?
251 The Menubar and Toolbar:
252 * Q3.8.1:: How do I get rid of the menu (or menubar)?
253 * Q3.8.2:: Can I customize the basic menubar?
254 * Q3.8.3:: How do I control how many buffers are listed in the menu @code{Buffers} list?
255 * Q3.8.4:: Resources like @code{Emacs*menubar*font} are not working?
256 * Q3.8.5:: How can I bind a key to a function to toggle the toolbar?
259 * Q3.9.1:: How can I disable the scrollbar?
260 * Q3.9.2:: How can one use resources to change scrollbar colors?
261 * Q3.9.3:: Moving the scrollbar can move the point; can I disable this?
262 * Q3.9.4:: How can I turn off automatic horizontal scrolling in specific modes?
265 * Q3.10.1:: How can I turn off or change highlighted selections?
266 * Q3.10.2:: How do I get that typing on an active region removes it?
267 * Q3.10.3:: Can I turn off the highlight during isearch?
268 * Q3.10.4:: How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
269 * Q3.10.5:: The region disappears when I hit the end of buffer while scrolling.
273 * Q4.0.1:: How do I set up VM to retrieve remote mail using POP?
274 * Q4.0.2:: How do I get VM to filter mail for me?
275 * Q4.0.3:: How can I get VM to automatically check for new mail?
276 * Q4.0.4:: [This question intentionally left blank]
277 * Q4.0.5:: How do I get my outgoing mail archived?
278 * Q4.0.6:: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"?
279 * Q4.0.7:: Is there a mailing list or FAQ for VM?
280 * Q4.0.8:: Remote mail reading with VM.
281 * Q4.0.9:: rmail or VM gets an error incorporating new mail.
282 * Q4.0.10:: How do I make VM stay in a single frame?
283 * Q4.0.11:: How do I make VM or mh-e display graphical smilies?
284 * Q4.0.12:: Customization of VM not covered in the manual or here.
286 Web browsing with W3:
287 * Q4.1.1:: What is W3?
288 * Q4.1.2:: How do I run W3 from behind a firewall?
289 * Q4.1.3:: Is it true that W3 supports style sheets and tables?
291 Reading Netnews and Mail with Gnus:
292 * Q4.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
293 * Q4.2.2:: [This question intentionally left blank]
294 * Q4.2.3:: How do I make Gnus stay within a single frame?
295 * Q4.2.4:: How do I customize the From: line?
298 * Q4.3.1:: How can I read and/or compose MIME messages?
299 * Q4.3.2:: What is TM and where do I get it?
300 * Q4.3.3:: Why isn't this @code{movemail} program working?
301 * Q4.3.4:: Movemail is also distributed by Netscape? Can that cause problems?
302 * Q4.3.5:: Where do I find pstogif (required by tm)?
304 Sparcworks, EOS, and WorkShop:
305 * Q4.4.1:: What is SPARCworks, EOS, and WorkShop
306 * Q4.4.2:: How do I start the Sun Workshop support in XEmacs 21?
309 * Q4.5.1:: What is/was Energize?
312 * Q4.6.1:: What is Infodock?
314 Other Unbundled Packages:
315 * Q4.7.1:: What is AUC TeX? Where do you get it?
316 * Q4.7.2:: Are there any Emacs Lisp Spreadsheets?
317 * Q4.7.3:: [This question intentionally left blank]
318 * Q4.7.4:: Problems installing AUC TeX
319 * Q4.7.5:: Is there a reason for an Emacs package not to be included in XEmacs?
320 * Q4.7.6:: Is there a MatLab mode?
321 * Q4.7.7:: Can I edit files on other hosts?
323 The Miscellaneous Stuff
325 * Q5.0.1:: How can I do source code highlighting using font-lock?
326 * Q5.0.2:: I do not like cc-mode. How do I use the old c-mode?
327 * Q5.0.3:: How do I get @samp{More} Syntax Highlighting on by default?
328 * Q5.0.4:: How can I enable auto-indent and/or Filladapt?
329 * Q5.0.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
330 * Q5.0.6:: How do I start up a second shell buffer?
331 * Q5.0.7:: Telnet from shell filters too much.
332 * Q5.0.8:: Why does edt emulation not work?
333 * Q5.0.9:: How can I emulate VI and use it as my default mode?
334 * Q5.0.10:: [This question intentionally left blank]
335 * Q5.0.11:: [This question intentionally left blank]
336 * Q5.0.12:: How do I disable gnuserv from opening a new frame?
337 * Q5.0.13:: How do I start gnuserv so that each subsequent XEmacs is a client?
338 * Q5.0.14:: Strange things are happening in Shell Mode.
339 * Q5.0.15:: Where do I get the latest CC Mode?
340 * Q5.0.16:: I find auto-show-mode disconcerting. How do I turn it off?
341 * Q5.0.17:: How can I get two instances of info?
342 * Q5.0.18:: [This question intentionally left blank]
343 * Q5.0.19:: Is there something better than LaTeX mode?
344 * Q5.0.20:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
346 Emacs Lisp Programming Techniques:
347 * Q5.1.1:: The difference in key sequences between XEmacs and GNU Emacs?
348 * Q5.1.2:: Can I generate "fake" keyboard events?
349 * Q5.1.3:: Could you explain @code{read-kbd-macro} in more detail?
350 * Q5.1.4:: What is the performance hit of @code{let}?
351 * Q5.1.5:: What is the recommended use of @code{setq}?
352 * Q5.1.6:: What is the typical misuse of @code{setq} ?
353 * Q5.1.7:: I like the @code{do} form of cl, does it slow things down?
354 * Q5.1.8:: I like recursion, does it slow things down?
355 * Q5.1.9:: How do I put a glyph as annotation in a buffer?
356 * Q5.1.10:: @code{map-extents} won't traverse all of my extents!
357 * Q5.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
360 * Q5.2.1:: How do I turn off the sound?
361 * Q5.2.2:: How do I get funky sounds instead of a boring beep?
362 * Q5.2.3:: What's NAS, how do I get it?
363 * Q5.2.4:: Sunsite sounds don't play.
366 * Q5.3.1:: How do you make XEmacs indent CL if-clauses correctly?
367 * Q5.3.2:: [This question intentionally left blank]
368 * Q5.3.3:: How can I print WYSIWYG a font-locked buffer?
369 * Q5.3.4:: Getting @kbd{M-x lpr} to work with postscript printer.
370 * Q5.3.5:: How do I specify the paths that XEmacs uses for finding files?
371 * Q5.3.6:: [This question intentionally left blank]
372 * Q5.3.7:: Can I have the end of the buffer delimited in some way?
373 * Q5.3.8:: How do I insert today's date into a buffer?
374 * Q5.3.9:: Are only certain syntactic character classes available for abbrevs?
375 * Q5.3.10:: How can I get those oh-so-neat X-Face lines?
376 * Q5.3.11:: How do I add new Info directories?
377 * Q5.3.12:: What do I need to change to make printing work?
382 * Q6.0.1:: What is the status of the XEmacs port to Windows?
383 * Q6.0.2:: What flavors of MS Windows are supported? The list name implies NT only.
384 * Q6.0.3:: Are binaries available?
385 * Q6.0.4:: Can I build XEmacs on MS Windows with X support? Do I need to?
386 * Q6.0.5:: I'd like to help out. What do I do?
387 * Q6.0.6:: What are Cygwin and MinGW, and do I need them to run XEmacs?
388 * Q6.0.7:: What exactly are all the different ways to build XEmacs under Windows?
390 Building XEmacs on MS Windows:
391 * Q6.1.1:: What compiler/libraries do I need to compile XEmacs?
392 * Q6.1.2:: How do I compile the native port?
393 * Q6.1.3:: What do I need for Cygwin?
394 * Q6.1.4:: How do I compile under Cygwin?
395 * Q6.1.5:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
396 * Q6.1.6:: I decided to run with X. Where do I get an X server?
397 * Q6.1.7:: How do I compile with X support?
399 Customization and User Interface:
400 * Q6.2.1:: How does the port cope with differences in the Windows user interface?
401 * Q6.2.2:: How do I change fonts in XEmacs on MS Windows?
402 * Q6.2.3:: Where do I put my @file{init.el}/@file{.emacs} file?
403 * Q6.2.4:: How do I get Windows Explorer to associate a file type with XEmacs?
404 * Q6.2.5:: Is it possible to print from XEmacs?
408 * Q6.3.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
409 * Q6.3.2:: What are the differences between the various MS Windows emacsen?
410 * Q6.3.3:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
411 * Q6.3.4:: What is the porting team doing at the moment?
414 * Q6.4.1:: XEmacs won't start on Windows.
415 * Q6.4.2:: Why do I get a blank toolbar on Windows 95?
418 * Q7.0.1:: What new features will be in XEmacs soon?
419 * Q7.0.2:: What's new in XEmacs 21.4?
420 * Q7.0.3:: What's new in XEmacs 21.1?
421 * Q7.0.4:: What's new in XEmacs 20.4?
422 * Q7.0.5:: What's new in XEmacs 20.3?
423 * Q7.0.6:: What's new in XEmacs 20.2?
427 @node Introduction, Installation, Top, Top
428 @unnumbered 1 Introduction, Policy, Credits
430 Learning XEmacs is a lifelong activity. Even people who have used Emacs
431 for years keep discovering new features. Therefore this document cannot
432 be complete. Instead it is aimed at the person who is either
433 considering XEmacs for their own use, or has just obtained it and is
434 wondering what to do next. It is also useful as a reference to
437 The previous maintainer of the FAQ was @email{rossini@@biostat.washington.edu,
438 Anthony Rossini}, who started it, after getting tired of hearing JWZ
439 complain about repeatedly having to answer questions.
440 @email{ben@@xemacs.org, Ben Wing} and @email{cthomp@@xemacs.org, Chuck
441 Thompson}, the principal authors of XEmacs, then took over and Ben did
442 a massive update reorganizing the whole thing. At which point Anthony
443 took back over, but then had to give it up again. Some of the other
444 contributors to this FAQ are listed later in this document.
446 The previous version was converted to hypertext format, and edited by
447 @email{steve@@xemacs.org, Steven L. Baur}. It was converted back to
448 texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}. The FAQ was then
449 maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it
450 on to ChristianNyb@o{}.
452 If you notice any errors or items which should be added or amended to
453 this FAQ please send email to @email{faq@@xemacs.org, Sandra
454 Wambold}. Include @samp{XEmacs FAQ} on the Subject: line.
458 * Q1.0.1:: What is XEmacs?
459 * Q1.0.2:: What is the current version of XEmacs?
460 * Q1.0.3:: Where can I find it?
461 * Q1.0.4:: Why Another Version of Emacs?
462 * Q1.0.5:: Why Haven't XEmacs and GNU Emacs Merged?
463 * Q1.0.6:: Where can I get help?
464 * Q1.0.7:: Where are the mailing lists archived?
465 * Q1.0.8:: How do you pronounce XEmacs?
466 * Q1.0.9:: What does XEmacs look like?
467 * Q1.0.10:: Is there a port of XEmacs to Microsoft ('95 or NT)?
468 * Q1.0.11:: Is there a port of XEmacs to the Macintosh?
469 * Q1.0.12:: Is there a port of XEmacs to NextStep?
470 * Q1.0.13:: Is there a port of XEmacs to OS/2?
471 * Q1.0.14:: Where can I get a printed copy of the XEmacs users manual?
474 * Q1.1.1:: What is the FAQ editorial policy?
475 * Q1.1.2:: How do I become a Beta Tester?
476 * Q1.1.3:: How do I contribute to XEmacs itself?
479 * Q1.2.1:: Who wrote XEmacs?
480 * Q1.2.2:: Who contributed to this version of the FAQ?
481 * Q1.2.3:: Who contributed to the FAQ in the past?
483 Internationalization:
484 * Q1.3.1:: What is the status of internationalization support aka MULE (including Asian language support?
485 * Q1.3.2:: How can I help with internationalization?
486 * Q1.3.3:: How do I type non-ASCII characters?
487 * Q1.3.4:: Can XEmacs messages come out in a different language?
488 * Q1.3.5:: Please explain the various input methods in MULE/XEmacs
489 * Q1.3.6:: How do I portably code for MULE/XEmacs?
490 * Q1.3.7:: How about Cyrillic Modes?
491 * Q1.3.8:: Does XEmacs support Unicode?
492 * Q1.3.9:: How does XEmacs display Unicode?
495 * Q1.4.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one?
496 * Q1.4.2:: Can I use the same @file{init.el}/@file{.emacs} with the other Emacs?
497 * Q1.4.3:: Any good XEmacs tutorials around?
498 * Q1.4.4:: May I see an example of a useful XEmacs Lisp function?
499 * Q1.4.5:: And how do I bind it to a key?
500 * Q1.4.6:: What's the difference between a macro and a function?
503 @node Q1.0.1, Q1.0.2, Introduction, Introduction
504 @unnumberedsec 1.0: Introduction
505 @unnumberedsubsec Q1.0.1: What is XEmacs?
508 XEmacs is a powerful, highly customizable open source text editor and
509 application development system, with full GUI support. It is protected
510 under the GNU Public License and related to other versions of Emacs, in
511 particular GNU Emacs. Its emphasis is on modern graphical user
512 interface support and an open software development model, similar to
513 Linux. XEmacs has an active development community numbering in the
514 hundreds (and thousands of active beta testers on top of this), and runs
515 on all versions of MS Windows, on Linux, and on nearly every other
516 version of Unix in existence. Support for XEmacs has been supplied by
517 Sun Microsystems, University of Illinois, Lucid, ETL/Electrotechnical
518 Laboratory, Amdahl Corporation, BeOpen, and others, as well as the
519 unpaid time of a great number of individual developers.
521 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction
522 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs?
524 XEmacs versions 21.1.* are releases made from the current stable
525 sources. XEmacs versions 21.2.* are releases made from the development
526 sources. Check at @uref{http://www.xemacs.org} for the current minor
529 XEmacs 19.16 was the last release of v19, released in November, 1997,
530 which was also the last version without international language support.
532 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction
533 @unnumberedsubsec Q1.0.3: Where can I find it?
535 The canonical source and binaries can be found via anonymous FTP at:
538 @uref{ftp://ftp.xemacs.org/pub/xemacs/}
541 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction
542 @unnumberedsubsec Q1.0.4: Why Another Version of Emacs?
544 For a detailed description of the differences between GNU Emacs and
545 XEmacs and a detailed history of XEmacs, check out the
547 @uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file}
550 However, here is a list of some of the reasons why we think you might
558 The XEmacs maintainers are generally more receptive to suggestions than
559 the GNU Emacs maintainers.
562 Many more bundled packages than GNU Emacs.
565 Binaries are available for many common operating systems.
568 Face support on TTY's.
574 Better Motif compliance.
577 Some internationalization support (including full MULE support, if
581 Variable-width fonts.
584 Variable-height lines.
587 Marginal annotations.
593 XEmacs can be used as an Xt widget, and can be embedded within another
597 Horizontal and vertical scrollbars (using real toolkit scrollbars).
600 Better APIs (and performance) for attaching fonts, colors, and other
604 The ability to embed arbitrary graphics in a buffer.
607 Completely compatible (at the C level) with the Xt-based toolkits.
611 @node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
612 @unnumberedsubsec Q1.0.5: Why Haven't XEmacs and GNU Emacs Merged?
614 There are currently irreconcilable differences in the views about
615 technical, programming, design and organizational matters between RMS
616 and the XEmacs development team which provide little hope for a merge to
617 take place in the short-term future.
619 If you have a comment to add regarding the merge, it is a good idea to
620 avoid posting to the newsgroups, because of the very heated flamewars
621 that often result. Mail your questions to @email{xemacs-beta@@xemacs.org} and
622 @email{bug-gnu-emacs@@prep.ai.mit.edu}.
624 @node Q1.0.6, Q1.0.7, Q1.0.5, Introduction
625 @unnumberedsubsec Q1.0.6: Where can I get help?
627 Probably the easiest way, if everything is installed, is to use Info, by
628 pressing @kbd{C-h i}, or looking for an Info item on the
629 Help Menu. @kbd{M-x apropos} can be used to look for particular commands.
631 For items not found in the manual, try reading this FAQ
632 @comment , examining the regular GNU Emacs FAQ (which can be
633 @comment found with the Emacs 19 distribution) as well as at
634 @comment @uref{http://www.eecs.nwu.edu/emacs/faq/}
635 and reading the Usenet group comp.emacs.xemacs.
637 If you choose to post to a newsgroup, @strong{please use
638 comp.emacs.xemacs}. Please do not post XEmacs related questions to
641 If you cannot post or read Usenet news, there is a corresponding mailing
642 list @email{xemacs-news@@xemacs.org} which is available. It can be
643 subscribed to via the Mailman Web interface or by sending mail to to
644 @email{xemacs-news-request@@xemacs.org} with @samp{subscribe} in the
645 body of the message. See also
646 @uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a
647 subscription, you may use the @email{xemacs-news-request@@xemacs.org}
648 address or the Web interface. Send a message with a subject of
649 @samp{unsubscribe} to be removed.
651 @node Q1.0.7, Q1.0.8, Q1.0.6, Introduction
652 @unnumberedsubsec Q1.0.7: Where are the mailing lists archived?
654 The archives can be found at @uref{http://list-archive.xemacs.org}
656 @node Q1.0.8, Q1.0.9, Q1.0.7, Introduction
657 @unnumberedsubsec Q1.0.8: How do you pronounce XEmacs?
659 The most common pronounciation is @samp{Eks eemax}.
661 @node Q1.0.9, Q1.0.10, Q1.0.8, Introduction
662 @unnumberedsubsec Q1.0.9: What does XEmacs look like?
664 Screen snapshots are available at
665 @uref{http://www.xemacs.org/About/Screenshots/index.html}
666 as part of the XEmacs website.
668 @node Q1.0.10, Q1.0.11, Q1.0.9, Introduction
669 @unnumberedsubsec Q1.0.10: Is there a port of XEmacs to Microsoft ('95 or NT)?
671 Yes. XEmacs can be built under MS Windows and is fully-featured and
672 actively developed. See @ref{MS Windows}.
674 @node Q1.0.11, Q1.0.12, Q1.0.10, Introduction
675 @unnumberedsubsec Q1.0.11: Is there a port of XEmacs to the Macintosh?
678 @c There has been a port to the MachTen environment of XEmacs 19.13, but no
679 @c patches have been submitted to the maintainers to get this in the
680 @c mainstream distribution.
682 @c For the MacOS, there is a port of
683 @c @uref{ftp://ftp.cs.cornell.edu/pub/parmet/, Emacs 18.59}.
687 XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly
688 will not feel very much like a Mac application as it has no Mac-specific
691 There is also a port of XEmacs 19.14 that works on all recent versions
692 of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com,
693 Pitts Jarvis}. It runs in an equivalent of TTY mode only (one single
694 Macintosh window, 25 colors), but has a large number of Mac-specific
695 additions. It's available at
696 @uref{http://homepage.mac.com/pjarvis/xemacs.html}.
698 @node Q1.0.12, Q1.0.13, Q1.0.11, Introduction
699 @unnumberedsubsec Q1.0.12: Is there a port of XEmacs to NextStep?
701 Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did
702 the port of GNU Emacs to NeXTstep and expressed interest in doing the
703 XEmacs port, but never went any farther.
705 @node Q1.0.13, Q1.0.14, Q1.0.12, Introduction
706 @unnumberedsubsec Q1.0.13: Is there a port of XEmacs to OS/2?
708 No, but Alexander Nikolaev <avn_1251@@mail.ru> is working on it.
710 @node Q1.0.14, Q1.1.1, Q1.0.13, Introduction
711 @unnumberedsubsec Q1.0.14: Where can I obtain a printed copy of the XEmacs User's Manual?
713 Pre-printed manuals are not available. If you are familiar with
714 TeX, you can generate your own manual from the XEmacs sources.
716 HTML and Postscript versions of XEmacs manuals are available from the
718 @uref{http://www.xemacs.org/Documentation/index.html}.
720 @node Q1.1.1, Q1.1.2, Q1.0.14, Introduction
721 @unnumberedsec 1.1: Policies
722 @unnumberedsubsec Q1.1.1: What is the FAQ editorial policy?
724 The FAQ is actively maintained and modified regularly. All links should
725 be up to date. Unfortunately, some of the information is out of date --
726 a situation which the FAQ maintainer is working on. All submissions are
727 welcome, please e-mail submissions to @email{faq@@xemacs.org, XEmacs FAQ
730 Please make sure that @samp{XEmacs FAQ} appears on the Subject: line.
731 If you think you have a better way of answering a question, or think a
732 question should be included, we'd like to hear about it. Questions and
733 answers included into the FAQ will be edited for spelling and grammar
734 and will be attributed. Answers appearing without attribution are
735 either from versions of the FAQ dated before May 1996 or are from
736 previous FAQ maintainers. Answers quoted from Usenet news articles will
737 always be attributed, regardless of the author.
739 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
740 @unnumberedsubsec Q1.1.2: How do I become a Beta Tester?
742 Send an email message to @email{xemacs-beta-request@@xemacs.org} with
743 the line @samp{subscribe} in the body of the message.
745 Be prepared to get your hands dirty, as beta testers are expected to
746 identify problems as best they can.
748 @node Q1.1.3, Q1.2.1, Q1.1.2, Introduction
749 @unnumberedsubsec Q1.1.3: How do I contribute to XEmacs itself?
751 Ben Wing @email{ben@@xemacs.org} writes:
754 BTW if you have a wish list of things that you want added, you have to
755 speak up about it! More specifically, you can do the following if you
756 want a feature added (in increasing order of usefulness):
760 Make a posting about a feature you want added.
763 Become a beta tester and make more postings about those same features.
766 Convince us that you're going to use the features in some cool and
770 Come up with a clear and well-thought-out API concerning the features.
773 Write the code to implement a feature and send us a patch.
776 (not that we're necessarily requiring you to write the code, but we can
780 @node Q1.2.1, Q1.2.2, Q1.1.3, Introduction
781 @unnumberedsec 1.2: Credits
782 @unnumberedsubsec Q1.2.1: Who wrote XEmacs?
784 XEmacs is the result of the time and effort of many people. The
785 developers responsible for recent releases are:
788 @item @email{martin@@xemacs.org, Martin Buchholz}
790 <br><img src="mrb.jpeg" alt="Portrait of Martin Buchholz"><br>
794 @item @email{turnbull@@sk.tsukuba.ac.jp, Steven Turnbull}
797 @item @email{ben@@xemacs.org, Ben Wing}
799 <br><img src="wing.gif" alt="Portrait of Ben Wing"><br>
803 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
806 <br><img src="hniksic.jpeg" alt="Portrait of Hrvoje Niksic"><br>
811 The developers responsible for older releases were:
814 @item @email{steve@@xemacs.org, Steve Baur}
817 <br><img src="steve.gif" alt="Portrait of Steve Baur"><br>
820 @item @email{cthomp@@xemacs.org, Chuck Thompson}
822 <br><img src="cthomp.jpeg" alt="Portrait of Chuck Thompson"><br>
825 @item @email{jwz@@jwz.org, Jamie Zawinski}
827 <br><img src="jwz.gif" alt="Portrait of Jamie Zawinski"><br>
830 @item @email{mly@@adoc.xerox.com, Richard Mlynarik}
832 Steve Baur was the primary maintainer for 19.15 through 21.0.
834 Chuck Thompson and Ben Wing were the maintainers for 19.11 through 19.14
835 and heavy code contributors for 19.8 through 19.10.
837 Jamie Zawinski was the maintainer for 19.0 through 19.10 (the entire
838 history of Lucid Emacs). Richard Mlynarik was a heavy code contributor
839 to 19.6 through 19.8.
843 Along with many other contributors, partially enumerated in the
844 @samp{About XEmacs} option in the Help menu.
846 @node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
847 @unnumberedsubsec Q1.2.2: Who contributed to this version of the FAQ?
849 The following people contributed valuable suggestions to building this
850 version of the FAQ (listed in alphabetical order):
853 @item @email{steve@@xemacs.org, SL Baur}
855 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
857 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
861 @node Q1.2.3, Q1.3.1, Q1.2.2, Introduction
862 @unnumberedsubsec Q1.2.3: Who contributed to the FAQ in the past?
864 This is only a partial list, as many names were lost in a hard disk
868 @item @email{binge@@aloft.att.com, Curtis.N.Bingham}
870 @item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan}
872 @item @email{rjc@@cogsci.ed.ac.uk, Richard Caley}
874 @item @email{cognot@@ensg.u-nancy.fr, Richard Cognot}
876 @item @email{daku@@nortel.ca, Mark Daku}
878 @item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque}
880 @item @email{eeide@@cs.utah.edu, Eric Eide}
882 @item @email{af@@biomath.jussieu.fr, Alain Fauconnet}
884 @item @email{cflatter@@nrao.edu, Chris Flatters}
886 @item @email{ginsparg@@adra.com, Evelyn Ginsparg}
888 @item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall}
890 @item @email{dkindred@@cmu.edu, Darrell Kindred}
892 @item @email{dmoore@@ucsd.edu, David Moore}
894 @item @email{arup+@@cmu.edu, Arup Mukherjee}
896 @item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen}
898 @item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell}
900 @item @email{dworkin@@ccs.neu.edu, Justin Sheehy}
902 @item @email{stig@@hackvan.com, Stig}
904 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
907 @node Q1.3.1, Q1.3.2, Q1.2.3, Introduction
908 @unnumberedsec 1.3: Internationalization
909 @unnumberedsubsec Q1.3.1: What is the status of internationalization support aka MULE (including Asian language support?
911 Both the stable and development versions of XEmacs include
912 internationalization support (aka MULE). MULE currently works on UNIX
913 and Linux systems; work for supporting MULE on Windows operating systems
914 is in progress. Binaries compiled without MULE support run faster than
915 MULE capable XEmacsen.
917 @node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
918 @unnumberedsubsec Q1.3.2: How can I help with internationalization?
920 If you would like to help, you may want to join the
921 @email{xemacs-mule@@xemacs.org} mailing list. Especially needed are
922 people who speak/write languages other than English, who are willing to
923 use XEmacs/MULE regularly, and have some experience with Elisp.
927 @node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
928 @unnumberedsubsec Q1.3.3: How do I type non-ASCII characters?
930 See question 3.5.7 (@pxref{Q3.5.7}) in part 3 of this FAQ.
932 @node Q1.3.4, Q1.3.5, Q1.3.3, Introduction
933 @unnumberedsubsec Q1.3.4: Can XEmacs messages come out in a different language?
935 The message-catalog support has mostly been written but doesn't
936 currently work. The first release of XEmacs 20 will @emph{not} support
937 it. However, menubar localization @emph{does} work. To
938 enable it, add to your @file{Emacs} file entries like this:
941 Emacs*XlwMenu.resourceLabels: True
942 Emacs*XlwMenu.file.labelString: Fichier
943 Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster oeffnen
946 The name of the resource is derived from the non-localized entry by
947 removing punctuation and capitalizing as above.
949 @node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
950 @unnumberedsubsec Q1.3.5: Please explain the various input methods in MULE/XEmacs
952 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
955 Original Mule supports the following input methods: Wnn4, Wnn6, Canna, SJ3
956 and XIM. Interfaces for Wnn and SJ3 uses the @code{egg} user
957 interface. Interface for Canna does not use @samp{egg}. I don't know
958 about XIM. It is to support ATOK, of course, it may work for another
961 Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
962 university. It is a powerful and complex system. Wnn4 is free and Wnn6
965 Canna supports only Japanese. It is made by NEC. It is a simple and
966 powerful system. Canna uses only grammar (Wnn uses grammar and
967 probability between words), so I think Wnn is cleverer than Canna,
968 however Canna users made a good grammar and dictionary. So for standard
969 modern Japanese, Canna seems cleverer than Wnn4. In addition, the UNIX
970 version of Canna is free (now there is a Microsoft Windows version).
972 SJ3 supports only Japanese. It is made by Sony. XIM supports was made
973 to use ATOK (a major input method in personal computer world). XIM is
974 the standard for accessing input methods bundled in Japanese versions of
975 Solaris. (XEmacs 20 will support XIM input).
977 Egg consists of following parts:
981 Input character Translation System (ITS) layer.
982 It translates ASCII inputs to Kana/PinYin/Hangul characters.
985 Kana/PinYin/Hangul to Kanji transfer layer.
986 It is interface layer for network Kana-Kanji server (Wnn and Sj3).
989 These input methods are modal, namely there are mode, alphabet mode and
990 Kana-Kanji transfer mode. However there are mode-less input methods for
991 Egg and Canna. @samp{Boiled-egg} is a mode-less input method running on
992 Egg. For Canna, @samp{canna.el} has a tiny boiled-egg like command,
993 @code{(canna-boil)}, and there are some boiled-egg like utilities. In
994 addition, it was planned to make an abstraction for all transfer type
995 input methods. However authors of input methods are busy, so maybe this
996 plan is stopped. Perhaps after Mule merged GNU Emacs will be released,
997 it will be continued.
1000 @node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
1001 @unnumberedsubsec Q1.3.6: How do I portably code for MULE/XEmacs?
1003 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
1006 MULE and XEmacs are quite different. So the application
1007 implementor must write separate code for these mule variants.
1009 MULE and the next version of Emacs are similar but the symbols are very
1010 different---requiring separate code as well.
1012 Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of
1013 emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called
1014 @code{emu} to provide a common interface.
1016 I have the following suggestions about dealing with mule variants:
1020 @code{(featurep 'mule)} @code{t} on all mule variants
1023 @code{(boundp 'MULE)} is @code{t} on only MULE. Maybe the next version
1024 of Emacs will not have this symbol.
1027 MULE has a variable @code{mule-version}. Perhaps the next version of
1028 Emacs will have this variable as well.
1031 Following is a sample to distinguish mule variants:
1034 (if (featurep 'mule)
1035 (cond ((boundp 'MULE)
1036 ;; for original Mule
1038 ((string-match "XEmacs" emacs-version)
1039 ;; for XEmacs with Mule
1042 ;; for next version of Emacs
1044 ;; for old emacs variants
1049 @node Q1.3.7, Q1.3.8, Q1.3.6, Introduction
1050 @unnumberedsubsec Q1.3.7: How about Cyrillic Modes?
1052 @email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes:
1055 There is a cyrillic mode in the file @file{mysetup.zip} in
1059 @uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}. This is a
1060 modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el}
1061 which can be obtained from
1064 @uref{http://ftpsearch.lycos.com/?query=russian.el.Z&form=medium}.
1066 @email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes:
1069 There is another cyrillic mode for both GNU Emacs and XEmacs by
1070 @email{manin@@camelot.mssm.edu, Dmitrii
1075 @uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}.
1076 @c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead.
1077 @c Changed to russian host instead
1080 @email{rebecca.ore@@op.net, Rebecca Ore} writes:
1083 The fullest resource I found on Russian language use (in and out of
1084 XEmacs) is @uref{http://www.ibiblio.org/sergei/Software/Software.html}
1087 @node Q1.3.8, Q1.3.9, Q1.3.7, Introduction
1088 @unnumberedsubsec Q1.3.8: Does XEmacs support Unicode?
1090 Partially, as an external encoding for files, processes, and terminals.
1091 It does not yet support Unicode fonts @ref{Q1.3.9, Does XEmacs support
1094 To get Unicode support, you need a Mule-enabled XEmacs. Install
1095 Mule-UCS from packages in the usual way. Put
1097 (require 'un-define)
1098 (set-coding-priority-list '(utf-8))
1099 (set-coding-category-system 'utf-8 utf-8)
1101 Install standard national fonts (not Unicode fonts) for all
1102 character sets you use.
1104 Mule-UCS also supports 16-bit forms of Unicode (UTF-16). It does not
1105 support 31-bit forms of Unicode (UTF-32 or UCS-4).
1107 @node Q1.3.9, Q1.4.1, Q1.3.8, Introduction
1108 @unnumberedsubsec Q1.3.9: How does XEmacs display Unicode?
1110 Mule doesn't have a Unicode charset internally, so there's nothing to
1111 bind a Unicode registry to. It would not be straightforward to create,
1112 either, because Unicode is not ISO 2022-compatible. You'd have to
1113 translate it to multiple 96x96 pages.
1115 This means that Mule-UCS uses ordinary national fonts for display. This
1116 is not really a problem, except for those languages that use the Unified
1117 Han characters. The problem here is that Mule-UCS maps from Unicode
1118 code points to national character sets in a deterministic way. By
1119 default, this means that Japanese fonts are tried first, then Chinese,
1120 then Korean. To change the priority ordering, use the command
1121 `un-define-change-charset-order'.
1123 It also means you can't use Unicode fonts directly, at least not without
1124 extreme hackery. You can run -nw with (set-terminal-coding-system
1125 'utf-8) if you really want a Unicode font for some reason.
1127 Real Unicode support will be introduced in XEmacs 22.0.
1129 @node Q1.4.1, Q1.4.2, Q1.3.9, Introduction
1130 @unnumberedsec 1.4: Getting Started, Backing up & Recovery
1131 @unnumberedsubsec Q1.4.1: What is an @file{init.el} or @file{.emacs} and is there a sample one?
1133 The @file{init.el} or @file{.emacs} file is used to customize XEmacs to
1134 your tastes. Starting in 21.4, the preferred location for the init file
1135 is @file{~/.xemacs/init.el}; in previous versions, it was
1136 @file{~/.emacs}. 21.4 still accepts the old location, but the first
1137 time you run it, it will ask to migrate your file to the new location.
1138 If you answer yes, the file will be moved, and a "compatibility"
1139 @file{.emacs} file will be placed in the old location so that you can
1140 still run older versions of XEmacs, and versions of GNU Emacs, which
1141 expect the old location. The @file{.emacs} file present is just a stub
1142 that loads the real file in @file{~/.xemacs/init.el}.
1144 No two init files are alike, nor are they expected to be alike, but
1145 that's the point. The XEmacs distribution contains an excellent starter
1146 example in the @file{etc/} directory called @file{sample.init.el}
1147 (starting in 21.4) or @file{sample.emacs} in older versions. Copy this
1148 file from there to @file{~/.xemacs/init.el} (starting in 21.4) or
1149 @file{~/.emacs} in older versions, where @samp{~} means your home
1150 directory, of course. Then edit it to suit.
1152 You may bring the @file{sample.init.el} or @file{sample.emacs} file into
1153 an XEmacs buffer from the menubar. (The menu entry for it is always
1154 under the @samp{Help} menu, but its location under that has changed in
1155 various versions. Recently, look under the @samp{Samples} submenu.) To
1156 determine the location of the @file{etc/} directory type the command
1157 @kbd{C-h v data-directory @key{RET}}.
1159 @node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
1160 @unnumberedsubsec Q1.4.2: Can I use the same @file{init.el}/@file{.emacs} with the other Emacs?
1162 Yes. The sample @file{init.el}/@file{.emacs} included in the XEmacs
1163 distribution will show you how to handle different versions and flavors
1166 @node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
1167 @unnumberedsubsec Q1.4.3: Any good tutorials around?
1169 There's the XEmacs tutorial available from the Help Menu under
1170 @samp{Basics->Tutorials}, or by typing @kbd{C-h t}. To check whether
1171 it's available in a non-english language, type @kbd{C-u C-h t TAB}, type
1172 the first letters of your preferred language, then type @key{RET}.
1174 @comment There's an Emacs Lisp tutorial at
1177 @comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
1178 @comment @end example
1180 @comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
1185 @comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}.
1187 @node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
1188 @unnumberedsubsec Q1.4.4: May I see an example of a useful XEmacs Lisp function?
1190 The following function does a little bit of everything useful. It does
1191 something with the prefix argument, it examines the text around the
1192 cursor, and it's interactive so it may be bound to a key. It inserts
1193 copies of the current word the cursor is sitting on at the cursor. If
1194 you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will
1198 (defun double-word (count)
1199 "Insert a copy of the current word underneath the cursor"
1201 (let (here there string)
1206 (setq there (point))
1207 (setq string (buffer-substring here there)))
1213 The best way to see what is going on here is to let XEmacs tell you.
1214 Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor
1215 sitting just to the right of the function you want explained. Eg. move
1216 the cursor to the SPACE between @code{interactive} and @samp{"*p"} and
1217 hit @kbd{C-h f} to see what the function @code{interactive} does. Doing
1218 this will tell you that the @code{*} requires a writable buffer, and
1219 @code{p} converts the prefix argument to a number, and
1220 @code{interactive} allows you to execute the command with @kbd{M-x}.
1222 @node Q1.4.5, Q1.4.6, Q1.4.4, Introduction
1223 @unnumberedsubsec Q1.4.5: And how do I bind it to a key?
1225 To bind to a key do:
1228 (global-set-key "\C-cd" 'double-word)
1231 Or interactively, @kbd{M-x global-set-key} and follow the prompts.
1233 @node Q1.4.6, , Q1.4.5, Introduction
1234 @unnumberedsubsec Q1.4.6: What's the difference between a macro and a function?
1236 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual:
1238 @dfn{Macros} enable you to define new control constructs and other
1239 language features. A macro is defined much like a function, but instead
1240 of telling how to compute a value, it tells how to compute another Lisp
1241 expression which will in turn compute the value. We call this
1242 expression the @dfn{expansion} of the macro.
1244 Macros can do this because they operate on the unevaluated expressions
1245 for the arguments, not on the argument values as functions do. They can
1246 therefore construct an expansion containing these argument expressions
1249 Do not confuse the two terms with @dfn{keyboard macros}, which are
1250 another matter, entirely. A keyboard macro is a key bound to several
1251 other keys. Refer to manual for details.
1253 @node Installation, Customization, Introduction, Top
1254 @unnumbered 2 Installation and Trouble Shooting
1256 This is part 2 of the XEmacs Frequently Asked Questions list. This
1257 section is devoted to Installation, Maintenance and Trouble Shooting.
1261 * Q2.0.1:: Running XEmacs without installing.
1262 * Q2.0.2:: XEmacs is too big.
1263 * Q2.0.3:: Compiling XEmacs with Netaudio.
1264 * Q2.0.4:: Problems with Linux and ncurses.
1265 * Q2.0.5:: Do I need X11 to run XEmacs?
1266 * Q2.0.6:: I'm having strange crashes. What do I do?
1267 * Q2.0.7:: Libraries in non-standard locations.
1268 * Q2.0.8:: can't resolve symbol _h_errno
1269 * Q2.0.9:: Where do I find external libraries?
1270 * Q2.0.10:: After I run configure I find a coredump, is something wrong?
1271 * Q2.0.11:: XEmacs can't resolve host names.
1272 * Q2.0.12:: Why can't I strip XEmacs?
1273 * Q2.0.13:: I don't need no steenkin' packages. Do I? (NEW)
1274 * Q2.0.14:: I don't want to install a million .els one at a time! (NEW)
1277 * Q2.1.1:: XEmacs just crashed on me!
1278 * Q2.1.2:: Cryptic Minibuffer messages.
1279 * Q2.1.3:: Translation Table Syntax messages at Startup.
1280 * Q2.1.4:: Startup warnings about deducing proper fonts?
1281 * Q2.1.5:: XEmacs cannot connect to my X Terminal.
1282 * Q2.1.6:: XEmacs just locked up my Linux X server.
1283 * Q2.1.7:: HP Alt key as Meta.
1284 * Q2.1.8:: got (wrong-type-argument color-instance-p nil)!
1285 * Q2.1.9:: XEmacs causes my OpenWindows 3.0 server to crash.
1286 * Q2.1.10:: Warnings from incorrect key modifiers.
1287 * Q2.1.11:: Can't instantiate image error... in toolbar
1288 * Q2.1.12:: Regular Expression Problems on DEC OSF1.
1289 * Q2.1.13:: HP/UX 10.10 and @code{create_process} failure
1290 * Q2.1.14:: @kbd{C-g} doesn't work for me. Is it broken?
1291 * Q2.1.15:: How to debug an XEmacs problem with a debugger.
1292 * Q2.1.16:: XEmacs crashes in @code{strcat} on HP/UX 10.
1293 * Q2.1.17:: @samp{Marker does not point anywhere}.
1294 * Q2.1.18:: XEmacs is outputting lots of X errors.
1295 * Q2.1.19:: XEmacs does not follow the local timezone.
1296 * Q2.1.20:: @samp{Symbol's function definition is void: hkey-help-show.}
1297 * Q2.1.21:: [This question intentionally left blank]
1298 * Q2.1.22:: XEmacs seems to take a really long time to do some things.
1299 * Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
1300 * Q2.1.24:: XEmacs won't start without network. (NEW)
1301 * Q2.1.25:: After upgrading, XEmacs won't do `foo' any more! (NEW)
1304 @node Q2.0.1, Q2.0.2, Installation, Installation
1305 @unnumberedsec 2.0: Installation
1306 @unnumberedsubsec Q2.0.1: Running XEmacs without installing
1308 How can I just try XEmacs without installing it?
1310 XEmacs will run in place without requiring installation and copying of
1311 the Lisp directories, and without having to specify a special build-time
1312 flag. It's the copying of the Lisp directories that requires so much
1313 space. XEmacs is largely written in Lisp.
1315 A good method is to make a shell alias for xemacs:
1318 alias xemacs=/i/xemacs-20.2/src/xemacs
1321 (You will obviously use whatever directory you downloaded the source
1322 tree to instead of @file{/i/xemacs-20.2}).
1324 This will let you run XEmacs without massive copying.
1326 @node Q2.0.2, Q2.0.3, Q2.0.1, Installation
1327 @unnumberedsubsec Q2.0.2: XEmacs is too big
1329 The space required by the installation directories can be
1330 reduced dramatically if desired. Gzip all the .el files. Remove all
1331 the packages you'll never want to use. Remove the TexInfo manuals.
1332 Remove the Info (and use just hardcopy versions of the manual). Remove
1333 most of the stuff in etc. Remove or gzip all the source code. Gzip or
1334 remove the C source code. Configure it so that copies are not made of
1337 These are all Emacs Lisp source code and bytecompiled object code. You
1338 may safely gzip everything named *.el here. You may remove any package
1339 you don't use. @emph{Nothing bad will happen if you delete a package
1340 that you do not use}. You must be sure you do not use it though, so be
1341 conservative at first.
1343 Possible candidates for deletion include w3, games, hyperbole, mh-e,
1344 hm-html-menus, vm, viper, oobr, gnus, etc. Ask yourself, @emph{Do I
1345 ever want to use this package?} If the answer is no, then it is a
1346 candidate for removal.
1348 First, gzip all the .el files. Then go about package by package and
1349 start gzipping the .elc files. Then run XEmacs and do whatever it is
1350 you normally do. If nothing bad happens, then delete the directory. Be
1351 conservative about deleting directories, and it would be handy to have a
1352 backup around in case you get too zealous.
1354 @file{prim}, @file{modes}, @file{packages}, and @file{utils} are four
1355 directories you definitely do @strong{not} want to delete, although
1356 certain packages can be removed from them if you do not use them.
1358 Online texinfo sources in the @file{info} can either be compressed them
1359 or remove them. In either case, @kbd{C-h i} (info mode) will no longer
1362 @node Q2.0.3, Q2.0.4, Q2.0.2, Installation
1363 @unnumberedsubsec Q2.0.3: Compiling XEmacs with Netaudio.
1365 What is the best way to compile XEmacs with the netaudio system, since I
1366 have got the netaudio system compiled but installed at a weird place, I
1367 am not root. Also in the READMEs it does not say anything about
1368 compiling with the audioserver?
1370 You should only need to add some stuff to the configure command line.
1371 To tell it to compile in netaudio support: @samp{--with-sound=both}, or
1372 @samp{--with-sound=nas} if you don't want native sound support for some
1373 reason.) To tell it where to find the netaudio includes and libraries:
1376 --site-libraries=WHATEVER
1377 --site-includes=WHATEVER
1380 Then (fingers crossed) it should compile and it will use netaudio if you
1381 have a server running corresponding to the X server. The netaudio server
1382 has to be there when XEmacs starts. If the netaudio server goes away and
1383 another is run, XEmacs should cope (fingers crossed, error handling in
1384 netaudio isn't perfect).
1386 BTW, netaudio has been renamed as it has a name clash with something
1387 else, so if you see references to NAS or Network Audio System, it's the
1388 same thing. It also might be found at
1389 @uref{ftp://ftp.x.org/contrib/audio/nas/}.
1391 @node Q2.0.4, Q2.0.5, Q2.0.3, Installation
1392 @unnumberedsubsec Q2.0.4: Problems with Linux and ncurses.
1394 On Linux 1.3.98 with termcap 2.0.8 and the ncurses that came with libc
1395 5.2.18, XEmacs 20.0b20 is unable to open a tty device:
1399 Initialization error:
1403 Terminal type `xterm' undefined (or can't access database?)
1406 @email{ben@@xemacs.org, Ben Wing} writes:
1409 Your ncurses configuration is messed up. Your /usr/lib/terminfo is a
1410 bad pointer, perhaps to a CD-ROM that is not inserted.
1413 @node Q2.0.5, Q2.0.6, Q2.0.4, Installation
1414 @unnumberedsubsec Q2.0.5: Do I need X11 to run XEmacs?
1416 No. The name @dfn{XEmacs} is unfortunate in the sense that it is
1417 @strong{not} an X Window System-only version of Emacs. XEmacs has
1418 full color support on a color-capable character terminal.
1420 @node Q2.0.6, Q2.0.7, Q2.0.5, Installation
1421 @unnumberedsubsec Q2.0.6: I'm having strange crashes. What do I do?
1423 There have been a variety of reports of crashes due to compilers with
1424 buggy optimizers. Please see the @file{PROBLEMS} file that comes with
1425 XEmacs to read what it says about your platform.
1427 @node Q2.0.7, Q2.0.8, Q2.0.6, Installation
1428 @unnumberedsubsec Q2.0.7: Libraries in non-standard locations
1430 I have x-faces, jpeg, xpm etc. all in different places. I've tried
1431 space-separated, comma-separated, several --site-libraries, all to no
1435 --site-libraries='/path/one /path/two /path/etc'
1438 @node Q2.0.8, Q2.0.9, Q2.0.7, Installation
1439 @unnumberedsubsec Q2.0.8: can't resolve symbol _h_errno
1441 You are using the Linux/ELF distribution of XEmacs 19.14, and your ELF
1442 libraries are out of date. You have the following options:
1446 Upgrade your libc to at least 5.2.16 (better is 5.2.18, 5.3.12, or
1450 Patch the XEmacs binary by replacing all occurrences of
1451 @samp{_h_errno^@@} with
1455 @samp{h_errno^@@^@@}. Any version of Emacs will
1456 suffice. If you don't understand how to do this, don't do it.
1459 Rebuild XEmacs yourself---any working ELF version of libc should be
1463 @email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
1466 Why not use a Perl one-liner for No. 2?
1469 perl -pi -e 's/_h_errno\0/h_errno\0\0/g' \
1470 /usr/local/bin/xemacs-19.14
1473 NB: You @emph{must} patch @file{/usr/local/bin/xemacs-19.14}, and not
1474 @file{xemacs} because @file{xemacs} is a link to @file{xemacs-19.14};
1475 the Perl @samp{-i} option will cause unwanted side-effects if applied to
1479 @email{steve@@xemacs.org, SL Baur} writes:
1482 If you build against a recent libc-5.4 (late enough to have caused
1483 problems earlier in the beta cycle) and then run with an earlier version
1488 xemacs: can't resolve symbol '__malloc_hook'
1489 zsh: 7942 segmentation fault (core dumped) xemacs
1492 (Example binary compiled against libc-5.4.23 and run with libc-5.4.16).
1494 The solution is to upgrade to at least libc-5.4.23. Sigh. Drat.
1497 @node Q2.0.9, Q2.0.10, Q2.0.8, Installation
1498 @unnumberedsubsec Q2.0.9: Where do I find external libraries?
1500 All external libraries used by XEmacs can be found at the XEmacs FTP
1505 @uref{ftp://ftp.xemacs.org/pub/xemacs/aux/}.
1507 @c Changed June Link above, <URL:ftp://ftp.xemacs.org/pub/aux/> was dead.
1508 @c This list is a pain in the you-know-what to keep in synch with the
1510 The canonical locations (at the time of this writing) are as follows:
1514 @uref{ftp://ftp.uu.net/graphics/jpeg/}. Version 6a is current.
1515 @c Check from host with legal IP address
1517 @uref{ftp://ftp.x.org/contrib/libraries/}. Version 3.4j is current.
1518 Older versions of this package are known to cause XEmacs crashes.
1521 @uref{ftp://ftp.sgi.com/graphics/tiff/}. v3.4 is current. The latest
1522 beta is v3.4b035. There is a HOWTO here.
1525 @uref{ftp://ftp.uu.net/graphics/png/}. 0.89c is current. XEmacs
1526 requires a fairly recent version to avoid using temporary files.
1527 @c Check from host with legal IP address
1529 @uref{ftp://swrinde.nde.swri.edu/pub/png/src/}
1532 @uref{ftp://ftp.cs.indiana.edu/pub/faces/compface/}. This library has
1533 been frozen for about 6 years, and is distributed without version
1534 numbers. @emph{It should be compiled with the same options that X11 was
1535 compiled with on your system}. The version of this library at
1536 XEmacs.org includes the @file{xbm2xface.pl} script, written by
1537 @email{stig@@hackvan.com}, which may be useful when generating your own xface.
1540 @uref{ftp://ftp.x.org/contrib/audio/nas/}.
1541 Version 1.2p5 is current. There is a FAQ here.
1544 @node Q2.0.10, Q2.0.11, Q2.0.9, Installation
1545 @unnumberedsubsec Q2.0.10: After I run configure I find a core dump, is something wrong?
1547 Not necessarily. If you have GNU sed 3.0 you should downgrade it to
1548 2.05. From the @file{README} at prep.ai.mit.edu:
1551 sed 3.0 has been withdrawn from distribution. It has major revisions,
1552 which mostly seem to be improvements; but it turns out to have bugs too
1553 which cause trouble in some common cases.
1555 Tom Lord won't be able to work fixing the bugs until May. So in the
1556 mean time, we've decided to withdraw sed 3.0 from distribution and make
1557 version 2.05 once again the recommended version.
1560 It has also been observed that the vfork test on Solaris will leave a
1563 @node Q2.0.11, Q2.0.12, Q2.0.10, Installation
1564 @unnumberedsubsec Q2.0.11: XEmacs doesn't resolve hostnames.
1566 This is the result of a long-standing problem with SunOS and the fact
1567 that stock SunOS systems do not ship with DNS resolver code in libc.
1569 @email{ckd@@loiosh.kei.com, Christopher Davis} writes:
1572 That's correct [The SunOS 4.1.3 precompiled binaries don't do name
1573 lookup]. Since Sun figured that everyone used NIS to do name lookups
1574 (that DNS thing was apparently only a passing fad, right?), the stock
1575 SunOS 4.x systems don't have DNS-based name lookups in libc.
1577 This is also why Netscape ships two binaries for SunOS 4.1.x.
1579 The best solution is to compile it yourself; the configure script will
1580 check to see if you've put DNS in the shared libc and will then proceed
1581 to link against the DNS resolver library code.
1584 @node Q2.0.12, Q2.0.13, Q2.0.11, Installation
1585 @unnumberedsubsec Q2.0.12: Why can't I strip XEmacs?
1587 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:
1590 Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The
1591 link gives you a bare-boned emacs (called temacs). temacs is then run,
1592 preloading some of the lisp files. The result is then dumped into a new
1593 executable, named xemacs, which will contain all of the preloaded lisp
1596 Now, during the dump itself, the executable (code+data+symbols) is
1597 written on disk using a special unexec() function. This function is
1598 obviously heavily system dependent. And on some systems, it leads to an
1599 executable which, although valid, cannot be stripped without damage. If
1600 memory serves, this is especially the case for AIX binaries. On other
1601 architectures it might work OK.
1603 The Right Way to strip the emacs binary is to strip temacs prior to
1604 dumping xemacs. This will always work, although you can do that only if
1605 you install from sources (as temacs is @file{not} part of the binary
1609 @email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes:
1616 [ ./configure; make ]
1628 cp src/xemacs /usr/local/bin/xemacs
1631 cp lib-src/DOC-19.16-XEmacs
1635 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
1639 @node Q2.0.13, Q2.0.14, Q2.0.12, Installation
1640 @unnumberedsubsec Q2.0.13: I don't need no steenkin' packages. Do I? (NEW)
1642 Strictly speaking, no. XEmacs will build and install just fine without
1643 any packages installed. However, only the most basic editing functions
1644 will be available with no packages installed, so installing packages is
1645 an essential part of making your installed XEmacs _useful_.
1647 @node Q2.0.14, Q2.1.1, Q2.0.13, Installation
1648 @unnumberedsubsec Q2.0.12: How do I figure out which packages to install? (NEW)
1650 Many people really liked the old way that packages were bundled and do
1651 not want to mess with packages at all. You can grab all the packages at
1652 once like you used to with old XEmacs versions. Download the file
1654 @file{xemacs-sumo.tar.gz}
1656 For an XEmacs compiled with Mule you also need
1658 @file{xemacs-mule-sumo.tar.gz}
1660 from the @file{packages} directory on your XEmacs mirror archive.
1661 N.B. They are called 'Sumo Tarballs' for good reason. They are
1662 currently about 15MB and 2.3MB (gzipped) respectively.
1666 @code{cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xf -}
1668 See README.packages for more detailed installation instructions.
1670 As the Sumo tarballs are not regenerated as often as the individual
1671 packages, it is recommended that you use the automatic package tools
1672 afterwards to pick up any recent updates.
1674 @node Q2.1.1, Q2.1.2, Q2.0.14, Installation
1675 @unnumberedsec 2.1: Trouble Shooting
1676 @unnumberedsubsec Q2.1.1: Help! XEmacs just crashed on me!
1678 First of all, don't panic. Whenever XEmacs crashes, it tries extremely
1679 hard to auto-save all of your files before dying. (The main time that
1680 this will not happen is if the machine physically lost power or if you
1681 killed the XEmacs process using @code{kill -9}). The next time you try
1682 to edit those files, you will be informed that a more recent auto-save
1683 file exists. You can use @kbd{M-x recover-file} to retrieve the
1684 auto-saved version of the file.
1686 You can use the command @kbd{M-x recover-session} after a crash to pick
1687 up where you left off.
1689 Now, XEmacs is not perfect, and there may occasionally be times, or
1690 particular sequences of actions, that cause it to crash. If you can
1691 come up with a reproducible way of doing this (or even if you have a
1692 pretty good memory of exactly what you were doing at the time), the
1693 maintainers would be very interested in knowing about it. Post a
1694 message to comp.emacs.xemacs or send mail to @email{crashes@@xemacs.org}.
1695 Please note that the @samp{crashes} address is exclusively for crash
1698 If at all possible, include a stack backtrace of the core dump that was
1699 produced. This shows where exactly things went wrong, and makes it much
1700 easier to diagnose problems. To do this, you need to locate the core
1701 file (it's called @file{core}, and is usually sitting in the directory
1702 that you started XEmacs from, or your home directory if that other
1703 directory was not writable). Then, go to that directory and execute a
1707 gdb `which xemacs` core
1710 and then issue the command @samp{where} to get the stack backtrace. You
1711 might have to use @code{dbx} or some similar debugger in place of
1712 @code{gdb}. If you don't have any such debugger available, complain to
1713 your system administrator.
1715 It's possible that a core file didn't get produced, in which case you're
1716 out of luck. Go complain to your system administrator and tell him not
1717 to disable core files by default. Also see @ref{Q2.1.15}, for tips and
1718 techniques for dealing with a debugger.
1720 When making a problem report make sure that:
1724 Report @strong{all} of the information output by XEmacs during the
1728 You mention what O/S & Hardware you are running XEmacs on.
1731 What version of XEmacs you are running.
1734 What build options you are using.
1737 If the problem is related to graphics, we will also need to know what
1738 version of the X Window System you are running, and what window manager
1742 If the problem happened on a tty, please include the terminal type.
1745 @node Q2.1.2, Q2.1.3, Q2.1.1, Installation
1746 @unnumberedsubsec Q2.1.2: Cryptic Minibuffer messages.
1748 When I try to use some particular option of some particular package, I
1749 get a cryptic error in the minibuffer.
1751 If you can't figure out what's going on, select Options/General
1752 Options/Debug on Error from the Menubar and then try and make the error
1753 happen again. This will give you a backtrace that may be enlightening.
1754 If not, try reading through this FAQ; if that fails, you could try
1755 posting to comp.emacs.xemacs (making sure to include the backtrace) and
1756 someone may be able to help. If you can identify which Emacs lisp
1757 source file the error is coming from you can get a more detailed stack
1758 backtrace by doing the following:
1762 Visit the .el file in an XEmacs buffer.
1765 Issue the command @kbd{M-x eval-current-buffer}.
1768 Reproduce the error.
1771 Depending on the version of XEmacs, you may either select View->Show
1772 Message Log (recent versions), Edit->Show Messages (some earlier
1773 versions) or Help->Recent Keystrokes/Messages (other earlier versions)
1774 from the menubar to see the most recent messages. This command is bound
1775 to @kbd{C-h l} by default.
1777 @node Q2.1.3, Q2.1.4, Q2.1.2, Installation
1778 @unnumberedsubsec Q2.1.3: Translation Table Syntax messages at Startup
1780 I get tons of translation table syntax error messages during startup.
1781 How do I get rid of them?
1783 There are two causes of this problem. The first usually only strikes
1784 people using the prebuilt binaries. The culprit in both cases is the
1785 file @file{XKeysymDB}.
1789 The binary cannot find the @file{XKeysymDB} file. The location is
1790 hardcoded at compile time so if the system the binary was built on puts
1791 it a different place than your system does, you have problems. To fix,
1792 set the environment variable @var{XKEYSYMDB} to the location of the
1793 @file{XKeysymDB} file on your system or to the location of the one
1794 included with XEmacs which should be at
1798 @file{<xemacs_root_directory>/lib/xemacs-19.16/etc/XKeysymDB}.
1801 The binary is finding the XKeysymDB but it is out-of-date on your system
1802 and does not contain the necessary lines. Either ask your system
1803 administrator to replace it with the one which comes with XEmacs (which
1804 is the stock R6 version and is backwards compatible) or set your
1805 @var{XKEYSYMDB} variable to the location of XEmacs's described above.
1808 @node Q2.1.4, Q2.1.5, Q2.1.3, Installation
1809 @unnumberedsubsec Q2.1.4: Startup warnings about deducing proper fonts?
1811 How can I avoid the startup warnings about deducing proper fonts?
1813 This is highly dependent on your installation, but try with the
1814 following font as your base font for XEmacs and see what it does:
1817 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
1820 More precisely, do the following in your resource file:
1823 Emacs.default.attributeFont: \
1824 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
1827 If you just don't want to see the @samp{*Warnings*} buffer at startup
1828 time, you can set this:
1831 (setq display-warning-minimum-level 'error)
1834 The buffer still exists; it just isn't in your face.
1836 @node Q2.1.5, Q2.1.6, Q2.1.4, Installation
1837 @unnumberedsubsec Q2.1.5: XEmacs cannot connect to my X Terminal!
1839 Help! I can not get XEmacs to display on my Envizex X-terminal!
1841 Try setting the @var{DISPLAY} variable using the numeric IP address of
1842 the host you are running XEmacs from.
1844 @node Q2.1.6, Q2.1.7, Q2.1.5, Installation
1845 @unnumberedsubsec Q2.1.6: XEmacs just locked up my Linux X server!
1847 There have been several reports of the X server locking up under Linux.
1848 In all reported cases removing speedo and scaled fonts from the font
1849 path corrected the problem. This can be done with the command
1852 It is possible that using a font server may also solve the problem.
1854 @node Q2.1.7, Q2.1.8, Q2.1.6, Installation
1855 @unnumberedsubsec Q2.1.7: HP Alt key as Meta.
1857 How can I make XEmacs recognize the Alt key of my HP workstation as a
1860 Put the following line into a file and load it with xmodmap(1) before
1864 remove Mod1 = Mode_switch
1867 @node Q2.1.8, Q2.1.9, Q2.1.7, Installation
1868 @unnumberedsubsec Q2.1.8: got (wrong-type-argument color-instance-p nil)
1870 @email{nataliek@@rd.scitec.com.au, Natalie Kershaw} writes:
1873 I am trying to run xemacs 19.13 under X11R4. Whenever I move the mouse I
1874 get the following error. Has anyone seen anything like this? This
1875 doesn't occur on X11R5.
1879 (error "got (wrong-type-argument color-instance-p nil)
1880 and I don't know why!")
1884 @email{map01kd@@gold.ac.uk, dinos} writes:
1887 I think this is due to undefined resources; You need to define color
1888 backgrounds and foregrounds into your @file{.../app-defaults/Emacs}
1892 *Foreground: Black ;everything will be of black on grey95,
1893 *Background: Grey95 ;unless otherwise specified.
1894 *cursorColor: Red3 ;red3 cursor with grey95 border.
1895 *pointerColor: Red3 ;red3 pointer with grey95 border.
1899 Natalie Kershaw adds:
1902 What fixed the problem was adding some more colors to the X color
1903 database (copying the X11R5 colors over), and also defining the
1904 following resources:
1907 xemacs*cursorColor: black
1908 xemacs*pointerColor: black
1911 With the new colors installed the problem still occurs if the above
1912 resources are not defined.
1914 If the new colors are not present then an additional error occurs on
1915 XEmacs startup, which says @samp{Color Red3} not defined.
1918 @node Q2.1.9, Q2.1.10, Q2.1.8, Installation
1919 @unnumberedsubsec Q2.1.9: XEmacs causes my OpenWindows 3.0 server to crash.
1921 The OpenWindows 3.0 server is incredibly buggy. Your best bet is to
1922 replace it with one from the generic MIT X11 release. You might also
1923 try disabling parts of your @file{init.el}/@file{.emacs}, like those
1924 that enable background pixmaps.
1926 @node Q2.1.10, Q2.1.11, Q2.1.9, Installation
1927 @unnumberedsubsec Q2.1.10: Warnings from incorrect key modifiers.
1929 The following information comes from the @file{PROBLEMS} file that comes
1932 If you're having troubles with HP/UX it is because HP/UX defines the
1933 modifiers wrong in X. Here is a shell script to fix the problem; be
1934 sure that it is run after VUE configures the X server.
1938 xmodmap 2> /dev/null - << EOF
1939 keysym Alt_L = Meta_L
1940 keysym Alt_R = Meta_R
1945 keysym Mode_switch = NoSymbol
1947 keysym Meta_R = Mode_switch
1948 add mod2 = Mode_switch
1952 @node Q2.1.11, Q2.1.12, Q2.1.10, Installation
1953 @unnumberedsubsec Q2.1.11: @samp{Can't instantiate image error...} in toolbar
1956 @email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes:
1958 I just installed the XEmacs (20.4-2) RPMS that I downloaded from
1959 @uref{http://www.xemacs.org/}. Everything works fine, except that when
1960 I place my mouse over the toolbar, it beeps and gives me this message:
1963 Can't instantiate image (probably cached):
1964 [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data
1965 (16 16 <strange control characters> ...
1968 @email{kyle_jones@@wonderworks.com, Kyle Jones} writes:
1970 This is problem specific to some Chips and Technologies video
1971 chips, when running XFree86. Putting
1973 @code{Option "sw_cursor"}
1975 in @file{XF86Config} gets rid of the problem.
1978 @node Q2.1.12, Q2.1.13, Q2.1.11, Installation
1979 @unnumberedsubsec Q2.1.12: Problems with Regular Expressions on DEC OSF1.
1981 I have xemacs 19.13 running on an alpha running OSF1 V3.2 148 and ispell
1982 would not run because it claimed the version number was incorrect
1983 although it was indeed OK. I traced the problem to the regular
1986 @email{douglask@@dstc.edu.au, Douglas Kosovic} writes:
1989 Actually it's a DEC cc optimization bug that screws up the regexp
1992 Rebuilding using the @samp{-migrate} switch for DEC cc (which uses a
1993 different sort of optimization) works fine.
1996 See @file{xemacs-19_13-dunix-3_2c.patch} at the following URL on how to
1997 build with the @samp{-migrate} flag:
2000 @uref{http://www-digital.cern.ch/carney/emacs/emacs.html}
2001 @c Link above, <URL:http://www-digital.cern.ch/carney/emacs/emacs.html> is
2002 @c dead. And the directory `carney' is empty.
2008 NOTE: There have been a variety of other problems reported that are
2009 fixed in this fashion.
2011 @node Q2.1.13, Q2.1.14, Q2.1.12, Installation
2012 @unnumberedsubsec Q2.1.13: HP/UX 10.10 and @code{create_process} failure.
2014 @email{Dave.Carrigan@@ipl.ca, Dave Carrigan} writes:
2017 With XEmacs 19.13 and HP/UX 10.10, anything that relies on the
2018 @code{create_process} function fails. This breaks a lot of things
2019 (shell-mode, compile, ange-ftp, to name a few).
2022 @email{johnson@@dtc.hp.com, Phil Johnson} writes:
2025 This is a problem specific to HP-UX 10.10. It only occurs when XEmacs
2026 is compiled for shared libraries (the default), so you can work around
2027 it by compiling a statically-linked binary (run configure with
2028 @samp{--dynamic=no}).
2030 I'm not sure whether the problem is with a particular shared library or
2031 if it's a kernel problem which crept into 10.10.
2034 @email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
2037 I had a few problems with 10.10. Apparently, some of them were solved by
2038 forcing a static link of libc (manually).
2041 @node Q2.1.14, Q2.1.15, Q2.1.13, Installation
2042 @unnumberedsubsec Q2.1.14: @kbd{C-g} doesn't work for me. Is it broken?
2044 @email{ben@@xemacs.org, Ben Wing} writes:
2047 @kbd{C-g} does work for most people in most circumstances. If it
2048 doesn't, there are only two explanations:
2052 The code is wrapped with a binding of @code{inhibit-quit} to
2053 @code{t}. @kbd{Ctrl-Shift-G} should still work, I think.
2056 SIGIO is broken on your system, but BROKEN_SIGIO isn't defined.
2059 To test #2, try executing @code{(while t)} from the @samp{*scratch*}
2060 buffer. If @kbd{C-g} doesn't interrupt, then you're seeing #2.
2063 @email{terra@@diku.dk, Morten Welinder} writes:
2066 On some (but @emph{not} all) machines a hung XEmacs can be revived by
2067 @code{kill -FPE <pid>}. This is a hack, of course, not a solution.
2068 This technique works on a Sun4 running 4.1.3_U1. To see if it works for
2069 you, start another XEmacs and test with that first. If you get a core
2070 dump the method doesn't work and if you get @samp{Arithmetic error} then
2074 @node Q2.1.15, Q2.1.16, Q2.1.14, Installation
2075 @unnumberedsubsec Q2.1.15: How to Debug an XEmacs problem with a debugger
2077 If XEmacs does crash on you, one of the most productive things you can
2078 do to help get the bug fixed is to poke around a bit with the debugger.
2079 Here are some hints:
2083 First of all, if the crash is at all reproducible, consider very
2084 strongly recompiling your XEmacs with debugging symbols and with no
2085 optimization (e.g. with GCC use the compiler flags @samp{-g -O0} --
2086 that's an "oh" followed by a zero), and with the configure options
2087 @samp{--debug=yes} and @samp{--error-checking=all}. This will make your
2088 XEmacs run somewhat slower but make it a lot more likely to catch the
2089 problem earlier (closer to its source), and a lot easier to determine
2090 what's going on with a debugger.
2093 If you're able to run XEmacs under a debugger and reproduce the crash
2094 (if it's inconvenient to do this because XEmacs is already running or is
2095 running in batch mode as part of a bunch of scripts, consider attaching
2096 to the existing process with your debugger; most debuggers let you do
2097 this by substituting the process ID for the core file when you invoke
2098 the debugger from the command line, or by using the @code{attach}
2099 command or something similar), here are some things you can do:
2102 If XEmacs is hitting an assertion failure, put a breakpoint on
2103 @code{assert_failed()}.
2106 If XEmacs is hitting some weird Lisp error that's causing it to crash
2107 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is
2108 declared static in eval.c.
2111 If XEmacs is outputting lots of X errors, put a breakpoint on
2112 @code{x_error_handler()}; that will tell you which call is causing them.
2115 Internally, you will probably see lots of variables that hold objects of
2116 type @code{Lisp_Object}. These are exactly what they appear to be,
2117 i.e. references to Lisp objects. Printing them out with the debugger
2118 probably won't be too useful---you'll likely just see a number. To
2119 decode them, do this:
2122 call debug_print (OBJECT)
2125 where @var{OBJECT} is whatever you want to decode (it can be a variable,
2126 a function call, etc.). This will print out a readable representation
2127 on the TTY from which the xemacs process was invoked.
2130 If you want to get a Lisp backtrace showing the Lisp call
2134 call debug_backtrace ()
2138 Using @code{debug_print} and @code{debug_backtrace} has two
2139 disadvantages - it can only be used with a running xemacs process, and
2140 it cannot display the internal C structure of a Lisp Object. Even if
2141 all you've got is a core dump, all is not lost.
2143 If you're using GDB, there are some macros in the file
2144 @file{src/.gdbinit} in the XEmacs source distribution that should make
2145 it easier for you to decode Lisp objects. This file is automatically
2146 read by gdb if gdb is run in the directory where xemacs was built, and
2147 contains these useful macros to inspect the state of xemacs:
2151 Usage: pobj lisp_object @*
2152 Print the internal C representation of a lisp object.
2155 Usage: xtype lisp_object @*
2156 Print the Lisp type of a lisp object.
2160 Print the current Lisp stack trace.
2161 Requires a running xemacs process.
2164 Usage: ldp lisp_object @*
2165 Print a Lisp Object value using the Lisp printer.
2166 Requires a running xemacs process.
2169 Usage: run-temacs @*
2170 Run temacs interactively, like xemacs.
2171 Use this with debugging tools (like purify) that cannot deal with dumping,
2172 or when temacs builds successfully, but xemacs does not.
2175 Usage: dump-temacs @*
2176 Run the dumping part of the build procedure.
2177 Use when debugging temacs, not xemacs!
2178 Use this when temacs builds successfully, but xemacs does not.
2181 Usage: check-xemacs @*
2182 Run the test suite. Equivalent to 'make check'.
2185 Usage: check-temacs @*
2186 Run the test suite on temacs. Equivalent to 'make check-temacs'.
2187 Use this with debugging tools (like purify) that cannot deal with dumping,
2188 or when temacs builds successfully, but xemacs does not.
2191 If you are using Sun's @file{dbx} debugger, there is an equivalent file
2192 @file{src/.dbxrc}, which defines the same commands for dbx.
2195 If you're using a debugger to get a C stack backtrace and you're seeing
2196 stack traces with some of the innermost frames mangled, it may be due to
2197 dynamic linking. (This happens especially under Linux.) Consider
2198 reconfiguring with @samp{--dynamic=no}. Also, sometimes (again under
2199 Linux), stack backtraces of core dumps will have the frame where the
2200 fatal signal occurred mangled; if you can obtain a stack trace while
2201 running the XEmacs process under a debugger, the stack trace should be
2204 @email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so version 1.8
2205 if dynamic linking and debugging is a problem on Linux.
2208 If you're using a debugger to get a C stack backtrace and you're
2209 getting a completely mangled and bogus stack trace, it's probably due to
2210 one of the following:
2214 Your executable has been stripped. Bad news. Tell your sysadmin not to
2215 do this---it doesn't accomplish anything except to save a bit of disk
2216 space, and makes debugging much much harder.
2219 Your stack is getting trashed. Debugging this is hard; you have to do a
2220 binary-search type of narrowing down where the crash occurs, until you
2221 figure out exactly which line is causing the problem. Of course, this
2222 only works if the bug is highly reproducible.
2225 If your stack trace has exactly one frame in it, with address 0x0, this
2226 could simply mean that XEmacs attempted to execute code at that address,
2227 e.g. through jumping to a null function pointer. Unfortunately, under
2228 those circumstances, GDB under Linux doesn't know how to get a stack
2229 trace. (Yes, this is the third Linux-related problem I've mentioned. I
2230 have no idea why GDB under Linux is so bogus. Complain to the GDB
2231 authors, or to comp.os.linux.development.system). Again, you'll have to
2232 use the narrowing-down process described above.
2235 You will get a Lisp backtrace output when XEmacs crashes, so you'll have
2241 If you compile with the newer gcc variants gcc-2.8 or egcs, you will
2242 also need gdb 4.17 or above. Earlier releases of gdb can't handle the
2243 debug information generated by the newer compilers.
2246 In versions of XEmacs before 21.2.27, @file{src/.gdbinit} was named
2247 @file{src/gdbinit}. This had the disadvantage of not being sourced
2248 automatically by gdb, so you had to set that up yourself.
2252 @node Q2.1.16, Q2.1.17, Q2.1.15, Installation
2253 @unnumberedsubsec Q2.1.16: XEmacs crashes in @code{strcat} on HP/UX 10
2255 From the problems database (through
2256 the former address http://support.mayfield.hp.com/):
2259 Problem Report: 5003302299
2262 System/Model: 9000/700
2263 Product Name: HPUX S800 10.0X
2264 Product Vers: 9245XB.10.00
2266 Description: strcat(3C) may read beyond
2267 end of source string, can cause SIGSEGV
2270 *** PROBLEM TEXT ***
2271 strcat(3C) may read beyond the source string onto an unmapped page,
2272 causing a segmentation violation.
2275 @node Q2.1.17, Q2.1.18, Q2.1.16, Installation
2276 @unnumberedsubsec Q2.1.17: @samp{Marker does not point anywhere}
2278 As with other errors, set @code{debug-on-error} to @code{t} to get the
2279 backtrace when the error occurs. Specifically, two problems have been
2280 reported (and fixed).
2284 A problem with line-number-mode in XEmacs 19.14 affected a large number
2285 of other packages. If you see this error message, turn off
2289 A problem with some early versions of Gnus 5.4 caused this error.
2293 @node Q2.1.18, Q2.1.19, Q2.1.17, Installation
2294 @unnumberedsubsec Q2.1.18: XEmacs is outputting lots of X errors.
2296 If this is happening, we would very much like to know what's causing
2297 them. To find this out, see @ref{Q2.1.15}. Try to get both a C and Lisp
2298 backtrace, and send them to @email{xemacs-beta@@xemacs.org}.
2300 @node Q2.1.19, Q2.1.20, Q2.1.18, Installation
2301 @unnumberedsubsec Q2.1.19: XEmacs does not follow the local timezone.
2303 When using one of the prebuilt binaries many users have observed that
2304 XEmacs uses the timezone under which it was built, but not the timezone
2305 under which it is running. The solution is to add:
2308 (set-time-zone-rule "MET")
2311 to your @file{init.el}/@file{.emacs} or the @file{site-start.el} file if
2312 you can. Replace @code{MET} with your local timezone.
2314 @node Q2.1.20, Q2.1.21, Q2.1.19, Installation
2315 @unnumberedsubsec Q2.1.20: @samp{Symbol's function definition is void: hkey-help-show.}
2317 This is a problem with a partially loaded hyperbole. Try adding:
2320 (require 'hmouse-drv)
2323 where you load hyperbole and the problem should go away.
2325 @node Q2.1.21, Q2.1.22, Q2.1.20, Installation
2326 @unnumberedsubsec Q2.1.21: [This question intentionally left blank]
2328 @node Q2.1.22, Q2.1.23, Q2.1.21, Installation
2329 @unnumberedsubsec Q2.1.22: XEmacs seems to take a really long time to do some things
2331 @email{dmoore@@ucsd.edu, David Moore} writes:
2334 Two things you can do:
2338 When you see it going mad like this, you might want to use gdb from an
2339 'xterm' to attach to the running process and get a stack trace. To do
2343 gdb /path/to/xemacs/xemacs ####
2346 Where @code{####} is the process id of your xemacs, instead of
2347 specifying the core. When gdb attaches, the xemacs will stop [1] and
2348 you can type `where' in gdb to get a stack trace as usual. To get
2349 things moving again, you can just type `quit' in gdb. It'll tell you
2350 the program is running and ask if you want to quit anyways. Say 'y' and
2351 it'll quit and have your emacs continue from where it was at.
2355 Turn on debug-on-quit early on. When you think things are going slow
2356 hit C-g and it may pop you in the debugger so you can see what routine
2357 is running. Press `c' to get going again.
2359 debug-on-quit doesn't work if something's turned on inhibit-quit or in
2360 some other strange cases.
2363 @node Q2.1.23, Q2.1.24, Q2.1.22, Installation
2364 @unnumberedsubsec Q2.1.23: Movemail on Linux does not work for XEmacs 19.15 and later.
2366 Movemail used to work fine in 19.14 but has stopped working in 19.15
2367 and 20.x. I am using Linux.
2369 @email{steve@@xemacs.org, SL Baur} writes:
2372 Movemail on Linux used to default to using flock file locking. With
2373 19.15 and later versions it now defaults to using @code{.lock} file
2374 locking. If this is not appropriate for your system, edit src/s/linux.h
2375 and uncomment the line that reads:
2378 #define MAIL_USE_FLOCK
2382 @node Q2.1.24, Q2.1.25, Q2.1.23, Installation
2383 @unnumberedsubsec Q2.1.24: XEmacs won't start without network. (NEW)
2385 If XEmacs starts when you're on the network, but fails when you're not
2386 on the network, you may be missing a "localhost" entry in your
2387 @file{/etc/hosts} file. The file should contain an entry like:
2393 Add that line, and XEmacs will be happy.
2395 @node Q2.1.25, , Q2.1.24, Installation
2396 @unnumberedsubsec Q2.1.25:: After upgrading, XEmacs won't do `foo' any more! (NEW)
2398 You have been used to doing `foo', but now when you invoke it (or click
2399 the toolbar button or select the menu item), nothing (or an error)
2400 happens. The simplest explanation is that you are missing a package
2401 that is essential to you. You can either track it down and install it
2402 (there is a list of packages and brief descriptions of their contents in
2403 @file{etc/PACKAGES}), or install the `Sumo Tarball' (@pxref{Q2.0.14}).
2405 @c #### should xref to XEmacs manual here
2407 @node Customization, Subsystems, Installation, Top
2408 @unnumbered 3 Customization and Options
2410 This is part 3 of the XEmacs Frequently Asked Questions list. This
2411 section is devoted to Customization and screen settings.
2414 Customization---Emacs Lisp and @file{init.el}/@file{.emacs}:
2415 * Q3.0.1:: What version of Emacs am I running?
2416 * Q3.0.2:: How do I evaluate Elisp expressions?
2417 * Q3.0.3:: @code{(setq tab-width 6)} behaves oddly.
2418 * Q3.0.4:: How can I add directories to the @code{load-path}?
2419 * Q3.0.5:: How to check if a lisp function is defined?
2420 * Q3.0.6:: Can I force the output of @code{(face-list)} to a buffer?
2421 * Q3.0.7:: Font selections don't get saved after @code{Save Options}.
2422 * Q3.0.8:: How do I make a single minibuffer frame?
2423 * Q3.0.9:: What is @code{Customize}?
2425 X Window System & Resources:
2426 * Q3.1.1:: Where is a list of X resources?
2427 * Q3.1.2:: How can I detect a color display?
2428 * Q3.1.3:: [This question intentionally left blank]
2429 * Q3.1.4:: [This question intentionally left blank]
2430 * Q3.1.5:: How can I get the icon to just say @samp{XEmacs}?
2431 * Q3.1.6:: How can I have the window title area display the full path?
2432 * Q3.1.7:: @samp{xemacs -name junk} doesn't work?
2433 * Q3.1.8:: @samp{-iconic} doesn't work.
2435 Textual Fonts & Colors:
2436 * Q3.2.1:: How can I set color options from @file{init.el}/@file{.emacs}?
2437 * Q3.2.2:: How do I set the text, menu and modeline fonts?
2438 * Q3.2.3:: How can I set the colors when highlighting a region?
2439 * Q3.2.4:: How can I limit color map usage?
2440 * Q3.2.5:: My tty supports color, but XEmacs doesn't use them.
2441 * Q3.2.6:: Can I have pixmap backgrounds in XEmacs?
2444 * Q3.3.1:: How can I make the modeline go away?
2445 * Q3.3.2:: How do you have XEmacs display the line number in the modeline?
2446 * Q3.3.3:: How do I get XEmacs to put the time of day on the modeline?
2447 * Q3.3.4:: How do I turn off current chapter from AUC TeX modeline?
2448 * Q3.3.5:: How can one change the modeline color based on the mode used?
2450 3.4 Multiple Device Support:
2451 * Q3.4.1:: How do I open a frame on another screen of my multi-headed display?
2452 * Q3.4.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
2455 * Q3.5.1:: How can I bind complex functions (or macros) to keys?
2456 * Q3.5.2:: How can I stop down-arrow from adding empty lines to the bottom of my buffers?
2457 * Q3.5.3:: How do I bind C-. and C-; to scroll one line up and down?
2458 * Q3.5.4:: Globally binding @kbd{Delete}?
2459 * Q3.5.5:: Scrolling one line at a time.
2460 * Q3.5.6:: How to map @kbd{Help} key alone on Sun type4 keyboard?
2461 * Q3.5.7:: How can you type in special characters in XEmacs?
2462 * Q3.5.8:: [This question intentionally left blank]
2463 * Q3.5.9:: How do I make the Delete key delete forward?
2464 * Q3.5.10:: Can I turn on @dfn{sticky} modifier keys?
2465 * Q3.5.11:: How do I map the arrow keys?
2468 * Q3.6.1:: Is there a way to make the bar cursor thicker?
2469 * Q3.6.2:: Is there a way to get back the old block cursor where the cursor covers the character in front of the point?
2470 * Q3.6.3:: Can I make the cursor blink?
2472 The Mouse and Highlighting:
2473 * Q3.7.1:: How can I turn off Mouse pasting?
2474 * Q3.7.2:: How do I set control/meta/etc modifiers on mouse buttons?
2475 * Q3.7.3:: Clicking the left button does not do anything in buffer list.
2476 * Q3.7.4:: How can I get a list of buffers when I hit mouse button 3?
2477 * Q3.7.5:: Why does cut-and-paste not work between XEmacs and a cmdtool?
2478 * Q3.7.6:: How I can set XEmacs up so that it pastes where the text cursor is?
2479 * Q3.7.7:: How do I select a rectangular region?
2480 * Q3.7.8:: Why does @kbd{M-w} take so long?
2482 The Menubar and Toolbar:
2483 * Q3.8.1:: How do I get rid of the menu (or menubar)?
2484 * Q3.8.2:: Can I customize the basic menubar?
2485 * Q3.8.3:: How do I control how many buffers are listed in the menu @code{Buffers} list?
2486 * Q3.8.4:: Resources like @code{Emacs*menubar*font} are not working?
2487 * Q3.8.5:: How can I bind a key to a function to toggle the toolbar?
2490 * Q3.9.1:: How can I disable the scrollbar?
2491 * Q3.9.2:: How can one use resources to change scrollbar colors?
2492 * Q3.9.3:: Moving the scrollbar can move the point; can I disable this?
2493 * Q3.9.4:: How can I turn off automatic horizontal scrolling in specific modes?
2496 * Q3.10.1:: How can I turn off or change highlighted selections?
2497 * Q3.10.2:: How do I get that typing on an active region removes it?
2498 * Q3.10.3:: Can I turn off the highlight during isearch?
2499 * Q3.10.4:: How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
2500 * Q3.10.5:: The region disappears when I hit the end of buffer while scrolling.
2503 @node Q3.0.1, Q3.0.2, Customization, Customization
2504 @unnumberedsec 3.0: Customization -- Emacs Lisp and @file{init.el}/@file{.emacs}
2505 @unnumberedsubsec Q3.0.1: What version of Emacs am I running?
2507 How can @file{init.el}/@file{.emacs} determine which of the family of
2510 To determine if you are currently running GNU Emacs 18, GNU Emacs 19,
2511 XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the
2512 example given in @file{etc/sample.init.el} (@file{etc/sample.emacs} in
2513 XEmacs versions prior to 21.4). There are other nifty things in there
2516 For all new code, all you really need to do is:
2519 (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
2522 @node Q3.0.2, Q3.0.3, Q3.0.1, Customization
2523 @unnumberedsubsec Q3.0.2: How can I evaluate Emacs-Lisp expressions?
2525 I know I can evaluate Elisp expressions from @code{*scratch*} buffer
2526 with @kbd{C-j} after the expression. How do I do it from another
2529 Press @kbd{M-:} (the default binding of @code{eval-expression}), and
2530 enter the expression to the minibuffer.
2532 @node Q3.0.3, Q3.0.4, Q3.0.2, Customization
2533 @unnumberedsubsec Q3.0.3: @code{(setq tab-width 6)} behaves oddly.
2535 If you put @code{(setq tab-width 6)} in your
2536 @file{init.el}/@file{.emacs} file it does not work! Is there a reason
2537 for this? If you do it at the EVAL prompt it works fine!! How strange.
2539 Use @code{setq-default} instead, since @code{tab-width} is
2542 @node Q3.0.4, Q3.0.5, Q3.0.3, Customization
2543 @unnumberedsubsec Q3.0.4: How can I add directories to the @code{load-path}?
2545 Here are two ways to do that, one that puts your directories at the
2546 front of the load-path, the other at the end:
2549 ;;; Add things at the beginning of the load-path, do not add
2550 ;;; duplicate directories:
2551 (pushnew "bar" load-path :test 'equal)
2553 (pushnew "foo" load-path :test 'equal)
2555 ;;; Add things at the end, unconditionally
2556 (setq load-path (nconc load-path '("foo" "bar")))
2559 @email{keithh@@nortel.ca, keith (k.p.) hanlan} writes:
2562 To add directories using Unix shell metacharacters use
2563 @file{expand-file-name} like this:
2566 (push (expand-file-name "~keithh/.emacsdir") load-path)
2570 @node Q3.0.5, Q3.0.6, Q3.0.4, Customization
2571 @unnumberedsubsec Q3.0.5: How to check if a lisp function is defined?
2573 Use the following elisp:
2579 It's almost always a mistake to test @code{emacs-version} or any similar
2582 Instead, use feature-tests, such as @code{featurep}, @code{boundp},
2583 @code{fboundp}, or even simple behavioral tests, eg.:
2586 (defvar foo-old-losing-code-p
2587 (condition-case nil (progn (losing-code t) nil)
2588 (wrong-number-of-arguments t)))
2591 There is an incredible amount of broken code out there which could work
2592 much better more often in more places if it did the above instead of
2593 trying to divine its environment from the value of one variable.
2595 @node Q3.0.6, Q3.0.7, Q3.0.5, Customization
2596 @unnumberedsubsec Q3.0.6: Can I force the output of @code{(face-list)} to a buffer?
2598 It would be good having it in a buffer, as the output of
2599 @code{(face-list)} is too wide to fit to a minibuffer.
2601 Evaluate the expression in the @samp{*scratch*} buffer with point after
2602 the rightmost paren and typing @kbd{C-j}.
2604 If the minibuffer smallness is the only problem you encounter, you can
2605 simply press @kbd{C-h l} to get the former minibuffer contents in a
2608 @node Q3.0.7, Q3.0.8, Q3.0.6, Customization
2609 @unnumberedsubsec Q3.0.7: Font selections in don't get saved after @code{Save Options}.
2611 @email{mannj@@ll.mit.edu, John Mann} writes:
2614 You have to go to Options->Frame Appearance and unselect
2615 @samp{Frame-Local Font Menu}. If this option is selected, font changes
2616 are only applied to the @emph{current} frame and do @emph{not} get saved
2617 when you save options.
2620 Also, set the following in your @file{init.el}/@file{.emacs}:
2623 (setq options-save-faces t)
2626 @node Q3.0.8, Q3.0.9, Q3.0.7, Customization
2627 @unnumberedsubsec Q3.0.8: How do I get a single minibuffer frame?
2629 @email{acs@@acm.org, Vin Shelton} writes:
2632 (setq initial-frame-plist '(minibuffer nil))
2633 (setq default-frame-plist '(minibuffer nil))
2634 (setq default-minibuffer-frame
2639 menubar-visible-p nil
2640 default-toolbar-visible-p nil
2644 has-modeline-p nil)))
2645 (frame-notice-user-settings)
2648 @strong{Please note:} The single minibuffer frame may not be to everyone's
2649 taste, and there any number of other XEmacs options settings that may
2650 make it difficult or inconvenient to use.
2652 @node Q3.0.9, Q3.1.1, Q3.0.8, Customization
2653 @unnumberedsubsec Q3.0.9: What is @code{Customize}?
2655 Starting with XEmacs 20.2 there is new system 'Customize' for customizing
2658 You can access @code{Customize} from the @code{Options} menu
2659 or invoking one of customize commands by typing eg.
2660 @kbd{M-x customize}, @kbd{M-x customize-face},
2661 @kbd{M-x customize-variable} or @kbd{M-x customize-apropos}.
2663 Starting with XEmacs 20.3 there is also new `browser' mode for Customize.
2664 Try it out with @kbd{M-x customize-browse}
2666 @node Q3.1.1, Q3.1.2, Q3.0.9, Customization
2667 @unnumberedsec 3.1: X Window System & Resources
2668 @unnumberedsubsec Q3.1.1: Where is a list of X resources?
2670 Search through the @file{NEWS} file for @samp{X Resources}. A fairly
2671 comprehensive list is given after it.
2673 In addition, an @file{app-defaults} file is supplied,
2674 @file{etc/Emacs.ad} listing the defaults. The file
2675 @file{etc/sample.Xdefaults} gives a set of defaults that you might
2676 consider. It is essentially the same as @file{etc/Emacs.ad} but some
2677 entries are slightly altered. Be careful about installing the contents
2678 of this file into your @file{.Xdefaults} or @file{.Xresources} file if
2679 you use GNU Emacs under X11 as well.
2681 @node Q3.1.2, Q3.1.3, Q3.1.1, Customization
2682 @unnumberedsubsec Q3.1.2: How can I detect a color display?
2684 You can test the return value of the function @code{(device-class)}, as
2688 (when (eq (device-class) 'color)
2689 (set-face-foreground 'font-lock-comment-face "Grey")
2690 (set-face-foreground 'font-lock-string-face "Red")
2695 @node Q3.1.3, Q3.1.4, Q3.1.2, Customization
2696 @unnumberedsubsec Q3.1.3: [This question intentionally left blank]
2698 @node Q3.1.4, Q3.1.5, Q3.1.3, Customization
2699 @unnumberedsubsec Q3.1.4: [This question intentionally left blank]
2701 @node Q3.1.5, Q3.1.6, Q3.1.4, Customization
2702 @unnumberedsubsec Q3.1.5: How can I get the icon to just say @samp{XEmacs}?
2704 I'd like the icon to just say @samp{XEmacs}, and not include the name of
2705 the current file in it.
2707 Add the following line to your @file{init.el}/@file{.emacs}:
2710 (setq frame-icon-title-format "XEmacs")
2713 @node Q3.1.6, Q3.1.7, Q3.1.5, Customization
2714 @unnumberedsubsec Q3.1.6: How can I have the window title area display the full path?
2716 I'd like to have the window title area display the full directory/name
2717 of the current buffer file and not just the name.
2719 Add the following line to your @file{init.el}/@file{.emacs}:
2722 (setq frame-title-format "%S: %f")
2725 A more sophisticated title might be:
2728 (setq frame-title-format
2729 '("%S: " (buffer-file-name "%f"
2730 (dired-directory dired-directory "%b"))))
2733 That is, use the file name, or the dired-directory, or the buffer name.
2735 @node Q3.1.7, Q3.1.8, Q3.1.6, Customization
2736 @unnumberedsubsec Q3.1.7: @samp{xemacs -name junk} doesn't work?
2738 When I run @samp{xterm -name junk}, I get an xterm whose class name
2739 according to xprop, is @samp{junk}. This is the way it's supposed to
2740 work, I think. When I run @samp{xemacs -name junk} the class name is
2741 not set to @samp{junk}. It's still @samp{emacs}. What does
2742 @samp{xemacs -name} really do? The reason I ask is that my window
2743 manager (fvwm) will make a window sticky and I use XEmacs to read my
2744 mail. I want that XEmacs window to be sticky, without having to use the
2745 window manager's function to set the window sticky. What gives?
2747 @samp{xemacs -name} sets the application name for the program (that is,
2748 the thing which normally comes from @samp{argv[0]}). Using @samp{-name}
2749 is the same as making a copy of the executable with that new name. The
2750 @code{WM_CLASS} property on each frame is set to the frame-name, and the
2751 application-class. So, if you did @samp{xemacs -name FOO} and then
2752 created a frame named @var{BAR}, you'd get an X window with WM_CLASS =
2753 @code{( "BAR", "Emacs")}. However, the resource hierarchy for this
2757 Name: FOO .shell .container .BAR
2758 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
2761 instead of the default
2764 Name: xemacs.shell .container .emacs
2765 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
2769 It is arguable that the first element of WM_CLASS should be set to the
2770 application-name instead of the frame-name, but I think that's less
2771 flexible, since it does not give you the ability to have multiple frames
2772 with different WM_CLASS properties. Another possibility would be for
2773 the default frame name to come from the application name instead of
2774 simply being @samp{emacs}. However, at this point, making that change
2775 would be troublesome: it would mean that many users would have to make
2776 yet another change to their resource files (since the default frame name
2777 would suddenly change from @samp{emacs} to @samp{xemacs}, or whatever
2778 the executable happened to be named), so we'd rather avoid it.
2780 To make a frame with a particular name use:
2783 (make-frame '((name . "the-name")))
2786 @node Q3.1.8, Q3.2.1, Q3.1.7, Customization
2787 @unnumberedsubsec Q3.1.8: @samp{-iconic} doesn't work.
2789 When I start up XEmacs using @samp{-iconic} it doesn't work right.
2790 Using @samp{-unmapped} on the command line, and setting the
2791 @code{initiallyUnmapped} X Resource don't seem to help much either...
2793 @email{ben@@xemacs.org, Ben Wing} writes:
2796 Ugh, this stuff is such an incredible mess that I've about given up
2797 getting it to work. The principal problem is numerous window-manager
2801 @node Q3.2.1, Q3.2.2, Q3.1.8, Customization
2802 @unnumberedsec 3.2: Textual Fonts & Colors
2803 @unnumberedsubsec Q3.2.1: How can I set color options from @file{init.el}/@file{.emacs}?
2805 How can I set the most commonly used color options from my
2806 @file{init.el}/@file{.emacs} instead of from my @file{.Xdefaults}?
2811 (set-face-background 'default "bisque") ; frame background
2812 (set-face-foreground 'default "black") ; normal text
2813 (set-face-background 'zmacs-region "red") ; When selecting w/
2815 (set-face-foreground 'zmacs-region "yellow")
2816 (set-face-font 'default "*courier-bold-r*120-100-100*")
2817 (set-face-background 'highlight "blue") ; Ie when selecting
2819 (set-face-foreground 'highlight "yellow")
2820 (set-face-background 'modeline "blue") ; Line at bottom
2822 (set-face-foreground 'modeline "white")
2823 (set-face-font 'modeline "*bold-r-normal*140-100-100*")
2824 (set-face-background 'isearch "yellow") ; When highlighting
2826 (set-face-foreground 'isearch "red")
2827 (setq x-pointer-foreground-color "black") ; Adds to bg color,
2829 (setq x-pointer-background-color "blue") ; This is color
2834 @node Q3.2.2, Q3.2.3, Q3.2.1, Customization
2835 @unnumberedsubsec Q3.2.2: How do I set the text, menu and modeline fonts?
2837 Note that you should use @samp{Emacs.} and not @samp{Emacs*} when
2838 setting face values.
2840 In @file{.Xdefaults}:
2843 Emacs.default.attributeFont: -*-*-medium-r-*-*-*-120-*-*-m-*-*-*
2844 Emacs*menubar*font: fixed
2845 Emacs.modeline.attributeFont: fixed
2848 This is confusing because modeline is a face, and can be found listed
2849 with all faces in the current mode by using @kbd{M-x set-face-font
2850 (enter) ?}. It uses the face specification of @code{attributeFont},
2851 while menubar is a normal X thing that uses the specification
2852 @code{font}. With Motif it may be necessary to use @code{fontList}
2853 instead of @code{font}.
2855 @node Q3.2.3, Q3.2.4, Q3.2.2, Customization
2856 @unnumberedsubsec Q3.2.3: How can I set the colors when highlighting a region?
2858 How can I set the background/foreground colors when highlighting a
2861 You can change the face @code{zmacs-region} either in your
2865 Emacs.zmacs-region.attributeForeground: firebrick
2866 Emacs.zmacs-region.attributeBackground: lightseagreen
2869 or in your @file{init.el}/@file{.emacs}:
2872 (set-face-background 'zmacs-region "red")
2873 (set-face-foreground 'zmacs-region "yellow")
2876 @node Q3.2.4, Q3.2.5, Q3.2.3, Customization
2877 @unnumberedsubsec Q3.2.4: How can I limit color map usage?
2879 I'm using Netscape (or another color grabber like XEmacs);
2880 is there any way to limit the number of available colors in the color map?
2882 Answer: No, but you can start Netscape before XEmacs, and it will use
2883 the closest available color if the colormap is full. You can also limit
2884 the number of colors Netscape uses, using the flags -mono, -ncols <#> or
2885 -install (for mono, limiting to <#> colors, or for using a private color
2888 If you have the money, another solution would be to use a truecolor or
2891 @node Q3.2.5, Q3.2.6, Q3.2.4, Customization
2892 @unnumberedsubsec Q3.2.5: My tty supports color, but XEmacs doesn't use them.
2894 XEmacs tries to automatically determine whether your tty supports color,
2895 but sometimes guesses wrong. In that case, you can make XEmacs Do The
2896 Right Thing using this Lisp code:
2899 (if (eq 'tty (device-type))
2900 (set-device-class nil 'color))
2903 @node Q3.2.6, Q3.3.1, Q3.2.5, Customization
2904 @unnumberedsubsec Q3.2.6: Can I have pixmap backgrounds in XEmacs?
2906 @email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes:
2909 There are several ways to do it. For example, you could specify a
2910 default pixmap image to use in your @file{~/.Xresources}, e.g.,
2914 Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm
2918 and then reload ~/.Xresources and restart XEmacs. Alternatively,
2919 since each face can have its own pixmap background, a better way
2920 would be to set a face's pixmap within your XEmacs init file, e.g.,
2923 (set-face-background-pixmap 'default "/path/to/image.xpm")
2924 (set-face-background-pixmap 'bold "/path/to/another_image.xpm")
2927 and so on. You can also do this interactively via @kbd{M-x edit-faces}.
2931 @node Q3.3.1, Q3.3.2, Q3.2.6, Customization
2932 @unnumberedsec 3.3: The Modeline
2933 @unnumberedsubsec Q3.3.1: How can I make the modeline go away?
2936 (set-specifier has-modeline-p nil)
2939 @c Starting with XEmacs 19.14 the modeline responds to mouse clicks, so if
2940 @c you haven't liked or used the modeline in the past, you might want to
2941 @c try the new version out.
2943 @node Q3.3.2, Q3.3.3, Q3.3.1, Customization
2944 @unnumberedsubsec Q3.3.2: How do you have XEmacs display the line number in the modeline?
2946 Add the following line to your @file{init.el}/@file{.emacs} file to
2947 display the line number:
2950 (line-number-mode 1)
2953 Use the following to display the column number:
2956 (column-number-mode 1)
2959 Or select from the @code{Options} menu
2963 @code{Advanced (Customize)->Emacs->Editing->Basics->Line Number Mode}
2968 @code{Advanced (Customize)->Emacs->Editing->Basics->Column Number Mode}
2970 Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
2972 @node Q3.3.3, Q3.3.4, Q3.3.2, Customization
2973 @unnumberedsubsec Q3.3.3: How do I get XEmacs to put the time of day on the modeline?
2975 Add the following line to your @file{init.el}/@file{.emacs} file to
2982 See @code{Customize} from the @code{Options} menu for customization.
2984 @node Q3.3.4, Q3.3.5, Q3.3.3, Customization
2985 @unnumberedsubsec Q3.3.4: How do I turn off current chapter from AUC TeX modeline?
2987 With AUC TeX, fast typing is hard because the current chapter, section
2988 etc. are given in the modeline. How can I turn this off?
2990 It's not AUC TeX, it comes from @code{func-menu} in @file{func-menu.el}.
2992 @c Add this code to your @file{init.el}/@file{.emacs} to turn it off:
2995 @c (setq fume-display-in-modeline-p nil)
2998 @c Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
3002 @c (add-hook 'TeX-mode-hook
3003 @c '(lambda () (setq fume-display-in-modeline-p nil)))
3006 @email{dhughes@@origin-at.co.uk, David Hughes} writes:
3009 Try this; you'll still get the function name displayed in the modeline,
3010 but it won't attempt to keep track when you modify the file. To refresh
3011 when it gets out of synch, you simply need click on the @samp{Rescan
3012 Buffer} option in the function-menu.
3015 (setq-default fume-auto-rescan-buffer-p nil)
3019 @node Q3.3.5, Q3.4.1, Q3.3.4, Customization
3020 @unnumberedsubsec Q3.3.5: How can one change the modeline color based on the mode used?
3022 You can use something like the following:
3025 (add-hook 'lisp-mode-hook
3027 (set-face-background 'modeline "red" (current-buffer))))
3030 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
3031 colors change from the default set in your @file{init.el}/@file{.emacs}.
3032 The change will only be made in the buffer you just entered (which
3033 contains the Lisp file you are editing) and will not affect the modeline
3034 colors anywhere else.
3040 @item The hook is the mode name plus @code{-hook}. eg. c-mode-hook,
3041 c++-mode-hook, emacs-lisp-mode-hook (used for your
3042 @file{init.el}/@file{.emacs} or a @file{xx.el} file),
3043 lisp-interaction-mode-hook (the @samp{*scratch*} buffer),
3044 text-mode-hook, etc.
3047 Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)},
3048 otherwise you will erase anything that anybody has already put on the
3052 You can also do @code{(set-face-font 'modeline @var{font})},
3053 eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*"
3054 (current-buffer))} if you wish the modeline font to vary based on the
3058 There are additional modeline faces, @code{modeline-buffer-id},
3059 @code{modeline-mousable}, and @code{modeline-mousable-minor-mode}, which
3060 you may want to customize.
3062 @node Q3.4.1, Q3.4.2, Q3.3.5, Customization
3063 @unnumberedsec 3.4: Multiple Device Support
3064 @unnumberedsubsec Q3.4.1: How do I open a frame on another screen of my multi-headed display?
3066 Use the command @kbd{M-x make-frame-on-display}. This command is also
3067 on the File menu in the menubar.
3069 The command @code{make-frame-on-tty} also exists, which will establish a
3070 connection to any tty-like device. Opening the TTY devices should be
3071 left to @code{gnuclient}, though.
3073 @node Q3.4.2, Q3.5.1, Q3.4.1, Customization
3074 @unnumberedsubsec Q3.4.2: Can I really connect to a running XEmacs after calling up over a modem? How?
3076 Yes. Use @code{gnuclient -nw}. (Prior to 20.3, use the @code{gnuattach}
3077 program supplied with XEmacs instead.)
3079 Also see @ref{Q5.0.12}.
3081 @node Q3.5.1, Q3.5.2, Q3.4.2, Customization
3082 @unnumberedsec 3.5: The Keyboard
3083 @unnumberedsubsec Q3.5.1: How can I bind complex functions (or macros) to keys?
3085 As an example, say you want the @kbd{paste} key on a Sun keyboard to
3086 insert the current Primary X selection at point. You can accomplish this
3090 (define-key global-map [f18] 'x-insert-selection)
3093 However, this only works if there is a current X selection (the
3094 selection will be highlighted). The functionality I like is for the
3095 @kbd{paste} key to insert the current X selection if there is one,
3096 otherwise insert the contents of the clipboard. To do this you need to
3097 pass arguments to @code{x-insert-selection}. This is done by wrapping
3098 the call in a 'lambda form:
3101 (global-set-key [f18]
3102 (lambda () (interactive) (x-insert-selection t nil)))
3105 This binds the f18 key to a @dfn{generic} functional object. The
3106 interactive spec is required because only interactive functions can be
3109 For the FAQ example you could use:
3112 (global-set-key [(control ?.)]
3113 (lambda () (interactive) (scroll-up 1)))
3114 (global-set-key [(control ?;)]
3115 (lambda () (interactive) (scroll-up -1)))
3118 This is fine if you only need a few functions within the lambda body.
3119 If you're doing more it's cleaner to define a separate function as in
3120 question 3.5.3 (@pxref{Q3.5.3}).
3122 @node Q3.5.2, Q3.5.3, Q3.5.1, Customization
3123 @unnumberedsubsec Q3.5.2: How can I stop down-arrow from adding empty lines to the bottom of my buffers?
3125 Add the following line to your @file{init.el}/@file{.emacs} file:
3128 (setq next-line-add-newlines nil)
3131 This has been the default setting in XEmacs for some time.
3133 @node Q3.5.3, Q3.5.4, Q3.5.2, Customization
3134 @unnumberedsubsec Q3.5.3: How do I bind C-. and C-; to scroll one line up and down?
3136 Add the following (Thanks to @email{mly@@adoc.xerox.com, Richard Mlynarik} and
3137 @email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}:
3140 (defun scroll-up-one-line ()
3144 (defun scroll-down-one-line ()
3148 (global-set-key [(control ?.)] 'scroll-up-one-line) ; C-.
3149 (global-set-key [(control ?;)] 'scroll-down-one-line) ; C-;
3152 The key point is that you can only bind simple functions to keys; you
3153 can not bind a key to a function that you're also passing arguments to.
3154 (@pxref{Q3.5.1} for a better answer).
3156 @node Q3.5.4, Q3.5.5, Q3.5.3, Customization
3157 @unnumberedsubsec Q3.5.4: Globally binding @kbd{Delete}?
3159 I cannot manage to globally bind my @kbd{Delete} key to something other
3160 than the default. How does one do this?
3162 Answer: The problem is that many modes explicitly bind @kbd{Delete}. To
3163 get around this, try the following:
3168 (message "You hit DELETE"))
3170 (define-key key-translation-map 'delete 'redirected-delete)
3171 (global-set-key 'redirected-delete 'foo)
3174 Also see @ref{Q3.5.10}.
3176 @node Q3.5.5, Q3.5.6, Q3.5.4, Customization
3177 @unnumberedsubsec Q3.5.5: Scrolling one line at a time.
3179 Can the cursor keys scroll the screen a line at a time, rather than the
3180 default half page jump? I tend it to find it disorienting.
3185 (defun scroll-one-line-up (&optional arg)
3186 "Scroll the selected window up (forward in the text) one line (or N lines)."
3188 (scroll-up (or arg 1)))
3190 (defun scroll-one-line-down (&optional arg)
3191 "Scroll the selected window down (backward in the text) one line (or N)."
3193 (scroll-down (or arg 1)))
3195 (global-set-key [up] 'scroll-one-line-up)
3196 (global-set-key [down] 'scroll-one-line-down)
3199 The following will also work but will affect more than just the cursor
3200 keys (i.e. @kbd{C-n} and @kbd{C-p}):
3203 (setq scroll-step 1)
3206 Starting with XEmacs-20.3 you can also change this with Customize.
3207 Select from the @code{Options} menu
3208 @code{Advanced (Customize)->Emacs->Environment->Windows->Scroll Step...} or type
3209 @kbd{M-x customize @key{RET} windows @key{RET}}.
3211 @node Q3.5.6, Q3.5.7, Q3.5.5, Customization
3212 @unnumberedsubsec Q3.5.6: How to map @kbd{Help} key alone on Sun type4 keyboard?
3214 The following works in GNU Emacs 19:
3217 (global-set-key [help] 'help-command);; Help
3220 The following works in XEmacs with the addition of shift:
3223 (global-set-key [(shift help)] 'help-command);; Help
3226 But it doesn't work alone. This is in the file @file{PROBLEMS} which
3227 should have come with your XEmacs installation: @emph{Emacs ignores the
3228 @kbd{help} key when running OLWM}.
3230 OLWM grabs the @kbd{help} key, and retransmits it to the appropriate
3235 @code{XSendEvent}. Allowing Emacs to react to synthetic
3236 events is a security hole, so this is turned off by default. You can
3237 enable it by setting the variable @code{x-allow-sendevents} to t. You
3238 can also cause fix this by telling OLWM to not grab the help key, with
3239 the null binding @code{OpenWindows.KeyboardCommand.Help:}.
3241 @node Q3.5.7, Q3.5.8, Q3.5.6, Customization
3242 @unnumberedsubsec Q3.5.7: How can you type in special characters in XEmacs?
3244 One way is to use the package @code{x-compose}. Then you can use
3245 sequences like @kbd{Compose " a} to get ä, etc.
3247 Another way is to use the @code{iso-insert} package. Then you can use
3248 sequences like @kbd{C-x 8 " a} to get ä, etc.
3250 @email{glynn@@sensei.co.uk, Glynn Clements} writes:
3253 It depends upon your X server.
3255 Generally, the simplest way is to define a key as Multi_key with
3257 @c hey, show some respect, willya -- there's xkeycaps, isn't there? --
3260 xmodmap -e 'keycode 0xff20 = Multi_key'
3263 You will need to pick an appropriate keycode. Use xev to find out the
3264 keycodes for each key.
3266 [NB: On a `Windows' keyboard, recent versions of XFree86 automatically
3267 define the right `Windows' key as Multi_key'.]
3269 Once you have Multi_key defined, you can use e.g.
3278 Also, recent versions of XFree86 define various AltGr-<key>
3279 combinations as dead keys, i.e.
3281 AltGr [ => dead_diaeresis
3282 AltGr ] => dead_tilde
3283 AltGr ; => dead_acute
3287 Running @samp{xmodmap -pk} will list all of the defined keysyms.
3290 @node Q3.5.8, Q3.5.9, Q3.5.7, Customization
3291 @unnumberedsubsec Q3.5.8: [This question intentionally left blank]
3293 Obsolete question, left blank to avoid renumbering.
3295 @node Q3.5.9, Q3.5.10, Q3.5.8, Customization
3296 @unnumberedsubsec Q3.5.9: How do I make the Delete key delete forward?
3298 With XEmacs-20.2 use the @code{delbs} package:
3304 This will give you the functions @code{delbs-enable-delete-forward} to
3305 set things up, and @code{delbs-disable-delete-forward} to revert to
3306 ``normal'' behavior. Note that @code{delbackspace} package is obsolete.
3308 Starting with XEmacs-20.3 better solution is to set variable
3309 @code{delete-key-deletes-forward} to t. You can also change this with
3310 Customize. Select from the @code{Options} menu
3311 @code{Advanced (Customize)->Emacs->Editing->Basics->Delete Key Deletes Forward} or
3312 type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
3314 Also see @ref{Q3.5.4}.
3316 @node Q3.5.10, Q3.5.11, Q3.5.9, Customization
3317 @unnumberedsubsec Q3.5.10: Can I turn on @dfn{sticky} modifier keys?
3319 Yes, with @code{(setq modifier-keys-are-sticky t)}. This will give the
3320 effect of being able to press and release Shift and have the next
3321 character typed come out in upper case. This will affect all the other
3322 modifier keys like Control and Meta as well.
3324 @email{ben@@xemacs.org, Ben Wing} writes:
3327 One thing about the sticky modifiers is that if you move the mouse out
3328 of the frame and back in, it cancels all currently ``stuck'' modifiers.
3331 @node Q3.5.11, Q3.6.1, Q3.5.10, Customization
3332 @unnumberedsubsec Q3.5.11: How do I map the arrow keys?
3334 Say you want to map @kbd{C-@key{right}} to forward-word:
3336 @email{sds@@usa.net, Sam Steingold} writes:
3340 ; both XEmacs and Emacs
3341 (define-key global-map [(control right)] 'forward-word)
3346 (define-key global-map [C-right] 'forward-word)
3351 (define-key global-map (kbd "C-<right>") 'forward-word)
3357 @node Q3.6.1, Q3.6.2, Q3.5.11, Customization
3358 @unnumberedsec 3.6: The Cursor
3359 @unnumberedsubsec Q3.6.1: Is there a way to make the bar cursor thicker?
3361 I'd like to have the bar cursor a little thicker, as I tend to "lose" it
3364 For a 1 pixel bar cursor, use:
3370 For a 2 pixel bar cursor, use:
3373 (setq bar-cursor 'anything-else)
3376 Starting with XEmacs-20.3 you can also change these with Customize.
3377 Select from the @code{Options} menu
3378 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
3379 @kbd{M-x customize @key{RET} display @key{RET}}.
3381 You can use a color to make it stand out better:
3384 Emacs*cursorColor: Red
3387 @node Q3.6.2, Q3.6.3, Q3.6.1, Customization
3388 @unnumberedsubsec Q3.6.2: Is there a way to get back the block cursor?
3391 (setq bar-cursor nil)
3394 Starting with XEmacs 20.3 you can also change this with Customize.
3395 Select from the @code{Options} menu
3396 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type
3397 @kbd{M-x customize @key{RET} display @key{RET}}.
3399 @node Q3.6.3, Q3.7.1, Q3.6.2, Customization
3400 @unnumberedsubsec Q3.6.3: Can I make the cursor blink?
3408 This function toggles between a steady cursor and a blinking cursor.
3409 You may also set this mode from the menu bar by selecting @samp{Options
3410 => Frame Appearance => Blinking Cursor}. Remember to save options.
3412 @node Q3.7.1, Q3.7.2, Q3.6.3, Customization
3413 @unnumberedsec 3.7: The Mouse and Highlighting
3414 @unnumberedsubsec Q3.7.1: How can I turn off Mouse pasting?
3416 I keep hitting the middle mouse button by accident and getting stuff
3417 pasted into my buffer so how can I turn this off?
3419 Here is an alternative binding, whereby the middle mouse button selects
3420 (but does not cut) the expression under the mouse. Clicking middle on a
3421 left or right paren will select to the matching one. Note that you can
3422 use @code{define-key} or @code{global-set-key}.
3425 (defun mouse-set-point-and-select (event)
3426 "Sets the point at the mouse location, then marks following form"
3428 (mouse-set-point event)
3430 (define-key global-map [button2] 'mouse-set-point-and-select)
3433 @node Q3.7.2, Q3.7.3, Q3.7.1, Customization
3434 @unnumberedsubsec Q3.7.2: How do I set control/meta/etc modifiers on mouse buttons?
3436 Use, for instance, @code{[(meta button1)]}. For example, here is a common
3437 setting for Common Lisp programmers who use the bundled @code{ilisp}
3438 package, whereby meta-button1 on a function name will find the file where
3439 the function name was defined, and put you at that location in the source
3442 [Inside a function that gets called by the lisp-mode-hook and
3446 (local-set-key [(meta button1)] 'edit-definitions-lisp)
3449 @node Q3.7.3, Q3.7.4, Q3.7.2, Customization
3450 @unnumberedsubsec Q3.7.3: Clicking the left button does not do anything in buffer list.
3452 I do @kbd{C-x C-b} to get a list of buffers and the entries get
3453 highlighted when I move the mouse over them but clicking the left mouse
3454 does not do anything.
3456 Use the middle mouse button.
3458 @node Q3.7.4, Q3.7.5, Q3.7.3, Customization
3459 @unnumberedsubsec Q3.7.4: How can I get a list of buffers when I hit mouse button 3?
3461 The following code will replace the default popup on button3:
3464 (global-set-key [button3] 'popup-buffer-menu)
3467 @node Q3.7.5, Q3.7.6, Q3.7.4, Customization
3468 @unnumberedsubsec Q3.7.5: Why does cut-and-paste not work between XEmacs and a cmdtool?
3470 We don't know. It's a bug. There does seem to be a work-around,
3471 however. Try running xclipboard first. It appears to fix the problem
3472 even if you exit it. (This should be mostly fixed in 19.13, but we
3473 haven't yet verified that).
3475 @node Q3.7.6, Q3.7.7, Q3.7.5, Customization
3476 @unnumberedsubsec Q3.7.6: How I can set XEmacs up so that it pastes where the text cursor is?
3478 By default XEmacs pastes X selections where the mouse pointer is. How
3481 Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank
3484 To get XEmacs to paste at the text cursor, add this your @file{init.el}/@file{.emacs}:
3487 (setq mouse-yank-at-point t)
3490 Starting with XEmacs-20.2 you can also change this with Customize.
3491 Select from the @code{Options} menu
3492 @code{Advanced (Customize)->Emacs->Editing->Mouse->Yank At Point...} or type
3493 @kbd{M-x customize @key{RET} mouse @key{RET}}.
3495 @node Q3.7.7, Q3.7.8, Q3.7.6, Customization
3496 @unnumberedsubsec Q3.7.7: How do I select a rectangular region?
3498 Just select the region normally, then use the rectangle commands (e.g.
3499 @code{kill-rectangle} on it. The region does not highlight as a
3500 rectangle, but the commands work just fine.
3502 To actually sweep out rectangular regions with the mouse you can use
3503 @code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}.
3504 Then use rectangle commands.
3506 You can also do the following to change default behavior to sweep out
3507 rectangular regions:
3510 (setq mouse-track-rectangle-p t)
3513 Starting with XEmacs-20.2 you can also change this with Customize.
3514 Select from the @code{Options} menu
3515 @code{Advanced (Customize)->Emacs->Editing->Mouse->Track Rectangle...} or type
3516 @kbd{M-x customize @key{RET} mouse @key{RET}}.
3520 mouse-track-do-rectangle: (event)
3521 -- an interactive compiled Lisp function.
3522 Like `mouse-track' but selects rectangles instead of regions.
3525 @node Q3.7.8, Q3.8.1, Q3.7.7, Customization
3526 @unnumberedsubsec Q3.7.8: Why does @kbd{M-w} take so long?
3528 It actually doesn't. It leaves the region visible for a second so that
3529 you can see what area is being yanked. If you start working, though, it
3530 will immediately complete its operation. In other words, it will only
3531 delay for a second if you let it.
3533 @node Q3.8.1, Q3.8.2, Q3.7.8, Customization
3534 @unnumberedsec 3.8: The Menubar and Toolbar
3535 @unnumberedsubsec Q3.8.1: How do I get rid of the menu (or menubar)?
3537 @c If you are running XEmacs 19.13 or earlier, add this command to your
3538 @c @file{init.el}/@file{.emacs}.
3541 @c (set-menubar nil)
3544 @c Starting with XEmacs 19.14 the preferred method is:
3547 (set-specifier menubar-visible-p nil)
3550 @node Q3.8.2, Q3.8.3, Q3.8.1, Customization
3551 @unnumberedsubsec Q3.8.2: Can I customize the basic menubar?
3553 For an extensive menubar, add this line to your @file{init.el}/@file{.emacs}:
3556 (load "big-menubar")
3559 If you'd like to write your own, this file provides as good a set of
3560 examples as any to start from. The file is located in
3561 @file{lisp/packages/big-menubar.el} in the XEmacs installation
3564 @node Q3.8.3, Q3.8.4, Q3.8.2, Customization
3565 @unnumberedsubsec Q3.8.3: How do I control how many buffers are listed in the menu @code{Buffers List}?
3567 Add the following to your @file{init.el}/@file{.emacs} (suit to fit):
3570 (setq buffers-menu-max-size 20)
3573 For no limit, use an argument of @samp{nil}.
3575 Starting with XEmacs-20.3 you can also change this with Customize.
3576 Select from the @code{Options} menu
3577 @code{Advanced (Customize)->Emacs->Environment->Menu->Buffers Menu->Max Size...} or
3578 type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}.
3580 @node Q3.8.4, Q3.8.5, Q3.8.3, Customization
3581 @unnumberedsubsec Q3.8.4: Resources like @code{Emacs*menubar*font} are not working?
3583 I am trying to use a resource like @code{Emacs*menubar*font} to set the
3584 font of the menubar but it's not working.
3586 If you are using the real Motif menubar, this resource is not
3587 recognized; you have to say:
3590 Emacs*menubar*fontList: FONT
3593 If you are using the Lucid menubar, the former resource will be
3594 recognized only if the latter resource is unset. This means that the
3604 Emacs*menubar*font: FONT
3607 even though the latter is more specific.
3609 @node Q3.8.5, Q3.9.1, Q3.8.4, Customization
3610 @unnumberedsubsec Q3.8.5: How can I bind a key to a function to toggle the toolbar?
3615 (defun my-toggle-toolbar ()
3617 (set-specifier default-toolbar-visible-p
3618 (not (specifier-instance default-toolbar-visible-p))))
3619 (global-set-key "\C-xT" 'my-toggle-toolbar)
3622 There are redisplay bugs in 19.14 that may make the preceding result in
3623 a messed-up display, especially for frames with multiple windows. You
3624 may need to resize the frame before XEmacs completely realizes the
3625 toolbar is really gone.
3627 Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct
3630 @node Q3.9.1, Q3.9.2, Q3.8.5, Customization
3631 @unnumberedsec 3.9: Scrollbars
3632 @unnumberedsubsec Q3.9.1: How can I disable the scrollbar?
3634 To disable them for all frames, add the following line to
3635 your @file{.Xdefaults}:
3638 Emacs.scrollBarWidth: 0
3641 Or select from the @code{Options} menu @code{Frame Appearance->Scrollbars}.
3642 Remember to save options.
3644 To turn the scrollbar off on a per-frame basis, use the following
3648 (set-specifier scrollbar-width 0 (selected-frame))
3651 You can actually turn the scrollbars on at any level you want by
3652 substituting for (selected-frame) in the above command. For example, to
3653 turn the scrollbars off only in a single buffer:
3656 (set-specifier scrollbar-width 0 (current-buffer))
3659 @c In XEmacs versions prior to 19.14, you had to use the hairier construct:
3662 @c (set-specifier scrollbar-width (cons (selected-frame) 0))
3665 @node Q3.9.2, Q3.9.3, Q3.9.1, Customization
3666 @unnumberedsubsec Q3.9.2: How can one use resources to change scrollbar colors?
3668 Here's a recap of how to use resources to change your scrollbar colors:
3673 Emacs*XmScrollBar.Background: skyblue
3674 Emacs*XmScrollBar.troughColor: lightgray
3678 Emacs*Scrollbar.Foreground: skyblue
3679 Emacs*Scrollbar.Background: lightgray
3682 Note the capitalization of @code{Scrollbar} for the Athena widget.
3684 @node Q3.9.3, Q3.9.4, Q3.9.2, Customization
3685 @unnumberedsubsec Q3.9.3: Moving the scrollbar can move the point; can I disable this?
3687 When I move the scrollbar in an XEmacs window, it moves the point as
3688 well, which should not be the default behavior. Is this a bug or a
3689 feature? Can I disable it?
3691 The current behavior is a feature, not a bug. Point remains at the same
3692 buffer position as long as that position does not scroll off the screen.
3693 In that event, point will end up in either the upper-left or lower-left
3696 This cannot be changed.
3698 @node Q3.9.4, Q3.10.1, Q3.9.3, Customization
3699 @unnumberedsubsec Q3.9.4: How can I turn off automatic horizontal scrolling in specific modes?
3701 Do @code{(setq truncate-lines t)} in the mode-hooks for any modes
3702 in which you want lines truncated.
3704 More precisely: If @code{truncate-lines} is nil, horizontal scrollbars
3705 will never appear. Otherwise, they will appear only if the value of
3706 @code{scrollbar-height} for that buffer/window/etc. is non-zero. If you
3710 (set-specifier scrollbar-height 0)
3713 then horizontal scrollbars will not appear in truncated buffers unless
3714 the package specifically asked for them.
3716 @node Q3.10.1, Q3.10.2, Q3.9.4, Customization
3717 @unnumberedsec 3.10: Text Selections
3718 @unnumberedsubsec Q3.10.1: How can I turn off or change highlighted selections?
3720 The @code{zmacs} mode allows for what some might call gratuitous
3721 highlighting for selected regions (either by setting mark or by using
3722 the mouse). This is the default behavior. To turn off, add the
3723 following line to your @file{init.el}/@file{.emacs} file:
3726 (setq zmacs-regions nil)
3729 Starting with XEmacs-20.2 you can also change this with Customize. Select
3730 from the @code{Options} menu @code{Advanced (Customize)->Emacs->Editing->Basics->Zmacs
3731 Regions} or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
3733 To change the face for selection, look at @code{Options->Customize} on
3736 @node Q3.10.2, Q3.10.3, Q3.10.1, Customization
3737 @unnumberedsubsec Q3.10.2: How do I get that typing on an active region removes it?
3739 I want to change things so that if I select some text and start typing,
3740 the typed text replaces the selected text, similar to Motif.
3742 You want to use something called @dfn{pending delete}. Pending delete
3743 is what happens when you select a region (with the mouse or keyboard)
3744 and you press a key to replace the selected region by the key you typed.
3745 Usually backspace kills the selected region.
3747 To get this behavior, add the following lines to your @file{init.el}/@file{.emacs}:
3751 ((fboundp 'turn-on-pending-delete)
3752 (turn-on-pending-delete))
3753 ((fboundp 'pending-delete-on)
3754 (pending-delete-on t)))
3757 Note that this will work with both Backspace and Delete. This code is a
3758 tad more complicated than it has to be for XEmacs in order to make it
3761 @node Q3.10.3, Q3.10.4, Q3.10.2, Customization
3762 @unnumberedsubsec Q3.10.3: Can I turn off the highlight during isearch?
3764 I do not like my text highlighted while I am doing isearch as I am not
3765 able to see what's underneath. How do I turn it off?
3767 Put the following in your @file{init.el}/@file{.emacs}:
3770 (setq isearch-highlight nil)
3773 Starting with XEmacs-20.2 you can also change this with Customize. Type
3774 @kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}.
3776 Note also that isearch-highlight affects query-replace and ispell.
3777 Instead of disabling isearch-highlight you may find that a better
3778 solution consists of customizing the @code{isearch} face.
3780 @node Q3.10.4, Q3.10.5, Q3.10.3, Customization
3781 @unnumberedsubsec Q3.10.4: How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
3783 Put this in your @code{.emacs}:
3786 (setq zmacs-regions nil)
3789 @strong{Warning: This command turns off all region highlighting.}
3791 Also see @ref{Q3.10.1}.
3793 @node Q3.10.5, , Q3.10.4, Customization
3794 @unnumberedsubsec Q3.10.5: The region disappears when I hit the end of buffer while scrolling.
3796 This has been fixed by default starting with XEmacs-20.3.
3798 With older versions you can turn this feature (if it indeed is a feature)
3802 (defadvice scroll-up (around scroll-up freeze)
3804 (let ((zmacs-region-stays t))
3808 (end-of-buffer (goto-char (point-max))))
3811 (defadvice scroll-down (around scroll-down freeze)
3813 (let ((zmacs-region-stays t))
3817 (beginning-of-buffer (goto-char (point-min))))
3821 Thanks to @email{raman@@adobe.com, T. V. Raman} for assistance in deriving this
3824 @node Subsystems, Miscellaneous, Customization, Top
3825 @unnumbered 4 Major Subsystems
3827 This is part 4 of the XEmacs Frequently Asked Questions list. This
3828 section is devoted to major XEmacs subsystems.
3831 Reading Mail with VM:
3832 * Q4.0.1:: How do I set up VM to retrieve remote mail using POP?
3833 * Q4.0.2:: How do I get VM to filter mail for me?
3834 * Q4.0.3:: How can I get VM to automatically check for new mail?
3835 * Q4.0.4:: [This question intentionally left blank]
3836 * Q4.0.5:: How do I get my outgoing mail archived?
3837 * Q4.0.6:: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"?
3838 * Q4.0.7:: Is there a mailing list or FAQ for VM?
3839 * Q4.0.8:: Remote mail reading with VM.
3840 * Q4.0.9:: rmail or VM gets an error incorporating new mail.
3841 * Q4.0.10:: How do I make VM stay in a single frame?
3842 * Q4.0.11:: How do I make VM or mh-e display graphical smilies?
3843 * Q4.0.12:: Customization of VM not covered in the manual or here.
3845 Web browsing with W3:
3846 * Q4.1.1:: What is W3?
3847 * Q4.1.2:: How do I run W3 from behind a firewall?
3848 * Q4.1.3:: Is it true that W3 supports style sheets and tables?
3850 Reading Netnews and Mail with Gnus:
3851 * Q4.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus,argh!
3852 * Q4.2.2:: [This question intentionally left blank]
3853 * Q4.2.3:: How do I make Gnus stay within a single frame?
3854 * Q4.2.4:: How do I customize the From: line?
3857 * Q4.3.1:: How can I read and/or compose MIME messages?
3858 * Q4.3.2:: What is TM and where do I get it?
3859 * Q4.3.3:: Why isn't this @code{movemail} program working?
3860 * Q4.3.4:: Movemail is also distributed by Netscape? Can that cause problems?
3861 * Q4.3.5:: Where do I find pstogif (required by tm)?
3863 Sparcworks, EOS, and WorkShop:
3864 * Q4.4.1:: What is SPARCworks, EOS, and WorkShop
3865 * Q4.4.2:: How do I start the Sun Workshop support in XEmacs 21?
3868 * Q4.5.1:: What is/was Energize?
3871 * Q4.6.1:: What is Infodock?
3873 Other Unbundled Packages:
3874 * Q4.7.1:: What is AUC TeX? Where do you get it?
3875 * Q4.7.2:: Are there any Emacs Lisp Spreadsheets?
3876 * Q4.7.3:: [This question intentionally left blank]
3877 * Q4.7.4:: Problems installing AUC TeX
3878 * Q4.7.5:: Is there a reason for an Emacs package not to be included in XEmacs?
3879 * Q4.7.6:: Is there a MatLab mode?
3880 * Q4.7.7:: Can I edit files on other hosts?
3883 @node Q4.0.1, Q4.0.2, Subsystems, Subsystems
3884 @unnumberedsec 4.0: Reading Mail with VM
3885 @unnumberedsubsec Q4.0.1: How do I set up VM to retrieve mail from a remote site using POP?
3887 Use @code{vm-spool-files}, like this for example:
3890 (setq vm-spool-files '("/var/spool/mail/wing"
3891 "netcom23.netcom.com:110:pass:wing:MYPASS"))
3894 Of course substitute your actual password for MYPASS.
3896 @node Q4.0.2, Q4.0.3, Q4.0.1, Subsystems
3897 @unnumberedsubsec Q4.0.2: How do I get VM to filter mail for me?
3899 One possibility is to use procmail to split your mail before it gets to
3900 VM. I prefer this personally, since there are many strange and
3901 wonderful things one can do with procmail. Procmail may be found at
3902 @uref{ftp://ftp.informatik.rwth-aachen.de/pub/packages/procmail/}.
3904 Also see the Mail Filtering FAQ at:
3908 @uref{ftp://rtfm.mit.edu/pub/usenet/news.answers/mail/filtering-faq}.
3910 @c <URL:http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html>
3913 @node Q4.0.3, Q4.0.4, Q4.0.2, Subsystems
3914 @unnumberedsubsec Q4.0.3: How can I get VM to automatically check for new mail?
3916 @email{turner@@lanl.gov, John Turner} writes:
3922 (setq vm-auto-get-new-mail 60)
3926 @node Q4.0.4, Q4.0.5, Q4.0.3, Subsystems
3927 @unnumberedsubsec Q4.0.4: [This question intentionally left blank]
3929 Obsolete question, left blank to avoid renumbering.
3931 @node Q4.0.5, Q4.0.6, Q4.0.4, Subsystems
3932 @unnumberedsubsec Q4.0.5: How do I get my outgoing mail archived?
3935 (setq mail-archive-file-name "~/outbox")
3938 @node Q4.0.6, Q4.0.7, Q4.0.5, Subsystems
3939 @unnumberedsubsec Q4.0.6: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"?
3941 Set @code{vm-reply-ignored-addresses} to a list, like
3944 (setq vm-reply-ignored-addresses
3945 '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com"
3946 "wing@@netcom.com" "wing@@xemacs.org"))
3949 Note that each string is a regular expression.
3951 @node Q4.0.7, Q4.0.8, Q4.0.6, Subsystems
3952 @unnumberedsubsec Q4.0.7: Is there a mailing list or FAQ for VM?
3954 A FAQ for VM exists at @uref{http://www.wonderworks.com/vm/FAQ.html}.
3956 VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug.
3958 @node Q4.0.8, Q4.0.9, Q4.0.7, Subsystems
3959 @unnumberedsubsec Q4.0.8: Remote mail reading with VM.
3961 My mailbox lives at the office on a big honkin server. My regular INBOX
3962 lives on my honkin desktop machine. I now can PPP to the office from
3963 home which is far from honking... I'd like to be able to read mail at
3964 home without storing it here and I'd like to use xemacs and VM at
3965 home... Is there a recommended setup?
3967 @email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes:
3970 There are several ways to do this.
3974 Set your display to your home machine and run dxpc or one of the other X
3978 NFS mount your desktop machine on your home machine and modify your pop
3979 command on your home machine to rsh to your desktop machine and actually
3983 Run a POP server on your desktop machine as well and do a sort of two
3988 @email{wmperry@@monolith.spry.com, William Perry} adds:
3991 Or you could run a pop script periodically on your desktop machine, and
3992 just use ange-ftp or NFS to get to your mailbox. I used to do this all
3993 the time back at IU.
3996 @node Q4.0.9, Q4.0.10, Q4.0.8, Subsystems
3997 @unnumberedsubsec Q4.0.9: rmail or VM gets an error incorporating new mail.
3999 Quoting the XEmacs PROBLEMS file:
4002 rmail and VM get new mail from @file{/usr/spool/mail/$USER} using a
4003 program called @code{movemail}. This program interlocks with
4004 @code{/bin/mail} using the protocol defined by @code{/bin/mail}.
4006 There are two different protocols in general use. One of them uses the
4007 @code{flock} system call. The other involves creating a lock file;
4008 @code{movemail} must be able to write in @file{/usr/spool/mail} in order
4009 to do this. You control which one is used by defining, or not defining,
4010 the macro @code{MAIL_USE_FLOCK} in @file{config.h} or the m- or s- file
4013 @strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
4014 SYSTEM, YOU CAN LOSE MAIL!}
4016 If your system uses the lock file protocol, and fascist restrictions
4017 prevent ordinary users from writing the lock files in
4018 @file{/usr/spool/mail}, you may need to make @code{movemail} setgid to a
4019 suitable group such as @samp{mail}. You can use these commands (as
4027 If your system uses the lock file protocol, and fascist restrictions
4028 prevent ordinary users from writing the lock files in
4029 @file{/usr/spool/mail}, you may need to make @code{movemail} setgid to a
4030 suitable group such as @code{mail}. To do this, use the following
4031 commands (as root) after doing the make install.
4038 Installation normally copies movemail from the build directory to an
4039 installation directory which is usually under @file{/usr/local/lib}.
4040 The installed copy of @code{movemail} is usually in the directory
4041 @file{/usr/local/lib/emacs/VERSION/TARGET}. You must change the group
4042 and mode of the installed copy; changing the group and mode of the build
4043 directory copy is ineffective.
4046 @node Q4.0.10, Q4.0.11, Q4.0.9, Subsystems
4047 @unnumberedsubsec Q4.0.10: How do I make VM stay in a single frame?
4049 John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes:
4053 ; Don't use multiple frames
4054 (setq vm-frame-per-composition nil)
4055 (setq vm-frame-per-folder nil)
4056 (setq vm-frame-per-edit nil)
4057 (setq vm-frame-per-summary nil)
4061 @node Q4.0.11, Q4.0.12, Q4.0.10, Subsystems
4062 @unnumberedsubsec Q4.0.11: How do I make VM or mh-e display graphical smilies?
4064 For mh-e use the following:
4067 (add-hook 'mh-show-mode-hook '(lambda ()
4068 (smiley-region (point-min)
4072 @email{bill@@carpenter.ORG, WJCarpenter} writes:
4073 For VM use the following:
4075 (autoload 'smiley-region "smiley" nil t)
4076 (add-hook 'vm-select-message-hook
4078 (smiley-region (point-min)
4082 For tm use the following:
4084 (autoload 'smiley-buffer "smiley" nil t)
4085 (add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer)
4088 @node Q4.0.12, Q4.1.1, Q4.0.11, Subsystems
4089 @unnumberedsubsec Q4.0.12: Customization of VM not covered in the manual, or here.
4091 @email{boffi@@hp735.stru.polimi.it, giacomo boffi} writes:
4094 The meta-answer is to look into the file @file{vm-vars.el}, in the vm
4095 directory of the lisp library.
4097 @file{vm-vars.el} contains, initializes and carefully describes, with
4098 examples of usage, the plethora of user options that @emph{fully}
4099 control VM's behavior.
4101 Enter vm-vars, @code{forward-search} for toolbar, find the variables
4102 that control the toolbar placement, appearance, existence, copy to your
4103 @file{init.el}/@file{.emacs} or @file{.vm} and modify according to the
4104 detailed instructions.
4106 The above also applies to all the various features of VM: search for
4107 some keywords, maybe the first you conjure isn't appropriate, find the
4108 appropriate variables, copy and experiment.
4111 @node Q4.1.1, Q4.1.2, Q4.0.12, Subsystems
4112 @unnumberedsec 4.1: Web browsing with W3
4113 @unnumberedsubsec Q4.1.1: What is W3?
4115 W3 is an advanced graphical browser written in Emacs lisp that runs on
4116 XEmacs. It has full support for cascaded style sheets, and more...
4118 It has a home web page at
4119 @uref{http://www.cs.indiana.edu/elisp/w3/docs.html}.
4121 @node Q4.1.2, Q4.1.3, Q4.1.1, Subsystems
4122 @unnumberedsubsec Q4.1.2: How do I run W3 from behind a firewall?
4124 There is a long, well-written, detailed section in the W3 manual that
4125 describes how to do this. Look in the section entitled "Firewalls".
4127 @node Q4.1.3, Q4.2.1, Q4.1.2, Subsystems
4128 @unnumberedsubsec Q4.1.3: Is it true that W3 supports style sheets and tables?
4130 Yes, and much more. W3, as distributed with the latest XEmacs is a
4131 full-featured web browser.
4133 @node Q4.2.1, Q4.2.2, Q4.1.3, Subsystems
4134 @unnumberedsec 4.2: Reading Netnews and Mail with Gnus
4135 @unnumberedsubsec Q4.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
4137 The Gnus numbering issues are not meant for mere mortals to know them.
4138 If you feel you @emph{must} enter the muddy waters of Gnus, visit the
4139 excellent FAQ, maintained by Justin Sheehy, at:
4142 @uref{http://www.ccs.neu.edu/software/contrib/gnus/}
4145 See also Gnus home page
4147 @uref{http://www.gnus.org/}
4150 @node Q4.2.2, Q4.2.3, Q4.2.1, Subsystems
4151 @unnumberedsubsec Q4.2.2: This question intentionally left blank.
4153 Obsolete question, left blank to avoid renumbering.
4155 @node Q4.2.3, Q4.2.4, Q4.2.2, Subsystems
4156 @unnumberedsubsec Q4.2.3: How do I make Gnus stay within a single frame?
4158 The toolbar code to start Gnus opens the new frame---and it's a feature
4159 rather than a bug. If you don't like it, but would still like to click
4160 on the seemly icon, use the following code:
4163 (defun toolbar-news ()
4167 It will redefine the callback function of the icon to just call
4168 @code{gnus}, without all the fancy frame stuff.
4170 @node Q4.2.4, Q4.3.1, Q4.2.3, Subsystems
4171 @unnumberedsubsec Q4.2.4: How do I customize the From: line?
4173 How do I change the @code{From:} line? I have set gnus-user-from-line
4176 Gail Gurman <gail.gurman@@sybase.com>
4178 @noindent , but XEmacs Gnus doesn't use
4181 Gail Mara Gurman @email{gailg@@deall}
4183 @noindent and then complains
4184 that it's incorrect. Also, as you perhaps can see, my Message-ID is
4185 screwy. How can I change that?
4187 @email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes:
4190 Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or
4191 @code{mail-host-address} to @samp{sybase.com}.
4194 @node Q4.3.1, Q4.3.2, Q4.2.4, Subsystems
4195 @unnumberedsec 4.3: Other Mail & News
4196 @unnumberedsubsec Q4.3.1: How can I read and/or compose MIME messages?
4199 VM supports MIME natively.
4201 You probably want to use the Tools for MIME (tm). @xref{Q4.3.2}, for
4204 @email{trey@@cs.berkeley.edu, Trey Jackson} has an Emacs & MIME web page at
4208 @uref{http://bmrc.berkeley.edu/~trey/emacs/mime.html}.
4211 Another possibility is RMIME. You may find RMIME at
4215 @uref{http://www.cinti.net/~rmoody/rmime/index.html}.
4218 @node Q4.3.2, Q4.3.3, Q4.3.1, Subsystems
4219 @unnumberedsubsec Q4.3.2: What is TM and where do I get it?
4221 TM stands for @dfn{Tools for MIME} and not Tiny MIME. TM integrates
4222 with all major XEmacs packages like Gnus (all flavors), VM, MH-E, and
4223 mailcrypt. It provides totally transparent and trouble-free MIME
4224 support. When appropriate a message will be decoded in place in an
4227 TM now comes as a package with XEmacs 19.16 and XEmacs 20.2.
4229 TM was written by @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} and
4230 @email{shuhei-k@@jaist.ac.jp, KOBAYASHI
4233 It is based on the work of @email{umerin@@mse.kyutech.ac.jp, UMEDA
4234 Masanobu}, the original writer of GNUS.
4236 The following information is from the @file{README}:
4238 @dfn{tm} is a MIME package for GNU Emacs.
4239 tm has following functions:
4242 @item MIME style multilingual header.
4243 @item MIME message viewer (mime/viewer-mode).
4244 @item MIME message composer (mime/editor-mode).
4245 @item MIME extenders for mh-e, GNUS, RMAIL and VM.
4248 tm is available from following anonymous ftp sites:
4250 @comment @item @uref{ftp://ftp.jaist.ac.jp/pub/GNU/elisp/mime/} (Japan).
4251 @comment @item @uref{ftp://ftp.nis.co.jp/pub/gnu/emacs-lisp/tm/} (Japan).
4252 @comment @c The host above is unknown.
4253 @comment @item @uref{ftp://ftp.nisiq.net/pub/gnu/emacs-lisp/tm/} (US).
4254 @comment @item @uref{ftp://ftp.miranova.com/pub/gnus/jaist.ac.jp/} (US).
4255 @item @uref{ftp://ftp.unicamp.br/pub/mail/mime/tm/} (Brasil).
4256 @item @uref{ftp://ftp.th-darmstadt.de/pub/editors/GNU-Emacs/lisp/mime/} (Germany).
4257 @item @uref{ftp://ftp.tnt.uni-hannover.de/pub/editors/xemacs/contrib/} (Germany).
4260 Don't let the installation procedure & instructions stop you from trying
4261 this package out---it's much simpler than it looks, and once installed,
4264 @node Q4.3.3, Q4.3.4, Q4.3.2, Subsystems
4265 @unnumberedsubsec Q4.3.3: Why isn't this @code{movemail} program working?
4267 Ben Wing @email{ben@@xemacs.org} writes:
4270 It wasn't chown'ed/chmod'd correctly.
4273 @node Q4.3.4, Q4.3.5, Q4.3.3, Subsystems
4274 @unnumberedsubsec Q4.3.4: Movemail is also distributed by Netscape? Can that cause problems?
4276 @email{steve@@xemacs.org, Steve Baur} writes:
4279 Yes. Always use the movemail installed with your XEmacs. Failure to do
4280 so can result in lost mail.
4283 Please refer to @email{jwz@@jwz.org, Jamie Zawinski's} notes at
4287 @uref{http://home.netscape.com/eng/mozilla/2.0/relnotes/demo/movemail.html}.
4288 In particular, this document will show you how to make Netscape use the
4289 version of movemail configured for your system by the person who built
4292 @node Q4.3.5, Q4.4.1, Q4.3.4, Subsystems
4293 @unnumberedsubsec Q4.3.5: Where do I find pstogif (required by tm)?
4295 pstogif is part of the latex2html package.
4297 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
4299 latex2html is best found at the CTAN hosts and their mirrors
4304 @file{tex-archive/support/latex2html}.
4309 @item @uref{ftp://ftp.tex.ac.uk/tex-archive/support/latex2html/}.
4310 @item @uref{ftp://ftp.dante.de/tex-archive/support/latex2html/}.
4313 There is a good mirror at ftp.cdrom.com;
4317 @uref{ftp://ftp.cdrom.com/pub/tex/ctan/support/latex2html/}.
4319 @node Q4.4.1, Q4.4.2, Q4.3.5, Subsystems
4320 @unnumberedsec 4.4: Sparcworks, EOS, and WorkShop
4321 @unnumberedsubsec Q4.4.1: What is SPARCworks, EOS, and WorkShop?
4323 @email{turner@@lanl.gov, John Turner} writes:
4326 SPARCworks is SunSoft's development environment, comprising compilers
4327 (C, C++, FORTRAN 77, Fortran 90, Ada, and Pascal), a debugger, and other
4328 tools such as TeamWare (for configuration management), MakeTool, etc.
4331 See @uref{http://www.sun.com/software/Developer-products/}
4334 EOS stands for "Era on SPARCworks", but I don't know what Era stands
4337 EOS is the integration of XEmacs with the SPARCworks debugger. It
4338 allows one to use an XEmacs frame to view code (complete with
4339 fontification, etc.), set breakpoints, print variables, etc., while
4340 using the SPARCworks debugger. It works very well and I use it all the
4343 @email{cthomp@@xemacs.org, Chuck Thompson} writes:
4346 Era stood for "Emacs Rewritten Again". It was what we were calling the
4347 modified version of Lucid Emacs for Sun when I was dragged, er, allowed
4348 to work on this wonderful editor.
4351 @email{martin@@xemacs.org, Martin Buchholz} writes:
4354 EOS is being replaced with a new graphical development environment
4355 called Sun WorkShop, which is currently (07/96) in Alpha Test. For more
4360 @uref{http://www.sun.com/software/Products/Developer-products}.
4363 @node Q4.4.2, Q4.5.1, Q4.4.1, Subsystems
4364 @unnumberedsubsec Q4.4.2: How do I start the Sun Workshop support in XEmacs 21?
4366 Add the switch ---with-workshop to the configure command when building
4367 XEmacs and put the following in one of your startup files
4368 (e.g. site-start.el or .emacs):
4371 (when (featurep 'tooltalk)
4372 (load "tooltalk-macros")
4373 (load "tooltalk-util")
4374 (load "tooltalk-init"))
4375 (when (featurep 'sparcworks)
4376 (load "sunpro-init")
4379 (load "annotations")
4383 If you are not using the latest Workshop (5.0) you have to apply the
4387 --- /opt/SUNWspro/lib/eserve.el.ORIG Fri May 14 15:23:26 1999
4388 +++ /opt/SUNWspro/lib/eserve.el Fri May 14 15:24:54 1999
4389 @@@@ -42,7 +42,7 @@@@
4390 (defvar running-xemacs nil "t if we're running XEmacs")
4391 (defvar running-emacs nil "t if we're running GNU Emacs 19")
4393 -(if (string-match "^\\(19\\|20\\)\..*\\(XEmacs\\|Lucid\\)" emacs-version)
4394 +(if (string-match "\\(XEmacs\\|Lucid\\)" emacs-version)
4395 (setq running-xemacs t)
4396 (setq running-emacs t))
4401 @node Q4.5.1, Q4.6.1, Q4.4.2, Subsystems
4402 @unnumberedsec 4.5: Energize
4403 @unnumberedsubsec Q4.5.1: What is/was Energize?
4405 @email{gray@@meteor.harlequin.com, David N Gray} writes:
4407 The files in @file{lisp/energize} are to enable Emacs to interface with
4408 the "Energize Programming System", a C and C++ development environment,
4409 which was a product of Lucid, Inc. Tragically, Lucid went out of
4410 business in 1994, so although Energize is still a great system, if you
4411 don't already have it, there isn't any way to get it now. (Unless you
4412 happen to be in Japan; INS Engineering may still be selling it there.
4413 Tartan bought the rights to sell it in the rest of the world, but never
4417 @node Q4.6.1, Q4.7.1, Q4.5.1, Subsystems
4418 @unnumberedsec 4.6: Infodock
4419 @unnumberedsubsec Q4.6.1: What is Infodock?
4421 @uref{http://sourceforge.net/projects/infodock/, InfoDock} is an
4422 integrated productivity toolset, mainly aimed at technical people,
4423 hosted at SourceForge.
4425 InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of
4426 the power of Emacs, but with an easier to use and more comprehensive
4427 menu-based user interface. The bottom portion of this text describes
4428 how it differs from XEmacs and GNU Emacs from the Free Software
4431 InfoDock is aimed at people who want a free, turn-key productivity
4432 environment. Although InfoDock is customizable, it is not intended for
4433 people who like basic versions of Emacs which need to be customized
4434 extensively for local use; standard Emacs distributions are better for
4435 such uses. InfoDock is for those people who want a complete,
4436 pre-customized environment in one package, which they need not touch
4437 more than once or twice a year to update to new revisions.
4439 InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX,
4440 and Intel Linux systems. It is intended for use on a color display,
4441 although most features will work on monochrome monitors. Simply unpack
4442 InfoDock according to the instructions in the ID-INSTALL file and you
4445 The InfoDock Manual is concise, yet sufficient as a user guide for users
4446 who have never used an Emacs-type editor before. For users who are
4447 already familiar with Emacs, it supplements the information in the GNU
4450 InfoDock menus are much more extensive and more mature than standard
4451 Emacs menus. Each menu offers a @samp{Manual} item which displays
4452 documentation associated with the menu's functions.
4455 Four types of menubars are provided:
4458 An extensive menubar providing access to global InfoDock commands.
4460 Mode-specific menubars tailored to the current major mode.
4462 A simple menubar for basic editing to help novices get started with InfoDock.
4464 The standard XEmacs menubar.
4467 Most modes also include mode-specific popup menus. Additionally, region and
4468 rectangle popup menus are included.
4470 @samp{Hyperbole}, the everyday information manager, is a core part of
4471 InfoDock. This provides context-sensitive mouse keys, a rolodex-type
4472 contact manager, programmable hypertext buttons, and an autonumbered
4473 outliner with embedded hyperlink anchors.
4475 The @samp{OO-Browser}, a multi-language object-oriented code browser, is a
4476 standard part of InfoDock.
4478 InfoDock saves a more extensive set of user options than other Emacs
4481 InfoDock inserts a useful file header in many file types, showing the
4482 author, summary, and last modification time of each file. A summary
4483 program can then be used to summarize all of the files in a directory,
4484 for easy MANIFEST file creation.
4486 Your working set of buffers is automatically saved and restored (if you
4487 answer yes to a prompt) between InfoDock sessions.
4489 Refined color choices for code highlighting are provided for both dark and
4490 light background display frames.
4492 The @kbd{C-z} key prefix performs frame-based commands which parallel the
4493 @kbd{C-x} key prefix for window-based commands.
4495 The Smart Menu system is included for producing command menus on dumb
4498 Lisp libraries are better categorized according to function.
4500 Extensions and improvements to many areas of Emacs are included, such as:
4501 paragraph filling, mail reading with Rmail, shell handling, outlining, code
4502 highlighting and browsing, and man page browsing.
4504 InfoDock questions, answers and discussion should go to the mail list
4508 @email{infodock@@infodock.com}. Use
4509 @email{infodock-request@@infodock.com} to be added or removed from the
4510 list. Always include your InfoDock version number when sending help
4513 InfoDock is available across the Internet via anonymous FTP. To get
4514 it, first move to a directory into which you want the InfoDock archive
4515 files placed. We will call this <DIST-DIR>.
4521 Ftp to ftp.xemacs.org (Internet Host ID = 128.174.252.16):
4524 prompt> ftp ftp.xemacs.org
4527 Login as @samp{anonymous} with your own <user-id>@@<site-name> as a password.
4530 Name (ftp.xemacs.org): anonymous
4531 331 Guest login ok, send your complete e-mail address as password.
4532 Password: -<your-user-id>@@<your-domain>
4533 230 Guest login ok, access restrictions apply.
4536 Move to the location of the InfoDock archives:
4539 ftp> cd pub/infodock
4542 Set your transfer mode to binary:
4553 Interactive mode off.
4556 Retrieve the InfoDock archives that you want, either by using a
4557 @samp{get <file>} for each file you want or by using the following to
4558 get a complete distribution, including all binaries:
4561 ftp> mget ID-INSTALL
4565 Close the FTP connection:
4572 Read the @file{ID-INSTALL} file which you just retrieved for
4573 step-by-step installation instructions.
4575 @node Q4.7.1, Q4.7.2, Q4.6.1, Subsystems
4576 @unnumberedsec 4.7: Other Unbundled Packages
4577 @unnumberedsubsec Q4.7.1: What is AUC TeX? Where do you get it?
4579 AUC TeX is a package written by @email{abraham@@dina.kvl.dk, Per Abrahamsen}.
4580 Starting with XEmacs 19.16, AUC TeX is bundled with XEmacs. The
4581 following information is from the @file{README} and website.
4583 AUC TeX is an extensible package that supports writing and formatting
4584 TeX files for most variants of GNU Emacs. Many different macro packages
4585 are supported, including AMS TeX, LaTeX, and TeXinfo.
4587 The most recent version is always available by ftp at
4591 @uref{ftp://sunsite.dk/packages/auctex/auctex.tar.gz}.
4593 In case you don't have access to anonymous ftp, you can get it by an
4594 email request to @email{ftpmail@@decwrl.dec.com}.
4596 WWW users may want to check out the AUC TeX page at
4600 @uref{http://sunsite.dk/auctex/}.
4602 @node Q4.7.2, Q4.7.3, Q4.7.1, Subsystems
4603 @unnumberedsubsec Q4.7.2: Are there any Emacs Lisp Spreadsheets?
4605 Yes. Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at
4609 @uref{ftp://cs.nyu.edu/pub/local/fox/dismal/}.
4611 @node Q4.7.3, Q4.7.4, Q4.7.2, Subsystems
4612 @unnumberedsubsec Q4.7.3: [This question intentionally left blank]
4614 @node Q4.7.4, Q4.7.5, Q4.7.3, Subsystems
4615 @unnumberedsubsec Q4.7.4: Problems installing AUC TeX.
4617 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
4620 AUC TeX works fine on both stock Emacs and XEmacs has been doing so for
4621 a very very long time. This is mostly due to the work of
4622 @email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu}
4623 package. Which leads to what is probably the problem...
4626 Most problems with AUC TeX are one of two things:
4630 The TeX-lisp-directory in @file{tex-site.el} and the makefile don't
4633 Fix: make sure you configure AUC TeX properly @strong{before} installing.
4636 You have an old version of easymenu.el in your path.
4638 Fix: use @code{locate-library} and remove old versions to make sure it
4639 @strong{only} finds the one that came with XEmacs.
4643 @node Q4.7.5, Q4.7.6, Q4.7.4, Subsystems
4644 @unnumberedsubsec Q4.7.5: Is there a reason for an Emacs package not to be included in XEmacs?
4646 The reason for an Emacs package not to be included in XEmacs is
4647 usually one or more of the following:
4651 The package has not been ported to XEmacs. This will typically happen
4652 when it uses GNU-Emacs-specific features, which make it fail under
4655 Porting a package to XEmacs can range from a trivial amount of change to
4656 a partial or full rewrite. Fortunately, the authors of modern packages
4657 usually choose to support both Emacsen themselves.
4660 The package has been decided not to be appropriate for XEmacs. It may
4661 have an equivalent or better replacement within XEmacs, in which case
4662 the developers may choose not to burden themselves with supporting an
4665 Each package bundled with XEmacs means more work for the maintainers,
4666 whether they want it or not. If you are ready to take over the
4667 maintenance responsibilities for the package you port, be sure to say
4668 so---we will more likely include it.
4671 The package simply hasn't been noted by the XEmacs development. If
4672 that's the case, the messages like yours are very useful for attracting
4676 The package was noted by the developers, but they simply haven't yet
4677 gotten around to including/porting it. Wait for the next release or,
4678 even better, offer your help. It will be gladly accepted and
4682 @node Q4.7.6, Q4.7.7, Q4.7.5, Subsystems
4683 @unnumberedsubsec Q4.7.5: Is there a MatLab mode?
4685 Yes, a matlab mode and other items are available at the
4686 @uref{ftp://ftp.mathworks.com/pub/contrib/emacs_add_ons,
4687 MathWorks' emacs_add_ons ftp directory}.
4689 @node Q4.7.7, , Q4.7.6, Subsystems
4690 @unnumberedsubsec Q4.7.7: Can I edit files on other hosts?
4692 Yes. Of course XEmacs can use any network file system (such as NFS or
4693 Windows file sharing) you have available, and includes some
4694 optimizations and safety features appropriate to those environments.
4696 It is also possible to transparently edit files via FTP, ssh, or rsh. That
4697 is, XEmacs makes a local copy using the transport in the background, and
4698 automatically refreshes the remote original from that copy when you save
4699 it. XEmacs also is capable of doing file system manipulations like
4700 creating and removing directories and files. The FTP interface is
4701 provided by the standard @samp{efs} package @ref{Top, EFS, , efs}. The
4702 ssh/rsh interface is provided by the optional @samp{tramp} package
4703 @ref{Top, TRAMP, , tramp}.
4705 @node Miscellaneous, MS Windows, Subsystems, Top
4706 @unnumbered 5 The Miscellaneous Stuff
4708 This is part 5 of the XEmacs Frequently Asked Questions list. This
4709 section is devoted to anything that doesn't fit neatly into the other
4713 Major & Minor Modes:
4714 * Q5.0.1:: How can I do source code highlighting using font-lock?
4715 * Q5.0.2:: I do not like cc-mode. How do I use the old c-mode?
4716 * Q5.0.3:: How do I get @samp{More} Syntax Highlighting on by default?
4717 * Q5.0.4:: How can I enable auto-indent and/or Filladapt?
4718 * Q5.0.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
4719 * Q5.0.6:: How do I start up a second shell buffer?
4720 * Q5.0.7:: Telnet from shell filters too much.
4721 * Q5.0.8:: Why does edt emulation not work?
4722 * Q5.0.9:: How can I emulate VI and use it as my default mode?
4723 * Q5.0.10:: [This question intentionally left blank]
4724 * Q5.0.11:: [This question intentionally left blank]
4725 * Q5.0.12:: How do I disable gnuserv from opening a new frame?
4726 * Q5.0.13:: How do I start gnuserv so that each subsequent XEmacs is a client?
4727 * Q5.0.14:: Strange things are happening in Shell Mode.
4728 * Q5.0.15:: Where do I get the latest CC Mode?
4729 * Q5.0.16:: I find auto-show-mode disconcerting. How do I turn it off?
4730 * Q5.0.17:: How can I get two instances of info?
4731 * Q5.0.18:: [This question intentionally left blank]
4732 * Q5.0.19:: Is there something better than LaTeX mode?
4733 * Q5.0.20:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
4735 Emacs Lisp Programming Techniques:
4736 * Q5.1.1:: The difference in key sequences between XEmacs and GNU Emacs?
4737 * Q5.1.2:: Can I generate "fake" keyboard events?
4738 * Q5.1.3:: Could you explain @code{read-kbd-macro} in more detail?
4739 * Q5.1.4:: What is the performance hit of @code{let}?
4740 * Q5.1.5:: What is the recommended use of @code{setq}?
4741 * Q5.1.6:: What is the typical misuse of @code{setq}?
4742 * Q5.1.7:: I like the @code{do} form of cl, does it slow things down?
4743 * Q5.1.8:: I like recursion, does it slow things down?
4744 * Q5.1.9:: How do I put a glyph as annotation in a buffer?
4745 * Q5.1.10:: @code{map-extents} won't traverse all of my extents!
4746 * Q5.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
4749 * Q5.2.1:: How do I turn off the sound?
4750 * Q5.2.2:: How do I get funky sounds instead of a boring beep?
4751 * Q5.2.3:: What's NAS, how do I get it?
4752 * Q5.2.4:: Sunsite sounds don't play.
4755 * Q5.3.1:: How do you make XEmacs indent CL if-clauses correctly?
4756 * Q5.3.2:: [This question intentionally left blank]
4757 * Q5.3.3:: How can I print WYSIWYG a font-locked buffer?
4758 * Q5.3.4:: Getting @kbd{M-x lpr} to work with postscript printer.
4759 * Q5.3.5:: How do I specify the paths that XEmacs uses for finding files?
4760 * Q5.3.6:: [This question intentionally left blank]
4761 * Q5.3.7:: Can I have the end of the buffer delimited in some way?
4762 * Q5.3.8:: How do I insert today's date into a buffer?
4763 * Q5.3.9:: Are only certain syntactic character classes available for abbrevs?
4764 * Q5.3.10:: How can I get those oh-so-neat X-Face lines?
4765 * Q5.3.11:: How do I add new Info directories?
4766 * Q5.3.12:: What do I need to change to make printing work?
4769 @node Q5.0.1, Q5.0.2, Miscellaneous, Miscellaneous
4770 @unnumberedsec 5.0: Major & Minor Modes
4771 @unnumberedsubsec Q5.0.1: How can I do source code highlighting using font-lock?
4773 For most modes, font-lock is already set up and just needs to be turned
4774 on. This can be done by adding the line:
4777 (require 'font-lock)
4780 to your @file{init.el}/@file{.emacs}. (You can turn it on for the
4781 current buffer and session only by @kbd{M-x font-lock-mode}.) See the
4782 file @file{etc/sample.init.el} (@file{etc/sample.emacs} in XEmacs
4783 versions prior to 21.4) for more information.
4786 @c (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
4787 @c (add-hook 'dired-mode-hook 'turn-on-font-lock)
4789 See also @code{Syntax Highlighting} from the @code{Options} menu.
4790 Remember to save options.
4792 @node Q5.0.2, Q5.0.3, Q5.0.1, Miscellaneous
4793 @unnumberedsubsec Q5.0.2: I do not like cc-mode. How do I use the old c-mode?
4795 Well, first off, consider if you really want to do this. cc-mode is
4796 much more powerful than the old c-mode. If you're having trouble
4797 getting your old offsets to work, try using @code{c-set-offset} instead.
4798 You might also consider using the package @code{cc-compat}.
4800 But, if you still insist, add the following lines to your @file{init.el}/@file{.emacs}:
4803 (fmakunbound 'c-mode)
4804 (makunbound 'c-mode-map)
4805 (fmakunbound 'c++-mode)
4806 (makunbound 'c++-mode-map)
4807 (makunbound 'c-style-alist)
4808 (load-library "old-c-mode")
4809 (load-library "old-c++-mode")
4812 This must be done before any other reference is made to either c-mode or
4815 @node Q5.0.3, Q5.0.4, Q5.0.2, Miscellaneous
4816 @unnumberedsubsec Q5.0.3: How do I get @samp{More} Syntax Highlighting on by default?
4818 Use the following code in your @file{init.el}/@file{.emacs}:
4821 (setq-default font-lock-maximum-decoration t)
4824 @c In versions of XEmacs prior to 19.14, you had to use a kludgy solution
4828 @c (setq c-font-lock-keywords c-font-lock-keywords-2
4829 @c c++-font-lock-keywords c++-font-lock-keywords-2
4830 @c lisp-font-lock-keywords lisp-font-lock-keywords-2)
4833 @c It will work for C, C++ and Lisp.
4835 See also @code{Syntax Highlighting} from the @code{Options} menu.
4836 Remember to save options.
4838 @node Q5.0.4, Q5.0.5, Q5.0.3, Miscellaneous
4839 @unnumberedsubsec Q5.0.4: How can I enable auto-indent and/or Filladapt?
4841 Put the following line in your @file{init.el}/@file{.emacs}:
4844 (setq indent-line-function 'indent-relative-maybe)
4847 If you want to get fancy, try the @code{filladapt} package available
4848 standard with XEmacs. Put this into your @file{init.el}/@file{.emacs}:
4851 (require 'filladapt)
4852 (setq-default filladapt-mode t)
4853 (add-hook 'c-mode-hook 'turn-off-filladapt-mode)
4856 This will enable Filladapt for all modes except C mode, where it doesn't
4857 work well. To turn Filladapt on only in particular major modes, remove
4858 the @code{(setq-default ...)} line and use
4859 @code{turn-on-filladapt-mode}, like this:
4862 (add-hook 'text-mode-hook 'turn-on-filladapt-mode)
4865 You can customize filling and adaptive filling with Customize.
4866 Select from the @code{Options} menu
4867 @code{Advanced (Customize)->Emacs->Editing->Fill->Fill...}
4868 or type @kbd{M-x customize @key{RET} fill @key{RET}}.
4870 Note that well-behaving text-lookalike modes will run
4871 @code{text-mode-hook} by default (e.g. that's what Message does). For
4872 the nasty ones, you'll have to provide the @code{add-hook}s yourself.
4874 Please note that the @code{fa-extras} package is no longer useful.
4876 @node Q5.0.5, Q5.0.6, Q5.0.4, Miscellaneous
4877 @unnumberedsubsec Q5.0.5: How can I get XEmacs to come up in text/auto-fill mode by default?
4879 Try the following lisp in your @file{init.el}/@file{.emacs}:
4882 (setq default-major-mode 'text-mode)
4883 (setq text-mode-hook 'turn-on-auto-fill)
4886 @strong{WARNING}: note that changing the value of
4887 @code{default-major-mode} from @code{fundamental-mode} can break a large
4888 amount of built-in code that expects newly created buffers to be in
4889 @code{fundamental-mode}. (Changing from @code{fundamental-mode} to
4890 @code{text-mode} might not wreak too much havoc, but changing to
4891 something more exotic like a lisp-mode would break many Emacs packages).
4893 Note that Emacs by default starts up in buffer @code{*scratch*} in
4894 @code{initial-major-mode}, which defaults to
4895 @code{lisp-interaction-mode}. Thus adding the following form to your
4896 Emacs init file will cause the initial @code{*scratch*} buffer to be put
4897 into auto-fill'ed @code{text-mode}:
4900 (setq initial-major-mode
4903 (turn-on-auto-fill)))
4906 Note that after your init file is loaded, if
4907 @code{inhibit-startup-message} is @code{nil} (the default) and the
4908 startup buffer is @code{*scratch*} then the startup message will be
4909 inserted into @code{*scratch*}; it will be removed after a timeout by
4910 erasing the entire @code{*scratch*} buffer. Keep in mind this default
4911 usage of @code{*scratch*} if you desire any prior manipulation of
4912 @code{*scratch*} from within your Emacs init file. In particular,
4913 anything you insert into @code{*scratch*} from your init file will be
4914 later erased. Also, if you change the mode of the @code{*scratch*}
4915 buffer, be sure that this will not interfere with possible later
4916 insertion of the startup message (e.g. if you put @code{*scratch*} into
4917 a nonstandard mode that has automatic font lock rules, then the startup
4918 message might get fontified in a strange foreign manner, e.g. as code in
4919 some programming language).
4921 @node Q5.0.6, Q5.0.7, Q5.0.5, Miscellaneous
4922 @unnumberedsubsec Q5.0.6: How do I start up a second shell buffer?
4924 In the @code{*shell*} buffer:
4927 M-x rename-buffer @key{RET} *shell-1* @key{RET}
4931 This will then start a second shell. The key is that no buffer named
4932 @samp{*shell*} can exist. It might be preferable to use @kbd{M-x
4933 rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x
4936 Alternately, you can set the variable @code{shell-multiple-shells}.
4937 If the value of this variable is non-nil, each time shell mode is invoked,
4940 @node Q5.0.7, Q5.0.8, Q5.0.6, Miscellaneous
4941 @unnumberedsubsec Q5.0.7: Telnet from shell filters too much
4943 I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke
4944 and use a telnet session within it. Everything works fine except that
4945 now all @samp{^M}'s are filtered out by Emacs. Fixes?
4947 Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather
4948 than doing rsh or telnet within the local shell buffer. Starting with
4949 XEmacs-20.3 you can also use @kbd{M-x ssh} to open secure remote session
4950 if you have @code{ssh} installed.
4952 @node Q5.0.8, Q5.0.9, Q5.0.7, Miscellaneous
4953 @unnumberedsubsec Q5.0.8: Why does edt emulation not work?
4955 We don't know, but you can use tpu-edt emulation instead, which works
4956 fine and is a little fancier than the standard edt emulation. To do
4957 this, add the following line to your @file{init.el}/@file{.emacs}:
4963 If you don't want it to replace @kbd{C-h} with an edt-style help menu
4967 (global-set-key [(control h)] 'help-for-help)
4970 @node Q5.0.9, Q5.0.10, Q5.0.8, Miscellaneous
4971 @unnumberedsubsec Q5.0.9: How can I emulate VI and use it as my default mode?
4973 Our recommended VI emulator is viper. To make viper-mode the default,
4974 add this to your @file{init.el}/@file{.emacs}:
4980 @email{kifer@@CS.SunySB.EDU, Michael Kifer} writes:
4983 This should be added as close to the top of @file{init.el}/@file{.emacs} as you can get
4984 it, otherwise some minor modes may not get viper-ized.
4987 @node Q5.0.10, Q5.0.11, Q5.0.9, Miscellaneous
4988 @unnumberedsubsec Q5.0.10: [This question intentionally left blank]
4990 Obsolete question, left blank to avoid renumbering
4992 @node Q5.0.11, Q5.0.12, Q5.0.10, Miscellaneous
4993 @unnumberedsubsec Q5.0.11: [This question intentionally left blank]
4995 Obsolete question, left blank to avoid renumbering
4997 @node Q5.0.12, Q5.0.13, Q5.0.11, Miscellaneous
4998 @unnumberedsubsec Q5.0.12: How do I disable gnuserv from opening a new frame?
5000 If you set the @code{gnuserv-frame} variable to the frame that should be
5001 used to display buffers that are pulled up, a new frame will not be
5002 created. For example, you could put
5005 (setq gnuserv-frame (selected-frame))
5008 early on in your @file{init.el}/@file{.emacs}, to ensure that the first frame created
5009 is the one used for your gnuserv buffers.
5011 There is an option to set the gnuserv target to the current frame. See
5012 @code{Options->Display->"Other Window" Location->Make Current Frame Gnuserv Target}
5014 Starting with XEmacs-20.3 you can also change this with Customize.
5015 Select from the @code{Options} menu
5016 @code{Advanced (Customize)->Emacs->Environment->Gnuserv->Gnuserv Frame...}
5017 or type @kbd{M-x customize @key{RET} gnuserv @key{RET}}.
5020 @node Q5.0.13, Q5.0.14, Q5.0.12, Miscellaneous
5021 @unnumberedsubsec Q5.0.13: How do I start gnuserv so that each subsequent XEmacs is a client?
5023 Put the following in your @file{init.el}/@file{.emacs} file to start the server:
5029 Start your first XEmacs as usual. After that, you can do:
5032 gnuclient randomfilename
5035 from the command line to get your existing XEmacs process to open a new
5036 frame and visit randomfilename in that window. When you're done editing
5037 randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the
5040 See also man page of gnuclient.
5042 @node Q5.0.14, Q5.0.15, Q5.0.13, Miscellaneous
5043 @unnumberedsubsec Q5.0.14: Strange things are happening in Shell Mode.
5045 Sometimes (i.e. it's not repeatable, and I can't work out why it
5046 happens) when I'm typing into shell mode, I hit return and only a
5047 portion of the command is given to the shell, and a blank prompt is
5048 returned. If I hit return again, the rest of the previous command is
5051 @email{martin@@xemacs.org, Martin Buchholz} writes:
5054 There is a known problem with interaction between @code{csh} and the
5055 @code{filec} option and XEmacs. You should add the following to your
5059 if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec
5063 @node Q5.0.15, Q5.0.16, Q5.0.14, Miscellaneous
5064 @unnumberedsubsec Q5.0.15: Where do I get the latest CC Mode?
5066 @email{bwarsaw@@cnri.reston.va.us, Barry A. Warsaw} writes:
5069 This can be had from @uref{http://www.python.org/emacs/}.
5072 @node Q5.0.16, Q5.0.17, Q5.0.15, Miscellaneous
5073 @unnumberedsubsec Q5.0.16: I find auto-show-mode disconcerting. How do I turn it off?
5075 @code{auto-show-mode} controls whether or not a horizontal scrollbar
5076 magically appears when a line is too long to be displayed. This is
5077 enabled by default. To turn it off, put the following in your
5078 @file{init.el}/@file{.emacs}:
5081 (setq auto-show-mode nil)
5082 (setq-default auto-show-mode nil)
5085 @node Q5.0.17, Q5.0.18, Q5.0.16, Miscellaneous
5086 @unnumberedsubsec Q5.0.17: How can I get two instances of info?
5088 Before 21.4, you can't. The @code{info} package does not provide for
5089 multiple info buffers. In 21.4, this should be fixed. #### how?
5091 @node Q5.0.18, Q5.0.19, Q5.0.17, Miscellaneous
5092 @unnumberedsubsec Q5.0.18: [This question intentionally left blank]
5094 @node Q5.0.19, Q5.0.20, Q5.0.18, Miscellaneous
5095 @unnumberedsubsec Q5.0.19: Is there something better than LaTeX mode?
5097 @email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes:
5100 The standard TeX modes leave much to be desired, and are somewhat
5101 leniently maintained. Serious TeX users use AUC TeX (@pxref{Q4.7.1}).
5104 @node Q5.0.20, Q5.1.1, Q5.0.19, Miscellaneous
5105 @unnumberedsubsec Q5.0.20: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
5107 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
5109 Here is one of the solutions, we have this in a script called
5110 @file{etc/editclient.sh}.
5113 if gnuclient -batch -eval t >/dev/null 2>&1
5115 exec gnuclient $@{1+"$@@"@}
5117 xemacs -unmapped -f gnuserv-start &
5118 until gnuclient -batch -eval t >/dev/null 2>&1
5122 exec gnuclient $@{1+"$@@"@}
5126 Note that there is a known problem when running XEmacs and 'gnuclient
5127 -nw' on the same TTY.
5130 @node Q5.1.1, Q5.1.2, Q5.0.20, Miscellaneous
5131 @unnumberedsec 5.1: Emacs Lisp Programming Techniques
5132 @unnumberedsubsec Q5.1.1: What is the difference in key sequences between XEmacs and GNU Emacs?
5134 @email{clerik@@naggum.no, Erik Naggum} writes;
5137 Emacs has a legacy of keyboards that produced characters with modifier
5138 bits, and therefore map a variety of input systems into this scheme even
5139 today. XEmacs is instead optimized for X events. This causes an
5140 incompatibility in the way key sequences are specified, but both Emacs
5141 and XEmacs will accept a key sequence as a vector of lists of modifiers
5142 that ends with a key, e.g., to bind @kbd{M-C-a}, you would say
5143 @code{[(meta control a)]} in both Emacsen. XEmacs has an abbreviated
5144 form for a single key, just (meta control a). Emacs has an abbreviated
5145 form for the Control and the Meta modifiers to string-characters (the
5146 ASCII characters), as in @samp{\M-\C-a}. XEmacs users need to be aware
5147 that the abbreviated form works only for one-character key sequences,
5148 while Emacs users need to be aware that the string-character is rather
5149 limited. Specifically, the string-character can accommodate only 256
5150 different values, 128 of which have the Meta modifier and 128 of which
5151 have not. In each of these blocks, only 32 characters have the Control
5152 modifier. Whereas @code{[(meta control A)]} differs from @code{[(meta
5153 control a)]} because the case differs, @samp{\M-\C-a} and @samp{\M-\C-A}
5154 do not. Programmers are advised to use the full common form, both
5155 because it is more readable and less error-prone, and because it is
5156 supported by both Emacsen.
5159 Another (even safer) way to be sure of the key-sequences is to use the
5160 @code{read-kbd-macro} function, which takes a string like @samp{C-c
5161 <up>}, and converts it to the internal key representation of the Emacs
5162 you use. The function is available both on XEmacs and GNU Emacs.
5164 @node Q5.1.2, Q5.1.3, Q5.1.1, Miscellaneous
5165 @unnumberedsubsec Q5.1.2: Can I generate "fake" keyboard events?
5167 I wonder if there is an interactive function that can generate
5168 @dfn{fake} keyboard events. This way, I could simply map them inside
5174 (defun cg--generate-char-event (ch)
5175 "Generate an event, as if ch has been typed"
5176 (dispatch-event (character-to-event ch)))
5178 ;; Backspace and Delete stuff
5179 (global-set-key [backspace]
5180 (lambda () (interactive) (cg--generate-char-event 127)))
5181 (global-set-key [unknown_keysym_0x4]
5182 (lambda () (interactive) (cg--generate-char-event 4)))
5185 @node Q5.1.3, Q5.1.4, Q5.1.2, Miscellaneous
5186 @unnumberedsubsec Q5.1.3: Could you explain @code{read-kbd-macro} in more detail?
5188 The @code{read-kbd-macro} function returns the internal Emacs
5189 representation of a human-readable string (which is its argument).
5193 (read-kbd-macro "C-c C-a")
5194 @result{} [(control ?c) (control ?a)]
5196 (read-kbd-macro "C-c C-. <up>")
5197 @result{} [(control ?c) (control ?.) up]
5200 In GNU Emacs the same forms will be evaluated to what GNU Emacs
5201 understands internally---the sequences @code{"\C-x\C-c"} and @code{[3
5202 67108910 up]}, respectively.
5204 The exact @dfn{human-readable} syntax is defined in the docstring of
5205 @code{edmacro-mode}. I'll repeat it here, for completeness.
5208 Format of keyboard macros during editing:
5210 Text is divided into @dfn{words} separated by whitespace. Except for
5211 the words described below, the characters of each word go directly as
5212 characters of the macro. The whitespace that separates words is
5213 ignored. Whitespace in the macro must be written explicitly, as in
5214 @kbd{foo @key{SPC} bar @key{RET}}.
5218 The special words @kbd{RET}, @kbd{SPC}, @kbd{TAB}, @kbd{DEL}, @kbd{LFD},
5219 @kbd{ESC}, and @kbd{NUL} represent special control characters. The
5220 words must be written in uppercase.
5223 A word in angle brackets, e.g., @code{<return>}, @code{<down>}, or
5224 @code{<f1>}, represents a function key. (Note that in the standard
5225 configuration, the function key @code{<return>} and the control key
5226 @key{RET} are synonymous.) You can use angle brackets on the words
5227 @key{RET}, @key{SPC}, etc., but they are not required there.
5230 Keys can be written by their @sc{ascii} code, using a backslash followed
5231 by up to six octal digits. This is the only way to represent keys with
5235 One or more prefixes @kbd{M-} (meta), @kbd{C-} (control), @kbd{S-}
5236 (shift), @kbd{A-} (alt), @kbd{H-} (hyper), and @kbd{s-} (super) may
5237 precede a character or key notation. For function keys, the prefixes
5238 may go inside or outside of the brackets: @code{C-<down>} @equiv{}
5239 @code{<C-down>}. The prefixes may be written in any order: @kbd{M-C-x}
5240 @equiv{} @kbd{C-M-x}.
5242 Prefixes are not allowed on multi-key words, e.g., @kbd{C-abc}, except
5243 that the Meta prefix is allowed on a sequence of digits and optional
5244 minus sign: @kbd{M--123} @equiv{} @kbd{M-- M-1 M-2 M-3}.
5247 The @code{^} notation for control characters also works: @kbd{^M}
5251 Double angle brackets enclose command names: @code{<<next-line>>} is
5252 shorthand for @kbd{M-x next-line @key{RET}}.
5255 Finally, @code{REM} or @code{;;} causes the rest of the line to be
5256 ignored as a comment.
5259 Any word may be prefixed by a multiplier in the form of a decimal number
5260 and @code{*}: @code{3*<right>} @equiv{} @code{<right> <right> <right>},
5261 and @code{10*foo} @equiv{}
5265 @code{foofoofoofoofoofoofoofoofoofoo}.
5267 Multiple text keys can normally be strung together to form a word, but
5268 you may need to add whitespace if the word would look like one of the
5269 above notations: @code{; ; ;} is a keyboard macro with three semicolons,
5270 but @code{;;;} is a comment. Likewise, @code{\ 1 2 3} is four keys but
5271 @code{\123} is a single key written in octal, and @code{< right >} is
5272 seven keys but @code{<right>} is a single function key. When in doubt,
5276 @node Q5.1.4, Q5.1.5, Q5.1.3, Miscellaneous
5277 @unnumberedsubsec Q5.1.4: What is the performance hit of @code{let}?
5279 In most cases, not noticeable. Besides, there's no avoiding
5280 @code{let}---you have to bind your local variables, after all. Some
5281 pose a question whether to nest @code{let}s, or use one @code{let} per
5282 function. I think because of clarity and maintenance (and possible
5283 future implementation), @code{let}-s should be used (nested) in a way to
5284 provide the clearest code.
5286 @node Q5.1.5, Q5.1.6, Q5.1.4, Miscellaneous
5287 @unnumberedsubsec Q5.1.5: What is the recommended use of @code{setq}?
5290 @item Global variables
5292 You will typically @code{defvar} your global variable to a default
5293 value, and use @code{setq} to set it later.
5295 It is never a good practice to @code{setq} user variables (like
5296 @code{case-fold-search}, etc.), as it ignores the user's choice
5297 unconditionally. Note that @code{defvar} doesn't change the value of a
5298 variable if it was bound previously. If you wish to change a
5299 user-variable temporarily, use @code{let}:
5302 (let ((case-fold-search nil))
5303 ... ; code with searches that must be case-sensitive
5307 You will notice the user-variables by their docstrings beginning with an
5308 asterisk (a convention).
5310 @item Local variables
5312 Bind them with @code{let}, which will unbind them (or restore their
5313 previous value, if they were bound) after exiting from the @code{let}
5314 form. Change the value of local variables with @code{setq} or whatever
5315 you like (e.g. @code{incf}, @code{setf} and such). The @code{let} form
5316 can even return one of its local variables.
5321 ;; iterate through the elements of the list returned by
5322 ;; `hairy-function-that-returns-list'
5323 (let ((l (hairy-function-that-returns-list)))
5325 ... do something with (car l) ...
5329 Another typical usage includes building a value simply to work with it.
5332 ;; Build the mode keymap out of the key-translation-alist
5333 (let ((inbox (file-truename (expand-file-name box)))
5335 ... code dealing with inbox ...
5339 This piece of code uses the local variable @code{inbox}, which becomes
5340 unbound (or regains old value) after exiting the form. The form also
5341 returns the value of @code{inbox}, which can be reused, for instance:
5344 (setq foo-processed-inbox
5349 @node Q5.1.6, Q5.1.7, Q5.1.5, Miscellaneous
5350 @unnumberedsubsec Q5.1.6: What is the typical misuse of @code{setq} ?
5352 A typical misuse is probably @code{setq}ing a variable that was meant to
5353 be local. Such a variable will remain bound forever, never to be
5354 garbage-collected. For example, the code doing:
5357 (defun my-function (whatever)
5359 ... build a large list ...
5363 does a bad thing, as @code{a} will keep consuming memory, never to be
5364 unbound. The correct thing is to do it like this:
5367 (defun my-function (whatever)
5368 (let (a) ; default initialization is to nil
5369 ... build a large list ...
5370 ... and exit, unbinding `a' in the process ...)
5373 Not only is this prettier syntactically, but it makes it possible for
5374 Emacs to garbage-collect the objects which @code{a} used to reference.
5376 Note that even global variables should not be @code{setq}ed without
5377 @code{defvar}ing them first, because the byte-compiler issues warnings.
5378 The reason for the warning is the following:
5381 (defun flurgoze nil) ; ok, global internal variable
5384 (setq flurghoze t) ; ops! a typo, but semantically correct.
5385 ; however, the byte-compiler warns.
5387 While compiling toplevel forms:
5388 ** assignment to free variable flurghoze
5391 @node Q5.1.7, Q5.1.8, Q5.1.6, Miscellaneous
5392 @unnumberedsubsec Q5.1.7: I like the @code{do} form of cl, does it slow things down?
5394 It shouldn't. Here is what Dave Gillespie has to say about cl.el
5398 Many of the advanced features of this package, such as @code{defun*},
5399 @code{loop}, and @code{setf}, are implemented as Lisp macros. In
5400 byte-compiled code, these complex notations will be expanded into
5401 equivalent Lisp code which is simple and efficient. For example, the
5409 are expanded at compile-time to the Lisp forms
5413 (setcar p (cons x (car p)))
5416 which are the most efficient ways of doing these respective operations
5417 in Lisp. Thus, there is no performance penalty for using the more
5418 readable @code{incf} and @code{push} forms in your compiled code.
5420 @emph{Interpreted} code, on the other hand, must expand these macros
5421 every time they are executed. For this reason it is strongly
5422 recommended that code making heavy use of macros be compiled. (The
5423 features labelled @dfn{Special Form} instead of @dfn{Function} in this
5424 manual are macros.) A loop using @code{incf} a hundred times will
5425 execute considerably faster if compiled, and will also garbage-collect
5426 less because the macro expansion will not have to be generated, used,
5427 and thrown away a hundred times.
5429 You can find out how a macro expands by using the @code{cl-prettyexpand}
5433 @node Q5.1.8, Q5.1.9, Q5.1.7, Miscellaneous
5434 @unnumberedsubsec Q5.1.8: I like recursion, does it slow things down?
5436 Yes. Emacs byte-compiler cannot do much to optimize recursion. But
5437 think well whether this is a real concern in Emacs. Much of the Emacs
5438 slowness comes from internal mechanisms such as redisplay, or from the
5439 fact that it is an interpreter.
5441 Please try not to make your code much uglier to gain a very small speed
5442 gain. It's not usually worth it.
5444 @node Q5.1.9, Q5.1.10, Q5.1.8, Miscellaneous
5445 @unnumberedsubsec Q5.1.9: How do I put a glyph as annotation in a buffer?
5447 Here is a solution that will insert the glyph annotation at the
5448 beginning of buffer:
5451 (make-annotation (make-glyph '([FORMAT :file FILE]
5452 [string :data "fallback-text"]))
5458 Replace @samp{FORMAT} with an unquoted symbol representing the format of
5459 the image (e.g. @code{xpm}, @code{xbm}, @code{gif}, @code{jpeg}, etc.)
5460 Instead of @samp{FILE}, use the image file name
5465 @file{/usr/local/lib/xemacs-21.4/etc/recycle.xpm}).
5467 You can turn this to a function (that optionally prompts you for a file
5468 name), and inserts the glyph at @code{(point)} instead of
5471 @node Q5.1.10, Q5.1.11, Q5.1.9, Miscellaneous
5472 @unnumberedsubsec Q5.1.10: @code{map-extents} won't traverse all of my extents!
5474 I tried to use @code{map-extents} to do an operation on all the extents
5475 in a region. However, it seems to quit after processing a random number
5476 of extents. Is it buggy?
5478 No. The documentation of @code{map-extents} states that it will iterate
5479 across the extents as long as @var{function} returns @code{nil}.
5480 Unexperienced programmers often forget to return @code{nil} explicitly,
5481 which results in buggy code. For instance, the following code is
5482 supposed to delete all the extents in a buffer, and issue as many
5483 @samp{fubar!} messages.
5486 (map-extents (lambda (ext ignore)
5488 (message "fubar!")))
5491 Instead, it will delete only the first extent, and stop right there --
5492 because @code{message} will return a non-nil value. The correct code
5496 (map-extents (lambda (ext ignore)
5502 @node Q5.1.11, Q5.2.1, Q5.1.10, Miscellaneous
5503 @unnumberedsubsec Q5.1.11: My elisp program is horribly slow. Is there
5504 an easy way to find out where it spends time?
5507 @email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
5509 Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence},
5510 press a key (say @key{RET} in the Gnus Group buffer), and get the
5511 results using @kbd{M-x profile-results}. It should give you an idea of
5512 where the time is being spent.
5515 @node Q5.2.1, Q5.2.2, Q5.1.11, Miscellaneous
5516 @unnumberedsubsec Q5.2.1: How do I turn off the sound?
5518 Add the following line to your @file{init.el}/@file{.emacs}:
5521 (setq bell-volume 0)
5522 (setq sound-alist nil)
5525 That will make your XEmacs totally silent---even the default ding sound
5526 (TTY beep on TTY-s) will be gone.
5528 Starting with XEmacs 20.2 you can also change these with Customize.
5529 Select from the @code{Options} menu
5530 @code{Advanced (Customize)->Emacs->Environment->Sound->Sound...} or type
5531 @kbd{M-x customize @key{RET} sound @key{RET}}.
5534 @node Q5.2.2, Q5.2.3, Q5.2.1, Miscellaneous
5535 @unnumberedsubsec Q5.2.2: How do I get funky sounds instead of a boring beep?
5537 Make sure your XEmacs was compiled with sound support, and then put this
5538 in your @file{init.el}/@file{.emacs}:
5541 (load-default-sounds)
5544 @c The sound support in XEmacs 19.14 was greatly improved over previous
5547 @node Q5.2.3, Q5.2.4, Q5.2.2, Miscellaneous
5548 @unnumberedsubsec Q5.2.3: What's NAS, how do I get it?
5550 @xref{Q2.0.3}, for an explanation of the @dfn{Network Audio System}.
5552 @node Q5.2.4, Q5.3.1, Q5.2.3, Miscellaneous
5553 @unnumberedsubsec Q5.2.4: Sunsite sounds don't play.
5555 I'm having some trouble with sounds I've downloaded from sunsite. They
5556 play when I run them through @code{showaudio} or cat them directly to
5557 @file{/dev/audio}, but XEmacs refuses to play them.
5559 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
5562 [Many of] These files have an (erroneous) 24byte header that tells about
5563 the format that they have been recorded in. If you cat them to
5564 @file{/dev/audio}, the header will be ignored and the default behavior
5565 for /dev/audio will be used. This happens to be 8kHz uLaw. It is
5566 probably possible to fix the header by piping through @code{sox} and
5567 passing explicit parameters for specifying the sampling format; you then
5568 need to perform a 'null' conversion from SunAudio to SunAudio.
5571 @node Q5.3.1, Q5.3.2, Q5.2.4, Miscellaneous
5572 @unnumberedsec 5.3: Miscellaneous
5573 @unnumberedsubsec Q5.3.1: How do you make XEmacs indent CL if-clauses correctly?
5575 I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the
5576 same amount instead of indenting the 3rd clause differently from the
5579 One way is to add, to @file{init.el}/@file{.emacs}:
5582 (put 'if 'lisp-indent-function nil)
5585 However, note that the package @code{cl-indent} that comes with
5586 XEmacs sets up this kind of indentation by default. @code{cl-indent}
5587 also knows about many other CL-specific forms. To use @code{cl-indent},
5592 (setq lisp-indent-function (function common-lisp-indent-function))
5595 One can also customize @file{cl-indent.el} so it mimics the default
5596 @code{if} indentation @code{then} indented more than the @code{else}.
5600 (put 'if 'common-lisp-indent-function '(nil nil &body))
5603 Also, a new version (1.2) of @file{cl-indent.el} was posted to
5604 comp.emacs.xemacs on 12/9/94. This version includes more documentation
5605 than previous versions. This may prove useful if you need to customize
5606 any indent-functions.
5608 @node Q5.3.2, Q5.3.3, Q5.3.1, Miscellaneous
5609 @unnumberedsubsec Q5.3.2: [This question intentionally left blank]
5611 Obsolete question, left blank to avoid renumbering.
5613 @node Q5.3.3, Q5.3.4, Q5.3.2, Miscellaneous
5614 @unnumberedsubsec Q5.3.3: How can I print WYSIWYG a font-locked buffer?
5616 Font-lock looks nice. How can I print (WYSIWYG) the highlighted
5619 The package @code{ps-print}, which is now included with XEmacs, provides
5620 the ability to do this. The source code contains complete instructions
5621 on its use, in @file{<xemacs_src_root>/lisp/packages/ps-print.el}.
5623 @node Q5.3.4, Q5.3.5, Q5.3.3, Miscellaneous
5624 @unnumberedsubsec Q5.3.4: Getting @kbd{M-x lpr} to work with postscript printer.
5626 My printer is a Postscript printer and @code{lpr} only works for
5627 Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x
5628 lpr-buffer} to work?
5630 Put something like this in your @file{init.el}/@file{.emacs}:
5633 (setq lpr-command "a2ps")
5634 (setq lpr-switches '("-p" "-1"))
5637 If you don't use a2ps to convert ASCII to postscript (why not, it's
5638 free?), replace with the command you do use. Note also that some
5639 versions of a2ps require a @samp{-Pprinter} to ensure spooling.
5641 @node Q5.3.5, Q5.3.6, Q5.3.4, Miscellaneous
5642 @unnumberedsubsec Q5.3.5: How do I specify the paths that XEmacs uses for finding files?
5644 You can specify what paths to use by using a number of different flags
5645 when running configure. See the section MAKE VARIABLES in the top-level
5646 file INSTALL in the XEmacs distribution for a listing of those flags.
5648 Most of the time, however, the simplest fix is: @strong{do not} specify
5649 paths as you might for GNU Emacs. XEmacs can generally determine the
5650 necessary paths dynamically at run time. The only path that generally
5651 needs to be specified is the root directory to install into. That can
5652 be specified by passing the @code{--prefix} flag to configure. For a
5653 description of the XEmacs install tree, please consult the @file{NEWS}
5656 @node Q5.3.6, Q5.3.7, Q5.3.5, Miscellaneous
5657 @unnumberedsubsec Q5.3.6: [This question intentionally left blank]
5659 Obsolete question, left blank to avoid renumbering.
5661 @node Q5.3.7, Q5.3.8, Q5.3.6, Miscellaneous
5662 @unnumberedsubsec Q5.3.7: Can I have the end of the buffer delimited in some way?
5664 Say, with: @samp{[END]}?
5669 (let ((ext (make-extent (point-min) (point-max))))
5670 (set-extent-property ext 'start-closed t)
5671 (set-extent-property ext 'end-closed t)
5672 (set-extent-property ext 'detachable nil)
5673 (set-extent-end-glyph ext (make-glyph [string :data "[END]"])))
5676 Since this is XEmacs, you can specify an icon to be shown on
5677 window-system devices. To do so, change the @code{make-glyph} call to
5678 something like this:
5681 (make-glyph '([xpm :file "~/something.xpm"]
5682 [string :data "[END]"]))
5685 You can inline the @sc{xpm} definition yourself by specifying
5686 @code{:data} instead of @code{:file}. Here is such a full-featured
5687 version that works on both X and TTY devices:
5690 (let ((ext (make-extent (point-min) (point-max))))
5691 (set-extent-property ext 'start-closed t)
5692 (set-extent-property ext 'end-closed t)
5693 (set-extent-property ext 'detachable nil)
5694 (set-extent-end-glyph ext (make-glyph '([xpm :data "\
5696 static char* eye = @{
5705 \"___________`_`_`___b_b_b_b_________`____\",
5706 \"_________`_`_`___b_c_c_c_b_b____________\",
5707 \"_____`_`_`_e___b_b_c_c_c___b___b_______`\",
5708 \"___`_`_e_a___b_b_d___b___b___b___b______\",
5709 \"_`_`_e_a_e___b_b_d_b___b___b___b___b____\",
5710 \"_`_`_a_e_a___b_b_d___b___b___b___b___b__\",
5711 \"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\",
5712 \"___`_`_e_a___b_b_b_d_c___b___b___d_b____\",
5713 \"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\",
5714 \"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\",
5715 \"___`_____`_`_`_`___b_b_b_b_b_b__________\",
5717 [string :data "[END]"]))))
5720 Note that you might want to make this a function, and put it to a hook.
5721 We leave that as an exercise for the reader.
5723 @node Q5.3.8, Q5.3.9, Q5.3.7, Miscellaneous
5724 @unnumberedsubsec Q5.3.8: How do I insert today's date into a buffer?
5729 (insert (current-time-string))
5732 @node Q5.3.9, Q5.3.10, Q5.3.8, Miscellaneous
5733 @unnumberedsubsec Q5.3.9: Are only certain syntactic character classes available for abbrevs?
5735 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
5738 Yes, abbrevs only expands word-syntax strings. While XEmacs does not
5739 prevent you from defining (e.g. with @kbd{C-x a g} or @kbd{C-x a l})
5740 abbrevs that contain special characters, it will refuse to expand
5741 them. So you need to ensure, that the abbreviation contains letters and
5742 digits only. This means that @samp{xd}, @samp{d5}, and @samp{5d} are
5743 valid abbrevs, but @samp{&d}, and @samp{x d} are not.
5745 If this sounds confusing to you, (re-)read the online documentation for
5746 abbrevs (@kbd{C-h i m XEmacs @key{RET} m Abbrevs @key{RET}}), and then come back and
5747 read this question/answer again.
5750 Starting with XEmacs 20.3 this restriction has been lifted.
5752 @node Q5.3.10, Q5.3.11, Q5.3.9, Miscellaneous
5753 @unnumberedsubsec Q5.3.10: How can I get those oh-so-neat X-Face lines?
5755 Firstly there is an ftp site which describes X-faces and has the
5756 associated tools mentioned below, at
5757 @uref{ftp://ftp.cs.indiana.edu:/pub/faces/}.
5763 Create 48x48x1 bitmap with your favorite tool
5766 Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc.,
5767 and then compile the face.
5771 cat file.xbm | xbm2ikon |compface > file.face
5775 Then be sure to quote things that are necessary for emacs strings:
5778 cat ./file.face | sed 's/\\/\\\\/g'
5782 | sed 's/\"/\\\"/g' > ./file.face.quoted
5786 Then set up emacs to include the file as a mail header - there were a
5787 couple of suggestions here---either something like:
5790 (setq mail-default-headers
5791 "X-Face: @email{Ugly looking text string here}")
5794 Or, alternatively, as:
5797 (defun mail-insert-x-face ()
5799 (goto-char (point-min))
5800 (search-forward mail-header-separator)
5803 (insert-file-contents "~/.face")))
5805 (add-hook 'mail-setup-hook 'mail-insert-x-face)
5809 However, 2 things might be wrong:
5811 Some versions of pbmtoicon produces some header lines that is not
5812 expected by the version of compface that I grabbed. So I found I had to
5813 include a @code{tail +3} in the pipeline like this:
5816 cat file.xbm | xbm2ikon | tail +3 |compface > file.face
5819 Some people have also found that if one uses the @code{(insert-file)}
5820 method, one should NOT quote the face string using the sed script .
5822 It might also be helpful to use @email{stig@@hackvan.com, Stig's} script
5823 (included in the compface distribution at XEmacs.org) to do the
5825 @comment For convenience xbm2xface is available for anonymous FTP at
5826 @comment @uref{ftp://ftp.miranova.com/pub/xemacs/xbm2xface.pl}.
5828 Contributors for this item:
5839 @node Q5.3.11, Q5.3.12, Q5.3.10, Miscellaneous
5840 @unnumberedsubsec Q5.3.11: How do I add new Info directories?
5842 You use something like:
5845 (setq Info-directory-list (cons
5846 (expand-file-name "~/info")
5847 Info-default-directory-list))
5850 @email{davidm@@prism.kla.com, David Masterson} writes:
5853 Emacs Info and XEmacs Info do many things differently. If you're trying to
5854 support a number of versions of Emacs, here are some notes to remember:
5858 Emacs Info scans @code{Info-directory-list} from right-to-left while
5859 XEmacs Info reads it from left-to-right, so append to the @emph{correct}
5863 Use @code{Info-default-directory-list} to initialize
5864 @code{Info-directory-list} @emph{if} it is available at startup, but not
5865 all Emacsen define it.
5868 Emacs Info looks for a standard @file{dir} file in each of the
5869 directories scanned from #1 and magically concatenates them together.
5872 XEmacs Info looks for a @file{localdir} file (which consists of just the
5873 menu entries from a @file{dir} file) in each of the directories scanned
5874 from #1 (except the first), does a simple concatenation of them, and
5875 magically attaches the resulting list to the end of the menu in the
5876 @file{dir} file in the first directory.
5879 Another alternative is to convert the documentation to HTML with
5880 texi2html and read it from a web browser like Lynx or W3.
5883 @node Q5.3.12, , Q5.3.11, Miscellaneous
5884 @unnumberedsubsec Q5.3.12: What do I need to change to make printing work?
5886 For regular printing there are two variables that can be customized.
5890 This should be set to a command that takes standard input and sends
5891 it to a printer. Something like:
5894 (setq lpr-command "lp")
5898 This should be set to a list that contains whatever the print command
5899 requires to do its job. Something like:
5902 (setq lpr-switches '("-depson"))
5906 For postscript printing there are three analogous variables to
5910 @item ps-lpr-command
5911 This should be set to a command that takes postscript on standard input
5912 and directs it to a postscript printer.
5914 @item ps-lpr-switches
5915 This should be set to a list of switches required for
5916 @code{ps-lpr-command} to do its job.
5918 @item ps-print-color-p
5919 This boolean variable should be set @code{t} if printing will be done in
5920 color, otherwise it should be set to @code{nil}.
5923 NOTE: It is an undocumented limitation in XEmacs that postscript
5924 printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a
5925 window system environment. It cannot be used outside of X11.
5927 @node MS Windows, Current Events, Miscellaneous, Top
5928 @unnumbered 6 XEmacs on MS Windows
5930 This is part 6 of the XEmacs Frequently Asked Questions list, written by
5931 Hrvoje Niksic and others. This section is devoted to the MS Windows
5937 * Q6.0.1:: What is the status of the XEmacs port to Windows?
5938 * Q6.0.2:: What flavors of MS Windows are supported?
5939 * Q6.0.3:: Where are the XEmacs on MS Windows binaries?
5940 * Q6.0.4:: Can I build XEmacs on MS Windows with X support? Do I need to?
5941 * Q6.0.5:: I'd like to help out. What do I do?
5942 * Q6.0.6:: What are Cygwin and MinGW, and do I need them to run XEmacs?
5943 * Q6.0.7:: What exactly are all the different ways to build XEmacs under Windows?
5945 Building XEmacs on MS Windows
5946 * Q6.1.1:: What compiler/libraries do I need to compile XEmacs?
5947 * Q6.1.2:: How do I compile the native port?
5948 * Q6.1.3:: What do I need for Cygwin?
5949 * Q6.1.4:: How do I compile under Cygwin?
5950 * Q6.1.5:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
5951 * Q6.1.6:: I decided to run with X. Where do I get an X server?
5952 * Q6.1.7:: How do I compile with X support?
5954 Customization and User Interface
5955 * Q6.2.1:: How does the port cope with differences in the Windows user interface?
5956 * Q6.2.2:: How do I change fonts in XEmacs on MS Windows?
5957 * Q6.2.3:: Where do I put my @file{init.el}/@file{.emacs} file?
5958 * Q6.2.4:: How do I get Windows Explorer to associate a file type with XEmacs?
5959 * Q6.2.5:: Is it possible to print from XEmacs?
5962 * Q6.3.1:: Does XEmacs rename all the win32-* symbols to w32-*?
5963 * Q6.3.2:: What are the differences between the various MS Windows emacsen?
5964 * Q6.3.3:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
5965 * Q6.3.4:: What is the porting team doing at the moment?
5968 * Q6.4.1:: XEmacs won't start on Windows.
5969 * Q6.4.2:: Why do I get a blank toolbar on Windows 95?
5972 @node Q6.0.1, Q6.0.2, MS Windows, MS Windows
5973 @unnumberedsec 6.0: General Info
5974 @unnumberedsubsec Q6.0.1: What is the status of the XEmacs port to Windows?
5976 Is XEmacs really ported to MS Windows? What is the status of the port?
5978 Beginning with release 21.0, XEmacs has worked under MS Windows. A
5979 group of dedicated developers actively maintains and improves the
5980 Windows-specific portions of the code. The mailing list at
5981 @email{xemacs-nt@@xemacs.org} is dedicated to that effort (please use
5982 the -request address to subscribe). (Despite its name, XEmacs actually
5983 works on all versions of Windows.)
5985 As of May 2001, XEmacs on MS Windows is stable and full-featured, and
5986 has been so for a year or more -- in fact, some features, such as
5987 printing, actually work better on Windows than native Unix. However,
5988 the internationalization (Mule) support does not work -- although this
5989 is being actively worked on.
5992 @node Q6.0.2, Q6.0.3, Q6.0.1, MS Windows
5993 @unnumberedsubsec Q6.0.2: What flavors of MS Windows are supported? The list name implies NT only.
5995 The list name is misleading, as XEmacs supports and has been compiled on
5996 Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows
5997 XP, and all newer versions of Windows. The MS Windows-specific code is
5998 based on Microsoft Win32 API, and will not work on MS Windows 3.x or on
6001 XEmacs also supports the Cygwin and MinGW development and runtime
6002 environments, where it also uses native Windows code for graphical
6006 @node Q6.0.3, Q6.0.4, Q6.0.2, MS Windows
6007 @unnumberedsubsec Q6.0.3: Are binaries available?
6009 Binaries are available at @uref{http://www.xemacs.org/Download/win32/}
6010 for the native and Cygwin MS Windows versions of 21.4, and the native
6013 The 21.4 binaries use a modified version of the Cygwin installer. Run
6014 the provided @file{setup.exe}, and follow the instructions.
6017 @node Q6.0.4, Q6.0.5, Q6.0.3, MS Windows
6018 @unnumberedsubsec Q6.0.4: Can I build XEmacs on MS Windows with X support? Do I need to?
6020 Yes, you can, but no you do not need to. In fact, we recommend that you
6021 use a native-GUI version unless you have a specific need for an X
6024 @node Q6.0.5, Q6.0.6, Q6.0.4, MS Windows
6025 @unnumberedsubsec Q6.0.5: I'd like to help out. What do I do?
6027 It depends on the knowledge and time you possess. If you are a
6028 programmer, try to build XEmacs and see if you can improve it.
6029 Windows-specific improvements like integration with established
6030 Windows environments are especially sought after.
6032 Otherwise, you can still help by downloading the binaries, using
6033 XEmacs as your everyday editor and reporting bugs you find to the
6036 Another area where we need help is the documentation: We need good
6037 documentation for building XEmacs and for using it. This FAQ is a
6038 small step in that direction.
6040 @node Q6.0.6, Q6.0.7, Q6.0.5, MS Windows
6041 @unnumberedsubsec Q6.0.6: What are Cygwin and MinGW, and do I need them to run XEmacs?
6043 To answer the second part of the question: No, you, you don't need
6044 Cygwin or MinGW to build or to run XEmacs. But if you have them and
6045 want to use them, XEmacs supports these environments.
6047 (One important reason to support Cygwin is that it lets the MS Windows
6048 developers test out their code in a Unix environment without actually
6049 having to have a Unix machine around. For this reason alone, Cygwin
6050 support is likely to remain supported for a long time in XEmacs. Same
6051 goes for the X support under Cygwin, for the same reasons. MinGW
6052 support, on the other hand, depends on volunteers to keep it up to date;
6053 but this is generally not hard.)
6055 Cygwin is a set of tools providing Unix-like API on top of Win32.
6056 It makes it easy to port large Unix programs without significant
6057 changes to their source code. It is a development environment as well
6058 as a runtime environment.
6060 When built with Cygwin, XEmacs supports all display types -- TTY, X &
6061 Win32 GUI, and can be built with support for all three simultaneously.
6062 If you build with Win32 GUI support then the Cygwin version uses the
6063 majority of the Windows-specific code, which is mostly related to
6064 display. If you want to build with X support you need X libraries (and
6065 an X server to display XEmacs on); see @ref{Q6.1.4}. TTY and Win32 GUI
6066 require no additional libraries beyond what comes standard with Cygwin.
6068 The advantages of the Cygwin version are that it integrates well with
6069 the Cygwin environment for existing Cygwin users; uses configure so
6070 building with different features is very easy; and actively supports X &
6071 TTY. Furthermore, the entire Cygwin environment and compiler are free,
6072 whereas Visual C++ costs money.
6074 The disadvantage is that it requires the whole Cygwin environment,
6075 whereas the native port requires only a suitable MS Windows compiler.
6076 Also, it follows the Unix filesystem and process model very closely
6077 (some will undoubtedly view this as an advantage).
6079 See @uref{http://sources.redhat.com/cygwin/} for more information on
6082 MinGW is a collection of header files and import libraries that allow
6083 one to use GCC under the Cygwin environment to compile and produce
6084 exactly the same native Win32 programs that you can using Visual C++.
6085 Programs compiled with MinGW make use of the standard Microsoft runtime
6086 library @file{MSVCRT.DLL}, present on all Windows systems, and look,
6087 feel, and act like a standard Visual-C-produced application. (The only
6088 difference is the compiler.) This means that, unlike a
6089 standardly-compiled Cygwin application, no extra runtime support
6090 (e.g. Cygwin's @file{cygwin1.dll}) is required. This, along with the
6091 fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y
6092 environment, for those die-hard Unix hackers out there), is the main
6093 advantage of MinGW. It is also potentially faster than Cygwin because
6094 it has less overhead when calling Windows, but you lose the POSIX
6095 emulation layer, which makes Unix programs harder to port. (But this is
6096 irrelevant for XEmacs since it's already ported to Win32.)
6098 See @uref{http://www.mingw.org/} for more information on MinGW.
6100 @node Q6.0.7, Q6.1.1, Q6.0.6, MS Windows
6101 @unnumberedsubsec Q6.0.7: What exactly are all the different ways to build XEmacs under Windows?
6103 XEmacs can be built in several ways in the MS Windows environment.
6105 The standard way is what we call the "native" port. It uses the Win32
6106 API and has no connection with X whatsoever -- it does not require X
6107 libraries to build, nor does it require an X server to run. The native
6108 port is the most reliable version and provides the best graphical
6109 support. Almost all development is geared towards this version, and
6110 there is little reason not to use it.
6112 The second way to build is the Cygwin port. It takes advantage of
6113 Cygnus emulation library under Win32. @xref{Q6.0.6}, for more
6116 A third way is the MinGW port. It uses the Cygwin environment to build
6117 but does not require it at runtime. @xref{Q6.0.6}, for more
6120 Finally, you might also be able to build the non-Cygwin, non-MinGW "X"
6121 port. This was actually the first version of XEmacs that ran under MS
6122 Windows, and although the code is still in XEmacs, it's essentially
6123 orphaned and it's unlikely it will compile without a lot of work. If
6124 you want an MS Windows versin of XEmacs that supports X, use the Cygwin
6125 version. (The X support there is actively maintained, so that Windows
6126 developers can test the X support in XEmacs.)
6129 @node Q6.1.1, Q6.1.2, Q6.0.7, MS Windows
6130 @unnumberedsec 6.1: Building XEmacs on MS Windows
6131 @unnumberedsubsec Q6.1.1: What compiler/libraries do I need to compile XEmacs?
6133 You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have
6134 some beta testers currently trying to compile with VC.NET, aka version
6135 7.0, but we can't yet report complete success.) For the Cygwin and MinGW
6136 versions, you need the Cygwin environment, which comes with GCC, the
6137 compiler used for those versions. @xref{Q6.0.6}, for more information
6138 on Cygwin and MinGW.
6140 @node Q6.1.2, Q6.1.3, Q6.1.1, MS Windows
6141 @unnumberedsubsec Q6.1.2: How do I compile the native port?
6143 Please read the file @file{nt/README} in the XEmacs distribution, which
6144 contains the full description.
6146 @node Q6.1.3, Q6.1.4, Q6.1.2, MS Windows
6147 @unnumberedsubsec Q6.1.3: What do I need for Cygwin?
6149 You can find the Cygwin tools and compiler at:
6151 @uref{http://sources.redhat.com/cygwin/}
6153 Click on the @samp{Install now!} link, which will download a file
6154 @file{setup.exe}, which you can use to download everything else. (You
6155 will need to pick a mirror site; @samp{mirrors.rcn.net} is probably the
6156 best.) You should go ahead and install everything -- you'll get various
6157 ancillary libraries that XEmacs needs or likes, e.g. XPM, PNG, JPEG,
6160 If you want to compile under X, you will also need the X libraries; see
6164 @node Q6.1.4, Q6.1.5, Q6.1.3, MS Windows
6165 @unnumberedsubsec Q6.1.4: How do I compile under Cygwin?
6167 Similar as on Unix; use the usual `configure' and `make' process.
6168 Some problems to watch out for:
6172 make sure HOME is set. This controls where you
6173 @file{init.el}/@file{.emacs} file comes from;
6176 CYGWIN needs to be set to tty for process support to work, e.g. CYGWIN=tty;
6179 picking up some other grep or other UNIX-like tools can kill configure;
6182 static heap too small, adjust @file{src/sheap-adjust.h} to a more positive
6186 (Unconfirmed) The Cygwin version doesn't understand
6187 @file{//machine/path} type paths so you will need to manually mount a
6188 directory of this form under a unix style directory for a build to work
6192 If you're building @strong{WITHOUT} X11, don't forget to change symlinks
6193 @file{/usr/lib/libXpm.a} and @file{/usr/lib/libXpm.dll.a} to point to
6194 the non-X versions of these libraries. By default they point to the X
6198 /usr/lib/libXpm.a -> /usr/lib/libXpm-noX.a
6199 /usr/lib/libXpm.dll.a -> /usr/lib/libXpm-noX.dll.a
6204 Other problems are listed in the @file{PROBLEMS} file, in the top-level
6205 directory of the XEmacs sources.
6210 @node Q6.1.5, Q6.1.6, Q6.1.4, MS Windows
6211 @unnumberedsubsec Q6.1.5: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})?
6213 Similar to the method for Unix. Things to remember:
6217 Specify the target host on the command line for @file{./configure}, e.g.
6218 @samp{./configure i586-pc-mingw32}.
6221 Be sure that your build directory is mounted such that it has the
6222 same path either as a cygwin path (@file{/build/xemacs}) or as a Windows
6223 path (@file{c:\build\xemacs}).
6226 Build @samp{gcc -mno-cygwin} versions of the extra libs, i.e. @file{libpng},
6227 @file{compface}, etc.
6230 Specify the target location of the extra libs on the command line
6231 to @file{configure}, e.g.
6232 @samp{./configure --site-prefixes=/build/libs i586-pc-mingw32}.
6236 @node Q6.1.6, Q6.1.7, Q6.1.5, MS Windows
6237 @unnumberedsubsec Q6.1.6: I decided to run with X. Where do I get an X server?
6239 As of May 2001, we are recommending that you use the port of XFree86 to
6240 Cygwin. This has recently stabilized, and will undoubtedly soon make
6241 most other MS Windows X servers obsolete. It is what the Windows
6242 developers use to test the MS Windows X support.
6244 To install, go to @uref{http://xfree86.cygwin.com/}. There is a
6245 detailed description on that site of exactly how to install it. This
6246 installation also provides the libraries, include files, and other stuff
6247 needed for development; a large collection of internationalized fonts;
6248 the standard X utilities (xterm, twm, etc.) -- in a word, the works.
6250 NOTE: As of late May 2001, there is a bug in the file
6251 @file{startxwin.bat}, used to start X Windows. It passes the option
6252 @samp{-engine -4} to the X server, which is bogus -- you need to edit
6253 the file and change it to @samp{-engine 4}.
6256 @node Q6.1.7, Q6.2.1, Q6.1.6, MS Windows
6257 @unnumberedsubsec Q6.1.7: How do I compile with X support?
6259 To compile under Cygwin, all you need to do is install XFree86
6260 (@pxref{Q6.1.6}). Once installed, @file{configure} should automatically
6261 find the X libraries and compile with X support.
6263 As noted above, the non-Cygwin X support is basically orphaned, and
6264 probably won't work. But if it want to try, it's described in
6265 @file{nt/README} in some detail. Basically, you need to get X11
6266 libraries from ftp.x.org, and compile them. If the precompiled versions
6267 are available somewhere, we don't know of it.
6270 @node Q6.2.1, Q6.2.2, Q6.1.7, MS Windows
6271 @unnumberedsec 6.2: Customization and User Interface
6272 @unnumberedsubsec Q6.2.1: How does the port cope with differences in the Windows user interface?
6274 XEmacs (and Emacs in general) UI is pretty different from what is
6275 expected of a typical MS Windows program. How does the MS Windows port
6278 As a general rule, we follow native MS Windows conventions as much as
6279 possible. In cases where there's a clear UI conflict, we currently use
6280 normal Unix XEmacs behavior by default, but make sure the MS Windows
6281 "look and feel" (mark via shift-arrow, self-inserting deletes region,
6282 Alt selects menu items, etc.) is easily configurable (respectively:
6283 using the variable @code{shifted-motion-keys-select-region} in 21.4 and
6284 above [it's in fact the default in these versions], or the
6285 @file{pc-select} package; using the @file{pending-del} package; and
6286 setting the variable @code{menu-accelerator-enabled} to
6287 @code{menu-force} in 21.4 and above). In fact, if you use the sample
6288 @file{init.el} file as your init file, you will get all these behaviors
6289 automatically turned on.
6291 In future versions, some of these features might be turned on by
6292 default in the MS Windows environment.
6295 @node Q6.2.2, Q6.2.3, Q6.2.1, MS Windows
6296 @unnumberedsubsec Q6.2.2: How do I change fonts in XEmacs on MS Windows?
6298 In 21.4 and above, use the font menu. In all versions, you can change
6299 font manually. For example:
6302 (set-face-font 'default "Lucida Console:Regular:10")
6303 (set-face-font 'modeline "MS Sans Serif:Regular:10")
6307 @node Q6.2.3, Q6.2.4, Q6.2.2, MS Windows
6308 @unnumberedsubsec Q6.2.3: Where do I put my @file{init.el}/@file{.emacs} file?
6310 @file{init.el} is the name of the init file starting with 21.4, and is
6311 located in the subdirectory @file{.xemacs/} of your home directory. In
6312 prior versions, the init file is called @file{.emacs} and is located in
6313 your home directory. Your home directory under Windows is determined by
6314 the @samp{HOME} environment variable. If this is not set, it defaults to
6317 To set this variable, modify @file{AUTOEXEC.BAT} under Windows 95/98, or
6318 select @samp{Control Panel->System->Advanced->Environment Variables...}
6319 under Windows NT/2000.
6322 @node Q6.2.4, Q6.2.5, Q6.2.3, MS Windows
6323 @unnumberedsubsec Q6.2.4: How do I get Windows Explorer to associate a file type with XEmacs?
6325 @unnumberedsubsubsec Associating a new file type with XEmacs.
6327 In Explorer select @samp{View/Options/File Types}, press @samp{[New
6328 Type...]} and fill in the dialog box, e.g.:
6331 Description of type: Emacs Lisp source
6332 Associated extension: el
6333 Content Type (MIME): text/plain
6336 then press @samp{[New...]} and fill in the @samp{Action} dialog box as
6343 Application used to perform action:
6344 D:\Full\path\for\xemacs.exe "%1"
6354 DDE Application Not Running:
6361 @unnumberedsubsubsec Associating an existing file type with XEmacs.
6363 In Explorer select @samp{View/Options/File Types}. Click on the file
6364 type in the list and press @samp{[Edit...]}. If the file type already
6365 has an @samp{Open} action, double click on it and fill in the
6366 @samp{Action} dialog box as described above; otherwise create a new
6369 If the file type has more than one action listed, you probably want to
6370 make the @samp{Open} action that you just edited the default by clicking on
6371 it and pressing @samp{Set Default}.
6373 Note for Windows 2000 users: Under Windows 2000, get to @samp{File Types}
6374 using @samp{Control Panel->Folder Options->File Types}.
6377 @node Q6.2.5, Q6.3.1, Q6.2.4, MS Windows
6378 @unnumberedsubsec Q6.2.5: Is it possible to print from XEmacs?
6380 As of 21.4, printing works on Windows, using simply @samp{File->Print},
6381 and can be configured with @samp{File->Page Setup}.
6383 Prior to 21.4, there is no built-in support, but there are some clever
6384 hacks out there. If you know how, please let us know and we'll put it
6388 @node Q6.3.1, Q6.3.2, Q6.2.5, MS Windows
6389 @unnumberedsec 6.3: Miscellaneous
6390 @unnumberedsubsec Q6.3.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
6392 In his flavor of Emacs 20, Richard Stallman has renamed all the @samp{win32-*}
6393 symbols to @samp{w32-*}. Does XEmacs do the same?
6395 We consider such a move counter-productive, thus we do not use the
6396 @samp{w32} prefix. (His rather questionable justification was that he
6397 did not consider Windows to be a "winning" platform.) However, the name
6398 @samp{Win32} is not particularly descriptive outside the Windows world,
6399 and using just @samp{windows-} would be too generic. So we chose a
6400 compromise, the prefix @samp{mswindows-} for Windows-related variables
6403 Thus all the XEmacs variables and functions directly related to either
6404 the Windows GUI or OS are prefixed @samp{mswindows-} (except for a
6405 couple of debugging variables, prefixed @samp{debug-mswindows-}). From
6406 an architectural perspective, however, we believe that this is mostly a
6407 non-issue because there should be a very small number of
6408 window-systems-specific variables anyway. Whenever possible, we try to
6409 provide generic interfaces that apply to all window systems.
6412 @c The user variables
6413 @c that share functionality with existing NT Emacs variables are be named
6414 @c with our convention, but we provide the GNU Emacs names as
6415 @c compatibility aliases.
6417 @node Q6.3.2, Q6.3.3, Q6.3.1, MS Windows
6418 @unnumberedsubsec Q6.3.2: What are the differences between the various MS Windows emacsen?
6420 XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing.
6421 Could you briefly explain the differences between them?
6423 Here is a recount of various Emacs versions running on MS Windows:
6433 Beginning with XEmacs 19.12, XEmacs' architecture was redesigned
6434 in such a way to allow clean support of multiple window systems. At
6435 this time the TTY support was added, making X and TTY the first two
6436 "window systems" XEmacs supported. The 19.12 design is the basis for
6437 the current native MS Windows code.
6440 Some time during 1997, David Hobley (soon joined by Marc Paquette)
6441 imported some of the NT-specific portions of GNU Emacs, making XEmacs
6442 with X support compile under Windows NT, and creating the "X" port.
6445 Several months later, Jonathan Harris sent out initial patches to use
6446 the Win32 API, thus creating the native port. Since then, various
6447 people have contributed, including Kirill M. Katsnelson (contributed
6448 support for menubars, subprocesses and network, as well as loads of
6449 other code), Andy Piper (ported XEmacs to Cygwin environment,
6450 contributed Windows unexec, Windows-specific glyphs and toolbars code,
6451 and more), Ben Wing (loads of improvements; currently the most active MS
6452 Windows developer), Jeff Sparkes (contributed scrollbars support) and
6462 GNU Emacs features support for MS-DOS and DJGPP (D. J. Delorie's DOS
6463 port of GCC). Such an Emacs is heavily underfeatured, because it does
6464 not supports long file names, lacks proper subprocesses support, and
6465 is far too big compared with typical DOS editors.
6469 GNU Emacs compiled with Win32
6474 Starting with version 19.30, it has been possible to compile GNU Emacs
6475 under MS Windows using the DJGPP compiler and X libraries. The result
6476 is very similar to GNU Emacs compiled under MS DOS, except that it
6477 supports longer file names, etc. This "port" is similar to the "X"
6478 flavor of XEmacs on MS Windows.
6487 NT Emacs is a version of GNU Emacs modified to compile and run under MS
6488 Windows 95 and NT using the native Win32 API. As such, it is close in
6489 spirit to the XEmacs "native" port.
6492 NT Emacs has been written by Geoff Voelker, and more information can be
6497 @uref{http://www.cs.washington.edu/homes/voelker/ntemacs.html}.
6506 Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X
6507 compatibility libraries. Win-Emacs was written by Ben Wing. The MS
6508 Windows code never made it back to Lucid Emacs, and its creator (Pearl
6509 Software) has long since gone out of business.
6518 GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
6519 port of Gcc). Such an Emacs is heavily underfeatured, because it does
6520 not support long file names, lacks proper subprocesses support, and
6521 is far too big compared to typical DOS editors.
6525 GNU Emacs compiled with Win32
6530 Starting with version 19.30, it has been possible to compile GNU Emacs
6531 under MS Windows using the DJGPP compiler and X libraries. The result
6532 is is very similar to GNU Emacs compiled under MS DOS, only it
6533 supports longer file names, etc. This "port" is similar to the "X"
6534 flavor of XEmacs on MS Windows.
6540 @node Q6.3.3, Q6.3.4, Q6.3.2, MS Windows
6541 @unnumberedsubsec Q6.3.3: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed?
6545 The console was there because @file{temacs} (and in turn, @file{xemacs})
6546 was a console application, and Windows typically creates a new
6547 console for a console process unless the creating process requests that
6548 one isn't created. This used to be fixed with @file{runemacs}, a small
6549 Windows application that existed merely to start @file{xemacs}, stating
6550 that it didn't want a console.
6552 XEmacs 21.4 fixes this cleanly by the virtue of being a true "GUI"
6553 application. The explanation of what that means is included for
6556 When building an application to be run in a Win32 environment, you must
6557 state which sub-system it is to run in. Valid subsystems include
6558 "console" and "gui". The subsystem you use affects the run time
6559 libraries linked into your application, the start up function that is
6560 run before control is handed over to your application, the entry point
6561 to your program, and how Windows normally invokes your program. (Console
6562 programs automatically get a console created for them at startup if
6563 their stdin/stdout don't point anywhere useful, which is the case when
6564 run from the GUI. This is a stupid design, of course -- instead, the
6565 console should get created only when the first I/O actually occurs!
6566 GUI programs have an equally stupid design: When called from
6567 @file{CMD.EXE}/@file{COMMAND.COM}, their stdin/stdout will be set to
6568 point nowhere useful, even though the command shell has its own
6569 stdin/stdout. It's as if someone who had learned a bit about stdio but
6570 had no actual knowledge of interprocess communication designed the
6571 scheme; unfortunately, the whole process-communication aspect of the
6572 Win32 API is equally badly designed.) For example, the entry point for a
6573 console app is "main" (which is what you'd expect for a C/C++ program),
6574 but the entry point for a "gui" app is "WinMain". This confuses and
6575 annoys a lot of programmers who've grown up on Unix systems, where the
6576 kernel doesn't really care whether your application is a gui program or
6579 For reasons not altogether clear, and are lost in the mists of time and
6580 tradition, XEmacs on Win32 started out as a console application, and
6581 therefore a console was automatically created for it. (It may have been
6582 made a console application partly because a console is needed in some
6583 circumstances, especially under Win95, to interrupt, terminate, or send
6584 signals to a child process, and because of the bogosity mentioned above
6585 with GUI programs and the standard command shell. Currently, XEmacs
6586 just creates and immediately hides a console when necessary, and
6587 works around the "no useful stdio" problem by creating its own console
6588 window as necessary to display messages in.)
6591 @node Q6.3.4, Q6.4.1, Q6.3.3, MS Windows
6592 @unnumberedsubsec Q6.3.4: What is the porting team doing at the moment?
6596 The porting team is continuing work on the MS Windows-specific code.
6597 Major projects are the development of Mule (internationalization)
6598 support for Windows and the improvement of the widget support (better
6599 support for dialog boxes, buttons, edit fields, and similar UI
6603 @node Q6.4.1, Q6.4.2, Q6.3.4, MS Windows
6604 @unnumberedsec 6.3: Troubleshooting
6605 @unnumberedsubsec Q6.4.1 XEmacs won't start on Windows.
6607 XEmacs relies on a process called "dumping" to generate a working
6608 executable. Under MS-Windows this process effectively fixes the memory
6609 addresses of information in the executable. When XEmacs starts up it tries
6610 to reserve these memory addresses so that the dumping process can be
6611 reversed -- putting the information back at the correct addresses.
6612 Unfortunately some .DLLs (for instance the soundblaster driver) occupy
6613 memory addresses that can conflict with those needed by the dumped XEmacs
6614 executable. In this instance XEmacs will fail to start without any
6615 explanation. Note that this is extremely machine specific.
6617 21.1.10 includes a fix for this that makes more intelligent guesses
6618 about which memory addresses will be free, and this should cure the
6619 problem for most people. 21.4 implements "portable dumping", which
6620 eliminates the problem altogether. We recommend you use the 21.4
6621 binaries, but you can use the 21.1 binaries if you are very paranoid
6622 about stability. @xref{Q6.0.3}.
6624 @node Q6.4.2, , Q6.4.1, MS Windows
6625 @unnumberedsubsec Q6.4.2 Why do I get a blank toolbar on Windows 95?
6627 You need at least version 4.71 of the system file @file{comctl32.dll}.
6628 The updated version is supplied with Internet Explorer 4 and later but if
6629 you are avoiding IE you can also download it from the Microsoft web
6630 site. Go into support and search for @file{comctl32.dll}. The download
6631 is a self-installing executable.
6634 @node Current Events, , MS Windows, Top
6635 @unnumbered 7 What the Future Holds
6637 This is part 7 of the XEmacs Frequently Asked Questions list. This
6638 section will change frequently, and (in theory) should contain any
6639 interesting items that have transpired recently. (But in practice it's
6640 not getting updated like this.)
6642 This section also contains descriptions of the new features in all the
6643 recent releases of XEmacs. For the most part, the information below is
6644 a synopsis of the more complete information that can be found in the
6645 file @file{NEWS} in the @file{etc} directory of the XEmacs distribution.
6646 You can view this file in XEmacs using @kbd{C-h n} or the @samp{Help}
6649 Information on older versions of XEmacs can be find in @file{ONEWS} in
6650 the same directory, or @file{OONEWS} for really old versions.
6654 * Q7.0.1:: What new features will be in XEmacs soon?
6655 * Q7.0.2:: What's new in XEmacs 21.4?
6656 * Q7.0.3:: What's new in XEmacs 21.1?
6657 * Q7.0.4:: What's new in XEmacs 20.4?
6658 * Q7.0.5:: What's new in XEmacs 20.3?
6659 * Q7.0.6:: What's new in XEmacs 20.2?
6662 @node Q7.0.1, Q7.0.2, Current Events, Current Events
6663 @unnumberedsec 7.0: Changes
6664 @unnumberedsubsec Q7.0.1: What new features will be in XEmacs soon?
6668 @node Q7.0.2, Q7.0.3, Q7.0.1, Current Events
6669 @unnumberedsubsec Q7.0.2: What's new in XEmacs 21.4?
6671 21.4 was the "stable" version of the 21.2 series, which was considered
6672 "experimental" throughout its life; thus there were no "official"
6673 releases at all. In essence, XEmacs is now following the "alternating"
6674 scheme of Linux, where at any point there are at least two different
6675 development branches, one "stable" and one "experimental". Periodic
6676 releases happen in both branches, but those in the experimental branch
6677 are not tested as well, and there's no guarantee they will work at all.
6678 The experiemental branch is open to any and all code that's acceptable
6679 to the developers; the stable branch, however, is in general limited
6680 only to bug fixes, and all contributions are carefully reviewed to make
6681 sure they will increase and not decrease stability.
6683 21.3 never existed at all; it was decided to follow the Linux scheme
6684 exactly, where odd-numbered series are experimental and even-numbered
6687 The following lists summarizes the essential changes made in this
6688 version. For a fuller list, see the @file{NEWS} in the @file{etc}
6689 directory of the XEmacs distribution, or use @kbd{C-h n} or the
6690 @samp{Help} menu to view this file inside of XEmacs.
6692 @unnumberedsubsubsec User-visible changes in XEmacs 21.4
6697 The delete key now deletes forward by default.
6699 Shifted motion keys now select text by default.
6701 You can now build XEmacs with support for GTK+ widget set.
6703 ~/.xemacs/init.el is now the preferred location for the init
6704 file. (XEmacs now supports a `~/.xemacs/init.el' startup file. Custom
6705 file will move to ~/.xemacs/custom.el.)
6707 Much-improved sample init.el, showing how to use many useful features.
6709 XEmacs support for menu accelerators has been much improved.
6711 Default menubar improvements. (Default menubar has many new commands and
6712 better organization. The font-menu is now available under MS Windows.)
6714 Dialog box improvements, including a real file dialog box. (XEmacs now has a proper file dialog box under MS Windows (and GTK)! The old clunky file dialog box is improved. Keyboard traversal now works correctly in MS Windows dialog boxes. There is a Search dialog box available from Edit->Find...)
6718 There is a new MS Windows installer, netinstall, ported from Cygwin.
6720 The subprocess quote-handling mechanism under Windows is much improved.
6722 Printing support now available under MS Windows.
6724 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).)
6726 Mail spool locking now works correctly.
6728 International support changes. (The default coding-priority-list is now
6729 safer. International keysyms are now supported under X. MS Windows
6730 1251 code page now supported. Czech, Thai, Cyrillic-KOI8, Vietnamese,
6731 Ethiopic now supported. Proper support for words in Latin 3 and Latin
6734 Help buffers contain hyperlinks, and other changes.
6736 The modeline's text is now scrollable.
6738 The mouse wheel under MS Windows now functions correctly.
6740 Interactive searching and matching case improvements. (Incremental search will now highlight all visible matches. Interactive searches always respect uppercase characters.)
6742 Rectangle functions rewritten to avoid inserting extra spaces.
6744 New command `kill-entire-line' that always kills the entire line.
6746 Default values correctly stored in minibuffer histories.
6748 You can now create "indirect buffers", like in GNU Emacs.
6750 Pixel-based scrolling has been implemented.
6752 Operation progress can be displayed using graphical widgets.
6754 User names following a tilde can now be completed at file name prompts.
6756 XEmacs can now play sound using Enlightenment Sound Daemon (ESD).
6758 X-Face support is now available under MS Windows.
6760 The PostgreSQL Relational Database Management System is now supported.
6762 Indentation no longer indents comments that begin at column zero.
6764 Face and variable settings can have comments in Customize.
6766 New locations for early package hierarchies.
6768 The `auto-save' library has been greatly improved.
6770 New variable `mswindows-alt-by-itself-activates-menu'.
6772 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.)
6774 Etags changes. See @file{NEWS} for full details.
6777 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.4
6781 @c APA: Texi2html produces invalid HTML from an empty list of bullets!
6782 @c Please uncomment following list when it does contain bullets.
6786 @node Q7.0.3, Q7.0.4, Q7.0.2, Current Events
6787 @unnumberedsubsec Q7.0.3: What's new in XEmacs 21.1?
6789 21.1 was the "stable" version of "experimental" 21.0 series.
6792 The following lists summarizes the essential changes made in this
6793 version. For a fuller list, see the @file{NEWS} in the @file{etc}
6794 directory of the XEmacs distribution, or use @kbd{C-h n} or the
6795 @samp{Help} menu to view this file inside of XEmacs.
6797 @unnumberedsubsubsec User-visible changes in XEmacs 21.1
6802 XEmacs is now supported under Microsoft Windows 95/98 and Windows NT
6803 operating systems. To discuss Windows-specific issues, subscribe to the
6804 mailing list at @email{xemacs-nt-request@@xemacs.org}.
6807 XEmacs has been unbundled into constituent installable packages.
6810 @strong{Other notable changes}: The @samp{Options} menu has been ported to
6811 Custom; XEmacs now is able to choose X visuals and use private
6812 colormaps; You can drag the vertical divider of "horizontally"
6813 (side-by-side) split windows.
6816 @strong{Building changes}: XEmacs can be built with support for 31-bit Lisp
6817 integers and 32-bit pointers (previously, it was 28-bit integers and
6818 pointers); XEmacs can be built with LDAP support; @file{dir} files can be
6819 removed in the Info subsystem, and will be regenerated on-the-fly.
6822 @strong{New packages}: @file{imenu}, @file{popper}, @file{gdb-highlight}
6825 @strong{Package changes}: Many changes to @file{cc-mode}, @file{gnus},
6826 @file{gnuclient}. See @file{NEWS} for full details.
6829 @strong{New commands, variables and functions}:
6830 @code{center-to-window-line} (like @code{recenter} but doesn't force a
6831 redisplay); variable @code{user-full-name} (customize what your full
6832 name looks like in mail); @kbd{M-x customize-changed-options} (customize
6833 options whose default values changes because you upgraded your XEmacs);
6834 @kbd{M-x add-log-convert} (converts an old-style ChangeLog buffer to
6835 new-style); @kbd{M-x zap-up-to-char} (like @code{zap-to-char} but
6836 doesn't delete the char searched for); commands to store, retrieve and
6837 increment numbers in registers, useful for macros.
6840 @strong{Changes to commands, variables, and functions}: @kbd{M-x
6841 query-replace} and friends operate only on the region when it's active;
6842 @code{echo-keystrokes} can now be a floating-point number; @kbd{M-.}
6843 searches exact tag matches before inexact ones; function
6844 @code{user-full-name} with no arguments returns the var
6845 @code{user-full-name}; a prefix arg to @kbd{M-:} and @kbd{C-h c} inserts
6846 the result in the current buffer.
6849 @strong{Other changes}: Under X, new application class @samp{XEmacs};
6850 byte-compilation of user-specs now works.
6853 @strong{XEmacs/Mule (internationalization) changes}: Mule support now
6854 works on TTY's; Egg/SJ3 input method now officially supported (Quail and
6855 Egg/Skk already available through LEIM since 20.3); localized Japanese
6856 menubars if XEmacs is built with the right support.
6860 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.1
6865 @strong{Specifier changes}: The window locale now has a higher
6866 precedence than the buffer locale when instantiating; new macro
6867 @code{let-specifier}; new specifiers
6868 @code{vertical-scrollbar-visible-p}, horizontal-scrollbar-visible-p',
6869 @code{scrollbar-on-left-p}, @code{scrollbar-on-top-p},
6870 @code{vertical-divider-always-visible-p},
6871 @code{vertical-divider-shadow-thickness},
6872 @code{vertical-divider-line-width}, @code{vertical-divider-spacing};
6873 specifiers and symbols whose value is a specifier allowed as modeline
6877 @strong{Frame focus changes}: @code{focus-follows-mouse} works like FSF,
6878 prevents any attempt to permanently change the selected frame; new
6879 function @code{focus-frame} sets the window system focus a frame; new
6880 special forms @code{save-selected-frame} and @code{with-selected-frame}.
6883 @strong{Window function changes}: @code{select-window} now has optional
6884 argument @var{NORECORD} to inhibit recording a buffer change;
6885 @code{vertical-motion} now correctly handles optional @var{WINDOW}
6886 argument and has new optional argument @var{PIXELS}, to have the
6887 returned values be in pixels; new function
6888 @code{vertical-motion-pixels}; new functions
6889 @code{window-text-area-pixel-@{width,height,edges@}}; new functions
6890 @code{shrink-window-pixels} and @code{enlarge-window-pixels}; new
6891 function @code{window-displayed-text-pixel-height}.
6894 @strong{Other function changes}: Arithmetic comparison functions
6895 @code{<}, @code{>}, @code{=}, @code{/=} now accept a variable number of
6896 arguments; hashtables now have a consistent read/print syntax; keyword
6897 symbols cannot be set to a value other than themselves; @code{concat} no
6898 longer accepts integer arguments; new function @code{string}, like
6899 @code{list}, @code{vector}, etc.; new function @code{temp-directory}
6900 (OS-independent way to get a temp directory); @code{load-average} has
6901 optional argument @var{USE-FLOATS}; @code{make-event} implemented
6902 completely; new function @code{function-interactive} (returns a
6903 function's interactive spec); new functions @code{lmessage},
6904 @code{lwarn} (printf-like versions of @code{display-wessage},
6905 @code{display-warning}); new keyword @code{:version} to
6909 @strong{Performance}: when the new GNU Malloc aka Doug Lea Malloc is
6910 available, it will be used (better performance on libc6 Linux systems);
6911 tracking line-numbers in modeline is now efficient; profiling records a
6912 call-count of all called functions, retrievable through
6913 @code{profile-call-count-results}.
6916 @strong{Startup and path searching}: code to assemble paths at startup
6917 rewritten for new package system; new function @code{split-path} (splits
6918 by @code{path-separator}); @code{Info-default-directory-list} obsolete,
6919 use @code{Info-directory-list} instead; site-lisp is deprecated and no
6920 longer on the load-path by default.
6924 @node Q7.0.4, Q7.0.5, Q7.0.3, Current Events
6925 @unnumberedsubsec Q7.0.4: What's new in XEmacs 20.4?
6927 XEmacs 20.4 is a bugfix release with no user-visible changes.
6928 @c Filled in from NEWS file of 20.5-b33
6930 @node Q7.0.5, Q7.0.6, Q7.0.4, Current Events
6931 @unnumberedsubsec Q7.0.5: What's new in XEmacs 20.3?
6933 XEmacs 20.3 was released in November 1997. It contains many bugfixes,
6934 and a number of new features, including Autoconf 2 based configuration,
6935 additional support for Mule (Multi-language extensions to Emacs), many
6936 more customizations, multiple frames on TTY-s, support for multiple info
6937 directories, an enhanced gnuclient, improvements to regexp matching,
6938 increased MIME support, and many, many synches with GNU Emacs 20.
6940 The XEmacs/Mule support has been only seriously tested in a Japanese
6941 locale, and no doubt many problems still remain. The support for
6942 ISO-Latin-1 and Japanese is fairly strong. MULE support comes at a
6943 price---about a 30% slowdown from 19.16. We're making progress on
6944 improving performance and XEmacs 20.3 compiled without Mule (which is
6945 the default) is definitely faster than XEmacs 19.16.
6947 XEmacs 20.3 is the first non-beta v20 release, and will be the
6948 basis for all further development.
6950 @node Q7.0.6, , Q7.0.5, Current Events
6951 @unnumberedsubsec Q7.0.6: What's new in XEmacs 20.2?
6953 The biggest changes in 20.2 include integration of EFS (the next
6954 generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a
6955 major mode for editing Tex and LaTeX, and a lot of other stuff). Many
6956 bugs from 20.0 have been fixed for this release. 20.2 also contains a
6957 new system for customizing XEmacs options, invoked via @kbd{M-x
6960 XEmacs 20.2 is the development release (20.0 was beta), and is no longer
6961 considered unstable.
6963 For older news, see the file @file{ONEWS} in the @file{etc} directory of
6964 the XEmacs distribution.