diff options
Diffstat (limited to 'etc')
| -rw-r--r-- | etc/ChangeLog | 4 | ||||
| -rw-r--r-- | etc/DEBUG | 40 | ||||
| -rw-r--r-- | etc/NEWS | 20 | ||||
| -rw-r--r-- | etc/orgcard.tex | 4 |
4 files changed, 52 insertions, 16 deletions
diff --git a/etc/ChangeLog b/etc/ChangeLog index ae722f53ec..391c072ca7 100644 --- a/etc/ChangeLog +++ b/etc/ChangeLog @@ -1,3 +1,7 @@ +2006-03-15 Carsten Dominik <[email protected]> + + * orgcard.tex: Version number change only. + 2006-03-15 Nick Roberts <[email protected]> * DEBUG (Note): Describe features for debugging with GDB in Emacs. @@ -506,22 +506,44 @@ the machine where you started GDB and use the debugger from there. The array `last_marked' (defined on alloc.c) can be used to display up to 500 last objects marked by the garbage collection process. Whenever the garbage collector marks a Lisp object, it records the -pointer to that object in the `last_marked' array. The variable -`last_marked_index' holds the index into the `last_marked' array one -place beyond where the pointer to the very last marked object is -stored. +pointer to that object in the `last_marked' array, which is maintained +as a circular buffer. The variable `last_marked_index' holds the +index into the `last_marked' array one place beyond where the pointer +to the very last marked object is stored. The single most important goal in debugging GC problems is to find the Lisp data structure that got corrupted. This is not easy since GC changes the tag bits and relocates strings which make it hard to look at Lisp objects with commands such as `pr'. It is sometimes necessary to convert Lisp_Object variables into pointers to C struct's manually. -Use the `last_marked' array and the source to reconstruct the sequence -that objects were marked. -Once you discover the corrupted Lisp object or data structure, it is -useful to look at it in a fresh Emacs session and compare its contents -with a session that you are debugging. +Use the `last_marked' array and the source to reconstruct the sequence +that objects were marked. In general, you need to correlate the +values recorded in the `last_marked' array with the corresponding +stack frames in the backtrace, beginning with the innermost frame. +Some subroutines of `mark_object' are invoked recursively, others loop +over portions of the data structure and mark them as they go. By +looking at the code of those routines and comparing the frames in the +backtrace with the values in `last_marked', you will be able to find +connections between the values in `last_marked'. E.g., when GC finds +a cons cell, it recursively marks its car and its cdr. Similar things +happen with properties of symbols, elements of vectors, etc. Use +these connections to reconstruct the data structure that was being +marked, paying special attention to the strings and names of symbols +that you encounter: these strings and symbol names can be used to grep +the sources to find out what high-level symbols and global variables +are involved in the crash. + +Once you discover the corrupted Lisp object or data structure, grep +the sources for its uses and try to figure out what could cause the +corruption. If looking at the sources doesn;t help, you could try +setting a watchpoint on the corrupted data, and see what code modifies +it in some invalid way. (Obviously, this technique is only useful for +data that is modified only very rarely.) + +It is also useful to look at the corrupted object or data structure in +a fresh Emacs session and compare its contents with a session that you +are debugging. ** Debugging problems with non-ASCII characters @@ -159,6 +159,10 @@ in the other directories in `load-path'. (-L is short for --directory.) ** The command line option --no-windows has been changed to --no-window-system. The old one still works, but is deprecated. +--- +** If the environment variable DISPLAY specifies an unreachable X display, +Emacs will now startup as if invoked with the --no-window-system option. + +++ ** The -f option, used from the command line to call a function, now reads arguments for the function interactively if it is @@ -320,6 +324,11 @@ cycle for each frame, using the frame-local buffer list. converts whitespace around point to N spaces. --- +** C-x 5 C-o displays a specified buffer in another frame +but does not switch to that frame. It's the multi-frame +analogue of C-x 4 C-o. + +--- ** New commands to operate on pairs of open and close characters: `insert-pair', `delete-pair', `raise-sexp'. @@ -873,11 +882,6 @@ fontification in Info, remove `turn-on-font-lock' from `Info-mode-hook'. +++ -*** font-lock-lines-before specifies a number of lines before the -current line that should be refontified when you change the buffer. -The default value is 1. - -+++ *** font-lock: in modes like C and Lisp where the fontification assumes that an open-paren in column 0 is always outside of any string or comment, font-lock now highlights any such open-paren-in-column-zero in bold-red @@ -2597,6 +2601,12 @@ of BibTeX entry to kill ring (bound to C-c C-t). bibtex-autokey-expand-strings control the expansion of strings when extracting the content of a BibTeX field. +*** The variables `bibtex-autokey-name-case-convert' and +`bibtex-autokey-titleword-case-convert' have been renamed to +`bibtex-autokey-name-case-convert-function' and +`bibtex-autokey-titleword-case-convert-function'. The old names are +still available as aliases. + +++ ** In Enriched mode, `set-left-margin' and `set-right-margin' are now by default bound to `C-c [' and `C-c ]' instead of the former `C-c C-l' diff --git a/etc/orgcard.tex b/etc/orgcard.tex index 1f520df353..cca7e525d9 100644 --- a/etc/orgcard.tex +++ b/etc/orgcard.tex @@ -1,4 +1,4 @@ -% Reference Card for Org Mode 4.09 +% Reference Card for Org Mode 4.10 % %**start of header \newcount\columnsperpage @@ -58,7 +58,7 @@ % Thanks to Paul Rubin, Bob Chassell, Len Tower, and Richard Mlynarik % for their many good ideas. -\def\orgversionnumber{4.09} +\def\orgversionnumber{4.10} \def\year{2006} \def\shortcopyrightnotice{\vskip 1ex plus 2 fill |