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