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