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/11/20 20:16:50 $
12 @author Tony Rossini <arossini@@stat.sc.edu>
13 @author Ben Wing <ben@@xemacs.org>
14 @author Chuck Thompson <cthomp@@xemacs.org>
15 @author Steve Baur <steve@@xemacs.org>
16 @author Andreas Kaempf <andreas@@sccon.com>
17 @author Christian Nyb@o{} <chr@@mediascience.no>
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
308 * Q4.4.2:: How do I start the Sun Workshop support in XEmacs 21?
311 * Q4.5.1:: What is/was Energize?
314 * Q4.6.1:: What is Infodock?
316 Other Unbundled Packages:
317 * Q4.7.1:: What is AUC TeX? Where do you get it?
318 * Q4.7.2:: Are there any Emacs Lisp Spreadsheets?
319 * Q4.7.3:: Byte compiling AUC TeX on XEmacs 19.14
320 * Q4.7.4:: Problems installing AUC TeX
321 * Q4.7.5:: Is there a reason for an Emacs package not to be included in XEmacs?
322 * Q4.7.6:: Is there a MatLab mode?
324 The Miscellaneous Stuff
326 * Q5.0.1:: How can I do source code highlighting using font-lock?
327 * Q5.0.2:: I do not like cc-mode. How do I use the old c-mode?
328 * Q5.0.3:: How do I get @samp{More} Syntax Highlighting on by default?
329 * Q5.0.4:: How can I enable auto-indent?
330 * Q5.0.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
331 * Q5.0.6:: How do I start up a second shell buffer?
332 * Q5.0.7:: Telnet from shell filters too much.
333 * Q5.0.8:: Why does edt emulation not work?
334 * Q5.0.9:: How can I emulate VI and use it as my default mode?
335 * Q5.0.10:: [This question intentionally left blank]
336 * Q5.0.11:: Filladapt doesn't work in 19.15?
337 * Q5.0.12:: How do I disable gnuserv from opening a new frame?
338 * Q5.0.13:: How do I start gnuserv so that each subsequent XEmacs is a client?
339 * Q5.0.14:: Strange things are happening in Shell Mode.
340 * Q5.0.15:: Where do I get the latest CC Mode?
341 * Q5.0.16:: I find auto-show-mode disconcerting. How do I turn it off?
342 * Q5.0.17:: How can I get two instances of info?
343 * Q5.0.18:: I upgraded to XEmacs 19.14 and gnuserv stopped working
344 * Q5.0.19:: Is there something better than LaTeX mode?
345 * Q5.0.20:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
347 Emacs Lisp Programming Techniques:
348 * Q5.1.1:: The difference in key sequences between XEmacs and GNU Emacs?
349 * Q5.1.2:: Can I generate "fake" keyboard events?
350 * Q5.1.3:: Could you explain @code{read-kbd-macro} in more detail?
351 * Q5.1.4:: What is the performance hit of @code{let}?
352 * Q5.1.5:: What is the recommended use of @code{setq}?
353 * Q5.1.6:: What is the typical misuse of @code{setq} ?
354 * Q5.1.7:: I like the the @code{do} form of cl, does it slow things down?
355 * Q5.1.8:: I like recursion, does it slow things down?
356 * Q5.1.9:: How do I put a glyph as annotation in a buffer?
357 * Q5.1.10:: @code{map-extents} won't traverse all of my extents!
358 * Q5.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
361 * Q5.2.1:: How do I turn off the sound?
362 * Q5.2.2:: How do I get funky sounds instead of a boring beep?
363 * Q5.2.3:: What's NAS, how do I get it?
364 * Q5.2.4:: Sunsite sounds don't play.
367 * Q5.3.1:: How do you make XEmacs indent CL if-clauses correctly?
368 * Q5.3.2:: Fontifying hangs when editing a postscript file.
369 * Q5.3.3:: How can I print WYSIWYG a font-locked buffer?
370 * Q5.3.4:: Getting @kbd{M-x lpr} to work with postscript printer.
371 * Q5.3.5:: How do I specify the paths that XEmacs uses for finding files?
372 * Q5.3.6:: [This question intentionally left blank]
373 * Q5.3.7:: Can I have the end of the buffer delimited in some way?
374 * Q5.3.8:: How do I insert today's date into a buffer?
375 * Q5.3.9:: Are only certain syntactic character classes available for abbrevs?
376 * Q5.3.10:: How can I get those oh-so-neat X-Face lines?
377 * Q5.3.11:: How do I add new Info directories?
378 * Q5.3.12:: What do I need to change to make printing work?
380 What the Future Holds
382 * Q6.0.1:: What is new in 20.2?
383 * Q6.0.2:: What is new in 20.3?
384 * Q6.0.3:: What is new in 20.4?
385 * Q6.0.4:: Procedural changes in XEmacs development.
389 @node Introduction, Installation, Top, Top
390 @unnumbered 1 Introduction, Policy, Credits
392 Learning XEmacs is a lifelong activity. Even people who have used Emacs
393 for years keep discovering new features. Therefore this document cannot
394 be complete. Instead it is aimed at the person who is either
395 considering XEmacs for their own use, or has just obtained it and is
396 wondering what to do next. It is also useful as a reference to
399 The previous maintainer of the FAQ was @email{rossini@@stat.sc.edu,
400 Anthony Rossini}, who started it, after getting tired of hearing JWZ
401 complain about repeatedly having to answer questions.
402 @email{ben@@xemacs.org, Ben Wing} and @email{cthomp@@xemacs.org, Chuck
403 Thompson}, the principal authors of XEmacs, then took over and Ben did
404 a massive update reorganizing the whole thing. At which point Anthony
405 took back over, but then had to give it up again. Some of the other
406 contributors to this FAQ are listed later in this document.
408 The previous version was converted to hypertext format, and edited by
409 @email{steve@@xemacs.org, Steven L. Baur}. It was converted back to
410 texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}.
412 The FAQ was then maintained by @email{andreas@@sccon.com, Andreas
413 Kaempf}, who passed it on to @email{faq@@xemacs.org, Christian
414 Nyb@o{}}, the current FAQ maintainer.
416 If you notice any errors or items which should be added or amended to
417 this FAQ please send email to @email{faq@@xemacs.org, Christian
418 Nyb@o{}}. Include @samp{XEmacs FAQ} on the Subject: line.
422 * Q1.0.1:: What is XEmacs?
423 * Q1.0.2:: What is the current version of XEmacs?
424 * Q1.0.3:: Where can I find it?
425 * Q1.0.4:: Why Another Version of Emacs?
426 * Q1.0.5:: Why Haven't XEmacs and GNU Emacs Merged?
427 * Q1.0.6:: Where can I get help?
428 * Q1.0.7:: Where is the mailing list archived?
429 * Q1.0.8:: How do you pronounce XEmacs?
430 * Q1.0.9:: What does XEmacs look like?
431 * Q1.0.10:: Is there a port of XEmacs to Microsoft ('95 or NT)?
432 * Q1.0.11:: Is there a port of XEmacs to the Macintosh?
433 * Q1.0.12:: Is there a port of XEmacs to NextStep?
434 * Q1.0.13:: Is there a port of XEmacs to OS/2?
435 * Q1.0.14:: Where can I get a printed copy of the XEmacs users manual?
438 * Q1.1.1:: What is the FAQ editorial policy?
439 * Q1.1.2:: How do I become a Beta Tester?
440 * Q1.1.3:: How do I contribute to XEmacs itself?
443 * Q1.2.1:: Who wrote XEmacs?
444 * Q1.2.2:: Who contributed to this version of the FAQ?
445 * Q1.2.3:: Who contributed to the FAQ in the past?
447 Internationalization:
448 * Q1.3.1:: What is the status of XEmacs v20?
449 * Q1.3.2:: What is the status of Asian-language support, aka @var{mule}?
450 * Q1.3.3:: How do I type non-ASCII characters?
451 * Q1.3.4:: Can XEmacs messages come out in a different language?
452 * Q1.3.5:: Please explain the various input methods in MULE/XEmacs 20.0
453 * Q1.3.6:: How do I portably code for MULE/XEmacs 20.0?
454 * Q1.3.7:: How about Cyrillic Modes?
457 * Q1.4.1:: What is a @file{.emacs} and is there a sample one?
458 * Q1.4.2:: Can I use the same @file{.emacs} with the other Emacs?
459 * Q1.4.3:: Any good XEmacs tutorials around?
460 * Q1.4.4:: May I see an example of a useful XEmacs Lisp function?
461 * Q1.4.5:: And how do I bind it to a key?
462 * Q1.4.6:: What's the difference between a macro and a function?
463 * Q1.4.7:: Why options saved with 19.13 don't work with 19.14 or later?
466 @node Q1.0.1, Q1.0.2, Introduction, Introduction
467 @unnumberedsec 1.0: Introduction
468 @unnumberedsubsec Q1.0.1: What is XEmacs?
471 An alternative to GNU Emacs, originally based on an early alpha version
472 of FSF's version 19, and has diverged quite a bit since then. XEmacs
473 was known as Lucid Emacs through version 19.10. Almost all features of
474 GNU Emacs are supported in XEmacs. The maintainers of XEmacs actively
475 track changes to GNU Emacs while also working to add new features.
477 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction
478 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs?
480 XEmacs 20.4 is a minor upgrade from 20.3, containing many bugfixes. It
481 was released in February 1998.
483 XEmacs 19.16 was the last release of v19, released in November, 1997,
484 which was also the last version without international language support.
486 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction
487 @unnumberedsubsec Q1.0.3: Where can I find it?
489 The canonical source and binaries is found via anonymous FTP at:
492 @uref{ftp://ftp.xemacs.org/pub/xemacs/}
495 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction
496 @unnumberedsubsec Q1.0.4: Why Another Version of Emacs?
498 For a detailed description of the differences between GNU Emacs and
499 XEmacs and a detailed history of XEmacs, check out the
501 @uref{http://www.xemacs.org/NEWS.html, NEWS file}
504 However, here is a list of some of the reasons why we think you might
512 The XEmacs maintainers are generally more receptive to suggestions than
513 the GNU Emacs maintainers.
516 Many more bundled packages than GNU Emacs
519 Binaries are available for many common operating systems.
522 Face support on TTY's.
528 Better Motif compliance.
531 Some internationalization support (including full MULE support, if
535 Variable-width fonts.
538 Variable-height lines.
541 Marginal annotations.
547 XEmacs can be used as an Xt widget, and can be embedded within another
551 Horizontal and vertical scrollbars (using real toolkit scrollbars).
554 Better APIs (and performance) for attaching fonts, colors, and other
558 The ability to embed arbitrary graphics in a buffer.
561 Completely compatible (at the C level) with the Xt-based toolkits.
564 First production Web Browser supporting Style Sheets.
567 @node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
568 @unnumberedsubsec Q1.0.5: Why Haven't XEmacs and GNU Emacs Merged?
570 There are currently irreconcilable differences in the views about
571 technical, programming, design and organizational matters between RMS
572 and the XEmacs development team which provide little hope for a merge to
573 take place in the short-term future.
575 If you have a comment to add regarding the merge, it is a good idea to
576 avoid posting to the newsgroups, because of the very heated flamewars
577 that often result. Mail your questions to @email{xemacs-beta@@xemacs.org} and
578 @email{bug-gnu-emacs@@prep.ai.mit.edu}.
580 @node Q1.0.6, Q1.0.7, Q1.0.5, Introduction
581 @unnumberedsubsec Q1.0.6: Where can I get help?
583 Probably the easiest way, if everything is installed, is to use info, by
584 pressing @kbd{C-h i}, or selecting @code{Manuals->Info} from the Help Menu.
586 Also, @kbd{M-x apropos} will look for commands for you.
588 Try reading this FAQ, examining the regular GNU Emacs FAQ (which can be
589 found with the Emacs 19 distribution) as well as at
590 @uref{http://www.eecs.nwu.edu/emacs/faq/} and reading the Usenet group
593 If that does not help, try posting your question to comp.emacs.xemacs.
594 Please @strong{do not} post XEmacs related questions to gnu.emacs.help.
596 If you cannot post or read Usenet news, there is a corresponding mailing
597 list which is available. It can be subscribed to by sending a message
598 with a subject of @samp{subscribe} to @email{xemacs-request@@xemacs.org}
599 for subscription information and @email{xemacs@@xemacs.org} to send messages
602 To cancel a subscription, you @strong{must} use the xemacs-request
603 address. Send a message with a subject of @samp{unsubscribe} to be
606 @node Q1.0.7, Q1.0.8, Q1.0.6, Introduction
607 @unnumberedsubsec Q1.0.7: Where is the mailing list archived?
609 The mailing list was archived in the directory
611 @uref{ftp://ftp.xemacs.org/pub/mlists/}.
614 However, this archive is out of date. The current mailing list server
615 supports an @code{archive} feature, which may be utilized.
617 @node Q1.0.8, Q1.0.9, Q1.0.7, Introduction
618 @unnumberedsubsec Q1.0.8: How do you pronounce XEmacs?
620 I pronounce it @samp{Eks eemax}.
622 @node Q1.0.9, Q1.0.10, Q1.0.8, Introduction
623 @unnumberedsubsec Q1.0.9: What does XEmacs look like?
625 Screen snapshots are available in the WWW version of the FAQ.
627 @uref{http://www.xemacs.org/faq/xemacs-faq.html}
630 @node Q1.0.10, Q1.0.11, Q1.0.9, Introduction
631 @unnumberedsubsec Q1.0.10: Is there a port of XEmacs to Microsoft ('95 or NT)?
633 Thanks to efforts of many people, coordinated by
634 @email{davidh@@wr.com.au, David Hobley} and @email{marcpa@@cam.org, Marc
635 Paquette}, beta versions of XEmacs now run on 32-bit Windows platforms
636 (NT and 95). The current betas require having an X server to run
637 XEmacs; however, a native NT/95 port is in alpha, thanks to
638 @email{jhar@@tardis.ed.ac.uk, Jonathan Harris}.
640 Although some features are still unimplemented, XEmacs 21.0 will support
643 The NT development is now coordinated by a mailing list at
644 @email{xemacs-nt@@xemacs.org}.
646 If you are willing to contribute or want to follow the progress, mail to
650 @email{xemacs-nt-request@@xemacs.org} to subscribe.
652 Furthermore, Altrasoft is seeking corporate and government sponsors to
653 help fund a fully native port of XEmacs to Windows 95 and NT using
654 full-time, senior-level staff working under a professionally managed
655 project structure. See @uref{http://www.altrasoft.com/, the Altrasoft
656 web site} for more details
657 or contact Altrasoft directly at 1-888-ALTSOFT.
660 The closest existing port is @dfn{Win-Emacs}, which is based on Lucid
661 Emacs 19.6. Available from @uref{http://www.pearlsoft.com/}.
663 There's a port of GNU Emacs (not XEmacs) at
665 @uref{http://www.cs.washington.edu/homes/voelker/ntemacs.html}.
668 @node Q1.0.11, Q1.0.12, Q1.0.10, Introduction
669 @unnumberedsubsec Q1.0.11: Is there a port of XEmacs to the Macintosh?
672 There has been a port to the MachTen environment of XEmacs 19.13, but no
673 patches have been submitted to the maintainers to get this in the
674 mainstream distribution.
676 For the MacOS, there is a port of
677 @uref{ftp://ftp.cs.cornell.edu/pub/parmet/, Emacs 18.59}.
679 @node Q1.0.12, Q1.0.13, Q1.0.11, Introduction
680 @unnumberedsubsec Q1.0.12: Is there a port of XEmacs to NextStep?
682 Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did
683 the port of GNU Emacs to NeXTstep and expressed interest in doing the
684 XEmacs port, but never went any farther.
686 @node Q1.0.13, Q1.0.14, Q1.0.12, Introduction
687 @unnumberedsubsec Q1.0.13: Is there a port of XEmacs to OS/2?
689 No, and there is no news of anyone working on it.
691 @node Q1.0.14, Q1.1.1, Q1.0.13, Introduction
692 @unnumberedsubsec Q1.0.14: Where can I obtain a printed copy of the XEmacs users manual?
694 Altrasoft Associates, a firm specializing in Emacs-related support and
695 development, will be maintaining the XEmacs user manual. The firm plans
696 to begin publishing printed copies of the manual soon.
697 @c This used to say `March 1997'!
700 Web: @uref{http://www.xemacs.com}
701 E-mail: @email{info@@xemacs.com}
705 @node Q1.1.1, Q1.1.2, Q1.0.14, Introduction
706 @unnumberedsec 1.1: Policies
707 @unnumberedsubsec Q1.1.1: What is the FAQ editorial policy?
709 The FAQ is actively maintained and modified regularly. All links should
712 Changes are displayed on a monthly basis. @dfn{Months}, for this
713 purpose are defined as the 5th of the month through the 5th of the
714 month. Preexisting questions that have been changed are marked as such.
715 Brand new questions are tagged.
717 All submissions are welcome. E-mail submissions
722 @email{faq@@xemacs.org, Christian Nyb@o{}}.
724 Please make sure that @samp{XEmacs FAQ} appears on the Subject: line.
725 If you think you have a better way of answering a question, or think a
726 question should be included, I'd like to hear about it. Questions and
727 answers included into the FAQ will be edited for spelling and grammar,
728 and will be attributed. Answers appearing without attribution are
729 either from versions of the FAQ dated before May 1996, or are from one
730 of the four people listed at the top of this document. Answers quoted
731 from Usenet news articles will always be attributed, regardless of the
734 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
735 @unnumberedsubsec Q1.1.2: How do I become a Beta Tester?
737 Send an email message to @email{xemacs-beta-request@@xemacs.org} with a
738 subject line of @samp{subscribe}.
740 Be prepared to get your hands dirty, as beta testers are expected to
741 identify problems as best they can.
743 @node Q1.1.3, Q1.2.1, Q1.1.2, Introduction
744 @unnumberedsubsec Q1.1.3: How do I contribute to XEmacs itself?
746 Ben Wing @email{ben@@xemacs.org} writes:
749 BTW if you have a wish list of things that you want added, you have to
750 speak up about it! More specifically, you can do the following if you
751 want a feature added (in increasing order of usefulness):
755 Make a posting about a feature you want added.
758 Become a beta tester and make more postings about those same features.
761 Convince us that you're going to use the features in some cool and
765 Come up with a clear and well-thought-out API concerning the features.
768 Write the code to implement a feature and send us a patch.
771 (not that we're necessarily requiring you to write the code, but we can
775 @node Q1.2.1, Q1.2.2, Q1.1.3, Introduction
776 @unnumberedsec 1.2: Credits
777 @unnumberedsubsec Q1.2.1: Who wrote XEmacs?
779 XEmacs is the result of the time and effort of many people. The
780 developers responsible for the 19.16/20.x releases are:
783 @item @email{martin@@xemacs.org, Martin Buchholz}
785 <br><img src="mrb.jpeg" alt="Portrait of Martin Buchholz"><br>
789 @item @email{steve@@xemacs.org, Steve Baur}
792 <br><img src="steve.gif" alt="Portrait of Steve Baur"><br>
796 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
799 <br><img src="hniksic.jpeg" alt="Portrait of Hrvoje Niksic"><br>
804 The developers responsible for the 19.14 release are:
807 @item @email{cthomp@@xemacs.org, Chuck Thompson}
809 <br><img src="cthomp.jpeg" alt="Portrait of Chuck Thompson"><br>
812 Chuck was Mr. XEmacs from 19.11 through 19.14, and is responsible
813 for XEmacs becoming a widely distributed program over the Internet.
815 @item @email{ben@@xemacs.org, Ben Wing}
817 <br><img src="wing.gif" alt="Portrait of Ben Wing"><br>
824 @item @email{jwz@@jwz.org, Jamie Zawinski}
826 <br><img src="jwz.gif" alt="Portrait of Jamie Zawinski"><br>
829 Jamie Zawinski was Mr. Lucid Emacs from 19.0 through 19.10, the last
830 release actually named Lucid Emacs. Richard Mlynarik was crucial to
831 most of those releases.
833 @item @email{mly@@adoc.xerox.com, Richard Mlynarik}
836 Along with many other contributors, partially enumerated in the
837 @samp{About XEmacs} option in the Help menu.
839 @node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
840 @unnumberedsubsec Q1.2.2: Who contributed to this version of the FAQ?
842 The following people contributed valuable suggestions to building this
843 version of the FAQ (listed in alphabetical order):
846 @item @email{steve@@xemacs.org, SL Baur}
848 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
850 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
854 @node Q1.2.3, Q1.3.1, Q1.2.2, Introduction
855 @unnumberedsubsec Q1.2.3: Who contributed to the FAQ in the past?
857 This is only a partial list, as many names were lost in a hard disk
861 @item @email{binge@@aloft.att.com, Curtis.N.Bingham}
863 @item @email{rjc@@cogsci.ed.ac.uk, Richard Caley}
865 @item @email{cognot@@ensg.u-nancy.fr, Richard Cognot}
867 @item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque}
869 @item @email{eeide@@cs.utah.edu, Eric Eide}
871 @item @email{cflatter@@nrao.edu, Chris Flatters}
873 @item @email{ginsparg@@adra.com, Evelyn Ginsparg}
875 @item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall}
877 @item @email{dkindred@@cmu.edu, Darrell Kindred}
879 @item @email{dmoore@@ucsd.edu, David Moore}
881 @item @email{arup+@@cmu.edu, Arup Mukherjee}
883 @item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen}
885 @item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell}
887 @item @email{dworkin@@ccs.neu.edu, Justin Sheehy}
889 @item @email{stig@@hackvan.com, Stig}
891 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
894 @node Q1.3.1, Q1.3.2, Q1.2.3, Introduction
895 @unnumberedsec 1.3: Internationalization
896 @unnumberedsubsec Q1.3.1: What is the status of XEmacs v20?
898 XEmacs v20 is the version of XEmacs that includes MULE (Asian-language)
899 support. XEmacs 20.0 was released in February 1997, followed by XEmacs
900 20.2 in May, XEmacs 20.3 in November and XEmacs 20.4 in February 1998. When compiled without MULE
901 support, 20.4 is approximately as stable as 19.16, and probably faster
902 (due to additional optimization work.)
904 As of XEmacs 20.3, version 20 is @emph{the} supported version of
905 XEmacs. This means that 19.16 will optionally receive stability fixes
906 (if any), but that all the real development work will be done on the v20
909 The incompatible changes in XEmacs 20 include the additional byte-codes,
910 new primitive data types (@code{character}, @code{char-table}, and
911 @code{range-table}). This means that the character-integer equivalence
912 inherent to all the previous Emacs and XEmacs releases no longer
915 However, to avoid breaking old code, many functions that should normally
916 accept characters work with integers, and vice versa. For more
917 information, see the Lisp reference manual. Here is a relevant excerpt,
918 for your convenience.
921 In XEmacs version 19, and in all versions of FSF GNU Emacs, a
922 @dfn{character} in XEmacs Lisp is nothing more than an integer.
923 This is yet another holdover from XEmacs Lisp's derivation from
924 vintage-1980 Lisps; modern versions of Lisp consider this equivalence
925 a bad idea, and have separate character types. In XEmacs version 20,
926 the modern convention is followed, and characters are their own
927 primitive types. (This change was necessary in order for @sc{mule},
928 i.e. Asian-language, support to be correctly implemented.)
930 Even in XEmacs version 20, remnants of the equivalence between
931 characters and integers still exist; this is termed the @dfn{char-int
932 confoundance disease}. In particular, many functions such as @code{eq},
933 @code{equal}, and @code{memq} have equivalent functions (@code{old-eq},
934 @code{old-equal}, @code{old-memq}, etc.) that pretend like characters
935 are integers are the same. Byte code compiled under any version 19
936 Emacs will have all such functions mapped to their @code{old-} equivalents
937 when the byte code is read into XEmacs 20. This is to preserve
938 compatibility -- Emacs 19 converts all constant characters to the equivalent
939 integer during byte-compilation, and thus there is no other way to preserve
940 byte-code compatibility even if the code has specifically been written
941 with the distinction between characters and integers in mind.
943 Every character has an equivalent integer, called the @dfn{character
944 code}. For example, the character @kbd{A} is represented as the
945 @w{integer 65}, following the standard @sc{ascii} representation of
946 characters. If XEmacs was not compiled with @sc{mule} support, the
947 range of this integer will always be 0 to 255 -- eight bits, or one
948 byte. (Integers outside this range are accepted but silently truncated;
949 however, you should most decidedly @emph{not} rely on this, because it
950 will not work under XEmacs with @sc{mule} support.) When @sc{mule}
951 support is present, the range of character codes is much
952 larger. (Currently, 19 bits are used.)
954 FSF GNU Emacs uses kludgy character codes above 255 to represent
955 keyboard input of @sc{ascii} characters in combination with certain
956 modifiers. XEmacs does not use this (a more general mechanism is
957 used that does not distinguish between @sc{ascii} keys and other
958 keys), so you will never find character codes above 255 in a
959 non-@sc{mule} XEmacs.
961 Individual characters are not often used in programs. It is far more
962 common to work with @emph{strings}, which are sequences composed of
966 @node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
967 @unnumberedsubsec Q1.3.2: What is the status of Asian-language support, aka MULE?
969 The MULE support works OK but still needs a fair amount of work before
970 it's really solid. We could definitely use some help here, esp. people
971 who speak Japanese and will use XEmacs/MULE to work with Japanese and
972 have some experience with E-Lisp.
974 As the fundings on Mule have stopped, the Mule part of XEmacs is currently
975 looking for a full-time maintainer. If you can provide help here, or
976 are willing to fund the work, please mail to @email{xemacs-beta@@xemacs.org}.
980 @node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
981 @unnumberedsubsec Q1.3.3: How do I type non-ASCII characters?
983 See question 3.5.7 (@pxref{Q3.5.7}) in part 3 of this FAQ.
985 @node Q1.3.4, Q1.3.5, Q1.3.3, Introduction
986 @unnumberedsubsec Q1.3.4: Can XEmacs messages come out in a different language?
988 The message-catalog support has mostly been written but doesn't
989 currently work. The first release of XEmacs 20 will @emph{not} support
990 it. However, menubar localization @emph{does} work, even in 19.14. To
991 enable it, add to your @file{Emacs} file entries like this:
994 Emacs*XlwMenu.resourceLabels: True
995 Emacs*XlwMenu.file.labelString: Fichier
996 Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster offnen
999 The name of the resource is derived from the non-localized entry by
1000 removing punctuation and capitalizing as above.
1002 @node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
1003 @unnumberedsubsec Q1.3.5: Please explain the various input methods in MULE/XEmacs 20.0
1005 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
1008 Original Mule supports the following input methods: Wnn4, Wnn6, Canna, SJ3
1009 and XIM. Interfaces for Wnn and SJ3 uses the @code{egg} user
1010 interface. Interface for Canna does not use @samp{egg}. I don't know
1011 about XIM. It is to support ATOK, of course, it may work for another
1014 Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
1015 university. It is a powerful and complex system. Wnn4 is free and Wnn6
1018 Canna supports only Japanese. It is made by NEC. It is a simple and
1019 powerful system. Canna uses only grammar (Wnn uses grammar and
1020 probability between words), so I think Wnn is cleverer than Canna,
1021 however Canna users made a good grammar and dictionary. So for standard
1022 modern Japanese, Canna seems cleverer than Wnn4. In addition, the UNIX
1023 version of Canna is free (now there is a Microsoft Windows version).
1025 SJ3 supports only Japanese. It is made by Sony. XIM supports was made
1026 to use ATOK (a major input method in personal computer world). XIM is
1027 the standard for accessing input methods bundled in Japanese versions of
1028 Solaris. (XEmacs 20 will support XIM input).
1030 Egg consists of following parts:
1034 Input character Translation System (ITS) layer.
1035 It translates ASCII inputs to Kana/PinYin/Hangul characters.
1038 Kana/PinYin/Hangul to Kanji transfer layer.
1039 It is interface layer for network Kana-Kanji server (Wnn and Sj3).
1042 These input methods are modal, namely there are mode, alphabet mode and
1043 Kana-Kanji transfer mode. However there are mode-less input methods for
1044 Egg and Canna. @samp{Boiled-egg} is a mode-less input method running on
1045 Egg. For Canna, @samp{canna.el} has a tiny boiled-egg like command,
1046 @code{(canna-boil)}, and there are some boiled-egg like utilities. In
1047 addition, it was planned to make an abstraction for all transfer type
1048 input methods. However authors of input methods are busy, so maybe this
1049 plan is stopped. Perhaps after Mule merged GNU Emacs will be released,
1050 it will be continued.
1053 @node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
1054 @unnumberedsubsec Q1.3.6: How do I portably code for MULE/XEmacs 20?
1056 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
1059 MULE and XEmacs are quite different. So the application
1060 implementor must write separate code for these mule variants.
1062 MULE and the next version of Emacs are similar but the symbols are very
1063 different---requiring separate code as well.
1065 Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of
1066 emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called
1067 @code{emu} to provide a common interface.
1069 I have the following suggestions about dealing with mule variants:
1073 @code{(featurep 'mule)} @code{t} on all mule variants
1076 @code{(boundp 'MULE)} is @code{t} on only MULE. Maybe the next version
1077 of Emacs will not have this symbol.
1080 MULE has a variable @code{mule-version}. Perhaps the next version of
1081 Emacs will have this variable as well.
1084 Following is a sample to distinguish mule variants:
1087 (if (featurep 'mule)
1088 (cond ((boundp 'MULE)
1089 ;; for original Mule
1091 ((string-match "XEmacs" emacs-version)
1092 ;; for XEmacs with Mule
1095 ;; for next version of Emacs
1097 ;; for old emacs variants
1102 @node Q1.3.7, Q1.4.1, Q1.3.6, Introduction
1103 @unnumberedsubsec Q1.3.7: How about Cyrillic Modes?
1105 @email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes:
1108 There is a cyrillic mode in the file @file{mysetup.zip} in
1112 @uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}. This is a
1113 modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el}
1114 which can be obtained from
1117 @uref{http://ftpsearch.ntnu.no/?query=russian.el.Z}.
1120 @email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes:
1123 There is another cyrillic mode for both GNU Emacs and XEmacs by
1124 @email{manin@@camelot.mssm.edu, Dmitrii
1129 @uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}.
1130 @c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead.
1131 @c Changed to russian host instead
1134 @email{rebecca.ore@@op.net, Rebecca Ore} writes:
1137 The fullest resource I found on Russian language use (in and out of
1138 XEmacs) is @uref{http://sunsite.oit.unc.edu/sergei/Software/Software.html}
1141 @node Q1.4.1, Q1.4.2, Q1.3.7, Introduction
1142 @unnumberedsec 1.4: Getting Started, Backing up & Recovery
1143 @unnumberedsubsec Q1.4.1: What is a @file{.emacs} and is there a sample one?
1145 The @file{.emacs} file is used to customize XEmacs to your tastes. No
1146 two are alike, nor are they expected to be alike, but that's the point.
1147 The XEmacs distribution contains an excellent starter example in the etc
1148 directory called @file{sample.emacs}. Copy this file from there to your
1149 home directory and rename it @file{.emacs}. Then edit it to suit.
1151 Starting with 19.14, you may bring the @file{sample.emacs} into an
1152 XEmacs buffer by selecting @samp{Help->Sample .emacs} from the menubar.
1153 To determine the location of the @file{etc} directory type the command
1154 @kbd{C-h v data-directory @key{RET}}.
1156 @node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
1157 @unnumberedsubsec Q1.4.2: Can I use the same @file{.emacs} with the other Emacs?
1159 Yes. The sample @file{.emacs} included in the XEmacs distribution will
1160 show you how to handle different versions and flavors of Emacs.
1162 @node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
1163 @unnumberedsubsec Q1.4.3: Any good tutorials around?
1165 There's the XEmacs tutorial available from the Help Menu under
1166 @samp{Basics->Tutorials}, or by typing @kbd{C-h t}. To check whether
1167 it's available in a non-english language, type @kbd{C-u C-h t TAB}, type
1168 the first letters of your preferred language, then type @key{RET}.
1170 There's an Emacs Lisp tutorial at
1173 @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
1176 @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
1181 @uref{http://petaxp.rug.ac.be/~erik/xemacs/}.
1183 @node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
1184 @unnumberedsubsec Q1.4.4: May I see an example of a useful XEmacs Lisp function?
1186 The following function does a little bit of everything useful. It does
1187 something with the prefix argument, it examines the text around the
1188 cursor, and it's interactive so it may be bound to a key. It inserts
1189 copies of the current word the cursor is sitting on at the cursor. If
1190 you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will
1194 (defun double-word (count)
1195 "Insert a copy of the current word underneath the cursor"
1197 (let (here there string)
1202 (setq there (point))
1203 (setq string (buffer-substring here there)))
1209 The best way to see what is going on here is to let XEmacs tell you.
1210 Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor
1211 sitting just to the right of the function you want explained. Eg. move
1212 the cursor to the SPACE between @code{interactive} and @samp{"*p"} and
1213 hit @kbd{C-h f} to see what the function @code{interactive} does. Doing
1214 this will tell you that the @code{*} requires a writable buffer, and
1215 @code{p} converts the prefix argument to a number, and
1216 @code{interactive} allows you to execute the command with @kbd{M-x}.
1218 @node Q1.4.5, Q1.4.6, Q1.4.4, Introduction
1219 @unnumberedsubsec Q1.4.5: And how do I bind it to a key?
1221 To bind to a key do:
1224 (global-set-key "\C-cd" 'double-word)
1227 Or interactively, @kbd{M-x global-set-key} and follow the prompts.
1229 @node Q1.4.6, Q1.4.7, Q1.4.5, Introduction
1230 @unnumberedsubsec Q1.4.6: What's the difference between a macro and a function?
1232 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual:
1234 @dfn{Macros} enable you to define new control constructs and other
1235 language features. A macro is defined much like a function, but instead
1236 of telling how to compute a value, it tells how to compute another Lisp
1237 expression which will in turn compute the value. We call this
1238 expression the @dfn{expansion} of the macro.
1240 Macros can do this because they operate on the unevaluated expressions
1241 for the arguments, not on the argument values as functions do. They can
1242 therefore construct an expansion containing these argument expressions
1245 Do not confuse the two terms with @dfn{keyboard macros}, which are
1246 another matter, entirely. A keyboard macro is a key bound to several
1247 other keys. Refer to manual for details.
1249 @node Q1.4.7, , Q1.4.6, Introduction
1250 @unnumberedsubsec Q1.4.7: How come options saved with 19.13 don't work with 19.14 or later?
1252 There's a problem with options of the form:
1255 (add-spec-list-to-specifier (face-property 'searchm-field 'font)
1259 saved by a 19.13 XEmacs that causes a 19.14 XEmacs grief. You must
1260 delete these options. XEmacs 19.14 and later no longer write the
1261 options directly to @file{.emacs} which should allow us to deal with
1262 version incompatibilities better in the future.
1264 Options saved under XEmacs 19.13 are protected by code that specifically
1265 requires a version 19 XEmacs. This won't be a problem unless you're
1266 using XEmacs v20. You should consider changing the code to read:
1270 ((and (string-match "XEmacs" emacs-version)
1271 (boundp 'emacs-major-version)
1272 (or (and (= emacs-major-version 19)
1273 (>= emacs-minor-version 12))
1274 (>= emacs-major-version 20)))
1279 @node Installation, Customization, Introduction, Top
1280 @unnumbered 2 Installation and Trouble Shooting
1282 This is part 2 of the XEmacs Frequently Asked Questions list. This
1283 section is devoted to Installation, Maintenance and Trouble Shooting.
1287 * Q2.0.1:: Running XEmacs without installing.
1288 * Q2.0.2:: XEmacs is too big.
1289 * Q2.0.3:: Compiling XEmacs with Netaudio.
1290 * Q2.0.4:: Problems with Linux and ncurses.
1291 * Q2.0.5:: Do I need X11 to run XEmacs?
1292 * Q2.0.6:: I'm having strange crashes. What do I do?
1293 * Q2.0.7:: Libraries in non-standard locations.
1294 * Q2.0.8:: can't resolve symbol _h_errno
1295 * Q2.0.9:: Where do I find external libraries?
1296 * Q2.0.10:: After I run configure I find a coredump, is something wrong?
1297 * Q2.0.11:: XEmacs can't resolve host names.
1298 * Q2.0.12:: Why can't I strip XEmacs?
1299 * Q2.0.13:: Can't link XEmacs on Solaris with Gcc.
1300 * Q2.0.14:: Make on HP/UX 9 fails after linking temacs
1303 * Q2.1.1:: XEmacs just crashed on me!
1304 * Q2.1.2:: Cryptic Minibuffer messages.
1305 * Q2.1.3:: Translation Table Syntax messages at Startup.
1306 * Q2.1.4:: Startup warnings about deducing proper fonts?
1307 * Q2.1.5:: XEmacs cannot connect to my X Terminal.
1308 * Q2.1.6:: XEmacs just locked up my Linux X server.
1309 * Q2.1.7:: HP Alt key as Meta.
1310 * Q2.1.8:: got (wrong-type-argument color-instance-p nil)!
1311 * Q2.1.9:: XEmacs causes my OpenWindows 3.0 server to crash.
1312 * Q2.1.10:: Warnings from incorrect key modifiers.
1313 * Q2.1.11:: Can't instantiate image error... in toolbar
1314 * Q2.1.12:: Regular Expression Problems on DEC OSF1.
1315 * Q2.1.13:: HP/UX 10.10 and @code{create_process} failure
1316 * Q2.1.14:: @kbd{C-g} doesn't work for me. Is it broken?
1317 * Q2.1.15:: How to debug an XEmacs problem with a debugger.
1318 * Q2.1.16:: XEmacs crashes in @code{strcat} on HP/UX 10.
1319 * Q2.1.17:: @samp{Marker does not point anywhere}.
1320 * Q2.1.18:: 19.14 hangs on HP/UX 10.10.
1321 * Q2.1.19:: XEmacs does not follow the local timezone.
1322 * Q2.1.20:: @samp{Symbol's function definition is void: hkey-help-show.}
1323 * Q2.1.21:: Every so often the XEmacs frame freezes.
1324 * Q2.1.22:: XEmacs seems to take a really long time to do some things.
1325 * Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
1328 @node Q2.0.1, Q2.0.2, Installation, Installation
1329 @unnumberedsec 2.0: Installation
1330 @unnumberedsubsec Q2.0.1: Running XEmacs without installing
1331 The @file{INSTALL} file says that up to 108 MB of space is needed
1332 temporarily during installation! How can I just try it out?
1334 XEmacs will run in place without requiring installation and copying of
1335 the Lisp directories, and without having to specify a special build-time
1336 flag. It's the copying of the Lisp directories that requires so much
1337 space. XEmacs is largely written in Lisp.
1339 A good method is to make a shell alias for xemacs:
1342 alias xemacs=/i/xemacs-20.2/src/xemacs
1345 (You will obviously use whatever directory you downloaded the source
1346 tree to instead of @file{/i/xemacs-20.2}).
1348 This will let you run XEmacs without massive copying.
1350 @node Q2.0.2, Q2.0.3, Q2.0.1, Installation
1351 @unnumberedsubsec Q2.0.2: XEmacs is too big
1353 Although this entry has been written for XEmacs 19.13, most of it still
1356 @email{steve@@xemacs.org, Steve Baur} writes:
1359 The 45MB of space required by the installation directories can be
1360 reduced dramatically if desired. Gzip all the .el files. Remove all
1361 the packages you'll never want to use (or even ones you do like the two
1362 obsolete mailcrypts and Gnus 4 in 19.13). Remove the TexInfo manuals.
1363 Remove the Info (and use just hardcopy versions of the manual). Remove
1364 most of the stuff in etc. Remove or gzip all the source code. Gzip or
1365 remove the C source code. Configure it so that copies are not made of
1366 the support lisp. I'm not advocating any of these things, just pointing
1367 out ways to reduce the disk requirements if desired.
1369 Now examine the space used by directory:
1372 0 /usr/local/bin/xemacs
1373 2048 /usr/local/bin/xemacs-19.13
1375 1546 /usr/local/lib/xemacs-19.13/i486-miranova-sco3.2v4.2
1376 1158 /usr/local/lib/xemacs-19.13/i486-unknown-linux1.2.13
1379 You need to keep these. XEmacs isn't stripped by default in
1380 installation, you should consider stripping. That will save you about
1384 207 /usr/local/lib/xemacs-19.13/etc/w3
1385 122 /usr/local/lib/xemacs-19.13/etc/sounds
1386 18 /usr/local/lib/xemacs-19.13/etc/sparcworks
1387 159 /usr/local/lib/xemacs-19.13/etc/vm
1388 6 /usr/local/lib/xemacs-19.13/etc/e
1389 21 /usr/local/lib/xemacs-19.13/etc/eos
1390 172 /usr/local/lib/xemacs-19.13/etc/toolbar
1391 61 /usr/local/lib/xemacs-19.13/etc/ns
1392 43 /usr/local/lib/xemacs-19.13/etc/gnus
1395 These are support directories for various packages. In general they
1396 match a directory under ./xemacs-19.13/lib/xemacs-19.13/lisp/. If you
1397 do not require the package, you may delete or gzip the support too.
1400 1959 /usr/local/lib/xemacs-19.13/etc
1401 175 /usr/local/lib/xemacs-19.13/lisp/bytecomp
1402 340 /usr/local/lib/xemacs-19.13/lisp/calendar
1403 342 /usr/local/lib/xemacs-19.13/lisp/comint
1404 517 /usr/local/lib/xemacs-19.13/lisp/dired
1405 42 /usr/local/lib/xemacs-19.13/lisp/electric
1406 212 /usr/local/lib/xemacs-19.13/lisp/emulators
1407 238 /usr/local/lib/xemacs-19.13/lisp/energize
1408 289 /usr/local/lib/xemacs-19.13/lisp/gnus
1409 457 /usr/local/lib/xemacs-19.13/lisp/ilisp
1410 1439 /usr/local/lib/xemacs-19.13/lisp/modes
1411 2276 /usr/local/lib/xemacs-19.13/lisp/packages
1412 1040 /usr/local/lib/xemacs-19.13/lisp/prim
1413 176 /usr/local/lib/xemacs-19.13/lisp/pcl-cvs
1414 154 /usr/local/lib/xemacs-19.13/lisp/rmail
1415 3 /usr/local/lib/xemacs-19.13/lisp/epoch
1416 45 /usr/local/lib/xemacs-19.13/lisp/term
1417 860 /usr/local/lib/xemacs-19.13/lisp/utils
1418 851 /usr/local/lib/xemacs-19.13/lisp/vm
1419 13 /usr/local/lib/xemacs-19.13/lisp/vms
1420 157 /usr/local/lib/xemacs-19.13/lisp/x11
1421 19 /usr/local/lib/xemacs-19.13/lisp/tooltalk
1422 14 /usr/local/lib/xemacs-19.13/lisp/sunpro
1423 291 /usr/local/lib/xemacs-19.13/lisp/games
1424 198 /usr/local/lib/xemacs-19.13/lisp/edebug
1425 619 /usr/local/lib/xemacs-19.13/lisp/w3
1426 229 /usr/local/lib/xemacs-19.13/lisp/eos
1427 55 /usr/local/lib/xemacs-19.13/lisp/iso
1428 59 /usr/local/lib/xemacs-19.13/lisp/mailcrypt
1429 187 /usr/local/lib/xemacs-19.13/lisp/eterm
1430 356 /usr/local/lib/xemacs-19.13/lisp/ediff
1431 408 /usr/local/lib/xemacs-19.13/lisp/hyperbole/kotl
1432 1262 /usr/local/lib/xemacs-19.13/lisp/hyperbole
1433 247 /usr/local/lib/xemacs-19.13/lisp/hm--html-menus
1434 161 /usr/local/lib/xemacs-19.13/lisp/mh-e
1435 299 /usr/local/lib/xemacs-19.13/lisp/viper
1436 53 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-x
1437 4 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/DocWindow.nib
1438 3 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/InfoPanel.nib
1439 3 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/TreeView.nib
1440 11 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj
1441 53 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx
1442 466 /usr/local/lib/xemacs-19.13/lisp/oobr
1443 14142 /usr/local/lib/xemacs-19.13/lisp
1446 These are all Emacs Lisp source code and bytecompiled object code. You
1447 may safely gzip everything named *.el here. You may remove any package
1448 you don't use. @emph{Nothing bad will happen if you delete a package
1449 that you do not use}. You must be sure you do not use it though, so be
1450 conservative at first.
1452 Possible candidates for deletion include w3 (newer versions exist, or
1453 you may just use Lynx or Netscape for web browsing), games, hyperbole,
1454 mh-e, hm--html-menus (better packages exist), vm, viper, oobr, gnus (new
1455 versions exist), etc. Ask yourself, @emph{Do I ever want to use this
1456 package?} If the answer is no, then it is a candidate for removal.
1458 First, gzip all the .el files. Then go about package by package and
1459 start gzipping the .elc files. Then run XEmacs and do whatever it is
1460 you normally do. If nothing bad happens, then delete the directory. Be
1461 conservative about deleting directories, and it would be handy to have a
1462 backup tape around in case you get too zealous.
1464 @file{prim}, @file{modes}, @file{packages}, and @file{utils} are four
1465 directories you definitely do @strong{not} want to delete, although
1466 certain packages can be removed from them if you do not use them.
1469 1972 /usr/local/lib/xemacs-19.13/info
1472 These are online texinfo sources. You may either gzip them or remove
1473 them. In either case, @kbd{C-h i} (info mode) will no longer work.
1476 20778 /usr/local/lib/xemacs-19.13
1479 The 20MB achieved is less than half of what the full distribution takes up,
1480 @strong{and} can be achieved without deleting a single file.
1483 @email{boffi@@hp735.stru.polimi.it, Giacomo Boffi} provides this procedure:
1486 Substitute @file{/usr/local/lib/} with the path where the xemacs tree is
1487 rooted, then use this script:
1492 r=/usr/local/lib/xemacs-19.13/lisp
1494 cd $r ; rm -f cmpr ; touch cmpr
1499 if test -d $d ; then
1502 # compress (remove) only (ONLY) the sources that have a
1503 # corresponding compiled file --- do not (DO NOT)
1504 # touch other sources
1505 if test -f $@{f@}c ; then gzip -v9 $f >> $r/cmpr ; fi
1514 A step beyond would be substituting @samp{rm -f} for @samp{gzip -v9},
1515 but you have to be desperate for removing the sources (remember that
1516 emacs can access compressed files transparently).
1518 Also, a good megabyte could easily be trimmed from the $r/../etc
1519 directory, e.g., the termcap files, some O+NEWS, others that I don't
1524 XEmacs 21.0 will unbundle the lisp hierarchy and allow the installer
1525 to choose exactly how much support code gets installed.
1528 @node Q2.0.3, Q2.0.4, Q2.0.2, Installation
1529 @unnumberedsubsec Q2.0.3: Compiling XEmacs with Netaudio.
1531 What is the best way to compile XEmacs with the netaudio system, since I
1532 have got the netaudio system compiled but installed at a weird place, I
1533 am not root. Also in the READMEs it does not say anything about
1534 compiling with the audioserver?
1536 You should only need to add some stuff to the configure command line.
1537 To tell it to compile in netaudio support: @samp{--with-sound=both}, or
1538 @samp{--with-sound=nas} if you don't want native sound support for some
1539 reason.) To tell it where to find the netaudio includes and libraries:
1542 --site-libraries=WHATEVER
1543 --site-includes=WHATEVER
1546 Then (fingers crossed) it should compile and it will use netaudio if you
1547 have a server running corresponding to the X server. The netaudio server
1548 has to be there when XEmacs starts. If the netaudio server goes away and
1549 another is run, XEmacs should cope (fingers crossed, error handling in
1550 netaudio isn't perfect).
1552 BTW, netaudio has been renamed as it has a name clash with something
1553 else, so if you see references to NAS or Network Audio System, it's the
1554 same thing. It also might be found at
1555 @uref{ftp://ftp.x.org/contrib/audio/nas/}.
1557 @node Q2.0.4, Q2.0.5, Q2.0.3, Installation
1558 @unnumberedsubsec Q2.0.4: Problems with Linux and ncurses.
1560 On Linux 1.3.98 with termcap 2.0.8 and the ncurses that came with libc
1561 5.2.18, XEmacs 20.0b20 is unable to open a tty device:
1565 Initialization error:
1569 Terminal type `xterm' undefined (or can't access database?)
1572 @email{ben@@xemacs.org, Ben Wing} writes:
1575 Your ncurses configuration is messed up. Your /usr/lib/terminfo is a
1576 bad pointer, perhaps to a CD-ROM that is not inserted.
1579 @node Q2.0.5, Q2.0.6, Q2.0.4, Installation
1580 @unnumberedsubsec Q2.0.5: Do I need X11 to run XEmacs?
1582 No. The name @dfn{XEmacs} is unfortunate in the sense that it is
1583 @strong{not} an X Window System-only version of Emacs. Starting with
1584 19.14 XEmacs has full color support on a color-capable character
1587 @node Q2.0.6, Q2.0.7, Q2.0.5, Installation
1588 @unnumberedsubsec Q2.0.6: I'm having strange crashes. What do I do?
1590 There have been a variety of reports of crashes due to compilers with
1591 buggy optimizers. Please see the @file{PROBLEMS} file that comes with
1592 XEmacs to read what it says about your platform.
1594 @node Q2.0.7, Q2.0.8, Q2.0.6, Installation
1595 @unnumberedsubsec Q2.0.7: Libraries in non-standard locations
1597 I have x-faces, jpeg, xpm etc. all in different places. I've tried
1598 space-separated, comma-separated, several --site-libraries, all to no
1602 --site-libraries='/path/one /path/two /path/etc'
1605 @node Q2.0.8, Q2.0.9, Q2.0.7, Installation
1606 @unnumberedsubsec Q2.0.8: can't resolve symbol _h_errno
1608 You are using the Linux/ELF distribution of XEmacs 19.14, and your ELF
1609 libraries are out of date. You have the following options:
1613 Upgrade your libc to at least 5.2.16 (better is 5.2.18, 5.3.12, or
1617 Patch the XEmacs binary by replacing all occurrences of
1618 @samp{_h_errno^@@} with
1622 @samp{h_errno^@@^@@}. Any version of Emacs will
1623 suffice. If you don't understand how to do this, don't do it.
1626 Rebuild XEmacs yourself -- any working ELF version of libc should be
1630 @email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
1633 Why not use a Perl one-liner for No. 2?
1636 perl -pi -e 's/_h_errno\0/h_errno\0\0/g' \
1637 /usr/local/bin/xemacs-19.14
1640 NB: You @emph{must} patch @file{/usr/local/bin/xemacs-19.14}, and not
1641 @file{xemacs} because @file{xemacs} is a link to @file{xemacs-19.14};
1642 the Perl @samp{-i} option will cause unwanted side-effects if applied to
1646 @email{steve@@xemacs.org, SL Baur} writes:
1649 If you build against a recent libc-5.4 (late enough to have caused
1650 problems earlier in the beta cycle) and then run with an earlier version
1655 xemacs: can't resolve symbol '__malloc_hook'
1656 zsh: 7942 segmentation fault (core dumped) xemacs
1659 (Example binary compiled against libc-5.4.23 and run with libc-5.4.16).
1661 The solution is to upgrade to at least libc-5.4.23. Sigh. Drat.
1664 @node Q2.0.9, Q2.0.10, Q2.0.8, Installation
1665 @unnumberedsubsec Q2.0.9: Where do I find external libraries?
1667 All external libraries used by XEmacs can be found at the XEmacs FTP
1672 @uref{ftp://ftp.xemacs.org/pub/xemacs/aux/}.
1674 @c Changed June Link above, <URL:ftp://ftp.xemacs.org/pub/aux/> was dead.
1675 @c This list is a pain in the you-know-what to keep in synch with the
1677 The canonical locations (at the time of this writing) are as follows:
1681 @uref{ftp://ftp.uu.net/graphics/jpeg/}. Version 6a is current.
1682 @c Check from host with legal IP address
1684 @uref{ftp://ftp.x.org/contrib/libraries/}. Version 3.4j is current.
1685 Older versions of this package are known to cause XEmacs crashes.
1688 @uref{ftp://ftp.sgi.com/graphics/tiff/}. v3.4 is current. The latest
1689 beta is v3.4b035. There is a HOWTO here.
1692 @uref{ftp://ftp.uu.net/graphics/png/}. 0.89c is current. XEmacs
1693 requires a fairly recent version to avoid using temporary files.
1694 @c Check from host with legal IP address
1696 @uref{ftp://swrinde.nde.swri.edu/pub/png/src/}
1699 @uref{ftp://ftp.cs.indiana.edu/pub/faces/compface/}. This library has
1700 been frozen for about 6 years, and is distributed without version
1701 numbers. @emph{It should be compiled with the same options that X11 was
1702 compiled with on your system}. The version of this library at
1703 XEmacs.org includes the @file{xbm2xface.pl} script, written by
1704 @email{stig@@hackvan.com}, which may be useful when generating your own xface.
1707 @uref{ftp://ftp.x.org/contrib/audio/nas/}.
1708 Version 1.2p5 is current. There is a FAQ here.
1711 @node Q2.0.10, Q2.0.11, Q2.0.9, Installation
1712 @unnumberedsubsec Q2.0.10: After I run configure I find a core dump, is something wrong?
1714 Not necessarily. If you have GNU sed 3.0 you should downgrade it to
1715 2.05. From the @file{README} at prep.ai.mit.edu:
1718 sed 3.0 has been withdrawn from distribution. It has major revisions,
1719 which mostly seem to be improvements; but it turns out to have bugs too
1720 which cause trouble in some common cases.
1722 Tom Lord won't be able to work fixing the bugs until May. So in the
1723 mean time, we've decided to withdraw sed 3.0 from distribution and make
1724 version 2.05 once again the recommended version.
1727 It has also been observed that the vfork test on Solaris will leave a
1730 @node Q2.0.11, Q2.0.12, Q2.0.10, Installation
1731 @unnumberedsubsec Q2.0.11: XEmacs doesn't resolve hostnames.
1733 This is the result of a long-standing problem with SunOS and the fact
1734 that stock SunOS systems do not ship with DNS resolver code in libc.
1736 @email{ckd@@loiosh.kei.com, Christopher Davis} writes:
1739 That's correct [The SunOS 4.1.3 precompiled binaries don't do name
1740 lookup]. Since Sun figured that everyone used NIS to do name lookups
1741 (that DNS thing was apparently only a passing fad, right?), the stock
1742 SunOS 4.x systems don't have DNS-based name lookups in libc.
1744 This is also why Netscape ships two binaries for SunOS 4.1.x.
1746 The best solution is to compile it yourself; the configure script will
1747 check to see if you've put DNS in the shared libc and will then proceed
1748 to link against the DNS resolver library code.
1751 @node Q2.0.12, Q2.0.13, Q2.0.11, Installation
1752 @unnumberedsubsec Q2.0.12: Why can't I strip XEmacs?
1754 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:
1757 Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The
1758 link gives you a bare-boned emacs (called temacs). temacs is then run,
1759 preloading some of the lisp files. The result is then dumped into a new
1760 executable, named xemacs, which will contain all of the preloaded lisp
1763 Now, during the dump itself, the executable (code+data+symbols) is
1764 written on disk using a special unexec() function. This function is
1765 obviously heavily system dependent. And on some systems, it leads to an
1766 executable which, although valid, cannot be stripped without damage. If
1767 memory serves, this is especially the case for AIX binaries. On other
1768 architecture it might work OK.
1770 The Right Way to strip the emacs binary is to strip temacs prior to
1771 dumping xemacs. This will always work, although you can do that only if
1772 you install from sources (as temacs is @file{not} part of the binary
1776 @email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes:
1783 [ ./configure; make ]
1795 cp src/xemacs /usr/local/bin/xemacs
1798 cp lib-src/DOC-19.16-XEmacs
1802 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
1806 @node Q2.0.13, Q2.0.14, Q2.0.12, Installation
1807 @unnumberedsubsec Q2.0.13: Problems linking with Gcc on Solaris
1809 There are known difficulties linking with Gnu ld on Solaris. A typical
1810 error message might look like:
1813 unexec(): dlopen(../dynodump/dynodump.so): ld.so.1: ./temacs:
1814 fatal: relocation error:
1815 symbol not found: main: referenced in ../dynodump/dynodump.so
1818 @email{martin@@xemacs.org, Martin Buchholz} writes:
1821 You need to specify @samp{-fno-gnu-linker} as part of your flags to pass
1822 to ld. Future releases of XEmacs will try to do this automatically.
1825 @node Q2.0.14, Q2.1.1, Q2.0.13, Installation
1826 @unnumberedsubsec Q2.0.14: Make on HP/UX 9 fails after linking temacs
1828 Problem when building xemacs-19.16 on hpux 9:
1830 @email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
1833 make on hpux fails after linking temacs with a message:
1836 "make: don't know how to make .y."
1839 Solution: This is a problem with HP make revision 70.X. Either use GNU
1840 make, or install PHCO_6552, which will bring make to revision
1845 @node Q2.1.1, Q2.1.2, Q2.0.14, Installation
1846 @unnumberedsec 2.1: Trouble Shooting
1847 @unnumberedsubsec Q2.1.1: Help! XEmacs just crashed on me!
1849 First of all, don't panic. Whenever XEmacs crashes, it tries extremely
1850 hard to auto-save all of your files before dying. (The main time that
1851 this will not happen is if the machine physically lost power or if you
1852 killed the XEmacs process using @code{kill -9}). The next time you try
1853 to edit those files, you will be informed that a more recent auto-save
1854 file exists. You can use @kbd{M-x recover-file} to retrieve the
1855 auto-saved version of the file.
1857 Starting with 19.14, you may use the command @kbd{M-x recover-session}
1858 after a crash to pick up where you left off.
1860 Now, XEmacs is not perfect, and there may occasionally be times, or
1861 particular sequences of actions, that cause it to crash. If you can
1862 come up with a reproducible way of doing this (or even if you have a
1863 pretty good memory of exactly what you were doing at the time), the
1864 maintainers would be very interested in knowing about it. Post a
1865 message to comp.emacs.xemacs or send mail to @email{crashes@@xemacs.org}.
1866 Please note that the @samp{crashes} address is exclusively for crash
1869 If at all possible, include a stack backtrace of the core dump that was
1870 produced. This shows where exactly things went wrong, and makes it much
1871 easier to diagnose problems. To do this, you need to locate the core
1872 file (it's called @file{core}, and is usually sitting in the directory
1873 that you started XEmacs from, or your home directory if that other
1874 directory was not writable). Then, go to that directory and execute a
1878 gdb `which xemacs` core
1881 and then issue the command @samp{where} to get the stack backtrace. You
1882 might have to use @code{dbx} or some similar debugger in place of
1883 @code{gdb}. If you don't have any such debugger available, complain to
1884 your system administrator.
1886 It's possible that a core file didn't get produced, in which case you're
1887 out of luck. Go complain to your system administrator and tell him not
1888 to disable core files by default. Also @xref{Q2.1.15}, for tips and
1889 techniques for dealing with a debugger.
1891 When making a problem report make sure that:
1895 Report @strong{all} of the information output by XEmacs during the
1899 You mention what O/S & Hardware you are running XEmacs on.
1902 What version of XEmacs you are running.
1905 What build options you are using.
1908 If the problem is related to graphics, we will also need to know what
1909 version of the X Window System you are running, and what window manager
1913 If the problem happened on a tty, please include the terminal type.
1916 @node Q2.1.2, Q2.1.3, Q2.1.1, Installation
1917 @unnumberedsubsec Q2.1.2: Cryptic Minibuffer messages.
1919 When I try to use some particular option of some particular package, I
1920 get a cryptic error in the minibuffer.
1922 If you can't figure out what's going on, select Options/General
1923 Options/Debug on Error from the Menubar and then try and make the error
1924 happen again. This will give you a backtrace that may be enlightening.
1925 If not, try reading through this FAQ; if that fails, you could try
1926 posting to comp.emacs.xemacs (making sure to include the backtrace) and
1927 someone may be able to help. If you can identify which Emacs lisp
1928 source file the error is coming from you can get a more detailed stack
1929 backtrace by doing the following:
1933 Visit the .el file in an XEmacs buffer.
1936 Issue the command @kbd{M-x eval-current-buffer}.
1939 Reproduce the error.
1942 Depending on the version of XEmacs, you may either select Edit->Show
1943 Messages (19.13 and earlier) or Help->Recent Keystrokes/Messages (19.14
1944 and later) from the menubar to see the most recent messages. This
1945 command is bound to @kbd{C-h l} by default.
1947 @node Q2.1.3, Q2.1.4, Q2.1.2, Installation
1948 @unnumberedsubsec Q2.1.3: Translation Table Syntax messages at Startup
1950 I get tons of translation table syntax error messages during startup.
1951 How do I get rid of them?
1953 There are two causes of this problem. The first usually only strikes
1954 people using the prebuilt binaries. The culprit in both cases is the
1955 file @file{XKeysymDB}.
1959 The binary cannot find the @file{XKeysymDB} file. The location is
1960 hardcoded at compile time so if the system the binary was built on puts
1961 it a different place than your system does, you have problems. To fix,
1962 set the environment variable @var{XKEYSYMDB} to the location of the
1963 @file{XKeysymDB} file on your system or to the location of the one
1964 included with XEmacs which should be at
1968 @file{<xemacs_root_directory>/lib/xemacs-19.16/etc/XKeysymDB}.
1971 The binary is finding the XKeysymDB but it is out-of-date on your system
1972 and does not contain the necessary lines. Either ask your system
1973 administrator to replace it with the one which comes with XEmacs (which
1974 is the stock R6 version and is backwards compatible) or set your
1975 @var{XKEYSYMDB} variable to the location of XEmacs's described above.
1978 @node Q2.1.4, Q2.1.5, Q2.1.3, Installation
1979 @unnumberedsubsec Q2.1.4: Startup warnings about deducing proper fonts?
1981 How can I avoid the startup warnings about deducing proper fonts?
1983 This is highly dependent on your installation, but try with the
1984 following font as your base font for XEmacs and see what it does:
1987 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
1990 More precisely, do the following in your resource file:
1993 Emacs.default.attributeFont: \
1994 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
1997 If you just don't want to see the @samp{*Warnings*} buffer at startup
1998 time, you can set this:
2001 (setq display-warning-minimum-level 'error)
2004 The buffer still exists; it just isn't in your face.
2006 @node Q2.1.5, Q2.1.6, Q2.1.4, Installation
2007 @unnumberedsubsec Q2.1.5: XEmacs cannot connect to my X Terminal!
2009 Help! I can not get XEmacs to display on my Envizex X-terminal!
2011 Try setting the @var{DISPLAY} variable using the numeric IP address of
2012 the host you are running XEmacs from.
2014 @node Q2.1.6, Q2.1.7, Q2.1.5, Installation
2015 @unnumberedsubsec Q2.1.6: XEmacs just locked up my Linux X server!
2017 There have been several reports of the X server locking up under Linux.
2018 In all reported cases removing speedo and scaled fonts from the font
2019 path corrected the problem. This can be done with the command
2022 It is possible that using a font server may also solve the problem.
2024 @node Q2.1.7, Q2.1.8, Q2.1.6, Installation
2025 @unnumberedsubsec Q2.1.7: HP Alt key as Meta.
2027 How can I make XEmacs recognize the Alt key of my HP workstation as a
2030 Put the following line into a file and load it with xmodmap(1) before
2034 remove Mod1 = Mode_switch
2037 @node Q2.1.8, Q2.1.9, Q2.1.7, Installation
2038 @unnumberedsubsec Q2.1.8: got (wrong-type-argument color-instance-p nil)
2040 @email{nataliek@@rd.scitec.com.au, Natalie Kershaw} writes:
2043 I am trying to run xemacs 19.13 under X11R4. Whenever I move the mouse I
2044 get the following error. Has anyone seen anything like this? This
2045 doesn't occur on X11R5.
2049 (error "got (wrong-type-argument color-instance-p nil)
2050 and I don't know why!")
2054 @email{map01kd@@gold.ac.uk, dinos} writes:
2057 I think this is due to undefined resources; You need to define color
2058 backgrounds and foregrounds into your @file{.../app-defaults/Emacs}
2062 *Foreground: Black ;everything will be of black on grey95,
2063 *Background: Grey95 ;unless otherwise specified.
2064 *cursorColor: Red3 ;red3 cursor with grey95 border.
2065 *pointerColor: Red3 ;red3 pointer with grey95 border.
2069 Natalie Kershaw adds:
2072 What fixed the problem was adding some more colors to the X color
2073 database (copying the X11R5 colors over), and also defining the
2074 following resources:
2077 xemacs*cursorColor: black
2078 xemacs*pointerColor: black
2081 With the new colors installed the problem still occurs if the above
2082 resources are not defined.
2084 If the new colors are not present then an additional error occurs on
2085 XEmacs startup, which says @samp{Color Red3} not defined.
2088 @node Q2.1.9, Q2.1.10, Q2.1.8, Installation
2089 @unnumberedsubsec Q2.1.9: XEmacs causes my OpenWindows 3.0 server to crash.
2091 The OpenWindows 3.0 server is incredibly buggy. Your best bet is to
2092 replace it with one from the generic MIT X11 release. You might also
2093 try disabling parts of your @file{.emacs}, like enabling background
2096 @node Q2.1.10, Q2.1.11, Q2.1.9, Installation
2097 @unnumberedsubsec Q2.1.10: Warnings from incorrect key modifiers.
2099 The following information comes from the @file{PROBLEMS} file that comes
2102 If you're having troubles with HP/UX it is because HP/UX defines the
2103 modifiers wrong in X. Here is a shell script to fix the problem; be
2104 sure that it is run after VUE configures the X server.
2108 xmodmap 2> /dev/null - << EOF
2109 keysym Alt_L = Meta_L
2110 keysym Alt_R = Meta_R
2115 keysym Mode_switch = NoSymbol
2117 keysym Meta_R = Mode_switch
2118 add mod2 = Mode_switch
2122 @node Q2.1.11, Q2.1.12, Q2.1.10, Installation
2123 @unnumberedsubsec Q2.1.11: @samp{Can't instantiate image error...} in toolbar
2126 @email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes:
2128 I just installed the XEmacs (20.4-2) RPMS that I downloaded from
2129 @uref{http://www.xemacs.org/}. Everything works fine, except that when
2130 I place my mouse over the toolbar, it beeps and gives me this message:
2133 Can't instantiate image (probably cached):
2134 [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data
2135 (16 16 <strange control characters> ...
2138 @email{kyle_jones@@wonderworks.com, Kyle Jones} writes:
2140 This is problem specific to some Chips and Technologies video
2141 chips, when running XFree86. Putting
2143 @code{Option "sw_cursor"}
2145 in @file{XF86Config} gets rid of the problem.
2148 @node Q2.1.12, Q2.1.13, Q2.1.11, Installation
2149 @unnumberedsubsec Q2.1.12: Problems with Regular Expressions on DEC OSF1.
2151 I have xemacs 19.13 running on an alpha running OSF1 V3.2 148 and ispell
2152 would not run because it claimed the version number was incorrect
2153 although it was indeed OK. I traced the problem to the regular
2156 @email{douglask@@dstc.edu.au, Douglas Kosovic} writes:
2159 Actually it's a DEC cc optimization bug that screws up the regexp
2162 Rebuilding using the @samp{-migrate} switch for DEC cc (which uses a
2163 different sort of optimization) works fine.
2166 See @file{xemacs-19_13-dunix-3_2c.patch} at the following URL on how to
2167 build with the @samp{-migrate} flag:
2170 @uref{http://www-digital.cern.ch/carney/emacs/emacs.html}
2171 @c Link above, <URL:http://www-digital.cern.ch/carney/emacs/emacs.html> is
2172 @c dead. And the directory `carney' is empty.
2178 NOTE: There have been a variety of other problems reported that are
2179 fixed in this fashion.
2181 @node Q2.1.13, Q2.1.14, Q2.1.12, Installation
2182 @unnumberedsubsec Q2.1.13: HP/UX 10.10 and @code{create_process} failure.
2184 @email{Dave.Carrigan@@ipl.ca, Dave Carrigan} writes:
2187 With XEmacs 19.13 and HP/UX 10.10, anything that relies on the
2188 @code{create_process} function fails. This breaks a lot of things
2189 (shell-mode, compile, ange-ftp, to name a few).
2192 @email{johnson@@dtc.hp.com, Phil Johnson} writes:
2195 This is a problem specific to HP-UX 10.10. It only occurs when XEmacs
2196 is compiled for shared libraries (the default), so you can work around
2197 it by compiling a statically-linked binary (run configure with
2198 @samp{--dynamic=no}).
2200 I'm not sure whether the problem is with a particular shared library or
2201 if it's a kernel problem which crept into 10.10.
2204 @email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
2207 I had a few problems with 10.10. Apparently, some of them were solved by
2208 forcing a static link of libc (manually).
2211 @node Q2.1.14, Q2.1.15, Q2.1.13, Installation
2212 @unnumberedsubsec Q2.1.14: @kbd{C-g} doesn't work for me. Is it broken?
2214 @email{ben@@xemacs.org, Ben Wing} writes:
2217 @kbd{C-g} does work for most people in most circumstances. If it
2218 doesn't, there are only two explanations:
2222 The code is wrapped with a binding of @code{inhibit-quit} to
2223 @code{t}. @kbd{Ctrl-Shift-G} should still work, I think.
2226 SIGIO is broken on your system, but BROKEN_SIGIO isn't defined.
2229 To test #2, try executing @code{(while t)} from the @samp{*scratch*}
2230 buffer. If @kbd{C-g} doesn't interrupt, then you're seeing #2.
2233 @email{terra@@diku.dk, Morten Welinder} writes:
2236 On some (but @emph{not} all) machines a hung XEmacs can be revived by
2237 @code{kill -FPE <pid>}. This is a hack, of course, not a solution.
2238 This technique works on a Sun4 running 4.1.3_U1. To see if it works for
2239 you, start another XEmacs and test with that first. If you get a core
2240 dump the method doesn't work and if you get @samp{Arithmetic error} then
2244 @node Q2.1.15, Q2.1.16, Q2.1.14, Installation
2245 @unnumberedsubsec Q2.1.15: How to Debug an XEmacs problem with a debugger
2247 If XEmacs does crash on you, one of the most productive things you can
2248 do to help get the bug fixed is to poke around a bit with the debugger.
2249 Here are some hints:
2253 First of all, if the crash is at all reproducible, consider very
2254 strongly recompiling your XEmacs with debugging symbols, with no
2255 optimization, and with the configure options @samp{--debug=yes} and
2256 @samp{--error-checking=all}. This will make your XEmacs run somewhat
2257 slower but make it a lot more likely to catch the problem earlier
2258 (closer to its source), and a lot easier to determine what's going on
2262 If you're able to run XEmacs under a debugger and reproduce the crash
2263 (if it's inconvenient to do this because XEmacs is already running or is
2264 running in batch mode as part of a bunch of scripts, consider attaching
2265 to the existing process with your debugger; most debuggers let you do
2266 this by substituting the process ID for the core file when you invoke
2267 the debugger from the command line, or by using the @code{attach}
2268 command or something similar), here are some things you can do:
2271 If XEmacs is hitting an assertion failure, put a breakpoint on
2272 @code{assert_failed()}.
2275 If XEmacs is hitting some weird Lisp error that's causing it to crash
2276 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is
2277 declared static in eval.c.
2280 Internally, you will probably see lots of variables that hold objects of
2281 type @code{Lisp_Object}. These are exactly what they appear to be,
2282 i.e. references to Lisp objects. Printing them out with the debugger
2283 probably won't be too useful---you'll likely just see a number. To
2284 decode them, do this:
2287 call debug_print (OBJECT)
2290 where @var{OBJECT} is whatever you want to decode (it can be a variable,
2291 a function call, etc.). This will print out a readable representation
2292 on the TTY from which the xemacs process was invoked.
2295 If you want to get a Lisp backtrace showing the Lisp call
2299 call debug_backtrace ()
2303 Using @code{debug_print} and @code{debug_backtrace} has two
2304 disadvantages - it can only be used with a running xemacs process, and
2305 it cannot display the internal C structure of a Lisp Object. Even if
2306 all you've got is a core dump, all is not lost.
2308 If you're using GDB, there are some macros in the file
2309 @file{src/gdbinit} in the XEmacs source distribution that should make it
2310 easier for you to decode Lisp objects. Copy this file to
2311 @file{~/.gdbinit}, or @code{source} it from @file{~/.gdbinit}, and use
2312 the macros defined therein. In particular, use the @code{pobj} macro to
2313 print the internal C representation of a lisp object. This will work
2314 with a core file or not-yet-run executable. The aliases @code{ldp} and
2315 @code{lbt} are provided for conveniently calling @code{debug_print} and
2316 @code{debug_backtrace}.
2318 If you are using Sun's @file{dbx} debugger, there is an equivalent file
2319 @file{src/dbxrc} to copy to or source from @file{~/.dbxrc}.
2322 If you're using a debugger to get a C stack backtrace and you're seeing
2323 stack traces with some of the innermost frames mangled, it may be due to
2324 dynamic linking. (This happens especially under Linux.) Consider
2325 reconfiguring with @samp{--dynamic=no}. Also, sometimes (again under
2326 Linux), stack backtraces of core dumps will have the frame where the
2327 fatal signal occurred mangled; if you can obtain a stack trace while
2328 running the XEmacs process under a debugger, the stack trace should be
2331 @email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so version 1.8
2332 if dynamic linking and debugging is a problem on Linux.
2335 If you're using a debugger to get a C stack backtrace and you're
2336 getting a completely mangled and bogus stack trace, it's probably due to
2337 one of the following:
2341 Your executable has been stripped. Bad news. Tell your sysadmin not to
2342 do this---it doesn't accomplish anything except to save a bit of disk
2343 space, and makes debugging much much harder.
2346 Your stack is getting trashed. Debugging this is hard; you have to do a
2347 binary-search type of narrowing down where the crash occurs, until you
2348 figure out exactly which line is causing the problem. Of course, this
2349 only works if the bug is highly reproducible.
2352 If your stack trace has exactly one frame in it, with address 0x0, this
2353 could simply mean that XEmacs attempted to execute code at that address,
2354 e.g. through jumping to a null function pointer. Unfortunately, under
2355 those circumstances, GDB under Linux doesn't know how to get a stack
2356 trace. (Yes, this is the third Linux-related problem I've mentioned. I
2357 have no idea why GDB under Linux is so bogus. Complain to the GDB
2358 authors, or to comp.os.linux.development.system). Again, you'll have to
2359 use the narrowing-down process described above.
2362 If you compiled 19.14 with @samp{--debug} (or by default in later
2363 versions), you will get a Lisp backtrace output when XEmacs crashes, so
2364 you'll have something useful.
2369 If you compile with the newer gcc variants gcc-2.8 or egcs, you will
2370 also need gdb 4.17. Earlier releases of gdb can't handle the debug
2371 information generated by the newer compilers.
2374 The above information on using @file{src/gdbinit} works for XEmacs-21.0
2375 and above. For older versions of XEmacs, there are different
2376 @file{gdbinit} files provided in the @file{src} directory. Use the one
2377 corresponding to the configure options used when building XEmacs.
2381 @node Q2.1.16, Q2.1.17, Q2.1.15, Installation
2382 @unnumberedsubsec Q2.1.16: XEmacs crashes in @code{strcat} on HP/UX 10
2384 >From the problems database (through
2385 @uref{http://support.mayfield.hp.com/}):
2388 Problem Report: 5003302299
2391 System/Model: 9000/700
2392 Product Name: HPUX S800 10.0X
2393 Product Vers: 9245XB.10.00
2395 Description: strcat(3C) may read beyond
2396 end of source string, can cause SIGSEGV
2399 *** PROBLEM TEXT ***
2400 strcat(3C) may read beyond the source string onto an unmapped page,
2401 causing a segmentation violation.
2404 @node Q2.1.17, Q2.1.18, Q2.1.16, Installation
2405 @unnumberedsubsec Q2.1.17: @samp{Marker does not point anywhere}
2407 As with other errors, set @code{debug-on-error} to @code{t} to get the
2408 backtrace when the error occurs. Specifically, two problems have been
2409 reported (and fixed).
2413 A problem with line-number-mode in XEmacs 19.14 affected a large number
2414 of other packages. If you see this error message, turn off
2418 A problem with some early versions of Gnus 5.4 caused this error.
2422 @node Q2.1.18, Q2.1.19, Q2.1.17, Installation
2423 @unnumberedsubsec Q2.1.18: 19.14 hangs on HP/UX 10.10.
2425 @email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
2428 For the record, compiling on hpux 10.10 leads to a hang in Gnus when
2429 compiled with optimization on.
2431 I've just discovered that my hpux 10.01 binary was working less well
2432 than expected. In fact, on a 10.10 system, @code{(while t)} was not
2433 interrupted by @kbd{C-g}. I defined @code{BROKEN_SIGIO} and recompiled on
2434 10.10, and... the hang is now gone.
2436 As far as configure goes, this will be a bit tricky: @code{BROKEN_SIGIO}
2437 is needed on 10.10, but @strong{not} on 10.01: if I run my 10.01 binary
2438 on a 10.01 machine, without @code{BROKEN_SIGIO} being defined, @kbd{C-g}
2442 @email{cognot@@ensg.u-nancy.fr, Richard Cognot} adds:
2445 Apparently somebody has found the reason why there is this
2450 interrupted...} message for each event. For some reason, libcurses
2451 reimplements a @code{select()} system call, in a highly broken fashion.
2452 The fix is to add a -lc to the link line @emph{before} the
2453 -lxcurses. XEmacs will then use the right version of @code{select()}.
2457 @email{af@@biomath.jussieu.fr, Alain Fauconnet} writes:
2460 The @emph{real} solution is to @emph{not} link -lcurses in! I just
2461 changed -lcurses to -ltermcap in the Makefile and it fixed:
2465 The @samp{poll: interrupted system call} message.
2468 A more serious problem I had discovered in the meantime, that is the
2469 fact that subprocess handling was seriously broken: subprocesses
2470 e.g. started by AUC TeX for TeX compilation of a buffer would
2471 @emph{hang}. Actually they would wait forever for emacs to read the
2472 socket which connects stdout...
2476 @node Q2.1.19, Q2.1.20, Q2.1.18, Installation
2477 @unnumberedsubsec Q2.1.19: XEmacs does not follow the local timezone.
2479 When using one of the prebuilt binaries many users have observed that
2480 XEmacs uses the timezone under which it was built, but not the timezone
2481 under which it is running. The solution is to add:
2484 (set-time-zone-rule "MET")
2487 to your @file{.emacs} or the @file{site-start.el} file if you can.
2488 Replace @code{MET} with your local timezone.
2490 @node Q2.1.20, Q2.1.21, Q2.1.19, Installation
2491 @unnumberedsubsec Q2.1.20: @samp{Symbol's function definition is void: hkey-help-show.}
2493 This is a problem with a partially loaded hyperbole. Try adding:
2496 (require 'hmouse-drv)
2499 where you load hyperbole and the problem should go away.
2501 @node Q2.1.21, Q2.1.22, Q2.1.20, Installation
2502 @unnumberedsubsec Q2.1.21: Every so often the XEmacs frame freezes
2504 This problem has been fixed in 19.15, and was due to a not easily
2505 reproducible race condition.
2507 @node Q2.1.22, Q2.1.23, Q2.1.21, Installation
2508 @unnumberedsubsec Q2.1.22: XEmacs seems to take a really long time to do some things
2510 @email{dmoore@@ucsd.edu, David Moore} writes:
2513 Two things you can do:
2517 When you see it going mad like this, you might want to use gdb from an
2518 'xterm' to attach to the running process and get a stack trace. To do
2522 gdb /path/to/xemacs/xemacs ####
2525 Where @code{####} is the process id of your xemacs, instead of
2526 specifying the core. When gdb attaches, the xemacs will stop [1] and
2527 you can type `where' in gdb to get a stack trace as usual. To get
2528 things moving again, you can just type `quit' in gdb. It'll tell you
2529 the program is running and ask if you want to quit anyways. Say 'y' and
2530 it'll quit and have your emacs continue from where it was at.
2534 Turn on debug-on-quit early on. When you think things are going slow
2535 hit C-g and it may pop you in the debugger so you can see what routine
2536 is running. Press `c' to get going again.
2538 debug-on-quit doesn't work if something's turned on inhibit-quit or in
2539 some other strange cases.
2542 @node Q2.1.23, , Q2.1.22, Installation
2543 @unnumberedsubsec Q2.1.23: Movemail on Linux does not work for XEmacs 19.15 and later.
2545 Movemail used to work fine in 19.14 but has stopped working in 19.15
2546 and 20.x. I am using Linux.
2548 @email{steve@@xemacs.org, SL Baur} writes:
2551 Movemail on Linux used to default to using flock file locking. With
2552 19.15 and later versions it now defaults to using @code{.lock} file
2553 locking. If this is not appropriate for your system, edit src/s/linux.h
2554 and uncomment the line that reads:
2557 #define MAIL_USE_FLOCK
2561 @node Customization, Subsystems, Installation, Top
2562 @unnumbered 3 Customization and Options
2564 This is part 3 of the XEmacs Frequently Asked Questions list. This
2565 section is devoted to Customization and screen settings.
2568 Customization---Emacs Lisp and @file{.emacs}:
2569 * Q3.0.1:: What version of Emacs am I running?
2570 * Q3.0.2:: How do I evaluate Elisp expressions?
2571 * Q3.0.3:: @code{(setq tab-width 6)} behaves oddly.
2572 * Q3.0.4:: How can I add directories to the @code{load-path}?
2573 * Q3.0.5:: How to check if a lisp function is defined?
2574 * Q3.0.6:: Can I force the output of @code{(face-list)} to a buffer?
2575 * Q3.0.7:: Font selections don't get saved after @code{Save Options}.
2576 * Q3.0.8:: How do I make a single minibuffer frame?
2577 * Q3.0.9:: What is @code{Customize}?
2579 X Window System & Resources:
2580 * Q3.1.1:: Where is a list of X resources?
2581 * Q3.1.2:: How can I detect a color display?
2582 * Q3.1.3:: @code{(set-screen-width)} worked in 19.6, but not in 19.13?
2583 * Q3.1.4:: Specifying @code{Emacs*EmacsScreen.geometry} in @file{.emacs} does not work in 19.15?
2584 * Q3.1.5:: How can I get the icon to just say @samp{XEmacs}?
2585 * Q3.1.6:: How can I have the window title area display the full path?
2586 * Q3.1.7:: @samp{xemacs -name junk} doesn't work?
2587 * Q3.1.8:: @samp{-iconic} doesn't work.
2589 Textual Fonts & Colors:
2590 * Q3.2.1:: How can I set color options from @file{.emacs}?
2591 * Q3.2.2:: How do I set the text, menu and modeline fonts?
2592 * Q3.2.3:: How can I set the colors when highlighting a region?
2593 * Q3.2.4:: How can I limit color map usage?
2594 * Q3.2.5:: My tty supports color, but XEmacs doesn't use them.
2595 * Q3.2.6:: Can I have pixmap backgrounds in XEmacs?
2598 * Q3.3.1:: How can I make the modeline go away?
2599 * Q3.3.2:: How do you have XEmacs display the line number in the modeline?
2600 * Q3.3.3:: How do I get XEmacs to put the time of day on the modeline?
2601 * Q3.3.4:: How do I turn off current chapter from AUC TeX modeline?
2602 * Q3.3.5:: How can one change the modeline color based on the mode used?
2604 3.4 Multiple Device Support:
2605 * Q3.4.1:: How do I open a frame on another screen of my multi-headed display?
2606 * Q3.4.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
2609 * Q3.5.1:: How can I bind complex functions (or macros) to keys?
2610 * Q3.5.2:: How can I stop down-arrow from adding empty lines to the bottom of my buffers?
2611 * Q3.5.3:: How do I bind C-. and C-; to scroll one line up and down?
2612 * Q3.5.4:: Globally binding @kbd{Delete}?
2613 * Q3.5.5:: Scrolling one line at a time.
2614 * Q3.5.6:: How to map @kbd{Help} key alone on Sun type4 keyboard?
2615 * Q3.5.7:: How can you type in special characters in XEmacs?
2616 * Q3.5.8:: Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
2617 * Q3.5.9:: How do I make the Delete key delete forward?
2618 * Q3.5.10:: Can I turn on @dfn{sticky} modifier keys?
2619 * Q3.5.11:: How do I map the arrow keys?
2622 * Q3.6.1:: Is there a way to make the bar cursor thicker?
2623 * 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?
2624 * Q3.6.3:: Can I make the cursor blink?
2626 The Mouse and Highlighting:
2627 * Q3.7.1:: How can I turn off Mouse pasting?
2628 * Q3.7.2:: How do I set control/meta/etc modifiers on mouse buttons?
2629 * Q3.7.3:: Clicking the left button does not do anything in buffer list.
2630 * Q3.7.4:: How can I get a list of buffers when I hit mouse button 3?
2631 * Q3.7.5:: Why does cut-and-paste not work between XEmacs and a cmdtool?
2632 * Q3.7.6:: How I can set XEmacs up so that it pastes where the text cursor is?
2633 * Q3.7.7:: How do I select a rectangular region?
2634 * Q3.7.8:: Why does @kbd{M-w} take so long?
2636 The Menubar and Toolbar:
2637 * Q3.8.1:: How do I get rid of the menu (or menubar)?
2638 * Q3.8.2:: Can I customize the basic menubar?
2639 * Q3.8.3:: How do I control how many buffers are listed in the menu @code{Buffers} list?
2640 * Q3.8.4:: Resources like @code{Emacs*menubar*font} are not working?
2641 * Q3.8.5:: How can I bind a key to a function to toggle the toolbar?
2644 * Q3.9.1:: How can I disable the scrollbar?
2645 * Q3.9.2:: How can one use resources to change scrollbar colors?
2646 * Q3.9.3:: Moving the scrollbar can move the point; can I disable this?
2647 * Q3.9.4:: How can I get automatic horizontal scrolling?
2650 * Q3.10.1:: How can I turn off or change highlighted selections?
2651 * Q3.10.2:: How do I get that typing on an active region removes it?
2652 * Q3.10.3:: Can I turn off the highlight during isearch?
2653 * Q3.10.4:: How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
2654 * Q3.10.5:: The region disappears when I hit the end of buffer while scrolling.
2657 @node Q3.0.1, Q3.0.2, Customization, Customization
2658 @unnumberedsec 3.0: Customization -- Emacs Lisp and .emacs
2659 @unnumberedsubsec Q3.0.1: What version of Emacs am I running?
2661 How can @file{.emacs} determine which of the family of Emacsen I am
2664 To determine if you are currently running GNU Emacs 18, GNU Emacs 19,
2665 XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the
2666 example given in @file{etc/sample.emacs}. There are other nifty things
2669 For all new code, all you really need to do is:
2672 (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
2675 @node Q3.0.2, Q3.0.3, Q3.0.1, Customization
2676 @unnumberedsubsec Q3.0.2: How can I evaluate Emacs-Lisp expressions?
2678 I know I can evaluate Elisp expressions from @code{*scratch*} buffer
2679 with @kbd{C-j} after the expression. How do I do it from another
2682 Press @kbd{M-:} (the default binding of @code{eval-expression}), and
2683 enter the expression to the minibuffer. In XEmacs prior to 19.15
2684 @code{eval-expression} used to be a disabled command by default. If
2685 this is the case, upgrade your XEmacs.
2687 @node Q3.0.3, Q3.0.4, Q3.0.2, Customization
2688 @unnumberedsubsec Q3.0.3: @code{(setq tab-width 6)} behaves oddly.
2690 If you put @code{(setq tab-width 6)} in your @file{.emacs} file it does
2691 not work! Is there a reason for this? If you do it at the EVAL prompt
2692 it works fine!! How strange.
2694 Use @code{setq-default} instead, since @code{tab-width} is
2697 @node Q3.0.4, Q3.0.5, Q3.0.3, Customization
2698 @unnumberedsubsec Q3.0.4: How can I add directories to the @code{load-path}?
2700 Here are two ways to do that, one that puts your directories at the
2701 front of the load-path, the other at the end:
2704 ;;; Add things at the beginning of the load-path, do not add
2705 ;;; duplicate directories:
2706 (pushnew "bar" load-path :test 'equal)
2708 (pushnew "foo" load-path :test 'equal)
2710 ;;; Add things at the end, unconditionally
2711 (setq load-path (nconc load-path '("foo" "bar")))
2714 @email{keithh@@nortel.ca, keith (k.p.) hanlan} writes:
2717 To add directories using Unix shell metacharacters use
2718 @file{expand-file-name} like this:
2721 (push (expand-file-name "~keithh/.emacsdir") load-path)
2725 @node Q3.0.5, Q3.0.6, Q3.0.4, Customization
2726 @unnumberedsubsec Q3.0.5: How to check if a lisp function is defined?
2728 Use the following elisp:
2734 It's almost always a mistake to test @code{emacs-version} or any similar
2737 Instead, use feature-tests, such as @code{featurep}, @code{boundp},
2738 @code{fboundp}, or even simple behaviroal tests, eg.:
2741 (defvar foo-old-losing-code-p
2742 (condition-case nil (progn (losing-code t) nil)
2743 (wrong-number-of-arguments t)))
2746 There is an incredible amount of broken code out there which could work
2747 much better more often in more places if it did the above instead of
2748 trying to divine its environment from the value of one variable.
2750 @node Q3.0.6, Q3.0.7, Q3.0.5, Customization
2751 @unnumberedsubsec Q3.0.6: Can I force the output of @code{(face-list)} to a buffer?
2753 It would be good having it in a buffer, as the output of
2754 @code{(face-list)} is too wide to fit to a minibuffer.
2756 Evaluate the expression in the @samp{*scratch*} buffer with point after
2757 the rightmost paren and typing @kbd{C-j}.
2759 If the minibuffer smallness is the only problem you encounter, you can
2760 simply press @kbd{C-h l} to get the former minibuffer contents in a
2763 @node Q3.0.7, Q3.0.8, Q3.0.6, Customization
2764 @unnumberedsubsec Q3.0.7: Font selections in don't get saved after @code{Save Options}.
2766 For XEmacs 19.14 and previous:
2768 @email{mannj@@ll.mit.edu, John Mann} writes:
2771 You have to go to Options->Frame Appearance and unselect
2772 @samp{Frame-Local Font Menu}. If this option is selected, font changes
2773 are only applied to the @emph{current} frame and do @emph{not} get saved
2774 when you save options.
2777 For XEmacs 19.15 and later:
2779 Implement the above as well as set the following in your @file{.emacs}
2782 (setq options-save-faces t)
2785 @node Q3.0.8, Q3.0.9, Q3.0.7, Customization
2786 @unnumberedsubsec Q3.0.8: How do I get a single minibuffer frame?
2788 @email{acs@@acm.org, Vin Shelton} writes:
2791 (setq initial-frame-plist '(minibuffer nil))
2792 (setq default-frame-plist '(minibuffer nil))
2793 (setq default-minibuffer-frame
2798 menubar-visible-p nil
2799 default-toolbar-visible-p nil
2803 has-modeline-p nil)))
2804 (frame-notice-user-settings)
2807 @strong{Please note:} The single minibuffer frame may not be to everyone's
2808 taste, and there any number of other XEmacs options settings that may
2809 make it difficult or inconvenient to use.
2811 @node Q3.0.9, Q3.1.1, Q3.0.8, Customization
2812 @unnumberedsubsec Q3.0.9: What is @code{Customize}?
2814 Starting with XEmacs 20.2 there is new system 'Customize' for customizing
2817 You can access @code{Customize} from the @code{Options} menu
2818 or invoking one of customize commands by typing eg.
2819 @kbd{M-x customize}, @kbd{M-x customize-face},
2820 @kbd{M-x customize-variable} or @kbd{M-x customize-apropos}.
2822 Starting with XEmacs 20.3 there is also new `browser' mode for Customize.
2823 Try it out with @kbd{M-x customize-browse}
2825 @node Q3.1.1, Q3.1.2, Q3.0.9, Customization
2826 @unnumberedsec 3.1: X Window System & Resources
2827 @unnumberedsubsec Q3.1.1: Where is a list of X resources?
2829 Search through the @file{NEWS} file for @samp{X Resources}. A fairly
2830 comprehensive list is given after it.
2832 In addition, an @file{app-defaults} file is supplied,
2833 @file{etc/Emacs.ad} listing the defaults. The file
2834 @file{etc/sample.Xdefaults} gives a set of defaults that you might
2835 consider. It is essentially the same as @file{etc/Emacs.ad} but some
2836 entries are slightly altered. Be careful about installing the contents
2837 of this file into your @file{.Xdefaults} or @file{.Xresources} file if
2838 you use GNU Emacs under X11 as well.
2840 @node Q3.1.2, Q3.1.3, Q3.1.1, Customization
2841 @unnumberedsubsec Q3.1.2: How can I detect a color display?
2843 You can test the return value of the function @code{(device-class)}, as
2847 (when (eq (device-class) 'color)
2848 (set-face-foreground 'font-lock-comment-face "Grey")
2849 (set-face-foreground 'font-lock-string-face "Red")
2854 @node Q3.1.3, Q3.1.4, Q3.1.2, Customization
2855 @unnumberedsubsec Q3.1.3: @code{(set-screen-width)} worked in 19.6, but not in 19.13?
2857 In Lucid Emacs 19.6 I did @code{(set-screen-width @var{characters})} and
2858 @code{(set-screen-height @var{lines})} in my @file{.emacs} instead of
2859 specifying @code{Emacs*EmacsScreen.geometry} in my
2863 @file{.Xdefaults} but
2864 this does not work in XEmacs 19.13.
2866 These two functions now take frame arguments:
2869 (set-frame-width (selected-frame) @var{characters})
2870 (set-frame-height (selected-frame) @var{lines})
2873 @node Q3.1.4, Q3.1.5, Q3.1.3, Customization
2874 @unnumberedsubsec Q3.1.4: Specifying @code{Emacs*EmacsScreen.geometry} in @file{.emacs} does not work in 19.15?
2876 In XEmacs 19.11 I specified @code{Emacs*EmacsScreen.geometry} in
2877 my @file{.emacs} but this does not work in XEmacs 19.15.
2879 We have switched from using the term @dfn{screen} to using the term
2882 The correct entry for your @file{.Xdefaults} is now:
2885 Emacs*EmacsFrame.geometry
2888 @node Q3.1.5, Q3.1.6, Q3.1.4, Customization
2889 @unnumberedsubsec Q3.1.5: How can I get the icon to just say @samp{XEmacs}?
2891 I'd like the icon to just say @samp{XEmacs}, and not include the name of
2892 the current file in it.
2894 Add the following line to your @file{.emacs}:
2897 (setq frame-icon-title-format "XEmacs")
2900 @node Q3.1.6, Q3.1.7, Q3.1.5, Customization
2901 @unnumberedsubsec Q3.1.6: How can I have the window title area display the full path?
2903 I'd like to have the window title area display the full directory/name
2904 of the current buffer file and not just the name.
2906 Add the following line to your @file{.emacs}:
2909 (setq frame-title-format "%S: %f")
2912 A more sophisticated title might be:
2915 (setq frame-title-format
2916 '("%S: " (buffer-file-name "%f"
2917 (dired-directory dired-directory "%b"))))
2920 That is, use the file name, or the dired-directory, or the buffer name.
2922 @node Q3.1.7, Q3.1.8, Q3.1.6, Customization
2923 @unnumberedsubsec Q3.1.7: @samp{xemacs -name junk} doesn't work?
2925 When I run @samp{xterm -name junk}, I get an xterm whose class name
2926 according to xprop, is @samp{junk}. This is the way it's supposed to
2927 work, I think. When I run @samp{xemacs -name junk} the class name is
2928 not set to @samp{junk}. It's still @samp{emacs}. What does
2929 @samp{xemacs -name} really do? The reason I ask is that my window
2930 manager (fvwm) will make a window sticky and I use XEmacs to read my
2931 mail. I want that XEmacs window to be sticky, without having to use the
2932 window manager's function to set the window sticky. What gives?
2934 @samp{xemacs -name} sets the application name for the program (that is,
2935 the thing which normally comes from @samp{argv[0]}). Using @samp{-name}
2936 is the same as making a copy of the executable with that new name. The
2937 @code{WM_CLASS} property on each frame is set to the frame-name, and the
2938 application-class. So, if you did @samp{xemacs -name FOO} and then
2939 created a frame named @var{BAR}, you'd get an X window with WM_CLASS =
2940 @code{( "BAR", "Emacs")}. However, the resource hierarchy for this
2944 Name: FOO .shell .container .BAR
2945 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
2948 instead of the default
2951 Name: xemacs.shell .container .emacs
2952 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
2956 It is arguable that the first element of WM_CLASS should be set to the
2957 application-name instead of the frame-name, but I think that's less
2958 flexible, since it does not give you the ability to have multiple frames
2959 with different WM_CLASS properties. Another possibility would be for
2960 the default frame name to come from the application name instead of
2961 simply being @samp{emacs}. However, at this point, making that change
2962 would be troublesome: it would mean that many users would have to make
2963 yet another change to their resource files (since the default frame name
2964 would suddenly change from @samp{emacs} to @samp{xemacs}, or whatever
2965 the executable happened to be named), so we'd rather avoid it.
2967 To make a frame with a particular name use:
2970 (make-frame '((name . "the-name")))
2973 @node Q3.1.8, Q3.2.1, Q3.1.7, Customization
2974 @unnumberedsubsec Q3.1.8: @samp{-iconic} doesn't work.
2976 When I start up XEmacs using @samp{-iconic} it doesn't work right.
2977 Using @samp{-unmapped} on the command line, and setting the
2978 @code{initiallyUnmapped} X Resource don't seem to help much either...
2980 @email{ben@@xemacs.org, Ben Wing} writes:
2983 Ugh, this stuff is such an incredible mess that I've about given up
2984 getting it to work. The principal problem is numerous window-manager
2988 @node Q3.2.1, Q3.2.2, Q3.1.8, Customization
2989 @unnumberedsec 3.2: Textual Fonts & Colors
2990 @unnumberedsubsec Q3.2.1: How can I set color options from @file{.emacs}?
2992 How can I set the most commonly used color options from my @file{.emacs}
2993 instead of from my @file{.Xdefaults}?
2998 (set-face-background 'default "bisque") ; frame background
2999 (set-face-foreground 'default "black") ; normal text
3000 (set-face-background 'zmacs-region "red") ; When selecting w/
3002 (set-face-foreground 'zmacs-region "yellow")
3003 (set-face-font 'default "*courier-bold-r*120-100-100*")
3004 (set-face-background 'highlight "blue") ; Ie when selecting
3006 (set-face-foreground 'highlight "yellow")
3007 (set-face-background 'modeline "blue") ; Line at bottom
3009 (set-face-foreground 'modeline "white")
3010 (set-face-font 'modeline "*bold-r-normal*140-100-100*")
3011 (set-face-background 'isearch "yellow") ; When highlighting
3013 (set-face-foreground 'isearch "red")
3014 (setq x-pointer-foreground-color "black") ; Adds to bg color,
3016 (setq x-pointer-background-color "blue") ; This is color
3021 @node Q3.2.2, Q3.2.3, Q3.2.1, Customization
3022 @unnumberedsubsec Q3.2.2: How do I set the text, menu and modeline fonts?
3024 Note that you should use @samp{Emacs.} and not @samp{Emacs*} when
3025 setting face values.
3027 In @file{.Xdefaults}:
3030 Emacs.default.attributeFont: -*-*-medium-r-*-*-*-120-*-*-m-*-*-*
3031 Emacs*menubar*font: fixed
3032 Emacs.modeline.attributeFont: fixed
3035 This is confusing because modeline is a face, and can be found listed
3036 with all faces in the current mode by using @kbd{M-x set-face-font
3037 (enter) ?}. It uses the face specification of @code{attributeFont},
3038 while menubar is a normal X thing that uses the specification
3039 @code{font}. With Motif it may be necessary to use @code{fontList}
3040 instead of @code{font}.
3042 @node Q3.2.3, Q3.2.4, Q3.2.2, Customization
3043 @unnumberedsubsec Q3.2.3: How can I set the colors when highlighting a region?
3045 How can I set the background/foreground colors when highlighting a
3048 You can change the face @code{zmacs-region} either in your
3052 Emacs.zmacs-region.attributeForeground: firebrick
3053 Emacs.zmacs-region.attributeBackground: lightseagreen
3056 or in your @file{.emacs}:
3059 (set-face-background 'zmacs-region "red")
3060 (set-face-foreground 'zmacs-region "yellow")
3063 @node Q3.2.4, Q3.2.5, Q3.2.3, Customization
3064 @unnumberedsubsec Q3.2.4: How can I limit color map usage?
3066 I'm using Netscape (or another color grabber like XEmacs);
3067 is there anyway to limit the number of available colors in the color map?
3069 XEmacs 19.13 didn't have such a mechanism (unlike netscape, or other
3070 color-hogs). One solution is to start XEmacs prior to netscape, since
3071 this will prevent Netscape from grabbing all colors (but Netscape will
3072 complain). You can use the flags for Netscape, like -mono, -ncols <#>
3073 or -install (for mono, limiting to <#> colors, or for using a private
3074 color map). Since Netscape will take the entire colormap and never
3075 release it, the only reasonable way to run it is with @samp{-install}.
3077 If you have the money, another solution would be to use a truecolor or
3080 Starting with XEmacs 19.14, XEmacs uses the closest available color if
3081 the colormap is full, so it's O.K. now to start Netscape first.
3083 @node Q3.2.5, Q3.2.6, Q3.2.4, Customization
3084 @unnumberedsubsec Q3.2.5: My tty supports color, but XEmacs doesn't use them.
3086 XEmacs tries to automatically determine whether your tty supports color,
3087 but sometimes guesses wrong. In that case, you can make XEmacs Do The
3088 Right Thing using this Lisp code:
3091 (if (eq 'tty (device-type))
3092 (set-device-class nil 'color))
3095 @node Q3.2.6, Q3.3.1, Q3.2.5, Customization
3096 @unnumberedsubsec Q3.2.6: Can I have pixmap backgrounds in XEmacs?
3098 @email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes:
3101 There are several ways to do it. For example, you could specify a
3102 default pixmap image to use in your @file{~/.Xresources}, e.g.,
3106 Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm
3110 and then reload ~/.Xresources and restart XEmacs. Alternatively,
3111 since each face can have its own pixmap background, a better way
3112 would be to set a face's pixmap within your XEmacs init file, e.g.,
3115 (set-face-background-pixmap 'default "/path/to/image.xpm")
3116 (set-face-background-pixmap 'bold "/path/to/another_image.xpm")
3119 and so on. You can also do this interactively via @kbd{M-x edit-faces}.
3123 @unnumberedsec 3.3: The Modeline
3124 @node Q3.3.1, Q3.3.2, Q3.2.6, Customization
3125 @unnumberedsubsec Q3.3.1: How can I make the modeline go away?
3128 (set-specifier has-modeline-p nil)
3131 Starting with XEmacs 19.14 the modeline responds to mouse clicks, so if
3132 you haven't liked or used the modeline in the past, you might want to
3133 try the new version out.
3135 @node Q3.3.2, Q3.3.3, Q3.3.1, Customization
3136 @unnumberedsubsec Q3.3.2: How do you have XEmacs display the line number in the modeline?
3138 Add the following line to your @file{.emacs} file to display the
3142 (line-number-mode 1)
3145 Use the following to display the column number:
3148 (column-number-mode 1)
3151 Or select from the @code{Options} menu
3155 @code{Customize->Emacs->Editing->Basics->Line Number Mode}
3160 @code{Customize->Emacs->Editing->Basics->Column Number Mode}
3162 Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
3164 @node Q3.3.3, Q3.3.4, Q3.3.2, Customization
3165 @unnumberedsubsec Q3.3.3: How do I get XEmacs to put the time of day on the modeline?
3167 Add the following line to your @file{.emacs} file to display the
3174 See @code{Customize} from the @code{Options} menu for customization.
3176 @node Q3.3.4, Q3.3.5, Q3.3.3, Customization
3177 @unnumberedsubsec Q3.3.4: How do I turn off current chapter from AUC TeX modeline?
3179 With AUC TeX, fast typing is hard because the current chapter, section
3180 etc. are given in the modeline. How can I turn this off?
3182 It's not AUC TeX, it comes from @code{func-menu} in @file{func-menu.el}.
3183 Add this code to your @file{.emacs} to turn it off:
3186 (setq fume-display-in-modeline-p nil)
3189 Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
3193 (add-hook 'TeX-mode-hook
3194 '(lambda () (setq fume-display-in-modeline-p nil)))
3197 @email{dhughes@@origin-at.co.uk, David Hughes} writes:
3200 If you have 19.14 or later, try this instead; you'll still get the
3201 function name displayed in the modeline, but it won't attempt to keep
3202 track when you modify the file. To refresh when it gets out of synch,
3203 you simply need click on the @samp{Rescan Buffer} option in the
3207 (setq-default fume-auto-rescan-buffer-p nil)
3211 @node Q3.3.5, Q3.4.1, Q3.3.4, Customization
3212 @unnumberedsubsec Q3.3.5: How can one change the modeline color based on the mode used?
3214 You can use something like the following:
3217 (add-hook 'lisp-mode-hook
3219 (set-face-background 'modeline "red" (current-buffer))))
3222 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
3223 colors change from the default set in your @file{.emacs}. The change
3224 will only be made in the buffer you just entered (which contains the
3225 Lisp file you are editing) and will not affect the modeline colors
3233 The hook is the mode name plus @code{-hook}. eg. c-mode-hook,
3234 c++-mode-hook, emacs-lisp-mode-hook (used for your @file{.emacs} or a
3235 @file{xx.el} file), lisp-interaction-mode-hook (the @samp{*scratch*}
3236 buffer), text-mode-hook, etc.
3239 Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)},
3240 otherwise you will erase anything that anybody has already put on the
3244 You can also do @code{(set-face-font 'modeline @var{font})},
3245 eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*"
3246 (current-buffer))} if you wish the modeline font to vary based on the
3250 This works in 19.15 as well, but there are additional modeline faces,
3251 @code{modeline-buffer-id}, @code{modeline-mousable}, and
3252 @code{modeline-mousable-minor-mode}, which you may want to customize.
3254 @node Q3.4.1, Q3.4.2, Q3.3.5, Customization
3255 @unnumberedsec 3.4: Multiple Device Support
3256 @unnumberedsubsec Q3.4.1: How do I open a frame on another screen of my multi-headed display?
3258 The support for this was revamped for 19.14. Use the command
3259 @kbd{M-x make-frame-on-display}. This command is also on the File menu
3262 XEmacs 19.14 and later also have the command @code{make-frame-on-tty}
3263 which will establish a connection to any tty-like device. Opening the
3264 TTY devices should be left to @code{gnuclient}, though.
3266 @node Q3.4.2, Q3.5.1, Q3.4.1, Customization
3267 @unnumberedsubsec Q3.4.2: Can I really connect to a running XEmacs after calling up over a modem? How?
3269 If you're not running at least XEmacs 19.14, you can't. Otherwise check
3270 out the @code{gnuattach} program supplied with XEmacs. Starting with
3271 XEmacs 20.3, @code{gnuattach} and @code{gnudoit} functionality is
3272 provided by @code{gnuclient}.
3274 Also @xref{Q5.0.12}.
3276 @node Q3.5.1, Q3.5.2, Q3.4.2, Customization
3277 @unnumberedsec 3.5: The Keyboard
3278 @unnumberedsubsec Q3.5.1: How can I bind complex functions (or macros) to keys?
3280 As an example, say you want the @kbd{paste} key on a Sun keyboard to
3281 insert the current Primary X selection at point. You can accomplish this
3285 (define-key global-map [f18] 'x-insert-selection)
3288 However, this only works if there is a current X selection (the
3289 selection will be highlighted). The functionality I like is for the
3290 @kbd{paste} key to insert the current X selection if there is one,
3291 otherwise insert the contents of the clipboard. To do this you need to
3292 pass arguments to @code{x-insert-selection}. This is done by wrapping
3293 the call in a 'lambda form:
3296 (global-set-key [f18]
3297 (lambda () (interactive) (x-insert-selection t nil)))
3300 This binds the f18 key to a @dfn{generic} functional object. The
3301 interactive spec is required because only interactive functions can be
3304 For the FAQ example you could use:
3307 (global-set-key [(control ?.)]
3308 (lambda () (interactive) (scroll-up 1)))
3309 (global-set-key [(control ? ;)]
3310 (lambda () (interactive) (scroll-up -1)))
3313 This is fine if you only need a few functions within the lambda body.
3314 If you're doing more it's cleaner to define a separate function as in
3315 question 3.5.3 (@pxref{Q3.5.3}).
3317 @node Q3.5.2, Q3.5.3, Q3.5.1, Customization
3318 @unnumberedsubsec Q3.5.2: How can I stop down-arrow from adding empty lines to the bottom of my buffers?
3320 Add the following line to your @file{.emacs} file:
3323 (setq next-line-add-newlines nil)
3326 This has been the default setting in XEmacs for some time.
3328 @node Q3.5.3, Q3.5.4, Q3.5.2, Customization
3329 @unnumberedsubsec Q3.5.3: How do I bind C-. and C-; to scroll one line up and down?
3331 Add the following (Thanks to @email{mly@@adoc.xerox.com, Richard Mlynarik} and
3332 @email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}:
3335 (defun scroll-up-one-line ()
3339 (defun scroll-down-one-line ()
3343 (global-set-key [(control ?.)] 'scroll-up-one-line) ; C-.
3344 (global-set-key [(control ? ;)] 'scroll-down-one-line) ; C-;
3347 The key point is that you can only bind simple functions to keys; you
3348 can not bind a key to a function that you're also passing arguments to.
3349 (@pxref{Q3.5.1} for a better answer).
3351 @node Q3.5.4, Q3.5.5, Q3.5.3, Customization
3352 @unnumberedsubsec Q3.5.4: Globally binding @kbd{Delete}?
3354 I cannot manage to globally bind my @kbd{Delete} key to something other
3355 than the default. How does one do this?
3360 (message "You hit DELETE"))
3362 (global-set-key 'delete 'foo)
3365 However, some modes explicitly bind @kbd{Delete}, so you would need to
3366 add a hook that does @code{local-set-key} for them. If what you want to
3367 do is make the Backspace and Delete keys work more PC/Motif-like, then
3368 take a look at the @file{delbs.el} package.
3370 New in XEmacs 19.14 is a variable called @code{key-translation-map}
3371 which makes it easier to bind @kbd{Delete}. @file{delbs.el} is a
3372 good example of how to do this correctly.
3374 Also @xref{Q3.5.10}.
3376 @node Q3.5.5, Q3.5.6, Q3.5.4, Customization
3377 @unnumberedsubsec Q3.5.5: Scrolling one line at a time.
3379 Can the cursor keys scroll the screen a line at a time, rather than the
3380 default half page jump? I tend it to find it disorienting.
3385 (defun scroll-one-line-up (&optional arg)
3386 "Scroll the selected window up (forward in the text) one line (or N lines)."
3388 (scroll-up (or arg 1)))
3390 (defun scroll-one-line-down (&optional arg)
3391 "Scroll the selected window down (backward in the text) one line (or N)."
3393 (scroll-down (or arg 1)))
3395 (global-set-key [up] 'scroll-one-line-up)
3396 (global-set-key [down] 'scroll-one-line-down)
3399 The following will also work but will affect more than just the cursor
3400 keys (i.e. @kbd{C-n} and @kbd{C-p}):
3403 (setq scroll-step 1)
3406 Starting with XEmacs-20.3 you can also change this with Customize.
3407 Select from the @code{Options} menu
3408 @code{Customize->Emacs->Environment->Windows->Scroll Step...} or type
3409 @kbd{M-x customize @key{RET} windows @key{RET}}.
3411 @node Q3.5.6, Q3.5.7, Q3.5.5, Customization
3412 @unnumberedsubsec Q3.5.6: How to map @kbd{Help} key alone on Sun type4 keyboard?
3414 The following works in GNU Emacs 19:
3417 (global-set-key [help] 'help-command);; Help
3420 The following works in XEmacs 19.15 with the addition of shift:
3423 (global-set-key [(shift help)] 'help-command);; Help
3426 But it doesn't work alone. This is in the file @file{PROBLEMS} which
3427 should have come with your XEmacs installation: @emph{Emacs ignores the
3428 @kbd{help} key when running OLWM}.
3430 OLWM grabs the @kbd{help} key, and retransmits it to the appropriate
3435 @code{XSendEvent}. Allowing Emacs to react to synthetic
3436 events is a security hole, so this is turned off by default. You can
3437 enable it by setting the variable @code{x-allow-sendevents} to t. You
3438 can also cause fix this by telling OLWM to not grab the help key, with
3439 the null binding @code{OpenWindows.KeyboardCommand.Help:}.
3441 @node Q3.5.7, Q3.5.8, Q3.5.6, Customization
3442 @unnumberedsubsec Q3.5.7: How can you type in special characters in XEmacs?
3444 One way is to use the package @code{x-compose}. Then you can use
3445 sequences like @kbd{Compose " a} to get ä, etc.
3447 Another way is to use the @code{iso-insert} package, provided in XEmacs
3448 19.15 and later. Then you can use sequences like @kbd{C-x 8 " a} to get
3451 @email{glynn@@sensei.co.uk, Glynn Clements} writes:
3454 It depends upon your X server.
3456 Generally, the simplest way is to define a key as Multi_key with
3458 @c hey, show some respect, willya -- there's xkeycaps, isn't there? --
3461 xmodmap -e 'keycode 0xff20 = Multi_key'
3464 You will need to pick an appropriate keycode. Use xev to find out the
3465 keycodes for each key.
3467 [NB: On a `Windows' keyboard, recent versions of XFree86 automatically
3468 define the right `Windows' key as Multi_key'.]
3470 Once you have Multi_key defined, you can use e.g.
3479 Also, recent versions of XFree86 define various AltGr-<key>
3480 combinations as dead keys, i.e.
3482 AltGr [ => dead_diaeresis
3483 AltGr ] => dead_tilde
3484 AltGr ; => dead_acute
3488 Running @samp{xmodmap -pk} will list all of the defined keysyms.
3491 @node Q3.5.8, Q3.5.9, Q3.5.7, Customization
3492 @unnumberedsubsec Q3.5.8: Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
3494 Why does @code{(define-key global-map [ delete-forward ] 'delete-char)}
3495 complain of not being able to bind an unknown key?
3500 (define-key global-map [delete_forward] 'delete-char)
3505 What you are seeing above is a bug due to code that is trying to check
3506 for GNU Emacs syntax like:
3508 (define-key global-map [C-M-a] 'delete-char)
3510 which otherwise would cause no errors but would not result in the
3513 This bug has been fixed in 19.14.
3515 @node Q3.5.9, Q3.5.10, Q3.5.8, Customization
3516 @unnumberedsubsec Q3.5.9: How do I make the Delete key delete forward?
3518 With XEmacs-20.2 use the @code{delbs} package:
3524 This will give you the functions @code{delbs-enable-delete-forward} to
3525 set things up, and @code{delbs-disable-delete-forward} to revert to
3526 ``normal'' behavior. Note that @code{delbackspace} package is obsolete.
3528 Starting with XEmacs-20.3 better solution is to set variable
3529 @code{delete-key-deletes-forward} to t. You can also change this with
3530 Customize. Select from the @code{Options} menu
3531 @code{Customize->Emacs->Editing->Basics->Delete Key Deletes Forward} or
3532 type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
3536 @node Q3.5.10, Q3.5.11, Q3.5.9, Customization
3537 @unnumberedsubsec Q3.5.10: Can I turn on @dfn{sticky} modifier keys?
3539 Yes, with @code{(setq modifier-keys-are-sticky t)}. This will give the
3540 effect of being able to press and release Shift and have the next
3541 character typed come out in upper case. This will affect all the other
3542 modifier keys like Control and Meta as well.
3544 @email{ben@@xemacs.org, Ben Wing} writes:
3547 One thing about the sticky modifiers is that if you move the mouse out
3548 of the frame and back in, it cancels all currently ``stuck'' modifiers.
3551 @node Q3.5.11, Q3.6.1, Q3.5.10, Customization
3552 @unnumberedsubsec Q3.5.11: How do I map the arrow keys?
3554 Say you want to map @kbd{C-@key{right}} to forward-word:
3556 @email{sds@@usa.net, Sam Steingold} writes:
3560 ; both XEmacs and Emacs
3561 (define-key global-map [(control right)] 'forward-word)
3566 (define-key global-map [C-right] 'forward-word)
3571 (define-key global-map (kbd "C-<right>") 'forward-word)
3577 @node Q3.6.1, Q3.6.2, Q3.5.11, Customization
3578 @unnumberedsec 3.6: The Cursor
3579 @unnumberedsubsec Q3.6.1: Is there a way to make the bar cursor thicker?
3581 I'd like to have the bar cursor a little thicker, as I tend to "lose" it
3584 For a 1 pixel bar cursor, use:
3590 For a 2 pixel bar cursor, use:
3593 (setq bar-cursor 'anything-else)
3596 Starting with XEmacs-20.3 you can also change these with Customize.
3597 Select from the @code{Options} menu
3598 @code{Customize->Emacs->Environment->Display->Bar Cursor...} or type
3599 @kbd{M-x customize @key{RET} display @key{RET}}.
3601 You can use a color to make it stand out better:
3604 Emacs*cursorColor: Red
3607 @node Q3.6.2, Q3.6.3, Q3.6.1, Customization
3608 @unnumberedsubsec Q3.6.2: Is there a way to get back the block cursor?
3611 (setq bar-cursor nil)
3614 Starting with XEmacs-20.3 you can also change this with Customize.
3615 Select from the @code{Options} menu
3616 @code{Customize->Emacs->Environment->Display->Bar Cursor...} or type
3617 @kbd{M-x customize @key{RET} display @key{RET}}.
3619 @node Q3.6.3, Q3.7.1, Q3.6.2, Customization
3620 @unnumberedsubsec Q3.6.3: Can I make the cursor blink?
3622 If you are running a version of XEmacs older than 19.14, no. Otherwise
3623 you can do the following:
3629 This function toggles between a steady cursor and a blinking cursor.
3630 You may also set this mode from the menu bar by selecting @samp{Options
3631 => Frame Appearance => Blinking Cursor}. Remember to save options.
3633 @node Q3.7.1, Q3.7.2, Q3.6.3, Customization
3634 @unnumberedsec 3.7: The Mouse and Highlighting
3635 @unnumberedsubsec Q3.7.1: How can I turn off Mouse pasting?
3637 I keep hitting the middle mouse button by accident and getting stuff
3638 pasted into my buffer so how can I turn this off?
3640 Here is an alternative binding, whereby the middle mouse button selects
3641 (but does not cut) the expression under the mouse. Clicking middle on a
3642 left or right paren will select to the matching one. Note that you can
3643 use @code{define-key} or @code{global-set-key}.
3646 (defun mouse-set-point-and-select (event)
3647 "Sets the point at the mouse location, then marks following form"
3649 (mouse-set-point event)
3651 (define-key global-map [button2] 'mouse-set-point-and-select)
3654 @node Q3.7.2, Q3.7.3, Q3.7.1, Customization
3655 @unnumberedsubsec Q3.7.2: How do I set control/meta/etc modifiers on mouse buttons?
3657 Use, for instance, @code{[(meta button1)]}. For example, here is a common
3658 setting for Common Lisp programmers who use the bundled @code{ilisp}
3659 package, whereby meta-button1 on a function name will find the file where
3660 the function name was defined, and put you at that location in the source
3663 [Inside a function that gets called by the lisp-mode-hook and
3667 (local-set-key [(meta button1)] 'edit-definitions-lisp)
3670 @node Q3.7.3, Q3.7.4, Q3.7.2, Customization
3671 @unnumberedsubsec Q3.7.3: Clicking the left button does not do anything in buffer list.
3673 I do @kbd{C-x C-b} to get a list of buffers and the entries get
3674 highlighted when I move the mouse over them but clicking the left mouse
3675 does not do anything.
3677 Use the middle mouse button.
3679 @node Q3.7.4, Q3.7.5, Q3.7.3, Customization
3680 @unnumberedsubsec Q3.7.4: How can I get a list of buffers when I hit mouse button 3?
3682 The following code will replace the default popup on button3:
3685 (global-set-key [button3] 'popup-buffer-menu)
3688 @node Q3.7.5, Q3.7.6, Q3.7.4, Customization
3689 @unnumberedsubsec Q3.7.5: Why does cut-and-paste not work between XEmacs and a cmdtool?
3691 We don't know. It's a bug. There does seem to be a work-around,
3692 however. Try running xclipboard first. It appears to fix the problem
3693 even if you exit it. (This should be mostly fixed in 19.13, but we
3694 haven't yet verified that).
3696 @node Q3.7.6, Q3.7.7, Q3.7.5, Customization
3697 @unnumberedsubsec Q3.7.6: How I can set XEmacs up so that it pastes where the text cursor is?
3699 By default XEmacs pastes X selections where the mouse pointer is. How
3702 Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank
3705 To get XEmacs to paste at the text cursor, add this your @file{.emacs}:
3708 (setq mouse-yank-at-point t)
3711 Starting with XEmacs-20.2 you can also change this with Customize.
3712 Select from the @code{Options} menu
3713 @code{Customize->Emacs->Editing->Mouse->Yank At Point...} or type
3714 @kbd{M-x customize @key{RET} mouse @key{RET}}.
3716 @node Q3.7.7, Q3.7.8, Q3.7.6, Customization
3717 @unnumberedsubsec Q3.7.7: How do I select a rectangular region?
3719 Just select the region normally, then use the rectangle commands (e.g.
3720 @code{kill-rectangle} on it. The region does not highlight as a
3721 rectangle, but the commands work just fine.
3723 To actually sweep out rectangular regions with the mouse you can use
3724 @code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}.
3725 Then use rectangle commands.
3727 You can also do the following to change default behavior to sweep out
3728 rectangular regions:
3731 (setq mouse-track-rectangle-p t)
3734 Starting with XEmacs-20.2 you can also change this with Customize.
3735 Select from the @code{Options} menu
3736 @code{Customize->Emacs->Editing->Mouse->Track Rectangle...} or type
3737 @kbd{M-x customize @key{RET} mouse @key{RET}}.
3741 mouse-track-do-rectangle: (event)
3742 -- an interactive compiled Lisp function.
3743 Like `mouse-track' but selects rectangles instead of regions.
3746 @node Q3.7.8, Q3.8.1, Q3.7.7, Customization
3747 @unnumberedsubsec Q3.7.8: Why does @kbd{M-w} take so long?
3749 It actually doesn't. It leaves the region visible for a second so that
3750 you can see what area is being yanked. If you start working, though, it
3751 will immediately complete its operation. In other words, it will only
3752 delay for a second if you let it.
3754 @node Q3.8.1, Q3.8.2, Q3.7.8, Customization
3755 @unnumberedsec 3.8: The Menubar and Toolbar
3756 @unnumberedsubsec Q3.8.1: How do I get rid of the menu (or menubar)?
3758 If you are running XEmacs 19.13 and earlier, add this command to your
3765 Starting with XEmacs 19.14 the preferred method is:
3768 (set-specifier menubar-visible-p nil)
3771 @node Q3.8.2, Q3.8.3, Q3.8.1, Customization
3772 @unnumberedsubsec Q3.8.2: Can I customize the basic menubar?
3774 For an extensive menubar, add this line to your @file{.emacs}:
3777 (load "big-menubar")
3780 If you'd like to write your own, this file provides as good a set of
3781 examples as any to start from. The file is located in
3782 @file{lisp/packages/big-menubar.el} in the XEmacs installation
3785 @node Q3.8.3, Q3.8.4, Q3.8.2, Customization
3786 @unnumberedsubsec Q3.8.3: How do I control how many buffers are listed in the menu @code{Buffers List}?
3788 Add the following to your @file{.emacs} (suit to fit):
3791 (setq buffers-menu-max-size 20)
3794 For no limit, use an argument of @samp{nil}.
3796 Starting with XEmacs-20.3 you can also change this with Customize.
3797 Select from the @code{Options} menu
3798 @code{Customize->Emacs->Environment->Menu->Buffers Menu->Max Size...} or
3799 type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}.
3801 @node Q3.8.4, Q3.8.5, Q3.8.3, Customization
3802 @unnumberedsubsec Q3.8.4: Resources like @code{Emacs*menubar*font} are not working?
3804 I am trying to use a resource like @code{Emacs*menubar*font} to set the
3805 font of the menubar but it's not working.
3807 If you are using the real Motif menubar, this resource is not
3808 recognized; you have to say:
3811 Emacs*menubar*fontList: FONT
3814 If you are using the Lucid menubar, the former resource will be
3815 recognized only if the latter resource is unset. This means that the
3825 Emacs*menubar*font: FONT
3828 even though the latter is more specific.
3830 @node Q3.8.5, Q3.9.1, Q3.8.4, Customization
3831 @unnumberedsubsec Q3.8.5: How can I bind a key to a function to toggle the toolbar?
3836 (defun my-toggle-toolbar ()
3838 (set-specifier default-toolbar-visible-p
3839 (not (specifier-instance default-toolbar-visible-p))))
3840 (global-set-key "\C-xT" 'my-toggle-toolbar)
3843 There are redisplay bugs in 19.14 that may make the preceding result in
3844 a messed-up display, especially for frames with multiple windows. You
3845 may need to resize the frame before XEmacs completely realizes the
3846 toolbar is really gone.
3848 Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct
3851 @node Q3.9.1, Q3.9.2, Q3.8.5, Customization
3852 @unnumberedsec 3.9: Scrollbars
3853 @unnumberedsubsec Q3.9.1: How can I disable the scrollbar?
3855 To disable them for all frames, add the following line to
3856 your @file{.Xdefaults}:
3859 Emacs.scrollBarWidth: 0
3862 Or select from the @code{Options} menu @code{Frame Appearance->Scrollbars}.
3863 Remember to save options.
3865 To turn the scrollbar off on a per-frame basis, use the following
3869 (set-specifier scrollbar-width 0 (selected-frame))
3872 You can actually turn the scrollbars on at any level you want by
3873 substituting for (selected-frame) in the above command. For example, to
3874 turn the scrollbars off only in a single buffer:
3877 (set-specifier scrollbar-width 0 (current-buffer))
3880 In XEmacs versions prior to 19.14, you had to use the hairier construct:
3883 (set-specifier scrollbar-width (cons (selected-frame) 0))
3886 @node Q3.9.2, Q3.9.3, Q3.9.1, Customization
3887 @unnumberedsubsec Q3.9.2: How can one use resources to change scrollbar colors?
3889 Here's a recap of how to use resources to change your scrollbar colors:
3894 Emacs*XmScrollBar.Background: skyblue
3895 Emacs*XmScrollBar.troughColor: lightgray
3899 Emacs*Scrollbar.Foreground: skyblue
3900 Emacs*Scrollbar.Background: lightgray
3903 Note the capitalization of @code{Scrollbar} for the Athena widget.
3905 @node Q3.9.3, Q3.9.4, Q3.9.2, Customization
3906 @unnumberedsubsec Q3.9.3: Moving the scrollbar can move the point; can I disable this?
3908 When I move the scrollbar in an XEmacs window, it moves the point as
3909 well, which should not be the default behavior. Is this a bug or a
3910 feature? Can I disable it?
3912 The current behavior is a feature, not a bug. Point remains at the same
3913 buffer position as long as that position does not scroll off the screen.
3914 In that event, point will end up in either the upper-left or lower-left
3917 This cannot be changed.
3919 @node Q3.9.4, Q3.10.1, Q3.9.3, Customization
3920 @unnumberedsubsec Q3.9.4: How can I get automatic horizontal scrolling?
3922 By the same token, how can I turn it off in specific modes?
3924 To do this, add to your @file{.emacs} file:
3927 (require 'auto-show)
3930 Then do @code{(setq truncate-lines t)} in the mode-hooks for any modes
3931 in which you want lines truncated.
3933 More precisely: If @code{truncate-lines} is nil, horizontal scrollbars
3934 will never appear. Otherwise, they will appear only if the value of
3935 @code{scrollbar-height} for that buffer/window/etc. is non-zero. If you
3939 (set-specifier scrollbar-height 0)
3942 then horizontal scrollbars will not appear in truncated buffers unless
3943 the package specifically asked for them.
3945 Automatic horizontal scrolling is now standard, starting with 19.14.
3947 @node Q3.10.1, Q3.10.2, Q3.9.4, Customization
3948 @unnumberedsec 3.10: Text Selections
3949 @unnumberedsubsec Q3.10.1: How can I turn off or change highlighted selections?
3951 The @code{zmacs} mode allows for what some might call gratuitous
3952 highlighting for selected regions (either by setting mark or by using
3953 the mouse). This is the default behavior. To turn off, add the
3954 following line to your @file{.emacs} file:
3957 (setq zmacs-regions nil)
3960 Starting with XEmacs-20.2 you can also change this with Customize. Select
3961 from the @code{Options} menu @code{Customize->Emacs->Editing->Basics->Zmacs
3962 Regions} or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
3964 To change the face for selection, look at @code{Options->Customize} on
3967 @node Q3.10.2, Q3.10.3, Q3.10.1, Customization
3968 @unnumberedsubsec Q3.10.2: How do I get that typing on an active region removes it?
3970 I want to change things so that if I select some text and start typing,
3971 the typed text replaces the selected text, similar to Motif.
3973 You want to use something called @dfn{pending delete}. Pending delete
3974 is what happens when you select a region (with the mouse or keyboard)
3975 and you press a key to replace the selected region by the key you typed.
3976 Usually backspace kills the selected region.
3978 To get this behavior, add the following line to your @file{.emacs}:
3981 (turn-on-pending-delete)
3984 Note that this will work with both Backspace and Delete.
3986 @node Q3.10.3, Q3.10.4, Q3.10.2, Customization
3987 @unnumberedsubsec Q3.10.3: Can I turn off the highlight during isearch?
3989 I do not like my text highlighted while I am doing isearch as I am not
3990 able to see what's underneath. How do I turn it off?
3992 Put the following in your @file{.emacs}:
3995 (setq isearch-highlight nil)
3998 Starting with XEmacs-20.2 you can also change this with Customize. Type
3999 @kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}.
4001 Note also that isearch-highlight affects query-replace and ispell.
4002 Instead of disabling isearch-highlight you may find that a better
4003 solution consists of customizing the @code{isearch} face.
4005 @node Q3.10.4, Q3.10.5, Q3.10.3, Customization
4006 @unnumberedsubsec Q3.10.4: How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
4008 Put this in your @code{.emacs}:
4011 (setq zmacs-regions nil)
4014 @strong{Warning: This command turns off all region highlighting.}
4016 Also @xref{Q3.10.1}.
4018 @node Q3.10.5, , Q3.10.4, Customization
4019 @unnumberedsubsec Q3.10.5: The region disappears when I hit the end of buffer while scrolling.
4021 This has been fixed by default starting with XEmacs-20.3.
4023 With older versions you can turn this feature (if it indeed is a feature)
4027 (defadvice scroll-up (around scroll-up freeze)
4029 (let ((zmacs-region-stays t))
4033 (end-of-buffer (goto-char (point-max))))
4036 (defadvice scroll-down (around scroll-down freeze)
4038 (let ((zmacs-region-stays t))
4042 (beginning-of-buffer (goto-char (point-min))))
4046 Thanks to @email{raman@@adobe.com, T. V. Raman} for assistance in deriving this
4049 @node Subsystems, Miscellaneous, Customization, Top
4050 @unnumbered 4 Major Subsystems
4052 This is part 4 of the XEmacs Frequently Asked Questions list. This
4053 section is devoted to major XEmacs subsystems.
4056 Reading Mail with VM:
4057 * Q4.0.1:: How do I set up VM to retrieve remote mail using POP?
4058 * Q4.0.2:: How do I get VM to filter mail for me?
4059 * Q4.0.3:: How can I get VM to automatically check for new mail?
4060 * Q4.0.4:: [This question intentionally left blank]
4061 * Q4.0.5:: How do I get my outgoing mail archived?
4062 * 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"?
4063 * Q4.0.7:: Is there a mailing list or FAQ for VM?
4064 * Q4.0.8:: Remote mail reading with VM.
4065 * Q4.0.9:: rmail or VM gets an error incorporating new mail.
4066 * Q4.0.10:: How do I make VM stay in a single frame?
4067 * Q4.0.11:: How do I make VM or mh-e display graphical smilies?
4068 * Q4.0.12:: Customization of VM not covered in the manual or here.
4070 Web browsing with W3:
4071 * Q4.1.1:: What is W3?
4072 * Q4.1.2:: How do I run W3 from behind a firewall?
4073 * Q4.1.3:: Is it true that W3 supports style sheets and tables?
4075 Reading Netnews and Mail with Gnus:
4076 * Q4.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus,argh!
4077 * Q4.2.2:: [This question intentionally left blank]
4078 * Q4.2.3:: How do I make Gnus stay within a single frame?
4079 * Q4.2.4:: How do I customize the From: line?
4082 * Q4.3.1:: How can I read and/or compose MIME messages?
4083 * Q4.3.2:: What is TM and where do I get it?
4084 * Q4.3.3:: Why isn't this @code{movemail} program working?
4085 * Q4.3.4:: Movemail is also distributed by Netscape? Can that cause problems?
4086 * Q4.3.5:: Where do I find pstogif (required by tm)?
4088 Sparcworks, EOS, and WorkShop:
4089 * Q4.4.1:: What is SPARCworks, EOS, and WorkShop
4090 * Q4.4.2:: How do I start the Sun Workshop support in XEmacs 21?
4093 * Q4.5.1:: What is/was Energize?
4096 * Q4.6.1:: What is Infodock?
4098 Other Unbundled Packages:
4099 * Q4.7.1:: What is AUC TeX? Where do you get it?
4100 * Q4.7.2:: Are there any Emacs Lisp Spreadsheets?
4101 * Q4.7.3:: Byte compiling AUC TeX on XEmacs 19.14
4102 * Q4.7.4:: Problems installing AUC TeX
4103 * Q4.7.5:: Is there a reason for an Emacs package not to be included in XEmacs?
4104 * Q4.7.6:: Is there a MatLab mode?
4107 @node Q4.0.1, Q4.0.2, Subsystems, Subsystems
4108 @unnumberedsec 4.0: Reading Mail with VM
4109 @unnumberedsubsec Q4.0.1: How do I set up VM to retrieve mail from a remote site using POP?
4111 Use @code{vm-spool-files}, like this for example:
4114 (setq vm-spool-files '("/var/spool/mail/wing"
4115 "netcom23.netcom.com:110:pass:wing:MYPASS"))
4118 Of course substitute your actual password for MYPASS.
4120 @node Q4.0.2, Q4.0.3, Q4.0.1, Subsystems
4121 @unnumberedsubsec Q4.0.2: How do I get VM to filter mail for me?
4123 One possibility is to use procmail to split your mail before it gets to
4124 VM. I prefer this personally, since there are many strange and
4125 wonderful things one can do with procmail. Procmail may be found at
4126 @uref{ftp://ftp.informatik.rwth-aachen.de/pub/packages/procmail/}.
4128 Also see the Mail Filtering FAQ at:
4132 @uref{ftp://rtfm.mit.edu/pub/usenet/news.answers/mail/filtering-faq}.
4134 @c <URL:http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html>
4137 @node Q4.0.3, Q4.0.4, Q4.0.2, Subsystems
4138 @unnumberedsubsec Q4.0.3: How can I get VM to automatically check for new mail?
4140 @email{turner@@lanl.gov, John Turner} writes:
4146 (setq vm-auto-get-new-mail 60)
4150 @node Q4.0.4, Q4.0.5, Q4.0.3, Subsystems
4151 @unnumberedsubsec Q4.0.4: [This question intentionally left blank]
4153 Obsolete question, left blank to avoid renumbering.
4155 @node Q4.0.5, Q4.0.6, Q4.0.4, Subsystems
4156 @unnumberedsubsec Q4.0.5: How do I get my outgoing mail archived?
4159 (setq mail-archive-file-name "~/outbox")
4162 @node Q4.0.6, Q4.0.7, Q4.0.5, Subsystems
4163 @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"?
4165 Set @code{vm-reply-ignored-addresses} to a list, like
4168 (setq vm-reply-ignored-addresses
4169 '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com"
4170 "wing@@netcom.com" "wing@@xemacs.org"))
4173 Note that each string is a regular expression.
4175 @node Q4.0.7, Q4.0.8, Q4.0.6, Subsystems
4176 @unnumberedsubsec Q4.0.7: Is there a mailing list or FAQ for VM?
4178 A FAQ for VM exists at @uref{http://www.cyberpass.net/~gorkab/vmfaq.htm}.
4180 VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug.
4182 @node Q4.0.8, Q4.0.9, Q4.0.7, Subsystems
4183 @unnumberedsubsec Q4.0.8: Remote mail reading with VM.
4185 My mailbox lives at the office on a big honkin server. My regular INBOX
4186 lives on my honkin desktop machine. I now can PPP to the office from
4187 home which is far from honking... I'd like to be able to read mail at
4188 home without storing it here and I'd like to use xemacs and VM at
4189 home... Is there a recommended setup?
4191 @email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes:
4194 There are several ways to do this.
4198 Set your display to your home machine and run dxpc or one of the other X
4202 NFS mount your desktop machine on your home machine and modify your pop
4203 command on your home machine to rsh to your desktop machine and actually
4207 Run a POP server on your desktop machine as well and do a sort of two
4212 @email{wmperry@@monolith.spry.com, William Perry} adds:
4215 Or you could run a pop script periodically on your desktop machine, and
4216 just use ange-ftp or NFS to get to your mailbox. I used to do this all
4217 the time back at IU.
4220 @node Q4.0.9, Q4.0.10, Q4.0.8, Subsystems
4221 @unnumberedsubsec Q4.0.9: rmail or VM gets an error incorporating new mail.
4223 Quoting the XEmacs PROBLEMS file:
4226 rmail and VM get new mail from @file{/usr/spool/mail/$USER} using a
4227 program called @code{movemail}. This program interlocks with
4228 @code{/bin/mail} using the protocol defined by @code{/bin/mail}.
4230 There are two different protocols in general use. One of them uses the
4231 @code{flock} system call. The other involves creating a lock file;
4232 @code{movemail} must be able to write in @file{/usr/spool/mail} in order
4233 to do this. You control which one is used by defining, or not defining,
4234 the macro @code{MAIL_USE_FLOCK} in @file{config.h} or the m- or s- file
4237 @strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
4238 SYSTEM, YOU CAN LOSE MAIL!}
4240 If your system uses the lock file protocol, and fascist restrictions
4241 prevent ordinary users from writing the lock files in
4242 @file{/usr/spool/mail}, you may need to make @code{movemail} setgid to a
4243 suitable group such as @samp{mail}. You can use these commands (as
4251 If your system uses the lock file protocol, and fascist restrictions
4252 prevent ordinary users from writing the lock files in
4253 @file{/usr/spool/mail}, you may need to make @code{movemail} setgid to a
4254 suitable group such as @code{mail}. To do this, use the following
4255 commands (as root) after doing the make install.
4262 Installation normally copies movemail from the build directory to an
4263 installation directory which is usually under @file{/usr/local/lib}.
4264 The installed copy of @code{movemail} is usually in the directory
4265 @file{/usr/local/lib/emacs/VERSION/TARGET}. You must change the group
4266 and mode of the installed copy; changing the group and mode of the build
4267 directory copy is ineffective.
4270 @node Q4.0.10, Q4.0.11, Q4.0.9, Subsystems
4271 @unnumberedsubsec Q4.0.10: How do I make VM stay in a single frame?
4273 John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes:
4277 ; Don't use multiple frames
4278 (setq vm-frame-per-composition nil)
4279 (setq vm-frame-per-folder nil)
4280 (setq vm-frame-per-edit nil)
4281 (setq vm-frame-per-summary nil)
4285 @node Q4.0.11, Q4.0.12, Q4.0.10, Subsystems
4286 @unnumberedsubsec Q4.0.11: How do I make VM or mh-e display graphical smilies?
4288 For mh-e use the following:
4291 (add-hook 'mh-show-mode-hook '(lambda ()
4292 (smiley-region (point-min)
4296 @email{bill@@carpenter.ORG, WJCarpenter} writes:
4297 For VM use the following:
4299 (autoload 'smiley-region "smiley" nil t)
4300 (add-hook 'vm-select-message-hook
4302 (smiley-region (point-min)
4306 For tm use the following:
4308 (autoload 'smiley-buffer "smiley" nil t)
4309 (add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer)
4312 @node Q4.0.12, Q4.1.1, Q4.0.11, Subsystems
4313 @unnumberedsubsec Q4.0.12: Customization of VM not covered in the manual, or here.
4315 @email{boffi@@hp735.stru.polimi.it, giacomo boffi} writes:
4318 The meta-answer is to look into the file @file{vm-vars.el}, in the vm
4319 directory of the lisp library.
4321 @file{vm-vars.el} contains, initializes and carefully describes, with
4322 examples of usage, the plethora of user options that @emph{fully}
4323 control VM's behavior.
4325 Enter vm-vars, @code{forward-search} for toolbar, find the variables
4326 that control the toolbar placement, appearance, existence, copy to your
4327 @file{.emacs} or @file{.vm} and modify according to the detailed
4330 The above also applies to all the various features of VM: search for
4331 some keywords, maybe the first you conjure isn't appropriate, find the
4332 appropriate variables, copy and experiment.
4335 @node Q4.1.1, Q4.1.2, Q4.0.12, Subsystems
4336 @unnumberedsec 4.1: Web browsing with W3
4337 @unnumberedsubsec Q4.1.1: What is W3?
4339 W3 is an advanced graphical browser written in Emacs lisp that runs on
4340 XEmacs. It has full support for cascaded style sheets, and more...
4342 It has a home web page at
4343 @uref{http://www.cs.indiana.edu/elisp/w3/docs.html}.
4345 @node Q4.1.2, Q4.1.3, Q4.1.1, Subsystems
4346 @unnumberedsubsec Q4.1.2: How do I run W3 from behind a firewall?
4348 There is a long, well-written, detailed section in the W3 manual that
4349 describes how to do this. Look in the section entitled "Firewalls".
4351 @node Q4.1.3, Q4.2.1, Q4.1.2, Subsystems
4352 @unnumberedsubsec Q4.1.3: Is it true that W3 supports style sheets and tables?
4354 Yes, and much more. W3, as distributed with the latest XEmacs is a
4355 full-featured web browser.
4357 @node Q4.2.1, Q4.2.2, Q4.1.3, Subsystems
4358 @unnumberedsec 4.2: Reading Netnews and Mail with Gnus
4359 @unnumberedsubsec Q4.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
4361 The Gnus numbering issues are not meant for mere mortals to know them.
4362 If you feel you @emph{must} enter the muddy waters of Gnus, visit the
4363 excellent FAQ, maintained by Justin Sheehy, at:
4366 @uref{http://www.ccs.neu.edu/software/contrib/gnus/}
4369 See also Gnus home page
4371 @uref{http://www.gnus.org/}
4374 @node Q4.2.2, Q4.2.3, Q4.2.1, Subsystems
4375 @unnumberedsubsec Q4.2.2: This question intentionally left blank.
4377 Obsolete question, left blank to avoid renumbering.
4379 @node Q4.2.3, Q4.2.4, Q4.2.2, Subsystems
4380 @unnumberedsubsec Q4.2.3: How do I make Gnus stay within a single frame?
4382 The toolbar code to start Gnus opens the new frame---and it's a feature
4383 rather than a bug. If you don't like it, but would still like to click
4384 on the seemly icon, use the following code:
4387 (defun toolbar-news ()
4391 It will redefine the callback function of the icon to just call
4392 @code{gnus}, without all the fancy frame stuff.
4394 @node Q4.2.4, Q4.3.1, Q4.2.3, Subsystems
4395 @unnumberedsubsec Q4.2.4: How do I customize the From: line?
4397 How do I change the @code{From:} line? I have set gnus-user-from-line
4400 Gail Gurman <gail.gurman@@sybase.com>
4402 @noindent , but XEmacs Gnus doesn't use
4405 Gail Mara Gurman @email{gailg@@deall}
4407 @noindent and then complains
4408 that it's incorrect. Also, as you perhaps can see, my Message-ID is
4409 screwy. How can I change that?
4411 @email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes:
4414 Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or
4415 @code{mail-host-address} to @samp{sybase.com}.
4418 @node Q4.3.1, Q4.3.2, Q4.2.4, Subsystems
4419 @unnumberedsec 4.3: Other Mail & News
4420 @unnumberedsubsec Q4.3.1: How can I read and/or compose MIME messages?
4423 VM supports MIME natively.
4425 You probably want to use the Tools for MIME (tm). @xref{Q4.3.2}, for
4428 @email{trey@@cs.berkeley.edu, Trey Jackson} has an Emacs & MIME web page at
4432 @uref{http://bmrc.berkeley.edu/~trey/emacs/mime.html}.
4435 Another possibility is RMIME. You may find RMIME at
4439 @uref{http://www.cinti.net/~rmoody/rmime/index.html}.
4442 @node Q4.3.2, Q4.3.3, Q4.3.1, Subsystems
4443 @unnumberedsubsec Q4.3.2: What is TM and where do I get it?
4445 TM stands for @dfn{Tools for MIME} and not Tiny MIME. TM integrates
4446 with all major XEmacs packages like Gnus (all flavors), VM, MH-E, and
4447 mailcrypt. It provides totally transparent and trouble-free MIME
4448 support. When appropriate a message will be decoded in place in an
4451 TM now comes as a package with XEmacs 19.16 and XEmacs 20.2.
4453 TM was written by @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} and
4454 @email{shuhei-k@@jaist.ac.jp, KOBAYASHI
4457 It is based on the work of @email{umerin@@mse.kyutech.ac.jp, UMEDA
4458 Masanobu}, the original writer of GNUS.
4460 The following information is from the @file{README}:
4462 @dfn{tm} is a MIME package for GNU Emacs.
4463 tm has following functions:
4466 @item MIME style multilingual header.
4467 @item MIME message viewer (mime/viewer-mode).
4468 @item MIME message composer (mime/editor-mode).
4469 @item MIME extenders for mh-e, GNUS, RMAIL and VM.
4472 tm is available from following anonymous ftp sites:
4474 @item @uref{ftp://ftp.jaist.ac.jp/pub/GNU/elisp/mime/} (Japan).
4475 @item @uref{ftp://ftp.nis.co.jp/pub/gnu/emacs-lisp/tm/} (Japan).
4476 @c The host above is unknown.
4478 @item @uref{ftp://ftp.nisiq.net/pub/gnu/emacs-lisp/tm/} (US).
4479 @item @uref{ftp://ftp.miranova.com/pub/gnus/jaist.ac.jp/} (US).
4480 @item @uref{ftp://ftp.unicamp.br/pub/mail/mime/tm/} (Brasil).
4481 @item @uref{ftp://ftp.th-darmstadt.de/pub/editors/GNU-Emacs/lisp/mime/} (Germany).
4482 @item @uref{ftp://ftp.tnt.uni-hannover.de/pub/editors/xemacs/contrib/} (Germany).
4485 Don't let the installation procedure & instructions stop you from trying
4486 this package out---it's much simpler than it looks, and once installed,
4489 @node Q4.3.3, Q4.3.4, Q4.3.2, Subsystems
4490 @unnumberedsubsec Q4.3.3: Why isn't this @code{movemail} program working?
4492 Ben Wing @email{ben@@xemacs.org} writes:
4495 It wasn't chown'ed/chmod'd correctly.
4498 @node Q4.3.4, Q4.3.5, Q4.3.3, Subsystems
4499 @unnumberedsubsec Q4.3.4: Movemail is also distributed by Netscape? Can that cause problems?
4501 @email{steve@@xemacs.org, Steve Baur} writes:
4504 Yes. Always use the movemail installed with your XEmacs. Failure to do
4505 so can result in lost mail.
4508 Please refer to @email{jwz@@jwz.org, Jamie Zawinski's} notes at
4512 @uref{http://home.netscape.com/eng/mozilla/2.0/relnotes/demo/movemail.html}.
4513 In particular, this document will show you how to make Netscape use the
4514 version of movemail configured for your system by the person who built
4517 @node Q4.3.5, Q4.4.1, Q4.3.4, Subsystems
4518 @unnumberedsubsec Q4.3.5: Where do I find pstogif (required by tm)?
4520 pstogif is part of the latex2html package.
4522 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
4524 latex2html is best found at the CTAN hosts and their mirrors
4529 @file{tex-archive/support/latex2html}.
4534 @item @uref{ftp://ftp.tex.ac.uk/tex-archive/support/latex2html/}.
4535 @item @uref{ftp://ftp.dante.de/tex-archive/support/latex2html/}.
4538 There is a good mirror at ftp.cdrom.com;
4542 @uref{ftp://ftp.cdrom.com/pub/tex/ctan/support/latex2html/}.
4544 @node Q4.4.1, Q4.4.2, Q4.3.5, Subsystems
4545 @unnumberedsec 4.4: Sparcworks, EOS, and WorkShop
4546 @unnumberedsubsec Q4.4.1: What is SPARCworks, EOS, and WorkShop?
4548 @email{turner@@lanl.gov, John Turner} writes:
4551 SPARCworks is SunSoft's development environment, comprising compilers
4552 (C, C++, FORTRAN 77, Fortran 90, Ada, and Pascal), a debugger, and other
4553 tools such as TeamWare (for configuration management), MakeTool, etc.
4556 See @uref{http://www.sun.com/software/Developer-products/}
4559 EOS stands for "Era on SPARCworks", but I don't know what Era stands
4562 EOS is the integration of XEmacs with the SPARCworks debugger. It
4563 allows one to use an XEmacs frame to view code (complete with
4564 fontification, etc.), set breakpoints, print variables, etc., while
4565 using the SPARCworks debugger. It works very well and I use it all the
4568 @email{cthomp@@xemacs.org, Chuck Thompson} writes:
4571 Era stood for "Emacs Rewritten Again". It was what we were calling the
4572 modified version of Lucid Emacs for Sun when I was dragged, er, allowed
4573 to work on this wonderful editor.
4576 @email{martin@@xemacs.org, Martin Buchholz} writes:
4579 EOS is being replaced with a new graphical development environment
4580 called Sun WorkShop, which is currently (07/96) in Alpha Test. For more
4585 @uref{http://www.sun.com/software/Products/Developer-products/programs.html}.
4588 @node Q4.4.2, Q4.5.1, Q4.4.1, Subsystems
4589 @unnumberedsubsec Q4.4.2: How do I start the Sun Workshop support in XEmacs 21?
4591 Add the switch ---with-workshop to the configure command when building
4592 XEmacs and put the following in one of your startup files
4593 (e.g. site-start.el or .emacs):
4596 (when (featurep 'tooltalk)
4597 (load "tooltalk-macros")
4598 (load "tooltalk-util")
4599 (load "tooltalk-init"))
4600 (when (featurep 'sparcworks)
4601 (load "sunpro-init")
4604 (load "annotations")
4608 If you are not using the latest Workshop (5.0) you have to apply the
4612 --- /opt/SUNWspro/lib/eserve.el.ORIG Fri May 14 15:23:26 1999
4613 +++ /opt/SUNWspro/lib/eserve.el Fri May 14 15:24:54 1999
4614 @@@@ -42,7 +42,7 @@@@
4615 (defvar running-xemacs nil "t if we're running XEmacs")
4616 (defvar running-emacs nil "t if we're running GNU Emacs 19")
4618 -(if (string-match "^\\(19\\|20\\)\..*\\(XEmacs\\|Lucid\\)" emacs-version)
4619 +(if (string-match "\\(XEmacs\\|Lucid\\)" emacs-version)
4620 (setq running-xemacs t)
4621 (setq running-emacs t))
4626 @node Q4.5.1, Q4.6.1, Q4.4.2, Subsystems
4627 @unnumberedsec 4.5: Energize
4628 @unnumberedsubsec Q4.5.1: What is/was Energize?
4630 @email{gray@@meteor.harlequin.com, David N Gray} writes:
4632 The files in @file{lisp/energize} are to enable Emacs to interface with
4633 the "Energize Programming System", a C and C++ development environment,
4634 which was a product of Lucid, Inc. Tragically, Lucid went out of
4635 business in 1994, so although Energize is still a great system, if you
4636 don't already have it, there isn't any way to get it now. (Unless you
4637 happen to be in Japan; INS Engineering may still be selling it there.
4638 Tartan bought the rights to sell it in the rest of the world, but never
4642 @node Q4.6.1, Q4.7.1, Q4.5.1, Subsystems
4643 @unnumberedsec 4.6: Infodock
4644 @unnumberedsubsec Q4.6.1: What is Infodock?
4646 InfoDock is an integrated productivity toolset, mainly aimed at
4647 technical people. It is developed and supported by InfoDock
4648 Associates, a firm that offers custom support and development
4649 for InfoDock, XEmacs and GNU Emacs. ( @uref{http://www.infodock.com},
4650 @email{info@@infodock.com}, +1 408 243 3300).
4652 InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of
4653 the power of Emacs, but with an easier to use and more comprehensive
4654 menu-based user interface. The bottom portion of this text describes
4655 how it differs from XEmacs and GNU Emacs from the Free Software
4658 InfoDock is aimed at people who want a free, turn-key productivity
4659 environment. Although InfoDock is customizable, it is not intended for
4660 people who like basic versions of Emacs which need to be customized
4661 extensively for local use; standard Emacs distributions are better for
4662 such uses. InfoDock is for those people who want a complete,
4663 pre-customized environment in one package, which they need not touch
4664 more than once or twice a year to update to new revisions.
4666 InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX,
4667 and Intel Linux systems. It is intended for use on a color display,
4668 although most features will work on monochrome monitors. Simply unpack
4669 InfoDock according to the instructions in the ID-INSTALL file and you
4672 The InfoDock Manual is concise, yet sufficient as a user guide for users
4673 who have never used an Emacs-type editor before. For users who are
4674 already familiar with Emacs, it supplements the information in the GNU
4677 InfoDock menus are much more extensive and more mature than standard
4678 Emacs menus. Each menu offers a @samp{Manual} item which displays
4679 documentation associated with the menu's functions.
4682 Four types of menubars are provided:
4685 An extensive menubar providing access to global InfoDock commands.
4687 Mode-specific menubars tailored to the current major mode.
4689 A simple menubar for basic editing to help novices get started with InfoDock.
4691 The standard XEmacs menubar.
4694 Most modes also include mode-specific popup menus. Additionally, region and
4695 rectangle popup menus are included.
4697 @samp{Hyperbole}, the everyday information manager, is a core part of
4698 InfoDock. This provides context-sensitive mouse keys, a rolodex-type
4699 contact manager, programmable hypertext buttons, and an autonumbered
4700 outliner with embedded hyperlink anchors.
4702 The @samp{OO-Browser}, a multi-language object-oriented code browser, is a
4703 standard part of InfoDock.
4705 InfoDock saves a more extensive set of user options than other Emacs
4708 InfoDock inserts a useful file header in many file types, showing the
4709 author, summary, and last modification time of each file. A summary
4710 program can then be used to summarize all of the files in a directory,
4711 for easy MANIFEST file creation.
4713 Your working set of buffers is automatically saved and restored (if you
4714 answer yes to a prompt) between InfoDock sessions.
4716 Refined color choices for code highlighting are provided for both dark and
4717 light background display frames.
4719 The @kbd{C-z} key prefix performs frame-based commands which parallel the
4720 @kbd{C-x} key prefix for window-based commands.
4722 The Smart Menu system is included for producing command menus on dumb
4725 Lisp libraries are better categorized according to function.
4727 Extensions and improvements to many areas of Emacs are included, such as:
4728 paragraph filling, mail reading with Rmail, shell handling, outlining, code
4729 highlighting and browsing, and man page browsing.
4731 InfoDock questions, answers and discussion should go to the mail list
4735 @email{infodock@@infodock.com}. Use
4736 @email{infodock-request@@infodock.com} to be added or removed from the
4737 list. Always include your InfoDock version number when sending help
4740 InfoDock is available across the Internet via anonymous FTP. To get
4741 it, first move to a directory into which you want the InfoDock archive
4742 files placed. We will call this <DIST-DIR>.
4748 Ftp to ftp.xemacs.org (Internet Host ID = 128.174.252.16):
4751 prompt> ftp ftp.xemacs.org
4754 Login as @samp{anonymous} with your own <user-id>@@<site-name> as a password.
4757 Name (ftp.xemacs.org): anonymous
4758 331 Guest login ok, send your complete e-mail address as password.
4759 Password: -<your-user-id>@@<your-domain>
4760 230 Guest login ok, access restrictions apply.
4763 Move to the location of the InfoDock archives:
4766 ftp> cd pub/infodock
4769 Set your transfer mode to binary:
4780 Interactive mode off.
4783 Retrieve the InfoDock archives that you want, either by using a
4784 @samp{get <file>} for each file you want or by using the following to
4785 get a complete distribution, including all binaries:
4788 ftp> mget ID-INSTALL
4792 Close the FTP connection:
4799 Read the @file{ID-INSTALL} file which you just retrieved for
4800 step-by-step installation instructions.
4802 @node Q4.7.1, Q4.7.2, Q4.6.1, Subsystems
4803 @unnumberedsec 4.7: Other Unbundled Packages
4804 @unnumberedsubsec Q4.7.1: What is AUC TeX? Where do you get it?
4806 AUC TeX is a package written by @email{abraham@@dina.kvl.dk, Per Abrahamsen}.
4807 Starting with XEmacs 19.16, AUC TeX is bundled with XEmacs. The
4808 following information is from the @file{README} and website.
4810 AUC TeX is an extensible package that supports writing and formatting
4811 TeX files for most variants of GNU Emacs. Many different macro packages
4812 are supported, including AMS TeX, LaTeX, and TeXinfo.
4814 The most recent version is always available by ftp at
4818 @uref{ftp://sunsite.auc.dk/packages/auctex/auctex.tar.gz}.
4820 In case you don't have access to anonymous ftp, you can get it by an
4821 email request to @email{ftpmail@@decwrl.dec.com}.
4823 WWW users may want to check out the AUC TeX page at
4827 @uref{http://sunsite.auc.dk/auctex/}.
4829 @node Q4.7.2, Q4.7.3, Q4.7.1, Subsystems
4830 @unnumberedsubsec Q4.7.2: Are there any Emacs Lisp Spreadsheets?
4832 Yes. Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at
4836 @uref{ftp://cs.nyu.edu/pub/local/fox/dismal/}.
4838 @node Q4.7.3, Q4.7.4, Q4.7.2, Subsystems
4839 @unnumberedsubsec Q4.7.3: Byte compiling AUC TeX on XEmacs 19.14.
4841 @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan} writes:
4844 When byte compiling auctex-9.4g, you must use the command:
4847 xemacs -batch -l lpath.el
4851 @node Q4.7.4, Q4.7.5, Q4.7.3, Subsystems
4852 @unnumberedsubsec Q4.7.4: Problems installing AUC TeX.
4854 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
4857 AUC TeX works fine on both stock Emacs and XEmacs has been doing so for
4858 a very very long time. This is mostly due to the work of
4859 @email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu}
4860 package. Which leads to what is probably the problem...
4863 Most problems with AUC TeX are one of two things:
4867 The TeX-lisp-directory in @file{tex-site.el} and the makefile don't
4870 Fix: make sure you configure AUC TeX properly @strong{before} installing.
4873 You have an old version of easymenu.el in your path.
4875 Fix: use @code{locate-library} and remove old versions to make sure it
4876 @strong{only} finds the one that came with XEmacs.
4880 @node Q4.7.5, Q4.7.6, Q4.7.4, Subsystems
4881 @unnumberedsubsec Q4.7.5: Is there a reason for an Emacs package not to be included in XEmacs?
4883 The reason for an Emacs package not to be included in XEmacs is
4884 usually one or more of the following:
4888 The package has not been ported to XEmacs. This will typically happen
4889 when it uses GNU-Emacs-specific features, which make it fail under
4892 Porting a package to XEmacs can range from a trivial amount of change to
4893 a partial or full rewrite. Fortunately, the authors of modern packages
4894 usually choose to support both Emacsen themselves.
4897 The package has been decided not to be appropriate for XEmacs. It may
4898 have an equivalent or better replacement within XEmacs, in which case
4899 the developers may choose not to burden themselves with supporting an
4902 Each package bundled with XEmacs means more work for the maintainers,
4903 whether they want it or not. If you are ready to take over the
4904 maintenance responsibilities for the package you port, be sure to say
4905 so -- we will more likely include it.
4908 The package simply hasn't been noted by the XEmacs development. If
4909 that's the case, the messages like yours are very useful for attracting
4913 The package was noted by the developers, but they simply haven't yet
4914 gotten around to including/porting it. Wait for the next release or,
4915 even better, offer your help. It will be gladly accepted and
4919 @node Q4.7.6, , Q4.7.5, Subsystems
4920 @unnumberedsubsec Q4.7.5: Is there a MatLab mode?
4922 Is there any way I can get syntax highlighting for MatLab .m files?
4923 Can I "teach" emacs what words are MatLab commands, comments, etc. ?
4925 @email{elsner@@mathematik.tu-chemnitz.de, Ulrich Elsner} writes:
4927 One way to do this (and much more) is by using the
4931 @uref{ftp://ftp.mathworks.com/pub/contrib/v5/tools/matlab.el, matlab mode}.
4933 Instructions on how to install this mode are included in this file.
4937 @node Miscellaneous, Current Events, Subsystems, Top
4938 @unnumbered 5 The Miscellaneous Stuff
4940 This is part 5 of the XEmacs Frequently Asked Questions list. This
4941 section is devoted to anything that doesn't fit neatly into the other
4945 Major & Minor Modes:
4946 * Q5.0.1:: How can I do source code highlighting using font-lock?
4947 * Q5.0.2:: I do not like cc-mode. How do I use the old c-mode?
4948 * Q5.0.3:: How do I get @samp{More} Syntax Highlighting on by default?
4949 * Q5.0.4:: How can I enable auto-indent?
4950 * Q5.0.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
4951 * Q5.0.6:: How do I start up a second shell buffer?
4952 * Q5.0.7:: Telnet from shell filters too much.
4953 * Q5.0.8:: Why does edt emulation not work?
4954 * Q5.0.9:: How can I emulate VI and use it as my default mode?
4955 * Q5.0.10:: [This question intentionally left blank]
4956 * Q5.0.11:: Filladapt doesn't work in 19.15?
4957 * Q5.0.12:: How do I disable gnuserv from opening a new frame?
4958 * Q5.0.13:: How do I start gnuserv so that each subsequent XEmacs is a client?
4959 * Q5.0.14:: Strange things are happening in Shell Mode.
4960 * Q5.0.15:: Where do I get the latest CC Mode?
4961 * Q5.0.16:: I find auto-show-mode disconcerting. How do I turn it off?
4962 * Q5.0.17:: How can I get two instances of info?
4963 * Q5.0.18:: I upgraded to XEmacs 19.14 and gnuserv stopped working
4964 * Q5.0.19:: Is there something better than LaTeX mode?
4965 * Q5.0.20:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
4967 Emacs Lisp Programming Techniques:
4968 * Q5.1.1:: The difference in key sequences between XEmacs and GNU Emacs?
4969 * Q5.1.2:: Can I generate "fake" keyboard events?
4970 * Q5.1.3:: Could you explain @code{read-kbd-macro} in more detail?
4971 * Q5.1.4:: What is the performance hit of @code{let}?
4972 * Q5.1.5:: What is the recommended use of @code{setq}?
4973 * Q5.1.6:: What is the typical misuse of @code{setq}?
4974 * Q5.1.7:: I like the the @code{do} form of cl, does it slow things down?
4975 * Q5.1.8:: I like recursion, does it slow things down?
4976 * Q5.1.9:: How do I put a glyph as annotation in a buffer?
4977 * Q5.1.10:: @code{map-extents} won't traverse all of my extents!
4978 * Q5.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
4981 * Q5.2.1:: How do I turn off the sound?
4982 * Q5.2.2:: How do I get funky sounds instead of a boring beep?
4983 * Q5.2.3:: What's NAS, how do I get it?
4984 * Q5.2.4:: Sunsite sounds don't play.
4987 * Q5.3.1:: How do you make XEmacs indent CL if-clauses correctly?
4988 * Q5.3.2:: Fontifying hangs when editing a postscript file.
4989 * Q5.3.3:: How can I print WYSIWYG a font-locked buffer?
4990 * Q5.3.4:: Getting @kbd{M-x lpr} to work with postscript printer.
4991 * Q5.3.5:: How do I specify the paths that XEmacs uses for finding files?
4992 * Q5.3.6:: [This question intentionally left blank]
4993 * Q5.3.7:: Can I have the end of the buffer delimited in some way?
4994 * Q5.3.8:: How do I insert today's date into a buffer?
4995 * Q5.3.9:: Are only certain syntactic character classes available for abbrevs?
4996 * Q5.3.10:: How can I get those oh-so-neat X-Face lines?
4997 * Q5.3.11:: How do I add new Info directories?
4998 * Q5.3.12:: What do I need to change to make printing work?
5001 @node Q5.0.1, Q5.0.2, Miscellaneous, Miscellaneous
5002 @unnumberedsec 5.0: Major & Minor Modes
5003 @unnumberedsubsec Q5.0.1: How can I do source code highlighting using font-lock?
5005 For most modes, font-lock is already set up and just needs to be turned
5006 on. This can be done by @kbd{M-x font-lock-mode}, or by having XEmacs
5007 automatically start it by adding lines like:
5010 (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
5011 (add-hook 'dired-mode-hook 'turn-on-font-lock)
5014 to your @file{.emacs}. See the file @file{etc/sample.emacs} for more
5017 See also @code{Syntax Highlighting} from the @code{Options} menu.
5018 Remember to save options.
5020 @node Q5.0.2, Q5.0.3, Q5.0.1, Miscellaneous
5021 @unnumberedsubsec Q5.0.2: I do not like cc-mode. How do I use the old c-mode?
5023 Well, first off, consider if you really want to do this. cc-mode is
5024 much more powerful than the old c-mode. If you're having trouble
5025 getting your old offsets to work, try using @code{c-set-offset} instead.
5026 You might also consider using the package @code{cc-compat}.
5028 But, if you still insist, add the following lines to your @file{.emacs}:
5031 (fmakunbound 'c-mode)
5032 (makunbound 'c-mode-map)
5033 (fmakunbound 'c++-mode)
5034 (makunbound 'c++-mode-map)
5035 (makunbound 'c-style-alist)
5036 (load-library "old-c-mode")
5037 (load-library "old-c++-mode")
5040 This must be done before any other reference is made to either c-mode or
5043 @node Q5.0.3, Q5.0.4, Q5.0.2, Miscellaneous
5044 @unnumberedsubsec Q5.0.3: How do I get @samp{More} Syntax Highlighting on by default?
5046 Use the following code in your @file{.emacs}:
5049 (setq-default font-lock-maximum-decoration t)
5052 In versions of XEmacs prior to 19.14, you had to use a kludgy solution
5056 (setq c-font-lock-keywords c-font-lock-keywords-2
5057 c++-font-lock-keywords c++-font-lock-keywords-2
5058 lisp-font-lock-keywords lisp-font-lock-keywords-2)
5061 It will work for C, C++ and Lisp.
5063 See also @code{Syntax Highlighting} from the @code{Options} menu.
5064 Remember to save options.
5066 @node Q5.0.4, Q5.0.5, Q5.0.3, Miscellaneous
5067 @unnumberedsubsec Q5.0.4: How can I enable auto-indent?
5069 Put the following line in your @file{.emacs}:
5072 (setq indent-line-function 'indent-relative-maybe)
5075 If you want to get fancy, try the @code{filladapt} package available
5076 standard with XEmacs. Put this into your @file{.emacs}:
5079 (require 'filladapt)
5080 (add-hook 'text-mode-hook 'turn-on-filladapt-mode)
5084 You can customize filling and adaptive filling with Customize.
5085 Select from the @code{Options} menu
5086 @code{Customize->Emacs->->Editing->Fill->Fill...}
5087 or type @kbd{M-x customize @key{RET} fill @key{RET}}.
5089 Note that well-behaving text-lookalike modes will run
5090 @code{text-mode-hook} by default (e.g. that's what Message does). For
5091 the nasty ones, you'll have to provide the @code{add-hook}s yourself.
5093 Please note that the @code{fa-extras} package is no longer useful.
5095 @node Q5.0.5, Q5.0.6, Q5.0.4, Miscellaneous
5096 @unnumberedsubsec Q5.0.5: How can I get XEmacs to come up in text/auto-fill mode by default?
5098 Try the following lisp in your @file{.emacs}:
5101 (setq default-major-mode 'text-mode)
5102 (setq text-mode-hook 'turn-on-auto-fill)
5105 @strong{WARNING}: note that changing the value of
5106 @code{default-major-mode} from @code{fundamental-mode} can break a large
5107 amount of built-in code that expects newly created buffers to be in
5108 @code{fundamental-mode}. (Changing from @code{fundamental-mode} to
5109 @code{text-mode} might not wreak too much havoc, but changing to
5110 something more exotic like a lisp-mode would break many Emacs packages).
5112 Note that Emacs by default starts up in buffer @code{*scratch*} in
5113 @code{initial-major-mode}, which defaults to
5114 @code{lisp-interaction-mode}. Thus adding the following form to your
5115 Emacs init file will cause the initial @code{*scratch*} buffer to be put
5116 into auto-fill'ed @code{text-mode}:
5119 (setq initial-major-mode
5122 (turn-on-auto-fill)))
5125 Note that after your init file is loaded, if
5126 @code{inhibit-startup-message} is @code{nil} (the default) and the
5127 startup buffer is @code{*scratch*} then the startup message will be
5128 inserted into @code{*scratch*}; it will be removed after a timeout by
5129 erasing the entire @code{*scratch*} buffer. Keep in mind this default
5130 usage of @code{*scratch*} if you desire any prior manipulation of
5131 @code{*scratch*} from within your Emacs init file. In particular,
5132 anything you insert into @code{*scratch*} from your init file will be
5133 later erased. Also, if you change the mode of the @code{*scratch*}
5134 buffer, be sure that this will not interfere with possible later
5135 insertion of the startup message (e.g. if you put @code{*scratch*} into
5136 a nonstandard mode that has automatic font lock rules, then the startup
5137 message might get fontified in a strange foreign manner, e.g. as code in
5138 some programming language).
5140 @node Q5.0.6, Q5.0.7, Q5.0.5, Miscellaneous
5141 @unnumberedsubsec Q5.0.6: How do I start up a second shell buffer?
5143 In the @code{*shell*} buffer:
5146 M-x rename-buffer @key{RET} *shell-1* @key{RET}
5150 This will then start a second shell. The key is that no buffer named
5151 @samp{*shell*} can exist. It might be preferable to use @kbd{M-x
5152 rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x
5155 Alternately, you can set the variable @code{shell-multiple-shells}.
5156 If the value of this variable is non-nil, each time shell mode is invoked,
5159 @node Q5.0.7, Q5.0.8, Q5.0.6, Miscellaneous
5160 @unnumberedsubsec Q5.0.7: Telnet from shell filters too much
5162 I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke
5163 and use a telnet session within it. Everything works fine except that
5164 now all @samp{^M}'s are filtered out by Emacs. Fixes?
5166 Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather
5167 than doing rsh or telnet within the local shell buffer. Starting with
5168 XEmacs-20.3 you can also use @kbd{M-x ssh} to open secure remote session
5169 if you have @code{ssh} installed.
5171 @node Q5.0.8, Q5.0.9, Q5.0.7, Miscellaneous
5172 @unnumberedsubsec Q5.0.8: Why does edt emulation not work?
5174 We don't know, but you can use tpu-edt emulation instead, which works
5175 fine and is a little fancier than the standard edt emulation. To do
5176 this, add the following line to your @file{.emacs}:
5182 If you don't want it to replace @kbd{C-h} with an edt-style help menu
5186 (global-set-key [(control h)] 'help-for-help)
5189 @node Q5.0.9, Q5.0.10, Q5.0.8, Miscellaneous
5190 @unnumberedsubsec Q5.0.9: How can I emulate VI and use it as my default mode?
5192 Our recommended VI emulator is viper. To make viper-mode the default,
5193 add this to your @file{.emacs}:
5199 @email{kifer@@CS.SunySB.EDU, Michael Kifer} writes:
5202 This should be added as close to the top of @file{.emacs} as you can get
5203 it, otherwise some minor modes may not get viper-ized.
5206 @node Q5.0.10, Q5.0.11, Q5.0.9, Miscellaneous
5207 @unnumberedsubsec Q5.0.10: [This question intentionally left blank]
5209 Obsolete question, left blank to avoid renumbering
5211 @node Q5.0.11, Q5.0.12, Q5.0.10, Miscellaneous
5212 @unnumberedsubsec Q5.0.11: Filladapt doesn't work in 19.15
5214 Filladapt 2.x is included in 19.15. In it filladapt is now a minor
5215 mode and minor modes are traditionally off by default. The following
5216 added to your @file{.emacs} will turn it on for all buffers:
5219 (setq-default filladapt-mode t)
5222 Use @code{turn-on-filladapt-mode} to turn Filladapt on in particular
5223 major modes, like this:
5226 (add-hook 'text-mode-hook 'turn-on-filladapt-mode)
5229 @node Q5.0.12, Q5.0.13, Q5.0.11, Miscellaneous
5230 @unnumberedsubsec Q5.0.12: How do I disable gnuserv from opening a new frame?
5232 If you set the @code{gnuserv-frame} variable to the frame that should be
5233 used to display buffers that are pulled up, a new frame will not be
5234 created. For example, you could put
5237 (setq gnuserv-frame (selected-frame))
5240 early on in your @file{.emacs}, to ensure that the first frame created
5241 is the one used for your gnuserv buffers.
5243 Starting in 19.15, there is an option to set the gnuserv target to
5244 the current frame. See
5245 @code{Options->"Other Window" Location->Make current frame gnuserv target}
5247 Starting with XEmacs-20.3 you can also change this with Customize.
5248 Select from the @code{Options} menu
5249 @code{Customize->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type
5250 @kbd{M-x customize @key{RET} gnuserv @key{RET}}.
5253 @node Q5.0.13, Q5.0.14, Q5.0.12, Miscellaneous
5254 @unnumberedsubsec Q5.0.13: How do I start gnuserv so that each subsequent XEmacs is a client?
5256 Put the following in your @file{.emacs} file to start the server:
5262 Start your first XEmacs as usual. After that, you can do:
5265 gnuclient randomfilename
5268 from the command line to get your existing XEmacs process to open a new
5269 frame and visit randomfilename in that window. When you're done editing
5270 randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the
5273 See also man page of gnuclient.
5275 @node Q5.0.14, Q5.0.15, Q5.0.13, Miscellaneous
5276 @unnumberedsubsec Q5.0.14: Strange things are happening in Shell Mode.
5278 Sometimes (i.e. it's not repeatable, and I can't work out why it
5279 happens) when I'm typing into shell mode, I hit return and only a
5280 portion of the command is given to the shell, and a blank prompt is
5281 returned. If I hit return again, the rest of the previous command is
5284 @email{martin@@xemacs.org, Martin Buchholz} writes:
5287 There is a known problem with interaction between @code{csh} and the
5288 @code{filec} option and XEmacs. You should add the following to your
5292 if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec
5296 @node Q5.0.15, Q5.0.16, Q5.0.14, Miscellaneous
5297 @unnumberedsubsec Q5.0.15: Where do I get the latest CC Mode?
5299 @email{bwarsaw@@cnri.reston.va.us, Barry A. Warsaw} writes:
5302 This can be had from @uref{http://www.python.org/ftp/emacs/}.
5305 @node Q5.0.16, Q5.0.17, Q5.0.15, Miscellaneous
5306 @unnumberedsubsec Q5.0.16: I find auto-show-mode disconcerting. How do I turn it off?
5308 @code{auto-show-mode} controls whether or not a horizontal scrollbar
5309 magically appears when a line is too long to be displayed. This is
5310 enabled by default. To turn it off, put the following in your
5314 (setq auto-show-mode nil)
5315 (setq-default auto-show-mode nil)
5318 @node Q5.0.17, Q5.0.18, Q5.0.16, Miscellaneous
5319 @unnumberedsubsec Q5.0.17: How can I get two instances of info?
5321 You can't. The @code{info} package does not provide for multiple info buffers.
5323 @node Q5.0.18, Q5.0.19, Q5.0.17, Miscellaneous
5324 @unnumberedsubsec Q5.0.18: I upgraded to XEmacs 19.14 and gnuserv stopped working.
5326 @email{daku@@nortel.ca, Mark Daku} writes:
5329 It turns out I was using an older version of gnuserv. The installation
5330 didn't put the binary into the public bin directory. It put it in
5334 @file{lib/xemacs-19.14/hppa1.1-hp-hpux9.05/gnuserv}. Shouldn't it have
5335 been put in @file{bin/hppa1.1-hp-hpux9.0}?
5338 @node Q5.0.19, Q5.0.20, Q5.0.18, Miscellaneous
5339 @unnumberedsubsec Q5.0.19: Is there something better than LaTeX mode?
5341 @email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes:
5344 The standard TeX modes leave much to be desired, and are somewhat
5345 leniently maintained. Serious TeX users use AUC TeX (@pxref{Q4.7.1}).
5348 @node Q5.0.20, Q5.1.1, Q5.0.19, Miscellaneous
5349 @unnumberedsubsec Q5.0.20: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
5351 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
5353 Here is one of the solutions, we have this in a script called
5354 @file{etc/editclient.sh}.
5357 if gnuclient -batch -eval t >/dev/null 2>&1
5359 exec gnuclient $@{1+"$@@"@}
5361 xemacs -unmapped -f gnuserv-start &
5362 until gnuclient -batch -eval t >/dev/null 2>&1
5366 exec gnuclient $@{1+"$@@"@}
5370 Note that there is a known problem when running XEmacs and 'gnuclient
5371 -nw' on the same TTY.
5374 @node Q5.1.1, Q5.1.2, Q5.0.20, Miscellaneous
5375 @unnumberedsec 5.1: Emacs Lisp Programming Techniques
5376 @unnumberedsubsec Q5.1.1: What is the difference in key sequences between XEmacs and GNU Emacs?
5378 @email{clerik@@naggum.no, Erik Naggum} writes;
5381 Emacs has a legacy of keyboards that produced characters with modifier
5382 bits, and therefore map a variety of input systems into this scheme even
5383 today. XEmacs is instead optimized for X events. This causes an
5384 incompatibility in the way key sequences are specified, but both Emacs
5385 and XEmacs will accept a key sequence as a vector of lists of modifiers
5386 that ends with a key, e.g., to bind @kbd{M-C-a}, you would say
5387 @code{[(meta control a)]} in both Emacsen. XEmacs has an abbreviated
5388 form for a single key, just (meta control a). Emacs has an abbreviated
5389 form for the Control and the Meta modifiers to string-characters (the
5390 ASCII characters), as in @samp{\M-\C-a}. XEmacs users need to be aware
5391 that the abbreviated form works only for one-character key sequences,
5392 while Emacs users need to be aware that the string-character is rather
5393 limited. Specifically, the string-character can accommodate only 256
5394 different values, 128 of which have the Meta modifier and 128 of which
5395 have not. In each of these blocks, only 32 characters have the Control
5396 modifier. Whereas @code{[(meta control A)]} differs from @code{[(meta
5397 control a)]} because the case differs, @samp{\M-\C-a} and @samp{\M-\C-A}
5398 do not. Programmers are advised to use the full common form, both
5399 because it is more readable and less error-prone, and because it is
5400 supported by both Emacsen.
5403 Another (even safer) way to be sure of the key-sequences is to use the
5404 @code{read-kbd-macro} function, which takes a string like @samp{C-c
5405 <up>}, and converts it to the internal key representation of the Emacs
5406 you use. The function is available both on XEmacs and GNU Emacs.
5408 @node Q5.1.2, Q5.1.3, Q5.1.1, Miscellaneous
5409 @unnumberedsubsec Q5.1.2: Can I generate "fake" keyboard events?
5411 I wonder if there is an interactive function that can generate
5412 @dfn{fake} keyboard events. This way, I could simply map them inside
5418 (defun cg--generate-char-event (ch)
5419 "Generate an event, as if ch has been typed"
5420 (dispatch-event (character-to-event ch)))
5422 ;; Backspace and Delete stuff
5423 (global-set-key [backspace]
5424 (lambda () (interactive) (cg--generate-char-event 127)))
5425 (global-set-key [unknown_keysym_0x4]
5426 (lambda () (interactive) (cg--generate-char-event 4)))
5429 @node Q5.1.3, Q5.1.4, Q5.1.2, Miscellaneous
5430 @unnumberedsubsec Q5.1.3: Could you explain @code{read-kbd-macro} in more detail?
5432 The @code{read-kbd-macro} function returns the internal Emacs
5433 representation of a human-readable string (which is its argument).
5437 (read-kbd-macro "C-c C-a")
5438 @result{} [(control ?c) (control ?a)]
5440 (read-kbd-macro "C-c C-. <up>")
5441 @result{} [(control ?c) (control ?.) up]
5444 In GNU Emacs the same forms will be evaluated to what GNU Emacs
5445 understands internally---the sequences @code{"\C-x\C-c"} and @code{[3
5446 67108910 up]}, respectively.
5448 The exact @dfn{human-readable} syntax is defined in the docstring of
5449 @code{edmacro-mode}. I'll repeat it here, for completeness.
5452 Format of keyboard macros during editing:
5454 Text is divided into @dfn{words} separated by whitespace. Except for
5455 the words described below, the characters of each word go directly as
5456 characters of the macro. The whitespace that separates words is
5457 ignored. Whitespace in the macro must be written explicitly, as in
5458 @kbd{foo @key{SPC} bar @key{RET}}.
5462 The special words @kbd{RET}, @kbd{SPC}, @kbd{TAB}, @kbd{DEL}, @kbd{LFD},
5463 @kbd{ESC}, and @kbd{NUL} represent special control characters. The
5464 words must be written in uppercase.
5467 A word in angle brackets, e.g., @code{<return>}, @code{<down>}, or
5468 @code{<f1>}, represents a function key. (Note that in the standard
5469 configuration, the function key @code{<return>} and the control key
5470 @key{RET} are synonymous.) You can use angle brackets on the words
5471 @key{RET}, @key{SPC}, etc., but they are not required there.
5474 Keys can be written by their @sc{ascii} code, using a backslash followed
5475 by up to six octal digits. This is the only way to represent keys with
5479 One or more prefixes @kbd{M-} (meta), @kbd{C-} (control), @kbd{S-}
5480 (shift), @kbd{A-} (alt), @kbd{H-} (hyper), and @kbd{s-} (super) may
5481 precede a character or key notation. For function keys, the prefixes
5482 may go inside or outside of the brackets: @code{C-<down>} @equiv{}
5483 @code{<C-down>}. The prefixes may be written in any order: @kbd{M-C-x}
5484 @equiv{} @kbd{C-M-x}.
5486 Prefixes are not allowed on multi-key words, e.g., @kbd{C-abc}, except
5487 that the Meta prefix is allowed on a sequence of digits and optional
5488 minus sign: @kbd{M--123} @equiv{} @kbd{M-- M-1 M-2 M-3}.
5491 The @code{^} notation for control characters also works: @kbd{^M}
5495 Double angle brackets enclose command names: @code{<<next-line>>} is
5496 shorthand for @kbd{M-x next-line @key{RET}}.
5499 Finally, @code{REM} or @code{;;} causes the rest of the line to be
5500 ignored as a comment.
5503 Any word may be prefixed by a multiplier in the form of a decimal number
5504 and @code{*}: @code{3*<right>} @equiv{} @code{<right> <right> <right>},
5505 and @code{10*foo} @equiv{}
5509 @code{foofoofoofoofoofoofoofoofoofoo}.
5511 Multiple text keys can normally be strung together to form a word, but
5512 you may need to add whitespace if the word would look like one of the
5513 above notations: @code{; ; ;} is a keyboard macro with three semicolons,
5514 but @code{;;;} is a comment. Likewise, @code{\ 1 2 3} is four keys but
5515 @code{\123} is a single key written in octal, and @code{< right >} is
5516 seven keys but @code{<right>} is a single function key. When in doubt,
5520 @node Q5.1.4, Q5.1.5, Q5.1.3, Miscellaneous
5521 @unnumberedsubsec Q5.1.4: What is the performance hit of @code{let}?
5523 In most cases, not noticeable. Besides, there's no avoiding
5524 @code{let}---you have to bind your local variables, after all. Some
5525 pose a question whether to nest @code{let}s, or use one @code{let} per
5526 function. I think because of clarity and maintenance (and possible
5527 future implementation), @code{let}-s should be used (nested) in a way to
5528 provide the clearest code.
5530 @node Q5.1.5, Q5.1.6, Q5.1.4, Miscellaneous
5531 @unnumberedsubsec Q5.1.5: What is the recommended use of @code{setq}?
5534 @item Global variables
5536 You will typically @code{defvar} your global variable to a default
5537 value, and use @code{setq} to set it later.
5539 It is never a good practice to @code{setq} user variables (like
5540 @code{case-fold-search}, etc.), as it ignores the user's choice
5541 unconditionally. Note that @code{defvar} doesn't change the value of a
5542 variable if it was bound previously. If you wish to change a
5543 user-variable temporarily, use @code{let}:
5546 (let ((case-fold-search nil))
5547 ... ; code with searches that must be case-sensitive
5551 You will notice the user-variables by their docstrings beginning with an
5552 asterisk (a convention).
5554 @item Local variables
5556 Bind them with @code{let}, which will unbind them (or restore their
5557 previous value, if they were bound) after exiting from the @code{let}
5558 form. Change the value of local variables with @code{setq} or whatever
5559 you like (e.g. @code{incf}, @code{setf} and such). The @code{let} form
5560 can even return one of its local variables.
5565 ;; iterate through the elements of the list returned by
5566 ;; `hairy-function-that-returns-list'
5567 (let ((l (hairy-function-that-returns-list)))
5569 ... do something with (car l) ...
5573 Another typical usage includes building a value simply to work with it.
5576 ;; Build the mode keymap out of the key-translation-alist
5577 (let ((inbox (file-truename (expand-file-name box)))
5579 ... code dealing with inbox ...
5583 This piece of code uses the local variable @code{inbox}, which becomes
5584 unbound (or regains old value) after exiting the form. The form also
5585 returns the value of @code{inbox}, which can be reused, for instance:
5588 (setq foo-processed-inbox
5593 @node Q5.1.6, Q5.1.7, Q5.1.5, Miscellaneous
5594 @unnumberedsubsec Q5.1.6: What is the typical misuse of @code{setq} ?
5596 A typical misuse is probably @code{setq}ing a variable that was meant to
5597 be local. Such a variable will remain bound forever, never to be
5598 garbage-collected. For example, the code doing:
5601 (defun my-function (whatever)
5603 ... build a large list ...
5607 does a bad thing, as @code{a} will keep consuming memory, never to be
5608 unbound. The correct thing is to do it like this:
5611 (defun my-function (whatever)
5612 (let (a) ; default initialization is to nil
5613 ... build a large list ...
5614 ... and exit, unbinding `a' in the process ...)
5617 Not only is this prettier syntactically, but it makes it possible for
5618 Emacs to garbage-collect the objects which @code{a} used to reference.
5620 Note that even global variables should not be @code{setq}ed without
5621 @code{defvar}ing them first, because the byte-compiler issues warnings.
5622 The reason for the warning is the following:
5625 (defun flurgoze nil) ; ok, global internal variable
5628 (setq flurghoze t) ; ops! a typo, but semantically correct.
5629 ; however, the byte-compiler warns.
5631 While compiling toplevel forms:
5632 ** assignment to free variable flurghoze
5635 @node Q5.1.7, Q5.1.8, Q5.1.6, Miscellaneous
5636 @unnumberedsubsec Q5.1.7: I like the the @code{do} form of cl, does it slow things down?
5638 It shouldn't. Here is what Dave Gillespie has to say about cl.el
5642 Many of the advanced features of this package, such as @code{defun*},
5643 @code{loop}, and @code{setf}, are implemented as Lisp macros. In
5644 byte-compiled code, these complex notations will be expanded into
5645 equivalent Lisp code which is simple and efficient. For example, the
5653 are expanded at compile-time to the Lisp forms
5657 (setcar p (cons x (car p)))
5660 which are the most efficient ways of doing these respective operations
5661 in Lisp. Thus, there is no performance penalty for using the more
5662 readable @code{incf} and @code{push} forms in your compiled code.
5664 @emph{Interpreted} code, on the other hand, must expand these macros
5665 every time they are executed. For this reason it is strongly
5666 recommended that code making heavy use of macros be compiled. (The
5667 features labelled @dfn{Special Form} instead of @dfn{Function} in this
5668 manual are macros.) A loop using @code{incf} a hundred times will
5669 execute considerably faster if compiled, and will also garbage-collect
5670 less because the macro expansion will not have to be generated, used,
5671 and thrown away a hundred times.
5673 You can find out how a macro expands by using the @code{cl-prettyexpand}
5677 @node Q5.1.8, Q5.1.9, Q5.1.7, Miscellaneous
5678 @unnumberedsubsec Q5.1.8: I like recursion, does it slow things down?
5680 Yes. Emacs byte-compiler cannot do much to optimize recursion. But
5681 think well whether this is a real concern in Emacs. Much of the Emacs
5682 slowness comes from internal mechanisms such as redisplay, or from the
5683 fact that it is an interpreter.
5685 Please try not to make your code much uglier to gain a very small speed
5686 gain. It's not usually worth it.
5688 @node Q5.1.9, Q5.1.10, Q5.1.8, Miscellaneous
5689 @unnumberedsubsec Q5.1.9: How do I put a glyph as annotation in a buffer?
5691 Here is a solution that will insert the glyph annotation at the
5692 beginning of buffer:
5695 (make-annotation (make-glyph '([FORMAT :file FILE]
5696 [string :data "fallback-text"]))
5702 Replace @samp{FORMAT} with an unquoted symbol representing the format of
5703 the image (e.g. @code{xpm}, @code{xbm}, @code{gif}, @code{jpeg}, etc.)
5704 Instead of @samp{FILE}, use the image file name
5709 @file{/usr/local/lib/xemacs-20.2/etc/recycle.xpm}).
5711 You can turn this to a function (that optionally prompts you for a file
5712 name), and inserts the glyph at @code{(point)} instead of
5715 @node Q5.1.10, Q5.1.11, Q5.1.9, Miscellaneous
5716 @unnumberedsubsec Q5.1.10: @code{map-extents} won't traverse all of my extents!
5718 I tried to use @code{map-extents} to do an operation on all the extents
5719 in a region. However, it seems to quit after processing a random number
5720 of extents. Is it buggy?
5722 No. The documentation of @code{map-extents} states that it will iterate
5723 across the extents as long as @var{function} returns @code{nil}.
5724 Unexperienced programmers often forget to return @code{nil} explicitly,
5725 which results in buggy code. For instance, the following code is
5726 supposed to delete all the extents in a buffer, and issue as many
5727 @samp{fubar!} messages.
5730 (map-extents (lambda (ext ignore)
5732 (message "fubar!")))
5735 Instead, it will delete only the first extent, and stop right there --
5736 because @code{message} will return a non-nil value. The correct code
5740 (map-extents (lambda (ext ignore)
5746 @node Q5.1.11, Q5.2.1, Q5.1.10, Miscellaneous
5747 @unnumberedsubsec Q5.1.11: My elisp program is horribly slow. Is there
5748 an easy way to find out where it spends time?
5751 z@email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
5753 Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence}, press a key
5754 (say @key{RET} in the Gnus Group buffer), and get the results using
5755 @kbd{M-x profile-results}. It should give you an idea of where the time
5759 @node Q5.2.1, Q5.2.2, Q5.1.11, Miscellaneous
5760 @unnumberedsubsec Q5.2.1: How do I turn off the sound?
5762 Add the following line to your @file{.emacs}:
5765 (setq bell-volume 0)
5766 (setq sound-alist nil)
5769 That will make your XEmacs totally silent -- even the default ding sound
5770 (TTY beep on TTY-s) will be gone.
5772 Starting with XEmacs-20.2 you can also change these with Customize.
5773 Select from the @code{Options} menu
5774 @code{Customize->Emacs->Environment->Sound->Sound...} or type
5775 @kbd{M-x customize @key{RET} sound @key{RET}}.
5778 @node Q5.2.2, Q5.2.3, Q5.2.1, Miscellaneous
5779 @unnumberedsubsec Q5.2.2: How do I get funky sounds instead of a boring beep?
5781 Make sure your XEmacs was compiled with sound support, and then put this
5782 in your @file{.emacs}:
5785 (load-default-sounds)
5788 The sound support in XEmacs 19.14 was greatly improved over previous
5791 @node Q5.2.3, Q5.2.4, Q5.2.2, Miscellaneous
5792 @unnumberedsubsec Q5.2.3: What's NAS, how do I get it?
5794 @xref{Q2.0.3}, for an explanation of the @dfn{Network Audio System}.
5796 @node Q5.2.4, Q5.3.1, Q5.2.3, Miscellaneous
5797 @unnumberedsubsec Q5.2.4: Sunsite sounds don't play.
5799 I'm having some trouble with sounds I've downloaded from sunsite. They
5800 play when I run them through @code{showaudio} or cat them directly to
5801 @file{/dev/audio}, but XEmacs refuses to play them.
5803 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
5806 [Many of] These files have an (erroneous) 24byte header that tells about
5807 the format that they have been recorded in. If you cat them to
5808 @file{/dev/audio}, the header will be ignored and the default behavior
5809 for /dev/audio will be used. This happens to be 8kHz uLaw. It is
5810 probably possible to fix the header by piping through @code{sox} and
5811 passing explicit parameters for specifying the sampling format; you then
5812 need to perform a 'null' conversion from SunAudio to SunAudio.
5815 @node Q5.3.1, Q5.3.2, Q5.2.4, Miscellaneous
5816 @unnumberedsec 5.3: Miscellaneous
5817 @unnumberedsubsec Q5.3.1: How do you make XEmacs indent CL if-clauses correctly?
5819 I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the
5820 same amount instead of indenting the 3rd clause differently from the
5823 One way is to add, to @file{.emacs}:
5826 (put 'if 'lisp-indent-function nil)
5829 However, note that the package @code{cl-indent} that comes with
5830 XEmacs sets up this kind of indentation by default. @code{cl-indent}
5831 also knows about many other CL-specific forms. To use @code{cl-indent},
5836 (setq lisp-indent-function (function common-lisp-indent-function))
5839 One can also customize @file{cl-indent.el} so it mimics the default
5840 @code{if} indentation @code{then} indented more than the @code{else}.
5844 (put 'if 'common-lisp-indent-function '(nil nil &body))
5847 Also, a new version (1.2) of @file{cl-indent.el} was posted to
5848 comp.emacs.xemacs on 12/9/94. This version includes more documentation
5849 than previous versions. This may prove useful if you need to customize
5850 any indent-functions.
5852 @node Q5.3.2, Q5.3.3, Q5.3.1, Miscellaneous
5853 @unnumberedsubsec Q5.3.2: Fontifying hang when editing a postscript file.
5855 When I try to edit a postscript file it gets stuck saying:
5856 @samp{fontifying 'filename' (regexps....)} and it just sits there. If I
5857 press @kbd{C-c} in the window where XEmacs was started, it suddenly
5858 becomes alive again.
5860 This was caused by a bug in the Postscript font-lock regular
5861 expressions. It was fixed in 19.13. For earlier versions of XEmacs,
5862 have a look at your @file{.emacs} file. You will probably have a line
5866 (add-hook 'postscript-mode-hook 'turn-on-font-lock)
5869 Take it out, restart XEmacs, and it won't try to fontify your postscript
5872 @node Q5.3.3, Q5.3.4, Q5.3.2, Miscellaneous
5873 @unnumberedsubsec Q5.3.3: How can I print WYSIWYG a font-locked buffer?
5875 Font-lock looks nice. How can I print (WYSIWYG) the highlighted
5878 The package @code{ps-print}, which is now included with XEmacs, provides
5879 the ability to do this. The source code contains complete instructions
5880 on its use, in @file{<xemacs_src_root>/lisp/packages/ps-print.el}.
5882 @node Q5.3.4, Q5.3.5, Q5.3.3, Miscellaneous
5883 @unnumberedsubsec Q5.3.4: Getting @kbd{M-x lpr} to work with postscript printer.
5885 My printer is a Postscript printer and @code{lpr} only works for
5886 Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x
5887 lpr-buffer} to work?
5889 Put something like this in your @file{.emacs}:
5892 (setq lpr-command "a2ps")
5893 (setq lpr-switches '("-p" "-1"))
5896 If you don't use a2ps to convert ASCII to postscript (why not, it's
5897 free?), replace with the command you do use. Note also that some
5898 versions of a2ps require a @samp{-Pprinter} to ensure spooling.
5900 @node Q5.3.5, Q5.3.6, Q5.3.4, Miscellaneous
5901 @unnumberedsubsec Q5.3.5: How do I specify the paths that XEmacs uses for finding files?
5903 You can specify what paths to use by using a number of different flags
5904 when running configure. See the section MAKE VARIABLES in the top-level
5905 file INSTALL in the XEmacs distribution for a listing of those flags.
5907 Most of the time, however, the simplest fix is: @strong{do not} specify
5908 paths as you might for GNU Emacs. XEmacs can generally determine the
5909 necessary paths dynamically at run time. The only path that generally
5910 needs to be specified is the root directory to install into. That can
5911 be specified by passing the @code{--prefix} flag to configure. For a
5912 description of the XEmacs install tree, please consult the @file{NEWS}
5915 @node Q5.3.6, Q5.3.7, Q5.3.5, Miscellaneous
5916 @unnumberedsubsec Q5.3.6: [This question intentionally left blank]
5918 Obsolete question, left blank to avoid renumbering.
5920 @node Q5.3.7, Q5.3.8, Q5.3.6, Miscellaneous
5921 @unnumberedsubsec Q5.3.7: Can I have the end of the buffer delimited in some way?
5923 Say, with: @samp{[END]}?
5928 (let ((ext (make-extent (point-min) (point-max))))
5929 (set-extent-property ext 'start-closed t)
5930 (set-extent-property ext 'end-closed t)
5931 (set-extent-property ext 'detachable nil)
5932 (set-extent-end-glyph ext (make-glyph [string :data "[END]"])))
5935 Since this is XEmacs, you can specify an icon to be shown on
5936 window-system devices. To do so, change the @code{make-glyph} call to
5937 something like this:
5940 (make-glyph '([xpm :file "~/something.xpm"]
5941 [string :data "[END]"]))
5944 You can inline the @sc{xpm} definition yourself by specifying
5945 @code{:data} instead of @code{:file}. Here is such a full-featured
5946 version that works on both X and TTY devices:
5949 (let ((ext (make-extent (point-min) (point-max))))
5950 (set-extent-property ext 'start-closed t)
5951 (set-extent-property ext 'end-closed t)
5952 (set-extent-property ext 'detachable nil)
5953 (set-extent-end-glyph ext (make-glyph '([xpm :data "\
5955 static char* eye = @{
5964 \"___________`_`_`___b_b_b_b_________`____\",
5965 \"_________`_`_`___b_c_c_c_b_b____________\",
5966 \"_____`_`_`_e___b_b_c_c_c___b___b_______`\",
5967 \"___`_`_e_a___b_b_d___b___b___b___b______\",
5968 \"_`_`_e_a_e___b_b_d_b___b___b___b___b____\",
5969 \"_`_`_a_e_a___b_b_d___b___b___b___b___b__\",
5970 \"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\",
5971 \"___`_`_e_a___b_b_b_d_c___b___b___d_b____\",
5972 \"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\",
5973 \"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\",
5974 \"___`_____`_`_`_`___b_b_b_b_b_b__________\",
5976 [string :data "[END]"]))))
5979 Note that you might want to make this a function, and put it to a hook.
5980 We leave that as an exercise for the reader.
5982 @node Q5.3.8, Q5.3.9, Q5.3.7, Miscellaneous
5983 @unnumberedsubsec Q5.3.8: How do I insert today's date into a buffer?
5988 (insert (current-time-string))
5991 @node Q5.3.9, Q5.3.10, Q5.3.8, Miscellaneous
5992 @unnumberedsubsec Q5.3.9: Are only certain syntactic character classes available for abbrevs?
5994 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
5997 Yes, abbrevs only expands word-syntax strings. While XEmacs does not
5998 prevent you from defining (e.g. with @kbd{C-x a g} or @kbd{C-x a l})
5999 abbrevs that contain special characters, it will refuse to expand
6000 them. So you need to ensure, that the abbreviation contains letters and
6001 digits only. This means that @samp{xd}, @samp{d5}, and @samp{5d} are
6002 valid abbrevs, but @samp{&d}, and @samp{x d} are not.
6004 If this sounds confusing to you, (re-)read the online documentation for
6005 abbrevs (@kbd{C-h i m XEmacs @key{RET} m Abbrevs @key{RET}}), and then come back and
6006 read this question/answer again.
6009 Starting with XEmacs 20.3 this restriction has been lifted.
6011 @node Q5.3.10, Q5.3.11, Q5.3.9, Miscellaneous
6012 @unnumberedsubsec Q5.3.10: How can I get those oh-so-neat X-Face lines?
6014 Firstly there is an ftp site which describes X-faces and has the
6015 associated tools mentioned below, at
6016 @uref{ftp://ftp.cs.indiana.edu:/pub/faces/}.
6022 Create 48x48x1 bitmap with your favorite tool
6025 Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc.,
6026 and then compile the face.
6030 cat file.xbm | xbm2ikon |compface > file.face
6034 Then be sure to quote things that are necessary for emacs strings:
6037 cat ./file.face | sed 's/\\/\\\\/g'
6041 | sed 's/\"/\\\"/g' > ./file.face.quoted
6045 Then set up emacs to include the file as a mail header - there were a
6046 couple of suggestions here---either something like:
6049 (setq mail-default-headers
6050 "X-Face: @email{Ugly looking text string here}")
6053 Or, alternatively, as:
6056 (defun mail-insert-x-face ()
6058 (goto-char (point-min))
6059 (search-forward mail-header-separator)
6062 (insert-file-contents "~/.face")))
6064 (add-hook 'mail-setup-hook 'mail-insert-x-face)
6068 However, 2 things might be wrong:
6070 Some versions of pbmtoicon produces some header lines that is not
6071 expected by the version of compface that I grabbed. So I found I had to
6072 include a @code{tail +3} in the pipeline like this:
6075 cat file.xbm | xbm2ikon | tail +3 |compface > file.face
6078 Some people have also found that if one uses the @code{(insert-file)}
6079 method, one should NOT quote the face string using the sed script .
6081 It might also be helpful to use @email{stig@@hackvan.com, Stig's} script
6082 (included in the compface distribution at XEmacs.org) to do the
6083 conversion. For convenience xbm2xface is available for anonymous FTP at
6084 @uref{ftp://ftp.miranova.com/pub/xemacs/xbm2xface.pl}.
6086 Contributors for this item:
6097 @node Q5.3.11, Q5.3.12, Q5.3.10, Miscellaneous
6098 @unnumberedsubsec Q5.3.11: How do I add new Info directories?
6100 You use something like:
6103 (setq Info-directory-list (cons
6104 (expand-file-name "~/info")
6105 Info-default-directory-list))
6108 @email{davidm@@prism.kla.com, David Masterson} writes:
6111 Emacs Info and XEmacs Info do many things differently. If you're trying to
6112 support a number of versions of Emacs, here are some notes to remember:
6116 Emacs Info scans @code{Info-directory-list} from right-to-left while
6117 XEmacs Info reads it from left-to-right, so append to the @emph{correct}
6121 Use @code{Info-default-directory-list} to initialize
6122 @code{Info-directory-list} @emph{if} it is available at startup, but not
6123 all Emacsen define it.
6126 Emacs Info looks for a standard @file{dir} file in each of the
6127 directories scanned from #1 and magically concatenates them together.
6130 XEmacs Info looks for a @file{localdir} file (which consists of just the
6131 menu entries from a @file{dir} file) in each of the directories scanned
6132 from #1 (except the first), does a simple concatenation of them, and
6133 magically attaches the resulting list to the end of the menu in the
6134 @file{dir} file in the first directory.
6137 Another alternative is to convert the documentation to HTML with
6138 texi2html and read it from a web browser like Lynx or W3.
6141 @node Q5.3.12, , Q5.3.11, Miscellaneous
6142 @unnumberedsubsec Q5.3.12: What do I need to change to make printing work?
6144 For regular printing there are two variables that can be customized.
6148 This should be set to a command that takes standard input and sends
6149 it to a printer. Something like:
6152 (setq lpr-command "lp")
6156 This should be set to a list that contains whatever the print command
6157 requires to do its job. Something like:
6160 (setq lpr-switches '("-depson"))
6164 For postscript printing there are three analogous variables to
6168 @item ps-lpr-command
6169 This should be set to a command that takes postscript on standard input
6170 and directs it to a postscript printer.
6172 @item ps-lpr-switches
6173 This should be set to a list of switches required for
6174 @code{ps-lpr-command} to do its job.
6176 @item ps-print-color-p
6177 This boolean variable should be set @code{t} if printing will be done in
6178 color, otherwise it should be set to @code{nil}.
6181 NOTE: It is an undocumented limitation in XEmacs that postscript
6182 printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a
6183 window system environment. It cannot be used outside of X11.
6185 @node Current Events, , Miscellaneous, Top
6186 @unnumbered 6 What the Future Holds
6188 This is part 6 of the XEmacs Frequently Asked Questions list. This
6189 section will change monthly, and contains any interesting items that have
6190 transpired over the previous month. If you are reading this from the
6191 XEmacs distribution, please see the version on the Web or archived at the
6192 various FAQ FTP sites, as this file is surely out of date.
6195 * Q6.0.1:: What is new in 20.2?
6196 * Q6.0.2:: What is new in 20.3?
6197 * Q6.0.3:: What is new in 20.4?
6198 * Q6.0.4:: Procedural changes in XEmacs development.
6201 @node Q6.0.1, Q6.0.2, Current Events, Current Events
6202 @unnumberedsec 6.0: Changes
6203 @unnumberedsubsec Q6.0.1: What is new in 20.2?
6205 The biggest changes in 20.2 include integration of EFS (the next
6206 generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a
6207 major mode for editing Tex and LaTeX, and a lot of other stuff). Many
6208 bugs from 20.0 have been fixed for this release. 20.2 also contains a
6209 new system for customizing XEmacs options, invoked via @kbd{M-x
6212 XEmacs 20.2 is the development release (20.0 was beta), and is no longer
6213 considered unstable.
6215 @node Q6.0.2, Q6.0.3, Q6.0.1, Current Events
6216 @unnumberedsubsec Q6.0.2: What is new in 20.3?
6218 XEmacs 20.3 was released in November 1997. It contains many bugfixes,
6219 and a number of new features, including Autoconf 2 based configuration,
6220 additional support for Mule (Multi-language extensions to Emacs), many
6221 more customizations, multiple frames on TTY-s, support for multiple info
6222 directories, an enhanced gnuclient, improvements to regexp matching,
6223 increased MIME support, and many, many synches with GNU Emacs 20.
6225 The XEmacs/Mule support has been only seriously tested in a Japanese
6226 locale, and no doubt many problems still remain. The support for
6227 ISO-Latin-1 and Japanese is fairly strong. MULE support comes at a
6228 price -- about a 30% slowdown from 19.16. We're making progress on
6229 improving performance and XEmacs 20.3 compiled without Mule (which is
6230 the default) is definitely faster than XEmacs 19.16.
6232 XEmacs 20.3 is the first non-beta v20 release, and will be the
6233 basis for all further development.
6235 @node Q6.0.3, Q6.0.4, Q6.0.2, Current Events
6236 @unnumberedsubsec Q6.0.3: What's new in XEmacs 20.4?
6238 XEmacs 20.4 is a bugfix release with no user-visible changes.
6239 @c Filled in from NEWS file of 20.5-b33
6242 @node Q6.0.4, , Q6.0.3, Current Events
6243 @unnumberedsubsec Q6.0.4: Procedural changes in XEmacs development.
6247 Discussion about the development of XEmacs occurs on the xemacs-beta
6248 mailing list. Subscriptions to this list will now be fully automated
6249 instead of being handled by hand. Send a mail message to
6250 @email{xemacs-beta-request@@xemacs.org} with @samp{subscribe} as the
6251 BODY of the message to join the list. Please note this is a developers
6252 mailing list for people who have an active interest in the development
6255 The discussion of NT XEmacs development is taking place on a separate
6256 mailing list. Send mail to
6260 @email{xemacs-nt-request@@xemacs.org} to
6264 Due to the long development cycle in between releases, it has been
6265 decided that intermediate versions will be made available in source only
6266 form for the truly interested.
6268 XEmacs 19.16 was the last 19 release, basically consisting of 19.15 plus
6269 the collected bugfixes.
6272 As of December 1996, @email{steve@@xemacs.org, Steve Baur} has become
6273 the lead maintainer of XEmacs.