Mercurial > hg > xemacs-beta
view src/README @ 844:047d37eb70d7
[xemacs-hg @ 2002-05-16 13:30:23 by ben]
ui fixes for things that were bothering me
bytecode.c, editfns.c, lisp.h, lread.c: Fix save-restriction to use markers rather than pseudo-markers
(integers representing the amount of text on either side of the
region). That way, all inserts are handled correctly, not just
those inside old restriction.
Add buffer argument to save_restriction_save().
process.c: Clean up very dirty and kludgy code that outputs into a buffer --
use proper unwind protects, etc.
font-lock.c: Do save-restriction/widen around the function -- otherwise, incorrect
results will ensue when a buffer has been narrowed before a call to
e.g. `buffer-syntactic-context' -- something that happens quite often.
fileio.c: Look for a handler for make-temp-name.
window.c, winslots.h: Try to solve this annoying problem: have two frames displaying the
buffer, in different places; in one, temporarily switch away to
another buffer and then back -- and you've lost your position;
it's reset to the other one in the other frame. My current
solution involves window-level caches of buffers and points (also
a cache for window-start); when set-window-buffer is called, it
looks to see if the buffer was previously visited in the window,
and if so, uses the most recent point at that time. (It's a
marker, so it handles changes.)
#### Note: It could be argued that doing it on the frame level
would be better -- e.g. if you visit a buffer temporarily through
a grep, and then go back to that buffer, you presumably want the
grep's position rather than some previous position provided
everything was in the same frame, even though the grep was in
another window in the frame. However, doing it on the frame level
fails when you have two windows on the same frame. Perhaps we
keep both a window and a frame cache, and use the frame cache if
there are no other windows on the frame showing the buffer, else
the window's cache? This is probably something to be configurable
using a specifier. Suggestions please please please?
window.c: Clean up a bit code that deals with the annoyance of window-point
vs. point.
dialog.el: Function to ask a
multiple-choice question, automatically choosing a dialog box or
minibuffer representation as necessary. Generalized version of
yes-or-no-p, y-or-n-p.
files.el: Use get-user-response to ask "yes/no/diff" question when recovering.
"diff" means that a diff is displayed between the current file and the
autosave. (Converts/deconverts escape-quoted as necessary. No more
complaints from you, Mr. Turnbull!) One known problem: when a dialog
is used, it's modal, so you can't scroll the diff. Will fix soon.
lisp-mode.el: If we're filling a string, don't treat semicolon as a comment,
which would give very unfriendly results.
Uses `buffer-syntactic-context'.
simple.el: all changes back to the beginning. (Useful if you've saved the file
in the middle of the changes.)
simple.el: Add option kill-word-into-kill-ring, which controls whether words
deleted with kill-word, backward-kill-word, etc. are "cut" into the
kill ring, or "cleared" into nothingness. (My preference is the
latter, by far. I'd almost go so far as suggesting we make it the
default, as you can always select a word and then cut it if you want
it cut.)
menubar-items.el: Add option corresponding to kill-word-into-kill-ring.
| author | ben |
|---|---|
| date | Thu, 16 May 2002 13:30:58 +0000 |
| parents | abe6d1db359e |
| children | 304aebb79cd3 |
line wrap: on
line source
This directory contains the source files for the C component of XEmacs. Nothing in this directory is needed for using XEmacs once it is built and installed, if the dumped Emacs is copied elsewhere. See the files ../README and then ../INSTALL for installation instructions. Under Unix, the file `Makefile.in.in' is used as a template by the script `../configure' to produce `Makefile.in'. The same script then uses `cpp' to produce the machine-dependent `Makefile' from `Makefile.in'; `Makefile' is the file which actually controls the compilation of Emacs. Most of this should work transparently to the user; you should only need to run `../configure', and then type `make'. General changes for XEmacs: --------------------------- 1. Lisp objects. -- XFASTINT has been eliminated. Use of this expression as an lvalue is incompatible with the union form of Lisp objects, and use as an rvalue is likely to lead to errors and doesn't really save much time. Expressions of the form `XFASTINT (obj) = num;' get replaced by `obj = make_int (num);' or `XSETINT (obj, num);' and expressions of the form `num = XFASTINT (obj);' get replaced by `num = XINT (obj);'. Use Qzero in place of `make_int (0)'. -- Use of XTYPE gets replaced by the appropriate predicate. Using XTYPE only works for the small number of types that are not stored using the Lisp_Record type (int, cons, string, and vector). For example, `(XTYPE (foo) == Lisp_Buffer)' gets replaced by `(BUFFERP (foo))'. -- `XSET (obj, Lisp_Int, num)' gets replaced by `XSETINT (obj, num)', for consistency. -- Some occurrences of XSET need to get replaced by XSETR -- specifically, those where the type is not a primitive type (primitive types are int, cons, string, and vector). -- References to `XSTRING (obj)->size' get replaced with `XSTRING_LENGTH (obj)'. This is currently for cosmetic reasons but there may be other reasons in the future. (This change is currently incomplete in the source files.) 2. Storage classes: -- All occurrences of `register' should be replaced by `REGISTER'. It interferes with backtraces so we disable it if DEBUG_XEMACS is defined. 3. Errors, messages, I18N3 snarfing: -- Errors are continuable in XEmacs but are not in FSF Emacs. Therefore, it's important that functions do something reasonable if an error gets continued. If you want to signal a non- continuable error, the call to Fsignal() gets put inside a `while (1)' loop. To facilitate this, and also for proper I18N3 message snarfing, most calls to Fsignal() have been replaced by calls to signal_error(), signal_simple_error(), etc. Look at eval.c for a classification of various error functions. -- Constant strings occurring in source files need to get wrapped in a call to GETTEXT (or if inside of a call to `build_string', change that function to `build_translated_string') if they don't occur in certain places where the I18N3 message snarfer will see them. For a complete discussion of this, see the file lib-src/make-msgfile.lex. NOTE: I18N3 support is not currently working, so the above may or may not apply. Thus it is not a good idea to add random GETTEXTs, unless you really know what you are doing. -- Calls to `fprintf (stderr, ...)' and `printf (...)' get replaced with calls to `stderr_out' and `stdout_out'. This is for I18N3 message snarfing. 4. Initialization: -- FSF constructs like `obj = intern ("string"); staticpro (&obj);' get replaced by `defsymbol (&obj);'. This is for code cleanness and better purespace usage. -- FSF constructs like obj = intern ("error"); Fput (obj, Qerror_message, "message"); Fput (obj, Qerror_conditions, some list); get replaced by calls to deferror(). See the definition of deferror() for how the correct arguments to pass. This is for code cleanness and I18N3 message snarfing. -- Code in keys_of_foo() functions has been moved into Lisp.