|
0
|
1 -*- mode:outline; minor-mode:outl-mouse -*-
|
|
|
2
|
|
|
3 * Introduction
|
|
|
4 ==============
|
|
|
5
|
|
|
6 This file presents some general information about XEmacs. It is primarily
|
|
|
7 about the evolution of XEmacs and its release history.
|
|
|
8
|
|
|
9 There are five sections.
|
|
|
10
|
|
|
11 Introduction................(this section) provides an introduction
|
|
|
12
|
|
|
13 Using Outline Mode..........briefly explains how to use outline mode
|
|
|
14
|
|
|
15 The History of XEmacs.......some historical notes
|
|
|
16
|
|
70
|
17 What's Different?...........new or changed capabilities
|
|
|
18
|
|
|
19 XEmacs Release Notes........details of the changes between releases
|
|
|
20
|
|
|
21 New users should look at the next section on "Using Outline Mode". You will
|
|
|
22 be more efficient when you can navigate quickly through this file. Users
|
|
|
23 interested in some of the details of how XEmacs differs from FSF GNU Emacs
|
|
|
24 should read the section "What's Different?". Users who would to know which
|
|
|
25 capabilities have been introduced in each release should look at the
|
|
|
26 appropriate subsection of the "XEmacs Release Notes."
|
|
|
27
|
|
|
28 N.B. The term "FSF GNU Emacs" refers to any release of Emacs Version 19
|
|
|
29 from the Free Software Foundation's GNU Project. (We do not say just
|
|
|
30 "GNU Emacs" because Richard M. Stallman ["RMS"] thinks that this term
|
|
|
31 is too generic; although we sometimes say e.g. "GNU Emacs 19.30" to refer
|
|
|
32 to a specific version of FSF GNU Emacs. We do not say merely "Emacs", as
|
|
|
33 RMS prefers, because that is clearly an even more generic term.) The term
|
|
|
34 "XEmacs" refers to this program or to its predecessors "Era" and
|
|
|
35 "Lucid Emacs". The predecessor of all these program is called "Emacs 18".
|
|
|
36 When no particular version is implied, "Emacs" will be used.
|
|
0
|
37
|
|
|
38
|
|
|
39 * Using Outline Mode
|
|
|
40 ====================
|
|
|
41
|
|
|
42 This file is in outline mode, a major mode for viewing (or editing)
|
|
|
43 outlines. It allows you to make parts of the text temporarily invisible so
|
|
|
44 that you can see just the overall structure of the outline.
|
|
|
45
|
|
|
46 There are two ways of using outline mode: with keys or with menus. Using
|
|
|
47 outline mode with menus is the simplest and is just as effective as using
|
|
|
48 keystrokes. There are menus for outline mode on the menubar as well as in
|
|
|
49 popup menus activated by pressing mouse button 3.
|
|
|
50
|
|
70
|
51 Experiment with the menu commands. Menu items under "Headings" allow
|
|
|
52 you to navigate from heading to heading. Menu items under "Show" make
|
|
|
53 visible portions of the outline while menu items under "Hide" do the
|
|
|
54 opposite.
|
|
|
55
|
|
|
56 A special minor mode called "outl-mouse" has been automatically enabled. In
|
|
|
57 this minor mode, glyphs appear which, when clicked on, will alternately hide
|
|
|
58 or show sections of the outline.
|
|
|
59
|
|
0
|
60 You may at any time press `C-h m' to get a listing of the outline mode key
|
|
70
|
61 bindings. They are reproduced here:
|
|
|
62
|
|
|
63 Commands:
|
|
|
64 C-c C-n outline-next-visible-heading move by visible headings
|
|
|
65 C-c C-p outline-previous-visible-heading
|
|
|
66 C-c C-f outline-forward-same-level similar but skip subheadings
|
|
|
67 C-c C-b outline-backward-same-level
|
|
|
68 C-c C-u outline-up-heading move from subheading to heading
|
|
|
69
|
|
|
70 C-c C-t make all text invisible (not headings).
|
|
|
71 M-x show-all make everything in buffer visible.
|
|
|
72
|
|
|
73 The remaining commands are used when point is on a heading line.
|
|
|
74 They apply to some of the body or subheadings of that heading.
|
|
|
75 C-c C-d hide-subtree make body and subheadings invisible.
|
|
|
76 C-c C-s show-subtree make body and subheadings visible.
|
|
|
77 C-c tab show-children make direct subheadings visible.
|
|
|
78 No effect on body, or subheadings 2 or more levels down.
|
|
|
79 With arg N, affects subheadings N levels down.
|
|
|
80 C-c C-c make immediately following body invisible.
|
|
|
81 C-c C-e make it visible.
|
|
|
82 C-c C-l make body under heading and under its subheadings invisible.
|
|
|
83 The subheadings remain visible.
|
|
|
84 C-c C-k make all subheadings at all levels visible.x1
|
|
|
85
|
|
0
|
86
|
|
|
87 * The History of XEmacs
|
|
|
88 =======================
|
|
|
89
|
|
|
90 This product is an extension of GNU Emacs, previously known to some as
|
|
|
91 "Lucid Emacs" or "ERA". It was initially based on an early version of Emacs
|
|
|
92 Version 19 from the Free Software Foundation and has since been kept
|
|
|
93 up-to-date with recent versions of that product. It stems from a
|
|
|
94 collaboration of Lucid, Inc. with SunSoft DevPro (a division of Sun
|
|
|
95 Microsystems, Inc.; formerly called SunPro) and the University of Illinois.
|
|
|
96
|
|
|
97 NOTE: Lucid, Inc. is currently out of business but development on XEmacs
|
|
|
98 continues strong. Recently, Amdahl Corporation and INS Engineering have
|
|
|
99 both contributed significantly to the development of XEmacs.
|
|
|
100
|
|
|
101
|
|
70
|
102 * What's Different?
|
|
0
|
103 ===================
|
|
|
104
|
|
|
105
|
|
70
|
106 ** Differences between XEmacs and FSF GNU Emacs 19
|
|
0
|
107 ==================================================
|
|
88
|
108 In XEmacs 20, characters are first-class objects. Characters can be
|
|
|
109 converted to integers, but are not integers. FSF 19, XEmacs 19, and Mule
|
|
|
110 represent them as integers.
|
|
0
|
111
|
|
|
112 In XEmacs, events are first-class objects. FSF 19 represents them as
|
|
|
113 integers, which obscures the differences between a key gesture and the
|
|
|
114 ancient ASCII code used to represent a particular overlapping subset of them.
|
|
|
115
|
|
|
116 In XEmacs, keymaps are first-class opaque objects. FSF 19 represents them as
|
|
|
117 complicated combinations of association lists and vectors. If you use the
|
|
|
118 advertised functional interface to manipulation of keymaps, the same code
|
|
70
|
119 will work in XEmacs, Emacs 18, and FSF GNU Emacs 19; if your code depends
|
|
0
|
120 on the underlying implementation of keymaps, it will not.
|
|
|
121
|
|
|
122 XEmacs uses "extents" to represent all non-textual aspects of buffers;
|
|
|
123 FSF 19 uses two distinct objects, "text properties" and "overlays",
|
|
|
124 which divide up the functionality between them. Extents are a
|
|
|
125 superset of the functionality of the two FSF data types. The full FSF
|
|
|
126 19 interface to text properties is supported in XEmacs (with extents
|
|
|
127 being the underlying representation).
|
|
|
128
|
|
|
129 Extents can be made to be copied into strings, and thus restored by kill
|
|
|
130 and yank. Thus, one can specify this behavior on either "extents" or
|
|
|
131 "text properties", whereas in FSF 19 text properties always have this
|
|
|
132 behavior and overlays never do.
|
|
|
133
|
|
|
134 Many more packages are provided standard with XEmacs than with FSF 19.
|
|
|
135
|
|
|
136 Pixmaps of arbitrary size can be embedded in a buffer.
|
|
|
137
|
|
|
138 Variable width fonts work.
|
|
|
139
|
|
|
140 The height of a line is the height of the tallest font on that line, instead
|
|
|
141 of all lines having the same height.
|
|
|
142
|
|
|
143 XEmacs uses the MIT "Xt" toolkit instead of raw Xlib calls, which
|
|
|
144 makes it be a more well-behaved X citizen (and also improves
|
|
|
145 portability). A result of this is that it is possible to include
|
|
|
146 other Xt "Widgets" in the XEmacs window. Also, XEmacs understands the
|
|
|
147 standard Xt command-line arguments.
|
|
|
148
|
|
|
149 XEmacs provides support for ToolTalk on systems that have it.
|
|
|
150
|
|
|
151 XEmacs can ask questions using popup dialog boxes. Any command executed from
|
|
|
152 a menu will ask yes/no questions with dialog boxes, while commands executed
|
|
|
153 via the keyboard will use the minibuffer.
|
|
|
154
|
|
|
155 XEmacs has a built-in toolbar. Four toolbars can actually be configured:
|
|
|
156 top, bottom, left, and right toolbars.
|
|
|
157
|
|
|
158 XEmacs has vertical and horizontal scrollbars. Unlike in FSF 19 (which
|
|
|
159 provides a primitive form of vertical scrollbar), these are true toolkit
|
|
|
160 scrollbars. A look-alike Motif scrollbar is provided for those who
|
|
|
161 don't have Motif. (Even for those who do, the look-alike may be preferable
|
|
|
162 as it is faster.)
|
|
|
163
|
|
70
|
164 If you're running on a machine with audio hardware, you can specify sound
|
|
0
|
165 files for XEmacs to play instead of the default X beep. See the documentation
|
|
|
166 of the function load-sound-file and the variable sound-alist.
|
|
|
167
|
|
|
168 An XEmacs frame can be placed within an "external client widget" managed by
|
|
|
169 another application. This allows an application to use an XEmacs frame as its
|
|
|
170 text pane rather than the standard Text widget that is provided with Motif or
|
|
|
171 Athena. XEmacs supports Motif applications, generic Xt (e.g. Athena)
|
|
|
172 applications, and raw Xlib applications.
|
|
|
173
|
|
|
174 Here are some more specifics about the XEmacs implementation:
|
|
|
175
|
|
|
176 *** The Input Model
|
|
|
177 -------------------
|
|
|
178
|
|
|
179 The fundamental unit of input is an "event" instead of a character. An
|
|
|
180 event is a new data type that contains several pieces of information.
|
|
|
181 There are several kinds of event, and corresponding accessor and utility
|
|
|
182 functions. We tried to abstract them so that they would apply equally
|
|
|
183 well to a number of window systems.
|
|
|
184
|
|
|
185 NOTE: All timestamps are measured as milliseconds since Emacs started.
|
|
|
186
|
|
70
|
187 key_press_event
|
|
|
188 event_channel A token representing which keyboard generated it.
|
|
88
|
189 For this kind of event, this is a console object.
|
|
70
|
190 timestamp When it happened
|
|
88
|
191 key What keysym this is; a character or a symbol.
|
|
|
192 If it is a character, it will be a printing
|
|
|
193 ASCII character.
|
|
70
|
194 modifiers Bucky-bits on that key: control, meta, etc.
|
|
|
195 For most keys, Shift is not a bit; that is implicit
|
|
|
196 in the keyboard layout.
|
|
0
|
197
|
|
|
198 button_press_event
|
|
|
199 button_release_event
|
|
70
|
200 event_channel A token representing which mouse generated it.
|
|
|
201 For this kind of event, this is a frame object.
|
|
|
202 timestamp When it happened
|
|
|
203 button What button went down or up.
|
|
|
204 modifiers Bucky-bits on that button: shift, control, meta, etc.
|
|
|
205 x, y Where it was at the button-state-change (in pixels).
|
|
0
|
206
|
|
|
207 pointer_motion_event
|
|
70
|
208 event_channel A token representing which mouse generated it.
|
|
|
209 For this kind of event, this is a frame object.
|
|
|
210 timestamp When it happened
|
|
|
211 x, y Where it was after it moved (in pixels).
|
|
|
212 modifiers Bucky-bits down when the motion was detected.
|
|
|
213 (Possibly not all window systems will provide this?)
|
|
0
|
214
|
|
|
215 process_event
|
|
70
|
216 timestamp When it happened
|
|
|
217 process the emacs "process" object in question
|
|
0
|
218
|
|
|
219 timeout_event
|
|
70
|
220 timestamp Now (really, when the timeout was signaled)
|
|
|
221 interval_id The ID returned when the associated call to
|
|
|
222 add_timeout_cb() was made
|
|
|
223 ------ the rest of the fields are filled in by Emacs -----
|
|
|
224 id_number The Emacs timeout ID for this timeout (more
|
|
|
225 than one timeout event can have the same value
|
|
|
226 here, since Emacs timeouts, as opposed to
|
|
|
227 add_timeout_cb() timeouts, can resignal
|
|
|
228 themselves)
|
|
|
229 function An elisp function to call when this timeout is
|
|
|
230 processed.
|
|
|
231 object The object passed to that function.
|
|
0
|
232
|
|
|
233 eval_event
|
|
70
|
234 timestamp When it happened
|
|
|
235 function An elisp function to call with this event object.
|
|
|
236 object Anything.
|
|
|
237 This kind of event is used internally; sometimes the
|
|
|
238 window system interface would like to inform emacs of
|
|
|
239 some user action (such as focusing on another frame)
|
|
|
240 but needs that to happen synchronously with the other
|
|
|
241 user input, like keypresses. This is useful when
|
|
|
242 events are reported through callbacks rather
|
|
|
243 than in the standard event stream.
|
|
0
|
244
|
|
|
245 misc_user_event
|
|
70
|
246 timestamp When it happened
|
|
|
247 function An elisp function to call with this event object.
|
|
|
248 object Anything.
|
|
|
249 This is similar to an eval_event, except that it is
|
|
|
250 generated by user actions: selections in the
|
|
|
251 menubar or scrollbar actions. It is a "command"
|
|
|
252 event, like key and mouse presses (and unlike mouse
|
|
|
253 motion, process output, and enter and leave window
|
|
|
254 hooks). In many ways, eval_events are not the same
|
|
|
255 as keypresses or misc_user_events.
|
|
0
|
256
|
|
|
257 magic_event
|
|
70
|
258 No user-serviceable parts within. This is for things
|
|
|
259 like KeymapNotify and ExposeRegion events and so on
|
|
|
260 that emacs itself doesn't care about, but which it
|
|
|
261 must do something with for proper interaction with
|
|
|
262 the window system.
|
|
|
263
|
|
|
264 Magic_events are handled somewhat asynchronously, just
|
|
|
265 like subprocess filters. However, occasionally a
|
|
|
266 magic_event needs to be handled synchronously; in that
|
|
|
267 case, the asynchronous handling of the magic_event will
|
|
|
268 push an eval_event back onto the queue, which will be
|
|
|
269 handled synchronously later. This is one of the
|
|
|
270 reasons why eval_events exist; I'm not entirely happy
|
|
|
271 with this aspect of this event model.
|
|
|
272
|
|
|
273
|
|
|
274 The function `next-event' blocks and returns one of the above-described
|
|
0
|
275 event objects. The function `dispatch-event' takes an event and processes
|
|
|
276 it in the appropriate way.
|
|
|
277
|
|
|
278 For a process-event, dispatch-event calls the process's handler; for a
|
|
|
279 mouse-motion event, the mouse-motion-handler hook is called, and so on.
|
|
|
280 For magic-events, dispatch-event does window-system-dependent things,
|
|
|
281 including calling some non-window-system-dependent hooks: map-frame-hook,
|
|
|
282 unmap-frame-hook, mouse-enter-frame-hook, and mouse-leave-frame-hook.
|
|
|
283
|
|
|
284 The function `next-command-event' calls `next-event' until it gets a key or
|
|
|
285 button from the user (that is, not a process, motion, timeout, or magic
|
|
|
286 event). If it gets an event that is not a key or button, it calls
|
|
|
287 `dispatch-event' on it immediately and reads another one. The
|
|
|
288 next-command-event function could be implemented in Emacs Lisp, though it
|
|
|
289 isn't. Generally one should call `next-command-event' instead of
|
|
|
290 `next-event'.
|
|
|
291
|
|
|
292 read-char calls next-command-event; if it doesn't get an event that can be
|
|
|
293 converted to an ASCII character, it signals an error. Otherwise it returns
|
|
|
294 an integer.
|
|
|
295
|
|
|
296 The variable `last-command-char' always contains an integer, or nil (if the
|
|
|
297 last read event has no ASCII equivalent, as when it is a mouse-click or a
|
|
|
298 non-ASCII character chord.)
|
|
|
299
|
|
|
300 The new variable `last-command-event' holds an event object, that could be
|
|
|
301 a non-ASCII character, a button click, a menu selection, etc.
|
|
|
302
|
|
|
303 The variable `unread-command-char' no longer exists, and has been replaced
|
|
|
304 by `unread-command-events'. With the new event model, it is incorrect for
|
|
|
305 code to do (setq unread-command-char (read-char)), because all user-input
|
|
70
|
306 can't be represented as ASCII characters. *** This is an incompatible
|
|
0
|
307 change. Code which sets `unread-command-char' must be updated to use the
|
|
|
308 combination of `next-command-event' and `unread-command-events' instead.
|
|
|
309
|
|
|
310 The functions `this-command-keys' and `recent-keys' return a vector of
|
|
|
311 event objects, instead of a string of ASCII characters. *** This also
|
|
|
312 is an incompatible change.
|
|
|
313
|
|
|
314 Almost nothing happens at interrupt level; the SIGIO handler simply sets a
|
|
|
315 flag, and later, the X event queue is scanned for KeyPress events which map
|
|
|
316 to ^G. All redisplay happens in the main thread of the process.
|
|
|
317
|
|
|
318
|
|
|
319 *** Keymaps
|
|
|
320 -----------
|
|
|
321
|
|
|
322 Instead of keymaps being alists or obarrays, they are a new primary data
|
|
|
323 type. The only user access to the contents of a keymap is through the
|
|
|
324 existing keymap-manipulation functions, and a new function, map-keymap.
|
|
70
|
325 This means that existing code that manipulates keymaps may need to
|
|
0
|
326 be changed.
|
|
|
327
|
|
|
328 One of our goals with the new input and keymap code was to make more
|
|
|
329 character combinations available for binding, besides just ASCII and
|
|
70
|
330 function keys. We want to be able bind different commands to Control-a
|
|
0
|
331 and Control-Shift-a; we also want it to be possible for the keys Control-h
|
|
|
332 and Backspace (and Control-M and Return, and Control-I and Tab, etc) to
|
|
|
333 be distinct.
|
|
|
334
|
|
|
335 One of the most common complaints that new Emacs users have is that backspace
|
|
|
336 is help. The answer is to play around with the keyboard-translate-table, or
|
|
|
337 be lucky enough to have a system administrator who has done this for you
|
|
|
338 already; but if it were possible to bind backspace and C-h to different
|
|
|
339 things, then (under a window manager at least) both backspace and delete
|
|
70
|
340 would delete a character, and ^H would be help. There's no need to deal
|
|
0
|
341 with xmodmap, kbd-translate-table, etc.
|
|
|
342
|
|
70
|
343 Here are some more examples: suppose you want to bind one function to Tab,
|
|
0
|
344 and another to Control-Tab. This can't be done if Tab and Control-I are the
|
|
|
345 same thing. What about control keys that have no ASCII equivalent, like
|
|
|
346 Control-< ? One might want that to be bound to set-mark-at-point-min. We
|
|
|
347 want M-C-Backspace to be kill-backward-sexp. But we want M-Backspace to be
|
|
|
348 kill-backward-word. Again, this can't be done if Backspace and C-h are
|
|
|
349 indistinguishable.
|
|
|
350
|
|
|
351 The user represents keys as a string of ASCII characters (when possible and
|
|
70
|
352 convenient), or as a vector of event objects, or as a vector of "key
|
|
|
353 description lists", that looks like (control a), or (control meta delete)
|
|
0
|
354 or (shift f1). The order of the modifier-names is not significant, so
|
|
|
355 (meta control x) and (control meta x) are the same.
|
|
|
356
|
|
|
357 `define-key' knows how to take any of the above representations and store them
|
|
|
358 into a keymap. When Emacs wants to return a key sequence (this-command-keys,
|
|
|
359 recent-keys, keyboard-macros, and read-key-sequence, for example) it returns
|
|
|
360 a vector of event objects. Keyboard macros can also be represented as ASCII
|
|
70
|
361 strings or as vectors of key description lists.
|
|
0
|
362
|
|
|
363 This is an incompatible change: code which calls `this-command-keys',
|
|
|
364 `recent-keys', `read-key-sequence', or manipulates keyboard-macros probably
|
|
|
365 needs to be changed so that it no longer assumes that the returned value is a
|
|
|
366 string.
|
|
|
367
|
|
|
368 Control-Shift-a is specified as (control A), not (control shift a), since A
|
|
|
369 is a two-case character. But for keys that don't have an upper case
|
|
|
370 version, like F1, Backspace, and Escape, you use the (shift backspace) syntax.
|
|
|
371
|
|
|
372 See the doc string for our version of define-key, reproduced below in the
|
|
|
373 `Changed Functions' section. Note that when the KEYS argument is a string,
|
|
|
374 it has the same semantics as the v18 define-key.
|
|
|
375
|
|
|
376
|
|
|
377 *** Xt Integration
|
|
|
378 ------------------
|
|
|
379
|
|
|
380 The heart of the event loop is implemented in terms of the Xt event functions
|
|
|
381 (specifically XtAppProcessEvent), and uses Xt's concept of timeouts and
|
|
|
382 file-descriptor callbacks, eliminating a large amount of system-dependent code
|
|
|
383 (Xt does it for you.)
|
|
|
384
|
|
|
385 If Emacs is compiled with support for X, it uses the Xt event loop even when
|
|
|
386 Emacs is not running on an X display (the Xt event loop supports this). This
|
|
|
387 makes it possible to run Emacs on a dumb TTY, and later connect it to one or
|
|
|
388 more X servers. It should also be possible to later connect an existing Emacs
|
|
|
389 process to additional TTY's, although this code is still experimental. (Our
|
|
|
390 intent at this point is not to have an Emacs that is being used by multiple
|
|
|
391 people at the same time: it is to make it possible for someone to go home, log
|
|
|
392 in on a dialup line, and connect to the same Emacs process that is running
|
|
|
393 under X in their office without having to recreate their buffer state and so
|
|
|
394 on.)
|
|
|
395
|
|
|
396 If Emacs is not compiled with support for X, then it instead uses more general
|
|
|
397 code, something like what v18 does; but this way of doing things is a lot more
|
|
|
398 modular.
|
|
|
399
|
|
|
400 (Linking Emacs with Xt seems to only add about 300k to the executable size,
|
|
|
401 compared with an Emacs linked with Xlib only.)
|
|
|
402
|
|
|
403
|
|
|
404 *** Region Highlighting
|
|
|
405 -----------------------
|
|
|
406
|
|
|
407 If the variable `zmacs-regions' is true, then the region between point and
|
|
|
408 mark will be highlighted when "active". Those commands which push a mark
|
|
|
409 (such as C-SPC, and C-x C-x) make the region become "active" and thus
|
|
|
410 highlighted. Most commands (all non-motion commands, basically) cause it to
|
|
|
411 become non-highlighted (non-"active"). Commands that operate on the region
|
|
|
412 (such as C-w, C-x C-l, etc.) only work if the region is in the highlighted
|
|
|
413 state.
|
|
|
414
|
|
|
415 zmacs-activate-region-hook and zmacs-deactivate-region-hook are run at the
|
|
|
416 appropriate times; under X, zmacs-activate-region-hook makes the X selection
|
|
|
417 be the region between point and mark, thus doing two things at once: making
|
|
|
418 the region and the X selection be the same; and making the region highlight
|
|
|
419 in the same way as the X selection.
|
|
|
420
|
|
|
421 If `zmacs-regions' is true, then the `mark-marker' command returns nil unless
|
|
|
422 the region is currently in the active (highlighted) state. With an argument
|
|
|
423 of t, this returns the mark (if there is one) regardless of the active-region
|
|
|
424 state. You should *generally* not use the mark unless the region is active,
|
|
|
425 if the user has expressed a preference for the active-region model. Watch
|
|
|
426 out! Moving this marker changes the mark position. If you set the marker not
|
|
|
427 to point anywhere, the buffer will have no mark.
|
|
|
428
|
|
|
429 In this way, the primary selection is a fairly transitory entity; but
|
|
|
430 when something is copied to the kill ring, it is made the Clipboard
|
|
|
431 selection. It is also stored into CUT_BUFFER0, for compatibility with
|
|
|
432 X applications that don't understand selections (like Emacs18).
|
|
|
433
|
|
|
434 Compatibility note: if you have code which uses (mark) or (mark-marker),
|
|
|
435 then you need to either: change those calls to (mark t) or (mark-marker t);
|
|
|
436 or simply bind `zmacs-regions' to nil around the call to mark or mark-marker.
|
|
|
437 This is probably the best solution, since it will work in Emacs 18 as well.
|
|
|
438
|
|
|
439
|
|
|
440 *** Menubars and Dialog Boxes
|
|
|
441 -----------------------------
|
|
|
442
|
|
|
443 Here is an example of a menubar definition:
|
|
|
444
|
|
|
445 (defvar default-menubar
|
|
|
446 '(("File" ["Open File..." find-file t]
|
|
|
447 ["Save Buffer" save-buffer t]
|
|
|
448 ["Save Buffer As..." write-file t]
|
|
|
449 ["Revert Buffer" revert-buffer t]
|
|
|
450 "-----"
|
|
|
451 ["Print Buffer" lpr-buffer t]
|
|
|
452 "-----"
|
|
|
453 ["Delete Frame" delete-frame t]
|
|
|
454 ["Kill Buffer..." kill-buffer t]
|
|
|
455 ["Exit Emacs" save-buffers-kill-emacs t]
|
|
|
456 )
|
|
|
457 ("Edit" ["Undo" advertised-undo t]
|
|
|
458 ["Cut" kill-primary-selection t]
|
|
|
459 ["Copy" copy-primary-selection t]
|
|
|
460 ["Paste" yank-clipboard-selection t]
|
|
|
461 ["Clear" delete-primary-selection t]
|
|
|
462 )
|
|
|
463 ...))
|
|
|
464
|
|
|
465 The first element of each menu item is the string to print on the menu.
|
|
|
466
|
|
|
467 The second element is the callback function; if it is a symbol, it is
|
|
|
468 invoked with `call-interactively.' If it is a list, it is invoked with
|
|
70
|
469 `eval'.
|
|
0
|
470
|
|
|
471 If the second element is a symbol, then the menu also displays the key that
|
|
|
472 is bound to that command (if any).
|
|
|
473
|
|
|
474 The third element of the menu items determines whether the item is selectable.
|
|
|
475 It may be t, nil, or a form to evaluate. Also, a hook is run just before a
|
|
70
|
476 menu is exposed, which can be used to change the value of these slots.
|
|
0
|
477 For example, there is a hook that makes the "undo" menu item be selectable
|
|
70
|
478 only in the cases when `advertised-undo' would not signal an error.
|
|
0
|
479
|
|
|
480 Menus may have other menus nested within them; they will cascade.
|
|
|
481
|
|
|
482 There are utility functions for adding items to menus, deleting items,
|
|
|
483 disabling them, etc.
|
|
|
484
|
|
70
|
485 The function `popup-menu' takes a menu description and pops it up.
|
|
|
486
|
|
|
487 The function `popup-dialog-box' takes a dialog-box description and pops
|
|
0
|
488 it up. Dialog box descriptions look a lot like menu descriptions.
|
|
|
489
|
|
70
|
490 The menubar, menu, and dialog-box code is implemented as a library,
|
|
|
491 with an interface which hides the toolkit that implements it.
|
|
0
|
492
|
|
|
493
|
|
|
494 *** Isearch Changes
|
|
|
495 -------------------
|
|
|
496
|
|
|
497 Isearch has been reimplemented in a different way, adding some new features,
|
|
|
498 and causing a few incompatible changes.
|
|
|
499
|
|
|
500 - the old isearch-*-char variables are no longer supported. In the old
|
|
|
501 system, one could make ^A mean "repeat the search" by doing something
|
|
70
|
502 like (setq search-repeat-char ?C-a). In the new system, this is
|
|
|
503 accomplished with
|
|
0
|
504
|
|
|
505 (define-key isearch-mode-map "\C-a" 'isearch-repeat-forward)
|
|
|
506
|
|
|
507 - The advantage of using the normal keymap mechanism for this is that you
|
|
|
508 can bind more than one key to an isearch command: for example, both C-a
|
|
|
509 and C-s could do the same thing inside isearch mode. You can also bind
|
|
|
510 multi-key sequences inside of isearch mode, and bind non-ASCII keys.
|
|
|
511 For example, to use the F1 key to terminate a search:
|
|
|
512
|
|
|
513 (define-key isearch-mode-map 'f1 'isearch-exit)
|
|
|
514
|
|
|
515 or to make ``C-c C-c'' terminate a search:
|
|
|
516
|
|
|
517 (define-key isearch-mode-map "\C-c\C-c" 'isearch-exit)
|
|
|
518
|
|
|
519 - If isearch is behaving case-insensitively (the default) and you type an
|
|
|
520 upper case character, then the search will become case-sensitive. This
|
|
|
521 can be disabled by setting `search-caps-disable-folding' to nil.
|
|
|
522
|
|
|
523 - There is a history ring of the strings previously searched for; typing
|
|
|
524 M-p or M-n while searching will cycle through this ring. Typing M-TAB
|
|
|
525 will do completion across the set of items in the history ring.
|
|
|
526
|
|
|
527 - The ESC key is no longer used to terminate an incremental search. The
|
|
|
528 RET key should be used instead. This change is necessary for it to be
|
|
|
529 possible to bind "meta" characters to isearch commands.
|
|
|
530
|
|
|
531
|
|
|
532 *** Startup Code Changes
|
|
|
533 ------------------------
|
|
|
534
|
|
|
535 The initial X frame is mapped before the user's .emacs file is executed.
|
|
|
536 Without this, there is no way for the user to see any error messages
|
|
|
537 generated by their .emacs file, any windows created by the .emacs file
|
|
|
538 don't show up, and the copyleft notice isn't shown.
|
|
|
539
|
|
|
540 The default values for load-path, exec-path, lock-directory, and
|
|
|
541 Info-directory-list are not (necessarily) built into Emacs, but are
|
|
70
|
542 computed at startup time.
|
|
0
|
543
|
|
|
544 First, Emacs looks at the directory in which its executable file resides:
|
|
|
545
|
|
|
546 o If that directory contains subdirectories named "lisp" and "lib-src",
|
|
|
547 then those directories are used as the lisp library and exec directory.
|
|
|
548
|
|
|
549 o If the parent of the directory in which the emacs executable is located
|
|
|
550 contains "lisp" and "lib-src" subdirectories, then those are used.
|
|
|
551
|
|
|
552 o If ../lib/xemacs-<version> (starting from the directory in which the
|
|
|
553 emacs executable is located) contains a "lisp" subdirectory and either
|
|
|
554 a "lib-src" subdirectory or a <configuration-name> subdirectory, then
|
|
|
555 those are used.
|
|
|
556
|
|
|
557 o If the emacs executable that was run is a symbolic link, then the link
|
|
|
558 is chased, and the resultant directory is checked as above.
|
|
|
559
|
|
|
560 (Actually, it doesn't just look for "lisp/", it looks for "lisp/prim/",
|
|
|
561 which reduces the chances of a false positive.)
|
|
|
562
|
|
|
563 If the lisp directory contains subdirectories, they are added to the default
|
|
|
564 load-path as well. If the site-lisp directory exists and contains
|
|
|
565 subdirectories, they are then added. Subdirectories whose names begin with
|
|
|
566 a dot or a hyphen are not added to the load-path.
|
|
|
567
|
|
|
568 These heuristics fail if the Emacs binary was copied from the main Emacs
|
|
|
569 tree to some other directory, and links for the lisp directory were not put
|
|
|
570 in. This isn't much of a restriction: either make there be subdirectories
|
|
|
571 (or symbolic links) of the directory of the emacs executable, or make the
|
|
|
572 "installed" emacs executable be a symbolic link to an executable in a more
|
|
|
573 appropriate directory structure. For example, this setup works:
|
|
|
574
|
|
|
575 /usr/local/xemacs/xemacs* ; The executable.
|
|
|
576 /usr/local/xemacs/lisp/ ; The associated directories.
|
|
|
577 /usr/local/xemacs/etc/ ; Any of the files in this list
|
|
|
578 /usr/local/xemacs/lock/ ; could be symbolic links as well.
|
|
|
579 /usr/local/xemacs/info/
|
|
|
580
|
|
|
581 As does this:
|
|
|
582
|
|
|
583 /usr/local/bin/xemacs -> ../xemacs/src/xemacs-19.14 ; A link...
|
|
|
584 /usr/local/xemacs/src/xemacs-19.14* ; The executable,
|
|
|
585 /usr/local/xemacs/lisp/ ; and the rest of
|
|
2
|
586 /usr/local/xemacs/etc/ ; the source tree
|
|
|
587 /usr/local/xemacs/lock/
|
|
0
|
588 /usr/local/xemacs/info/
|
|
|
589
|
|
|
590 This configuration might be used for a multi-architecture installation; assume
|
|
70
|
591 that $LOCAL refers to a directory which contains only files specific to a
|
|
|
592 particular architecture (i.e., executables) and $SHARED refers to those files
|
|
0
|
593 which are not machine specific (i.e., lisp code and documentation.)
|
|
|
594
|
|
|
595 $LOCAL/bin/xemacs@ -> $LOCAL/xemacs-19.14/xemacs*
|
|
|
596 $LOCAL/xemacs-19.14/lisp@ -> $SHARED/xemacs-19.14/lisp/
|
|
|
597 $LOCAL/xemacs-19.14/etc@ -> $SHARED/xemacs-19.14/etc/
|
|
|
598 $LOCAL/xemacs-19.14/info@ -> $SHARED/xemacs-19.14/info/
|
|
|
599
|
|
|
600 The following would also work, but the above is probably more attractive:
|
|
|
601
|
|
|
602 $LOCAL/bin/xemacs*
|
|
|
603 $LOCAL/bin/lisp@ -> $SHARED/xemacs-19.14/lisp/
|
|
|
604 $LOCAL/bin/etc@ -> $SHARED/xemacs-19.14/etc/
|
|
|
605 $LOCAL/bin/info@ -> $SHARED/xemacs-19.14/info/
|
|
|
606
|
|
|
607 If Emacs can't find the requisite directories, it writes a message like this
|
|
|
608 (or some appropriate subset of it) to stderr:
|
|
|
609
|
|
|
610 WARNING:
|
|
|
611 couldn't find an obvious default for load-path, exec-directory, and
|
|
|
612 lock-directory, and there were no defaults specified in paths.h when
|
|
|
613 Emacs was built. Perhaps some directories don't exist, or the Emacs
|
|
|
614 executable, /cadillac-th/jwz/somewhere/xemacs is in a strange place?
|
|
|
615
|
|
|
616 Without both exec-directory and load-path, Emacs will be very broken.
|
|
|
617 Consider making a symbolic link from /cadillac-th/jwz/somewhere/etc
|
|
|
618 to wherever the appropriate Emacs etc/ directory is, and from
|
|
|
619 /cadillac-th/jwz/somewhere/lisp/ to wherever the appropriate Emacs
|
|
|
620 lisp library is.
|
|
|
621
|
|
|
622 Without lock-directory set, file locking won't work. Consider
|
|
|
623 creating /cadillac-th/jwz/somewhere/lock as a directory or symbolic
|
|
|
624 link for use as the lock directory.
|
|
|
625
|
|
|
626 The default installation tree is the following:
|
|
|
627
|
|
|
628 /usr/local/bin/b2m ;
|
|
|
629 ctags ; executables that
|
|
|
630 emacsclient ; should be in
|
|
|
631 etags ; user's path
|
|
|
632 xemacs -> xemacs-<version> ;
|
|
|
633 xemacs ;
|
|
|
634 /usr/local/lib/xemacs/site-lisp
|
|
|
635 /usr/local/lib/xemacs/lock
|
|
|
636 /usr/local/lib/xemacs-<version>/etc ; architecture ind. files
|
|
|
637 /usr/local/lib/xemacs-<version>/info
|
|
|
638 /usr/local/lib/xemacs-<version>/lisp
|
|
|
639 /usr/local/lib/xemacs-<version>/<configuration> ; binaries emacs may run
|
|
|
640
|
|
|
641
|
|
|
642 *** X Resources
|
|
|
643 ---------------
|
|
|
644
|
|
|
645 (Note: This section is copied verbatim from the XEmacs Reference Manual.)
|
|
|
646
|
|
|
647 The Emacs resources are generally set per-frame. Each Emacs frame
|
|
|
648 can have its own name or the same name as another, depending on the
|
|
|
649 name passed to the `make-frame' function.
|
|
|
650
|
|
|
651 You can specify resources for all frames with the syntax:
|
|
|
652
|
|
|
653 Emacs*parameter: value
|
|
|
654
|
|
|
655 or
|
|
|
656
|
|
|
657 Emacs*EmacsFrame.parameter:value
|
|
|
658
|
|
|
659 You can specify resources for a particular frame with the syntax:
|
|
|
660
|
|
|
661 Emacs*FRAME-NAME.parameter: value
|
|
|
662
|
|
|
663
|
|
|
664 **** Geometry Resources
|
|
|
665 -----------------------
|
|
|
666
|
|
|
667 To make the default size of all Emacs frames be 80 columns by 55
|
|
|
668 lines, do this:
|
|
|
669
|
|
|
670 Emacs*EmacsFrame.geometry: 80x55
|
|
|
671
|
|
|
672 To set the geometry of a particular frame named `fred', do this:
|
|
|
673
|
|
|
674 Emacs*fred.geometry: 80x55
|
|
|
675
|
|
|
676 Important! Do not use the following syntax:
|
|
|
677
|
|
|
678 Emacs*geometry: 80x55
|
|
|
679
|
|
|
680 You should never use `*geometry' with any X application. It does not
|
|
|
681 say "make the geometry of Emacs be 80 columns by 55 lines." It really
|
|
|
682 says, "make Emacs and all subwindows thereof be 80x55 in whatever units
|
|
|
683 they care to measure in." In particular, that is both telling the
|
|
|
684 Emacs text pane to be 80x55 in characters, and telling the menubar pane
|
|
|
685 to be 80x55 pixels, which is surely not what you want.
|
|
|
686
|
|
|
687 As a special case, this geometry specification also works (and sets
|
|
|
688 the default size of all Emacs frames to 80 columns by 55 lines):
|
|
|
689
|
|
|
690 Emacs.geometry: 80x55
|
|
|
691
|
|
|
692 since that is the syntax used with most other applications (since most
|
|
|
693 other applications have only one top-level window, unlike Emacs). In
|
|
|
694 general, however, the top-level shell (the unmapped ApplicationShell
|
|
|
695 widget named `Emacs' that is the parent of the shell widgets that
|
|
|
696 actually manage the individual frames) does not have any interesting
|
|
|
697 resources on it, and you should set the resources on the frames instead.
|
|
|
698
|
|
|
699 The `-geometry' command-line argument sets only the geometry of the
|
|
|
700 initial frame created by Emacs.
|
|
|
701
|
|
|
702 A more complete explanation of geometry-handling is
|
|
|
703
|
|
|
704 * The `-geometry' command-line option sets the `Emacs.geometry'
|
|
|
705 resource, that is, the geometry of the ApplicationShell.
|
|
|
706
|
|
|
707 * For the first frame created, the size of the frame is taken from
|
|
|
708 the ApplicationShell if it is specified, otherwise from the
|
|
|
709 geometry of the frame.
|
|
|
710
|
|
|
711 * For subsequent frames, the order is reversed: First the frame, and
|
|
|
712 then the ApplicationShell.
|
|
|
713
|
|
|
714 * For the first frame created, the position of the frame is taken
|
|
|
715 from the ApplicationShell (`Emacs.geometry') if it is specified,
|
|
|
716 otherwise from the geometry of the frame.
|
|
|
717
|
|
|
718 * For subsequent frames, the position is taken only from the frame,
|
|
|
719 and never from the ApplicationShell.
|
|
|
720
|
|
|
721 This is rather complicated, but it does seem to provide the most
|
|
|
722 intuitive behavior with respect to the default sizes and positions of
|
|
|
723 frames created in various ways.
|
|
|
724
|
|
|
725
|
|
|
726 **** Iconic Resources
|
|
|
727 ---------------------
|
|
|
728
|
|
|
729 Analogous to `-geometry', the `-iconic' command-line option sets the
|
|
|
730 iconic flag of the ApplicationShell (`Emacs.iconic') and always applies
|
|
|
731 to the first frame created regardless of its name. However, it is
|
|
|
732 possible to set the iconic flag on particular frames (by name) by using
|
|
|
733 the `Emacs*FRAME-NAME.iconic' resource.
|
|
|
734
|
|
|
735
|
|
|
736 **** Resource List
|
|
|
737 ------------------
|
|
|
738
|
|
|
739 Emacs frames accept the following resources:
|
|
|
740
|
|
|
741 `geometry' (class `Geometry'): string
|
|
|
742 Initial geometry for the frame. *Note Geometry Resources:: for a
|
|
|
743 complete discussion of how this works.
|
|
|
744
|
|
|
745 `iconic' (class `Iconic'): boolean
|
|
|
746 Whether this frame should appear in the iconified state.
|
|
|
747
|
|
|
748 `internalBorderWidth' (class `InternalBorderWidth'): int
|
|
|
749 How many blank pixels to leave between the text and the edge of the
|
|
|
750 window.
|
|
|
751
|
|
|
752 `interline' (class `Interline'): int
|
|
|
753 How many pixels to leave between each line (may not be
|
|
|
754 implemented).
|
|
|
755
|
|
|
756 `menubar' (class `Menubar'): boolean
|
|
|
757 Whether newly-created frames should initially have a menubar. Set
|
|
|
758 to true by default.
|
|
|
759
|
|
|
760 `initiallyUnmapped' (class `InitiallyUnmapped'): boolean
|
|
|
761 Whether XEmacs should leave the initial frame unmapped when it
|
|
|
762 starts up. This is useful if you are starting XEmacs as a server
|
|
|
763 (e.g. in conjunction with gnuserv or the external client widget).
|
|
|
764 You can also control this with the `-unmapped' command-line option.
|
|
|
765
|
|
|
766 `barCursor' (class `BarColor'): boolean
|
|
|
767 Whether the cursor should be displayed as a bar, or the
|
|
|
768 traditional box.
|
|
|
769
|
|
|
770 `textPointer' (class `Cursor'): cursor-name
|
|
|
771 The cursor to use when the mouse is over text. This resource is
|
|
|
772 used to initialize the variable `x-pointer-shape'.
|
|
|
773
|
|
|
774 `selectionPointer' (class `Cursor'): cursor-name
|
|
|
775 The cursor to use when the mouse is over a selectable text region
|
|
|
776 (an extent with the `highlight' property; for example, an Info
|
|
|
777 cross-reference). This resource is used to initialize the variable
|
|
|
778 `x-selection-pointer-shape'.
|
|
|
779
|
|
|
780 `spacePointer' (class `Cursor'): cursor-name
|
|
|
781 The cursor to use when the mouse is over a blank space in a buffer
|
|
|
782 (that is, after the end of a line or after the end-of-file). This
|
|
|
783 resource is used to initialize the variable
|
|
|
784 `x-nontext-pointer-shape'.
|
|
|
785
|
|
|
786 `modeLinePointer' (class `Cursor'): cursor-name
|
|
|
787 The cursor to use when the mouse is over a mode line. This
|
|
|
788 resource is used to initialize the variable `x-mode-pointer-shape'.
|
|
|
789
|
|
|
790 `gcPointer' (class `Cursor'): cursor-name
|
|
|
791 The cursor to display when a garbage-collection is in progress.
|
|
|
792 This resource is used to initialize the variable
|
|
|
793 `x-gc-pointer-shape'.
|
|
|
794
|
|
|
795 `scrollbarPointer' (class `Cursor'): cursor-name
|
|
|
796 The cursor to use when the mouse is over the scrollbar. This
|
|
|
797 resource is used to initialize the variable
|
|
|
798 `x-scrollbar-pointer-shape'.
|
|
|
799
|
|
|
800 `pointerColor' (class `Foreground'): color-name
|
|
|
801 `pointerBackground' (class `Background'): color-name
|
|
|
802 The foreground and background colors of the mouse cursor. These
|
|
|
803 resources are used to initialize the variables
|
|
|
804 `x-pointer-foreground-color' and `x-pointer-background-color'.
|
|
|
805
|
|
|
806 `scrollBarWidth' (class `ScrollBarWidth'): integer
|
|
|
807 How wide the vertical scrollbars should be, in pixels; 0 means no
|
|
|
808 vertical scrollbars. You can also use a resource specification of
|
|
|
809 the form `*scrollbar.width', or the usual toolkit scrollbar
|
|
|
810 resources: `*XmScrollBar.width' (Motif), `*XlwScrollBar.width'
|
|
|
811 (Lucid), or `*Scrollbar.thickness' (Athena). We don't recommend
|
|
|
812 that you use the toolkit resources, though, because they're
|
|
|
813 dependent on how exactly your particular build of XEmacs was
|
|
|
814 configured.
|
|
|
815
|
|
|
816 `scrollBarHeight' (class `ScrollBarHeight'): integer
|
|
|
817 How high the horizontal scrollbars should be, in pixels; 0 means no
|
|
|
818 horizontal scrollbars. You can also use a resource specification
|
|
|
819 of the form `*scrollbar.height', or the usual toolkit scrollbar
|
|
|
820 resources: `*XmScrollBar.height' (Motif), `*XlwScrollBar.height'
|
|
|
821 (Lucid), or `*Scrollbar.thickness' (Athena). We don't recommend
|
|
|
822 that you use the toolkit resources, though, because they're
|
|
|
823 dependent on how exactly your particular build of XEmacs was
|
|
|
824 configured.
|
|
|
825
|
|
|
826 `scrollBarPlacement' (class `ScrollBarPlacement'): string
|
|
|
827 Where the horizontal and vertical scrollbars should be positioned.
|
|
|
828 This should be one of the four strings `bottom-left',
|
|
|
829 `bottom-right', `top-left', and `top-right'. Default is
|
|
|
830 `bottom-right' for the Motif and Lucid scrollbars and
|
|
|
831 `bottom-left' for the Athena scrollbars.
|
|
|
832
|
|
|
833 `topToolBarHeight' (class `TopToolBarHeight'): integer
|
|
|
834 `bottomToolBarHeight' (class `BottomToolBarHeight'): integer
|
|
|
835 `leftToolBarWidth' (class `LeftToolBarWidth'): integer
|
|
|
836 `rightToolBarWidth' (class `RightToolBarWidth'): integer
|
|
|
837 Height and width of the four possible toolbars.
|
|
|
838
|
|
|
839 `topToolBarShadowColor' (class `TopToolBarShadowColor'): color-name
|
|
|
840 `bottomToolBarShadowColor' (class `BottomToolBarShadowColor'): color-name
|
|
|
841 Color of the top and bottom shadows for the toolbars. NOTE: These
|
|
|
842 resources do *not* have anything to do with the top and bottom
|
|
|
843 toolbars (i.e. the toolbars at the top and bottom of the frame)!
|
|
|
844 Rather, they affect the top and bottom shadows around the edges of
|
|
|
845 all four kinds of toolbars.
|
|
|
846
|
|
|
847 `topToolBarShadowPixmap' (class `TopToolBarShadowPixmap'): pixmap-name
|
|
|
848 `bottomToolBarShadowPixmap' (class `BottomToolBarShadowPixmap'): pixmap-name
|
|
|
849 Pixmap of the top and bottom shadows for the toolbars. If set,
|
|
|
850 these resources override the corresponding color resources. NOTE:
|
|
|
851 These resources do *not* have anything to do with the top and
|
|
|
852 bottom toolbars (i.e. the toolbars at the top and bottom of the
|
|
|
853 frame)! Rather, they affect the top and bottom shadows around the
|
|
|
854 edges of all four kinds of toolbars.
|
|
|
855
|
|
|
856 `toolBarShadowThickness' (class `ToolBarShadowThickness'): integer
|
|
|
857 Thickness of the shadows around the toolbars, in pixels.
|
|
|
858
|
|
|
859 `visualBell' (class `VisualBell'): boolean
|
|
|
860 Whether XEmacs should flash the screen rather than making an
|
|
|
861 audible beep.
|
|
|
862
|
|
|
863 `bellVolume' (class `BellVolume'): integer
|
|
|
864 Volume of the audible beep.
|
|
|
865
|
|
|
866 `useBackingStore' (class `UseBackingStore'): boolean
|
|
|
867 Whether XEmacs should set the backing-store attribute of the X
|
|
|
868 windows it creates. This increases the memory usage of the X
|
|
|
869 server but decreases the amount of X traffic necessary to update
|
|
|
870 the screen, and is useful when the connection to the X server goes
|
|
|
871 over a low-bandwidth line such as a modem connection.
|
|
|
872
|
|
|
873
|
|
|
874 **** Face Resources
|
|
|
875 -------------------
|
|
|
876
|
|
|
877 The attributes of faces are also per-frame. They can be specified as:
|
|
|
878
|
|
|
879 Emacs.FACE_NAME.parameter: value
|
|
|
880
|
|
|
881 (*do not* use `Emacs*FACE_NAME...')
|
|
|
882
|
|
|
883 or
|
|
|
884
|
|
|
885 Emacs*FRAME_NAME.FACE_NAME.parameter: value
|
|
|
886
|
|
|
887 Faces accept the following resources:
|
|
|
888
|
|
|
889 `attributeFont' (class `AttributeFont'): font-name
|
|
|
890 The font of this face.
|
|
|
891
|
|
|
892 `attributeForeground' (class `AttributeForeground'): color-name
|
|
|
893 `attributeBackground' (class `AttributeBackground'): color-name
|
|
|
894 The foreground and background colors of this face.
|
|
|
895
|
|
|
896 `attributeBackgroundPixmap' (class `AttributeBackgroundPixmap'): file-name
|
|
|
897 The name of an XBM file (or XPM file, if your version of Emacs
|
|
|
898 supports XPM), to use as a background stipple.
|
|
|
899
|
|
|
900 `attributeUnderline' (class `AttributeUnderline'): boolean
|
|
|
901 Whether text in this face should be underlined.
|
|
|
902
|
|
|
903 All text is displayed in some face, defaulting to the face named
|
|
|
904 `default'. To set the font of normal text, use
|
|
|
905 `Emacs*default.attributeFont'. To set it in the frame named `fred', use
|
|
|
906 `Emacs*fred.default.attributeFont'.
|
|
|
907
|
|
|
908 These are the names of the predefined faces:
|
|
|
909
|
|
|
910 `default'
|
|
|
911 Everything inherits from this.
|
|
|
912
|
|
|
913 `bold'
|
|
|
914 If this is not specified in the resource database, Emacs tries to
|
|
|
915 find a bold version of the font of the default face.
|
|
|
916
|
|
|
917 `italic'
|
|
|
918 If this is not specified in the resource database, Emacs tries to
|
|
|
919 find an italic version of the font of the default face.
|
|
|
920
|
|
|
921 `bold-italic'
|
|
|
922 If this is not specified in the resource database, Emacs tries to
|
|
|
923 find a bold-italic version of the font of the default face.
|
|
|
924
|
|
|
925 `modeline'
|
|
|
926 This is the face that the modeline is displayed in. If not
|
|
|
927 specified in the resource database, it is determined from the
|
|
|
928 default face by reversing the foreground and background colors.
|
|
|
929
|
|
|
930 `highlight'
|
|
|
931 This is the face that highlighted extents (for example, Info
|
|
|
932 cross-references and possible completions, when the mouse passes
|
|
|
933 over them) are displayed in.
|
|
|
934
|
|
|
935 `left-margin'
|
|
|
936 `right-margin'
|
|
|
937 These are the faces that the left and right annotation margins are
|
|
|
938 displayed in.
|
|
|
939
|
|
2
|
940 `zmacs-region'
|
|
0
|
941 This is the face that mouse selections are displayed in.
|
|
|
942
|
|
|
943 `text-cursor'
|
|
|
944 This is the face that the cursor is displayed in.
|
|
|
945
|
|
|
946 `isearch'
|
|
|
947 This is the face that the matched text being searched for is
|
|
|
948 displayed in.
|
|
|
949
|
|
|
950 `info-node'
|
|
|
951 This is the face of info menu items. If unspecified, it is copied
|
|
|
952 from `bold-italic'.
|
|
|
953
|
|
|
954 `info-xref'
|
|
|
955 This is the face of info cross-references. If unspecified, it is
|
|
|
956 copied from `bold'. (Note that, when the mouse passes over a
|
|
|
957 cross-reference, the cross-reference's face is determined from a
|
|
|
958 combination of the `info-xref' and `highlight' faces.)
|
|
|
959
|
|
|
960 Other packages might define their own faces; to see a list of all
|
|
|
961 faces, use any of the interactive face-manipulation commands such as
|
|
|
962 `set-face-font' and type `?' when you are prompted for the name of a
|
|
|
963 face.
|
|
|
964
|
|
|
965 If the `bold', `italic', and `bold-italic' faces are not specified
|
|
|
966 in the resource database, then XEmacs attempts to derive them from the
|
|
|
967 font of the default face. It can only succeed at this if you have
|
|
|
968 specified the default font using the XLFD (X Logical Font Description)
|
|
|
969 format, which looks like
|
|
|
970
|
|
|
971 *-courier-medium-r-*-*-*-120-*-*-*-*-*-*
|
|
|
972
|
|
|
973 If you use any of the other, less strict font name formats, some of
|
|
|
974 which look like
|
|
|
975
|
|
|
976 lucidasanstypewriter-12
|
|
|
977 fixed
|
|
|
978 9x13
|
|
|
979
|
|
|
980 then XEmacs won't be able to guess the names of the bold and italic
|
|
|
981 versions. All X fonts can be referred to via XLFD-style names, so you
|
|
|
982 should use those forms. See the man pages for `X(1)', `xlsfonts(1)',
|
|
|
983 and `xfontsel(1)'.
|
|
|
984
|
|
|
985
|
|
|
986 **** Widgets
|
|
|
987 ------------
|
|
|
988
|
|
|
989 There are several structural widgets between the terminal EmacsFrame
|
|
|
990 widget and the top level ApplicationShell; the exact names and types of
|
|
|
991 these widgets change from release to release (for example, they changed
|
|
|
992 in 19.9, 19.10, 19.12, and 19.13) and are subject to further change in
|
|
|
993 the future, so you should avoid mentioning them in your resource database.
|
|
|
994 The above-mentioned syntaxes should be forward-compatible. As of 19.14,
|
|
|
995 the exact widget hierarchy is as follows:
|
|
|
996
|
|
|
997 INVOCATION-NAME "shell" "container" FRAME-NAME
|
|
|
998 x-emacs-application-class "TopLevelEmacsShell" "EmacsManager" "EmacsFrame"
|
|
|
999
|
|
|
1000 (for normal frames)
|
|
|
1001
|
|
|
1002 or
|
|
|
1003
|
|
|
1004 INVOCATION-NAME "shell" "container" FRAME-NAME
|
|
|
1005 x-emacs-application-class "TransientEmacsShell" "EmacsManager" "EmacsFrame"
|
|
|
1006
|
|
|
1007 (for popup/dialog-box frames)
|
|
|
1008
|
|
|
1009 where INVOCATION-NAME is the terminal component of the name of the
|
|
|
1010 XEmacs executable (usually `xemacs'), and `x-emacs-application-class'
|
|
|
1011 is generally `Emacs'.
|
|
|
1012
|
|
|
1013
|
|
|
1014 **** Menubar Resources
|
|
|
1015 ----------------------
|
|
|
1016
|
|
|
1017 As the menubar is implemented as a widget which is not a part of
|
|
|
1018 XEmacs proper, it does not use the face mechanism for specifying fonts
|
|
|
1019 and colors: It uses whatever resources are appropriate to the type of
|
|
|
1020 widget which is used to implement it.
|
|
|
1021
|
|
|
1022 If Emacs was compiled to use only the Motif-lookalike menu widgets,
|
|
|
1023 then one way to specify the font of the menubar would be
|
|
|
1024
|
|
|
1025 Emacs*menubar*font: *-courier-medium-r-*-*-*-120-*-*-*-*-*-*
|
|
|
1026
|
|
|
1027 If the Motif library is being used, then one would have to use
|
|
|
1028
|
|
|
1029 Emacs*menubar*fontList: *-courier-medium-r-*-*-*-120-*-*-*-*-*-*
|
|
|
1030
|
|
|
1031 because the Motif library uses the `fontList' resource name instead
|
|
|
1032 of `font', which has subtly different semantics.
|
|
|
1033
|
|
|
1034 The same is true of the scrollbars: They accept whichever resources
|
|
|
1035 are appropriate for the toolkit in use.
|
|
|
1036
|
|
|
1037
|
|
|
1038 *** Source Code Highlighting
|
|
|
1039 ----------------------------
|
|
|
1040
|
|
|
1041 It's possible to have your buffers "decorated" with fonts or colors
|
|
|
1042 indicating syntactic structures (such as strings, comments, function names,
|
|
|
1043 "reserved words", etc.). In XEmacs, the preferred way to do this is with
|
|
|
1044 font-lock-mode; activate it by adding the following code to your .emacs file:
|
|
|
1045
|
|
|
1046 (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
|
|
|
1047 (add-hook 'c-mode-hook 'turn-on-font-lock)
|
|
|
1048 (add-hook 'c++-mode-hook 'turn-on-font-lock)
|
|
|
1049 (add-hook 'dired-mode-hook 'turn-on-font-lock)
|
|
|
1050 ...etc...
|
|
|
1051
|
|
|
1052 To customize it, see the descriptions of the function `font-lock-mode' and
|
|
|
1053 the variables `font-lock-keywords', `c-font-lock-keywords', etc.
|
|
|
1054
|
|
|
1055 There exist several other source code highlighting packages, but font-lock
|
|
2
|
1056 does one thing that most others don't do: highlights as you type new text;
|
|
|
1057 and one thing that no others do: bases part of its decoration on the
|
|
0
|
1058 syntax table of the major mode. Font-lock has C-level support to do this
|
|
|
1059 efficiently, so it should also be significantly faster than the others.
|
|
|
1060
|
|
|
1061 If there's something that another highlighting package does that you can't
|
|
|
1062 make font-lock do, let us know. We would prefer to consolidate all of the
|
|
|
1063 desired functionality into one package rather than ship several different
|
|
|
1064 packages which do essentially the same thing in different ways.
|
|
|
1065
|
|
|
1066
|
|
|
1067 ** Differences Between XEmacs and Emacs 18
|
|
|
1068 ==========================================
|
|
|
1069
|
|
|
1070 Auto-configure support has been added, so it should be fairly easy to compile
|
|
|
1071 XEmacs on different systems. If you have any problems or feedback about
|
|
|
1072 compiling on your system, please let us know.
|
|
|
1073
|
|
|
1074 We have reimplemented the basic input model in a more general way; instead of
|
|
|
1075 X input being a special-case of the normal ASCII input stream, XEmacs has a
|
|
|
1076 concept of "input events", and ASCII characters are a subset of that. The
|
|
|
1077 events that XEmacs knows about are not X events, but are a generalization of
|
|
|
1078 them, so that XEmacs can eventually be ported to different window systems.
|
|
|
1079
|
|
|
1080 We have reimplemented keymaps so that sequences of events can be stored into
|
|
|
1081 them instead of just ASCII codes; it is possible to, for example, bind
|
|
|
1082 different commands to each of the chords Control-h, Control-H, Backspace,
|
|
|
1083 Control-Backspace, and Super-Shift-Backspace. Key bindings, function key
|
|
|
1084 bindings, and mouse bindings live in the same keymaps.
|
|
|
1085
|
|
|
1086 Input and display of all ISO-8859-1 characters is supported.
|
|
|
1087
|
|
|
1088 You can have multiple X windows ("frames" in XEmacs terminology).
|
|
|
1089
|
|
|
1090 XEmacs has objects called "extents" and "faces", which are roughly
|
|
|
1091 analogous to Epoch's "buttons," "zones," and "styles." An extent is a
|
|
|
1092 region of text (a start position and an end position) and a face is a
|
|
|
1093 collection of textual attributes like fonts and colors. Every extent
|
|
|
1094 is displayed in some "face", so changing the properties of a face
|
|
|
1095 immediately updates the display of all associated extents. Faces can
|
|
|
1096 be frame-local: you can have a region of text which displays with
|
|
|
1097 completely different attributes when its buffer is viewed from a
|
|
|
1098 different X window.
|
|
|
1099
|
|
|
1100 The display attributes of faces may be specified either in lisp or through
|
|
|
1101 the X resource manager.
|
|
|
1102
|
|
|
1103 Pixmaps of arbitrary size can be embedded in a buffer.
|
|
|
1104
|
|
|
1105 Variable width fonts work.
|
|
|
1106
|
|
|
1107 The height of a line is the height of the tallest font on that line, instead
|
|
|
1108 of all lines having the same height.
|
|
|
1109
|
|
|
1110 XEmacs uses the MIT "Xt" toolkit instead of raw Xlib calls, which
|
|
|
1111 makes it be a more well-behaved X citizen (and also improves
|
|
|
1112 portability). A result of this is that it is possible to include
|
|
|
1113 other Xt "Widgets" in the XEmacs window. Also, XEmacs understands the
|
|
|
1114 standard Xt command-line arguments.
|
|
|
1115
|
|
|
1116 XEmacs understands the X11 "Selection" mechanism; it's possible to define
|
|
70
|
1117 and customize selection converter functions and new selection types from
|
|
0
|
1118 Emacs Lisp, without having to recompile XEmacs.
|
|
|
1119
|
|
|
1120 XEmacs provides support for ToolTalk on systems that have it.
|
|
|
1121
|
|
|
1122 XEmacs supports the Zmacs/Lispm style of region highlighting, where the
|
|
|
1123 region between the point and mark is highlighted when in its "active" state.
|
|
|
1124
|
|
|
1125 XEmacs has a menubar, whose contents are customizable from emacs-lisp.
|
|
|
1126 This menubar looks Motif-ish, but does not require Motif. If you already
|
|
|
1127 own Motif, however, you can configure XEmacs to use a *real* Motif menubar
|
|
|
1128 instead.
|
|
|
1129
|
|
|
1130 XEmacs can ask questions using popup dialog boxes. Any command executed from
|
|
|
1131 a menu will ask yes/no questions with dialog boxes, while commands executed
|
|
|
1132 via the keyboard will use the minibuffer.
|
|
|
1133
|
|
|
1134 XEmacs has vertical and horizontal scrollbars.
|
|
|
1135
|
|
|
1136 The initial load-path is computed at run-time, instead of at compile-time.
|
|
|
1137 This means that if you move the XEmacs executable and associated directories
|
|
|
1138 to somewhere else, you don't have to recompile anything.
|
|
|
1139
|
|
|
1140 You can specify what the title of the XEmacs windows and icons should be
|
|
|
1141 with the variables `frame-title-format' and `frame-icon-title-format',
|
|
|
1142 which have the same syntax as `mode-line-format'.
|
|
|
1143
|
|
|
1144 XEmacs now supports floating-point numbers.
|
|
|
1145
|
|
|
1146 XEmacs now knows about timers directly, instead of them being simulated by
|
|
|
1147 a subprocess.
|
|
|
1148
|
|
|
1149 XEmacs understands truenames, and can be configured to notice when you are
|
|
|
1150 visiting two names of the same file. See the variables find-file-use-truenames
|
|
|
1151 and find-file-compare-truenames.
|
|
|
1152
|
|
70
|
1153 If you're running on a machine with audio hardware, you can specify sound
|
|
0
|
1154 files for XEmacs to play instead of the default X beep. See the documentation
|
|
|
1155 of the function load-sound-file and the variable sound-alist.
|
|
|
1156
|
|
|
1157 An XEmacs frame can be placed within an "external client widget" managed by
|
|
|
1158 another application. This allows an application to use an XEmacs frame as its
|
|
|
1159 text pane rather than the standard Text widget that is provided with Motif or
|
|
|
1160 Athena. XEmacs supports Motif applications, generic Xt (e.g. Athena)
|
|
|
1161 applications, and raw Xlib applications.
|
|
|
1162
|
|
|
1163 Random changes to the emacs-lisp library: (some of this was not written by
|
|
|
1164 us, but is included because it's free software and we think it's good stuff)
|
|
|
1165
|
|
|
1166 - there is a new optimizing byte-compiler
|
|
|
1167 - there is a new abbrev-based mail-alias mechanism
|
|
|
1168 - the -*- line can contain local-variable settings
|
|
|
1169 - there is a new TAGS package
|
|
|
1170 - there is a new VI-emulation mode (viper)
|
|
|
1171 - there is a new implementation of Dired
|
|
|
1172 - there is a new implementation of Isearch
|
|
|
1173 - the VM package for reading mail is provided
|
|
|
1174 - the W3 package for browsing the World Wide Web hypertext information
|
|
|
1175 system is provided
|
|
|
1176 - the Hyperbole package, a programmable information management and
|
|
|
1177 hypertext system
|
|
|
1178 - the OO-Browser package, a multi-language object-oriented browser
|
|
|
1179
|
|
|
1180 There are many more specifics in the "Miscellaneous Changes" section, below.
|
|
|
1181
|
|
|
1182 The online Emacs Manual and Emacs-Lisp Manual are now both relatively
|
|
|
1183 up-to-date.
|
|
|
1184
|
|
70
|
1185 * XEmacs Release Notes
|
|
|
1186 ======================
|
|
|
1187
|
|
|
1188 ** Future Plans for XEmacs
|
|
|
1189 ==========================
|
|
|
1190
|
|
|
1191 For the curious, the biggest changes in 19.15 will include integration
|
|
|
1192 of TM (a MIME package for VM and GNUS), EFS (the next generation of
|
|
|
1193 ange-ftp), and Auc-TeX, and a "lite" distribution that includes a
|
|
|
1194 minimal base and a set of optional packages (which will include TM,
|
|
|
1195 EFS, and Auc-TeX, as well as all of the large packages currently
|
|
|
1196 distributed with XEmacs). There will also still be a full distribution
|
|
|
1197 that includes all the optional packages.
|
|
|
1198
|
|
88
|
1199 We are working on improving the Mule support in future releases:
|
|
|
1200
|
|
|
1201 -- Other input methods, such as wnn, will be supported.
|
|
|
1202
|
|
|
1203 -- More user-level documentation on using Mule.
|
|
|
1204
|
|
|
1205 ** Major Differences Between 19.14 and 20.0
|
|
|
1206
|
|
|
1207 XEmacs 20.0 is the first public release to have support for MULE
|
|
|
1208 (Multi-Lingual Emacs). The --with-mule configuration flag must be
|
|
|
1209 used to enable Mule support.
|
|
|
1210
|
|
|
1211 Many bugs have been fixed. An effort has been made to eradicate all
|
|
|
1212 XEmacs crashes, although we are not quite done yet. The overall
|
|
|
1213 quality of XEmacs should be higher than any previous release. XEmacs
|
|
|
1214 now compiles with nary a warning with some compilers.
|
|
|
1215
|
|
|
1216 -- Multiple character sets can be displayed in a buffer. The file
|
|
|
1217 mule-doc/demo in the distribution contains a greeting in many
|
|
|
1218 different languages.
|
|
|
1219
|
|
|
1220 -- Although the Mule work is for all languages, particular effort has
|
|
|
1221 been invested in Japanese, with particular focus on Japanese users
|
|
|
1222 of Sun WorkShop. Many menubar labels have been translated into
|
|
90
|
1223 Japanese. Martin Buchholz, the maintainer of MULE features within
|
|
|
1224 XEmacs normaly runs XEmacs in a Japanese language environment.
|
|
|
1225 Some of the other contributors are Japanese, most importantly
|
|
|
1226 Morioka Tomohiko, author of the TM package, providing MIME support
|
|
|
1227 for Mail and News.
|
|
88
|
1228
|
|
|
1229 -- Input for complex Asian languages is supported via XIM, a mechanism
|
|
|
1230 introduced in X11R5 to allow applications to get localized input
|
|
|
1231 without knowledge of the language. The way XIM works is that when
|
|
|
1232 the locale has a complex character set, such as Japanese, and extra
|
|
|
1233 minibuffer-like status window appears attached to various
|
|
|
1234 application windows, and indicates the status of the input method.
|
|
|
1235 Composed input in XEmacs should work the same as with other
|
|
|
1236 applications. If Motif and Mule support is configured into XEmacs,
|
|
|
1237 then XIM support is automatically configured in as well.
|
|
|
1238
|
|
|
1239 -- TM (Tools for Mime) now comes with XEmacs. This provides MIME
|
|
|
1240 (Multi-purpose Internet Multi-media Extensions?) support for Mail
|
|
|
1241 and News. The primary author is Morioka Tomohiko.
|
|
|
1242
|
|
|
1243 -- Japanese input can also be input using the `canna' input method.
|
|
|
1244 This support was contributed by Morioka Tomohiko. Setting up canna
|
|
|
1245 usually requires more user effort (and better knowledge of Japanese!)
|
|
|
1246 than XIM, but provides a better-integrated input method.
|
|
|
1247
|
|
|
1248 -- A mini-tutorial on using Mule:
|
|
|
1249
|
|
|
1250 -- Every time data passes between XEmacs and the rest of the
|
|
|
1251 environment, via file or process input or output, XEmacs must
|
|
|
1252 convert between its internal multi-character representation and
|
|
|
1253 the external representation (`coding system'). Many
|
|
|
1254 difficulties with Mule are related to controlling these coding
|
|
|
1255 system conversions.
|
|
|
1256
|
|
|
1257 -- file-coding-system, file-coding-system-for-read,
|
|
|
1258 overriding-file-coding-system, and file-coding-system-alist
|
|
|
1259 are used to determine the coding systems used on file input
|
|
|
1260 and output.
|
|
|
1261
|
|
|
1262 -- For each process, (set-process-input-coding-system) and
|
|
|
1263 (set-process-output-coding-system) determine the coding
|
|
|
1264 system used for I/O from the process.
|
|
|
1265
|
|
|
1266 -- Many other things are encoded using pathname-coding-system:
|
|
|
1267 -- file and directory names
|
|
|
1268 -- window manager properties: window title, icon name
|
|
|
1269 -- process names and process arguments
|
|
|
1270 -- XIM input.
|
|
|
1271
|
|
|
1272 -- In many cases, you will want to have the same values for all
|
|
|
1273 the above variables in many cases. For example, in a
|
|
|
1274 Japanese environment, you will want to use the 'euc-japan
|
|
|
1275 coding system consistently, except when running certain
|
|
|
1276 processes that do byte-oriented, rather than
|
|
|
1277 character-oriented I/O, such as gzip, or when processing Mail
|
|
|
1278 or News, where ISO2022-based coding systems are the norm,
|
|
|
1279 since they support multiple character sets.
|
|
|
1280
|
|
|
1281 -- To add support for a new language or character set, start by
|
|
|
1282 trying to copy code in japanese-hooks.el.
|
|
|
1283
|
|
|
1284 -- The traditional pre-Mule data conversion is equivalent to the
|
|
|
1285 'binary coding system under Mule. In this case all characters
|
|
|
1286 are treated as iso8859-1 (i.e. characters for English + Western
|
|
|
1287 European languages).
|
|
|
1288
|
|
|
1289 -- many fileio-related commands such as find-file and write-file
|
|
|
1290 take an extra argument, coding-system, which specifies the
|
|
|
1291 encoding to be used with the file on disk. For example, here is
|
|
|
1292 a command that converts from the Japanese EUC to ISO2022 format:
|
|
|
1293
|
|
|
1294 xemacs -batch -eval '(progn (find-file
|
|
|
1295 "locale-start.el.euc" (quote euc-japan)) (write-file
|
|
|
1296 "locale-start.el" nil (quote iso-2022-8-unix)))'
|
|
|
1297
|
|
|
1298 Interactively, you can be prompted for a coding system by
|
|
|
1299 providing a prefix argument to the fileio command. In
|
|
|
1300 particular, C-u C-x C-f is a useful sequence to edit a file
|
|
|
1301 using a particular coding system.
|
|
|
1302
|
|
|
1303 -- In an Asian locale (i.e. if $LANG is set to ja, ko, or zh),
|
|
|
1304 XEmacs automatically sets up a language environment assuming
|
|
|
1305 that the operating system encodes information in the national
|
|
|
1306 version of EUC, which supports English and the national
|
|
|
1307 language, but typically no other character sets.
|
|
|
1308
|
|
|
1309 -- Command line processing should work much better now - no more order
|
|
|
1310 dependencies.
|
|
|
1311
|
|
|
1312 -- Many many package upgraded (thanks go to countless maintainers):
|
|
|
1313
|
|
|
1314 -- ediff 2.64 (Michael Kifer)
|
|
90
|
1315 -- Gnus 5.2.40 (Lars Magne Ingebrigtsen)
|
|
88
|
1316 -- w3 3.0.51 (Bill Perry)
|
|
90
|
1317 -- ilisp 5.8 (Chris McConnell, Ivan Vasquez, Marco Antoniotti, Rick
|
|
|
1318 Campbell)
|
|
88
|
1319 -- VM 5.97 (Kyle Jones)
|
|
|
1320 -- etags 11.78 (Francesco Potorti`)
|
|
|
1321 -- ksh-mode.el 2.9
|
|
|
1322 -- vhdl-mode.el 2.73 (Rod Whitby)
|
|
|
1323 -- id-select.el (Bob Weiner)
|
|
|
1324 -- EDT/TPU emulation modes should work now for the first time.
|
|
|
1325 -- viper 2.92 (Michael Kifer) is now the `official' vi emulator for XEmacs.
|
|
|
1326 -- big-menubar should work much better now.
|
|
|
1327 -- mode-motion+.el 3.16
|
|
|
1328 -- backup-dir 2.0 (Greg Klanderman)
|
|
|
1329 -- ps-print.el-3.05 (Jacques Duthen Prestataire)
|
|
90
|
1330 -- lazy-lock-1.15 (Simon Marshall)
|
|
|
1331 -- reporter 3.3 (Barry Warsaw)
|
|
88
|
1332 -- hm--html-menus 5.0 (Heiko Muenkel)
|
|
|
1333 -- cc-mode 4.322 (Barry Warsaw)
|
|
|
1334 -- elp 2.37 (Barry Warsaw)
|
|
|
1335
|
|
|
1336
|
|
|
1337 -- Many new packages have been added:
|
|
|
1338 -- m4-mode 1.8 (Andrew Csillag)
|
|
|
1339 -- crisp.el - crisp/brief emulation (Gary D. Foster)
|
|
|
1340 -- Johan Vroman's iso-acc.el has been ported to XEmacs by Alexandre Oliva
|
|
90
|
1341 -- psgml-1.01 (Lennart Staflin, James Clark)
|
|
88
|
1342 -- python-mode.el 2.83 (Barry Warsaw)
|
|
|
1343 -- vrml-mode.el (Ben Wing)
|
|
90
|
1344 -- enriched.el, face-menu.el (Boris Goldowsky, Michael Sperber)
|
|
|
1345 -- sh-script.el (Daniel Pfeiffer)
|
|
|
1346 -- decipher.el (Christopher J. Madsen)
|
|
88
|
1347
|
|
|
1348 -- New function x-keysym-on-keyboard-p helps determine keyboard
|
|
|
1349 characteristics for key rebinding:
|
|
|
1350
|
|
|
1351 x-keysym-on-keyboard-p: (KEYSYM &optional DEVICE)
|
|
|
1352 -- a built-in function.
|
|
|
1353 Return true if KEYSYM names a key on the keyboard of DEVICE.
|
|
|
1354 More precisely, return true if pressing a physical key
|
|
|
1355 on the keyboard of DEVICE without any modifier keys generates KEYSYM.
|
|
|
1356 Valid keysyms are listed in the files /usr/include/X11/keysymdef.h and in
|
|
|
1357 /usr/lib/X11/XKeysymDB, or whatever the equivalents are on your system.
|
|
|
1358
|
|
|
1359 -- Installed info files are now compressed (support courtesy of Joseph J Nuspl)
|
|
|
1360
|
|
|
1361 -- (load-average) works on Solaris, even if you're not root. Thanks to
|
|
|
1362 Hrvoje Niksic.
|
|
|
1363
|
|
|
1364 -- OffiX drag-and-drop support added
|
|
|
1365
|
|
|
1366 -- lots of syncing with 19.34 elisp files, most by Steven Baur
|
|
70
|
1367
|
|
|
1368
|
|
0
|
1369 ** Major Differences Between 19.13 and 19.14
|
|
|
1370 ============================================
|
|
|
1371
|
|
|
1372 XEmacs has a new address! The canonical ftp site is now
|
|
|
1373 ftp.xemacs.org:/pub/xemacs and the Web page is now at
|
|
|
1374 http://www.xemacs.org/. All mailing lists now have @xemacs.org
|
|
|
1375 addresses. For the time being the @cs.uiuc.edu addresses will
|
|
|
1376 continue to function.
|
|
|
1377
|
|
|
1378 This is a major new release. Many features have been added, as well
|
|
|
1379 as many bugs fixed. The Motif menubar has still _NOT_ been fixed for
|
|
|
1380 19.14. You should use the Lucid menubar instead.
|
|
|
1381
|
|
|
1382
|
|
|
1383
|
|
|
1384 Major user-visible changes:
|
|
|
1385 ---------------------------
|
|
|
1386
|
|
|
1387 -- Color support in TTY mode is provided. You have to have a TTY capable
|
|
|
1388 of displaying them, such as color xterm or the console under Linux.
|
|
|
1389 If your terminal type supports colors (e.g. `xterm-color'), XEmacs
|
|
|
1390 will automatically notice this and start using color.
|
|
|
1391
|
|
|
1392 -- blink-cursor-mode enables a blinking text cursor. There is a
|
|
|
1393 menubar option for this also.
|
|
|
1394
|
|
|
1395 -- auto-show-mode is turned on by default; this means that XEmacs
|
|
|
1396 will automatically scroll a window horizontally as necessary to
|
|
|
1397 keep point in view.
|
|
|
1398
|
|
|
1399 -- a file dialog box is provided and will be used whenever you
|
|
|
1400 are prompted for a filename as a result of a menubar selection.
|
|
|
1401
|
|
|
1402 -- XEmacs can be compiled with built-in GIF, JPEG, and PNG support.
|
|
|
1403 The GIF libraries are supplied with XEmacs; for JPEG and PNG,
|
|
|
1404 you have to obtain the appropriate libraries (this is well-
|
|
|
1405 documented). This makes image display much easier and faster under
|
|
|
1406 W3 (the web browser) and TM (adds MIME support to VM and GNUS;
|
|
|
1407 not yet included with XEmacs but will be in 19.15).
|
|
|
1408
|
|
|
1409 -- XEmacs provides a really nice mode (PSGML with "Wing improvements")
|
|
|
1410 for editing HTML and other SGML documents. It parses the document,
|
|
|
1411 and as a result it does proper indentation, can show you the context
|
|
|
1412 you're in, the allowed tags at a particular position, etc.
|
|
|
1413
|
|
|
1414 -- XEmacs comes standard with modes for editing Java and VRML code,
|
|
|
1415 including font-lock support.
|
|
|
1416
|
|
|
1417 -- GNUS 5.2 comes standard with XEmacs.
|
|
|
1418
|
|
|
1419 -- You can now embed colors in the modeline, with different sections
|
|
|
1420 of the modeline responding appropriately to various mouse gestures:
|
|
|
1421 For example, clicking on the "read-only" indicator toggles the
|
|
|
1422 read-only status of a buffer, and clicking on the buffer name
|
|
|
1423 cycles to the next buffer. Pressing button3 on these areas brings
|
|
|
1424 up a popup menu of appropriate commands.
|
|
|
1425
|
|
|
1426 -- There is a much nicer mode for completion lists and such.
|
|
|
1427 At the minibuffer prompt, if you hit page-up or Meta-V, the completion
|
|
|
1428 buffer will be displayed (if it wasn't already), you're moved into
|
|
|
1429 it, and can move around and select filenames using the arrow keys
|
|
|
1430 and the return key. Rather than a cursor, a filename is highlighted,
|
|
|
1431 and the arrow keys change which filename is highlighted.
|
|
|
1432
|
|
|
1433 -- The edit-faces subsystem has also been much improved, in somewhat
|
|
|
1434 similar ways to the completion list improvements.
|
|
|
1435
|
|
|
1436 -- Many improvements were made to the multi-device support.
|
|
|
1437 We now provide an auxiliary utility called "gnuattach" that
|
|
|
1438 lets you connect to an existing XEmacs process and display
|
|
|
1439 a TTY frame on the current TTY connection, and commands
|
|
|
1440 `make-frame-on-display' (with a corresponding menubar entry)
|
|
|
1441 and `make-frame-on-tty' for more easily creating frames on
|
|
|
1442 new TTY or X connections.
|
|
|
1443
|
|
|
1444 -- We have incorporated nearly all of the functionality of GNU Emacs
|
|
|
1445 19.30 into XEmacs. This includes support for lazy-loaded
|
|
|
1446 byte code and documentation strings, improved paragraph filling,
|
|
|
1447 better support for margins within documents, v19 regular expression
|
|
|
1448 routines (including caching of compiled regexps), etc.
|
|
|
1449
|
|
|
1450 -- In accordance with GNU Emacs 19.30, the following key binding
|
|
|
1451 changes have been made:
|
|
|
1452
|
|
|
1453 C-x ESC -> C-x ESC ESC
|
|
|
1454 ESC ESC -> ESC :
|
|
|
1455 ESC ESC ESC is "abort anything" (keyboard-escape-quit).
|
|
|
1456
|
|
|
1457 -- All major packages have been updated to their latest-released
|
|
|
1458 versions.
|
|
|
1459
|
|
|
1460 -- XEmacs now gracefully handles a full colormap (such as typically
|
|
|
1461 results when running Netscape). The nearest available color
|
|
|
1462 is automatically substituted.
|
|
|
1463
|
|
|
1464 -- Many bug fixes to the subprocess/PTY code, ps-print, menubar
|
|
|
1465 functions, `set-text-properties', DEC Alpha support, toolbar
|
|
|
1466 resizing (the "phantom VM toolbar" bug), and lots and lots
|
|
|
1467 of other things were made.
|
|
|
1468
|
|
|
1469 -- The ncurses library (a replacement for curses, found especially
|
|
|
1470 under Linux) is supported, and will be automatically used
|
|
|
1471 if it can be found.
|
|
|
1472
|
|
|
1473 -- You can now undo in the minibuffer.
|
|
|
1474
|
|
|
1475 -- Surrogate minibuffers now work. These are also sometimes referred
|
|
|
1476 to as "global" minibuffers.
|
|
|
1477
|
|
|
1478 -- font-lock has been merged with GNU Emacs 19.30, improved defaults
|
|
|
1479 have been added, and changes have been made to the way it is
|
|
|
1480 configured.
|
|
|
1481
|
|
|
1482 -- Many, many modes have menubar entries for them.
|
|
|
1483
|
|
|
1484 -- `recover-session' lets you recover whatever files can be recovered
|
|
|
1485 after your XEmacs process has died unexpectedly.
|
|
|
1486
|
|
|
1487 -- C-h k followed by a toolbar button press correctly reports
|
|
|
1488 the binding of the toolbar button.
|
|
|
1489
|
|
|
1490 -- `function-key-map', `key-translation-map', and `keyboard-translate-table'
|
|
|
1491 are now correctly implemented.
|
|
|
1492
|
|
|
1493 -- `show-message-log' (and its menubar entry under Edit) have been
|
|
|
1494 removed; instead use `view-lossage' (and its menubar entry under
|
|
|
1495 Help).
|
|
|
1496
|
|
|
1497 -- There is a standard menubar entry for specifying which browser
|
|
|
1498 (Netscape, W3, Mosaic, etc.) to use when dispatching URL's
|
|
|
1499 in mail, Usenet news, etc.
|
|
|
1500
|
|
|
1501 -- Improved native sound support under Linux.
|
|
|
1502
|
|
|
1503 -- Lots of other things we forgot to mention.
|
|
|
1504
|
|
|
1505
|
|
|
1506
|
|
|
1507 Significant Lisp-level changes:
|
|
|
1508 -------------------------------
|
|
|
1509
|
|
|
1510 -- Many improvements to the E-Lisp documentation have been made;
|
|
|
1511 it should now be up-to-date and complete in nearly all cases.
|
|
|
1512
|
|
|
1513 -- XEmacs has extensive documentation on its internals, for
|
|
|
1514 would-be C hackers.
|
|
|
1515
|
|
|
1516 -- Common-Lisp support (the CL package) is now dumped standard
|
|
|
1517 into XEmacs. No more need for (require 'cl) or anything
|
|
|
1518 like that.
|
|
|
1519
|
|
|
1520 -- Full support for extents and text properties over strings is
|
|
|
1521 provided.
|
|
|
1522
|
|
|
1523 -- The extent properties `start-open', `end-open', `start-closed',
|
|
|
1524 and `end-closed' now work correctly w.r.t. text properties.
|
|
|
1525
|
|
|
1526 -- The `face' property of extents and text properties can now
|
|
|
1527 be a list.
|
|
|
1528
|
|
70
|
1529 -- The `mouse-face' property from FSF GNU Emacs is now supported.
|
|
0
|
1530 It supersedes the `highlight' property.
|
|
|
1531
|
|
70
|
1532 -- `enriched' and `facemenu' packages from FSF GNU Emacs have been ported.
|
|
0
|
1533
|
|
|
1534 -- New functions for easier creation of dialog boxes:
|
|
|
1535 `get-dialog-box-response', `message-box', and `message-or-box'.
|
|
|
1536
|
|
|
1537 -- `function-min-args' and `function-max-args' allow you to determine
|
|
|
1538 the minimum and maximum allowed arguments for any type of
|
|
|
1539 function (i.e. subr, lambda expression, byte-compiled function, etc.).
|
|
|
1540
|
|
|
1541 -- Some C-level support for doing E-Lisp profiling is provided.
|
|
|
1542 See `start-profiling', `stop-profiling', and
|
|
|
1543 `pretty-print-profiling-info'.
|
|
|
1544
|
|
|
1545 -- `current-process-time' reports the user, system, and real times
|
|
|
1546 for the currently running XEmacs process.
|
|
|
1547
|
|
|
1548 -- `next-window', `previous-window', `next-frame', `previous-frame',
|
|
|
1549 `other-window', `get-lru-window', etc. have an extra device
|
|
|
1550 argument that allows you to restrict which devices it includes
|
|
|
1551 (normally all devices). Some functions that incorrectly ignored
|
|
|
1552 frames on different devices (e.g. C-x 0) are fixed.
|
|
|
1553
|
|
|
1554 -- new functions `run-hook-with-args-until-success',
|
|
|
1555 `run-hook-with-args-until-failure'.
|
|
|
1556
|
|
|
1557 -- generalized facility for local vs. global hooks. See `make-local-hook',
|
|
|
1558 `add-hook'.
|
|
|
1559
|
|
|
1560 -- New functions for querying the window tree: `frame-leftmost-window',
|
|
|
1561 `frame-rightmost-window', `window-first-hchild', `window-first-vchild',
|
|
|
1562 `window-next-child', `window-previous-child', and `window-parent'.
|
|
|
1563
|
|
|
1564 -- Epoch support works. This gets you direct access to some X events
|
|
|
1565 and objects (e.g. properties and property-notify events).
|
|
|
1566
|
|
|
1567 -- The multi-device support has been majorly revamped. There is now
|
|
|
1568 a new concept of "consoles" (devices grouped together under a
|
|
|
1569 common keyboard/mouse), console-local variables, and a generalized
|
|
|
1570 concept of device/console connection.
|
|
|
1571
|
|
|
1572 -- `display-buffer' synched with GNU Emacs 19.30, giving you lots of
|
|
|
1573 wondrous cruft such as
|
|
|
1574 -- unsplittable frames
|
|
|
1575 -- pop-up-frames, pop-up-frame-function
|
|
|
1576 -- special-display-buffer-names, special-display-regexps,
|
|
|
1577 special-display-function
|
|
|
1578 -- same-window-buffer-names, same-window-regexps
|
|
|
1579
|
|
|
1580 -- XEmacs has support for accessing DBM- and/or DB-format databases,
|
|
|
1581 provided that you have the appropriate libraries on your system.
|
|
|
1582
|
|
|
1583 -- There is a new font style: "strikethru" fonts.
|
|
|
1584
|
|
|
1585 -- New data type "weak list", which is a list with special
|
|
|
1586 garbage-collection properties, similar to weak hash tables.
|
|
|
1587
|
|
|
1588 -- `set-face-parent' makes one face inherit all properties from another.
|
|
|
1589
|
|
|
1590 -- The junky frame parameters mechanism has been revamped as
|
|
|
1591 frame properties, which a standard property-list interface.
|
|
|
1592
|
|
|
1593 -- Lots and lots of functions for working with property lists have
|
|
|
1594 been added.
|
|
|
1595
|
|
|
1596 -- New functions `push-window-configuration', `pop-window-configuration',
|
|
|
1597 `unpop-window-configuration' for maintain a stack of window
|
|
|
1598 configurations.
|
|
|
1599
|
|
|
1600 -- Many fixups to the glyph code; icons and mouse pointers are now
|
|
|
1601 properly merged into the glyph mechanism.
|
|
|
1602
|
|
|
1603 -- `set-specifier' works more sensibly, like `set-face-property'.
|
|
|
1604
|
|
|
1605 -- Many new specifiers for individually controlling toolbar height/width
|
|
|
1606 and visibility and text cursor visibility.
|
|
|
1607
|
|
|
1608 -- New face `text-cursor' controls the colors of the text cursor.
|
|
|
1609
|
|
|
1610 -- Many new variables for turning on debug information about the
|
|
|
1611 inner workings of XEmacs.
|
|
|
1612
|
|
|
1613 -- Hash tables can now compare their keys using `equal' or `eql'
|
|
|
1614 as well as `eq'.
|
|
|
1615
|
|
|
1616 -- Other things too numerous to mention.
|
|
|
1617
|
|
|
1618
|
|
|
1619
|
|
|
1620 Significant configuration/build changes:
|
|
|
1621 ----------------------------------------
|
|
|
1622
|
|
|
1623 -- You can disable TTY support, toolbar support, scrollbar support,
|
|
|
1624 menubar support, and/or dialog box support at configure time
|
|
|
1625 to save memory.
|
|
|
1626
|
|
|
1627 -- New configure option `--extra-verbose' shows the diagnostic
|
|
|
1628 output from feature testing; this should help track down
|
|
|
1629 problems with incorrect feature detection.
|
|
|
1630
|
|
|
1631 -- `dont-have-xmu' is now `with-xmu', with the reversed sense.
|
|
|
1632 (It defaults to `yes'.)
|
|
|
1633
|
|
|
1634 -- `with-mocklisp' lets you add Mocklisp support if you really
|
|
|
1635 need this.
|
|
|
1636
|
|
|
1637 -- `with-term' for adding TERM support for Linux users.
|
|
|
1638
|
|
|
1639
|
|
|
1640
|
|
|
1641 ** Major Differences Between 19.12 and 19.13
|
|
|
1642 ============================================
|
|
|
1643
|
|
|
1644 This is primarily a bug-fix release. Lots of bugs have been fixed.
|
|
|
1645 Hopefully only a few have been introduced. The most noteworthy bug
|
|
|
1646 fixes are:
|
|
|
1647
|
|
|
1648 -- There should be no more problems connecting XEmacs to an X
|
|
|
1649 server over SLIP or other slow connections.
|
|
|
1650 -- Periodic crashes when using the Buffers menu should be gone.
|
|
|
1651 -- etags would sometimes erase the current buffer; it doesn't
|
|
|
1652 any more.
|
|
|
1653 -- XEmacs will correctly exit if the X server dies.
|
|
|
1654 -- uniconified frames are displayed properly under TVTWM.
|
|
|
1655 -- Breakage in `add-menu-item' / `add-menu-button' is fixed.
|
|
|
1656
|
|
|
1657 The Motif menubar has _NOT_ been fixed for 19.13. You should use the
|
|
|
1658 Lucid menubar instead.
|
|
|
1659
|
|
|
1660 Multi-device support should now be working properly. You can now open
|
|
|
1661 an X device after having started out on a TTY device.
|
|
|
1662
|
|
|
1663 Background pixmaps now work. See `set-face-background-pixmap'.
|
|
|
1664
|
|
|
1665 Echo area messages are now saved to a buffer, " *Message Log*". To
|
|
|
1666 see this buffer, use the command `show-message-log'. It is possible
|
|
|
1667 to filter the message which are actually included by modifying the
|
|
|
1668 variables `log-message-ignore-regexps' and `log-message-ignore-labels'.
|
|
|
1669
|
|
|
1670 You can now control which warnings you want to see. See
|
|
|
1671 `display-warning-suppressed-classes' and friends.
|
|
|
1672
|
|
|
1673 You can now set the default location of an "other window" from the
|
|
|
1674 Options menu.
|
|
|
1675
|
|
|
1676 "Save Options" now saves the state of all faces.
|
|
|
1677
|
|
|
1678 You can choose which file "Save Options" writes into; see
|
|
|
1679 `save-options-file'.
|
|
|
1680
|
|
|
1681 XPM support is no longer required for the toolbar.
|
|
|
1682
|
|
|
1683 The relocating allocator is now enabled by default whenever possible.
|
|
|
1684 This allows buffer memory to be returned to the system when no longer
|
|
|
1685 in use which helps keep XEmacs process size down.
|
|
|
1686
|
|
|
1687 The ability to have captioned toolbars has been added. Currently only
|
|
|
1688 the default toolbar actually has a captioned version provided. A new
|
|
|
1689 specifier variable, `toolbar-buttons-captioned-p' controls whether the
|
|
|
1690 toolbar is captioned.
|
|
|
1691
|
|
|
1692 A copy of the XEmacs FAQ is now included and is available through info.
|
|
|
1693
|
|
|
1694 The on-line E-Lisp reference manual has been significantly updated.
|
|
|
1695
|
|
|
1696 There is now audio support under Linux.
|
|
|
1697
|
|
|
1698 Modifier keys can now be sticky. This is controlled by the variable
|
|
|
1699 `modifier-keys-are-sticky'.
|
|
|
1700
|
|
|
1701 manual-entry should now work correctly under Irix with the penalty of
|
|
|
1702 a longer startup time the first time it is invoked. If you are having
|
|
|
1703 problems with this on another system try setting
|
|
|
1704 `Manual-use-subdirectory-list' to t.
|
|
|
1705
|
|
|
1706 make-tty-device no longer automatically creates the first frame.
|
|
|
1707
|
|
|
1708 Rectangular regions now work correctly.
|
|
|
1709
|
|
|
1710 ediff no longer sets synchronize-minibuffers to t unless you first set
|
|
|
1711 ediff-synchronize-minibuffers
|
|
|
1712
|
|
|
1713 keyboard-translate-table has been implemented. This means that the
|
|
|
1714 `enable-flow-control' command for dealing with TTY connections that
|
|
|
1715 filter out ^S and ^Q now works.
|
|
|
1716
|
|
|
1717 You can now create frames that are initially unmapped and frames that
|
|
|
1718 are "transient for another frame", meaning that they behave more like
|
|
|
1719 dialog-box frames.
|
|
|
1720
|
|
|
1721 Other E-Lisp changes:
|
|
|
1722
|
|
|
1723 -- Specifier `menubar-visible-p' for controlling menubar visibility
|
|
|
1724 -- Local command hooks should be set using `local-pre-command-hook'
|
|
|
1725 and `local-post-command-hook' instead of making the global
|
|
|
1726 equivalents be buffer-local.
|
|
|
1727 -- `quit-char', `help-char', `meta-prefix-char' can be any key specifier
|
|
|
1728 instead of just an integer.
|
|
|
1729 -- new functions `add-async-timeout' and `disable-async-timeout'.
|
|
|
1730 These let you create asynchronous timeouts, which are like
|
|
|
1731 normal timeouts except that they're executed even during
|
|
|
1732 running Lisp code. Use this with care!
|
|
|
1733 -- `debug-on-error' and `stack-trace-on-error' now enter the debugger
|
|
|
1734 only when an *unhandled* error occurs. If you want the old
|
|
|
1735 behavior, use `debug-on-signal' and `stack-trace-on-signal'.
|
|
|
1736 -- \U, \L, \u, \l, \E recognized specially in `replace-match'.
|
|
|
1737 These are standard ex/perl commands for changing the case of
|
|
|
1738 replaced text.
|
|
|
1739 -- New function event-matches-key-specifier-p. This provides
|
|
|
1740 a clean way of comparing keypress events with key specifiers
|
|
|
1741 such as 65, (shift home), etc. without having to resort
|
|
|
1742 to ugly `character-to-event' / `event-to-character' hacks.
|
|
|
1743 -- New function `add-to-list'
|
|
|
1744 -- New Common-Lisp functions `some', `every', `notevery', `notany',
|
|
|
1745 `adjoin', `union', `intersection', `set-difference',
|
|
|
1746 `set-exclusive-or', `subsetp'
|
|
|
1747 -- `remove-face-property' provides a clean way of removing a
|
|
|
1748 face property.
|
|
|
1749
|
|
|
1750 Many of the Emacs Lisp packages have been updated. Some of the new
|
|
|
1751 Emacs Lisp packages ---
|
|
|
1752
|
|
|
1753 ada-mode: major mode for editing Ada source
|
|
|
1754
|
|
|
1755 arc-mode: simple editing of archives
|
|
|
1756
|
|
70
|
1757 auto-show-mode: automatically scrolls horizontally to keep point on-screen
|
|
0
|
1758
|
|
|
1759 completion: dynamic word completion mode
|
|
|
1760
|
|
|
1761 dabbrev: the dynamic abbrev package has been rewritten and is much
|
|
|
1762 more powerful -- e.g. it searches in other buffers as well
|
|
|
1763 as the current one
|
|
|
1764
|
|
|
1765 easymenu: menu support package
|
|
|
1766
|
|
|
1767 live-icon: makes frame icons represent the current frame contents
|
|
|
1768
|
|
|
1769 mailcrypt 3.2: mail encryption with PGP; included but v2.4 is still
|
|
70
|
1770 the default
|
|
|
1771
|
|
|
1772 two-column: for editing two-column text
|
|
0
|
1773
|
|
|
1774
|
|
|
1775 ** Major Differences Between 19.11 and 19.12
|
|
|
1776 ============================================
|
|
|
1777
|
|
|
1778 This is a huge new release. Almost every aspect of XEmacs has been changed
|
|
|
1779 at least somewhat. The highlights are:
|
|
|
1780
|
|
|
1781 -- TTY support (includes face support)
|
|
|
1782 -- new redisplay engine; should be faster, less buggy, and more powerful
|
|
|
1783 -- terminology change from "screen" to "frame"
|
|
|
1784 -- built-in toolbar
|
|
|
1785 -- toolbar support added to many packages
|
|
|
1786 -- multiple device support (still in beta; improvements to come in
|
|
|
1787 19.13)
|
|
|
1788 -- Purify used to ensure that there are no memory leaks or memory corruption
|
|
|
1789 problems
|
|
|
1790 -- horizontal and vertical scrollbars in all windows
|
|
|
1791 -- new Lucid (i.e. look-alike Motif) scrollbar widget
|
|
|
1792 -- stay-up menus in the Lucid (look-alike Motif) menubar widget
|
|
|
1793 -- 3-d modeline
|
|
|
1794 -- new extents engine; should be faster, less buggy, and more powerful
|
|
|
1795 -- much more powerful control over faces
|
|
|
1796 -- expanded menubar
|
|
|
1797 -- more work on synching with GNU Emacs 19.28
|
|
|
1798 -- new packages: Hyperbole, OOBR (object browser), hm--html-menus, viper,
|
|
|
1799 lazy-lock.el, ksh-mode.el, rsz-minibuf.el
|
|
|
1800 -- package updates for all major packages
|
|
|
1801 -- dynodump package for Solaris: provides proper undumping and portable
|
|
|
1802 binaries across different OS versions and machine types
|
|
|
1803 -- Greatly expanded concept of "glyphs" (pixmaps etc. in a buffer)
|
|
|
1804 -- built-in support for displaying X-Faces, if the X-Face library is
|
|
|
1805 available
|
|
|
1806 -- built-in support for SOCKS if the SOCKS library is available
|
|
|
1807 -- graceful behavior when the colormap is full (e.g. Netscape ate
|
|
|
1808 all the colors)
|
|
|
1809 -- built-in MD5 (secure hashing function) support
|
|
|
1810
|
|
|
1811
|
|
|
1812 More specific information:
|
|
|
1813
|
|
|
1814 *** TTY Support
|
|
|
1815 ---------------
|
|
|
1816
|
|
|
1817 The long-awaited TTY support is now available. XEmacs will start up
|
|
|
1818 in TTY mode (using the tty you started XEmacs from) if the DISPLAY
|
|
|
1819 environment variable is not set or if you use the `-nw' option.
|
|
|
1820
|
|
|
1821 Faces are available on TTY's. For a demonstration, try editing a C
|
|
|
1822 file and turning on font-lock-mode.
|
|
|
1823
|
|
|
1824 You can also connect to additional TTY's using `make-tty-device',
|
|
|
1825 whether your first frame was a TTY or an X window. This ability is
|
|
|
1826 not yet completely finished.
|
|
|
1827
|
|
|
1828 The full event-loop capabilities (processes, timeouts, etc.) are
|
|
|
1829 available on TTY's.
|
|
|
1830
|
|
|
1831
|
|
|
1832
|
|
|
1833 *** New Redisplay Engine
|
|
|
1834 ------------------------
|
|
|
1835
|
|
|
1836 The redisplay engine has been rewritten to improve its efficiency and
|
|
|
1837 to increase its functionality. It should also be significantly more
|
|
|
1838 bug-free than the previous redisplay engine.
|
|
|
1839
|
|
|
1840 A line that is not big enough to display at the bottom of the window
|
|
|
1841 will normally be clipped (so that it is partially visible) rather than
|
|
|
1842 not displayed at all. The variable `pixel-vertical-clip-threshold'
|
|
|
1843 can be used to control the minimum space that must be available for a
|
|
|
1844 line to be clipped rather than not displayed at all.
|
|
|
1845
|
|
|
1846 Tabs are displayed in such a way that things line up fairly well even
|
|
|
1847 in the presence of variable-width fonts and/or lines with
|
|
|
1848 multiply-sized fonts.
|
|
|
1849
|
|
|
1850 Display tables are implemented, through the specifier variable
|
|
|
1851 `current-display-table'. They can be buffer-local, window-local,
|
|
|
1852 frame-local, or device-local. See below for info about specifiers.
|
|
|
1853
|
|
|
1854
|
|
|
1855
|
|
|
1856 *** Toolbar
|
|
|
1857 -----------
|
|
|
1858
|
|
|
1859 There is now built-in support for a toolbar. A sample toolbar is
|
|
|
1860 visible by default at the top of the frame. Four separate toolbars
|
|
|
1861 can be configured (at the top, bottom, left, and right of the frame).
|
|
|
1862 The toolbar specification is similar to the menubar specification.
|
|
|
1863 The up, down, and disabled glyphs of a toolbar button can be
|
|
|
1864 separately controlled. Explanatory text can be echoed in the echo
|
|
|
1865 area when the mouse passes over a toolbar button. The size, contents,
|
|
|
1866 and visibility of the various toolbars can be controlled on a
|
|
|
1867 per-buffer, per-window, per-frame, and per-device basis through the
|
|
|
1868 use of specifiers. See the chapter on toolbars in the Lisp Reference
|
|
|
1869 Manual (included with XEmacs) for more information.
|
|
|
1870
|
|
|
1871 The toolbar color and shadow thicknesses are currently controlled only
|
|
|
1872 through `modify-frame-parameters' and through X resources. We are
|
|
|
1873 planning on making these controllable through specifiers as well. (Our
|
|
|
1874 hope is to make `modify-frame-parameters' obsolete, as it is a clunky
|
|
|
1875 and not very powerful mechanism.)
|
|
|
1876
|
|
|
1877 Info, GNUS, VM, W3, and various other packages include custom toolbars
|
|
|
1878 with them.
|
|
|
1879
|
|
|
1880
|
|
|
1881
|
|
|
1882 *** Menubar
|
|
|
1883 -----------
|
|
|
1884
|
|
|
1885 Stay-up menus are implemented in the look-alike Motif menubar.
|
|
|
1886
|
|
|
1887 The default menubar has been expanded to include most commonly-used
|
|
|
1888 functions in XEmacs.
|
|
|
1889
|
|
|
1890 The options menu has been greatly expanded to include many more
|
|
|
1891 options.
|
|
|
1892
|
|
|
1893 The menubar specification format has been greatly expanded. Per-menu
|
|
|
1894 activation hooks can be specified through the :filter keyword (thus
|
|
|
1895 obsoleting `activate-menubar-hook'); this allows for fast response
|
|
|
1896 time when you have a large and complex menu. You can dynamically
|
|
|
1897 control whether menu items are present through the :included and
|
|
|
1898 :config keywords. (The latter keyword implements a simple menubar
|
|
|
1899 configuration scheme, in conjunction with the variable
|
|
|
1900 `menubar-configuration'.) Many different menu-item separators (single
|
|
|
1901 or double line; solid or dashed; flat, etched-in, or etched-out) are
|
|
|
1902 available. See the chapter on menus in the Lisp Reference Manual for
|
|
|
1903 more information about all of this.
|
|
|
1904
|
|
|
1905 New functions `add-submenu' and `add-menu-button' are available.
|
|
|
1906 These supersede the older `add-menu' and `add-menu-item' functions,
|
|
|
1907 and provide a more powerful and consistent interface.
|
|
|
1908
|
|
|
1909 New convenience functions for popping up the part or all of the
|
|
|
1910 menubar in a pop-up menu are available: `popup-menubar-menu' and
|
|
|
1911 `popup-buffer-menu'.
|
|
|
1912
|
|
|
1913 Menus are now incrementally constructed greatly improving menubar
|
|
|
1914 response time.
|
|
|
1915
|
|
|
1916
|
|
|
1917
|
|
|
1918 *** Scrollbars
|
|
|
1919 --------------
|
|
|
1920
|
|
|
1921 A look-alike Motif scrollbar is now included with XEmacs. No longer
|
|
|
1922 will you have to suffer with ugly Athena scrollbars.
|
|
|
1923
|
|
|
1924 Windows can now have horizontal scrollbars. Normally they are visible
|
|
|
1925 when the window's buffer is set to truncate lines rather than wrap
|
|
|
1926 them (e.g. `(setq truncate-lines t)').
|
|
|
1927
|
|
|
1928 All windows, not only the right-most ones, can have vertical
|
|
|
1929 scrollbars.
|
|
|
1930
|
|
|
1931 The functions to change a scrollbar's width have been superseded by
|
|
|
1932 the specifier variables `scrollbar-width' and `scrollbar-height'.
|
|
|
1933 This allows their values to be controlled on a buffer-local,
|
|
|
1934 window-local, frame-local, and device-local basis. See below.
|
|
|
1935
|
|
|
1936 The scrollbars interact better with the event loop (for example, you
|
|
|
1937 can type `C-h k', do a scrollbar action, and see a description of this
|
|
|
1938 scrollbar action printed as if you had pressed a key sequence or
|
|
|
1939 selected a menu item).
|
|
|
1940
|
|
|
1941 The scrollbar behavior can be reprogrammed, by advising the
|
|
|
1942 `scrollbar-*' functions.
|
|
|
1943
|
|
|
1944
|
|
|
1945
|
|
|
1946 *** Key Bindings
|
|
|
1947 ----------------
|
|
|
1948
|
|
|
1949 The oft-used function `goto-line' now has its own binding: M-g.
|
|
|
1950
|
|
|
1951 New bindings are available for scrolling the "other" window: M-next,
|
|
|
1952 M-prior, M-home, M-end. (On many keyboards, `next' and `prior'
|
|
|
1953 labelled `PgUp' and `PgDn'.)
|
|
|
1954
|
|
|
1955 You can reactivate a deactivated Zmacs region, without having any
|
|
|
1956 other effects, with the binding M-C-z.
|
|
|
1957
|
|
|
1958 The bindings `M-u', `M-l', and `M-c' now work on the region (if a
|
|
|
1959 region is active) or work on a word, as before.
|
|
|
1960
|
|
|
1961 Shift-Control-G forces a "critical quit", which drops immediately into
|
|
|
1962 the debugger; see below.
|
|
|
1963
|
|
|
1964
|
|
|
1965
|
|
|
1966 *** Modeline
|
|
|
1967 ------------
|
|
|
1968
|
|
|
1969 The modeline can now have a 3-d look; this is enabled by default. The
|
|
|
1970 specifier variable `modeline-shadow-thickness' controls the size.
|
|
|
1971
|
|
|
1972 The modeline can now be turned off on a per-buffer, per-window,
|
|
|
1973 per-frame, or per-device basis. The specifier variable
|
|
|
1974 `has-modeline-p' controls whether the modeline is visible. See below
|
|
|
1975 for details about the vastly powerful specifier mechanism.
|
|
|
1976
|
|
|
1977 The modeline functions and variables have been renamed to be
|
|
|
1978 `*-modeline-*' rather than `*-mode-line-*'. Aliases are provided for
|
|
|
1979 all the old names.
|
|
|
1980
|
|
|
1981 Variable width fonts now work correctly when used in the modeline.
|
|
|
1982
|
|
|
1983
|
|
|
1984
|
|
|
1985 *** Minibuffer, Echo Area
|
|
|
1986 -------------------------
|
|
|
1987
|
|
|
1988 The minibuffer is no longer constrained to be one line high. The
|
|
|
1989 package rsz-minibuf.el is included to automatically resize the
|
|
|
1990 minibuffer when its contents are too big; enable this with
|
|
|
1991 `resize-minibuffer-mode'.
|
|
|
1992
|
|
|
1993 The echo area is now a true buffer, called " *Echo Area*". This
|
|
|
1994 allows you to customize the echo area behavior through
|
|
|
1995 before-change-functions and after-change-functions.
|
|
|
1996
|
|
|
1997
|
|
|
1998
|
|
|
1999 *** Specifiers
|
|
|
2000 --------------
|
|
|
2001
|
|
|
2002 XEmacs has a new concept called "specifiers", used to configure most
|
|
|
2003 display options (toolbar size and contents, scrollbar size, face
|
|
|
2004 properties, modeline visibility and shadow-thickness, glyphs, display
|
|
|
2005 tables, etc.). We are planning on converting all display
|
|
|
2006 characteristics to use specifiers, and obsoleting the clunky functions
|
|
|
2007 `frame-parameters' and `modify-frame-parameters'. Specifically:
|
|
|
2008
|
|
|
2009 -- You can specify values (called "instantiators") for particular
|
|
|
2010 "locales" (i.e. buffers, windows, frames, devices, or a global value).
|
|
|
2011 When determining what the actual value (or "instance") of a specifier
|
|
|
2012 is, the specifications that are provided are searched from most
|
|
|
2013 specific (i.e. buffer-local) to most general (i.e. global), looking
|
|
|
2014 for a matching one.
|
|
|
2015
|
|
|
2016 -- You can specify multiple instantiators for a particular locale.
|
|
|
2017 For example, when specifying what the foreground color of a face
|
|
|
2018 is in a particular buffer, you could specify two instantiators:
|
|
|
2019 "dark sea green" and "green". The color would then be dark sea
|
|
|
2020 green on devices that recognize that color, and green on other
|
|
|
2021 devices. You have effectively provided a fallback value to make
|
|
|
2022 sure you get reasonable behavior on all devices.
|
|
|
2023
|
|
|
2024 -- You can add one or more tags to an instantiator, where a tag
|
|
|
2025 is a symbol that has been previously registered with XEmacs.
|
|
|
2026 This allows you to identify your instantiators for later
|
|
|
2027 removal in a way that won't interfere with other applications
|
|
|
2028 using the same specifier. Furthermore, particular tags can
|
|
|
2029 be restricted to match only particular sorts of devices.
|
|
|
2030 Any tagged instantiator will be ignored if the device over which
|
|
|
2031 it is being instanced does not match any of its tags. This
|
|
|
2032 allows you, for example, to restrict an instantiator to a
|
|
|
2033 particular device type (X or TTY) and/or class (color, grayscale,
|
|
|
2034 or mono). (You might want to specify, for example, that a
|
|
|
2035 particular face is displayed in green on color devices and is
|
|
|
2036 underlined on mono devices.)
|
|
|
2037
|
|
|
2038 -- A full API is provided for manipulating specifiers, and full
|
|
|
2039 documentation is provided in the Lisp Reference Manual.
|
|
|
2040
|
|
|
2041
|
|
|
2042
|
|
|
2043 *** Basic Lisp Stuff
|
|
|
2044 --------------------
|
|
|
2045
|
|
|
2046 Common-Lisp backquote syntax is recognized. For example, the old
|
|
|
2047 expression
|
|
|
2048
|
|
|
2049 (` (a b (, c)))
|
|
|
2050
|
|
|
2051 can now be written
|
|
|
2052
|
|
|
2053 `(a b ,c)
|
|
|
2054
|
|
|
2055 The old backquote syntax is still accepted.
|
|
|
2056
|
|
|
2057 The new function `type-of' returns a symbol describing the type of a
|
|
|
2058 Lisp object (`integer', `string', `symbol', etc.)
|
|
|
2059
|
|
|
2060 Symbols beginning with a colon (called "keywords") are treated
|
|
|
2061 specially in that they are automatically made self-evaluating when
|
|
|
2062 they are interned into `obarray'. The new function `keywordp' returns
|
|
|
2063 whether a symbol begins with a colon.
|
|
|
2064
|
|
|
2065 `get', `put', and `remprop' have been generalized to allow you to set
|
|
|
2066 and retrieve properties on many different kinds of objects: symbols,
|
|
|
2067 strings, faces, glyphs, and extents (for extents, however, this is not
|
|
|
2068 yet implemented). They are joined by a new function `object-props'
|
|
|
2069 that returns all of the properties that have been set on an object.
|
|
|
2070
|
|
|
2071 New functions `plists-eq' and `plists-equal' are provided for
|
|
|
2072 comparing property lists (a property list is an alternating list
|
|
|
2073 of keys and values).
|
|
|
2074
|
|
|
2075 The Common-Lisp functions `caar', `cadr', `cdar', `cddr', `caaar', etc.
|
|
|
2076 (up to four a's and/or d's), `first', `second', `third', etc. (up to
|
|
|
2077 `tenth'), `last', `rest', and `endp' have been added, for more
|
|
|
2078 convenient manipulation of lists.
|
|
|
2079
|
|
|
2080 New function `mapvector' maps over a sequence and returns a vector
|
|
|
2081 of the results, analogous to `mapcar'.
|
|
|
2082
|
|
|
2083 New functions `rassoc', `remassoc', `remassq', `remrassoc', and
|
|
|
2084 `remrassq' are provided for working with alists.
|
|
|
2085
|
|
|
2086 New functions `defvaralias', `variable-alias' and `indirect-variable'
|
|
|
2087 are provided for creating variable aliases.
|
|
|
2088
|
|
|
2089 Strings have a modified-tick that is bumped every time a string
|
|
|
2090 is modified in-place with `aset' or `fillarray'. This is retrieved
|
|
|
2091 with the new function `string-modified-tick'.
|
|
|
2092
|
|
|
2093 New macro `push' destructively adds an element to the beginning of a
|
|
|
2094 list. New macro `pop' destructively removes and returns the first
|
|
|
2095 element of a list.
|
|
|
2096
|
|
|
2097
|
|
|
2098
|
|
|
2099 *** Buffers
|
|
|
2100 -----------
|
|
|
2101
|
|
|
2102 Most functions that operate on buffer text now take an optional BUFFER
|
|
|
2103 argument, specifying which buffer they operate on. (Previously, they
|
|
|
2104 always operated on the current buffer.)
|
|
|
2105
|
|
|
2106 The new function `transpose-regions' is provided, ported from GNU
|
|
|
2107 Emacs.
|
|
|
2108
|
|
|
2109 The new function `save-current-buffer' works like `save-excursion'
|
|
|
2110 but only saves the current buffer, not the location of point in
|
|
|
2111 that buffer.
|
|
|
2112
|
|
|
2113
|
|
|
2114
|
|
|
2115 *** Devices
|
|
|
2116 -----------
|
|
|
2117
|
|
|
2118 XEmacs has a new concept of "device", which is represents a particular
|
|
|
2119 X display or TTY connection. `make-frame' has a new, optional device
|
|
|
2120 parameter that allows you to specify which device the frame is to be
|
|
|
2121 created on.
|
|
|
2122
|
|
|
2123 Multiple simultaneous TTY and/or X connections may be made. The
|
|
|
2124 specifier mechanism provides reasonable behavior of glyphs, faces,
|
|
|
2125 etc. over heterogeneous device types and over devices whose individual
|
|
|
2126 capabilities may vary.
|
|
|
2127
|
|
|
2128 There is also a device type called "stream" that represents a STDIO
|
|
|
2129 device that has no redisplay or cursor-motion capabilities, such as
|
|
|
2130 the "glass terminal" that XEmacs uses when it is run noninteractively.
|
|
|
2131 There is not all that much you can do with stream devices currently;
|
|
|
2132 please let us know if there are good uses you can think of for this
|
|
|
2133 capability. (For example, log files?)
|
|
|
2134
|
|
|
2135 A new device API is provided. Functions are provided such as
|
|
|
2136 `device-name' (the name of the device, which generally is based on the
|
|
|
2137 X display or TTY file name), `device-type' (X, TTY, or stream),
|
|
|
2138 `device-class' (color, grayscale, or mono), etc. See the Lisp
|
|
|
2139 Reference Manual.
|
|
|
2140
|
|
|
2141 Many functions have been extended to contain an additional, optional
|
|
|
2142 device argument, where such an extension makes sense. In general, if
|
|
|
2143 the argument is omitted, it is equivalent to specifying
|
|
|
2144 `(selected-device)'.
|
|
|
2145
|
|
|
2146 Many previous functions and variables are obsoleted in favor of the
|
|
|
2147 device API. For example, `window-system' is obsoleted by
|
|
|
2148 `device-type', and `x-color-display-p' and friends are obsoleted by
|
|
|
2149 `device-class'.
|
|
|
2150
|
|
70
|
2151 ** NOTE **: The obsolete variable `window-system' is going
|
|
0
|
2152 to be deleted soon, probably in 19.14. Please correct all
|
|
|
2153 your code to use `device-type'.
|
|
|
2154
|
|
70
|
2155 ** INCOMPATIBLE CHANGE **: The function `x-display-visual-class'
|
|
0
|
2156 returns different values from previous versions of XEmacs.
|
|
|
2157
|
|
|
2158
|
|
|
2159
|
|
|
2160 *** Errors, Warnings, C-g
|
|
|
2161 -------------------------
|
|
|
2162
|
|
|
2163 There is a new warnings system implemented. Many warnings that were
|
|
|
2164 formerly displayed in various ad-hoc ways (e.g. warnings about screwy
|
|
|
2165 modifier mappings, messages about failures handling the mouse cursor
|
|
|
2166 and errors in a gc-hook) have been regularized through this system.
|
|
|
2167 The new function `warn' displays a warning before the next redisplay
|
|
|
2168 (the actually display of the warning messages is accomplished through
|
|
|
2169 `display-warning-buffer'). Both `warn' and `display-warning-buffer'
|
|
|
2170 are Lisp functions (the C code calls out to them as necessary), and
|
|
|
2171 thus you can customize the warning system.
|
|
|
2172
|
|
|
2173 Under an X display, you can press Shift-Control-G to force a "critical
|
|
|
2174 quit". This will immediately display a backtrace and pop you into the
|
|
|
2175 debugger, regardless of the settings of `inhibit-quit' and
|
|
|
2176 `debug-on-quit'.
|
|
|
2177
|
|
|
2178 C-g now works properly even on systems that don't implement SIGIO or
|
|
|
2179 for which SIGIO is broken (e.g. IRIX 5.3 and older versions of Linux).
|
|
|
2180 In addition, the SIGIO support has been fixed for many systems on
|
|
|
2181 which it didn't always work properly before (e.g. HPUX and Solaris).
|
|
|
2182
|
|
70
|
2183
|
|
0
|
2184
|
|
|
2185 *** Events
|
|
|
2186 ----------
|
|
|
2187
|
|
70
|
2188 ** INCOMPATIBLE CHANGE **: Many event functions have been changed to
|
|
0
|
2189 accept and return windows instead of frames.
|
|
|
2190
|
|
|
2191 New function: `event-live-p', specifying whether `deallocate-event'
|
|
|
2192 has been called on an event.
|
|
|
2193
|
|
|
2194 The "menu event" type has been renamed to "misc-user event", and
|
|
|
2195 encompasses scrollbar events as well as menu events. We are planning
|
|
|
2196 on making it also encompass toolbar events in a future release.
|
|
|
2197
|
|
|
2198 New functions are provided for determining whether an particular
|
|
|
2199 sections of a frame: `event-over-border-p', `event-over-glyph-p',
|
|
|
2200 `event-over-modeline-p', `event-over-text-area-p', and
|
|
|
2201 `event-over-toolbar-p'. The old, kludgey methods of checking the
|
|
|
2202 window-height, the internal-border-width, etc. are unreliable and
|
|
|
2203 should not be used.
|
|
|
2204
|
|
|
2205 New functions `event-window-x-pixel' and `event-window-y-pixel' are
|
|
|
2206 provided for determining where in a particular window an event
|
|
|
2207 happened.
|
|
|
2208
|
|
|
2209 New functions `event-glyph-x-pixel' and `event-glyph-y-pixel' are
|
|
|
2210 provided for determining where in a particular glyph an event
|
|
|
2211 happened.
|
|
|
2212
|
|
|
2213 New function `event-closest-point', which returns the closest buffer
|
|
|
2214 position to the event even if the event did not occur over any text.
|
|
|
2215
|
|
|
2216 New variable `unread-command-events', superseding the older
|
|
|
2217 `unread-command-event'.
|
|
|
2218
|
|
|
2219 Many event-loop bugs have been fixed.
|
|
|
2220
|
|
|
2221
|
|
|
2222
|
|
|
2223 *** Extents
|
|
|
2224 -----------
|
|
|
2225
|
|
|
2226 The extent code has been largely rewritten. It should be faster and
|
|
|
2227 more reliable.
|
|
|
2228
|
|
|
2229 The text-property implementation has been greatly improved.
|
|
|
2230
|
|
|
2231 Some new extent primitives are provided to return the position of the
|
|
|
2232 next or previous property change in a buffer.
|
|
|
2233
|
|
|
2234 Extents can now have a parent specified; then all of its properties
|
|
|
2235 (except for the buffer it's in and its position in that buffer) come
|
|
|
2236 from that extent. Hierarchies of such extents can be created.
|
|
|
2237
|
|
|
2238 Extents now have a `detachable' property that controls what happens
|
|
|
2239 (they either get detached or shrink down to zero-length) when their
|
|
|
2240 text is deleted. Previously, such extents would always be detached.
|
|
|
2241
|
|
|
2242 The `invisible' property on extents now works.
|
|
|
2243
|
|
|
2244 `map-extents' has three additional parameters that provide more
|
|
|
2245 control over which extents are mapped.
|
|
|
2246
|
|
|
2247 `map-extents' deals better with changes made to extents in the
|
|
|
2248 buffer being mapped over.
|
|
|
2249
|
|
|
2250 A new function `mapcar-extents' (an alternative to `map-extents') has
|
|
|
2251 been provided and should be easier to use than `map-extents'.
|
|
|
2252
|
|
|
2253
|
|
|
2254
|
|
|
2255 *** Faces
|
|
|
2256 ---------
|
|
|
2257
|
|
|
2258 Faces can now be buffer-local, window-local, and device-local as well
|
|
|
2259 as frame-local, and can be further restricted to a particular device
|
|
|
2260 type or class. The way in which faces can be controlled is now based
|
|
|
2261 on the general and powerful specifier mechanism; see above.
|
|
|
2262
|
|
|
2263 The new function `set-face-property' generalizes `set-face-font',
|
|
|
2264 `set-face-foreground', etc. and takes many new optional arguments, in
|
|
|
2265 accordance with the new specifier mechanism.
|
|
|
2266
|
|
|
2267 The new functions `face-property' and `face-property-instance'
|
|
|
2268 generalize `face-font', `face-foreground', etc. and take many new
|
|
|
2269 optional arguments, in accordance with the new specifier mechanism.
|
|
|
2270 (`face-property' returns the value, if any, that was specified for a
|
|
|
2271 particular locale, and `face-property-instance' returns the actual
|
|
|
2272 value that will be used for display. See the section on specifiers.)
|
|
|
2273
|
|
|
2274 The functions `face-font', `face-foreground', `face-background',
|
|
|
2275 `set-face-font', `set-face-foreground', `set-face-background',
|
|
|
2276 etc. are now convenience functions, trivially implemented using
|
|
|
2277 `face-property' and `set-face-property' and take new optioanl
|
|
|
2278 arguments in accordance with those functions. New convenience
|
|
|
2279 functions `face-font-instance', `face-foreground-instance',
|
|
|
2280 `face-background-instance', etc. are provided and are trivially
|
|
|
2281 implemented using `face-property-instance'.
|
|
|
2282
|
|
|
2283 Inheritance of face properties can now be specified. Each individual
|
|
|
2284 face property can inherit differently from other properties, or not
|
|
|
2285 inherit at all.
|
|
|
2286
|
|
|
2287 You can set user-defined properties on faces using
|
|
|
2288 `set-face-property'.
|
|
|
2289
|
|
|
2290 You can create "temporary" faces, which are faces that disappear
|
|
|
2291 when they are no longer in use. This is as opposed to normal
|
|
|
2292 faces, which stay around forever.
|
|
|
2293
|
|
|
2294 The function `make-face' takes a new optional argument specifying
|
|
|
2295 whether a face should be permanent or temporary, and returns the
|
|
|
2296 actual face object rather than the face symbol, as in previous
|
|
|
2297 versions of XEmacs.
|
|
|
2298
|
|
|
2299 The function `face-list' takes a new optional argument specifying
|
|
|
2300 whether permanent, temporary, or both kinds of faces should be
|
|
|
2301 returned.
|
|
|
2302
|
|
|
2303 Faces have new TTY-specific properties: `highlight', `reverse',
|
|
|
2304 `alternate', `blinking', and `dim'.
|
|
|
2305
|
|
|
2306 Redisplay is smarter about dealing with face changes: changes to a
|
|
|
2307 particular face no longer cause all frames to be cleared and
|
|
|
2308 redisplayed.
|
|
|
2309
|
|
|
2310 The Edit-Faces package is provided for interactively changing faces.
|
|
|
2311 A menu item on the options menu is provided for this.
|
|
|
2312
|
|
|
2313 New functions are provided for retrieving the ascent, descent, height,
|
|
|
2314 and width of a character in a particular face.
|
|
|
2315
|
|
|
2316
|
|
|
2317
|
|
|
2318 *** Fonts, Colors
|
|
|
2319 -----------------
|
|
|
2320
|
|
70
|
2321 ** INCOMPATIBLE CHANGE **: The old "font" and "pixel" objects are gone.
|
|
0
|
2322 In place are new objects "font specifier", "font instance", "color
|
|
|
2323 specifier", and "color instance". Functions `font-name', `pixel-name'
|
|
|
2324 (an obsolete alias for `color-name'), etc. are now convenience
|
|
|
2325 functions for working with font and color specifiers. Old code that
|
|
|
2326 is not too sophisticated about working with font and pixel objects may
|
|
|
2327 still work, though. (For example, the idiom `(font-name (face-font
|
|
|
2328 'default))' still works.)
|
|
|
2329
|
|
|
2330 You can now extract the RGB components of a color-instance object
|
|
|
2331 (similar to the old pixel object) with the function
|
|
|
2332 `color-instance-rgb-components'. There is also a convenience function
|
|
|
2333 `color-rgb-components' for working with color specifiers.
|
|
|
2334
|
|
|
2335 If there are no more colors available in the colormap, the nearest
|
|
|
2336 existing color will be used when allocating a new color.
|
|
|
2337
|
|
|
2338
|
|
|
2339
|
|
|
2340 *** Frames
|
|
|
2341 ----------
|
|
|
2342
|
|
|
2343 What used to be called "screens" are now called "frames", for clarity
|
|
|
2344 and consistency with GNU Emacs. Aliases are provided for all the old
|
|
|
2345 screen functions and variables, to avoid introducing a huge E-Lisp
|
|
|
2346 incompatibility.
|
|
|
2347
|
|
|
2348 The frame code has been merged with GNU Emacs 19.28, providing
|
|
|
2349 improved functionality for many functions.
|
|
|
2350
|
|
|
2351
|
|
|
2352
|
|
|
2353 *** Glyphs, Images, and Pixmaps
|
|
|
2354 -------------------------------
|
|
|
2355
|
|
|
2356 Glyphs (used in various places, i.e. as begin-glyphs and end-glyphs
|
|
|
2357 attached to extents and appearing in a buffer or in marginal
|
|
|
2358 annotations; as the truncator and continuor glyphs marking line wrap
|
|
|
2359 or truncation; as an overlay at the beginning of a line; as the
|
|
|
2360 displayable element in a toolbar button; etc.) can now be
|
|
|
2361 buffer-local, window-local, frame-local, and device-local, and can be
|
|
|
2362 further restricted to a particular device type or class. The way in
|
|
|
2363 which faces can be controlled is now based on the general and powerful
|
|
|
2364 specifier mechanism; see above.
|
|
|
2365
|
|
70
|
2366 ** INCOMPATIBLE CHANGE **: The glyph and pixmap API has been completely
|
|
0
|
2367 overhauled. A new Lisp object "glyph" is provided and should be used
|
|
|
2368 where the old "pixmap" object would have been used. The pixmap object
|
|
|
2369 exists no longer. There are also new Lisp objects "image specifier"
|
|
|
2370 and "image instance" (an image-instance is the closest equivalent to
|
|
|
2371 what a pixmap object was). More work on glyphs and images is slated
|
|
|
2372 for 19.13. The glyph and image docs in the Lisp Reference Manual are
|
|
|
2373 incomplete and will be finished in 19.13.
|
|
|
2374
|
|
|
2375 The new function `set-glyph-property' allows setting of all the
|
|
|
2376 glyph properties (`baseline', `contrib-p', etc.). Convenience
|
|
|
2377 functions for particular properties are also provided, just like
|
|
|
2378 for faces.
|
|
|
2379
|
|
|
2380 You can set user-defined properties on glyphs using the new function
|
|
|
2381 `set-glyph-property'.
|
|
|
2382
|
|
|
2383 When displaying pixmaps, existing, closest-matching colors will be
|
|
|
2384 used if the colormap is full.
|
|
|
2385
|
|
|
2386 If the compface library is compiled into XEmacs, there is built-in
|
|
|
2387 support for displaying X-Face bitmaps. (These are typically small
|
|
|
2388 pictures of people's faces, included in a mail message through the
|
|
|
2389 X-Face: header.) VM and highlight-headers will automatically use the
|
|
|
2390 built-in X-Face support if it is available.
|
|
|
2391
|
|
|
2392 Annotations in the right margin (as well as the left margin) are now
|
|
|
2393 implemented. The left and right margin width functions have been
|
|
|
2394 superseded by the specifier variables `left-margin-width' and
|
|
|
2395 `right-margin-width', allowing much more flexible control through the
|
|
|
2396 specifier mechanism.
|
|
|
2397
|
|
70
|
2398 ** INCOMPATIBLE CHANGE **: The variable `use-left-overflow',
|
|
0
|
2399 for controlling annotations in the left margin, is now a specifier
|
|
|
2400 variable instead of a buffer-local variable. (There is also a new
|
|
|
2401 variable `use-right-overflow', that is complementary.)
|
|
|
2402
|
|
|
2403
|
|
|
2404
|
|
|
2405 *** Hashing
|
|
|
2406 -----------
|
|
|
2407
|
|
|
2408 Two new types of weak hashtables can be created: key-weak and
|
|
|
2409 value-weak. In a key-weak hashtable, an entry remains around
|
|
|
2410 if its key is referenced elsewhere, regardless of whether this
|
|
|
2411 is also the case for the value. Value-weak hashtables are
|
|
|
2412 complementary. (This is as opposed to the traditional weak
|
|
|
2413 hashtables, where an entry remains around only if both the
|
|
|
2414 key and value are referenced elsewhere.) New functions
|
|
|
2415 `make-key-weak-hashtable' and `make-value-weak-hashtable'
|
|
|
2416 are provided for creating these hashtables.
|
|
|
2417
|
|
|
2418 The new function `md5' is provided for performing an MD5
|
|
|
2419 hash of an object. MD5 is a secure message digest algorithm
|
|
|
2420 developed by RSA, inc.
|
|
|
2421
|
|
|
2422
|
|
|
2423
|
|
|
2424 *** Keymaps
|
|
|
2425 -----------
|
|
|
2426
|
|
70
|
2427 The FSF GNU Emacs concept of `function-key-map' is now partially
|
|
0
|
2428 implemented. This allows conversion of function-key escape sequences
|
|
|
2429 such as `ESC [ 1 1 ~' into an equivalent human-readable keysym such as
|
|
|
2430 `F1'. This work will be completed in 19.14. The function-key map is
|
|
|
2431 device-local and controllable through the functions
|
|
|
2432 `device-function-key-map' and `set-device-function-key-map'.
|
|
|
2433
|
|
|
2434 `where-is-internal' now correctly searches minor-mode keymaps,
|
|
|
2435 extent-local keymaps, etc. As a side effect of this, menu items will
|
|
|
2436 now correctly show the keyboard equivalent for commands that are
|
|
|
2437 available through a minor-mode keymap, extent-local keymap, etc.
|
|
|
2438
|
|
70
|
2439 ** INCOMPATIBLE CHANGE **: The modifier key "Symbol" has
|
|
0
|
2440 been renamed to "Alt", for compatibility with the rest of the world.
|
|
|
2441 Keep in mind that on many keyboards, the key labelled "Alt" actually
|
|
|
2442 generates the "Meta" modifier. (On Sun keyboards, however, the key
|
|
|
2443 labelled "Alt" does indeed generate the "Alt" modifier, and the key
|
|
|
2444 labelled with a diamond generates the "Meta" modifier.)
|
|
|
2445
|
|
|
2446
|
|
|
2447
|
|
|
2448 *** Mouse, Active Region
|
|
|
2449 ------------------------
|
|
|
2450
|
|
|
2451 The mouse internals in mouse.el have been rewritten. Hooks have been
|
|
|
2452 provided for easier customization of mouse behavior. For example, you
|
|
|
2453 can now easily specify an action to be invoked on single-click
|
|
|
2454 (i.e. down-up without appreciable motion), double-click, drag-up, etc.
|
|
|
2455
|
|
70
|
2456 Some code from FSF GNU Emacs has been ported over, generalizing some of
|
|
0
|
2457 the X-specific mouse stuff.
|
|
|
2458
|
|
70
|
2459 ** INCOMPATIBLE CHANGE **: The function `set-mouse-position' accepts
|
|
0
|
2460 a window instead of a frame.
|
|
|
2461
|
|
|
2462 New function `mouse-position' that obsoletes and is more powerful than
|
|
|
2463 `read-mouse-position'.
|
|
|
2464
|
|
|
2465 New functions `mouse-pixel-positon' and `set-mouse-pixel-position' for
|
|
|
2466 working with pixels instead of characters.
|
|
|
2467
|
|
|
2468 The active (Zmacs) region is now highlighted using the `zmacs-region-face'
|
|
|
2469 instead of the `primary-selection-face'; this generalizes what used
|
|
|
2470 to be X-specific.
|
|
|
2471
|
|
|
2472 New functions `region-active-p', `region-exists-p', and `activate-region'
|
|
|
2473 provide a uniform API for dealing with the region irrespective of
|
|
|
2474 whether the variable `zmacs-regions' is set.
|
|
|
2475
|
|
|
2476 XEmacs is now a better X citizen with respect to the primary selection:
|
|
|
2477 it does not stomp on the primary selection quite so much. This makes
|
|
|
2478 things more manageable if you set `zmacs-regions' to nil.
|
|
|
2479
|
|
|
2480
|
|
|
2481
|
|
|
2482 *** Processes
|
|
|
2483 -------------
|
|
|
2484
|
|
|
2485 Various process race conditions and bugs have been fixed. Problems
|
|
|
2486 with process termination not getting noticed until much later (if at
|
|
|
2487 all) should be gone now, as well as problems with zombie processes
|
|
|
2488 under some systems.
|
|
|
2489
|
|
|
2490 SOCKS support is now included. SOCKS is a package that allows hosts
|
|
|
2491 behind a firewall to gain full access to the Internet without
|
|
|
2492 requiring direct IP reachability.
|
|
|
2493
|
|
|
2494
|
|
|
2495
|
|
|
2496 *** Windows
|
|
|
2497 -----------
|
|
|
2498
|
|
|
2499 Windows 95 is still not out yet.
|
|
|
2500
|
|
70
|
2501 ** INCOMPATIBLE CHANGE **: The functions `locate-window-from-coordinates'
|
|
0
|
2502 and `window-edges' have been eliminated. It no longer makes sense to
|
|
|
2503 work with windows in terms of character positions, because windows can
|
|
|
2504 (and often do) have many differently-sized fonts in them, because the
|
|
|
2505 3-D modeline is not exactly one line high, etc.
|
|
|
2506
|
|
|
2507 The new functions `window-pixel-edges', `window-highest-p',
|
|
|
2508 `window-lowest-p', `frame-highest-window', and `frame-lowest-window'
|
|
|
2509 are provided as substitutes for the above-mentioned, deleted
|
|
|
2510 functions.
|
|
|
2511
|
|
|
2512 The function `window-end' now takes an optional GUARANTEE argument
|
|
|
2513 that will ensure that the value is actually correct as of the next
|
|
|
2514 redisplay.
|
|
|
2515
|
|
|
2516 The window code has been merged with GNU Emacs 19.28, providing
|
|
|
2517 improved functionality for many functions.
|
|
|
2518
|
|
|
2519
|
|
|
2520
|
|
|
2521 *** System-Specific Information
|
|
|
2522 -------------------------------
|
|
|
2523
|
|
|
2524 Georg Nikodym's dynodump package is provided, for proper unexec()ing
|
|
|
2525 on Solaris systems. Executables built on Solaris 2.3 can now run on
|
|
|
2526 Solaris 2.4 without crashing; similarly with executables built on one
|
|
|
2527 type of Sun machine and run on another.
|
|
|
2528
|
|
|
2529 AIX 4.x is supported.
|
|
|
2530
|
|
|
2531 The NeXTstep operating system is supported in TTY mode (this is still
|
|
|
2532 in beta). There are plans to port XEmacs to the NeXTstep window
|
|
|
2533 system, but it may be awhile before this is complete.
|
|
|
2534
|
|
|
2535 Problems with the `round' function causing arithmetic errors on HPUX 9
|
|
|
2536 have been fixed.
|
|
|
2537
|
|
|
2538 You can now build XEmacs as an ELF executable on Linux systems that
|
|
|
2539 support ELF.
|
|
|
2540
|
|
|
2541 Various other new system configurations are supported.
|
|
|
2542
|
|
|
2543
|
|
|
2544
|
|
70
|
2545 *** Packages
|
|
|
2546 ------------
|
|
|
2547
|
|
|
2548 Most packages have been updated to the latest available versions.
|
|
|
2549
|
|
|
2550
|
|
|
2551 Some of the new Emacs Lisp packages ---
|
|
|
2552
|
|
|
2553 Hyperbole: the everyday information manager. Provides a Rolodex,
|
|
|
2554 allows links to be embedded in text, etc.
|
|
|
2555
|
|
|
2556 OOBR: a sophisticated class browser for object-oriented languages.
|
|
|
2557
|
|
|
2558 viper: a better VI emulator that allows Emacs and VI features
|
|
|
2559 to coexist happily.
|
|
|
2560
|
|
|
2561 hm--html-menus: a sophisticated package for editing HTML code,
|
|
|
2562 from Heiko Muenkel.
|
|
|
2563
|
|
|
2564 ksh-mode.el: for editing shell scripts.
|
|
|
2565
|
|
|
2566 lazy-lock.el: a lazy, on-the-fly fontifier.
|
|
|
2567
|
|
|
2568 paren.el: an improved matching paren highlighter
|
|
|
2569
|
|
|
2570
|
|
|
2571
|
|
|
2572 Major changes to existing packages --
|
|
|
2573
|
|
|
2574 VM: has a toolbar, many other nice features.
|
|
|
2575
|
|
|
2576 w3: has a toolbar, many other nice features.
|
|
|
2577
|
|
|
2578 ediff: provides three-way merging, has a better user interface.
|
|
|
2579
|
|
|
2580 info: has a toolbar.
|
|
|
2581
|
|
|
2582 highlight-headers.el: now highlights URL's and makes them active so
|
|
|
2583 that when clicked either Netscape 1.1 is called
|
|
|
2584 or Emacs W3 is run.
|
|
|
2585
|
|
0
|
2586
|
|
|
2587 ** Major Differences Between 19.10 and 19.11
|
|
|
2588 ============================================
|
|
70
|
2589
|
|
0
|
2590 The name has changed from "Lucid Emacs" to "XEmacs". Along with this is a
|
|
|
2591 new canonical ftp site: cs.uiuc.edu:/pub/xemacs.
|
|
|
2592
|
|
|
2593 XEmacs now has its very own World Wide Web page! It contains a
|
|
|
2594 complete list of the FTP distribution sites, the most recent FAQ,
|
|
|
2595 pointers to Emacs Lisp packages not included with the distribution, and
|
|
|
2596 other useful stuff. Check it out at http://xemacs.cs.uiuc.edu/.
|
|
|
2597
|
|
|
2598 A preliminary New Users Guide.
|
|
|
2599
|
|
|
2600 cc-mode.el now provides the default C, C++ and Objective-C modes.
|
|
|
2601
|
|
|
2602 The primary goal of this release is stability. Very few new features have
|
|
|
2603 been introduced but lots of bugs have been fixed. Many of the Emacs Lisp
|
|
|
2604 packages have been updated.
|
|
|
2605
|
|
|
2606 Some of the new Emacs Lisp packages ---
|
|
|
2607
|
|
|
2608 tcl-mode.el: major mode for editing TCL code
|
|
|
2609
|
|
|
2610 fast-lock.el: saves and restores font-lock highlighting, greatly
|
|
|
2611 reducing the time necessary for loading a font-lock'ed
|
|
|
2612 file
|
|
|
2613
|
|
|
2614 ps-print.el: prints buffers to Postscript printers preserving the
|
|
|
2615 buffer's bold and italic text attributes
|
|
|
2616
|
|
|
2617 toolbar.el: provides a "fake" toolbar for use with XEmacs (an
|
|
|
2618 integrated one will be included with 19.12)
|
|
|
2619
|
|
|
2620
|
|
|
2621 ** Major Differences Between 19.9 and 19.10
|
|
|
2622 ===========================================
|
|
|
2623
|
|
|
2624 The GNU `configure' system is now used to build lemacs.
|
|
|
2625
|
|
|
2626 The Emacs Manual and Emacs Lisp Reference Manual now document version 19.10.
|
|
|
2627 If you notice any errors, please let us know.
|
|
|
2628
|
|
|
2629 When pixmaps are displayed in a buffer, they contribute to the line height -
|
|
|
2630 that is, if the glyph is taller than the rest of the text on the line, the
|
|
|
2631 line will be as tall as necessary to display the glyph.
|
|
|
2632
|
|
|
2633 In addition to using arbitrary sound files as emacs beeps, one can control
|
|
|
2634 the pitch and duration of the standard X beep, on X servers which allow that
|
|
|
2635 (Note: most don't.)
|
|
|
2636
|
|
|
2637 There is support for playing sounds on systems with NetAudio servers.
|
|
|
2638
|
|
|
2639 Minor modes may have mode-specific key bindings; keymaps may have an arbitrary
|
|
|
2640 number of parent maps.
|
|
|
2641
|
|
|
2642 Menus can have toggle and radio buttons in them.
|
|
|
2643
|
|
|
2644 There is a font selection menu.
|
|
|
2645
|
|
|
2646 Some default key bindings have changed to match FSF19; the new bindings are
|
|
|
2647
|
|
|
2648 Screen-related commands:
|
|
|
2649 C-x 5 2 make-screen
|
|
|
2650 C-x 5 0 delete-screen
|
|
|
2651 C-x 5 b switch-to-buffer-other-screen
|
|
|
2652 C-x 5 f find-file-other-screen
|
|
|
2653 C-x 5 C-f find-file-other-screen
|
|
|
2654 C-x 5 m mail-other-screen
|
|
|
2655 C-x 5 o other-screen
|
|
|
2656 C-x 5 r find-file-read-only-other-screen
|
|
|
2657 Abbrev-related commands:
|
|
|
2658 C-x a l add-mode-abbrev
|
|
|
2659 C-x a C-a add-mode-abbrev
|
|
|
2660 C-x a g add-global-abbrev
|
|
|
2661 C-x a + add-mode-abbrev
|
|
|
2662 C-x a i g inverse-add-global-abbrev
|
|
|
2663 C-x a i l inverse-add-mode-abbrev
|
|
|
2664 C-x a - inverse-add-global-abbrev
|
|
|
2665 C-x a e expand-abbrev
|
|
|
2666 C-x a ' expand-abbrev
|
|
|
2667 Register-related commands:
|
|
|
2668 C-x r C-SPC point-to-register
|
|
|
2669 C-x r SPC point-to-register
|
|
|
2670 C-x r j jump-to-register
|
|
|
2671 C-x r s copy-to-register
|
|
|
2672 C-x r x copy-to-register
|
|
|
2673 C-x r i insert-register
|
|
|
2674 C-x r g insert-register
|
|
|
2675 C-x r r copy-rectangle-to-register
|
|
|
2676 C-x r c clear-rectangle
|
|
|
2677 C-x r k kill-rectangle
|
|
|
2678 C-x r y yank-rectangle
|
|
|
2679 C-x r o open-rectangle
|
|
|
2680 C-x r t string-rectangle
|
|
|
2681 C-x r w window-configuration-to-register
|
|
|
2682 Narrowing-related commands:
|
|
|
2683 C-x n n narrow-to-region
|
|
|
2684 C-x n w widen
|
|
|
2685 Other changes:
|
|
|
2686 C-x 3 split-window-horizontally (was undefined)
|
|
|
2687 C-x - shrink-window-if-larger-than-buffer
|
|
|
2688 C-x + balance-windows
|
|
|
2689
|
|
70
|
2690 The variable allow-deletion-of-last-visible-screen has been removed, since
|
|
0
|
2691 it was widely hated. You can now always delete the last visible screen if
|
|
|
2692 there are other iconified screens in existence.
|
|
|
2693
|
|
|
2694 ToolTalk support is provided.
|
|
|
2695
|
|
|
2696 An Emacs screen can be placed within an "external client widget" managed
|
|
|
2697 by another application. This allows an application to use an Emacs screen
|
|
|
2698 as its text pane rather than the standard Text widget that is provided
|
|
|
2699 with Motif or Athena.
|
|
|
2700
|
|
|
2701 Additional compatibility with Epoch is provided (though this is not yet
|
|
|
2702 complete.)
|
|
|
2703
|
|
|
2704
|
|
|
2705 ** Major Differences Between 19.8 and 19.9
|
|
|
2706 ==========================================
|
|
|
2707
|
|
|
2708 Scrollbars! If you have Motif, these are real Motif scrollbars; otherwise,
|
|
|
2709 Athena scrollbars are used. They obey all the usual resources of their
|
|
|
2710 respective toolkits.
|
|
|
2711
|
|
2
|
2712 There is now an implementation of dialog boxes based on the Athena
|
|
0
|
2713 widgets, as well as the existing Motif implementation.
|
|
|
2714
|
|
70
|
2715 This release works with Motif 1.2 as well as 1.1. If you link with Motif,
|
|
0
|
2716 you do not also need to link with Athena.
|
|
|
2717
|
|
|
2718 If you compile lwlib with both USE_MOTIF and USE_LUCID defined (which is the
|
|
|
2719 recommended configuration) then the Lucid menus will draw text using the Motif
|
|
|
2720 string-drawing library, instead of the Xlib one. The reason for this is that
|
|
|
2721 one can take advantage of the XmString facilities for including non-Latin1
|
|
|
2722 characters in resource specifications. However, this is a user-visible change
|
|
70
|
2723 in that, in this configuration, the menubar will use the "*fontList" resource
|
|
0
|
2724 in preference to the "*font" resource, if it is set.
|
|
|
2725
|
|
|
2726 It's possible to make extents which are copied/pasted by kill and undo.
|
|
|
2727 There is an implementation of FSF19-style text properties based on this.
|
|
|
2728
|
|
|
2729 There is a new variable, minibuffer-max-depth, which is intended to circumvent
|
|
|
2730 a common source of confusion among new Emacs users. Since, under a window
|
|
|
2731 system, it's easy to jump out of the minibuffer (by doing M-x, then getting
|
|
|
2732 distracted, and clicking elsewhere) many, many novice users have had the
|
|
|
2733 problem of having multiple minibuffers build up, even to the point of
|
|
|
2734 exhausting the lisp stack. So the default behavior is to disallow the
|
|
|
2735 minibuffer to ever be reinvoked while active; if you attempt to do so, you
|
|
|
2736 will be prompted about it.
|
|
|
2737
|
|
|
2738 There is a new variable, teach-extended-commands-p, which if set, will cause
|
|
|
2739 `M-x' to remind you of any key bindings of the command you just invoked the
|
|
|
2740 "long way."
|
|
|
2741
|
|
|
2742 There are menus in Dired, Tar, Comint, Compile, and Grep modes.
|
|
|
2743
|
|
|
2744 There is a menu of window management commands on the right mouse button over
|
|
|
2745 the modelines.
|
|
|
2746
|
|
70
|
2747 Popup menus now have titles at the top; this is controlled by the new
|
|
0
|
2748 variable `popup-menu-titles'.
|
|
|
2749
|
|
|
2750 The `Find' key on Sun keyboards will search for the next (or previous)
|
|
|
2751 occurrence of the selected text, as in OpenWindows programs.
|
|
|
2752
|
|
|
2753 The `timer' package has been renamed to `itimer' to avoid a conflict with
|
|
|
2754 a different package called `timer'.
|
|
|
2755
|
|
|
2756 VM 5.40 is included.
|
|
|
2757
|
|
|
2758 W3, the emacs interface to the World Wide Web, is included.
|
|
|
2759
|
|
|
2760 Felix Lee's GNUS speedups have been installed, including his new version of
|
|
|
2761 nntp.el which makes GNUS efficiently utilize the NNTP XOVER command if
|
|
70
|
2762 available (which is much faster.)
|
|
0
|
2763
|
|
|
2764 GNUS should also be much friendlier to new users: it starts up much faster,
|
|
|
2765 and doesn't (necessarily) subscribe you to every single newsgroup.
|
|
|
2766
|
|
|
2767 The byte-compiler issues a new class of warnings: variables which are
|
|
|
2768 bound but not used. This is merely an advisory, and does not mean the
|
|
|
2769 code is incorrect; you can disable these warnings in the usual way with
|
|
|
2770 the `byte-compiler-options' macro.
|
|
|
2771
|
|
|
2772 the `start-open' and `end-open' extent properties, for specifying whether
|
|
|
2773 characters inserted exactly at a boundary of an extent should go into the
|
|
|
2774 extent or out of it, now work correctly.
|
|
|
2775
|
|
|
2776 The `extent-data' slot has been generalized/replaced with a property list,
|
|
|
2777 so it's easier to attach arbitrary data to extent objects.
|
|
|
2778
|
|
|
2779 The `event-modifiers' and `event-modifier-bits' functions work on motion
|
|
|
2780 events as well as other mouse and keyboard events.
|
|
|
2781
|
|
|
2782 Forms-mode uses fonts and read-only regions.
|
|
|
2783
|
|
|
2784 The behavior of the -geometry command line option should be correct now.
|
|
|
2785
|
|
|
2786 The `iconic' screen parameter works when passed to x-create-screen.
|
|
|
2787
|
|
|
2788 The user's manual now documents Lucid Emacs 19.9.
|
|
|
2789
|
|
|
2790 The relocating buffer allocator is turned on by default; this means that when
|
|
70
|
2791 buffers are killed, their storage will be returned to the operating system,
|
|
0
|
2792 and the size of the emacs process will shrink.
|
|
|
2793
|
|
|
2794 CAVEAT: code which contains calls to certain `face' accessor functions will
|
|
|
2795 need to be recompiled by version 19.9 before it will work. The functions
|
|
|
2796 whose callers must be recompiled are: face-font, face-foreground,
|
|
|
2797 face-background, face-background-pixmap, and face-underline-p. The symptom
|
|
|
2798 of this problem is the error "Wrong type argument, arrayp, #<face ... >".
|
|
|
2799 The .elc files generated by version 19.9 will work in 19.6 and 19.8, but
|
|
|
2800 older .elc files which contain calls to these functions will not work in 19.9.
|
|
|
2801
|
|
|
2802 Work In Progress:
|
|
|
2803
|
|
|
2804 - We have been in the process of internationalizing Lucid Emacs. This code is
|
|
|
2805 ***not*** ready for general use yet. However, the code is included (and
|
|
|
2806 turned off by default) in this release.
|
|
|
2807
|
|
|
2808 - If you define I18N2 at compile-time, then sorting/collation will be done
|
|
|
2809 according to the locale returned by setlocale().
|
|
|
2810
|
|
|
2811 - If you define I18N3 at compile-time, then all messages printed by lemacs
|
|
|
2812 will be filtered through the gettext() library routine, to enable the use
|
|
|
2813 of locale-specific translation catalogues. The current implementation of
|
|
70
|
2814 this is quite dependent on Solaris 2, and has a very large impact on
|
|
0
|
2815 existing code, therefore we are going to be making major changes soon.
|
|
|
2816 (You'll notice calls to `gettext' and `GETTEXT' scattered around much of
|
|
|
2817 the lisp and C code; ignore it, this will be going away.)
|
|
|
2818
|
|
|
2819 - If you define I18N4 at compile-time, then lemacs will internally use a
|
|
|
2820 wide representation of characters, enabling the use of large character
|
|
70
|
2821 sets such as Kanji. This code is very OS dependent: it requires X11R5,
|
|
0
|
2822 and several OS-supplied library routines for reading and writing wide
|
|
|
2823 characters (getwc(), putwc(), and a few others.) Performance is also a
|
|
|
2824 problem. This code is also scheduled for a major overhaul, with the
|
|
70
|
2825 intent of improving performance and portability.
|
|
0
|
2826
|
|
|
2827 Our eventual goal is to merge with MULE, or at least provide the same base
|
|
70
|
2828 level of functionality. If you would like to help out with this, let us
|
|
0
|
2829 know.
|
|
|
2830
|
|
70
|
2831 - Other work-in-progress includes Motif drag-and-drop support, ToolTalk
|
|
|
2832 support, and support for embedding an Emacs widget inside another
|
|
0
|
2833 application (where it can function as that other application's text-entry
|
|
|
2834 area). This code has not been extensively tested, and may (or may not)
|
|
70
|
2835 have portability problems, but it's there for the adventurous. Comments,
|
|
0
|
2836 suggestions, bug reports, and especially fixes are welcome. But have no
|
|
|
2837 expectations that this experimental code will work at all.
|
|
|
2838
|
|
|
2839
|
|
|
2840 ** Major Differences Between 19.6 and 19.8
|
|
|
2841 ==========================================
|
|
|
2842
|
|
|
2843 There were almost no differences between versions 19.6 and 19.7; version 19.7
|
|
|
2844 was a bug-fix release that was distributed with Energize 2.1.
|
|
|
2845
|
|
|
2846 Lucid Emacs 19.8 represents the first stage of the Lucid Emacs/Epoch merger.
|
|
|
2847 The redisplay engine now in lemacs is an improved descendant of the Epoch
|
|
|
2848 redisplay. As a result, many bugs have been eliminated, and several disabled
|
|
|
2849 features have been re-enabled. Notably:
|
|
|
2850
|
|
|
2851 Selective display (and outline-mode) work.
|
|
|
2852
|
|
|
2853 Horizontally split windows work.
|
|
|
2854
|
|
|
2855 The height of a line is the height of the tallest font displayed on that line;
|
|
|
2856 it is possible for a screen to display lines of differing heights. (Previously,
|
|
|
2857 the height of all lines was the height of the tallest font loaded.)
|
|
|
2858
|
|
|
2859 There is lisp code to scale fonts up and down, for example, to load the next-
|
|
|
2860 taller version of a font.
|
|
|
2861
|
|
|
2862 There is a new internal representation for lisp objects, giving emacs-lisp 28
|
|
|
2863 bit integers and a 28 bit address space, up from the previous maximum of 26.
|
|
|
2864 We expect eventually to increase this to 30 bit integers and a 32 bit address
|
|
|
2865 space, eliminating the need for DATA_SEG_BITS on some architectures. (On 64
|
|
|
2866 bit machines, add 32 to all of these numbers.)
|
|
|
2867
|
|
|
2868 GC performance is improved.
|
|
|
2869
|
|
|
2870 Various X objects (fonts, colors, cursors, pixmaps) are accessible as first-
|
|
|
2871 class lisp objects, with finalization.
|
|
|
2872
|
|
|
2873 An alternate interface to embedding images in the text is provided, called
|
|
|
2874 "annotations." You may create an "annotation margin" which is whitespace at
|
|
|
2875 the left side of the screen that contains only annotations, not buffer text.
|
|
|
2876
|
|
|
2877 When using XPM files, one can specify the values of logical color names to be
|
|
|
2878 used when loading the files.
|
|
|
2879
|
|
|
2880 It is possible to resize windows by dragging their modelines up and down. More
|
|
|
2881 generally, it is possible to add bindings for mouse gestures on the modelines.
|
|
|
2882
|
|
|
2883 There is support for playing sound files on HP machines.
|
|
|
2884
|
|
|
2885 ILISP version 5.5 is included.
|
|
|
2886
|
|
|
2887 The Common Lisp #' read syntax is supported (#' is to "function" as ' is to
|
|
|
2888 "quote".)
|
|
|
2889
|
|
|
2890 The `active-p' slot of menu items is now evaluated, so one can put arbitrary
|
|
|
2891 lisp code in a menu to decide whether that item should be selectable, rather
|
|
|
2892 than doing this with an `activate-menubar-hook'.
|
|
|
2893
|
|
|
2894 The X resource hierarchy has changed slightly, to be more consistent. It used
|
|
|
2895 to be
|
|
|
2896 argv[0] SCREEN-NAME pane screen
|
|
|
2897 ApplicationShell EmacsShell Paned EmacsFrame
|
|
|
2898
|
|
|
2899 now it is
|
|
|
2900
|
|
|
2901 argv[0] shell pane SCREEN-NAME
|
|
|
2902 ApplicationShell EmacsShell Paned EmacsFrame
|
|
|
2903
|
|
|
2904 The Lucid Emacs sources have been largely merged with FSF version 19; this
|
|
|
2905 means that the lisp library contains the most recent releases of various
|
|
|
2906 packages, and many new features of FSF 19 have been incorporated.
|
|
|
2907
|
|
|
2908 Because of this, the lemacs sources should also be substantially more portable.
|
|
|
2909
|
|
|
2910
|
|
|
2911 ** Major Differences Between 19.4 and 19.6
|
|
|
2912 ==========================================
|
|
|
2913
|
|
|
2914 There were almost no differences between versions 19.4 and 19.5; we fixed
|
|
|
2915 a few minor bugs and repacked 19.4 as 19.5 for a CD-ROM that we gave away
|
|
|
2916 as a trade show promotion.
|
|
|
2917
|
|
|
2918 The primary goal of the 19.6 release is stability, rather than improved
|
|
|
2919 functionality, so there aren't many user-visible changes. The most notable
|
|
|
2920 changes are:
|
|
|
2921
|
|
|
2922 - The -geometry command-line option now correctly overrides geometry
|
|
|
2923 specifications in the resource database.
|
|
|
2924 - The `width' and `height' screen-parameters work.
|
|
|
2925 - Font-lock-mode considers the comment start and end characters to be
|
|
|
2926 a part of the comment.
|
|
|
2927 - The lhilit package has been removed. Use font-lock-mode instead.
|
|
|
2928 - vm-isearch has been fixed to work with isearch-mode.
|
|
|
2929 - new versions of ispell and calendar.
|
|
|
2930 - sccs.el has menus.
|
|
|
2931
|
|
|
2932 Lots of bugs were fixed, including the problem that lemacs occasionally
|
|
|
2933 grabbed the keyboard focus.
|
|
|
2934
|
|
|
2935 Also, as of Lucid Emacs 19.6 and Energize 2.0 (shipping now) it is possible
|
|
|
2936 to compile the public release of Lucid Emacs with support for Energize; so
|
|
|
2937 now Energize users will be able to build their own Energize-aware versions
|
|
|
2938 of lemacs, and will be able to use newer versions of lemacs as they are
|
|
|
2939 released to the net. (Of course, this is not behavior covered by your
|
|
|
2940 Energize support contract; you do it at your own risk.)
|
|
|
2941
|
|
|
2942 I have not incorporated all portability patches that I have been sent since
|
|
|
2943 19.4; I will try to get to them soon. However, if you need to make any
|
|
|
2944 changes to lemacs to get it to compile on your system, it would be quite
|
|
|
2945 helpful if you would send me context diffs (diff -c) against version 19.6.
|
|
|
2946
|
|
|
2947
|
|
|
2948 ** Major Differences Between 19.3 and 19.4
|
|
|
2949 ==========================================
|
|
|
2950
|
|
|
2951 Prototypes have been added for all functions. Emacs compiles in the strict
|
|
|
2952 ANSI modes of lcc and gcc, so portability should be vastly improved.
|
|
|
2953
|
|
70
|
2954 Many many many many core leaks have been plugged, especially in screen
|
|
0
|
2955 creation and deletion.
|
|
|
2956
|
|
|
2957 The float support reworked to be more portable and ANSI conformant. This
|
|
70
|
2958 resulted in these new configuration parameters: HAVE_INVERSE_HYPERBOLIC,
|
|
|
2959 HAVE_CBRT, HAVE_RINT, FLOAT_CHECK_ERRNO, FLOAT_CATCH_SIGILL,
|
|
0
|
2960 FLOAT_CHECK_DOMAIN. Let us know if you had to change the defaults on your
|
|
|
2961 architecture.
|
|
|
2962
|
|
70
|
2963 The SunOS unexec has been rewritten, and now works with either static or
|
|
0
|
2964 dynamic libraries, depending on whether -Bstatic or -Bdynamic were specified
|
|
|
2965 at link-time.
|
|
|
2966
|
|
|
2967 Small (character-sized) bitmaps can be mixed in with buffer text via the new
|
|
|
2968 functions set-extent-begin-glyph and set-extent-end-glyph. (This is actually
|
|
|
2969 a piece of functionality that Energize has been using for a while, but we've
|
|
|
2970 just gotten around to making it possible to use it without Energize. See how
|
|
|
2971 nice we are? Go buy our product.)
|
|
|
2972
|
|
|
2973 If compiled with Motif support, one can pop up dialog boxes from emacs lisp.
|
|
|
2974 We encourage someone to contribute Athena an version of this code; it
|
|
70
|
2975 shouldn't be much work.
|
|
0
|
2976
|
|
|
2977 If dialog boxes are available, then y-or-n-p and yes-or-no-p use dialog boxes
|
|
70
|
2978 instead of the minibuffer if invoked as a result of a command that was
|
|
0
|
2979 executed from a menu instead of from the keyboard.
|
|
|
2980
|
|
|
2981 Multiple screen support works better; check out doc of get-screen-for-buffer.
|
|
|
2982
|
|
|
2983 The default binding of backspace is the same as delete. (C-h is still help.)
|
|
|
2984
|
|
70
|
2985 A middle click while the minibuffer is active does completion if you click on
|
|
0
|
2986 a highlighted completion, otherwise it executes the global binding of button2.
|
|
|
2987
|
|
|
2988 New versions of Barry Warsaw's c++-mode and syntax.c. Font-lock-mode works
|
|
|
2989 with C++ mode now.
|
|
|
2990
|
|
|
2991 The semantics of activate-menubar-hook has changed; the functions are called
|
|
|
2992 with no arguments now.
|
|
|
2993
|
|
|
2994 `truename' no longer hacks the automounter; use directory-abbrev-alist instead.
|
|
|
2995
|
|
|
2996 Most minibuffer handling has been reimplemented in emacs-lisp.
|
|
|
2997
|
|
|
2998 There is now a builtin minibuffer history mechanism which replaces gmhist.
|
|
|
2999
|
|
|
3000
|
|
|
3001 ** Major Differences Between 19.2 and 19.3
|
|
|
3002 ==========================================
|
|
|
3003
|
|
|
3004 The ISO characters have correct case and syntax tables now, so the word-motion
|
|
|
3005 and case-converting commands work sensibly on them.
|
|
|
3006
|
|
|
3007 If you set ctl-arrow to an integer, you can control exactly which characters
|
|
|
3008 are printable. (There will be a less crufty way to do this eventually.)
|
|
|
3009
|
|
|
3010 Menubars can now be buffer local; the function set-screen-menubar no longer
|
|
70
|
3011 exists. Look at GNUS and VM for examples of how to do this, or read
|
|
0
|
3012 menubar.el.
|
|
|
3013
|
|
|
3014 When emacs is reading from the minibuffer with completions, any completions
|
|
|
3015 which are visible on the screen will highlight when the mouse moves over them;
|
|
|
3016 clicking middle on a completion is the same as typing it at the minibuffer.
|
|
|
3017 Some implications of this: The *Completions* buffer is always mousable. If
|
|
|
3018 you're using the completion feature of find-tag, your source code will be
|
|
70
|
3019 mousable when you type M-. Dired buffers will be mousable as soon as you
|
|
0
|
3020 type ^X^F. And so on.
|
|
|
3021
|
|
|
3022 The old isearch code has been replaced with a descendant of Dan LaLiberte's
|
|
|
3023 excellent isearch-mode; it is more customizable, and generally less bogus.
|
|
|
3024 You can search for "composed" characters. There are new commands, too; see
|
|
|
3025 the doc for ^S, or the NEWS file.
|
|
|
3026
|
|
|
3027 A patched GNUS 3.14 is included.
|
|
|
3028
|
|
|
3029 The user's manual now documents Lucid Emacs 19.3.
|
|
|
3030
|
|
|
3031 A few more modes have mouse and menu support.
|
|
|
3032
|
|
|
3033 The startup code should be a little more robust, and give you more reasonable
|
|
|
3034 error messages when things aren't installed quite right (instead of the
|
|
|
3035 ubiquitous "cannot open DISPLAY"...)
|
|
|
3036
|
|
|
3037 Subdirectories of the lisp directory whose names begin with a hyphen or dot
|
|
|
3038 are not automatically added to the load-path, so you can use this to avoid
|
|
|
3039 accidentally inflicting experimental software on your users.
|
|
|
3040
|
|
|
3041 I've tried to incorporate all of the portability patches that were sent to
|
|
70
|
3042 me; I tried to solve some of the problems in different ways than the
|
|
0
|
3043 patches did, so let me know if I missed something.
|
|
|
3044
|
|
|
3045 Some systems will need to define NEED_STRDUP, NEED_REALPATH, HAVE_DREM, or
|
|
|
3046 HAVE_REMAINDER in config.h. Really this should be done in the appropriate
|
|
|
3047 s- or m- files, but I don't know which systems need these and which don't.
|
|
|
3048 If yours does, let me know which file it should be in.
|
|
|
3049
|
|
|
3050 Check out these new packages:
|
|
|
3051
|
|
|
3052 blink-paren.el: causes the matching parenthesis to flash on and off whenever
|
|
|
3053 the cursor is sitting on a paren-syntax character.
|
|
|
3054
|
|
|
3055 pending-del.el: Certain commands implicitly delete the highlighted region:
|
|
|
3056 Typing a character when there is a highlighted region replaces
|
|
|
3057 that region with the typed character.
|
|
|
3058
|
|
|
3059 font-lock.el: A code-highlighting package, driven off of syntax tables, so
|
|
70
|
3060 that it understands block comments, strings, etc. The
|
|
0
|
3061 insertion hook is used to fontify text as you type it in.
|
|
|
3062
|
|
|
3063 shell-font.el: Displays your shell-buffer prompt in boldface.
|
