1 \input texinfo.tex @c -*-texinfo-*-
3 @setfilename ../info/xemacs-faq.info
4 @settitle Frequently asked questions about XEmacs
10 @subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 1999/05/13 12:26:40 $
12 @author Tony Rossini <arossini@@stat.sc.edu>
13 @author Ben Wing <wing@@666.com>
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>
22 @dircategory XEmacs Editor
24 * FAQ: (xemacs-faq). XEmacs FAQ.
28 @node Top, Introduction, (dir), (dir)
30 @unnumbered Introduction
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. It is much more than just a Text Editor.
36 This FAQ is freely redistributable. I take no liability for the
37 correctness and safety of any procedures or advice given here. This
38 FAQ is distributed in the hope that it will be useful, but WITHOUT ANY
39 WARRANTY; without even the implied warranty of MERCHANTABILITY or
40 FITNESS FOR A PARTICULAR PURPOSE.
42 If you have a Web browser, the official hypertext version is at
46 @uref{http://www.xemacs.org/faq/xemacs-faq.html}.
48 This version is somewhat nicer than the unofficial hypertext versions
49 that are archived at Utrecht, Oxford, Smart Pages, and other FAQ
54 This document is available in several different formats:
57 @uref{xemacs-faq.txt, As a single ASCII file}, produced by
58 @code{makeinfo --no-headers}
60 @uref{xemacs-faq.dvi, As a .dvi file}, as used with
61 @uref{http://www.tug.org, TeX.}
63 As a PostScript file @uref{xemacs-faq-a4.ps, in A4 format},
64 as well as in @uref{xemacs-faq-letter.ps, letter format}
66 In html format, @uref{xemacs-faq_1.html, split by chapter}, or in
67 @uref{xemacs-faq.html, one monolithic} document.
69 The canonical version of the FAQ is the texinfo document
70 @uref{xemacs-faq.texi, man/xemacs-faq.texi}.
72 If you do not have makeinfo installed, you may @uref{xemacs-faq.info,
73 download the faq} in info format, and install it in @file{<XEmacs
74 library directory>/info/}. For example in
75 @file{/usr/local/lib/xemacs-20.4/info/}.
83 @c end ifset points to CANONICAL
86 * Introduction:: Introduction, Policy, Credits.
87 * Installation:: Installation and Trouble Shooting.
88 * Customization:: Customization and Options.
89 * Subsystems:: Major Subsystems.
90 * Miscellaneous:: The Miscellaneous Stuff.
91 * Current Events:: What the Future Holds.
95 --- The Detailed Node Listing ---
97 Introduction, Policy, Credits
99 * Q1.0.1:: What is XEmacs?
100 * Q1.0.2:: What is the current version of XEmacs?
101 * Q1.0.3:: Where can I find it?
102 * Q1.0.4:: Why Another Version of Emacs?
103 * Q1.0.5:: Why Haven't XEmacs and GNU Emacs Merged?
104 * Q1.0.6:: Where can I get help?
105 * Q1.0.7:: Where is the mailing list archived?
106 * Q1.0.8:: How do you pronounce XEmacs?
107 * Q1.0.9:: What does XEmacs look like?
108 * Q1.0.10:: Is there a port of XEmacs to Microsoft ('95 or NT)?
109 * Q1.0.11:: Is there a port of XEmacs to the Macintosh?
110 * Q1.0.12:: Is there a port of XEmacs to NextStep?
111 * Q1.0.13:: Is there a port of XEmacs to OS/2?
112 * Q1.0.14:: Where can I get a printed copy of the XEmacs users manual?
115 * Q1.1.1:: What is the FAQ editorial policy?
116 * Q1.1.2:: How do I become a Beta Tester?
117 * Q1.1.3:: How do I contribute to XEmacs itself?
120 * Q1.2.1:: Who wrote XEmacs?
121 * Q1.2.2:: Who contributed to this version of the FAQ?
122 * Q1.2.3:: Who contributed to the FAQ in the past?
124 Internationalization:
125 * Q1.3.1:: What is the status of XEmacs v20?
126 * Q1.3.2:: What is the status of Asian-language support, aka @var{mule}?
127 * Q1.3.3:: How do I type non-ASCII characters?
128 * Q1.3.4:: Can XEmacs messages come out in a different language?
129 * Q1.3.5:: Please explain the various input methods in MULE/XEmacs 20.0
130 * Q1.3.6:: How do I portably code for MULE/XEmacs 20.0?
131 * Q1.3.7:: How about Cyrillic Modes?
134 * Q1.4.1:: What is a @file{.emacs} and is there a sample one?
135 * Q1.4.2:: Can I use the same @file{.emacs} with the other Emacs?
136 * Q1.4.3:: Any good XEmacs tutorials around?
137 * Q1.4.4:: May I see an example of a useful XEmacs Lisp function?
138 * Q1.4.5:: And how do I bind it to a key?
139 * Q1.4.6:: What's the difference between a macro and a function?
140 * Q1.4.7:: Why options saved with 19.13 don't work with 19.14 or later?
142 Installation and Trouble Shooting
144 * Q2.0.1:: Running XEmacs without installing.
145 * Q2.0.2:: XEmacs is too big.
146 * Q2.0.3:: Compiling XEmacs with Netaudio.
147 * Q2.0.4:: Problems with Linux and ncurses.
148 * Q2.0.5:: Do I need X11 to run XEmacs?
149 * Q2.0.6:: I'm having strange crashes. What do I do?
150 * Q2.0.7:: Libraries in non-standard locations.
151 * Q2.0.8:: can't resolve symbol _h_errno
152 * Q2.0.9:: Where do I find external libraries?
153 * Q2.0.10:: After I run configure I find a coredump, is something wrong?
154 * Q2.0.11:: XEmacs can't resolve host names.
155 * Q2.0.12:: Why can't I strip XEmacs?
156 * Q2.0.13:: Can't link XEmacs on Solaris with Gcc.
157 * Q2.0.14:: Make on HP/UX 9 fails after linking temacs
160 * Q2.1.1:: XEmacs just crashed on me!
161 * Q2.1.2:: Cryptic Minibuffer messages.
162 * Q2.1.3:: Translation Table Syntax messages at Startup.
163 * Q2.1.4:: Startup warnings about deducing proper fonts?
164 * Q2.1.5:: XEmacs cannot connect to my X Terminal.
165 * Q2.1.6:: XEmacs just locked up my Linux X server.
166 * Q2.1.7:: HP Alt key as Meta.
167 * Q2.1.8:: got (wrong-type-argument color-instance-p nil)!
168 * Q2.1.9:: XEmacs causes my OpenWindows 3.0 server to crash.
169 * Q2.1.10:: Warnings from incorrect key modifiers.
170 * Q2.1.11:: Can't instantiate image error... in toolbar
171 * Q2.1.12:: Regular Expression Problems on DEC OSF1.
172 * Q2.1.13:: HP/UX 10.10 and @code{create_process} failure
173 * Q2.1.14:: @kbd{C-g} doesn't work for me. Is it broken?
174 * Q2.1.15:: How to debug an XEmacs problem with a debugger.
175 * Q2.1.16:: XEmacs crashes in @code{strcat} on HP/UX 10.
176 * Q2.1.17:: @samp{Marker does not point anywhere}.
177 * Q2.1.18:: 19.14 hangs on HP/UX 10.10.
178 * Q2.1.19:: XEmacs does not follow the local timezone.
179 * Q2.1.20:: @samp{Symbol's function definition is void: hkey-help-show.}
180 * Q2.1.21:: Every so often the XEmacs frame freezes.
181 * Q2.1.22:: XEmacs seems to take a really long time to do some things.
182 * Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
184 Customization and Options
186 * Q3.0.1:: What version of Emacs am I running?
187 * Q3.0.2:: How do I evaluate Elisp expressions?
188 * Q3.0.3:: @code{(setq tab-width 6)} behaves oddly.
189 * Q3.0.4:: How can I add directories to the @code{load-path}?
190 * Q3.0.5:: How to check if a lisp function is defined?
191 * Q3.0.6:: Can I force the output of @code{(face-list)} to a buffer?
192 * Q3.0.7:: Font selections don't get saved after @code{Save Options}.
193 * Q3.0.8:: How do I make a single minibuffer frame?
194 * Q3.0.9:: What is @code{Customize}?
196 X Window System & Resources:
197 * Q3.1.1:: Where is a list of X resources?
198 * Q3.1.2:: How can I detect a color display?
199 * Q3.1.3:: @code{(set-screen-width)} worked in 19.6, but not in 19.13?
200 * Q3.1.4:: Specifying @code{Emacs*EmacsScreen.geometry} in @file{.emacs} does not work in 19.15?
201 * Q3.1.5:: How can I get the icon to just say @samp{XEmacs}?
202 * Q3.1.6:: How can I have the window title area display the full path?
203 * Q3.1.7:: @samp{xemacs -name junk} doesn't work?
204 * Q3.1.8:: @samp{-iconic} doesn't work.
206 Textual Fonts & Colors:
207 * Q3.2.1:: How can I set color options from @file{.emacs}?
208 * Q3.2.2:: How do I set the text, menu and modeline fonts?
209 * Q3.2.3:: How can I set the colors when highlighting a region?
210 * Q3.2.4:: How can I limit color map usage?
211 * Q3.2.5:: My tty supports color, but XEmacs doesn't use them.
212 * Q3.2.6:: Can I have pixmap backgrounds in XEmacs?
215 * Q3.3.1:: How can I make the modeline go away?
216 * Q3.3.2:: How do you have XEmacs display the line number in the modeline?
217 * Q3.3.3:: How do I get XEmacs to put the time of day on the modeline?
218 * Q3.3.4:: How do I turn off current chapter from AUC TeX modeline?
219 * Q3.3.5:: How can one change the modeline color based on the mode used?
221 Multiple Device Support:
222 * Q3.4.1:: How do I open a frame on another screen of my multi-headed display?
223 * Q3.4.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
226 * Q3.5.1:: How can I bind complex functions (or macros) to keys?
227 * Q3.5.2:: How can I stop down-arrow from adding empty lines to the bottom of my buffers?
228 * Q3.5.3:: How do I bind C-. and C-; to scroll one line up and down?
229 * Q3.5.4:: Globally binding @kbd{Delete}?
230 * Q3.5.5:: Scrolling one line at a time.
231 * Q3.5.6:: How to map @kbd{Help} key alone on Sun type4 keyboard?
232 * Q3.5.7:: How can you type in special characters in XEmacs?
233 * Q3.5.8:: Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
234 * Q3.5.9:: How do I make the Delete key delete forward?
235 * Q3.5.10:: Can I turn on @dfn{sticky} modifier keys?
236 * Q3.5.11:: How do I map the arrow keys?
239 * Q3.6.1:: Is there a way to make the bar cursor thicker?
240 * 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?
241 * Q3.6.3:: Can I make the cursor blink?
243 The Mouse and Highlighting:
244 * Q3.7.1:: How can I turn off Mouse pasting?
245 * Q3.7.2:: How do I set control/meta/etc modifiers on mouse buttons?
246 * Q3.7.3:: Clicking the left button does not do anything in buffer list.
247 * Q3.7.4:: How can I get a list of buffers when I hit mouse button 3?
248 * Q3.7.5:: Why does cut-and-paste not work between XEmacs and a cmdtool?
249 * Q3.7.6:: How I can set XEmacs up so that it pastes where the text cursor is?
250 * Q3.7.7:: How do I select a rectangular region?
251 * Q3.7.8:: Why does @kbd{M-w} take so long?
253 The Menubar and Toolbar:
254 * Q3.8.1:: How do I get rid of the menu (or menubar)?
255 * Q3.8.2:: Can I customize the basic menubar?
256 * Q3.8.3:: How do I control how many buffers are listed in the menu @code{Buffers} list?
257 * Q3.8.4:: Resources like @code{Emacs*menubar*font} are not working?
258 * Q3.8.5:: How can I bind a key to a function to toggle the toolbar?
261 * Q3.9.1:: How can I disable the scrollbar?
262 * Q3.9.2:: How can one use resources to change scrollbar colors?
263 * Q3.9.3:: Moving the scrollbar can move the point; can I disable this?
264 * Q3.9.4:: How can I get automatic horizontal scrolling?
267 * Q3.10.1:: How can I turn off or change highlighted selections?
268 * Q3.10.2:: How do I get that typing on an active region removes it?
269 * Q3.10.3:: Can I turn off the highlight during isearch?
270 * Q3.10.4:: How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
271 * Q3.10.5:: The region disappears when I hit the end of buffer while scrolling.
275 * Q4.0.1:: How do I set up VM to retrieve remote mail using POP?
276 * Q4.0.2:: How do I get VM to filter mail for me?
277 * Q4.0.3:: How can I get VM to automatically check for new mail?
278 * Q4.0.4:: [This question intentionally left blank]
279 * Q4.0.5:: How do I get my outgoing mail archived?
280 * 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"?
281 * Q4.0.7:: Is there a mailing list or FAQ for VM?
282 * Q4.0.8:: Remote mail reading with VM.
283 * Q4.0.9:: rmail or VM gets an error incorporating new mail.
284 * Q4.0.10:: How do I make VM stay in a single frame?
285 * Q4.0.11:: How do I make VM or mh-e display graphical smilies?
286 * Q4.0.12:: Customization of VM not covered in the manual or here.
288 Web browsing with W3:
289 * Q4.1.1:: What is W3?
290 * Q4.1.2:: How do I run W3 from behind a firewall?
291 * Q4.1.3:: Is it true that W3 supports style sheets and tables?
293 Reading Netnews and Mail with Gnus:
294 * Q4.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
295 * Q4.2.2:: [This question intentionally left blank]
296 * Q4.2.3:: How do I make Gnus stay within a single frame?
297 * Q4.2.4:: How do I customize the From: line?
300 * Q4.3.1:: How can I read and/or compose MIME messages?
301 * Q4.3.2:: What is TM and where do I get it?
302 * Q4.3.3:: Why isn't this @code{movemail} program working?
303 * Q4.3.4:: Movemail is also distributed by Netscape? Can that cause problems?
304 * Q4.3.5:: Where do I find pstogif (required by tm)?
306 Sparcworks, EOS, and WorkShop:
307 * Q4.4.1:: What is SPARCworks, EOS, and WorkShop
310 * Q4.5.1:: What is/was Energize?
313 * Q4.6.1:: What is Infodock?
315 Other Unbundled Packages:
316 * Q4.7.1:: What is AUC TeX? Where do you get it?
317 * Q4.7.2:: Are there any Emacs Lisp Spreadsheets?
318 * Q4.7.3:: Byte compiling AUC TeX on XEmacs 19.14
319 * Q4.7.4:: Problems installing AUC TeX
320 * Q4.7.5:: Is there a reason for an Emacs package not to be included in XEmacs?
321 * Q4.7.6:: Is there a MatLab mode?
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?
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:: Filladapt doesn't work in 19.15?
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:: I upgraded to XEmacs 19.14 and gnuserv stopped working
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 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:: Fontifying hangs when editing a postscript file.
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?
379 What the Future Holds
381 * Q6.0.1:: What is new in 20.2?
382 * Q6.0.2:: What is new in 20.3?
383 * Q6.0.3:: What is new in 20.4?
384 * Q6.0.4:: Procedural changes in XEmacs development.
388 @node Introduction, Installation, Top, Top
389 @unnumbered 1 Introduction, Policy, Credits
391 Learning XEmacs is a lifelong activity. Even people who have used Emacs
392 for years keep discovering new features. Therefore this document cannot
393 be complete. Instead it is aimed at the person who is either
394 considering XEmacs for their own use, or has just obtained it and is
395 wondering what to do next. It is also useful as a reference to
398 The previous maintainer of the FAQ was @email{rossini@@stat.sc.edu,
399 Anthony Rossini}, who started it, after getting tired of hearing JWZ
400 complain about repeatedly having to answer questions.
401 @email{ben@@666.com, Ben Wing} and @email{cthomp@@xemacs.org, Chuck
402 Thompson}, the principal authors of XEmacs, then took over and Ben did
403 a massive update reorganizing the whole thing. At which point Anthony
404 took back over, but then had to give it up again. Some of the other
405 contributors to this FAQ are listed later in this document.
407 The previous version was converted to hypertext format, and edited by
408 @email{steve@@altair.xemacs.org, Steven L. Baur}. It was converted back to
409 texinfo by @email{hniksic@@srce.hr, Hrvoje Niksic}.
411 The FAQ was then maintained by @email{andreas@@sccon.com, Andreas
412 Kaempf}, who passed it on to @email{faq@@xemacs.org, Christian
413 Nyb@o{}}, the current FAQ maintainer.
415 If you notice any errors or items which should be added or amended to
416 this FAQ please send email to @email{faq@@xemacs.org, Christian
417 Nyb@o{}}. Include @samp{XEmacs FAQ} on the Subject: line.
421 * Q1.0.1:: What is XEmacs?
422 * Q1.0.2:: What is the current version of XEmacs?
423 * Q1.0.3:: Where can I find it?
424 * Q1.0.4:: Why Another Version of Emacs?
425 * Q1.0.5:: Why Haven't XEmacs and GNU Emacs Merged?
426 * Q1.0.6:: Where can I get help?
427 * Q1.0.7:: Where is the mailing list archived?
428 * Q1.0.8:: How do you pronounce XEmacs?
429 * Q1.0.9:: What does XEmacs look like?
430 * Q1.0.10:: Is there a port of XEmacs to Microsoft ('95 or NT)?
431 * Q1.0.11:: Is there a port of XEmacs to the Macintosh?
432 * Q1.0.12:: Is there a port of XEmacs to NextStep?
433 * Q1.0.13:: Is there a port of XEmacs to OS/2?
434 * Q1.0.14:: Where can I get a printed copy of the XEmacs users manual?
437 * Q1.1.1:: What is the FAQ editorial policy?
438 * Q1.1.2:: How do I become a Beta Tester?
439 * Q1.1.3:: How do I contribute to XEmacs itself?
442 * Q1.2.1:: Who wrote XEmacs?
443 * Q1.2.2:: Who contributed to this version of the FAQ?
444 * Q1.2.3:: Who contributed to the FAQ in the past?
446 Internationalization:
447 * Q1.3.1:: What is the status of XEmacs v20?
448 * Q1.3.2:: What is the status of Asian-language support, aka @var{mule}?
449 * Q1.3.3:: How do I type non-ASCII characters?
450 * Q1.3.4:: Can XEmacs messages come out in a different language?
451 * Q1.3.5:: Please explain the various input methods in MULE/XEmacs 20.0
452 * Q1.3.6:: How do I portably code for MULE/XEmacs 20.0?
453 * Q1.3.7:: How about Cyrillic Modes?
456 * Q1.4.1:: What is a @file{.emacs} and is there a sample one?
457 * Q1.4.2:: Can I use the same @file{.emacs} with the other Emacs?
458 * Q1.4.3:: Any good XEmacs tutorials around?
459 * Q1.4.4:: May I see an example of a useful XEmacs Lisp function?
460 * Q1.4.5:: And how do I bind it to a key?
461 * Q1.4.6:: What's the difference between a macro and a function?
462 * Q1.4.7:: Why options saved with 19.13 don't work with 19.14 or later?
465 @node Q1.0.1, Q1.0.2, Introduction, Introduction
466 @unnumberedsec 1.0: Introduction
467 @unnumberedsubsec Q1.0.1: What is XEmacs?
470 An alternative to GNU Emacs, originally based on an early alpha version
471 of FSF's version 19, and has diverged quite a bit since then. XEmacs
472 was known as Lucid Emacs through version 19.10. Almost all features of
473 GNU Emacs are supported in XEmacs. The maintainers of XEmacs actively
474 track changes to GNU Emacs while also working to add new features.
476 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction
477 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs?
479 XEmacs 20.4 is a minor upgrade from 20.3, containing many bugfixes. It
480 was released in February 1998.
482 XEmacs 19.16 was the last release of v19, released in November, 1997,
483 which was also the last version without international language support.
485 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction
486 @unnumberedsubsec Q1.0.3: Where can I find it?
488 The canonical source and binaries is found via anonymous FTP at:
491 @uref{ftp://ftp.xemacs.org/pub/xemacs/}
494 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction
495 @unnumberedsubsec Q1.0.4: Why Another Version of Emacs?
497 For a detailed description of the differences between GNU Emacs and
498 XEmacs and a detailed history of XEmacs, check out the
500 @uref{http://www.xemacs.org/NEWS.html, NEWS file}
503 However, here is a list of some of the reasons why we think you might
511 The XEmacs maintainers are generally more receptive to suggestions than
512 the GNU Emacs maintainers.
515 Many more bundled packages than GNU Emacs
518 Binaries are available for many common operating systems.
521 Face support on TTY's.
527 Better Motif compliance.
530 Some internationalization support (including full MULE support, if
534 Variable-width fonts.
537 Variable-height lines.
540 Marginal annotations.
546 XEmacs can be used as an Xt widget, and can be embedded within another
550 Horizontal and vertical scrollbars (using real toolkit scrollbars).
553 Better APIs (and performance) for attaching fonts, colors, and other
557 The ability to embed arbitrary graphics in a buffer.
560 Completely compatible (at the C level) with the Xt-based toolkits.
563 First production Web Browser supporting Style Sheets.
566 @node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
567 @unnumberedsubsec Q1.0.5: Why Haven't XEmacs and GNU Emacs Merged?
569 There are currently irreconcilable differences in the views about
570 technical, programming, design and organizational matters between RMS
571 and the XEmacs development team which provide little hope for a merge to
572 take place in the short-term future.
574 If you have a comment to add regarding the merge, it is a good idea to
575 avoid posting to the newsgroups, because of the very heated flamewars
576 that often result. Mail your questions to @email{xemacs-beta@@xemacs.org} and
577 @email{bug-gnu-emacs@@prep.ai.mit.edu}.
579 @node Q1.0.6, Q1.0.7, Q1.0.5, Introduction
580 @unnumberedsubsec Q1.0.6: Where can I get help?
582 Probably the easiest way, if everything is installed, is to use info, by
583 pressing @kbd{C-h i}, or selecting @code{Emacs Info} from the Help Menu.
585 Also, @kbd{M-x apropos} will look for commands for you.
587 Try reading this FAQ, examining the regular GNU Emacs FAQ (which can be
588 found with the Emacs 19 distribution) as well as at
589 @uref{http://www.eecs.nwu.edu/emacs/faq/} and reading the Usenet group
592 If that does not help, try posting your question to comp.emacs.xemacs.
593 Please @strong{do not} post XEmacs related questions to gnu.emacs.help.
595 If you cannot post or read Usenet news, there is a corresponding mailing
596 list which is available. It can be subscribed to by sending a message
597 with a subject of @samp{subscribe} to @email{xemacs-request@@xemacs.org}
598 for subscription information and @email{xemacs@@xemacs.org} to send messages
601 To cancel a subscription, you @strong{must} use the xemacs-request
602 address. Send a message with a subject of @samp{unsubscribe} to be
605 @node Q1.0.7, Q1.0.8, Q1.0.6, Introduction
606 @unnumberedsubsec Q1.0.7: Where is the mailing list archived?
608 The mailing list was archived in the directory
610 @uref{ftp://ftp.xemacs.org/pub/mlists/}.
613 However, this archive is out of date. The current mailing list server
614 supports an @code{archive} feature, which may be utilized.
616 @node Q1.0.8, Q1.0.9, Q1.0.7, Introduction
617 @unnumberedsubsec Q1.0.8: How do you pronounce XEmacs?
619 I pronounce it @samp{Eks eemax}.
621 @node Q1.0.9, Q1.0.10, Q1.0.8, Introduction
622 @unnumberedsubsec Q1.0.9: What does XEmacs look like?
624 Screen snapshots are available in the WWW version of the FAQ.
626 @uref{http://www.xemacs.org/faq/xemacs-faq.html}
629 @node Q1.0.10, Q1.0.11, Q1.0.9, Introduction
630 @unnumberedsubsec Q1.0.10: Is there a port of XEmacs to Microsoft ('95 or NT)?
632 Thanks to efforts of many people, coordinated by
633 @email{davidh@@wr.com.au, David Hobley} and @email{marcpa@@cam.org, Marc
634 Paquette}, beta versions of XEmacs now run on 32-bit Windows platforms
635 (NT and 95). The current betas require having an X server to run
636 XEmacs; however, a native NT/95 port is in alpha, thanks to
637 @email{jhar@@tardis.ed.ac.uk, Jonathan Harris}.
639 Although some features are still unimplemented, XEmacs 21.0 will support
642 The NT development is now coordinated by a mailing list at
643 @email{xemacs-nt@@xemacs.org}.
645 If you are willing to contribute or want to follow the progress, mail to
649 @email{xemacs-nt-request@@xemacs.org} to subscribe.
651 Furthermore, Altrasoft is seeking corporate and government sponsors to
652 help fund a fully native port of XEmacs to Windows 95 and NT using
653 full-time, senior-level staff working under a professionally managed
654 project structure. See @uref{http://www.altrasoft.com/, the Altrasoft
655 web site} for more details
656 or contact Altrasoft directly at 1-888-ALTSOFT.
659 The closest existing port is @dfn{Win-Emacs}, which is based on Lucid
660 Emacs 19.6. Available from @uref{http://www.pearlsoft.com/}.
662 There's a port of GNU Emacs (not XEmacs) at
664 @uref{http://www.cs.washington.edu/homes/voelker/ntemacs.html}.
667 @node Q1.0.11, Q1.0.12, Q1.0.10, Introduction
668 @unnumberedsubsec Q1.0.11: Is there a port of XEmacs to the Macintosh?
671 There has been a port to the MachTen environment of XEmacs 19.13, but no
672 patches have been submitted to the maintainers to get this in the
673 mainstream distribution.
675 For the MacOS, there is a port of
676 @uref{ftp://ftp.cs.cornell.edu/pub/parmet/, Emacs 18.59}.
678 @node Q1.0.12, Q1.0.13, Q1.0.11, Introduction
679 @unnumberedsubsec Q1.0.12: Is there a port of XEmacs to NextStep?
681 Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did
682 the port of GNU Emacs to NeXTstep and expressed interest in doing the
683 XEmacs port, but never went any farther.
685 @node Q1.0.13, Q1.0.14, Q1.0.12, Introduction
686 @unnumberedsubsec Q1.0.13: Is there a port of XEmacs to OS/2?
688 No, and there is no news of anyone working on it.
690 @node Q1.0.14, Q1.1.1, Q1.0.13, Introduction
691 @unnumberedsubsec Q1.0.14: Where can I obtain a printed copy of the XEmacs users manual?
693 Altrasoft Associates, a firm specializing in Emacs-related support and
694 development, will be maintaining the XEmacs user manual. The firm plans
695 to begin publishing printed copies of the manual soon.
696 @c This used to say `March 1997'!
699 Web: @uref{http://www.xemacs.com}
700 E-mail: @email{info@@xemacs.com}
704 @node Q1.1.1, Q1.1.2, Q1.0.14, Introduction
705 @unnumberedsec 1.1: Policies
706 @unnumberedsubsec Q1.1.1: What is the FAQ editorial policy?
708 The FAQ is actively maintained and modified regularly. All links should
711 Changes are displayed on a monthly basis. @dfn{Months}, for this
712 purpose are defined as the 5th of the month through the 5th of the
713 month. Preexisting questions that have been changed are marked as such.
714 Brand new questions are tagged.
716 All submissions are welcome. E-mail submissions
721 @email{faq@@xemacs.org, Christian Nyb@o{}}.
723 Please make sure that @samp{XEmacs FAQ} appears on the Subject: line.
724 If you think you have a better way of answering a question, or think a
725 question should be included, I'd like to hear about it. Questions and
726 answers included into the FAQ will be edited for spelling and grammar,
727 and will be attributed. Answers appearing without attribution are
728 either from versions of the FAQ dated before May 1996, or are from one
729 of the four people listed at the top of this document. Answers quoted
730 from Usenet news articles will always be attributed, regardless of the
733 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
734 @unnumberedsubsec Q1.1.2: How do I become a Beta Tester?
736 Send an email message to @email{xemacs-beta-request@@xemacs.org} with a
737 subject line of @samp{subscribe}.
739 Be prepared to get your hands dirty, as beta testers are expected to
740 identify problems as best they can.
742 @node Q1.1.3, Q1.2.1, Q1.1.2, Introduction
743 @unnumberedsubsec Q1.1.3: How do I contribute to XEmacs itself?
745 Ben Wing @email{ben@@666.com} writes:
748 BTW if you have a wish list of things that you want added, you have to
749 speak up about it! More specifically, you can do the following if you
750 want a feature added (in increasing order of usefulness):
754 Make a posting about a feature you want added.
757 Become a beta tester and make more postings about those same features.
760 Convince us that you're going to use the features in some cool and
764 Come up with a clear and well-thought-out API concerning the features.
767 Write the code to implement a feature and send us a patch.
770 (not that we're necessarily requiring you to write the code, but we can
774 @node Q1.2.1, Q1.2.2, Q1.1.3, Introduction
775 @unnumberedsec 1.2: Credits
776 @unnumberedsubsec Q1.2.1: Who wrote XEmacs?
778 XEmacs is the result of the time and effort of many people. The
779 developers responsible for the 19.16/20.x releases are:
782 @item @email{martin@@xemacs.org, Martin Buchholz}
784 <br><img src="mrb.jpeg" alt="Portrait of Martin Buchholz"><br>
788 @item @email{steve@@altair.xemacs.org, Steve Baur}
791 <br><img src="steve.gif" alt="Portrait of Steve Baur"><br>
795 @item @email{hniksic@@srce.hr, Hrvoje Niksic}
798 <br><img src="hniksic.jpeg" alt="Portrait of Hrvoje Niksic"><br>
803 The developers responsible for the 19.14 release are:
806 @item @email{cthomp@@xemacs.org, Chuck Thompson}
808 <br><img src="cthomp.jpeg" alt="Portrait of Chuck Thompson"><br>
811 Chuck was Mr. XEmacs from 19.11 through 19.14, and is responsible
812 for XEmacs becoming a widely distributed program over the Internet.
814 @item @email{ben@@666.com, Ben Wing}
816 <br><img src="wing.gif" alt="Portrait of Ben Wing"><br>
823 @item @email{jwz@@netscape.com, Jamie Zawinski}
825 <br><img src="jwz.gif" alt="Portrait of Jamie Zawinski"><br>
828 Jamie Zawinski was Mr. Lucid Emacs from 19.0 through 19.10, the last
829 release actually named Lucid Emacs. Richard Mlynarik was crucial to
830 most of those releases.
832 @item @email{mly@@adoc.xerox.com, Richard Mlynarik}
835 Along with many other contributors, partially enumerated in the
836 @samp{About XEmacs} option in the Help menu.
838 @node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
839 @unnumberedsubsec Q1.2.2: Who contributed to this version of the FAQ?
841 The following people contributed valuable suggestions to building this
842 version of the FAQ (listed in alphabetical order):
845 @item @email{steve@@xemacs.org, SL Baur}
847 @item @email{hniksic@@srce.hr, Hrvoje Niksic}
849 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
853 @node Q1.2.3, Q1.3.1, Q1.2.2, Introduction
854 @unnumberedsubsec Q1.2.3: Who contributed to the FAQ in the past?
856 This is only a partial list, as many names were lost in a hard disk
860 @item @email{binge@@aloft.att.com, Curtis.N.Bingham}
862 @item @email{rjc@@cogsci.ed.ac.uk, Richard Caley}
864 @item @email{cognot@@ensg.u-nancy.fr, Richard Cognot}
866 @item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque}
868 @item @email{eeide@@cs.utah.edu, Eric Eide}
870 @item @email{cflatter@@nrao.edu, Chris Flatters}
872 @item @email{ginsparg@@adra.com, Evelyn Ginsparg}
874 @item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall}
876 @item @email{dkindred@@cmu.edu, Darrell Kindred}
878 @item @email{dmoore@@ucsd.edu, David Moore}
880 @item @email{arup+@@cmu.edu, Arup Mukherjee}
882 @item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen}
884 @item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell}
886 @item @email{dworkin@@ccs.neu.edu, Justin Sheehy}
888 @item @email{stig@@hackvan.com, Stig}
890 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
893 @node Q1.3.1, Q1.3.2, Q1.2.3, Introduction
894 @unnumberedsec 1.3: Internationalization
895 @unnumberedsubsec Q1.3.1: What is the status of XEmacs v20?
897 XEmacs v20 is the version of XEmacs that includes MULE (Asian-language)
898 support. XEmacs 20.0 was released in February 1997, followed by XEmacs
899 20.2 in May, XEmacs 20.3 in November and XEmacs 20.4 in February 1998. When compiled without MULE
900 support, 20.4 is approximately as stable as 19.16, and probably faster
901 (due to additional optimization work.)
903 As of XEmacs 20.3, version 20 is @emph{the} supported version of
904 XEmacs. This means that 19.16 will optionally receive stability fixes
905 (if any), but that all the real development work will be done on the v20
908 The incompatible changes in XEmacs 20 include the additional byte-codes,
909 new primitive data types (@code{character}, @code{char-table}, and
910 @code{range-table}). This means that the character-integer equivalence
911 inherent to all the previous Emacs and XEmacs releases no longer
914 However, to avoid breaking old code, many functions that should normally
915 accept characters work with integers, and vice versa. For more
916 information, see the Lisp reference manual. Here is a relevant excerpt,
917 for your convenience.
920 In XEmacs version 19, and in all versions of FSF GNU Emacs, a
921 @dfn{character} in XEmacs Lisp is nothing more than an integer.
922 This is yet another holdover from XEmacs Lisp's derivation from
923 vintage-1980 Lisps; modern versions of Lisp consider this equivalence
924 a bad idea, and have separate character types. In XEmacs version 20,
925 the modern convention is followed, and characters are their own
926 primitive types. (This change was necessary in order for @sc{MULE},
927 i.e. Asian-language, support to be correctly implemented.)
929 Even in XEmacs version 20, remnants of the equivalence between
930 characters and integers still exist; this is termed the @dfn{char-int
931 confoundance disease}. In particular, many functions such as @code{eq},
932 @code{equal}, and @code{memq} have equivalent functions (@code{old-eq},
933 @code{old-equal}, @code{old-memq}, etc.) that pretend like characters
934 are integers are the same. Byte code compiled under any version 19
935 Emacs will have all such functions mapped to their @code{old-} equivalents
936 when the byte code is read into XEmacs 20. This is to preserve
937 compatibility -- Emacs 19 converts all constant characters to the equivalent
938 integer during byte-compilation, and thus there is no other way to preserve
939 byte-code compatibility even if the code has specifically been written
940 with the distinction between characters and integers in mind.
942 Every character has an equivalent integer, called the @dfn{character
943 code}. For example, the character @kbd{A} is represented as the
944 @w{integer 65}, following the standard @sc{ASCII} representation of
945 characters. If XEmacs was not compiled with @sc{MULE} support, the
946 range of this integer will always be 0 to 255 -- eight bits, or one
947 byte. (Integers outside this range are accepted but silently truncated;
948 however, you should most decidedly @emph{not} rely on this, because it
949 will not work under XEmacs with @sc{MULE} support.) When @sc{MULE}
950 support is present, the range of character codes is much
951 larger. (Currently, 19 bits are used.)
953 FSF GNU Emacs uses kludgy character codes above 255 to represent
954 keyboard input of @sc{ASCII} characters in combination with certain
955 modifiers. XEmacs does not use this (a more general mechanism is
956 used that does not distinguish between @sc{ASCII} keys and other
957 keys), so you will never find character codes above 255 in a
958 non-@sc{MULE} XEmacs.
960 Individual characters are not often used in programs. It is far more
961 common to work with @emph{strings}, which are sequences composed of
965 @node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
966 @unnumberedsubsec Q1.3.2: What is the status of Asian-language support, aka MULE?
968 The MULE support works OK but still needs a fair amount of work before
969 it's really solid. We could definitely use some help here, esp. people
970 who speak Japanese and will use XEmacs/MULE to work with Japanese and
971 have some experience with E-Lisp.
973 As the fundings on Mule have stopped, the Mule part of XEmacs is currently
974 looking for a full-time maintainer. If you can provide help here, or
975 are willing to fund the work, please mail to @email{xemacs-beta@@xemacs.org}.
979 @node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
980 @unnumberedsubsec Q1.3.3: How do I type non-ASCII characters?
982 See question 3.5.7 (@pxref{Q3.5.7}) in part 3 of this FAQ.
984 @node Q1.3.4, Q1.3.5, Q1.3.3, Introduction
985 @unnumberedsubsec Q1.3.4: Can XEmacs messages come out in a different language?
987 The message-catalog support has mostly been written but doesn't
988 currently work. The first release of XEmacs 20 will @emph{not} support
989 it. However, menubar localization @emph{does} work, even in 19.14. To
990 enable it, add to your @file{Emacs} file entries like this:
993 Emacs*XlwMenu.resourceLabels: True
994 Emacs*XlwMenu.file.labelString: Fichier
995 Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster offnen
998 The name of the resource is derived from the non-localized entry by
999 removing punctuation and capitalizing as above.
1001 @node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
1002 @unnumberedsubsec Q1.3.5: Please explain the various input methods in MULE/XEmacs 20.0
1004 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
1007 Original Mule supports the following input methods: Wnn4, Wnn6, Canna, SJ3
1008 and XIM. Interfaces for Wnn and SJ3 uses the @code{egg} user
1009 interface. Interface for Canna does not use @samp{egg}. I don't know
1010 about XIM. It is to support ATOK, of course, it may work for another
1013 Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
1014 university. It is a powerful and complex system. Wnn4 is free and Wnn6
1017 Canna supports only Japanese. It is made by NEC. It is a simple and
1018 powerful system. Canna uses only grammar (Wnn uses grammar and
1019 probability between words), so I think Wnn is cleverer than Canna,
1020 however Canna users made a good grammar and dictionary. So for standard
1021 modern Japanese, Canna seems cleverer than Wnn4. In addition, the UNIX
1022 version of Canna is free (now there is a Microsoft Windows version).
1024 SJ3 supports only Japanese. It is made by Sony. XIM supports was made
1025 to use ATOK (a major input method in personal computer world). XIM is
1026 the standard for accessing input methods bundled in Japanese versions of
1027 Solaris. (XEmacs 20 will support XIM input).
1029 Egg consists of following parts:
1033 Input character Translation System (ITS) layer.
1034 It translates ASCII inputs to Kana/PinYin/Hangul characters.
1037 Kana/PinYin/Hangul to Kanji transfer layer.
1038 It is interface layer for network Kana-Kanji server (Wnn and Sj3).
1041 These input methods are modal, namely there are mode, alphabet mode and
1042 Kana-Kanji transfer mode. However there are mode-less input methods for
1043 Egg and Canna. @samp{Boiled-egg} is a mode-less input method running on
1044 Egg. For Canna, @samp{canna.el} has a tiny boiled-egg like command,
1045 @code{(canna-boil)}, and there are some boiled-egg like utilities. In
1046 addition, it was planned to make an abstraction for all transfer type
1047 input methods. However authors of input methods are busy, so maybe this
1048 plan is stopped. Perhaps after Mule merged GNU Emacs will be released,
1049 it will be continued.
1052 @node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
1053 @unnumberedsubsec Q1.3.6: How do I portably code for MULE/XEmacs 20?
1055 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
1058 MULE and XEmacs are quite different. So the application
1059 implementor must write separate code for these mule variants.
1061 MULE and the next version of Emacs are similar but the symbols are very
1062 different---requiring separate code as well.
1064 Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of
1065 emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called
1066 @code{emu} to provide a common interface.
1068 I have the following suggestions about dealing with mule variants:
1072 @code{(featurep 'mule)} @code{t} on all mule variants
1075 @code{(boundp 'MULE)} is @code{t} on only MULE. Maybe the next version
1076 of Emacs will not have this symbol.
1079 MULE has a variable @code{mule-version}. Perhaps the next version of
1080 Emacs will have this variable as well.
1083 Following is a sample to distinguish mule variants:
1086 (if (featurep 'mule)
1087 (cond ((boundp 'MULE)
1088 ;; for original Mule
1090 ((string-match "XEmacs" emacs-version)
1091 ;; for XEmacs with Mule
1094 ;; for next version of Emacs
1096 ;; for old emacs variants
1101 @node Q1.3.7, Q1.4.1, Q1.3.6, Introduction
1102 @unnumberedsubsec Q1.3.7: How about Cyrillic Modes?
1104 @email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes:
1107 There is a cyrillic mode in the file @file{mysetup.zip} in
1111 @uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}. This is a
1112 modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el}
1113 which can be obtained from
1116 @uref{http://ftpsearch.ntnu.no/?query=russian.el.Z}.
1119 @email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes:
1122 There is another cyrillic mode for both GNU Emacs and XEmacs by
1123 @email{manin@@camelot.mssm.edu, Dmitrii
1128 @uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}.
1129 @c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead.
1130 @c Changed to russian host instead
1133 @email{rebecca.ore@@op.net, Rebecca Ore} writes:
1136 The fullest resource I found on Russian language use (in and out of
1137 XEmacs) is @uref{http://sunsite.oit.unc.edu/sergei/Software/Software.html}
1140 @node Q1.4.1, Q1.4.2, Q1.3.7, Introduction
1141 @unnumberedsec 1.4: Getting Started, Backing up & Recovery
1142 @unnumberedsubsec Q1.4.1: What is a @file{.emacs} and is there a sample one?
1144 The @file{.emacs} file is used to customize XEmacs to your tastes. No
1145 two are alike, nor are they expected to be alike, but that's the point.
1146 The XEmacs distribution contains an excellent starter example in the etc
1147 directory called @file{sample.emacs}. Copy this file from there to your
1148 home directory and rename it @file{.emacs}. Then edit it to suit.
1150 Starting with 19.14, you may bring the @file{sample.emacs} into an
1151 XEmacs buffer by selecting @samp{Help->Sample .emacs} from the menubar.
1152 To determine the location of the @file{etc} directory type the command
1153 @kbd{C-h v data-directory @key{RET}}.
1155 @node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
1156 @unnumberedsubsec Q1.4.2: Can I use the same @file{.emacs} with the other Emacs?
1158 Yes. The sample @file{.emacs} included in the XEmacs distribution will
1159 show you how to handle different versions and flavors of Emacs.
1161 @node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
1162 @unnumberedsubsec Q1.4.3: Any good tutorials around?
1164 There's the XEmacs tutorial available from the Help Menu, or by typing
1165 @kbd{C-h t}. To check whether it's available in a non-english language,
1166 type @kbd{C-u C-h t TAB}, type the first letters of your preferred
1167 language, then type @key{RET}.
1169 There's an Emacs Lisp tutorial at
1172 @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
1175 @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
1180 @uref{http://petaxp.rug.ac.be/~erik/xemacs/}.
1182 @node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
1183 @unnumberedsubsec Q1.4.4: May I see an example of a useful XEmacs Lisp function?
1185 The following function does a little bit of everything useful. It does
1186 something with the prefix argument, it examines the text around the
1187 cursor, and it's interactive so it may be bound to a key. It inserts
1188 copies of the current word the cursor is sitting on at the cursor. If
1189 you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will
1193 (defun double-word (count)
1194 "Insert a copy of the current word underneath the cursor"
1196 (let (here there string)
1201 (setq there (point))
1202 (setq string (buffer-substring here there)))
1208 The best way to see what is going on here is to let XEmacs tell you.
1209 Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor
1210 sitting just to the right of the function you want explained. Eg. move
1211 the cursor to the SPACE between @code{interactive} and @samp{"*p"} and
1212 hit @kbd{C-h f} to see what the function @code{interactive} does. Doing
1213 this will tell you that the @code{*} requires a writable buffer, and
1214 @code{p} converts the prefix argument to a number, and
1215 @code{interactive} allows you to execute the command with @kbd{M-x}.
1217 @node Q1.4.5, Q1.4.6, Q1.4.4, Introduction
1218 @unnumberedsubsec Q1.4.5: And how do I bind it to a key?
1220 To bind to a key do:
1223 (global-set-key "\C-cd" 'double-word)
1226 Or interactively, @kbd{M-x global-set-key} and follow the prompts.
1228 @node Q1.4.6, Q1.4.7, Q1.4.5, Introduction
1229 @unnumberedsubsec Q1.4.6: What's the difference between a macro and a function?
1231 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual:
1233 @dfn{Macros} enable you to define new control constructs and other
1234 language features. A macro is defined much like a function, but instead
1235 of telling how to compute a value, it tells how to compute another Lisp
1236 expression which will in turn compute the value. We call this
1237 expression the @dfn{expansion} of the macro.
1239 Macros can do this because they operate on the unevaluated expressions
1240 for the arguments, not on the argument values as functions do. They can
1241 therefore construct an expansion containing these argument expressions
1244 Do not confuse the two terms with @dfn{keyboard macros}, which are
1245 another matter, entirely. A keyboard macro is a key bound to several
1246 other keys. Refer to manual for details.
1248 @node Q1.4.7, , Q1.4.6, Introduction
1249 @unnumberedsubsec Q1.4.7: How come options saved with 19.13 don't work with 19.14 or later?
1251 There's a problem with options of the form:
1254 (add-spec-list-to-specifier (face-property 'searchm-field 'font)
1258 saved by a 19.13 XEmacs that causes a 19.14 XEmacs grief. You must
1259 delete these options. XEmacs 19.14 and later no longer write the
1260 options directly to @file{.emacs} which should allow us to deal with
1261 version incompatibilities better in the future.
1263 Options saved under XEmacs 19.13 are protected by code that specifically
1264 requires a version 19 XEmacs. This won't be a problem unless you're
1265 using XEmacs v20. You should consider changing the code to read:
1269 ((and (string-match "XEmacs" emacs-version)
1270 (boundp 'emacs-major-version)
1271 (or (and (= emacs-major-version 19)
1272 (>= emacs-minor-version 12))
1273 (>= emacs-major-version 20)))
1278 @node Installation, Customization, Introduction, Top
1279 @unnumbered 2 Installation and Trouble Shooting
1281 This is part 2 of the XEmacs Frequently Asked Questions list. This
1282 section is devoted to Installation, Maintenance and Trouble Shooting.
1286 * Q2.0.1:: Running XEmacs without installing.
1287 * Q2.0.2:: XEmacs is too big.
1288 * Q2.0.3:: Compiling XEmacs with Netaudio.
1289 * Q2.0.4:: Problems with Linux and ncurses.
1290 * Q2.0.5:: Do I need X11 to run XEmacs?
1291 * Q2.0.6:: I'm having strange crashes. What do I do?
1292 * Q2.0.7:: Libraries in non-standard locations.
1293 * Q2.0.8:: can't resolve symbol _h_errno
1294 * Q2.0.9:: Where do I find external libraries?
1295 * Q2.0.10:: After I run configure I find a coredump, is something wrong?
1296 * Q2.0.11:: XEmacs can't resolve host names.
1297 * Q2.0.12:: Why can't I strip XEmacs?
1298 * Q2.0.13:: Can't link XEmacs on Solaris with Gcc.
1299 * Q2.0.14:: Make on HP/UX 9 fails after linking temacs
1302 * Q2.1.1:: XEmacs just crashed on me!
1303 * Q2.1.2:: Cryptic Minibuffer messages.
1304 * Q2.1.3:: Translation Table Syntax messages at Startup.
1305 * Q2.1.4:: Startup warnings about deducing proper fonts?
1306 * Q2.1.5:: XEmacs cannot connect to my X Terminal.
1307 * Q2.1.6:: XEmacs just locked up my Linux X server.
1308 * Q2.1.7:: HP Alt key as Meta.
1309 * Q2.1.8:: got (wrong-type-argument color-instance-p nil)!
1310 * Q2.1.9:: XEmacs causes my OpenWindows 3.0 server to crash.
1311 * Q2.1.10:: Warnings from incorrect key modifiers.
1312 * Q2.1.11:: Can't instantiate image error... in toolbar
1313 * Q2.1.12:: Regular Expression Problems on DEC OSF1.
1314 * Q2.1.13:: HP/UX 10.10 and @code{create_process} failure
1315 * Q2.1.14:: @kbd{C-g} doesn't work for me. Is it broken?
1316 * Q2.1.15:: How to debug an XEmacs problem with a debugger.
1317 * Q2.1.16:: XEmacs crashes in @code{strcat} on HP/UX 10.
1318 * Q2.1.17:: @samp{Marker does not point anywhere}.
1319 * Q2.1.18:: 19.14 hangs on HP/UX 10.10.
1320 * Q2.1.19:: XEmacs does not follow the local timezone.
1321 * Q2.1.20:: @samp{Symbol's function definition is void: hkey-help-show.}
1322 * Q2.1.21:: Every so often the XEmacs frame freezes.
1323 * Q2.1.22:: XEmacs seems to take a really long time to do some things.
1324 * Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
1327 @node Q2.0.1, Q2.0.2, Installation, Installation
1328 @unnumberedsec 2.0: Installation
1329 @unnumberedsubsec Q2.0.1: Running XEmacs without installing
1330 The @file{INSTALL} file says that up to 108 MB of space is needed
1331 temporarily during installation! How can I just try it out?
1333 XEmacs will run in place without requiring installation and copying of
1334 the Lisp directories, and without having to specify a special build-time
1335 flag. It's the copying of the Lisp directories that requires so much
1336 space. XEmacs is largely written in Lisp.
1338 A good method is to make a shell alias for xemacs:
1341 alias xemacs=/i/xemacs-20.2/src/xemacs
1344 (You will obviously use whatever directory you downloaded the source
1345 tree to instead of @file{/i/xemacs-20.2}).
1347 This will let you run XEmacs without massive copying.
1349 @node Q2.0.2, Q2.0.3, Q2.0.1, Installation
1350 @unnumberedsubsec Q2.0.2: XEmacs is too big
1352 Although this entry has been written for XEmacs 19.13, most of it still
1355 @email{steve@@altair.xemacs.org, Steve Baur} writes:
1358 The 45MB of space required by the installation directories can be
1359 reduced dramatically if desired. Gzip all the .el files. Remove all
1360 the packages you'll never want to use (or even ones you do like the two
1361 obsolete mailcrypts and Gnus 4 in 19.13). Remove the TexInfo manuals.
1362 Remove the Info (and use just hardcopy versions of the manual). Remove
1363 most of the stuff in etc. Remove or gzip all the source code. Gzip or
1364 remove the C source code. Configure it so that copies are not made of
1365 the support lisp. I'm not advocating any of these things, just pointing
1366 out ways to reduce the disk requirements if desired.
1368 Now examine the space used by directory:
1371 0 /usr/local/bin/xemacs
1372 2048 /usr/local/bin/xemacs-19.13
1374 1546 /usr/local/lib/xemacs-19.13/i486-miranova-sco3.2v4.2
1375 1158 /usr/local/lib/xemacs-19.13/i486-unknown-linux1.2.13
1378 You need to keep these. XEmacs isn't stripped by default in
1379 installation, you should consider stripping. That will save you about
1383 207 /usr/local/lib/xemacs-19.13/etc/w3
1384 122 /usr/local/lib/xemacs-19.13/etc/sounds
1385 18 /usr/local/lib/xemacs-19.13/etc/sparcworks
1386 159 /usr/local/lib/xemacs-19.13/etc/vm
1387 6 /usr/local/lib/xemacs-19.13/etc/e
1388 21 /usr/local/lib/xemacs-19.13/etc/eos
1389 172 /usr/local/lib/xemacs-19.13/etc/toolbar
1390 61 /usr/local/lib/xemacs-19.13/etc/ns
1391 43 /usr/local/lib/xemacs-19.13/etc/gnus
1394 These are support directories for various packages. In general they
1395 match a directory under ./xemacs-19.13/lib/xemacs-19.13/lisp/. If you
1396 do not require the package, you may delete or gzip the support too.
1399 1959 /usr/local/lib/xemacs-19.13/etc
1400 175 /usr/local/lib/xemacs-19.13/lisp/bytecomp
1401 340 /usr/local/lib/xemacs-19.13/lisp/calendar
1402 342 /usr/local/lib/xemacs-19.13/lisp/comint
1403 517 /usr/local/lib/xemacs-19.13/lisp/dired
1404 42 /usr/local/lib/xemacs-19.13/lisp/electric
1405 212 /usr/local/lib/xemacs-19.13/lisp/emulators
1406 238 /usr/local/lib/xemacs-19.13/lisp/energize
1407 289 /usr/local/lib/xemacs-19.13/lisp/gnus
1408 457 /usr/local/lib/xemacs-19.13/lisp/ilisp
1409 1439 /usr/local/lib/xemacs-19.13/lisp/modes
1410 2276 /usr/local/lib/xemacs-19.13/lisp/packages
1411 1040 /usr/local/lib/xemacs-19.13/lisp/prim
1412 176 /usr/local/lib/xemacs-19.13/lisp/pcl-cvs
1413 154 /usr/local/lib/xemacs-19.13/lisp/rmail
1414 3 /usr/local/lib/xemacs-19.13/lisp/epoch
1415 45 /usr/local/lib/xemacs-19.13/lisp/term
1416 860 /usr/local/lib/xemacs-19.13/lisp/utils
1417 851 /usr/local/lib/xemacs-19.13/lisp/vm
1418 13 /usr/local/lib/xemacs-19.13/lisp/vms
1419 157 /usr/local/lib/xemacs-19.13/lisp/x11
1420 19 /usr/local/lib/xemacs-19.13/lisp/tooltalk
1421 14 /usr/local/lib/xemacs-19.13/lisp/sunpro
1422 291 /usr/local/lib/xemacs-19.13/lisp/games
1423 198 /usr/local/lib/xemacs-19.13/lisp/edebug
1424 619 /usr/local/lib/xemacs-19.13/lisp/w3
1425 229 /usr/local/lib/xemacs-19.13/lisp/eos
1426 55 /usr/local/lib/xemacs-19.13/lisp/iso
1427 59 /usr/local/lib/xemacs-19.13/lisp/mailcrypt
1428 187 /usr/local/lib/xemacs-19.13/lisp/eterm
1429 356 /usr/local/lib/xemacs-19.13/lisp/ediff
1430 408 /usr/local/lib/xemacs-19.13/lisp/hyperbole/kotl
1431 1262 /usr/local/lib/xemacs-19.13/lisp/hyperbole
1432 247 /usr/local/lib/xemacs-19.13/lisp/hm--html-menus
1433 161 /usr/local/lib/xemacs-19.13/lisp/mh-e
1434 299 /usr/local/lib/xemacs-19.13/lisp/viper
1435 53 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-x
1436 4 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/DocWindow.nib
1437 3 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/InfoPanel.nib
1438 3 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/TreeView.nib
1439 11 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj
1440 53 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx
1441 466 /usr/local/lib/xemacs-19.13/lisp/oobr
1442 14142 /usr/local/lib/xemacs-19.13/lisp
1445 These are all Emacs Lisp source code and bytecompiled object code. You
1446 may safely gzip everything named *.el here. You may remove any package
1447 you don't use. @emph{Nothing bad will happen if you delete a package
1448 that you do not use}. You must be sure you do not use it though, so be
1449 conservative at first.
1451 Possible candidates for deletion include w3 (newer versions exist, or
1452 you may just use Lynx or Netscape for web browsing), games, hyperbole,
1453 mh-e, hm--html-menus (better packages exist), vm, viper, oobr, gnus (new
1454 versions exist), etc. Ask yourself, @emph{Do I ever want to use this
1455 package?} If the answer is no, then it is a candidate for removal.
1457 First, gzip all the .el files. Then go about package by package and
1458 start gzipping the .elc files. Then run XEmacs and do whatever it is
1459 you normally do. If nothing bad happens, then delete the directory. Be
1460 conservative about deleting directories, and it would be handy to have a
1461 backup tape around in case you get too zealous.
1463 @file{prim}, @file{modes}, @file{packages}, and @file{utils} are four
1464 directories you definitely do @strong{not} want to delete, although
1465 certain packages can be removed from them if you do not use them.
1468 1972 /usr/local/lib/xemacs-19.13/info
1471 These are online texinfo sources. You may either gzip them or remove
1472 them. In either case, @kbd{C-h i} (info mode) will no longer work.
1475 20778 /usr/local/lib/xemacs-19.13
1478 The 20MB achieved is less than half of what the full distribution takes up,
1479 @strong{and} can be achieved without deleting a single file.
1482 @email{boffi@@hp735.stru.polimi.it, Giacomo Boffi} provides this procedure:
1485 Substitute @file{/usr/local/lib/} with the path where the xemacs tree is
1486 rooted, then use this script:
1491 r=/usr/local/lib/xemacs-19.13/lisp
1493 cd $r ; rm -f cmpr ; touch cmpr
1498 if test -d $d ; then
1501 # compress (remove) only (ONLY) the sources that have a
1502 # corresponding compiled file --- do not (DO NOT)
1503 # touch other sources
1504 if test -f $@{f@}c ; then gzip -v9 $f >> $r/cmpr ; fi
1513 A step beyond would be substituting @samp{rm -f} for @samp{gzip -v9},
1514 but you have to be desperate for removing the sources (remember that
1515 emacs can access compressed files transparently).
1517 Also, a good megabyte could easily be trimmed from the $r/../etc
1518 directory, e.g., the termcap files, some O+NEWS, others that I don't
1523 XEmacs 21.0 will unbundle the lisp hierarchy and allow the installer
1524 to choose exactly how much support code gets installed.
1527 @node Q2.0.3, Q2.0.4, Q2.0.2, Installation
1528 @unnumberedsubsec Q2.0.3: Compiling XEmacs with Netaudio.
1530 What is the best way to compile XEmacs with the netaudio system, since I
1531 have got the netaudio system compiled but installed at a weird place, I
1532 am not root. Also in the READMEs it does not say anything about
1533 compiling with the audioserver?
1535 You should only need to add some stuff to the configure command line.
1536 To tell it to compile in netaudio support: @samp{--with-sound=both}, or
1537 @samp{--with-sound=nas} if you don't want native sound support for some
1538 reason.) To tell it where to find the netaudio includes and libraries:
1541 --site-libraries=WHATEVER
1542 --site-includes=WHATEVER
1545 Then (fingers crossed) it should compile and it will use netaudio if you
1546 have a server running corresponding to the X server. The netaudio server
1547 has to be there when XEmacs starts. If the netaudio server goes away and
1548 another is run, XEmacs should cope (fingers crossed, error handling in
1549 netaudio isn't perfect).
1551 BTW, netaudio has been renamed as it has a name clash with something
1552 else, so if you see references to NAS or Network Audio System, it's the
1553 same thing. It also might be found at
1554 @uref{ftp://ftp.x.org/contrib/audio/nas/}.
1556 @node Q2.0.4, Q2.0.5, Q2.0.3, Installation
1557 @unnumberedsubsec Q2.0.4: Problems with Linux and ncurses.
1559 On Linux 1.3.98 with termcap 2.0.8 and the ncurses that came with libc
1560 5.2.18, XEmacs 20.0b20 is unable to open a tty device:
1564 Initialization error:
1568 Terminal type `xterm' undefined (or can't access database?)
1571 @email{ben@@666.com, Ben Wing} writes:
1574 Your ncurses configuration is messed up. Your /usr/lib/terminfo is a
1575 bad pointer, perhaps to a CD-ROM that is not inserted.
1578 @node Q2.0.5, Q2.0.6, Q2.0.4, Installation
1579 @unnumberedsubsec Q2.0.5: Do I need X11 to run XEmacs?
1581 No. The name @dfn{XEmacs} is unfortunate in the sense that it is
1582 @strong{not} an X Window System-only version of Emacs. Starting with
1583 19.14 XEmacs has full color support on a color capable character
1586 @node Q2.0.6, Q2.0.7, Q2.0.5, Installation
1587 @unnumberedsubsec Q2.0.6: I'm having strange crashes. What do I do?
1589 There have been a variety of reports of crashes due to compilers with
1590 buggy optimizers. Please see the @file{PROBLEMS} file that comes with
1591 XEmacs to read what it says about your platform.
1593 @node Q2.0.7, Q2.0.8, Q2.0.6, Installation
1594 @unnumberedsubsec Q2.0.7: Libraries in non-standard locations
1596 I have x-faces, jpeg, xpm etc. all in different places. I've tried
1597 space-separated, comma-separated, several --site-libraries, all to no
1601 --site-libraries='/path/one /path/two /path/etc'
1604 @node Q2.0.8, Q2.0.9, Q2.0.7, Installation
1605 @unnumberedsubsec Q2.0.8: can't resolve symbol _h_errno
1607 You are using the Linux/ELF distribution of XEmacs 19.14, and your ELF
1608 libraries are out of date. You have the following options:
1612 Upgrade your libc to at least 5.2.16 (better is 5.2.18, 5.3.12, or
1616 Patch the XEmacs binary by replacing all occurrences of
1617 @samp{_h_errno^@@} with
1621 @samp{h_errno^@@^@@}. Any version of Emacs will
1622 suffice. If you don't understand how to do this, don't do it.
1625 Rebuild XEmacs yourself -- any working ELF version of libc should be
1629 @email{hniksic@@srce.hr, Hrvoje Niksic} writes:
1632 Why not use a Perl one-liner for No. 2?
1635 perl -pi -e 's/_h_errno\0/h_errno\0\0/g' \
1636 /usr/local/bin/xemacs-19.14
1639 NB: You @emph{must} patch @file{/usr/local/bin/xemacs-19.14}, and not
1640 @file{xemacs} because @file{xemacs} is a link to @file{xemacs-19.14};
1641 the Perl @samp{-i} option will cause unwanted side-effects if applied to
1645 @email{steve@@xemacs.org, SL Baur} writes:
1648 If you build against a recent libc-5.4 (late enough to have caused
1649 problems earlier in the beta cycle) and then run with an earlier version
1654 xemacs: can't resolve symbol '__malloc_hook'
1655 zsh: 7942 segmentation fault (core dumped) xemacs
1658 (Example binary compiled against libc-5.4.23 and run with libc-5.4.16).
1660 The solution is to upgrade to at least libc-5.4.23. Sigh. Drat.
1663 @node Q2.0.9, Q2.0.10, Q2.0.8, Installation
1664 @unnumberedsubsec Q2.0.9: Where do I find external libraries?
1666 All external libraries used by XEmacs can be found at the XEmacs FTP
1671 @uref{ftp://ftp.xemacs.org/pub/xemacs/aux/}.
1673 @c Changed June Link above, <URL:ftp://ftp.xemacs.org/pub/aux/> was dead.
1674 @c This list is a pain in the you-know-what to keep in synch with the
1676 The canonical locations (at the time of this writing) are as follows:
1680 @uref{ftp://ftp.uu.net/graphics/jpeg/}. Version 6a is current.
1681 @c Check from host with legal IP address
1683 @uref{ftp://ftp.x.org/contrib/libraries/}. Version 3.4j is current.
1684 Older versions of this package are known to cause XEmacs crashes.
1687 @uref{ftp://ftp.sgi.com/graphics/tiff/}. v3.4 is current. The latest
1688 beta is v3.4b035. There is a HOWTO here.
1691 @uref{ftp://ftp.uu.net/graphics/png/}. 0.89c is current. XEmacs
1692 requires a fairly recent version to avoid using temporary files.
1693 @c Check from host with legal IP address
1695 @uref{ftp://swrinde.nde.swri.edu/pub/png/src/}
1698 @uref{ftp://ftp.cs.indiana.edu/pub/faces/compface/}. This library has
1699 been frozen for about 6 years, and is distributed without version
1700 numbers. @emph{It should be compiled with the same options that X11 was
1701 compiled with on your system}. The version of this library at
1702 XEmacs.org includes the @file{xbm2xface.pl} script, written by
1703 @email{stig@@hackvan.com}, which may be useful when generating your own xface.
1706 @uref{ftp://ftp.x.org/contrib/audio/nas/}.
1707 Version 1.2p5 is current. There is a FAQ here.
1710 @node Q2.0.10, Q2.0.11, Q2.0.9, Installation
1711 @unnumberedsubsec Q2.0.10: After I run configure I find a core dump, is something wrong?
1713 Not necessarily. If you have GNU sed 3.0 you should downgrade it to
1714 2.05. From the @file{README} at prep.ai.mit.edu:
1717 sed 3.0 has been withdrawn from distribution. It has major revisions,
1718 which mostly seem to be improvements; but it turns out to have bugs too
1719 which cause trouble in some common cases.
1721 Tom Lord won't be able to work fixing the bugs until May. So in the
1722 mean time, we've decided to withdraw sed 3.0 from distribution and make
1723 version 2.05 once again the recommended version.
1726 It has also been observed that the vfork test on Solaris will leave a
1729 @node Q2.0.11, Q2.0.12, Q2.0.10, Installation
1730 @unnumberedsubsec Q2.0.11: XEmacs doesn't resolve hostnames.
1732 This is the result of a long-standing problem with SunOS and the fact
1733 that stock SunOS systems do not ship with DNS resolver code in libc.
1735 @email{ckd@@loiosh.kei.com, Christopher Davis} writes:
1738 That's correct [The SunOS 4.1.3 precompiled binaries don't do name
1739 lookup]. Since Sun figured that everyone used NIS to do name lookups
1740 (that DNS thing was apparently only a passing fad, right?), the stock
1741 SunOS 4.x systems don't have DNS-based name lookups in libc.
1743 This is also why Netscape ships two binaries for SunOS 4.1.x.
1745 The best solution is to compile it yourself; the configure script will
1746 check to see if you've put DNS in the shared libc and will then proceed
1747 to link against the DNS resolver library code.
1750 @node Q2.0.12, Q2.0.13, Q2.0.11, Installation
1751 @unnumberedsubsec Q2.0.12: Why can't I strip XEmacs?
1753 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:
1756 Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The
1757 link gives you a bare-boned emacs (called temacs). temacs is then run,
1758 preloading some of the lisp files. The result is then dumped into a new
1759 executable, named xemacs, which will contain all of the preloaded lisp
1762 Now, during the dump itself, the executable (code+data+symbols) is
1763 written on disk using a special unexec() function. This function is
1764 obviously heavily system dependent. And on some systems, it leads to an
1765 executable which, although valid, cannot be stripped without damage. If
1766 memory serves, this is especially the case for AIX binaries. On other
1767 architecture it might work OK.
1769 The Right Way to strip the emacs binary is to strip temacs prior to
1770 dumping xemacs. This will always work, although you can do that only if
1771 you install from sources (as temacs is @file{not} part of the binary
1775 @email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes:
1782 [ ./configure; make ]
1794 cp src/xemacs /usr/local/bin/xemacs
1797 cp lib-src/DOC-19.16-XEmacs
1801 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
1805 @node Q2.0.13, Q2.0.14, Q2.0.12, Installation
1806 @unnumberedsubsec Q2.0.13: Problems linking with Gcc on Solaris
1808 There are known difficulties linking with Gnu ld on Solaris. A typical
1809 error message might look like:
1812 unexec(): dlopen(../dynodump/dynodump.so): ld.so.1: ./temacs:
1813 fatal: relocation error:
1814 symbol not found: main: referenced in ../dynodump/dynodump.so
1817 @email{martin@@xemacs.org, Martin Buchholz} writes:
1820 You need to specify @samp{-fno-gnu-linker} as part of your flags to pass
1821 to ld. Future releases of XEmacs will try to do this automatically.
1824 @node Q2.0.14, Q2.1.1, Q2.0.13, Installation
1825 @unnumberedsubsec Q2.0.14: Make on HP/UX 9 fails after linking temacs
1827 Problem when building xemacs-19.16 on hpux 9:
1829 @email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
1832 make on hpux fails after linking temacs with a message:
1835 "make: don't know how to make .y."
1838 Solution: This is a problem with HP make revision 70.X. Either use GNU
1839 make, or install PHCO_6552, which will bring make to revision
1844 @node Q2.1.1, Q2.1.2, Q2.0.14, Installation
1845 @unnumberedsec 2.1: Trouble Shooting
1846 @unnumberedsubsec Q2.1.1: Help! XEmacs just crashed on me!
1848 First of all, don't panic. Whenever XEmacs crashes, it tries extremely
1849 hard to auto-save all of your files before dying. (The main time that
1850 this will not happen is if the machine physically lost power or if you
1851 killed the XEmacs process using @code{kill -9}). The next time you try
1852 to edit those files, you will be informed that a more recent auto-save
1853 file exists. You can use @kbd{M-x recover-file} to retrieve the
1854 auto-saved version of the file.
1856 Starting with 19.14, you may use the command @kbd{M-x recover-session}
1857 after a crash to pick up where you left off.
1859 Now, XEmacs is not perfect, and there may occasionally be times, or
1860 particular sequences of actions, that cause it to crash. If you can
1861 come up with a reproducible way of doing this (or even if you have a
1862 pretty good memory of exactly what you were doing at the time), the
1863 maintainers would be very interested in knowing about it. Post a
1864 message to comp.emacs.xemacs or send mail to @email{crashes@@xemacs.org}.
1865 Please note that the @samp{crashes} address is exclusively for crash
1868 If at all possible, include a stack backtrace of the core dump that was
1869 produced. This shows where exactly things went wrong, and makes it much
1870 easier to diagnose problems. To do this, you need to locate the core
1871 file (it's called @file{core}, and is usually sitting in the directory
1872 that you started XEmacs from, or your home directory if that other
1873 directory was not writable). Then, go to that directory and execute a
1877 gdb `which xemacs` core
1880 and then issue the command @samp{where} to get the stack backtrace. You
1881 might have to use @code{dbx} or some similar debugger in place of
1882 @code{gdb}. If you don't have any such debugger available, complain to
1883 your system administrator.
1885 It's possible that a core file didn't get produced, in which case you're
1886 out of luck. Go complain to your system administrator and tell him not
1887 to disable core files by default. Also @xref{Q2.1.15}, for tips and
1888 techniques for dealing with a debugger.
1890 When making a problem report make sure that:
1894 Report @strong{all} of the information output by XEmacs during the
1898 You mention what O/S & Hardware you are running XEmacs on.
1901 What version of XEmacs you are running.
1904 What build options you are using.
1907 If the problem is related to graphics, we will also need to know what
1908 version of the X Window System you are running, and what window manager
1912 If the problem happened on a tty, please include the terminal type.
1915 @node Q2.1.2, Q2.1.3, Q2.1.1, Installation
1916 @unnumberedsubsec Q2.1.2: Cryptic Minibuffer messages.
1918 When I try to use some particular option of some particular package, I
1919 get a cryptic error in the minibuffer.
1921 If you can't figure out what's going on, select Options/General
1922 Options/Debug on Error from the Menubar and then try and make the error
1923 happen again. This will give you a backtrace that may be enlightening.
1924 If not, try reading through this FAQ; if that fails, you could try
1925 posting to comp.emacs.xemacs (making sure to include the backtrace) and
1926 someone may be able to help. If you can identify which Emacs lisp
1927 source file the error is coming from you can get a more detailed stack
1928 backtrace by doing the following:
1932 Visit the .el file in an XEmacs buffer.
1935 Issue the command @kbd{M-x eval-current-buffer}.
1938 Reproduce the error.
1941 Depending on the version of XEmacs, you may either select Edit->Show
1942 Messages (19.13 and earlier) or Help->Recent Keystrokes/Messages (19.14
1943 and later) from the menubar to see the most recent messages. This
1944 command is bound to @kbd{C-h l} by default.
1946 @node Q2.1.3, Q2.1.4, Q2.1.2, Installation
1947 @unnumberedsubsec Q2.1.3: Translation Table Syntax messages at Startup
1949 I get tons of translation table syntax error messages during startup.
1950 How do I get rid of them?
1952 There are two causes of this problem. The first usually only strikes
1953 people using the prebuilt binaries. The culprit in both cases is the
1954 file @file{XKeysymDB}.
1958 The binary cannot find the @file{XKeysymDB} file. The location is
1959 hardcoded at compile time so if the system the binary was built on puts
1960 it a different place than your system does, you have problems. To fix,
1961 set the environment variable @var{XKEYSYMDB} to the location of the
1962 @file{XKeysymDB} file on your system or to the location of the one
1963 included with XEmacs which should be at
1967 @file{<xemacs_root_directory>/lib/xemacs-19.16/etc/XKeysymDB}.
1970 The binary is finding the XKeysymDB but it is out-of-date on your system
1971 and does not contain the necessary lines. Either ask your system
1972 administrator to replace it with the one which comes with XEmacs (which
1973 is the stock R6 version and is backwards compatible) or set your
1974 @var{XKEYSYMDB} variable to the location of XEmacs's described above.
1977 @node Q2.1.4, Q2.1.5, Q2.1.3, Installation
1978 @unnumberedsubsec Q2.1.4: Startup warnings about deducing proper fonts?
1980 How can I avoid the startup warnings about deducing proper fonts?
1982 This is highly dependent on your installation, but try with the
1983 following font as your base font for XEmacs and see what it does:
1986 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
1989 More precisely, do the following in your resource file:
1992 Emacs.default.attributeFont: \
1993 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
1996 If you just don't want to see the @samp{*Warnings*} buffer at startup
1997 time, you can set this:
2000 (setq display-warning-minimum-level 'error)
2003 The buffer still exists; it just isn't in your face.
2005 @node Q2.1.5, Q2.1.6, Q2.1.4, Installation
2006 @unnumberedsubsec Q2.1.5: XEmacs cannot connect to my X Terminal!
2008 Help! I can not get XEmacs to display on my Envizex X-terminal!
2010 Try setting the @var{DISPLAY} variable using the numeric IP address of
2011 the host you are running XEmacs from.
2013 @node Q2.1.6, Q2.1.7, Q2.1.5, Installation
2014 @unnumberedsubsec Q2.1.6: XEmacs just locked up my Linux X server!
2016 There have been several reports of the X server locking up under Linux.
2017 In all reported cases removing speedo and scaled fonts from the font
2018 path corrected the problem. This can be done with the command
2021 It is possible that using a font server may also solve the problem.
2023 @node Q2.1.7, Q2.1.8, Q2.1.6, Installation
2024 @unnumberedsubsec Q2.1.7: HP Alt key as Meta.
2026 How can I make XEmacs recognize the Alt key of my HP workstation as a
2029 Put the following line into a file and load it with xmodmap(1) before
2033 remove Mod1 = Mode_switch
2036 @node Q2.1.8, Q2.1.9, Q2.1.7, Installation
2037 @unnumberedsubsec Q2.1.8: got (wrong-type-argument color-instance-p nil)
2039 @email{nataliek@@rd.scitec.com.au, Natalie Kershaw} writes:
2042 I am trying to run xemacs 19.13 under X11R4. Whenever I move the mouse I
2043 get the following error. Has anyone seen anything like this? This
2044 doesn't occur on X11R5.
2048 (error "got (wrong-type-argument color-instance-p nil)
2049 and I don't know why!")
2053 @email{map01kd@@gold.ac.uk, dinos} writes:
2056 I think this is due to undefined resources; You need to define color
2057 backgrounds and foregrounds into your @file{.../app-defaults/Emacs}
2061 *Foreground: Black ;everything will be of black on grey95,
2062 *Background: Grey95 ;unless otherwise specified.
2063 *cursorColor: Red3 ;red3 cursor with grey95 border.
2064 *pointerColor: Red3 ;red3 pointer with grey95 border.
2068 Natalie Kershaw adds:
2071 What fixed the problem was adding some more colors to the X color
2072 database (copying the X11R5 colors over), and also defining the
2073 following resources:
2076 xemacs*cursorColor: black
2077 xemacs*pointerColor: black
2080 With the new colors installed the problem still occurs if the above
2081 resources are not defined.
2083 If the new colors are not present then an additional error occurs on
2084 XEmacs startup, which says @samp{Color Red3} not defined.
2087 @node Q2.1.9, Q2.1.10, Q2.1.8, Installation
2088 @unnumberedsubsec Q2.1.9: XEmacs causes my OpenWindows 3.0 server to crash.
2090 The OpenWindows 3.0 server is incredibly buggy. Your best bet is to
2091 replace it with one from the generic MIT X11 release. You might also
2092 try disabling parts of your @file{.emacs}, like enabling background
2095 @node Q2.1.10, Q2.1.11, Q2.1.9, Installation
2096 @unnumberedsubsec Q2.1.10: Warnings from incorrect key modifiers.
2098 The following information comes from the @file{PROBLEMS} file that comes
2101 If you're having troubles with HP/UX it is because HP/UX defines the
2102 modifiers wrong in X. Here is a shell script to fix the problem; be
2103 sure that it is run after VUE configures the X server.
2107 xmodmap 2> /dev/null - << EOF
2108 keysym Alt_L = Meta_L
2109 keysym Alt_R = Meta_R
2114 keysym Mode_switch = NoSymbol
2116 keysym Meta_R = Mode_switch
2117 add mod2 = Mode_switch
2121 @node Q2.1.11, Q2.1.12, Q2.1.10, Installation
2122 @unnumberedsubsec Q2.1.11: @samp{Can't instantiate image error...} in toolbar
2125 @email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes:
2127 I just installed the XEmacs (20.4-2) RPMS that I downloaded from
2128 @uref{http://www.xemacs.org/}. Everything works fine, except that when
2129 I place my mouse over the toolbar, it beeps and gives me this message:
2132 Can't instantiate image (probably cached):
2133 [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data
2134 (16 16 <strange control characters> ...
2137 @email{kyle_jones@@wonderworks.com, Kyle Jones} writes:
2139 This is problem specific to some Chips and Technologies video
2140 chips, when running XFree86. Putting
2142 @code{Option "sw_cursor"}
2144 in @file{XF86Config} gets rid of the problem.
2147 @node Q2.1.12, Q2.1.13, Q2.1.11, Installation
2148 @unnumberedsubsec Q2.1.12: Problems with Regular Expressions on DEC OSF1.
2150 I have xemacs 19.13 running on an alpha running OSF1 V3.2 148 and ispell
2151 would not run because it claimed the version number was incorrect
2152 although it was indeed OK. I traced the problem to the regular
2155 @email{douglask@@dstc.edu.au, Douglas Kosovic} writes:
2158 Actually it's a DEC cc optimization bug that screws up the regexp
2161 Rebuilding using the @samp{-migrate} switch for DEC cc (which uses a
2162 different sort of optimization) works fine.
2165 See @file{xemacs-19_13-dunix-3_2c.patch} at the following URL on how to
2166 build with the @samp{-migrate} flag:
2169 @uref{http://www-digital.cern.ch/carney/emacs/emacs.html}
2170 @c Link above, <URL:http://www-digital.cern.ch/carney/emacs/emacs.html> is
2171 @c dead. And the directory `carney' is empty.
2177 NOTE: There have been a variety of other problems reported that are
2178 fixed in this fashion.
2180 @node Q2.1.13, Q2.1.14, Q2.1.12, Installation
2181 @unnumberedsubsec Q2.1.13: HP/UX 10.10 and @code{create_process} failure.
2183 @email{Dave.Carrigan@@ipl.ca, Dave Carrigan} writes:
2186 With XEmacs 19.13 and HP/UX 10.10, anything that relies on the
2187 @code{create_process} function fails. This breaks a lot of things
2188 (shell-mode, compile, ange-ftp, to name a few).
2191 @email{johnson@@dtc.hp.com, Phil Johnson} writes:
2194 This is a problem specific to HP-UX 10.10. It only occurs when XEmacs
2195 is compiled for shared libraries (the default), so you can work around
2196 it by compiling a statically-linked binary (run configure with
2197 @samp{--dynamic=no}).
2199 I'm not sure whether the problem is with a particular shared library or
2200 if it's a kernel problem which crept into 10.10.
2203 @email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
2206 I had a few problems with 10.10. Apparently, some of them were solved by
2207 forcing a static link of libc (manually).
2210 @node Q2.1.14, Q2.1.15, Q2.1.13, Installation
2211 @unnumberedsubsec Q2.1.14: @kbd{C-g} doesn't work for me. Is it broken?
2213 @email{ben@@666.com, Ben Wing} writes:
2216 @kbd{C-g} does work for most people in most circumstances. If it
2217 doesn't, there are only two explanations:
2221 The code is wrapped with a binding of @code{inhibit-quit} to
2222 @code{t}. @kbd{Ctrl-Shift-G} should still work, I think.
2225 SIGIO is broken on your system, but BROKEN_SIGIO isn't defined.
2228 To test #2, try executing @code{(while t)} from the @samp{*scratch*}
2229 buffer. If @kbd{C-g} doesn't interrupt, then you're seeing #2.
2232 @email{terra@@diku.dk, Morten Welinder} writes:
2235 On some (but @emph{not} all) machines a hung XEmacs can be revived by
2236 @code{kill -FPE <pid>}. This is a hack, of course, not a solution.
2237 This technique works on a Sun4 running 4.1.3_U1. To see if it works for
2238 you, start another XEmacs and test with that first. If you get a core
2239 dump the method doesn't work and if you get @samp{Arithmetic error} then
2243 @node Q2.1.15, Q2.1.16, Q2.1.14, Installation
2244 @unnumberedsubsec Q2.1.15: How to Debug an XEmacs problem with a debugger
2246 If XEmacs does crash on you, one of the most productive things you can
2247 do to help get the bug fixed is to poke around a bit with the debugger.
2248 Here are some hints:
2252 First of all, if the crash is at all reproducible, consider very
2253 strongly recompiling your XEmacs with debugging symbols, with no
2254 optimization, and with the configure options @samp{--debug=yes} and
2255 @samp{--error-checking=all}. This will make your XEmacs run somewhat
2256 slower but make it a lot more likely to catch the problem earlier
2257 (closer to its source), and a lot easier to determine what's going on
2261 If you're able to run XEmacs under a debugger and reproduce the crash
2262 (if it's inconvenient to do this because XEmacs is already running or is
2263 running in batch mode as part of a bunch of scripts, consider attaching
2264 to the existing process with your debugger; most debuggers let you do
2265 this by substituting the process ID for the core file when you invoke
2266 the debugger from the command line, or by using the @code{attach}
2267 command or something similar), here are some things you can do:
2270 If XEmacs is hitting an assertion failure, put a breakpoint on
2271 @code{assert_failed()}.
2274 If XEmacs is hitting some weird Lisp error that's causing it to crash
2275 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is
2276 declared static in eval.c.
2279 Internally, you will probably see lots of variables that hold objects of
2280 type @code{Lisp_Object}. These are exactly what they appear to be,
2281 i.e. references to Lisp objects. Printing them out with the debugger
2282 probably won't be too useful---you'll likely just see a number. To
2283 decode them, do this:
2286 call debug_print (OBJECT)
2289 where @var{OBJECT} is whatever you want to decode (it can be a variable,
2290 a function call, etc.). This will print out a readable representation
2291 on the TTY from which the xemacs process was invoked.
2294 If you want to get a Lisp backtrace showing the Lisp call
2298 call debug_backtrace ()
2302 Using @code{debug_print} and @code{debug_backtrace} has two
2303 disadvantages - it can only be used with a running xemacs process, and
2304 it cannot display the internal C structure of a Lisp Object. Even if
2305 all you've got is a core dump, all is not lost.
2307 If you're using GDB, there are some macros in the file
2308 @file{src/gdbinit} in the XEmacs source distribution that should make it
2309 easier for you to decode Lisp objects. Copy this file to
2310 @file{~/.gdbinit}, or @code{source} it from @file{~/.gdbinit}, and use
2311 the macros defined therein. In particular, use the @code{pobj} macro to
2312 print the internal C representation of a lisp object. This will work
2313 with a core file or not-yet-run executable. The aliases @code{ldp} and
2314 @code{lbt} are provided for conveniently calling @code{debug_print} and
2315 @code{debug_backtrace}.
2317 If you are using Sun's @file{dbx} debugger, there is an equivalent file
2318 @file{src/dbxrc} to copy to or source from @file{~/.dbxrc}.
2321 If you're using a debugger to get a C stack backtrace and you're seeing
2322 stack traces with some of the innermost frames mangled, it may be due to
2323 dynamic linking. (This happens especially under Linux.) Consider
2324 reconfiguring with @samp{--dynamic=no}. Also, sometimes (again under
2325 Linux), stack backtraces of core dumps will have the frame where the
2326 fatal signal occurred mangled; if you can obtain a stack trace while
2327 running the XEmacs process under a debugger, the stack trace should be
2330 @email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so version 1.8
2331 if dynamic linking and debugging is a problem on Linux.
2334 If you're using a debugger to get a C stack backtrace and you're
2335 getting a completely mangled and bogus stack trace, it's probably due to
2336 one of the following:
2340 Your executable has been stripped. Bad news. Tell your sysadmin not to
2341 do this---it doesn't accomplish anything except to save a bit of disk
2342 space, and makes debugging much much harder.
2345 Your stack is getting trashed. Debugging this is hard; you have to do a
2346 binary-search type of narrowing down where the crash occurs, until you
2347 figure out exactly which line is causing the problem. Of course, this
2348 only works if the bug is highly reproducible.
2351 If your stack trace has exactly one frame in it, with address 0x0, this
2352 could simply mean that XEmacs attempted to execute code at that address,
2353 e.g. through jumping to a null function pointer. Unfortunately, under
2354 those circumstances, GDB under Linux doesn't know how to get a stack
2355 trace. (Yes, this is the third Linux-related problem I've mentioned. I
2356 have no idea why GDB under Linux is so bogus. Complain to the GDB
2357 authors, or to comp.os.linux.development.system). Again, you'll have to
2358 use the narrowing-down process described above.
2361 If you compiled 19.14 with @samp{--debug} (or by default in later
2362 versions), you will get a Lisp backtrace output when XEmacs crashes, so
2363 you'll have something useful.
2368 If you compile with the newer gcc variants gcc-2.8 or egcs, you will
2369 also need gdb 4.17. Earlier releases of gdb can't handle the debug
2370 information generated by the newer compilers.
2373 The above information on using @file{src/gdbinit} works for XEmacs-21.0
2374 and above. For older versions of XEmacs, there are different
2375 @file{gdbinit} files provided in the @file{src} directory. Use the one
2376 corresponding to the configure options used when building XEmacs.
2380 @node Q2.1.16, Q2.1.17, Q2.1.15, Installation
2381 @unnumberedsubsec Q2.1.16: XEmacs crashes in @code{strcat} on HP/UX 10
2383 >From the problems database (through
2384 @uref{http://support.mayfield.hp.com/}):
2387 Problem Report: 5003302299
2390 System/Model: 9000/700
2391 Product Name: HPUX S800 10.0X
2392 Product Vers: 9245XB.10.00
2394 Description: strcat(3C) may read beyond
2395 end of source string, can cause SIGSEGV
2398 *** PROBLEM TEXT ***
2399 strcat(3C) may read beyond the source string onto an unmapped page,
2400 causing a segmentation violation.
2403 @node Q2.1.17, Q2.1.18, Q2.1.16, Installation
2404 @unnumberedsubsec Q2.1.17: @samp{Marker does not point anywhere}
2406 As with other errors, set @code{debug-on-error} to @code{t} to get the
2407 backtrace when the error occurs. Specifically, two problems have been
2408 reported (and fixed).
2412 A problem with line-number-mode in XEmacs 19.14 affected a large number
2413 of other packages. If you see this error message, turn off
2417 A problem with some early versions of Gnus 5.4 caused this error.
2421 @node Q2.1.18, Q2.1.19, Q2.1.17, Installation
2422 @unnumberedsubsec Q2.1.18: 19.14 hangs on HP/UX 10.10.
2424 @email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
2427 For the record, compiling on hpux 10.10 leads to a hang in Gnus when
2428 compiled with optimization on.
2430 I've just discovered that my hpux 10.01 binary was working less well
2431 than expected. In fact, on a 10.10 system, @code{(while t)} was not
2432 interrupted by @kbd{C-g}. I defined @code{BROKEN_SIGIO} and recompiled on
2433 10.10, and... the hang is now gone.
2435 As far as configure goes, this will be a bit tricky: @code{BROKEN_SIGIO}
2436 is needed on 10.10, but @strong{not} on 10.01: if I run my 10.01 binary
2437 on a 10.01 machine, without @code{BROKEN_SIGIO} being defined, @kbd{C-g}
2441 @email{cognot@@ensg.u-nancy.fr, Richard Cognot} adds:
2444 Apparently somebody has found the reason why there is this
2449 interrupted...} message for each event. For some reason, libcurses
2450 reimplements a @code{select()} system call, in a highly broken fashion.
2451 The fix is to add a -lc to the link line @emph{before} the
2452 -lxcurses. XEmacs will then use the right version of @code{select()}.
2456 @email{af@@biomath.jussieu.fr, Alain Fauconnet} writes:
2459 The @emph{real} solution is to @emph{not} link -lcurses in! I just
2460 changed -lcurses to -ltermcap in the Makefile and it fixed:
2464 The @samp{poll: interrupted system call} message.
2467 A more serious problem I had discovered in the meantime, that is the
2468 fact that subprocess handling was seriously broken: subprocesses
2469 e.g. started by AUC TeX for TeX compilation of a buffer would
2470 @emph{hang}. Actually they would wait forever for emacs to read the
2471 socket which connects stdout...
2475 @node Q2.1.19, Q2.1.20, Q2.1.18, Installation
2476 @unnumberedsubsec Q2.1.19: XEmacs does not follow the local timezone.
2478 When using one of the prebuilt binaries many users have observed that
2479 XEmacs uses the timezone under which it was built, but not the timezone
2480 under which it is running. The solution is to add:
2483 (set-time-zone-rule "MET")
2486 to your @file{.emacs} or the @file{site-start.el} file if you can.
2487 Replace @code{MET} with your local timezone.
2489 @node Q2.1.20, Q2.1.21, Q2.1.19, Installation
2490 @unnumberedsubsec Q2.1.20: @samp{Symbol's function definition is void: hkey-help-show.}
2492 This is a problem with a partially loaded hyperbole. Try adding:
2495 (require 'hmouse-drv)
2498 where you load hyperbole and the problem should go away.
2500 @node Q2.1.21, Q2.1.22, Q2.1.20, Installation
2501 @unnumberedsubsec Q2.1.21: Every so often the XEmacs frame freezes
2503 This problem has been fixed in 19.15, and was due to a not easily
2504 reproducible race condition.
2506 @node Q2.1.22, Q2.1.23, Q2.1.21, Installation
2507 @unnumberedsubsec Q2.1.22: XEmacs seems to take a really long time to do some things
2509 @email{dmoore@@ucsd.edu, David Moore} writes:
2512 Two things you can do:
2516 When you see it going mad like this, you might want to use gdb from an
2517 'xterm' to attach to the running process and get a stack trace. To do
2521 gdb /path/to/xemacs/xemacs ####
2524 Where @code{####} is the process id of your xemacs, instead of
2525 specifying the core. When gdb attaches, the xemacs will stop [1] and
2526 you can type `where' in gdb to get a stack trace as usual. To get
2527 things moving again, you can just type `quit' in gdb. It'll tell you
2528 the program is running and ask if you want to quit anyways. Say 'y' and
2529 it'll quit and have your emacs continue from where it was at.
2533 Turn on debug-on-quit early on. When you think things are going slow
2534 hit C-g and it may pop you in the debugger so you can see what routine
2535 is running. Press `c' to get going again.
2537 debug-on-quit doesn't work if something's turned on inhibit-quit or in
2538 some other strange cases.
2541 @node Q2.1.23, , Q2.1.22, Installation
2542 @unnumberedsubsec Q2.1.23: Movemail on Linux does not work for XEmacs 19.15 and later.
2544 Movemail used to work fine in 19.14 but has stopped working in 19.15
2545 and 20.x. I am using Linux.
2547 @email{steve@@xemacs.org, SL Baur} writes:
2550 Movemail on Linux used to default to using flock file locking. With
2551 19.15 and later versions it now defaults to using @code{.lock} file
2552 locking. If this is not appropriate for your system, edit src/s/linux.h
2553 and uncomment the line that reads:
2556 #define MAIL_USE_FLOCK
2560 @node Customization, Subsystems, Installation, Top
2561 @unnumbered 3 Customization and Options
2563 This is part 3 of the XEmacs Frequently Asked Questions list. This
2564 section is devoted to Customization and screen settings.
2567 Customization---Emacs Lisp and @file{.emacs}:
2568 * Q3.0.1:: What version of Emacs am I running?
2569 * Q3.0.2:: How do I evaluate Elisp expressions?
2570 * Q3.0.3:: @code{(setq tab-width 6)} behaves oddly.
2571 * Q3.0.4:: How can I add directories to the @code{load-path}?
2572 * Q3.0.5:: How to check if a lisp function is defined?
2573 * Q3.0.6:: Can I force the output of @code{(face-list)} to a buffer?
2574 * Q3.0.7:: Font selections don't get saved after @code{Save Options}.
2575 * Q3.0.8:: How do I make a single minibuffer frame?
2576 * Q3.0.9:: What is @code{Customize}?
2578 X Window System & Resources:
2579 * Q3.1.1:: Where is a list of X resources?
2580 * Q3.1.2:: How can I detect a color display?
2581 * Q3.1.3:: @code{(set-screen-width)} worked in 19.6, but not in 19.13?
2582 * Q3.1.4:: Specifying @code{Emacs*EmacsScreen.geometry} in @file{.emacs} does not work in 19.15?
2583 * Q3.1.5:: How can I get the icon to just say @samp{XEmacs}?
2584 * Q3.1.6:: How can I have the window title area display the full path?
2585 * Q3.1.7:: @samp{xemacs -name junk} doesn't work?
2586 * Q3.1.8:: @samp{-iconic} doesn't work.
2588 Textual Fonts & Colors:
2589 * Q3.2.1:: How can I set color options from @file{.emacs}?
2590 * Q3.2.2:: How do I set the text, menu and modeline fonts?
2591 * Q3.2.3:: How can I set the colors when highlighting a region?
2592 * Q3.2.4:: How can I limit color map usage?
2593 * Q3.2.5:: My tty supports color, but XEmacs doesn't use them.
2594 * Q3.2.6:: Can I have pixmap backgrounds in XEmacs?
2597 * Q3.3.1:: How can I make the modeline go away?
2598 * Q3.3.2:: How do you have XEmacs display the line number in the modeline?
2599 * Q3.3.3:: How do I get XEmacs to put the time of day on the modeline?
2600 * Q3.3.4:: How do I turn off current chapter from AUC TeX modeline?
2601 * Q3.3.5:: How can one change the modeline color based on the mode used?
2603 3.4 Multiple Device Support:
2604 * Q3.4.1:: How do I open a frame on another screen of my multi-headed display?
2605 * Q3.4.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
2608 * Q3.5.1:: How can I bind complex functions (or macros) to keys?
2609 * Q3.5.2:: How can I stop down-arrow from adding empty lines to the bottom of my buffers?
2610 * Q3.5.3:: How do I bind C-. and C-; to scroll one line up and down?
2611 * Q3.5.4:: Globally binding @kbd{Delete}?
2612 * Q3.5.5:: Scrolling one line at a time.
2613 * Q3.5.6:: How to map @kbd{Help} key alone on Sun type4 keyboard?
2614 * Q3.5.7:: How can you type in special characters in XEmacs?
2615 * Q3.5.8:: Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
2616 * Q3.5.9:: How do I make the Delete key delete forward?
2617 * Q3.5.10:: Can I turn on @dfn{sticky} modifier keys?
2618 * Q3.5.11:: How do I map the arrow keys?
2621 * Q3.6.1:: Is there a way to make the bar cursor thicker?
2622 * 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?
2623 * Q3.6.3:: Can I make the cursor blink?
2625 The Mouse and Highlighting:
2626 * Q3.7.1:: How can I turn off Mouse pasting?
2627 * Q3.7.2:: How do I set control/meta/etc modifiers on mouse buttons?
2628 * Q3.7.3:: Clicking the left button does not do anything in buffer list.
2629 * Q3.7.4:: How can I get a list of buffers when I hit mouse button 3?
2630 * Q3.7.5:: Why does cut-and-paste not work between XEmacs and a cmdtool?
2631 * Q3.7.6:: How I can set XEmacs up so that it pastes where the text cursor is?
2632 * Q3.7.7:: How do I select a rectangular region?
2633 * Q3.7.8:: Why does @kbd{M-w} take so long?
2635 The Menubar and Toolbar:
2636 * Q3.8.1:: How do I get rid of the menu (or menubar)?
2637 * Q3.8.2:: Can I customize the basic menubar?
2638 * Q3.8.3:: How do I control how many buffers are listed in the menu @code{Buffers} list?
2639 * Q3.8.4:: Resources like @code{Emacs*menubar*font} are not working?
2640 * Q3.8.5:: How can I bind a key to a function to toggle the toolbar?
2643 * Q3.9.1:: How can I disable the scrollbar?
2644 * Q3.9.2:: How can one use resources to change scrollbar colors?
2645 * Q3.9.3:: Moving the scrollbar can move the point; can I disable this?
2646 * Q3.9.4:: How can I get automatic horizontal scrolling?
2649 * Q3.10.1:: How can I turn off or change highlighted selections?
2650 * Q3.10.2:: How do I get that typing on an active region removes it?
2651 * Q3.10.3:: Can I turn off the highlight during isearch?
2652 * Q3.10.4:: How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
2653 * Q3.10.5:: The region disappears when I hit the end of buffer while scrolling.
2656 @node Q3.0.1, Q3.0.2, Customization, Customization
2657 @unnumberedsec 3.0: Customization -- Emacs Lisp and .emacs
2658 @unnumberedsubsec Q3.0.1: What version of Emacs am I running?
2660 How can @file{.emacs} determine which of the family of Emacsen I am
2663 To determine if you are currently running GNU Emacs 18, GNU Emacs 19,
2664 XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the
2665 example given in @file{etc/sample.emacs}. There are other nifty things
2668 For all new code, all you really need to do is:
2671 (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
2674 @node Q3.0.2, Q3.0.3, Q3.0.1, Customization
2675 @unnumberedsubsec Q3.0.2: How can I evaluate Emacs-Lisp expressions?
2677 I know I can evaluate Elisp expressions from @code{*scratch*} buffer
2678 with @kbd{C-j} after the expression. How do I do it from another
2681 Press @kbd{M-:} (the default binding of @code{eval-expression}), and
2682 enter the expression to the minibuffer. In XEmacs prior to 19.15
2683 @code{eval-expression} used to be a disabled command by default. If
2684 this is the case, upgrade your XEmacs.
2686 @node Q3.0.3, Q3.0.4, Q3.0.2, Customization
2687 @unnumberedsubsec Q3.0.3: @code{(setq tab-width 6)} behaves oddly.
2689 If you put @code{(setq tab-width 6)} in your @file{.emacs} file it does
2690 not work! Is there a reason for this? If you do it at the EVAL prompt
2691 it works fine!! How strange.
2693 Use @code{setq-default} instead, since @code{tab-width} is
2696 @node Q3.0.4, Q3.0.5, Q3.0.3, Customization
2697 @unnumberedsubsec Q3.0.4: How can I add directories to the @code{load-path}?
2699 Here are two ways to do that, one that puts your directories at the
2700 front of the load-path, the other at the end:
2703 ;;; Add things at the beginning of the load-path, do not add
2704 ;;; duplicate directories:
2705 (pushnew "bar" load-path :test 'equal)
2707 (pushnew "foo" load-path :test 'equal)
2709 ;;; Add things at the end, unconditionally
2710 (setq load-path (nconc load-path '("foo" "bar")))
2713 @email{keithh@@nortel.ca, keith (k.p.) hanlan} writes:
2716 To add directories using Unix shell metacharacters use
2717 @file{expand-file-name} like this:
2720 (push (expand-file-name "~keithh/.emacsdir") load-path)
2724 @node Q3.0.5, Q3.0.6, Q3.0.4, Customization
2725 @unnumberedsubsec Q3.0.5: How to check if a lisp function is defined?
2727 Use the following elisp:
2733 It's almost always a mistake to test @code{emacs-version} or any similar
2736 Instead, use feature-tests, such as @code{featurep}, @code{boundp},
2737 @code{fboundp}, or even simple behavioral tests, eg.:
2740 (defvar foo-old-losing-code-p
2741 (condition-case nil (progn (losing-code t) nil)
2742 (wrong-number-of-arguments t)))
2745 There is an incredible amount of broken code out there which could work
2746 much better more often in more places if it did the above instead of
2747 trying to divine its environment from the value of one variable.
2749 @node Q3.0.6, Q3.0.7, Q3.0.5, Customization
2750 @unnumberedsubsec Q3.0.6: Can I force the output of @code{(face-list)} to a buffer?
2752 It would be good having it in a buffer, as the output of
2753 @code{(face-list)} is too wide to fit to a minibuffer.
2755 Evaluate the expression in the @samp{*scratch*} buffer with point after
2756 the rightmost paren and typing @kbd{C-j}.
2758 If the minibuffer smallness is the only problem you encounter, you can
2759 simply press @kbd{C-h l} to get the former minibuffer contents in a
2762 @node Q3.0.7, Q3.0.8, Q3.0.6, Customization
2763 @unnumberedsubsec Q3.0.7: Font selections in don't get saved after @code{Save Options}.
2765 For XEmacs 19.14 and previous:
2767 @email{mannj@@ll.mit.edu, John Mann} writes:
2770 You have to go to Options->Frame Appearance and unselect
2771 @samp{Frame-Local Font Menu}. If this option is selected, font changes
2772 are only applied to the @emph{current} frame and do @emph{not} get saved
2773 when you save options.
2776 For XEmacs 19.15 and later:
2778 Implement the above as well as set the following in your @file{.emacs}
2781 (setq options-save-faces t)
2784 @node Q3.0.8, Q3.0.9, Q3.0.7, Customization
2785 @unnumberedsubsec Q3.0.8: How do I get a single minibuffer frame?
2787 @email{acs@@acm.org, Vin Shelton} writes:
2790 (setq initial-frame-plist '(minibuffer nil))
2791 (setq default-frame-plist '(minibuffer nil))
2792 (setq default-minibuffer-frame
2797 menubar-visible-p nil
2798 default-toolbar-visible-p nil
2802 has-modeline-p nil)))
2803 (frame-notice-user-settings)
2806 @strong{Please note:} The single minibuffer frame may not be to everyone's
2807 taste, and there any number of other XEmacs options settings that may
2808 make it difficult or inconvenient to use.
2810 @node Q3.0.9, Q3.1.1, Q3.0.8, Customization
2811 @unnumberedsubsec Q3.0.9: What is @code{Customize}?
2813 Starting with XEmacs 20.2 there is new system 'Customize' for customizing
2816 You can access @code{Customize} from the @code{Options} menu
2817 or invoking one of customize commands by typing eg.
2818 @kbd{M-x customize}, @kbd{M-x customize-face},
2819 @kbd{M-x customize-variable} or @kbd{M-x customize-apropos}.
2821 Starting with XEmacs 20.3 there is also new `browser' mode for Customize.
2822 Try it out with @kbd{M-x customize-browse}
2824 @node Q3.1.1, Q3.1.2, Q3.0.9, Customization
2825 @unnumberedsec 3.1: X Window System & Resources
2826 @unnumberedsubsec Q3.1.1: Where is a list of X resources?
2828 Search through the @file{NEWS} file for @samp{X Resources}. A fairly
2829 comprehensive list is given after it.
2831 In addition, an @file{app-defaults} file is supplied,
2832 @file{etc/Emacs.ad} listing the defaults. The file
2833 @file{etc/sample.Xdefaults} gives a set of defaults that you might
2834 consider. It is essentially the same as @file{etc/Emacs.ad} but some
2835 entries are slightly altered. Be careful about installing the contents
2836 of this file into your @file{.Xdefaults} or @file{.Xresources} file if
2837 you use GNU Emacs under X11 as well.
2839 @node Q3.1.2, Q3.1.3, Q3.1.1, Customization
2840 @unnumberedsubsec Q3.1.2: How can I detect a color display?
2842 You can test the return value of the function @code{(device-class)}, as
2846 (when (eq (device-class) 'color)
2847 (set-face-foreground 'font-lock-comment-face "Grey")
2848 (set-face-foreground 'font-lock-string-face "Red")
2853 @node Q3.1.3, Q3.1.4, Q3.1.2, Customization
2854 @unnumberedsubsec Q3.1.3: @code{(set-screen-width)} worked in 19.6, but not in 19.13?
2856 In Lucid Emacs 19.6 I did @code{(set-screen-width @var{characters})} and
2857 @code{(set-screen-height @var{lines})} in my @file{.emacs} instead of
2858 specifying @code{Emacs*EmacsScreen.geometry} in my
2862 @file{.Xdefaults} but
2863 this does not work in XEmacs 19.13.
2865 These two functions now take frame arguments:
2868 (set-frame-width (selected-frame) @var{characters})
2869 (set-frame-height (selected-frame) @var{lines})
2872 @node Q3.1.4, Q3.1.5, Q3.1.3, Customization
2873 @unnumberedsubsec Q3.1.4: Specifying @code{Emacs*EmacsScreen.geometry} in @file{.emacs} does not work in 19.15?
2875 In XEmacs 19.11 I specified @code{Emacs*EmacsScreen.geometry} in
2876 my @file{.emacs} but this does not work in XEmacs 19.15.
2878 We have switched from using the term @dfn{screen} to using the term
2881 The correct entry for your @file{.Xdefaults} is now:
2884 Emacs*EmacsFrame.geometry
2887 @node Q3.1.5, Q3.1.6, Q3.1.4, Customization
2888 @unnumberedsubsec Q3.1.5: How can I get the icon to just say @samp{XEmacs}?
2890 I'd like the icon to just say @samp{XEmacs}, and not include the name of
2891 the current file in it.
2893 Add the following line to your @file{.emacs}:
2896 (setq frame-icon-title-format "XEmacs")
2899 @node Q3.1.6, Q3.1.7, Q3.1.5, Customization
2900 @unnumberedsubsec Q3.1.6: How can I have the window title area display the full path?
2902 I'd like to have the window title area display the full directory/name
2903 of the current buffer file and not just the name.
2905 Add the following line to your @file{.emacs}:
2908 (setq frame-title-format "%S: %f")
2911 A more sophisticated title might be:
2914 (setq frame-title-format
2915 '("%S: " (buffer-file-name "%f"
2916 (dired-directory dired-directory "%b"))))
2919 That is, use the file name, or the dired-directory, or the buffer name.
2921 @node Q3.1.7, Q3.1.8, Q3.1.6, Customization
2922 @unnumberedsubsec Q3.1.7: @samp{xemacs -name junk} doesn't work?
2924 When I run @samp{xterm -name junk}, I get an xterm whose class name
2925 according to xprop, is @samp{junk}. This is the way it's supposed to
2926 work, I think. When I run @samp{xemacs -name junk} the class name is
2927 not set to @samp{junk}. It's still @samp{emacs}. What does
2928 @samp{xemacs -name} really do? The reason I ask is that my window
2929 manager (fvwm) will make a window sticky and I use XEmacs to read my
2930 mail. I want that XEmacs window to be sticky, without having to use the
2931 window manager's function to set the window sticky. What gives?
2933 @samp{xemacs -name} sets the application name for the program (that is,
2934 the thing which normally comes from @samp{argv[0]}). Using @samp{-name}
2935 is the same as making a copy of the executable with that new name. The
2936 @code{WM_CLASS} property on each frame is set to the frame-name, and the
2937 application-class. So, if you did @samp{xemacs -name FOO} and then
2938 created a frame named @var{BAR}, you'd get an X window with WM_CLASS =
2939 @code{( "BAR", "Emacs")}. However, the resource hierarchy for this
2943 Name: FOO .shell .container .BAR
2944 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
2947 instead of the default
2950 Name: xemacs.shell .container .emacs
2951 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
2955 It is arguable that the first element of WM_CLASS should be set to the
2956 application-name instead of the frame-name, but I think that's less
2957 flexible, since it does not give you the ability to have multiple frames
2958 with different WM_CLASS properties. Another possibility would be for
2959 the default frame name to come from the application name instead of
2960 simply being @samp{emacs}. However, at this point, making that change
2961 would be troublesome: it would mean that many users would have to make
2962 yet another change to their resource files (since the default frame name
2963 would suddenly change from @samp{emacs} to @samp{xemacs}, or whatever
2964 the executable happened to be named), so we'd rather avoid it.
2966 To make a frame with a particular name use:
2969 (make-frame '((name . "the-name")))
2972 @node Q3.1.8, Q3.2.1, Q3.1.7, Customization
2973 @unnumberedsubsec Q3.1.8: @samp{-iconic} doesn't work.
2975 When I start up XEmacs using @samp{-iconic} it doesn't work right.
2976 Using @samp{-unmapped} on the command line, and setting the
2977 @code{initiallyUnmapped} X Resource don't seem to help much either...
2979 @email{ben@@666.com, Ben Wing} writes:
2982 Ugh, this stuff is such an incredible mess that I've about given up
2983 getting it to work. The principal problem is numerous window-manager
2987 @node Q3.2.1, Q3.2.2, Q3.1.8, Customization
2988 @unnumberedsec 3.2: Textual Fonts & Colors
2989 @unnumberedsubsec Q3.2.1: How can I set color options from @file{.emacs}?
2991 How can I set the most commonly used color options from my @file{.emacs}
2992 instead of from my @file{.Xdefaults}?
2997 (set-face-background 'default "bisque") ; frame background
2998 (set-face-foreground 'default "black") ; normal text
2999 (set-face-background 'zmacs-region "red") ; When selecting w/
3001 (set-face-foreground 'zmacs-region "yellow")
3002 (set-face-font 'default "*courier-bold-r*120-100-100*")
3003 (set-face-background 'highlight "blue") ; Ie when selecting
3005 (set-face-foreground 'highlight "yellow")
3006 (set-face-background 'modeline "blue") ; Line at bottom
3008 (set-face-foreground 'modeline "white")
3009 (set-face-font 'modeline "*bold-r-normal*140-100-100*")
3010 (set-face-background 'isearch "yellow") ; When highlighting
3012 (set-face-foreground 'isearch "red")
3013 (setq x-pointer-foreground-color "black") ; Adds to bg color,
3015 (setq x-pointer-background-color "blue") ; This is color
3020 @node Q3.2.2, Q3.2.3, Q3.2.1, Customization
3021 @unnumberedsubsec Q3.2.2: How do I set the text, menu and modeline fonts?
3023 Note that you should use @samp{Emacs.} and not @samp{Emacs*} when
3024 setting face values.
3026 In @file{.Xdefaults}:
3029 Emacs.default.attributeFont: -*-*-medium-r-*-*-*-120-*-*-m-*-*-*
3030 Emacs*menubar*font: fixed
3031 Emacs.modeline.attributeFont: fixed
3034 This is confusing because modeline is a face, and can be found listed
3035 with all faces in the current mode by using @kbd{M-x set-face-font
3036 (enter) ?}. It uses the face specification of @code{attributeFont},
3037 while menubar is a normal X thing that uses the specification
3038 @code{font}. With Motif it may be necessary to use @code{fontList}
3039 instead of @code{font}.
3041 @node Q3.2.3, Q3.2.4, Q3.2.2, Customization
3042 @unnumberedsubsec Q3.2.3: How can I set the colors when highlighting a region?
3044 How can I set the background/foreground colors when highlighting a
3047 You can change the face @code{zmacs-region} either in your
3051 Emacs.zmacs-region.attributeForeground: firebrick
3052 Emacs.zmacs-region.attributeBackground: lightseagreen
3055 or in your @file{.emacs}:
3058 (set-face-background 'zmacs-region "red")
3059 (set-face-foreground 'zmacs-region "yellow")
3062 @node Q3.2.4, Q3.2.5, Q3.2.3, Customization
3063 @unnumberedsubsec Q3.2.4: How can I limit color map usage?
3065 I'm using Netscape (or another color grabber like XEmacs);
3066 is there anyway to limit the number of available colors in the color map?
3068 XEmacs 19.13 didn't have such a mechanism (unlike netscape, or other
3069 color-hogs). One solution is to start XEmacs prior to netscape, since
3070 this will prevent Netscape from grabbing all colors (but Netscape will
3071 complain). You can use the flags for Netscape, like -mono, -ncols <#>
3072 or -install (for mono, limiting to <#> colors, or for using a private
3073 color map). Since Netscape will take the entire colormap and never
3074 release it, the only reasonable way to run it is with @samp{-install}.
3076 If you have the money, another solution would be to use a truecolor or
3079 Starting with XEmacs 19.14, XEmacs uses the closest available color if
3080 the colormap is full, so it's O.K. now to start Netscape first.
3082 @node Q3.2.5, Q3.2.6, Q3.2.4, Customization
3083 @unnumberedsubsec Q3.2.5: My tty supports color, but XEmacs doesn't use them.
3085 XEmacs tries to automatically determine whether your tty supports color,
3086 but sometimes guesses wrong. In that case, you can make XEmacs Do The
3087 Right Thing using this Lisp code:
3090 (if (eq 'tty (device-type))
3091 (set-device-class nil 'color))
3094 @node Q3.2.6, Q3.3.1, Q3.2.5, Customization
3095 @unnumberedsubsec Q3.2.6: Can I have pixmap backgrounds in XEmacs?
3097 @email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes:
3100 There are several ways to do it. For example, you could specify a
3101 default pixmap image to use in your @file{~/.Xresources}, e.g.,
3105 Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm
3109 and then reload ~/.Xresources and restart XEmacs. Alternatively,
3110 since each face can have its own pixmap background, a better way
3111 would be to set a face's pixmap within your XEmacs init file, e.g.,
3114 (set-face-background-pixmap 'default "/path/to/image.xpm")
3115 (set-face-background-pixmap 'bold "/path/to/another_image.xpm")
3118 and so on. You can also do this interactively via @kbd{M-x edit-faces}.
3122 @unnumberedsec 3.3: The Modeline
3123 @node Q3.3.1, Q3.3.2, Q3.2.6, Customization
3124 @unnumberedsubsec Q3.3.1: How can I make the modeline go away?
3127 (set-specifier has-modeline-p nil)
3130 Starting with XEmacs 19.14 the modeline responds to mouse clicks, so if
3131 you haven't liked or used the modeline in the past, you might want to
3132 try the new version out.
3134 @node Q3.3.2, Q3.3.3, Q3.3.1, Customization
3135 @unnumberedsubsec Q3.3.2: How do you have XEmacs display the line number in the modeline?
3137 Add the following line to your @file{.emacs} file to display the
3141 (line-number-mode 1)
3144 Use the following to display the column number:
3147 (column-number-mode 1)
3150 Or select from the @code{Options} menu
3154 @code{Customize->Emacs->Editing->Basics->Line Number Mode}
3159 @code{Customize->Emacs->Editing->Basics->Column Number Mode}
3161 Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
3163 @node Q3.3.3, Q3.3.4, Q3.3.2, Customization
3164 @unnumberedsubsec Q3.3.3: How do I get XEmacs to put the time of day on the modeline?
3166 Add the following line to your @file{.emacs} file to display the
3173 See @code{Customize} from the @code{Options} menu for customization.
3175 @node Q3.3.4, Q3.3.5, Q3.3.3, Customization
3176 @unnumberedsubsec Q3.3.4: How do I turn off current chapter from AUC TeX modeline?
3178 With AUC TeX, fast typing is hard because the current chapter, section
3179 etc. are given in the modeline. How can I turn this off?
3181 It's not AUC TeX, it comes from @code{func-menu} in @file{func-menu.el}.
3182 Add this code to your @file{.emacs} to turn it off:
3185 (setq fume-display-in-modeline-p nil)
3188 Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
3192 (add-hook 'TeX-mode-hook
3193 '(lambda () (setq fume-display-in-modeline-p nil)))
3196 @email{dhughes@@origin-at.co.uk, David Hughes} writes:
3199 If you have 19.14 or later, try this instead; you'll still get the
3200 function name displayed in the modeline, but it won't attempt to keep
3201 track when you modify the file. To refresh when it gets out of synch,
3202 you simply need click on the @samp{Rescan Buffer} option in the
3206 (setq-default fume-auto-rescan-buffer-p nil)
3210 @node Q3.3.5, Q3.4.1, Q3.3.4, Customization
3211 @unnumberedsubsec Q3.3.5: How can one change the modeline color based on the mode used?
3213 You can use something like the following:
3216 (add-hook 'lisp-mode-hook
3218 (set-face-background 'modeline "red" (current-buffer))))
3221 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
3222 colors change from the default set in your @file{.emacs}. The change
3223 will only be made in the buffer you just entered (which contains the
3224 Lisp file you are editing) and will not affect the modeline colors
3232 The hook is the mode name plus @code{-hook}. eg. c-mode-hook,
3233 c++-mode-hook, emacs-lisp-mode-hook (used for your @file{.emacs} or a
3234 @file{xx.el} file), lisp-interaction-mode-hook (the @samp{*scratch*}
3235 buffer), text-mode-hook, etc.
3238 Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)},
3239 otherwise you will erase anything that anybody has already put on the
3243 You can also do @code{(set-face-font 'modeline @var{font})},
3244 eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*"
3245 (current-buffer))} if you wish the modeline font to vary based on the
3249 This works in 19.15 as well, but there are additional modeline faces,
3250 @code{modeline-buffer-id}, @code{modeline-mousable}, and
3251 @code{modeline-mousable-minor-mode}, which you may want to customize.
3253 @node Q3.4.1, Q3.4.2, Q3.3.5, Customization
3254 @unnumberedsec 3.4: Multiple Device Support
3255 @unnumberedsubsec Q3.4.1: How do I open a frame on another screen of my multi-headed display?
3257 The support for this was revamped for 19.14. Use the command
3258 @kbd{M-x make-frame-on-display}. This command is also on the File menu
3261 XEmacs 19.14 and later also have the command @code{make-frame-on-tty}
3262 which will establish a connection to any tty-like device. Opening the
3263 TTY devices should be left to @code{gnuclient}, though.
3265 @node Q3.4.2, Q3.5.1, Q3.4.1, Customization
3266 @unnumberedsubsec Q3.4.2: Can I really connect to a running XEmacs after calling up over a modem? How?
3268 If you're not running at least XEmacs 19.14, you can't. Otherwise check
3269 out the @code{gnuattach} program supplied with XEmacs. Starting with
3270 XEmacs 20.3, @code{gnuattach} and @code{gnudoit} functionality is
3271 provided by @code{gnuclient}.
3273 Also @xref{Q5.0.12}.
3275 @node Q3.5.1, Q3.5.2, Q3.4.2, Customization
3276 @unnumberedsec 3.5: The Keyboard
3277 @unnumberedsubsec Q3.5.1: How can I bind complex functions (or macros) to keys?
3279 As an example, say you want the @kbd{paste} key on a Sun keyboard to
3280 insert the current Primary X selection at point. You can accomplish this
3284 (define-key global-map [f18] 'x-insert-selection)
3287 However, this only works if there is a current X selection (the
3288 selection will be highlighted). The functionality I like is for the
3289 @kbd{paste} key to insert the current X selection if there is one,
3290 otherwise insert the contents of the clipboard. To do this you need to
3291 pass arguments to @code{x-insert-selection}. This is done by wrapping
3292 the call in a 'lambda form:
3295 (global-set-key [f18]
3296 (lambda () (interactive) (x-insert-selection t nil)))
3299 This binds the f18 key to a @dfn{generic} functional object. The
3300 interactive spec is required because only interactive functions can be
3303 For the FAQ example you could use:
3306 (global-set-key [(control ?.)]
3307 (lambda () (interactive) (scroll-up 1)))
3308 (global-set-key [(control ? ;)]
3309 (lambda () (interactive) (scroll-up -1)))
3312 This is fine if you only need a few functions within the lambda body.
3313 If you're doing more it's cleaner to define a separate function as in
3314 question 3.5.3 (@pxref{Q3.5.3}).
3316 @node Q3.5.2, Q3.5.3, Q3.5.1, Customization
3317 @unnumberedsubsec Q3.5.2: How can I stop down-arrow from adding empty lines to the bottom of my buffers?
3319 Add the following line to your @file{.emacs} file:
3322 (setq next-line-add-newlines nil)
3325 This has been the default setting in XEmacs for some time.
3327 @node Q3.5.3, Q3.5.4, Q3.5.2, Customization
3328 @unnumberedsubsec Q3.5.3: How do I bind C-. and C-; to scroll one line up and down?
3330 Add the following (Thanks to @email{mly@@adoc.xerox.com, Richard Mlynarik} and
3331 @email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}:
3334 (defun scroll-up-one-line ()
3338 (defun scroll-down-one-line ()
3342 (global-set-key [(control ?.)] 'scroll-up-one-line) ; C-.
3343 (global-set-key [(control ? ;)] 'scroll-down-one-line) ; C-;
3346 The key point is that you can only bind simple functions to keys; you
3347 can not bind a key to a function that you're also passing arguments to.
3348 (@pxref{Q3.5.1} for a better answer).
3350 @node Q3.5.4, Q3.5.5, Q3.5.3, Customization
3351 @unnumberedsubsec Q3.5.4: Globally binding @kbd{Delete}?
3353 I cannot manage to globally bind my @kbd{Delete} key to something other
3354 than the default. How does one do this?
3359 (message "You hit DELETE"))
3361 (global-set-key 'delete 'foo)
3364 However, some modes explicitly bind @kbd{Delete}, so you would need to
3365 add a hook that does @code{local-set-key} for them. If what you want to
3366 do is make the Backspace and Delete keys work more PC/Motif-like, then
3367 take a look at the @file{delbs.el} package.
3369 New in XEmacs 19.14 is a variable called @code{key-translation-map}
3370 which makes it easier to bind @kbd{Delete}. @file{delbs.el} is a
3371 good example of how to do this correctly.
3373 Also @xref{Q3.5.10}.
3375 @node Q3.5.5, Q3.5.6, Q3.5.4, Customization
3376 @unnumberedsubsec Q3.5.5: Scrolling one line at a time.
3378 Can the cursor keys scroll the screen a line at a time, rather than the
3379 default half page jump? I tend it to find it disorienting.
3384 (defun scroll-one-line-up (&optional arg)
3385 "Scroll the selected window up (forward in the text) one line (or N lines)."
3387 (scroll-up (or arg 1)))
3389 (defun scroll-one-line-down (&optional arg)
3390 "Scroll the selected window down (backward in the text) one line (or N)."
3392 (scroll-down (or arg 1)))
3394 (global-set-key [up] 'scroll-one-line-up)
3395 (global-set-key [down] 'scroll-one-line-down)
3398 The following will also work but will affect more than just the cursor
3399 keys (i.e. @kbd{C-n} and @kbd{C-p}):
3402 (setq scroll-step 1)
3405 Starting with XEmacs-20.3 you can also change this with Customize.
3406 Select from the @code{Options} menu
3407 @code{Customize->Emacs->Environment->Windows->Scroll Step...} or type
3408 @kbd{M-x customize @key{RET} windows @key{RET}}.
3410 @node Q3.5.6, Q3.5.7, Q3.5.5, Customization
3411 @unnumberedsubsec Q3.5.6: How to map @kbd{Help} key alone on Sun type4 keyboard?
3413 The following works in GNU Emacs 19:
3416 (global-set-key [help] 'help-command);; Help
3419 The following works in XEmacs 19.15 with the addition of shift:
3422 (global-set-key [(shift help)] 'help-command);; Help
3425 But it doesn't work alone. This is in the file @file{PROBLEMS} which
3426 should have come with your XEmacs installation: @emph{Emacs ignores the
3427 @kbd{help} key when running OLWM}.
3429 OLWM grabs the @kbd{help} key, and retransmits it to the appropriate
3434 @code{XSendEvent}. Allowing Emacs to react to synthetic
3435 events is a security hole, so this is turned off by default. You can
3436 enable it by setting the variable @code{x-allow-sendevents} to t. You
3437 can also cause fix this by telling OLWM to not grab the help key, with
3438 the null binding @code{OpenWindows.KeyboardCommand.Help:}.
3440 @node Q3.5.7, Q3.5.8, Q3.5.6, Customization
3441 @unnumberedsubsec Q3.5.7: How can you type in special characters in XEmacs?
3443 One way is to use the package @code{x-compose}. Then you can use
3444 sequences like @kbd{Compose " a} to get ä, etc.
3446 Another way is to use the @code{iso-insert} package, provided in XEmacs
3447 19.15 and later. Then you can use sequences like @kbd{C-x 8 " a} to get
3450 @email{glynn@@sensei.co.uk, Glynn Clements} writes:
3453 It depends upon your X server.
3455 Generally, the simplest way is to define a key as Multi_key with
3457 @c hey, show some respect, willya -- there's xkeycaps, isn't there? --
3460 xmodmap -e 'keycode 0xff20 = Multi_key'
3463 You will need to pick an appropriate keycode. Use xev to find out the
3464 keycodes for each key.
3466 [NB: On a `Windows' keyboard, recent versions of XFree86 automatically
3467 define the right `Windows' key as Multi_key'.]
3469 Once you have Multi_key defined, you can use e.g.
3478 Also, recent versions of XFree86 define various AltGr-<key>
3479 combinations as dead keys, i.e.
3481 AltGr [ => dead_diaeresis
3482 AltGr ] => dead_tilde
3483 AltGr ; => dead_acute
3487 Running @samp{xmodmap -pk} will list all of the defined keysyms.
3490 @node Q3.5.8, Q3.5.9, Q3.5.7, Customization
3491 @unnumberedsubsec Q3.5.8: Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
3493 Why does @code{(define-key global-map [ delete-forward ] 'delete-char)}
3494 complain of not being able to bind an unknown key?
3499 (define-key global-map [delete_forward] 'delete-char)
3504 What you are seeing above is a bug due to code that is trying to check
3505 for GNU Emacs syntax like:
3507 (define-key global-map [C-M-a] 'delete-char)
3509 which otherwise would cause no errors but would not result in the
3512 This bug has been fixed in 19.14.
3514 @node Q3.5.9, Q3.5.10, Q3.5.8, Customization
3515 @unnumberedsubsec Q3.5.9: How do I make the Delete key delete forward?
3517 With XEmacs-20.2 use the @code{delbs} package:
3523 This will give you the functions @code{delbs-enable-delete-forward} to
3524 set things up, and @code{delbs-disable-delete-forward} to revert to
3525 ``normal'' behavior. Note that @code{delbackspace} package is obsolete.
3527 Starting with XEmacs-20.3 better solution is to set variable
3528 @code{delete-key-deletes-forward} to t. You can also change this with
3529 Customize. Select from the @code{Options} menu
3530 @code{Customize->Emacs->Editing->Basics->Delete Key Deletes Forward} or
3531 type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
3535 @node Q3.5.10, Q3.5.11, Q3.5.9, Customization
3536 @unnumberedsubsec Q3.5.10: Can I turn on @dfn{sticky} modifier keys?
3538 Yes, with @code{(setq modifier-keys-are-sticky t)}. This will give the
3539 effect of being able to press and release Shift and have the next
3540 character typed come out in upper case. This will affect all the other
3541 modifier keys like Control and Meta as well.
3543 @email{ben@@666.com, Ben Wing} writes:
3546 One thing about the sticky modifiers is that if you move the mouse out
3547 of the frame and back in, it cancels all currently ``stuck'' modifiers.
3550 @node Q3.5.11, Q3.6.1, Q3.5.10, Customization
3551 @unnumberedsubsec Q3.5.11: How do I map the arrow keys?
3553 Say you want to map @kbd{C-@key{right}} to forward-word:
3555 @email{sds@@usa.net, Sam Steingold} writes:
3559 ; both XEmacs and Emacs
3560 (define-key global-map [(control right)] 'forward-word)
3565 (define-key global-map [C-right] 'forward-word)
3570 (define-key global-map (kbd "C-<right>") 'forward-word)
3576 @node Q3.6.1, Q3.6.2, Q3.5.11, Customization
3577 @unnumberedsec 3.6: The Cursor
3578 @unnumberedsubsec Q3.6.1: Is there a way to make the bar cursor thicker?
3580 I'd like to have the bar cursor a little thicker, as I tend to "lose" it
3583 For a 1 pixel bar cursor, use:
3589 For a 2 pixel bar cursor, use:
3592 (setq bar-cursor 'anything-else)
3595 Starting with XEmacs-20.3 you can also change these with Customize.
3596 Select from the @code{Options} menu
3597 @code{Customize->Emacs->Environment->Display->Bar Cursor...} or type
3598 @kbd{M-x customize @key{RET} display @key{RET}}.
3600 You can use a color to make it stand out better:
3603 Emacs*cursorColor: Red
3606 @node Q3.6.2, Q3.6.3, Q3.6.1, Customization
3607 @unnumberedsubsec Q3.6.2: Is there a way to get back the block cursor?
3610 (setq bar-cursor nil)
3613 Starting with XEmacs-20.3 you can also change this with Customize.
3614 Select from the @code{Options} menu
3615 @code{Customize->Emacs->Environment->Display->Bar Cursor...} or type
3616 @kbd{M-x customize @key{RET} display @key{RET}}.
3618 @node Q3.6.3, Q3.7.1, Q3.6.2, Customization
3619 @unnumberedsubsec Q3.6.3: Can I make the cursor blink?
3621 If you are running a version of XEmacs older than 19.14, no. Otherwise
3622 you can do the following:
3628 This function toggles between a steady cursor and a blinking cursor.
3629 You may also set this mode from the menu bar by selecting @samp{Options
3630 => Frame Appearance => Blinking Cursor}. Remember to save options.
3632 @node Q3.7.1, Q3.7.2, Q3.6.3, Customization
3633 @unnumberedsec 3.7: The Mouse and Highlighting
3634 @unnumberedsubsec Q3.7.1: How can I turn off Mouse pasting?
3636 I keep hitting the middle mouse button by accident and getting stuff
3637 pasted into my buffer so how can I turn this off?
3639 Here is an alternative binding, whereby the middle mouse button selects
3640 (but does not cut) the expression under the mouse. Clicking middle on a
3641 left or right paren will select to the matching one. Note that you can
3642 use @code{define-key} or @code{global-set-key}.
3645 (defun mouse-set-point-and-select (event)
3646 "Sets the point at the mouse location, then marks following form"
3648 (mouse-set-point event)
3650 (define-key global-map [button2] 'mouse-set-point-and-select)
3653 @node Q3.7.2, Q3.7.3, Q3.7.1, Customization
3654 @unnumberedsubsec Q3.7.2: How do I set control/meta/etc modifiers on mouse buttons?
3656 Use, for instance, @code{[(meta button1)]}. For example, here is a common
3657 setting for Common Lisp programmers who use the bundled @code{ilisp}
3658 package, whereby meta-button1 on a function name will find the file where
3659 the function name was defined, and put you at that location in the source
3662 [Inside a function that gets called by the lisp-mode-hook and
3666 (local-set-key [(meta button1)] 'edit-definitions-lisp)
3669 @node Q3.7.3, Q3.7.4, Q3.7.2, Customization
3670 @unnumberedsubsec Q3.7.3: Clicking the left button does not do anything in buffer list.
3672 I do @kbd{C-x C-b} to get a list of buffers and the entries get
3673 highlighted when I move the mouse over them but clicking the left mouse
3674 does not do anything.
3676 Use the middle mouse button.
3678 @node Q3.7.4, Q3.7.5, Q3.7.3, Customization
3679 @unnumberedsubsec Q3.7.4: How can I get a list of buffers when I hit mouse button 3?
3681 The following code will replace the default popup on button3:
3684 (global-set-key [button3] 'popup-buffer-menu)
3687 @node Q3.7.5, Q3.7.6, Q3.7.4, Customization
3688 @unnumberedsubsec Q3.7.5: Why does cut-and-paste not work between XEmacs and a cmdtool?
3690 We don't know. It's a bug. There does seem to be a work-around,
3691 however. Try running xclipboard first. It appears to fix the problem
3692 even if you exit it. (This should be mostly fixed in 19.13, but we
3693 haven't yet verified that).
3695 @node Q3.7.6, Q3.7.7, Q3.7.5, Customization
3696 @unnumberedsubsec Q3.7.6: How I can set XEmacs up so that it pastes where the text cursor is?
3698 By default XEmacs pastes X selections where the mouse pointer is. How
3701 Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank
3704 To get XEmacs to paste at the text cursor, add this your @file{.emacs}:
3707 (setq mouse-yank-at-point t)
3710 Starting with XEmacs-20.2 you can also change this with Customize.
3711 Select from the @code{Options} menu
3712 @code{Customize->Emacs->Editing->Mouse->Yank At Point...} or type
3713 @kbd{M-x customize @key{RET} mouse @key{RET}}.
3715 @node Q3.7.7, Q3.7.8, Q3.7.6, Customization
3716 @unnumberedsubsec Q3.7.7: How do I select a rectangular region?
3718 Just select the region normally, then use the rectangle commands (e.g.
3719 @code{kill-rectangle} on it. The region does not highlight as a
3720 rectangle, but the commands work just fine.
3722 To actually sweep out rectangular regions with the mouse you can use
3723 @code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}.
3724 Then use rectangle commands.
3726 You can also do the following to change default behavior to sweep out
3727 rectangular regions:
3730 (setq mouse-track-rectangle-p t)
3733 Starting with XEmacs-20.2 you can also change this with Customize.
3734 Select from the @code{Options} menu
3735 @code{Customize->Emacs->Editing->Mouse->Track Rectangle...} or type
3736 @kbd{M-x customize @key{RET} mouse @key{RET}}.
3740 mouse-track-do-rectangle: (event)
3741 -- an interactive compiled Lisp function.
3742 Like `mouse-track' but selects rectangles instead of regions.
3745 @node Q3.7.8, Q3.8.1, Q3.7.7, Customization
3746 @unnumberedsubsec Q3.7.8: Why does @kbd{M-w} take so long?
3748 It actually doesn't. It leaves the region visible for a second so that
3749 you can see what area is being yanked. If you start working, though, it
3750 will immediately complete its operation. In other words, it will only
3751 delay for a second if you let it.
3753 @node Q3.8.1, Q3.8.2, Q3.7.8, Customization
3754 @unnumberedsec 3.8: The Menubar and Toolbar
3755 @unnumberedsubsec Q3.8.1: How do I get rid of the menu (or menubar)?
3757 If you are running XEmacs 19.13 and earlier, add this command to your
3764 Starting with XEmacs 19.14 the preferred method is:
3767 (set-specifier menubar-visible-p nil)
3770 @node Q3.8.2, Q3.8.3, Q3.8.1, Customization
3771 @unnumberedsubsec Q3.8.2: Can I customize the basic menubar?
3773 For an extensive menubar, add this line to your @file{.emacs}:
3776 (load "big-menubar")
3779 If you'd like to write your own, this file provides as good a set of
3780 examples as any to start from. The file is located in
3781 @file{lisp/packages/big-menubar.el} in the XEmacs installation
3784 @node Q3.8.3, Q3.8.4, Q3.8.2, Customization
3785 @unnumberedsubsec Q3.8.3: How do I control how many buffers are listed in the menu @code{Buffers List}?
3787 Add the following to your @file{.emacs} (suit to fit):
3790 (setq buffers-menu-max-size 20)
3793 For no limit, use an argument of @samp{nil}.
3795 Starting with XEmacs-20.3 you can also change this with Customize.
3796 Select from the @code{Options} menu
3797 @code{Customize->Emacs->Environment->Menu->Buffers Menu->Max Size...} or
3798 type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}.
3800 @node Q3.8.4, Q3.8.5, Q3.8.3, Customization
3801 @unnumberedsubsec Q3.8.4: Resources like @code{Emacs*menubar*font} are not working?
3803 I am trying to use a resource like @code{Emacs*menubar*font} to set the
3804 font of the menubar but it's not working.
3806 If you are using the real Motif menubar, this resource is not
3807 recognized; you have to say:
3810 Emacs*menubar*fontList: FONT
3813 If you are using the Lucid menubar, the former resource will be
3814 recognized only if the latter resource is unset. This means that the
3824 Emacs*menubar*font: FONT
3827 even though the latter is more specific.
3829 @node Q3.8.5, Q3.9.1, Q3.8.4, Customization
3830 @unnumberedsubsec Q3.8.5: How can I bind a key to a function to toggle the toolbar?
3835 (defun my-toggle-toolbar ()
3837 (set-specifier default-toolbar-visible-p
3838 (not (specifier-instance default-toolbar-visible-p))))
3839 (global-set-key "\C-xT" 'my-toggle-toolbar)
3842 There are redisplay bugs in 19.14 that may make the preceding result in
3843 a messed-up display, especially for frames with multiple windows. You
3844 may need to resize the frame before XEmacs completely realizes the
3845 toolbar is really gone.
3847 Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct
3850 @node Q3.9.1, Q3.9.2, Q3.8.5, Customization
3851 @unnumberedsec 3.9: Scrollbars
3852 @unnumberedsubsec Q3.9.1: How can I disable the scrollbar?
3854 To disable them for all frames, add the following line to
3855 your @file{.Xdefaults}:
3858 Emacs.scrollBarWidth: 0
3861 Or select from the @code{Options} menu @code{Frame Appearance->Scrollbars}.
3862 Remember to save options.
3864 To turn the scrollbar off on a per-frame basis, use the following
3868 (set-specifier scrollbar-width 0 (selected-frame))
3871 You can actually turn the scrollbars on at any level you want by
3872 substituting for (selected-frame) in the above command. For example, to
3873 turn the scrollbars off only in a single buffer:
3876 (set-specifier scrollbar-width 0 (current-buffer))
3879 In XEmacs versions prior to 19.14, you had to use the hairier construct:
3882 (set-specifier scrollbar-width (cons (selected-frame) 0))
3885 @node Q3.9.2, Q3.9.3, Q3.9.1, Customization
3886 @unnumberedsubsec Q3.9.2: How can one use resources to change scrollbar colors?
3888 Here's a recap of how to use resources to change your scrollbar colors:
3893 Emacs*XmScrollBar.Background: skyblue
3894 Emacs*XmScrollBar.troughColor: lightgray
3898 Emacs*Scrollbar.Foreground: skyblue
3899 Emacs*Scrollbar.Background: lightgray
3902 Note the capitalization of @code{Scrollbar} for the Athena widget.
3904 @node Q3.9.3, Q3.9.4, Q3.9.2, Customization
3905 @unnumberedsubsec Q3.9.3: Moving the scrollbar can move the point; can I disable this?
3907 When I move the scrollbar in an XEmacs window, it moves the point as
3908 well, which should not be the default behavior. Is this a bug or a
3909 feature? Can I disable it?
3911 The current behavior is a feature, not a bug. Point remains at the same
3912 buffer position as long as that position does not scroll off the screen.
3913 In that event, point will end up in either the upper-left or lower-left
3916 This cannot be changed.
3918 @node Q3.9.4, Q3.10.1, Q3.9.3, Customization
3919 @unnumberedsubsec Q3.9.4: How can I get automatic horizontal scrolling?
3921 By the same token, how can I turn it off in specific modes?
3923 To do this, add to your @file{.emacs} file:
3926 (require 'auto-show)
3929 Then do @code{(setq truncate-lines t)} in the mode-hooks for any modes
3930 in which you want lines truncated.
3932 More precisely: If @code{truncate-lines} is nil, horizontal scrollbars
3933 will never appear. Otherwise, they will appear only if the value of
3934 @code{scrollbar-height} for that buffer/window/etc. is non-zero. If you
3938 (set-specifier scrollbar-height 0)
3941 then horizontal scrollbars will not appear in truncated buffers unless
3942 the package specifically asked for them.
3944 Automatic horizontal scrolling is now standard, starting with 19.14.
3946 @node Q3.10.1, Q3.10.2, Q3.9.4, Customization
3947 @unnumberedsec 3.10: Text Selections
3948 @unnumberedsubsec Q3.10.1: How can I turn off or change highlighted selections?
3950 The @code{zmacs} mode allows for what some might call gratuitous
3951 highlighting for selected regions (either by setting mark or by using
3952 the mouse). This is the default behavior. To turn off, add the
3953 following line to your @file{.emacs} file:
3956 (setq zmacs-regions nil)
3959 Starting with XEmacs-20.2 you can also change this with Customize. Select
3960 from the @code{Options} menu @code{Customize->Emacs->Editing->Basics->Zmacs
3961 Regions} or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
3963 To change the face for selection, look at @code{Options->Customize} on
3966 @node Q3.10.2, Q3.10.3, Q3.10.1, Customization
3967 @unnumberedsubsec Q3.10.2: How do I get that typing on an active region removes it?
3969 I want to change things so that if I select some text and start typing,
3970 the typed text replaces the selected text, similar to Motif.
3972 You want to use something called @dfn{pending delete}. Pending delete
3973 is what happens when you select a region (with the mouse or keyboard)
3974 and you press a key to replace the selected region by the key you typed.
3975 Usually backspace kills the selected region.
3977 To get this behavior, add the following line to your @file{.emacs}:
3980 (turn-on-pending-delete)
3983 Note that this will work with both Backspace and Delete.
3985 @node Q3.10.3, Q3.10.4, Q3.10.2, Customization
3986 @unnumberedsubsec Q3.10.3: Can I turn off the highlight during isearch?
3988 I do not like my text highlighted while I am doing isearch as I am not
3989 able to see what's underneath. How do I turn it off?
3991 Put the following in your @file{.emacs}:
3994 (setq isearch-highlight nil)
3997 Starting with XEmacs-20.2 you can also change this with Customize. Type
3998 @kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}.
4000 Note also that isearch-highlight affects query-replace and ispell.
4001 Instead of disabling isearch-highlight you may find that a better
4002 solution consists of customizing the @code{isearch} face.
4004 @node Q3.10.4, Q3.10.5, Q3.10.3, Customization
4005 @unnumberedsubsec Q3.10.4: How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
4007 Put this in your @code{.emacs}:
4010 (setq zmacs-regions nil)
4013 @strong{Warning: This command turns off all region highlighting.}
4015 Also @xref{Q3.10.1}.
4017 @node Q3.10.5, , Q3.10.4, Customization
4018 @unnumberedsubsec Q3.10.5: The region disappears when I hit the end of buffer while scrolling.
4020 This has been fixed by default starting with XEmacs-20.3.
4022 With older versions you can turn this feature (if it indeed is a feature)
4026 (defadvice scroll-up (around scroll-up freeze)
4028 (let ((zmacs-region-stays t))
4032 (end-of-buffer (goto-char (point-max))))
4035 (defadvice scroll-down (around scroll-down freeze)
4037 (let ((zmacs-region-stays t))
4041 (beginning-of-buffer (goto-char (point-min))))
4045 Thanks to @email{raman@@adobe.com, T. V. Raman} for assistance in deriving this
4048 @node Subsystems, Miscellaneous, Customization, Top
4049 @unnumbered 4 Major Subsystems
4051 This is part 4 of the XEmacs Frequently Asked Questions list. This
4052 section is devoted to major XEmacs subsystems.
4055 Reading Mail with VM:
4056 * Q4.0.1:: How do I set up VM to retrieve remote mail using POP?
4057 * Q4.0.2:: How do I get VM to filter mail for me?
4058 * Q4.0.3:: How can I get VM to automatically check for new mail?
4059 * Q4.0.4:: [This question intentionally left blank]
4060 * Q4.0.5:: How do I get my outgoing mail archived?
4061 * 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"?
4062 * Q4.0.7:: Is there a mailing list or FAQ for VM?
4063 * Q4.0.8:: Remote mail reading with VM.
4064 * Q4.0.9:: rmail or VM gets an error incorporating new mail.
4065 * Q4.0.10:: How do I make VM stay in a single frame?
4066 * Q4.0.11:: How do I make VM or mh-e display graphical smilies?
4067 * Q4.0.12:: Customization of VM not covered in the manual or here.
4069 Web browsing with W3:
4070 * Q4.1.1:: What is W3?
4071 * Q4.1.2:: How do I run W3 from behind a firewall?
4072 * Q4.1.3:: Is it true that W3 supports style sheets and tables?
4074 Reading Netnews and Mail with Gnus:
4075 * Q4.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus,argh!
4076 * Q4.2.2:: [This question intentionally left blank]
4077 * Q4.2.3:: How do I make Gnus stay within a single frame?
4078 * Q4.2.4:: How do I customize the From: line?
4081 * Q4.3.1:: How can I read and/or compose MIME messages?
4082 * Q4.3.2:: What is TM and where do I get it?
4083 * Q4.3.3:: Why isn't this @code{movemail} program working?
4084 * Q4.3.4:: Movemail is also distributed by Netscape? Can that cause problems?
4085 * Q4.3.5:: Where do I find pstogif (required by tm)?
4087 Sparcworks, EOS, and WorkShop:
4088 * Q4.4.1:: What is SPARCworks, EOS, and WorkShop
4091 * Q4.5.1:: What is/was Energize?
4094 * Q4.6.1:: What is Infodock?
4096 Other Unbundled Packages:
4097 * Q4.7.1:: What is AUC TeX? Where do you get it?
4098 * Q4.7.2:: Are there any Emacs Lisp Spreadsheets?
4099 * Q4.7.3:: Byte compiling AUC TeX on XEmacs 19.14
4100 * Q4.7.4:: Problems installing AUC TeX
4101 * Q4.7.5:: Is there a reason for an Emacs package not to be included in XEmacs?
4102 * Q4.7.6:: Is there a MatLab mode?
4105 @node Q4.0.1, Q4.0.2, Subsystems, Subsystems
4106 @unnumberedsec 4.0: Reading Mail with VM
4107 @unnumberedsubsec Q4.0.1: How do I set up VM to retrieve mail from a remote site using POP?
4109 Use @code{vm-spool-files}, like this for example:
4112 (setq vm-spool-files '("/var/spool/mail/wing"
4113 "netcom23.netcom.com:110:pass:wing:MYPASS"))
4116 Of course substitute your actual password for MYPASS.
4118 @node Q4.0.2, Q4.0.3, Q4.0.1, Subsystems
4119 @unnumberedsubsec Q4.0.2: How do I get VM to filter mail for me?
4121 One possibility is to use procmail to split your mail before it gets to
4122 VM. I prefer this personally, since there are many strange and
4123 wonderful things one can do with procmail. Procmail may be found at
4124 @uref{ftp://ftp.informatik.rwth-aachen.de/pub/packages/procmail/}.
4126 Also see the Mail Filtering FAQ at:
4130 @uref{ftp://rtfm.mit.edu/pub/usenet/news.answers/mail/filtering-faq}.
4132 @c <URL:http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html>
4135 @node Q4.0.3, Q4.0.4, Q4.0.2, Subsystems
4136 @unnumberedsubsec Q4.0.3: How can I get VM to automatically check for new mail?
4138 @email{turner@@lanl.gov, John Turner} writes:
4144 (setq vm-auto-get-new-mail 60)
4148 @node Q4.0.4, Q4.0.5, Q4.0.3, Subsystems
4149 @unnumberedsubsec Q4.0.4: [This question intentionally left blank]
4151 Obsolete question, left blank to avoid renumbering.
4153 @node Q4.0.5, Q4.0.6, Q4.0.4, Subsystems
4154 @unnumberedsubsec Q4.0.5: How do I get my outgoing mail archived?
4157 (setq mail-archive-file-name "~/outbox")
4160 @node Q4.0.6, Q4.0.7, Q4.0.5, Subsystems
4161 @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"?
4163 Set @code{vm-reply-ignored-addresses} to a list, like
4166 (setq vm-reply-ignored-addresses
4167 '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com"
4168 "wing@@netcom.com" "wing@@666.com"))
4171 Note that each string is a regular expression.
4173 @node Q4.0.7, Q4.0.8, Q4.0.6, Subsystems
4174 @unnumberedsubsec Q4.0.7: Is there a mailing list or FAQ for VM?
4176 A FAQ for VM exists at @uref{http://www.cyberpass.net/~gorkab/vmfaq.htm}.
4178 VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug.
4180 @node Q4.0.8, Q4.0.9, Q4.0.7, Subsystems
4181 @unnumberedsubsec Q4.0.8: Remote mail reading with VM.
4183 My mailbox lives at the office on a big honkin server. My regular INBOX
4184 lives on my honkin desktop machine. I now can PPP to the office from
4185 home which is far from honking... I'd like to be able to read mail at
4186 home without storing it here and I'd like to use xemacs and VM at
4187 home... Is there a recommended setup?
4189 @email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes:
4192 There are several ways to do this.
4196 Set your display to your home machine and run dxpc or one of the other X
4200 NFS mount your desktop machine on your home machine and modify your pop
4201 command on your home machine to rsh to your desktop machine and actually
4205 Run a POP server on your desktop machine as well and do a sort of two
4210 @email{wmperry@@monolith.spry.com, William Perry} adds:
4213 Or you could run a pop script periodically on your desktop machine, and
4214 just use ange-ftp or NFS to get to your mailbox. I used to do this all
4215 the time back at IU.
4218 @node Q4.0.9, Q4.0.10, Q4.0.8, Subsystems
4219 @unnumberedsubsec Q4.0.9: rmail or VM gets an error incorporating new mail.
4221 Quoting the XEmacs PROBLEMS file:
4224 rmail and VM get new mail from @file{/usr/spool/mail/$USER} using a
4225 program called @code{movemail}. This program interlocks with
4226 @code{/bin/mail} using the protocol defined by @code{/bin/mail}.
4228 There are two different protocols in general use. One of them uses the
4229 @code{flock} system call. The other involves creating a lock file;
4230 @code{movemail} must be able to write in @file{/usr/spool/mail} in order
4231 to do this. You control which one is used by defining, or not defining,
4232 the macro @code{MAIL_USE_FLOCK} in @file{config.h} or the m- or s- file
4235 @strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
4236 SYSTEM, YOU CAN LOSE MAIL!}
4238 If your system uses the lock file protocol, and fascist restrictions
4239 prevent ordinary users from writing the lock files in
4240 @file{/usr/spool/mail}, you may need to make @code{movemail} setgid to a
4241 suitable group such as @samp{mail}. You can use these commands (as
4249 If your system uses the lock file protocol, and fascist restrictions
4250 prevent ordinary users from writing the lock files in
4251 @file{/usr/spool/mail}, you may need to make @code{movemail} setgid to a
4252 suitable group such as @code{mail}. To do this, use the following
4253 commands (as root) after doing the make install.
4260 Installation normally copies movemail from the build directory to an
4261 installation directory which is usually under @file{/usr/local/lib}.
4262 The installed copy of @code{movemail} is usually in the directory
4263 @file{/usr/local/lib/emacs/VERSION/TARGET}. You must change the group
4264 and mode of the installed copy; changing the group and mode of the build
4265 directory copy is ineffective.
4268 @node Q4.0.10, Q4.0.11, Q4.0.9, Subsystems
4269 @unnumberedsubsec Q4.0.10: How do I make VM stay in a single frame?
4271 John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes:
4275 ; Don't use multiple frames
4276 (setq vm-frame-per-composition nil)
4277 (setq vm-frame-per-folder nil)
4278 (setq vm-frame-per-edit nil)
4279 (setq vm-frame-per-summary nil)
4283 @node Q4.0.11, Q4.0.12, Q4.0.10, Subsystems
4284 @unnumberedsubsec Q4.0.11: How do I make VM or mh-e display graphical smilies?
4286 For mh-e use the following:
4289 (add-hook 'mh-show-mode-hook '(lambda ()
4290 (smiley-region (point-min)
4294 @email{bill@@carpenter.ORG, WJCarpenter} writes:
4295 For VM use the following:
4297 (autoload 'smiley-region "smiley" nil t)
4298 (add-hook 'vm-select-message-hook
4300 (smiley-region (point-min)
4304 For tm use the following:
4306 (autoload 'smiley-buffer "smiley" nil t)
4307 (add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer)
4310 @node Q4.0.12, Q4.1.1, Q4.0.11, Subsystems
4311 @unnumberedsubsec Q4.0.12: Customization of VM not covered in the manual, or here.
4313 @email{boffi@@hp735.stru.polimi.it, giacomo boffi} writes:
4316 The meta-answer is to look into the file @file{vm-vars.el}, in the vm
4317 directory of the lisp library.
4319 @file{vm-vars.el} contains, initializes and carefully describes, with
4320 examples of usage, the plethora of user options that @emph{fully}
4321 control VM's behavior.
4323 Enter vm-vars, @code{forward-search} for toolbar, find the variables
4324 that control the toolbar placement, appearance, existence, copy to your
4325 @file{.emacs} or @file{.vm} and modify according to the detailed
4328 The above also applies to all the various features of VM: search for
4329 some keywords, maybe the first you conjure isn't appropriate, find the
4330 appropriate variables, copy and experiment.
4333 @node Q4.1.1, Q4.1.2, Q4.0.12, Subsystems
4334 @unnumberedsec 4.1: Web browsing with W3
4335 @unnumberedsubsec Q4.1.1: What is W3?
4337 W3 is an advanced graphical browser written in Emacs lisp that runs on
4338 XEmacs. It has full support for cascaded style sheets, and more...
4340 It has a home web page at
4341 @uref{http://www.cs.indiana.edu/elisp/w3/docs.html}.
4343 @node Q4.1.2, Q4.1.3, Q4.1.1, Subsystems
4344 @unnumberedsubsec Q4.1.2: How do I run W3 from behind a firewall?
4346 There is a long, well-written, detailed section in the W3 manual that
4347 describes how to do this. Look in the section entitled "Firewalls".
4349 @node Q4.1.3, Q4.2.1, Q4.1.2, Subsystems
4350 @unnumberedsubsec Q4.1.3: Is it true that W3 supports style sheets and tables?
4352 Yes, and much more. W3, as distributed with the latest XEmacs is a
4353 full-featured web browser.
4355 @node Q4.2.1, Q4.2.2, Q4.1.3, Subsystems
4356 @unnumberedsec 4.2: Reading Netnews and Mail with Gnus
4357 @unnumberedsubsec Q4.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
4359 The Gnus numbering issues are not meant for mere mortals to know them.
4360 If you feel you @emph{must} enter the muddy waters of Gnus, visit the
4361 excellent FAQ, maintained by Justin Sheehy, at:
4364 @uref{http://www.ccs.neu.edu/software/contrib/gnus/}
4367 See also Gnus home page
4369 @uref{http://www.gnus.org/}
4372 @node Q4.2.2, Q4.2.3, Q4.2.1, Subsystems
4373 @unnumberedsubsec Q4.2.2: This question intentionally left blank.
4375 Obsolete question, left blank to avoid renumbering.
4377 @node Q4.2.3, Q4.2.4, Q4.2.2, Subsystems
4378 @unnumberedsubsec Q4.2.3: How do I make Gnus stay within a single frame?
4380 The toolbar code to start Gnus opens the new frame---and it's a feature
4381 rather than a bug. If you don't like it, but would still like to click
4382 on the seemly icon, use the following code:
4385 (defun toolbar-news ()
4389 It will redefine the callback function of the icon to just call
4390 @code{gnus}, without all the fancy frame stuff.
4392 @node Q4.2.4, Q4.3.1, Q4.2.3, Subsystems
4393 @unnumberedsubsec Q4.2.4: How do I customize the From: line?
4395 How do I change the @code{From:} line? I have set gnus-user-from-line
4398 Gail Gurman <gail.gurman@@sybase.com>
4400 @noindent , but XEmacs Gnus doesn't use
4403 Gail Mara Gurman @email{gailg@@deall}
4405 @noindent and then complains
4406 that it's incorrect. Also, as you perhaps can see, my Message-ID is
4407 screwy. How can I change that?
4409 @email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes:
4412 Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or
4413 @code{mail-host-address} to @samp{sybase.com}.
4416 @node Q4.3.1, Q4.3.2, Q4.2.4, Subsystems
4417 @unnumberedsec 4.3: Other Mail & News
4418 @unnumberedsubsec Q4.3.1: How can I read and/or compose MIME messages?
4421 VM supports MIME natively.
4423 You probably want to use the Tools for MIME (tm). @xref{Q4.3.2}, for
4426 @email{trey@@cs.berkeley.edu, Trey Jackson} has an Emacs & MIME web page at
4430 @uref{http://bmrc.berkeley.edu/~trey/emacs/mime.html}.
4433 Another possibility is RMIME. You may find RMIME at
4437 @uref{http://www.cinti.net/~rmoody/rmime/index.html}.
4440 @node Q4.3.2, Q4.3.3, Q4.3.1, Subsystems
4441 @unnumberedsubsec Q4.3.2: What is TM and where do I get it?
4443 TM stands for @dfn{Tools for MIME} and not Tiny MIME. TM integrates
4444 with all major XEmacs packages like Gnus (all flavors), VM, MH-E, and
4445 mailcrypt. It provides totally transparent and trouble-free MIME
4446 support. When appropriate a message will be decoded in place in an
4449 TM now comes as a package with XEmacs 19.16 and XEmacs 20.2.
4451 TM was written by @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} and
4452 @email{shuhei-k@@jaist.ac.jp, KOBAYASHI
4455 It is based on the work of @email{umerin@@mse.kyutech.ac.jp, UMEDA
4456 Masanobu}, the original writer of GNUS.
4458 The following information is from the @file{README}:
4460 @dfn{tm} is a MIME package for GNU Emacs.
4461 tm has following functions:
4464 @item MIME style multilingual header.
4465 @item MIME message viewer (mime/viewer-mode).
4466 @item MIME message composer (mime/editor-mode).
4467 @item MIME extenders for mh-e, GNUS, RMAIL and VM.
4470 tm is available from following anonymous ftp sites:
4472 @item @uref{ftp://ftp.jaist.ac.jp/pub/GNU/elisp/mime/} (Japan).
4473 @item @uref{ftp://ftp.nis.co.jp/pub/gnu/emacs-lisp/tm/} (Japan).
4474 @c The host above is unknown.
4476 @item @uref{ftp://ftp.nisiq.net/pub/gnu/emacs-lisp/tm/} (US).
4477 @item @uref{ftp://ftp.miranova.com/pub/gnus/jaist.ac.jp/} (US).
4478 @item @uref{ftp://ftp.unicamp.br/pub/mail/mime/tm/} (Brasil).
4479 @item @uref{ftp://ftp.th-darmstadt.de/pub/editors/GNU-Emacs/lisp/mime/} (Germany).
4480 @item @uref{ftp://ftp.tnt.uni-hannover.de/pub/editors/xemacs/contrib/} (Germany).
4483 Don't let the installation procedure & instructions stop you from trying
4484 this package out---it's much simpler than it looks, and once installed,
4487 @node Q4.3.3, Q4.3.4, Q4.3.2, Subsystems
4488 @unnumberedsubsec Q4.3.3: Why isn't this @code{movemail} program working?
4490 Ben Wing @email{ben@@666.com} writes:
4493 It wasn't chown'ed/chmod'd correctly.
4496 @node Q4.3.4, Q4.3.5, Q4.3.3, Subsystems
4497 @unnumberedsubsec Q4.3.4: Movemail is also distributed by Netscape? Can that cause problems?
4499 @email{steve@@altair.xemacs.org, Steve Baur} writes:
4502 Yes. Always use the movemail installed with your XEmacs. Failure to do
4503 so can result in lost mail.
4506 Please refer to @email{jwz@@netscape.com, Jamie Zawinski's} notes at
4510 @uref{http://home.netscape.com/eng/mozilla/2.0/relnotes/demo/movemail.html}.
4511 In particular, this document will show you how to make Netscape use the
4512 version of movemail configured for your system by the person who built
4515 @node Q4.3.5, Q4.4.1, Q4.3.4, Subsystems
4516 @unnumberedsubsec Q4.3.5: Where do I find pstogif (required by tm)?
4518 pstogif is part of the latex2html package.
4520 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
4522 latex2html is best found at the CTAN hosts and their mirrors
4527 @file{tex-archive/support/latex2html}.
4532 @item @uref{ftp://ftp.tex.ac.uk/tex-archive/support/latex2html/}.
4533 @item @uref{ftp://ftp.dante.de/tex-archive/support/latex2html/}.
4536 There is a good mirror at ftp.cdrom.com;
4540 @uref{ftp://ftp.cdrom.com/pub/tex/ctan/support/latex2html/}.
4542 @node Q4.4.1, Q4.5.1, Q4.3.5, Subsystems
4543 @unnumberedsec 4.4: Sparcworks, EOS, and WorkShop
4544 @unnumberedsubsec Q4.4.1: What is SPARCworks, EOS, and WorkShop?
4546 @email{turner@@lanl.gov, John Turner} writes:
4549 SPARCworks is SunSoft's development environment, comprising compilers
4550 (C, C++, FORTRAN 77, Fortran 90, Ada, and Pascal), a debugger, and other
4551 tools such as TeamWare (for configuration management), MakeTool, etc.
4554 See @uref{http://www.sun.com/software/Developer-products/}
4557 EOS stands for "Era on SPARCworks", but I don't know what Era stands
4560 EOS is the integration of XEmacs with the SPARCworks debugger. It
4561 allows one to use an XEmacs frame to view code (complete with
4562 fontification, etc.), set breakpoints, print variables, etc., while
4563 using the SPARCworks debugger. It works very well and I use it all the
4566 @email{cthomp@@xemacs.org, Chuck Thompson} writes:
4569 Era stood for "Emacs Rewritten Again". It was what we were calling the
4570 modified version of Lucid Emacs for Sun when I was dragged, er, allowed
4571 to work on this wonderful editor.
4574 @email{martin@@xemacs.org, Martin Buchholz} writes:
4577 EOS is being replaced with a new graphical development environment
4578 called Sun WorkShop, which is currently (07/96) in Alpha Test. For more
4583 @uref{http://www.sun.com/software/Products/Developer-products/programs.html}.
4586 @node Q4.5.1, Q4.6.1, Q4.4.1, Subsystems
4587 @unnumberedsec 4.5: Energize
4588 @unnumberedsubsec Q4.5.1: What is/was Energize?
4590 @email{gray@@meteor.harlequin.com, David N Gray} writes:
4592 The files in @file{lisp/energize} are to enable Emacs to interface with
4593 the "Energize Programming System", a C and C++ development environment,
4594 which was a product of Lucid, Inc. Tragically, Lucid went out of
4595 business in 1994, so although Energize is still a great system, if you
4596 don't already have it, there isn't any way to get it now. (Unless you
4597 happen to be in Japan; INS Engineering may still be selling it there.
4598 Tartan bought the rights to sell it in the rest of the world, but never
4602 @node Q4.6.1, Q4.7.1, Q4.5.1, Subsystems
4603 @unnumberedsec 4.6: Infodock
4604 @unnumberedsubsec Q4.6.1: What is Infodock?
4606 InfoDock is an integrated productivity toolset, mainly aimed at
4607 technical people. It is developed and supported by InfoDock
4608 Associates, a firm that offers custom support and development
4609 for InfoDock, XEmacs and GNU Emacs. ( @uref{http://www.infodock.com},
4610 @email{info@@infodock.com}, +1 408 243 3300).
4612 InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of
4613 the power of Emacs, but with an easier to use and more comprehensive
4614 menu-based user interface. The bottom portion of this text describes
4615 how it differs from XEmacs and GNU Emacs from the Free Software
4618 InfoDock is aimed at people who want a free, turn-key productivity
4619 environment. Although InfoDock is customizable, it is not intended for
4620 people who like basic versions of Emacs which need to be customized
4621 extensively for local use; standard Emacs distributions are better for
4622 such uses. InfoDock is for those people who want a complete,
4623 pre-customized environment in one package, which they need not touch
4624 more than once or twice a year to update to new revisions.
4626 InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX,
4627 and Intel Linux systems. It is intended for use on a color display,
4628 although most features will work on monochrome monitors. Simply unpack
4629 InfoDock according to the instructions in the ID-INSTALL file and you
4632 The InfoDock Manual is concise, yet sufficient as a user guide for users
4633 who have never used an Emacs-type editor before. For users who are
4634 already familiar with Emacs, it supplements the information in the GNU
4637 InfoDock menus are much more extensive and more mature than standard
4638 Emacs menus. Each menu offers a @samp{Manual} item which displays
4639 documentation associated with the menu's functions.
4642 Four types of menubars are provided:
4645 An extensive menubar providing access to global InfoDock commands.
4647 Mode-specific menubars tailored to the current major mode.
4649 A simple menubar for basic editing to help novices get started with InfoDock.
4651 The standard XEmacs menubar.
4654 Most modes also include mode-specific popup menus. Additionally, region and
4655 rectangle popup menus are included.
4657 @samp{Hyperbole}, the everyday information manager, is a core part of
4658 InfoDock. This provides context-sensitive mouse keys, a rolodex-type
4659 contact manager, programmable hypertext buttons, and an autonumbered
4660 outliner with embedded hyperlink anchors.
4662 The @samp{OO-Browser}, a multi-language object-oriented code browser, is a
4663 standard part of InfoDock.
4665 InfoDock saves a more extensive set of user options than other Emacs
4668 InfoDock inserts a useful file header in many file types, showing the
4669 author, summary, and last modification time of each file. A summary
4670 program can then be used to summarize all of the files in a directory,
4671 for easy MANIFEST file creation.
4673 Your working set of buffers is automatically saved and restored (if you
4674 answer yes to a prompt) between InfoDock sessions.
4676 Refined color choices for code highlighting are provided for both dark and
4677 light background display frames.
4679 The @kbd{C-z} key prefix performs frame-based commands which parallel the
4680 @kbd{C-x} key prefix for window-based commands.
4682 The Smart Menu system is included for producing command menus on dumb
4685 Lisp libraries are better categorized according to function.
4687 Extensions and improvements to many areas of Emacs are included, such as:
4688 paragraph filling, mail reading with Rmail, shell handling, outlining, code
4689 highlighting and browsing, and man page browsing.
4691 InfoDock questions, answers and discussion should go to the mail list
4695 @email{infodock@@infodock.com}. Use
4696 @email{infodock-request@@infodock.com} to be added or removed from the
4697 list. Always include your InfoDock version number when sending help
4700 InfoDock is available across the Internet via anonymous FTP. To get
4701 it, first move to a directory into which you want the InfoDock archive
4702 files placed. We will call this <DIST-DIR>.
4708 Ftp to ftp.xemacs.org (Internet Host ID = 128.174.252.16):
4711 prompt> ftp ftp.xemacs.org
4714 Login as @samp{anonymous} with your own <user-id>@@<site-name> as a password.
4717 Name (ftp.xemacs.org): anonymous
4718 331 Guest login ok, send your complete e-mail address as password.
4719 Password: -<your-user-id>@@<your-domain>
4720 230 Guest login ok, access restrictions apply.
4723 Move to the location of the InfoDock archives:
4726 ftp> cd pub/infodock
4729 Set your transfer mode to binary:
4740 Interactive mode off.
4743 Retrieve the InfoDock archives that you want, either by using a
4744 @samp{get <file>} for each file you want or by using the following to
4745 get a complete distribution, including all binaries:
4748 ftp> mget ID-INSTALL
4752 Close the FTP connection:
4759 Read the @file{ID-INSTALL} file which you just retrieved for
4760 step-by-step installation instructions.
4762 @node Q4.7.1, Q4.7.2, Q4.6.1, Subsystems
4763 @unnumberedsec 4.7: Other Unbundled Packages
4764 @unnumberedsubsec Q4.7.1: What is AUC TeX? Where do you get it?
4766 AUC TeX is a package written by @email{abraham@@dina.kvl.dk, Per Abrahamsen}.
4767 Starting with XEmacs 19.16, AUC TeX is bundled with XEmacs. The
4768 following information is from the @file{README} and website.
4770 AUC TeX is an extensible package that supports writing and formatting
4771 TeX files for most variants of GNU Emacs. Many different macro packages
4772 are supported, including AMS TeX, LaTeX, and TeXinfo.
4774 The most recent version is always available by ftp at
4778 @uref{ftp://sunsite.auc.dk/packages/auctex/auctex.tar.gz}.
4780 In case you don't have access to anonymous ftp, you can get it by an
4781 email request to @email{ftpmail@@decwrl.dec.com}.
4783 WWW users may want to check out the AUC TeX page at
4787 @uref{http://sunsite.auc.dk/auctex/}.
4789 @node Q4.7.2, Q4.7.3, Q4.7.1, Subsystems
4790 @unnumberedsubsec Q4.7.2: Are there any Emacs Lisp Spreadsheets?
4792 Yes. Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at
4796 @uref{ftp://cs.nyu.edu/pub/local/fox/dismal/}.
4798 @node Q4.7.3, Q4.7.4, Q4.7.2, Subsystems
4799 @unnumberedsubsec Q4.7.3: Byte compiling AUC TeX on XEmacs 19.14.
4801 @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan} writes:
4804 When byte compiling auctex-9.4g, you must use the command:
4807 xemacs -batch -l lpath.el
4811 @node Q4.7.4, Q4.7.5, Q4.7.3, Subsystems
4812 @unnumberedsubsec Q4.7.4: Problems installing AUC TeX.
4814 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
4817 AUC TeX works fine on both stock Emacs and XEmacs has been doing so for
4818 a very very long time. This is mostly due to the work of
4819 @email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu}
4820 package. Which leads to what is probably the problem...
4823 Most problems with AUC TeX are one of two things:
4827 The TeX-lisp-directory in @file{tex-site.el} and the makefile don't
4830 Fix: make sure you configure AUC TeX properly @strong{before} installing.
4833 You have an old version of easymenu.el in your path.
4835 Fix: use @code{locate-library} and remove old versions to make sure it
4836 @strong{only} finds the one that came with XEmacs.
4840 @node Q4.7.5, Q4.7.6, Q4.7.4, Subsystems
4841 @unnumberedsubsec Q4.7.5: Is there a reason for an Emacs package not to be included in XEmacs?
4843 The reason for an Emacs package not to be included in XEmacs is
4844 usually one or more of the following:
4848 The package has not been ported to XEmacs. This will typically happen
4849 when it uses GNU-Emacs-specific features, which make it fail under
4852 Porting a package to XEmacs can range from a trivial amount of change to
4853 a partial or full rewrite. Fortunately, the authors of modern packages
4854 usually choose to support both Emacsen themselves.
4857 The package has been decided not to be appropriate for XEmacs. It may
4858 have an equivalent or better replacement within XEmacs, in which case
4859 the developers may choose not to burden themselves with supporting an
4862 Each package bundled with XEmacs means more work for the maintainers,
4863 whether they want it or not. If you are ready to take over the
4864 maintenance responsibilities for the package you port, be sure to say
4865 so -- we will more likely include it.
4868 The package simply hasn't been noted by the XEmacs development. If
4869 that's the case, the messages like yours are very useful for attracting
4873 The package was noted by the developers, but they simply haven't yet
4874 gotten around to including/porting it. Wait for the next release or,
4875 even better, offer your help. It will be gladly accepted and
4879 @node Q4.7.6, , Q4.7.5, Subsystems
4880 @unnumberedsubsec Q4.7.5: Is there a MatLab mode?
4882 Is there any way I can get syntax highlighting for MatLab .m files?
4883 Can I "teach" emacs what words are MatLab commands, comments, etc. ?
4885 @email{elsner@@mathematik.tu-chemnitz.de, Ulrich Elsner} writes:
4887 One way to do this (and much more) is by using the
4891 @uref{ftp://ftp.mathworks.com/pub/contrib/v5/tools/matlab.el, matlab mode}.
4893 Instructions on how to install this mode are included in this file.
4897 @node Miscellaneous, Current Events, Subsystems, Top
4898 @unnumbered 5 The Miscellaneous Stuff
4900 This is part 5 of the XEmacs Frequently Asked Questions list. This
4901 section is devoted to anything that doesn't fit neatly into the other
4905 Major & Minor Modes:
4906 * Q5.0.1:: How can I do source code highlighting using font-lock?
4907 * Q5.0.2:: I do not like cc-mode. How do I use the old c-mode?
4908 * Q5.0.3:: How do I get @samp{More} Syntax Highlighting on by default?
4909 * Q5.0.4:: How can I enable auto-indent?
4910 * Q5.0.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
4911 * Q5.0.6:: How do I start up a second shell buffer?
4912 * Q5.0.7:: Telnet from shell filters too much.
4913 * Q5.0.8:: Why does edt emulation not work?
4914 * Q5.0.9:: How can I emulate VI and use it as my default mode?
4915 * Q5.0.10:: [This question intentionally left blank]
4916 * Q5.0.11:: Filladapt doesn't work in 19.15?
4917 * Q5.0.12:: How do I disable gnuserv from opening a new frame?
4918 * Q5.0.13:: How do I start gnuserv so that each subsequent XEmacs is a client?
4919 * Q5.0.14:: Strange things are happening in Shell Mode.
4920 * Q5.0.15:: Where do I get the latest CC Mode?
4921 * Q5.0.16:: I find auto-show-mode disconcerting. How do I turn it off?
4922 * Q5.0.17:: How can I get two instances of info?
4923 * Q5.0.18:: I upgraded to XEmacs 19.14 and gnuserv stopped working
4924 * Q5.0.19:: Is there something better than LaTeX mode?
4925 * Q5.0.20:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
4927 Emacs Lisp Programming Techniques:
4928 * Q5.1.1:: The difference in key sequences between XEmacs and GNU Emacs?
4929 * Q5.1.2:: Can I generate "fake" keyboard events?
4930 * Q5.1.3:: Could you explain @code{read-kbd-macro} in more detail?
4931 * Q5.1.4:: What is the performance hit of @code{let}?
4932 * Q5.1.5:: What is the recommended use of @code{setq}?
4933 * Q5.1.6:: What is the typical misuse of @code{setq}?
4934 * Q5.1.7:: I like the the @code{do} form of cl, does it slow things down?
4935 * Q5.1.8:: I like recursion, does it slow things down?
4936 * Q5.1.9:: How do I put a glyph as annotation in a buffer?
4937 * Q5.1.10:: @code{map-extents} won't traverse all of my extents!
4938 * Q5.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
4941 * Q5.2.1:: How do I turn off the sound?
4942 * Q5.2.2:: How do I get funky sounds instead of a boring beep?
4943 * Q5.2.3:: What's NAS, how do I get it?
4944 * Q5.2.4:: Sunsite sounds don't play.
4947 * Q5.3.1:: How do you make XEmacs indent CL if-clauses correctly?
4948 * Q5.3.2:: Fontifying hangs when editing a postscript file.
4949 * Q5.3.3:: How can I print WYSIWYG a font-locked buffer?
4950 * Q5.3.4:: Getting @kbd{M-x lpr} to work with postscript printer.
4951 * Q5.3.5:: How do I specify the paths that XEmacs uses for finding files?
4952 * Q5.3.6:: [This question intentionally left blank]
4953 * Q5.3.7:: Can I have the end of the buffer delimited in some way?
4954 * Q5.3.8:: How do I insert today's date into a buffer?
4955 * Q5.3.9:: Are only certain syntactic character classes available for abbrevs?
4956 * Q5.3.10:: How can I get those oh-so-neat X-Face lines?
4957 * Q5.3.11:: How do I add new Info directories?
4958 * Q5.3.12:: What do I need to change to make printing work?
4961 @node Q5.0.1, Q5.0.2, Miscellaneous, Miscellaneous
4962 @unnumberedsec 5.0: Major & Minor Modes
4963 @unnumberedsubsec Q5.0.1: How can I do source code highlighting using font-lock?
4965 For most modes, font-lock is already set up and just needs to be turned
4966 on. This can be done by @kbd{M-x font-lock-mode}, or by having XEmacs
4967 automatically start it by adding lines like:
4970 (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
4971 (add-hook 'dired-mode-hook 'turn-on-font-lock)
4974 to your @file{.emacs}. See the file @file{etc/sample.emacs} for more
4977 See also @code{Syntax Highlighting} from the @code{Options} menu.
4978 Remember to save options.
4980 @node Q5.0.2, Q5.0.3, Q5.0.1, Miscellaneous
4981 @unnumberedsubsec Q5.0.2: I do not like cc-mode. How do I use the old c-mode?
4983 Well, first off, consider if you really want to do this. cc-mode is
4984 much more powerful than the old c-mode. If you're having trouble
4985 getting your old offsets to work, try using @code{c-set-offset} instead.
4986 You might also consider using the package @code{cc-compat}.
4988 But, if you still insist, add the following lines to your @file{.emacs}:
4991 (fmakunbound 'c-mode)
4992 (makunbound 'c-mode-map)
4993 (fmakunbound 'c++-mode)
4994 (makunbound 'c++-mode-map)
4995 (makunbound 'c-style-alist)
4996 (load-library "old-c-mode")
4997 (load-library "old-c++-mode")
5000 This must be done before any other reference is made to either c-mode or
5003 @node Q5.0.3, Q5.0.4, Q5.0.2, Miscellaneous
5004 @unnumberedsubsec Q5.0.3: How do I get @samp{More} Syntax Highlighting on by default?
5006 Use the following code in your @file{.emacs}:
5009 (setq-default font-lock-maximum-decoration t)
5012 In versions of XEmacs prior to 19.14, you had to use a kludgy solution
5016 (setq c-font-lock-keywords c-font-lock-keywords-2
5017 c++-font-lock-keywords c++-font-lock-keywords-2
5018 lisp-font-lock-keywords lisp-font-lock-keywords-2)
5021 It will work for C, C++ and Lisp.
5023 See also @code{Syntax Highlighting} from the @code{Options} menu.
5024 Remember to save options.
5026 @node Q5.0.4, Q5.0.5, Q5.0.3, Miscellaneous
5027 @unnumberedsubsec Q5.0.4: How can I enable auto-indent?
5029 Put the following line in your @file{.emacs}:
5032 (setq indent-line-function 'indent-relative-maybe)
5035 If you want to get fancy, try the @code{filladapt} package available
5036 standard with XEmacs. Put this into your @file{.emacs}:
5039 (require 'filladapt)
5040 (add-hook 'text-mode-hook 'turn-on-filladapt-mode)
5044 You can customize filling and adaptive filling with Customize.
5045 Select from the @code{Options} menu
5046 @code{Customize->Emacs->->Editing->Fill->Fill...}
5047 or type @kbd{M-x customize @key{RET} fill @key{RET}}.
5049 Note that well-behaving text-lookalike modes will run
5050 @code{text-mode-hook} by default (e.g. that's what Message does). For
5051 the nasty ones, you'll have to provide the @code{add-hook}s yourself.
5053 Please note that the @code{fa-extras} package is no longer useful.
5055 @node Q5.0.5, Q5.0.6, Q5.0.4, Miscellaneous
5056 @unnumberedsubsec Q5.0.5: How can I get XEmacs to come up in text/auto-fill mode by default?
5058 Try the following lisp in your @file{.emacs}:
5061 (setq default-major-mode 'text-mode)
5062 (setq text-mode-hook 'turn-on-auto-fill)
5065 @strong{WARNING}: note that changing the value of
5066 @code{default-major-mode} from @code{fundamental-mode} can break a large
5067 amount of built-in code that expects newly created buffers to be in
5068 @code{fundamental-mode}. (Changing from @code{fundamental-mode} to
5069 @code{text-mode} might not wreak too much havoc, but changing to
5070 something more exotic like a lisp-mode would break many Emacs packages).
5072 Note that Emacs by default starts up in buffer @code{*scratch*} in
5073 @code{initial-major-mode}, which defaults to
5074 @code{lisp-interaction-mode}. Thus adding the following form to your
5075 Emacs init file will cause the initial @code{*scratch*} buffer to be put
5076 into auto-fill'ed @code{text-mode}:
5079 (setq initial-major-mode
5082 (turn-on-auto-fill)))
5085 Note that after your init file is loaded, if
5086 @code{inhibit-startup-message} is @code{nil} (the default) and the
5087 startup buffer is @code{*scratch*} then the startup message will be
5088 inserted into @code{*scratch*}; it will be removed after a timeout by
5089 erasing the entire @code{*scratch*} buffer. Keep in mind this default
5090 usage of @code{*scratch*} if you desire any prior manipulation of
5091 @code{*scratch*} from within your Emacs init file. In particular,
5092 anything you insert into @code{*scratch*} from your init file will be
5093 later erased. Also, if you change the mode of the @code{*scratch*}
5094 buffer, be sure that this will not interfere with possible later
5095 insertion of the startup message (e.g. if you put @code{*scratch*} into
5096 a nonstandard mode that has automatic font lock rules, then the startup
5097 message might get fontified in a strange foreign manner, e.g. as code in
5098 some programming language).
5100 @node Q5.0.6, Q5.0.7, Q5.0.5, Miscellaneous
5101 @unnumberedsubsec Q5.0.6: How do I start up a second shell buffer?
5103 In the @code{*shell*} buffer:
5106 M-x rename-buffer @key{RET} *shell-1* @key{RET}
5110 This will then start a second shell. The key is that no buffer named
5111 @samp{*shell*} can exist. It might be preferable to use @kbd{M-x
5112 rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x
5115 @node Q5.0.7, Q5.0.8, Q5.0.6, Miscellaneous
5116 @unnumberedsubsec Q5.0.7: Telnet from shell filters too much
5118 I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke
5119 and use a telnet session within it. Everything works fine except that
5120 now all @samp{^M}'s are filtered out by Emacs. Fixes?
5122 Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather
5123 than doing rsh or telnet within the local shell buffer. Starting with
5124 XEmacs-20.3 you can also use @kbd{M-x ssh} to open secure remote session
5125 if you have @code{ssh} installed.
5127 @node Q5.0.8, Q5.0.9, Q5.0.7, Miscellaneous
5128 @unnumberedsubsec Q5.0.8: Why does edt emulation not work?
5130 We don't know, but you can use tpu-edt emulation instead, which works
5131 fine and is a little fancier than the standard edt emulation. To do
5132 this, add the following line to your @file{.emacs}:
5138 If you don't want it to replace @kbd{C-h} with an edt-style help menu
5142 (global-set-key [(control h)] 'help-for-help)
5145 @node Q5.0.9, Q5.0.10, Q5.0.8, Miscellaneous
5146 @unnumberedsubsec Q5.0.9: How can I emulate VI and use it as my default mode?
5148 Our recommended VI emulator is viper. To make viper-mode the default,
5149 add this to your @file{.emacs}:
5155 @email{kifer@@CS.SunySB.EDU, Michael Kifer} writes:
5158 This should be added as close to the top of @file{.emacs} as you can get
5159 it, otherwise some minor modes may not get viper-ized.
5162 @node Q5.0.10, Q5.0.11, Q5.0.9, Miscellaneous
5163 @unnumberedsubsec Q5.0.10: [This question intentionally left blank]
5165 Obsolete question, left blank to avoid renumbering
5167 @node Q5.0.11, Q5.0.12, Q5.0.10, Miscellaneous
5168 @unnumberedsubsec Q5.0.11: Filladapt doesn't work in 19.15
5170 Filladapt 2.x is included in 19.15. In it filladapt is now a minor
5171 mode and minor modes are traditionally off by default. The following
5172 added to your @file{.emacs} will turn it on for all buffers:
5175 (setq-default filladapt-mode t)
5178 Use @code{turn-on-filladapt-mode} to turn Filladapt on in particular
5179 major modes, like this:
5182 (add-hook 'text-mode-hook 'turn-on-filladapt-mode)
5185 @node Q5.0.12, Q5.0.13, Q5.0.11, Miscellaneous
5186 @unnumberedsubsec Q5.0.12: How do I disable gnuserv from opening a new frame?
5188 If you set the @code{gnuserv-frame} variable to the frame that should be
5189 used to display buffers that are pulled up, a new frame will not be
5190 created. For example, you could put
5193 (setq gnuserv-frame (selected-frame))
5196 early on in your @file{.emacs}, to ensure that the first frame created
5197 is the one used for your gnuserv buffers.
5199 Starting in 19.15, there is an option to set the gnuserv target to
5200 the current frame. See
5201 @code{Options->"Other Window" Location->Make current frame gnuserv target}
5203 Starting with XEmacs-20.3 you can also change this with Customize.
5204 Select from the @code{Options} menu
5205 @code{Customize->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type
5206 @kbd{M-x customize @key{RET} gnuserv @key{RET}}.
5209 @node Q5.0.13, Q5.0.14, Q5.0.12, Miscellaneous
5210 @unnumberedsubsec Q5.0.13: How do I start gnuserv so that each subsequent XEmacs is a client?
5212 Put the following in your @file{.emacs} file to start the server:
5218 Start your first XEmacs as usual. After that, you can do:
5221 gnuclient randomfilename
5224 from the command line to get your existing XEmacs process to open a new
5225 frame and visit randomfilename in that window. When you're done editing
5226 randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the
5229 See also man page of gnuclient.
5231 @node Q5.0.14, Q5.0.15, Q5.0.13, Miscellaneous
5232 @unnumberedsubsec Q5.0.14: Strange things are happening in Shell Mode.
5234 Sometimes (i.e. it's not repeatable, and I can't work out why it
5235 happens) when I'm typing into shell mode, I hit return and only a
5236 portion of the command is given to the shell, and a blank prompt is
5237 returned. If I hit return again, the rest of the previous command is
5240 @email{martin@@xemacs.org, Martin Buchholz} writes:
5243 There is a known problem with interaction between @code{csh} and the
5244 @code{filec} option and XEmacs. You should add the following to your
5248 if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec
5252 @node Q5.0.15, Q5.0.16, Q5.0.14, Miscellaneous
5253 @unnumberedsubsec Q5.0.15: Where do I get the latest CC Mode?
5255 @email{bwarsaw@@cnri.reston.va.us, Barry A. Warsaw} writes:
5258 This can be had from @uref{http://www.python.org/ftp/emacs/}.
5261 @node Q5.0.16, Q5.0.17, Q5.0.15, Miscellaneous
5262 @unnumberedsubsec Q5.0.16: I find auto-show-mode disconcerting. How do I turn it off?
5264 @code{auto-show-mode} controls whether or not a horizontal scrollbar
5265 magically appears when a line is too long to be displayed. This is
5266 enabled by default. To turn it off, put the following in your
5270 (setq auto-show-mode nil)
5271 (setq-default auto-show-mode nil)
5274 @node Q5.0.17, Q5.0.18, Q5.0.16, Miscellaneous
5275 @unnumberedsubsec Q5.0.17: How can I get two instances of info?
5277 You can't. The @code{info} package does not provide for multiple info buffers.
5279 @node Q5.0.18, Q5.0.19, Q5.0.17, Miscellaneous
5280 @unnumberedsubsec Q5.0.18: I upgraded to XEmacs 19.14 and gnuserv stopped working.
5282 @email{daku@@nortel.ca, Mark Daku} writes:
5285 It turns out I was using an older version of gnuserv. The installation
5286 didn't put the binary into the public bin directory. It put it in
5290 @file{lib/xemacs-19.14/hppa1.1-hp-hpux9.05/gnuserv}. Shouldn't it have
5291 been put in @file{bin/hppa1.1-hp-hpux9.0}?
5294 @node Q5.0.19, Q5.0.20, Q5.0.18, Miscellaneous
5295 @unnumberedsubsec Q5.0.19: Is there something better than LaTeX mode?
5297 @email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes:
5300 The standard TeX modes leave much to be desired, and are somewhat
5301 leniently maintained. Serious TeX users use AUC TeX (@pxref{Q4.7.1}).
5304 @node Q5.0.20, Q5.1.1, Q5.0.19, Miscellaneous
5305 @unnumberedsubsec Q5.0.20: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
5307 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
5309 Here is one of the solutions, we have this in a script called
5310 @file{etc/editclient.sh}.
5313 if gnuclient -batch -eval t >/dev/null 2>&1
5315 exec gnuclient $@{1+"$@@"@}
5317 xemacs -unmapped -f gnuserv-start &
5318 until gnuclient -batch -eval t >/dev/null 2>&1
5322 exec gnuclient $@{1+"$@@"@}
5326 Note that there is a known problem when running XEmacs and 'gnuclient
5327 -nw' on the same TTY.
5330 @node Q5.1.1, Q5.1.2, Q5.0.20, Miscellaneous
5331 @unnumberedsec 5.1: Emacs Lisp Programming Techniques
5332 @unnumberedsubsec Q5.1.1: What is the difference in key sequences between XEmacs and GNU Emacs?
5334 @email{clerik@@naggum.no, Erik Naggum} writes;
5337 Emacs has a legacy of keyboards that produced characters with modifier
5338 bits, and therefore map a variety of input systems into this scheme even
5339 today. XEmacs is instead optimized for X events. This causes an
5340 incompatibility in the way key sequences are specified, but both Emacs
5341 and XEmacs will accept a key sequence as a vector of lists of modifiers
5342 that ends with a key, e.g., to bind @kbd{M-C-a}, you would say
5343 @code{[(meta control a)]} in both Emacsen. XEmacs has an abbreviated
5344 form for a single key, just (meta control a). Emacs has an abbreviated
5345 form for the Control and the Meta modifiers to string-characters (the
5346 ASCII characters), as in @samp{\M-\C-a}. XEmacs users need to be aware
5347 that the abbreviated form works only for one-character key sequences,
5348 while Emacs users need to be aware that the string-character is rather
5349 limited. Specifically, the string-character can accommodate only 256
5350 different values, 128 of which have the Meta modifier and 128 of which
5351 have not. In each of these blocks, only 32 characters have the Control
5352 modifier. Whereas @code{[(meta control A)]} differs from @code{[(meta
5353 control a)]} because the case differs, @samp{\M-\C-a} and @samp{\M-\C-A}
5354 do not. Programmers are advised to use the full common form, both
5355 because it is more readable and less error-prone, and because it is
5356 supported by both Emacsen.
5359 Another (even safer) way to be sure of the key-sequences is to use the
5360 @code{read-kbd-macro} function, which takes a string like @samp{C-c
5361 <up>}, and converts it to the internal key representation of the Emacs
5362 you use. The function is available both on XEmacs and GNU Emacs.
5364 @node Q5.1.2, Q5.1.3, Q5.1.1, Miscellaneous
5365 @unnumberedsubsec Q5.1.2: Can I generate "fake" keyboard events?
5367 I wonder if there is an interactive function that can generate
5368 @dfn{fake} keyboard events. This way, I could simply map them inside
5374 (defun cg--generate-char-event (ch)
5375 "Generate an event, as if ch has been typed"
5376 (dispatch-event (character-to-event ch)))
5378 ;; Backspace and Delete stuff
5379 (global-set-key [backspace]
5380 (lambda () (interactive) (cg--generate-char-event 127)))
5381 (global-set-key [unknown_keysym_0x4]
5382 (lambda () (interactive) (cg--generate-char-event 4)))
5385 @node Q5.1.3, Q5.1.4, Q5.1.2, Miscellaneous
5386 @unnumberedsubsec Q5.1.3: Could you explain @code{read-kbd-macro} in more detail?
5388 The @code{read-kbd-macro} function returns the internal Emacs
5389 representation of a human-readable string (which is its argument).
5393 (read-kbd-macro "C-c C-a")
5394 @result{} [(control ?c) (control ?a)]
5396 (read-kbd-macro "C-c C-. <up>")
5397 @result{} [(control ?c) (control ?.) up]
5400 In GNU Emacs the same forms will be evaluated to what GNU Emacs
5401 understands internally---the sequences @code{"\C-x\C-c"} and @code{[3
5402 67108910 up]}, respectively.
5404 The exact @dfn{human-readable} syntax is defined in the docstring of
5405 @code{edmacro-mode}. I'll repeat it here, for completeness.
5408 Format of keyboard macros during editing:
5410 Text is divided into @dfn{words} separated by whitespace. Except for
5411 the words described below, the characters of each word go directly as
5412 characters of the macro. The whitespace that separates words is
5413 ignored. Whitespace in the macro must be written explicitly, as in
5414 @kbd{foo @key{SPC} bar @key{RET}}.
5418 The special words @kbd{RET}, @kbd{SPC}, @kbd{TAB}, @kbd{DEL}, @kbd{LFD},
5419 @kbd{ESC}, and @kbd{NUL} represent special control characters. The
5420 words must be written in uppercase.
5423 A word in angle brackets, e.g., @code{<return>}, @code{<down>}, or
5424 @code{<f1>}, represents a function key. (Note that in the standard
5425 configuration, the function key @code{<return>} and the control key
5426 @key{RET} are synonymous.) You can use angle brackets on the words
5427 @key{RET}, @key{SPC}, etc., but they are not required there.
5430 Keys can be written by their @sc{ascii} code, using a backslash followed
5431 by up to six octal digits. This is the only way to represent keys with
5435 One or more prefixes @kbd{M-} (meta), @kbd{C-} (control), @kbd{S-}
5436 (shift), @kbd{A-} (alt), @kbd{H-} (hyper), and @kbd{s-} (super) may
5437 precede a character or key notation. For function keys, the prefixes
5438 may go inside or outside of the brackets: @code{C-<down>} @equiv{}
5439 @code{<C-down>}. The prefixes may be written in any order: @kbd{M-C-x}
5440 @equiv{} @kbd{C-M-x}.
5442 Prefixes are not allowed on multi-key words, e.g., @kbd{C-abc}, except
5443 that the Meta prefix is allowed on a sequence of digits and optional
5444 minus sign: @kbd{M--123} @equiv{} @kbd{M-- M-1 M-2 M-3}.
5447 The @code{^} notation for control characters also works: @kbd{^M}
5451 Double angle brackets enclose command names: @code{<<next-line>>} is
5452 shorthand for @kbd{M-x next-line @key{RET}}.
5455 Finally, @code{REM} or @code{;;} causes the rest of the line to be
5456 ignored as a comment.
5459 Any word may be prefixed by a multiplier in the form of a decimal number
5460 and @code{*}: @code{3*<right>} @equiv{} @code{<right> <right> <right>},
5461 and @code{10*foo} @equiv{}
5465 @code{foofoofoofoofoofoofoofoofoofoo}.
5467 Multiple text keys can normally be strung together to form a word, but
5468 you may need to add whitespace if the word would look like one of the
5469 above notations: @code{; ; ;} is a keyboard macro with three semicolons,
5470 but @code{;;;} is a comment. Likewise, @code{\ 1 2 3} is four keys but
5471 @code{\123} is a single key written in octal, and @code{< right >} is
5472 seven keys but @code{<right>} is a single function key. When in doubt,
5476 @node Q5.1.4, Q5.1.5, Q5.1.3, Miscellaneous
5477 @unnumberedsubsec Q5.1.4: What is the performance hit of @code{let}?
5479 In most cases, not noticeable. Besides, there's no avoiding
5480 @code{let}---you have to bind your local variables, after all. Some
5481 pose a question whether to nest @code{let}s, or use one @code{let} per
5482 function. I think because of clarity and maintenance (and possible
5483 future implementation), @code{let}-s should be used (nested) in a way to
5484 provide the clearest code.
5486 @node Q5.1.5, Q5.1.6, Q5.1.4, Miscellaneous
5487 @unnumberedsubsec Q5.1.5: What is the recommended use of @code{setq}?
5490 @item Global variables
5492 You will typically @code{defvar} your global variable to a default
5493 value, and use @code{setq} to set it later.
5495 It is never a good practice to @code{setq} user variables (like
5496 @code{case-fold-search}, etc.), as it ignores the user's choice
5497 unconditionally. Note that @code{defvar} doesn't change the value of a
5498 variable if it was bound previously. If you wish to change a
5499 user-variable temporarily, use @code{let}:
5502 (let ((case-fold-search nil))
5503 ... ; code with searches that must be case-sensitive
5507 You will notice the user-variables by their docstrings beginning with an
5508 asterisk (a convention).
5510 @item Local variables
5512 Bind them with @code{let}, which will unbind them (or restore their
5513 previous value, if they were bound) after exiting from the @code{let}
5514 form. Change the value of local variables with @code{setq} or whatever
5515 you like (e.g. @code{incf}, @code{setf} and such). The @code{let} form
5516 can even return one of its local variables.
5521 ;; iterate through the elements of the list returned by
5522 ;; `hairy-function-that-returns-list'
5523 (let ((l (hairy-function-that-returns-list)))
5525 ... do something with (car l) ...
5529 Another typical usage includes building a value simply to work with it.
5532 ;; Build the mode keymap out of the key-translation-alist
5533 (let ((inbox (file-truename (expand-file-name box)))
5535 ... code dealing with inbox ...
5539 This piece of code uses the local variable @code{inbox}, which becomes
5540 unbound (or regains old value) after exiting the form. The form also
5541 returns the value of @code{inbox}, which can be reused, for instance:
5544 (setq foo-processed-inbox
5549 @node Q5.1.6, Q5.1.7, Q5.1.5, Miscellaneous
5550 @unnumberedsubsec Q5.1.6: What is the typical misuse of @code{setq} ?
5552 A typical misuse is probably @code{setq}ing a variable that was meant to
5553 be local. Such a variable will remain bound forever, never to be
5554 garbage-collected. For example, the code doing:
5557 (defun my-function (whatever)
5559 ... build a large list ...
5563 does a bad thing, as @code{a} will keep consuming memory, never to be
5564 unbound. The correct thing is to do it like this:
5567 (defun my-function (whatever)
5568 (let (a) ; default initialization is to nil
5569 ... build a large list ...
5570 ... and exit, unbinding `a' in the process ...)
5573 Not only is this prettier syntactically, but it makes it possible for
5574 Emacs to garbage-collect the objects which @code{a} used to reference.
5576 Note that even global variables should not be @code{setq}ed without
5577 @code{defvar}ing them first, because the byte-compiler issues warnings.
5578 The reason for the warning is the following:
5581 (defun flurgoze nil) ; ok, global internal variable
5584 (setq flurghoze t) ; ops! a typo, but semantically correct.
5585 ; however, the byte-compiler warns.
5587 While compiling toplevel forms:
5588 ** assignment to free variable flurghoze
5591 @node Q5.1.7, Q5.1.8, Q5.1.6, Miscellaneous
5592 @unnumberedsubsec Q5.1.7: I like the the @code{do} form of cl, does it slow things down?
5594 It shouldn't. Here is what Dave Gillespie has to say about cl.el
5598 Many of the advanced features of this package, such as @code{defun*},
5599 @code{loop}, and @code{setf}, are implemented as Lisp macros. In
5600 byte-compiled code, these complex notations will be expanded into
5601 equivalent Lisp code which is simple and efficient. For example, the
5609 are expanded at compile-time to the Lisp forms
5613 (setcar p (cons x (car p)))
5616 which are the most efficient ways of doing these respective operations
5617 in Lisp. Thus, there is no performance penalty for using the more
5618 readable @code{incf} and @code{push} forms in your compiled code.
5620 @emph{Interpreted} code, on the other hand, must expand these macros
5621 every time they are executed. For this reason it is strongly
5622 recommended that code making heavy use of macros be compiled. (The
5623 features labelled @dfn{Special Form} instead of @dfn{Function} in this
5624 manual are macros.) A loop using @code{incf} a hundred times will
5625 execute considerably faster if compiled, and will also garbage-collect
5626 less because the macro expansion will not have to be generated, used,
5627 and thrown away a hundred times.
5629 You can find out how a macro expands by using the @code{cl-prettyexpand}
5633 @node Q5.1.8, Q5.1.9, Q5.1.7, Miscellaneous
5634 @unnumberedsubsec Q5.1.8: I like recursion, does it slow things down?
5636 Yes. Emacs byte-compiler cannot do much to optimize recursion. But
5637 think well whether this is a real concern in Emacs. Much of the Emacs
5638 slowness comes from internal mechanisms such as redisplay, or from the
5639 fact that it is an interpreter.
5641 Please try not to make your code much uglier to gain a very small speed
5642 gain. It's not usually worth it.
5644 @node Q5.1.9, Q5.1.10, Q5.1.8, Miscellaneous
5645 @unnumberedsubsec Q5.1.9: How do I put a glyph as annotation in a buffer?
5647 Here is a solution that will insert the glyph annotation at the
5648 beginning of buffer:
5651 (make-annotation (make-glyph '([FORMAT :file FILE]
5652 [string :data "fallback-text"]))
5658 Replace @samp{FORMAT} with an unquoted symbol representing the format of
5659 the image (e.g. @code{xpm}, @code{xbm}, @code{gif}, @code{jpeg}, etc.)
5660 Instead of @samp{FILE}, use the image file name
5665 @file{/usr/local/lib/xemacs-20.2/etc/recycle.xpm}).
5667 You can turn this to a function (that optionally prompts you for a file
5668 name), and inserts the glyph at @code{(point)} instead of
5671 @node Q5.1.10, Q5.1.11, Q5.1.9, Miscellaneous
5672 @unnumberedsubsec Q5.1.10: @code{map-extents} won't traverse all of my extents!
5674 I tried to use @code{map-extents} to do an operation on all the extents
5675 in a region. However, it seems to quit after processing a random number
5676 of extents. Is it buggy?
5678 No. The documentation of @code{map-extents} states that it will iterate
5679 across the extents as long as @var{function} returns @code{nil}.
5680 Unexperienced programmers often forget to return @code{nil} explicitly,
5681 which results in buggy code. For instance, the following code is
5682 supposed to delete all the extents in a buffer, and issue as many
5683 @samp{fubar!} messages.
5686 (map-extents (lambda (ext ignore)
5688 (message "fubar!")))
5691 Instead, it will delete only the first extent, and stop right there --
5692 because @code{message} will return a non-nil value. The correct code
5696 (map-extents (lambda (ext ignore)
5702 @node Q5.1.11, Q5.2.1, Q5.1.10, Miscellaneous
5703 @unnumberedsubsec Q5.1.11: My elisp program is horribly slow. Is there
5704 an easy way to find out where it spends time?
5707 z@email{hniksic@@srce.hr, Hrvoje Niksic} writes:
5709 Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence}, press a key
5710 (say @key{RET} in the Gnus Group buffer), and get the results using
5711 @kbd{M-x profile-results}. It should give you an idea of where the time
5715 @node Q5.2.1, Q5.2.2, Q5.1.11, Miscellaneous
5716 @unnumberedsubsec Q5.2.1: How do I turn off the sound?
5718 Add the following line to your @file{.emacs}:
5721 (setq bell-volume 0)
5722 (setq sound-alist nil)
5725 That will make your XEmacs totally silent -- even the default ding sound
5726 (TTY beep on TTY-s) will be gone.
5728 Starting with XEmacs-20.2 you can also change these with Customize.
5729 Select from the @code{Options} menu
5730 @code{Customize->Emacs->Environment->Sound->Sound...} or type
5731 @kbd{M-x customize @key{RET} sound @key{RET}}.
5734 @node Q5.2.2, Q5.2.3, Q5.2.1, Miscellaneous
5735 @unnumberedsubsec Q5.2.2: How do I get funky sounds instead of a boring beep?
5737 Make sure your XEmacs was compiled with sound support, and then put this
5738 in your @file{.emacs}:
5741 (load-default-sounds)
5744 The sound support in XEmacs 19.14 was greatly improved over previous
5747 @node Q5.2.3, Q5.2.4, Q5.2.2, Miscellaneous
5748 @unnumberedsubsec Q5.2.3: What's NAS, how do I get it?
5750 @xref{Q2.0.3}, for an explanation of the @dfn{Network Audio System}.
5752 @node Q5.2.4, Q5.3.1, Q5.2.3, Miscellaneous
5753 @unnumberedsubsec Q5.2.4: Sunsite sounds don't play.
5755 I'm having some trouble with sounds I've downloaded from sunsite. They
5756 play when I run them through @code{showaudio} or cat them directly to
5757 @file{/dev/audio}, but XEmacs refuses to play them.
5759 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
5762 [Many of] These files have an (erroneous) 24byte header that tells about
5763 the format that they have been recorded in. If you cat them to
5764 @file{/dev/audio}, the header will be ignored and the default behavior
5765 for /dev/audio will be used. This happens to be 8kHz uLaw. It is
5766 probably possible to fix the header by piping through @code{sox} and
5767 passing explicit parameters for specifying the sampling format; you then
5768 need to perform a 'null' conversion from SunAudio to SunAudio.
5771 @node Q5.3.1, Q5.3.2, Q5.2.4, Miscellaneous
5772 @unnumberedsec 5.3: Miscellaneous
5773 @unnumberedsubsec Q5.3.1: How do you make XEmacs indent CL if-clauses correctly?
5775 I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the
5776 same amount instead of indenting the 3rd clause differently from the
5779 One way is to add, to @file{.emacs}:
5782 (put 'if 'lisp-indent-function nil)
5785 However, note that the package @code{cl-indent} that comes with
5786 XEmacs sets up this kind of indentation by default. @code{cl-indent}
5787 also knows about many other CL-specific forms. To use @code{cl-indent},
5792 (setq lisp-indent-function (function common-lisp-indent-function))
5795 One can also customize @file{cl-indent.el} so it mimics the default
5796 @code{if} indentation @code{then} indented more than the @code{else}.
5800 (put 'if 'common-lisp-indent-function '(nil nil &body))
5803 Also, a new version (1.2) of @file{cl-indent.el} was posted to
5804 comp.emacs.xemacs on 12/9/94. This version includes more documentation
5805 than previous versions. This may prove useful if you need to customize
5806 any indent-functions.
5808 @node Q5.3.2, Q5.3.3, Q5.3.1, Miscellaneous
5809 @unnumberedsubsec Q5.3.2: Fontifying hang when editing a postscript file.
5811 When I try to edit a postscript file it gets stuck saying:
5812 @samp{fontifying 'filename' (regexps....)} and it just sits there. If I
5813 press @kbd{C-c} in the window where XEmacs was started, it suddenly
5814 becomes alive again.
5816 This was caused by a bug in the Postscript font-lock regular
5817 expressions. It was fixed in 19.13. For earlier versions of XEmacs,
5818 have a look at your @file{.emacs} file. You will probably have a line
5822 (add-hook 'postscript-mode-hook 'turn-on-font-lock)
5825 Take it out, restart XEmacs, and it won't try to fontify your postscript
5828 @node Q5.3.3, Q5.3.4, Q5.3.2, Miscellaneous
5829 @unnumberedsubsec Q5.3.3: How can I print WYSIWYG a font-locked buffer?
5831 Font-lock looks nice. How can I print (WYSIWYG) the highlighted
5834 The package @code{ps-print}, which is now included with XEmacs, provides
5835 the ability to do this. The source code contains complete instructions
5836 on its use, in @file{<xemacs_src_root>/lisp/packages/ps-print.el}.
5838 @node Q5.3.4, Q5.3.5, Q5.3.3, Miscellaneous
5839 @unnumberedsubsec Q5.3.4: Getting @kbd{M-x lpr} to work with postscript printer.
5841 My printer is a Postscript printer and @code{lpr} only works for
5842 Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x
5843 lpr-buffer} to work?
5845 Put something like this in your @file{.emacs}:
5848 (setq lpr-command "a2ps")
5849 (setq lpr-switches '("-p" "-1"))
5852 If you don't use a2ps to convert ASCII to postscript (why not, it's
5853 free?), replace with the command you do use. Note also that some
5854 versions of a2ps require a @samp{-Pprinter} to ensure spooling.
5856 @node Q5.3.5, Q5.3.6, Q5.3.4, Miscellaneous
5857 @unnumberedsubsec Q5.3.5: How do I specify the paths that XEmacs uses for finding files?
5859 You can specify what paths to use by using a number of different flags
5860 when running configure. See the section MAKE VARIABLES in the top-level
5861 file INSTALL in the XEmacs distribution for a listing of those flags.
5863 Most of the time, however, the simplest fix is: @strong{do not} specify
5864 paths as you might for GNU Emacs. XEmacs can generally determine the
5865 necessary paths dynamically at run time. The only path that generally
5866 needs to be specified is the root directory to install into. That can
5867 be specified by passing the @code{--prefix} flag to configure. For a
5868 description of the XEmacs install tree, please consult the @file{NEWS}
5871 @node Q5.3.6, Q5.3.7, Q5.3.5, Miscellaneous
5872 @unnumberedsubsec Q5.3.6: [This question intentionally left blank]
5874 Obsolete question, left blank to avoid renumbering.
5876 @node Q5.3.7, Q5.3.8, Q5.3.6, Miscellaneous
5877 @unnumberedsubsec Q5.3.7: Can I have the end of the buffer delimited in some way?
5879 Say, with: @samp{[END]}?
5884 (let ((ext (make-extent (point-min) (point-max))))
5885 (set-extent-property ext 'start-closed t)
5886 (set-extent-property ext 'end-closed t)
5887 (set-extent-property ext 'detachable nil)
5888 (set-extent-end-glyph ext (make-glyph [string :data "[END]"])))
5891 Since this is XEmacs, you can specify an icon to be shown on
5892 window-system devices. To do so, change the @code{make-glyph} call to
5893 something like this:
5896 (make-glyph '([xpm :file "~/something.xpm"]
5897 [string :data "[END]"]))
5900 You can inline the @sc{xpm} definition yourself by specifying
5901 @code{:data} instead of @code{:file}. Here is such a full-featured
5902 version that works on both X and TTY devices:
5905 (let ((ext (make-extent (point-min) (point-max))))
5906 (set-extent-property ext 'start-closed t)
5907 (set-extent-property ext 'end-closed t)
5908 (set-extent-property ext 'detachable nil)
5909 (set-extent-end-glyph ext (make-glyph '([xpm :data "\
5911 static char* eye = @{
5920 \"___________`_`_`___b_b_b_b_________`____\",
5921 \"_________`_`_`___b_c_c_c_b_b____________\",
5922 \"_____`_`_`_e___b_b_c_c_c___b___b_______`\",
5923 \"___`_`_e_a___b_b_d___b___b___b___b______\",
5924 \"_`_`_e_a_e___b_b_d_b___b___b___b___b____\",
5925 \"_`_`_a_e_a___b_b_d___b___b___b___b___b__\",
5926 \"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\",
5927 \"___`_`_e_a___b_b_b_d_c___b___b___d_b____\",
5928 \"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\",
5929 \"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\",
5930 \"___`_____`_`_`_`___b_b_b_b_b_b__________\",
5932 [string :data "[END]"]))))
5935 Note that you might want to make this a function, and put it to a hook.
5936 We leave that as an exercise for the reader.
5938 @node Q5.3.8, Q5.3.9, Q5.3.7, Miscellaneous
5939 @unnumberedsubsec Q5.3.8: How do I insert today's date into a buffer?
5944 (insert (current-time-string))
5947 @node Q5.3.9, Q5.3.10, Q5.3.8, Miscellaneous
5948 @unnumberedsubsec Q5.3.9: Are only certain syntactic character classes available for abbrevs?
5950 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
5953 Yes, abbrevs only expands word-syntax strings. While XEmacs does not
5954 prevent you from defining (e.g. with @kbd{C-x a g} or @kbd{C-x a l})
5955 abbrevs that contain special characters, it will refuse to expand
5956 them. So you need to ensure, that the abbreviation contains letters and
5957 digits only. This means that @samp{xd}, @samp{d5}, and @samp{5d} are
5958 valid abbrevs, but @samp{&d}, and @samp{x d} are not.
5960 If this sounds confusing to you, (re-)read the online documentation for
5961 abbrevs (@kbd{C-h i m XEmacs @key{RET} m Abbrevs @key{RET}}), and then come back and
5962 read this question/answer again.
5965 Starting with XEmacs 20.3 this restriction has been lifted.
5967 @node Q5.3.10, Q5.3.11, Q5.3.9, Miscellaneous
5968 @unnumberedsubsec Q5.3.10: How can I get those oh-so-neat X-Face lines?
5970 Firstly there is an ftp site which describes X-faces and has the
5971 associated tools mentioned below, at
5972 @uref{ftp://ftp.cs.indiana.edu:/pub/faces/}.
5978 Create 48x48x1 bitmap with your favorite tool
5981 Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc.,
5982 and then compile the face.
5986 cat file.xbm | xbm2ikon |compface > file.face
5990 Then be sure to quote things that are necessary for emacs strings:
5993 cat ./file.face | sed 's/\\/\\\\/g'
5997 | sed 's/\"/\\\"/g' > ./file.face.quoted
6001 Then set up emacs to include the file as a mail header - there were a
6002 couple of suggestions here---either something like:
6005 (setq mail-default-headers
6006 "X-Face: @email{Ugly looking text string here}")
6009 Or, alternatively, as:
6012 (defun mail-insert-x-face ()
6014 (goto-char (point-min))
6015 (search-forward mail-header-separator)
6018 (insert-file-contents "~/.face")))
6020 (add-hook 'mail-setup-hook 'mail-insert-x-face)
6024 However, 2 things might be wrong:
6026 Some versions of pbmtoicon produces some header lines that is not
6027 expected by the version of compface that I grabbed. So I found I had to
6028 include a @code{tail +3} in the pipeline like this:
6031 cat file.xbm | xbm2ikon | tail +3 |compface > file.face
6034 Some people have also found that if one uses the @code{(insert-file)}
6035 method, one should NOT quote the face string using the sed script .
6037 It might also be helpful to use @email{stig@@hackvan.com, Stig's} script
6038 (included in the compface distribution at XEmacs.org) to do the
6039 conversion. For convenience xbm2xface is available for anonymous FTP at
6040 @uref{ftp://ftp.miranova.com/pub/xemacs/xbm2xface.pl}.
6042 Contributors for this item:
6053 @node Q5.3.11, Q5.3.12, Q5.3.10, Miscellaneous
6054 @unnumberedsubsec Q5.3.11: How do I add new Info directories?
6056 You use something like:
6059 (setq Info-directory-list (cons
6060 (expand-file-name "~/info")
6061 Info-default-directory-list))
6064 @email{davidm@@prism.kla.com, David Masterson} writes:
6067 Emacs Info and XEmacs Info do many things differently. If you're trying to
6068 support a number of versions of Emacs, here are some notes to remember:
6072 Emacs Info scans @code{Info-directory-list} from right-to-left while
6073 XEmacs Info reads it from left-to-right, so append to the @emph{correct}
6077 Use @code{Info-default-directory-list} to initialize
6078 @code{Info-directory-list} @emph{if} it is available at startup, but not
6079 all Emacsen define it.
6082 Emacs Info looks for a standard @file{dir} file in each of the
6083 directories scanned from #1 and magically concatenates them together.
6086 XEmacs Info looks for a @file{localdir} file (which consists of just the
6087 menu entries from a @file{dir} file) in each of the directories scanned
6088 from #1 (except the first), does a simple concatenation of them, and
6089 magically attaches the resulting list to the end of the menu in the
6090 @file{dir} file in the first directory.
6093 Another alternative is to convert the documentation to HTML with
6094 texi2html and read it from a web browser like Lynx or W3.
6097 @node Q5.3.12, , Q5.3.11, Miscellaneous
6098 @unnumberedsubsec Q5.3.12: What do I need to change to make printing work?
6100 For regular printing there are two variables that can be customized.
6104 This should be set to a command that takes standard input and sends
6105 it to a printer. Something like:
6108 (setq lpr-command "lp")
6112 This should be set to a list that contains whatever the print command
6113 requires to do its job. Something like:
6116 (setq lpr-switches '("-depson"))
6120 For postscript printing there are three analogous variables to
6124 @item ps-lpr-command
6125 This should be set to a command that takes postscript on standard input
6126 and directs it to a postscript printer.
6128 @item ps-lpr-switches
6129 This should be set to a list of switches required for
6130 @code{ps-lpr-command} to do its job.
6132 @item ps-print-color-p
6133 This boolean variable should be set @code{t} if printing will be done in
6134 color, otherwise it should be set to @code{nil}.
6137 NOTE: It is an undocumented limitation in XEmacs that postscript
6138 printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a
6139 window system environment. It cannot be used outside of X11.
6141 @node Current Events, , Miscellaneous, Top
6142 @unnumbered 6 What the Future Holds
6144 This is part 6 of the XEmacs Frequently Asked Questions list. This
6145 section will change monthly, and contains any interesting items that have
6146 transpired over the previous month. If you are reading this from the
6147 XEmacs distribution, please see the version on the Web or archived at the
6148 various FAQ FTP sites, as this file is surely out of date.
6151 * Q6.0.1:: What is new in 20.2?
6152 * Q6.0.2:: What is new in 20.3?
6153 * Q6.0.3:: What is new in 20.4?
6154 * Q6.0.4:: Procedural changes in XEmacs development.
6157 @node Q6.0.1, Q6.0.2, Current Events, Current Events
6158 @unnumberedsec 6.0: Changes
6159 @unnumberedsubsec Q6.0.1: What is new in 20.2?
6161 The biggest changes in 20.2 include integration of EFS (the next
6162 generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a
6163 major mode for editing Tex and LaTeX, and a lot of other stuff). Many
6164 bugs from 20.0 have been fixed for this release. 20.2 also contains a
6165 new system for customizing XEmacs options, invoked via @kbd{M-x
6168 XEmacs 20.2 is the development release (20.0 was beta), and is no longer
6169 considered unstable.
6171 @node Q6.0.2, Q6.0.3, Q6.0.1, Current Events
6172 @unnumberedsubsec Q6.0.2: What is new in 20.3?
6174 XEmacs 20.3 was released in November 1997. It contains many bugfixes,
6175 and a number of new features, including Autoconf 2 based configuration,
6176 additional support for Mule (Multi-language extensions to Emacs), many
6177 more customizations, multiple frames on TTY-s, support for multiple info
6178 directories, an enhanced gnuclient, improvements to regexp matching,
6179 increased MIME support, and many, many synches with GNU Emacs 20.
6181 The XEmacs/Mule support has been only seriously tested in a Japanese
6182 locale, and no doubt many problems still remain. The support for
6183 ISO-Latin-1 and Japanese is fairly strong. MULE support comes at a
6184 price -- about a 30% slowdown from 19.16. We're making progress on
6185 improving performance and XEmacs 20.3 compiled without Mule (which is
6186 the default) is definitely faster than XEmacs 19.16.
6188 XEmacs 20.3 is the first non-beta v20 release, and will be the
6189 basis for all further development.
6191 @node Q6.0.3, Q6.0.4, Q6.0.2, Current Events
6192 @unnumberedsubsec Q6.0.3: What's new in XEmacs 20.4?
6194 XEmacs 20.4 is a bugfix release with no user-visible changes.
6195 @c Filled in from NEWS file of 20.5-b33
6198 @node Q6.0.4, , Q6.0.3, Current Events
6199 @unnumberedsubsec Q6.0.4: Procedural changes in XEmacs development.
6203 Discussion about the development of XEmacs occurs on the xemacs-beta
6204 mailing list. Subscriptions to this list will now be fully automated
6205 instead of being handled by hand. Send a mail message to
6206 @email{xemacs-beta-request@@xemacs.org} with @samp{subscribe} as the
6207 BODY of the message to join the list. Please note this is a developers
6208 mailing list for people who have an active interest in the development
6211 The discussion of NT XEmacs development is taking place on a separate
6212 mailing list. Send mail to
6216 @email{xemacs-nt-request@@xemacs.org} to
6220 Due to the long development cycle in between releases, it has been
6221 decided that intermediate versions will be made available in source only
6222 form for the truly interested.
6224 XEmacs 19.16 was the last 19 release, basically consisting of 19.15 plus
6225 the collected bugfixes.
6228 As of December 1996, @email{steve@@altair.xemacs.org, Steve Baur} has become
6229 the lead maintainer of XEmacs.