|
25856
|
1
|
|
|
2 This is a list of known problems to date with the Windows NT/95 port of
|
|
|
3 GNU Emacs.
|
|
|
4
|
|
|
5 * Handle wildcards in ls-lisp (e.g., C-x d *.c).
|
|
|
6
|
|
|
7 * Interactive subprocess output is buffered in jerky
|
|
|
8
|
|
|
9 * Presently, C:\foo\bar and C:/foo/bar bring up two buffers on the same file.
|
|
|
10 Solve this by adding a switch that canonicalizes path separators
|
|
|
11 (e.g., make them all / or all \)?
|
|
|
12
|
|
|
13 * call-process-region: Another tricky situation with binary and text modes.
|
|
|
14 An example by dsrosing@reston.ingr.com: use crypt++ to load compressed
|
|
|
15 data into a buffer, edit the buffer, save the data back out. (Also
|
|
|
16 need to propagate the "/C" switch change sent the shell in crypt++.el
|
|
|
17 back to the author.)
|
|
|
18
|
|
|
19 * Dired uses ls-lisp, which reports all files as being owned by the
|
|
|
20 current user. Need to dig through the security descriptor to extract
|
|
|
21 the owner of the file (and the group?) using LookupAccountSid.
|
|
|
22
|
|
|
23 * Integrate the build for NT into the GNU config process once
|
|
|
24 a decent shell becomes freely available
|
|
|
25
|
|
|
26 * Integrate networking.
|
|
|
27
|
|
|
28 * Fix Win95 subprocesses.
|
