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