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