Mercurial > hg > xemacs-beta
annotate modules/README @ 5803:b79e1e02bf01
Preserve extent information in the command builder code.
src/ChangeLog addition:
2014-07-14 Aidan Kehoe <kehoea@parhasard.net>
* event-stream.c:
* event-stream.c (mark_command_builder):
* event-stream.c (finalize_command_builder): Removed.
* event-stream.c (allocate_command_builder):
* event-stream.c (free_command_builder): Removed. Use
free_normal_lisp_object() instead.
* event-stream.c (echo_key_event):
* event-stream.c (regenerate_echo_keys_from_this_command_keys):
Detach all extents here.
* event-stream.c (maybe_echo_keys):
* event-stream.c (reset_key_echo):
* event-stream.c (execute_help_form):
* event-stream.c (Fnext_event):
* event-stream.c (command_builder_find_leaf_no_jit_binding):
* event-stream.c (command_builder_find_leaf):
* event-stream.c (lookup_command_event):
* events.h (struct command_builder):
Move the command builder's echo_buf to being a Lisp string rather
than a malloced Ibyte array. This allows passing through extent
information, which was previously dropped. It also simplifies the
allocation and release code for the command builder.
Rename echo_buf_index to echo_buf_fill_pointer, better reflecting
its function.
Don't rely on zero-termination (something not particularly
compatible with Lisp-level code) when showing a substring of
echo_buf that differs from that designated by
echo_buf_fill_pointer, keep a separate counter instead and use
that.
* minibuf.c:
* minibuf.c (echo_area_append):
Use the new START and END keyword arguments to #'append-message,
rather than consing a new string for basically every #'next-event
prompt displayed.
test/ChangeLog addition:
2014-07-14 Aidan Kehoe <kehoea@parhasard.net>
* automated/extent-tests.el:
Check that extent information is passed through to the echo area
correctly with #'next-event's PROMPT argument.
lisp/ChangeLog addition:
2014-07-14 Aidan Kehoe <kehoea@parhasard.net>
* simple.el (raw-append-message):
Use #'write-sequence in this, take its START and END keyword
arguments, so our callers don't have to cons as much.
* simple.el (append-message):
Pass through START and END here.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Mon, 14 Jul 2014 13:42:42 +0100 |
| parents | da1365dd3f07 |
| children |
| rev | line source |
|---|---|
|
5436
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
1 This file is part of XEmacs. |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
2 |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
3 XEmacs is free software: you can redistribute it and/or modify it |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
4 under the terms of the GNU General Public License as published by the |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
5 Free Software Foundation, either version 3 of the License, or (at your |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
6 option) any later version. |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
7 |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
8 XEmacs is distributed in the hope that it will be useful, but WITHOUT |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
9 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
10 FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
11 for more details. |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
12 |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
13 You should have received a copy of the GNU General Public License |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
14 along with XEmacs. If not, see <http://www.gnu.org/licenses/>. |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
15 |
|
da1365dd3f07
Added GPLv3 or later license to modules/README.
Mats Lidell <matsl@xemacs.org>
parents:
996
diff
changeset
|
16 |
| 996 | 17 This directory contains a number of XEmacs dynamic modules. These |
| 18 modules can be loaded directly with the command 'M-x load-module'. | |
| 19 However, the preferred method of loading a module is to issue a | |
| 20 "(require 'module-name)" command to the Lisp interpreter. This will | |
| 21 store information so that a later "(unload-feature 'module-name)" can | |
| 22 succeed. | |
| 388 | 23 |
| 996 | 24 To compile one of these modules, simply enter the desired directory, |
| 25 type 'configure', and then 'make'. If you are building the module for | |
| 26 an installed XEmacs, then 'make install' will place the module in the | |
| 27 appropriate directory for XEmacs to find it later (assuming you have | |
| 28 permission to write to that directory). A subsequent 'load-module' or | |
| 29 'require' will then load the module, as described above. | |
| 388 | 30 |
| 996 | 31 Each of these demonstrates different features and limitations of the |
| 32 XEmacs module loading technology. For a complete discussion on XEmacs | |
| 33 dynamic modules, please consult the XEmacs Module Writers Guide, which | |
| 34 can be found in the ../info directory. | |
| 388 | 35 |
| 996 | 36 For those wanting to get started with module writing, please see the |
| 37 'sample' directory. It contains two subdirectories: internal and | |
| 38 external. The 'internal' subdirectory contains the framework needed to | |
| 39 migrate some core piece of XEmacs functionality into code that can | |
| 40 either be compiled into the core or built as a separate module. The | |
| 41 'external' subdirectory contains the somewhat simpler framework needed | |
| 42 to build a module separately from XEmacs. These should be considered | |
| 43 starting places for module writing. |
