view nt/TODO @ 34752:f04f551e94ce

* message.el (message-narrow-to-head-1): New function. (message-narrow-to-head): Use it. (message-reply): Ditto. (message-cancel-news): Ditto. (message-supersede): Ditto. (message-make-forward-subject): Ditto. (message-bounce): Ditto. * gnus-msg.el (gnus-summary-mail-forward): Use original buffer. * message.el (message-forward): Copy buffer in unibyte mode. (message-make-forward-subject): Don't widen. Decode. (message-forward): Don't decode subject. * mml.el (gnus-ems): Require it. * gnus-msg.el (gnus-summary-mail-forward): * message.el (message-forward): Move mime-to-mml here. * nnmbox.el (nnmbox-file-coding-system): Use binary. (nnmbox-active-file-coding-system): Ditto. * gnus-cus.el (gnus-group-parameters): Add posting-style. * mm-uu.el: Require binhex. * qp.el (quoted-printable-encode-region): Upcase QP.
author ShengHuo ZHU <zsh@cs.rochester.edu>
date Wed, 20 Dec 2000 20:20:51 +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.