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