Things not fixed for 19.34.5: - Frederick J Sieber reports that ediff-buffers has problems with non 8.3 files on Win95. -> Gerald Pani reports that it works for him: (setq ediff-shell "c:/path/tcsh.exe") and Reed Kotler diff. - attempt to reproduce frame refresh problem when 2nd frame is obscured by Internet Explorer. -> check with reworked obscured frame detection. -> cannot reproduce - investigate reported problem with menu bar constantly refreshing when Emacs is in the background (possibly connected with Internet Explorer refresh problem?). - fix menu refresh problem (redisplay can't keep up with typing or mouse selection) by implementing lazy menu construction. - "Ray Rizzuto" suggests cmdproxy support the /e:+nnnn syntax accepted by command.com to specify how much to increase the environment size by (as well as supporting the absolute size syntax). - Richard Stanton reports that emacs -nw running under SLNet telnet server thinks there is one more display line than there really is. (Turning off the Kermit status bar to get an extra line solves it.) - Peter Cherna reports that movemail hangs retrieving POP3 mail when the message contains a NUL byte. -> design of pop_multi_* in pop.c is at fault, specifically because getline returns a NUL terminated string. Need to check whether NUL is legal in POP3 spec. Could provide second arg (int*) to getline to return length of string, since only pop_multi_next needs to accept NUL. - look at problem with cd tracking in shell-mode - quite possibly related to the problem with comint-dynamic-completion, which I seem to have messed up by changing comint-file-name-chars. -> doesn't seem related to comint-file-name-chars. Part of the problem is that when changing drive (using the "X:" command), Emacs thinks the cwd for that drive is root, except when switching back to the startup drive for which the cwd is now the emacs bin dir (because of a deliberate change). -> separate problem is that shell-mode gets confused when cd changes to a directory name containing a space. - try improving comint-dynamic-complete-filename et al to recognise quoted arguments, and thus allow spaces in quoted filenames. - maybe try to debug why Emacs abort()s when using xmouse (focus follows mouse behaviour) on Win95 - apparently okay with 0ms delay but not with 1ms or greater. - investigate reported problem with Emacs hanging (in an infinite loop?) after killing *Messages* buffer (or other buffers). - investigate reported problem with Emacs crashing when exceeding max-specpdl-size (because of recursive `require') with stack-trace-on-error set to t. (Crashes on second occurence?) - apparently sometimes C-z doesn't minimize frame but leaves it "half-dazed" (ie. doesn't refresh - probably lisp thinks it is iconified?) - possibly check why key binding for Command Apropos (C-h c) is not shown in the Help menu. - investigate reports that Win95 OSR2 gets messed up after two or three shell buffer invocations (subprocess freezes and no console app will work, even if started outside Emacs). Stainless Steel Rat believes might only happen with optimized build (happened with 19.34.2 as well). -> Doesn't happen to me on Win95b, even with optimized build. -> "Rat" is investigating his system setup; seems likely to be specific to certain drivers or applications. - report a sensible error if win32-win.el[c] cannot be found - currently, Emacs crashes. - try to fix reported bug with dired not seeing files that start with ~. (Also try to solve related problem with expand-file-name.) Eric Hanchrow : ... and here's my suggested fix: change line 124 of ls-lisp.el from (cons x (file-attributes (expand-file-name x))))) to (cons x (file-attributes x)))) => Applied Eric's fix. However, this is not sufficient, since file-attributes calls expand-file-name internally. Personally I would like to change expand-file-name to not strip leading directories when a ~ or // (etc) is found. (The problem is that .../~foo/... is always treated as ~foo/..., even if initial filename is already absolute.) -> check with RMS if expand-file-name could be changed (aside: doc string for expand-file-name does not mention this behaviour; it is described in the doc string for substitute-in-file-name - however the description in the elisp manual does mention it). => as it happens, RMS has made precisely this change in 20.0 - not sure if many elisp changes were required; if not then do this. (Checking src and lisp ChangeLogs, there is no mention of lisp changes, so I think this change is safe to make.) ==> Done. (Kept under #if 0 .. #endif just in case.) Something isn't quite right though.