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