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