Mercurial > emacs
view etc/=TO-DO @ 18260:a642c99198ec
(PTR_TO_OFFSET): New macro.
(POS_AS_IN_BUFFER): New macro.
(SYNTAX_ENTRY_VIA_PROPERTY): Set to take `syntax-table' text
property into account when doing SYNTAX (c).
(re_compile_fastmap): disable fastmap if any of wordbound
notwordbound wordbeg wordend notsyntaxspec syntaxspec are seen.
(re_search_2): SETUP_SYNTAX_TABLE_FOR_OBJECT at the start.
(re_match_object): New variable.
(re_match_2): SETUP_SYNTAX_TABLE_FOR_OBJECT at the start.
(re_match_2_internal): For any of wordbound notwordbound wordbeg
wordend notsyntaxspec syntaxspec call UPDATE_SYNTAX_TABLE before
doing SYNTAX (c).
[emacs]: Include charset.h and category.h
[!emacs] (BASE_LEADING_CODE_P, WORD_BOUNDARY_P, CHAR_HEAD_P,
SINGLE_BYTE_CHAR_P, SAME_CHARSET_P, MULTIBYTE_FORM_LENGTH,
STRING_CHAR_AND_LENGTH, GET_CHAR_AFTER_2, GET_CHAR_BEFORE_2):
New dummy macros.
(enum re_opcode_t): New member categoryspec and notcategoryspec.
(STORE_CHARACTER_AND_INCR, EXTRACT_CHARACTER,
CHARSET_LOOKUP_RANGE_TABLE_WITH_COUNT,
CHARSET_LOOKUP_RANGE_TABLE, CHARSET_BITMAP_SIZE,
CHARSET_RANGE_TABLE_EXISTS_P, CHARSET_RANGE_TABLE
CHARSET_PAST_RANGE_TABLE): New macros.
(TRANSLATE): Cast return value to unsigned char, not char.
(struct range_table_work_area): New structure.
(EXTEND_RANGE_TABLE_WORK_AREA, SET_RANGE_TABLE_WORK_AREA,
FREE_RANGE_TABLE_WORK_AREA, CLEAR_RANGE_TABLE_WORK_USED,
RANGE_TABLE_WORK_USED, RANGE_TABLE_WORK_ELT): New macros.
(FREE_STACK_RETURN): Call FREE_RANGE_TABLE_WORK_AREA.
(regex_compile): Declare `c' and `c1' as int to store multibyte characters.
Declare range_table_work and initialize it.
Initialize bufp->multibyte to 0 if not emacs.
For case '[' and `default', code re-written to handle multibyte characters.
Add code for case 'c' and 'C' to handle category spec.
(re_compile_fastmap): New local variables k, simple_char_max,
and match_any_multibyte_characters.
Use macro CHARSET_BITMAP_SIZE.
Handle multibyte characters in cases charset, charset_not,
wordchar, notwordchar, anychar, syntaxspec, notsyntaxspec,
categoryspec, notcategoryspec.
(STOP_ADDR_VSTRING, POS_ADDR_VSTRING): New macros.
(re_search_2): Code re-written to handle multibyte characters.
(AT_WORD_BOUNDARY): Macro disabled.
(re_match_2_internal): New local variable multibyte. `d' is
incremented while paying attention to multibyte characters if necessary.
For case charset, charsetnot, wordbound, notwordbound,
wordbeg, wordend, matchsyntax, and matchnotsyntax, code
re-written to handle multibyte characters.
Add code for case categoryspec and notcategoryspec.
Declare c, c1 as unsigned int, not unsigned char.
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Sun, 15 Jun 1997 19:00:12 +0000 |
parents | 59c8668f70c7 |
children |
line wrap: on
line source
Things useful to do for GNU Emacs: * Primitive for random access insertion of part of a file. * Making I/O streams for files, so that read and prin1 can be used on files directly. The I/O stream itself would serve as a function to read or write one character. * If a file you can't write is in a directory you can write, make sure it works to modify and save this file. * Make dired's commands handle correctly the case where ls has listed several subdirectories' contents. It needs to be able to tell which directory each file is really in, by searching backward for the line which identifies the start of a directory. * Add more dired commands, such as sorting (use the sort utility through call-process-region). * Make display.c record inverse-video-ness on a character by character basis. Then make non-full-screen-width mode lines inverse video, and display the marked location in inverse video. * VMS code to list a file directory. Make dired work. Long range: Ideas for extending GNU Emacs to deal with arbitrary character sets. I would like GNU Emacs to be extended to handle all the world's alphabets and word signs. I don't expect to have time to do such a thing in the next few years, so here are my ideas on the best way to do it. * Each graphic is represented by a sequence of ordinary 8-bit characters. * All the characters that make up such a sequence have codes >= 0200. * The first character of such a sequence is between 0200 and 0237. * The remaining characters of such a sequence are all 0240 or higher. * The first character of the sequence determines the number of characters in the sequence. Thus, 0200...0207 could start two-character sequences, 0210...0227 could start three-character sequences, and 0230 could start four-character sequences. (Codes 0231...0237 would be reserved.) * Several common alphabets, and some mathematical symbols, would get two-character sequences. (Probably Greek, Russian, Hebrew(?), Arabic(?), Korean, and Japanese kana). The remaining alphabets, and some versions of Chinese, would get three-character sequences. Other sets of Chinese characters would get four-character sequences. Each country that uses Chinese characters has its own standard character set, and it is not easy to correlate them to avoid overlap. So there may need to be several sets of Chinese characters. That is why they need so much code space. True support for Hebrew and Arabic requires dealing with the problem of writing direction for mixed text; I don't know what to do for that. * The functions that use syntax table would determine the syntax of a sequence from its first character. * Functions in indent.c for computing widths and columns would determine the width of a sequence from its first character. So would display routines. * Only a few other editing routines would need any change. In particular, searching and regexp matching might not need any change. * Most of the work required would be in redisplay. The only case that needs to be supported is with X windows, since ordinary terminals can't display all these characters anyway. * There might need to be code to translate files from this format to whatever format is typically stored on disk. I would be very unhappy with half-measures, such as support for Japanese only.