Mercurial > hg > xemacs-beta

diff PROBLEMS @ 1332:6aa23bb3da6b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2003-03-02 02:18:05 by ben] To: xemacs-patches@xemacs.org PROBLEMS: Include nt/PROBLEMS and update. Add note about incremental linking badness. cmdloop.el, custom.el, dumped-lisp.el, files.el, keydefs.el, keymap.el, lisp-mode.el, make-docfile.el, replace.el, simple.el, subr.el, view-less.el, wid-edit.el: Lots of syncing with FSF 21.2. Use if-fboundp in wid-edit.el. New file newcomment.el from FSF. internals/internals.texi: Fix typo. (Build-Time Dependencies): New node. PROBLEMS: Delete. config.inc.samp, xemacs.mak: Eliminate HAVE_VC6, use SUPPORT_EDIT_AND_CONTINUE in its place. No incremental linking unless SUPPORT_EDIT_AND_CONTINUE, since it can cause nasty crashes in pdump. Put warnings about this in config.inc.samp. Report the full compile flags used for src and lib-src in the Installation output. alloc.c, lisp.h, ralloc.c, regex.c: Use ALLOCA() in regex.c to avoid excessive stack allocation. Also fix subtle problem with REL_ALLOC() -- any call to malloc() (direct or indirect) may relocate rel-alloced data, causing buffer text to shift. After any such call, regex must update all its pointers to such data. Add a system, when ERROR_CHECK_MALLOC, whereby regex.c indicates all the places it is prepared to handle malloc()/realloc()/free(), and any calls anywhere in XEmacs outside of this will trigger an abort. alloc.c, dialog-msw.c, eval.c, event-stream.c, general-slots.h, insdel.c, lisp.h, menubar-msw.c, menubar-x.c: Change *run_hook*_trapping_problems to take a warning class, not a string. Factor out code to issue warnings, add flag to call_trapping_problems() to postpone warning issue, and make *run_hook*_trapping_problems issue their own warnings tailored to the hook, postponed in the case of safe_run_hook_trapping_problems() so that the appropriate message can be issued about resetting to nil only when not `quit'. Make record_unwind_protect_restoring_int() non-static. dumper.c: Issue notes about incremental linking problems under Windows. fileio.c: Mule-ize encrypt/decrypt-string code. text.h: Spacing changes.
author ben
date Sun, 02 Mar 2003 02:18:12 +0000
parents b531bf8658e9
children 6355bae896e3
line wrap: on
line diff
--- a/PROBLEMS	Sat Mar 01 22:52:33 2003 +0000
+++ b/PROBLEMS	Sun Mar 02 02:18:12 2003 +0000
@@ -2,7 +2,7 @@
 
 This file describes various problems that have been encountered
 in compiling, installing and running XEmacs.  It has been updated for
-XEmacs 21.4.
+XEmacs 21.5.
 
 This file is rather large, but we have tried to sort the entries by
 their respective relevance for XEmacs, but may have not succeeded
@@ -738,6 +738,16 @@
 Note: Much of the above entry is probably not valid for XEmacs 21.0
 and later.
 
+** Windows
+
+*** Weird crashes in pdump load or shortly after pdump load.
+
+This can happen with incremental linking.  Check if you have set
+SUPPORT_EDIT_AND_CONTINUE to non-zero in config.inc, which must allow
+incremental linking to be enabled (otherwise it's disabled).  Either turn
+this off, execute `nmake -f xemacs.mak clean', or manually remove
+`temacs.exe' and `xemacs.exe'.
+
 ** Cygwin
 
 See also Intel Architecture General, above.
@@ -747,7 +757,7 @@
 This appears to happen when using the traditional dumping mechanism and
 the system malloc.  Andy Piper writes:
 
-  Traditional dumping on cygwin relies on using gmalloc (there are specific
+  Traditional dumping on Cygwin relies on using gmalloc (there are specific
   hacks in our version of gmalloc to support this), I suspect using sysmalloc
   is the problem.
 
@@ -762,10 +772,12 @@
 *** Syntax errors running configure scripts, make failing with exit code 127
     in inexplicable situations, etc.
 
-This may be because you are using the default cygwin shell.  The
-default cygwin shell (/bin/sh.exe) is ash which appears to work in
-most circumstances but has some weird failure modes.  You need to
-replace the symlink with bash.exe.
+[[ This may be because you are using the default Cygwin shell, under old
+versions of Cygwin.  The default Cygwin shell (/bin/sh.exe) is ash, which
+appears to work in most circumstances but has some weird failure modes.
+You may need to replace the symlink with bash.exe. ]] This doesn't appear
+to affect Cygwin any longer, and /bin/sh.exe is no longer a symlink in
+any case.
 
 *** Lots of compile errors, esp. on lines containing macro definitions
     terminated by backslashes.
@@ -786,8 +798,8 @@
 
 *** The info files will not build.
 
-makeinfo that ships with Cygwin (all versions) doesn't work.  You need to
-obtain makeinfo from somewhere or build it yourself.
+makeinfo that ships with old versions of Cygwin doesn't work.
+Upgrade to the latest Cygwin version.
 
 *** XEmacs hangs while attempting to rebuild the .elc files.
 
@@ -798,33 +810,27 @@
 *** Trying to build with X, but X11 not detected.
 
 This is usually because xmkmf is not in your path or because you are
-using the default cygwin shell. (See above.)
+using the default Cygwin shell. (See above.)
 
 
 * Problems with running XEmacs
 ==============================
 ** General
-*** At startup I get a warning on stderr about missing charsets:
- 
-    Warning: Missing charsets in String to FontSet conversion
- 
-You need to specify appropriate charsets for your locale (usually the
-value of the LANG environment variable) in .Xresources.  See
-etc/Emacs.ad for the relevant resources (mostly menubar fonts and
-fontsets).  Do not edit this file, it's purely informative.
-
-If you have no satisfactory fonts for iso-8859-1, XEmacs will crash.
-
-It looks like XFree86 4.x (the usual server on Linux and *BSD) has
-some braindamage where .UTF-8 locales will always generate this
-message, because the XFree86 (font)server doesn't know that UTF-8 will
-use the ISO10646-1 font registry (or a Cmap or something).
-
-If you are not using a .UTF-8 locale and see this warning for a
-character set not listed in the default in Emacs.ad, please let
-xemacs-beta@xemacs.org know about it, so we can add fonts to the
-appropriate fontsets and stifle this warning.  (Unfortunately it's
-buried in Xlib, so we can't easily get rid of it otherwise.)
+
+*** Changes made to .el files do not take effect.
+
+You may have forgotten to recompile them into .elc files.  Then the
+old .elc files will be loaded, and your changes will not be seen.  To
+fix this, do `M-x byte-recompile-directory' and specify the directory
+that contains the Lisp files.
+
+Note that you will get a warning when loading a .elc file that is
+older than the corresponding .el file.
+
+*** VM appears to hang in large folders.
+
+This is normal (trust us) when upgrading to VM-6.22 from earlier
+versions.  Let VM finish what it is doing and all will be well.
 
 *** Starting with 21.4.x, killing text is absurdly slow.
 
@@ -851,11 +857,7 @@
 You can defeat the use of TMPDIR by unsetting USE_TMPDIR at the top of
 gnuserv.h at build time.
 
-*** C-z just refreshes the screen instead of suspending Emacs.
-
-You are probably using a shell that doesn't support job control, even
-though the system itself is capable of it.  Try using a different
-shell.
+** General Unix
 
 *** You type Control-H (Backspace) expecting to delete characters.
 
@@ -878,6 +880,28 @@
 
     (global-set-key "\M-?" 'help-command)
 
+*** At startup I get a warning on stderr about missing charsets:
+ 
+    Warning: Missing charsets in String to FontSet conversion
+ 
+You need to specify appropriate charsets for your locale (usually the
+value of the LANG environment variable) in .Xresources.  See
+etc/Emacs.ad for the relevant resources (mostly menubar fonts and
+fontsets).  Do not edit this file, it's purely informative.
+
+If you have no satisfactory fonts for iso-8859-1, XEmacs will crash.
+
+It looks like XFree86 4.x (the usual server on Linux and *BSD) has
+some braindamage where .UTF-8 locales will always generate this
+message, because the XFree86 (font)server doesn't know that UTF-8 will
+use the ISO10646-1 font registry (or a Cmap or something).
+
+If you are not using a .UTF-8 locale and see this warning for a
+character set not listed in the default in Emacs.ad, please let
+xemacs-beta@xemacs.org know about it, so we can add fonts to the
+appropriate fontsets and stifle this warning.  (Unfortunately it's
+buried in Xlib, so we can't easily get rid of it otherwise.)
+
 *** Mail agents (VM, Gnus, rmail) cannot get new mail
 
 rmail and VM get new mail from /usr/spool/mail/$USER using a program
@@ -908,21 +932,6 @@
 mode of the installed copy; changing the group and mode of the build
 directory copy is ineffective.
 
-*** VM appears to hang in large folders.
-
-This is normal (trust us) when upgrading to VM-6.22 from earlier
-versions.  Let VM finish what it is doing and all will be well.
-
-*** Changes made to .el files do not take effect.
-
-You may have forgotten to recompile them into .elc files.  Then the
-old .elc files will be loaded, and your changes will not be seen.  To
-fix this, do `M-x byte-recompile-directory' and specify the directory
-that contains the Lisp files.
-
-Note that you will get a warning when loading a .elc file that is
-older than the corresponding .el file.
-
 *** Things which should be bold or italic (such as the initial
 copyright notice) are not.
 
@@ -966,7 +975,7 @@
 Try evaluating the form (setq lock-directory nil) and see if that helps.
 There is a problem with file-locking on some systems (possibly related
 to NFS) that I don't understand.  Please send mail to the address
-xemacs@xemacs.org if you figure this one out.
+xemacs-beta@xemacs.org if you figure this one out.
 
 *** When emacs starts up, I get lots of warnings about unknown keysyms.
 
@@ -1145,7 +1154,7 @@
 slow.
 
 If you are interested in fixing this, please let us know at
-<xemacs@xemacs.org>.
+<xemacs-beta@xemacs.org>.
 
 *** Screen is updated wrong, but only on one kind of terminal.
 
@@ -1350,6 +1359,11 @@
 workaround is to recompile the module with optimization turned on.  Any
 optimization level, including -Os, appears to work.
 
+*** C-z just refreshes the screen instead of suspending Emacs.
+
+You are probably using a shell that doesn't support job control, even
+though the system itself is capable of it.  Try using a different
+shell.
 
 ** MacOS/X, Darwin
 *** XEmacs crashes on MacOS within font-lock, or when dealing
@@ -1963,11 +1977,119 @@
 
 
 ** Windows
-*** In general, the Windows code is less mature than the Unix code.
-
-The Windows code base is still changing quickly.  If you are
-experiencing problems, try the latest beta version to see if the
-problem still exists.  Also ask on xemacs-nt@xemacs.org.
+*** Conflicts with FSF NTEmacs
+
+Depending on how it is installed, FSF NTEmacs may setup various EMACS*
+variables in your environment.  The presence of these variables may
+cause XEmacs to fail at startup, cause you to see corrupted
+doc-strings, or cause other random problems.
+
+You should remove these variables from your environment.  These
+variables are not required to run FSF NTEmacs if you start it by
+running emacs.bat.
+
+*** XEmacs can't find my init file
+
+XEmacs looks for your init in your "home" directory -- either in
+`~/.xemacs/init.el' or `~/.emacs'.  XEmacs decides that your "home"
+directory is, in order of preference:
+	
+- The value of the HOME environment variable, if the variable exists.
+- The value of the registry entry SOFTWARE\XEmacs\XEmacs\HOME,
+  if it exists.
+- The value of the HOMEDRIVE and HOMEPATH environment variables, if
+  these variables both exist.
+- C:\.
+
+To determine what XEmacs thinks your home directory is, try opening
+a file in the `~' directory, and you should see its expansion in the
+modeline.  If this doesn't work, type ESC : (user-home-directory).
+
+*** XEmacs can't find any packages
+
+XEmacs looks for your packages in subdirectories of a directory which
+is set at compile-time (see `config.inc'), and whose default is
+`C:\Program Files\XEmacs'.  XEmacs also looks in `~/.xemacs', where
+`~' refers to your home directory (see previous entry).  The variable
+`configure-package-path' holds the actual path that was compiled into
+your copy of XEmacs.
+
+The compile-time default location can be overridden by the EMACSPACKAGEPATH
+environment variable or by the SOFTWARE\XEmacs\XEmacs\EMACSPACKAGEPATH
+registry entry.  You should check that these variables, if they exist,
+point to the actual location of your package tree.
+
+*** XEmacs doesn't die when shutting down Windows 95 or 98
+
+When shutting down Windows 95 or 98 you may see a dialog that says
+  "xemacs / You must quit this program before you quit Windows".
+It is safe to
+  "Click OK to quit the program and Windows",
+but you won't be offered a chance to save any modified XEmacs buffers.
+
+*** Key bindings
+
+The C-z, C-x, C-c, and C-v keystrokes have traditional uses in both
+emacs and Windows programs. XEmacs binds these keys to their
+traditional emacs uses, and provides Windows 3.x style bindings for
+the Cut, Copy and Paste functions.
+
+	Function	XEmacs binding
+	--------	--------------
+	Undo		C-_
+	Cut		Sh-Del
+ 	Copy		C-Insert
+	Paste		Sh-Insert
+
+You can rebind keys to make XEmacs more Windows-compatible; for
+example, to bind C-z to undo:
+
+       (global-set-key [(control z)] 'undo)
+
+Rebindind C-x and C-c is trickier because by default these are prefix
+keys in XEmacs. See the "Key Bindings" node in the XEmacs manual.
+
+*** Behavior of selected regions
+
+Use the pending-del package to enable the standard Windows behavior of
+self-inserting deletes region.
+
+*** Limitations on the use of the AltGr key.
+
+In some locale and OS combinations you can't generate M-AltGr-key or
+C-M-AltGr-key sequences at all.
+
+To generate C-AltGr-key or C-M-AltGr-key sequences you must use the
+right-hand Control key and you must press it *after* AltGr.
+
+These limitations arise from fundamental problems in the way that the
+win32 API reports AltGr key events. There isn't anything that XEmacs
+can do to work round these problems that it isn't already doing.
+
+You may want to create alternative bindings if any of the standard
+XEmacs bindings require you to use some combination of Control or Meta
+and AltGr.
+
+*** Limited support for subprocesses under Windows 9x
+
+Attempting to use call-process to run a 16bit program gives a
+"Spawning child process: Exec format error". For example shell-command
+fails under Windows 95 and 98 if you use command.com or any other
+16bit program as your shell.
+
+XEmacs may incorrectly quote your call-process command if it contains
+double quotes, backslashes or spaces.
+
+start-process and functions that rely on it are supported under Windows 95,
+98 and NT. However, starting a 16bit program that requires keyboard input
+may cause XEmacs to hang or crash under Windows 95 and 98, and will leave
+the orphaned 16bit program consuming all available CPU time.
+
+Sending signals to subprocesses started by call-process or by
+start-process fails with a "Cannot send signal to process" error under
+Windows 95 and 98. As a side effect of this, quitting XEmacs while it
+is still running subprocesses causes it to crash under Windows 95 and
+98.
 
 
 ** Cygwin