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