view nt/TODO @ 30487:6165da9c89c6

(Qsafe_charsets): This variable deleted. (Qsafe_chars, Vchar_coding_system_table, Qchar_coding_system): New variables. (coding_safe_chars): New function. (CODING_SAFE_CHAR_P): New macro. (CHARSET_OK): New arg C. Call CODING_SAFE_CHAR_P instead of checking safe_charsets member of the coding system. Caller changed. (detect_coding_iso2022): New local variable safe_chars. (DECODE_DESIGNATION): Call CODING_SAFE_CHAR_P instead of checking safe_charsets member of the coding system. (decode_coding_iso2022): New local variable safe_chars. (ENCODE_ISO_CHARACTER_DIMENSION1): Don't check unsafe chars here. (ENCODE_ISO_CHARACTER_DIMENSION2): Likewise. (ENCODE_ISO_CHARACTER): Arguments changed. Caller changed. (ENCODE_UNSAFE_CHARACTER): New macro. (encode_coding_iso2022): New local variable safe_chars. Check unsafe chars. (setup_coding_system): Delete the code to initialize coding->safe_charses (intersection, find_safe_codings): New functions. (Ffind_coding_systems_region_internal): New function. (syms_of_coding): Defsubr it. Initialize Qsafe_chars, Qsafe_cding_system. Make Vchar_coding_system_table a Lisp variable and initialize it.
author Kenichi Handa <handa@m17n.org>
date Thu, 27 Jul 2000 06:01:19 +0000
parents 354e0c45cedf
children
line wrap: on
line source


This is a list of known problems to date with the Windows NT/95 port of
GNU Emacs.

* Handle wildcards in ls-lisp (e.g., C-x d *.c).

* Interactive subprocess output is buffered in jerky

* Presently, C:\foo\bar and C:/foo/bar bring up two buffers on the same file.
  Solve this by adding a switch that canonicalizes path separators
  (e.g., make them all / or all \)?

* call-process-region: Another tricky situation with binary and text modes.
  An example by dsrosing@reston.ingr.com: use crypt++ to load compressed
  data into a buffer, edit the buffer, save the data back out.  (Also
  need to propagate the "/C" switch change sent the shell in crypt++.el
  back to the author.)

* Dired uses ls-lisp, which reports all files as being owned by the
  current user.  Need to dig through the security descriptor to extract
  the owner of the file (and the group?) using LookupAccountSid.

* Integrate the build for NT into the GNU config process once
  a decent shell becomes freely available

* Integrate networking.

* Fix Win95 subprocesses.