mirror/emacs
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/emacs.git synced 2024-11-25 07:28:20 +00:00
Code Issues Releases Activity
0583403316
emacs/etc/PROBLEMS

3092 lines
126 KiB
Plaintext
Raw Normal View History

Add header line.
2008-02-29 23:44:30 +00:00
Known Problems with GNU Emacs
Update copyright year to 2014 by running admin/update-copyright.
2014-01-01 07:43:34 +00:00
Copyright (C) 1987-1989, 1993-1999, 2001-2014 Free Software Foundation,
Update copyright notices for 2013.
2013-01-01 09:11:05 +00:00
Inc.
Switch to standard GPL text for license.
2007-02-11 01:18:25 +00:00
See the end of the file for license conditions.
#
1999-10-03 12:39:42 +00:00
This file describes various problems that have been encountered
Fix initial comment on outline mode.
2009-01-27 03:48:02 +00:00
in compiling, installing and running GNU Emacs. Try doing C-c C-t
and browsing through the outline headers. (See C-h m for help on
* etc/PROBLEMS: Remove old information no longer of relevance.
2010-05-27 05:51:43 +00:00
Outline mode.) Information about systems that are no longer supported,
and old Emacs releases, has been removed. Consult older versions of
this file if you are interested in that information.
#
1999-10-03 12:39:42 +00:00
* etc/PROBLEMS: Remove some old stuff; other small edits
2014-01-07 02:06:00 +00:00
* Mule-UCS doesn't work in Emacs 23 onwards
*** empty log message ***
2003-09-11 13:54:47 +00:00
It's completely redundant now, as far as we know.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
* Emacs startup failures
Document the workaround for the Mac OS X port not picking up the environment variables from the dotfiles.
2004-05-30 00:35:44 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Emacs fails to start, complaining about missing fonts.
Document the workaround for the Mac OS X port not picking up the environment variables from the dotfiles.
2004-05-30 00:35:44 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
A typical error message might be something like
Document the workaround for the Mac OS X port not picking up the environment variables from the dotfiles.
2004-05-30 00:35:44 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
No fonts match `-*-fixed-medium-r-*--6-*-*-*-*-*-iso8859-1'
Sync to HEAD
2004-04-16 12:51:06 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This happens because some X resource specifies a bad font family for
Emacs to use. The possible places where this specification might be
are:
Sync to HEAD
2004-04-16 12:51:06 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
- in your ~/.Xdefaults file
Sync to HEAD
2004-04-16 12:51:06 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
- client-side X resource file, such as ~/Emacs or
/usr/X11R6/lib/app-defaults/Emacs or
/usr/X11R6/lib/X11/app-defaults/Emacs
Sync to HEAD
2004-04-16 12:51:06 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
One of these files might have bad or malformed specification of a
fontset that Emacs should use. To fix the problem, you need to find
the problematic line(s) and correct them.
Sync to HEAD
2004-04-16 12:51:06 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Emacs aborts while starting up, only when run without X.
Sync to HEAD
2004-04-16 12:51:06 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This problem often results from compiling Emacs with GCC when GCC was
installed incorrectly. The usual error in installing GCC is to
specify --includedir=/usr/include. Installation of GCC makes
corrected copies of the system header files. GCC is supposed to use
the corrected copies in preference to the original system headers.
Specifying --includedir=/usr/include causes the original system header
files to be used. On some systems, the definition of ioctl in the
original system header files is invalid for ANSI C and causes Emacs
not to work.
Sync to HEAD
2004-04-16 12:51:06 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The fix is to reinstall GCC, and this time do not specify --includedir
when you configure it. Then recompile Emacs. Specifying --includedir
is appropriate only in very special cases and it should *never* be the
same directory where system header files are kept.
Sync to HEAD
2004-04-16 12:51:06 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Emacs does not start, complaining that it cannot open termcap database file.
Sync to HEAD
2004-04-16 12:51:06 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If your system uses Terminfo rather than termcap (most modern
systems do), this could happen if the proper version of
ncurses is not visible to the Emacs configure script (i.e. it
cannot be found along the usual path the linker looks for
libraries). It can happen because your version of ncurses is
obsolete, or is available only in form of binaries.
Sync to HEAD
2004-04-16 12:51:06 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The solution is to install an up-to-date version of ncurses in
the developer's form (header files, static libraries and
symbolic links); in some GNU/Linux distributions (e.g. Debian)
it constitutes a separate package.
Sync to HEAD
2004-04-16 12:51:06 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Emacs 20 and later fails to load Lisp files at startup.
Truncated process output with pty's on Mac OS X.
2003-07-22 17:51:57 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The typical error message might be like this:
Truncated process output with pty's on Mac OS X.
2003-07-22 17:51:57 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
"Cannot open load file: fontset"
Adding comment about Mac OS X binary incompatibility between 10.2.1 and 10.2.2
2002-11-14 06:30:15 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This could happen if you compress the file lisp/subdirs.el. That file
tells Emacs what are the directories where it should look for Lisp
files. Emacs cannot work with subdirs.el compressed, since the
Auto-compress mode it needs for this will not be loaded until later,
when your .emacs file is processed. (The package `fontset.el' is
required to set up fonts used to display text on window systems, and
it's loaded very early in the startup procedure.)
Mention problem with Emacs executable crashing after system updates solved.
2002-11-25 16:24:23 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Similarly, any other .el file for which there's no corresponding .elc
file could fail to load if it is compressed.
*** empty log message ***
2002-07-24 23:01:32 +00:00
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
The solution is to uncompress all .el files that don't have a .elc file.
Sync to HEAD
2004-04-16 12:51:06 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Another possible reason for such failures is stale *.elc files
* etc/PROBLEMS: Remove some more old information.
2010-05-27 06:13:23 +00:00
lurking somewhere on your load-path -- see the next section.
XFree86 4 iso10646-1 fonts.
2002-10-24 22:13:59 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Emacs prints an error at startup after upgrading from an earlier version.
XFree86 4 iso10646-1 fonts.
2002-10-24 22:13:59 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
An example of such an error is:
XFree86 4 iso10646-1 fonts.
2002-10-24 22:13:59 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
x-complement-fontset-spec: "Wrong type argument: stringp, nil"
Correct Unicode stuff.
2003-05-29 18:15:21 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can be another symptom of stale *.elc files in your load-path.
The following command will print any duplicate Lisp files that are
present in load-path:
Correct Unicode stuff.
2003-05-29 18:15:21 +00:00
-batch implies -q. * etc/PROBLEMS: -batch implies -q. * msdos/sedleim.inp (RUN-EMACS): -batch imples --no-init-file.
2011-01-08 02:49:27 +00:00
emacs -batch -f list-load-path-shadows
Correct Unicode stuff.
2003-05-29 18:15:21 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If this command prints any file names, some of these files are stale,
and should be deleted or their directories removed from your
load-path.
Mention Unicode limitations.
2003-04-29 13:35:52 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
* Crash bugs
*** empty log message ***
2002-08-02 18:03:01 +00:00
Add check for buggy version of GCC (Bug#6031). * configure.in: Add check for buggy version of GCC (Bug#6031). * configure: Regenerate * etc/NEWS: Minor tweak to problem description.
2010-05-03 01:42:50 +00:00
** Emacs crashes when running in a terminal, if compiled with GCC 4.5.0
* PROBLEMS: Document gcc-4.5 bug (Bug#6031).
2010-04-27 15:36:16 +00:00
This version of GCC is buggy: see
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6031
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43904
You can work around this error in gcc-4.5 by omitting sibling call
optimization. To do this, configure Emacs with
CFLAGS="-g -O2 -fno-optimize-sibling-calls" ./configure
etc/PROBLEMS: Mention crashes on MS-Windows when compiled with GCC 4.6.1.
2011-10-21 12:29:07 +00:00
** Emacs compiled with GCC 4.6.1 crashes on MS-Windows when C-g is pressed
This is known to happen when Emacs is compiled with MinGW GCC 4.6.1
with the -O2 option (which is the default in the Windows build). The
reason is a bug in MinGW GCC 4.6.1; to work around, either add the
`-fno-omit-frame-pointer' switch to GCC or compile without
optimizations (`--no-opt' switch to the configure.bat script).
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Emacs crashes in x-popup-dialog.
*** empty log message ***
2002-08-02 18:03:01 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can happen if the dialog widget cannot find the font it wants to
use. You can work around the problem by specifying another font with
an X resource--for example, `Emacs.dialog*.font: 9x15' (or any font that
happens to exist on your X server).
*** empty log message ***
2002-07-24 23:01:32 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Emacs crashes when you use Bibtex mode.
*** empty log message ***
2002-07-24 23:01:32 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This happens if your system puts a small limit on stack size. You can
prevent the problem by using a suitable shell command (often `ulimit')
to raise the stack size limit before you run Emacs.
Trailing whitespace deleted.
2003-02-04 14:56:31 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Patches to raise the stack size limit automatically in `main'
(src/emacs.c) on various systems would be greatly appreciated.
*** empty log message ***
2002-07-24 23:01:32 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Error message `Symbol's value as variable is void: x', followed by
a segmentation fault and core dump.
Document problems with linking libraries compiled with GCC.
2002-01-16 18:21:14 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This has been tracked to a bug in tar! People report that tar erroneously
added a line like this at the beginning of files of Lisp code:
Document problems with linking libraries compiled with GCC.
2002-01-16 18:21:14 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
x FILENAME, N bytes, B tape blocks
Document problems with linking libraries compiled with GCC.
2002-01-16 18:21:14 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If your tar has this problem, install GNU tar--if you can manage to
untar it :-).
Document problems with linking libraries compiled with GCC.
2002-01-16 18:21:14 +00:00
* PROBLEMS: Fix previous change: any kind of transparency can crash. Fixes: debbugs:13867
2013-03-18 16:41:24 +00:00
** Emacs can crash when displaying PNG images with transparency.
Emacs crashes with ImageMagick 6.8.2-3 through 6.8.3-9. * configure.ac (IMAGEMAGICK_MODULE): Reject 6.8.2. We want to reject 6.8.2-3 through 6.8.3-9, but there seems to be no way to do this in pkg-config, so make do with a reasonable approximation. * etc/PROBLEMS: Mention problem with ImageMagick 6.8.2-3 through 6.8.3-9. Fixes: debbugs:13867
2013-03-18 05:26:56 +00:00
This is due to a bug introduced in ImageMagick 6.8.2-3. The bug
should be fixed in ImageMagick 6.8.3-10. Please see Bug#13867.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Crashes when displaying GIF images in Emacs built with version
libungif-4.1.0 are resolved by using version libungif-4.1.0b1.
Configure checks for the correct version, but this problem could occur
if a binary built against a shared libungif is run on a system with an
older version.
Wording changes suggested by Richard M. Stallman.
2002-01-18 07:53:34 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Emacs aborts inside the function `tparam1'.
Add note about need to specify extra compiler flags with recent Cygwin ports of gcc.
2001-02-03 18:26:12 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can happen if Emacs was built without terminfo support, but the
terminal's capabilities use format that is only supported by terminfo.
If your system has ncurses installed, this might happen if your
version of ncurses is broken; upgrading to a newer version of ncurses
and reconfiguring and rebuilding Emacs should solve this.
Add note about need to specify extra compiler flags with recent Cygwin ports of gcc.
2001-02-03 18:26:12 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
All modern systems support terminfo, so even if ncurses is not the
problem, you should look for a way to configure Emacs so that it uses
terminfo when built.
Add note about need to specify extra compiler flags with recent Cygwin ports of gcc.
2001-02-03 18:26:12 +00:00
Tweak entry about Exceed X server (Bug#3383).
2009-05-26 03:23:13 +00:00
** Emacs crashes when using some version of the Exceed X server.
Added note about CreateProcess failures from make.exe
2004-05-10 21:31:34 +00:00
Tweak entry about Exceed X server (Bug#3383).
2009-05-26 03:23:13 +00:00
Upgrading to a newer version of Exceed has been reported to prevent
these crashes. You should consider switching to a free X server, such
as Xming or Cygwin/X.
Added note about CreateProcess failures from make.exe
2004-05-10 21:31:34 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Emacs crashes with SIGSEGV in XtInitializeWidgetClass.
Document problems (with WinZip) whereby *.tit files get converted to DOS-style EOLs while unpacking Leim.
2001-01-24 08:09:48 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
It crashes on X, but runs fine when called with option "-nw".
Document problems (with WinZip) whereby *.tit files get converted to DOS-style EOLs while unpacking Leim.
2001-01-24 08:09:48 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This has been observed when Emacs is linked with GNU ld but without passing
the -z nocombreloc flag. Emacs normally knows to pass the -z nocombreloc
flag when needed, so if you come across a situation where the flag is
necessary but missing, please report it via M-x report-emacs-bug.
Document problems (with WinZip) whereby *.tit files get converted to DOS-style EOLs while unpacking Leim.
2001-01-24 08:09:48 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
On platforms such as Solaris, you can also work around this problem by
configuring your compiler to use the native linker instead of GNU ld.
Document problems (with WinZip) whereby *.tit files get converted to DOS-style EOLs while unpacking Leim.
2001-01-24 08:09:48 +00:00
Document GTK Emacs kill on display close in PROBLEMS. * src/xterm.c (x_connection_closed): Update comment.
2010-10-25 16:04:54 +00:00
** When Emacs is compiled with Gtk+, closing a display kills Emacs.
Add "Emacs compiled with Gtk+ crashes when closing a display (x-close-connection)."
2006-09-10 12:29:10 +00:00
Document GTK Emacs kill on display close in PROBLEMS. * src/xterm.c (x_connection_closed): Update comment.
2010-10-25 16:04:54 +00:00
There is a long-standing bug in GTK that prevents it from recovering
from disconnects: http://bugzilla.gnome.org/show_bug.cgi?id=85715.
Add "Emacs compiled with Gtk+ crashes when closing a display (x-close-connection)."
2006-09-10 12:29:10 +00:00
Document GTK Emacs kill on display close in PROBLEMS. * src/xterm.c (x_connection_closed): Update comment.
2010-10-25 16:04:54 +00:00
Thus, for instance, when Emacs is run as a server on a text terminal,
and an X frame is created, and the X server for that frame crashes or
exits unexpectedly, Emacs must exit to prevent a GTK error that would
result in an endless loop.
Added some text about Gtk+ looping when X server dies.
2008-12-18 19:18:12 +00:00
Document GTK Emacs kill on display close in PROBLEMS. * src/xterm.c (x_connection_closed): Update comment.
2010-10-25 16:04:54 +00:00
If you need Emacs to be able to recover from closing displays, compile
it with the Lucid toolkit instead of GTK.
Added some text about Gtk+ looping when X server dies.
2008-12-18 19:18:12 +00:00
Add a PROBLEMS note about the libotf name-clash annoyance
2012-06-28 07:47:19 +00:00
** Emacs crashes when you try to view a file with complex characters.
For example, the etc/HELLO file (as shown by C-h h).
The message "symbol lookup error: /usr/bin/emacs: undefined symbol: OTF_open"
is shown in the terminal from which you launched Emacs.
This problem only happens when you use a graphical display (ie not
with -nw) and compiled Emacs with the "libotf" library for complex
text handling.
This problem occurs because unfortunately there are two libraries
called "libotf". One is the library for handling OpenType fonts,
http://www.m17n.org/libotf/, which is the one that Emacs expects.
The other is a library for Open Trace Format, and is used by some
versions of the MPI message passing interface for parallel
programming.
For example, on RHEL6 GNU/Linux, the OpenMPI rpm provides a version
of "libotf.so" in /usr/lib/openmpi/lib. This directory is not
normally in the ld search path, but if you want to use OpenMPI,
you must issue the command "module load openmpi". This adds
/usr/lib/openmpi/lib to LD_LIBRARY_PATH. If you then start Emacs from
the same shell, you will encounter this crash.
* etc/PROBLEMS: Remove some old stuff; other small edits
2014-01-07 02:06:00 +00:00
Ref: <URL:https://bugzilla.redhat.com/show_bug.cgi?id=844776>
Add a PROBLEMS note about the libotf name-clash annoyance
2012-06-28 07:47:19 +00:00
There is no good solution to this problem if you need to use both
OpenMPI and Emacs with libotf support. The best you can do is use a
wrapper shell script (or function) "emacs" that removes the offending
element from LD_LIBRARY_PATH before starting emacs proper.
Or you could recompile Emacs with an -Wl,-rpath option that
gives the location of the correct libotf.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
* General runtime problems
Document problems (with WinZip) whereby *.tit files get converted to DOS-style EOLs while unpacking Leim.
2001-01-24 08:09:48 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Lisp problems
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide a work-around.
2001-10-17 17:47:54 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Changes made to .el files do not take effect.
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide a work-around.
2001-10-17 17:47:54 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
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.
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide a work-around.
2001-10-17 17:47:54 +00:00
* etc/PROBLEMS: Remove some old stuff; other small edits
2014-01-07 02:06:00 +00:00
Emacs prints a warning when loading a .elc file which is older
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
than the corresponding .el file.
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide a work-around.
2001-10-17 17:47:54 +00:00
* etc/PROBLEMS: Remove some old stuff; other small edits
2014-01-07 02:06:00 +00:00
Alternatively, if you set the option `load-prefer-newer' non-nil,
Emacs will load whichever version of a file is the newest.
*** Watch out for the EMACSLOADPATH environment variable
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide a work-around.
2001-10-17 17:47:54 +00:00
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
EMACSLOADPATH overrides which directories the function "load" will search.
Mention the crashes on Yellow Dog GNU/Linux on MacPPC, and provide a work-around.
2001-10-17 17:47:54 +00:00
* etc/PROBLEMS: Remove some old stuff; other small edits
2014-01-07 02:06:00 +00:00
If you observe strange problems, check for this variable in your
environment.
*** empty log message ***
2001-03-14 19:52:43 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Using epop3.el package causes Emacs to signal an error.
*** empty log message ***
2001-03-14 19:52:43 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The error message might be something like this:
Document problems with the MS-Windows port of v21.1 and with the Cygwin port of Bash when run under Emacs.
2001-01-30 13:47:51 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
"Lisp nesting exceeds max-lisp-eval-depth"
Document problems with the MS-Windows port of v21.1 and with the Cygwin port of Bash when run under Emacs.
2001-01-30 13:47:51 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This happens because epop3 redefines the function gethash, which is a
built-in primitive beginning with Emacs 21.1. We don't have a patch
for epop3 that fixes this, but perhaps a newer version of epop3
corrects that.
Trailing whitespace deleted.
2003-02-04 14:56:31 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Buffers from `with-output-to-temp-buffer' get set up in Help mode.
Trailing whitespace deleted.
2003-02-04 14:56:31 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Changes in Emacs 20.4 to the hooks used by that function cause
problems for some packages, specifically BBDB. See the function's
documentation for the hooks involved. BBDB 2.00.06 fixes the problem.
Trailing whitespace deleted.
2003-02-04 14:56:31 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** The Hyperbole package causes *Help* buffers not to be displayed in
Help mode due to setting `temp-buffer-show-hook' rather than using
`add-hook'. Using `(add-hook 'temp-buffer-show-hook
'help-mode-maybe)' after loading Hyperbole should fix this.
Trailing whitespace deleted.
2003-02-04 14:56:31 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Keyboard problems
Document problems with the MS-Windows port of v21.1 and with the Cygwin port of Bash when run under Emacs.
2001-01-30 13:47:51 +00:00
etc/PROBLEMS: Document keyboard ghosting with M-| (Bug#10740).
2012-03-12 09:55:35 +00:00
*** Unable to enter the M-| key on some German keyboards.
Some users have reported that M-| suffers from "keyboard ghosting".
This can't be fixed by Emacs, as the keypress never gets passed to it
at all (as can be verified using "xev"). You can work around this by
typing `ESC |' instead.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** "Compose Character" key does strange things when used as a Meta key.
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If you define one key to serve as both Meta and Compose Character, you
will get strange results. In previous Emacs versions, this "worked"
in that the key acted as Meta--that's because the older Emacs versions
did not try to support Compose Character. Now Emacs tries to do
character composition in the standard X way. This means that you
must pick one meaning or the other for any given key.
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
You can use both functions (Meta, and Compose Character) if you assign
them to two different keys.
Improve recommendations for speedups over the net.
2002-10-07 22:46:09 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** C-z just refreshes the screen instead of suspending Emacs.
Improve recommendations for speedups over the net.
2002-10-07 22:46:09 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
You are probably using a shell that doesn't support job control, even
though the system itself is capable of it. Either use a different shell,
or set the variable `cannot-suspend' to a non-nil value.
Improve recommendations for speedups over the net.
2002-10-07 22:46:09 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** With M-x enable-flow-control, you need to type C-\ twice
to do incremental search--a single C-\ gets no response.
Improve recommendations for speedups over the net.
2002-10-07 22:46:09 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This has been traced to communicating with your machine via kermit,
with C-\ as the kermit escape character. One solution is to use
another escape character in kermit. One user did
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
set escape-character 17
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
in his .kermrc file, to make C-q the kermit escape character.
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Mailers and other helper programs
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** movemail compiled with POP support can't connect to the POP server.
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Make sure that the `pop' entry in /etc/services, or in the services
NIS map if your machine uses NIS, has the same port number as the
entry on the POP server. A common error is for the POP server to be
listening on port 110, the assigned port for the POP3 protocol, while
the client is trying to connect on port 109, the assigned port for the
old POP protocol.
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** RMAIL gets error getting new mail.
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
RMAIL gets new mail from /usr/spool/mail/$USER using a program
called `movemail'. This program interlocks with /bin/mail using
the protocol defined by /bin/mail.
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
There are two different protocols in general use. One of them uses
the `flock' system call. The other involves creating a lock file;
`movemail' must be able to write in /usr/spool/mail in order to do
this. You control which one is used by defining, or not defining,
etc/PROBLEMS small updates Remove references to m/ and s/ files. Remove reference to hpux _FILE_OFFSET_BITS issue, no longer true since 2012-05-31.
2012-07-31 06:58:54 +00:00
the macro MAIL_USE_FLOCK in config.h.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
SYSTEM, YOU CAN LOSE MAIL!
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If your system uses the lock file protocol, and fascist restrictions
prevent ordinary users from writing the lock files in /usr/spool/mail,
you may need to make `movemail' setgid to a suitable group such as
`mail'. To do this, use the following commands (as root) after doing the
make install.
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
chgrp mail movemail
chmod 2755 movemail
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Installation normally copies movemail from the build directory to an
installation directory which is usually under /usr/local/lib. The
installed copy of movemail is usually in the directory
/usr/local/lib/emacs/VERSION/TARGET. You must change the group and
mode of the installed copy; changing the group and mode of the build
directory copy is ineffective.
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** rcs2log gives you the awk error message "too many fields".
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is due to an arbitrary limit in certain versions of awk.
The solution is to use gawk (GNU awk).
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Problems with hostname resolution
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Emacs fails to understand most Internet host names, even though
the names work properly with other programs on the same system.
*** Emacs won't work with X-windows if the value of DISPLAY is HOSTNAME:0.
Fix capitalization of "Gnus".
2005-08-26 10:17:00 +00:00
*** Gnus can't make contact with the specified host for nntp.
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This typically happens on Suns and other systems that use shared
libraries. The cause is that the site has installed a version of the
shared library which uses a name server--but has not installed a
similar version of the unshared library which Emacs uses.
More info about wrong UNDERLINE_POSITION in some fonts.
2001-10-19 10:28:44 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The result is that most programs, using the shared library, work with
the nameserver, but Emacs does not.
Document problems with ange-ftp in the Windows port and the Cygwin FTP client.
2001-09-10 15:26:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The fix is to install an unshared library that corresponds to what you
installed in the shared library, and then relink Emacs.
*** empty log message ***
2000-12-29 12:26:18 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If you have already installed the name resolver in the file libresolv.a,
Simplify data_start configuration. This is a followon simplification to the fix for Bug#13650. * admin/CPP-DEFINES (DATA_START, ORDINARY_LINK): Remove. * configure.ac (CRT_DIR, LIB_STANDARD, START_FILES, DATA_START) (LD_FIRSTFLAG, ORDINARY_LINK, LIB_GCC): Remove. (AC_CHECK_HEADERS_ONCE): Remove sys/resource.h, as it's not always needed. (HAVE_DATA_START): New macro. * etc/PROBLEMS (LIBS_SYSTEM, LIBS_MACHINE, LIBS_STANDARD): Remove. Remove legacy-systems section, as this stuff is no longer applicable with current linking strategies. * src/Makefile.in (LD_FIRSTFLAG, LIB_GCC, CRT_DIR, LIB_STANDARD) (START_FILES): Remove. All uses removed. (otherobj): Remove $(VMLIMIT_OBJ), as it's now first. (ALLOBJS): Move here from autodeps.mk, and with VMLIMITS_OBJ first. (buildobj.h): Use it. ($(ALLOBJS)): Depend on globals.h. (temacs$(EXEEXT)): Use $(ALLOBJS). * src/autodeps.mk (ALLOBJS): Move to Makefile.in. * src/deps.mk (vm-limit.o): * src/makefile.w32-in ($(BLD)/vm-limit.$(O)): Do not depend on mem-limits.h. * src/emacs.c (__do_global_ctors, __do_global_ctors_aux) (__do_global_dtors, __CTOR_LIST__, __DTOR_LIST__) [__GNUC__ && !ORDINARY_LINK]: Remove. * src/mem-limits.h, src/pre-crt0.c: Remove. * src/unexaix.c, src/unexcoff.c: Don't include mem-limits.h. * src/unexcoff.c (etext): New decl. (make_hdr): Use it instead of start_of_data. * src/vm-limit.c: Move most of mem-limits.h's contents here. (data_start): New decl. It's OK if this is approximate, so simplify-away some unnecessary exactness. (POINTER): Remove; all uses removed. (data_space_start): Now char *, to avoid casts. (exceeds_lisp_ptr): New function, replacing the old EXCEEDS_LISP_PTR macro. All uses changed. (check_memory_limits): Simplify and remove casts. (start_of_data) [!CANNOT_DUMP || !SYSTEM_MALLOC]: Remove. (memory_warnings): Use data_start instead of start_of_data. Fixes: debbugs:13783
2013-02-25 05:55:37 +00:00
then you need to compile Emacs to use that library.
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
2002-01-04 10:15:04 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Emacs does not know your host's fully-qualified domain name.
Suggest to upgrade ncurses if Emacs aborts inside tparam1.
2002-01-04 10:15:04 +00:00
Expand a bit on Emacs not knowing fqdn.
2007-04-19 17:07:15 +00:00
For example, (system-name) returns some variation on
"localhost.localdomain", rather the name you were expecting.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
You need to configure your machine with a fully qualified domain name,
Expand a bit on Emacs not knowing fqdn.
2007-04-19 17:07:15 +00:00
(i.e. a name with at least one ".") either in /etc/hosts,
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
/etc/hostname, the NIS, or wherever your system calls for specifying this.
Document problems with insufficient number of colors on X.
2002-01-22 11:03:19 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If you cannot fix the configuration, you can set the Lisp variable
mail-host-address to the value you want.
Document problems with insufficient number of colors on X.
2002-01-22 11:03:19 +00:00
* etc/PROBLEMS: More removal of old stuff
2014-01-07 02:11:14 +00:00
** NFS
Document problems with insufficient number of colors on X.
2002-01-22 11:03:19 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Emacs says it has saved a file, but the file does not actually
appear on disk.
Document problems with insufficient number of colors on X.
2002-01-22 11:03:19 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can happen on certain systems when you are using NFS, if the
remote disk is full. It is due to a bug in NFS (or certain NFS
implementations), and there is apparently nothing Emacs can do to
detect the problem. Emacs checks the failure codes of all the system
calls involved in writing a file, including `close'; but in the case
where the problem occurs, none of those system calls fails.
Document problems with insufficient number of colors on X.
2002-01-22 11:03:19 +00:00
* etc/PROBLEMS: Remove some more old information.
2010-05-27 06:13:23 +00:00
** PSGML conflicts with sgml-mode.
A work-around for blinking block cursor on a GNU/Linux console.
2001-11-17 17:25:41 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
PSGML package uses the same names of some variables (like keymap)
as built-in sgml-mode.el because it was created as a replacement
of that package. The conflict will be shown if you load
sgml-mode.el before psgml.el. E.g. this could happen if you edit
HTML page and then start to work with SGML or XML file. html-mode
(from sgml-mode.el) is used for HTML file and loading of psgml.el
(for sgml-mode or xml-mode) will cause an error.
A work-around for blinking block cursor on a GNU/Linux console.
2001-11-17 17:25:41 +00:00
Document problems with PCL-CVS wrt CVS v1.12.8 and 1.12.9.
2005-02-19 12:56:21 +00:00
** PCL-CVS
*** Lines are not updated or new lines are added in the buffer upon commit.
When committing files located higher in the hierarchy than the examined
directory, some versions of the CVS program return an ambiguous message
from which PCL-CVS cannot extract the full location of the committed
files. As a result, the corresponding lines in the PCL-CVS buffer are
not updated with the new revision of these files, and new lines are
added to the top-level directory.
This can happen with CVS versions 1.12.8 and 1.12.9. Upgrade to CVS
1.12.10 or newer to fix this problem.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Miscellaneous problems
Document that help echo for menu items doesn't work on Windows.
2001-07-27 11:13:18 +00:00
* etc/PROBLEMS: Very long lines being slow is a known issue.
2011-09-24 18:27:18 +00:00
*** Editing files with very long lines is slow.
For example, simply moving through a file that contains hundreds of
thousands of characters per line is slow, and consumes a lot of CPU.
This is a known limitation of Emacs with no solution at this time.
Mention problems with Semantic.
2007-10-06 09:22:07 +00:00
*** Emacs uses 100% of CPU time
* etc/PROBLEMS: More removal of old stuff
2014-01-07 02:11:14 +00:00
This was a known problem with some old versions of the Semantic package.
The solution was to upgrade Semantic to version 2.0pre4 (distributed
with CEDET 1.0pre4) or later. Note that Emacs includes Semantic since
23.2, and this issue does not apply to the included version.
Mention problems with Semantic.
2007-10-06 09:22:07 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Self-documentation messages are garbled.
*** empty log message ***
2002-04-28 18:56:22 +00:00
Use just DOC instead of DOC-nn.mm. * lisp/loadup.el: Just use unversioned DOC. * Makefile.in (install-doc): DOC file is not version specific any more. * .bzrignore: Don't ignore DOC-* any more. * admin/quick-install-emacs: Don't prune DOC-* files a any more. * doc/lispref/loading.texi (Autoload): * doc/lispref/help.texi (Documentation Basics, Accessing Documentation) (Accessing Documentation, Accessing Documentation): DOC-* is now DOC. * etc/.gitignore: Don't ignore DOC-* any more. * lib-src/makefile.w32-in ($(DOC)): Use DOC rather than DOC-X. * msdos/sed1x.inp: Don't rewrite DOC any more. * nt/makefile.w32-in (clean, top-distclean): DOC-X doesn't exist any more. * src/Makefile.in (bootstrap-clean): DOC-* doesn't exist any more. * src/makefile.w32-in (DOC): Use just "DOC".
2013-05-15 20:12:53 +00:00
This means that the file `etc/DOC' doesn't properly correspond
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
with the Emacs executable. Redumping Emacs and then installing the
corresponding pair of files should fix the problem.
Document problems with the MS-Windows port of v21.1 and with the Cygwin port of Bash when run under Emacs.
2001-01-30 13:47:51 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Programs running under terminal emulator do not recognize `emacs'
terminal type.
Document problems with the MS-Windows port of v21.1 and with the Cygwin port of Bash when run under Emacs.
2001-01-30 13:47:51 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The cause of this is a shell startup file that sets the TERMCAP
environment variable. The terminal emulator uses that variable to
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
provide the information on the special terminal type that Emacs emulates.
Document problems with the MS-Windows port of v21.1 and with the Cygwin port of Bash when run under Emacs.
2001-01-30 13:47:51 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Rewrite your shell startup file so that it does not change TERMCAP
in such a case. You could use the following conditional which sets
it only if it is undefined.
Document problems with the MS-Windows port of v21.1 and with the Cygwin port of Bash when run under Emacs.
2001-01-30 13:47:51 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file
Document problems with NTEmacs on Windows 2000, related to the Windows i18n features.
2001-04-27 16:51:05 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Or you could set TERMCAP only when you set TERM--which should not
happen in a non-login shell.
Added note about format-time-string deficiencies on MS-Windows.
2002-03-12 20:27:24 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** In Shell mode, you get a ^M at the end of every line.
Document problems with libjpeg unavailable as a shared library.
2001-02-09 10:42:05 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This happens to people who use tcsh, because it is trying to be too
smart. It sees that the Shell uses terminal type `unknown' and turns
on the flag to output ^M at the end of each line. You can fix the
problem by adding this to your .cshrc file:
*** empty log message ***
2002-07-24 03:59:52 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
if ($?EMACS) then
* etc/NEWS: In terminal-oriented subshells, the EMACS environment variable now defaults to Emacs's absolute file name, instead of to "t". * etc/PROBLEMS: Adjust tcsh advice for this. * make-dist (EMACS): Exit and fail if the EMACS environment variable is set to something other than an absolute file name. * lisp/comint.el (comint-exec-1): Set EMACS to the full name of Emacs, not to "t". * lisp/progmodes/compile.el (compilation-start): Likewise. * lisp/progmodes/idlwave.el (idlwave-rescan-asynchronously): Don't use expand-file-name on invocation-directory, since this might mishandle special characters in invocation-directory. * man/faq.texi (Escape sequences in shell output): EMACS is now set to Emacs's absolute file name, not to "t". (^M in the shell buffer): Likewise. * man/misc.texi (Interactive Shell): Likewise.
2006-09-12 16:43:25 +00:00
if ("$EMACS" =~ /*) then
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
unset edit
stty -icrnl -onlcr -echo susp ^Z
endif
endif
Document problems with libjpeg unavailable as a shared library.
2001-02-09 10:42:05 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Emacs startup on GNU/Linux systems (and possibly other systems) is slow.
Document the problems with "Text file busy" due to buggy NFS servers.
2001-03-01 13:50:51 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can happen if the system is misconfigured and Emacs can't get the
full qualified domain name, FQDN. You should have your FQDN in the
/etc/hosts file, something like this:
Document Font Lock problems with parens in column zero.
2001-09-17 14:44:14 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
127.0.0.1 localhost
129.187.137.82 nuc04.t30.physik.tu-muenchen.de nuc04
Document Font Lock problems with parens in column zero.
2001-09-17 14:44:14 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The way to set this up may vary on non-GNU systems.
Add an entry about fonts and colors problems on KDE.
2001-12-08 10:37:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Attempting to visit remote files via ange-ftp fails.
Add an entry about fonts and colors problems on KDE.
2001-12-08 10:37:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If the error message is "ange-ftp-file-modtime: Specified time is not
representable", then this could happen when `lukemftp' is used as the
ftp client. This was reported to happen on Debian GNU/Linux, kernel
version 2.4.3, with `lukemftp' 1.5-5, but might happen on other
systems as well. To avoid this problem, switch to using the standard
ftp client. On a Debian system, type
Add an entry about fonts and colors problems on KDE.
2001-12-08 10:37:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
update-alternatives --config ftp
Add an entry about fonts and colors problems on KDE.
2001-12-08 10:37:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
and then choose /usr/bin/netkit-ftp.
Add an entry about fonts and colors problems on KDE.
2001-12-08 10:37:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** JPEG images aren't displayed.
Document problems with the MS-Windows port of v21.1 and with the Cygwin port of Bash when run under Emacs.
2001-01-30 13:47:51 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This has been reported when Emacs is built with jpeg-6a library.
Upgrading to jpeg-6b solves the problem. Configure checks for the
correct version, but this problem could occur if a binary built
against a shared libjpeg is run on a system with an older version.
Document problems with the MS-Windows port of v21.1 and with the Cygwin port of Bash when run under Emacs.
2001-01-30 13:47:51 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Dired is very slow.
Document problems with `df' slowing down Dired.
2002-03-15 15:23:15 +00:00
This could happen if invocation of the `df' program takes a long
time. Possible reasons for this include:
- ClearCase mounted filesystems (VOBs) that sometimes make `df'
response time extremely slow (dozens of seconds);
- slow automounters on some old versions of Unix;
- slow operation of some versions of `df'.
To work around the problem, you could either (a) set the variable
`directory-free-space-program' to nil, and thus prevent Emacs from
invoking `df'; (b) use `df' from the GNU Fileutils package; or
(c) use CVS, which is Free Software, instead of ClearCase.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** ps-print commands fail to find prologue files ps-prin*.ps.
Document problems with AIX's /bin/c89 compiler and with old versions of X-Symbol.
2001-12-21 12:25:47 +00:00
This can happen if you use an old version of X-Symbol package: it
defines compatibility functions which trick ps-print into thinking it
runs in XEmacs, and look for the prologue files in a wrong directory.
The solution is to upgrade X-Symbol to a later version.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** On systems with shared libraries you might encounter run-time errors
*** empty log message ***
2000-11-28 15:36:30 +00:00
from the dynamic linker telling you that it is unable to find some
shared libraries, for instance those for Xaw3d or image support.
These errors mean Emacs has been linked with a library whose shared
library is not in the default search path of the dynamic linker.
Clarify that problems with shared libraries can also happen during the build.
2001-10-30 11:58:45 +00:00
Similar problems could prevent Emacs from building, since the build
process invokes Emacs several times.
*** empty log message ***
2000-11-28 15:36:30 +00:00
On many systems, it is possible to set LD_LIBRARY_PATH in your
environment to specify additional directories where shared libraries
can be found.
Other systems allow to set LD_RUN_PATH in a similar way, but before
Emacs is linked. With LD_RUN_PATH set, the linker will include a
specified run-time search path in the executable.
Minor cleanup.
2002-01-22 23:03:47 +00:00
On some systems, Emacs can crash due to problems with dynamic
Document crashes on Irix due to some problem with `rld'.
2002-01-22 11:50:36 +00:00
linking. Specifically, on SGI Irix 6.5, crashes were reported with
backtraces like this:
(dbx) where
0 strcmp(0xf49239d, 0x4031184, 0x40302b4, 0x12, 0xf0000000, 0xf4923aa, 0x0, 0x492ddb2) ["/xlv22/ficus-jan23/work/irix/lib/libc/libc_n32_M3_ns/strings/strcmp.s":35, 0xfb7e480]
1 general_find_symbol(0xf49239d, 0x0, 0x0, 0x0, 0xf0000000, 0xf4923aa, 0x0, 0x492ddb2)
["/comp2/mtibuild/v73/workarea/v7.3/rld/rld.c":2140, 0xfb65a98]
2 resolve_symbol(0xf49239d, 0x4031184, 0x0, 0xfbdd438, 0x0, 0xf4923aa, 0x0, 0x492ddb2)
["/comp2/mtibuild/v73/workarea/v7.3/rld/rld.c":1947, 0xfb657e4]
3 lazy_text_resolve(0xd18, 0x1a3, 0x40302b4, 0x12, 0xf0000000, 0xf4923aa, 0x0, 0x492ddb2)
["/comp2/mtibuild/v73/workarea/v7.3/rld/rld.c":997, 0xfb64d44]
4 _rld_text_resolve(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
["/comp2/mtibuild/v73/workarea/v7.3/rld/rld_bridge.s":175, 0xfb6032c]
Minor cleanup.
2002-01-22 23:03:47 +00:00
(`rld' is the dynamic linker.) We don't know yet why this
happens, but setting the environment variable LD_BIND_NOW to 1 (which
Document crashes on Irix due to some problem with `rld'.
2002-01-22 11:50:36 +00:00
forces the dynamic linker to bind all shared objects early on) seems
to work around the problem.
*** empty log message ***
2000-11-28 15:36:30 +00:00
Please refer to the documentation of your dynamic linker for details.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** You request inverse video, and the first Emacs frame is in inverse
video, but later frames are not in inverse video.
Document problems with OPENSTEP's gcc. Provide a work-around.
2001-06-15 11:37:56 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can happen if you have an old version of the custom library in
your search path for Lisp packages. Use M-x list-load-path-shadows to
check whether this is true. If it is, delete the old custom library.
Document problems with OPENSTEP's gcc. Provide a work-around.
2001-06-15 11:37:56 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** When you run Ispell from Emacs, it reports a "misalignment" error.
Document problems with OPENSTEP's gcc. Provide a work-around.
2001-06-15 11:37:56 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can happen if you compiled the Ispell program to use ASCII
characters only and then try to use it from Emacs with non-ASCII
characters, like Latin-1. The solution is to recompile Ispell with
support for 8-bit characters.
Document problems with OPENSTEP's gcc. Provide a work-around.
2001-06-15 11:37:56 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
To see whether your Ispell program supports 8-bit characters, type
this at your shell's prompt:
Document problems with OPENSTEP's gcc. Provide a work-around.
2001-06-15 11:37:56 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
ispell -vv
Document problems with OPENSTEP's gcc. Provide a work-around.
2001-06-15 11:37:56 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
and look in the output for the string "NO8BIT". If Ispell says
"!NO8BIT (8BIT)", your speller supports 8-bit characters; otherwise it
does not.
Document problems with bad specifications of the default fontset.
2001-09-26 19:21:00 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
To rebuild Ispell with 8-bit character support, edit the local.h file
in the Ispell distribution and make sure it does _not_ define NO8BIT.
Then rebuild the speller.
Document problems with bad specifications of the default fontset.
2001-09-26 19:21:00 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Another possible cause for "misalignment" error messages is that the
version of Ispell installed on your machine is old. Upgrade.
Document problems with bad specifications of the default fontset.
2001-09-26 19:21:00 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Yet another possibility is that you are trying to spell-check a word
in a language that doesn't fit the dictionary you choose for use by
Ispell. (Ispell can only spell-check one language at a time, because
it uses a single dictionary.) Make sure that the text you are
spelling and the dictionary used by Ispell conform to each other.
Document problems with bad specifications of the default fontset.
2001-09-26 19:21:00 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If your spell-checking program is Aspell, it has been reported that if
you have a personal configuration file (normally ~/.aspell.conf), it
can cause this error. Remove that file, execute `ispell-kill-ispell'
in Emacs, and then try spell-checking again.
Document problems with bad specifications of the default fontset.
2001-09-26 19:21:00 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
* Runtime problems related to font handling
Document problems with bad specifications of the default fontset.
2001-09-26 19:21:00 +00:00
Document monospace font problems.
2008-10-25 17:19:12 +00:00
** Characters are displayed as empty boxes or with wrong font under X.
*** This can occur when two different versions of FontConfig are used.
For example, XFree86 4.3.0 has one version and Gnome usually comes
with a newer version. Emacs compiled with Gtk+ will then use the
newer version. In most cases the problem can be temporarily fixed by
stopping the application that has the error (it can be Emacs or any
other application), removing ~/.fonts.cache-1, and then start the
application again. If removing ~/.fonts.cache-1 and restarting
doesn't help, the application with problem must be recompiled with the
same version of FontConfig as the rest of the system uses. For KDE,
it is sufficient to recompile Qt.
*** Some fonts have a missing glyph and no default character. This is
known to occur for character number 160 (no-break space) in some
fonts, such as Lucida but Emacs sets the display table for the unibyte
and Latin-1 version of this character to display a space.
*** Some of the fonts called for in your fontset may not exist on your
X server.
Document problems with bad specifications of the default fontset.
2001-09-26 19:21:00 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Each X11 font covers just a fraction of the characters that Emacs
supports. To display the whole range of Emacs characters requires
Document monospace font problems.
2008-10-25 17:19:12 +00:00
many different fonts, collected into a fontset. You can remedy the
problem by installing additional fonts.
Document problems with compressed subdirs.el.
2001-06-20 10:52:38 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The intlfonts distribution includes a full spectrum of fonts that can
Mention etl-unicode fonts in addition to intlfonts.
2006-06-30 12:40:06 +00:00
display all the characters Emacs supports. The etl-unicode collection
of fonts (available from <URL:ftp://ftp.x.org/contrib/fonts/> and
<URL:ftp://ftp.xfree86.org/pub/mirror/X.Org/contrib/fonts/>) includes
fonts that can display many Unicode characters; they can also be used
by ps-print and ps-mule to print Unicode characters.
Document problems with compressed subdirs.el.
2001-06-20 10:52:38 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Under X11, some characters appear improperly aligned in their lines.
Document problems with compressed subdirs.el.
2001-06-20 10:52:38 +00:00
Mention etl-unicode fonts in addition to intlfonts.
2006-06-30 12:40:06 +00:00
You may have bad X11 fonts; try installing the intlfonts distribution
Document monospace font problems.
2008-10-25 17:19:12 +00:00
or the etl-unicode collection (see above).
** Under X, an unexpected monospace font is used as the default font.
When compiled with XFT, Emacs tries to use a default font named
"monospace". This is a "virtual font", which the operating system
(Fontconfig) redirects to a suitable font such as DejaVu Sans Mono.
On some systems, there exists a font that is actually named Monospace,
which takes over the virtual font. This is considered an operating
system bug; see
Document problems with compressed subdirs.el.
2001-06-20 10:52:38 +00:00
Document monospace font problems.
2008-10-25 17:19:12 +00:00
http://lists.gnu.org/archive/html/emacs-devel/2008-10/msg00696.html
Another reason for failures related to fontset.elc.
2001-11-30 08:24:22 +00:00
Document monospace font problems.
2008-10-25 17:19:12 +00:00
If you encounter this problem, set the default font to a specific font
in your .Xresources or initialization file. For instance, you can put
the following in your .Xresources:
Emacs.font: DejaVu Sans Mono 12
** Certain fonts make each line take one pixel more than it should.
This is because these fonts contain characters a little taller than
the font's nominal height. Emacs needs to make sure that lines do not
overlap.
Another reason for failures related to fontset.elc.
2001-11-30 08:24:22 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Loading fonts is very slow.
Another reason for failures related to fontset.elc.
2001-11-30 08:24:22 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
You might be getting scalable fonts instead of precomputed bitmaps.
Known scalable font directories are "Type1" and "Speedo". A font
directory contains scalable fonts if it contains the file
"fonts.scale".
Added stale load-path problems.
2001-12-02 21:03:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If this is so, re-order your X windows font path to put the scalable
font directories last. See the documentation of `xset' for details.
Added stale load-path problems.
2001-12-02 21:03:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
With some X servers, it may be necessary to take the scalable font
directories out of your path entirely, at least for Emacs 19.26.
Changes in the future may make this unnecessary.
Added stale load-path problems.
2001-12-02 21:03:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Font Lock displays portions of the buffer in incorrect faces.
Added stale load-path problems.
2001-12-02 21:03:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
By far the most frequent cause of this is a parenthesis `(' or a brace
`{' in column zero. Font Lock assumes that such a paren is outside of
any comment or string. This is of course not true in general, but the
vast majority of well-formatted program source files don't have such
parens, and therefore this assumption is used to allow optimizations
in Font Lock's syntactical analysis. These optimizations avoid some
pathological cases where jit-lock, the Just-in-Time fontification
introduced with Emacs 21.1, could significantly slow down scrolling
through the buffer, especially scrolling backwards, and also jumping
to the end of a very large buffer.
Added stale load-path problems.
2001-12-02 21:03:42 +00:00
Change release version from 21.4 to 22.1 throughout. Change development version from 21.3.50 to 22.0.50.
2005-02-09 15:50:47 +00:00
Beginning with version 22.1, a parenthesis or a brace in column zero
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
is highlighted in bold-red face if it is inside a string or a comment,
to indicate that it could interfere with Font Lock (and also with
indentation) and should be moved or escaped with a backslash.
Added stale load-path problems.
2001-12-02 21:03:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If you don't use large buffers, or have a very fast machine which
makes the delays insignificant, you can avoid the incorrect
fontification by setting the variable
`font-lock-beginning-of-syntax-function' to a nil value. (This must
be done _after_ turning on Font Lock.)
Document problems with lukemftp.
2001-05-09 15:21:44 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Another alternative is to avoid a paren in column zero. For example,
in a Lisp string you could precede the paren with a backslash.
Document problems with lukemftp.
2001-05-09 15:21:44 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** With certain fonts, when the cursor appears on a character, the
character doesn't appear--you get a solid box instead.
Document problems with lukemftp.
2001-05-09 15:21:44 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
One user on a Linux-based GNU system reported that this problem went
away with installation of a new X server. The failing server was
XFree86 3.1.1. XFree86 3.1.2 works.
Document problems with lukemftp.
2001-05-09 15:21:44 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Emacs pauses for several seconds when changing the default font.
Document the problems with MS-Windows antivirus problems.
2001-08-23 12:00:09 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This has been reported for fvwm 2.2.5 and the window manager of KDE
2.1. The reason for the pause is Xt waiting for a ConfigureNotify
event from the window manager, which the window manager doesn't send.
Xt stops waiting after a default timeout of usually 5 seconds.
Added note about subprocesses on Windows 9x.
2000-11-19 12:36:50 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
A workaround for this is to add something like
Added note about subprocesses on Windows 9x.
2000-11-19 12:36:50 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
emacs.waitForWM: false
Updates for current state of Windows port.
2002-01-14 21:07:59 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
to your X resources. Alternatively, add `(wait-for-wm . nil)' to a
frame's parameter list, like this:
Updates for current state of Windows port.
2002-01-14 21:07:59 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
(modify-frame-parameters nil '((wait-for-wm . nil)))
Documented Mouse wheel problems on MS-Windows.
2003-06-14 11:26:08 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
(this should go into your `.emacs' file).
Documented Mouse wheel problems on MS-Windows.
2003-06-14 11:26:08 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Underlines appear at the wrong position.
Documented Mouse wheel problems on MS-Windows.
2003-06-14 11:26:08 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is caused by fonts having a wrong UNDERLINE_POSITION property.
Examples are the font 7x13 on XFree prior to version 4.1, or the jmk
Derek Upham <sand at blarg.net> (tiny change) xfonts-jmk has correct UNDERLINE_POSITION from 3.0.17 onwards.
2008-05-03 21:07:14 +00:00
neep font from the Debian xfonts-jmk package prior to version 3.0.17.
To circumvent this problem, set x-use-underline-position-properties
to nil in your `.emacs'.
Documented Mouse wheel problems on MS-Windows.
2003-06-14 11:26:08 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
To see what is the value of UNDERLINE_POSITION defined by the font,
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
type `xlsfonts -lll FONT' and look at the font's UNDERLINE_POSITION property.
Exchange mail mangling.
2000-11-13 23:31:10 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** When using Exceed, fonts sometimes appear too tall.
More information about how to find the Meta keys.
2001-07-26 15:43:08 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
When the display is set to an Exceed X-server and fonts are specified
(either explicitly with the -fn option or implicitly with X resources)
then the fonts may appear "too tall". The actual character sizes are
correct but there is too much vertical spacing between rows, which
gives the appearance of "double spacing".
More information about how to find the Meta keys.
2001-07-26 15:43:08 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
To prevent this, turn off the Exceed's "automatic font substitution"
feature (in the font part of the configuration window).
More information about how to find the Meta keys.
2001-07-26 15:43:08 +00:00
Mention Tex superscript font issue.
2007-09-28 03:30:10 +00:00
** Subscript/superscript text in TeX is hard to read.
If `tex-fontify-script' is non-nil, tex-mode displays
subscript/superscript text in the faces subscript/superscript, which
are smaller than the normal font and lowered/raised. With some fonts,
nested superscripts (say) can be hard to read. Switching to a
different font, or changing your antialiasing setting (on an LCD
screen), can both make the problem disappear. Alternatively, customize
the following variables: tex-font-script-display (how much to
lower/raise); tex-suscript-height-ratio (how much smaller than
normal); tex-suscript-height-minimum (minimum height).
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
* Internationalization problems
More information about how to find the Meta keys.
2001-07-26 15:43:08 +00:00
*** empty log message ***
2006-09-28 19:10:27 +00:00
** M-{ does not work on a Spanish PC keyboard.
Many Spanish keyboards seem to ignore that combination. Emacs can't
do anything about it.
* PROBLEMS: Document Athena/Lucid internationalization problem (Bug#4333).
2009-09-13 20:46:46 +00:00
** International characters aren't displayed under X.
*** Missing X fonts
More information about how to find the Meta keys.
2001-07-26 15:43:08 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
XFree86 4 contains many fonts in iso10646-1 encoding which have
minimal character repertoires (whereas the encoding part of the font
name is meant to be a reasonable indication of the repertoire
according to the XLFD spec). Emacs may choose one of these to display
characters from the mule-unicode charsets and then typically won't be
able to find the glyphs to display many characters. (Check with C-u
C-x = .) To avoid this, you may need to use a fontset which sets the
font for the mule-unicode sets explicitly. E.g. to use GNU unifont,
include in the fontset spec:
More information about how to find the Meta keys.
2001-07-26 15:43:08 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
mule-unicode-2500-33ff:-gnu-unifont-*-iso10646-1,\
mule-unicode-e000-ffff:-gnu-unifont-*-iso10646-1,\
mule-unicode-0100-24ff:-gnu-unifont-*-iso10646-1
More information about how to find the Meta keys.
2001-07-26 15:43:08 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** The UTF-8/16/7 coding systems don't encode CJK (Far Eastern) characters.
More information about how to find the Meta keys.
2001-07-26 15:43:08 +00:00
Fix the paragraph describing the limitation of UTF-8/16/7.
2005-09-15 02:55:22 +00:00
Emacs directly supports the Unicode BMP whose code points are in the
ranges 0000-33ff and e000-ffff, and indirectly supports the parts of
CJK characters belonging to these legacy charsets:
GB2312, Big5, JISX0208, JISX0212, JISX0213-1, JISX0213-2, KSC5601
The latter support is done in Utf-Translate-Cjk mode (turned on by
default). Which Unicode CJK characters are decoded into which Emacs
charset is decided by the current language environment. For instance,
in Chinese-GB, most of them are decoded into chinese-gb2312.
OSF M-SPC.
2000-09-08 16:53:08 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If you read UTF-8 data with code points outside these ranges, the
characters appear in the buffer as raw bytes of the original UTF-8
(composed into a single quasi-character) and they will be written back
correctly as UTF-8, assuming you don't break the composed sequences.
If you read such characters from UTF-16 or UTF-7 data, they are
substituted with the Unicode `replacement character', and you lose
information.
OSF M-SPC.
2000-09-08 16:53:08 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Accented ISO-8859-1 characters are displayed as | or _.
#
1999-10-03 12:39:42 +00:00
Document problems with ISO-8859 fonts which actually include only ASCII glyphs.
2000-12-19 17:21:55 +00:00
Try other font set sizes (S-mouse-1). If the problem persists with
other sizes as well, your text is corrupted, probably through software
that is not 8-bit clean. If the problem goes away with another font
size, it's probably because some fonts pretend to be ISO-8859-1 fonts
when they are really ASCII fonts. In particular the schumacher-clean
fonts have this bug in some versions of X.
#
1999-10-03 12:39:42 +00:00
Document problems with ISO-8859 fonts which actually include only ASCII glyphs.
2000-12-19 17:21:55 +00:00
To see what glyphs are included in a font, use `xfd', like this:
#
1999-10-03 12:39:42 +00:00
Document problems with ISO-8859 fonts which actually include only ASCII glyphs.
2000-12-19 17:21:55 +00:00
xfd -fn -schumacher-clean-medium-r-normal--12-120-75-75-c-60-iso8859-1
#
1999-10-03 12:39:42 +00:00
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
If this shows only ASCII glyphs, the font is indeed the source of the problem.
#
1999-10-03 12:39:42 +00:00
Document problems with ISO-8859 fonts which actually include only ASCII glyphs.
2000-12-19 17:21:55 +00:00
The solution is to remove the corresponding lines from the appropriate
`fonts.alias' file, then run `mkfontdir' in that directory, and then run
`xset fp rehash'.
Trailing whitespace deleted.
2003-02-04 14:56:31 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** The `oc-unicode' package doesn't work with Emacs 21.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This package tries to define more private charsets than there are free
slots now. The current built-in Unicode support is actually more
flexible. (Use option `utf-translate-cjk-mode' if you need CJK
support.) Files encoded as emacs-mule using oc-unicode aren't
generally read correctly by Emacs 21.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** After a while, Emacs slips into unibyte mode.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The VM mail package, which is not part of Emacs, sometimes does
(standard-display-european t)
That should be changed to
(standard-display-european 1 t)
Document the problems with S-C-t on X.
2000-12-27 16:20:44 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
* X runtime problems
Document the problems with S-C-t on X.
2000-12-27 16:20:44 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** X keyboard problems
Document the problems with S-C-t on X.
2000-12-27 16:20:44 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** You "lose characters" after typing Compose Character key.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is because the Compose Character key is defined as the keysym
Multi_key, and Emacs (seeing that) does the proper X11
character-composition processing. If you don't want your Compose key
to do that, you can redefine it with xmodmap.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
For example, here's one way to turn it into a Meta key:
Trailing whitespace deleted.
2003-02-04 14:56:31 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
xmodmap -e "keysym Multi_key = Meta_L"
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If all users at your site of a particular keyboard prefer Meta to
Compose, you can make the remapping happen automatically by adding the
xmodmap command to the xdm setup script for that display.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Using X Windows, control-shift-leftbutton makes Emacs hang.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Use the shell command `xset bc' to make the old X Menu package work.
#
1999-10-03 12:39:42 +00:00
(C-SPC fails ...): Explicitly say fcitx in the header.
2006-04-12 06:53:43 +00:00
*** C-SPC fails to work on Fedora GNU/Linux (or with fcitx input method).
*** empty log message ***
2005-06-25 04:48:24 +00:00
Fedora Core 4 steals the C-SPC key by default for the `iiimx' program
which is the input method for some languages. It blocks Emacs users
from using the C-SPC key for `set-mark-command'.
One solutions is to remove the `<Ctrl>space' from the `Iiimx' file
which can be found in the `/usr/lib/X11/app-defaults' directory.
However, that requires root access.
Another is to specify `Emacs*useXIM: false' in your X resources.
Another is to build Emacs with the `--without-xim' configure option.
(C-SPC fails ...): Add description for fcitx.
2006-04-11 01:28:04 +00:00
The same problem happens on any other system if you are using fcitx
(Chinese input method) which by default use C-SPC for toggling. If
you want to use fcitx with Emacs, you have two choices. Toggle fcitx
by another key (e.g. C-\) by modifying ~/.fcitx/config, or be
accustomed to use C-@ for `set-mark-command'.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** M-SPC seems to be ignored as input.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
See if your X server is set up to use this as a command
for character composition.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** The S-C-t key combination doesn't get passed to Emacs on X.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This happens because some X configurations assign the Ctrl-Shift-t
combination the same meaning as the Multi_key. The offending
definition is in the file `...lib/X11/locale/iso8859-1/Compose'; there
might be other similar combinations which are grabbed by X for similar
purposes.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
We think that this can be countermanded with the `xmodmap' utility, if
you want to be able to bind one of these key sequences within Emacs.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Under X, C-v and/or other keys don't work.
#
1999-10-03 12:39:42 +00:00
These may have been intercepted by your window manager. In
particular, AfterStep 1.6 is reported to steal C-v in its default
configuration. Various Meta keys are also likely to be taken by the
configuration of the `feel'. See the WM's documentation for how to
change this.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Clicking C-mouse-2 in the scroll bar doesn't split the window.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This currently doesn't work with scroll-bar widgets (and we don't know
a good way of implementing it with widgets). If Emacs is configured
--without-toolkit-scroll-bars, C-mouse-2 on the scroll bar does work.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Inability to send an Alt-modified key, when Emacs is communicating
directly with an X server.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If you have tried to bind an Alt-modified key as a command, and it
does not work to type the command, the first thing you should check is
whether the key is getting through to Emacs. To do this, type C-h c
followed by the Alt-modified key. C-h c should say what kind of event
it read. If it says it read an Alt-modified key, then make sure you
have made the key binding correctly.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If C-h c reports an event that doesn't have the Alt modifier, it may
be because your X server has no key for the Alt modifier. The X
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
server that comes from MIT does not set up the Alt modifier by default.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If your keyboard has keys named Alt, you can enable them as follows:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
xmodmap -e 'add mod2 = Alt_L'
xmodmap -e 'add mod2 = Alt_R'
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If the keyboard has just one key named Alt, then only one of those
commands is needed. The modifier `mod2' is a reasonable choice if you
are using an unmodified MIT version of X. Otherwise, choose any
modifier bit not otherwise used.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If your keyboard does not have keys named Alt, you can use some other
keys. Use the keysym command in xmodmap to turn a function key (or
some other 'spare' key) into Alt_L or into Alt_R, and then use the
commands show above to make them modifier keys.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Note that if you have Alt keys but no Meta keys, Emacs translates Alt
into Meta. This is because of the great importance of Meta in Emacs.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Window-manager and toolkit-related problems
#
1999-10-03 12:39:42 +00:00
Mention Metacity hang on Emacs resize.
2009-11-26 07:15:33 +00:00
*** Metacity: Resizing Emacs or ALT-Tab causes X to be unresponsive.
This happens sometimes when using Metacity. Resizing Emacs or ALT-Tab:bing
makes the system unresponsive to the mouse or the keyboard. Killing Emacs
* PROBLEMS: Add note about use of backslashes in Windows paths.
2010-07-20 18:32:42 +00:00
or shifting out from X11 and back again usually cures it (i.e. Ctrl-Alt-F1
Mention Metacity hang on Emacs resize.
2009-11-26 07:15:33 +00:00
and then Alt-F7). A bug for it is here:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/231034.
Note that a permanent fix seems to be to disable "assistive technologies".
* PROBLEMS: Document Emacs/XIM/gnome-settings-terminal clash.
2006-09-30 17:58:29 +00:00
*** Gnome: Emacs receives input directly from the keyboard, bypassing XIM.
This seems to happen when gnome-settings-daemon version 2.12 or later
is running. If gnome-settings-daemon is not running, Emacs receives
input through XIM without any problem. Furthermore, this seems only
to happen in *.UTF-8 locales; zh_CN.GB2312 and zh_CN.GBK locales, for
example, work fine. A bug report has been filed in the Gnome
bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=357032
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Gnome: Emacs' xterm-mouse-mode doesn't work on the Gnome terminal.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
A symptom of this bug is that double-clicks insert a control sequence
into the buffer. The reason this happens is an apparent
incompatibility of the Gnome terminal with Xterm, which also affects
other programs using the Xterm mouse interface. A problem report has
been filed.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** KDE: When running on KDE, colors or fonts are not as specified for Emacs,
or messed up.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
For example, you could see background you set for Emacs only in the
empty portions of the Emacs display, while characters have some other
background.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This happens because KDE's defaults apply its color and font
definitions even to applications that weren't compiled for KDE. The
solution is to uncheck the "Apply fonts and colors to non-KDE apps"
option in Preferences->Look&Feel->Style (KDE 2). In KDE 3, this option
is in the "Colors" section, rather than "Style".
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Alternatively, if you do want the KDE defaults to apply to other
applications, but not to Emacs, you could modify the file `Emacs.ad'
(should be in the `/usr/share/apps/kdisplay/app-defaults/' directory)
so that it doesn't set the default background and foreground only for
Emacs. For example, make sure the following resources are either not
present or commented out:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Emacs.default.attributeForeground
Emacs.default.attributeBackground
Emacs*Foreground
Emacs*Background
#
1999-10-03 12:39:42 +00:00
(bugzilla): Mention gtk-engines-qt bug.
2007-07-14 09:02:35 +00:00
It is also reported that a bug in the gtk-engines-qt engine can cause this if
Emacs is compiled with Gtk+.
The bug is fixed in version 0.7 or newer of gtk-engines-qt.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** KDE: Emacs hangs on KDE when a large portion of text is killed.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is caused by a bug in the KDE applet `klipper' which periodically
requests the X clipboard contents from applications. Early versions
ICCM => ICCCM
2005-12-12 12:29:57 +00:00
of klipper don't implement the ICCCM protocol for large selections,
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
which leads to Emacs being flooded with selection requests. After a
* PROBLEMS: Update information about klipper on KDE.
2004-12-07 13:39:30 +00:00
while, Emacs may print a message:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Timed out waiting for property-notify event
#
1999-10-03 12:39:42 +00:00
* PROBLEMS: Update information about klipper on KDE.
2004-12-07 13:39:30 +00:00
A workaround is to not use `klipper'. An upgrade to the `klipper' that
comes with KDE 3.3 or later also solves the problem.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** CDE: Frames may cover dialogs they created when using CDE.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can happen if you have "Allow Primary Windows On Top" enabled which
seems to be the default in the Common Desktop Environment.
To change, go in to "Desktop Controls" -> "Window Style Manager"
and uncheck "Allow Primary Windows On Top".
Document problems with AUC TeX and Emacs 21.
2001-02-05 17:16:40 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Xaw3d : When using Xaw3d scroll bars without arrows, the very first mouse
click in a scroll bar might be ignored by the scroll bar widget. This
is probably a bug in Xaw3d; when Xaw3d is compiled with arrows, the
problem disappears.
Document problems with AUC TeX and Emacs 21.
2001-02-05 17:16:40 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Xaw: There are known binary incompatibilities between Xaw, Xaw3d, neXtaw,
XawM and the few other derivatives of Xaw. So when you compile with
one of these, it may not work to dynamically link with another one.
For example, strange problems, such as Emacs exiting when you type
"C-x 1", were reported when Emacs compiled with Xaw3d and libXaw was
used with neXtaw at run time.
What to do when AUC TeX don't fontify.
2001-11-20 19:14:55 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The solution is to rebuild Emacs with the toolkit version you actually
want to use, or set LD_PRELOAD to preload the same toolkit version you
built Emacs with.
What to do when AUC TeX don't fontify.
2001-11-20 19:14:55 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Open Motif: Problems with file dialogs in Emacs built with Open Motif.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
When Emacs 21 is built with Open Motif 2.1, it can happen that the
graphical file dialog boxes do not work properly. The "OK", "Filter"
and "Cancel" buttons do not respond to mouse clicks. Dragging the
file dialog window usually causes the buttons to work again.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The solution is to use LessTif instead. LessTif is a free replacement
for Motif. See the file INSTALL for information on how to do this.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Another workaround is not to use the mouse to trigger file prompts,
but to use the keyboard. This way, you will be prompted for a file in
the minibuffer instead of a graphical file dialog.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** LessTif: Problems in Emacs built with LessTif.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The problems seem to depend on the version of LessTif and the Motif
emulation for which it is set up.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Only the Motif 1.2 emulation seems to be stable enough in LessTif.
Fix some typos.
2007-04-12 04:16:47 +00:00
LessTif 0.92-17's Motif 1.2 emulation seems to work okay on FreeBSD.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
On GNU/Linux systems, lesstif-0.92.6 configured with "./configure
--enable-build-12 --enable-default-12" is reported to be the most
successful. The binary GNU/Linux package
lesstif-devel-0.92.0-1.i386.rpm was reported to have problems with
menu placement.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
On some systems, even with Motif 1.2 emulation, Emacs occasionally
locks up, grabbing all mouse and keyboard events. We still don't know
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
what causes these problems; they are not reproducible by Emacs developers.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Motif: The Motif version of Emacs paints the screen a solid color.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This has been observed to result from the following X resource:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Emacs*default.attributeFont: -*-courier-medium-r-*-*-*-140-*-*-*-*-iso8859-*
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
That the resource has this effect indicates a bug in something, but we
do not yet know what. If it is an Emacs bug, we hope someone can
explain what the bug is so we can fix it. In the mean time, removing
the resource prevents the problem.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** General X problems
Document problems with KDE's klipper.
2001-06-15 10:51:45 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Redisplay using X11 is much slower than previous Emacs versions.
Document problems with KDE's klipper.
2001-06-15 10:51:45 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
We've noticed that certain X servers draw the text much slower when
scroll bars are on the left. We don't know why this happens. If this
happens to you, you can work around it by putting the scroll bars
on the right (as they were in Emacs 19).
Document problems with KDE's klipper.
2001-06-15 10:51:45 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Here's how to do this:
Document problems with KDE's klipper.
2001-06-15 10:51:45 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
(set-scroll-bar-mode 'right)
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If you're not sure whether (or how much) this problem affects you,
try that and see how much difference it makes. To set things back
to normal, do
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
(set-scroll-bar-mode 'left)
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Error messages about undefined colors on X.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The messages might say something like this:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Unable to load color "grey95"
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
(typically, in the `*Messages*' buffer), or something like this:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Error while displaying tooltip: (error Undefined color lightyellow)
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
These problems could happen if some other X program has used up too
many colors of the X palette, leaving Emacs with insufficient system
resources to load all the colors it needs.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
A solution is to exit the offending X programs before starting Emacs.
#
1999-10-03 12:39:42 +00:00
*** empty log message ***
2006-03-11 15:46:24 +00:00
"undefined color" messages can also occur if the RgbPath entry in the
X configuration file is incorrect, or the rgb.txt file is not where
X expects to find it.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Improving performance with slow X connections.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
There are several ways to improve this performance, any subset of which can
be carried out at the same time:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
1) If you don't need X Input Methods (XIM) for entering text in some
language you use, you can improve performance on WAN links by using
the X resource useXIM to turn off use of XIM. This does not affect
the use of Emacs' own input methods, which are part of the Leim
package.
Clarify the causes for "misalignment" error messages in Ispell.
2001-06-13 12:31:09 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
2) If the connection is very slow, you might also want to consider
More details about disabling features that hamper performance with slow X connections.
2007-01-27 18:12:50 +00:00
switching off scroll bars, menu bar, and tool bar. Adding the
following forms to your .emacs file will accomplish that, but only
fix many doubled-word typos
2011-05-10 13:57:12 +00:00
after the initial frame is displayed:
More details about disabling features that hamper performance with slow X connections.
2007-01-27 18:12:50 +00:00
(scroll-bar-mode -1)
(menu-bar-mode -1)
(tool-bar-mode -1)
For still quicker startup, put these X resources in your .Xdefaults
file:
Emacs.verticalScrollBars: off
Emacs.menuBar: off
Emacs.toolBar: off
Clarify the causes for "misalignment" error messages in Ispell.
2001-06-13 12:31:09 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
3) Use ssh to forward the X connection, and enable compression on this
forwarded X connection (ssh -XC remotehostname emacs ...).
Clarify the causes for "misalignment" error messages in Ispell.
2001-06-13 12:31:09 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
4) Use lbxproxy on the remote end of the connection. This is an interface
to the low bandwidth X extension in most modern X servers, which
improves performance dramatically, at the slight expense of correctness
Spelling fixes.
2011-11-14 23:59:56 +00:00
of the X protocol. lbxproxy achieves the performance gain by grouping
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
several X requests in one TCP packet and sending them off together,
Fix some typos.
2007-04-12 04:16:47 +00:00
instead of requiring a round-trip for each X request in a separate
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
packet. The switches that seem to work best for emacs are:
-noatomsfile -nowinattr -cheaterrors -cheatevents
Note that the -nograbcmap option is known to cause problems.
For more about lbxproxy, see:
http://www.xfree86.org/4.3.0/lbxproxy.1.html
Clarify the causes for "misalignment" error messages in Ispell.
2001-06-13 12:31:09 +00:00
Add Tip to speed up copy/kill for remote X session.
2006-11-03 09:24:40 +00:00
5) If copying and killing is slow, try to disable the interaction with the
native system's clipboard by adding these lines to your .emacs file:
(setq interprogram-cut-function nil)
(setq interprogram-paste-function nil)
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Emacs gives the error, Couldn't find per display information.
Clarify the causes for "misalignment" error messages in Ispell.
2001-06-13 12:31:09 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can result if the X server runs out of memory because Emacs uses
a large number of fonts. On systems where this happens, C-h h is
likely to cause it.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
We do not know of a way to prevent the problem.
*** empty log message ***
2002-08-17 00:08:54 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Emacs does not notice when you release the mouse.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
There are reports that this happened with (some) Microsoft mice and
that replacing the mouse made it stop.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** You can't select from submenus (in the X toolkit version).
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
On certain systems, mouse-tracking and selection in top-level menus
works properly with the X toolkit, but neither of them works when you
bring up a submenu (such as Bookmarks or Compare or Apply Patch, in
the Files menu).
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This works on most systems. There is speculation that the failure is
due to bugs in old versions of X toolkit libraries, but no one really
knows. If someone debugs this and finds the precise cause, perhaps a
workaround can be found.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** An error message such as `X protocol error: BadMatch (invalid
parameter attributes) on protocol request 93'.
Advise not to use Exceed 6.1.
2002-05-03 09:56:01 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This comes from having an invalid X resource, such as
emacs*Cursor: black
(which is invalid because it specifies a color name for something
that isn't a color.)
Advise not to use Exceed 6.1.
2002-05-03 09:56:01 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The fix is to correct your X resources.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Slow startup on X11R6 with X windows.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If Emacs takes two minutes to start up on X11R6, see if your X
resources specify any Adobe fonts. That causes the type-1 font
renderer to start up, even if the font you asked for is not a type-1
font.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
One way to avoid this problem is to eliminate the type-1 fonts from
your font path, like this:
#
1999-10-03 12:39:42 +00:00
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
xset -fp /usr/X11R6/lib/X11/fonts/Type1/
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Pull-down menus appear in the wrong place, in the toolkit version of Emacs.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
An X resource of this form can cause the problem:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Emacs*geometry: 80x55+0+0
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This resource is supposed to apply, and does apply, to the menus
individually as well as to Emacs frames. If that is not what you
want, rewrite the resource.
Update Solaris 2.6 and 7 problems.
1999-11-30 18:44:14 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
To check thoroughly for such resource specifications, use `xrdb
-query' to see what resources the X server records, and also look at
the user's ~/.Xdefaults and ~/.Xdefaults-* files.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Emacs running under X Windows does not handle mouse clicks.
*** `emacs -geometry 80x20' finds a file named `80x20'.
Added information on how to set options in CDE so dialogs are not covered by the parent frame.
2002-03-02 11:14:03 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
One cause of such problems is having (setq term-file-prefix nil) in
your .emacs file. Another cause is a bad value of EMACSLOADPATH in
the environment.
Added information on how to set options in CDE so dialogs are not covered by the parent frame.
2002-03-02 11:14:03 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** X Windows doesn't work if DISPLAY uses a hostname.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
People have reported kernel bugs in certain systems that cause Emacs
not to work with X Windows if DISPLAY is set using a host name. But
the problem does not occur if DISPLAY is set to `unix:0.0'. I think
the bug has to do with SIGIO or FIONREAD.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
You may be able to compensate for the bug by doing (set-input-mode nil nil).
However, that has the disadvantage of turning off interrupts, so that
you are unable to quit out of a Lisp program by typing C-g.
#
1999-10-03 12:39:42 +00:00
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
*** Prevent double pastes in X
The problem: a region, such as a command, is pasted twice when you copy
it with your mouse from GNU Emacs to an xterm or an RXVT shell in X.
The solution: try the following in your X configuration file,
/etc/X11/xorg.conf This should enable both PS/2 and USB mice for
single copies. You do not need any other drivers or options.
Section "InputDevice"
Identifier "Generic Mouse"
Driver "mousedev"
Option "Device" "/dev/input/mice"
EndSection
Add PROBLEMS entry for X clipboard managers slowing down exit See http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8869#92
2012-02-25 01:54:17 +00:00
*** Emacs is slow to exit in X
After you use e.g. C-x C-c to exit, it takes many seconds before the
Emacs window disappears. If Emacs was started from a terminal, you
see the message:
Error saving to X clipboard manager.
If the problem persists, set `x-select-enable-clipboard-manager' to nil.
As the message suggests, this problem occurs when Emacs thinks you
have a clipboard manager program running, but has trouble contacting it.
If you don't want to use a clipboard manager, you can set the
suggested variable. Or you can make Emacs not wait so long by
reducing the value of `x-selection-timeout', either in .emacs or with
X resources.
Sometimes this problem is due to a bug in your clipboard manager.
Updating to the latest version of the manager can help.
For example, in the Xfce 4.8 desktop environment, the clipboard
manager in versions of xfce4-settings-helper before 4.8.2 is buggy;
https://bugzilla.xfce.org/show_bug.cgi?id=7588 .
* PROBLEMS: Mention Ubuntu warnings about libdbusmenu.
2013-04-07 11:01:56 +00:00
*** Warning messages when running in Ubuntu
When you start Emacs you may see something like this:
(emacs:2286): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion
`GTK_IS_MENU_SHELL(menu)' failed
Fix typos
2013-04-10 01:20:51 +00:00
This happens if the Emacs binary has been renamed. The cause is the Ubuntu
* PROBLEMS: Mention Ubuntu warnings about libdbusmenu.
2013-04-07 11:01:56 +00:00
appmenu concept. It tries to track Emacs menus and show them in the top
panel, instead of in each Emacs window. This is not properly implemented,
so it fails for Emacs. The order of menus is wrong, and things like copy/paste
Fix typos
2013-04-10 01:20:51 +00:00
that depend on what state Emacs is in are usually wrong (i.e. paste disabled
* PROBLEMS: Mention Ubuntu warnings about libdbusmenu.
2013-04-07 11:01:56 +00:00
even if you should be able to paste, and similar).
You can get back menus on each frame by starting emacs like this:
% env UBUNTU_MENUPROXY= emacs
Fix some typos.
2007-04-12 04:16:47 +00:00
* Runtime problems on character terminals
#
1999-10-03 12:39:42 +00:00
Document Bug#5541.
2010-03-19 15:15:27 +00:00
** The meta key does not work on xterm.
Typing M-x rings the terminal bell, and inserts a string like ";120~".
For recent xterm versions (>= 216), Emacs uses xterm's modifyOtherKeys
feature to generate strings for key combinations that are not
otherwise usable. One circumstance in which this can cause problems
is if you have specified the X resource
xterm*VT100.Translations
to contain translations that use the meta key. Then xterm will not
use meta in modified function-keys, which confuses Emacs. To fix
this, you can remove the X resource or put this in your init file:
(xterm-remove-modify-other-keys)
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Emacs spontaneously displays "I-search: " at the bottom of the screen.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This means that Control-S/Control-Q (XON/XOFF) "flow control" is being
used. C-s/C-q flow control is bad for Emacs editors because it takes
away C-s and C-q as user commands. Since editors do not output long
streams of text without user commands, there is no need for a
user-issuable "stop output" command in an editor; therefore, a
properly designed flow control mechanism would transmit all possible
input characters without interference. Designing such a mechanism is
easy, for a person with at least half a brain.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
There are three possible reasons why flow control could be taking place:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
1) Terminal has not been told to disable flow control
2) Insufficient padding for the terminal in use
3) Some sort of terminal concentrator or line switch is responsible
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
First of all, many terminals have a set-up mode which controls whether
they generate XON/XOFF flow control characters. This must be set to
Merge in a few snippets just deleted from faq.texi.
2009-06-16 02:55:46 +00:00
"no XON/XOFF" in order for Emacs to work. (For example, on a VT220
you may select "No XOFF" in the setup menu.) Sometimes there is an
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
escape sequence that the computer can send to turn flow control off
and on. If so, perhaps the termcap `ti' string should turn flow
control off, and the `te' string should turn it on.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Once the terminal has been told "no flow control", you may find it
needs more padding. The amount of padding Emacs sends is controlled
by the termcap entry for the terminal in use, and by the output baud
rate as known by the kernel. The shell command `stty' will print
your output baud rate; `stty' with suitable arguments will set it if
it is wrong. Setting to a higher speed causes increased padding. If
the results are wrong for the correct speed, there is probably a
problem in the termcap entry. You must speak to a local Unix wizard
to fix this. Perhaps you are just using the wrong terminal type.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
For terminals that lack a "no flow control" mode, sometimes just
giving lots of padding will prevent actual generation of flow control
codes. You might as well try it.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If you are really unlucky, your terminal is connected to the computer
through a concentrator which sends XON/XOFF flow control to the
computer, or it insists on sending flow control itself no matter how
much padding you give it. Unless you can figure out how to turn flow
control off on this concentrator (again, refer to your local wizard),
you are screwed! You should have the terminal or concentrator
replaced with a properly designed one. In the mean time, some drastic
measures can make Emacs semi-work.
NBSP as hollow box
2001-01-11 23:09:41 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
You can make Emacs ignore C-s and C-q and let the operating system
handle them. To do this on a per-session basis, just type M-x
enable-flow-control RET. You will see a message that C-\ and C-^ are
now translated to C-s and C-q. (Use the same command M-x
enable-flow-control to turn *off* this special mode. It toggles flow
control handling.)
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If C-\ and C-^ are inconvenient for you (for example, if one of them
is the escape character of your terminal concentrator), you can choose
other characters by setting the variables flow-control-c-s-replacement
and flow-control-c-q-replacement. But choose carefully, since all
other control characters are already used by emacs.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
IMPORTANT: if you type C-s by accident while flow control is enabled,
Emacs output will freeze, and you will have to remember to type C-q in
order to continue.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If you work in an environment where a majority of terminals of a
certain type are flow control hobbled, you can use the function
`enable-flow-control-on' to turn on this flow control avoidance scheme
automatically. Here is an example:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
(enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If this isn't quite correct (e.g. you have a mixture of flow-control hobbled
and good vt200 terminals), you can still run enable-flow-control
manually.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
I have no intention of ever redesigning the Emacs command set for the
assumption that terminals use C-s/C-q flow control. XON/XOFF flow
control technique is a bad design, and terminals that need it are bad
merchandise and should not be purchased. Now that X is becoming
widespread, XON/XOFF seems to be on the way out. If you can get some
use out of GNU Emacs on inferior terminals, more power to you, but I
will not make Emacs worse for properly designed systems for the sake
of inferior systems.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Control-S and Control-Q commands are ignored completely.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
For some reason, your system is using brain-damaged C-s/C-q flow
control despite Emacs's attempts to turn it off. Perhaps your
terminal is connected to the computer through a concentrator
that wants to use flow control.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
You should first try to tell the concentrator not to use flow control.
If you succeed in this, try making the terminal work without
flow control, as described in the preceding section.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If that line of approach is not successful, map some other characters
into C-s and C-q using keyboard-translate-table. The example above
shows how to do this with C-^ and C-\.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Screen is updated wrong, but only on one kind of terminal.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This could mean that the termcap entry you are using for that
terminal is wrong, or it could mean that Emacs has a bug handing
the combination of features specified for that terminal.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The first step in tracking this down is to record what characters
Emacs is sending to the terminal. Execute the Lisp expression
(open-termscript "./emacs-script") to make Emacs write all
terminal output into the file ~/emacs-script as well; then do
what makes the screen update wrong, and look at the file
and decode the characters using the manual for the terminal.
There are several possibilities:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
1) The characters sent are correct, according to the terminal manual.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
In this case, there is no obvious bug in Emacs, and most likely you
need more padding, or possibly the terminal manual is wrong.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
2) The characters sent are incorrect, due to an obscure aspect
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
of the terminal behavior not described in an obvious way by termcap.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This case is hard. It will be necessary to think of a way for
Emacs to distinguish between terminals with this kind of behavior
and other terminals that behave subtly differently but are
classified the same by termcap; or else find an algorithm for
Emacs to use that avoids the difference. Such changes must be
tested on many kinds of terminals.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
3) The termcap entry is wrong.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
See the file etc/TERMS for information on changes
that are known to be needed in commonly used termcap entries
for certain terminals.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
4) The characters sent are incorrect, and clearly cannot be
right for any terminal with the termcap entry you were using.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is unambiguously an Emacs bug, and can probably be fixed
in termcap.c, tparam.c, term.c, scroll.c, cm.c or dispnew.c.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Control-S and Control-Q commands are ignored completely on a net connection.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Some versions of rlogin (and possibly telnet) do not pass flow
control characters to the remote system to which they connect.
On such systems, emacs on the remote system cannot disable flow
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
control on the local system. Sometimes `rlogin -8' will avoid this problem.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
One way to cure this is to disable flow control on the local host
(the one running rlogin, not the one running rlogind) using the
stty command, before starting the rlogin process. On many systems,
Merge in a few snippets just deleted from faq.texi.
2009-06-16 02:55:46 +00:00
"stty start u stop u" will do this. On some systems, use
* PROBLEMS: Add note about use of backslashes in Windows paths.
2010-07-20 18:32:42 +00:00
"stty -ixon" instead.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Some versions of tcsh will prevent even this from working. One way
around this is to start another shell before starting rlogin, and
issue the stty command to disable flow control from that shell.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If none of these methods work, the best solution is to type
M-x enable-flow-control at the beginning of your emacs session, or
if you expect the problem to continue, add a line such as the
following to your .emacs (on the host running rlogind):
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
(enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
#
1999-10-03 12:39:42 +00:00
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
See the entry about spontaneous display of I-search (above) for more info.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Output from Control-V is slow.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
On many bit-map terminals, scrolling operations are fairly slow.
Often the termcap entry for the type of terminal in use fails
to inform Emacs of this. The two lines at the bottom of the screen
before a Control-V command are supposed to appear at the top after
the Control-V command. If Emacs thinks scrolling the lines is fast,
it will scroll them to the top of the screen.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If scrolling is slow but Emacs thinks it is fast, the usual reason is
that the termcap entry for the terminal you are using does not
specify any padding time for the `al' and `dl' strings. Emacs
concludes that these operations take only as much time as it takes to
send the commands at whatever line speed you are using. You must
fix the termcap entry to specify, for the `al' and `dl', as much
time as the operations really take.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Currently Emacs thinks in terms of serial lines which send characters
at a fixed rate, so that any operation which takes time for the
terminal to execute must also be padded. With bit-map terminals
operated across networks, often the network provides some sort of
flow control so that padding is never needed no matter how slow
an operation is. You must still specify a padding time if you want
Emacs to realize that the operation takes a long time. This will
cause padding characters to be sent unnecessarily, but they do
not really cost much. They will be transmitted while the scrolling
is happening and then discarded quickly by the terminal.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Most bit-map terminals provide commands for inserting or deleting
multiple lines at once. Define the `AL' and `DL' strings in the
termcap entry to say how to do these things, and you will have
fast output without wasted padding characters. These strings should
each contain a single %-spec saying how to send the number of lines
to be scrolled. These %-specs are like those in the termcap
`cm' string.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
You should also define the `IC' and `DC' strings if your terminal
has a command to insert or delete multiple characters. These
take the number of positions to insert or delete as an argument.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
A `cs' string to set the scrolling region will reduce the amount
of motion you see on the screen when part of the screen is scrolled.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** You type Control-H (Backspace) expecting to delete characters.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Put `stty dec' in your .login file and your problems will disappear
after a day or two.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The choice of Backspace for erasure was based on confusion, caused by
the fact that backspacing causes erasure (later, when you type another
character) on most display terminals. But it is a mistake. Deletion
of text is not the same thing as backspacing followed by failure to
overprint. I do not wish to propagate this confusion by conforming
to it.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
For this reason, I believe `stty dec' is the right mode to use,
and I have designed Emacs to go with that. If there were a thousand
other control characters, I would define Control-h to delete as well;
but there are not very many other control characters, and I think
that providing the most mnemonic possible Help character is more
important than adapting to people who don't use `stty dec'.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If you are obstinate about confusing buggy overprinting with deletion,
you can redefine Backspace in your .emacs file:
(global-set-key "\b" 'delete-backward-char)
You can probably access help-command via f1.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Colors are not available on a tty or in xterm.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Emacs 21 supports colors on character terminals and terminal
emulators, but this support relies on the terminfo or termcap database
entry to specify that the display supports color. Emacs looks at the
"Co" capability for the terminal to find out how many colors are
supported; it should be non-zero to activate the color support within
Emacs. (Most color terminals support 8 or 16 colors.) If your system
uses terminfo, the name of the capability equivalent to "Co" is
"colors".
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
In addition to the "Co" capability, Emacs needs the "op" (for
``original pair'') capability, which tells how to switch the terminal
back to the default foreground and background colors. Emacs will not
use colors if this capability is not defined. If your terminal entry
doesn't provide such a capability, try using the ANSI standard escape
sequence \E[00m (that is, define a new termcap/terminfo entry and make
it use your current terminal's entry plus \E[00m for the "op"
capability).
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Finally, the "NC" capability (terminfo name: "ncv") tells Emacs which
attributes cannot be used with colors. Setting this capability
incorrectly might have the effect of disabling colors; try setting
this capability to `0' (zero) and see if that helps.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Emacs uses the database entry for the terminal whose name is the value
of the environment variable TERM. With `xterm', a common terminal
entry that supports color is `xterm-color', so setting TERM's value to
`xterm-color' might activate the color support on an xterm-compatible
emulator.
#
1999-10-03 12:39:42 +00:00
Change release version from 21.4 to 22.1 throughout. Change development version from 21.3.50 to 22.0.50.
2005-02-09 15:50:47 +00:00
Beginning with version 22.1, Emacs supports the --color command-line
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
option which may be used to force Emacs to use one of a few popular
modes for getting colors on a tty. For example, --color=ansi8 sets up
for using the ANSI-standard escape sequences that support 8 colors.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Some modes do not use colors unless you turn on the Font-lock mode.
Some people have long ago set their `~/.emacs' files to turn on
Font-lock on X only, so they won't see colors on a tty. The
recommended way of turning on Font-lock is by typing "M-x
global-font-lock-mode RET" or by customizing the variable
`global-font-lock-mode'.
#
1999-10-03 12:39:42 +00:00
Doc fix for xterm-extra-capabilities * lisp/term/xterm.el (xterm-extra-capabilities): Doc fix. * etc/PROBLEMS: Mention xterm-extra-capabilities issue.
2012-03-31 20:22:04 +00:00
** Unexpected characters inserted into the buffer when you start Emacs.
See eg http://debbugs.gnu.org/11129
This can happen when you start Emacs in -nw mode in an Xterm.
For example, in the *scratch* buffer, you might see something like:
0;276;0c
This is more likely to happen if you are using Emacs over a slow
connection, and begin typing before Emacs is ready to respond.
This occurs when Emacs tries to query the terminal to see what
capabilities it supports, and gets confused by the answer.
To avoid it, set xterm-extra-capabilities to a value other than
`check' (the default). See that variable's documentation (in
term/xterm.el) for more details.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
* Runtime problems specific to individual Unix variants
Document problems with DJGPP and NT's `redir' program.
2001-04-25 21:33:25 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** GNU/Linux
Document problems with DJGPP and NT's `redir' program.
2001-04-25 21:33:25 +00:00
Linux kernel 2.6.10 may corrupt process output. Warn that using CVS+SSH may corrupt files, include work-around.
2005-06-08 12:13:32 +00:00
*** GNU/Linux: Process output is corrupted.
There is a bug in Linux kernel 2.6.10 PTYs that can cause emacs to
read corrupted process output.
*** GNU/Linux: Remote access to CVS with SSH causes file corruption.
If you access a remote CVS repository via SSH, files may be corrupted
due to bad interaction between CVS, SSH, and libc.
To fix the problem, save the following script into a file, make it
executable, and set CVS_RSH environment variable to the file name of
the script:
#!/bin/bash
exec 2> >(exec cat >&2 2>/dev/null)
exec ssh "$@"
* etc/PROBLEMS: Add note about svn+ssh. (Bug#7791)
2011-01-18 02:31:59 +00:00
*** GNU/Linux: Truncated svn annotate output with SSH.
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7791
The symptoms are: you are accessing a svn repository over SSH.
You use vc-annotate on a large (several thousand line) file, and the
result is truncated around the 1000 line mark. It works fine with
other access methods (eg http), or from outside Emacs.
This may be a similar libc/SSH issue to the one mentioned above for CVS.
A similar workaround seems to be effective: create a script with the
same contents as the one used above for CVS_RSH, and set the SVN_SSH
environment variable to point to it.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** GNU/Linux: On Linux-based GNU systems using libc versions 5.4.19 through
5.4.22, Emacs crashes at startup with a segmentation fault.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This problem happens if libc defines the symbol __malloc_initialized.
One known solution is to upgrade to a newer libc version. 5.4.33 is
known to work.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** GNU/Linux: After upgrading to a newer version of Emacs,
the Meta key stops working.
More about long file names and the MSDOS port.
2001-06-24 13:16:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This was reported to happen on a GNU/Linux system distributed by
Mandrake. The reason is that the previous version of Emacs was
modified by Mandrake to make the Alt key act as the Meta key, on a
keyboard where the Windows key is the one which produces the Meta
modifier. A user who started using a newer version of Emacs, which
was not hacked by Mandrake, expected the Alt key to continue to act as
Meta, and was astonished when that didn't happen.
More about long file names and the MSDOS port.
2001-06-24 13:16:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The solution is to find out what key on your keyboard produces the Meta
modifier, and use that key instead. Try all of the keys to the left
and to the right of the space bar, together with the `x' key, and see
which combination produces "M-x" in the echo area. You can also use
the `xmodmap' utility to show all the keys which produce a Meta
modifier:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
xmodmap -pk | egrep -i "meta|alt"
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
A more convenient way of finding out which keys produce a Meta modifier
is to use the `xkbprint' utility, if it's available on your system:
More about long file names and the MSDOS port.
2001-06-24 13:16:33 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
xkbprint 0:0 /tmp/k.ps
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This produces a PostScript file `/tmp/k.ps' with a picture of your
keyboard; printing that file on a PostScript printer will show what
keys can serve as Meta.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The `xkeycaps' also shows a visual representation of the current
keyboard settings. It also allows to modify them.
#
1999-10-03 12:39:42 +00:00
Fix typo.
2006-06-03 21:55:47 +00:00
*** GNU/Linux: slow startup on Linux-based GNU systems.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
People using systems based on the Linux kernel sometimes report that
startup takes 10 to 15 seconds longer than `usual'.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is because Emacs looks up the host name when it starts.
Normally, this takes negligible time; the extra delay is due to
improper system configuration. This problem can occur for both
networked and non-networked machines.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Here is how to fix the configuration. It requires being root.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
**** Networked Case.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
First, make sure the files `/etc/hosts' and `/etc/host.conf' both
exist. The first line in the `/etc/hosts' file should look like this
(replace HOSTNAME with your host name):
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
127.0.0.1 HOSTNAME
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Also make sure that the `/etc/host.conf' files contains the following
lines:
Document failure to start due to old version of ncurses.
2002-05-18 11:10:35 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
order hosts, bind
multi on
Clarify "can't open termcap database" item.
2002-10-25 05:58:04 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Any changes, permanent and temporary, to the host name should be
indicated in the `/etc/hosts' file, since it acts a limited local
database of addresses and names (e.g., some SLIP connections
dynamically allocate ip addresses).
Document failure to start due to old version of ncurses.
2002-05-18 11:10:35 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
**** Non-Networked Case.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The solution described in the networked case applies here as well.
However, if you never intend to network your machine, you can use a
simpler solution: create an empty `/etc/host.conf' file. The command
`touch /etc/host.conf' suffices to create the file. The `/etc/hosts'
file is not necessary with this approach.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** GNU/Linux: Emacs on a tty switches the cursor to large blinking block.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This was reported to happen on some GNU/Linux systems which use
ncurses version 5.0, but could be relevant for other versions as well.
These versions of ncurses come with a `linux' terminfo entry, where
the "cvvis" capability (termcap "vs") is defined as "\E[?25h\E[?8c"
(show cursor, change size). This escape sequence switches on a
blinking hardware text-mode cursor whose size is a full character
cell. This blinking cannot be stopped, since a hardware cursor
always blinks.
Clarify the causes for "misalignment" error messages in Ispell.
2001-06-13 12:31:09 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
A work-around is to redefine the "cvvis" capability so that it
enables a *software* cursor. The software cursor works by inverting
the colors of the character at point, so what you see is a block
cursor that doesn't blink. For this to work, you need to redefine
the "cnorm" capability as well, so that it operates on the software
cursor instead of the hardware cursor.
Clarify the causes for "misalignment" error messages in Ispell.
2001-06-13 12:31:09 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
To this end, run "infocmp linux > linux-term", edit the file
`linux-term' to make both the "cnorm" and "cvvis" capabilities send
the sequence "\E[?25h\E[?17;0;64c", and then run "tic linux-term" to
produce a modified terminfo entry.
Clarify the causes for "misalignment" error messages in Ispell.
2001-06-13 12:31:09 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Alternatively, if you want a blinking underscore as your Emacs cursor,
change the "cvvis" capability to send the "\E[?25h\E[?0c" command.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** GNU/Linux: Error messages `internal facep []' happen on GNU/Linux systems.
#
1999-10-03 12:39:42 +00:00
There is a report that replacing libc.so.5.0.9 with libc.so.5.2.16
caused this to start happening. People are not sure why, but the
problem seems unlikely to be in Emacs itself. Some suspect that it
is actually Xlib which won't work with libc.so.5.2.16.
Using the old library version is a workaround.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** FreeBSD
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** FreeBSD 2.1.5: useless symbolic links remain in /tmp or other
directories that have the +t bit.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is because of a kernel bug in FreeBSD 2.1.5 (fixed in 2.2).
Emacs uses symbolic links to implement file locks. In a directory
with +t bit, the directory owner becomes the owner of the symbolic
link, so that it cannot be removed by anyone else.
#
1999-10-03 12:39:42 +00:00
All the cool platforms support CLASH_DETECTION... * configure.ac (CLASH_DETECTION): Define unconditionally. Every platform using configure supports it. * src/s/aix4-2.h, src/s/bsd-common.h, src/s/cygwin.h, src/s/darwin.h: * src/s/gnu-linux.h, src/s/hpux10-20.h, src/s/template.h: * src/s/usg5-4-common.h: Move CLASH_DETECTION to configure. * etc/PROBLEMS: Recommend customizing create-lockfiles rather than recompiling with CLASH_DETECTION unset.
2012-07-11 07:07:19 +00:00
If you don't like those useless links, you can customize
the option `create-lockfiles'.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** FreeBSD: Getting a Meta key on the console.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
By default, neither Alt nor any other key acts as a Meta key on
FreeBSD, but this can be changed using kbdcontrol(1). Dump the
current keymap to a file with the command
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
$ kbdcontrol -d >emacs.kbd
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Edit emacs.kbd, and give the key you want to be the Meta key the
definition `meta'. For instance, if your keyboard has a ``Windows''
key with scan code 105, change the line for scan code 105 in emacs.kbd
to look like this
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
105 meta meta meta meta meta meta meta meta O
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
to make the Windows key the Meta key. Load the new keymap with
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
$ kbdcontrol -l emacs.kbd
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** HP-UX
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** HP/UX : Shell mode gives the message, "`tty`: Ambiguous".
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
christos@theory.tn.cornell.edu says:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The problem is that in your .cshrc you have something that tries to
execute `tty`. If you are not running the shell on a real tty then
tty will print "not a tty". Csh expects one word in some places,
but tty is giving it back 3.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The solution is to add a pair of quotes around `tty` to make it a single
word:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
if (`tty` == "/dev/console")
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
should be changed to:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
if ("`tty`" == "/dev/console")
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Even better, move things that set up terminal sections out of .cshrc
and into .login.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** HP/UX: `Pid xxx killed due to text modification or page I/O error'.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
On HP/UX, you can get that error when the Emacs executable is on an NFS
file system. HP/UX responds this way if it tries to swap in a page and
does not get a response from the server within a timeout whose default
value is just ten seconds.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If this happens to you, extend the timeout period.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** HP/UX: The right Alt key works wrong on German HP keyboards (and perhaps
other non-English HP keyboards too).
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is because HP-UX defines the modifiers wrong in X. Here is a
shell script to fix the problem; be sure that it is run after VUE
configures the X server.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
xmodmap 2> /dev/null - << EOF
keysym Alt_L = Meta_L
keysym Alt_R = Meta_R
EOF
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
xmodmap - << EOF
clear mod1
keysym Mode_switch = NoSymbol
add mod1 = Meta_L
keysym Meta_R = Mode_switch
add mod2 = Mode_switch
EOF
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** HP/UX: "Cannot find callback list" messages from dialog boxes in
Emacs built with Motif.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This problem resulted from a bug in GCC 2.4.5. Newer GCC versions
such as 2.7.0 fix the problem.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** HP/UX: Emacs does not recognize the AltGr key.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
To fix this, set up a file ~/.dt/sessions/sessionetc with executable
rights, containing this text:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
--------------------------------
xmodmap 2> /dev/null - << EOF
keysym Alt_L = Meta_L
keysym Alt_R = Meta_R
EOF
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
xmodmap - << EOF
clear mod1
keysym Mode_switch = NoSymbol
add mod1 = Meta_L
keysym Meta_R = Mode_switch
add mod2 = Mode_switch
EOF
--------------------------------
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** HP/UX 11.0: Emacs makes HP/UX 11.0 crash.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is a bug in HPUX; HPUX patch PHKL_16260 is said to fix it.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** AIX
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** AIX: Trouble using ptys.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
People often install the pty devices on AIX incorrectly.
Use `smit pty' to reinstall them properly.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** AIXterm: Your Delete key sends a Backspace to the terminal.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The solution is to include in your .Xdefaults the lines:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*aixterm.Translations: #override <Key>BackSpace: string(0x7f)
aixterm*ttyModes: erase ^?
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This makes your Backspace key send DEL (ASCII 127).
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** AIX: If linking fails because libXbsd isn't found, check if you
are compiling with the system's `cc' and CFLAGS containing `-O5'. If
so, you have hit a compiler bug. Please make sure to re-configure
Emacs so that it isn't compiled with `-O5'.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** AIX 4.3.x or 4.4: Compiling fails.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This could happen if you use /bin/c89 as your compiler, instead of
the default `cc'. /bin/c89 treats certain warnings, such as benign
redefinitions of macros, as errors, and fails the build. A solution
is to use the default compiler `cc'.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** AIX 4: Some programs fail when run in a Shell buffer
with an error message like No terminfo entry for "unknown".
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
On AIX, many terminal type definitions are not installed by default.
`unknown' is one of them. Install the "Special Generic Terminal
Definitions" to make them defined.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Solaris
#
1999-10-03 12:39:42 +00:00
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
We list bugs in current versions here. See also the section on legacy
systems.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** On Solaris, C-x doesn't get through to Emacs when you use the console.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is a Solaris feature (at least on Intel x86 cpus). Type C-r
C-r C-t, to toggle whether C-x gets through to Emacs.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Problem with remote X server on Suns.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
On a Sun, running Emacs on one machine with the X server on another
may not work if you have used the unshared system libraries. This
is because the unshared libraries fail to use YP for host name lookup.
As a result, the host name you specify may not be recognized.
#
1999-10-03 12:39:42 +00:00
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
*** Solaris 2.6: Emacs crashes with SIGBUS or SIGSEGV on Solaris after you delete a frame.
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
We suspect that this is a bug in the X libraries provided by
Sun. There is a report that one of these patches fixes the bug and
makes the problem stop:
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
105216-01 105393-01 105518-01 105621-01 105665-01 105615-02 105216-02
105667-01 105401-08 105615-03 105621-02 105686-02 105736-01 105755-03
106033-01 105379-01 105786-01 105181-04 105379-03 105786-04 105845-01
105284-05 105669-02 105837-01 105837-02 105558-01 106125-02 105407-01
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
Another person using a newer system (kernel patch level Generic_105181-06)
suspects that the bug was fixed by one of these more recent patches:
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
106040-07 SunOS 5.6: X Input & Output Method patch
106222-01 OpenWindows 3.6: filemgr (ff.core) fixes
105284-12 Motif 1.2.7: sparc Runtime library patch
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
*** Solaris 7 or 8: Emacs reports a BadAtom error (from X)
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
This happens when Emacs was built on some other version of Solaris.
Rebuild it on Solaris 8.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** When using M-x dbx with the SparcWorks debugger, the `up' and `down'
commands do not move the arrow in Emacs.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
You can fix this by adding the following line to `~/.dbxinit':
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
dbxenv output_short_file_name off
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
*** On Solaris, CTRL-t is ignored by Emacs when you use
the fr.ISO-8859-15 locale (and maybe other related locales).
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
You can fix this by editing the file:
#
1999-10-03 12:39:42 +00:00
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
/usr/openwin/lib/locale/iso8859-15/Compose
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
Near the bottom there is a line that reads:
#
1999-10-03 12:39:42 +00:00
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
Ctrl<t> <quotedbl> <Y> : "\276" threequarters
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
that should read:
#
1999-10-03 12:39:42 +00:00
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
Ctrl<T> <quotedbl> <Y> : "\276" threequarters
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
Note the lower case <t>. Changing this line should make C-t work.
#
1999-10-03 12:39:42 +00:00
Add "Point before start of properties" bug.
2008-02-15 16:08:27 +00:00
*** On Solaris, Emacs fails to set menu-bar-update-hook on startup, with error
"Error in menu-bar-update-hook: (error Point before start of properties)".
This seems to be a GCC optimization bug that occurs for GCC 4.1.2 (-g
and -g -O2) and GCC 4.2.3 (-g -O and -g -O2). You can fix this by
compiling with GCC 4.2.3 or CC 5.7, with no optimizations.
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
** Irix
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Irix 6.5: Emacs crashes on the SGI R10K, when compiled with GCC.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This seems to be fixed in GCC 2.95.
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
*** Irix: Trouble using ptys, or running out of ptys.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The program mkpts (which may be in `/usr/adm' or `/usr/sbin') needs to
be set-UID to root, or non-root programs like Emacs will not be able
to allocate ptys reliably.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
* Runtime problems specific to MS-Windows
#
1999-10-03 12:39:42 +00:00
* PROBLEMS (Windows): Add entry about TCC/4NT and App Paths keys.
2009-01-28 23:44:12 +00:00
** PATH can contain unexpanded environment variables
Old releases of TCC (version 9) and 4NT (up to version 8) do not correctly
expand App Paths entries of type REG_EXPAND_SZ. When Emacs is run from TCC
and such an entry exists for emacs.exe, exec-path will contain the
unexpanded entry. This has been fixed in TCC 10. For more information,
see bug#2062.
Mention trouble with XKeymacs and the Windows keys.
2009-01-24 20:39:10 +00:00
** Setting w32-pass-rwindow-to-system and w32-pass-lwindow-to-system to nil
does not prevent the Start menu from popping up when the left or right
``Windows'' key is pressed.
This was reported to happen when XKeymacs is installed. At least with
XKeymacs Version 3.47, deactivating XKeymacs when Emacs is active is
not enough to avoid its messing with the keyboard input. Exiting
XKeymacs completely is reported to solve the problem.
Emacs now requires ws2_32.dll on Windows.
2006-07-14 15:03:52 +00:00
** Windows 95 and networking.
To support server sockets, Emacs 22.1 loads ws2_32.dll. If this file
is missing, all Emacs networking features are disabled.
Old versions of Windows 95 may not have the required DLL. To use
Emacs' networking features on Windows 95, you must install the
"Windows Socket 2" update available from MicroSoft's support Web.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Emacs exits with "X protocol error" when run with an X server for MS-Windows.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
A certain X server for Windows had a bug which caused this.
Supposedly the newer 32-bit version of this server doesn't have the
problem.
Trailing whitespace deleted.
2003-02-04 14:56:31 +00:00
bug #719
2008-08-16 03:41:26 +00:00
** Emacs crashes when opening a file with a UNC path and rails-mode is loaded.
Loading rails-mode seems to interfere with UNC path handling. This has been
reported as a bug against both Emacs and rails-mode, so look for an updated
rails-mode that avoids this crash, or avoid using UNC paths if using
rails-mode.
** Known problems with the MS-Windows port of Emacs 22.3
Added note about create-fontset-from-ascii-font problem on MS-Windows.
2005-10-25 21:28:54 +00:00
M-x term does not work on Windows.
2008-03-17 23:34:55 +00:00
M-x term does not work on MS-Windows. TTY emulation on Windows is
undocumented, and programs such as stty which are used on posix platforms
to control tty emulation do not exist for native windows terminals.
Added note about create-fontset-from-ascii-font problem on MS-Windows.
2005-10-25 21:28:54 +00:00
Using create-fontset-from-ascii-font or the --font startup parameter
with a Chinese, Japanese or Korean font leads to display problems.
Use a Latin-only font as your default font. If you want control over
which font is used to display Chinese, Japanese or Korean character,
use create-fontset-from-fontset-spec to define a fontset.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Frames are not refreshed while the File or Font dialog or a pop-up menu
is displayed. This also means help text for pop-up menus is not
displayed at all. This is because message handling under Windows is
synchronous, so we cannot handle repaint (or any other) messages while
waiting for a system function to return the result of the dialog or
pop-up menu interaction.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Windows 95 and Windows NT up to version 4.0 do not support help text
for menus. Help text is only available in later versions of Windows.
#
1999-10-03 12:39:42 +00:00
Describe problems on Windows with ClearType enabled.
2007-04-09 08:42:03 +00:00
When "ClearType" method is selected as the "method to smooth edges of
screen fonts" (in Display Properties, Appearance tab, under
"Effects"), there are various problems related to display of
Fixed part of Cleartype problem.
2008-02-15 23:24:04 +00:00
characters: Bold fonts can be hard to read, small portions of some
characters could appear chopped, etc. This happens because, under
ClearType, characters are drawn outside their advertised bounding box.
Emacs 21 disabled the use of ClearType, whereas Emacs 22 allows it and
has some code to enlarge the width of the bounding box. Apparently,
this display feature needs more changes to get it 100% right. A
workaround is to disable ClearType.
Describe problems on Windows with ClearType enabled.
2007-04-09 08:42:03 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
There are problems with display if mouse-tracking is enabled and the
mouse is moved off a frame, over another frame then back over the first
frame. A workaround is to click the left mouse button inside the frame
after moving back into it.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Some minor flickering still persists during mouse-tracking, although
not as severely as in 21.1.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
An inactive cursor remains in an active window after the Windows
Manager driven switch of the focus, until a key is pressed.
#
1999-10-03 12:39:42 +00:00
Update information about non-support of Windows input methods.
2007-04-08 08:59:32 +00:00
Windows input methods are not recognized by Emacs. However, some
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
of these input methods cause the keyboard to send characters encoded
in the appropriate coding system (e.g., ISO 8859-1 for Latin-1
Update information about non-support of Windows input methods.
2007-04-08 08:59:32 +00:00
characters, ISO 8859-8 for Hebrew characters, etc.). To make these
input methods work with Emacs, set the keyboard coding system to the
appropriate value after you activate the Windows input method. For
example, if you activate the Hebrew input method, type this:
C-x RET k hebrew-iso-8bit RET
(Emacs ought to recognize the Windows language-change event and set up
the appropriate keyboard encoding automatically, but it doesn't do
that yet.) In addition, to use these Windows input methods, you
should set your "Language for non-Unicode programs" (on Windows XP,
this is on the Advanced tab of Regional Settings) to the language of
the input method.
#
1999-10-03 12:39:42 +00:00
(MS-Windows problems): How to bind non-ASCII keys with modifiers.
2007-03-31 10:01:51 +00:00
To bind keys that produce non-ASCII characters with modifiers, you
must specify raw byte codes. For instance, if you want to bind
META-a-grave to a command, you need to specify this in your `~/.emacs':
(global-set-key [?\M-\340] ...)
The above example is for the Latin-1 environment where the byte code
of the encoded a-grave is 340 octal. For other environments, use the
encoding appropriate to that environment.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The %b specifier for format-time-string does not produce abbreviated
month names with consistent widths for some locales on some versions
of Windows. This is caused by a deficiency in the underlying system
library function.
#
1999-10-03 12:39:42 +00:00
display-time-world does not exist yet.
2007-10-21 01:01:33 +00:00
The function set-time-zone-rule gives incorrect results for many
non-US timezones. This is due to over-simplistic handling of
daylight savings switchovers by the Windows libraries.
display-world-time does not work on Windows.
2007-10-17 22:27:24 +00:00
Mention problems with files larger than 4GB on MS-Windows.
2007-04-27 13:37:31 +00:00
Files larger than 4GB cause overflow in the size (represented as a
32-bit integer) reported by `file-attributes'. This affects Dired as
well, since the Windows port uses a Lisp emulation of `ls' that relies
on `file-attributes'.
Document that :data is unsupported for playing sound on Windows.
2007-06-16 12:50:37 +00:00
Sound playing is not supported with the `:data DATA' key-value pair.
You _must_ use the `:file FILE' method.
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
** Typing Alt-Shift has strange effects on MS-Windows.
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
This combination of keys is a command to change keyboard layout. If
you proceed to type another non-modifier key before you let go of Alt
and Shift, the Alt and Shift act as modifiers in the usual way. A
more permanent work around is to change it to another key combination,
Provide exact information about customizing Alt-Shift on Windows XP.
2007-11-17 11:16:40 +00:00
or disable it in the "Regional and Language Options" applet of the
Control Panel. (The exact sequence of mouse clicks in the "Regional
and Language Options" applet needed to find the key combination that
changes the keyboard layout depends on your Windows version; for XP,
in the Languages tab, click "Details" and then "Key Settings".)
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
** Interrupting Cygwin port of Bash from Emacs doesn't work.
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
Cygwin 1.x builds of the ported Bash cannot be interrupted from the
MS-Windows version of Emacs. This is due to some change in the Bash
port or in the Cygwin library which apparently make Bash ignore the
keyboard interrupt event sent by Emacs to Bash. (Older Cygwin ports
of Bash, up to b20.1, did receive SIGINT from Emacs.)
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
** Accessing remote files with ange-ftp hangs the MS-Windows version of Emacs.
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
If the FTP client is the Cygwin port of GNU `ftp', this appears to be
due to some bug in the Cygwin DLL or some incompatibility between it
and the implementation of asynchronous subprocesses in the Windows
port of Emacs. Specifically, some parts of the FTP server responses
are not flushed out, apparently due to buffering issues, which
confuses ange-ftp.
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
The solution is to downgrade to an older version of the Cygwin DLL
(version 1.3.2 was reported to solve the problem), or use the stock
Windows FTP client, usually found in the `C:\WINDOWS' or 'C:\WINNT'
directory. To force ange-ftp use the stock Windows client, set the
variable `ange-ftp-ftp-program-name' to the absolute file name of the
client's executable. For example:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
(setq ange-ftp-ftp-program-name "c:/windows/ftp.exe")
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If you want to stick with the Cygwin FTP client, you can work around
this problem by putting this in your `.emacs' file:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
(setq ange-ftp-ftp-program-args '("-i" "-n" "-g" "-v" "--prompt" "")
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** lpr commands don't work on MS-Windows with some cheap printers.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This problem may also strike other platforms, but the solution is
likely to be a global one, and not Emacs specific.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Many cheap inkjet, and even some cheap laser printers, do not
print plain text anymore, they will only print through graphical
printer drivers. A workaround on MS-Windows is to use Windows' basic
built in editor to print (this is possibly the only useful purpose it
has):
#
1999-10-03 12:39:42 +00:00
Fix commenting convention in PROBLEMS example
2012-04-04 07:30:02 +00:00
(setq printer-name "") ; notepad takes the default
(setq lpr-command "notepad") ; notepad
(setq lpr-switches nil) ; not needed
(setq lpr-printer-switch "/P") ; run notepad as batch printer
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Antivirus software interacts badly with the MS-Windows version of Emacs.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The usual manifestation of these problems is that subprocesses don't
work or even wedge the entire system. In particular, "M-x shell RET"
was reported to fail to work. But other commands also sometimes don't
work when an antivirus package is installed.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The solution is to switch the antivirus software to a less aggressive
mode (e.g., disable the ``auto-protect'' feature), or even uninstall
or disable it entirely.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Pressing the mouse button on MS-Windows does not give a mouse-2 event.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is usually a problem with the mouse driver. Because most Windows
programs do not do anything useful with the middle mouse button, many
mouse drivers allow you to define the wheel press to do something
different. Some drivers do not even have the option to generate a
middle button press. In such cases, setting the wheel press to
"scroll" sometimes works if you press the button twice. Trying a
generic mouse driver might help.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Scrolling the mouse wheel on MS-Windows always scrolls the top window.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is another common problem with mouse drivers. Instead of
generating scroll events, some mouse drivers try to fake scroll bar
movement. But they are not intelligent enough to handle multiple
scroll bars within a frame. Trying a generic mouse driver might help.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Mail sent through Microsoft Exchange in some encodings appears to be
mangled and is not seen correctly in Rmail or Gnus. We don't know
exactly what happens, but it isn't an Emacs problem in cases we've
seen.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** On MS-Windows, you cannot use the right-hand ALT key and the left-hand
CTRL key together to type a Control-Meta character.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is a consequence of a misfeature beyond Emacs's control.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Under Windows, the AltGr key on international keyboards generates key
events with the modifiers Right-Alt and Left-Ctrl. Since Emacs cannot
distinguish AltGr from an explicit Right-Alt and Left-Ctrl
combination, whenever it sees Right-Alt and Left-Ctrl it assumes that
AltGr has been pressed. The variable `w32-recognize-altgr' can be set
to nil to tell Emacs that AltGr is really Ctrl and Alt.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Under some X-servers running on MS-Windows, Emacs' display is incorrect.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The symptoms are that Emacs does not completely erase blank areas of the
screen during scrolling or some other screen operations (e.g., selective
display or when killing a region). M-x recenter will cause the screen
to be completely redisplayed and the "extra" characters will disappear.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is known to occur under Exceed 6, and possibly earlier versions
as well; it is reportedly solved in version 6.2.0.16 and later. The
problem lies in the X-server settings.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
There are reports that you can solve the problem with Exceed by
running `Xconfig' from within NT, choosing "X selection", then
un-checking the boxes "auto-copy X selection" and "auto-paste to X
selection".
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Of this does not work, please inform bug-gnu-emacs@gnu.org. Then
please call support for your X-server and see if you can get a fix.
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
If you do, please send it to bug-gnu-emacs@gnu.org so we can list it here.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
* Build-time problems
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Configuration
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** The `configure' script doesn't find the jpeg library.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
There are reports that this happens on some systems because the linker
by default only looks for shared libraries, but jpeg distribution by
default only installs a nonshared version of the library, `libjpeg.a'.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If this is the problem, you can configure the jpeg library with the
`--enable-shared' option and then rebuild libjpeg. This produces a
shared version of libjpeg, which you need to install. Finally, rerun
the Emacs configure script, which should now find the jpeg library.
Alternatively, modify the generated src/Makefile to link the .a file
explicitly, and edit src/config.h to define HAVE_JPEG.
#
1999-10-03 12:39:42 +00:00
(Configuration): Add entries on compiler/preprocessor mismatch, and on preprocessor inserting whitespace.
2007-04-04 02:58:38 +00:00
*** `configure' warns ``accepted by the compiler, rejected by the preprocessor''.
This indicates a mismatch between the C compiler and preprocessor that
configure is using. For example, on Solaris 10 trying to use
CC=/opt/SUNWspro/bin/cc (the Sun Studio compiler) together with
CPP=/usr/ccs/lib/cpp can result in errors of this form (you may also
see the error ``"/usr/include/sys/isa_defs.h", line 500: undefined control'').
The solution is to tell configure to use the correct C preprocessor
for your C compiler (CPP="/opt/SUNWspro/bin/cc -E" in the above
example).
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Compilation
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Building Emacs over NFS fails with ``Text file busy''.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This was reported to happen when building Emacs on a GNU/Linux system
Fix some typos.
2007-04-12 04:16:47 +00:00
(Red Hat Linux 6.2) using a build directory automounted from Solaris
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
(SunOS 5.6) file server, but it might not be limited to that
configuration alone. Presumably, the NFS server doesn't commit the
files' data to disk quickly enough, and the Emacs executable file is
left ``busy'' for several seconds after Emacs has finished dumping
itself. This causes the subsequent commands which invoke the dumped
Emacs executable to fail with the above message.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
In some of these cases, a time skew between the NFS server and the
machine where Emacs is built is detected and reported by GNU Make
(it says that some of the files have modification time in the future).
This might be a symptom of NFS-related problems.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If the NFS server runs on Solaris, apply the Solaris patch 105379-05
(Sunos 5.6: /kernel/misc/nfssrv patch). If that doesn't work, or if
you have a different version of the OS or the NFS server, you can
force the NFS server to use 1KB blocks, which was reported to fix the
problem albeit at a price of slowing down file I/O. You can force 1KB
blocks by specifying the "-o rsize=1024,wsize=1024" options to the
`mount' command, or by adding ",rsize=1024,wsize=1024" to the mount
options in the appropriate system configuration file, such as
`/etc/auto.home'.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Alternatively, when Make fails due to this problem, you could wait for
a few seconds and then invoke Make again. In one particular case,
waiting for 10 or more seconds between the two Make invocations seemed
to work around the problem.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Similar problems can happen if your machine NFS-mounts a directory
onto itself. Suppose the Emacs sources live in `/usr/local/src' and
you are working on the host called `marvin'. Then an entry in the
`/etc/fstab' file like the following is asking for trouble:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
marvin:/usr/local/src /usr/local/src ...options.omitted...
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The solution is to remove this line from `etc/fstab'.
#
1999-10-03 12:39:42 +00:00
Add information on compiling 32-bit Emacs on 64-bit GNU/Linux. Update copyright for years post-Emacs 21 to present.
2007-01-13 02:25:58 +00:00
*** Building a 32-bit executable on a 64-bit GNU/Linux architecture.
First ensure that the necessary 32-bit system libraries and include
files are installed. Then use:
env CC="gcc -m32" ./configure --build=i386-linux-gnu \
--x-libraries=/usr/X11R6/lib
(using the location of the 32-bit X libraries on your system).
* etc/PROBLEMS: Update Cygwin GCC information. (Bug#6458)
2010-06-19 02:34:30 +00:00
*** Building Emacs for Cygwin can fail with GCC 3
As of Emacs 22.1, there have been stability problems with Cygwin
builds of Emacs using GCC 3. Cygwin users are advised to use GCC 4.
Document problems with Cygwin builds of GCC 3.4.4.
2006-11-04 12:11:21 +00:00
* PROBLEMS: Mention problem with Cygwin 1.5.19.
2010-07-27 19:50:01 +00:00
*** Building Emacs 23.3 and later will fail under Cygwin 1.5.19
This is a consequence of a change to src/dired.c on 2010-07-27. The
issue is that Cygwin 1.5.19 did not have d_ino in 'struct dirent'.
See
http://lists.gnu.org/archive/html/emacs-devel/2010-07/msg01266.html
Document problems on MS-Windows with incompatible regex.h headers. PROBLEMS: Mention problems on MS-Windows with incompatible regex.h headers.
2010-03-27 12:52:55 +00:00
*** Building the native MS-Windows port fails due to unresolved externals
The linker error messages look like this:
oo-spd/i386/ctags.o:ctags.c:(.text+0x156e): undefined reference to `_imp__re_set_syntax'
collect2: ld returned 1 exit status
This happens because GCC finds an incompatible header regex.h
somewhere on the include path, before the version of regex.h supplied
with Emacs. One such incompatible version of regex.h is part of the
GnuWin32 Regex package.
The solution is to remove the incompatible regex.h from the include
path, when compiling Emacs. Alternatively, re-run the configure.bat
script with the "-isystem C:/GnuWin32/include" switch (adapt for your
system's place where you keep the GnuWin32 include files) -- this will
cause the compiler to search headers in the directories specified by
the Emacs Makefile _before_ it looks in the GnuWin32 include
directories.
Document problems with Cygwin builds of GCC 3.4.4.
2006-11-04 12:11:21 +00:00
*** Building the native MS-Windows port with Cygwin GCC can fail.
#
1999-10-03 12:39:42 +00:00
(Cygwin GCC): recent -> some, as the information is no longer current.
2008-02-04 11:26:17 +00:00
Emacs may not build using some Cygwin builds of GCC, such as Cygwin
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
version 1.1.8, using the default configure settings. It appears to be
necessary to specify the -mwin32 flag when compiling, and define
__MSVCRT__, like so:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
configure --with-gcc --cflags -mwin32 --cflags -D__MSVCRT__
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Building the MS-Windows port fails with a CreateProcess failure.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Some versions of mingw32 make on some versions of Windows do not seem
to detect the shell correctly. Try "make SHELL=cmd.exe", or if that
fails, try running make from Cygwin bash instead.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Building `ctags' for MS-Windows with the MinGW port of GCC fails.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This might happen due to a bug in the MinGW header assert.h, which
defines the `assert' macro with a trailing semi-colon. The following
patch to assert.h should solve this:
#
1999-10-03 12:39:42 +00:00
Fix last change. Indent the patch for assert.h one column.
2007-03-03 11:03:50 +00:00
*** include/assert.h.orig Sun Nov 7 02:41:36 1999
--- include/assert.h Mon Jan 29 11:49:10 2001
***************
*** 41,47 ****
/*
* If not debugging, assert does nothing.
*/
! #define assert(x) ((void)0);
#else /* debugging enabled */
--- 41,47 ----
/*
* If not debugging, assert does nothing.
*/
! #define assert(x) ((void)0)
#else /* debugging enabled */
#
1999-10-03 12:39:42 +00:00
Note added about the Visual Studio 2005 problem.
2007-03-03 01:18:47 +00:00
*** Building the MS-Windows port with Visual Studio 2005 fails.
#
1999-10-03 12:39:42 +00:00
Note added about the Visual Studio 2005 problem.
2007-03-03 01:18:47 +00:00
Microsoft no longer ships the single threaded version of the C library
with their compiler, and the multithreaded static library is missing
Fix last change. Indent the patch for assert.h one column.
2007-03-03 11:03:50 +00:00
some functions that Microsoft have deemed non-threadsafe. The
Note added about the Visual Studio 2005 problem.
2007-03-03 01:18:47 +00:00
dynamically linked C library has all the functions, but there is a
conflict between the versions of malloc in the DLL and in Emacs, which
is not resolvable due to the way Windows does dynamic linking.
#
1999-10-03 12:39:42 +00:00
(CPP): Note problem with resource compiler of MSVC.
2009-02-04 09:13:18 +00:00
We recommend the use of the MinGW port of GCC for compiling Emacs, as
Note added about the Visual Studio 2005 problem.
2007-03-03 01:18:47 +00:00
not only does it not suffer these problems, but it is also Free
software like Emacs.
#
1999-10-03 12:39:42 +00:00
(CPP): Note problem with resource compiler of MSVC.
2009-02-04 09:13:18 +00:00
*** Building the MS-Windows port with Visual Studio fails compiling emacs.rc
If the build fails with the following message then the problem
described here most likely applies:
../nt/emacs.rc(1) : error RC2176 : old DIB in icons\emacs.ico; pass it
through SDKPAINT
The Emacs icon contains a high resolution PNG icon for Vista, which is
not recognized by older versions of the resource compiler. There are
several workarounds for this problem:
1. Use Free MinGW tools to compile, which do not have this problem.
2. Install the latest Windows SDK.
3. Replace emacs.ico with an older or edited icon.
* PROBLEMS: Add note about use of backslashes in Windows paths.
2010-07-20 18:32:42 +00:00
*** Building the MS-Windows port complains about unknown escape sequences.
Errors and warnings can look like this:
w32.c:1959:27: error: \x used with no following hex digits
w32.c:1959:27: warning: unknown escape sequence '\i'
This happens when paths using backslashes are passed to the compiler or
linker (via -I and possibly other compiler flags); when these paths are
included in source code, the backslashes are interpreted as escape sequences.
See http://lists.gnu.org/archive/html/emacs-devel/2010-07/msg00995.html
The fix is to use forward slashes in all paths passed to the compiler.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Linking
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Building Emacs with a system compiler fails to link because of an
undefined symbol such as __eprintf which does not appear in Emacs.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can happen if some of the libraries linked into Emacs were built
with GCC, but Emacs itself is being linked with a compiler other than
GCC. Object files compiled with GCC might need some helper functions
from libgcc.a, the library which comes with GCC, but the system
compiler does not instruct the linker to search libgcc.a during the
link stage.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
A solution is to link with GCC, like this:
#
1999-10-03 12:39:42 +00:00
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
make CC=gcc
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Since the .o object files already exist, this will not recompile Emacs
with GCC, but just restart by trying again to link temacs.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Sun with acc: Link failure when using acc on a Sun.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
To use acc, you need additional options just before the libraries, such as
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
/usr/lang/SC2.0.1/values-Xt.o -L/usr/lang/SC2.0.1/cg87 -L/usr/lang/SC2.0.1
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
and you need to add -lansi just before -lc.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The precise file names depend on the compiler version, so we
cannot easily arrange to supply them.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Linking says that the functions insque and remque are undefined.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Change oldXMenu/Makefile by adding insque.o to the variable OBJS.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** `tparam' reported as a multiply-defined symbol when linking with ncurses.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This problem results from an incompatible change in ncurses, in
version 1.9.9e approximately. This version is unable to provide a
definition of tparm without also defining tparam. This is also
incompatible with Terminfo; as a result, the Emacs Terminfo support
does not work with this version of ncurses.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The fix is to install a newer version of ncurses, such as version 4.2.
#
1999-10-03 12:39:42 +00:00
Mention Ubuntu make weirdness.
2008-09-05 04:01:53 +00:00
** Bootstrapping
Bootstrapping (compiling the .el files) is normally only necessary
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
with development builds, since the .elc files are pre-compiled in releases.
Mention Ubuntu make weirdness.
2008-09-05 04:01:53 +00:00
*** "No rule to make target" with Ubuntu 8.04 make 3.81-3build1
Compiling the lisp files fails at random places, complaining:
"No rule to make target `/path/to/some/lisp.elc'".
The causes of this problem are not understood. Using GNU make 3.81 compiled
from source, rather than the Ubuntu version, worked. See Bug#327,821.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Dumping
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Linux: Segfault during `make bootstrap' under certain recent versions of the Linux kernel.
#
1999-10-03 12:39:42 +00:00
Fix some typos.
2007-04-12 04:16:47 +00:00
With certain recent Linux kernels (like the one of Red Hat Fedora Core
* PROBLEMS (Fedora Core 4 GNU/Linux: Segfault during dumping): Added it again.
2005-07-03 21:47:06 +00:00
1 and newer), the new "Exec-shield" functionality is enabled by default, which
Added that emacs tries to handle exec-shield at build time.
2005-07-03 21:50:53 +00:00
creates a different memory layout that breaks the emacs dumper. Emacs tries
to handle this at build time, but if the workaround used fails, these
instructions can be useful.
* PROBLEMS (Fedora Core 4 GNU/Linux: Segfault during dumping): Added it again.
2005-07-03 21:47:06 +00:00
The work-around explained here is not enough on Fedora Core 4 (and possible
newer). Read the next item.
#
1999-10-03 12:39:42 +00:00
* PROBLEMS: Updated exec-shield description.
2004-09-25 20:39:13 +00:00
Configure can overcome the problem of exec-shield if the architecture is
x86 and the program setarch is present. On other architectures no
workaround is known.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
You can check the Exec-shield state like this:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
cat /proc/sys/kernel/exec-shield
#
1999-10-03 12:39:42 +00:00
* PROBLEMS: Updated exec-shield description.
2004-09-25 20:39:13 +00:00
It returns non-zero when Exec-shield is enabled, 0 otherwise. Please
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
read your system documentation for more details on Exec-shield and
* PROBLEMS: Updated exec-shield description.
2004-09-25 20:39:13 +00:00
associated commands. Exec-shield can be turned off with this command:
echo "0" > /proc/sys/kernel/exec-shield
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
When Exec-shield is enabled, building Emacs will segfault during the
execution of this command:
#
1999-10-03 12:39:42 +00:00
* PROBLEMS: Updated exec-shield description.
2004-09-25 20:39:13 +00:00
./temacs --batch --load loadup [dump|bootstrap]
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
To work around this problem, it is necessary to temporarily disable
* PROBLEMS: Updated exec-shield description.
2004-09-25 20:39:13 +00:00
Exec-shield while building Emacs, or, on x86, by using the `setarch'
command when running temacs like this:
setarch i386 ./temacs --batch --load loadup [dump|bootstrap]
#
1999-10-03 12:39:42 +00:00
Emacs now requires ws2_32.dll on Windows.
2006-07-14 15:03:52 +00:00
(Fedora Core 4 GNU/Linux: Segfault during dumping): New.
2005-06-28 18:52:26 +00:00
*** Fedora Core 4 GNU/Linux: Segfault during dumping.
In addition to exec-shield explained above "Linux: Segfault during
`make bootstrap' under certain recent versions of the Linux kernel"
item, Linux kernel shipped with Fedora Core 4 randomizes the virtual
* PROBLEMS (Fedora Core 4 GNU/Linux: Segfault during dumping): Added it again.
2005-07-03 21:47:06 +00:00
address space of a process. As the result dumping may fail even if
you turn off exec-shield. In this case, use the -R option to the setarch
(Fedora Core 4 GNU/Linux: Segfault during dumping): New.
2005-06-28 18:52:26 +00:00
command:
* PROBLEMS (Fedora Core 4 GNU/Linux: Segfault during dumping): -R comes after i386 in setarch command.
2005-07-19 09:35:56 +00:00
setarch i386 -R ./temacs --batch --load loadup [dump|bootstrap]
(Fedora Core 4 GNU/Linux: Segfault during dumping): New.
2005-06-28 18:52:26 +00:00
or
Emacs now requires ws2_32.dll on Windows.
2006-07-14 15:03:52 +00:00
setarch i386 -R make bootstrap
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Fatal signal in the command temacs -l loadup inc dump.
#
1999-10-03 12:39:42 +00:00
This command is the final stage of building Emacs. It is run by the
* bitmaps/README: * xfns.c: * termcap.c: * term.c: * syswait.h: * systty.h: * systime.h: * syssignal.h: * sysdep.c: * process.h: * process.c: * print.c: * ndir.h: * lread.c: * keyboard.c: * getpagesize.h: * floatfns.c: * fileio.c: * emacs.c: * doc.c: * dispnew.c: * dired.c: * data.c: * callproc.c: * buffer.c: * README: * Makefile.in: * s/template.h: * s/msdos.h: * m/vax.h: Remove VMS support. * s/vms.h: * vlimit.h: * uaf.h: * temacs.opt: * param.h: * ioctl.h: Remove file. * descrip.mms: * compile.com: Remove file. * Create.c: Remove VMS support. * message.el (Module): * gnus-start.el (Module): * gnus-registry.el (Module): * textmodes/texinfmt.el: * nxml/nxml-enc.el: * mail/feedmail.el: * international/mule.el: * international/latexenc.el: * emulation/viper-util.el: * emulation/viper-init.el: * emulation/viper-ex.el: * emacs-lisp/bytecomp.el: * version.el: * subr.el: * startup.el: * sort.el: * shadowfile.el: * recentf.el: * printing.el: * paths.el: * minibuffer.el: * ls-lisp.el: * loadup.el: * hippie-exp.el: * finder.el: * files.el: * ediff-util.el: * ediff-ptch.el: * ediff-init.el: * ediff-diff.el: * dired.el: * dired-aux.el: * cus-edit.el: * bindings.el: * arc-mode.el: * add-log.el: Remove VMS support. * obsolete/vmsproc.el: * obsolete/vms-pmail.el: * obsolete/vms-patch.el: Remove file. * etags.c: * emacsclient.c: Remove VMS support. * termcap.src: Remove file. * README: * PROBLEMS: * MACHINES: Remove VMS info. * ediff.texi: Remove VMS support. * os.texi: * intro.texi: * files.texi: Remove VMS support. * emacs.texi: Remove VMS support. * make-dist: * README: Remove VMS support. * vms: Remove directory.
2008-07-31 05:33:56 +00:00
Makefile in the src subdirectory.
#
1999-10-03 12:39:42 +00:00
It has been known to get fatal errors due to insufficient swapping
space available on the machine.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
On 68000s, it has also happened because of bugs in the
#
1999-10-03 12:39:42 +00:00
subroutine `alloca'. Verify that `alloca' works right, even
for large blocks (many pages).
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** test-distrib says that the distribution has been clobbered.
*** or, temacs prints "Command key out of range 0-127".
*** or, temacs runs and dumps emacs, but emacs totally fails to work.
*** or, temacs gets errors dumping emacs.
#
1999-10-03 12:39:42 +00:00
This can be because the .elc files have been garbled. Do not be
fooled by the fact that most of a .elc file is text: these are
binary files and can contain all 256 byte values.
In particular `shar' cannot be used for transmitting GNU Emacs.
It typically truncates "lines". What appear to be "lines" in
a binary file can of course be of any length. Even once `shar'
itself is made to work correctly, `sh' discards null characters
when unpacking the shell archive.
I have also seen character \177 changed into \377. I do not know
what transfer means caused this problem. Various network
file transfer programs are suspected of clobbering the high bit.
If you have a copy of Emacs that has been damaged in its
nonprinting characters, you can fix them:
1) Record the names of all the .elc files.
2) Delete all the .elc files.
3) Recompile alloc.c with a value of PURESIZE twice as large.
(See puresize.h.) You might as well save the old alloc.o.
4) Remake emacs. It should work now.
5) Running emacs, do Meta-x byte-compile-file repeatedly
to recreate all the .elc files that used to exist.
You may need to increase the value of the variable
max-lisp-eval-depth to succeed in running the compiler interpreted
on certain .el files. 400 was sufficient as of last report.
6) Reinstall the old alloc.o (undoing changes to alloc.c if any)
and remake temacs.
7) Remake emacs. It should work now, with valid .elc files.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** temacs prints "Pure Lisp storage exhausted".
#
1999-10-03 12:39:42 +00:00
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
This means that the Lisp code loaded from the .elc and .el files
during temacs -l loadup inc dump took up more space than was allocated.
#
1999-10-03 12:39:42 +00:00
This could be caused by
1) adding code to the preloaded Lisp files
2) adding more preloaded files in loadup.el
3) having a site-init.el or site-load.el which loads files.
Note that ANY site-init.el or site-load.el is nonstandard;
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
if you have received Emacs from some other site and it contains a
site-init.el or site-load.el file, consider deleting that file.
#
1999-10-03 12:39:42 +00:00
4) getting the wrong .el or .elc files
(not from the directory you expected).
5) deleting some .elc files that are supposed to exist.
This would cause the source files (.el files) to be
loaded instead. They take up more room, so you lose.
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
6) a bug in the Emacs distribution which underestimates the space required.
#
1999-10-03 12:39:42 +00:00
If the need for more space is legitimate, change the definition
of PURESIZE in puresize.h.
But in some of the cases listed above, this problem is a consequence
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
of something else that is wrong. Be sure to check and fix the real problem.
#
1999-10-03 12:39:42 +00:00
(Dumping): Mention OpenBSD macppc problem.
2007-05-17 07:58:16 +00:00
*** OpenBSD 4.0 macppc: Segfault during dumping.
The build aborts with signal 11 when the command `./temacs --batch
Tweak previous change.
2007-05-18 07:43:29 +00:00
--load loadup bootstrap' tries to load files.el. A workaround seems
Add info on compiler version to previous change.
2007-05-17 08:02:52 +00:00
to be to reduce the level of compiler optimization used during the
Tweak previous change.
2007-05-18 07:43:29 +00:00
build (from -O2 to -O1). It is possible this is an OpenBSD
GCC problem specific to the macppc architecture, possibly only
occurring with older versions of GCC (e.g. 3.3.5).
(Dumping): Mention OpenBSD macppc problem.
2007-05-17 07:58:16 +00:00
Mention openSUSE bcopy issue.
2007-10-09 02:40:01 +00:00
*** openSUSE 10.3: Segfault in bcopy during dumping.
This is due to a bug in the bcopy implementation in openSUSE 10.3.
It is/will be fixed in an openSUSE update.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Installation
#
1999-10-03 12:39:42 +00:00
David R. Linn <drl at jekyll.vuse.vanderbilt.edu> Add section on Solaris out-of-tree install issues with non-GNU make.
2007-04-28 19:16:10 +00:00
*** On Solaris, use GNU Make when installing an out-of-tree build
The Emacs configuration process allows you to configure the
build environment so that you can build emacs in a directory
outside of the distribution tree. When installing Emacs from an
out-of-tree build directory on Solaris, you may need to use GNU
make. The make programs bundled with Solaris support the VPATH
macro but use it differently from the way the VPATH macro is
used by GNU make. The differences will cause the "make install"
step to fail, leaving you with an incomplete emacs
installation. GNU make is available in /usr/sfw/bin on Solaris
10 and can be installed as /opt/sfw/bin/gmake from the Solaris 9
Software Companion CDROM.
The problems due to the VPATH processing differences affect only
out of tree builds so, if you are on a Solaris installation
without GNU make, you can install Emacs completely by installing
from a build environment using the original emacs distribution tree.
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** First execution
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Emacs binary is not in executable format, and cannot be run.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This was reported to happen when Emacs is built in a directory mounted
via NFS, for some combinations of NFS client and NFS server.
Usually, the file `emacs' produced in these cases is full of
binary null characters, and the `file' utility says:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
emacs: ASCII text, with no line terminators
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
We don't know what exactly causes this failure. A work-around is to
build Emacs in a directory on a local disk.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** The dumped Emacs crashes when run, trying to write pure data.
#
1999-10-03 12:39:42 +00:00
Remove obsolete '#define static' cruft. * etc/PROBLEMS: Remove obsolete '#define static' cruft. * lwlib/xlwmenu.c [emacs]: Include "bitmaps/gray.xbm". (gray_bitmap_width, gray_bitmap_height, gray_bitmap_bits) [!emacs]: Remove; all uses replaced with definiens. * src/s/hpux10-20.h (_FILE_OFFSET_BITS): Don't #undef. This #undef was "temporary" in 2000; it is no longer needed now that '#define static' has gone away. * src/xfns.c, src/xterm.h (gray_bitmap_width, gray_bitmap_height) (gray_bitmap_bits): Remove; no longer needed. All uses replaced with definiens. * src/xterm.c: Include "bitmaps/gray.xbm".
2012-05-31 05:08:37 +00:00
On a system where getpagesize is not a system call, it is defined
Rename src/unexec.c => src/unexcoff.c. src/unexcoff.c: Renamed from unexec.c. src/deps.mk (unexcoff.o): Rename unexec.[co] => unexcoff.[co]. configure.in (UNEXEC_OBJ): Rename unexec.o => unexcoff.o. admin/MAINTAINERS: Rename src/unexec.c => src/unexcoff.c. etc/AUTHORS: Rename unexec.o => unexcoff.o. etc/PROBLEMS: Rename unexec.o => unex*.o. lisp/emacs-lisp/find-gc.el (find-gc-source-files): Rename unexec.c => unexcoff.c. lisp/emacs-lisp/authors.el (authors-fixed-entries): Rename unexec.c => unexcoff.c. msdos/sed1v2.inp (UNEXEC_OBJ): Edit to unexcoff.o, due to renaming of unexec.c => unexcoff.c.
2010-08-05 17:11:32 +00:00
as a macro. If the definition (in both unex*.c and malloc.c) is wrong,
#
1999-10-03 12:39:42 +00:00
it can cause problems like this. You might be able to find the correct
value in the man page for a.out (5).
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
* Runtime problems on legacy systems
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This section covers bugs reported on very old hardware or software.
If you are using hardware and an operating system shipped after 2000,
it is unlikely you will see any of these.
#
1999-10-03 12:39:42 +00:00
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
*** OPENSTEP 4.2: Compiling syntax.c with gcc 2.7.2.1 fails.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The compiler was reported to crash while compiling syntax.c with the
following message:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
cc: Internal compiler error: program cc1obj got fatal signal 11
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
To work around this, replace the macros UPDATE_SYNTAX_TABLE_FORWARD,
INC_BOTH, and INC_FROM with functions. To this end, first define 3
functions, one each for every macro. Here's an example:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
static int update_syntax_table_forward(int from)
{
return(UPDATE_SYNTAX_TABLE_FORWARD(from));
}/*update_syntax_table_forward*/
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Then replace all references to UPDATE_SYNTAX_TABLE_FORWARD in syntax.c
with a call to the function update_syntax_table_forward.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Solaris 2.x
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
**** Strange results from format %d in a few cases, on a Sun.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Sun compiler version SC3.0 has been found to miscompile part of
editfns.c. The workaround is to compile with some other compiler such
as GCC.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
**** On Solaris, Emacs dumps core if lisp-complete-symbol is called.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If you compile Emacs with the -fast or -xO4 option with version 3.0.2
of the Sun C compiler, Emacs dumps core when lisp-complete-symbol is
called. The problem does not happen if you compile with GCC.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
**** On Solaris, Emacs crashes if you use (display-time).
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can happen if you configure Emacs without specifying the precise
version of Solaris that you are using.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
**** Solaris 2.x: GCC complains "64 bit integer types not supported".
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This suggests that GCC is not installed correctly. Most likely you
are using GCC 2.7.2.3 (or earlier) on Solaris 2.6 (or later); this
does not work without patching. To run GCC 2.7.2.3 on Solaris 2.6 or
later, you must patch fixinc.svr4 and reinstall GCC from scratch as
described in the Solaris FAQ
<http://www.wins.uva.nl/pub/solaris/solaris2.html>. A better fix is
to upgrade to GCC 2.8.1 or later.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
**** Solaris 2.7: Building Emacs with WorkShop Compilers 5.0 98/12/15
C 5.0 failed, apparently with non-default CFLAGS, most probably due to
compiler bugs. Using Sun Solaris 2.7 Sun WorkShop 6 update 1 C
release was reported to work without problems. It worked OK on
another system with Solaris 8 using apparently the same 5.0 compiler
and the default CFLAGS.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
**** Solaris 2.x: Emacs dumps core when built with Motif.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
The Solaris Motif libraries are buggy, at least up through Solaris 2.5.1.
Install the current Motif runtime library patch appropriate for your host.
(Make sure the patch is current; some older patch versions still have the bug.)
You should install the other patches recommended by Sun for your host, too.
You can obtain Sun patches from ftp://sunsolve.sun.com/pub/patches/;
look for files with names ending in `.PatchReport' to see which patches
are currently recommended for your host.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
On Solaris 2.6, Emacs is said to work with Motif when Solaris patch
105284-12 is installed, but fail when 105284-15 is installed.
105284-18 might fix it again.
#
1999-10-03 12:39:42 +00:00
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
**** Solaris 2.6 and 7: the Compose key does not work.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is a bug in Motif in Solaris. Supposedly it has been fixed for
the next major release of Solaris. However, if someone with Sun
support complains to Sun about the bug, they may release a patch.
If you do this, mention Sun bug #4188711.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
One workaround is to use a locale that allows non-ASCII characters.
For example, before invoking emacs, set the LC_ALL environment
variable to "en_US" (American English). The directory /usr/lib/locale
lists the supported locales; any locale other than "C" or "POSIX"
should do.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
pen@lysator.liu.se says (Feb 1998) that the Compose key does work
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
if you link with the MIT X11 libraries instead of the Solaris X11 libraries.
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
*** HP/UX: Emacs is slow using X11R5.
This happens if you use the MIT versions of the X libraries--it
doesn't run as fast as HP's version. People sometimes use the version
because they see the HP version doesn't have the libraries libXaw.a,
libXmu.a, libXext.a and others. HP/UX normally doesn't come with
those libraries installed. To get good performance, you need to
install them and rebuild Emacs.
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
*** UnixWare 2.1: Error 12 (virtual memory exceeded) when dumping Emacs.
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
Paul Abrahams (abrahams@acm.org) reports that with the installed
virtual memory settings for UnixWare 2.1.2, an Error 12 occurs during
the "make" that builds Emacs, when running temacs to dump emacs. That
error indicates that the per-process virtual memory limit has been
exceeded. The default limit is probably 32MB. Raising the virtual
memory limit to 40MB should make it possible to finish building Emacs.
You can do this with the command `ulimit' (sh) or `limit' (csh).
But you have to be root to do it.
According to Martin Sohnius, you can also retune this in the kernel:
# /etc/conf/bin/idtune SDATLIM 33554432 ## soft data size limit
# /etc/conf/bin/idtune HDATLIM 33554432 ## hard "
# /etc/conf/bin/idtune SVMMSIZE unlimited ## soft process size limit
# /etc/conf/bin/idtune HVMMSIZE unlimited ## hard "
# /etc/conf/bin/idbuild -B
(He recommends you not change the stack limit, though.)
These changes take effect when you reboot.
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
** MS-Windows 95, 98, ME, and NT
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
*** MS-Windows NT/95: Problems running Perl under Emacs
`perl -de 0' just hangs when executed in an Emacs subshell.
The fault lies with Perl (indirectly with Windows NT/95).
The problem is that the Perl debugger explicitly opens a connection to
"CON", which is the DOS/NT equivalent of "/dev/tty", for interacting
with the user.
On Unix, this is okay, because Emacs (or the shell?) creates a
pseudo-tty so that /dev/tty is really the pipe Emacs is using to
communicate with the subprocess.
On NT, this fails because CON always refers to the handle for the
relevant console (approximately equivalent to a tty), and cannot be
redirected to refer to the pipe Emacs assigned to the subprocess as
stdin.
A workaround is to modify perldb.pl to use STDIN/STDOUT instead of CON.
For Perl 4:
*** PERL/LIB/PERLDB.PL.orig Wed May 26 08:24:18 1993
--- PERL/LIB/PERLDB.PL Mon Jul 01 15:28:16 1996
***************
*** 68,74 ****
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
$rcfile=".perldb";
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
}
else {
! $console = "con";
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
$rcfile="perldb.ini";
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
}
--- 68,74 ----
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
$rcfile=".perldb";
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
}
else {
! $console = "";
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
$rcfile="perldb.ini";
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
}
For Perl 5:
*** perl/5.001/lib/perl5db.pl.orig Sun Jun 04 21:13:40 1995
--- perl/5.001/lib/perl5db.pl Mon Jul 01 17:00:08 1996
***************
*** 22,28 ****
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
$rcfile=".perldb";
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
}
elsif (-e "con") {
! $console = "con";
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
$rcfile="perldb.ini";
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
}
else {
--- 22,28 ----
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
$rcfile=".perldb";
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
}
elsif (-e "con") {
! $console = "";
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
$rcfile="perldb.ini";
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
}
else {
*** MS-Windows 95: Alt-f6 does not get through to Emacs.
This character seems to be trapped by the kernel in Windows 95.
You can enter M-f6 by typing ESC f6.
*** MS-Windows 95/98/ME: subprocesses do not terminate properly.
This is a limitation of the Operating System, and can cause problems
Update location of Emacs on MS Windows FAQ
2013-08-27 19:40:24 +00:00
when shutting down Windows. Ensure that all subprocesses are exited
cleanly before exiting Emacs. For more details, see the Emacs on MS
Windows FAQ (info manual "efaq-w32").
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
*** MS-Windows 95/98/ME: crashes when Emacs invokes non-existent programs.
When a program you are trying to run is not found on the PATH,
Windows might respond by crashing or locking up your system. In
particular, this has been reported when trying to compile a Java
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
program in JDEE when javac.exe is installed, but not on the system PATH.
From Eric S. Raymond: More reorganization to exile old stuff to the pre-2000 section. I looked up end-of-life dates for a bunch of old Unixes to check.
2004-09-04 12:25:43 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** MS-DOS
#
1999-10-03 12:39:42 +00:00
(MS-DOS): Document the problems on Vista.
2008-12-19 11:13:11 +00:00
*** When compiling with DJGPP on MS-Windows NT or later, "config msdos" fails.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
If the error message is "VDM has been already loaded", this is because
Windows has a program called `redir.exe' that is incompatible with a
program by the same name supplied with DJGPP, which is used by
config.bat. To resolve this, move the DJGPP's `bin' subdirectory to
the front of your PATH environment variable.
#
1999-10-03 12:39:42 +00:00
Mention problems with username in the MS-DOS port on MS-Windows.
2009-02-24 19:09:03 +00:00
*** When Emacs compiled with DJGPP runs on Windows 2000 and later, it cannot
find your HOME directory.
This was reported to happen when you click on "Save for future
sessions" button in a Customize buffer. You might see an error
message like this one:
basic-save-buffer-2: c:/FOO/BAR/~dosuser/: no such directory
(The telltale sign is the "~USER" part at the end of the directory
Emacs complains about, where USER is your username or the literal
string "dosuser", which is the default username set up by the DJGPP
startup file DJGPP.ENV.)
This happens when the functions `user-login-name' and
`user-real-login-name' return different strings for your username as
Emacs sees it. To correct this, make sure both USER and USERNAME
environment variables are set to the same value. Windows 2000 and
later sets USERNAME, so if you want to keep that, make sure USER is
set to the same value. If you don't want to set USER globally, you
can do it in the [emacs] section of your DJGPP.ENV file.
(MS-DOS): Document the problems on Vista.
2008-12-19 11:13:11 +00:00
*** When Emacs compiled with DJGPP runs on Vista, it runs out of memory.
If Emacs running on Vista displays "!MEM FULL!" in the mode line, you
are hitting the memory allocation bugs in the Vista DPMI server. See
msdos/INSTALL for how to work around these bugs (search for "Vista").
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** When compiling with DJGPP on MS-Windows 95, Make fails for some targets
like make-docfile.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can happen if long file name support (the setting of environment
variable LFN) when Emacs distribution was unpacked and during
(MS-DOS): Document the problems on Vista.
2008-12-19 11:13:11 +00:00
compilation are not the same. See msdos/INSTALL for the explanation
of how to avoid this problem.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Emacs compiled with DJGPP complains at startup:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
"Wrong type of argument: internal-facep, msdos-menu-active-face"
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can happen if you define an environment variable `TERM'. Emacs
on MSDOS uses an internal terminal emulator which is disabled if the
value of `TERM' is anything but the string "internal". Emacs then
works as if its terminal were a dumb glass teletype that doesn't
support faces. To work around this, arrange for `TERM' to be
undefined when Emacs runs. The best way to do that is to add an
[emacs] section to the DJGPP.ENV file which defines an empty value for
`TERM'; this way, only Emacs gets the empty value, while the rest of
your system works as before.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** MS-DOS: Emacs crashes at startup.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Some users report that Emacs 19.29 requires dpmi memory management,
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
and crashes on startup if the system does not have it. We don't
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
know why this happens--perhaps these machines don't have enough real
memory, or perhaps something is wrong in Emacs or the compiler.
However, arranging to use dpmi support is a workaround.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
You can find out if you have a dpmi host by running go32 without
arguments; it will tell you if it uses dpmi memory. For more
information about dpmi memory, consult the djgpp FAQ. (djgpp
is the GNU C compiler as packaged for MSDOS.)
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Compiling Emacs under MSDOS is extremely sensitive for proper memory
configuration. If you experience problems during compilation, consider
removing some or all memory resident programs (notably disk caches)
and make sure that your memory managers are properly configured. See
the djgpp faq for configuration hints.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Emacs compiled with DJGPP for MS-DOS/MS-Windows cannot access files
in the directory with the special name `dev' under the root of any
drive, e.g. `c:/dev'.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This is an unfortunate side-effect of the support for Unix-style
device names such as /dev/null in the DJGPP runtime library. A
work-around is to rename the problem directory to another name.
#
1999-10-03 12:39:42 +00:00
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
*** MS-DOS+DJGPP: Problems on MS-DOS if DJGPP v2.0 is used to compile Emacs.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
There are two DJGPP library bugs which cause problems:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
* Running `shell-command' (or `compile', or `grep') you get
`Searching for program: permission denied (EACCES), c:/command.com';
* After you shell to DOS, Ctrl-Break kills Emacs.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
To work around these bugs, you can use two files in the msdos
subdirectory: `is_exec.c' and `sigaction.c'. Compile them and link
them into the Emacs executable `temacs'; then they will replace the
incorrect library functions.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** MS-DOS: Emacs compiled for MSDOS cannot find some Lisp files, or other
run-time support files, when long filename support is enabled.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Usually, this problem will manifest itself when Emacs exits
immediately after flashing the startup screen, because it cannot find
the Lisp files it needs to load at startup. Redirect Emacs stdout
and stderr to a file to see the error message printed by Emacs.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Another manifestation of this problem is that Emacs is unable to load
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
the support for editing program sources in languages such as C and Lisp.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This can happen if the Emacs distribution was unzipped without LFN
support, thus causing long filenames to be truncated to the first 6
characters and a numeric tail that Windows 95 normally attaches to it.
You should unzip the files again with a utility that supports long
filenames (such as djtar from DJGPP or InfoZip's UnZip program
(MS-DOS): Document the problems on Vista.
2008-12-19 11:13:11 +00:00
compiled with DJGPP v2). The file msdos/INSTALL explains this issue
in more detail.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Another possible reason for such failures is that Emacs compiled for
MSDOS is used on Windows NT, where long file names are not supported
by this version of Emacs, but the distribution was unpacked by an
unzip program that preserved the long file names instead of truncating
them to DOS 8+3 limits. To be useful on NT, the MSDOS port of Emacs
must be unzipped by a DOS utility, so that long file names are
properly truncated.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Archaic window managers and toolkits
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** OpenLook: Under OpenLook, the Emacs window disappears when you type M-q.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
Some versions of the Open Look window manager interpret M-q as a quit
command for whatever window you are typing at. If you want to use
Emacs with that window manager, you should try to configure the window
manager to use some other command. You can disable the
shortcut keys entirely by adding this line to ~/.OWdefaults:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
OpenWindows.WindowMenuAccelerators: False
#
1999-10-03 12:39:42 +00:00
* etc/PROBLEMS: Remove some more obsolete information. Also some re-filling.
2010-05-28 03:23:08 +00:00
*** twm: A position you specified in .Xdefaults is ignored, using twm.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
twm normally ignores "program-specified" positions.
You can tell it to obey them with this command in your `.twmrc' file:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
UsePPosition "on" #allow clients to request a position
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
** Bugs related to old DEC hardware
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** The Compose key on a DEC keyboard does not work as Meta key.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This shell command should fix it:
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
xmodmap -e 'keycode 0xb1 = Meta_L'
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
*** Keyboard input gets confused after a beep when using a DECserver
as a concentrator.
#
1999-10-03 12:39:42 +00:00
Massively rearranged by category, to make environment features and symptoms easier to find. Bugs relating to 20th-century systems moved to the end. Most problem headers changed to "object: variation" format.
2004-08-21 11:31:45 +00:00
This problem seems to be a matter of configuring the DECserver to use
7 bit characters rather than 8 bit characters.
Use outline-mode.
2001-12-06 09:26:21 +00:00
Switch to standard GPL text for license.
2007-02-11 01:18:25 +00:00
This file is part of GNU Emacs.
Add copyright notice and permission notice.
2002-11-06 05:11:59 +00:00
Switch to recommended form of GPLv3 permissions notice.
2008-05-15 07:32:14 +00:00
GNU Emacs is free software: you can redistribute it and/or modify
Switch to standard GPL text for license.
2007-02-11 01:18:25 +00:00
it under the terms of the GNU General Public License as published by
Switch to recommended form of GPLv3 permissions notice.
2008-05-15 07:32:14 +00:00
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
Add copyright notice and permission notice.
2002-11-06 05:11:59 +00:00
Switch to standard GPL text for license.
2007-02-11 01:18:25 +00:00
GNU Emacs is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
Switch to recommended form of GPLv3 permissions notice.
2008-05-15 07:32:14 +00:00
along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
Switch to standard GPL text for license.
2007-02-11 01:18:25 +00:00
Use outline-mode.
2001-12-06 09:26:21 +00:00
Local variables:
mode: outline
Prevent pasting a region twice on an xterm or rxvt in X.
2008-08-26 20:02:17 +00:00
paragraph-separate: "[ ]*$"
Use outline-mode.
2001-12-06 09:26:21 +00:00
end:
Reference in New Issue Copy Permalink