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