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