|
361
|
1 \input texinfo.tex @c -*- mode: texinfo; coding: iso-2022-8 -*-
|
|
0
|
2 @c %**start of header
|
|
290
|
3 @setfilename ../info/xemacs-faq.info
|
|
0
|
4 @settitle Frequently asked questions about XEmacs
|
|
|
5 @setchapternewpage off
|
|
|
6 @c %**end of header
|
|
274
|
7 @finalout
|
|
0
|
8 @titlepage
|
|
|
9 @title XEmacs FAQ
|
|
369
|
10 @subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2001/01/20 20:49:32 $
|
|
0
|
11 @sp 1
|
|
365
|
12 @author Tony Rossini <rossini@@biostat.washington.edu>
|
|
359
|
13 @author Ben Wing <ben@@xemacs.org>
|
|
215
|
14 @author Chuck Thompson <cthomp@@xemacs.org>
|
|
|
15 @author Steve Baur <steve@@xemacs.org>
|
|
126
|
16 @author Andreas Kaempf <andreas@@sccon.com>
|
|
274
|
17 @author Christian Nyb@o{} <chr@@mediascience.no>
|
|
365
|
18 @author Sandra Wambold <wambold@@xemacs.org>
|
|
0
|
19 @page
|
|
|
20 @end titlepage
|
|
|
21
|
|
343
|
22 @ifinfo
|
|
|
23 @dircategory XEmacs Editor
|
|
|
24 @direntry
|
|
365
|
25 * FAQ: (xemacs-faq). XEmacs FAQ.
|
|
343
|
26 @end direntry
|
|
|
27 @end ifinfo
|
|
|
28
|
|
82
|
29 @node Top, Introduction, (dir), (dir)
|
|
|
30 @top XEmacs FAQ
|
|
282
|
31 @unnumbered Introduction
|
|
82
|
32
|
|
|
33 This is the guide to the XEmacs Frequently Asked Questions list---a
|
|
|
34 compendium of questions and answers pertaining to one of the finest
|
|
365
|
35 programs ever written. XEmacs is much more than just a Text Editor.
|
|
|
36
|
|
|
37 This FAQ is freely redistributable. This FAQ is distributed in the hope
|
|
|
38 that it will be useful, but WITHOUT ANY WARRANTY; without even the
|
|
|
39 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
|
82
|
40
|
|
|
41 If you have a Web browser, the official hypertext version is at
|
|
282
|
42 @iftex
|
|
|
43 @*
|
|
|
44 @end iftex
|
|
365
|
45 @uref{http://www.xemacs.org/faq/xemacs-faq.html}
|
|
0
|
46
|
|
282
|
47 @ifset CANONICAL
|
|
|
48 @html
|
|
|
49 This document is available in several different formats:
|
|
|
50 @itemize @bullet
|
|
|
51 @item
|
|
|
52 @uref{xemacs-faq.txt, As a single ASCII file}, produced by
|
|
|
53 @code{makeinfo --no-headers}
|
|
|
54 @item
|
|
|
55 @uref{xemacs-faq.dvi, As a .dvi file}, as used with
|
|
|
56 @uref{http://www.tug.org, TeX.}
|
|
|
57 @item
|
|
|
58 As a PostScript file @uref{xemacs-faq-a4.ps, in A4 format},
|
|
|
59 as well as in @uref{xemacs-faq-letter.ps, letter format}
|
|
|
60 @item
|
|
|
61 In html format, @uref{xemacs-faq_1.html, split by chapter}, or in
|
|
|
62 @uref{xemacs-faq.html, one monolithic} document.
|
|
|
63 @item
|
|
|
64 The canonical version of the FAQ is the texinfo document
|
|
|
65 @uref{xemacs-faq.texi, man/xemacs-faq.texi}.
|
|
|
66 @item
|
|
|
67 If you do not have makeinfo installed, you may @uref{xemacs-faq.info,
|
|
|
68 download the faq} in info format, and install it in @file{<XEmacs
|
|
359
|
69 library directory>/info/}. For example in
|
|
282
|
70 @file{/usr/local/lib/xemacs-20.4/info/}.
|
|
|
71
|
|
|
72 @end itemize
|
|
|
73
|
|
|
74 @end html
|
|
|
75
|
|
|
76 @end ifset
|
|
|
77
|
|
|
78 @c end ifset points to CANONICAL
|
|
|
79
|
|
0
|
80 @menu
|
|
82
|
81 * Introduction:: Introduction, Policy, Credits.
|
|
|
82 * Installation:: Installation and Trouble Shooting.
|
|
|
83 * Customization:: Customization and Options.
|
|
|
84 * Subsystems:: Major Subsystems.
|
|
|
85 * Miscellaneous:: The Miscellaneous Stuff.
|
|
359
|
86 * MS Windows:: XEmacs on Microsoft Windows.
|
|
82
|
87 * Current Events:: What the Future Holds.
|
|
207
|
88
|
|
|
89 @detailmenu
|
|
|
90
|
|
|
91 --- The Detailed Node Listing ---
|
|
|
92
|
|
|
93 Introduction, Policy, Credits
|
|
|
94
|
|
|
95 * Q1.0.1:: What is XEmacs?
|
|
|
96 * Q1.0.2:: What is the current version of XEmacs?
|
|
|
97 * Q1.0.3:: Where can I find it?
|
|
|
98 * Q1.0.4:: Why Another Version of Emacs?
|
|
|
99 * Q1.0.5:: Why Haven't XEmacs and GNU Emacs Merged?
|
|
282
|
100 * Q1.0.6:: Where can I get help?
|
|
365
|
101 * Q1.0.7:: Where are the mailing lists archived?
|
|
207
|
102 * Q1.0.8:: How do you pronounce XEmacs?
|
|
282
|
103 * Q1.0.9:: What does XEmacs look like?
|
|
207
|
104 * Q1.0.10:: Is there a port of XEmacs to Microsoft ('95 or NT)?
|
|
|
105 * Q1.0.11:: Is there a port of XEmacs to the Macintosh?
|
|
|
106 * Q1.0.12:: Is there a port of XEmacs to NextStep?
|
|
|
107 * Q1.0.13:: Is there a port of XEmacs to OS/2?
|
|
|
108 * Q1.0.14:: Where can I get a printed copy of the XEmacs users manual?
|
|
|
109
|
|
|
110 Policies:
|
|
|
111 * Q1.1.1:: What is the FAQ editorial policy?
|
|
|
112 * Q1.1.2:: How do I become a Beta Tester?
|
|
|
113 * Q1.1.3:: How do I contribute to XEmacs itself?
|
|
|
114
|
|
|
115 Credits:
|
|
|
116 * Q1.2.1:: Who wrote XEmacs?
|
|
282
|
117 * Q1.2.2:: Who contributed to this version of the FAQ?
|
|
|
118 * Q1.2.3:: Who contributed to the FAQ in the past?
|
|
207
|
119
|
|
|
120 Internationalization:
|
|
365
|
121 * Q1.3.1:: What is the status of internationalization support aka MULE (including Asian language support?
|
|
|
122 * Q1.3.2:: How can I help with internationalization?
|
|
207
|
123 * Q1.3.3:: How do I type non-ASCII characters?
|
|
|
124 * Q1.3.4:: Can XEmacs messages come out in a different language?
|
|
365
|
125 * Q1.3.5:: Please explain the various input methods in MULE/XEmacs
|
|
|
126 * Q1.3.6:: How do I portably code for MULE/XEmacs?
|
|
282
|
127 * Q1.3.7:: How about Cyrillic Modes?
|
|
207
|
128
|
|
|
129 Getting Started:
|
|
|
130 * Q1.4.1:: What is a @file{.emacs} and is there a sample one?
|
|
|
131 * Q1.4.2:: Can I use the same @file{.emacs} with the other Emacs?
|
|
|
132 * Q1.4.3:: Any good XEmacs tutorials around?
|
|
|
133 * Q1.4.4:: May I see an example of a useful XEmacs Lisp function?
|
|
|
134 * Q1.4.5:: And how do I bind it to a key?
|
|
|
135 * Q1.4.6:: What's the difference between a macro and a function?
|
|
|
136
|
|
|
137 Installation and Trouble Shooting
|
|
|
138
|
|
282
|
139 * Q2.0.1:: Running XEmacs without installing.
|
|
|
140 * Q2.0.2:: XEmacs is too big.
|
|
207
|
141 * Q2.0.3:: Compiling XEmacs with Netaudio.
|
|
|
142 * Q2.0.4:: Problems with Linux and ncurses.
|
|
|
143 * Q2.0.5:: Do I need X11 to run XEmacs?
|
|
|
144 * Q2.0.6:: I'm having strange crashes. What do I do?
|
|
|
145 * Q2.0.7:: Libraries in non-standard locations.
|
|
|
146 * Q2.0.8:: can't resolve symbol _h_errno
|
|
282
|
147 * Q2.0.9:: Where do I find external libraries?
|
|
207
|
148 * Q2.0.10:: After I run configure I find a coredump, is something wrong?
|
|
|
149 * Q2.0.11:: XEmacs can't resolve host names.
|
|
282
|
150 * Q2.0.12:: Why can't I strip XEmacs?
|
|
367
|
151 * Q2.0.13:: I don't need no steenkin' packages. Do I? (NEW)
|
|
|
152 * Q2.0.14:: How do I figure out which packages to install? (NEW)
|
|
207
|
153
|
|
|
154 Trouble Shooting:
|
|
|
155 * Q2.1.1:: XEmacs just crashed on me!
|
|
|
156 * Q2.1.2:: Cryptic Minibuffer messages.
|
|
|
157 * Q2.1.3:: Translation Table Syntax messages at Startup.
|
|
|
158 * Q2.1.4:: Startup warnings about deducing proper fonts?
|
|
|
159 * Q2.1.5:: XEmacs cannot connect to my X Terminal.
|
|
|
160 * Q2.1.6:: XEmacs just locked up my Linux X server.
|
|
|
161 * Q2.1.7:: HP Alt key as Meta.
|
|
|
162 * Q2.1.8:: got (wrong-type-argument color-instance-p nil)!
|
|
|
163 * Q2.1.9:: XEmacs causes my OpenWindows 3.0 server to crash.
|
|
|
164 * Q2.1.10:: Warnings from incorrect key modifiers.
|
|
282
|
165 * Q2.1.11:: Can't instantiate image error... in toolbar
|
|
207
|
166 * Q2.1.12:: Regular Expression Problems on DEC OSF1.
|
|
|
167 * Q2.1.13:: HP/UX 10.10 and @code{create_process} failure
|
|
|
168 * Q2.1.14:: @kbd{C-g} doesn't work for me. Is it broken?
|
|
|
169 * Q2.1.15:: How to debug an XEmacs problem with a debugger.
|
|
|
170 * Q2.1.16:: XEmacs crashes in @code{strcat} on HP/UX 10.
|
|
|
171 * Q2.1.17:: @samp{Marker does not point anywhere}.
|
|
365
|
172 * Q2.1.18:: [This question intentionally left blank]
|
|
207
|
173 * Q2.1.19:: XEmacs does not follow the local timezone.
|
|
|
174 * Q2.1.20:: @samp{Symbol's function definition is void: hkey-help-show.}
|
|
365
|
175 * Q2.1.21:: [This question intentionally left blank]
|
|
207
|
176 * Q2.1.22:: XEmacs seems to take a really long time to do some things.
|
|
|
177 * Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
|
|
365
|
178 * Q2.1.24:: XEmacs won't start without network. (NEW)
|
|
367
|
179 * Q2.1.25:: After upgrading, XEmacs won't do `foo' any more! (NEW)
|
|
207
|
180
|
|
|
181 Customization and Options
|
|
|
182
|
|
282
|
183 * Q3.0.1:: What version of Emacs am I running?
|
|
207
|
184 * Q3.0.2:: How do I evaluate Elisp expressions?
|
|
|
185 * Q3.0.3:: @code{(setq tab-width 6)} behaves oddly.
|
|
|
186 * Q3.0.4:: How can I add directories to the @code{load-path}?
|
|
|
187 * Q3.0.5:: How to check if a lisp function is defined?
|
|
|
188 * Q3.0.6:: Can I force the output of @code{(face-list)} to a buffer?
|
|
282
|
189 * Q3.0.7:: Font selections don't get saved after @code{Save Options}.
|
|
207
|
190 * Q3.0.8:: How do I make a single minibuffer frame?
|
|
217
|
191 * Q3.0.9:: What is @code{Customize}?
|
|
207
|
192
|
|
|
193 X Window System & Resources:
|
|
|
194 * Q3.1.1:: Where is a list of X resources?
|
|
|
195 * Q3.1.2:: How can I detect a color display?
|
|
365
|
196 * Q3.1.3:: [This question intentionally left blank]
|
|
|
197 * Q3.1.4:: [This question intentionally left blank]
|
|
207
|
198 * Q3.1.5:: How can I get the icon to just say @samp{XEmacs}?
|
|
|
199 * Q3.1.6:: How can I have the window title area display the full path?
|
|
|
200 * Q3.1.7:: @samp{xemacs -name junk} doesn't work?
|
|
282
|
201 * Q3.1.8:: @samp{-iconic} doesn't work.
|
|
207
|
202
|
|
|
203 Textual Fonts & Colors:
|
|
|
204 * Q3.2.1:: How can I set color options from @file{.emacs}?
|
|
|
205 * Q3.2.2:: How do I set the text, menu and modeline fonts?
|
|
|
206 * Q3.2.3:: How can I set the colors when highlighting a region?
|
|
282
|
207 * Q3.2.4:: How can I limit color map usage?
|
|
207
|
208 * Q3.2.5:: My tty supports color, but XEmacs doesn't use them.
|
|
282
|
209 * Q3.2.6:: Can I have pixmap backgrounds in XEmacs?
|
|
207
|
210
|
|
|
211 The Modeline:
|
|
|
212 * Q3.3.1:: How can I make the modeline go away?
|
|
|
213 * Q3.3.2:: How do you have XEmacs display the line number in the modeline?
|
|
|
214 * Q3.3.3:: How do I get XEmacs to put the time of day on the modeline?
|
|
|
215 * Q3.3.4:: How do I turn off current chapter from AUC TeX modeline?
|
|
|
216 * Q3.3.5:: How can one change the modeline color based on the mode used?
|
|
|
217
|
|
282
|
218 Multiple Device Support:
|
|
|
219 * Q3.4.1:: How do I open a frame on another screen of my multi-headed display?
|
|
207
|
220 * Q3.4.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
221
|
|
282
|
222 The Keyboard:
|
|
207
|
223 * Q3.5.1:: How can I bind complex functions (or macros) to keys?
|
|
|
224 * Q3.5.2:: How can I stop down-arrow from adding empty lines to the bottom of my buffers?
|
|
|
225 * Q3.5.3:: How do I bind C-. and C-; to scroll one line up and down?
|
|
|
226 * Q3.5.4:: Globally binding @kbd{Delete}?
|
|
|
227 * Q3.5.5:: Scrolling one line at a time.
|
|
282
|
228 * Q3.5.6:: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
207
|
229 * Q3.5.7:: How can you type in special characters in XEmacs?
|
|
|
230 * Q3.5.8:: Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
|
|
|
231 * Q3.5.9:: How do I make the Delete key delete forward?
|
|
|
232 * Q3.5.10:: Can I turn on @dfn{sticky} modifier keys?
|
|
282
|
233 * Q3.5.11:: How do I map the arrow keys?
|
|
369
|
234 * Q3.5.12:: XEmacs complains about my xmodmap (I hate the default X keymap).
|
|
207
|
235
|
|
|
236 The Cursor:
|
|
|
237 * Q3.6.1:: Is there a way to make the bar cursor thicker?
|
|
|
238 * Q3.6.2:: Is there a way to get back the old block cursor where the cursor covers the character in front of the point?
|
|
|
239 * Q3.6.3:: Can I make the cursor blink?
|
|
|
240
|
|
|
241 The Mouse and Highlighting:
|
|
|
242 * Q3.7.1:: How can I turn off Mouse pasting?
|
|
|
243 * Q3.7.2:: How do I set control/meta/etc modifiers on mouse buttons?
|
|
|
244 * Q3.7.3:: Clicking the left button does not do anything in buffer list.
|
|
|
245 * Q3.7.4:: How can I get a list of buffers when I hit mouse button 3?
|
|
|
246 * Q3.7.5:: Why does cut-and-paste not work between XEmacs and a cmdtool?
|
|
|
247 * Q3.7.6:: How I can set XEmacs up so that it pastes where the text cursor is?
|
|
|
248 * Q3.7.7:: How do I select a rectangular region?
|
|
|
249 * Q3.7.8:: Why does @kbd{M-w} take so long?
|
|
|
250
|
|
|
251 The Menubar and Toolbar:
|
|
|
252 * Q3.8.1:: How do I get rid of the menu (or menubar)?
|
|
|
253 * Q3.8.2:: Can I customize the basic menubar?
|
|
|
254 * Q3.8.3:: How do I control how many buffers are listed in the menu @code{Buffers} list?
|
|
|
255 * Q3.8.4:: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
256 * Q3.8.5:: How can I bind a key to a function to toggle the toolbar?
|
|
|
257
|
|
|
258 Scrollbars:
|
|
|
259 * Q3.9.1:: How can I disable the scrollbar?
|
|
|
260 * Q3.9.2:: How can one use resources to change scrollbar colors?
|
|
|
261 * Q3.9.3:: Moving the scrollbar can move the point; can I disable this?
|
|
|
262 * Q3.9.4:: How can I get automatic horizontal scrolling?
|
|
|
263
|
|
|
264 Text Selections:
|
|
282
|
265 * Q3.10.1:: How can I turn off or change highlighted selections?
|
|
207
|
266 * Q3.10.2:: How do I get that typing on an active region removes it?
|
|
|
267 * Q3.10.3:: Can I turn off the highlight during isearch?
|
|
|
268 * Q3.10.4:: How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
|
|
|
269 * Q3.10.5:: The region disappears when I hit the end of buffer while scrolling.
|
|
|
270
|
|
|
271 Major Subsystems
|
|
|
272
|
|
|
273 * Q4.0.1:: How do I set up VM to retrieve remote mail using POP?
|
|
|
274 * Q4.0.2:: How do I get VM to filter mail for me?
|
|
|
275 * Q4.0.3:: How can I get VM to automatically check for new mail?
|
|
|
276 * Q4.0.4:: [This question intentionally left blank]
|
|
|
277 * Q4.0.5:: How do I get my outgoing mail archived?
|
|
|
278 * Q4.0.6:: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"?
|
|
|
279 * Q4.0.7:: Is there a mailing list or FAQ for VM?
|
|
217
|
280 * Q4.0.8:: Remote mail reading with VM.
|
|
207
|
281 * Q4.0.9:: rmail or VM gets an error incorporating new mail.
|
|
|
282 * Q4.0.10:: How do I make VM stay in a single frame?
|
|
|
283 * Q4.0.11:: How do I make VM or mh-e display graphical smilies?
|
|
|
284 * Q4.0.12:: Customization of VM not covered in the manual or here.
|
|
|
285
|
|
|
286 Web browsing with W3:
|
|
|
287 * Q4.1.1:: What is W3?
|
|
|
288 * Q4.1.2:: How do I run W3 from behind a firewall?
|
|
|
289 * Q4.1.3:: Is it true that W3 supports style sheets and tables?
|
|
|
290
|
|
|
291 Reading Netnews and Mail with Gnus:
|
|
282
|
292 * Q4.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
207
|
293 * Q4.2.2:: [This question intentionally left blank]
|
|
|
294 * Q4.2.3:: How do I make Gnus stay within a single frame?
|
|
|
295 * Q4.2.4:: How do I customize the From: line?
|
|
|
296
|
|
|
297 Other Mail & News:
|
|
|
298 * Q4.3.1:: How can I read and/or compose MIME messages?
|
|
|
299 * Q4.3.2:: What is TM and where do I get it?
|
|
|
300 * Q4.3.3:: Why isn't this @code{movemail} program working?
|
|
|
301 * Q4.3.4:: Movemail is also distributed by Netscape? Can that cause problems?
|
|
|
302 * Q4.3.5:: Where do I find pstogif (required by tm)?
|
|
|
303
|
|
|
304 Sparcworks, EOS, and WorkShop:
|
|
282
|
305 * Q4.4.1:: What is SPARCworks, EOS, and WorkShop
|
|
353
|
306 * Q4.4.2:: How do I start the Sun Workshop support in XEmacs 21?
|
|
207
|
307
|
|
|
308 Energize:
|
|
|
309 * Q4.5.1:: What is/was Energize?
|
|
|
310
|
|
|
311 Infodock:
|
|
|
312 * Q4.6.1:: What is Infodock?
|
|
|
313
|
|
|
314 Other Unbundled Packages:
|
|
|
315 * Q4.7.1:: What is AUC TeX? Where do you get it?
|
|
|
316 * Q4.7.2:: Are there any Emacs Lisp Spreadsheets?
|
|
365
|
317 * Q4.7.3:: [This question intentionally left blank]
|
|
207
|
318 * Q4.7.4:: Problems installing AUC TeX
|
|
|
319 * Q4.7.5:: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
282
|
320 * Q4.7.6:: Is there a MatLab mode?
|
|
207
|
321
|
|
|
322 The Miscellaneous Stuff
|
|
|
323
|
|
|
324 * Q5.0.1:: How can I do source code highlighting using font-lock?
|
|
|
325 * Q5.0.2:: I do not like cc-mode. How do I use the old c-mode?
|
|
|
326 * Q5.0.3:: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
327 * Q5.0.4:: How can I enable auto-indent?
|
|
|
328 * Q5.0.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
329 * Q5.0.6:: How do I start up a second shell buffer?
|
|
|
330 * Q5.0.7:: Telnet from shell filters too much.
|
|
|
331 * Q5.0.8:: Why does edt emulation not work?
|
|
|
332 * Q5.0.9:: How can I emulate VI and use it as my default mode?
|
|
282
|
333 * Q5.0.10:: [This question intentionally left blank]
|
|
365
|
334 * Q5.0.11:: How do I turn on filladapt for all buffers?
|
|
207
|
335 * Q5.0.12:: How do I disable gnuserv from opening a new frame?
|
|
|
336 * Q5.0.13:: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
|
337 * Q5.0.14:: Strange things are happening in Shell Mode.
|
|
|
338 * Q5.0.15:: Where do I get the latest CC Mode?
|
|
|
339 * Q5.0.16:: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
340 * Q5.0.17:: How can I get two instances of info?
|
|
365
|
341 * Q5.0.18:: [This question intentionally left blank]
|
|
207
|
342 * Q5.0.19:: Is there something better than LaTeX mode?
|
|
274
|
343 * Q5.0.20:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
207
|
344
|
|
|
345 Emacs Lisp Programming Techniques:
|
|
|
346 * Q5.1.1:: The difference in key sequences between XEmacs and GNU Emacs?
|
|
|
347 * Q5.1.2:: Can I generate "fake" keyboard events?
|
|
|
348 * Q5.1.3:: Could you explain @code{read-kbd-macro} in more detail?
|
|
|
349 * Q5.1.4:: What is the performance hit of @code{let}?
|
|
|
350 * Q5.1.5:: What is the recommended use of @code{setq}?
|
|
|
351 * Q5.1.6:: What is the typical misuse of @code{setq} ?
|
|
367
|
352 * Q5.1.7:: I like the @code{do} form of cl, does it slow things down?
|
|
207
|
353 * Q5.1.8:: I like recursion, does it slow things down?
|
|
|
354 * Q5.1.9:: How do I put a glyph as annotation in a buffer?
|
|
282
|
355 * Q5.1.10:: @code{map-extents} won't traverse all of my extents!
|
|
|
356 * Q5.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
207
|
357
|
|
|
358 Sound:
|
|
|
359 * Q5.2.1:: How do I turn off the sound?
|
|
|
360 * Q5.2.2:: How do I get funky sounds instead of a boring beep?
|
|
|
361 * Q5.2.3:: What's NAS, how do I get it?
|
|
|
362 * Q5.2.4:: Sunsite sounds don't play.
|
|
|
363
|
|
|
364 Miscellaneous:
|
|
|
365 * Q5.3.1:: How do you make XEmacs indent CL if-clauses correctly?
|
|
|
366 * Q5.3.2:: Fontifying hangs when editing a postscript file.
|
|
|
367 * Q5.3.3:: How can I print WYSIWYG a font-locked buffer?
|
|
|
368 * Q5.3.4:: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
|
369 * Q5.3.5:: How do I specify the paths that XEmacs uses for finding files?
|
|
|
370 * Q5.3.6:: [This question intentionally left blank]
|
|
|
371 * Q5.3.7:: Can I have the end of the buffer delimited in some way?
|
|
|
372 * Q5.3.8:: How do I insert today's date into a buffer?
|
|
|
373 * Q5.3.9:: Are only certain syntactic character classes available for abbrevs?
|
|
|
374 * Q5.3.10:: How can I get those oh-so-neat X-Face lines?
|
|
|
375 * Q5.3.11:: How do I add new Info directories?
|
|
|
376 * Q5.3.12:: What do I need to change to make printing work?
|
|
|
377
|
|
359
|
378 XEmacs on MS Windows
|
|
|
379
|
|
|
380 General Info:
|
|
365
|
381 * Q6.0.1:: What is the status of the XEmacs port to Windows?
|
|
|
382 * Q6.0.2:: What flavors of MS Windows are supported?
|
|
|
383 * Q6.0.3:: Are binary kits available?
|
|
|
384 * Q6.0.4:: Does XEmacs on MS Windows require an X server to run?
|
|
359
|
385
|
|
|
386 Building XEmacs on MS Windows:
|
|
365
|
387 * Q6.1.1:: I decided to run with X. Where do I get an X server?
|
|
|
388 * Q6.1.2:: What compiler do I need to compile XEmacs?
|
|
|
389 * Q6.1.3:: How do I compile for the native port?
|
|
|
390 * Q6.1.4:: How do I compile for the X port?
|
|
|
391 * Q6.1.5:: How do I compile for Cygnus' Cygwin?
|
|
|
392 * Q6.1.6:: What do I need for Cygwin?
|
|
359
|
393
|
|
|
394 Customization and User Interface:
|
|
365
|
395 * Q6.2.1:: How will the port cope with differences in the Windows user interface?
|
|
|
396 * Q6.2.2:: How do I change fonts in XEmacs on MS Windows?
|
|
|
397 * Q6.2.3:: Where do I put my @file{.emacs} file?
|
|
359
|
398
|
|
|
399 Miscellaneous:
|
|
365
|
400 * Q6.3.1:: Will XEmacs rename all the win32-* symbols to w32-*?
|
|
|
401 * Q6.3.2:: What are the differences between the various MS Windows emacsen?
|
|
|
402 * Q6.3.3:: What is the porting team doing at the moment?
|
|
359
|
403
|
|
361
|
404 Troubleshooting:
|
|
|
405 * Q6.4.1:: XEmacs won't start on Windows. (NEW)
|
|
|
406
|
|
359
|
407 Current Events:
|
|
|
408
|
|
|
409 * Q7.0.1:: What is new in 20.2?
|
|
|
410 * Q7.0.2:: What is new in 20.3?
|
|
|
411 * Q7.0.3:: What is new in 20.4?
|
|
|
412 * Q7.0.4:: Procedural changes in XEmacs development.
|
|
207
|
413 @end detailmenu
|
|
70
|
414 @end menu
|
|
|
415
|
|
82
|
416 @node Introduction, Installation, Top, Top
|
|
274
|
417 @unnumbered 1 Introduction, Policy, Credits
|
|
|
418
|
|
|
419 Learning XEmacs is a lifelong activity. Even people who have used Emacs
|
|
|
420 for years keep discovering new features. Therefore this document cannot
|
|
|
421 be complete. Instead it is aimed at the person who is either
|
|
|
422 considering XEmacs for their own use, or has just obtained it and is
|
|
|
423 wondering what to do next. It is also useful as a reference to
|
|
|
424 available resources.
|
|
|
425
|
|
365
|
426 The previous maintainer of the FAQ was @email{rossini@@biostat.washington.edu,
|
|
274
|
427 Anthony Rossini}, who started it, after getting tired of hearing JWZ
|
|
|
428 complain about repeatedly having to answer questions.
|
|
359
|
429 @email{ben@@xemacs.org, Ben Wing} and @email{cthomp@@xemacs.org, Chuck
|
|
274
|
430 Thompson}, the principal authors of XEmacs, then took over and Ben did
|
|
|
431 a massive update reorganizing the whole thing. At which point Anthony
|
|
|
432 took back over, but then had to give it up again. Some of the other
|
|
|
433 contributors to this FAQ are listed later in this document.
|
|
82
|
434
|
|
116
|
435 The previous version was converted to hypertext format, and edited by
|
|
359
|
436 @email{steve@@xemacs.org, Steven L. Baur}. It was converted back to
|
|
365
|
437 texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}. The FAQ was then
|
|
|
438 maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it
|
|
|
439 on to ChristianNyb@o{}.
|
|
274
|
440
|
|
|
441 If you notice any errors or items which should be added or amended to
|
|
365
|
442 this FAQ please send email to @email{faq@@xemacs.org, Sandra
|
|
|
443 Wambold}. Include @samp{XEmacs FAQ} on the Subject: line.
|
|
70
|
444
|
|
|
445 @menu
|
|
82
|
446 Introduction:
|
|
|
447 * Q1.0.1:: What is XEmacs?
|
|
|
448 * Q1.0.2:: What is the current version of XEmacs?
|
|
|
449 * Q1.0.3:: Where can I find it?
|
|
|
450 * Q1.0.4:: Why Another Version of Emacs?
|
|
|
451 * Q1.0.5:: Why Haven't XEmacs and GNU Emacs Merged?
|
|
282
|
452 * Q1.0.6:: Where can I get help?
|
|
365
|
453 * Q1.0.7:: Where are the mailing lists archived?
|
|
82
|
454 * Q1.0.8:: How do you pronounce XEmacs?
|
|
282
|
455 * Q1.0.9:: What does XEmacs look like?
|
|
82
|
456 * Q1.0.10:: Is there a port of XEmacs to Microsoft ('95 or NT)?
|
|
|
457 * Q1.0.11:: Is there a port of XEmacs to the Macintosh?
|
|
|
458 * Q1.0.12:: Is there a port of XEmacs to NextStep?
|
|
|
459 * Q1.0.13:: Is there a port of XEmacs to OS/2?
|
|
86
|
460 * Q1.0.14:: Where can I get a printed copy of the XEmacs users manual?
|
|
82
|
461
|
|
|
462 Policies:
|
|
|
463 * Q1.1.1:: What is the FAQ editorial policy?
|
|
|
464 * Q1.1.2:: How do I become a Beta Tester?
|
|
|
465 * Q1.1.3:: How do I contribute to XEmacs itself?
|
|
|
466
|
|
|
467 Credits:
|
|
|
468 * Q1.2.1:: Who wrote XEmacs?
|
|
282
|
469 * Q1.2.2:: Who contributed to this version of the FAQ?
|
|
|
470 * Q1.2.3:: Who contributed to the FAQ in the past?
|
|
82
|
471
|
|
|
472 Internationalization:
|
|
365
|
473 * Q1.3.1:: What is the status of internationalization support aka MULE (including Asian language support?
|
|
|
474 * Q1.3.2:: How can I help with internationalization?
|
|
82
|
475 * Q1.3.3:: How do I type non-ASCII characters?
|
|
|
476 * Q1.3.4:: Can XEmacs messages come out in a different language?
|
|
365
|
477 * Q1.3.5:: Please explain the various input methods in MULE/XEmacs
|
|
|
478 * Q1.3.6:: How do I portably code for MULE/XEmacs?
|
|
282
|
479 * Q1.3.7:: How about Cyrillic Modes?
|
|
82
|
480
|
|
|
481 Getting Started:
|
|
|
482 * Q1.4.1:: What is a @file{.emacs} and is there a sample one?
|
|
163
|
483 * Q1.4.2:: Can I use the same @file{.emacs} with the other Emacs?
|
|
82
|
484 * Q1.4.3:: Any good XEmacs tutorials around?
|
|
|
485 * Q1.4.4:: May I see an example of a useful XEmacs Lisp function?
|
|
|
486 * Q1.4.5:: And how do I bind it to a key?
|
|
|
487 * Q1.4.6:: What's the difference between a macro and a function?
|
|
0
|
488 @end menu
|
|
|
489
|
|
82
|
490 @node Q1.0.1, Q1.0.2, Introduction, Introduction
|
|
274
|
491 @unnumberedsec 1.0: Introduction
|
|
|
492 @unnumberedsubsec Q1.0.1: What is XEmacs?
|
|
|
493
|
|
0
|
494
|
|
|
495 An alternative to GNU Emacs, originally based on an early alpha version
|
|
82
|
496 of FSF's version 19, and has diverged quite a bit since then. XEmacs
|
|
|
497 was known as Lucid Emacs through version 19.10. Almost all features of
|
|
227
|
498 GNU Emacs are supported in XEmacs. The maintainers of XEmacs actively
|
|
82
|
499 track changes to GNU Emacs while also working to add new features.
|
|
|
500
|
|
|
501 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction
|
|
274
|
502 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs?
|
|
|
503
|
|
365
|
504 XEmacs versions 21.1.* are releases made from the current stable
|
|
|
505 sources. XEmacs versions 21.2.* are releases made from the development
|
|
|
506 sources. Check at @uref{http://www.xemacs.org} for the current minor
|
|
|
507 version.
|
|
215
|
508
|
|
|
509 XEmacs 19.16 was the last release of v19, released in November, 1997,
|
|
|
510 which was also the last version without international language support.
|
|
82
|
511
|
|
|
512 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction
|
|
274
|
513 @unnumberedsubsec Q1.0.3: Where can I find it?
|
|
82
|
514
|
|
359
|
515 The canonical source and binaries can be found via anonymous FTP at:
|
|
82
|
516
|
|
|
517 @example
|
|
274
|
518 @uref{ftp://ftp.xemacs.org/pub/xemacs/}
|
|
82
|
519 @end example
|
|
|
520
|
|
|
521 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction
|
|
274
|
522 @unnumberedsubsec Q1.0.4: Why Another Version of Emacs?
|
|
82
|
523
|
|
0
|
524 For a detailed description of the differences between GNU Emacs and
|
|
|
525 XEmacs and a detailed history of XEmacs, check out the
|
|
82
|
526 @example
|
|
359
|
527 @uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file}
|
|
82
|
528 @end example
|
|
|
529
|
|
|
530 However, here is a list of some of the reasons why we think you might
|
|
|
531 consider using it:
|
|
0
|
532
|
|
|
533 @itemize @bullet
|
|
|
534 @item
|
|
82
|
535 It looks nicer.
|
|
|
536
|
|
0
|
537 @item
|
|
|
538 The XEmacs maintainers are generally more receptive to suggestions than
|
|
82
|
539 the GNU Emacs maintainers.
|
|
|
540
|
|
0
|
541 @item
|
|
82
|
542 Many more bundled packages than GNU Emacs
|
|
|
543
|
|
0
|
544 @item
|
|
82
|
545 Binaries are available for many common operating systems.
|
|
|
546
|
|
0
|
547 @item
|
|
82
|
548 Face support on TTY's.
|
|
|
549
|
|
0
|
550 @item
|
|
82
|
551 A built-in toolbar.
|
|
|
552
|
|
0
|
553 @item
|
|
82
|
554 Better Motif compliance.
|
|
|
555
|
|
0
|
556 @item
|
|
163
|
557 Some internationalization support (including full MULE support, if
|
|
|
558 compiled with it.)
|
|
82
|
559
|
|
|
560 @item
|
|
|
561 Variable-width fonts.
|
|
|
562
|
|
16
|
563 @item
|
|
82
|
564 Variable-height lines.
|
|
|
565
|
|
0
|
566 @item
|
|
82
|
567 Marginal annotations.
|
|
|
568
|
|
0
|
569 @item
|
|
82
|
570 ToolTalk support.
|
|
|
571
|
|
0
|
572 @item
|
|
|
573 XEmacs can be used as an Xt widget, and can be embedded within another
|
|
82
|
574 application.
|
|
|
575
|
|
0
|
576 @item
|
|
82
|
577 Horizontal and vertical scrollbars (using real toolkit scrollbars).
|
|
|
578
|
|
0
|
579 @item
|
|
|
580 Better APIs (and performance) for attaching fonts, colors, and other
|
|
82
|
581 properties to text.
|
|
|
582
|
|
0
|
583 @item
|
|
82
|
584 The ability to embed arbitrary graphics in a buffer.
|
|
|
585
|
|
0
|
586 @item
|
|
82
|
587 Completely compatible (at the C level) with the Xt-based toolkits.
|
|
|
588
|
|
|
589 @item
|
|
|
590 First production Web Browser supporting Style Sheets.
|
|
0
|
591 @end itemize
|
|
|
592
|
|
82
|
593 @node Q1.0.5, Q1.0.6, Q1.0.4, Introduction
|
|
274
|
594 @unnumberedsubsec Q1.0.5: Why Haven't XEmacs and GNU Emacs Merged?
|
|
82
|
595
|
|
|
596 There are currently irreconcilable differences in the views about
|
|
|
597 technical, programming, design and organizational matters between RMS
|
|
|
598 and the XEmacs development team which provide little hope for a merge to
|
|
|
599 take place in the short-term future.
|
|
|
600
|
|
207
|
601 If you have a comment to add regarding the merge, it is a good idea to
|
|
274
|
602 avoid posting to the newsgroups, because of the very heated flamewars
|
|
282
|
603 that often result. Mail your questions to @email{xemacs-beta@@xemacs.org} and
|
|
274
|
604 @email{bug-gnu-emacs@@prep.ai.mit.edu}.
|
|
207
|
605
|
|
82
|
606 @node Q1.0.6, Q1.0.7, Q1.0.5, Introduction
|
|
274
|
607 @unnumberedsubsec Q1.0.6: Where can I get help?
|
|
0
|
608
|
|
359
|
609 Probably the easiest way, if everything is installed, is to use Info, by
|
|
|
610 pressing @kbd{C-h i}, or selecting @code{Manuals->Info} from the
|
|
|
611 Help Menu. @kbd{M-x apropos} can be used to look for particular commands.
|
|
|
612
|
|
|
613 For items not found in the manual, try reading this FAQ
|
|
|
614 @comment , examining the regular GNU Emacs FAQ (which can be
|
|
|
615 @comment found with the Emacs 19 distribution) as well as at
|
|
|
616 @comment @uref{http://www.eecs.nwu.edu/emacs/faq/}
|
|
|
617 and reading the Usenet group comp.emacs.xemacs.
|
|
|
618
|
|
|
619 If you choose to post to a newsgroup, @strong{please use
|
|
|
620 comp.emacs.xemacs}. Please do not post XEmacs related questions to
|
|
|
621 gnu.emacs.help.
|
|
82
|
622
|
|
|
623 If you cannot post or read Usenet news, there is a corresponding mailing
|
|
|
624 list which is available. It can be subscribed to by sending a message
|
|
359
|
625 to @email{xemacs-request@@xemacs.org} with @samp{subscribe} in the
|
|
|
626 body of the message. Send to the list at @email{xemacs@@xemacs.org}.
|
|
|
627 list. To cancel a subscription, you @strong{must} use the
|
|
|
628 xemacs-request address. Send a message with a subject of
|
|
|
629 @samp{unsubscribe} to be removed.
|
|
82
|
630
|
|
|
631 @node Q1.0.7, Q1.0.8, Q1.0.6, Introduction
|
|
365
|
632 @unnumberedsubsec Q1.0.7: Where are the mailing lists archived?
|
|
82
|
633
|
|
359
|
634 The archives can be found at @uref{http://www.xemacs.org/Lists/Archive}
|
|
207
|
635
|
|
82
|
636 @node Q1.0.8, Q1.0.9, Q1.0.7, Introduction
|
|
274
|
637 @unnumberedsubsec Q1.0.8: How do you pronounce XEmacs?
|
|
82
|
638
|
|
359
|
639 The most common pronounciation is @samp{Eks eemax}.
|
|
82
|
640
|
|
|
641 @node Q1.0.9, Q1.0.10, Q1.0.8, Introduction
|
|
274
|
642 @unnumberedsubsec Q1.0.9: What does XEmacs look like?
|
|
82
|
643
|
|
|
644 Screen snapshots are available in the WWW version of the FAQ.
|
|
126
|
645 @example
|
|
274
|
646 @uref{http://www.xemacs.org/faq/xemacs-faq.html}
|
|
126
|
647 @end example
|
|
82
|
648
|
|
|
649 @node Q1.0.10, Q1.0.11, Q1.0.9, Introduction
|
|
274
|
650 @unnumberedsubsec Q1.0.10: Is there a port of XEmacs to Microsoft ('95 or NT)?
|
|
|
651
|
|
359
|
652 Yes, @xref{MS Windows}.
|
|
|
653
|
|
|
654 @comment Thanks to efforts of many people, coordinated by
|
|
|
655 @comment @email{davidh@@wr.com.au, David Hobley} and @email{marcpa@@cam.org, Marc
|
|
|
656 @comment Paquette}, beta versions of XEmacs now run on 32-bit Windows platforms
|
|
|
657 @comment (NT and 95). The current betas require having an X server to run
|
|
|
658 @comment XEmacs; however, a native NT/95 port is in alpha, thanks to
|
|
|
659 @comment @email{jhar@@tardis.ed.ac.uk, Jonathan Harris}.
|
|
365
|
660 @comment
|
|
359
|
661 @comment Although some features are still unimplemented, XEmacs 21.0 will support
|
|
|
662 @comment MS-Windows.
|
|
365
|
663 @comment
|
|
359
|
664 @comment The NT development is now coordinated by a mailing list at
|
|
|
665 @comment @email{xemacs-nt@@xemacs.org}.
|
|
365
|
666 @comment
|
|
359
|
667 @comment If you are willing to contribute or want to follow the progress, mail to
|
|
|
668 @comment @iftex
|
|
|
669 @comment @*
|
|
|
670 @comment @end iftex
|
|
|
671 @comment @email{xemacs-nt-request@@xemacs.org} to subscribe.
|
|
365
|
672 @comment
|
|
359
|
673 @comment Furthermore, Altrasoft is seeking corporate and government sponsors to
|
|
|
674 @comment help fund a fully native port of XEmacs to Windows 95 and NT using
|
|
|
675 @comment full-time, senior-level staff working under a professionally managed
|
|
|
676 @comment project structure. See @uref{http://www.altrasoft.com/, the Altrasoft
|
|
|
677 @comment web site} for more details
|
|
|
678 @comment or contact Altrasoft directly at 1-888-ALTSOFT.
|
|
365
|
679 @comment
|
|
|
680 @comment
|
|
359
|
681 @comment The closest existing port is @dfn{Win-Emacs}, which is based on Lucid
|
|
|
682 @comment Emacs 19.6. Available from @uref{http://www.pearlsoft.com/}.
|
|
365
|
683 @comment
|
|
359
|
684 @comment There's a port of GNU Emacs (not XEmacs) at
|
|
|
685 @comment @example
|
|
|
686 @comment @uref{http://www.cs.washington.edu/homes/voelker/ntemacs.html}.
|
|
|
687 @comment @end example
|
|
82
|
688
|
|
|
689 @node Q1.0.11, Q1.0.12, Q1.0.10, Introduction
|
|
274
|
690 @unnumberedsubsec Q1.0.11: Is there a port of XEmacs to the Macintosh?
|
|
282
|
691 @c changed
|
|
82
|
692
|
|
365
|
693 @c There has been a port to the MachTen environment of XEmacs 19.13, but no
|
|
|
694 @c patches have been submitted to the maintainers to get this in the
|
|
|
695 @c mainstream distribution.
|
|
|
696 @c
|
|
|
697 @c For the MacOS, there is a port of
|
|
|
698 @c @uref{ftp://ftp.cs.cornell.edu/pub/parmet/, Emacs 18.59}.
|
|
|
699
|
|
|
700 Yes, there is a port of XEmacs 19.14, tested on MacOS 7.6.1 and MacOS
|
|
|
701 8.5.1 by @email{pjarvis@@ispchannel.com, Pitts Jarvis}. It's available
|
|
369
|
702 at @uref{http://homepage.mac.com/pjarvis/xemacs.html}.
|
|
282
|
703
|
|
82
|
704 @node Q1.0.12, Q1.0.13, Q1.0.11, Introduction
|
|
274
|
705 @unnumberedsubsec Q1.0.12: Is there a port of XEmacs to NextStep?
|
|
|
706
|
|
|
707 Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did
|
|
|
708 the port of GNU Emacs to NeXTstep and expressed interest in doing the
|
|
|
709 XEmacs port, but never went any farther.
|
|
82
|
710
|
|
86
|
711 @node Q1.0.13, Q1.0.14, Q1.0.12, Introduction
|
|
274
|
712 @unnumberedsubsec Q1.0.13: Is there a port of XEmacs to OS/2?
|
|
82
|
713
|
|
365
|
714 No, but Alexander Nikolaev <avn_1251@@mail.ru> is working on it.
|
|
82
|
715
|
|
86
|
716 @node Q1.0.14, Q1.1.1, Q1.0.13, Introduction
|
|
274
|
717 @unnumberedsubsec Q1.0.14: Where can I obtain a printed copy of the XEmacs users manual?
|
|
86
|
718
|
|
365
|
719 Pre-printed manuals are not available. If you are familiar with
|
|
359
|
720 TeX, you can generate your own manual from the XEmacs sources.
|
|
|
721
|
|
|
722 HTML and Postscript versions of XEmacs manuals may be available from the
|
|
365
|
723 XEmacs web site in the future. Send requests to @email{faq@@xemacs.org}.
|
|
86
|
724
|
|
88
|
725 @node Q1.1.1, Q1.1.2, Q1.0.14, Introduction
|
|
274
|
726 @unnumberedsec 1.1: Policies
|
|
|
727 @unnumberedsubsec Q1.1.1: What is the FAQ editorial policy?
|
|
82
|
728
|
|
|
729 The FAQ is actively maintained and modified regularly. All links should
|
|
365
|
730 be up to date. Unfortunately, some of the information is out of date --
|
|
|
731 a situation which the FAQ maintainer is working on. All submissions are
|
|
|
732 welcome, please e-mail submissions to @email{faq@@xemacs.org, XEmacs FAQ
|
|
|
733 maintainers}.
|
|
82
|
734
|
|
|
735 Please make sure that @samp{XEmacs FAQ} appears on the Subject: line.
|
|
|
736 If you think you have a better way of answering a question, or think a
|
|
359
|
737 question should be included, we'd like to hear about it. Questions and
|
|
365
|
738 answers included into the FAQ will be edited for spelling and grammar
|
|
82
|
739 and will be attributed. Answers appearing without attribution are
|
|
365
|
740 either from versions of the FAQ dated before May 1996 or are from
|
|
|
741 previous FAQ maintainers. Answers quoted from Usenet news articles will
|
|
|
742 always be attributed, regardless of the author.
|
|
82
|
743
|
|
|
744 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction
|
|
274
|
745 @unnumberedsubsec Q1.1.2: How do I become a Beta Tester?
|
|
|
746
|
|
359
|
747 Send an email message to @email{xemacs-beta-request@@xemacs.org} with
|
|
|
748 the line @samp{subscribe} in the body of the message.
|
|
82
|
749
|
|
|
750 Be prepared to get your hands dirty, as beta testers are expected to
|
|
|
751 identify problems as best they can.
|
|
|
752
|
|
|
753 @node Q1.1.3, Q1.2.1, Q1.1.2, Introduction
|
|
274
|
754 @unnumberedsubsec Q1.1.3: How do I contribute to XEmacs itself?
|
|
|
755
|
|
359
|
756 Ben Wing @email{ben@@xemacs.org} writes:
|
|
82
|
757
|
|
|
758 @quotation
|
|
|
759 BTW if you have a wish list of things that you want added, you have to
|
|
|
760 speak up about it! More specifically, you can do the following if you
|
|
|
761 want a feature added (in increasing order of usefulness):
|
|
|
762
|
|
|
763 @itemize @bullet
|
|
|
764 @item
|
|
|
765 Make a posting about a feature you want added.
|
|
|
766
|
|
|
767 @item
|
|
|
768 Become a beta tester and make more postings about those same features.
|
|
|
769
|
|
|
770 @item
|
|
|
771 Convince us that you're going to use the features in some cool and
|
|
|
772 useful way.
|
|
|
773
|
|
|
774 @item
|
|
|
775 Come up with a clear and well-thought-out API concerning the features.
|
|
|
776
|
|
|
777 @item
|
|
|
778 Write the code to implement a feature and send us a patch.
|
|
|
779 @end itemize
|
|
|
780
|
|
|
781 (not that we're necessarily requiring you to write the code, but we can
|
|
|
782 always hope :)
|
|
|
783 @end quotation
|
|
|
784
|
|
|
785 @node Q1.2.1, Q1.2.2, Q1.1.3, Introduction
|
|
274
|
786 @unnumberedsec 1.2: Credits
|
|
|
787 @unnumberedsubsec Q1.2.1: Who wrote XEmacs?
|
|
82
|
788
|
|
|
789 XEmacs is the result of the time and effort of many people. The
|
|
213
|
790 developers responsible for the 19.16/20.x releases are:
|
|
82
|
791
|
|
|
792 @itemize @bullet
|
|
282
|
793 @item @email{martin@@xemacs.org, Martin Buchholz}
|
|
367
|
794 @html
|
|
282
|
795 <br><img src="mrb.jpeg" alt="Portrait of Martin Buchholz"><br>
|
|
367
|
796 @end html
|
|
274
|
797
|
|
|
798
|
|
359
|
799 @item @email{steve@@xemacs.org, Steve Baur}
|
|
274
|
800
|
|
367
|
801 @html
|
|
282
|
802 <br><img src="steve.gif" alt="Portrait of Steve Baur"><br>
|
|
367
|
803 @end html
|
|
274
|
804
|
|
|
805
|
|
359
|
806 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
|
|
274
|
807
|
|
367
|
808 @html
|
|
282
|
809 <br><img src="hniksic.jpeg" alt="Portrait of Hrvoje Niksic"><br>
|
|
367
|
810 @end html
|
|
274
|
811
|
|
82
|
812 @end itemize
|
|
|
813
|
|
|
814 The developers responsible for the 19.14 release are:
|
|
|
815
|
|
|
816 @itemize @bullet
|
|
274
|
817 @item @email{cthomp@@xemacs.org, Chuck Thompson}
|
|
367
|
818 @html
|
|
282
|
819 <br><img src="cthomp.jpeg" alt="Portrait of Chuck Thompson"><br>
|
|
367
|
820 @end html
|
|
82
|
821
|
|
|
822 Chuck was Mr. XEmacs from 19.11 through 19.14, and is responsible
|
|
|
823 for XEmacs becoming a widely distributed program over the Internet.
|
|
|
824
|
|
359
|
825 @item @email{ben@@xemacs.org, Ben Wing}
|
|
367
|
826 @html
|
|
282
|
827 <br><img src="wing.gif" alt="Portrait of Ben Wing"><br>
|
|
367
|
828 @end html
|
|
274
|
829
|
|
82
|
830 @end itemize
|
|
|
831
|
|
282
|
832
|
|
|
833 @itemize @bullet
|
|
359
|
834 @item @email{jwz@@jwz.org, Jamie Zawinski}
|
|
367
|
835 @html
|
|
282
|
836 <br><img src="jwz.gif" alt="Portrait of Jamie Zawinski"><br>
|
|
367
|
837 @end html
|
|
282
|
838
|
|
82
|
839 Jamie Zawinski was Mr. Lucid Emacs from 19.0 through 19.10, the last
|
|
|
840 release actually named Lucid Emacs. Richard Mlynarik was crucial to
|
|
|
841 most of those releases.
|
|
|
842
|
|
367
|
843 @item @email{Mly@@POBox.COM, Richard Mlynarik}
|
|
82
|
844 @end itemize
|
|
|
845
|
|
|
846 Along with many other contributors, partially enumerated in the
|
|
|
847 @samp{About XEmacs} option in the Help menu.
|
|
|
848
|
|
|
849 @node Q1.2.2, Q1.2.3, Q1.2.1, Introduction
|
|
274
|
850 @unnumberedsubsec Q1.2.2: Who contributed to this version of the FAQ?
|
|
82
|
851
|
|
|
852 The following people contributed valuable suggestions to building this
|
|
|
853 version of the FAQ (listed in alphabetical order):
|
|
|
854
|
|
|
855 @itemize @bullet
|
|
274
|
856 @item @email{steve@@xemacs.org, SL Baur}
|
|
|
857
|
|
359
|
858 @item @email{hniksic@@xemacs.org, Hrvoje Niksic}
|
|
274
|
859
|
|
|
860 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
|
|
227
|
861
|
|
82
|
862 @end itemize
|
|
|
863
|
|
|
864 @node Q1.2.3, Q1.3.1, Q1.2.2, Introduction
|
|
274
|
865 @unnumberedsubsec Q1.2.3: Who contributed to the FAQ in the past?
|
|
82
|
866
|
|
|
867 This is only a partial list, as many names were lost in a hard disk
|
|
|
868 crash some time ago.
|
|
|
869
|
|
|
870 @itemize @bullet
|
|
274
|
871 @item @email{binge@@aloft.att.com, Curtis.N.Bingham}
|
|
|
872
|
|
365
|
873 @item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan}
|
|
|
874
|
|
274
|
875 @item @email{rjc@@cogsci.ed.ac.uk, Richard Caley}
|
|
|
876
|
|
|
877 @item @email{cognot@@ensg.u-nancy.fr, Richard Cognot}
|
|
|
878
|
|
365
|
879 @item @email{daku@@nortel.ca, Mark Daku}
|
|
|
880
|
|
274
|
881 @item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque}
|
|
|
882
|
|
|
883 @item @email{eeide@@cs.utah.edu, Eric Eide}
|
|
|
884
|
|
365
|
885 @item @email{af@@biomath.jussieu.fr, Alain Fauconnet}
|
|
|
886
|
|
274
|
887 @item @email{cflatter@@nrao.edu, Chris Flatters}
|
|
|
888
|
|
|
889 @item @email{ginsparg@@adra.com, Evelyn Ginsparg}
|
|
|
890
|
|
|
891 @item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall}
|
|
|
892
|
|
|
893 @item @email{dkindred@@cmu.edu, Darrell Kindred}
|
|
|
894
|
|
|
895 @item @email{dmoore@@ucsd.edu, David Moore}
|
|
|
896
|
|
|
897 @item @email{arup+@@cmu.edu, Arup Mukherjee}
|
|
|
898
|
|
|
899 @item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen}
|
|
|
900
|
|
|
901 @item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell}
|
|
|
902
|
|
|
903 @item @email{dworkin@@ccs.neu.edu, Justin Sheehy}
|
|
|
904
|
|
|
905 @item @email{stig@@hackvan.com, Stig}
|
|
|
906
|
|
|
907 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari}
|
|
82
|
908 @end itemize
|
|
|
909
|
|
|
910 @node Q1.3.1, Q1.3.2, Q1.2.3, Introduction
|
|
274
|
911 @unnumberedsec 1.3: Internationalization
|
|
365
|
912 @unnumberedsubsec Q1.3.1: What is the status of internationalization support aka MULE (including Asian language support?
|
|
|
913
|
|
|
914 Both the stable and development versions of XEmacs include
|
|
|
915 internationalization support (aka MULE). MULE currently works on UNIX
|
|
|
916 and Linux systems; work for supporting MULE on Windows operating systems
|
|
|
917 is in progress. Binaries compiled without MULE support run faster than
|
|
|
918 MULE capable XEmacsen.
|
|
82
|
919
|
|
|
920 @node Q1.3.2, Q1.3.3, Q1.3.1, Introduction
|
|
365
|
921 @unnumberedsubsec Q1.3.2: How can I help with internationalization?
|
|
359
|
922
|
|
|
923 If you would like to help, you may want to join the
|
|
|
924 @email{xemacs-mule@@xemacs.org} mailing list. Especially needed are
|
|
|
925 people who speak/write languages other than English, who are willing to
|
|
|
926 use XEmacs/MULE regularly, and have some experience with Elisp.
|
|
207
|
927
|
|
|
928 @xref{Q1.1.2}.
|
|
82
|
929
|
|
|
930 @node Q1.3.3, Q1.3.4, Q1.3.2, Introduction
|
|
274
|
931 @unnumberedsubsec Q1.3.3: How do I type non-ASCII characters?
|
|
82
|
932
|
|
335
|
933 See question 3.5.7 (@pxref{Q3.5.7}) in part 3 of this FAQ.
|
|
82
|
934
|
|
|
935 @node Q1.3.4, Q1.3.5, Q1.3.3, Introduction
|
|
274
|
936 @unnumberedsubsec Q1.3.4: Can XEmacs messages come out in a different language?
|
|
82
|
937
|
|
|
938 The message-catalog support has mostly been written but doesn't
|
|
|
939 currently work. The first release of XEmacs 20 will @emph{not} support
|
|
365
|
940 it. However, menubar localization @emph{does} work. To
|
|
82
|
941 enable it, add to your @file{Emacs} file entries like this:
|
|
|
942
|
|
|
943 @example
|
|
365
|
944 Emacs*XlwMenu.resourceLabels: True
|
|
|
945 Emacs*XlwMenu.file.labelString: Fichier
|
|
363
|
946 Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster oeffnen
|
|
82
|
947 @end example
|
|
|
948
|
|
|
949 The name of the resource is derived from the non-localized entry by
|
|
272
|
950 removing punctuation and capitalizing as above.
|
|
82
|
951
|
|
|
952 @node Q1.3.5, Q1.3.6, Q1.3.4, Introduction
|
|
365
|
953 @unnumberedsubsec Q1.3.5: Please explain the various input methods in MULE/XEmacs
|
|
274
|
954
|
|
|
955 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
|
|
82
|
956
|
|
|
957 @quotation
|
|
282
|
958 Original Mule supports the following input methods: Wnn4, Wnn6, Canna, SJ3
|
|
82
|
959 and XIM. Interfaces for Wnn and SJ3 uses the @code{egg} user
|
|
|
960 interface. Interface for Canna does not use @samp{egg}. I don't know
|
|
|
961 about XIM. It is to support ATOK, of course, it may work for another
|
|
|
962 servers.
|
|
|
963
|
|
|
964 Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
|
|
|
965 university. It is a powerful and complex system. Wnn4 is free and Wnn6
|
|
|
966 is not free.
|
|
|
967
|
|
|
968 Canna supports only Japanese. It is made by NEC. It is a simple and
|
|
|
969 powerful system. Canna uses only grammar (Wnn uses grammar and
|
|
|
970 probability between words), so I think Wnn is cleverer than Canna,
|
|
|
971 however Canna users made a good grammar and dictionary. So for standard
|
|
|
972 modern Japanese, Canna seems cleverer than Wnn4. In addition, the UNIX
|
|
|
973 version of Canna is free (now there is a Microsoft Windows version).
|
|
|
974
|
|
|
975 SJ3 supports only Japanese. It is made by Sony. XIM supports was made
|
|
|
976 to use ATOK (a major input method in personal computer world). XIM is
|
|
|
977 the standard for accessing input methods bundled in Japanese versions of
|
|
|
978 Solaris. (XEmacs 20 will support XIM input).
|
|
|
979
|
|
|
980 Egg consists of following parts:
|
|
|
981
|
|
|
982 @enumerate
|
|
290
|
983 @item
|
|
|
984 Input character Translation System (ITS) layer.
|
|
82
|
985 It translates ASCII inputs to Kana/PinYin/Hangul characters.
|
|
|
986
|
|
290
|
987 @item
|
|
|
988 Kana/PinYin/Hangul to Kanji transfer layer.
|
|
126
|
989 It is interface layer for network Kana-Kanji server (Wnn and Sj3).
|
|
82
|
990 @end enumerate
|
|
|
991
|
|
|
992 These input methods are modal, namely there are mode, alphabet mode and
|
|
|
993 Kana-Kanji transfer mode. However there are mode-less input methods for
|
|
|
994 Egg and Canna. @samp{Boiled-egg} is a mode-less input method running on
|
|
|
995 Egg. For Canna, @samp{canna.el} has a tiny boiled-egg like command,
|
|
|
996 @code{(canna-boil)}, and there are some boiled-egg like utilities. In
|
|
|
997 addition, it was planned to make an abstraction for all transfer type
|
|
|
998 input methods. However authors of input methods are busy, so maybe this
|
|
|
999 plan is stopped. Perhaps after Mule merged GNU Emacs will be released,
|
|
|
1000 it will be continued.
|
|
|
1001 @end quotation
|
|
|
1002
|
|
|
1003 @node Q1.3.6, Q1.3.7, Q1.3.5, Introduction
|
|
365
|
1004 @unnumberedsubsec Q1.3.6: How do I portably code for MULE/XEmacs?
|
|
274
|
1005
|
|
|
1006 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes:
|
|
82
|
1007
|
|
|
1008 @quotation
|
|
|
1009 MULE and XEmacs are quite different. So the application
|
|
|
1010 implementor must write separate code for these mule variants.
|
|
|
1011
|
|
|
1012 MULE and the next version of Emacs are similar but the symbols are very
|
|
|
1013 different---requiring separate code as well.
|
|
|
1014
|
|
|
1015 Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of
|
|
|
1016 emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called
|
|
|
1017 @code{emu} to provide a common interface.
|
|
|
1018
|
|
|
1019 I have the following suggestions about dealing with mule variants:
|
|
|
1020
|
|
|
1021 @itemize @bullet
|
|
|
1022 @item
|
|
|
1023 @code{(featurep 'mule)} @code{t} on all mule variants
|
|
|
1024
|
|
|
1025 @item
|
|
|
1026 @code{(boundp 'MULE)} is @code{t} on only MULE. Maybe the next version
|
|
|
1027 of Emacs will not have this symbol.
|
|
|
1028
|
|
|
1029 @item
|
|
|
1030 MULE has a variable @code{mule-version}. Perhaps the next version of
|
|
|
1031 Emacs will have this variable as well.
|
|
|
1032 @end itemize
|
|
|
1033
|
|
|
1034 Following is a sample to distinguish mule variants:
|
|
|
1035
|
|
|
1036 @lisp
|
|
|
1037 (if (featurep 'mule)
|
|
|
1038 (cond ((boundp 'MULE)
|
|
|
1039 ;; for original Mule
|
|
|
1040 )
|
|
365
|
1041 ((string-match "XEmacs" emacs-version)
|
|
|
1042 ;; for XEmacs with Mule
|
|
|
1043 )
|
|
|
1044 (t
|
|
|
1045 ;; for next version of Emacs
|
|
|
1046 ))
|
|
82
|
1047 ;; for old emacs variants
|
|
|
1048 )
|
|
|
1049 @end lisp
|
|
|
1050 @end quotation
|
|
|
1051
|
|
|
1052 @node Q1.3.7, Q1.4.1, Q1.3.6, Introduction
|
|
274
|
1053 @unnumberedsubsec Q1.3.7: How about Cyrillic Modes?
|
|
|
1054
|
|
|
1055 @email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes:
|
|
82
|
1056
|
|
|
1057 @quotation
|
|
|
1058 There is a cyrillic mode in the file @file{mysetup.zip} in
|
|
274
|
1059 @iftex
|
|
|
1060 @*
|
|
282
|
1061 @end iftex
|
|
274
|
1062 @uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}. This is a
|
|
|
1063 modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el}
|
|
282
|
1064 which can be obtained from
|
|
82
|
1065 @end quotation
|
|
|
1066
|
|
282
|
1067 @uref{http://ftpsearch.ntnu.no/?query=russian.el.Z}.
|
|
|
1068 @c dead link above
|
|
|
1069
|
|
274
|
1070 @email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes:
|
|
82
|
1071
|
|
|
1072 @quotation
|
|
274
|
1073 There is another cyrillic mode for both GNU Emacs and XEmacs by
|
|
|
1074 @email{manin@@camelot.mssm.edu, Dmitrii
|
|
282
|
1075 (Mitya) Manin} at
|
|
274
|
1076 @iftex
|
|
|
1077
|
|
282
|
1078 @end iftex
|
|
|
1079 @uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}.
|
|
|
1080 @c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead.
|
|
|
1081 @c Changed to russian host instead
|
|
82
|
1082 @end quotation
|
|
|
1083
|
|
274
|
1084 @email{rebecca.ore@@op.net, Rebecca Ore} writes:
|
|
203
|
1085
|
|
|
1086 @quotation
|
|
|
1087 The fullest resource I found on Russian language use (in and out of
|
|
274
|
1088 XEmacs) is @uref{http://sunsite.oit.unc.edu/sergei/Software/Software.html}
|
|
203
|
1089 @end quotation
|
|
|
1090
|
|
82
|
1091 @node Q1.4.1, Q1.4.2, Q1.3.7, Introduction
|
|
274
|
1092 @unnumberedsec 1.4: Getting Started, Backing up & Recovery
|
|
|
1093 @unnumberedsubsec Q1.4.1: What is a @file{.emacs} and is there a sample one?
|
|
82
|
1094
|
|
|
1095 The @file{.emacs} file is used to customize XEmacs to your tastes. No
|
|
|
1096 two are alike, nor are they expected to be alike, but that's the point.
|
|
|
1097 The XEmacs distribution contains an excellent starter example in the etc
|
|
|
1098 directory called @file{sample.emacs}. Copy this file from there to your
|
|
|
1099 home directory and rename it @file{.emacs}. Then edit it to suit.
|
|
|
1100
|
|
|
1101 Starting with 19.14, you may bring the @file{sample.emacs} into an
|
|
|
1102 XEmacs buffer by selecting @samp{Help->Sample .emacs} from the menubar.
|
|
|
1103 To determine the location of the @file{etc} directory type the command
|
|
282
|
1104 @kbd{C-h v data-directory @key{RET}}.
|
|
82
|
1105
|
|
|
1106 @node Q1.4.2, Q1.4.3, Q1.4.1, Introduction
|
|
274
|
1107 @unnumberedsubsec Q1.4.2: Can I use the same @file{.emacs} with the other Emacs?
|
|
82
|
1108
|
|
|
1109 Yes. The sample @file{.emacs} included in the XEmacs distribution will
|
|
|
1110 show you how to handle different versions and flavors of Emacs.
|
|
|
1111
|
|
|
1112 @node Q1.4.3, Q1.4.4, Q1.4.2, Introduction
|
|
274
|
1113 @unnumberedsubsec Q1.4.3: Any good tutorials around?
|
|
82
|
1114
|
|
359
|
1115 There's the XEmacs tutorial available from the Help Menu under
|
|
|
1116 @samp{Basics->Tutorials}, or by typing @kbd{C-h t}. To check whether
|
|
|
1117 it's available in a non-english language, type @kbd{C-u C-h t TAB}, type
|
|
|
1118 the first letters of your preferred language, then type @key{RET}.
|
|
|
1119
|
|
|
1120 @comment There's an Emacs Lisp tutorial at
|
|
365
|
1121 @comment
|
|
359
|
1122 @comment @example
|
|
|
1123 @comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}.
|
|
|
1124 @comment @end example
|
|
365
|
1125 @comment
|
|
359
|
1126 @comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web
|
|
|
1127 @comment page at
|
|
|
1128 @comment @iftex
|
|
|
1129 @comment @*
|
|
|
1130 @comment @end iftex
|
|
|
1131 @comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}.
|
|
82
|
1132
|
|
|
1133 @node Q1.4.4, Q1.4.5, Q1.4.3, Introduction
|
|
274
|
1134 @unnumberedsubsec Q1.4.4: May I see an example of a useful XEmacs Lisp function?
|
|
82
|
1135
|
|
|
1136 The following function does a little bit of everything useful. It does
|
|
|
1137 something with the prefix argument, it examines the text around the
|
|
|
1138 cursor, and it's interactive so it may be bound to a key. It inserts
|
|
|
1139 copies of the current word the cursor is sitting on at the cursor. If
|
|
|
1140 you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will
|
|
|
1141 insert 3 copies.
|
|
|
1142
|
|
|
1143 @lisp
|
|
|
1144 (defun double-word (count)
|
|
|
1145 "Insert a copy of the current word underneath the cursor"
|
|
|
1146 (interactive "*p")
|
|
|
1147 (let (here there string)
|
|
|
1148 (save-excursion
|
|
|
1149 (forward-word -1)
|
|
|
1150 (setq here (point))
|
|
|
1151 (forward-word 1)
|
|
|
1152 (setq there (point))
|
|
|
1153 (setq string (buffer-substring here there)))
|
|
|
1154 (while (>= count 1)
|
|
163
|
1155 (insert string)
|
|
|
1156 (decf count))))
|
|
82
|
1157 @end lisp
|
|
|
1158
|
|
|
1159 The best way to see what is going on here is to let XEmacs tell you.
|
|
|
1160 Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor
|
|
|
1161 sitting just to the right of the function you want explained. Eg. move
|
|
|
1162 the cursor to the SPACE between @code{interactive} and @samp{"*p"} and
|
|
|
1163 hit @kbd{C-h f} to see what the function @code{interactive} does. Doing
|
|
|
1164 this will tell you that the @code{*} requires a writable buffer, and
|
|
|
1165 @code{p} converts the prefix argument to a number, and
|
|
|
1166 @code{interactive} allows you to execute the command with @kbd{M-x}.
|
|
|
1167
|
|
|
1168 @node Q1.4.5, Q1.4.6, Q1.4.4, Introduction
|
|
274
|
1169 @unnumberedsubsec Q1.4.5: And how do I bind it to a key?
|
|
82
|
1170
|
|
|
1171 To bind to a key do:
|
|
|
1172
|
|
|
1173 @lisp
|
|
|
1174 (global-set-key "\C-cd" 'double-word)
|
|
|
1175 @end lisp
|
|
|
1176
|
|
|
1177 Or interactively, @kbd{M-x global-set-key} and follow the prompts.
|
|
|
1178
|
|
365
|
1179 @node Q1.4.6, , Q1.4.5, Introduction
|
|
274
|
1180 @unnumberedsubsec Q1.4.6: What's the difference between a macro and a function?
|
|
82
|
1181
|
|
163
|
1182 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual:
|
|
82
|
1183
|
|
|
1184 @dfn{Macros} enable you to define new control constructs and other
|
|
|
1185 language features. A macro is defined much like a function, but instead
|
|
|
1186 of telling how to compute a value, it tells how to compute another Lisp
|
|
|
1187 expression which will in turn compute the value. We call this
|
|
|
1188 expression the @dfn{expansion} of the macro.
|
|
|
1189
|
|
|
1190 Macros can do this because they operate on the unevaluated expressions
|
|
|
1191 for the arguments, not on the argument values as functions do. They can
|
|
|
1192 therefore construct an expansion containing these argument expressions
|
|
|
1193 or parts of them.
|
|
|
1194
|
|
163
|
1195 Do not confuse the two terms with @dfn{keyboard macros}, which are
|
|
|
1196 another matter, entirely. A keyboard macro is a key bound to several
|
|
|
1197 other keys. Refer to manual for details.
|
|
|
1198
|
|
82
|
1199 @node Installation, Customization, Introduction, Top
|
|
274
|
1200 @unnumbered 2 Installation and Trouble Shooting
|
|
82
|
1201
|
|
|
1202 This is part 2 of the XEmacs Frequently Asked Questions list. This
|
|
|
1203 section is devoted to Installation, Maintenance and Trouble Shooting.
|
|
|
1204
|
|
|
1205 @menu
|
|
|
1206 Installation:
|
|
282
|
1207 * Q2.0.1:: Running XEmacs without installing.
|
|
|
1208 * Q2.0.2:: XEmacs is too big.
|
|
82
|
1209 * Q2.0.3:: Compiling XEmacs with Netaudio.
|
|
163
|
1210 * Q2.0.4:: Problems with Linux and ncurses.
|
|
82
|
1211 * Q2.0.5:: Do I need X11 to run XEmacs?
|
|
|
1212 * Q2.0.6:: I'm having strange crashes. What do I do?
|
|
|
1213 * Q2.0.7:: Libraries in non-standard locations.
|
|
|
1214 * Q2.0.8:: can't resolve symbol _h_errno
|
|
282
|
1215 * Q2.0.9:: Where do I find external libraries?
|
|
82
|
1216 * Q2.0.10:: After I run configure I find a coredump, is something wrong?
|
|
|
1217 * Q2.0.11:: XEmacs can't resolve host names.
|
|
282
|
1218 * Q2.0.12:: Why can't I strip XEmacs?
|
|
367
|
1219 * Q2.0.13:: I don't need no steenkin' packages. Do I? (NEW)
|
|
|
1220 * Q2.0.14:: I don't want to install a million .els one at a time! (NEW)
|
|
82
|
1221
|
|
|
1222 Trouble Shooting:
|
|
|
1223 * Q2.1.1:: XEmacs just crashed on me!
|
|
|
1224 * Q2.1.2:: Cryptic Minibuffer messages.
|
|
163
|
1225 * Q2.1.3:: Translation Table Syntax messages at Startup.
|
|
82
|
1226 * Q2.1.4:: Startup warnings about deducing proper fonts?
|
|
|
1227 * Q2.1.5:: XEmacs cannot connect to my X Terminal.
|
|
|
1228 * Q2.1.6:: XEmacs just locked up my Linux X server.
|
|
|
1229 * Q2.1.7:: HP Alt key as Meta.
|
|
|
1230 * Q2.1.8:: got (wrong-type-argument color-instance-p nil)!
|
|
|
1231 * Q2.1.9:: XEmacs causes my OpenWindows 3.0 server to crash.
|
|
|
1232 * Q2.1.10:: Warnings from incorrect key modifiers.
|
|
282
|
1233 * Q2.1.11:: Can't instantiate image error... in toolbar
|
|
82
|
1234 * Q2.1.12:: Regular Expression Problems on DEC OSF1.
|
|
|
1235 * Q2.1.13:: HP/UX 10.10 and @code{create_process} failure
|
|
|
1236 * Q2.1.14:: @kbd{C-g} doesn't work for me. Is it broken?
|
|
|
1237 * Q2.1.15:: How to debug an XEmacs problem with a debugger.
|
|
|
1238 * Q2.1.16:: XEmacs crashes in @code{strcat} on HP/UX 10.
|
|
|
1239 * Q2.1.17:: @samp{Marker does not point anywhere}.
|
|
365
|
1240 * Q2.1.18:: [This question intentionally left blank]
|
|
82
|
1241 * Q2.1.19:: XEmacs does not follow the local timezone.
|
|
|
1242 * Q2.1.20:: @samp{Symbol's function definition is void: hkey-help-show.}
|
|
365
|
1243 * Q2.1.21:: [This question intentionally left blank]
|
|
116
|
1244 * Q2.1.22:: XEmacs seems to take a really long time to do some things.
|
|
163
|
1245 * Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
|
|
365
|
1246 * Q2.1.24:: XEmacs won't start without network. (NEW)
|
|
367
|
1247 * Q2.1.25:: After upgrading, XEmacs won't do `foo' any more! (NEW)
|
|
82
|
1248 @end menu
|
|
|
1249
|
|
|
1250 @node Q2.0.1, Q2.0.2, Installation, Installation
|
|
274
|
1251 @unnumberedsec 2.0: Installation
|
|
|
1252 @unnumberedsubsec Q2.0.1: Running XEmacs without installing
|
|
365
|
1253
|
|
|
1254 How can I just try XEmacs without installing it?
|
|
82
|
1255
|
|
|
1256 XEmacs will run in place without requiring installation and copying of
|
|
|
1257 the Lisp directories, and without having to specify a special build-time
|
|
|
1258 flag. It's the copying of the Lisp directories that requires so much
|
|
|
1259 space. XEmacs is largely written in Lisp.
|
|
|
1260
|
|
|
1261 A good method is to make a shell alias for xemacs:
|
|
|
1262
|
|
|
1263 @example
|
|
163
|
1264 alias xemacs=/i/xemacs-20.2/src/xemacs
|
|
82
|
1265 @end example
|
|
|
1266
|
|
|
1267 (You will obviously use whatever directory you downloaded the source
|
|
163
|
1268 tree to instead of @file{/i/xemacs-20.2}).
|
|
82
|
1269
|
|
|
1270 This will let you run XEmacs without massive copying.
|
|
|
1271
|
|
|
1272 @node Q2.0.2, Q2.0.3, Q2.0.1, Installation
|
|
274
|
1273 @unnumberedsubsec Q2.0.2: XEmacs is too big
|
|
82
|
1274
|
|
365
|
1275 The space required by the installation directories can be
|
|
175
|
1276 reduced dramatically if desired. Gzip all the .el files. Remove all
|
|
365
|
1277 the packages you'll never want to use. Remove the TexInfo manuals.
|
|
175
|
1278 Remove the Info (and use just hardcopy versions of the manual). Remove
|
|
|
1279 most of the stuff in etc. Remove or gzip all the source code. Gzip or
|
|
|
1280 remove the C source code. Configure it so that copies are not made of
|
|
365
|
1281 the support lisp.
|
|
175
|
1282
|
|
|
1283 These are all Emacs Lisp source code and bytecompiled object code. You
|
|
|
1284 may safely gzip everything named *.el here. You may remove any package
|
|
|
1285 you don't use. @emph{Nothing bad will happen if you delete a package
|
|
|
1286 that you do not use}. You must be sure you do not use it though, so be
|
|
|
1287 conservative at first.
|
|
|
1288
|
|
365
|
1289 Possible candidates for deletion include w3, games, hyperbole, mh-e,
|
|
|
1290 hm-html-menus, vm, viper, oobr, gnus, etc. Ask yourself, @emph{Do I
|
|
|
1291 ever want to use this package?} If the answer is no, then it is a
|
|
|
1292 candidate for removal.
|
|
175
|
1293
|
|
|
1294 First, gzip all the .el files. Then go about package by package and
|
|
|
1295 start gzipping the .elc files. Then run XEmacs and do whatever it is
|
|
|
1296 you normally do. If nothing bad happens, then delete the directory. Be
|
|
|
1297 conservative about deleting directories, and it would be handy to have a
|
|
365
|
1298 backup around in case you get too zealous.
|
|
175
|
1299
|
|
|
1300 @file{prim}, @file{modes}, @file{packages}, and @file{utils} are four
|
|
|
1301 directories you definitely do @strong{not} want to delete, although
|
|
|
1302 certain packages can be removed from them if you do not use them.
|
|
|
1303
|
|
365
|
1304 Online texinfo sources in the @file{info} can either be compressed them
|
|
|
1305 or remove them. In either case, @kbd{C-h i} (info mode) will no longer
|
|
|
1306 work.
|
|
82
|
1307
|
|
|
1308 @node Q2.0.3, Q2.0.4, Q2.0.2, Installation
|
|
274
|
1309 @unnumberedsubsec Q2.0.3: Compiling XEmacs with Netaudio.
|
|
82
|
1310
|
|
|
1311 What is the best way to compile XEmacs with the netaudio system, since I
|
|
|
1312 have got the netaudio system compiled but installed at a weird place, I
|
|
|
1313 am not root. Also in the READMEs it does not say anything about
|
|
|
1314 compiling with the audioserver?
|
|
|
1315
|
|
|
1316 You should only need to add some stuff to the configure command line.
|
|
|
1317 To tell it to compile in netaudio support: @samp{--with-sound=both}, or
|
|
|
1318 @samp{--with-sound=nas} if you don't want native sound support for some
|
|
|
1319 reason.) To tell it where to find the netaudio includes and libraries:
|
|
16
|
1320
|
|
|
1321 @example
|
|
82
|
1322 --site-libraries=WHATEVER
|
|
|
1323 --site-includes=WHATEVER
|
|
|
1324 @end example
|
|
|
1325
|
|
|
1326 Then (fingers crossed) it should compile and it will use netaudio if you
|
|
|
1327 have a server running corresponding to the X server. The netaudio server
|
|
|
1328 has to be there when XEmacs starts. If the netaudio server goes away and
|
|
|
1329 another is run, XEmacs should cope (fingers crossed, error handling in
|
|
|
1330 netaudio isn't perfect).
|
|
|
1331
|
|
|
1332 BTW, netaudio has been renamed as it has a name clash with something
|
|
|
1333 else, so if you see references to NAS or Network Audio System, it's the
|
|
|
1334 same thing. It also might be found at
|
|
274
|
1335 @uref{ftp://ftp.x.org/contrib/audio/nas/}.
|
|
82
|
1336
|
|
|
1337 @node Q2.0.4, Q2.0.5, Q2.0.3, Installation
|
|
274
|
1338 @unnumberedsubsec Q2.0.4: Problems with Linux and ncurses.
|
|
82
|
1339
|
|
|
1340 On Linux 1.3.98 with termcap 2.0.8 and the ncurses that came with libc
|
|
126
|
1341 5.2.18, XEmacs 20.0b20 is unable to open a tty device:
|
|
82
|
1342
|
|
|
1343 @example
|
|
|
1344 src/xemacs -nw -q
|
|
282
|
1345 Initialization error:
|
|
|
1346 @iftex
|
|
274
|
1347 @*
|
|
282
|
1348 @end iftex
|
|
274
|
1349 Terminal type `xterm' undefined (or can't access database?)
|
|
82
|
1350 @end example
|
|
|
1351
|
|
359
|
1352 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
82
|
1353
|
|
|
1354 @quotation
|
|
|
1355 Your ncurses configuration is messed up. Your /usr/lib/terminfo is a
|
|
|
1356 bad pointer, perhaps to a CD-ROM that is not inserted.
|
|
|
1357 @end quotation
|
|
|
1358
|
|
|
1359 @node Q2.0.5, Q2.0.6, Q2.0.4, Installation
|
|
274
|
1360 @unnumberedsubsec Q2.0.5: Do I need X11 to run XEmacs?
|
|
82
|
1361
|
|
|
1362 No. The name @dfn{XEmacs} is unfortunate in the sense that it is
|
|
365
|
1363 @strong{not} an X Window System-only version of Emacs. XEmacs has
|
|
|
1364 full color support on a color-capable character terminal.
|
|
82
|
1365
|
|
|
1366 @node Q2.0.6, Q2.0.7, Q2.0.5, Installation
|
|
274
|
1367 @unnumberedsubsec Q2.0.6: I'm having strange crashes. What do I do?
|
|
82
|
1368
|
|
|
1369 There have been a variety of reports of crashes due to compilers with
|
|
|
1370 buggy optimizers. Please see the @file{PROBLEMS} file that comes with
|
|
|
1371 XEmacs to read what it says about your platform.
|
|
|
1372
|
|
|
1373 @node Q2.0.7, Q2.0.8, Q2.0.6, Installation
|
|
274
|
1374 @unnumberedsubsec Q2.0.7: Libraries in non-standard locations
|
|
82
|
1375
|
|
|
1376 I have x-faces, jpeg, xpm etc. all in different places. I've tried
|
|
|
1377 space-separated, comma-separated, several --site-libraries, all to no
|
|
|
1378 avail.
|
|
|
1379
|
|
|
1380 @example
|
|
|
1381 --site-libraries='/path/one /path/two /path/etc'
|
|
|
1382 @end example
|
|
|
1383
|
|
|
1384 @node Q2.0.8, Q2.0.9, Q2.0.7, Installation
|
|
274
|
1385 @unnumberedsubsec Q2.0.8: can't resolve symbol _h_errno
|
|
82
|
1386
|
|
|
1387 You are using the Linux/ELF distribution of XEmacs 19.14, and your ELF
|
|
|
1388 libraries are out of date. You have the following options:
|
|
|
1389
|
|
|
1390 @enumerate
|
|
|
1391 @item
|
|
|
1392 Upgrade your libc to at least 5.2.16 (better is 5.2.18, 5.3.12, or
|
|
|
1393 5.4.10).
|
|
|
1394
|
|
|
1395 @item
|
|
|
1396 Patch the XEmacs binary by replacing all occurrences of
|
|
282
|
1397 @samp{_h_errno^@@} with
|
|
|
1398 @iftex
|
|
274
|
1399 @*
|
|
282
|
1400 @end iftex
|
|
274
|
1401 @samp{h_errno^@@^@@}. Any version of Emacs will
|
|
82
|
1402 suffice. If you don't understand how to do this, don't do it.
|
|
|
1403
|
|
|
1404 @item
|
|
365
|
1405 Rebuild XEmacs yourself---any working ELF version of libc should be
|
|
82
|
1406 O.K.
|
|
|
1407 @end enumerate
|
|
|
1408
|
|
359
|
1409 @email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
|
|
82
|
1410
|
|
|
1411 @quotation
|
|
|
1412 Why not use a Perl one-liner for No. 2?
|
|
|
1413
|
|
|
1414 @example
|
|
274
|
1415 perl -pi -e 's/_h_errno\0/h_errno\0\0/g' \
|
|
|
1416 /usr/local/bin/xemacs-19.14
|
|
82
|
1417 @end example
|
|
|
1418
|
|
|
1419 NB: You @emph{must} patch @file{/usr/local/bin/xemacs-19.14}, and not
|
|
|
1420 @file{xemacs} because @file{xemacs} is a link to @file{xemacs-19.14};
|
|
|
1421 the Perl @samp{-i} option will cause unwanted side-effects if applied to
|
|
|
1422 a symbolic link.
|
|
|
1423 @end quotation
|
|
|
1424
|
|
274
|
1425 @email{steve@@xemacs.org, SL Baur} writes:
|
|
116
|
1426
|
|
|
1427 @quotation
|
|
|
1428 If you build against a recent libc-5.4 (late enough to have caused
|
|
|
1429 problems earlier in the beta cycle) and then run with an earlier version
|
|
|
1430 of libc, you get a
|
|
|
1431
|
|
|
1432 @example
|
|
|
1433 $ xemacs
|
|
|
1434 xemacs: can't resolve symbol '__malloc_hook'
|
|
|
1435 zsh: 7942 segmentation fault (core dumped) xemacs
|
|
|
1436 @end example
|
|
|
1437
|
|
|
1438 (Example binary compiled against libc-5.4.23 and run with libc-5.4.16).
|
|
|
1439
|
|
|
1440 The solution is to upgrade to at least libc-5.4.23. Sigh. Drat.
|
|
|
1441 @end quotation
|
|
|
1442
|
|
82
|
1443 @node Q2.0.9, Q2.0.10, Q2.0.8, Installation
|
|
274
|
1444 @unnumberedsubsec Q2.0.9: Where do I find external libraries?
|
|
82
|
1445
|
|
|
1446 All external libraries used by XEmacs can be found at the XEmacs FTP
|
|
282
|
1447 site
|
|
274
|
1448 @iftex
|
|
|
1449 @*
|
|
282
|
1450 @end iftex
|
|
|
1451 @uref{ftp://ftp.xemacs.org/pub/xemacs/aux/}.
|
|
|
1452
|
|
|
1453 @c Changed June Link above, <URL:ftp://ftp.xemacs.org/pub/aux/> was dead.
|
|
207
|
1454 @c This list is a pain in the you-know-what to keep in synch with the
|
|
|
1455 @c world.
|
|
163
|
1456 The canonical locations (at the time of this writing) are as follows:
|
|
82
|
1457
|
|
|
1458 @table @asis
|
|
|
1459 @item JPEG
|
|
274
|
1460 @uref{ftp://ftp.uu.net/graphics/jpeg/}. Version 6a is current.
|
|
282
|
1461 @c Check from host with legal IP address
|
|
82
|
1462 @item XPM
|
|
274
|
1463 @uref{ftp://ftp.x.org/contrib/libraries/}. Version 3.4j is current.
|
|
82
|
1464 Older versions of this package are known to cause XEmacs crashes.
|
|
|
1465
|
|
|
1466 @item TIFF
|
|
274
|
1467 @uref{ftp://ftp.sgi.com/graphics/tiff/}. v3.4 is current. The latest
|
|
82
|
1468 beta is v3.4b035. There is a HOWTO here.
|
|
|
1469
|
|
|
1470 @item PNG
|
|
274
|
1471 @uref{ftp://ftp.uu.net/graphics/png/}. 0.89c is current. XEmacs
|
|
82
|
1472 requires a fairly recent version to avoid using temporary files.
|
|
282
|
1473 @c Check from host with legal IP address
|
|
82
|
1474
|
|
274
|
1475 @uref{ftp://swrinde.nde.swri.edu/pub/png/src/}
|
|
82
|
1476
|
|
|
1477 @item Compface
|
|
274
|
1478 @uref{ftp://ftp.cs.indiana.edu/pub/faces/compface/}. This library has
|
|
82
|
1479 been frozen for about 6 years, and is distributed without version
|
|
|
1480 numbers. @emph{It should be compiled with the same options that X11 was
|
|
|
1481 compiled with on your system}. The version of this library at
|
|
|
1482 XEmacs.org includes the @file{xbm2xface.pl} script, written by
|
|
274
|
1483 @email{stig@@hackvan.com}, which may be useful when generating your own xface.
|
|
82
|
1484
|
|
|
1485 @item NAS
|
|
274
|
1486 @uref{ftp://ftp.x.org/contrib/audio/nas/}.
|
|
82
|
1487 Version 1.2p5 is current. There is a FAQ here.
|
|
|
1488 @end table
|
|
|
1489
|
|
|
1490 @node Q2.0.10, Q2.0.11, Q2.0.9, Installation
|
|
274
|
1491 @unnumberedsubsec Q2.0.10: After I run configure I find a core dump, is something wrong?
|
|
82
|
1492
|
|
|
1493 Not necessarily. If you have GNU sed 3.0 you should downgrade it to
|
|
|
1494 2.05. From the @file{README} at prep.ai.mit.edu:
|
|
|
1495
|
|
|
1496 @quotation
|
|
|
1497 sed 3.0 has been withdrawn from distribution. It has major revisions,
|
|
|
1498 which mostly seem to be improvements; but it turns out to have bugs too
|
|
|
1499 which cause trouble in some common cases.
|
|
|
1500
|
|
|
1501 Tom Lord won't be able to work fixing the bugs until May. So in the
|
|
|
1502 mean time, we've decided to withdraw sed 3.0 from distribution and make
|
|
|
1503 version 2.05 once again the recommended version.
|
|
|
1504 @end quotation
|
|
|
1505
|
|
|
1506 It has also been observed that the vfork test on Solaris will leave a
|
|
126
|
1507 core dump.
|
|
82
|
1508
|
|
|
1509 @node Q2.0.11, Q2.0.12, Q2.0.10, Installation
|
|
274
|
1510 @unnumberedsubsec Q2.0.11: XEmacs doesn't resolve hostnames.
|
|
82
|
1511
|
|
|
1512 This is the result of a long-standing problem with SunOS and the fact
|
|
|
1513 that stock SunOS systems do not ship with DNS resolver code in libc.
|
|
|
1514
|
|
274
|
1515 @email{ckd@@loiosh.kei.com, Christopher Davis} writes:
|
|
82
|
1516
|
|
|
1517 @quotation
|
|
|
1518 That's correct [The SunOS 4.1.3 precompiled binaries don't do name
|
|
|
1519 lookup]. Since Sun figured that everyone used NIS to do name lookups
|
|
|
1520 (that DNS thing was apparently only a passing fad, right?), the stock
|
|
|
1521 SunOS 4.x systems don't have DNS-based name lookups in libc.
|
|
|
1522
|
|
|
1523 This is also why Netscape ships two binaries for SunOS 4.1.x.
|
|
|
1524
|
|
|
1525 The best solution is to compile it yourself; the configure script will
|
|
|
1526 check to see if you've put DNS in the shared libc and will then proceed
|
|
|
1527 to link against the DNS resolver library code.
|
|
|
1528 @end quotation
|
|
|
1529
|
|
367
|
1530 @node Q2.0.12, Q2.0.13, Q2.0.11, Installation
|
|
274
|
1531 @unnumberedsubsec Q2.0.12: Why can't I strip XEmacs?
|
|
|
1532
|
|
|
1533 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes:
|
|
82
|
1534
|
|
|
1535 @quotation
|
|
|
1536 Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The
|
|
|
1537 link gives you a bare-boned emacs (called temacs). temacs is then run,
|
|
|
1538 preloading some of the lisp files. The result is then dumped into a new
|
|
|
1539 executable, named xemacs, which will contain all of the preloaded lisp
|
|
|
1540 functions and data.
|
|
|
1541
|
|
|
1542 Now, during the dump itself, the executable (code+data+symbols) is
|
|
|
1543 written on disk using a special unexec() function. This function is
|
|
|
1544 obviously heavily system dependent. And on some systems, it leads to an
|
|
|
1545 executable which, although valid, cannot be stripped without damage. If
|
|
|
1546 memory serves, this is especially the case for AIX binaries. On other
|
|
|
1547 architecture it might work OK.
|
|
|
1548
|
|
|
1549 The Right Way to strip the emacs binary is to strip temacs prior to
|
|
|
1550 dumping xemacs. This will always work, although you can do that only if
|
|
|
1551 you install from sources (as temacs is @file{not} part of the binary
|
|
|
1552 kits).
|
|
|
1553 @end quotation
|
|
|
1554
|
|
274
|
1555 @email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes:
|
|
82
|
1556
|
|
|
1557 @quotation
|
|
|
1558 Here is the trick:
|
|
|
1559
|
|
|
1560 @enumerate
|
|
|
1561 @item
|
|
163
|
1562 [ ./configure; make ]
|
|
82
|
1563
|
|
|
1564 @item
|
|
163
|
1565 rm src/xemacs
|
|
82
|
1566
|
|
|
1567 @item
|
|
163
|
1568 strip src/temacs
|
|
82
|
1569
|
|
|
1570 @item
|
|
|
1571 make
|
|
|
1572
|
|
|
1573 @item
|
|
|
1574 cp src/xemacs /usr/local/bin/xemacs
|
|
|
1575
|
|
|
1576 @item
|
|
282
|
1577 cp lib-src/DOC-19.16-XEmacs
|
|
274
|
1578 @iftex
|
|
|
1579 \ @*
|
|
282
|
1580 @end iftex
|
|
274
|
1581 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout
|
|
82
|
1582 @end enumerate
|
|
|
1583 @end quotation
|
|
|
1584
|
|
367
|
1585 @node Q2.0.13, Q2.0.14, Q2.0.12, Installation
|
|
|
1586 @unnumberedsubsec Q2.0.13: I don't need no steenkin' packages. Do I? (NEW)
|
|
|
1587
|
|
|
1588 Strictly speaking, no. XEmacs will build and install just fine without
|
|
|
1589 any packages installed. However, only the most basic editing functions
|
|
|
1590 will be available with no packages installed, so installing packages is
|
|
|
1591 an essential part of making your installed XEmacs _useful_.
|
|
|
1592
|
|
|
1593 @node Q2.0.14, Q2.1.1, Q2.0.13, Installation
|
|
|
1594 @unnumberedsubsec Q2.0.12: How do I figure out which packages to install? (NEW)
|
|
|
1595
|
|
|
1596 Many people really liked the old way that packages were bundled and do
|
|
|
1597 not want to mess with packages at all. You can grab all the packages at
|
|
|
1598 once like you used to with old XEmacs versions. Download the file
|
|
|
1599
|
|
|
1600 @file{xemacs-sumo.tar.gz}
|
|
|
1601
|
|
|
1602 For an XEmacs compiled with Mule you also need
|
|
|
1603
|
|
|
1604 @file{xemacs-mule-sumo.tar.gz}
|
|
|
1605
|
|
|
1606 N.B. They are called 'Sumo Tarballs' for good reason. They are
|
|
|
1607 currently about 15MB and 2.3MB (gzipped) respectively.
|
|
|
1608
|
|
|
1609 Install them by
|
|
|
1610
|
|
|
1611 @code{cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xf -}
|
|
|
1612
|
|
|
1613 As the Sumo tarballs are not regenerated as often as the individual
|
|
|
1614 packages, it is recommended that you use the automatic package tools
|
|
|
1615 afterwards to pick up any recent updates.
|
|
|
1616
|
|
|
1617 @node Q2.1.1, Q2.1.2, Q2.0.14, Installation
|
|
274
|
1618 @unnumberedsec 2.1: Trouble Shooting
|
|
|
1619 @unnumberedsubsec Q2.1.1: Help! XEmacs just crashed on me!
|
|
82
|
1620
|
|
|
1621 First of all, don't panic. Whenever XEmacs crashes, it tries extremely
|
|
163
|
1622 hard to auto-save all of your files before dying. (The main time that
|
|
82
|
1623 this will not happen is if the machine physically lost power or if you
|
|
163
|
1624 killed the XEmacs process using @code{kill -9}). The next time you try
|
|
82
|
1625 to edit those files, you will be informed that a more recent auto-save
|
|
|
1626 file exists. You can use @kbd{M-x recover-file} to retrieve the
|
|
|
1627 auto-saved version of the file.
|
|
|
1628
|
|
|
1629 Starting with 19.14, you may use the command @kbd{M-x recover-session}
|
|
|
1630 after a crash to pick up where you left off.
|
|
|
1631
|
|
|
1632 Now, XEmacs is not perfect, and there may occasionally be times, or
|
|
|
1633 particular sequences of actions, that cause it to crash. If you can
|
|
|
1634 come up with a reproducible way of doing this (or even if you have a
|
|
|
1635 pretty good memory of exactly what you were doing at the time), the
|
|
|
1636 maintainers would be very interested in knowing about it. Post a
|
|
274
|
1637 message to comp.emacs.xemacs or send mail to @email{crashes@@xemacs.org}.
|
|
82
|
1638 Please note that the @samp{crashes} address is exclusively for crash
|
|
|
1639 reports.
|
|
|
1640
|
|
|
1641 If at all possible, include a stack backtrace of the core dump that was
|
|
|
1642 produced. This shows where exactly things went wrong, and makes it much
|
|
|
1643 easier to diagnose problems. To do this, you need to locate the core
|
|
|
1644 file (it's called @file{core}, and is usually sitting in the directory
|
|
|
1645 that you started XEmacs from, or your home directory if that other
|
|
|
1646 directory was not writable). Then, go to that directory and execute a
|
|
|
1647 command like:
|
|
|
1648
|
|
|
1649 @example
|
|
|
1650 gdb `which xemacs` core
|
|
|
1651 @end example
|
|
|
1652
|
|
|
1653 and then issue the command @samp{where} to get the stack backtrace. You
|
|
|
1654 might have to use @code{dbx} or some similar debugger in place of
|
|
|
1655 @code{gdb}. If you don't have any such debugger available, complain to
|
|
|
1656 your system administrator.
|
|
|
1657
|
|
|
1658 It's possible that a core file didn't get produced, in which case you're
|
|
|
1659 out of luck. Go complain to your system administrator and tell him not
|
|
335
|
1660 to disable core files by default. Also @xref{Q2.1.15}, for tips and
|
|
82
|
1661 techniques for dealing with a debugger.
|
|
|
1662
|
|
|
1663 When making a problem report make sure that:
|
|
|
1664
|
|
|
1665 @enumerate
|
|
|
1666 @item
|
|
|
1667 Report @strong{all} of the information output by XEmacs during the
|
|
|
1668 crash.
|
|
|
1669
|
|
|
1670 @item
|
|
|
1671 You mention what O/S & Hardware you are running XEmacs on.
|
|
|
1672
|
|
|
1673 @item
|
|
|
1674 What version of XEmacs you are running.
|
|
|
1675
|
|
|
1676 @item
|
|
|
1677 What build options you are using.
|
|
|
1678
|
|
|
1679 @item
|
|
|
1680 If the problem is related to graphics, we will also need to know what
|
|
|
1681 version of the X Window System you are running, and what window manager
|
|
|
1682 you are using.
|
|
|
1683
|
|
|
1684 @item
|
|
|
1685 If the problem happened on a tty, please include the terminal type.
|
|
|
1686 @end enumerate
|
|
|
1687
|
|
|
1688 @node Q2.1.2, Q2.1.3, Q2.1.1, Installation
|
|
274
|
1689 @unnumberedsubsec Q2.1.2: Cryptic Minibuffer messages.
|
|
82
|
1690
|
|
|
1691 When I try to use some particular option of some particular package, I
|
|
|
1692 get a cryptic error in the minibuffer.
|
|
|
1693
|
|
|
1694 If you can't figure out what's going on, select Options/General
|
|
|
1695 Options/Debug on Error from the Menubar and then try and make the error
|
|
|
1696 happen again. This will give you a backtrace that may be enlightening.
|
|
|
1697 If not, try reading through this FAQ; if that fails, you could try
|
|
|
1698 posting to comp.emacs.xemacs (making sure to include the backtrace) and
|
|
|
1699 someone may be able to help. If you can identify which Emacs lisp
|
|
|
1700 source file the error is coming from you can get a more detailed stack
|
|
|
1701 backtrace by doing the following:
|
|
|
1702
|
|
|
1703 @enumerate
|
|
|
1704 @item
|
|
|
1705 Visit the .el file in an XEmacs buffer.
|
|
|
1706
|
|
|
1707 @item
|
|
|
1708 Issue the command @kbd{M-x eval-current-buffer}.
|
|
|
1709
|
|
|
1710 @item
|
|
|
1711 Reproduce the error.
|
|
|
1712 @end enumerate
|
|
|
1713
|
|
|
1714 Depending on the version of XEmacs, you may either select Edit->Show
|
|
|
1715 Messages (19.13 and earlier) or Help->Recent Keystrokes/Messages (19.14
|
|
|
1716 and later) from the menubar to see the most recent messages. This
|
|
|
1717 command is bound to @kbd{C-h l} by default.
|
|
|
1718
|
|
|
1719 @node Q2.1.3, Q2.1.4, Q2.1.2, Installation
|
|
274
|
1720 @unnumberedsubsec Q2.1.3: Translation Table Syntax messages at Startup
|
|
82
|
1721
|
|
|
1722 I get tons of translation table syntax error messages during startup.
|
|
|
1723 How do I get rid of them?
|
|
|
1724
|
|
|
1725 There are two causes of this problem. The first usually only strikes
|
|
|
1726 people using the prebuilt binaries. The culprit in both cases is the
|
|
|
1727 file @file{XKeysymDB}.
|
|
|
1728
|
|
|
1729 @itemize @bullet
|
|
|
1730 @item
|
|
|
1731 The binary cannot find the @file{XKeysymDB} file. The location is
|
|
|
1732 hardcoded at compile time so if the system the binary was built on puts
|
|
|
1733 it a different place than your system does, you have problems. To fix,
|
|
|
1734 set the environment variable @var{XKEYSYMDB} to the location of the
|
|
|
1735 @file{XKeysymDB} file on your system or to the location of the one
|
|
|
1736 included with XEmacs which should be at
|
|
274
|
1737 @iftex
|
|
|
1738 @*
|
|
282
|
1739 @end iftex
|
|
213
|
1740 @file{<xemacs_root_directory>/lib/xemacs-19.16/etc/XKeysymDB}.
|
|
82
|
1741
|
|
|
1742 @item
|
|
|
1743 The binary is finding the XKeysymDB but it is out-of-date on your system
|
|
|
1744 and does not contain the necessary lines. Either ask your system
|
|
|
1745 administrator to replace it with the one which comes with XEmacs (which
|
|
|
1746 is the stock R6 version and is backwards compatible) or set your
|
|
|
1747 @var{XKEYSYMDB} variable to the location of XEmacs's described above.
|
|
|
1748 @end itemize
|
|
|
1749
|
|
|
1750 @node Q2.1.4, Q2.1.5, Q2.1.3, Installation
|
|
274
|
1751 @unnumberedsubsec Q2.1.4: Startup warnings about deducing proper fonts?
|
|
82
|
1752
|
|
|
1753 How can I avoid the startup warnings about deducing proper fonts?
|
|
|
1754
|
|
|
1755 This is highly dependent on your installation, but try with the
|
|
|
1756 following font as your base font for XEmacs and see what it does:
|
|
|
1757
|
|
282
|
1758 @format
|
|
82
|
1759 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
|
|
282
|
1760 @end format
|
|
82
|
1761
|
|
|
1762 More precisely, do the following in your resource file:
|
|
|
1763
|
|
282
|
1764 @format
|
|
|
1765 Emacs.default.attributeFont: \
|
|
|
1766 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1
|
|
|
1767 @end format
|
|
16
|
1768
|
|
82
|
1769 If you just don't want to see the @samp{*Warnings*} buffer at startup
|
|
|
1770 time, you can set this:
|
|
|
1771
|
|
|
1772 @lisp
|
|
|
1773 (setq display-warning-minimum-level 'error)
|
|
|
1774 @end lisp
|
|
|
1775
|
|
|
1776 The buffer still exists; it just isn't in your face.
|
|
|
1777
|
|
|
1778 @node Q2.1.5, Q2.1.6, Q2.1.4, Installation
|
|
274
|
1779 @unnumberedsubsec Q2.1.5: XEmacs cannot connect to my X Terminal!
|
|
82
|
1780
|
|
|
1781 Help! I can not get XEmacs to display on my Envizex X-terminal!
|
|
|
1782
|
|
|
1783 Try setting the @var{DISPLAY} variable using the numeric IP address of
|
|
|
1784 the host you are running XEmacs from.
|
|
|
1785
|
|
|
1786 @node Q2.1.6, Q2.1.7, Q2.1.5, Installation
|
|
274
|
1787 @unnumberedsubsec Q2.1.6: XEmacs just locked up my Linux X server!
|
|
82
|
1788
|
|
|
1789 There have been several reports of the X server locking up under Linux.
|
|
|
1790 In all reported cases removing speedo and scaled fonts from the font
|
|
|
1791 path corrected the problem. This can be done with the command
|
|
163
|
1792 @code{xset}.
|
|
82
|
1793
|
|
|
1794 It is possible that using a font server may also solve the problem.
|
|
|
1795
|
|
|
1796 @node Q2.1.7, Q2.1.8, Q2.1.6, Installation
|
|
274
|
1797 @unnumberedsubsec Q2.1.7: HP Alt key as Meta.
|
|
82
|
1798
|
|
|
1799 How can I make XEmacs recognize the Alt key of my HP workstation as a
|
|
|
1800 Meta key?
|
|
|
1801
|
|
|
1802 Put the following line into a file and load it with xmodmap(1) before
|
|
|
1803 starting XEmacs:
|
|
|
1804
|
|
|
1805 @example
|
|
|
1806 remove Mod1 = Mode_switch
|
|
|
1807 @end example
|
|
|
1808
|
|
|
1809 @node Q2.1.8, Q2.1.9, Q2.1.7, Installation
|
|
274
|
1810 @unnumberedsubsec Q2.1.8: got (wrong-type-argument color-instance-p nil)
|
|
|
1811
|
|
|
1812 @email{nataliek@@rd.scitec.com.au, Natalie Kershaw} writes:
|
|
82
|
1813
|
|
|
1814 @quotation
|
|
|
1815 I am trying to run xemacs 19.13 under X11R4. Whenever I move the mouse I
|
|
|
1816 get the following error. Has anyone seen anything like this? This
|
|
|
1817 doesn't occur on X11R5.
|
|
|
1818
|
|
|
1819 @lisp
|
|
282
|
1820 Signalling:
|
|
|
1821 (error "got (wrong-type-argument color-instance-p nil)
|
|
274
|
1822 and I don't know why!")
|
|
82
|
1823 @end lisp
|
|
|
1824 @end quotation
|
|
|
1825
|
|
274
|
1826 @email{map01kd@@gold.ac.uk, dinos} writes:
|
|
82
|
1827
|
|
|
1828 @quotation
|
|
|
1829 I think this is due to undefined resources; You need to define color
|
|
|
1830 backgrounds and foregrounds into your @file{.../app-defaults/Emacs}
|
|
|
1831 like:
|
|
|
1832
|
|
|
1833 @example
|
|
365
|
1834 *Foreground: Black ;everything will be of black on grey95,
|
|
|
1835 *Background: Grey95 ;unless otherwise specified.
|
|
|
1836 *cursorColor: Red3 ;red3 cursor with grey95 border.
|
|
|
1837 *pointerColor: Red3 ;red3 pointer with grey95 border.
|
|
82
|
1838 @end example
|
|
|
1839 @end quotation
|
|
|
1840
|
|
|
1841 Natalie Kershaw adds:
|
|
|
1842
|
|
|
1843 @quotation
|
|
|
1844 What fixed the problem was adding some more colors to the X color
|
|
|
1845 database (copying the X11R5 colors over), and also defining the
|
|
|
1846 following resources:
|
|
|
1847
|
|
|
1848 @example
|
|
|
1849 xemacs*cursorColor: black
|
|
|
1850 xemacs*pointerColor: black
|
|
|
1851 @end example
|
|
|
1852
|
|
282
|
1853 With the new colors installed the problem still occurs if the above
|
|
82
|
1854 resources are not defined.
|
|
|
1855
|
|
282
|
1856 If the new colors are not present then an additional error occurs on
|
|
82
|
1857 XEmacs startup, which says @samp{Color Red3} not defined.
|
|
|
1858 @end quotation
|
|
|
1859
|
|
|
1860 @node Q2.1.9, Q2.1.10, Q2.1.8, Installation
|
|
274
|
1861 @unnumberedsubsec Q2.1.9: XEmacs causes my OpenWindows 3.0 server to crash.
|
|
82
|
1862
|
|
|
1863 The OpenWindows 3.0 server is incredibly buggy. Your best bet is to
|
|
|
1864 replace it with one from the generic MIT X11 release. You might also
|
|
|
1865 try disabling parts of your @file{.emacs}, like enabling background
|
|
|
1866 pixmaps.
|
|
|
1867
|
|
|
1868 @node Q2.1.10, Q2.1.11, Q2.1.9, Installation
|
|
274
|
1869 @unnumberedsubsec Q2.1.10: Warnings from incorrect key modifiers.
|
|
82
|
1870
|
|
|
1871 The following information comes from the @file{PROBLEMS} file that comes
|
|
|
1872 with XEmacs.
|
|
|
1873
|
|
|
1874 If you're having troubles with HP/UX it is because HP/UX defines the
|
|
|
1875 modifiers wrong in X. Here is a shell script to fix the problem; be
|
|
|
1876 sure that it is run after VUE configures the X server.
|
|
|
1877
|
|
|
1878 @example
|
|
|
1879 #! /bin/sh
|
|
|
1880 xmodmap 2> /dev/null - << EOF
|
|
|
1881 keysym Alt_L = Meta_L
|
|
|
1882 keysym Alt_R = Meta_R
|
|
|
1883 EOF
|
|
|
1884
|
|
|
1885 xmodmap - << EOF
|
|
|
1886 clear mod1
|
|
|
1887 keysym Mode_switch = NoSymbol
|
|
|
1888 add mod1 = Meta_L
|
|
|
1889 keysym Meta_R = Mode_switch
|
|
|
1890 add mod2 = Mode_switch
|
|
|
1891 EOF
|
|
|
1892 @end example
|
|
|
1893
|
|
|
1894 @node Q2.1.11, Q2.1.12, Q2.1.10, Installation
|
|
282
|
1895 @unnumberedsubsec Q2.1.11: @samp{Can't instantiate image error...} in toolbar
|
|
|
1896 @c New
|
|
|
1897
|
|
|
1898 @email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes:
|
|
|
1899
|
|
|
1900 I just installed the XEmacs (20.4-2) RPMS that I downloaded from
|
|
|
1901 @uref{http://www.xemacs.org/}. Everything works fine, except that when
|
|
|
1902 I place my mouse over the toolbar, it beeps and gives me this message:
|
|
|
1903
|
|
|
1904 @example
|
|
|
1905 Can't instantiate image (probably cached):
|
|
|
1906 [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data
|
|
|
1907 (16 16 <strange control characters> ...
|
|
|
1908 @end example
|
|
|
1909
|
|
|
1910 @email{kyle_jones@@wonderworks.com, Kyle Jones} writes:
|
|
|
1911 @quotation
|
|
|
1912 This is problem specific to some Chips and Technologies video
|
|
|
1913 chips, when running XFree86. Putting
|
|
|
1914
|
|
|
1915 @code{Option "sw_cursor"}
|
|
|
1916
|
|
|
1917 in @file{XF86Config} gets rid of the problem.
|
|
|
1918 @end quotation
|
|
82
|
1919
|
|
|
1920 @node Q2.1.12, Q2.1.13, Q2.1.11, Installation
|
|
274
|
1921 @unnumberedsubsec Q2.1.12: Problems with Regular Expressions on DEC OSF1.
|
|
82
|
1922
|
|
|
1923 I have xemacs 19.13 running on an alpha running OSF1 V3.2 148 and ispell
|
|
|
1924 would not run because it claimed the version number was incorrect
|
|
|
1925 although it was indeed OK. I traced the problem to the regular
|
|
|
1926 expression handler.
|
|
|
1927
|
|
274
|
1928 @email{douglask@@dstc.edu.au, Douglas Kosovic} writes:
|
|
82
|
1929
|
|
|
1930 @quotation
|
|
282
|
1931 Actually it's a DEC cc optimization bug that screws up the regexp
|
|
82
|
1932 handling in XEmacs.
|
|
|
1933
|
|
|
1934 Rebuilding using the @samp{-migrate} switch for DEC cc (which uses a
|
|
282
|
1935 different sort of optimization) works fine.
|
|
82
|
1936 @end quotation
|
|
|
1937
|
|
|
1938 See @file{xemacs-19_13-dunix-3_2c.patch} at the following URL on how to
|
|
|
1939 build with the @samp{-migrate} flag:
|
|
|
1940
|
|
|
1941 @example
|
|
274
|
1942 @uref{http://www-digital.cern.ch/carney/emacs/emacs.html}
|
|
282
|
1943 @c Link above, <URL:http://www-digital.cern.ch/carney/emacs/emacs.html> is
|
|
|
1944 @c dead. And the directory `carney' is empty.
|
|
|
1945
|
|
|
1946
|
|
|
1947
|
|
82
|
1948 @end example
|
|
|
1949
|
|
|
1950 NOTE: There have been a variety of other problems reported that are
|
|
|
1951 fixed in this fashion.
|
|
|
1952
|
|
|
1953 @node Q2.1.13, Q2.1.14, Q2.1.12, Installation
|
|
274
|
1954 @unnumberedsubsec Q2.1.13: HP/UX 10.10 and @code{create_process} failure.
|
|
|
1955
|
|
|
1956 @email{Dave.Carrigan@@ipl.ca, Dave Carrigan} writes:
|
|
82
|
1957
|
|
|
1958 @quotation
|
|
|
1959 With XEmacs 19.13 and HP/UX 10.10, anything that relies on the
|
|
|
1960 @code{create_process} function fails. This breaks a lot of things
|
|
|
1961 (shell-mode, compile, ange-ftp, to name a few).
|
|
|
1962 @end quotation
|
|
|
1963
|
|
274
|
1964 @email{johnson@@dtc.hp.com, Phil Johnson} writes:
|
|
82
|
1965
|
|
|
1966 @quotation
|
|
|
1967 This is a problem specific to HP-UX 10.10. It only occurs when XEmacs
|
|
|
1968 is compiled for shared libraries (the default), so you can work around
|
|
|
1969 it by compiling a statically-linked binary (run configure with
|
|
|
1970 @samp{--dynamic=no}).
|
|
|
1971
|
|
|
1972 I'm not sure whether the problem is with a particular shared library or
|
|
|
1973 if it's a kernel problem which crept into 10.10.
|
|
|
1974 @end quotation
|
|
|
1975
|
|
274
|
1976 @email{cognot@@ensg.u-nancy.fr, Richard Cognot} writes:
|
|
82
|
1977
|
|
|
1978 @quotation
|
|
|
1979 I had a few problems with 10.10. Apparently, some of them were solved by
|
|
|
1980 forcing a static link of libc (manually).
|
|
|
1981 @end quotation
|
|
|
1982
|
|
|
1983 @node Q2.1.14, Q2.1.15, Q2.1.13, Installation
|
|
274
|
1984 @unnumberedsubsec Q2.1.14: @kbd{C-g} doesn't work for me. Is it broken?
|
|
|
1985
|
|
359
|
1986 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
82
|
1987
|
|
|
1988 @quotation
|
|
|
1989 @kbd{C-g} does work for most people in most circumstances. If it
|
|
|
1990 doesn't, there are only two explanations:
|
|
|
1991
|
|
|
1992 @enumerate
|
|
|
1993 @item
|
|
|
1994 The code is wrapped with a binding of @code{inhibit-quit} to
|
|
|
1995 @code{t}. @kbd{Ctrl-Shift-G} should still work, I think.
|
|
|
1996
|
|
|
1997 @item
|
|
|
1998 SIGIO is broken on your system, but BROKEN_SIGIO isn't defined.
|
|
|
1999 @end enumerate
|
|
|
2000
|
|
|
2001 To test #2, try executing @code{(while t)} from the @samp{*scratch*}
|
|
|
2002 buffer. If @kbd{C-g} doesn't interrupt, then you're seeing #2.
|
|
|
2003 @end quotation
|
|
|
2004
|
|
274
|
2005 @email{terra@@diku.dk, Morten Welinder} writes:
|
|
82
|
2006
|
|
|
2007 @quotation
|
|
|
2008 On some (but @emph{not} all) machines a hung XEmacs can be revived by
|
|
|
2009 @code{kill -FPE <pid>}. This is a hack, of course, not a solution.
|
|
|
2010 This technique works on a Sun4 running 4.1.3_U1. To see if it works for
|
|
|
2011 you, start another XEmacs and test with that first. If you get a core
|
|
|
2012 dump the method doesn't work and if you get @samp{Arithmetic error} then
|
|
|
2013 it does.
|
|
|
2014 @end quotation
|
|
|
2015
|
|
|
2016 @node Q2.1.15, Q2.1.16, Q2.1.14, Installation
|
|
274
|
2017 @unnumberedsubsec Q2.1.15: How to Debug an XEmacs problem with a debugger
|
|
82
|
2018
|
|
|
2019 If XEmacs does crash on you, one of the most productive things you can
|
|
|
2020 do to help get the bug fixed is to poke around a bit with the debugger.
|
|
|
2021 Here are some hints:
|
|
|
2022
|
|
|
2023 @itemize @bullet
|
|
|
2024 @item
|
|
|
2025 First of all, if the crash is at all reproducible, consider very
|
|
|
2026 strongly recompiling your XEmacs with debugging symbols, with no
|
|
282
|
2027 optimization, and with the configure options @samp{--debug=yes} and
|
|
|
2028 @samp{--error-checking=all}. This will make your XEmacs run somewhat
|
|
|
2029 slower but make it a lot more likely to catch the problem earlier
|
|
|
2030 (closer to its source), and a lot easier to determine what's going on
|
|
|
2031 with a debugger.
|
|
82
|
2032
|
|
|
2033 @item
|
|
|
2034 If you're able to run XEmacs under a debugger and reproduce the crash
|
|
|
2035 (if it's inconvenient to do this because XEmacs is already running or is
|
|
|
2036 running in batch mode as part of a bunch of scripts, consider attaching
|
|
|
2037 to the existing process with your debugger; most debuggers let you do
|
|
|
2038 this by substituting the process ID for the core file when you invoke
|
|
|
2039 the debugger from the command line, or by using the @code{attach}
|
|
|
2040 command or something similar), here are some things you can do:
|
|
|
2041
|
|
|
2042 @item
|
|
|
2043 If XEmacs is hitting an assertion failure, put a breakpoint on
|
|
|
2044 @code{assert_failed()}.
|
|
|
2045
|
|
|
2046 @item
|
|
|
2047 If XEmacs is hitting some weird Lisp error that's causing it to crash
|
|
|
2048 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is
|
|
|
2049 declared static in eval.c.
|
|
|
2050
|
|
|
2051 @item
|
|
|
2052 Internally, you will probably see lots of variables that hold objects of
|
|
|
2053 type @code{Lisp_Object}. These are exactly what they appear to be,
|
|
|
2054 i.e. references to Lisp objects. Printing them out with the debugger
|
|
282
|
2055 probably won't be too useful---you'll likely just see a number. To
|
|
|
2056 decode them, do this:
|
|
82
|
2057
|
|
|
2058 @example
|
|
|
2059 call debug_print (OBJECT)
|
|
|
2060 @end example
|
|
|
2061
|
|
|
2062 where @var{OBJECT} is whatever you want to decode (it can be a variable,
|
|
|
2063 a function call, etc.). This will print out a readable representation
|
|
|
2064 on the TTY from which the xemacs process was invoked.
|
|
|
2065
|
|
|
2066 @item
|
|
|
2067 If you want to get a Lisp backtrace showing the Lisp call
|
|
|
2068 stack, do this:
|
|
|
2069
|
|
|
2070 @example
|
|
|
2071 call debug_backtrace ()
|
|
|
2072 @end example
|
|
|
2073
|
|
|
2074 @item
|
|
272
|
2075 Using @code{debug_print} and @code{debug_backtrace} has two
|
|
|
2076 disadvantages - it can only be used with a running xemacs process, and
|
|
|
2077 it cannot display the internal C structure of a Lisp Object. Even if
|
|
|
2078 all you've got is a core dump, all is not lost.
|
|
|
2079
|
|
|
2080 If you're using GDB, there are some macros in the file
|
|
365
|
2081 @file{src/.gdbinit} in the XEmacs source distribution that should make
|
|
|
2082 it easier for you to decode Lisp objects. This file is automatically
|
|
|
2083 read by gdb if gdb is run in the directory where xemacs was built, and
|
|
|
2084 contains these useful macros to inspect the state of xemacs:
|
|
|
2085
|
|
|
2086 @table @code
|
|
|
2087 @item pobj
|
|
|
2088 Usage: pobj lisp_object @*
|
|
|
2089 Print the internal C representation of a lisp object.
|
|
|
2090
|
|
|
2091 @item xtype
|
|
|
2092 Usage: xtype lisp_object @*
|
|
|
2093 Print the Lisp type of a lisp object.
|
|
|
2094
|
|
|
2095 @item lbt
|
|
|
2096 Usage: lbt @*
|
|
|
2097 Print the current Lisp stack trace.
|
|
|
2098 Requires a running xemacs process.
|
|
|
2099
|
|
|
2100 @item ldp
|
|
|
2101 Usage: ldp lisp_object @*
|
|
|
2102 Print a Lisp Object value using the Lisp printer.
|
|
|
2103 Requires a running xemacs process.
|
|
|
2104
|
|
|
2105 @item run-temacs
|
|
|
2106 Usage: run-temacs @*
|
|
|
2107 Run temacs interactively, like xemacs.
|
|
|
2108 Use this with debugging tools (like purify) that cannot deal with dumping,
|
|
|
2109 or when temacs builds successfully, but xemacs does not.
|
|
|
2110
|
|
|
2111 @item dump-temacs
|
|
|
2112 Usage: dump-temacs @*
|
|
|
2113 Run the dumping part of the build procedure.
|
|
|
2114 Use when debugging temacs, not xemacs!
|
|
|
2115 Use this when temacs builds successfully, but xemacs does not.
|
|
|
2116
|
|
|
2117 @item check-xemacs
|
|
|
2118 Usage: check-xemacs @*
|
|
|
2119 Run the test suite. Equivalent to 'make check'.
|
|
|
2120
|
|
|
2121 @item check-temacs
|
|
|
2122 Usage: check-temacs @*
|
|
|
2123 Run the test suite on temacs. Equivalent to 'make check-temacs'.
|
|
|
2124 Use this with debugging tools (like purify) that cannot deal with dumping,
|
|
|
2125 or when temacs builds successfully, but xemacs does not.
|
|
|
2126 @end table
|
|
272
|
2127
|
|
|
2128 If you are using Sun's @file{dbx} debugger, there is an equivalent file
|
|
365
|
2129 @file{src/.dbxrc}, which defines the same commands for dbx.
|
|
82
|
2130
|
|
|
2131 @item
|
|
|
2132 If you're using a debugger to get a C stack backtrace and you're seeing
|
|
|
2133 stack traces with some of the innermost frames mangled, it may be due to
|
|
|
2134 dynamic linking. (This happens especially under Linux.) Consider
|
|
|
2135 reconfiguring with @samp{--dynamic=no}. Also, sometimes (again under
|
|
|
2136 Linux), stack backtraces of core dumps will have the frame where the
|
|
|
2137 fatal signal occurred mangled; if you can obtain a stack trace while
|
|
|
2138 running the XEmacs process under a debugger, the stack trace should be
|
|
|
2139 clean.
|
|
|
2140
|
|
274
|
2141 @email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so version 1.8
|
|
82
|
2142 if dynamic linking and debugging is a problem on Linux.
|
|
|
2143
|
|
|
2144 @item
|
|
|
2145 If you're using a debugger to get a C stack backtrace and you're
|
|
|
2146 getting a completely mangled and bogus stack trace, it's probably due to
|
|
|
2147 one of the following:
|
|
|
2148
|
|
|
2149 @enumerate a
|
|
|
2150 @item
|
|
|
2151 Your executable has been stripped. Bad news. Tell your sysadmin not to
|
|
|
2152 do this---it doesn't accomplish anything except to save a bit of disk
|
|
|
2153 space, and makes debugging much much harder.
|
|
|
2154
|
|
|
2155 @item
|
|
|
2156 Your stack is getting trashed. Debugging this is hard; you have to do a
|
|
282
|
2157 binary-search type of narrowing down where the crash occurs, until you
|
|
82
|
2158 figure out exactly which line is causing the problem. Of course, this
|
|
|
2159 only works if the bug is highly reproducible.
|
|
|
2160
|
|
|
2161 @item
|
|
|
2162 If your stack trace has exactly one frame in it, with address 0x0, this
|
|
|
2163 could simply mean that XEmacs attempted to execute code at that address,
|
|
|
2164 e.g. through jumping to a null function pointer. Unfortunately, under
|
|
|
2165 those circumstances, GDB under Linux doesn't know how to get a stack
|
|
|
2166 trace. (Yes, this is the third Linux-related problem I've mentioned. I
|
|
|
2167 have no idea why GDB under Linux is so bogus. Complain to the GDB
|
|
|
2168 authors, or to comp.os.linux.development.system). Again, you'll have to
|
|
|
2169 use the narrowing-down process described above.
|
|
|
2170
|
|
|
2171 @item
|
|
163
|
2172 If you compiled 19.14 with @samp{--debug} (or by default in later
|
|
|
2173 versions), you will get a Lisp backtrace output when XEmacs crashes, so
|
|
282
|
2174 you'll have something useful.
|
|
274
|
2175
|
|
82
|
2176 @end enumerate
|
|
272
|
2177
|
|
282
|
2178 @item
|
|
|
2179 If you compile with the newer gcc variants gcc-2.8 or egcs, you will
|
|
365
|
2180 also need gdb 4.17 or above. Earlier releases of gdb can't handle the
|
|
|
2181 debug information generated by the newer compilers.
|
|
282
|
2182
|
|
|
2183 @item
|
|
365
|
2184 In versions of XEmacs before 21.2.27, @file{src/.gdbinit} was named
|
|
|
2185 @file{src/gdbinit}. This had the disadvantage of not being sourced
|
|
|
2186 automatically by gdb, so you had to set that up yourself.
|
|
282
|
2187
|
|
82
|
2188 @end itemize
|
|
|
2189
|
|
|
2190 @node Q2.1.16, Q2.1.17, Q2.1.15, Installation
|
|
274
|
2191 @unnumberedsubsec Q2.1.16: XEmacs crashes in @code{strcat} on HP/UX 10
|
|
82
|
2192
|
|
359
|
2193 From the problems database (through
|
|
|
2194 the former address http://support.mayfield.hp.com/):
|
|
54
|
2195
|
|
|
2196 @example
|
|
82
|
2197 Problem Report: 5003302299
|
|
|
2198 Status: Open
|
|
|
2199
|
|
|
2200 System/Model: 9000/700
|
|
|
2201 Product Name: HPUX S800 10.0X
|
|
|
2202 Product Vers: 9245XB.10.00
|
|
|
2203
|
|
274
|
2204 Description: strcat(3C) may read beyond
|
|
|
2205 end of source string, can cause SIGSEGV
|
|
82
|
2206
|
|
|
2207
|
|
|
2208 *** PROBLEM TEXT ***
|
|
|
2209 strcat(3C) may read beyond the source string onto an unmapped page,
|
|
|
2210 causing a segmentation violation.
|
|
|
2211 @end example
|
|
|
2212
|
|
|
2213 @node Q2.1.17, Q2.1.18, Q2.1.16, Installation
|
|
274
|
2214 @unnumberedsubsec Q2.1.17: @samp{Marker does not point anywhere}
|
|
82
|
2215
|
|
163
|
2216 As with other errors, set @code{debug-on-error} to @code{t} to get the
|
|
|
2217 backtrace when the error occurs. Specifically, two problems have been
|
|
|
2218 reported (and fixed).
|
|
|
2219
|
|
|
2220 @enumerate
|
|
|
2221 @item
|
|
|
2222 A problem with line-number-mode in XEmacs 19.14 affected a large number
|
|
|
2223 of other packages. If you see this error message, turn off
|
|
82
|
2224 line-number-mode.
|
|
|
2225
|
|
163
|
2226 @item
|
|
|
2227 A problem with some early versions of Gnus 5.4 caused this error.
|
|
|
2228 Upgrade your Gnus.
|
|
|
2229 @end enumerate
|
|
|
2230
|
|
82
|
2231 @node Q2.1.18, Q2.1.19, Q2.1.17, Installation
|
|
365
|
2232 @unnumberedsubsec Q2.1.18: removed
|
|
82
|
2233
|
|
|
2234 @node Q2.1.19, Q2.1.20, Q2.1.18, Installation
|
|
274
|
2235 @unnumberedsubsec Q2.1.19: XEmacs does not follow the local timezone.
|
|
82
|
2236
|
|
|
2237 When using one of the prebuilt binaries many users have observed that
|
|
|
2238 XEmacs uses the timezone under which it was built, but not the timezone
|
|
|
2239 under which it is running. The solution is to add:
|
|
|
2240
|
|
|
2241 @lisp
|
|
|
2242 (set-time-zone-rule "MET")
|
|
|
2243 @end lisp
|
|
|
2244
|
|
|
2245 to your @file{.emacs} or the @file{site-start.el} file if you can.
|
|
|
2246 Replace @code{MET} with your local timezone.
|
|
|
2247
|
|
|
2248 @node Q2.1.20, Q2.1.21, Q2.1.19, Installation
|
|
274
|
2249 @unnumberedsubsec Q2.1.20: @samp{Symbol's function definition is void: hkey-help-show.}
|
|
82
|
2250
|
|
|
2251 This is a problem with a partially loaded hyperbole. Try adding:
|
|
|
2252
|
|
|
2253 @lisp
|
|
|
2254 (require 'hmouse-drv)
|
|
|
2255 @end lisp
|
|
|
2256
|
|
|
2257 where you load hyperbole and the problem should go away.
|
|
|
2258
|
|
116
|
2259 @node Q2.1.21, Q2.1.22, Q2.1.20, Installation
|
|
365
|
2260 @unnumberedsubsec Q2.1.21: [This question intentionally left blank]
|
|
82
|
2261
|
|
126
|
2262 @node Q2.1.22, Q2.1.23, Q2.1.21, Installation
|
|
274
|
2263 @unnumberedsubsec Q2.1.22: XEmacs seems to take a really long time to do some things
|
|
|
2264
|
|
|
2265 @email{dmoore@@ucsd.edu, David Moore} writes:
|
|
116
|
2266
|
|
|
2267 @quotation
|
|
|
2268 Two things you can do:
|
|
|
2269
|
|
|
2270 1) C level:
|
|
|
2271
|
|
|
2272 When you see it going mad like this, you might want to use gdb from an
|
|
|
2273 'xterm' to attach to the running process and get a stack trace. To do
|
|
|
2274 this just run:
|
|
|
2275
|
|
|
2276 @example
|
|
|
2277 gdb /path/to/xemacs/xemacs ####
|
|
|
2278 @end example
|
|
|
2279
|
|
163
|
2280 Where @code{####} is the process id of your xemacs, instead of
|
|
|
2281 specifying the core. When gdb attaches, the xemacs will stop [1] and
|
|
|
2282 you can type `where' in gdb to get a stack trace as usual. To get
|
|
|
2283 things moving again, you can just type `quit' in gdb. It'll tell you
|
|
|
2284 the program is running and ask if you want to quit anyways. Say 'y' and
|
|
|
2285 it'll quit and have your emacs continue from where it was at.
|
|
116
|
2286
|
|
|
2287 2) Lisp level:
|
|
|
2288
|
|
|
2289 Turn on debug-on-quit early on. When you think things are going slow
|
|
|
2290 hit C-g and it may pop you in the debugger so you can see what routine
|
|
|
2291 is running. Press `c' to get going again.
|
|
|
2292
|
|
|
2293 debug-on-quit doesn't work if something's turned on inhibit-quit or in
|
|
|
2294 some other strange cases.
|
|
|
2295 @end quotation
|
|
|
2296
|
|
365
|
2297 @node Q2.1.23, Q2.1.24, Q2.1.22, Installation
|
|
282
|
2298 @unnumberedsubsec Q2.1.23: Movemail on Linux does not work for XEmacs 19.15 and later.
|
|
126
|
2299
|
|
|
2300 Movemail used to work fine in 19.14 but has stopped working in 19.15
|
|
|
2301 and 20.x. I am using Linux.
|
|
|
2302
|
|
274
|
2303 @email{steve@@xemacs.org, SL Baur} writes:
|
|
126
|
2304
|
|
|
2305 @quotation
|
|
163
|
2306 Movemail on Linux used to default to using flock file locking. With
|
|
|
2307 19.15 and later versions it now defaults to using @code{.lock} file
|
|
|
2308 locking. If this is not appropriate for your system, edit src/s/linux.h
|
|
|
2309 and uncomment the line that reads:
|
|
|
2310
|
|
|
2311 @example
|
|
|
2312 #define MAIL_USE_FLOCK
|
|
|
2313 @end example
|
|
126
|
2314 @end quotation
|
|
|
2315
|
|
367
|
2316 @node Q2.1.24, Q2.1.25, Q2.1.23, Installation
|
|
365
|
2317 @unnumberedsubsec Q2.1.24: XEmacs won't start without network. (NEW)
|
|
|
2318
|
|
|
2319 If XEmacs starts when you're on the network, but fails when you're not
|
|
|
2320 on the network, you may be missing a "localhost" entry in your
|
|
|
2321 @file{/etc/hosts} file. The file should contain an entry like:
|
|
|
2322
|
|
|
2323 @example
|
|
|
2324 127.0.0.1 localhost
|
|
|
2325 @end example
|
|
|
2326
|
|
|
2327 Add that line, and XEmacs will be happy.
|
|
|
2328
|
|
367
|
2329 @node Q2.1.25, , Q2.1.24, Installation
|
|
|
2330 @unnumberedsubsec Q2.1.25:: After upgrading, XEmacs won't do `foo' any more! (NEW)
|
|
|
2331
|
|
|
2332 You have been used to doing `foo', but now when you invoke it (or click
|
|
|
2333 the toolbar button or select the menu item), nothing (or an error)
|
|
|
2334 happens. The simplest explanation is that you are missing a package
|
|
|
2335 that is essential to you. You can either track it down and install it,
|
|
|
2336 or install the `Sumo Tarball' (see @pxref{Q2.0.14}).
|
|
|
2337
|
|
82
|
2338 @node Customization, Subsystems, Installation, Top
|
|
274
|
2339 @unnumbered 3 Customization and Options
|
|
82
|
2340
|
|
|
2341 This is part 3 of the XEmacs Frequently Asked Questions list. This
|
|
|
2342 section is devoted to Customization and screen settings.
|
|
|
2343
|
|
|
2344 @menu
|
|
|
2345 Customization---Emacs Lisp and @file{.emacs}:
|
|
282
|
2346 * Q3.0.1:: What version of Emacs am I running?
|
|
82
|
2347 * Q3.0.2:: How do I evaluate Elisp expressions?
|
|
|
2348 * Q3.0.3:: @code{(setq tab-width 6)} behaves oddly.
|
|
|
2349 * Q3.0.4:: How can I add directories to the @code{load-path}?
|
|
|
2350 * Q3.0.5:: How to check if a lisp function is defined?
|
|
|
2351 * Q3.0.6:: Can I force the output of @code{(face-list)} to a buffer?
|
|
282
|
2352 * Q3.0.7:: Font selections don't get saved after @code{Save Options}.
|
|
82
|
2353 * Q3.0.8:: How do I make a single minibuffer frame?
|
|
217
|
2354 * Q3.0.9:: What is @code{Customize}?
|
|
82
|
2355
|
|
|
2356 X Window System & Resources:
|
|
|
2357 * Q3.1.1:: Where is a list of X resources?
|
|
|
2358 * Q3.1.2:: How can I detect a color display?
|
|
365
|
2359 * Q3.1.3:: [This question intentionally left blank]
|
|
|
2360 * Q3.1.4:: [This question intentionally left blank]
|
|
82
|
2361 * Q3.1.5:: How can I get the icon to just say @samp{XEmacs}?
|
|
|
2362 * Q3.1.6:: How can I have the window title area display the full path?
|
|
|
2363 * Q3.1.7:: @samp{xemacs -name junk} doesn't work?
|
|
282
|
2364 * Q3.1.8:: @samp{-iconic} doesn't work.
|
|
82
|
2365
|
|
|
2366 Textual Fonts & Colors:
|
|
|
2367 * Q3.2.1:: How can I set color options from @file{.emacs}?
|
|
|
2368 * Q3.2.2:: How do I set the text, menu and modeline fonts?
|
|
|
2369 * Q3.2.3:: How can I set the colors when highlighting a region?
|
|
282
|
2370 * Q3.2.4:: How can I limit color map usage?
|
|
82
|
2371 * Q3.2.5:: My tty supports color, but XEmacs doesn't use them.
|
|
282
|
2372 * Q3.2.6:: Can I have pixmap backgrounds in XEmacs?
|
|
82
|
2373
|
|
|
2374 The Modeline:
|
|
|
2375 * Q3.3.1:: How can I make the modeline go away?
|
|
|
2376 * Q3.3.2:: How do you have XEmacs display the line number in the modeline?
|
|
|
2377 * Q3.3.3:: How do I get XEmacs to put the time of day on the modeline?
|
|
163
|
2378 * Q3.3.4:: How do I turn off current chapter from AUC TeX modeline?
|
|
|
2379 * Q3.3.5:: How can one change the modeline color based on the mode used?
|
|
82
|
2380
|
|
|
2381 3.4 Multiple Device Support:
|
|
282
|
2382 * Q3.4.1:: How do I open a frame on another screen of my multi-headed display?
|
|
82
|
2383 * Q3.4.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
|
2384
|
|
|
2385 3.5 The Keyboard:
|
|
|
2386 * Q3.5.1:: How can I bind complex functions (or macros) to keys?
|
|
|
2387 * Q3.5.2:: How can I stop down-arrow from adding empty lines to the bottom of my buffers?
|
|
|
2388 * Q3.5.3:: How do I bind C-. and C-; to scroll one line up and down?
|
|
|
2389 * Q3.5.4:: Globally binding @kbd{Delete}?
|
|
|
2390 * Q3.5.5:: Scrolling one line at a time.
|
|
282
|
2391 * Q3.5.6:: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
82
|
2392 * Q3.5.7:: How can you type in special characters in XEmacs?
|
|
|
2393 * Q3.5.8:: Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
|
|
|
2394 * Q3.5.9:: How do I make the Delete key delete forward?
|
|
|
2395 * Q3.5.10:: Can I turn on @dfn{sticky} modifier keys?
|
|
282
|
2396 * Q3.5.11:: How do I map the arrow keys?
|
|
369
|
2397 * Q3.5.12:: XEmacs complains about my xmodmap (I hate the default X keymap).
|
|
82
|
2398
|
|
|
2399 The Cursor:
|
|
|
2400 * Q3.6.1:: Is there a way to make the bar cursor thicker?
|
|
|
2401 * 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?
|
|
|
2402 * Q3.6.3:: Can I make the cursor blink?
|
|
|
2403
|
|
|
2404 The Mouse and Highlighting:
|
|
|
2405 * Q3.7.1:: How can I turn off Mouse pasting?
|
|
|
2406 * Q3.7.2:: How do I set control/meta/etc modifiers on mouse buttons?
|
|
|
2407 * Q3.7.3:: Clicking the left button does not do anything in buffer list.
|
|
|
2408 * Q3.7.4:: How can I get a list of buffers when I hit mouse button 3?
|
|
|
2409 * Q3.7.5:: Why does cut-and-paste not work between XEmacs and a cmdtool?
|
|
|
2410 * Q3.7.6:: How I can set XEmacs up so that it pastes where the text cursor is?
|
|
|
2411 * Q3.7.7:: How do I select a rectangular region?
|
|
|
2412 * Q3.7.8:: Why does @kbd{M-w} take so long?
|
|
|
2413
|
|
|
2414 The Menubar and Toolbar:
|
|
|
2415 * Q3.8.1:: How do I get rid of the menu (or menubar)?
|
|
|
2416 * Q3.8.2:: Can I customize the basic menubar?
|
|
|
2417 * Q3.8.3:: How do I control how many buffers are listed in the menu @code{Buffers} list?
|
|
|
2418 * Q3.8.4:: Resources like @code{Emacs*menubar*font} are not working?
|
|
|
2419 * Q3.8.5:: How can I bind a key to a function to toggle the toolbar?
|
|
|
2420
|
|
|
2421 Scrollbars:
|
|
|
2422 * Q3.9.1:: How can I disable the scrollbar?
|
|
|
2423 * Q3.9.2:: How can one use resources to change scrollbar colors?
|
|
|
2424 * Q3.9.3:: Moving the scrollbar can move the point; can I disable this?
|
|
|
2425 * Q3.9.4:: How can I get automatic horizontal scrolling?
|
|
|
2426
|
|
|
2427 Text Selections:
|
|
282
|
2428 * Q3.10.1:: How can I turn off or change highlighted selections?
|
|
82
|
2429 * Q3.10.2:: How do I get that typing on an active region removes it?
|
|
|
2430 * Q3.10.3:: Can I turn off the highlight during isearch?
|
|
|
2431 * Q3.10.4:: How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
|
|
|
2432 * Q3.10.5:: The region disappears when I hit the end of buffer while scrolling.
|
|
|
2433 @end menu
|
|
|
2434
|
|
|
2435 @node Q3.0.1, Q3.0.2, Customization, Customization
|
|
274
|
2436 @unnumberedsec 3.0: Customization -- Emacs Lisp and .emacs
|
|
|
2437 @unnumberedsubsec Q3.0.1: What version of Emacs am I running?
|
|
82
|
2438
|
|
|
2439 How can @file{.emacs} determine which of the family of Emacsen I am
|
|
|
2440 using?
|
|
|
2441
|
|
|
2442 To determine if you are currently running GNU Emacs 18, GNU Emacs 19,
|
|
126
|
2443 XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the
|
|
|
2444 example given in @file{etc/sample.emacs}. There are other nifty things
|
|
|
2445 in there as well!
|
|
82
|
2446
|
|
|
2447 For all new code, all you really need to do is:
|
|
|
2448
|
|
|
2449 @lisp
|
|
|
2450 (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))
|
|
|
2451 @end lisp
|
|
|
2452
|
|
|
2453 @node Q3.0.2, Q3.0.3, Q3.0.1, Customization
|
|
274
|
2454 @unnumberedsubsec Q3.0.2: How can I evaluate Emacs-Lisp expressions?
|
|
82
|
2455
|
|
|
2456 I know I can evaluate Elisp expressions from @code{*scratch*} buffer
|
|
|
2457 with @kbd{C-j} after the expression. How do I do it from another
|
|
|
2458 buffer?
|
|
|
2459
|
|
163
|
2460 Press @kbd{M-:} (the default binding of @code{eval-expression}), and
|
|
|
2461 enter the expression to the minibuffer. In XEmacs prior to 19.15
|
|
|
2462 @code{eval-expression} used to be a disabled command by default. If
|
|
|
2463 this is the case, upgrade your XEmacs.
|
|
82
|
2464
|
|
|
2465 @node Q3.0.3, Q3.0.4, Q3.0.2, Customization
|
|
274
|
2466 @unnumberedsubsec Q3.0.3: @code{(setq tab-width 6)} behaves oddly.
|
|
82
|
2467
|
|
|
2468 If you put @code{(setq tab-width 6)} in your @file{.emacs} file it does
|
|
|
2469 not work! Is there a reason for this? If you do it at the EVAL prompt
|
|
|
2470 it works fine!! How strange.
|
|
|
2471
|
|
|
2472 Use @code{setq-default} instead, since @code{tab-width} is
|
|
|
2473 all-buffer-local.
|
|
|
2474
|
|
|
2475 @node Q3.0.4, Q3.0.5, Q3.0.3, Customization
|
|
274
|
2476 @unnumberedsubsec Q3.0.4: How can I add directories to the @code{load-path}?
|
|
82
|
2477
|
|
|
2478 Here are two ways to do that, one that puts your directories at the
|
|
|
2479 front of the load-path, the other at the end:
|
|
|
2480
|
|
|
2481 @lisp
|
|
|
2482 ;;; Add things at the beginning of the load-path, do not add
|
|
|
2483 ;;; duplicate directories:
|
|
163
|
2484 (pushnew "bar" load-path :test 'equal)
|
|
|
2485
|
|
|
2486 (pushnew "foo" load-path :test 'equal)
|
|
82
|
2487
|
|
|
2488 ;;; Add things at the end, unconditionally
|
|
163
|
2489 (setq load-path (nconc load-path '("foo" "bar")))
|
|
82
|
2490 @end lisp
|
|
|
2491
|
|
274
|
2492 @email{keithh@@nortel.ca, keith (k.p.) hanlan} writes:
|
|
82
|
2493
|
|
|
2494 @quotation
|
|
|
2495 To add directories using Unix shell metacharacters use
|
|
|
2496 @file{expand-file-name} like this:
|
|
|
2497
|
|
|
2498 @lisp
|
|
163
|
2499 (push (expand-file-name "~keithh/.emacsdir") load-path)
|
|
82
|
2500 @end lisp
|
|
|
2501 @end quotation
|
|
|
2502
|
|
|
2503 @node Q3.0.5, Q3.0.6, Q3.0.4, Customization
|
|
274
|
2504 @unnumberedsubsec Q3.0.5: How to check if a lisp function is defined?
|
|
82
|
2505
|
|
|
2506 Use the following elisp:
|
|
|
2507
|
|
|
2508 @lisp
|
|
|
2509 (fboundp 'foo)
|
|
|
2510 @end lisp
|
|
|
2511
|
|
|
2512 It's almost always a mistake to test @code{emacs-version} or any similar
|
|
|
2513 variables.
|
|
|
2514
|
|
|
2515 Instead, use feature-tests, such as @code{featurep}, @code{boundp},
|
|
359
|
2516 @code{fboundp}, or even simple behavioral tests, eg.:
|
|
82
|
2517
|
|
|
2518 @lisp
|
|
282
|
2519 (defvar foo-old-losing-code-p
|
|
82
|
2520 (condition-case nil (progn (losing-code t) nil)
|
|
274
|
2521 (wrong-number-of-arguments t)))
|
|
82
|
2522 @end lisp
|
|
|
2523
|
|
|
2524 There is an incredible amount of broken code out there which could work
|
|
|
2525 much better more often in more places if it did the above instead of
|
|
|
2526 trying to divine its environment from the value of one variable.
|
|
|
2527
|
|
|
2528 @node Q3.0.6, Q3.0.7, Q3.0.5, Customization
|
|
274
|
2529 @unnumberedsubsec Q3.0.6: Can I force the output of @code{(face-list)} to a buffer?
|
|
82
|
2530
|
|
|
2531 It would be good having it in a buffer, as the output of
|
|
|
2532 @code{(face-list)} is too wide to fit to a minibuffer.
|
|
|
2533
|
|
|
2534 Evaluate the expression in the @samp{*scratch*} buffer with point after
|
|
|
2535 the rightmost paren and typing @kbd{C-j}.
|
|
|
2536
|
|
163
|
2537 If the minibuffer smallness is the only problem you encounter, you can
|
|
|
2538 simply press @kbd{C-h l} to get the former minibuffer contents in a
|
|
|
2539 buffer.
|
|
|
2540
|
|
82
|
2541 @node Q3.0.7, Q3.0.8, Q3.0.6, Customization
|
|
274
|
2542 @unnumberedsubsec Q3.0.7: Font selections in don't get saved after @code{Save Options}.
|
|
126
|
2543
|
|
|
2544 For XEmacs 19.14 and previous:
|
|
82
|
2545
|
|
274
|
2546 @email{mannj@@ll.mit.edu, John Mann} writes:
|
|
82
|
2547
|
|
|
2548 @quotation
|
|
343
|
2549 You have to go to Options->Frame Appearance and unselect
|
|
82
|
2550 @samp{Frame-Local Font Menu}. If this option is selected, font changes
|
|
|
2551 are only applied to the @emph{current} frame and do @emph{not} get saved
|
|
|
2552 when you save options.
|
|
|
2553 @end quotation
|
|
|
2554
|
|
126
|
2555 For XEmacs 19.15 and later:
|
|
|
2556
|
|
282
|
2557 Implement the above as well as set the following in your @file{.emacs}
|
|
126
|
2558
|
|
|
2559 @lisp
|
|
163
|
2560 (setq options-save-faces t)
|
|
126
|
2561 @end lisp
|
|
|
2562
|
|
215
|
2563 @node Q3.0.8, Q3.0.9, Q3.0.7, Customization
|
|
274
|
2564 @unnumberedsubsec Q3.0.8: How do I get a single minibuffer frame?
|
|
|
2565
|
|
|
2566 @email{acs@@acm.org, Vin Shelton} writes:
|
|
82
|
2567
|
|
|
2568 @lisp
|
|
|
2569 (setq initial-frame-plist '(minibuffer nil))
|
|
|
2570 (setq default-frame-plist '(minibuffer nil))
|
|
|
2571 (setq default-minibuffer-frame
|
|
|
2572 (make-frame
|
|
274
|
2573 '(minibuffer only
|
|
365
|
2574 width 86
|
|
|
2575 height 1
|
|
|
2576 menubar-visible-p nil
|
|
|
2577 default-toolbar-visible-p nil
|
|
|
2578 name "minibuffer"
|
|
|
2579 top -2
|
|
|
2580 left -2
|
|
|
2581 has-modeline-p nil)))
|
|
82
|
2582 (frame-notice-user-settings)
|
|
|
2583 @end lisp
|
|
|
2584
|
|
298
|
2585 @strong{Please note:} The single minibuffer frame may not be to everyone's
|
|
82
|
2586 taste, and there any number of other XEmacs options settings that may
|
|
|
2587 make it difficult or inconvenient to use.
|
|
|
2588
|
|
215
|
2589 @node Q3.0.9, Q3.1.1, Q3.0.8, Customization
|
|
274
|
2590 @unnumberedsubsec Q3.0.9: What is @code{Customize}?
|
|
217
|
2591
|
|
|
2592 Starting with XEmacs 20.2 there is new system 'Customize' for customizing
|
|
215
|
2593 XEmacs options.
|
|
|
2594
|
|
|
2595 You can access @code{Customize} from the @code{Options} menu
|
|
217
|
2596 or invoking one of customize commands by typing eg.
|
|
215
|
2597 @kbd{M-x customize}, @kbd{M-x customize-face},
|
|
|
2598 @kbd{M-x customize-variable} or @kbd{M-x customize-apropos}.
|
|
|
2599
|
|
217
|
2600 Starting with XEmacs 20.3 there is also new `browser' mode for Customize.
|
|
215
|
2601 Try it out with @kbd{M-x customize-browse}
|
|
|
2602
|
|
|
2603 @node Q3.1.1, Q3.1.2, Q3.0.9, Customization
|
|
274
|
2604 @unnumberedsec 3.1: X Window System & Resources
|
|
|
2605 @unnumberedsubsec Q3.1.1: Where is a list of X resources?
|
|
82
|
2606
|
|
|
2607 Search through the @file{NEWS} file for @samp{X Resources}. A fairly
|
|
|
2608 comprehensive list is given after it.
|
|
|
2609
|
|
|
2610 In addition, an @file{app-defaults} file is supplied,
|
|
|
2611 @file{etc/Emacs.ad} listing the defaults. The file
|
|
|
2612 @file{etc/sample.Xdefaults} gives a set of defaults that you might
|
|
|
2613 consider. It is essentially the same as @file{etc/Emacs.ad} but some
|
|
|
2614 entries are slightly altered. Be careful about installing the contents
|
|
|
2615 of this file into your @file{.Xdefaults} or @file{.Xresources} file if
|
|
|
2616 you use GNU Emacs under X11 as well.
|
|
|
2617
|
|
|
2618 @node Q3.1.2, Q3.1.3, Q3.1.1, Customization
|
|
274
|
2619 @unnumberedsubsec Q3.1.2: How can I detect a color display?
|
|
82
|
2620
|
|
|
2621 You can test the return value of the function @code{(device-class)}, as
|
|
|
2622 in:
|
|
|
2623
|
|
|
2624 @lisp
|
|
|
2625 (when (eq (device-class) 'color)
|
|
|
2626 (set-face-foreground 'font-lock-comment-face "Grey")
|
|
|
2627 (set-face-foreground 'font-lock-string-face "Red")
|
|
|
2628 ....
|
|
|
2629 )
|
|
|
2630 @end lisp
|
|
|
2631
|
|
|
2632 @node Q3.1.3, Q3.1.4, Q3.1.2, Customization
|
|
365
|
2633 @unnumberedsubsec Q3.1.3: [This question intentionally left blank]
|
|
82
|
2634
|
|
|
2635 @node Q3.1.4, Q3.1.5, Q3.1.3, Customization
|
|
365
|
2636 @unnumberedsubsec Q3.1.4: [This question intentionally left blank]
|
|
82
|
2637
|
|
|
2638 @node Q3.1.5, Q3.1.6, Q3.1.4, Customization
|
|
274
|
2639 @unnumberedsubsec Q3.1.5: How can I get the icon to just say @samp{XEmacs}?
|
|
82
|
2640
|
|
|
2641 I'd like the icon to just say @samp{XEmacs}, and not include the name of
|
|
|
2642 the current file in it.
|
|
|
2643
|
|
|
2644 Add the following line to your @file{.emacs}:
|
|
|
2645
|
|
|
2646 @lisp
|
|
|
2647 (setq frame-icon-title-format "XEmacs")
|
|
|
2648 @end lisp
|
|
|
2649
|
|
|
2650 @node Q3.1.6, Q3.1.7, Q3.1.5, Customization
|
|
274
|
2651 @unnumberedsubsec Q3.1.6: How can I have the window title area display the full path?
|
|
82
|
2652
|
|
|
2653 I'd like to have the window title area display the full directory/name
|
|
|
2654 of the current buffer file and not just the name.
|
|
|
2655
|
|
|
2656 Add the following line to your @file{.emacs}:
|
|
|
2657
|
|
|
2658 @lisp
|
|
|
2659 (setq frame-title-format "%S: %f")
|
|
|
2660 @end lisp
|
|
|
2661
|
|
|
2662 A more sophisticated title might be:
|
|
|
2663
|
|
|
2664 @lisp
|
|
|
2665 (setq frame-title-format
|
|
282
|
2666 '("%S: " (buffer-file-name "%f"
|
|
365
|
2667 (dired-directory dired-directory "%b"))))
|
|
82
|
2668 @end lisp
|
|
|
2669
|
|
|
2670 That is, use the file name, or the dired-directory, or the buffer name.
|
|
|
2671
|
|
|
2672 @node Q3.1.7, Q3.1.8, Q3.1.6, Customization
|
|
274
|
2673 @unnumberedsubsec Q3.1.7: @samp{xemacs -name junk} doesn't work?
|
|
82
|
2674
|
|
|
2675 When I run @samp{xterm -name junk}, I get an xterm whose class name
|
|
|
2676 according to xprop, is @samp{junk}. This is the way it's supposed to
|
|
|
2677 work, I think. When I run @samp{xemacs -name junk} the class name is
|
|
|
2678 not set to @samp{junk}. It's still @samp{emacs}. What does
|
|
|
2679 @samp{xemacs -name} really do? The reason I ask is that my window
|
|
|
2680 manager (fvwm) will make a window sticky and I use XEmacs to read my
|
|
|
2681 mail. I want that XEmacs window to be sticky, without having to use the
|
|
|
2682 window manager's function to set the window sticky. What gives?
|
|
|
2683
|
|
|
2684 @samp{xemacs -name} sets the application name for the program (that is,
|
|
|
2685 the thing which normally comes from @samp{argv[0]}). Using @samp{-name}
|
|
|
2686 is the same as making a copy of the executable with that new name. The
|
|
|
2687 @code{WM_CLASS} property on each frame is set to the frame-name, and the
|
|
|
2688 application-class. So, if you did @samp{xemacs -name FOO} and then
|
|
|
2689 created a frame named @var{BAR}, you'd get an X window with WM_CLASS =
|
|
|
2690 @code{( "BAR", "Emacs")}. However, the resource hierarchy for this
|
|
|
2691 widget would be:
|
|
|
2692
|
|
|
2693 @example
|
|
|
2694 Name: FOO .shell .container .BAR
|
|
|
2695 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
|
|
|
2696 @end example
|
|
|
2697
|
|
|
2698 instead of the default
|
|
|
2699
|
|
|
2700 @example
|
|
|
2701 Name: xemacs.shell .container .emacs
|
|
|
2702 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
|
|
|
2703 @end example
|
|
|
2704
|
|
|
2705
|
|
|
2706 It is arguable that the first element of WM_CLASS should be set to the
|
|
|
2707 application-name instead of the frame-name, but I think that's less
|
|
|
2708 flexible, since it does not give you the ability to have multiple frames
|
|
|
2709 with different WM_CLASS properties. Another possibility would be for
|
|
|
2710 the default frame name to come from the application name instead of
|
|
|
2711 simply being @samp{emacs}. However, at this point, making that change
|
|
|
2712 would be troublesome: it would mean that many users would have to make
|
|
|
2713 yet another change to their resource files (since the default frame name
|
|
|
2714 would suddenly change from @samp{emacs} to @samp{xemacs}, or whatever
|
|
|
2715 the executable happened to be named), so we'd rather avoid it.
|
|
|
2716
|
|
|
2717 To make a frame with a particular name use:
|
|
|
2718
|
|
|
2719 @lisp
|
|
|
2720 (make-frame '((name . "the-name")))
|
|
|
2721 @end lisp
|
|
|
2722
|
|
|
2723 @node Q3.1.8, Q3.2.1, Q3.1.7, Customization
|
|
274
|
2724 @unnumberedsubsec Q3.1.8: @samp{-iconic} doesn't work.
|
|
82
|
2725
|
|
|
2726 When I start up XEmacs using @samp{-iconic} it doesn't work right.
|
|
|
2727 Using @samp{-unmapped} on the command line, and setting the
|
|
|
2728 @code{initiallyUnmapped} X Resource don't seem to help much either...
|
|
|
2729
|
|
359
|
2730 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
82
|
2731
|
|
|
2732 @quotation
|
|
|
2733 Ugh, this stuff is such an incredible mess that I've about given up
|
|
|
2734 getting it to work. The principal problem is numerous window-manager
|
|
|
2735 bugs...
|
|
|
2736 @end quotation
|
|
|
2737
|
|
|
2738 @node Q3.2.1, Q3.2.2, Q3.1.8, Customization
|
|
274
|
2739 @unnumberedsec 3.2: Textual Fonts & Colors
|
|
|
2740 @unnumberedsubsec Q3.2.1: How can I set color options from @file{.emacs}?
|
|
82
|
2741
|
|
|
2742 How can I set the most commonly used color options from my @file{.emacs}
|
|
|
2743 instead of from my @file{.Xdefaults}?
|
|
|
2744
|
|
|
2745 Like this:
|
|
|
2746
|
|
|
2747 @lisp
|
|
274
|
2748 (set-face-background 'default "bisque") ; frame background
|
|
|
2749 (set-face-foreground 'default "black") ; normal text
|
|
|
2750 (set-face-background 'zmacs-region "red") ; When selecting w/
|
|
365
|
2751 ; mouse
|
|
82
|
2752 (set-face-foreground 'zmacs-region "yellow")
|
|
|
2753 (set-face-font 'default "*courier-bold-r*120-100-100*")
|
|
274
|
2754 (set-face-background 'highlight "blue") ; Ie when selecting
|
|
365
|
2755 ; buffers
|
|
82
|
2756 (set-face-foreground 'highlight "yellow")
|
|
282
|
2757 (set-face-background 'modeline "blue") ; Line at bottom
|
|
365
|
2758 ; of buffer
|
|
82
|
2759 (set-face-foreground 'modeline "white")
|
|
|
2760 (set-face-font 'modeline "*bold-r-normal*140-100-100*")
|
|
282
|
2761 (set-face-background 'isearch "yellow") ; When highlighting
|
|
365
|
2762 ; while searching
|
|
82
|
2763 (set-face-foreground 'isearch "red")
|
|
274
|
2764 (setq x-pointer-foreground-color "black") ; Adds to bg color,
|
|
365
|
2765 ; so keep black
|
|
282
|
2766 (setq x-pointer-background-color "blue") ; This is color
|
|
365
|
2767 ; you really
|
|
|
2768 ; want ptr/crsr
|
|
82
|
2769 @end lisp
|
|
|
2770
|
|
|
2771 @node Q3.2.2, Q3.2.3, Q3.2.1, Customization
|
|
274
|
2772 @unnumberedsubsec Q3.2.2: How do I set the text, menu and modeline fonts?
|
|
82
|
2773
|
|
|
2774 Note that you should use @samp{Emacs.} and not @samp{Emacs*} when
|
|
|
2775 setting face values.
|
|
|
2776
|
|
|
2777 In @file{.Xdefaults}:
|
|
|
2778
|
|
|
2779 @example
|
|
282
|
2780 Emacs.default.attributeFont: -*-*-medium-r-*-*-*-120-*-*-m-*-*-*
|
|
82
|
2781 Emacs*menubar*font: fixed
|
|
|
2782 Emacs.modeline.attributeFont: fixed
|
|
|
2783 @end example
|
|
|
2784
|
|
|
2785 This is confusing because modeline is a face, and can be found listed
|
|
|
2786 with all faces in the current mode by using @kbd{M-x set-face-font
|
|
|
2787 (enter) ?}. It uses the face specification of @code{attributeFont},
|
|
|
2788 while menubar is a normal X thing that uses the specification
|
|
|
2789 @code{font}. With Motif it may be necessary to use @code{fontList}
|
|
|
2790 instead of @code{font}.
|
|
|
2791
|
|
|
2792 @node Q3.2.3, Q3.2.4, Q3.2.2, Customization
|
|
274
|
2793 @unnumberedsubsec Q3.2.3: How can I set the colors when highlighting a region?
|
|
82
|
2794
|
|
|
2795 How can I set the background/foreground colors when highlighting a
|
|
|
2796 region?
|
|
|
2797
|
|
|
2798 You can change the face @code{zmacs-region} either in your
|
|
|
2799 @file{.Xdefaults}:
|
|
|
2800
|
|
|
2801 @example
|
|
|
2802 Emacs.zmacs-region.attributeForeground: firebrick
|
|
|
2803 Emacs.zmacs-region.attributeBackground: lightseagreen
|
|
16
|
2804 @end example
|
|
|
2805
|
|
82
|
2806 or in your @file{.emacs}:
|
|
|
2807
|
|
|
2808 @lisp
|
|
282
|
2809 (set-face-background 'zmacs-region "red")
|
|
82
|
2810 (set-face-foreground 'zmacs-region "yellow")
|
|
|
2811 @end lisp
|
|
|
2812
|
|
|
2813 @node Q3.2.4, Q3.2.5, Q3.2.3, Customization
|
|
274
|
2814 @unnumberedsubsec Q3.2.4: How can I limit color map usage?
|
|
82
|
2815
|
|
|
2816 I'm using Netscape (or another color grabber like XEmacs);
|
|
|
2817 is there anyway to limit the number of available colors in the color map?
|
|
|
2818
|
|
126
|
2819 XEmacs 19.13 didn't have such a mechanism (unlike netscape, or other
|
|
82
|
2820 color-hogs). One solution is to start XEmacs prior to netscape, since
|
|
|
2821 this will prevent Netscape from grabbing all colors (but Netscape will
|
|
|
2822 complain). You can use the flags for Netscape, like -mono, -ncols <#>
|
|
|
2823 or -install (for mono, limiting to <#> colors, or for using a private
|
|
|
2824 color map). Since Netscape will take the entire colormap and never
|
|
|
2825 release it, the only reasonable way to run it is with @samp{-install}.
|
|
|
2826
|
|
|
2827 If you have the money, another solution would be to use a truecolor or
|
|
|
2828 direct color video.
|
|
|
2829
|
|
|
2830 Starting with XEmacs 19.14, XEmacs uses the closest available color if
|
|
|
2831 the colormap is full, so it's O.K. now to start Netscape first.
|
|
|
2832
|
|
282
|
2833 @node Q3.2.5, Q3.2.6, Q3.2.4, Customization
|
|
274
|
2834 @unnumberedsubsec Q3.2.5: My tty supports color, but XEmacs doesn't use them.
|
|
82
|
2835
|
|
|
2836 XEmacs tries to automatically determine whether your tty supports color,
|
|
|
2837 but sometimes guesses wrong. In that case, you can make XEmacs Do The
|
|
|
2838 Right Thing using this Lisp code:
|
|
|
2839
|
|
|
2840 @lisp
|
|
|
2841 (if (eq 'tty (device-type))
|
|
|
2842 (set-device-class nil 'color))
|
|
|
2843 @end lisp
|
|
|
2844
|
|
282
|
2845 @node Q3.2.6, Q3.3.1, Q3.2.5, Customization
|
|
|
2846 @unnumberedsubsec Q3.2.6: Can I have pixmap backgrounds in XEmacs?
|
|
|
2847 @c New
|
|
|
2848 @email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes:
|
|
|
2849
|
|
|
2850 @quotation
|
|
|
2851 There are several ways to do it. For example, you could specify a
|
|
|
2852 default pixmap image to use in your @file{~/.Xresources}, e.g.,
|
|
|
2853
|
|
|
2854
|
|
|
2855 @example
|
|
|
2856 Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm
|
|
|
2857 @end example
|
|
|
2858
|
|
|
2859
|
|
|
2860 and then reload ~/.Xresources and restart XEmacs. Alternatively,
|
|
|
2861 since each face can have its own pixmap background, a better way
|
|
|
2862 would be to set a face's pixmap within your XEmacs init file, e.g.,
|
|
|
2863
|
|
|
2864 @lisp
|
|
|
2865 (set-face-background-pixmap 'default "/path/to/image.xpm")
|
|
|
2866 (set-face-background-pixmap 'bold "/path/to/another_image.xpm")
|
|
|
2867 @end lisp
|
|
|
2868
|
|
|
2869 and so on. You can also do this interactively via @kbd{M-x edit-faces}.
|
|
|
2870
|
|
|
2871 @end quotation
|
|
|
2872
|
|
365
|
2873 @node Q3.3.1, Q3.3.2, Q3.2.6, Customization
|
|
282
|
2874 @unnumberedsec 3.3: The Modeline
|
|
274
|
2875 @unnumberedsubsec Q3.3.1: How can I make the modeline go away?
|
|
82
|
2876
|
|
|
2877 @lisp
|
|
|
2878 (set-specifier has-modeline-p nil)
|
|
|
2879 @end lisp
|
|
|
2880
|
|
|
2881 Starting with XEmacs 19.14 the modeline responds to mouse clicks, so if
|
|
|
2882 you haven't liked or used the modeline in the past, you might want to
|
|
|
2883 try the new version out.
|
|
|
2884
|
|
|
2885 @node Q3.3.2, Q3.3.3, Q3.3.1, Customization
|
|
274
|
2886 @unnumberedsubsec Q3.3.2: How do you have XEmacs display the line number in the modeline?
|
|
82
|
2887
|
|
|
2888 Add the following line to your @file{.emacs} file to display the
|
|
|
2889 line number:
|
|
|
2890
|
|
|
2891 @lisp
|
|
215
|
2892 (line-number-mode 1)
|
|
82
|
2893 @end lisp
|
|
|
2894
|
|
|
2895 Use the following to display the column number:
|
|
|
2896
|
|
|
2897 @lisp
|
|
215
|
2898 (column-number-mode 1)
|
|
82
|
2899 @end lisp
|
|
|
2900
|
|
215
|
2901 Or select from the @code{Options} menu
|
|
274
|
2902 @iftex
|
|
|
2903 @*
|
|
282
|
2904 @end iftex
|
|
274
|
2905 @code{Customize->Emacs->Editing->Basics->Line Number Mode}
|
|
215
|
2906 and/or
|
|
274
|
2907 @iftex
|
|
|
2908 @*
|
|
282
|
2909 @end iftex
|
|
274
|
2910 @code{Customize->Emacs->Editing->Basics->Column Number Mode}
|
|
215
|
2911
|
|
282
|
2912 Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
|
|
215
|
2913
|
|
82
|
2914 @node Q3.3.3, Q3.3.4, Q3.3.2, Customization
|
|
274
|
2915 @unnumberedsubsec Q3.3.3: How do I get XEmacs to put the time of day on the modeline?
|
|
82
|
2916
|
|
215
|
2917 Add the following line to your @file{.emacs} file to display the
|
|
|
2918 time:
|
|
|
2919
|
|
82
|
2920 @lisp
|
|
|
2921 (display-time)
|
|
|
2922 @end lisp
|
|
|
2923
|
|
215
|
2924 See @code{Customize} from the @code{Options} menu for customization.
|
|
|
2925
|
|
82
|
2926 @node Q3.3.4, Q3.3.5, Q3.3.3, Customization
|
|
274
|
2927 @unnumberedsubsec Q3.3.4: How do I turn off current chapter from AUC TeX modeline?
|
|
163
|
2928
|
|
|
2929 With AUC TeX, fast typing is hard because the current chapter, section
|
|
82
|
2930 etc. are given in the modeline. How can I turn this off?
|
|
|
2931
|
|
163
|
2932 It's not AUC TeX, it comes from @code{func-menu} in @file{func-menu.el}.
|
|
82
|
2933 Add this code to your @file{.emacs} to turn it off:
|
|
|
2934
|
|
|
2935 @lisp
|
|
|
2936 (setq fume-display-in-modeline-p nil)
|
|
|
2937 @end lisp
|
|
|
2938
|
|
|
2939 Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX
|
|
|
2940 mode:
|
|
|
2941
|
|
|
2942 @lisp
|
|
282
|
2943 (add-hook 'TeX-mode-hook
|
|
365
|
2944 '(lambda () (setq fume-display-in-modeline-p nil)))
|
|
82
|
2945 @end lisp
|
|
|
2946
|
|
274
|
2947 @email{dhughes@@origin-at.co.uk, David Hughes} writes:
|
|
82
|
2948
|
|
|
2949 @quotation
|
|
|
2950 If you have 19.14 or later, try this instead; you'll still get the
|
|
|
2951 function name displayed in the modeline, but it won't attempt to keep
|
|
|
2952 track when you modify the file. To refresh when it gets out of synch,
|
|
|
2953 you simply need click on the @samp{Rescan Buffer} option in the
|
|
|
2954 function-menu.
|
|
|
2955
|
|
|
2956 @lisp
|
|
|
2957 (setq-default fume-auto-rescan-buffer-p nil)
|
|
|
2958 @end lisp
|
|
|
2959 @end quotation
|
|
|
2960
|
|
|
2961 @node Q3.3.5, Q3.4.1, Q3.3.4, Customization
|
|
274
|
2962 @unnumberedsubsec Q3.3.5: How can one change the modeline color based on the mode used?
|
|
82
|
2963
|
|
|
2964 You can use something like the following:
|
|
|
2965
|
|
|
2966 @lisp
|
|
282
|
2967 (add-hook 'lisp-mode-hook
|
|
163
|
2968 (lambda ()
|
|
|
2969 (set-face-background 'modeline "red" (current-buffer))))
|
|
82
|
2970 @end lisp
|
|
|
2971
|
|
|
2972 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline
|
|
|
2973 colors change from the default set in your @file{.emacs}. The change
|
|
|
2974 will only be made in the buffer you just entered (which contains the
|
|
|
2975 Lisp file you are editing) and will not affect the modeline colors
|
|
|
2976 anywhere else.
|
|
|
2977
|
|
|
2978 Notes:
|
|
|
2979
|
|
|
2980 @itemize @bullet
|
|
|
2981
|
|
|
2982 @item
|
|
|
2983 The hook is the mode name plus @code{-hook}. eg. c-mode-hook,
|
|
|
2984 c++-mode-hook, emacs-lisp-mode-hook (used for your @file{.emacs} or a
|
|
|
2985 @file{xx.el} file), lisp-interaction-mode-hook (the @samp{*scratch*}
|
|
|
2986 buffer), text-mode-hook, etc.
|
|
|
2987
|
|
|
2988 @item
|
|
|
2989 Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)},
|
|
|
2990 otherwise you will erase anything that anybody has already put on the
|
|
|
2991 hook.
|
|
|
2992
|
|
|
2993 @item
|
|
|
2994 You can also do @code{(set-face-font 'modeline @var{font})},
|
|
|
2995 eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*"
|
|
|
2996 (current-buffer))} if you wish the modeline font to vary based on the
|
|
|
2997 current mode.
|
|
|
2998 @end itemize
|
|
|
2999
|
|
126
|
3000 This works in 19.15 as well, but there are additional modeline faces,
|
|
82
|
3001 @code{modeline-buffer-id}, @code{modeline-mousable}, and
|
|
|
3002 @code{modeline-mousable-minor-mode}, which you may want to customize.
|
|
|
3003
|
|
|
3004 @node Q3.4.1, Q3.4.2, Q3.3.5, Customization
|
|
274
|
3005 @unnumberedsec 3.4: Multiple Device Support
|
|
|
3006 @unnumberedsubsec Q3.4.1: How do I open a frame on another screen of my multi-headed display?
|
|
82
|
3007
|
|
163
|
3008 The support for this was revamped for 19.14. Use the command
|
|
82
|
3009 @kbd{M-x make-frame-on-display}. This command is also on the File menu
|
|
|
3010 in the menubar.
|
|
|
3011
|
|
163
|
3012 XEmacs 19.14 and later also have the command @code{make-frame-on-tty}
|
|
|
3013 which will establish a connection to any tty-like device. Opening the
|
|
|
3014 TTY devices should be left to @code{gnuclient}, though.
|
|
82
|
3015
|
|
|
3016 @node Q3.4.2, Q3.5.1, Q3.4.1, Customization
|
|
274
|
3017 @unnumberedsubsec Q3.4.2: Can I really connect to a running XEmacs after calling up over a modem? How?
|
|
82
|
3018
|
|
|
3019 If you're not running at least XEmacs 19.14, you can't. Otherwise check
|
|
163
|
3020 out the @code{gnuattach} program supplied with XEmacs. Starting with
|
|
227
|
3021 XEmacs 20.3, @code{gnuattach} and @code{gnudoit} functionality is
|
|
163
|
3022 provided by @code{gnuclient}.
|
|
82
|
3023
|
|
227
|
3024 Also @xref{Q5.0.12}.
|
|
|
3025
|
|
82
|
3026 @node Q3.5.1, Q3.5.2, Q3.4.2, Customization
|
|
274
|
3027 @unnumberedsec 3.5: The Keyboard
|
|
|
3028 @unnumberedsubsec Q3.5.1: How can I bind complex functions (or macros) to keys?
|
|
82
|
3029
|
|
|
3030 As an example, say you want the @kbd{paste} key on a Sun keyboard to
|
|
|
3031 insert the current Primary X selection at point. You can accomplish this
|
|
|
3032 with:
|
|
|
3033
|
|
|
3034 @lisp
|
|
|
3035 (define-key global-map [f18] 'x-insert-selection)
|
|
|
3036 @end lisp
|
|
|
3037
|
|
|
3038 However, this only works if there is a current X selection (the
|
|
|
3039 selection will be highlighted). The functionality I like is for the
|
|
|
3040 @kbd{paste} key to insert the current X selection if there is one,
|
|
|
3041 otherwise insert the contents of the clipboard. To do this you need to
|
|
|
3042 pass arguments to @code{x-insert-selection}. This is done by wrapping
|
|
|
3043 the call in a 'lambda form:
|
|
|
3044
|
|
|
3045 @lisp
|
|
163
|
3046 (global-set-key [f18]
|
|
274
|
3047 (lambda () (interactive) (x-insert-selection t nil)))
|
|
82
|
3048 @end lisp
|
|
|
3049
|
|
|
3050 This binds the f18 key to a @dfn{generic} functional object. The
|
|
|
3051 interactive spec is required because only interactive functions can be
|
|
163
|
3052 bound to keys.
|
|
82
|
3053
|
|
|
3054 For the FAQ example you could use:
|
|
|
3055
|
|
|
3056 @lisp
|
|
|
3057 (global-set-key [(control ?.)]
|
|
274
|
3058 (lambda () (interactive) (scroll-up 1)))
|
|
365
|
3059 (global-set-key [(control ?;)]
|
|
|
3060 (lambda () (interactive) (scroll-up -1)))
|
|
82
|
3061 @end lisp
|
|
|
3062
|
|
|
3063 This is fine if you only need a few functions within the lambda body.
|
|
|
3064 If you're doing more it's cleaner to define a separate function as in
|
|
335
|
3065 question 3.5.3 (@pxref{Q3.5.3}).
|
|
82
|
3066
|
|
|
3067 @node Q3.5.2, Q3.5.3, Q3.5.1, Customization
|
|
274
|
3068 @unnumberedsubsec Q3.5.2: How can I stop down-arrow from adding empty lines to the bottom of my buffers?
|
|
82
|
3069
|
|
|
3070 Add the following line to your @file{.emacs} file:
|
|
|
3071
|
|
|
3072 @lisp
|
|
|
3073 (setq next-line-add-newlines nil)
|
|
|
3074 @end lisp
|
|
|
3075
|
|
163
|
3076 This has been the default setting in XEmacs for some time.
|
|
|
3077
|
|
82
|
3078 @node Q3.5.3, Q3.5.4, Q3.5.2, Customization
|
|
274
|
3079 @unnumberedsubsec Q3.5.3: How do I bind C-. and C-; to scroll one line up and down?
|
|
|
3080
|
|
367
|
3081 Add the following (Thanks to @email{Mly@@POBox.COM, Richard Mlynarik} and
|
|
274
|
3082 @email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}:
|
|
82
|
3083
|
|
|
3084 @lisp
|
|
|
3085 (defun scroll-up-one-line ()
|
|
|
3086 (interactive)
|
|
|
3087 (scroll-up 1))
|
|
|
3088
|
|
|
3089 (defun scroll-down-one-line ()
|
|
|
3090 (interactive)
|
|
|
3091 (scroll-down 1))
|
|
|
3092
|
|
274
|
3093 (global-set-key [(control ?.)] 'scroll-up-one-line) ; C-.
|
|
365
|
3094 (global-set-key [(control ?;)] 'scroll-down-one-line) ; C-;
|
|
82
|
3095 @end lisp
|
|
|
3096
|
|
|
3097 The key point is that you can only bind simple functions to keys; you
|
|
|
3098 can not bind a key to a function that you're also passing arguments to.
|
|
335
|
3099 (@pxref{Q3.5.1} for a better answer).
|
|
82
|
3100
|
|
|
3101 @node Q3.5.4, Q3.5.5, Q3.5.3, Customization
|
|
274
|
3102 @unnumberedsubsec Q3.5.4: Globally binding @kbd{Delete}?
|
|
82
|
3103
|
|
|
3104 I cannot manage to globally bind my @kbd{Delete} key to something other
|
|
|
3105 than the default. How does one do this?
|
|
|
3106
|
|
|
3107 @lisp
|
|
163
|
3108 (defun foo ()
|
|
82
|
3109 (interactive)
|
|
163
|
3110 (message "You hit DELETE"))
|
|
|
3111
|
|
|
3112 (global-set-key 'delete 'foo)
|
|
82
|
3113 @end lisp
|
|
|
3114
|
|
|
3115 However, some modes explicitly bind @kbd{Delete}, so you would need to
|
|
227
|
3116 add a hook that does @code{local-set-key} for them. If what you want to
|
|
82
|
3117 do is make the Backspace and Delete keys work more PC/Motif-like, then
|
|
215
|
3118 take a look at the @file{delbs.el} package.
|
|
82
|
3119
|
|
|
3120 New in XEmacs 19.14 is a variable called @code{key-translation-map}
|
|
227
|
3121 which makes it easier to bind @kbd{Delete}. @file{delbs.el} is a
|
|
82
|
3122 good example of how to do this correctly.
|
|
|
3123
|
|
215
|
3124 Also @xref{Q3.5.10}.
|
|
|
3125
|
|
82
|
3126 @node Q3.5.5, Q3.5.6, Q3.5.4, Customization
|
|
274
|
3127 @unnumberedsubsec Q3.5.5: Scrolling one line at a time.
|
|
82
|
3128
|
|
|
3129 Can the cursor keys scroll the screen a line at a time, rather than the
|
|
|
3130 default half page jump? I tend it to find it disorienting.
|
|
|
3131
|
|
|
3132 Try this:
|
|
|
3133
|
|
|
3134 @lisp
|
|
|
3135 (defun scroll-one-line-up (&optional arg)
|
|
|
3136 "Scroll the selected window up (forward in the text) one line (or N lines)."
|
|
|
3137 (interactive "p")
|
|
|
3138 (scroll-up (or arg 1)))
|
|
|
3139
|
|
|
3140 (defun scroll-one-line-down (&optional arg)
|
|
|
3141 "Scroll the selected window down (backward in the text) one line (or N)."
|
|
|
3142 (interactive "p")
|
|
|
3143 (scroll-down (or arg 1)))
|
|
|
3144
|
|
163
|
3145 (global-set-key [up] 'scroll-one-line-up)
|
|
|
3146 (global-set-key [down] 'scroll-one-line-down)
|
|
82
|
3147 @end lisp
|
|
|
3148
|
|
|
3149 The following will also work but will affect more than just the cursor
|
|
|
3150 keys (i.e. @kbd{C-n} and @kbd{C-p}):
|
|
|
3151
|
|
|
3152 @lisp
|
|
|
3153 (setq scroll-step 1)
|
|
|
3154 @end lisp
|
|
|
3155
|
|
227
|
3156 Starting with XEmacs-20.3 you can also change this with Customize.
|
|
215
|
3157 Select from the @code{Options} menu
|
|
227
|
3158 @code{Customize->Emacs->Environment->Windows->Scroll Step...} or type
|
|
282
|
3159 @kbd{M-x customize @key{RET} windows @key{RET}}.
|
|
215
|
3160
|
|
82
|
3161 @node Q3.5.6, Q3.5.7, Q3.5.5, Customization
|
|
274
|
3162 @unnumberedsubsec Q3.5.6: How to map @kbd{Help} key alone on Sun type4 keyboard?
|
|
82
|
3163
|
|
|
3164 The following works in GNU Emacs 19:
|
|
|
3165
|
|
|
3166 @lisp
|
|
274
|
3167 (global-set-key [help] 'help-command);; Help
|
|
82
|
3168 @end lisp
|
|
|
3169
|
|
126
|
3170 The following works in XEmacs 19.15 with the addition of shift:
|
|
82
|
3171
|
|
|
3172 @lisp
|
|
274
|
3173 (global-set-key [(shift help)] 'help-command);; Help
|
|
82
|
3174 @end lisp
|
|
|
3175
|
|
|
3176 But it doesn't work alone. This is in the file @file{PROBLEMS} which
|
|
|
3177 should have come with your XEmacs installation: @emph{Emacs ignores the
|
|
|
3178 @kbd{help} key when running OLWM}.
|
|
|
3179
|
|
|
3180 OLWM grabs the @kbd{help} key, and retransmits it to the appropriate
|
|
282
|
3181 client using
|
|
274
|
3182 @iftex
|
|
|
3183 @*
|
|
282
|
3184 @end iftex
|
|
274
|
3185 @code{XSendEvent}. Allowing Emacs to react to synthetic
|
|
82
|
3186 events is a security hole, so this is turned off by default. You can
|
|
|
3187 enable it by setting the variable @code{x-allow-sendevents} to t. You
|
|
|
3188 can also cause fix this by telling OLWM to not grab the help key, with
|
|
|
3189 the null binding @code{OpenWindows.KeyboardCommand.Help:}.
|
|
|
3190
|
|
|
3191 @node Q3.5.7, Q3.5.8, Q3.5.6, Customization
|
|
274
|
3192 @unnumberedsubsec Q3.5.7: How can you type in special characters in XEmacs?
|
|
282
|
3193 @c Changed
|
|
227
|
3194 One way is to use the package @code{x-compose}. Then you can use
|
|
82
|
3195 sequences like @kbd{Compose " a} to get ä, etc.
|
|
|
3196
|
|
227
|
3197 Another way is to use the @code{iso-insert} package, provided in XEmacs
|
|
|
3198 19.15 and later. Then you can use sequences like @kbd{C-x 8 " a} to get
|
|
|
3199 ä, etc.
|
|
82
|
3200
|
|
282
|
3201 @email{glynn@@sensei.co.uk, Glynn Clements} writes:
|
|
|
3202
|
|
|
3203 @quotation
|
|
|
3204 It depends upon your X server.
|
|
|
3205
|
|
|
3206 Generally, the simplest way is to define a key as Multi_key with
|
|
|
3207 xmodmap, e.g.
|
|
|
3208 @c hey, show some respect, willya -- there's xkeycaps, isn't there? --
|
|
|
3209 @c chr ;)
|
|
369
|
3210 @c Fixed. sjt ;)
|
|
282
|
3211 @example
|
|
365
|
3212 xmodmap -e 'keycode 0xff20 = Multi_key'
|
|
282
|
3213 @end example
|
|
|
3214
|
|
|
3215 You will need to pick an appropriate keycode. Use xev to find out the
|
|
|
3216 keycodes for each key.
|
|
|
3217
|
|
|
3218 [NB: On a `Windows' keyboard, recent versions of XFree86 automatically
|
|
|
3219 define the right `Windows' key as Multi_key'.]
|
|
|
3220
|
|
|
3221 Once you have Multi_key defined, you can use e.g.
|
|
|
3222 @example
|
|
365
|
3223 Multi a ' => á
|
|
|
3224 Multi e " => ë
|
|
|
3225 Multi c , => ç
|
|
282
|
3226 @end example
|
|
|
3227
|
|
|
3228 etc.
|
|
|
3229
|
|
|
3230 Also, recent versions of XFree86 define various AltGr-<key>
|
|
|
3231 combinations as dead keys, i.e.
|
|
|
3232 @example
|
|
365
|
3233 AltGr [ => dead_diaeresis
|
|
|
3234 AltGr ] => dead_tilde
|
|
|
3235 AltGr ; => dead_acute
|
|
282
|
3236 @end example
|
|
|
3237 etc.
|
|
|
3238
|
|
|
3239 Running @samp{xmodmap -pk} will list all of the defined keysyms.
|
|
|
3240 @end quotation
|
|
|
3241
|
|
369
|
3242 Actually, the simplest way to define keys on the X server is to use
|
|
|
3243 XKeyCaps (@pxref{Q3.5.12}), which provides an efficient GUI interface
|
|
|
3244 and will write correct @samp{xmodmap} scripts for you.
|
|
|
3245
|
|
82
|
3246 @node Q3.5.8, Q3.5.9, Q3.5.7, Customization
|
|
274
|
3247 @unnumberedsubsec Q3.5.8: Why does @code{(global-set-key [delete-forward] 'delete-char)} complain?
|
|
82
|
3248
|
|
|
3249 Why does @code{(define-key global-map [ delete-forward ] 'delete-char)}
|
|
|
3250 complain of not being able to bind an unknown key?
|
|
|
3251
|
|
|
3252 Try this instead:
|
|
|
3253
|
|
|
3254 @lisp
|
|
|
3255 (define-key global-map [delete_forward] 'delete-char)
|
|
|
3256 @end lisp
|
|
|
3257
|
|
|
3258 and it will work.
|
|
|
3259
|
|
|
3260 What you are seeing above is a bug due to code that is trying to check
|
|
|
3261 for GNU Emacs syntax like:
|
|
|
3262
|
|
|
3263 (define-key global-map [C-M-a] 'delete-char)
|
|
|
3264
|
|
|
3265 which otherwise would cause no errors but would not result in the
|
|
|
3266 expected behavior.
|
|
|
3267
|
|
|
3268 This bug has been fixed in 19.14.
|
|
|
3269
|
|
|
3270 @node Q3.5.9, Q3.5.10, Q3.5.8, Customization
|
|
274
|
3271 @unnumberedsubsec Q3.5.9: How do I make the Delete key delete forward?
|
|
82
|
3272
|
|
227
|
3273 With XEmacs-20.2 use the @code{delbs} package:
|
|
82
|
3274
|
|
|
3275 @lisp
|
|
163
|
3276 (require 'delbs)
|
|
82
|
3277 @end lisp
|
|
|
3278
|
|
163
|
3279 This will give you the functions @code{delbs-enable-delete-forward} to
|
|
|
3280 set things up, and @code{delbs-disable-delete-forward} to revert to
|
|
227
|
3281 ``normal'' behavior. Note that @code{delbackspace} package is obsolete.
|
|
|
3282
|
|
|
3283 Starting with XEmacs-20.3 better solution is to set variable
|
|
|
3284 @code{delete-key-deletes-forward} to t. You can also change this with
|
|
|
3285 Customize. Select from the @code{Options} menu
|
|
|
3286 @code{Customize->Emacs->Editing->Basics->Delete Key Deletes Forward} or
|
|
282
|
3287 type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
|
|
215
|
3288
|
|
82
|
3289 Also @xref{Q3.5.4}.
|
|
|
3290
|
|
282
|
3291 @node Q3.5.10, Q3.5.11, Q3.5.9, Customization
|
|
274
|
3292 @unnumberedsubsec Q3.5.10: Can I turn on @dfn{sticky} modifier keys?
|
|
82
|
3293
|
|
|
3294 Yes, with @code{(setq modifier-keys-are-sticky t)}. This will give the
|
|
|
3295 effect of being able to press and release Shift and have the next
|
|
|
3296 character typed come out in upper case. This will affect all the other
|
|
|
3297 modifier keys like Control and Meta as well.
|
|
|
3298
|
|
359
|
3299 @email{ben@@xemacs.org, Ben Wing} writes:
|
|
82
|
3300
|
|
|
3301 @quotation
|
|
|
3302 One thing about the sticky modifiers is that if you move the mouse out
|
|
163
|
3303 of the frame and back in, it cancels all currently ``stuck'' modifiers.
|
|
82
|
3304 @end quotation
|
|
|
3305
|
|
369
|
3306 @node Q3.5.11, Q3.5.12, Q3.5.10, Customization
|
|
282
|
3307 @unnumberedsubsec Q3.5.11: How do I map the arrow keys?
|
|
|
3308 @c New
|
|
|
3309 Say you want to map @kbd{C-@key{right}} to forward-word:
|
|
|
3310
|
|
|
3311 @email{sds@@usa.net, Sam Steingold} writes:
|
|
|
3312
|
|
|
3313 @quotation
|
|
|
3314 @lisp
|
|
|
3315 ; both XEmacs and Emacs
|
|
|
3316 (define-key global-map [(control right)] 'forward-word)
|
|
|
3317 @end lisp
|
|
|
3318 or
|
|
|
3319 @lisp
|
|
|
3320 ; Emacs only
|
|
|
3321 (define-key global-map [C-right] 'forward-word)
|
|
|
3322 @end lisp
|
|
|
3323 or
|
|
|
3324 @lisp
|
|
|
3325 ; ver > 20, both
|
|
|
3326 (define-key global-map (kbd "C-<right>") 'forward-word)
|
|
|
3327 @end lisp
|
|
|
3328 @end quotation
|
|
|
3329
|
|
369
|
3330 @node Q3.5.12, Q3.6.1, Q3.5.11, Customization
|
|
|
3331 @unnumberedsubsec Q3.5.12: XEmacs complains about my xmodmap (I hate the default X keymap).
|
|
|
3332 @c New
|
|
|
3333
|
|
|
3334 Get XKeyCaps from @uref{http://www.jwz.org/xkeycaps/}. It knows more
|
|
|
3335 than 200 keyboards by name, and provides nice pictures so you can tell
|
|
|
3336 if yours is a lookalike OEM version. It sports an efficient GUI
|
|
|
3337 interface for remapping, and it knows how to write correct
|
|
|
3338 @samp{xmodmap} scripts.
|
|
|
3339
|
|
|
3340 Most Linux and BSD distributions provide packages or ports.
|
|
|
3341
|
|
|
3342 If you haven't tried XKeyCaps for your X11 keymapping problems, then
|
|
|
3343 you're wasting your time. It is highly unlikely that a human being will
|
|
|
3344 be able to give you as good advice as XKeyCaps will for most problems.
|
|
|
3345 Even XKeyCaps's author has forgotten the details of the X11 keyboard
|
|
|
3346 mechanism. There are a few problems it can't handle, but try it first.
|
|
|
3347
|
|
|
3348
|
|
|
3349
|
|
|
3350 @node Q3.6.1, Q3.6.2, Q3.5.12, Customization
|
|
274
|
3351 @unnumberedsec 3.6: The Cursor
|
|
|
3352 @unnumberedsubsec Q3.6.1: Is there a way to make the bar cursor thicker?
|
|
82
|
3353
|
|
|
3354 I'd like to have the bar cursor a little thicker, as I tend to "lose" it
|
|
|
3355 often.
|
|
|
3356
|
|
|
3357 For a 1 pixel bar cursor, use:
|
|
|
3358
|
|
|
3359 @lisp
|
|
|
3360 (setq bar-cursor t)
|
|
|
3361 @end lisp
|
|
|
3362
|
|
|
3363 For a 2 pixel bar cursor, use:
|
|
|
3364
|
|
|
3365 @lisp
|
|
|
3366 (setq bar-cursor 'anything-else)
|
|
|
3367 @end lisp
|
|
|
3368
|
|
227
|
3369 Starting with XEmacs-20.3 you can also change these with Customize.
|
|
215
|
3370 Select from the @code{Options} menu
|
|
227
|
3371 @code{Customize->Emacs->Environment->Display->Bar Cursor...} or type
|
|
282
|
3372 @kbd{M-x customize @key{RET} display @key{RET}}.
|
|
215
|
3373
|
|
82
|
3374 You can use a color to make it stand out better:
|
|
|
3375
|
|
|
3376 @example
|
|
365
|
3377 Emacs*cursorColor: Red
|
|
82
|
3378 @end example
|
|
|
3379
|
|
|
3380 @node Q3.6.2, Q3.6.3, Q3.6.1, Customization
|
|
274
|
3381 @unnumberedsubsec Q3.6.2: Is there a way to get back the block cursor?
|
|
82
|
3382
|
|
|
3383 @lisp
|
|
|
3384 (setq bar-cursor nil)
|
|
|
3385 @end lisp
|
|
|
3386
|
|
227
|
3387 Starting with XEmacs-20.3 you can also change this with Customize.
|
|
215
|
3388 Select from the @code{Options} menu
|
|
227
|
3389 @code{Customize->Emacs->Environment->Display->Bar Cursor...} or type
|
|
282
|
3390 @kbd{M-x customize @key{RET} display @key{RET}}.
|
|
215
|
3391
|
|
82
|
3392 @node Q3.6.3, Q3.7.1, Q3.6.2, Customization
|
|
274
|
3393 @unnumberedsubsec Q3.6.3: Can I make the cursor blink?
|
|
82
|
3394
|
|
|
3395 If you are running a version of XEmacs older than 19.14, no. Otherwise
|
|
|
3396 you can do the following:
|
|
|
3397
|
|
|
3398 @lisp
|
|
|
3399 (blink-cursor-mode)
|
|
|
3400 @end lisp
|
|
|
3401
|
|
|
3402 This function toggles between a steady cursor and a blinking cursor.
|
|
|
3403 You may also set this mode from the menu bar by selecting @samp{Options
|
|
227
|
3404 => Frame Appearance => Blinking Cursor}. Remember to save options.
|
|
82
|
3405
|
|
|
3406 @node Q3.7.1, Q3.7.2, Q3.6.3, Customization
|
|
274
|
3407 @unnumberedsec 3.7: The Mouse and Highlighting
|
|
|
3408 @unnumberedsubsec Q3.7.1: How can I turn off Mouse pasting?
|
|
82
|
3409
|
|
|
3410 I keep hitting the middle mouse button by accident and getting stuff
|
|
|
3411 pasted into my buffer so how can I turn this off?
|
|
|
3412
|
|
|
3413 Here is an alternative binding, whereby the middle mouse button selects
|
|
|
3414 (but does not cut) the expression under the mouse. Clicking middle on a
|
|
|
3415 left or right paren will select to the matching one. Note that you can
|
|
|
3416 use @code{define-key} or @code{global-set-key}.
|
|
|
3417
|
|
|
3418 @lisp
|
|
163
|
3419 (defun mouse-set-point-and-select (event)
|
|
82
|
3420 "Sets the point at the mouse location, then marks following form"
|
|
|
3421 (interactive "@@e")
|
|
|
3422 (mouse-set-point event)
|
|
163
|
3423 (mark-sexp 1))
|
|
|
3424 (define-key global-map [button2] 'mouse-set-point-and-select)
|
|
82
|
3425 @end lisp
|
|
|
3426
|
|
|
3427 @node Q3.7.2, Q3.7.3, Q3.7.1, Customization
|
|
274
|
3428 @unnumberedsubsec Q3.7.2: How do I set control/meta/etc modifiers on mouse buttons?
|
|
82
|
3429
|
|
227
|
3430 Use, for instance, @code{[(meta button1)]}. For example, here is a common
|
|
|
3431 setting for Common Lisp programmers who use the bundled @code{ilisp}
|
|
|
3432 package, whereby meta-button1 on a function name will find the file where
|
|
|
3433 the function name was defined, and put you at that location in the source
|
|
|
3434 file.
|
|
82
|
3435
|
|
|
3436 [Inside a function that gets called by the lisp-mode-hook and
|
|
|
3437 ilisp-mode-hook]
|
|
|
3438
|
|
|
3439 @lisp
|
|
|
3440 (local-set-key [(meta button1)] 'edit-definitions-lisp)
|
|
|
3441 @end lisp
|
|
|
3442
|
|
|
3443 @node Q3.7.3, Q3.7.4, Q3.7.2, Customization
|
|
274
|
3444 @unnumberedsubsec Q3.7.3: Clicking the left button does not do anything in buffer list.
|
|
82
|
3445
|
|
|
3446 I do @kbd{C-x C-b} to get a list of buffers and the entries get
|
|
|
3447 highlighted when I move the mouse over them but clicking the left mouse
|
|
|
3448 does not do anything.
|
|
|
3449
|
|
|
3450 Use the middle mouse button.
|
|
|
3451
|
|
|
3452 @node Q3.7.4, Q3.7.5, Q3.7.3, Customization
|
|
274
|
3453 @unnumberedsubsec Q3.7.4: How can I get a list of buffers when I hit mouse button 3?
|
|
82
|
3454
|
|
163
|
3455 The following code will replace the default popup on button3:
|
|
82
|
3456
|
|
|
3457 @lisp
|
|
163
|
3458 (global-set-key [button3] 'popup-buffer-menu)
|
|
82
|
3459 @end lisp
|
|
|
3460
|
|
|
3461 @node Q3.7.5, Q3.7.6, Q3.7.4, Customization
|
|
274
|
3462 @unnumberedsubsec Q3.7.5: Why does cut-and-paste not work between XEmacs and a cmdtool?
|
|
82
|
3463
|
|
|
3464 We don't know. It's a bug. There does seem to be a work-around,
|
|
|
3465 however. Try running xclipboard first. It appears to fix the problem
|
|
|
3466 even if you exit it. (This should be mostly fixed in 19.13, but we
|
|
|
3467 haven't yet verified that).
|
|
|
3468
|
|
|
3469 @node Q3.7.6, Q3.7.7, Q3.7.5, Customization
|
|
274
|
3470 @unnumberedsubsec Q3.7.6: How I can set XEmacs up so that it pastes where the text cursor is?
|
|
82
|
3471
|
|
|
3472 By default XEmacs pastes X selections where the mouse pointer is. How
|
|
|
3473 do I disable this?
|
|
|
3474
|
|
|
3475 Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank
|
|
282
|
3476 @key{RET}}.
|
|
82
|
3477
|
|
|
3478 To get XEmacs to paste at the text cursor, add this your @file{.emacs}:
|
|
|
3479
|
|
|
3480 @lisp
|
|
|
3481 (setq mouse-yank-at-point t)
|
|
|
3482 @end lisp
|
|
|
3483
|
|
227
|
3484 Starting with XEmacs-20.2 you can also change this with Customize.
|
|
|
3485 Select from the @code{Options} menu
|
|
|
3486 @code{Customize->Emacs->Editing->Mouse->Yank At Point...} or type
|
|
282
|
3487 @kbd{M-x customize @key{RET} mouse @key{RET}}.
|
|
227
|
3488
|
|
82
|
3489 @node Q3.7.7, Q3.7.8, Q3.7.6, Customization
|
|
274
|
3490 @unnumberedsubsec Q3.7.7: How do I select a rectangular region?
|
|
82
|
3491
|
|
|
3492 Just select the region normally, then use the rectangle commands (e.g.
|
|
|
3493 @code{kill-rectangle} on it. The region does not highlight as a
|
|
|
3494 rectangle, but the commands work just fine.
|
|
|
3495
|
|
227
|
3496 To actually sweep out rectangular regions with the mouse you can use
|
|
|
3497 @code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}.
|
|
|
3498 Then use rectangle commands.
|
|
|
3499
|
|
|
3500 You can also do the following to change default behavior to sweep out
|
|
|
3501 rectangular regions:
|
|
82
|
3502
|
|
|
3503 @lisp
|
|
|
3504 (setq mouse-track-rectangle-p t)
|
|
|
3505 @end lisp
|
|
|
3506
|
|
227
|
3507 Starting with XEmacs-20.2 you can also change this with Customize.
|
|
|
3508 Select from the @code{Options} menu
|
|
|
3509 @code{Customize->Emacs->Editing->Mouse->Track Rectangle...} or type
|
|
282
|
3510 @kbd{M-x customize @key{RET} mouse @key{RET}}.
|
|
227
|
3511
|
|
82
|
3512
|
|
|
3513 @example
|
|
|
3514 mouse-track-do-rectangle: (event)
|
|
|
3515 -- an interactive compiled Lisp function.
|
|
|
3516 Like `mouse-track' but selects rectangles instead of regions.
|
|
|
3517 @end example
|
|
|
3518
|
|
|
3519 @node Q3.7.8, Q3.8.1, Q3.7.7, Customization
|
|
274
|
3520 @unnumberedsubsec Q3.7.8: Why does @kbd{M-w} take so long?
|
|
82
|
3521
|
|
|
3522 It actually doesn't. It leaves the region visible for a second so that
|
|
|
3523 you can see what area is being yanked. If you start working, though, it
|
|
|
3524 will immediately complete its operation. In other words, it will only
|
|
|
3525 delay for a second if you let it.
|
|
|
3526
|
|
|
3527 @node Q3.8.1, Q3.8.2, Q3.7.8, Customization
|
|
274
|
3528 @unnumberedsec 3.8: The Menubar and Toolbar
|
|
|
3529 @unnumberedsubsec Q3.8.1: How do I get rid of the menu (or menubar)?
|
|
82
|
3530
|
|
|
3531 If you are running XEmacs 19.13 and earlier, add this command to your
|
|
|
3532 @file{.emacs}.
|
|
|
3533
|
|
|
3534 @lisp
|
|
|
3535 (set-menubar nil)
|
|
|
3536 @end lisp
|
|
|
3537
|
|
|
3538 Starting with XEmacs 19.14 the preferred method is:
|
|
|
3539
|
|
|
3540 @lisp
|
|
|
3541 (set-specifier menubar-visible-p nil)
|
|
|
3542 @end lisp
|
|
|
3543
|
|
|
3544 @node Q3.8.2, Q3.8.3, Q3.8.1, Customization
|
|
274
|
3545 @unnumberedsubsec Q3.8.2: Can I customize the basic menubar?
|
|
82
|
3546
|
|
|
3547 For an extensive menubar, add this line to your @file{.emacs}:
|
|
|
3548
|
|
|
3549 @lisp
|
|
|
3550 (load "big-menubar")
|
|
|
3551 @end lisp
|
|
|
3552
|
|
|
3553 If you'd like to write your own, this file provides as good a set of
|
|
|
3554 examples as any to start from. The file is located in
|
|
|
3555 @file{lisp/packages/big-menubar.el} in the XEmacs installation
|
|
|
3556 directory.
|
|
|
3557
|
|
|
3558 @node Q3.8.3, Q3.8.4, Q3.8.2, Customization
|
|
274
|
3559 @unnumberedsubsec Q3.8.3: How do I control how many buffers are listed in the menu @code{Buffers List}?
|
|
82
|
3560
|
|
|
3561 Add the following to your @file{.emacs} (suit to fit):
|
|
|
3562
|
|
|
3563 @lisp
|
|
|
3564 (setq buffers-menu-max-size 20)
|
|
|
3565 @end lisp
|
|
|
3566
|
|
|
3567 For no limit, use an argument of @samp{nil}.
|
|
|
3568
|
|
227
|
3569 Starting with XEmacs-20.3 you can also change this with Customize.
|
|
|
3570 Select from the @code{Options} menu
|
|
|
3571 @code{Customize->Emacs->Environment->Menu->Buffers Menu->Max Size...} or
|
|
282
|
3572 type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}.
|
|
227
|
3573
|
|
82
|
3574 @node Q3.8.4, Q3.8.5, Q3.8.3, Customization
|
|
274
|
3575 @unnumberedsubsec Q3.8.4: Resources like @code{Emacs*menubar*font} are not working?
|
|
82
|
3576
|
|
|
3577 I am trying to use a resource like @code{Emacs*menubar*font} to set the
|
|
|
3578 font of the menubar but it's not working.
|
|
|
3579
|
|
|
3580 If you are using the real Motif menubar, this resource is not
|
|
|
3581 recognized; you have to say:
|
|
|
3582
|
|
|
3583 @example
|
|
|
3584 Emacs*menubar*fontList: FONT
|
|
|
3585 @end example
|
|
|
3586
|
|
|
3587 If you are using the Lucid menubar, the former resource will be
|
|
|
3588 recognized only if the latter resource is unset. This means that the
|
|
|
3589 resource
|
|
|
3590
|
|
|
3591 @example
|
|
|
3592 *fontList: FONT
|
|
|
3593 @end example
|
|
|
3594
|
|
|
3595 will override
|
|
|
3596
|
|
|
3597 @example
|
|
|
3598 Emacs*menubar*font: FONT
|
|
|
3599 @end example
|
|
|
3600
|
|
|
3601 even though the latter is more specific.
|
|
|
3602
|
|
|
3603 @node Q3.8.5, Q3.9.1, Q3.8.4, Customization
|
|
274
|
3604 @unnumberedsubsec Q3.8.5: How can I bind a key to a function to toggle the toolbar?
|
|
82
|
3605
|
|
|
3606 Try something like:
|
|
|
3607
|
|
|
3608 @lisp
|
|
163
|
3609 (defun my-toggle-toolbar ()
|
|
|
3610 (interactive)
|
|
|
3611 (set-specifier default-toolbar-visible-p
|
|
|
3612 (not (specifier-instance default-toolbar-visible-p))))
|
|
|
3613 (global-set-key "\C-xT" 'my-toggle-toolbar)
|
|
82
|
3614 @end lisp
|
|
|
3615
|
|
|
3616 There are redisplay bugs in 19.14 that may make the preceding result in
|
|
|
3617 a messed-up display, especially for frames with multiple windows. You
|
|
|
3618 may need to resize the frame before XEmacs completely realizes the
|
|
|
3619 toolbar is really gone.
|
|
|
3620
|
|
274
|
3621 Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct
|
|
82
|
3622 code.
|
|
|
3623
|
|
|
3624 @node Q3.9.1, Q3.9.2, Q3.8.5, Customization
|
|
274
|
3625 @unnumberedsec 3.9: Scrollbars
|
|
|
3626 @unnumberedsubsec Q3.9.1: How can I disable the scrollbar?
|
|
82
|
3627
|
|
|
3628 To disable them for all frames, add the following line to
|
|
|
3629 your @file{.Xdefaults}:
|
|
|
3630
|
|
|
3631 @example
|
|
|
3632 Emacs.scrollBarWidth: 0
|
|
|
3633 @end example
|
|
|
3634
|
|
282
|
3635 Or select from the @code{Options} menu @code{Frame Appearance->Scrollbars}.
|
|
227
|
3636 Remember to save options.
|
|
|
3637
|
|
82
|
3638 To turn the scrollbar off on a per-frame basis, use the following
|
|
|
3639 function:
|
|
|
3640
|
|
|
3641 @lisp
|
|
163
|
3642 (set-specifier scrollbar-width 0 (selected-frame))
|
|
82
|
3643 @end lisp
|
|
|
3644
|
|
|
3645 You can actually turn the scrollbars on at any level you want by
|
|
|
3646 substituting for (selected-frame) in the above command. For example, to
|
|
|
3647 turn the scrollbars off only in a single buffer:
|
|
|
3648
|
|
|
3649 @lisp
|
|
163
|
3650 (set-specifier scrollbar-width 0 (current-buffer))
|
|
82
|
3651 @end lisp
|
|
|
3652
|
|
163
|
3653 In XEmacs versions prior to 19.14, you had to use the hairier construct:
|
|
82
|
3654
|
|
|
3655 @lisp
|
|
163
|
3656 (set-specifier scrollbar-width (cons (selected-frame) 0))
|
|
82
|
3657 @end lisp
|
|
|
3658
|
|
|
3659 @node Q3.9.2, Q3.9.3, Q3.9.1, Customization
|
|
274
|
3660 @unnumberedsubsec Q3.9.2: How can one use resources to change scrollbar colors?
|
|
82
|
3661
|
|
|
3662 Here's a recap of how to use resources to change your scrollbar colors:
|
|
|
3663
|
|
|
3664 @example
|
|
|
3665 ! Motif scrollbars
|
|
|
3666
|
|
|
3667 Emacs*XmScrollBar.Background: skyblue
|
|
|
3668 Emacs*XmScrollBar.troughColor: lightgray
|
|
|
3669
|
|
|
3670 ! Athena scrollbars
|
|
|
3671
|
|
|
3672 Emacs*Scrollbar.Foreground: skyblue
|
|
|
3673 Emacs*Scrollbar.Background: lightgray
|
|
|
3674 @end example
|
|
|
3675
|
|
|
3676 Note the capitalization of @code{Scrollbar} for the Athena widget.
|
|
|
3677
|
|
|
3678 @node Q3.9.3, Q3.9.4, Q3.9.2, Customization
|
|
274
|
3679 @unnumberedsubsec Q3.9.3: Moving the scrollbar can move the point; can I disable this?
|
|
82
|
3680
|
|
|
3681 When I move the scrollbar in an XEmacs window, it moves the point as
|
|
|
3682 well, which should not be the default behavior. Is this a bug or a
|
|
|
3683 feature? Can I disable it?
|
|
|
3684
|
|
|
3685 The current behavior is a feature, not a bug. Point remains at the same
|
|
|
3686 buffer position as long as that position does not scroll off the screen.
|
|
|
3687 In that event, point will end up in either the upper-left or lower-left
|
|
|
3688 hand corner.
|
|
|
3689
|
|
|
3690 This cannot be changed.
|
|
|
3691
|
|
|
3692 @node Q3.9.4, Q3.10.1, Q3.9.3, Customization
|
|
274
|
3693 @unnumberedsubsec Q3.9.4: How can I get automatic horizontal scrolling?
|
|
82
|
3694
|
|
|
3695 By the same token, how can I turn it off in specific modes?
|
|
|
3696
|
|
|
3697 To do this, add to your @file{.emacs} file:
|
|
|
3698
|
|
|
3699 @lisp
|
|
|
3700 (require 'auto-show)
|
|
|
3701 @end lisp
|
|
|
3702
|
|
|
3703 Then do @code{(setq truncate-lines t)} in the mode-hooks for any modes
|
|
|
3704 in which you want lines truncated.
|
|
|
3705
|
|
|
3706 More precisely: If @code{truncate-lines} is nil, horizontal scrollbars
|
|
|
3707 will never appear. Otherwise, they will appear only if the value of
|
|
|
3708 @code{scrollbar-height} for that buffer/window/etc. is non-zero. If you
|
|
|
3709 do
|
|
|
3710
|
|
|
3711 @lisp
|
|
|
3712 (set-specifier scrollbar-height 0)
|
|
|
3713 @end lisp
|
|
|
3714
|
|
|
3715 then horizontal scrollbars will not appear in truncated buffers unless
|
|
|
3716 the package specifically asked for them.
|
|
|
3717
|
|
|
3718 Automatic horizontal scrolling is now standard, starting with 19.14.
|
|
|
3719
|
|
|
3720 @node Q3.10.1, Q3.10.2, Q3.9.4, Customization
|
|
282
|
3721 @unnumberedsec 3.10: Text Selections
|
|
274
|
3722 @unnumberedsubsec Q3.10.1: How can I turn off or change highlighted selections?
|
|
82
|
3723
|
|
|
3724 The @code{zmacs} mode allows for what some might call gratuitous
|
|
|
3725 highlighting for selected regions (either by setting mark or by using
|
|
|
3726 the mouse). This is the default behavior. To turn off, add the
|
|
|
3727 following line to your @file{.emacs} file:
|
|
|
3728
|
|
|
3729 @lisp
|
|
|
3730 (setq zmacs-regions nil)
|
|
|
3731 @end lisp
|
|
|
3732
|
|
227
|
3733 Starting with XEmacs-20.2 you can also change this with Customize. Select
|
|
|
3734 from the @code{Options} menu @code{Customize->Emacs->Editing->Basics->Zmacs
|
|
282
|
3735 Regions} or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}.
|
|
215
|
3736
|
|
126
|
3737 To change the face for selection, look at @code{Options->Customize} on
|
|
82
|
3738 the menubar.
|
|
|
3739
|
|
|
3740 @node Q3.10.2, Q3.10.3, Q3.10.1, Customization
|
|
274
|
3741 @unnumberedsubsec Q3.10.2: How do I get that typing on an active region removes it?
|
|
82
|
3742
|
|
|
3743 I want to change things so that if I select some text and start typing,
|
|
|
3744 the typed text replaces the selected text, similar to Motif.
|
|
|
3745
|
|
|
3746 You want to use something called @dfn{pending delete}. Pending delete
|
|
|
3747 is what happens when you select a region (with the mouse or keyboard)
|
|
|
3748 and you press a key to replace the selected region by the key you typed.
|
|
|
3749 Usually backspace kills the selected region.
|
|
|
3750
|
|
365
|
3751 To get this behavior, add the following lines to your @file{.emacs}:
|
|
82
|
3752
|
|
|
3753 @lisp
|
|
365
|
3754 (cond
|
|
|
3755 ((fboundp 'turn-on-pending-delete)
|
|
|
3756 (turn-on-pending-delete))
|
|
|
3757 ((fboundp 'pending-delete-on)
|
|
|
3758 (pending-delete-on t)))
|
|
82
|
3759 @end lisp
|
|
|
3760
|
|
365
|
3761 Note that this will work with both Backspace and Delete. This code is a
|
|
|
3762 tad more complicated than it has to be for XEmacs in order to make it
|
|
|
3763 more portable.
|
|
82
|
3764
|
|
|
3765 @node Q3.10.3, Q3.10.4, Q3.10.2, Customization
|
|
274
|
3766 @unnumberedsubsec Q3.10.3: Can I turn off the highlight during isearch?
|
|
82
|
3767
|
|
|
3768 I do not like my text highlighted while I am doing isearch as I am not
|
|
|
3769 able to see what's underneath. How do I turn it off?
|
|
|
3770
|
|
|
3771 Put the following in your @file{.emacs}:
|
|
|
3772
|
|
|
3773 @lisp
|
|
|
3774 (setq isearch-highlight nil)
|
|
|
3775 @end lisp
|
|
|
3776
|
|
227
|
3777 Starting with XEmacs-20.2 you can also change this with Customize. Type
|
|
282
|
3778 @kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}.
|
|
215
|
3779
|
|
82
|
3780 Note also that isearch-highlight affects query-replace and ispell.
|
|
|
3781 Instead of disabling isearch-highlight you may find that a better
|
|
|
3782 solution consists of customizing the @code{isearch} face.
|
|
|
3783
|
|
|
3784 @node Q3.10.4, Q3.10.5, Q3.10.3, Customization
|
|
274
|
3785 @unnumberedsubsec Q3.10.4: How do I turn off highlighting after @kbd{C-x C-p} (mark-page)?
|
|
82
|
3786
|
|
|
3787 Put this in your @code{.emacs}:
|
|
|
3788
|
|
|
3789 @lisp
|
|
|
3790 (setq zmacs-regions nil)
|
|
|
3791 @end lisp
|
|
|
3792
|
|
|
3793 @strong{Warning: This command turns off all region highlighting.}
|
|
|
3794
|
|
215
|
3795 Also @xref{Q3.10.1}.
|
|
|
3796
|
|
82
|
3797 @node Q3.10.5, , Q3.10.4, Customization
|
|
274
|
3798 @unnumberedsubsec Q3.10.5: The region disappears when I hit the end of buffer while scrolling.
|
|
82
|
3799
|
|
227
|
3800 This has been fixed by default starting with XEmacs-20.3.
|
|
|
3801
|
|
|
3802 With older versions you can turn this feature (if it indeed is a feature)
|
|
|
3803 off like this:
|
|
82
|
3804
|
|
|
3805 @lisp
|
|
|
3806 (defadvice scroll-up (around scroll-up freeze)
|
|
|
3807 (interactive "_P")
|
|
|
3808 (let ((zmacs-region-stays t))
|
|
|
3809 (if (interactive-p)
|
|
365
|
3810 (condition-case nil
|
|
|
3811 ad-do-it
|
|
|
3812 (end-of-buffer (goto-char (point-max))))
|
|
82
|
3813 ad-do-it)))
|
|
|
3814
|
|
|
3815 (defadvice scroll-down (around scroll-down freeze)
|
|
|
3816 (interactive "_P")
|
|
|
3817 (let ((zmacs-region-stays t))
|
|
|
3818 (if (interactive-p)
|
|
365
|
3819 (condition-case nil
|
|
|
3820 ad-do-it
|
|
|
3821 (beginning-of-buffer (goto-char (point-min))))
|
|
82
|
3822 ad-do-it)))
|
|
|
3823 @end lisp
|
|
|
3824
|
|
274
|
3825 Thanks to @email{raman@@adobe.com, T. V. Raman} for assistance in deriving this
|
|
82
|
3826 answer.
|
|
|
3827
|
|
|
3828 @node Subsystems, Miscellaneous, Customization, Top
|
|
274
|
3829 @unnumbered 4 Major Subsystems
|
|
82
|
3830
|
|
|
3831 This is part 4 of the XEmacs Frequently Asked Questions list. This
|
|
|
3832 section is devoted to major XEmacs subsystems.
|
|
|
3833
|
|
|
3834 @menu
|
|
|
3835 Reading Mail with VM:
|
|
|
3836 * Q4.0.1:: How do I set up VM to retrieve remote mail using POP?
|
|
|
3837 * Q4.0.2:: How do I get VM to filter mail for me?
|
|
|
3838 * Q4.0.3:: How can I get VM to automatically check for new mail?
|
|
|
3839 * Q4.0.4:: [This question intentionally left blank]
|
|
|
3840 * Q4.0.5:: How do I get my outgoing mail archived?
|
|
|
3841 * 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"?
|
|
|
3842 * Q4.0.7:: Is there a mailing list or FAQ for VM?
|
|
217
|
3843 * Q4.0.8:: Remote mail reading with VM.
|
|
82
|
3844 * Q4.0.9:: rmail or VM gets an error incorporating new mail.
|
|
|
3845 * Q4.0.10:: How do I make VM stay in a single frame?
|
|
|
3846 * Q4.0.11:: How do I make VM or mh-e display graphical smilies?
|
|
|
3847 * Q4.0.12:: Customization of VM not covered in the manual or here.
|
|
|
3848
|
|
|
3849 Web browsing with W3:
|
|
|
3850 * Q4.1.1:: What is W3?
|
|
|
3851 * Q4.1.2:: How do I run W3 from behind a firewall?
|
|
163
|
3852 * Q4.1.3:: Is it true that W3 supports style sheets and tables?
|
|
82
|
3853
|
|
|
3854 Reading Netnews and Mail with Gnus:
|
|
282
|
3855 * Q4.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus,argh!
|
|
82
|
3856 * Q4.2.2:: [This question intentionally left blank]
|
|
|
3857 * Q4.2.3:: How do I make Gnus stay within a single frame?
|
|
|
3858 * Q4.2.4:: How do I customize the From: line?
|
|
|
3859
|
|
|
3860 Other Mail & News:
|
|
|
3861 * Q4.3.1:: How can I read and/or compose MIME messages?
|
|
|
3862 * Q4.3.2:: What is TM and where do I get it?
|
|
|
3863 * Q4.3.3:: Why isn't this @code{movemail} program working?
|
|
|
3864 * Q4.3.4:: Movemail is also distributed by Netscape? Can that cause problems?
|
|
|
3865 * Q4.3.5:: Where do I find pstogif (required by tm)?
|
|
|
3866
|
|
|
3867 Sparcworks, EOS, and WorkShop:
|
|
282
|
3868 * Q4.4.1:: What is SPARCworks, EOS, and WorkShop
|
|
353
|
3869 * Q4.4.2:: How do I start the Sun Workshop support in XEmacs 21?
|
|
82
|
3870
|
|
|
3871 Energize:
|
|
|
3872 * Q4.5.1:: What is/was Energize?
|
|
|
3873
|
|
|
3874 Infodock:
|
|
|
3875 * Q4.6.1:: What is Infodock?
|
|
|
3876
|
|
|
3877 Other Unbundled Packages:
|
|
163
|
3878 * Q4.7.1:: What is AUC TeX? Where do you get it?
|
|
82
|
3879 * Q4.7.2:: Are there any Emacs Lisp Spreadsheets?
|
|
365
|
3880 * Q4.7.3:: [This question intentionally left blank]
|
|
163
|
3881 * Q4.7.4:: Problems installing AUC TeX
|
|
|
3882 * Q4.7.5:: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
282
|
3883 * Q4.7.6:: Is there a MatLab mode?
|
|
82
|
3884 @end menu
|
|
|
3885
|
|
|
3886 @node Q4.0.1, Q4.0.2, Subsystems, Subsystems
|
|
282
|
3887 @unnumberedsec 4.0: Reading Mail with VM
|
|
274
|
3888 @unnumberedsubsec Q4.0.1: How do I set up VM to retrieve mail from a remote site using POP?
|
|
82
|
3889
|
|
|
3890 Use @code{vm-spool-files}, like this for example:
|
|
|
3891
|
|
|
3892 @lisp
|
|
|
3893 (setq vm-spool-files '("/var/spool/mail/wing"
|
|
|
3894 "netcom23.netcom.com:110:pass:wing:MYPASS"))
|
|
|
3895 @end lisp
|
|
|
3896
|
|
|
3897 Of course substitute your actual password for MYPASS.
|
|
|
3898
|
|
|
3899 @node Q4.0.2, Q4.0.3, Q4.0.1, Subsystems
|
|
274
|
3900 @unnumberedsubsec Q4.0.2: How do I get VM to filter mail for me?
|
|
82
|
3901
|
|
|
3902 One possibility is to use procmail to split your mail before it gets to
|
|
|
3903 VM. I prefer this personally, since there are many strange and
|
|
|
3904 wonderful things one can do with procmail. Procmail may be found at
|
|
274
|
3905 @uref{ftp://ftp.informatik.rwth-aachen.de/pub/packages/procmail/}.
|
|
82
|
3906
|
|
|
3907 Also see the Mail Filtering FAQ at:
|
|
274
|
3908 @iftex
|
|
|
3909 @*
|
|
282
|
3910 @end iftex
|
|
|
3911 @uref{ftp://rtfm.mit.edu/pub/usenet/news.answers/mail/filtering-faq}.
|
|
|
3912 @c Link above,
|
|
|
3913 @c <URL:http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering-faq/faq.html>
|
|
|
3914 @c was dead.
|
|
82
|
3915
|
|
|
3916 @node Q4.0.3, Q4.0.4, Q4.0.2, Subsystems
|
|
274
|
3917 @unnumberedsubsec Q4.0.3: How can I get VM to automatically check for new mail?
|
|
|
3918
|
|
|
3919 @email{turner@@lanl.gov, John Turner} writes:
|
|
82
|
3920
|
|
|
3921 @quotation
|
|
|
3922 Use the following:
|
|
|
3923
|
|
|
3924 @lisp
|
|
|
3925 (setq vm-auto-get-new-mail 60)
|
|
|
3926 @end lisp
|
|
|
3927 @end quotation
|
|
|
3928
|
|
|
3929 @node Q4.0.4, Q4.0.5, Q4.0.3, Subsystems
|
|
274
|
3930 @unnumberedsubsec Q4.0.4: [This question intentionally left blank]
|
|
82
|
3931
|
|
|
3932 Obsolete question, left blank to avoid renumbering.
|
|
|
3933
|
|
|
3934 @node Q4.0.5, Q4.0.6, Q4.0.4, Subsystems
|
|
274
|
3935 @unnumberedsubsec Q4.0.5: How do I get my outgoing mail archived?
|
|
82
|
3936
|
|
|
3937 @lisp
|
|
|
3938 (setq mail-archive-file-name "~/outbox")
|
|
|
3939 @end lisp
|
|
|
3940
|
|
|
3941 @node Q4.0.6, Q4.0.7, Q4.0.5, Subsystems
|
|
274
|
3942 @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"?
|
|
82
|
3943
|
|
|
3944 Set @code{vm-reply-ignored-addresses} to a list, like
|
|
|
3945
|
|
|
3946 @lisp
|
|
282
|
3947 (setq vm-reply-ignored-addresses
|
|
274
|
3948 '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com"
|
|
365
|
3949 "wing@@netcom.com" "wing@@xemacs.org"))
|
|
82
|
3950 @end lisp
|
|
|
3951
|
|
|
3952 Note that each string is a regular expression.
|
|
|
3953
|
|
|
3954 @node Q4.0.7, Q4.0.8, Q4.0.6, Subsystems
|
|
274
|
3955 @unnumberedsubsec Q4.0.7: Is there a mailing list or FAQ for VM?
|
|
|
3956
|
|
282
|
3957 A FAQ for VM exists at @uref{http://www.cyberpass.net/~gorkab/vmfaq.htm}.
|
|
82
|
3958
|
|
163
|
3959 VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug.
|
|
82
|
3960
|
|
274
|
3961 @node Q4.0.8, Q4.0.9, Q4.0.7, Subsystems
|
|
|
3962 @unnumberedsubsec Q4.0.8: Remote mail reading with VM.
|
|
82
|
3963
|
|
|
3964 My mailbox lives at the office on a big honkin server. My regular INBOX
|
|
|
3965 lives on my honkin desktop machine. I now can PPP to the office from
|
|
|
3966 home which is far from honking... I'd like to be able to read mail at
|
|
|
3967 home without storing it here and I'd like to use xemacs and VM at
|
|
|
3968 home... Is there a recommended setup?
|
|
|
3969
|
|
274
|
3970 @email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes:
|
|
82
|
3971
|
|
|
3972 @quotation
|
|
|
3973 There are several ways to do this.
|
|
|
3974
|
|
|
3975 @enumerate
|
|
|
3976 @item
|
|
|
3977 Set your display to your home machine and run dxpc or one of the other X
|
|
|
3978 compressors.
|
|
|
3979
|
|
|
3980 @item
|
|
|
3981 NFS mount your desktop machine on your home machine and modify your pop
|
|
|
3982 command on your home machine to rsh to your desktop machine and actually
|
|
|
3983 do the pop get's.
|
|
|
3984
|
|
|
3985 @item
|
|
|
3986 Run a POP server on your desktop machine as well and do a sort of two
|
|
|
3987 tiered POP get.
|
|
|
3988 @end enumerate
|
|
|
3989 @end quotation
|
|
|
3990
|
|
274
|
3991 @email{wmperry@@monolith.spry.com, William Perry} adds:
|
|
82
|
3992
|
|
|
3993 @quotation
|
|
|
3994 Or you could run a pop script periodically on your desktop machine, and
|
|
|
3995 just use ange-ftp or NFS to get to your mailbox. I used to do this all
|
|
|
3996 the time back at IU.
|
|
|
3997 @end quotation
|
|
|
3998
|
|
|
3999 @node Q4.0.9, Q4.0.10, Q4.0.8, Subsystems
|
|
274
|
4000 @unnumberedsubsec Q4.0.9: rmail or VM gets an error incorporating new mail.
|
|
82
|
4001
|
|
163
|
4002 Quoting the XEmacs PROBLEMS file:
|
|
82
|
4003
|
|
|
4004 @quotation
|
|
|
4005 rmail and VM get new mail from @file{/usr/spool/mail/$USER} using a
|
|
|
4006 program called @code{movemail}. This program interlocks with
|
|
|
4007 @code{/bin/mail} using the protocol defined by @code{/bin/mail}.
|
|
282
|
4008
|
|
82
|
4009 There are two different protocols in general use. One of them uses the
|
|
|
4010 @code{flock} system call. The other involves creating a lock file;
|
|
|
4011 @code{movemail} must be able to write in @file{/usr/spool/mail} in order
|
|
|
4012 to do this. You control which one is used by defining, or not defining,
|
|
|
4013 the macro @code{MAIL_USE_FLOCK} in @file{config.h} or the m- or s- file
|
|
|
4014 it includes.
|
|
|
4015
|
|
|
4016 @strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
|
|
|
4017 SYSTEM, YOU CAN LOSE MAIL!}
|
|
|
4018
|
|
|
4019 If your system uses the lock file protocol, and fascist restrictions
|
|
|
4020 prevent ordinary users from writing the lock files in
|
|
|
4021 @file{/usr/spool/mail}, you may need to make @code{movemail} setgid to a
|
|
|
4022 suitable group such as @samp{mail}. You can use these commands (as
|
|
|
4023 root):
|
|
|
4024
|
|
|
4025 @example
|
|
|
4026 chgrp mail movemail
|
|
|
4027 chmod 2755 movemail
|
|
|
4028 @end example
|
|
|
4029
|
|
|
4030 If your system uses the lock file protocol, and fascist restrictions
|
|
|
4031 prevent ordinary users from writing the lock files in
|
|
|
4032 @file{/usr/spool/mail}, you may need to make @code{movemail} setgid to a
|
|
|
4033 suitable group such as @code{mail}. To do this, use the following
|
|
|
4034 commands (as root) after doing the make install.
|
|
|
4035
|
|
|
4036 @example
|
|
|
4037 chgrp mail movemail
|
|
|
4038 chmod 2755 movemail
|
|
|
4039 @end example
|
|
|
4040
|
|
|
4041 Installation normally copies movemail from the build directory to an
|
|
|
4042 installation directory which is usually under @file{/usr/local/lib}.
|
|
|
4043 The installed copy of @code{movemail} is usually in the directory
|
|
|
4044 @file{/usr/local/lib/emacs/VERSION/TARGET}. You must change the group
|
|
|
4045 and mode of the installed copy; changing the group and mode of the build
|
|
|
4046 directory copy is ineffective.
|
|
|
4047 @end quotation
|
|
|
4048
|
|
|
4049 @node Q4.0.10, Q4.0.11, Q4.0.9, Subsystems
|
|
274
|
4050 @unnumberedsubsec Q4.0.10: How do I make VM stay in a single frame?
|
|
|
4051
|
|
|
4052 John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes:
|
|
82
|
4053
|
|
|
4054 @quotation
|
|
|
4055 @lisp
|
|
365
|
4056 ; Don't use multiple frames
|
|
82
|
4057 (setq vm-frame-per-composition nil)
|
|
|
4058 (setq vm-frame-per-folder nil)
|
|
|
4059 (setq vm-frame-per-edit nil)
|
|
|
4060 (setq vm-frame-per-summary nil)
|
|
|
4061 @end lisp
|
|
|
4062 @end quotation
|
|
|
4063
|
|
|
4064 @node Q4.0.11, Q4.0.12, Q4.0.10, Subsystems
|
|
274
|
4065 @unnumberedsubsec Q4.0.11: How do I make VM or mh-e display graphical smilies?
|
|
282
|
4066 @c Changed June
|
|
82
|
4067 For mh-e use the following:
|
|
|
4068
|
|
|
4069 @lisp
|
|
282
|
4070 (add-hook 'mh-show-mode-hook '(lambda ()
|
|
365
|
4071 (smiley-region (point-min)
|
|
274
|
4072 (point-max))))
|
|
82
|
4073 @end lisp
|
|
|
4074
|
|
282
|
4075 @email{bill@@carpenter.ORG, WJCarpenter} writes:
|
|
|
4076 For VM use the following:
|
|
82
|
4077 @lisp
|
|
282
|
4078 (autoload 'smiley-region "smiley" nil t)
|
|
|
4079 (add-hook 'vm-select-message-hook
|
|
|
4080 '(lambda ()
|
|
|
4081 (smiley-region (point-min)
|
|
|
4082 (point-max))))
|
|
82
|
4083 @end lisp
|
|
|
4084
|
|
|
4085 For tm use the following:
|
|
|
4086 @lisp
|
|
|
4087 (autoload 'smiley-buffer "smiley" nil t)
|
|
|
4088 (add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer)
|
|
|
4089 @end lisp
|
|
|
4090
|
|
|
4091 @node Q4.0.12, Q4.1.1, Q4.0.11, Subsystems
|
|
274
|
4092 @unnumberedsubsec Q4.0.12: Customization of VM not covered in the manual, or here.
|
|
|
4093
|
|
|
4094 @email{boffi@@hp735.stru.polimi.it, giacomo boffi} writes:
|
|
82
|
4095
|
|
|
4096 @quotation
|
|
|
4097 The meta-answer is to look into the file @file{vm-vars.el}, in the vm
|
|
|
4098 directory of the lisp library.
|
|
|
4099
|
|
|
4100 @file{vm-vars.el} contains, initializes and carefully describes, with
|
|
|
4101 examples of usage, the plethora of user options that @emph{fully}
|
|
|
4102 control VM's behavior.
|
|
|
4103
|
|
|
4104 Enter vm-vars, @code{forward-search} for toolbar, find the variables
|
|
|
4105 that control the toolbar placement, appearance, existence, copy to your
|
|
|
4106 @file{.emacs} or @file{.vm} and modify according to the detailed
|
|
|
4107 instructions.
|
|
|
4108
|
|
|
4109 The above also applies to all the various features of VM: search for
|
|
|
4110 some keywords, maybe the first you conjure isn't appropriate, find the
|
|
|
4111 appropriate variables, copy and experiment.
|
|
|
4112 @end quotation
|
|
|
4113
|
|
|
4114 @node Q4.1.1, Q4.1.2, Q4.0.12, Subsystems
|
|
282
|
4115 @unnumberedsec 4.1: Web browsing with W3
|
|
274
|
4116 @unnumberedsubsec Q4.1.1: What is W3?
|
|
82
|
4117
|
|
|
4118 W3 is an advanced graphical browser written in Emacs lisp that runs on
|
|
|
4119 XEmacs. It has full support for cascaded style sheets, and more...
|
|
|
4120
|
|
|
4121 It has a home web page at
|
|
274
|
4122 @uref{http://www.cs.indiana.edu/elisp/w3/docs.html}.
|
|
82
|
4123
|
|
163
|
4124 @node Q4.1.2, Q4.1.3, Q4.1.1, Subsystems
|
|
274
|
4125 @unnumberedsubsec Q4.1.2: How do I run W3 from behind a firewall?
|
|
82
|
4126
|
|
|
4127 There is a long, well-written, detailed section in the W3 manual that
|
|
|
4128 describes how to do this. Look in the section entitled "Firewalls".
|
|
|
4129
|
|
163
|
4130 @node Q4.1.3, Q4.2.1, Q4.1.2, Subsystems
|
|
274
|
4131 @unnumberedsubsec Q4.1.3: Is it true that W3 supports style sheets and tables?
|
|
163
|
4132
|
|
|
4133 Yes, and much more. W3, as distributed with the latest XEmacs is a
|
|
|
4134 full-featured web browser.
|
|
|
4135
|
|
|
4136 @node Q4.2.1, Q4.2.2, Q4.1.3, Subsystems
|
|
282
|
4137 @unnumberedsec 4.2: Reading Netnews and Mail with Gnus
|
|
274
|
4138 @unnumberedsubsec Q4.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh!
|
|
82
|
4139
|
|
163
|
4140 The Gnus numbering issues are not meant for mere mortals to know them.
|
|
|
4141 If you feel you @emph{must} enter the muddy waters of Gnus, visit the
|
|
|
4142 excellent FAQ, maintained by Justin Sheehy, at:
|
|
|
4143
|
|
|
4144 @example
|
|
282
|
4145 @uref{http://www.ccs.neu.edu/software/contrib/gnus/}
|
|
163
|
4146 @end example
|
|
82
|
4147
|
|
215
|
4148 See also Gnus home page
|
|
|
4149 @example
|
|
274
|
4150 @uref{http://www.gnus.org/}
|
|
215
|
4151 @end example
|
|
|
4152
|
|
82
|
4153 @node Q4.2.2, Q4.2.3, Q4.2.1, Subsystems
|
|
274
|
4154 @unnumberedsubsec Q4.2.2: This question intentionally left blank.
|
|
82
|
4155
|
|
|
4156 Obsolete question, left blank to avoid renumbering.
|
|
|
4157
|
|
|
4158 @node Q4.2.3, Q4.2.4, Q4.2.2, Subsystems
|
|
274
|
4159 @unnumberedsubsec Q4.2.3: How do I make Gnus stay within a single frame?
|
|
82
|
4160
|
|
163
|
4161 The toolbar code to start Gnus opens the new frame---and it's a feature
|
|
|
4162 rather than a bug. If you don't like it, but would still like to click
|
|
|
4163 on the seemly icon, use the following code:
|
|
82
|
4164
|
|
|
4165 @lisp
|
|
|
4166 (defun toolbar-news ()
|
|
|
4167 (gnus))
|
|
|
4168 @end lisp
|
|
163
|
4169
|
|
|
4170 It will redefine the callback function of the icon to just call
|
|
|
4171 @code{gnus}, without all the fancy frame stuff.
|
|
82
|
4172
|
|
|
4173 @node Q4.2.4, Q4.3.1, Q4.2.3, Subsystems
|
|
274
|
4174 @unnumberedsubsec Q4.2.4: How do I customize the From: line?
|
|
82
|
4175
|
|
|
4176 How do I change the @code{From:} line? I have set gnus-user-from-line
|
|
282
|
4177 to
|
|
|
4178 @example
|
|
274
|
4179 Gail Gurman <gail.gurman@@sybase.com>
|
|
|
4180 @end example
|
|
|
4181 @noindent , but XEmacs Gnus doesn't use
|
|
282
|
4182 it. Instead it uses
|
|
|
4183 @example
|
|
|
4184 Gail Mara Gurman @email{gailg@@deall}
|
|
274
|
4185 @end example
|
|
|
4186 @noindent and then complains
|
|
82
|
4187 that it's incorrect. Also, as you perhaps can see, my Message-ID is
|
|
|
4188 screwy. How can I change that?
|
|
|
4189
|
|
274
|
4190 @email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes:
|
|
82
|
4191
|
|
|
4192 @quotation
|
|
|
4193 Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or
|
|
|
4194 @code{mail-host-address} to @samp{sybase.com}.
|
|
|
4195 @end quotation
|
|
|
4196
|
|
|
4197 @node Q4.3.1, Q4.3.2, Q4.2.4, Subsystems
|
|
282
|
4198 @unnumberedsec 4.3: Other Mail & News
|
|
274
|
4199 @unnumberedsubsec Q4.3.1: How can I read and/or compose MIME messages?
|
|
282
|
4200 @c Changed June
|
|
|
4201
|
|
|
4202 VM supports MIME natively.
|
|
82
|
4203
|
|
335
|
4204 You probably want to use the Tools for MIME (tm). @xref{Q4.3.2}, for
|
|
82
|
4205 details.
|
|
|
4206
|
|
274
|
4207 @email{trey@@cs.berkeley.edu, Trey Jackson} has an Emacs & MIME web page at
|
|
|
4208 @iftex
|
|
|
4209 @*
|
|
282
|
4210 @end iftex
|
|
274
|
4211 @uref{http://bmrc.berkeley.edu/~trey/emacs/mime.html}.
|
|
82
|
4212
|
|
282
|
4213
|
|
|
4214 Another possibility is RMIME. You may find RMIME at
|
|
|
4215 @iftex
|
|
|
4216 @*
|
|
|
4217 @end iftex
|
|
|
4218 @uref{http://www.cinti.net/~rmoody/rmime/index.html}.
|
|
|
4219
|
|
|
4220
|
|
82
|
4221 @node Q4.3.2, Q4.3.3, Q4.3.1, Subsystems
|
|
274
|
4222 @unnumberedsubsec Q4.3.2: What is TM and where do I get it?
|
|
82
|
4223
|
|
|
4224 TM stands for @dfn{Tools for MIME} and not Tiny MIME. TM integrates
|
|
|
4225 with all major XEmacs packages like Gnus (all flavors), VM, MH-E, and
|
|
|
4226 mailcrypt. It provides totally transparent and trouble-free MIME
|
|
|
4227 support. When appropriate a message will be decoded in place in an
|
|
|
4228 XEmacs buffer.
|
|
|
4229
|
|
213
|
4230 TM now comes as a package with XEmacs 19.16 and XEmacs 20.2.
|
|
126
|
4231
|
|
274
|
4232 TM was written by @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} and
|
|
|
4233 @email{shuhei-k@@jaist.ac.jp, KOBAYASHI
|
|
282
|
4234 Shuhei}.
|
|
274
|
4235
|
|
|
4236 It is based on the work of @email{umerin@@mse.kyutech.ac.jp, UMEDA
|
|
|
4237 Masanobu}, the original writer of GNUS.
|
|
82
|
4238
|
|
|
4239 The following information is from the @file{README}:
|
|
|
4240
|
|
|
4241 @dfn{tm} is a MIME package for GNU Emacs.
|
|
|
4242 tm has following functions:
|
|
|
4243
|
|
|
4244 @itemize @bullet
|
|
|
4245 @item MIME style multilingual header.
|
|
|
4246 @item MIME message viewer (mime/viewer-mode).
|
|
|
4247 @item MIME message composer (mime/editor-mode).
|
|
|
4248 @item MIME extenders for mh-e, GNUS, RMAIL and VM.
|
|
|
4249 @end itemize
|
|
|
4250
|
|
|
4251 tm is available from following anonymous ftp sites:
|
|
|
4252 @itemize @bullet
|
|
359
|
4253 @comment @item @uref{ftp://ftp.jaist.ac.jp/pub/GNU/elisp/mime/} (Japan).
|
|
|
4254 @comment @item @uref{ftp://ftp.nis.co.jp/pub/gnu/emacs-lisp/tm/} (Japan).
|
|
|
4255 @comment @c The host above is unknown.
|
|
|
4256 @comment @item @uref{ftp://ftp.nisiq.net/pub/gnu/emacs-lisp/tm/} (US).
|
|
|
4257 @comment @item @uref{ftp://ftp.miranova.com/pub/gnus/jaist.ac.jp/} (US).
|
|
274
|
4258 @item @uref{ftp://ftp.unicamp.br/pub/mail/mime/tm/} (Brasil).
|
|
|
4259 @item @uref{ftp://ftp.th-darmstadt.de/pub/editors/GNU-Emacs/lisp/mime/} (Germany).
|
|
|
4260 @item @uref{ftp://ftp.tnt.uni-hannover.de/pub/editors/xemacs/contrib/} (Germany).
|
|
82
|
4261 @end itemize
|
|
|
4262
|
|
|
4263 Don't let the installation procedure & instructions stop you from trying
|
|
|
4264 this package out---it's much simpler than it looks, and once installed,
|
|
|
4265 trivial to use.
|
|
|
4266
|
|
|
4267 @node Q4.3.3, Q4.3.4, Q4.3.2, Subsystems
|
|
274
|
4268 @unnumberedsubsec Q4.3.3: Why isn't this @code{movemail} program working?
|
|
|
4269
|
|
359
|
4270 Ben Wing @email{ben@@xemacs.org} writes:
|
|
82
|
4271
|
|
|
4272 @quotation
|
|
|
4273 It wasn't chown'ed/chmod'd correctly.
|
|
|
4274 @end quotation
|
|
|
4275
|
|
|
4276 @node Q4.3.4, Q4.3.5, Q4.3.3, Subsystems
|
|
274
|
4277 @unnumberedsubsec Q4.3.4: Movemail is also distributed by Netscape? Can that cause problems?
|
|
|
4278
|
|
359
|
4279 @email{steve@@xemacs.org, Steve Baur} writes:
|
|
82
|
4280
|
|
|
4281 @quotation
|
|
|
4282 Yes. Always use the movemail installed with your XEmacs. Failure to do
|
|
|
4283 so can result in lost mail.
|
|
|
4284 @end quotation
|
|
|
4285
|
|
359
|
4286 Please refer to @email{jwz@@jwz.org, Jamie Zawinski's} notes at
|
|
274
|
4287 @iftex
|
|
|
4288 @*
|
|
282
|
4289 @end iftex
|
|
274
|
4290 @uref{http://home.netscape.com/eng/mozilla/2.0/relnotes/demo/movemail.html}.
|
|
82
|
4291 In particular, this document will show you how to make Netscape use the
|
|
|
4292 version of movemail configured for your system by the person who built
|
|
|
4293 XEmacs.
|
|
|
4294
|
|
|
4295 @node Q4.3.5, Q4.4.1, Q4.3.4, Subsystems
|
|
274
|
4296 @unnumberedsubsec Q4.3.5: Where do I find pstogif (required by tm)?
|
|
82
|
4297
|
|
|
4298 pstogif is part of the latex2html package.
|
|
|
4299
|
|
274
|
4300 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
|
|
82
|
4301
|
|
|
4302 latex2html is best found at the CTAN hosts and their mirrors
|
|
282
|
4303 in
|
|
274
|
4304 @iftex
|
|
|
4305 @*
|
|
282
|
4306 @end iftex
|
|
274
|
4307 @file{tex-archive/support/latex2html}.
|
|
82
|
4308
|
|
|
4309 CTAN hosts are:
|
|
|
4310
|
|
|
4311 @itemize @bullet
|
|
274
|
4312 @item @uref{ftp://ftp.tex.ac.uk/tex-archive/support/latex2html/}.
|
|
|
4313 @item @uref{ftp://ftp.dante.de/tex-archive/support/latex2html/}.
|
|
82
|
4314 @end itemize
|
|
|
4315
|
|
|
4316 There is a good mirror at ftp.cdrom.com;
|
|
274
|
4317 @iftex
|
|
|
4318 @*
|
|
282
|
4319 @end iftex
|
|
274
|
4320 @uref{ftp://ftp.cdrom.com/pub/tex/ctan/support/latex2html/}.
|
|
82
|
4321
|
|
353
|
4322 @node Q4.4.1, Q4.4.2, Q4.3.5, Subsystems
|
|
282
|
4323 @unnumberedsec 4.4: Sparcworks, EOS, and WorkShop
|
|
274
|
4324 @unnumberedsubsec Q4.4.1: What is SPARCworks, EOS, and WorkShop?
|
|
|
4325
|
|
|
4326 @email{turner@@lanl.gov, John Turner} writes:
|
|
82
|
4327
|
|
|
4328 @quotation
|
|
|
4329 SPARCworks is SunSoft's development environment, comprising compilers
|
|
|
4330 (C, C++, FORTRAN 77, Fortran 90, Ada, and Pascal), a debugger, and other
|
|
|
4331 tools such as TeamWare (for configuration management), MakeTool, etc.
|
|
|
4332 @end quotation
|
|
|
4333
|
|
282
|
4334 See @uref{http://www.sun.com/software/Developer-products/}
|
|
82
|
4335 for more info.
|
|
|
4336
|
|
|
4337 EOS stands for "Era on SPARCworks", but I don't know what Era stands
|
|
|
4338 for.
|
|
|
4339
|
|
|
4340 EOS is the integration of XEmacs with the SPARCworks debugger. It
|
|
|
4341 allows one to use an XEmacs frame to view code (complete with
|
|
|
4342 fontification, etc.), set breakpoints, print variables, etc., while
|
|
|
4343 using the SPARCworks debugger. It works very well and I use it all the
|
|
|
4344 time.
|
|
|
4345
|
|
274
|
4346 @email{cthomp@@xemacs.org, Chuck Thompson} writes:
|
|
82
|
4347
|
|
|
4348 @quotation
|
|
|
4349 Era stood for "Emacs Rewritten Again". It was what we were calling the
|
|
|
4350 modified version of Lucid Emacs for Sun when I was dragged, er, allowed
|
|
|
4351 to work on this wonderful editor.
|
|
|
4352 @end quotation
|
|
|
4353
|
|
274
|
4354 @email{martin@@xemacs.org, Martin Buchholz} writes:
|
|
82
|
4355
|
|
|
4356 @quotation
|
|
|
4357 EOS is being replaced with a new graphical development environment
|
|
|
4358 called Sun WorkShop, which is currently (07/96) in Alpha Test. For more
|
|
|
4359 details, check out
|
|
274
|
4360 @iftex
|
|
|
4361 @*
|
|
282
|
4362 @end iftex
|
|
359
|
4363 @uref{http://www.sun.com/software/Products/Developer-products}.
|
|
82
|
4364 @end quotation
|
|
|
4365
|
|
353
|
4366 @node Q4.4.2, Q4.5.1, Q4.4.1, Subsystems
|
|
|
4367 @unnumberedsubsec Q4.4.2: How do I start the Sun Workshop support in XEmacs 21?
|
|
|
4368
|
|
|
4369 Add the switch ---with-workshop to the configure command when building
|
|
|
4370 XEmacs and put the following in one of your startup files
|
|
|
4371 (e.g. site-start.el or .emacs):
|
|
|
4372
|
|
|
4373 @lisp
|
|
|
4374 (when (featurep 'tooltalk)
|
|
|
4375 (load "tooltalk-macros")
|
|
|
4376 (load "tooltalk-util")
|
|
|
4377 (load "tooltalk-init"))
|
|
|
4378 (when (featurep 'sparcworks)
|
|
|
4379 (load "sunpro-init")
|
|
|
4380 (load "ring")
|
|
|
4381 (load "comint")
|
|
|
4382 (load "annotations")
|
|
|
4383 (sunpro-startup))
|
|
|
4384 @end lisp
|
|
|
4385
|
|
|
4386 If you are not using the latest Workshop (5.0) you have to apply the
|
|
|
4387 following patch:
|
|
|
4388
|
|
|
4389 @format
|
|
|
4390 --- /opt/SUNWspro/lib/eserve.el.ORIG Fri May 14 15:23:26 1999
|
|
|
4391 +++ /opt/SUNWspro/lib/eserve.el Fri May 14 15:24:54 1999
|
|
|
4392 @@@@ -42,7 +42,7 @@@@
|
|
|
4393 (defvar running-xemacs nil "t if we're running XEmacs")
|
|
|
4394 (defvar running-emacs nil "t if we're running GNU Emacs 19")
|
|
365
|
4395
|
|
353
|
4396 -(if (string-match "^\\(19\\|20\\)\..*\\(XEmacs\\|Lucid\\)" emacs-version)
|
|
|
4397 +(if (string-match "\\(XEmacs\\|Lucid\\)" emacs-version)
|
|
|
4398 (setq running-xemacs t)
|
|
|
4399 (setq running-emacs t))
|
|
365
|
4400 @end format
|
|
353
|
4401
|
|
|
4402
|
|
|
4403
|
|
|
4404 @node Q4.5.1, Q4.6.1, Q4.4.2, Subsystems
|
|
282
|
4405 @unnumberedsec 4.5: Energize
|
|
274
|
4406 @unnumberedsubsec Q4.5.1: What is/was Energize?
|
|
|
4407
|
|
|
4408 @email{gray@@meteor.harlequin.com, David N Gray} writes:
|
|
82
|
4409 @quotation
|
|
|
4410 The files in @file{lisp/energize} are to enable Emacs to interface with
|
|
|
4411 the "Energize Programming System", a C and C++ development environment,
|
|
|
4412 which was a product of Lucid, Inc. Tragically, Lucid went out of
|
|
|
4413 business in 1994, so although Energize is still a great system, if you
|
|
|
4414 don't already have it, there isn't any way to get it now. (Unless you
|
|
|
4415 happen to be in Japan; INS Engineering may still be selling it there.
|
|
|
4416 Tartan bought the rights to sell it in the rest of the world, but never
|
|
|
4417 did so.)
|
|
|
4418 @end quotation
|
|
|
4419
|
|
|
4420 @node Q4.6.1, Q4.7.1, Q4.5.1, Subsystems
|
|
282
|
4421 @unnumberedsec 4.6: Infodock
|
|
274
|
4422 @unnumberedsubsec Q4.6.1: What is Infodock?
|
|
82
|
4423
|
|
0
|
4424 InfoDock is an integrated productivity toolset, mainly aimed at
|
|
86
|
4425 technical people. It is developed and supported by InfoDock
|
|
|
4426 Associates, a firm that offers custom support and development
|
|
274
|
4427 for InfoDock, XEmacs and GNU Emacs. ( @uref{http://www.infodock.com},
|
|
|
4428 @email{info@@infodock.com}, +1 408 243 3300).
|
|
86
|
4429
|
|
|
4430 InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of
|
|
|
4431 the power of Emacs, but with an easier to use and more comprehensive
|
|
|
4432 menu-based user interface. The bottom portion of this text describes
|
|
|
4433 how it differs from XEmacs and GNU Emacs from the Free Software
|
|
|
4434 Foundation.
|
|
0
|
4435
|
|
|
4436 InfoDock is aimed at people who want a free, turn-key productivity
|
|
|
4437 environment. Although InfoDock is customizable, it is not intended for
|
|
|
4438 people who like basic versions of Emacs which need to be customized
|
|
|
4439 extensively for local use; standard Emacs distributions are better for
|
|
|
4440 such uses. InfoDock is for those people who want a complete,
|
|
|
4441 pre-customized environment in one package, which they need not touch
|
|
|
4442 more than once or twice a year to update to new revisions.
|
|
|
4443
|
|
86
|
4444 InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX,
|
|
|
4445 and Intel Linux systems. It is intended for use on a color display,
|
|
|
4446 although most features will work on monochrome monitors. Simply unpack
|
|
|
4447 InfoDock according to the instructions in the ID-INSTALL file and you
|
|
|
4448 are ready to run.
|
|
0
|
4449
|
|
|
4450 The InfoDock Manual is concise, yet sufficient as a user guide for users
|
|
|
4451 who have never used an Emacs-type editor before. For users who are
|
|
|
4452 already familiar with Emacs, it supplements the information in the GNU
|
|
|
4453 Emacs Manual.
|
|
|
4454
|
|
|
4455 InfoDock menus are much more extensive and more mature than standard
|
|
86
|
4456 Emacs menus. Each menu offers a @samp{Manual} item which displays
|
|
0
|
4457 documentation associated with the menu's functions.
|
|
282
|
4458
|
|
86
|
4459 @noindent
|
|
|
4460 Four types of menubars are provided:
|
|
0
|
4461 @enumerate
|
|
|
4462 @item
|
|
|
4463 An extensive menubar providing access to global InfoDock commands.
|
|
|
4464 @item
|
|
|
4465 Mode-specific menubars tailored to the current major mode.
|
|
|
4466 @item
|
|
86
|
4467 A simple menubar for basic editing to help novices get started with InfoDock.
|
|
|
4468 @item
|
|
|
4469 The standard XEmacs menubar.
|
|
0
|
4470 @end enumerate
|
|
|
4471
|
|
86
|
4472 Most modes also include mode-specific popup menus. Additionally, region and
|
|
|
4473 rectangle popup menus are included.
|
|
|
4474
|
|
|
4475 @samp{Hyperbole}, the everyday information manager, is a core part of
|
|
0
|
4476 InfoDock. This provides context-sensitive mouse keys, a rolodex-type
|
|
|
4477 contact manager, programmable hypertext buttons, and an autonumbered
|
|
|
4478 outliner with embedded hyperlink anchors.
|
|
82
|
4479
|
|
86
|
4480 The @samp{OO-Browser}, a multi-language object-oriented code browser, is a
|
|
|
4481 standard part of InfoDock.
|
|
0
|
4482
|
|
|
4483 InfoDock saves a more extensive set of user options than other Emacs
|
|
|
4484 versions.
|
|
|
4485
|
|
|
4486 InfoDock inserts a useful file header in many file types, showing the
|
|
|
4487 author, summary, and last modification time of each file. A summary
|
|
|
4488 program can then be used to summarize all of the files in a directory,
|
|
|
4489 for easy MANIFEST file creation.
|
|
|
4490
|
|
|
4491 Your working set of buffers is automatically saved and restored (if you
|
|
|
4492 answer yes to a prompt) between InfoDock sessions.
|
|
|
4493
|
|
86
|
4494 Refined color choices for code highlighting are provided for both dark and
|
|
|
4495 light background display frames.
|
|
|
4496
|
|
|
4497 The @kbd{C-z} key prefix performs frame-based commands which parallel the
|
|
|
4498 @kbd{C-x} key prefix for window-based commands.
|
|
0
|
4499
|
|
|
4500 The Smart Menu system is included for producing command menus on dumb
|
|
86
|
4501 terminals.
|
|
0
|
4502
|
|
|
4503 Lisp libraries are better categorized according to function.
|
|
|
4504
|
|
86
|
4505 Extensions and improvements to many areas of Emacs are included, such as:
|
|
|
4506 paragraph filling, mail reading with Rmail, shell handling, outlining, code
|
|
|
4507 highlighting and browsing, and man page browsing.
|
|
0
|
4508
|
|
|
4509 InfoDock questions, answers and discussion should go to the mail list
|
|
274
|
4510 @iftex
|
|
|
4511 @*
|
|
282
|
4512 @end iftex
|
|
274
|
4513 @email{infodock@@infodock.com}. Use
|
|
|
4514 @email{infodock-request@@infodock.com} to be added or removed from the
|
|
86
|
4515 list. Always include your InfoDock version number when sending help
|
|
|
4516 requests.
|
|
|
4517
|
|
|
4518 InfoDock is available across the Internet via anonymous FTP. To get
|
|
|
4519 it, first move to a directory into which you want the InfoDock archive
|
|
|
4520 files placed. We will call this <DIST-DIR>.
|
|
282
|
4521
|
|
86
|
4522 @example
|
|
|
4523 cd <DIST-DIR>
|
|
|
4524 @end example
|
|
|
4525
|
|
|
4526 Ftp to ftp.xemacs.org (Internet Host ID = 128.174.252.16):
|
|
82
|
4527
|
|
0
|
4528 @example
|
|
86
|
4529 prompt> ftp ftp.xemacs.org
|
|
0
|
4530 @end example
|
|
|
4531
|
|
86
|
4532 Login as @samp{anonymous} with your own <user-id>@@<site-name> as a password.
|
|
|
4533
|
|
282
|
4534 @example
|
|
86
|
4535 Name (ftp.xemacs.org): anonymous
|
|
|
4536 331 Guest login ok, send your complete e-mail address as password.
|
|
274
|
4537 Password: -<your-user-id>@@<your-domain>
|
|
86
|
4538 230 Guest login ok, access restrictions apply.
|
|
0
|
4539 @end example
|
|
|
4540
|
|
|
4541 Move to the location of the InfoDock archives:
|
|
|
4542
|
|
|
4543 @example
|
|
86
|
4544 ftp> cd pub/infodock
|
|
0
|
4545 @end example
|
|
|
4546
|
|
|
4547 Set your transfer mode to binary:
|
|
|
4548
|
|
|
4549 @example
|
|
86
|
4550 ftp> bin
|
|
|
4551 200 Type set to I.
|
|
0
|
4552 @end example
|
|
|
4553
|
|
|
4554 Turn off prompting:
|
|
|
4555
|
|
|
4556 @example
|
|
86
|
4557 ftp> prompt
|
|
|
4558 Interactive mode off.
|
|
0
|
4559 @end example
|
|
|
4560
|
|
|
4561 Retrieve the InfoDock archives that you want, either by using a
|
|
86
|
4562 @samp{get <file>} for each file you want or by using the following to
|
|
0
|
4563 get a complete distribution, including all binaries:
|
|
|
4564
|
|
|
4565 @example
|
|
86
|
4566 ftp> mget ID-INSTALL
|
|
|
4567 ftp> mget id-*
|
|
0
|
4568 @end example
|
|
|
4569
|
|
|
4570 Close the FTP connection:
|
|
|
4571
|
|
|
4572 @example
|
|
86
|
4573 ftp> quit
|
|
|
4574 221 Goodbye.
|
|
0
|
4575 @end example
|
|
|
4576
|
|
|
4577 Read the @file{ID-INSTALL} file which you just retrieved for
|
|
|
4578 step-by-step installation instructions.
|
|
|
4579
|
|
82
|
4580 @node Q4.7.1, Q4.7.2, Q4.6.1, Subsystems
|
|
282
|
4581 @unnumberedsec 4.7: Other Unbundled Packages
|
|
274
|
4582 @unnumberedsubsec Q4.7.1: What is AUC TeX? Where do you get it?
|
|
|
4583
|
|
|
4584 AUC TeX is a package written by @email{abraham@@dina.kvl.dk, Per Abrahamsen}.
|
|
213
|
4585 Starting with XEmacs 19.16, AUC TeX is bundled with XEmacs. The
|
|
163
|
4586 following information is from the @file{README} and website.
|
|
82
|
4587
|
|
|
4588 AUC TeX is an extensible package that supports writing and formatting
|
|
|
4589 TeX files for most variants of GNU Emacs. Many different macro packages
|
|
|
4590 are supported, including AMS TeX, LaTeX, and TeXinfo.
|
|
|
4591
|
|
|
4592 The most recent version is always available by ftp at
|
|
274
|
4593 @iftex
|
|
|
4594 @*
|
|
282
|
4595 @end iftex
|
|
274
|
4596 @uref{ftp://sunsite.auc.dk/packages/auctex/auctex.tar.gz}.
|
|
82
|
4597
|
|
|
4598 In case you don't have access to anonymous ftp, you can get it by an
|
|
274
|
4599 email request to @email{ftpmail@@decwrl.dec.com}.
|
|
82
|
4600
|
|
|
4601 WWW users may want to check out the AUC TeX page at
|
|
274
|
4602 @iftex
|
|
|
4603 @*
|
|
282
|
4604 @end iftex
|
|
274
|
4605 @uref{http://sunsite.auc.dk/auctex/}.
|
|
82
|
4606
|
|
|
4607 @node Q4.7.2, Q4.7.3, Q4.7.1, Subsystems
|
|
274
|
4608 @unnumberedsubsec Q4.7.2: Are there any Emacs Lisp Spreadsheets?
|
|
82
|
4609
|
|
|
4610 Yes. Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at
|
|
274
|
4611 @iftex
|
|
|
4612 @*
|
|
282
|
4613 @end iftex
|
|
274
|
4614 @uref{ftp://cs.nyu.edu/pub/local/fox/dismal/}.
|
|
82
|
4615
|
|
|
4616 @node Q4.7.3, Q4.7.4, Q4.7.2, Subsystems
|
|
365
|
4617 @unnumberedsubsec Q4.7.3: [This question intentionally left blank]
|
|
82
|
4618
|
|
163
|
4619 @node Q4.7.4, Q4.7.5, Q4.7.3, Subsystems
|
|
274
|
4620 @unnumberedsubsec Q4.7.4: Problems installing AUC TeX.
|
|
|
4621
|
|
|
4622 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
|
|
82
|
4623
|
|
|
4624 @quotation
|
|
163
|
4625 AUC TeX works fine on both stock Emacs and XEmacs has been doing so for
|
|
274
|
4626 a very very long time. This is mostly due to the work of
|
|
|
4627 @email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu}
|
|
82
|
4628 package. Which leads to what is probably the problem...
|
|
|
4629 @end quotation
|
|
|
4630
|
|
163
|
4631 Most problems with AUC TeX are one of two things:
|
|
0
|
4632
|
|
|
4633 @itemize @bullet
|
|
|
4634 @item
|
|
82
|
4635 The TeX-lisp-directory in @file{tex-site.el} and the makefile don't
|
|
|
4636 match.
|
|
|
4637
|
|
163
|
4638 Fix: make sure you configure AUC TeX properly @strong{before} installing.
|
|
82
|
4639
|
|
54
|
4640 @item
|
|
82
|
4641 You have an old version of easymenu.el in your path.
|
|
|
4642
|
|
|
4643 Fix: use @code{locate-library} and remove old versions to make sure it
|
|
|
4644 @strong{only} finds the one that came with XEmacs.
|
|
70
|
4645 @end itemize
|
|
|
4646
|
|
163
|
4647
|
|
282
|
4648 @node Q4.7.5, Q4.7.6, Q4.7.4, Subsystems
|
|
274
|
4649 @unnumberedsubsec Q4.7.5: Is there a reason for an Emacs package not to be included in XEmacs?
|
|
163
|
4650
|
|
|
4651 The reason for an Emacs package not to be included in XEmacs is
|
|
|
4652 usually one or more of the following:
|
|
|
4653
|
|
|
4654 @enumerate
|
|
|
4655 @item
|
|
|
4656 The package has not been ported to XEmacs. This will typically happen
|
|
|
4657 when it uses GNU-Emacs-specific features, which make it fail under
|
|
|
4658 XEmacs.
|
|
|
4659
|
|
|
4660 Porting a package to XEmacs can range from a trivial amount of change to
|
|
|
4661 a partial or full rewrite. Fortunately, the authors of modern packages
|
|
|
4662 usually choose to support both Emacsen themselves.
|
|
|
4663
|
|
|
4664 @item
|
|
|
4665 The package has been decided not to be appropriate for XEmacs. It may
|
|
|
4666 have an equivalent or better replacement within XEmacs, in which case
|
|
|
4667 the developers may choose not to burden themselves with supporting an
|
|
|
4668 additional package.
|
|
|
4669
|
|
|
4670 Each package bundled with XEmacs means more work for the maintainers,
|
|
|
4671 whether they want it or not. If you are ready to take over the
|
|
217
|
4672 maintenance responsibilities for the package you port, be sure to say
|
|
365
|
4673 so---we will more likely include it.
|
|
163
|
4674
|
|
|
4675 @item
|
|
|
4676 The package simply hasn't been noted by the XEmacs development. If
|
|
|
4677 that's the case, the messages like yours are very useful for attracting
|
|
|
4678 our attention.
|
|
|
4679
|
|
|
4680 @item
|
|
|
4681 The package was noted by the developers, but they simply haven't yet
|
|
|
4682 gotten around to including/porting it. Wait for the next release or,
|
|
|
4683 even better, offer your help. It will be gladly accepted and
|
|
|
4684 appreciated.
|
|
|
4685 @end enumerate
|
|
|
4686
|
|
282
|
4687 @node Q4.7.6, , Q4.7.5, Subsystems
|
|
|
4688 @unnumberedsubsec Q4.7.5: Is there a MatLab mode?
|
|
365
|
4689
|
|
|
4690 Yes, a matlab mode and other items are available at the
|
|
|
4691 @uref{ftp://ftp.mathworks.com/pub/contrib/emacs_add_ons,
|
|
|
4692 MathWorks' emacs_add_ons ftp directory}.
|
|
282
|
4693
|
|
359
|
4694 @node Miscellaneous, MS Windows, Subsystems, Top
|
|
274
|
4695 @unnumbered 5 The Miscellaneous Stuff
|
|
82
|
4696
|
|
|
4697 This is part 5 of the XEmacs Frequently Asked Questions list. This
|
|
|
4698 section is devoted to anything that doesn't fit neatly into the other
|
|
|
4699 sections.
|
|
70
|
4700
|
|
|
4701 @menu
|
|
82
|
4702 Major & Minor Modes:
|
|
|
4703 * Q5.0.1:: How can I do source code highlighting using font-lock?
|
|
|
4704 * Q5.0.2:: I do not like cc-mode. How do I use the old c-mode?
|
|
|
4705 * Q5.0.3:: How do I get @samp{More} Syntax Highlighting on by default?
|
|
|
4706 * Q5.0.4:: How can I enable auto-indent?
|
|
|
4707 * Q5.0.5:: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
|
4708 * Q5.0.6:: How do I start up a second shell buffer?
|
|
|
4709 * Q5.0.7:: Telnet from shell filters too much.
|
|
|
4710 * Q5.0.8:: Why does edt emulation not work?
|
|
|
4711 * Q5.0.9:: How can I emulate VI and use it as my default mode?
|
|
282
|
4712 * Q5.0.10:: [This question intentionally left blank]
|
|
365
|
4713 * Q5.0.11:: How do I turn on filladapt for all buffers?
|
|
82
|
4714 * Q5.0.12:: How do I disable gnuserv from opening a new frame?
|
|
|
4715 * Q5.0.13:: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
|
4716 * Q5.0.14:: Strange things are happening in Shell Mode.
|
|
|
4717 * Q5.0.15:: Where do I get the latest CC Mode?
|
|
|
4718 * Q5.0.16:: I find auto-show-mode disconcerting. How do I turn it off?
|
|
|
4719 * Q5.0.17:: How can I get two instances of info?
|
|
365
|
4720 * Q5.0.18:: [This question intentionally left blank]
|
|
82
|
4721 * Q5.0.19:: Is there something better than LaTeX mode?
|
|
274
|
4722 * Q5.0.20:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
82
|
4723
|
|
|
4724 Emacs Lisp Programming Techniques:
|
|
|
4725 * Q5.1.1:: The difference in key sequences between XEmacs and GNU Emacs?
|
|
|
4726 * Q5.1.2:: Can I generate "fake" keyboard events?
|
|
163
|
4727 * Q5.1.3:: Could you explain @code{read-kbd-macro} in more detail?
|
|
|
4728 * Q5.1.4:: What is the performance hit of @code{let}?
|
|
|
4729 * Q5.1.5:: What is the recommended use of @code{setq}?
|
|
213
|
4730 * Q5.1.6:: What is the typical misuse of @code{setq}?
|
|
367
|
4731 * Q5.1.7:: I like the @code{do} form of cl, does it slow things down?
|
|
163
|
4732 * Q5.1.8:: I like recursion, does it slow things down?
|
|
|
4733 * Q5.1.9:: How do I put a glyph as annotation in a buffer?
|
|
213
|
4734 * Q5.1.10:: @code{map-extents} won't traverse all of my extents!
|
|
282
|
4735 * Q5.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time?
|
|
82
|
4736
|
|
|
4737 Sound:
|
|
|
4738 * Q5.2.1:: How do I turn off the sound?
|
|
163
|
4739 * Q5.2.2:: How do I get funky sounds instead of a boring beep?
|
|
82
|
4740 * Q5.2.3:: What's NAS, how do I get it?
|
|
|
4741 * Q5.2.4:: Sunsite sounds don't play.
|
|
|
4742
|
|
|
4743 Miscellaneous:
|
|
|
4744 * Q5.3.1:: How do you make XEmacs indent CL if-clauses correctly?
|
|
|
4745 * Q5.3.2:: Fontifying hangs when editing a postscript file.
|
|
|
4746 * Q5.3.3:: How can I print WYSIWYG a font-locked buffer?
|
|
|
4747 * Q5.3.4:: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
|
4748 * Q5.3.5:: How do I specify the paths that XEmacs uses for finding files?
|
|
|
4749 * Q5.3.6:: [This question intentionally left blank]
|
|
|
4750 * Q5.3.7:: Can I have the end of the buffer delimited in some way?
|
|
|
4751 * Q5.3.8:: How do I insert today's date into a buffer?
|
|
|
4752 * Q5.3.9:: Are only certain syntactic character classes available for abbrevs?
|
|
|
4753 * Q5.3.10:: How can I get those oh-so-neat X-Face lines?
|
|
|
4754 * Q5.3.11:: How do I add new Info directories?
|
|
|
4755 * Q5.3.12:: What do I need to change to make printing work?
|
|
70
|
4756 @end menu
|
|
|
4757
|
|
82
|
4758 @node Q5.0.1, Q5.0.2, Miscellaneous, Miscellaneous
|
|
282
|
4759 @unnumberedsec 5.0: Major & Minor Modes
|
|
274
|
4760 @unnumberedsubsec Q5.0.1: How can I do source code highlighting using font-lock?
|
|
82
|
4761
|
|
|
4762 For most modes, font-lock is already set up and just needs to be turned
|
|
|
4763 on. This can be done by @kbd{M-x font-lock-mode}, or by having XEmacs
|
|
|
4764 automatically start it by adding lines like:
|
|
|
4765
|
|
|
4766 @lisp
|
|
365
|
4767 (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
|
|
|
4768 (add-hook 'dired-mode-hook 'turn-on-font-lock)
|
|
82
|
4769 @end lisp
|
|
|
4770
|
|
|
4771 to your @file{.emacs}. See the file @file{etc/sample.emacs} for more
|
|
|
4772 examples.
|
|
|
4773
|
|
215
|
4774 See also @code{Syntax Highlighting} from the @code{Options} menu.
|
|
|
4775 Remember to save options.
|
|
|
4776
|
|
82
|
4777 @node Q5.0.2, Q5.0.3, Q5.0.1, Miscellaneous
|
|
274
|
4778 @unnumberedsubsec Q5.0.2: I do not like cc-mode. How do I use the old c-mode?
|
|
82
|
4779
|
|
|
4780 Well, first off, consider if you really want to do this. cc-mode is
|
|
|
4781 much more powerful than the old c-mode. If you're having trouble
|
|
|
4782 getting your old offsets to work, try using @code{c-set-offset} instead.
|
|
|
4783 You might also consider using the package @code{cc-compat}.
|
|
|
4784
|
|
|
4785 But, if you still insist, add the following lines to your @file{.emacs}:
|
|
|
4786
|
|
|
4787 @lisp
|
|
|
4788 (fmakunbound 'c-mode)
|
|
|
4789 (makunbound 'c-mode-map)
|
|
|
4790 (fmakunbound 'c++-mode)
|
|
|
4791 (makunbound 'c++-mode-map)
|
|
|
4792 (makunbound 'c-style-alist)
|
|
|
4793 (load-library "old-c-mode")
|
|
282
|
4794 (load-library "old-c++-mode")
|
|
82
|
4795 @end lisp
|
|
|
4796
|
|
|
4797 This must be done before any other reference is made to either c-mode or
|
|
|
4798 c++-mode.
|
|
|
4799
|
|
|
4800 @node Q5.0.3, Q5.0.4, Q5.0.2, Miscellaneous
|
|
274
|
4801 @unnumberedsubsec Q5.0.3: How do I get @samp{More} Syntax Highlighting on by default?
|
|
82
|
4802
|
|
163
|
4803 Use the following code in your @file{.emacs}:
|
|
82
|
4804
|
|
|
4805 @lisp
|
|
163
|
4806 (setq-default font-lock-maximum-decoration t)
|
|
82
|
4807 @end lisp
|
|
|
4808
|
|
163
|
4809 In versions of XEmacs prior to 19.14, you had to use a kludgy solution
|
|
|
4810 like this:
|
|
|
4811
|
|
|
4812 @lisp
|
|
|
4813 (setq c-font-lock-keywords c-font-lock-keywords-2
|
|
|
4814 c++-font-lock-keywords c++-font-lock-keywords-2
|
|
|
4815 lisp-font-lock-keywords lisp-font-lock-keywords-2)
|
|
|
4816 @end lisp
|
|
|
4817
|
|
|
4818 It will work for C, C++ and Lisp.
|
|
|
4819
|
|
215
|
4820 See also @code{Syntax Highlighting} from the @code{Options} menu.
|
|
|
4821 Remember to save options.
|
|
|
4822
|
|
82
|
4823 @node Q5.0.4, Q5.0.5, Q5.0.3, Miscellaneous
|
|
274
|
4824 @unnumberedsubsec Q5.0.4: How can I enable auto-indent?
|
|
82
|
4825
|
|
|
4826 Put the following line in your @file{.emacs}:
|
|
|
4827
|
|
|
4828 @lisp
|
|
|
4829 (setq indent-line-function 'indent-relative-maybe)
|
|
|
4830 @end lisp
|
|
|
4831
|
|
|
4832 If you want to get fancy, try the @code{filladapt} package available
|
|
|
4833 standard with XEmacs. Put this into your @file{.emacs}:
|
|
|
4834
|
|
|
4835 @lisp
|
|
|
4836 (require 'filladapt)
|
|
|
4837 (add-hook 'text-mode-hook 'turn-on-filladapt-mode)
|
|
163
|
4838 ;;; and others ...
|
|
82
|
4839 @end lisp
|
|
|
4840
|
|
215
|
4841 You can customize filling and adaptive filling with Customize.
|
|
|
4842 Select from the @code{Options} menu
|
|
|
4843 @code{Customize->Emacs->->Editing->Fill->Fill...}
|
|
282
|
4844 or type @kbd{M-x customize @key{RET} fill @key{RET}}.
|
|
215
|
4845
|
|
163
|
4846 Note that well-behaving text-lookalike modes will run
|
|
|
4847 @code{text-mode-hook} by default (e.g. that's what Message does). For
|
|
|
4848 the nasty ones, you'll have to provide the @code{add-hook}s yourself.
|
|
|
4849
|
|
82
|
4850 Please note that the @code{fa-extras} package is no longer useful.
|
|
|
4851
|
|
|
4852 @node Q5.0.5, Q5.0.6, Q5.0.4, Miscellaneous
|
|
274
|
4853 @unnumberedsubsec Q5.0.5: How can I get XEmacs to come up in text/auto-fill mode by default?
|
|
82
|
4854
|
|
|
4855 Try the following lisp in your @file{.emacs}:
|
|
|
4856
|
|
|
4857 @lisp
|
|
|
4858 (setq default-major-mode 'text-mode)
|
|
|
4859 (setq text-mode-hook 'turn-on-auto-fill)
|
|
|
4860 @end lisp
|
|
|
4861
|
|
|
4862 @strong{WARNING}: note that changing the value of
|
|
|
4863 @code{default-major-mode} from @code{fundamental-mode} can break a large
|
|
|
4864 amount of built-in code that expects newly created buffers to be in
|
|
|
4865 @code{fundamental-mode}. (Changing from @code{fundamental-mode} to
|
|
|
4866 @code{text-mode} might not wreak too much havoc, but changing to
|
|
|
4867 something more exotic like a lisp-mode would break many Emacs packages).
|
|
|
4868
|
|
|
4869 Note that Emacs by default starts up in buffer @code{*scratch*} in
|
|
|
4870 @code{initial-major-mode}, which defaults to
|
|
|
4871 @code{lisp-interaction-mode}. Thus adding the following form to your
|
|
|
4872 Emacs init file will cause the initial @code{*scratch*} buffer to be put
|
|
|
4873 into auto-fill'ed @code{text-mode}:
|
|
|
4874
|
|
|
4875 @lisp
|
|
|
4876 (setq initial-major-mode
|
|
163
|
4877 (lambda ()
|
|
82
|
4878 (text-mode)
|
|
163
|
4879 (turn-on-auto-fill)))
|
|
82
|
4880 @end lisp
|
|
|
4881
|
|
|
4882 Note that after your init file is loaded, if
|
|
163
|
4883 @code{inhibit-startup-message} is @code{nil} (the default) and the
|
|
|
4884 startup buffer is @code{*scratch*} then the startup message will be
|
|
|
4885 inserted into @code{*scratch*}; it will be removed after a timeout by
|
|
|
4886 erasing the entire @code{*scratch*} buffer. Keep in mind this default
|
|
|
4887 usage of @code{*scratch*} if you desire any prior manipulation of
|
|
82
|
4888 @code{*scratch*} from within your Emacs init file. In particular,
|
|
|
4889 anything you insert into @code{*scratch*} from your init file will be
|
|
|
4890 later erased. Also, if you change the mode of the @code{*scratch*}
|
|
|
4891 buffer, be sure that this will not interfere with possible later
|
|
|
4892 insertion of the startup message (e.g. if you put @code{*scratch*} into
|
|
|
4893 a nonstandard mode that has automatic font lock rules, then the startup
|
|
|
4894 message might get fontified in a strange foreign manner, e.g. as code in
|
|
|
4895 some programming language).
|
|
|
4896
|
|
|
4897 @node Q5.0.6, Q5.0.7, Q5.0.5, Miscellaneous
|
|
274
|
4898 @unnumberedsubsec Q5.0.6: How do I start up a second shell buffer?
|
|
82
|
4899
|
|
|
4900 In the @code{*shell*} buffer:
|
|
|
4901
|
|
|
4902 @lisp
|
|
282
|
4903 M-x rename-buffer @key{RET} *shell-1* @key{RET}
|
|
82
|
4904 M-x shell RET
|
|
|
4905 @end lisp
|
|
|
4906
|
|
|
4907 This will then start a second shell. The key is that no buffer named
|
|
|
4908 @samp{*shell*} can exist. It might be preferable to use @kbd{M-x
|
|
|
4909 rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x
|
|
|
4910 rename-buffer}.
|
|
|
4911
|
|
353
|
4912 Alternately, you can set the variable @code{shell-multiple-shells}.
|
|
365
|
4913 If the value of this variable is non-nil, each time shell mode is invoked,
|
|
353
|
4914 a new shell is made
|
|
|
4915
|
|
82
|
4916 @node Q5.0.7, Q5.0.8, Q5.0.6, Miscellaneous
|
|
274
|
4917 @unnumberedsubsec Q5.0.7: Telnet from shell filters too much
|
|
82
|
4918
|
|
|
4919 I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke
|
|
|
4920 and use a telnet session within it. Everything works fine except that
|
|
|
4921 now all @samp{^M}'s are filtered out by Emacs. Fixes?
|
|
|
4922
|
|
|
4923 Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather
|
|
227
|
4924 than doing rsh or telnet within the local shell buffer. Starting with
|
|
|
4925 XEmacs-20.3 you can also use @kbd{M-x ssh} to open secure remote session
|
|
|
4926 if you have @code{ssh} installed.
|
|
82
|
4927
|
|
|
4928 @node Q5.0.8, Q5.0.9, Q5.0.7, Miscellaneous
|
|
274
|
4929 @unnumberedsubsec Q5.0.8: Why does edt emulation not work?
|
|
82
|
4930
|
|
|
4931 We don't know, but you can use tpu-edt emulation instead, which works
|
|
|
4932 fine and is a little fancier than the standard edt emulation. To do
|
|
|
4933 this, add the following line to your @file{.emacs}:
|
|
|
4934
|
|
|
4935 @lisp
|
|
163
|
4936 (tpu-edt)
|
|
82
|
4937 @end lisp
|
|
|
4938
|
|
|
4939 If you don't want it to replace @kbd{C-h} with an edt-style help menu
|
|
|
4940 add this as well:
|
|
|
4941
|
|
|
4942 @lisp
|
|
163
|
4943 (global-set-key [(control h)] 'help-for-help)
|
|
82
|
4944 @end lisp
|
|
|
4945
|
|
|
4946 @node Q5.0.9, Q5.0.10, Q5.0.8, Miscellaneous
|
|
274
|
4947 @unnumberedsubsec Q5.0.9: How can I emulate VI and use it as my default mode?
|
|
82
|
4948
|
|
|
4949 Our recommended VI emulator is viper. To make viper-mode the default,
|
|
|
4950 add this to your @file{.emacs}:
|
|
|
4951
|
|
|
4952 @lisp
|
|
|
4953 (viper-mode)
|
|
|
4954 @end lisp
|
|
|
4955
|
|
274
|
4956 @email{kifer@@CS.SunySB.EDU, Michael Kifer} writes:
|
|
82
|
4957
|
|
|
4958 @quotation
|
|
|
4959 This should be added as close to the top of @file{.emacs} as you can get
|
|
|
4960 it, otherwise some minor modes may not get viper-ized.
|
|
|
4961 @end quotation
|
|
|
4962
|
|
|
4963 @node Q5.0.10, Q5.0.11, Q5.0.9, Miscellaneous
|
|
274
|
4964 @unnumberedsubsec Q5.0.10: [This question intentionally left blank]
|
|
126
|
4965
|
|
|
4966 Obsolete question, left blank to avoid renumbering
|
|
282
|
4967
|
|
82
|
4968 @node Q5.0.11, Q5.0.12, Q5.0.10, Miscellaneous
|
|
365
|
4969 @unnumberedsubsec Q5.0.11: How do I turn on filladapt for all buffers?
|
|
|
4970
|
|
|
4971 Filladapt is a minor mode and minor modes are traditionally off by
|
|
|
4972 default. The following added to your @file{.emacs} will turn it on for
|
|
|
4973 all buffers:
|
|
82
|
4974
|
|
|
4975 @lisp
|
|
|
4976 (setq-default filladapt-mode t)
|
|
|
4977 @end lisp
|
|
|
4978
|
|
|
4979 Use @code{turn-on-filladapt-mode} to turn Filladapt on in particular
|
|
|
4980 major modes, like this:
|
|
|
4981
|
|
|
4982 @lisp
|
|
282
|
4983 (add-hook 'text-mode-hook 'turn-on-filladapt-mode)
|
|
82
|
4984 @end lisp
|
|
|
4985
|
|
|
4986 @node Q5.0.12, Q5.0.13, Q5.0.11, Miscellaneous
|
|
274
|
4987 @unnumberedsubsec Q5.0.12: How do I disable gnuserv from opening a new frame?
|
|
82
|
4988
|
|
|
4989 If you set the @code{gnuserv-frame} variable to the frame that should be
|
|
|
4990 used to display buffers that are pulled up, a new frame will not be
|
|
|
4991 created. For example, you could put
|
|
|
4992
|
|
|
4993 @lisp
|
|
|
4994 (setq gnuserv-frame (selected-frame))
|
|
|
4995 @end lisp
|
|
|
4996
|
|
|
4997 early on in your @file{.emacs}, to ensure that the first frame created
|
|
|
4998 is the one used for your gnuserv buffers.
|
|
|
4999
|
|
|
5000 Starting in 19.15, there is an option to set the gnuserv target to
|
|
|
5001 the current frame. See
|
|
|
5002 @code{Options->"Other Window" Location->Make current frame gnuserv target}
|
|
|
5003
|
|
227
|
5004 Starting with XEmacs-20.3 you can also change this with Customize.
|
|
|
5005 Select from the @code{Options} menu
|
|
|
5006 @code{Customize->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type
|
|
282
|
5007 @kbd{M-x customize @key{RET} gnuserv @key{RET}}.
|
|
227
|
5008
|
|
|
5009
|
|
82
|
5010 @node Q5.0.13, Q5.0.14, Q5.0.12, Miscellaneous
|
|
274
|
5011 @unnumberedsubsec Q5.0.13: How do I start gnuserv so that each subsequent XEmacs is a client?
|
|
82
|
5012
|
|
|
5013 Put the following in your @file{.emacs} file to start the server:
|
|
|
5014
|
|
|
5015 @lisp
|
|
|
5016 (gnuserv-start)
|
|
|
5017 @end lisp
|
|
|
5018
|
|
|
5019 Start your first XEmacs as usual. After that, you can do:
|
|
70
|
5020
|
|
|
5021 @example
|
|
82
|
5022 gnuclient randomfilename
|
|
70
|
5023 @end example
|
|
|
5024
|
|
82
|
5025 from the command line to get your existing XEmacs process to open a new
|
|
|
5026 frame and visit randomfilename in that window. When you're done editing
|
|
|
5027 randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the
|
|
|
5028 frame.
|
|
|
5029
|
|
227
|
5030 See also man page of gnuclient.
|
|
|
5031
|
|
82
|
5032 @node Q5.0.14, Q5.0.15, Q5.0.13, Miscellaneous
|
|
274
|
5033 @unnumberedsubsec Q5.0.14: Strange things are happening in Shell Mode.
|
|
82
|
5034
|
|
|
5035 Sometimes (i.e. it's not repeatable, and I can't work out why it
|
|
|
5036 happens) when I'm typing into shell mode, I hit return and only a
|
|
|
5037 portion of the command is given to the shell, and a blank prompt is
|
|
|
5038 returned. If I hit return again, the rest of the previous command is
|
|
|
5039 given to the shell.
|
|
|
5040
|
|
274
|
5041 @email{martin@@xemacs.org, Martin Buchholz} writes:
|
|
82
|
5042
|
|
|
5043 @quotation
|
|
|
5044 There is a known problem with interaction between @code{csh} and the
|
|
|
5045 @code{filec} option and XEmacs. You should add the following to your
|
|
|
5046 @file{.cshrc}:
|
|
70
|
5047
|
|
|
5048 @example
|
|
82
|
5049 if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec
|
|
70
|
5050 @end example
|
|
82
|
5051 @end quotation
|
|
|
5052
|
|
|
5053 @node Q5.0.15, Q5.0.16, Q5.0.14, Miscellaneous
|
|
274
|
5054 @unnumberedsubsec Q5.0.15: Where do I get the latest CC Mode?
|
|
|
5055
|
|
|
5056 @email{bwarsaw@@cnri.reston.va.us, Barry A. Warsaw} writes:
|
|
82
|
5057
|
|
|
5058 @quotation
|
|
359
|
5059 This can be had from @uref{http://www.python.org/emacs/}.
|
|
82
|
5060 @end quotation
|
|
|
5061
|
|
|
5062 @node Q5.0.16, Q5.0.17, Q5.0.15, Miscellaneous
|
|
274
|
5063 @unnumberedsubsec Q5.0.16: I find auto-show-mode disconcerting. How do I turn it off?
|
|
82
|
5064
|
|
|
5065 @code{auto-show-mode} controls whether or not a horizontal scrollbar
|
|
|
5066 magically appears when a line is too long to be displayed. This is
|
|
|
5067 enabled by default. To turn it off, put the following in your
|
|
|
5068 @file{.emacs}:
|
|
|
5069
|
|
|
5070 @lisp
|
|
|
5071 (setq auto-show-mode nil)
|
|
|
5072 (setq-default auto-show-mode nil)
|
|
|
5073 @end lisp
|
|
|
5074
|
|
|
5075 @node Q5.0.17, Q5.0.18, Q5.0.16, Miscellaneous
|
|
274
|
5076 @unnumberedsubsec Q5.0.17: How can I get two instances of info?
|
|
82
|
5077
|
|
227
|
5078 You can't. The @code{info} package does not provide for multiple info buffers.
|
|
82
|
5079
|
|
|
5080 @node Q5.0.18, Q5.0.19, Q5.0.17, Miscellaneous
|
|
365
|
5081 @unnumberedsubsec Q5.0.18: [This question intentionally left blank]
|
|
82
|
5082
|
|
274
|
5083 @node Q5.0.19, Q5.0.20, Q5.0.18, Miscellaneous
|
|
|
5084 @unnumberedsubsec Q5.0.19: Is there something better than LaTeX mode?
|
|
|
5085
|
|
|
5086 @email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes:
|
|
82
|
5087
|
|
|
5088 @quotation
|
|
|
5089 The standard TeX modes leave much to be desired, and are somewhat
|
|
335
|
5090 leniently maintained. Serious TeX users use AUC TeX (@pxref{Q4.7.1}).
|
|
82
|
5091 @end quotation
|
|
|
5092
|
|
274
|
5093 @node Q5.0.20, Q5.1.1, Q5.0.19, Miscellaneous
|
|
|
5094 @unnumberedsubsec Q5.0.20: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
|
|
|
5095
|
|
|
5096 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes:
|
|
|
5097 @quotation
|
|
|
5098 Here is one of the solutions, we have this in a script called
|
|
|
5099 @file{etc/editclient.sh}.
|
|
|
5100 @example
|
|
|
5101 #!/bin/sh
|
|
|
5102 if gnuclient -batch -eval t >/dev/null 2>&1
|
|
|
5103 then
|
|
|
5104 exec gnuclient $@{1+"$@@"@}
|
|
|
5105 else
|
|
|
5106 xemacs -unmapped -f gnuserv-start &
|
|
|
5107 until gnuclient -batch -eval t >/dev/null 2>&1
|
|
|
5108 do
|
|
|
5109 sleep 1
|
|
|
5110 done
|
|
|
5111 exec gnuclient $@{1+"$@@"@}
|
|
|
5112 fi
|
|
|
5113 @end example
|
|
|
5114
|
|
|
5115 Note that there is a known problem when running XEmacs and 'gnuclient
|
|
|
5116 -nw' on the same TTY.
|
|
|
5117 @end quotation
|
|
|
5118
|
|
|
5119 @node Q5.1.1, Q5.1.2, Q5.0.20, Miscellaneous
|
|
282
|
5120 @unnumberedsec 5.1: Emacs Lisp Programming Techniques
|
|
274
|
5121 @unnumberedsubsec Q5.1.1: What is the difference in key sequences between XEmacs and GNU Emacs?
|
|
|
5122
|
|
|
5123 @email{clerik@@naggum.no, Erik Naggum} writes;
|
|
82
|
5124
|
|
|
5125 @quotation
|
|
|
5126 Emacs has a legacy of keyboards that produced characters with modifier
|
|
|
5127 bits, and therefore map a variety of input systems into this scheme even
|
|
|
5128 today. XEmacs is instead optimized for X events. This causes an
|
|
|
5129 incompatibility in the way key sequences are specified, but both Emacs
|
|
|
5130 and XEmacs will accept a key sequence as a vector of lists of modifiers
|
|
163
|
5131 that ends with a key, e.g., to bind @kbd{M-C-a}, you would say
|
|
|
5132 @code{[(meta control a)]} in both Emacsen. XEmacs has an abbreviated
|
|
|
5133 form for a single key, just (meta control a). Emacs has an abbreviated
|
|
|
5134 form for the Control and the Meta modifiers to string-characters (the
|
|
|
5135 ASCII characters), as in @samp{\M-\C-a}. XEmacs users need to be aware
|
|
|
5136 that the abbreviated form works only for one-character key sequences,
|
|
|
5137 while Emacs users need to be aware that the string-character is rather
|
|
217
|
5138 limited. Specifically, the string-character can accommodate only 256
|
|
163
|
5139 different values, 128 of which have the Meta modifier and 128 of which
|
|
|
5140 have not. In each of these blocks, only 32 characters have the Control
|
|
|
5141 modifier. Whereas @code{[(meta control A)]} differs from @code{[(meta
|
|
|
5142 control a)]} because the case differs, @samp{\M-\C-a} and @samp{\M-\C-A}
|
|
|
5143 do not. Programmers are advised to use the full common form, both
|
|
|
5144 because it is more readable and less error-prone, and because it is
|
|
|
5145 supported by both Emacsen.
|
|
82
|
5146 @end quotation
|
|
|
5147
|
|
163
|
5148 Another (even safer) way to be sure of the key-sequences is to use the
|
|
|
5149 @code{read-kbd-macro} function, which takes a string like @samp{C-c
|
|
|
5150 <up>}, and converts it to the internal key representation of the Emacs
|
|
|
5151 you use. The function is available both on XEmacs and GNU Emacs.
|
|
|
5152
|
|
82
|
5153 @node Q5.1.2, Q5.1.3, Q5.1.1, Miscellaneous
|
|
274
|
5154 @unnumberedsubsec Q5.1.2: Can I generate "fake" keyboard events?
|
|
82
|
5155
|
|
163
|
5156 I wonder if there is an interactive function that can generate
|
|
|
5157 @dfn{fake} keyboard events. This way, I could simply map them inside
|
|
|
5158 XEmacs.
|
|
70
|
5159
|
|
|
5160 This seems to work:
|
|
82
|
5161
|
|
|
5162 @lisp
|
|
70
|
5163 (defun cg--generate-char-event (ch)
|
|
|
5164 "Generate an event, as if ch has been typed"
|
|
|
5165 (dispatch-event (character-to-event ch)))
|
|
|
5166
|
|
|
5167 ;; Backspace and Delete stuff
|
|
163
|
5168 (global-set-key [backspace]
|
|
274
|
5169 (lambda () (interactive) (cg--generate-char-event 127)))
|
|
163
|
5170 (global-set-key [unknown_keysym_0x4]
|
|
274
|
5171 (lambda () (interactive) (cg--generate-char-event 4)))
|
|
82
|
5172 @end lisp
|
|
|
5173
|
|
|
5174 @node Q5.1.3, Q5.1.4, Q5.1.2, Miscellaneous
|
|
274
|
5175 @unnumberedsubsec Q5.1.3: Could you explain @code{read-kbd-macro} in more detail?
|
|
163
|
5176
|
|
|
5177 The @code{read-kbd-macro} function returns the internal Emacs
|
|
|
5178 representation of a human-readable string (which is its argument).
|
|
|
5179 Thus:
|
|
82
|
5180
|
|
|
5181 @lisp
|
|
163
|
5182 (read-kbd-macro "C-c C-a")
|
|
274
|
5183 @result{} [(control ?c) (control ?a)]
|
|
163
|
5184
|
|
|
5185 (read-kbd-macro "C-c C-. <up>")
|
|
274
|
5186 @result{} [(control ?c) (control ?.) up]
|
|
82
|
5187 @end lisp
|
|
|
5188
|
|
163
|
5189 In GNU Emacs the same forms will be evaluated to what GNU Emacs
|
|
|
5190 understands internally---the sequences @code{"\C-x\C-c"} and @code{[3
|
|
|
5191 67108910 up]}, respectively.
|
|
|
5192
|
|
|
5193 The exact @dfn{human-readable} syntax is defined in the docstring of
|
|
|
5194 @code{edmacro-mode}. I'll repeat it here, for completeness.
|
|
|
5195
|
|
|
5196 @quotation
|
|
|
5197 Format of keyboard macros during editing:
|
|
|
5198
|
|
|
5199 Text is divided into @dfn{words} separated by whitespace. Except for
|
|
|
5200 the words described below, the characters of each word go directly as
|
|
|
5201 characters of the macro. The whitespace that separates words is
|
|
|
5202 ignored. Whitespace in the macro must be written explicitly, as in
|
|
282
|
5203 @kbd{foo @key{SPC} bar @key{RET}}.
|
|
163
|
5204
|
|
|
5205 @itemize @bullet
|
|
|
5206 @item
|
|
|
5207 The special words @kbd{RET}, @kbd{SPC}, @kbd{TAB}, @kbd{DEL}, @kbd{LFD},
|
|
|
5208 @kbd{ESC}, and @kbd{NUL} represent special control characters. The
|
|
|
5209 words must be written in uppercase.
|
|
|
5210
|
|
|
5211 @item
|
|
|
5212 A word in angle brackets, e.g., @code{<return>}, @code{<down>}, or
|
|
|
5213 @code{<f1>}, represents a function key. (Note that in the standard
|
|
|
5214 configuration, the function key @code{<return>} and the control key
|
|
282
|
5215 @key{RET} are synonymous.) You can use angle brackets on the words
|
|
|
5216 @key{RET}, @key{SPC}, etc., but they are not required there.
|
|
163
|
5217
|
|
|
5218 @item
|
|
|
5219 Keys can be written by their @sc{ascii} code, using a backslash followed
|
|
|
5220 by up to six octal digits. This is the only way to represent keys with
|
|
|
5221 codes above \377.
|
|
|
5222
|
|
|
5223 @item
|
|
|
5224 One or more prefixes @kbd{M-} (meta), @kbd{C-} (control), @kbd{S-}
|
|
|
5225 (shift), @kbd{A-} (alt), @kbd{H-} (hyper), and @kbd{s-} (super) may
|
|
|
5226 precede a character or key notation. For function keys, the prefixes
|
|
|
5227 may go inside or outside of the brackets: @code{C-<down>} @equiv{}
|
|
|
5228 @code{<C-down>}. The prefixes may be written in any order: @kbd{M-C-x}
|
|
|
5229 @equiv{} @kbd{C-M-x}.
|
|
|
5230
|
|
|
5231 Prefixes are not allowed on multi-key words, e.g., @kbd{C-abc}, except
|
|
|
5232 that the Meta prefix is allowed on a sequence of digits and optional
|
|
|
5233 minus sign: @kbd{M--123} @equiv{} @kbd{M-- M-1 M-2 M-3}.
|
|
|
5234
|
|
|
5235 @item
|
|
|
5236 The @code{^} notation for control characters also works: @kbd{^M}
|
|
|
5237 @equiv{} @kbd{C-m}.
|
|
|
5238
|
|
|
5239 @item
|
|
|
5240 Double angle brackets enclose command names: @code{<<next-line>>} is
|
|
282
|
5241 shorthand for @kbd{M-x next-line @key{RET}}.
|
|
163
|
5242
|
|
|
5243 @item
|
|
|
5244 Finally, @code{REM} or @code{;;} causes the rest of the line to be
|
|
|
5245 ignored as a comment.
|
|
|
5246 @end itemize
|
|
|
5247
|
|
|
5248 Any word may be prefixed by a multiplier in the form of a decimal number
|
|
|
5249 and @code{*}: @code{3*<right>} @equiv{} @code{<right> <right> <right>},
|
|
282
|
5250 and @code{10*foo} @equiv{}
|
|
274
|
5251 @iftex
|
|
|
5252 @*
|
|
282
|
5253 @end iftex
|
|
274
|
5254 @code{foofoofoofoofoofoofoofoofoofoo}.
|
|
163
|
5255
|
|
|
5256 Multiple text keys can normally be strung together to form a word, but
|
|
|
5257 you may need to add whitespace if the word would look like one of the
|
|
|
5258 above notations: @code{; ; ;} is a keyboard macro with three semicolons,
|
|
|
5259 but @code{;;;} is a comment. Likewise, @code{\ 1 2 3} is four keys but
|
|
|
5260 @code{\123} is a single key written in octal, and @code{< right >} is
|
|
|
5261 seven keys but @code{<right>} is a single function key. When in doubt,
|
|
|
5262 use whitespace.
|
|
|
5263 @end quotation
|
|
|
5264
|
|
|
5265 @node Q5.1.4, Q5.1.5, Q5.1.3, Miscellaneous
|
|
274
|
5266 @unnumberedsubsec Q5.1.4: What is the performance hit of @code{let}?
|
|
163
|
5267
|
|
217
|
5268 In most cases, not noticeable. Besides, there's no avoiding
|
|
163
|
5269 @code{let}---you have to bind your local variables, after all. Some
|
|
|
5270 pose a question whether to nest @code{let}s, or use one @code{let} per
|
|
|
5271 function. I think because of clarity and maintenance (and possible
|
|
|
5272 future implementation), @code{let}-s should be used (nested) in a way to
|
|
|
5273 provide the clearest code.
|
|
|
5274
|
|
|
5275 @node Q5.1.5, Q5.1.6, Q5.1.4, Miscellaneous
|
|
274
|
5276 @unnumberedsubsec Q5.1.5: What is the recommended use of @code{setq}?
|
|
163
|
5277
|
|
|
5278 @itemize @bullet
|
|
|
5279 @item Global variables
|
|
|
5280
|
|
|
5281 You will typically @code{defvar} your global variable to a default
|
|
|
5282 value, and use @code{setq} to set it later.
|
|
|
5283
|
|
|
5284 It is never a good practice to @code{setq} user variables (like
|
|
|
5285 @code{case-fold-search}, etc.), as it ignores the user's choice
|
|
|
5286 unconditionally. Note that @code{defvar} doesn't change the value of a
|
|
|
5287 variable if it was bound previously. If you wish to change a
|
|
|
5288 user-variable temporarily, use @code{let}:
|
|
82
|
5289
|
|
|
5290 @lisp
|
|
163
|
5291 (let ((case-fold-search nil))
|
|
365
|
5292 ... ; code with searches that must be case-sensitive
|
|
163
|
5293 ...)
|
|
82
|
5294 @end lisp
|
|
|
5295
|
|
163
|
5296 You will notice the user-variables by their docstrings beginning with an
|
|
|
5297 asterisk (a convention).
|
|
|
5298
|
|
|
5299 @item Local variables
|
|
|
5300
|
|
|
5301 Bind them with @code{let}, which will unbind them (or restore their
|
|
|
5302 previous value, if they were bound) after exiting from the @code{let}
|
|
|
5303 form. Change the value of local variables with @code{setq} or whatever
|
|
|
5304 you like (e.g. @code{incf}, @code{setf} and such). The @code{let} form
|
|
|
5305 can even return one of its local variables.
|
|
|
5306
|
|
|
5307 Typical usage:
|
|
82
|
5308
|
|
|
5309 @lisp
|
|
163
|
5310 ;; iterate through the elements of the list returned by
|
|
|
5311 ;; `hairy-function-that-returns-list'
|
|
|
5312 (let ((l (hairy-function-that-returns-list)))
|
|
|
5313 (while l
|
|
|
5314 ... do something with (car l) ...
|
|
|
5315 (setq l (cdr l))))
|
|
|
5316 @end lisp
|
|
|
5317
|
|
|
5318 Another typical usage includes building a value simply to work with it.
|
|
|
5319
|
|
|
5320 @lisp
|
|
|
5321 ;; Build the mode keymap out of the key-translation-alist
|
|
|
5322 (let ((inbox (file-truename (expand-file-name box)))
|
|
|
5323 (i 0))
|
|
|
5324 ... code dealing with inbox ...
|
|
|
5325 inbox)
|
|
|
5326 @end lisp
|
|
|
5327
|
|
|
5328 This piece of code uses the local variable @code{inbox}, which becomes
|
|
|
5329 unbound (or regains old value) after exiting the form. The form also
|
|
|
5330 returns the value of @code{inbox}, which can be reused, for instance:
|
|
|
5331
|
|
|
5332 @lisp
|
|
|
5333 (setq foo-processed-inbox
|
|
|
5334 (let .....))
|
|
82
|
5335 @end lisp
|
|
163
|
5336 @end itemize
|
|
|
5337
|
|
|
5338 @node Q5.1.6, Q5.1.7, Q5.1.5, Miscellaneous
|
|
274
|
5339 @unnumberedsubsec Q5.1.6: What is the typical misuse of @code{setq} ?
|
|
163
|
5340
|
|
|
5341 A typical misuse is probably @code{setq}ing a variable that was meant to
|
|
|
5342 be local. Such a variable will remain bound forever, never to be
|
|
|
5343 garbage-collected. For example, the code doing:
|
|
|
5344
|
|
|
5345 @lisp
|
|
|
5346 (defun my-function (whatever)
|
|
|
5347 (setq a nil)
|
|
|
5348 ... build a large list ...
|
|
|
5349 ... and exit ...)
|
|
|
5350 @end lisp
|
|
|
5351
|
|
|
5352 does a bad thing, as @code{a} will keep consuming memory, never to be
|
|
|
5353 unbound. The correct thing is to do it like this:
|
|
|
5354
|
|
|
5355 @lisp
|
|
|
5356 (defun my-function (whatever)
|
|
365
|
5357 (let (a) ; default initialization is to nil
|
|
163
|
5358 ... build a large list ...
|
|
|
5359 ... and exit, unbinding `a' in the process ...)
|
|
|
5360 @end lisp
|
|
|
5361
|
|
|
5362 Not only is this prettier syntactically, but it makes it possible for
|
|
|
5363 Emacs to garbage-collect the objects which @code{a} used to reference.
|
|
|
5364
|
|
|
5365 Note that even global variables should not be @code{setq}ed without
|
|
|
5366 @code{defvar}ing them first, because the byte-compiler issues warnings.
|
|
|
5367 The reason for the warning is the following:
|
|
|
5368
|
|
|
5369 @lisp
|
|
365
|
5370 (defun flurgoze nil) ; ok, global internal variable
|
|
163
|
5371 ...
|
|
|
5372
|
|
365
|
5373 (setq flurghoze t) ; ops! a typo, but semantically correct.
|
|
|
5374 ; however, the byte-compiler warns.
|
|
163
|
5375
|
|
|
5376 While compiling toplevel forms:
|
|
274
|
5377 ** assignment to free variable flurghoze
|
|
163
|
5378 @end lisp
|
|
|
5379
|
|
|
5380 @node Q5.1.7, Q5.1.8, Q5.1.6, Miscellaneous
|
|
367
|
5381 @unnumberedsubsec Q5.1.7: I like the @code{do} form of cl, does it slow things down?
|
|
163
|
5382
|
|
|
5383 It shouldn't. Here is what Dave Gillespie has to say about cl.el
|
|
|
5384 performance:
|
|
82
|
5385
|
|
|
5386 @quotation
|
|
163
|
5387 Many of the advanced features of this package, such as @code{defun*},
|
|
|
5388 @code{loop}, and @code{setf}, are implemented as Lisp macros. In
|
|
|
5389 byte-compiled code, these complex notations will be expanded into
|
|
|
5390 equivalent Lisp code which is simple and efficient. For example, the
|
|
|
5391 forms
|
|
82
|
5392
|
|
|
5393 @lisp
|
|
163
|
5394 (incf i n)
|
|
|
5395 (push x (car p))
|
|
82
|
5396 @end lisp
|
|
|
5397
|
|
163
|
5398 are expanded at compile-time to the Lisp forms
|
|
82
|
5399
|
|
|
5400 @lisp
|
|
163
|
5401 (setq i (+ i n))
|
|
|
5402 (setcar p (cons x (car p)))
|
|
82
|
5403 @end lisp
|
|
|
5404
|
|
163
|
5405 which are the most efficient ways of doing these respective operations
|
|
|
5406 in Lisp. Thus, there is no performance penalty for using the more
|
|
|
5407 readable @code{incf} and @code{push} forms in your compiled code.
|
|
|
5408
|
|
|
5409 @emph{Interpreted} code, on the other hand, must expand these macros
|
|
|
5410 every time they are executed. For this reason it is strongly
|
|
|
5411 recommended that code making heavy use of macros be compiled. (The
|
|
|
5412 features labelled @dfn{Special Form} instead of @dfn{Function} in this
|
|
|
5413 manual are macros.) A loop using @code{incf} a hundred times will
|
|
|
5414 execute considerably faster if compiled, and will also garbage-collect
|
|
|
5415 less because the macro expansion will not have to be generated, used,
|
|
|
5416 and thrown away a hundred times.
|
|
|
5417
|
|
|
5418 You can find out how a macro expands by using the @code{cl-prettyexpand}
|
|
|
5419 function.
|
|
82
|
5420 @end quotation
|
|
|
5421
|
|
163
|
5422 @node Q5.1.8, Q5.1.9, Q5.1.7, Miscellaneous
|
|
274
|
5423 @unnumberedsubsec Q5.1.8: I like recursion, does it slow things down?
|
|
163
|
5424
|
|
|
5425 Yes. Emacs byte-compiler cannot do much to optimize recursion. But
|
|
|
5426 think well whether this is a real concern in Emacs. Much of the Emacs
|
|
|
5427 slowness comes from internal mechanisms such as redisplay, or from the
|
|
|
5428 fact that it is an interpreter.
|
|
|
5429
|
|
|
5430 Please try not to make your code much uglier to gain a very small speed
|
|
|
5431 gain. It's not usually worth it.
|
|
|
5432
|
|
213
|
5433 @node Q5.1.9, Q5.1.10, Q5.1.8, Miscellaneous
|
|
274
|
5434 @unnumberedsubsec Q5.1.9: How do I put a glyph as annotation in a buffer?
|
|
163
|
5435
|
|
|
5436 Here is a solution that will insert the glyph annotation at the
|
|
|
5437 beginning of buffer:
|
|
|
5438
|
|
|
5439 @lisp
|
|
|
5440 (make-annotation (make-glyph '([FORMAT :file FILE]
|
|
|
5441 [string :data "fallback-text"]))
|
|
|
5442 (point-min)
|
|
|
5443 'text
|
|
|
5444 (current-buffer))
|
|
|
5445 @end lisp
|
|
|
5446
|
|
282
|
5447 Replace @samp{FORMAT} with an unquoted symbol representing the format of
|
|
163
|
5448 the image (e.g. @code{xpm}, @code{xbm}, @code{gif}, @code{jpeg}, etc.)
|
|
|
5449 Instead of @samp{FILE}, use the image file name
|
|
282
|
5450 (e.g.
|
|
274
|
5451 @iftex
|
|
|
5452 @*
|
|
282
|
5453 @end iftex
|
|
274
|
5454 @file{/usr/local/lib/xemacs-20.2/etc/recycle.xpm}).
|
|
163
|
5455
|
|
|
5456 You can turn this to a function (that optionally prompts you for a file
|
|
|
5457 name), and inserts the glyph at @code{(point)} instead of
|
|
|
5458 @code{(point-min)}.
|
|
|
5459
|
|
282
|
5460 @node Q5.1.10, Q5.1.11, Q5.1.9, Miscellaneous
|
|
274
|
5461 @unnumberedsubsec Q5.1.10: @code{map-extents} won't traverse all of my extents!
|
|
213
|
5462
|
|
|
5463 I tried to use @code{map-extents} to do an operation on all the extents
|
|
282
|
5464 in a region. However, it seems to quit after processing a random number
|
|
213
|
5465 of extents. Is it buggy?
|
|
|
5466
|
|
282
|
5467 No. The documentation of @code{map-extents} states that it will iterate
|
|
213
|
5468 across the extents as long as @var{function} returns @code{nil}.
|
|
|
5469 Unexperienced programmers often forget to return @code{nil} explicitly,
|
|
|
5470 which results in buggy code. For instance, the following code is
|
|
|
5471 supposed to delete all the extents in a buffer, and issue as many
|
|
|
5472 @samp{fubar!} messages.
|
|
|
5473
|
|
|
5474 @lisp
|
|
|
5475 (map-extents (lambda (ext ignore)
|
|
|
5476 (delete-extent ext)
|
|
|
5477 (message "fubar!")))
|
|
|
5478 @end lisp
|
|
|
5479
|
|
|
5480 Instead, it will delete only the first extent, and stop right there --
|
|
|
5481 because @code{message} will return a non-nil value. The correct code
|
|
|
5482 is:
|
|
|
5483
|
|
|
5484 @lisp
|
|
|
5485 (map-extents (lambda (ext ignore)
|
|
|
5486 (delete-extent ext)
|
|
|
5487 (message "fubar!")
|
|
|
5488 nil))
|
|
|
5489 @end lisp
|
|
|
5490
|
|
282
|
5491 @node Q5.1.11, Q5.2.1, Q5.1.10, Miscellaneous
|
|
|
5492 @unnumberedsubsec Q5.1.11: My elisp program is horribly slow. Is there
|
|
|
5493 an easy way to find out where it spends time?
|
|
|
5494 @c New
|
|
|
5495
|
|
359
|
5496 z@email{hniksic@@xemacs.org, Hrvoje Niksic} writes:
|
|
282
|
5497 @quotation
|
|
|
5498 Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence}, press a key
|
|
|
5499 (say @key{RET} in the Gnus Group buffer), and get the results using
|
|
|
5500 @kbd{M-x profile-results}. It should give you an idea of where the time
|
|
|
5501 is being spent.
|
|
|
5502 @end quotation
|
|
|
5503
|
|
|
5504 @node Q5.2.1, Q5.2.2, Q5.1.11, Miscellaneous
|
|
274
|
5505 @unnumberedsubsec Q5.2.1: How do I turn off the sound?
|
|
82
|
5506
|
|
|
5507 Add the following line to your @file{.emacs}:
|
|
|
5508
|
|
|
5509 @lisp
|
|
|
5510 (setq bell-volume 0)
|
|
|
5511 (setq sound-alist nil)
|
|
|
5512 @end lisp
|
|
|
5513
|
|
365
|
5514 That will make your XEmacs totally silent---even the default ding sound
|
|
163
|
5515 (TTY beep on TTY-s) will be gone.
|
|
|
5516
|
|
227
|
5517 Starting with XEmacs-20.2 you can also change these with Customize.
|
|
|
5518 Select from the @code{Options} menu
|
|
|
5519 @code{Customize->Emacs->Environment->Sound->Sound...} or type
|
|
282
|
5520 @kbd{M-x customize @key{RET} sound @key{RET}}.
|
|
227
|
5521
|
|
|
5522
|
|
82
|
5523 @node Q5.2.2, Q5.2.3, Q5.2.1, Miscellaneous
|
|
274
|
5524 @unnumberedsubsec Q5.2.2: How do I get funky sounds instead of a boring beep?
|
|
82
|
5525
|
|
|
5526 Make sure your XEmacs was compiled with sound support, and then put this
|
|
|
5527 in your @file{.emacs}:
|
|
|
5528
|
|
|
5529 @lisp
|
|
|
5530 (load-default-sounds)
|
|
|
5531 @end lisp
|
|
|
5532
|
|
126
|
5533 The sound support in XEmacs 19.14 was greatly improved over previous
|
|
82
|
5534 versions.
|
|
|
5535
|
|
|
5536 @node Q5.2.3, Q5.2.4, Q5.2.2, Miscellaneous
|
|
274
|
5537 @unnumberedsubsec Q5.2.3: What's NAS, how do I get it?
|
|
82
|
5538
|
|
335
|
5539 @xref{Q2.0.3}, for an explanation of the @dfn{Network Audio System}.
|
|
82
|
5540
|
|
|
5541 @node Q5.2.4, Q5.3.1, Q5.2.3, Miscellaneous
|
|
274
|
5542 @unnumberedsubsec Q5.2.4: Sunsite sounds don't play.
|
|
82
|
5543
|
|
|
5544 I'm having some trouble with sounds I've downloaded from sunsite. They
|
|
|
5545 play when I run them through @code{showaudio} or cat them directly to
|
|
|
5546 @file{/dev/audio}, but XEmacs refuses to play them.
|
|
|
5547
|
|
274
|
5548 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
|
|
82
|
5549
|
|
|
5550 @quotation
|
|
|
5551 [Many of] These files have an (erroneous) 24byte header that tells about
|
|
|
5552 the format that they have been recorded in. If you cat them to
|
|
|
5553 @file{/dev/audio}, the header will be ignored and the default behavior
|
|
|
5554 for /dev/audio will be used. This happens to be 8kHz uLaw. It is
|
|
|
5555 probably possible to fix the header by piping through @code{sox} and
|
|
|
5556 passing explicit parameters for specifying the sampling format; you then
|
|
|
5557 need to perform a 'null' conversion from SunAudio to SunAudio.
|
|
|
5558 @end quotation
|
|
|
5559
|
|
|
5560 @node Q5.3.1, Q5.3.2, Q5.2.4, Miscellaneous
|
|
282
|
5561 @unnumberedsec 5.3: Miscellaneous
|
|
274
|
5562 @unnumberedsubsec Q5.3.1: How do you make XEmacs indent CL if-clauses correctly?
|
|
82
|
5563
|
|
|
5564 I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the
|
|
|
5565 same amount instead of indenting the 3rd clause differently from the
|
|
|
5566 first two.
|
|
70
|
5567
|
|
|
5568 One way is to add, to @file{.emacs}:
|
|
|
5569
|
|
82
|
5570 @lisp
|
|
70
|
5571 (put 'if 'lisp-indent-function nil)
|
|
82
|
5572 @end lisp
|
|
70
|
5573
|
|
227
|
5574 However, note that the package @code{cl-indent} that comes with
|
|
82
|
5575 XEmacs sets up this kind of indentation by default. @code{cl-indent}
|
|
|
5576 also knows about many other CL-specific forms. To use @code{cl-indent},
|
|
|
5577 one can do this:
|
|
|
5578
|
|
|
5579 @lisp
|
|
70
|
5580 (load "cl-indent")
|
|
|
5581 (setq lisp-indent-function (function common-lisp-indent-function))
|
|
82
|
5582 @end lisp
|
|
|
5583
|
|
|
5584 One can also customize @file{cl-indent.el} so it mimics the default
|
|
|
5585 @code{if} indentation @code{then} indented more than the @code{else}.
|
|
|
5586 Here's how:
|
|
|
5587
|
|
|
5588 @lisp
|
|
70
|
5589 (put 'if 'common-lisp-indent-function '(nil nil &body))
|
|
82
|
5590 @end lisp
|
|
70
|
5591
|
|
|
5592 Also, a new version (1.2) of @file{cl-indent.el} was posted to
|
|
82
|
5593 comp.emacs.xemacs on 12/9/94. This version includes more documentation
|
|
|
5594 than previous versions. This may prove useful if you need to customize
|
|
|
5595 any indent-functions.
|
|
|
5596
|
|
|
5597 @node Q5.3.2, Q5.3.3, Q5.3.1, Miscellaneous
|
|
274
|
5598 @unnumberedsubsec Q5.3.2: Fontifying hang when editing a postscript file.
|
|
82
|
5599
|
|
|
5600 When I try to edit a postscript file it gets stuck saying:
|
|
|
5601 @samp{fontifying 'filename' (regexps....)} and it just sits there. If I
|
|
|
5602 press @kbd{C-c} in the window where XEmacs was started, it suddenly
|
|
|
5603 becomes alive again.
|
|
70
|
5604
|
|
|
5605 This was caused by a bug in the Postscript font-lock regular
|
|
82
|
5606 expressions. It was fixed in 19.13. For earlier versions of XEmacs,
|
|
|
5607 have a look at your @file{.emacs} file. You will probably have a line
|
|
|
5608 like:
|
|
|
5609
|
|
|
5610 @lisp
|
|
365
|
5611 (add-hook 'postscript-mode-hook 'turn-on-font-lock)
|
|
82
|
5612 @end lisp
|
|
|
5613
|
|
|
5614 Take it out, restart XEmacs, and it won't try to fontify your postscript
|
|
|
5615 files anymore.
|
|
|
5616
|
|
|
5617 @node Q5.3.3, Q5.3.4, Q5.3.2, Miscellaneous
|
|
274
|
5618 @unnumberedsubsec Q5.3.3: How can I print WYSIWYG a font-locked buffer?
|
|
82
|
5619
|
|
|
5620 Font-lock looks nice. How can I print (WYSIWYG) the highlighted
|
|
|
5621 document?
|
|
|
5622
|
|
227
|
5623 The package @code{ps-print}, which is now included with XEmacs, provides
|
|
|
5624 the ability to do this. The source code contains complete instructions
|
|
282
|
5625 on its use, in @file{<xemacs_src_root>/lisp/packages/ps-print.el}.
|
|
82
|
5626
|
|
|
5627 @node Q5.3.4, Q5.3.5, Q5.3.3, Miscellaneous
|
|
274
|
5628 @unnumberedsubsec Q5.3.4: Getting @kbd{M-x lpr} to work with postscript printer.
|
|
82
|
5629
|
|
|
5630 My printer is a Postscript printer and @code{lpr} only works for
|
|
|
5631 Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x
|
|
|
5632 lpr-buffer} to work?
|
|
|
5633
|
|
|
5634 Put something like this in your @file{.emacs}:
|
|
|
5635
|
|
|
5636 @lisp
|
|
|
5637 (setq lpr-command "a2ps")
|
|
|
5638 (setq lpr-switches '("-p" "-1"))
|
|
|
5639 @end lisp
|
|
|
5640
|
|
|
5641 If you don't use a2ps to convert ASCII to postscript (why not, it's
|
|
|
5642 free?), replace with the command you do use. Note also that some
|
|
|
5643 versions of a2ps require a @samp{-Pprinter} to ensure spooling.
|
|
|
5644
|
|
|
5645 @node Q5.3.5, Q5.3.6, Q5.3.4, Miscellaneous
|
|
274
|
5646 @unnumberedsubsec Q5.3.5: How do I specify the paths that XEmacs uses for finding files?
|
|
0
|
5647
|
|
|
5648 You can specify what paths to use by using a number of different flags
|
|
|
5649 when running configure. See the section MAKE VARIABLES in the top-level
|
|
|
5650 file INSTALL in the XEmacs distribution for a listing of those flags.
|
|
|
5651
|
|
82
|
5652 Most of the time, however, the simplest fix is: @strong{do not} specify
|
|
|
5653 paths as you might for GNU Emacs. XEmacs can generally determine the
|
|
0
|
5654 necessary paths dynamically at run time. The only path that generally
|
|
|
5655 needs to be specified is the root directory to install into. That can
|
|
|
5656 be specified by passing the @code{--prefix} flag to configure. For a
|
|
82
|
5657 description of the XEmacs install tree, please consult the @file{NEWS}
|
|
|
5658 file.
|
|
|
5659
|
|
|
5660 @node Q5.3.6, Q5.3.7, Q5.3.5, Miscellaneous
|
|
274
|
5661 @unnumberedsubsec Q5.3.6: [This question intentionally left blank]
|
|
82
|
5662
|
|
|
5663 Obsolete question, left blank to avoid renumbering.
|
|
|
5664
|
|
|
5665 @node Q5.3.7, Q5.3.8, Q5.3.6, Miscellaneous
|
|
274
|
5666 @unnumberedsubsec Q5.3.7: Can I have the end of the buffer delimited in some way?
|
|
82
|
5667
|
|
163
|
5668 Say, with: @samp{[END]}?
|
|
|
5669
|
|
|
5670 Try this:
|
|
|
5671
|
|
|
5672 @lisp
|
|
|
5673 (let ((ext (make-extent (point-min) (point-max))))
|
|
|
5674 (set-extent-property ext 'start-closed t)
|
|
|
5675 (set-extent-property ext 'end-closed t)
|
|
282
|
5676 (set-extent-property ext 'detachable nil)
|
|
163
|
5677 (set-extent-end-glyph ext (make-glyph [string :data "[END]"])))
|
|
|
5678 @end lisp
|
|
|
5679
|
|
|
5680 Since this is XEmacs, you can specify an icon to be shown on
|
|
|
5681 window-system devices. To do so, change the @code{make-glyph} call to
|
|
|
5682 something like this:
|
|
|
5683
|
|
|
5684 @lisp
|
|
|
5685 (make-glyph '([xpm :file "~/something.xpm"]
|
|
|
5686 [string :data "[END]"]))
|
|
|
5687 @end lisp
|
|
|
5688
|
|
|
5689 You can inline the @sc{xpm} definition yourself by specifying
|
|
|
5690 @code{:data} instead of @code{:file}. Here is such a full-featured
|
|
|
5691 version that works on both X and TTY devices:
|
|
82
|
5692
|
|
|
5693 @lisp
|
|
163
|
5694 (let ((ext (make-extent (point-min) (point-max))))
|
|
|
5695 (set-extent-property ext 'start-closed t)
|
|
|
5696 (set-extent-property ext 'end-closed t)
|
|
282
|
5697 (set-extent-property ext 'detachable nil)
|
|
163
|
5698 (set-extent-end-glyph ext (make-glyph '([xpm :data "\
|
|
|
5699 /* XPM */
|
|
|
5700 static char* eye = @{
|
|
|
5701 \"20 11 7 2\",
|
|
|
5702 \"__ c None\"
|
|
|
5703 \"_` c #7f7f7f\",
|
|
|
5704 \"_a c #fefefe\",
|
|
|
5705 \"_b c #7f0000\",
|
|
|
5706 \"_c c #fefe00\",
|
|
|
5707 \"_d c #fe0000\",
|
|
|
5708 \"_e c #bfbfbf\",
|
|
282
|
5709 \"___________`_`_`___b_b_b_b_________`____\",
|
|
|
5710 \"_________`_`_`___b_c_c_c_b_b____________\",
|
|
|
5711 \"_____`_`_`_e___b_b_c_c_c___b___b_______`\",
|
|
|
5712 \"___`_`_e_a___b_b_d___b___b___b___b______\",
|
|
|
5713 \"_`_`_e_a_e___b_b_d_b___b___b___b___b____\",
|
|
|
5714 \"_`_`_a_e_a___b_b_d___b___b___b___b___b__\",
|
|
|
5715 \"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\",
|
|
|
5716 \"___`_`_e_a___b_b_b_d_c___b___b___d_b____\",
|
|
|
5717 \"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\",
|
|
|
5718 \"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\",
|
|
|
5719 \"___`_____`_`_`_`___b_b_b_b_b_b__________\",
|
|
163
|
5720 @} ;"]
|
|
|
5721 [string :data "[END]"]))))
|
|
82
|
5722 @end lisp
|
|
|
5723
|
|
163
|
5724 Note that you might want to make this a function, and put it to a hook.
|
|
217
|
5725 We leave that as an exercise for the reader.
|
|
82
|
5726
|
|
|
5727 @node Q5.3.8, Q5.3.9, Q5.3.7, Miscellaneous
|
|
274
|
5728 @unnumberedsubsec Q5.3.8: How do I insert today's date into a buffer?
|
|
82
|
5729
|
|
|
5730 Like this:
|
|
|
5731
|
|
|
5732 @lisp
|
|
|
5733 (insert (current-time-string))
|
|
|
5734 @end lisp
|
|
|
5735
|
|
|
5736 @node Q5.3.9, Q5.3.10, Q5.3.8, Miscellaneous
|
|
274
|
5737 @unnumberedsubsec Q5.3.9: Are only certain syntactic character classes available for abbrevs?
|
|
|
5738
|
|
|
5739 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
|
|
82
|
5740
|
|
|
5741 @quotation
|
|
|
5742 Yes, abbrevs only expands word-syntax strings. While XEmacs does not
|
|
|
5743 prevent you from defining (e.g. with @kbd{C-x a g} or @kbd{C-x a l})
|
|
|
5744 abbrevs that contain special characters, it will refuse to expand
|
|
|
5745 them. So you need to ensure, that the abbreviation contains letters and
|
|
|
5746 digits only. This means that @samp{xd}, @samp{d5}, and @samp{5d} are
|
|
|
5747 valid abbrevs, but @samp{&d}, and @samp{x d} are not.
|
|
|
5748
|
|
|
5749 If this sounds confusing to you, (re-)read the online documentation for
|
|
282
|
5750 abbrevs (@kbd{C-h i m XEmacs @key{RET} m Abbrevs @key{RET}}), and then come back and
|
|
82
|
5751 read this question/answer again.
|
|
|
5752 @end quotation
|
|
|
5753
|
|
227
|
5754 Starting with XEmacs 20.3 this restriction has been lifted.
|
|
163
|
5755
|
|
82
|
5756 @node Q5.3.10, Q5.3.11, Q5.3.9, Miscellaneous
|
|
274
|
5757 @unnumberedsubsec Q5.3.10: How can I get those oh-so-neat X-Face lines?
|
|
82
|
5758
|
|
|
5759 Firstly there is an ftp site which describes X-faces and has the
|
|
|
5760 associated tools mentioned below, at
|
|
274
|
5761 @uref{ftp://ftp.cs.indiana.edu:/pub/faces/}.
|
|
82
|
5762
|
|
|
5763 Then the steps are
|
|
|
5764
|
|
|
5765 @enumerate
|
|
|
5766 @item
|
|
|
5767 Create 48x48x1 bitmap with your favorite tool
|
|
|
5768
|
|
|
5769 @item
|
|
|
5770 Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc.,
|
|
|
5771 and then compile the face.
|
|
|
5772
|
|
|
5773 @item
|
|
0
|
5774 @example
|
|
82
|
5775 cat file.xbm | xbm2ikon |compface > file.face
|
|
0
|
5776 @end example
|
|
|
5777
|
|
82
|
5778 @item
|
|
|
5779 Then be sure to quote things that are necessary for emacs strings:
|
|
0
|
5780
|
|
|
5781 @example
|
|
274
|
5782 cat ./file.face | sed 's/\\/\\\\/g'
|
|
|
5783 @iftex
|
|
|
5784 \ @*
|
|
282
|
5785 @end iftex
|
|
274
|
5786 | sed 's/\"/\\\"/g' > ./file.face.quoted
|
|
0
|
5787 @end example
|
|
|
5788
|
|
82
|
5789 @item
|
|
|
5790 Then set up emacs to include the file as a mail header - there were a
|
|
|
5791 couple of suggestions here---either something like:
|
|
|
5792
|
|
|
5793 @lisp
|
|
282
|
5794 (setq mail-default-headers
|
|
274
|
5795 "X-Face: @email{Ugly looking text string here}")
|
|
82
|
5796 @end lisp
|
|
|
5797
|
|
|
5798 Or, alternatively, as:
|
|
|
5799
|
|
|
5800 @lisp
|
|
|
5801 (defun mail-insert-x-face ()
|
|
282
|
5802 (save-excursion
|
|
82
|
5803 (goto-char (point-min))
|
|
|
5804 (search-forward mail-header-separator)
|
|
163
|
5805 (beginning-of-line)
|
|
82
|
5806 (insert "X-Face:")
|
|
163
|
5807 (insert-file-contents "~/.face")))
|
|
82
|
5808
|
|
|
5809 (add-hook 'mail-setup-hook 'mail-insert-x-face)
|
|
|
5810 @end lisp
|
|
|
5811 @end enumerate
|
|
|
5812
|
|
|
5813 However, 2 things might be wrong:
|
|
|
5814
|
|
|
5815 Some versions of pbmtoicon produces some header lines that is not
|
|
|
5816 expected by the version of compface that I grabbed. So I found I had to
|
|
|
5817 include a @code{tail +3} in the pipeline like this:
|
|
0
|
5818
|
|
|
5819 @example
|
|
82
|
5820 cat file.xbm | xbm2ikon | tail +3 |compface > file.face
|
|
0
|
5821 @end example
|
|
|
5822
|
|
82
|
5823 Some people have also found that if one uses the @code{(insert-file)}
|
|
|
5824 method, one should NOT quote the face string using the sed script .
|
|
|
5825
|
|
274
|
5826 It might also be helpful to use @email{stig@@hackvan.com, Stig's} script
|
|
82
|
5827 (included in the compface distribution at XEmacs.org) to do the
|
|
359
|
5828 conversion.
|
|
|
5829 @comment For convenience xbm2xface is available for anonymous FTP at
|
|
|
5830 @comment @uref{ftp://ftp.miranova.com/pub/xemacs/xbm2xface.pl}.
|
|
82
|
5831
|
|
|
5832 Contributors for this item:
|
|
|
5833
|
|
282
|
5834 Paul Emsley,
|
|
82
|
5835 Ricardo Marek,
|
|
|
5836 Amir J. Katz,
|
|
|
5837 Glen McCort,
|
|
282
|
5838 Heinz Uphoff,
|
|
82
|
5839 Peter Arius,
|
|
|
5840 Paul Harrison, and
|
|
|
5841 Vegard Vesterheim
|
|
|
5842
|
|
|
5843 @node Q5.3.11, Q5.3.12, Q5.3.10, Miscellaneous
|
|
274
|
5844 @unnumberedsubsec Q5.3.11: How do I add new Info directories?
|
|
82
|
5845
|
|
|
5846 You use something like:
|
|
|
5847
|
|
|
5848 @lisp
|
|
282
|
5849 (setq Info-directory-list (cons
|
|
365
|
5850 (expand-file-name "~/info")
|
|
|
5851 Info-default-directory-list))
|
|
82
|
5852 @end lisp
|
|
|
5853
|
|
274
|
5854 @email{davidm@@prism.kla.com, David Masterson} writes:
|
|
82
|
5855
|
|
|
5856 @quotation
|
|
|
5857 Emacs Info and XEmacs Info do many things differently. If you're trying to
|
|
|
5858 support a number of versions of Emacs, here are some notes to remember:
|
|
|
5859
|
|
|
5860 @enumerate
|
|
|
5861 @item
|
|
|
5862 Emacs Info scans @code{Info-directory-list} from right-to-left while
|
|
|
5863 XEmacs Info reads it from left-to-right, so append to the @emph{correct}
|
|
|
5864 end of the list.
|
|
|
5865
|
|
|
5866 @item
|
|
|
5867 Use @code{Info-default-directory-list} to initialize
|
|
|
5868 @code{Info-directory-list} @emph{if} it is available at startup, but not
|
|
|
5869 all Emacsen define it.
|
|
|
5870
|
|
|
5871 @item
|
|
|
5872 Emacs Info looks for a standard @file{dir} file in each of the
|
|
|
5873 directories scanned from #1 and magically concatenates them together.
|
|
|
5874
|
|
|
5875 @item
|
|
|
5876 XEmacs Info looks for a @file{localdir} file (which consists of just the
|
|
|
5877 menu entries from a @file{dir} file) in each of the directories scanned
|
|
217
|
5878 from #1 (except the first), does a simple concatenation of them, and
|
|
82
|
5879 magically attaches the resulting list to the end of the menu in the
|
|
|
5880 @file{dir} file in the first directory.
|
|
|
5881 @end enumerate
|
|
|
5882
|
|
|
5883 Another alternative is to convert the documentation to HTML with
|
|
|
5884 texi2html and read it from a web browser like Lynx or W3.
|
|
|
5885 @end quotation
|
|
|
5886
|
|
|
5887 @node Q5.3.12, , Q5.3.11, Miscellaneous
|
|
274
|
5888 @unnumberedsubsec Q5.3.12: What do I need to change to make printing work?
|
|
82
|
5889
|
|
|
5890 For regular printing there are two variables that can be customized.
|
|
|
5891
|
|
|
5892 @table @code
|
|
|
5893 @item lpr-command
|
|
|
5894 This should be set to a command that takes standard input and sends
|
|
|
5895 it to a printer. Something like:
|
|
|
5896
|
|
|
5897 @lisp
|
|
|
5898 (setq lpr-command "lp")
|
|
|
5899 @end lisp
|
|
|
5900
|
|
|
5901 @item lpr-switches
|
|
|
5902 This should be set to a list that contains whatever the print command
|
|
|
5903 requires to do its job. Something like:
|
|
|
5904
|
|
|
5905 @lisp
|
|
|
5906 (setq lpr-switches '("-depson"))
|
|
|
5907 @end lisp
|
|
|
5908 @end table
|
|
|
5909
|
|
|
5910 For postscript printing there are three analogous variables to
|
|
|
5911 customize.
|
|
|
5912
|
|
|
5913 @table @code
|
|
|
5914 @item ps-lpr-command
|
|
|
5915 This should be set to a command that takes postscript on standard input
|
|
|
5916 and directs it to a postscript printer.
|
|
|
5917
|
|
|
5918 @item ps-lpr-switches
|
|
|
5919 This should be set to a list of switches required for
|
|
|
5920 @code{ps-lpr-command} to do its job.
|
|
|
5921
|
|
|
5922 @item ps-print-color-p
|
|
|
5923 This boolean variable should be set @code{t} if printing will be done in
|
|
|
5924 color, otherwise it should be set to @code{nil}.
|
|
|
5925 @end table
|
|
|
5926
|
|
|
5927 NOTE: It is an undocumented limitation in XEmacs that postscript
|
|
|
5928 printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a
|
|
|
5929 window system environment. It cannot be used outside of X11.
|
|
|
5930
|
|
359
|
5931 @node MS Windows, Current Events, Miscellaneous, Top
|
|
|
5932 @unnumbered 6 XEmacs on MS Windows
|
|
|
5933
|
|
|
5934 This is part 6 of the XEmacs Frequently Asked Questions list, written by
|
|
|
5935 Hrvoje Niksic and others. This section is devoted to the MS Windows
|
|
|
5936 port of XEmacs.
|
|
|
5937
|
|
|
5938 @menu
|
|
|
5939
|
|
|
5940 General Info
|
|
365
|
5941 * Q6.0.1:: What is the status of the XEmacs port to Windows?
|
|
|
5942 * Q6.0.2:: What flavors of MS Windows are supported?
|
|
359
|
5943 * Q6.0.3:: Where are the XEmacs on MS Windows binaries?
|
|
365
|
5944 * Q6.0.4:: Does XEmacs on MS Windows require an X server to run?
|
|
359
|
5945
|
|
|
5946 Building XEmacs on MS Windows
|
|
365
|
5947 * Q6.1.1:: I decided to run with X. Where do I get an X server?
|
|
|
5948 * Q6.1.2:: What compiler do I need to compile XEmacs?
|
|
|
5949 * Q6.1.3:: How do I compile for the native port?
|
|
|
5950 * Q6.1.4:: How do I compile for the X port?
|
|
|
5951 * Q6.1.5:: How do I compile for Cygnus' Cygwin?
|
|
|
5952 * Q6.1.6:: What do I need for Cygwin?
|
|
359
|
5953
|
|
|
5954 Customization and User Interface
|
|
365
|
5955 * Q6.2.1:: How will the port cope with differences in the Windows user interface?
|
|
|
5956 * Q6.2.2:: How do I change fonts in XEmacs on MS Windows?
|
|
|
5957 * Q6.2.3:: Where do I put my @file{.emacs} file?
|
|
359
|
5958
|
|
|
5959 Miscellaneous
|
|
365
|
5960 * Q6.3.1:: Will XEmacs rename all the win32-* symbols to w32-*?
|
|
|
5961 * Q6.3.2:: What are the differences between the various MS Windows emacsen?
|
|
|
5962 * Q6.3.3:: What is the porting team doing at the moment?
|
|
359
|
5963
|
|
361
|
5964 Troubleshooting:
|
|
|
5965 * Q6.4.1:: XEmacs won't start on Windows. (NEW)
|
|
|
5966
|
|
359
|
5967 @end menu
|
|
|
5968
|
|
|
5969 @node Q6.0.1, Q6.0.2, MS Windows, MS Windows
|
|
|
5970 @unnumberedsec 6.0: General Info
|
|
|
5971 @unnumberedsubsec Q6.0.1: What is the status of the XEmacs port to Windows?
|
|
|
5972
|
|
|
5973 Is XEmacs really getting ported to MS Windows? What is the status of the port?
|
|
|
5974
|
|
|
5975 Yes, a group of volunteers actively works on making XEmacs code base
|
|
|
5976 cleanly compile and run on MS Windows operating systems. The mailing
|
|
|
5977 list at @email{xemacs-nt@@xemacs.org} is dedicated to that effort (please use
|
|
|
5978 the -request address to subscribe).
|
|
|
5979
|
|
|
5980 At this time, XEmacs on MS Windows is usable, but lacks some of the
|
|
|
5981 features of XEmacs on UNIX and UNIX-like systems. Notably,
|
|
|
5982 internationalization does not work.
|
|
|
5983
|
|
|
5984 @node Q6.0.2, Q6.0.3, Q6.0.1, MS Windows
|
|
|
5985 @unnumberedsubsec Q6.0.2: What flavors of MS Windows are supported? The list name implies NT only.
|
|
|
5986
|
|
|
5987 The list name is misleading, as XEmacs will support both Windows 95,
|
|
|
5988 Windows 98 and Windows NT. The MS Windows-specific code is based on
|
|
|
5989 Microsoft Win32 API, and will not work on MS Windows 3.x or on MS-DOS.
|
|
|
5990
|
|
|
5991
|
|
|
5992 @node Q6.0.3, Q6.0.4, Q6.0.2, MS Windows
|
|
|
5993 @unnumberedsubsec Q6.0.3: Are binary kits available?
|
|
|
5994
|
|
|
5995 Binary kits are available at
|
|
|
5996 @uref{ftp://ftp.xemacs.org/pub/xemacs/binary-kits/win32/} for the
|
|
|
5997 "plain" MS Windows version.
|
|
|
5998
|
|
|
5999 @node Q6.0.4, Q6.1.1, Q6.0.3, MS Windows
|
|
|
6000 @unnumberedsubsec Q6.0.4: Does XEmacs on MS Windows require an X server to run?
|
|
|
6001
|
|
|
6002 Short answer: No.
|
|
|
6003
|
|
|
6004 Long answer: XEmacs can be built in several ways in the MS Windows
|
|
|
6005 environment, some of them requiring an X server and some not.
|
|
|
6006
|
|
365
|
6007 One is what we call the "X" port---it requires X libraries to build
|
|
359
|
6008 and an X server to run. Internally it uses the Xt event loop and
|
|
|
6009 makes use of X toolkits. Its look is quite un-Windowsy, but it works
|
|
|
6010 reliably and supports all of the graphical features of Unix XEmacs.
|
|
|
6011
|
|
|
6012 The other is what we call the "native" port. It uses the Win32 API
|
|
|
6013 and does not require X libraries to build, nor does it require an X to
|
|
|
6014 run. In fact, it has no connection with X whatsoever. At this time,
|
|
|
6015 the native port obsoletes the X port, providing almost all of its
|
|
|
6016 features, including support for menus, scrollbars, toolbars, embedded
|
|
|
6017 images and background pixmaps, frame pointers, etc. Most of the
|
|
|
6018 future work will be based on the native port.
|
|
|
6019
|
|
|
6020 There is also a third special case, the Cygwin port. It takes
|
|
|
6021 advantage of Cygnus emulation library under Win32, which enables it to
|
|
|
6022 reuse much of the Unix XEmacs code base, such as processes and network
|
|
|
6023 support, or internal select() mechanisms.
|
|
|
6024
|
|
365
|
6025 Cygwin port supports all display types---TTY, X & MS gui, and can be
|
|
359
|
6026 built with support for all three. If you build with ms gui support
|
|
|
6027 then the Cygwin version uses the majority of the msw code, which is
|
|
|
6028 mostly related to display. If you want to build with X support you
|
|
|
6029 need X libraries. If you want to build with tty support you need
|
|
|
6030 ncurses. MS gui requires no additional libraries.
|
|
|
6031
|
|
|
6032 Some of the advantages of the Cygwin version are that it:
|
|
|
6033
|
|
|
6034 @itemize @bullet
|
|
|
6035
|
|
|
6036 @item integrates well with Cygwin environment for existing Cygwin users;
|
|
|
6037 @item uses configure so building with different features is very easy;
|
|
|
6038 @item has process support in X & tty.
|
|
|
6039
|
|
|
6040 @end itemize
|
|
|
6041
|
|
|
6042 The disadvantage is that it requires several Unix utilities and the
|
|
|
6043 whole Cygwin environment, whereas the native port requires only a
|
|
|
6044 suitable MS Windows compiler. Also, it follows the Unix filesystem and
|
|
|
6045 process model very closely (some will undoubtedly view this as an
|
|
|
6046 advantage).
|
|
|
6047
|
|
|
6048 @node Q6.1.1, Q6.1.2, Q6.0.4, MS Windows
|
|
|
6049 @unnumberedsec 6.1: Building XEmacs on MS Windows
|
|
|
6050 @unnumberedsubsec Q6.1.1: I decided to run with X. Where do I get an X server?
|
|
|
6051
|
|
|
6052 Pointers to X servers can be found at
|
|
|
6053 @iftex
|
|
|
6054 @*
|
|
|
6055 @end iftex
|
|
365
|
6056 @uref{http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.3/};
|
|
359
|
6057
|
|
|
6058 look for "Where to get an X server". Also note that, although the above
|
|
|
6059 page talks about Cygnus gnu-win32 (Cygwin), the information on X servers
|
|
|
6060 is Cygwin-independent. You don't have to be running/using Cygwin to use
|
|
|
6061 these X servers, and you don't have to compile XEmacs under Cygwin to
|
|
|
6062 use XEmacs with these X servers. An "X port" XEmacs compiled under
|
|
|
6063 Visual C++ will work with these X servers (as will XEmacs running on a
|
|
|
6064 Unix box, redirected to the server running on your PC).
|
|
|
6065
|
|
|
6066
|
|
|
6067 @node Q6.1.2, Q6.1.3, Q6.1.1, MS Windows
|
|
|
6068 @unnumberedsubsec Q6.1.2: What compiler do I need to compile XEmacs?
|
|
|
6069
|
|
365
|
6070 You need Visual C++ 4.2, 5.0, or 6.0, with the exception of the Cygwin
|
|
|
6071 port, which uses Gcc. There is also a MINGW32 port of XEmacs (using
|
|
|
6072 Gcc, but using native libraries rather than the Cygwin libraries). ####
|
|
|
6073 More information about this should be provided.
|
|
359
|
6074
|
|
|
6075
|
|
|
6076 @node Q6.1.3, Q6.1.4, Q6.1.2, MS Windows
|
|
|
6077 @unnumberedsubsec Q6.1.3: How do I compile for the native port?
|
|
|
6078
|
|
|
6079 Please read the file @file{nt/README} in the XEmacs distribution, which
|
|
|
6080 contains the full description.
|
|
|
6081
|
|
|
6082
|
|
|
6083 @node Q6.1.4, Q6.1.5, Q6.1.3, MS Windows
|
|
|
6084 @unnumberedsubsec Q6.1.4: How do I compile for the X port?
|
|
|
6085
|
|
|
6086 Again, it is described in @file{nt/README} in some detail. Basically, you
|
|
|
6087 need to get X11 libraries from ftp.x.org, and compile them. If the
|
|
|
6088 precompiled versions are available somewhere, I don't know of it.
|
|
|
6089
|
|
|
6090
|
|
|
6091 @node Q6.1.5, Q6.1.6, Q6.1.4, MS Windows
|
|
|
6092 @unnumberedsubsec Q6.1.5: How do I compile for Cygnus' Cygwin?
|
|
|
6093
|
|
|
6094 Similar as on Unix; use the usual `configure' and `make' process.
|
|
|
6095 Some problems to watch out for:
|
|
|
6096
|
|
|
6097 @itemize @bullet
|
|
|
6098 @item
|
|
|
6099 make sure HOME is set. This controls where you @file{.emacs} file comes
|
|
|
6100 from;
|
|
|
6101
|
|
|
6102 @item
|
|
365
|
6103 CYGWIN needs to be set to tty for process support work. e.g. CYGWIN=tty;
|
|
|
6104 (use CYGWIN32=tty under b19 and older.)
|
|
359
|
6105
|
|
|
6106 @item
|
|
|
6107 picking up some other grep or other unix like tools can kill configure;
|
|
|
6108
|
|
|
6109 @item
|
|
|
6110 static heap too small, adjust src/sheap-adjust.h to a more positive
|
|
|
6111 number;
|
|
|
6112
|
|
|
6113 @item
|
|
|
6114 The Cygwin version doesn't understand @file{//machine/path} type paths so you
|
|
|
6115 will need to manually mount a directory of this form under a unix style
|
|
|
6116 directory for a build to work on the directory.
|
|
|
6117
|
|
|
6118 @end itemize
|
|
|
6119
|
|
|
6120 @node Q6.1.6, Q6.2.1, Q6.1.5, MS Windows
|
|
|
6121 @unnumberedsubsec Q6.1.6: What do I need for Cygwin?
|
|
|
6122
|
|
|
6123 You can find the Cygwin tools and compiler at:
|
|
|
6124
|
|
|
6125 @uref{http://sourceware.cygnus.com/cygwin/}
|
|
|
6126
|
|
|
6127 You will need version b19 or later.
|
|
365
|
6128 The latest current version is 1.1.1.
|
|
|
6129 Other common versions you will see are b20.1.
|
|
|
6130
|
|
|
6131 Another location, one of the mirror sites of the site just mentioned,
|
|
|
6132 is usually a last faster:
|
|
|
6133
|
|
|
6134 @uref{ftp://ftp.freesoftware.com/pub/sourceware/cygwin/}
|
|
|
6135
|
|
|
6136 You can obtain the latest version (currently 1.1.1) from the
|
|
|
6137 @samp{latest/} subdirectory of either of the above two just-mentioned
|
|
|
6138 URL's.
|
|
|
6139
|
|
|
6140 @strong{WARNING: The version of GCC supplied under @samp{latest/}, as of
|
|
|
6141 June 6th, 2000, does not appear to work. It generates loads of spurious
|
|
|
6142 preprocessor warnings and errors, which makes it impossible to compile
|
|
|
6143 XEmacs with it.}
|
|
|
6144
|
|
|
6145 You will also need the X libraries. You can get them on the XEmacs FTP
|
|
|
6146 site at
|
|
|
6147
|
|
|
6148 @uref{ftp://ftp.xemacs.org/pub/xemacs/aux/cygwin/}
|
|
|
6149
|
|
|
6150 You will find b19 and b20 versions of the X libraries, plus b19 and b20
|
|
|
6151 versions of stuff that should go into @samp{/usr/local/}, donated by
|
|
|
6152 Andy Piper. This includes pre-built versions of various graphics libraries,
|
|
|
6153 such as PNG, JPEG, TIFF, and XPM. (Remember, GIF support is built-in to
|
|
|
6154 XEmacs.)
|
|
|
6155
|
|
|
6156 (X libraries for v1 and beyond of Cygwin can be found on the Cygwin site
|
|
|
6157 itself -- look in the @samp{xfree/} subdirectory.)
|
|
|
6158
|
|
|
6159 @emph{NOTE:} There are two versions of the XPM library provided in
|
|
|
6160 Andy's packets. Once is for building with X support, and the other for
|
|
|
6161 building without. The X version should work if you're building with
|
|
|
6162 both X and Windows support. The two files are called @file{libXpm-X.a}
|
|
|
6163 and @file{libXpm-noX.a} respectively, and you must symlink the
|
|
|
6164 appropriate one to @file{libXpm.a}. @strong{CAREFUL:} By default, the
|
|
|
6165 non-X version is symlinked in. If you then configure XEmacs with X,
|
|
|
6166 you won't run into problems until you start compiling @file{events.c},
|
|
|
6167 at which point you'll get strange and decidedly non-obvious errors.
|
|
|
6168
|
|
|
6169 Please see @uref{http://www.xemacs.freeserve.co.uk/} (Andy Piper's home
|
|
|
6170 page) for more information.
|
|
|
6171
|
|
|
6172 BTW There are also libraries at
|
|
359
|
6173 @iftex
|
|
|
6174 @*
|
|
|
6175 @end iftex
|
|
|
6176 @uref{http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.3/}, but
|
|
365
|
6177 these are not b19 compatible, and may in fact be native-compiled.
|
|
359
|
6178
|
|
|
6179
|
|
|
6180 @node Q6.2.1, Q6.2.2, Q6.1.6, MS Windows
|
|
|
6181 @unnumberedsec 6.2: Customization and User Interface
|
|
|
6182 @unnumberedsubsec Q6.2.1: How will the port cope with differences in the Windows user interface?
|
|
|
6183
|
|
365
|
6184 XEmacs (and Emacs in general) UI is pretty
|
|
359
|
6185 different from what is expected of a typical MS Windows program. How will
|
|
|
6186 the MS Windows port cope with it?
|
|
|
6187
|
|
|
6188 Fortunately, Emacs is also one of the most configurable editor beasts
|
|
|
6189 in the world. The MS Windows "look and feel" (mark via shift-arrow,
|
|
|
6190 self-inserting deletes region, etc.) can be easily configured via
|
|
|
6191 various packages distributed with XEmacs. The `pending-delete'
|
|
|
6192 package is an example of such a utility.
|
|
|
6193
|
|
|
6194 In future versions, some of these packages might be turned on by
|
|
|
6195 default in the MS Windows environment.
|
|
|
6196
|
|
|
6197
|
|
|
6198 @node Q6.2.2, Q6.2.3, Q6.2.1, MS Windows
|
|
|
6199 @unnumberedsubsec Q6.2.2: How do I change fonts in XEmacs on MS Windows?
|
|
|
6200
|
|
365
|
6201 In 21.2.*, use the font menu. In 21.1.*, you can change font
|
|
|
6202 manually. For example:
|
|
359
|
6203
|
|
|
6204 @display
|
|
|
6205 (set-face-font 'default "Lucida Console:Regular:10")
|
|
|
6206 (set-face-font 'modeline "MS Sans Serif:Regular:10")
|
|
|
6207 @end display
|
|
|
6208
|
|
|
6209
|
|
|
6210 @node Q6.2.3, Q6.3.1, Q6.2.2, MS Windows
|
|
|
6211 @unnumberedsubsec Q6.2.3: Where do I put my @file{.emacs} file?
|
|
|
6212
|
|
|
6213 If the HOME environment variable is set, @file{.emacs} will be looked for
|
|
|
6214 there. Else the directory defaults to `c:\'.
|
|
|
6215
|
|
|
6216 @node Q6.3.1, Q6.3.2, Q6.2.3, MS Windows
|
|
|
6217 @unnumberedsec 6.3: Miscellaneous
|
|
|
6218 @unnumberedsubsec Q6.3.1: Will XEmacs rename all the win32-* symbols to w32-*?
|
|
|
6219
|
|
|
6220 In his flavor of Emacs 20, Richard Stallman has renamed all the win32-*
|
|
|
6221 symbols to w32-*. Will XEmacs do the same?
|
|
|
6222
|
|
|
6223 We consider such a move counter-productive, thus we will not use the
|
|
|
6224 `w32' prefix. However, we do recognize that Win32 name is little more
|
|
|
6225 than a marketing buzzword (will it be Win64 in the next release?), so
|
|
|
6226 we decided not to use it. Using `windows-' would be wrong because the
|
|
|
6227 term is too generic, which is why we settled on a compromise
|
|
|
6228 `mswindows' term.
|
|
|
6229
|
|
|
6230 Thus all the XEmacs variables and functions directly related to Win32
|
|
|
6231 are prefixed `mswindows-'. The user-variables shared with NT Emacs
|
|
|
6232 will be provided as compatibility aliases.
|
|
|
6233
|
|
|
6234 Architectural note: We believe that there should be a very small
|
|
|
6235 number of window-systems-specific variables, and will try to provide
|
|
|
6236 generic interfaces whenever possible.
|
|
|
6237
|
|
|
6238
|
|
|
6239 @node Q6.3.2, Q6.3.3, Q6.3.1, MS Windows
|
|
|
6240 @unnumberedsubsec Q6.3.2: What are the differences between the various MS Windows emacsen?
|
|
|
6241
|
|
|
6242 XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing.
|
|
|
6243 Could you briefly explain the differences between them?
|
|
|
6244
|
|
|
6245 Here is a recount of various Emacs versions running on MS Windows:
|
|
|
6246
|
|
|
6247 @itemize @bullet
|
|
|
6248
|
|
365
|
6249 @item
|
|
359
|
6250 Win-Emacs
|
|
|
6251
|
|
|
6252 @itemize @minus
|
|
|
6253
|
|
|
6254 @item
|
|
|
6255 Win-Emacs is a port of Lucid Emacs 19.6 to MS Windows using X
|
|
|
6256 compatibility libraries. Win-Emacs has been written by Ben Wing. The
|
|
|
6257 MS Windows code has not made it back to Lucid Emacs, which left Win-Emacs
|
|
|
6258 pretty much dead for our purposes. Win-Emacs used to be available at
|
|
|
6259 Pearlsoft, but not anymore, since Pearlsoft went out of business.
|
|
|
6260 @end itemize
|
|
|
6261
|
|
|
6262 @item
|
|
|
6263 GNU Emacs for DOS
|
|
|
6264
|
|
365
|
6265 @itemize @minus
|
|
359
|
6266
|
|
|
6267 @item
|
|
|
6268 GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS
|
|
|
6269 port of Gcc). Such an Emacs is heavily underfeatured, because it does
|
|
|
6270 not supports long file names, lacks proper subprocesses support, and
|
|
|
6271 is far too big compared to typical DOS editors.
|
|
|
6272 @end itemize
|
|
|
6273
|
|
|
6274 @item
|
|
|
6275 GNU Emacs compiled with Win32
|
|
|
6276
|
|
365
|
6277 @itemize @minus
|
|
359
|
6278
|
|
|
6279 @item
|
|
|
6280 Starting with version 19.30, it has been possible to compile GNU Emacs
|
|
|
6281 under MS Windows using the DJGPP compiler and X libraries. The result
|
|
|
6282 is is very similar to GNU Emacs compiled under MS DOS, only it
|
|
|
6283 supports longer file names, etc. This "port" is similar to the "X"
|
|
|
6284 flavor of XEmacs on MS Windows.
|
|
|
6285 @end itemize
|
|
|
6286
|
|
|
6287 @item
|
|
|
6288 NT Emacs
|
|
|
6289
|
|
365
|
6290 @itemize @minus
|
|
359
|
6291
|
|
|
6292 @item
|
|
|
6293 NT Emacs is a version of GNU Emacs modified to compile and run under
|
|
|
6294 MS MS Windows 95 and NT using the native Win32 API. As such, it is close
|
|
|
6295 in spirit to the XEmacs "native" port.
|
|
|
6296
|
|
|
6297 @item
|
|
|
6298 NT Emacs has been written by Geoff Voelker, and more information can be
|
|
365
|
6299 found at
|
|
359
|
6300 @iftex
|
|
|
6301 @*
|
|
|
6302 @end iftex
|
|
|
6303 @uref{http://www.cs.washington.edu/homes/voelker/ntemacs.html}.
|
|
|
6304
|
|
|
6305 @end itemize
|
|
|
6306
|
|
|
6307 @item
|
|
|
6308 XEmacs
|
|
|
6309
|
|
365
|
6310 @itemize @minus
|
|
359
|
6311
|
|
|
6312 @item
|
|
|
6313 Beginning with XEmacs 19.12, XEmacs' architecture has been redesigned
|
|
|
6314 in such a way to allow clean support of multiple window systems. At
|
|
|
6315 this time the TTY support was added, making X and TTY the first two
|
|
|
6316 "window systems" XEmacs supported. The 19.12 design is the basis for
|
|
|
6317 the current native MS Windows code.
|
|
|
6318
|
|
|
6319 @item
|
|
|
6320 Some time during 1997, David Hobley (soon joined by Marc Paquette)
|
|
|
6321 imported some of the NT-specific portions of GNU Emacs, making XEmacs
|
|
|
6322 with X support compile under Windows NT, and creating the "X" port.
|
|
|
6323
|
|
|
6324 @item
|
|
|
6325 Several months later, Jonathan Harris sent out initial patches to use
|
|
|
6326 the Win32 API, thus creating the native port. Since then, various
|
|
|
6327 people have contributed, including Kirill M. Katsnelson (contributed
|
|
|
6328 support for menubars, subprocesses and network, as well as loads of
|
|
|
6329 other code), Andy Piper (ported XEmacs to Cygwin environment,
|
|
|
6330 contributed Windows unexec, Windows-specific glyphs and toolbars code,
|
|
|
6331 and more), Jeff Sparkes (contributed scrollbars support) and many
|
|
|
6332 others.
|
|
|
6333
|
|
|
6334 @end itemize
|
|
|
6335
|
|
|
6336 @end itemize
|
|
|
6337
|
|
|
6338
|
|
361
|
6339 @node Q6.3.3, Q6.4.1, Q6.3.2, MS Windows
|
|
359
|
6340 @unnumberedsubsec Q6.3.3: What is the porting team doing at the moment?
|
|
|
6341
|
|
|
6342 The porting team is continuing work on the MS Windows-specific code.
|
|
|
6343
|
|
361
|
6344 @node Q6.4.1, ,Q6.3.3, MS Windows
|
|
|
6345 @unnumberedsec 6.3: Troubleshooting
|
|
|
6346 @unnumberedsubsec Q6.4.1 XEmacs won't start on Windows. (NEW)
|
|
|
6347
|
|
|
6348 XEmacs relies on a process called "dumping" to generate a working
|
|
|
6349 executable. Under MS-Windows this process effectively fixes the memory
|
|
|
6350 addresses of information in the executable. When XEmacs starts up it tries
|
|
|
6351 to reserve these memory addresses so that the dumping process can be
|
|
|
6352 reversed - putting the information back at the correct addresses.
|
|
|
6353 Unfortunately some .dlls (For instance the soundblaster driver) occupy
|
|
|
6354 memory addresses that can conflict with those needed by the dumped XEmacs
|
|
|
6355 executable. In this instance XEmacs will fail to start without any
|
|
|
6356 explanation. Note that this is extremely machine specific.
|
|
|
6357
|
|
365
|
6358 21.1.10 includes a fix for this that makes more intelligent guesses
|
|
|
6359 about which memory addresses will be free, and this should cure the
|
|
|
6360 problem for most people. Unfortunately, no binary is yet available for
|
|
|
6361 this version. Check back periodically at
|
|
|
6362
|
|
|
6363 @uref{ftp://ftp.xemacs.org/pub/xemacs/binaries/}.
|
|
361
|
6364
|
|
|
6365 21.2 implements "portable dumping" which will eliminate the problem
|
|
365
|
6366 altogether. You might have better luck with the 21.2 beta binary,
|
|
|
6367 available at
|
|
|
6368
|
|
|
6369 @uref{ftp://ftp.xemacs.org/pub/xemacs/beta/binaries/}.
|
|
|
6370
|
|
359
|
6371
|
|
|
6372 @node Current Events, , MS Windows, Top
|
|
|
6373 @unnumbered 7 What the Future Holds
|
|
|
6374
|
|
|
6375 This is part 7 of the XEmacs Frequently Asked Questions list. This
|
|
82
|
6376 section will change monthly, and contains any interesting items that have
|
|
|
6377 transpired over the previous month. If you are reading this from the
|
|
|
6378 XEmacs distribution, please see the version on the Web or archived at the
|
|
|
6379 various FAQ FTP sites, as this file is surely out of date.
|
|
|
6380
|
|
|
6381 @menu
|
|
359
|
6382 * Q7.0.1:: What is new in 20.2?
|
|
|
6383 * Q7.0.2:: What is new in 20.3?
|
|
|
6384 * Q7.0.3:: What is new in 20.4?
|
|
|
6385 * Q7.0.4:: Procedural changes in XEmacs development.
|
|
82
|
6386 @end menu
|
|
|
6387
|
|
359
|
6388 @node Q7.0.1, Q7.0.2, Current Events, Current Events
|
|
|
6389 @unnumberedsec 7.0: Changes
|
|
|
6390 @unnumberedsubsec Q7.0.1: What is new in 20.2?
|
|
163
|
6391
|
|
217
|
6392 The biggest changes in 20.2 include integration of EFS (the next
|
|
163
|
6393 generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a
|
|
126
|
6394 major mode for editing Tex and LaTeX, and a lot of other stuff). Many
|
|
163
|
6395 bugs from 20.0 have been fixed for this release. 20.2 also contains a
|
|
|
6396 new system for customizing XEmacs options, invoked via @kbd{M-x
|
|
|
6397 customize}.
|
|
|
6398
|
|
|
6399 XEmacs 20.2 is the development release (20.0 was beta), and is no longer
|
|
|
6400 considered unstable.
|
|
|
6401
|
|
359
|
6402 @node Q7.0.2, Q7.0.3, Q7.0.1, Current Events
|
|
|
6403 @unnumberedsubsec Q7.0.2: What is new in 20.3?
|
|
163
|
6404
|
|
227
|
6405 XEmacs 20.3 was released in November 1997. It contains many bugfixes,
|
|
|
6406 and a number of new features, including Autoconf 2 based configuration,
|
|
|
6407 additional support for Mule (Multi-language extensions to Emacs), many
|
|
|
6408 more customizations, multiple frames on TTY-s, support for multiple info
|
|
|
6409 directories, an enhanced gnuclient, improvements to regexp matching,
|
|
|
6410 increased MIME support, and many, many synches with GNU Emacs 20.
|
|
|
6411
|
|
|
6412 The XEmacs/Mule support has been only seriously tested in a Japanese
|
|
|
6413 locale, and no doubt many problems still remain. The support for
|
|
|
6414 ISO-Latin-1 and Japanese is fairly strong. MULE support comes at a
|
|
365
|
6415 price---about a 30% slowdown from 19.16. We're making progress on
|
|
227
|
6416 improving performance and XEmacs 20.3 compiled without Mule (which is
|
|
|
6417 the default) is definitely faster than XEmacs 19.16.
|
|
|
6418
|
|
|
6419 XEmacs 20.3 is the first non-beta v20 release, and will be the
|
|
215
|
6420 basis for all further development.
|
|
|
6421
|
|
359
|
6422 @node Q7.0.3, Q7.0.4, Q7.0.2, Current Events
|
|
|
6423 @unnumberedsubsec Q7.0.3: What's new in XEmacs 20.4?
|
|
274
|
6424
|
|
|
6425 XEmacs 20.4 is a bugfix release with no user-visible changes.
|
|
|
6426 @c Filled in from NEWS file of 20.5-b33
|
|
|
6427
|
|
|
6428
|
|
359
|
6429 @node Q7.0.4, , Q7.0.3, Current Events
|
|
|
6430 @unnumberedsubsec Q7.0.4: Procedural changes in XEmacs development.
|
|
82
|
6431
|
|
|
6432 @enumerate
|
|
|
6433 @item
|
|
|
6434 Discussion about the development of XEmacs occurs on the xemacs-beta
|
|
|
6435 mailing list. Subscriptions to this list will now be fully automated
|
|
|
6436 instead of being handled by hand. Send a mail message to
|
|
282
|
6437 @email{xemacs-beta-request@@xemacs.org} with @samp{subscribe} as the
|
|
|
6438 BODY of the message to join the list. Please note this is a developers
|
|
|
6439 mailing list for people who have an active interest in the development
|
|
|
6440 process.
|
|
82
|
6441
|
|
215
|
6442 The discussion of NT XEmacs development is taking place on a separate
|
|
282
|
6443 mailing list. Send mail to
|
|
|
6444 @iftex
|
|
|
6445 @*
|
|
|
6446 @end iftex
|
|
274
|
6447 @email{xemacs-nt-request@@xemacs.org} to
|
|
215
|
6448 subscribe.
|
|
|
6449
|
|
82
|
6450 @item
|
|
|
6451 Due to the long development cycle in between releases, it has been
|
|
|
6452 decided that intermediate versions will be made available in source only
|
|
|
6453 form for the truly interested.
|
|
|
6454
|
|
215
|
6455 XEmacs 19.16 was the last 19 release, basically consisting of 19.15 plus
|
|
|
6456 the collected bugfixes.
|
|
82
|
6457
|
|
|
6458 @item
|
|
359
|
6459 As of December 1996, @email{steve@@xemacs.org, Steve Baur} has become
|
|
82
|
6460 the lead maintainer of XEmacs.
|
|
163
|
6461 @end enumerate
|
|
82
|
6462
|
|
0
|
6463 @bye
|
