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