
This is a list of known problems to date with the Windows NT port of
GNU Emacs.  These are not necessarily difficult to fix; they have been
noticed in passing and just haven't been tracked down.

The first thing on the list should be

* Figure out everything that should go on this list (this is by
  far not complete)

* #define CANNOT_DUMP 1 --- it would be great to get a dumpable
  version

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

* Browse the lib-src and etc directories and figure out what is worth
  the effort of porting.

* Shell:  Doesn't follow cd, etc., yet.

* Dired:  If you don't have a 32-bit ls, then for now you're out of
	  luck.  If we get GNU ls ported, then this problem will go
	  away.  If you have a 32-bit ls, then you should be able to
          use much of dired.

* Temp files on FAT of the form "foo.bar~" cause emacs to bail out.

* Completion on FAT is messed up.  This could be painful.

* Completion after double-bash... or bash-slash and "c:\" and stuff doesn't
  always do the right thing.

* ^Z and cr-lf when reading files causes some problems;  emacs is
  not going into binary mode in all the right places.  This is most
  obvious when editing binary files.

* In lisp-interaction mode type "(while t)" then C-j...  You are hung.  C-g
  should get you out, but doesn't... I though it was working...

* Completion when no explict path and cd is '\', or an explicit path of '\'
  is broken.

* Can't 'cd'.

* Clicking mouse buttons and modifier keys don't necessarily do what
  you want them to do (e.g., the intro page).

* If the last directory in your HOME path ends with a digit, an error occurs.
  This is because Emacs treats the path as a regexp...since the path has backslashes
  in it, the regexp engine discovers bad backslash constructs.

* (file-attributes "file"), where "file" is a file in the root directory of a FAT
  drive, fails on an x86.  It fails because the CRT function lstat fails.  Why?
