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