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