|
788
|
1 March 20, 2002:
|
|
771
|
2
|
|
788
|
3 bugs:
|
|
771
|
4
|
|
788
|
5 -- TTY-mode problem. When you start up in TTY mode, XEmacs goes through
|
|
|
6 the loadup process and appears to be working -- you see the startup
|
|
|
7 screen pulsing through the different screens, and it appears to be
|
|
|
8 listening (hitting a key stops the screen motion), but it's frozen --
|
|
|
9 the screen won't get off the startup, key commands don't cause anything
|
|
|
10 to happen. STATUS: In progress.
|
|
|
11
|
|
793
|
12 -- Memory ballooning in some cases. Not yet understood.
|
|
|
13
|
|
|
14 -- other test suite failures?
|
|
|
15
|
|
|
16 -- need to review the handling of sounds. seems that not everything is
|
|
|
17 documented, not everything is consistently used where it's supposed to,
|
|
|
18 some sounds are ugly, etc. add sounds to `completer' as well.
|
|
|
19
|
|
|
20 -- redo with-trapping-errors so that the backtrace is stored away and only
|
|
|
21 outputted when an error actually occurs (i.e. in the condition-case
|
|
|
22 handler). test. (use ding of various sorts as a helpful way of checking
|
|
|
23 out what's going on.)
|
|
|
24
|
|
|
25 -- problems with process input: |uniq (for example) leaves ^M's at end of
|
|
|
26 line.
|
|
|
27
|
|
800
|
28 -- carefully review looking up of fonts by charset, esp. wrt the last
|
|
|
29 element of a font spec.
|
|
|
30
|
|
|
31 -- add package support to ignore certain files -- *-util.el for languages.
|
|
|
32
|
|
|
33 -- review use of escape-quoted in auto_save_1() vs. the buffer's own coding
|
|
|
34 system.
|
|
|
35
|
|
801
|
36 -- figure out how to get the total amount of data memory (i.e. everything
|
|
|
37 but the code, or even including the code if can't distinguish) used by
|
|
|
38 the process on each different OS, and use it in a new algorithm for
|
|
|
39 triggering GC: trigger only when a certain % of the data size has been
|
|
|
40 consed up; in addition, have a minimum.
|
|
|
41
|
|
800
|
42 fixed bugs???
|
|
|
43
|
|
|
44 -- Occasional crash when freeing display structures. The problem seems to
|
|
|
45 be this: A window has a "display line dynarr"; each display line has a
|
|
|
46 "display block dynarr". Sometimes this display block dynarr is getting
|
|
|
47 freed twice. It appears from looking at the code that sometimes a
|
|
|
48 display line from somewhere in the dynarr gets added to the end -- hence
|
|
|
49 two pointers to the same display block dynarr. need to review this
|
|
|
50 code.
|
|
788
|
51
|
|
|
52 August 29, 2001.
|
|
771
|
53
|
|
|
54 This is the most current list of priorities in `ben-mule-21-5'.
|
|
|
55 Updated often.
|
|
|
56
|
|
|
57 high-priority:
|
|
|
58
|
|
|
59 [input]
|
|
|
60
|
|
|
61 -- support for WM_IME_CHAR. IME input can work under -nuni if we use
|
|
|
62 WM_IME_CHAR. probably we should always be using this, instead of
|
|
|
63 snarfing input using WM_COMPOSITION. i'll check this out.
|
|
|
64 -- Russian C-x problem. see above.
|
|
|
65
|
|
|
66 [clean-up]
|
|
|
67
|
|
|
68 -- make sure it compiles and runs under non-mule. remember that some
|
|
|
69 code needs the unicode support, or at least a simple version of it.
|
|
|
70 -- make sure it compiles and runs under pdump. see below.
|
|
|
71 -- make sure it compiles and runs under cygwin. see below.
|
|
|
72 -- clean up mswindows-multibyte, TSTR_TO_C_STRING. expand dfc
|
|
|
73 optimizations to work across chain.
|
|
|
74 -- eliminate last vestiges of codepage<->charset conversion and similar stuff.
|
|
|
75
|
|
|
76 [other]
|
|
|
77
|
|
|
78 -- test the "file-coding is binary only on Unix, no-Mule" stuff.
|
|
|
79 -- test that things work correctly in -nuni if the system environment
|
|
|
80 is set to e.g. japanese -- i should get japanese menus, japanese
|
|
|
81 file names, etc. same for russian, hebrew ...
|
|
|
82 -- cut and paste. see below.
|
|
|
83 -- misc issues with handling lang environments. see also August 25,
|
|
|
84 "finally: working on the C-x in ...".
|
|
|
85 -- when switching lang env, needs to set keyboard layout.
|
|
|
86 -- user var to control whether, when moving into text of a
|
|
|
87 particular language, we set the appropriate keyboard layout. we
|
|
|
88 would need to have a lisp api for retrieving and setting the
|
|
|
89 keyboard layout, set text properties to indicate the layout of
|
|
|
90 text, and have a way of dealing with text with no property on
|
|
|
91 it. (e.g. saved text has no text properties on it.) basically,
|
|
|
92 we need to get a keyboard layout from a charset; getting a
|
|
|
93 language would do. Perhaps we need a table that maps charsets
|
|
|
94 to language environments.
|
|
|
95 -- test that the lang env is properly set at startup. test that
|
|
|
96 switching the lang env properly sets the C locale (call
|
|
|
97 setlocale(), set LANG, etc.) -- a spawned subprogram should have
|
|
|
98 the new locale in its environment.
|
|
|
99 -- look through everything below and see if anything is missed in this
|
|
|
100 priority list, and if so add it. create a separate file for the
|
|
|
101 priority list, so it can be updated as appropriate.
|
|
|
102
|
|
|
103
|
|
|
104 mid-priority:
|
|
|
105
|
|
|
106 -- clean up the chain coding system. its list should specify decode
|
|
|
107 order, not encode; i now think this way is more logical. it should
|
|
|
108 check the endpoints to make sure they make sense. it should also
|
|
|
109 allow for the specification of "reverse-direction coding systems":
|
|
|
110 use the specified coding system, but invert the sense of decode and
|
|
|
111 encode.
|
|
|
112
|
|
|
113 -- along with that, places that take an arbitrary coding system and
|
|
|
114 expect the ends to be anything specific need to check this, and add
|
|
|
115 the appropriate conversions from byte->char or char->byte.
|
|
|
116
|
|
|
117 -- get some support for arabic, thai, vietnamese, japanese jisx 0212:
|
|
|
118 at least get the unicode information in place and make sure we have
|
|
|
119 things tied together so that we can display them. worry about r2l
|
|
|
120 some other time.
|
|
|
121
|
|
|
122 -- check the handling of C-c. can XEmacs itself be interrupted with C-c?
|
|
|
123 is that impossible now that we are a window, not a console, app? at
|
|
|
124 least we should work something out with `i', so that if it receives a
|
|
|
125 C-c or C-break, it interrupts XEmacs, too. check out how process groups
|
|
|
126 work and if they apply only to console apps. also redo the way that
|
|
|
127 XEmacs sends C-c to other apps. the business of injecting code should
|
|
|
128 be last resort. we should try C-c first, and if that doesn't work, then
|
|
|
129 the next time we try to interrupt the same process, use the injection
|
|
|
130 method.
|
