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