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