2008-02-29 23:44:30 +00:00
|
|
|
|
Known Problems with GNU Emacs
|
|
|
|
|
|
2022-01-01 07:45:51 +00:00
|
|
|
|
Copyright (C) 1987-1989, 1993-1999, 2001-2022 Free Software Foundation,
|
2016-01-01 09:16:19 +00:00
|
|
|
|
Inc.
|
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
|
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
|
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
|
|
|
|
|
2014-01-07 02:06:00 +00:00
|
|
|
|
* Mule-UCS doesn't work in Emacs 23 onwards
|
2003-09-11 13:54:47 +00:00
|
|
|
|
|
|
|
|
|
It's completely redundant now, as far as we know.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
* Emacs startup failures
|
2004-05-30 00:35:44 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Emacs fails to start, complaining about missing fonts.
|
2004-05-30 00:35:44 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
A typical error message might be something like
|
2004-05-30 00:35:44 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
No fonts match ‘-*-fixed-medium-r-*--6-*-*-*-*-*-iso8859-1’
|
2004-04-16 12:51:06 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
This happens because some X resource specifies a bad font family for
|
2014-01-23 02:11:13 +00:00
|
|
|
|
Emacs to use. The possible places where this specification might be are:
|
2004-04-16 12:51:06 +00:00
|
|
|
|
|
2015-04-07 17:42:28 +00:00
|
|
|
|
- in the X server resources database, often initialized from
|
|
|
|
|
~/.Xresources (use $ xrdb -query to find out the current state)
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
- in your ~/.Xdefaults file
|
2004-04-16 12:51:06 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
- client-side X resource file, such as ~/Emacs or
|
2014-03-22 22:56:29 +00:00
|
|
|
|
/usr/share/X11/app-defaults/Emacs
|
2004-04-16 12:51:06 +00:00
|
|
|
|
|
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.
|
2004-04-16 12:51:06 +00:00
|
|
|
|
|
2015-04-07 17:42:28 +00:00
|
|
|
|
After correcting ~/.Xresources, the new data has to be merged into the
|
|
|
|
|
X server resources database. Depending on the circumstances, the
|
|
|
|
|
following command may do the trick. See xrdb(1) for more information.
|
|
|
|
|
|
|
|
|
|
$ xrdb -merge ~/.Xresources
|
|
|
|
|
|
2019-08-02 09:24:53 +00:00
|
|
|
|
** Emacs compiled with Cairo crashes when restoring session from desktop file.
|
|
|
|
|
|
|
|
|
|
This can happen if the '.emacs.desktop' file contains setting for
|
|
|
|
|
'font-backend' frame parameter. A workaround is to delete the
|
|
|
|
|
offending '.emacs.desktop' file, or edit it to remove the setting of
|
|
|
|
|
'font-backend'.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Emacs aborts while starting up, only when run without X.
|
2004-04-16 12:51:06 +00:00
|
|
|
|
|
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.
|
2004-04-16 12:51:06 +00:00
|
|
|
|
|
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.
|
2004-04-16 12:51:06 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Emacs does not start, complaining that it cannot open termcap database file.
|
2004-04-16 12:51:06 +00:00
|
|
|
|
|
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
|
2014-01-23 02:11:13 +00:00
|
|
|
|
libraries). It can happen because your version of ncurses is
|
2004-08-21 11:31:45 +00:00
|
|
|
|
obsolete, or is available only in form of binaries.
|
2004-04-16 12:51:06 +00:00
|
|
|
|
|
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.
|
2004-04-16 12:51:06 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Emacs 20 and later fails to load Lisp files at startup.
|
2003-07-22 17:51:57 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
The typical error message might be like this:
|
2003-07-22 17:51:57 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
"Cannot open load file: fontset"
|
2002-11-14 06:30:15 +00:00
|
|
|
|
|
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,
|
2015-08-26 21:05:43 +00:00
|
|
|
|
when your .emacs file is processed. (The package 'fontset.el' is
|
2004-08-21 11:31:45 +00:00
|
|
|
|
required to set up fonts used to display text on window systems, and
|
|
|
|
|
it's loaded very early in the startup procedure.)
|
2002-11-25 16:24:23 +00:00
|
|
|
|
|
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.
|
2002-07-24 23:01:32 +00:00
|
|
|
|
|
2010-05-28 03:23:08 +00:00
|
|
|
|
The solution is to uncompress all .el files that don't have a .elc file.
|
2004-04-16 12:51:06 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Another possible reason for such failures is stale *.elc files
|
2010-05-27 06:13:23 +00:00
|
|
|
|
lurking somewhere on your load-path -- see the next section.
|
2002-10-24 22:13:59 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Emacs prints an error at startup after upgrading from an earlier version.
|
2002-10-24 22:13:59 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
An example of such an error is:
|
2002-10-24 22:13:59 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
x-complement-fontset-spec: "Wrong type argument: stringp, nil"
|
2003-05-29 18:15:21 +00:00
|
|
|
|
|
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:
|
2003-05-29 18:15:21 +00:00
|
|
|
|
|
2011-01-08 02:49:27 +00:00
|
|
|
|
emacs -batch -f list-load-path-shadows
|
2003-05-29 18:15:21 +00:00
|
|
|
|
|
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.
|
2003-04-29 13:35:52 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
* Crash bugs
|
2002-08-02 18:03:01 +00:00
|
|
|
|
|
2010-10-25 16:04:54 +00:00
|
|
|
|
** When Emacs is compiled with Gtk+, closing a display kills Emacs.
|
2006-09-10 12:29:10 +00:00
|
|
|
|
|
2010-10-25 16:04:54 +00:00
|
|
|
|
There is a long-standing bug in GTK that prevents it from recovering
|
2018-05-26 23:42:52 +00:00
|
|
|
|
from disconnects: https://gitlab.gnome.org/GNOME/gtk/issues/221
|
2006-09-10 12:29:10 +00:00
|
|
|
|
|
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.
|
2008-12-18 19:18:12 +00:00
|
|
|
|
|
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.
|
2008-12-18 19:18:12 +00:00
|
|
|
|
|
2018-08-28 20:05:04 +00:00
|
|
|
|
** Emacs compiled with GTK+ 3 crashes when run under some X servers.
|
|
|
|
|
This happens when the X server does not provide certain display
|
|
|
|
|
features that the underlying GTK+ 3 toolkit assumes. For example, this
|
|
|
|
|
issue has been seen with remote X servers like X2Go. The symptoms
|
|
|
|
|
are an Emacs crash, possibly triggered by the mouse entering the Emacs
|
|
|
|
|
window, or an attempt to resize the Emacs window. The crash backtrace
|
|
|
|
|
contains a call to XQueryPointer.
|
|
|
|
|
|
|
|
|
|
This issue was fixed in the GTK+ 3 toolkit in commit 4b1c0256 in February 2018.
|
|
|
|
|
|
|
|
|
|
If your GTK+ 3 is still affected, you can avoid the issue by recompiling
|
|
|
|
|
Emacs with a different X toolkit, eg --with-toolkit=gtk2.
|
|
|
|
|
|
|
|
|
|
References:
|
|
|
|
|
https://gitlab.gnome.org/GNOME/gtk/commit/4b1c02560f0d8097bf5a11932e52fb72f3e9e94b
|
|
|
|
|
https://debbugs.gnu.org/24280
|
|
|
|
|
https://bugs.debian.org/901038
|
|
|
|
|
https://bugzilla.redhat.com/1483942
|
|
|
|
|
https://access.redhat.com/solutions/3410101
|
|
|
|
|
|
2017-05-09 16:48:18 +00:00
|
|
|
|
** Emacs compiled with GTK crashes at startup due to X protocol error.
|
|
|
|
|
|
|
|
|
|
This is known to happen on elementary OS GNU/Linux systems.
|
|
|
|
|
|
|
|
|
|
The error message is:
|
|
|
|
|
|
|
|
|
|
X protocol error: BadMatch (invalid parameter attributes) on protocol request 140
|
|
|
|
|
When compiled with GTK, Emacs cannot recover from X disconnects.
|
2018-05-26 23:42:52 +00:00
|
|
|
|
This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221
|
2017-05-09 16:48:18 +00:00
|
|
|
|
For details, see etc/PROBLEMS.
|
|
|
|
|
Fatal error 6: Aborted
|
|
|
|
|
|
|
|
|
|
followed by a C backtrace. (Sometimes the offending protocol request
|
|
|
|
|
number is 139.)
|
|
|
|
|
|
|
|
|
|
The relevant bug report is here:
|
|
|
|
|
|
|
|
|
|
https://bugs.launchpad.net/elementaryos/+bug/1355274
|
|
|
|
|
|
|
|
|
|
A workaround is to set XLIB_SKIP_ARGB_VISUALS=1 in the environment
|
|
|
|
|
before starting Emacs, or run Emacs as root.
|
|
|
|
|
|
2021-11-06 08:49:54 +00:00
|
|
|
|
** Emacs crashes with SIGTRAP when trying to start a WebKit xwidget.
|
|
|
|
|
|
|
|
|
|
This could happen if the version of WebKitGTK installed on your system
|
|
|
|
|
is buggy, and errors out trying to start a subprocess through
|
|
|
|
|
Bubblewrap sandboxing. You can avoid the crash by setting the
|
|
|
|
|
environment variables SNAP, SNAP_NAME and SNAP_REVISION, which will
|
2021-11-07 07:34:30 +00:00
|
|
|
|
make WebKit use GLib to launch subprocesses instead. For example,
|
2021-11-07 17:32:28 +00:00
|
|
|
|
invoke Emacs like this (where "..." stands for the other command-line
|
|
|
|
|
arguments you intend to pass to Emacs):
|
2021-11-07 07:34:30 +00:00
|
|
|
|
|
|
|
|
|
$ SNAP=1 SNAP_NAME=1 SNAP_REVISION=1 emacs ...
|
2021-11-06 08:49:54 +00:00
|
|
|
|
|
2012-06-28 07:47:19 +00:00
|
|
|
|
** Emacs crashes when you try to view a file with complex characters.
|
2014-03-22 22:56:29 +00:00
|
|
|
|
|
2018-01-27 09:18:59 +00:00
|
|
|
|
One possible reason for this could be a bug in the libotf or the
|
|
|
|
|
libm17n-flt/m17n-db libraries Emacs uses for displaying complex
|
2021-11-06 08:45:58 +00:00
|
|
|
|
scripts.
|
|
|
|
|
|
|
|
|
|
The easiest and the recommended way of solving these crashes is to
|
|
|
|
|
build Emacs with HarfBuzz as the shaping engine library instead of
|
|
|
|
|
libm17n-flt. Building with HarfBuzz is the default since Emacs 27.1.
|
|
|
|
|
|
|
|
|
|
If you must use libm17n-flt, read on.
|
|
|
|
|
|
|
|
|
|
Make sure you have the latest versions of these libraries
|
2018-01-27 09:18:59 +00:00
|
|
|
|
installed. If the problem still persists with the latest released
|
|
|
|
|
versions of these libraries, you can try building these libraries from
|
|
|
|
|
their CVS repository:
|
|
|
|
|
|
|
|
|
|
cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/m17n co libotf
|
|
|
|
|
cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/m17n co m17n-db
|
|
|
|
|
cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/m17n co m17n-lib
|
|
|
|
|
|
|
|
|
|
One known problem that causes such crashes is with using Noto Serif
|
|
|
|
|
Kannada fonts. To work around that, force Emacs not to select these
|
|
|
|
|
fonts, by adding the following to your ~/.emacs init file:
|
|
|
|
|
|
|
|
|
|
(push "Noto Serif Kannada" face-ignored-fonts)
|
|
|
|
|
|
|
|
|
|
You can try this interactively in a running Emacs session like this:
|
|
|
|
|
|
|
|
|
|
M-: (push "Noto Serif Kannada" face-ignored-fonts) RET
|
|
|
|
|
|
|
|
|
|
Another set of problems is caused by an incompatible libotf library.
|
|
|
|
|
In this case, displaying the etc/HELLO file (as shown by C-h h)
|
|
|
|
|
triggers the following message to be shown in the terminal from which
|
|
|
|
|
you launched Emacs:
|
|
|
|
|
|
|
|
|
|
symbol lookup error: /usr/bin/emacs: undefined symbol: OTF_open
|
2012-06-28 07:47:19 +00:00
|
|
|
|
|
|
|
|
|
This problem occurs because unfortunately there are two libraries
|
|
|
|
|
called "libotf". One is the library for handling OpenType fonts,
|
2019-09-23 06:53:39 +00:00
|
|
|
|
https://www.nongnu.org/m17n/, which is the one that Emacs expects.
|
2012-06-28 07:47:19 +00:00
|
|
|
|
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.
|
2014-01-07 02:06:00 +00:00
|
|
|
|
Ref: <URL:https://bugzilla.redhat.com/show_bug.cgi?id=844776>
|
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.
|
|
|
|
|
|
2021-11-06 08:45:58 +00:00
|
|
|
|
** Emacs crashes in x-popup-dialog.
|
|
|
|
|
|
|
|
|
|
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).
|
|
|
|
|
|
|
|
|
|
** Emacs crashes when you use Bibtex mode.
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
Patches to raise the stack size limit automatically in 'main'
|
|
|
|
|
(src/emacs.c) on various systems would be greatly appreciated.
|
|
|
|
|
|
|
|
|
|
** Error message 'Symbol’s value as variable is void: x', followed by
|
|
|
|
|
a segmentation fault and core dump.
|
|
|
|
|
|
|
|
|
|
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:
|
|
|
|
|
|
|
|
|
|
x FILENAME, N bytes, B tape blocks
|
|
|
|
|
|
|
|
|
|
If your tar has this problem, install GNU tar--if you can manage to
|
|
|
|
|
untar it :-).
|
|
|
|
|
|
|
|
|
|
** Emacs crashes when running in a terminal, if compiled with GCC 4.5.0
|
|
|
|
|
|
|
|
|
|
This version of GCC is buggy: see
|
|
|
|
|
|
|
|
|
|
https://debbugs.gnu.org/6031
|
|
|
|
|
https://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
|
|
|
|
|
|
|
|
|
|
./configure CFLAGS="-g -O2 -fno-optimize-sibling-calls"
|
|
|
|
|
|
|
|
|
|
** 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).
|
|
|
|
|
|
|
|
|
|
** Emacs can crash when displaying PNG images with transparency.
|
|
|
|
|
|
|
|
|
|
This is due to a bug introduced in ImageMagick 6.8.2-3. The bug should
|
|
|
|
|
be fixed in ImageMagick 6.8.3-10. See <URL:https://debbugs.gnu.org/13867>.
|
|
|
|
|
|
|
|
|
|
** 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.
|
|
|
|
|
|
|
|
|
|
** Emacs aborts inside the function 'tparam1'.
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
** Emacs crashes when using some version of the Exceed X server.
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
** Emacs crashes with SIGSEGV in XtInitializeWidgetClass.
|
|
|
|
|
|
|
|
|
|
It crashes on X, but runs fine when called with option "-nw".
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2020-01-28 07:04:20 +00:00
|
|
|
|
* Problems when reading or debugging Emacs C code
|
|
|
|
|
|
|
|
|
|
Because Emacs does not install a copy of its C source code, users
|
|
|
|
|
normally cannot easily read that code via commands like 'M-x
|
|
|
|
|
describe-function' (C-h f) that display the definition of a function.
|
|
|
|
|
However, some GNU/Linux systems provide separate packages containing
|
|
|
|
|
this source code which can get C-h f to work if you are willing to do
|
|
|
|
|
some tinkering, and some systems also provide packages containing
|
|
|
|
|
debug info, which when combined with the source can be used to debug
|
|
|
|
|
Emacs at the C level.
|
|
|
|
|
|
|
|
|
|
** Debian-based source and debuginfo
|
|
|
|
|
|
|
|
|
|
On recent Debian-based systems, you can obtain and use a source
|
|
|
|
|
package of Emacs as follows.
|
|
|
|
|
|
|
|
|
|
*** Add the appropriate URI to /etc/apt/sources.list.
|
|
|
|
|
|
|
|
|
|
To do this, become superuser and uncomment or add the appropriate
|
|
|
|
|
'deb-src' line. Details depend on the distribution.
|
|
|
|
|
|
|
|
|
|
*** Execute a command like 'apt-get source emacs'.
|
|
|
|
|
|
|
|
|
|
On older systems, append the top-level version number, e.g., 'apt-get
|
|
|
|
|
source emacs25'. The target directory for unpacking the source tree
|
|
|
|
|
is the current directory.
|
|
|
|
|
|
|
|
|
|
*** Set find-function-C-source-directory accordingly.
|
|
|
|
|
|
|
|
|
|
Once you have installed the source package, for example at
|
2020-11-16 17:05:31 +00:00
|
|
|
|
/home/myself/deb-src/emacs-27.1, add the following line to your
|
2020-01-28 07:04:20 +00:00
|
|
|
|
startup file:
|
|
|
|
|
|
|
|
|
|
(setq find-function-C-source-directory
|
2020-11-16 17:05:31 +00:00
|
|
|
|
"/home/myself/deb-src/emacs-27.1/src/")
|
2020-01-28 07:04:20 +00:00
|
|
|
|
|
|
|
|
|
The installation directory of the Emacs source package will contain
|
|
|
|
|
the exact package name and version number of Emacs that is installed
|
|
|
|
|
on your system. If a new Emacs package is installed, the source
|
|
|
|
|
package must be reinstalled as well, and the setting in your startup
|
|
|
|
|
file must be updated.
|
|
|
|
|
|
|
|
|
|
*** Debian-based debuginfo
|
|
|
|
|
|
|
|
|
|
You can also install a debug package of Emacs with a command like
|
|
|
|
|
'apt-get install emacs-dbg' (on older systems, 'apt-get install
|
|
|
|
|
emacs25-dbg'). You need to arrange for GDB to find where you
|
|
|
|
|
installed the source code, e.g., by using GDB's 'directory' command.
|
|
|
|
|
|
|
|
|
|
** Red Hat-based source and debuginfo
|
|
|
|
|
|
|
|
|
|
On recent Red Hat-based systems, you can install source and debug info
|
|
|
|
|
via superuser commands like the following:
|
|
|
|
|
|
|
|
|
|
# Add the *-debuginfo repositories (exact command depends on system).
|
|
|
|
|
dnf config-manager --set-enabled fedora-debuginfo updates-debuginfo'
|
|
|
|
|
|
|
|
|
|
# Install Emacs source and debug info.
|
|
|
|
|
dnf install emacs-debugsource
|
|
|
|
|
|
|
|
|
|
To get describe-function and similar commands to work, you can then
|
|
|
|
|
add something like the following to your startup file:
|
|
|
|
|
|
|
|
|
|
(setq find-function-C-source-directory
|
2020-11-16 17:05:31 +00:00
|
|
|
|
"/usr/src/debug/emacs-27.1-1.fc31.x86_64/src/")
|
2020-01-28 07:04:20 +00:00
|
|
|
|
|
|
|
|
|
However, the exact directory name will depend on the system, and you
|
|
|
|
|
will need to both upgrade source and debug info when your system
|
|
|
|
|
upgrades or patches Emacs, and change your startup file accordingly.
|
|
|
|
|
|
|
|
|
|
** Source and debuginfo for other systems
|
|
|
|
|
|
|
|
|
|
If your system follows neither the Debian nor the Red Hat patterns,
|
|
|
|
|
you can obtain the source and debuginfo by obtaining the source code
|
|
|
|
|
of Emacs, building Emacs with the appropriate debug flags enabled, and
|
|
|
|
|
running the just-built Emacs.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
* General runtime problems
|
2001-01-24 08:09:48 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Lisp problems
|
2001-10-17 17:47:54 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** Changes made to .el files do not take effect.
|
2001-10-17 17:47:54 +00:00
|
|
|
|
|
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.
|
2001-10-17 17:47:54 +00:00
|
|
|
|
|
2014-01-07 02:06:00 +00:00
|
|
|
|
Emacs prints a warning when loading a .elc file which is older
|
2004-08-21 11:31:45 +00:00
|
|
|
|
than the corresponding .el file.
|
2001-10-17 17:47:54 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
Alternatively, if you set the option 'load-prefer-newer' non-nil,
|
2014-01-07 02:06:00 +00:00
|
|
|
|
Emacs will load whichever version of a file is the newest.
|
|
|
|
|
|
|
|
|
|
*** Watch out for the EMACSLOADPATH environment variable
|
2001-10-17 17:47:54 +00:00
|
|
|
|
|
2010-05-28 03:23:08 +00:00
|
|
|
|
EMACSLOADPATH overrides which directories the function "load" will search.
|
2001-10-17 17:47:54 +00:00
|
|
|
|
|
2014-01-07 02:06:00 +00:00
|
|
|
|
If you observe strange problems, check for this variable in your
|
|
|
|
|
environment.
|
2001-03-14 19:52:43 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Keyboard problems
|
2001-01-30 13:47:51 +00:00
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
typing 'ESC |' instead.
|
2012-03-12 09:55:35 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** "Compose Character" key does strange things when used as a Meta key.
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
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.
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
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.
|
2002-10-07 22:46:09 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** C-z just refreshes the screen instead of suspending Emacs.
|
2002-10-07 22:46:09 +00:00
|
|
|
|
|
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,
|
2015-08-26 21:05:43 +00:00
|
|
|
|
or set the variable 'cannot-suspend' to a non-nil value.
|
2002-10-07 22:46:09 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Mailers and other helper programs
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** movemail compiled with POP support can't connect to the POP server.
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
2017-03-17 08:57:30 +00:00
|
|
|
|
This problem can occur if you do not configure --with-mailutils,
|
|
|
|
|
and don't have GNU Mailutils installed. Then Emacs uses its own
|
|
|
|
|
version of movemail, which doesn't support secure POP connections.
|
|
|
|
|
To solve this, install GNU Mailutils.
|
|
|
|
|
|
|
|
|
|
Also, 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.
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** RMAIL gets error getting new mail.
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
RMAIL gets new mail from /usr/spool/mail/$USER using a program
|
2015-08-26 21:05:43 +00:00
|
|
|
|
called 'movemail'. This program interlocks with /bin/mail using
|
2004-08-21 11:31:45 +00:00
|
|
|
|
the protocol defined by /bin/mail.
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
There are two different protocols in general use. One of them uses
|
2015-08-26 21:05:43 +00:00
|
|
|
|
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
|
2004-08-21 11:31:45 +00:00
|
|
|
|
this. You control which one is used by defining, or not defining,
|
2012-07-31 06:58:54 +00:00
|
|
|
|
the macro MAIL_USE_FLOCK in config.h.
|
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!
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
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,
|
2015-08-26 21:05:43 +00:00
|
|
|
|
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
|
2004-08-21 11:31:45 +00:00
|
|
|
|
make install.
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
2008-08-26 20:02:17 +00:00
|
|
|
|
chgrp mail movemail
|
|
|
|
|
chmod 2755 movemail
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
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.
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** rcs2log gives you the awk error message "too many fields".
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
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).
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Problems with hostname resolution
|
2001-09-10 15:26:33 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** Emacs does not know your host's fully-qualified domain name.
|
2002-01-04 10:15:04 +00:00
|
|
|
|
|
2007-04-19 17:07:15 +00:00
|
|
|
|
For example, (system-name) returns some variation on
|
|
|
|
|
"localhost.localdomain", rather the name you were expecting.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
You need to configure your machine with a fully qualified domain name,
|
2014-12-30 04:42:26 +00:00
|
|
|
|
(i.e., a name with at least one "."), either in /etc/hostname
|
|
|
|
|
or wherever your system calls for specifying this.
|
2002-01-22 11:03:19 +00:00
|
|
|
|
|
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.
|
2002-01-22 11:03:19 +00:00
|
|
|
|
|
2014-01-07 02:11:14 +00:00
|
|
|
|
** NFS
|
2002-01-22 11:03:19 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** Emacs says it has saved a file, but the file does not actually
|
|
|
|
|
appear on disk.
|
2002-01-22 11:03:19 +00:00
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
calls involved in writing a file, including 'close'; but in the case
|
2004-08-21 11:31:45 +00:00
|
|
|
|
where the problem occurs, none of those system calls fails.
|
2002-01-22 11:03:19 +00:00
|
|
|
|
|
2010-05-27 06:13:23 +00:00
|
|
|
|
** PSGML conflicts with sgml-mode.
|
2001-11-17 17:25:41 +00:00
|
|
|
|
|
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.
|
2001-11-17 17:25:41 +00:00
|
|
|
|
|
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.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Miscellaneous problems
|
2001-07-27 11:13:18 +00:00
|
|
|
|
|
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.
|
|
|
|
|
|
2018-01-27 15:26:29 +00:00
|
|
|
|
*** Display artifacts on GUI frames on X-based systems.
|
|
|
|
|
|
|
|
|
|
This is known to be caused by using double-buffering (which is enabled
|
|
|
|
|
by default in Emacs 26 and later). The artifacts typically appear
|
|
|
|
|
after commands that cause Emacs to scroll the display.
|
|
|
|
|
|
|
|
|
|
You can disable double-buffering by evaluating the following form:
|
|
|
|
|
|
|
|
|
|
(modify-all-frames-parameters '((inhibit-double-buffering . t)))
|
|
|
|
|
|
|
|
|
|
To make this permanent, add it to your ~/.emacs init file.
|
|
|
|
|
|
|
|
|
|
Note that disabling double-buffering will cause flickering of the
|
|
|
|
|
display in some situations.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** Self-documentation messages are garbled.
|
2002-04-28 18:56:22 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
This means that the file 'etc/DOC' doesn't properly correspond
|
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.
|
2001-01-30 13:47:51 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
*** Programs running under terminal emulator do not recognize 'emacs'
|
2004-08-21 11:31:45 +00:00
|
|
|
|
terminal type.
|
2001-01-30 13:47:51 +00:00
|
|
|
|
|
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
|
2010-05-28 03:23:08 +00:00
|
|
|
|
provide the information on the special terminal type that Emacs emulates.
|
2001-01-30 13:47:51 +00:00
|
|
|
|
|
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.
|
2001-01-30 13:47:51 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file
|
2001-04-27 16:51:05 +00:00
|
|
|
|
|
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.
|
2002-03-12 20:27:24 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** In Shell mode, you get a ^M at the end of every line.
|
2001-02-09 10:42:05 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
This happens to people who use tcsh, because it is trying to be too
|
2015-08-26 21:05:43 +00:00
|
|
|
|
smart. It sees that the Shell uses terminal type 'unknown' and turns
|
2004-08-21 11:31:45 +00:00
|
|
|
|
on the flag to output ^M at the end of each line. You can fix the
|
|
|
|
|
problem by adding this to your .cshrc file:
|
2002-07-24 03:59:52 +00:00
|
|
|
|
|
2016-04-07 23:52:01 +00:00
|
|
|
|
if ($?INSIDE_EMACS && $?tcsh)
|
|
|
|
|
unset edit
|
|
|
|
|
stty -icrnl -onlcr -echo susp ^Z
|
2004-08-21 11:31:45 +00:00
|
|
|
|
endif
|
2001-02-09 10:42:05 +00:00
|
|
|
|
|
2017-05-09 16:34:39 +00:00
|
|
|
|
*** In Shell buffers using ksh, resizing a window inserts random characters.
|
|
|
|
|
|
|
|
|
|
The characters come from the PS2 prompt, but they are not followed by
|
|
|
|
|
a newline, which messes up the next command you type. This strange
|
|
|
|
|
effect is caused by Emacs 25 and later telling the shell that its
|
|
|
|
|
screen size changed.
|
|
|
|
|
|
|
|
|
|
To work around the problem, customize the option
|
|
|
|
|
'window-adjust-process-window-size-function' to "Do not adjust process
|
|
|
|
|
window sizes" (Lisp value 'ignore').
|
|
|
|
|
|
2017-03-01 22:53:12 +00:00
|
|
|
|
*** In Inferior Python mode, input is echoed and native completion doesn't work.
|
|
|
|
|
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25753>
|
|
|
|
|
|
|
|
|
|
This happens when python uses a libedit based readline module, which
|
|
|
|
|
is the default on macOS. This can be worked around by installing a
|
|
|
|
|
GNU readline based module instead, for example, using setuptools
|
|
|
|
|
|
|
|
|
|
sudo easy_install gnureadline
|
|
|
|
|
|
|
|
|
|
And then rename the system's readline so that it won't be loaded:
|
|
|
|
|
|
|
|
|
|
cd /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload
|
|
|
|
|
mv readline.so readline.so.bak
|
|
|
|
|
|
|
|
|
|
See <https://pypi.python.org/pypi/gnureadline> for more details on
|
|
|
|
|
installation.
|
|
|
|
|
|
2015-03-23 00:10:10 +00:00
|
|
|
|
*** Visiting files in some auto-mounted directories causes Emacs to print
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'Error reading dir-locals: (file-error "Read error" "is a directory" ...'
|
2015-03-23 00:10:10 +00:00
|
|
|
|
|
|
|
|
|
This can happen if the auto-mounter mistakenly reports that
|
|
|
|
|
.dir-locals.el exists and is a directory. There is nothing Emacs can
|
|
|
|
|
do about this, but you can avoid the issue by adding a suitable entry
|
2015-08-26 21:05:43 +00:00
|
|
|
|
to the variable 'locate-dominating-stop-dir-regexp'. For example, if
|
2015-03-23 00:10:10 +00:00
|
|
|
|
the problem relates to "/smb/.dir-locals.el", set that variable
|
|
|
|
|
to a new value where you replace "net\\|afs" with "net\\|afs\\|smb".
|
|
|
|
|
(The default value already matches common auto-mount prefixes.)
|
2017-11-26 06:45:41 +00:00
|
|
|
|
See https://lists.gnu.org/r/help-gnu-emacs/2015-02/msg00461.html .
|
2015-03-23 00:10:10 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** Attempting to visit remote files via ange-ftp fails.
|
2001-12-08 10:37:33 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
If the error message is "ange-ftp-file-modtime: Specified time is not
|
2015-08-26 21:05:43 +00:00
|
|
|
|
representable", then this could happen when 'lukemftp' is used as the
|
2004-08-21 11:31:45 +00:00
|
|
|
|
ftp client. This was reported to happen on Debian GNU/Linux, kernel
|
2015-08-26 21:05:43 +00:00
|
|
|
|
version 2.4.3, with 'lukemftp' 1.5-5, but might happen on other
|
2004-08-21 11:31:45 +00:00
|
|
|
|
systems as well. To avoid this problem, switch to using the standard
|
|
|
|
|
ftp client. On a Debian system, type
|
2001-12-08 10:37:33 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
update-alternatives --config ftp
|
2001-12-08 10:37:33 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
and then choose /usr/bin/netkit-ftp.
|
2001-12-08 10:37:33 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** Dired is very slow.
|
2002-03-15 15:23:15 +00:00
|
|
|
|
|
2017-10-02 05:31:39 +00:00
|
|
|
|
This could happen if getting a file system's status takes a long
|
2002-03-15 15:23:15 +00:00
|
|
|
|
time. Possible reasons for this include:
|
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
- ClearCase mounted filesystems (VOBs) that sometimes make 'df'
|
2002-03-15 15:23:15 +00:00
|
|
|
|
response time extremely slow (dozens of seconds);
|
|
|
|
|
|
|
|
|
|
- slow automounters on some old versions of Unix;
|
|
|
|
|
|
2017-10-02 05:31:39 +00:00
|
|
|
|
To work around the problem, you could use Git or some other
|
|
|
|
|
free-software program, instead of ClearCase.
|
2002-03-15 15:23:15 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** ps-print commands fail to find prologue files ps-prin*.ps.
|
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.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** On systems with shared libraries you might encounter run-time errors
|
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.
|
|
|
|
|
|
2001-10-30 11:58:45 +00:00
|
|
|
|
Similar problems could prevent Emacs from building, since the build
|
|
|
|
|
process invokes Emacs several times.
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
Please refer to the documentation of your dynamic linker for details.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** When you run Ispell from Emacs, it reports a "misalignment" error.
|
2001-06-15 11:37:56 +00:00
|
|
|
|
|
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.
|
2001-06-15 11:37:56 +00:00
|
|
|
|
|
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:
|
2001-06-15 11:37:56 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
ispell -vv
|
2001-06-15 11:37:56 +00:00
|
|
|
|
|
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.
|
2001-09-26 19:21:00 +00:00
|
|
|
|
|
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.
|
2001-09-26 19:21:00 +00:00
|
|
|
|
|
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.
|
2001-09-26 19:21:00 +00:00
|
|
|
|
|
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.
|
2001-09-26 19:21:00 +00:00
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
can cause this error. Remove that file, execute 'ispell-kill-ispell'
|
2004-08-21 11:31:45 +00:00
|
|
|
|
in Emacs, and then try spell-checking again.
|
2001-09-26 19:21:00 +00:00
|
|
|
|
|
2016-08-23 19:27:54 +00:00
|
|
|
|
*** TLS problems, e.g., Gnus hangs when fetching via imaps
|
2017-09-13 22:52:52 +00:00
|
|
|
|
https://debbugs.gnu.org/24247
|
2016-08-23 19:27:54 +00:00
|
|
|
|
|
|
|
|
|
gnutls-cli 3.5.3 (2016-08-09) does not generate a "- Handshake was
|
|
|
|
|
completed" message that tls.el relies upon, causing affected Emacs
|
|
|
|
|
functions to hang. To work around the problem, use older or newer
|
|
|
|
|
versions of gnutls-cli, or use Emacs's built-in gnutls support.
|
|
|
|
|
|
2021-11-08 03:51:44 +00:00
|
|
|
|
*** SVG images may be cropped incorrectly with librsvg 2.45 or older.
|
|
|
|
|
|
|
|
|
|
Librsvg 2.46 and above have improved geometry code which Emacs is able
|
|
|
|
|
to take advantage of.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
* Runtime problems related to font handling
|
2001-09-26 19:21:00 +00:00
|
|
|
|
|
2008-10-25 17:19:12 +00:00
|
|
|
|
** Characters are displayed as empty boxes or with wrong font under X.
|
|
|
|
|
|
2021-01-05 13:42:10 +00:00
|
|
|
|
*** This may be due to your local fontconfig customization.
|
|
|
|
|
Try removing or moving aside "$XDG_CONFIG_HOME/fontconfig/conf.d" and
|
|
|
|
|
"$XDG_CONFIG_HOME/fontconfig/fonts.conf"
|
|
|
|
|
($XDG_CONFIG_HOME is treated as "~/.config" if not set)
|
|
|
|
|
|
2021-10-20 16:22:40 +00:00
|
|
|
|
Running Emacs as
|
|
|
|
|
|
|
|
|
|
FC_DEBUG=1024 emacs
|
|
|
|
|
|
|
|
|
|
will cause fontconfig to output information about which configuration
|
|
|
|
|
files it is reading. Running Emacs as
|
|
|
|
|
|
|
|
|
|
FC_DEBUG=1 emacs
|
|
|
|
|
|
|
|
|
|
will result in information about the results of fontconfig's font
|
|
|
|
|
matching (including the filename(s) of the resulting fonts).
|
|
|
|
|
|
2008-10-25 17:19:12 +00:00
|
|
|
|
*** 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
|
2015-04-07 17:42:28 +00:00
|
|
|
|
other application), removing ~/.fonts.cache-1, and then starting the
|
2008-10-25 17:19:12 +00:00
|
|
|
|
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
|
2021-10-20 16:27:36 +00:00
|
|
|
|
known to occur for character number 160 (no-break space, U+A0) in some
|
2008-10-25 17:19:12 +00:00
|
|
|
|
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.
|
2001-09-26 19:21:00 +00:00
|
|
|
|
|
2014-03-22 22:56:29 +00:00
|
|
|
|
Each X font covers just a fraction of the characters that Emacs
|
2004-08-21 11:31:45 +00:00
|
|
|
|
supports. To display the whole range of Emacs characters requires
|
2008-10-25 17:19:12 +00:00
|
|
|
|
many different fonts, collected into a fontset. You can remedy the
|
|
|
|
|
problem by installing additional fonts.
|
2001-06-20 10:52:38 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
The intlfonts distribution includes a full spectrum of fonts that can
|
2006-06-30 12:40:06 +00:00
|
|
|
|
display all the characters Emacs supports. The etl-unicode collection
|
2017-09-13 22:52:52 +00:00
|
|
|
|
of fonts (available from
|
|
|
|
|
<https://ftp.nluug.nl/windowing/X/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.
|
2001-06-20 10:52:38 +00:00
|
|
|
|
|
2014-03-22 22:56:29 +00:00
|
|
|
|
** Under X, some characters appear improperly aligned in their lines.
|
2001-06-20 10:52:38 +00:00
|
|
|
|
|
2014-03-22 22:56:29 +00:00
|
|
|
|
You may have bad fonts.
|
2008-10-25 17:19:12 +00:00
|
|
|
|
|
2020-01-14 09:49:28 +00:00
|
|
|
|
** Under X, some characters are unexpectedly wide.
|
|
|
|
|
|
|
|
|
|
e.g. recent versions of Inconsolata show this issue for almost all of
|
|
|
|
|
its characters. Due to what is probably an Xft bug, the determination
|
|
|
|
|
of the width of some characters is incorrect. One workaround is to
|
|
|
|
|
build emacs with Cairo enabled ("configure --with-cairo" and have the
|
|
|
|
|
appropriate Cairo development packages installed) as this
|
|
|
|
|
configuration does not suffer from this problem. See
|
|
|
|
|
<https://github.com/googlefonts/Inconsolata/issues/42> and
|
2020-10-09 10:23:02 +00:00
|
|
|
|
<https://lists.gnu.org/r/bug-gnu-emacs/2020-01/msg00456.html>
|
2020-01-14 09:49:28 +00:00
|
|
|
|
for more discussion.
|
|
|
|
|
|
2008-10-25 17:19:12 +00:00
|
|
|
|
** 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
|
2001-06-20 10:52:38 +00:00
|
|
|
|
|
2017-11-26 06:45:41 +00:00
|
|
|
|
https://lists.gnu.org/r/emacs-devel/2008-10/msg00696.html
|
2001-11-30 08:24:22 +00:00
|
|
|
|
|
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.
|
2001-11-30 08:24:22 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Font Lock displays portions of the buffer in incorrect faces.
|
2001-12-02 21:03:42 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +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
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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.
|
2001-12-02 21:03:42 +00:00
|
|
|
|
|
2005-02-09 15:50:47 +00:00
|
|
|
|
Beginning with version 22.1, a parenthesis or a brace in column zero
|
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.
|
2001-12-02 21:03:42 +00:00
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'font-lock-beginning-of-syntax-function' to a nil value. (This must
|
2004-08-21 11:31:45 +00:00
|
|
|
|
be done _after_ turning on Font Lock.)
|
2001-05-09 15:21:44 +00:00
|
|
|
|
|
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.
|
2001-05-09 15:21:44 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Emacs pauses for several seconds when changing the default font.
|
2001-08-23 12:00:09 +00:00
|
|
|
|
|
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.
|
2000-11-19 12:36:50 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
A workaround for this is to add something like
|
2000-11-19 12:36:50 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
emacs.waitForWM: false
|
2002-01-14 21:07:59 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
to your X resources. Alternatively, add '(wait-for-wm . nil)' to a
|
2004-08-21 11:31:45 +00:00
|
|
|
|
frame's parameter list, like this:
|
2002-01-14 21:07:59 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
(modify-frame-parameters nil '((wait-for-wm . nil)))
|
2003-06-14 11:26:08 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
(this should go into your '.emacs' file).
|
2003-06-14 11:26:08 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Underlines appear at the wrong position.
|
2003-06-14 11:26:08 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
This is caused by fonts having a wrong UNDERLINE_POSITION property.
|
2018-02-13 22:13:53 +00:00
|
|
|
|
To avoid this problem (seen in some very old X releases and font packages),
|
|
|
|
|
set x-use-underline-position-properties to nil.
|
2003-06-14 11:26:08 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
To see what is the value of UNDERLINE_POSITION defined by the font,
|
2015-08-26 21:05:43 +00:00
|
|
|
|
type 'xlsfonts -lll FONT' and look at the font's UNDERLINE_POSITION property.
|
2000-11-13 23:31:10 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** When using Exceed, fonts sometimes appear too tall.
|
2001-07-26 15:43:08 +00:00
|
|
|
|
|
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".
|
2001-07-26 15:43:08 +00:00
|
|
|
|
|
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).
|
2001-07-26 15:43:08 +00:00
|
|
|
|
|
2007-09-28 03:30:10 +00:00
|
|
|
|
** Subscript/superscript text in TeX is hard to read.
|
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
If 'tex-fontify-script' is non-nil, tex-mode displays
|
2007-09-28 03:30:10 +00:00
|
|
|
|
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).
|
|
|
|
|
|
2016-05-25 21:42:54 +00:00
|
|
|
|
** Screen refresh is slow when there are special characters for which no suitable font is available
|
|
|
|
|
|
|
|
|
|
If the display is too slow in refreshing when you scroll to a new
|
|
|
|
|
region, or when you edit the buffer, it might be due to the fact that
|
|
|
|
|
some characters cannot be displayed in the default font, and Emacs is
|
|
|
|
|
spending too much time in looking for a suitable font to display them.
|
|
|
|
|
|
|
|
|
|
You can suspect this if you have several characters that are displayed
|
|
|
|
|
as small rectangles containing a hexadecimal code inside.
|
|
|
|
|
|
|
|
|
|
The solution is to install the appropriate fonts on your machine. For
|
|
|
|
|
instance if you are editing a text with a lot of math symbols, then
|
|
|
|
|
installing a font like 'Symbola' should solve this problem.
|
|
|
|
|
|
2017-02-18 10:36:43 +00:00
|
|
|
|
Another reason for slow display is reportedly the nerd-fonts
|
|
|
|
|
installation, even when Symbola is installed as well. Uninstalling
|
|
|
|
|
nerd-fonts was reported to solve the problem in that case.
|
|
|
|
|
|
2017-03-04 13:56:50 +00:00
|
|
|
|
** Emacs running on GNU/Linux system with the m17n library Ver.1.7.1 or the
|
2017-03-04 19:32:39 +00:00
|
|
|
|
earlier version has a problem with rendering Bengali script.
|
2017-03-04 13:56:50 +00:00
|
|
|
|
|
|
|
|
|
The problem can be fixed by installing the newer version of the m17n
|
|
|
|
|
library (if any), or by following this procedure:
|
|
|
|
|
|
|
|
|
|
1. Locate the file BENG-OTF.flt installed on your system as part of the
|
|
|
|
|
m17n library. Usually it is under the directory /usr/share/m17n.
|
|
|
|
|
|
|
|
|
|
2. Apply the following patch to BENG-OTF.flt
|
|
|
|
|
|
|
|
|
|
------------------------------------------------------------
|
|
|
|
|
diff --git a/FLT/BENG-OTF.flt b/FLT/BENG-OTF.flt
|
|
|
|
|
index 45cc554..0cc5e76 100644
|
|
|
|
|
--- a/FLT/BENG-OTF.flt
|
|
|
|
|
+++ b/FLT/BENG-OTF.flt
|
|
|
|
|
@@ -232,7 +232,7 @@
|
|
|
|
|
(lang-forms
|
|
|
|
|
(cond
|
|
|
|
|
("(.H)J" (1 :otf=beng=half+))
|
|
|
|
|
- (".H" :otf=beng=blwf,half,vatu+)
|
|
|
|
|
+ (".+H" :otf=beng=blwf,half,vatu+)
|
|
|
|
|
("." =)))
|
|
|
|
|
|
|
|
|
|
(post
|
|
|
|
|
------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
If you can't modify that file directly, copy it to the directory
|
|
|
|
|
~/.m17n.d/ (create it if it doesn't exist), and apply the patch.
|
|
|
|
|
|
2017-11-07 11:53:32 +00:00
|
|
|
|
** Emacs running on GNU/Linux system with the m17n library Ver.1.7.1 or the
|
|
|
|
|
earlier version has a problem with rendering Lao script with OpenType font.
|
|
|
|
|
|
|
|
|
|
The problem can be fixed by installing the newer version of the m17n
|
|
|
|
|
library (if any), or by following this procedure:
|
|
|
|
|
|
|
|
|
|
1. Locate the file LAOO-OTF.flt installed on your system as part of the
|
|
|
|
|
m17n library. Usually it is under the directory /usr/share/m17n.
|
|
|
|
|
|
|
|
|
|
2. Apply the following patch to LAOO-OTF.flt
|
|
|
|
|
|
|
|
|
|
------------------------------------------------------------
|
|
|
|
|
diff --git a/FLT/LAOO-OTF.flt b/FLT/LAOO-OTF.flt
|
|
|
|
|
index 5504171..431adf8 100644
|
|
|
|
|
--- a/FLT/LAOO-OTF.flt
|
|
|
|
|
+++ b/FLT/LAOO-OTF.flt
|
|
|
|
|
@@ -3,7 +3,7 @@
|
|
|
|
|
;; See the end for copying conditions.
|
|
|
|
|
|
|
|
|
|
(font layouter laoo-otf nil
|
|
|
|
|
- (font (nil phetsarath\ ot unicode-bmp)))
|
|
|
|
|
+ (font (nil nil unicode-bmp :otf=lao\ )))
|
|
|
|
|
|
|
|
|
|
;;; <li> LAOO-OTF.flt
|
|
|
|
|
|
|
|
|
|
------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
If you can't modify that file directly, copy it to the directory
|
|
|
|
|
~/.m17n.d/ (create it if it doesn't exist), and apply the patch.
|
|
|
|
|
|
2020-09-20 11:08:35 +00:00
|
|
|
|
** On MS-Windows, some characters display as boxes with hex code.
|
|
|
|
|
|
|
|
|
|
Also, some characters could display with wrong fonts.
|
|
|
|
|
|
|
|
|
|
This can happen if Emacs was compiled without HarfBuzz support, and/or
|
|
|
|
|
if the HarfBuzz DLLs are not available at run time. Emacs will then
|
|
|
|
|
fall back to the Uniscribe as its shaping engine; Uniscribe was
|
|
|
|
|
deprecated by Microsoft, and sometimes fails to display correctly when
|
|
|
|
|
modern fonts are used, such as Noto Emoji or Ebrima.
|
|
|
|
|
|
|
|
|
|
The solution is to switch to a configuration that uses HarfBuzz as its
|
|
|
|
|
shaping engine, where these problems don't exist.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
* Internationalization problems
|
2001-07-26 15:43:08 +00:00
|
|
|
|
|
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.
|
|
|
|
|
|
2009-09-13 20:46:46 +00:00
|
|
|
|
** International characters aren't displayed under X.
|
|
|
|
|
|
|
|
|
|
*** Missing X fonts
|
2001-07-26 15:43:08 +00:00
|
|
|
|
|
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:
|
2001-07-26 15:43:08 +00:00
|
|
|
|
|
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
|
2001-07-26 15:43:08 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** The UTF-8/16/7 coding systems don't encode CJK (Far Eastern) characters.
|
2001-07-26 15:43:08 +00:00
|
|
|
|
|
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.
|
2000-09-08 16:53:08 +00:00
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
substituted with the Unicode 'replacement character', and you lose
|
2004-08-21 11:31:45 +00:00
|
|
|
|
information.
|
2000-09-08 16:53:08 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
2014-01-23 02:11:13 +00:00
|
|
|
|
when they are really ASCII fonts. In particular the schumacher-clean
|
2000-12-19 17:21:55 +00:00
|
|
|
|
fonts have this bug in some versions of X.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
To see what glyphs are included in a font, use 'xfd', like this:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2000-12-19 17:21:55 +00:00
|
|
|
|
The solution is to remove the corresponding lines from the appropriate
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'fonts.alias' file, then run 'mkfontdir' in that directory, and then run
|
|
|
|
|
'xset fp rehash'.
|
2003-02-04 14:56:31 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
** The 'oc-unicode' package doesn't work with Emacs 21.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
flexible. (Use option 'utf-translate-cjk-mode' if you need CJK
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
* X runtime problems
|
2000-12-27 16:20:44 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** X keyboard problems
|
2000-12-27 16:20:44 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** You "lose characters" after typing Compose Character key.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
This is because the Compose Character key is defined as the keysym
|
2014-03-22 22:56:29 +00:00
|
|
|
|
Multi_key, and Emacs (seeing that) does the proper X
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
For example, here's one way to turn it into a Meta key:
|
2003-02-04 14:56:31 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
xmodmap -e "keysym Multi_key = Meta_L"
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2015-04-07 17:42:28 +00:00
|
|
|
|
*** Using X Window System, control-shift-leftbutton makes Emacs hang.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
Use the shell command 'xset bc' to make the old X Menu package work.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2006-04-12 06:53:43 +00:00
|
|
|
|
*** C-SPC fails to work on Fedora GNU/Linux (or with fcitx input method).
|
2005-06-25 04:48:24 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
Fedora Core 4 steals the C-SPC key by default for the 'iiimx' program
|
2005-06-25 04:48:24 +00:00
|
|
|
|
which is the input method for some languages. It blocks Emacs users
|
2015-08-26 21:05:43 +00:00
|
|
|
|
from using the C-SPC key for 'set-mark-command'.
|
2005-06-25 04:48:24 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
One solutions is to remove the '<Ctrl>space' from the 'Iiimx' file
|
|
|
|
|
which can be found in the '/usr/lib/X11/app-defaults' directory.
|
2005-06-25 04:48:24 +00:00
|
|
|
|
However, that requires root access.
|
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
Another is to specify 'Emacs*useXIM: false' in your X resources.
|
2005-06-25 04:48:24 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
Another is to build Emacs with the '--without-xim' configure option.
|
2005-06-25 04:48:24 +00:00
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
accustomed to use C-@ for 'set-mark-command'.
|
2006-04-11 01:28:04 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** M-SPC seems to be ignored as input.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
definition is in the file '...lib/X11/locale/iso8859-1/Compose'; there
|
2004-08-21 11:31:45 +00:00
|
|
|
|
might be other similar combinations which are grabbed by X for similar
|
|
|
|
|
purposes.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
We think that this can be countermanded with the 'xmodmap' utility, if
|
2004-08-21 11:31:45 +00:00
|
|
|
|
you want to be able to bind one of these key sequences within Emacs.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2014-01-23 02:11:13 +00:00
|
|
|
|
These may have been intercepted by your window manager.
|
|
|
|
|
See the WM's documentation for how to change this.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
If the keyboard has just one key named Alt, then only one of those
|
2015-08-26 21:05:43 +00:00
|
|
|
|
commands is needed. The modifier 'mod2' is a reasonable choice if you
|
2004-08-21 11:31:45 +00:00
|
|
|
|
are using an unmodified MIT version of X. Otherwise, choose any
|
|
|
|
|
modifier bit not otherwise used.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2018-01-01 16:28:53 +00:00
|
|
|
|
*** Emacs hangs or crashes when a large portion of text is selected or killed.
|
|
|
|
|
|
|
|
|
|
This is caused by a bug in the clipboard management applets (it has
|
|
|
|
|
been observed in 'klipper' and 'clipit'), which periodically request
|
|
|
|
|
the X clipboard contents from applications. After a while, Emacs may
|
|
|
|
|
print a message:
|
|
|
|
|
|
|
|
|
|
Timed out waiting for property-notify event
|
|
|
|
|
|
|
|
|
|
A workaround is to not use 'klipper'/'clipit'. Upgrading 'klipper' to
|
|
|
|
|
the one coming with KDE 3.3 or later might solve the problem; if it
|
|
|
|
|
doesn't, set 'select-active-regions' to 'only' or nil.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Window-manager and toolkit-related problems
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2016-05-21 07:19:32 +00:00
|
|
|
|
*** Emacs built with GTK+ toolkit produces corrupted display on HiDPI screen
|
|
|
|
|
|
|
|
|
|
This can happen if you set GDK_SCALE=2 in the environment or in your
|
|
|
|
|
'.xinitrc' file. (This setting is usually accompanied by
|
|
|
|
|
GDK_DPI_SCALE=0.5.) Emacs can not support these settings correctly,
|
|
|
|
|
as it doesn't use GTK+ exclusively. The result is that sometimes
|
|
|
|
|
widgets like the scroll bar are displayed incorrectly, and frames
|
|
|
|
|
could be displayed "cropped" to only part of the stuff that should be
|
|
|
|
|
displayed.
|
|
|
|
|
|
|
|
|
|
The workaround is to explicitly disable these settings when invoking
|
|
|
|
|
Emacs, for example (from a Posix shell prompt):
|
|
|
|
|
|
|
|
|
|
$ GDK_SCALE=1 GDK_DPI_SCALE=1 emacs
|
|
|
|
|
|
2016-07-06 07:55:46 +00:00
|
|
|
|
*** Emacs built with GTK+ toolkit can unexpectedly widen frames
|
|
|
|
|
|
|
|
|
|
This resizing takes place when a frame is not wide enough to accommodate
|
|
|
|
|
its entire menu bar. Typically, it occurs when switching buffers or
|
|
|
|
|
changing a buffer's major mode and the new mode adds entries to the menu
|
|
|
|
|
bar. The frame is then widened by the window manager so that the menu
|
|
|
|
|
bar is fully shown. Subsequently switching to another buffer or
|
|
|
|
|
changing the buffer's mode will not shrink the frame back to its
|
|
|
|
|
previous width. The height of the frame remains unaltered. Apparently,
|
|
|
|
|
the failure is also dependent on the chosen font.
|
|
|
|
|
|
|
|
|
|
The resizing is usually accompanied by console output like
|
|
|
|
|
|
|
|
|
|
Gtk-CRITICAL **: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed
|
|
|
|
|
|
|
|
|
|
It's not clear whether the GTK version used has any impact on the
|
|
|
|
|
occurrence of the failure. So far, the failure has been observed with
|
2016-07-06 08:39:11 +00:00
|
|
|
|
GTK+ versions 3.4.2, 3.14.5 and 3.18.7. However, another 3.4.2 build
|
|
|
|
|
does not exhibit the bug.
|
2016-07-06 07:55:46 +00:00
|
|
|
|
|
2016-07-13 10:23:22 +00:00
|
|
|
|
Some window managers (Xfce) apparently work around this failure by
|
2016-07-06 07:55:46 +00:00
|
|
|
|
cropping the menu bar. With other windows managers, it's possible to
|
|
|
|
|
shrink the frame manually after the problem occurs, e.g. by dragging the
|
|
|
|
|
frame's border with the mouse. However, some window managers have been
|
|
|
|
|
reported to refuse such attempts and snap back to the width needed to
|
|
|
|
|
show the full menu bar (wmii) or at least cause the screen to flicker
|
2016-07-13 10:23:22 +00:00
|
|
|
|
during such resizing attempts (i3, IceWM).
|
2016-07-06 07:55:46 +00:00
|
|
|
|
|
2017-09-13 22:52:52 +00:00
|
|
|
|
See also https://debbugs.gnu.org/cgi/bugreport.cgi?bug=15700,
|
|
|
|
|
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22000,
|
|
|
|
|
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22898 and
|
2017-11-26 06:45:41 +00:00
|
|
|
|
https://lists.gnu.org/r/emacs-devel/2016-07/msg00154.html.
|
2016-07-06 08:39:11 +00:00
|
|
|
|
|
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
|
2014-03-22 22:56:29 +00:00
|
|
|
|
or shifting out from X and back again usually cures it (i.e. Ctrl-Alt-F1
|
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".
|
|
|
|
|
|
2022-01-20 09:30:08 +00:00
|
|
|
|
*** Enlightenment: Frames not redrawn after switching virtual desktops
|
|
|
|
|
|
|
|
|
|
With Enlightenment version 0.25, Emacs frames may no be redrawn orderly
|
|
|
|
|
after switching back from another virtual desktop. Setting the variable
|
|
|
|
|
'x-set-frame-visibility-more-laxly' to one of 'focus-in', 'expose' or
|
|
|
|
|
't' should fix this.
|
|
|
|
|
|
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
|
2018-08-24 17:13:08 +00:00
|
|
|
|
bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=357032
|
2006-09-30 17:58:29 +00:00
|
|
|
|
|
2017-03-04 09:17:40 +00:00
|
|
|
|
*** Gnome: GPaste clipboard manager causes erratic behavior of 'yank'
|
|
|
|
|
|
|
|
|
|
The symptom is that 'kill-line' followed by 'yank' often (but not
|
|
|
|
|
always) doesn't insert the whitespace of the killed and yanked line.
|
|
|
|
|
|
|
|
|
|
The solution is to set the GPaste "trim items" option to OFF.
|
|
|
|
|
|
2019-10-08 13:41:00 +00:00
|
|
|
|
*** Gnome: Navigation from Nautilus to remote files.
|
|
|
|
|
|
|
|
|
|
If you navigate to a file, which belongs to a remote server, in
|
|
|
|
|
Nautilus via "Open With Emacs" you might not be able to save this file
|
|
|
|
|
once you have modified it in Emacs. The reasons for the failure can
|
|
|
|
|
vary, and for some connection methods saving the file might even succeed.
|
|
|
|
|
|
|
|
|
|
If the remote connection in Nautilus uses ssh or sftp, you could
|
|
|
|
|
mitigate the problem by the following lines in your .emacs file:
|
|
|
|
|
|
|
|
|
|
(dir-locals-set-class-variables 'gvfs '((nil . ((create-lockfiles . nil)))))
|
|
|
|
|
(dir-locals-set-directory-class (format "/run/user/%d/gvfs" (user-uid)) 'gvfs)
|
|
|
|
|
|
|
|
|
|
A better approach might be to avoid navigation from Nautilus to Emacs
|
|
|
|
|
for such files, and instead to open the file in Emacs using Tramp
|
|
|
|
|
remote file name syntax.
|
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Alternatively, if you do want the KDE defaults to apply to other
|
2015-08-26 21:05:43 +00:00
|
|
|
|
applications, but not to Emacs, you could modify the file 'Emacs.ad'
|
|
|
|
|
(should be in the '/usr/share/apps/kdisplay/app-defaults/' directory)
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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.
|
|
|
|
|
|
2016-07-21 15:07:48 +00:00
|
|
|
|
*** KDE / Plasma 5: Emacs exhausts memory and needs to be killed
|
|
|
|
|
|
|
|
|
|
This problem occurs when large selections contain mixed line endings
|
|
|
|
|
(i.e. the buffer has LF line endings, but in some parts CRLF is used).
|
|
|
|
|
The source of the problem is currently under investigation, older
|
|
|
|
|
versions of Emacs up to 24.5 just hang for a few seconds and then
|
|
|
|
|
return with the message "Timed out waiting for property-notify event"
|
|
|
|
|
as described in the previous note. As a workaround, go to the
|
|
|
|
|
settings dialog for the Clipboard widget and select the option "Ignore
|
|
|
|
|
Selection".
|
|
|
|
|
|
|
|
|
|
Note: Plasma 5 has replaced the separate klipper process from earlier
|
|
|
|
|
KDE versions with functionality directly integrated into plasmashell,
|
|
|
|
|
so even if you've previously did not use klipper this will affect you.
|
|
|
|
|
Also, all configuration you might have done to klipper is not used by
|
|
|
|
|
the new Clipboard widget / plasmoid since it uses its own settings.
|
|
|
|
|
You can hide the Clipboard widget by removing its entry from the
|
|
|
|
|
system tray settings "Extra Items", but it's not clear if the
|
|
|
|
|
underlying functionality in plasmashell gets fully disabled as well.
|
|
|
|
|
At least a restart of plasmashell is required for the clipboard
|
|
|
|
|
history to be cleared.
|
|
|
|
|
|
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
|
|
|
|
|
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".
|
2001-02-05 17:16:40 +00:00
|
|
|
|
|
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.
|
2001-02-05 17:16:40 +00:00
|
|
|
|
|
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.
|
2001-11-20 19:14:55 +00:00
|
|
|
|
|
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.
|
2001-11-20 19:14:55 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2014-01-23 02:11:13 +00:00
|
|
|
|
As a workaround, you can try building Emacs using Motif or LessTif instead.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** LessTif: Problems in Emacs built with LessTif.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Only the Motif 1.2 emulation seems to be stable enough in LessTif.
|
2007-04-12 04:16:47 +00:00
|
|
|
|
LessTif 0.92-17's Motif 1.2 emulation seems to work okay on FreeBSD.
|
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
|
|
|
|
|
2014-01-23 02:11:13 +00:00
|
|
|
|
On some systems, Emacs occasionally locks up, grabbing all mouse and
|
|
|
|
|
keyboard events. We don't know what causes these problems; they are
|
|
|
|
|
not reproducible by Emacs developers.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Emacs*default.attributeFont: -*-courier-medium-r-*-*-*-140-*-*-*-*-iso8859-*
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
That the resource has this effect indicates a bug in something, but we
|
2014-01-23 02:11:13 +00:00
|
|
|
|
do not know what. If it is an Emacs bug, we hope someone can
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
|
|
|
|
2018-06-02 07:49:13 +00:00
|
|
|
|
*** FVWM: Some versions of FVWM incorrectly set the 'sticky' frame parameter.
|
|
|
|
|
|
|
|
|
|
Version 2.6.4 of the FVWM can make a frame sticky (appear on all user
|
|
|
|
|
desktops) when setting the 'sticky' frame parameter to nil. This may
|
|
|
|
|
happen without any special user interaction, for example, when Emacs
|
2018-06-02 09:05:52 +00:00
|
|
|
|
restores a saved desktop. A fix is to install version 2.6.8 of FVWM,
|
2018-06-02 07:49:13 +00:00
|
|
|
|
see https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31650.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** General X problems
|
2001-06-15 10:51:45 +00:00
|
|
|
|
|
2014-03-22 22:56:29 +00:00
|
|
|
|
*** Redisplay using X is much slower than previous Emacs versions.
|
2001-06-15 10:51:45 +00:00
|
|
|
|
|
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).
|
2001-06-15 10:51:45 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Here's how to do this:
|
2001-06-15 10:51:45 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
(set-scroll-bar-mode 'right)
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
(set-scroll-bar-mode 'left)
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** Error messages about undefined colors on X.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
The messages might say something like this:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Unable to load color "grey95"
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
(typically, in the '*Messages*' buffer), or something like this:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Error while displaying tooltip: (error Undefined color lightyellow)
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** Improving performance with slow X connections.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
2014-01-07 02:33:46 +00:00
|
|
|
|
the use of Emacs's own input methods, which are part of the Leim
|
2004-08-21 11:31:45 +00:00
|
|
|
|
package.
|
2001-06-13 12:31:09 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
2) If the connection is very slow, you might also want to consider
|
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
|
2011-05-10 13:57:12 +00:00
|
|
|
|
after the initial frame is displayed:
|
2007-01-27 18:12:50 +00:00
|
|
|
|
|
|
|
|
|
(scroll-bar-mode -1)
|
|
|
|
|
(menu-bar-mode -1)
|
|
|
|
|
(tool-bar-mode -1)
|
|
|
|
|
|
2015-04-07 17:42:28 +00:00
|
|
|
|
For still quicker startup, put these X resources in your
|
|
|
|
|
.Xresources or .Xdefaults file:
|
2007-01-27 18:12:50 +00:00
|
|
|
|
|
|
|
|
|
Emacs.verticalScrollBars: off
|
|
|
|
|
Emacs.menuBar: off
|
|
|
|
|
Emacs.toolBar: off
|
2001-06-13 12:31:09 +00:00
|
|
|
|
|
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 ...).
|
2001-06-13 12:31:09 +00:00
|
|
|
|
|
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
|
2011-11-14 23:59:56 +00:00
|
|
|
|
of the X protocol. lbxproxy achieves the performance gain by grouping
|
2004-08-21 11:31:45 +00:00
|
|
|
|
several X requests in one TCP packet and sending them off together,
|
2007-04-12 04:16:47 +00:00
|
|
|
|
instead of requiring a round-trip for each X request in a separate
|
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:
|
2015-04-07 17:42:28 +00:00
|
|
|
|
http://www.x.org/archive/X11R6.8.0/doc/lbxproxy.1.html
|
2001-06-13 12:31:09 +00:00
|
|
|
|
|
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)
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** Emacs gives the error, Couldn't find per display information.
|
2001-06-13 12:31:09 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
We do not know of a way to prevent the problem.
|
2002-08-17 00:08:54 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
*** An error message such as 'X protocol error: BadMatch (invalid
|
2004-08-21 11:31:45 +00:00
|
|
|
|
parameter attributes) on protocol request 93'.
|
2002-05-03 09:56:01 +00:00
|
|
|
|
|
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.)
|
2002-05-03 09:56:01 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
The fix is to correct your X resources.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** Slow startup on X11R6 with X windows.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2008-08-26 20:02:17 +00:00
|
|
|
|
xset -fp /usr/X11R6/lib/X11/fonts/Type1/
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Emacs*geometry: 80x55+0+0
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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.
|
1999-11-30 18:44:14 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
To check thoroughly for such resource specifications, use 'xrdb
|
2004-08-21 11:31:45 +00:00
|
|
|
|
-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
|
|
|
|
|
2015-04-07 17:42:28 +00:00
|
|
|
|
*** Emacs running under X Window System does not handle mouse clicks.
|
2015-08-26 21:05:43 +00:00
|
|
|
|
*** 'emacs -geometry 80x20' finds a file named '80x20'.
|
2002-03-02 11:14:03 +00:00
|
|
|
|
|
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.
|
2002-03-02 11:14:03 +00:00
|
|
|
|
|
2015-04-07 17:42:28 +00:00
|
|
|
|
*** X doesn't work if DISPLAY uses a hostname.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
People have reported kernel bugs in certain systems that cause Emacs
|
2015-04-07 17:42:28 +00:00
|
|
|
|
not to work with X if DISPLAY is set using a host name. But
|
2015-08-26 21:05:43 +00:00
|
|
|
|
the problem does not occur if DISPLAY is set to 'unix:0.0'. I think
|
2004-08-21 11:31:45 +00:00
|
|
|
|
the bug has to do with SIGIO or FIONREAD.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
|
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.
|
2015-08-26 21:05:43 +00:00
|
|
|
|
If the problem persists, set 'x-select-enable-clipboard-manager' to nil.
|
2012-02-25 01:54:17 +00:00
|
|
|
|
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
reducing the value of 'x-selection-timeout', either in .emacs or with
|
2012-02-25 01:54:17 +00:00
|
|
|
|
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 .
|
|
|
|
|
|
2013-04-07 11:01:56 +00:00
|
|
|
|
*** Warning messages when running in Ubuntu
|
|
|
|
|
|
|
|
|
|
When you start Emacs you may see something like this:
|
|
|
|
|
|
2014-05-03 07:09:16 +00:00
|
|
|
|
(emacs:2286): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'GTK_IS_MENU_SHELL(menu)' failed
|
2013-04-07 11:01:56 +00:00
|
|
|
|
|
2013-04-10 01:20:51 +00:00
|
|
|
|
This happens if the Emacs binary has been renamed. The cause is the Ubuntu
|
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
|
2013-04-10 01:20:51 +00:00
|
|
|
|
that depend on what state Emacs is in are usually wrong (i.e. paste disabled
|
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
|
|
|
|
|
|
2020-08-27 05:58:17 +00:00
|
|
|
|
*** Mouse click coordinates not recognized correctly on multiple monitors.
|
|
|
|
|
|
|
|
|
|
This happens on the proprietary X server ASTEC-X when the number of
|
|
|
|
|
monitors is changed after the server has started. A workaround is to
|
|
|
|
|
restart the X server after the monitor configuration has been changed.
|
|
|
|
|
|
2007-04-12 04:16:47 +00:00
|
|
|
|
* Runtime problems on character terminals
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2021-11-05 06:49:39 +00:00
|
|
|
|
*** With X forwarding, mouse highlighting can make Emacs slow.
|
|
|
|
|
|
|
|
|
|
If you see slow updates when moving the mouse in an Emacs running on a
|
|
|
|
|
remote X server, try this:
|
|
|
|
|
|
|
|
|
|
(setq mouse-highlight nil)
|
|
|
|
|
|
2010-03-19 15:15:27 +00:00
|
|
|
|
** The meta key does not work on xterm.
|
2014-03-22 22:56:29 +00:00
|
|
|
|
|
2010-03-19 15:15:27 +00:00
|
|
|
|
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)
|
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
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
|
2004-08-21 11:31:45 +00:00
|
|
|
|
escape sequence that the computer can send to turn flow control off
|
2015-08-26 21:05:43 +00:00
|
|
|
|
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
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
rate as known by the kernel. The shell command 'stty' will print
|
|
|
|
|
your output baud rate; 'stty' with suitable arguments will set it if
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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.
|
2001-01-11 23:09:41 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'enable-flow-control-on' to turn on this flow control avoidance scheme
|
2004-08-21 11:31:45 +00:00
|
|
|
|
automatically. Here is an example:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
(enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
This could mean that the termcap entry you are using for that
|
2015-04-07 17:42:28 +00:00
|
|
|
|
terminal is wrong, or it could mean that Emacs has a bug handling
|
2004-08-21 11:31:45 +00:00
|
|
|
|
the combination of features specified for that terminal.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
2) The characters sent are incorrect, due to an obscure aspect
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
3) The termcap entry is wrong.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
control on the local system. Sometimes 'rlogin -8' will avoid this problem.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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,
|
2009-06-16 02:55:46 +00:00
|
|
|
|
"stty start u stop u" will do this. On some systems, use
|
2010-07-20 18:32:42 +00:00
|
|
|
|
"stty -ixon" instead.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
(enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Output from Control-V is slow.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
specify any padding time for the 'al' and 'dl' strings. Emacs
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
fix the termcap entry to specify, for the 'al' and 'dl', as much
|
2004-08-21 11:31:45 +00:00
|
|
|
|
time as the operations really take.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Most bit-map terminals provide commands for inserting or deleting
|
2015-08-26 21:05:43 +00:00
|
|
|
|
multiple lines at once. Define the 'AL' and 'DL' strings in the
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'cm' string.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
You should also define the 'IC' and 'DC' strings if your terminal
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
A 'cs' string to set the scrolling region will reduce the amount
|
2004-08-21 11:31:45 +00:00
|
|
|
|
of motion you see on the screen when part of the screen is scrolled.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
Put 'stty dec' in your .login file and your problems will disappear
|
2004-08-21 11:31:45 +00:00
|
|
|
|
after a day or two.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
For this reason, I believe 'stty dec' is the right mode to use,
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
important than adapting to people who don't use 'stty dec'.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
In addition to the "Co" capability, Emacs needs the "op" (for
|
2015-08-26 21:05:43 +00:00
|
|
|
|
"original pair") capability, which tells how to switch the terminal
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
this capability to '0' (zero) and see if that helps.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Emacs uses the database entry for the terminal whose name is the value
|
2015-08-26 21:05:43 +00:00
|
|
|
|
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
|
2004-08-21 11:31:45 +00:00
|
|
|
|
emulator.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2005-02-09 15:50:47 +00:00
|
|
|
|
Beginning with version 22.1, Emacs supports the --color command-line
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Some modes do not use colors unless you turn on the Font-lock mode.
|
2015-08-26 21:05:43 +00:00
|
|
|
|
Some people have long ago set their '~/.emacs' files to turn on
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'global-font-lock-mode'.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2012-03-31 20:22:04 +00:00
|
|
|
|
** Unexpected characters inserted into the buffer when you start Emacs.
|
2017-09-13 22:52:52 +00:00
|
|
|
|
See e.g. <URL:https://debbugs.gnu.org/11129>
|
2012-03-31 20:22:04 +00:00
|
|
|
|
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'check' (the default). See that variable's documentation (in
|
2012-03-31 20:22:04 +00:00
|
|
|
|
term/xterm.el) for more details.
|
|
|
|
|
|
2021-10-04 16:29:34 +00:00
|
|
|
|
** Incorrect or corrupted display of some Unicode characters
|
|
|
|
|
|
|
|
|
|
*** Linux console problems with double-width characters
|
|
|
|
|
|
|
|
|
|
The Linux console declares UTF-8 encoding, but supports only a limited
|
|
|
|
|
number of Unicode characters, and can cause Emacs produce corrupted or
|
|
|
|
|
garbled display with some unusual characters and sequences. Emacs 28
|
|
|
|
|
and later by default disables 'auto-composition-mode' on this console,
|
|
|
|
|
for that reason, but this might not be enough. One known problem with
|
|
|
|
|
this console is that zero-width and double-width characters are
|
|
|
|
|
displayed incorrectly (as a single-column characters), and that causes
|
|
|
|
|
the cursor to be out of sync with the actual display.
|
|
|
|
|
|
|
|
|
|
One way of working around this is to use the display-table feature to
|
|
|
|
|
display the problematic characters as some other, less problematic
|
|
|
|
|
ones. Here's an example of setting up the standard display table to
|
|
|
|
|
show the U+01F64F PERSON WITH FOLDED HANDS character as a diamond with
|
|
|
|
|
a special face:
|
|
|
|
|
|
|
|
|
|
(or standard-display-table
|
|
|
|
|
(setq standard-display-table (make-display-table)))
|
|
|
|
|
(aset standard-display-table
|
|
|
|
|
#x1f64f (vector (make-glyph-code #xFFFD 'escape-glyph)))
|
|
|
|
|
|
|
|
|
|
Similar setup can be done with any other problematic character. If
|
|
|
|
|
the console cannot even display the U+FFFD REPLACEMENT CHARACTER, you
|
|
|
|
|
can use some ASCII character instead, like '?'; it will stand out due
|
|
|
|
|
to the 'escape-glyph' face. The disadvantage of this method is that
|
|
|
|
|
all such characters will look the same on display, and the only way of
|
|
|
|
|
knowing what is the real codepoint in the buffer is to go to the
|
|
|
|
|
character and type "C-u C-x =".
|
|
|
|
|
|
|
|
|
|
*** Messed-up display on the Kitty text terminal
|
|
|
|
|
|
|
|
|
|
This terminal has its own peculiar ideas about display of unusual
|
|
|
|
|
characters. For example, it hides the U+00AD SOFT HYPHEN characters
|
|
|
|
|
on display, which messes up Emacs cursor addressing, since Emacs
|
|
|
|
|
doesn't know these characters are effectively treated as zero-width
|
|
|
|
|
characters.
|
|
|
|
|
|
|
|
|
|
One way of working around such "hidden" characters is to tell Emacs to
|
|
|
|
|
display them as zero-width:
|
|
|
|
|
|
|
|
|
|
(aset glyphless-char-display #xAD 'zero-width)
|
|
|
|
|
|
|
|
|
|
Another possibility is to use display-table to display SOFT HYPHEN as
|
|
|
|
|
a regular ASCII dash character '-':
|
|
|
|
|
|
|
|
|
|
(or standard-display-table
|
|
|
|
|
(setq standard-display-table (make-display-table)))
|
|
|
|
|
(aset standard-display-table
|
|
|
|
|
#xAD (vector (make-glyph-code ?- 'escape-glyph)))
|
|
|
|
|
|
2021-10-05 14:12:49 +00:00
|
|
|
|
Another workaround is to set 'nobreak-char-ascii-display' to a non-nil
|
|
|
|
|
value, which will cause any non-ASCII space and hyphen characters to
|
|
|
|
|
be displayed as their ASCII counterparts, with a special face.
|
|
|
|
|
|
2021-10-04 16:29:34 +00:00
|
|
|
|
Kitty also differs from many other character terminals in how it
|
|
|
|
|
handles character compositions. As one example, Emoji sequences that
|
|
|
|
|
begin with a non-Emoji character and end in U+FE0F VARIATION SELECTOR
|
|
|
|
|
16 should be composed into an Emoji glyph; Kitty assumes that all such
|
|
|
|
|
Emoji glyphs have 2-column width, whereas Emacs and many other text
|
|
|
|
|
terminals display them as 1-column glyphs. Again, this causes cursor
|
|
|
|
|
addressing to get out of sync and eventually messes up the display.
|
|
|
|
|
|
|
|
|
|
One possible workaround for problems caused by character composition
|
|
|
|
|
is to turn off 'auto-composition-mode' on Kitty terminals.
|
|
|
|
|
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
* Runtime problems specific to individual Unix variants
|
2001-04-25 21:33:25 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** GNU/Linux
|
2001-04-25 21:33:25 +00:00
|
|
|
|
|
2019-02-02 01:58:05 +00:00
|
|
|
|
*** GNU/Linux: profiler-report outputs nothing.
|
|
|
|
|
|
|
|
|
|
A few versions of the Linux kernel have timer bugs that break CPU
|
2019-02-03 11:38:19 +00:00
|
|
|
|
profiling; see Bug#34235. To fix the problem, upgrade to one of the
|
|
|
|
|
kernel versions 4.14.97, 4.19.19, or 4.20.6, or later.
|
2019-02-02 01:58:05 +00:00
|
|
|
|
|
2005-06-08 12:13:32 +00:00
|
|
|
|
*** 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 "$@"
|
|
|
|
|
|
2011-01-18 02:31:59 +00:00
|
|
|
|
*** GNU/Linux: Truncated svn annotate output with SSH.
|
2017-09-13 22:52:52 +00:00
|
|
|
|
https://debbugs.gnu.org/7791
|
2011-01-18 02:31:59 +00:00
|
|
|
|
|
|
|
|
|
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
|
2015-04-07 17:42:28 +00:00
|
|
|
|
other access methods (e.g. http), or from outside Emacs.
|
2011-01-18 02:31:59 +00:00
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** GNU/Linux: After upgrading to a newer version of Emacs,
|
|
|
|
|
the Meta key stops working.
|
2001-06-24 13:16:33 +00:00
|
|
|
|
|
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.
|
2001-06-24 13:16:33 +00:00
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
and to the right of the space bar, together with the 'x' key, and see
|
2004-08-21 11:31:45 +00:00
|
|
|
|
which combination produces "M-x" in the echo area. You can also use
|
2015-08-26 21:05:43 +00:00
|
|
|
|
the 'xmodmap' utility to show all the keys which produce a Meta
|
2004-08-21 11:31:45 +00:00
|
|
|
|
modifier:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2016-05-05 19:48:33 +00:00
|
|
|
|
xmodmap -pk | grep -Ei "meta|alt"
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
A more convenient way of finding out which keys produce a Meta modifier
|
2015-08-26 21:05:43 +00:00
|
|
|
|
is to use the 'xkbprint' utility, if it's available on your system:
|
2001-06-24 13:16:33 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
xkbprint 0:0 /tmp/k.ps
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
This produces a PostScript file '/tmp/k.ps' with a picture of your
|
2004-08-21 11:31:45 +00:00
|
|
|
|
keyboard; printing that file on a PostScript printer will show what
|
|
|
|
|
keys can serve as Meta.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
The 'xkeycaps' also shows a visual representation of the current
|
2004-08-21 11:31:45 +00:00
|
|
|
|
keyboard settings. It also allows to modify them.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
People using systems based on the Linux kernel sometimes report that
|
2015-08-26 21:05:43 +00:00
|
|
|
|
startup takes 10 to 15 seconds longer than 'usual'.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
**** Networked Case.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +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
|
2004-08-21 11:31:45 +00:00
|
|
|
|
(replace HOSTNAME with your host name):
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
127.0.0.1 HOSTNAME
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
Also make sure that the '/etc/host.conf' files contains the following
|
2004-08-21 11:31:45 +00:00
|
|
|
|
lines:
|
2002-05-18 11:10:35 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
order hosts, bind
|
|
|
|
|
multi on
|
2002-10-25 05:58:04 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Any changes, permanent and temporary, to the host name should be
|
2015-08-26 21:05:43 +00:00
|
|
|
|
indicated in the '/etc/hosts' file, since it acts a limited local
|
2004-08-21 11:31:45 +00:00
|
|
|
|
database of addresses and names (e.g., some SLIP connections
|
|
|
|
|
dynamically allocate ip addresses).
|
2002-05-18 11:10:35 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
**** Non-Networked Case.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
simpler solution: create an empty '/etc/host.conf' file. The command
|
|
|
|
|
'touch /etc/host.conf' suffices to create the file. The '/etc/hosts'
|
2004-08-21 11:31:45 +00:00
|
|
|
|
file is not necessary with this approach.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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.
|
2015-08-26 21:05:43 +00:00
|
|
|
|
These versions of ncurses come with a 'linux' terminfo entry, where
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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.
|
2001-06-13 12:31:09 +00:00
|
|
|
|
|
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.
|
2001-06-13 12:31:09 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
To this end, run "infocmp linux > linux-term", edit the file
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'linux-term' to make both the "cnorm" and "cvvis" capabilities send
|
2004-08-21 11:31:45 +00:00
|
|
|
|
the sequence "\E[?25h\E[?17;0;64c", and then run "tic linux-term" to
|
|
|
|
|
produce a modified terminfo entry.
|
2001-06-13 12:31:09 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Alternatively, if you want a blinking underscore as your Emacs cursor,
|
2015-08-26 21:05:43 +00:00
|
|
|
|
set the 'visible-cursor' variable to nil in your ~/.emacs:
|
2015-04-07 17:42:28 +00:00
|
|
|
|
(setq visible-cursor nil)
|
|
|
|
|
|
|
|
|
|
Still other way is to change the "cvvis" capability to send the
|
|
|
|
|
"\E[?25h\E[?0c" command.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** FreeBSD
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** FreeBSD: Getting a Meta key on the console.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
$ kbdcontrol -d >emacs.kbd
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Edit emacs.kbd, and give the key you want to be the Meta key the
|
2015-08-26 21:05:43 +00:00
|
|
|
|
definition 'meta'. For instance, if your keyboard has a "Windows"
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
$ kbdcontrol -l emacs.kbd
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** HP-UX
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
christos@theory.tn.cornell.edu says:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
The problem is that in your .cshrc you have something that tries to
|
2015-08-26 21:05:43 +00:00
|
|
|
|
execute 'tty'. If you are not running the shell on a real tty then
|
2014-01-23 02:11:13 +00:00
|
|
|
|
tty will print "not a tty". Csh expects one word in some places,
|
2004-08-21 11:31:45 +00:00
|
|
|
|
but tty is giving it back 3.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
if (`tty` == "/dev/console")
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
should be changed to:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
if ("`tty`" == "/dev/console")
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
*** HP/UX: 'Pid xxx killed due to text modification or page I/O error'.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** AIX
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** AIX: Trouble using ptys.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
People often install the pty devices on AIX incorrectly.
|
2015-08-26 21:05:43 +00:00
|
|
|
|
Use 'smit pty' to reinstall them properly.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** AIX: If linking fails because libXbsd isn't found, check if you
|
2015-08-26 21:05:43 +00:00
|
|
|
|
are compiling with the system's 'cc' and CFLAGS containing '-O5'. If
|
2004-08-21 11:31:45 +00:00
|
|
|
|
so, you have hit a compiler bug. Please make sure to re-configure
|
2015-08-26 21:05:43 +00:00
|
|
|
|
Emacs so that it isn't compiled with '-O5'.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
This could happen if you use /bin/c89 as your compiler, instead of
|
2015-08-26 21:05:43 +00:00
|
|
|
|
the default 'cc'. /bin/c89 treats certain warnings, such as benign
|
2004-08-21 11:31:45 +00:00
|
|
|
|
redefinitions of macros, as errors, and fails the build. A solution
|
2015-08-26 21:05:43 +00:00
|
|
|
|
is to use the default compiler 'cc'.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
On AIX, many terminal type definitions are not installed by default.
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'unknown' is one of them. Install the "Special Generic Terminal
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Definitions" to make them defined.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Solaris
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2017-10-02 06:15:36 +00:00
|
|
|
|
*** On Solaris 10, Emacs crashes during the build process.
|
2020-08-06 00:36:50 +00:00
|
|
|
|
(This applies only with './configure --with-unexec=yes', which is rare.)
|
2017-10-02 06:15:36 +00:00
|
|
|
|
This was reported for Emacs 25.2 on i386-pc-solaris2.10 with Sun
|
|
|
|
|
Studio 12 (Sun C 5.9) and with Oracle Developer Studio 12.6 (Sun C
|
|
|
|
|
5.15), and intermittently for sparc-sun-solaris2.10 with Oracle
|
|
|
|
|
Developer Studio 12.5 (Sun C 5.14). Disabling compiler optimization
|
|
|
|
|
seems to fix the bug, as does upgrading the Solaris 10 operating
|
|
|
|
|
system to Update 11. The cause of the bug is unknown: it may be that
|
|
|
|
|
Emacs's archaic memory-allocation scheme is not compatible with
|
|
|
|
|
slightly-older versions of Solaris and/or Oracle Studio, or it may be
|
|
|
|
|
something else. Since the cause is not known, possibly the bug is
|
|
|
|
|
still present in newer versions of Emacs, Oracle Studio, and/or
|
|
|
|
|
Solaris. See Bug#26638.
|
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
* Runtime problems specific to MS-Windows
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2014-02-21 09:02:19 +00:00
|
|
|
|
** Emacs on Windows 9X requires UNICOWS.DLL
|
|
|
|
|
|
|
|
|
|
If that DLL is not available, Emacs will display an error dialog
|
|
|
|
|
stating its absence, and refuse to run.
|
|
|
|
|
|
|
|
|
|
This is because Emacs 24.4 and later uses functions whose non-stub
|
|
|
|
|
implementation is only available in UNICOWS.DLL, which implements the
|
|
|
|
|
Microsoft Layer for Unicode on Windows 9X, or "MSLU". This article on
|
|
|
|
|
MSDN:
|
|
|
|
|
|
2021-09-27 10:40:04 +00:00
|
|
|
|
https://web.archive.org/web/20151224032644/https://msdn.microsoft.com/en-us/goglobal/bb688166.aspx
|
2014-02-21 09:02:19 +00:00
|
|
|
|
|
|
|
|
|
includes a short description of MSLU and a link where it can be
|
|
|
|
|
downloaded.
|
|
|
|
|
|
2014-07-12 09:08:41 +00:00
|
|
|
|
** Emacs refuses to start on Windows 9X because ctime64 function is missing
|
|
|
|
|
|
|
|
|
|
This is a sign that Emacs was compiled with MinGW runtime version
|
|
|
|
|
4.0.x or later. These versions of runtime call in their startup code
|
|
|
|
|
the ctime64 function, which does not exist in MSVCRT.DLL, the C
|
|
|
|
|
runtime shared library, distributed with Windows 9X.
|
|
|
|
|
|
|
|
|
|
A workaround is to build Emacs with MinGW runtime 3.x (the latest
|
|
|
|
|
version is 3.20).
|
|
|
|
|
|
2016-01-16 09:23:42 +00:00
|
|
|
|
** addpm fails to run on Windows NT4, complaining about Shell32.dll
|
|
|
|
|
|
|
|
|
|
This is likely to happen because Shell32.dll shipped with NT4 lacks
|
|
|
|
|
the updates required by Emacs. Installing Internet Explorer 4 solves
|
|
|
|
|
the problem. Note that it is NOT enough to install IE6, because doing
|
|
|
|
|
so will not install the Shell32.dll update.
|
|
|
|
|
|
2014-02-21 09:02:19 +00:00
|
|
|
|
** A few seconds delay is seen at startup and for many file operations
|
|
|
|
|
|
|
|
|
|
This happens when the Net Logon service is enabled. During Emacs
|
|
|
|
|
startup, this service issues many DNS requests looking up for the
|
|
|
|
|
Windows Domain Controller. When Emacs accesses files on networked
|
|
|
|
|
drives, it automatically logs on the user into those drives, which
|
|
|
|
|
again causes delays when Net Logon is running.
|
|
|
|
|
|
|
|
|
|
The solution seems to be to disable Net Logon with this command typed
|
|
|
|
|
at the Windows shell prompt:
|
|
|
|
|
|
|
|
|
|
net stop netlogon
|
|
|
|
|
|
|
|
|
|
To start the service again, type "net start netlogon". (You can also
|
|
|
|
|
stop and start the service from the Computer Management application,
|
|
|
|
|
accessible by right-clicking "My Computer" or "Computer", selecting
|
|
|
|
|
"Manage", then clicking on "Services".)
|
|
|
|
|
|
2014-02-21 16:47:04 +00:00
|
|
|
|
** Emacs crashes when exiting the Emacs session
|
|
|
|
|
|
|
|
|
|
This was reported to happen when some optional DLLs, such as those
|
2014-11-26 15:54:24 +00:00
|
|
|
|
used for displaying images or the GnuTLS library or zlib compression
|
|
|
|
|
library, which are loaded on-demand, have a runtime dependency on the
|
|
|
|
|
libgcc DLL, libgcc_s_dw2-1.dll. The reason seems to be a bug in
|
|
|
|
|
libgcc which rears its ugly head whenever the libgcc DLL is loaded
|
|
|
|
|
after Emacs has started.
|
2014-02-21 16:47:04 +00:00
|
|
|
|
|
|
|
|
|
One solution for this problem is to find an alternative build of the
|
|
|
|
|
same optional library that does not depend on the libgcc DLL.
|
|
|
|
|
|
|
|
|
|
Another possibility is to rebuild Emacs with the -shared-libgcc
|
|
|
|
|
switch, which will force Emacs to load libgcc_s_dw2-1.dll on startup,
|
|
|
|
|
ahead of any optional DLLs loaded on-demand later in the session.
|
|
|
|
|
|
2014-07-12 09:25:29 +00:00
|
|
|
|
** File selection dialog opens in incorrect directories
|
|
|
|
|
|
|
|
|
|
Invoking the file selection dialog on Windows 7 or later shows a
|
2015-08-26 21:05:43 +00:00
|
|
|
|
directory that is different from what was passed to 'read-file-name'
|
|
|
|
|
or 'x-file-dialog' via their arguments.
|
2014-07-12 09:25:29 +00:00
|
|
|
|
|
|
|
|
|
This is due to a deliberate change in behavior of the file selection
|
|
|
|
|
dialogs introduced in Windows 7. It is explicitly described in the
|
|
|
|
|
MSDN documentation of the GetOpenFileName API used by Emacs to pop up
|
|
|
|
|
the file selection dialog. For the details, see
|
|
|
|
|
|
2021-09-27 10:40:04 +00:00
|
|
|
|
https://msdn.microsoft.com/en-us/library/windows/desktop/ms646839%28v=vs.85%29.aspx
|
2014-07-12 09:25:29 +00:00
|
|
|
|
|
|
|
|
|
The dialog shows the last directory in which the user selected a file
|
|
|
|
|
in a previous invocation of the dialog with the same initial
|
|
|
|
|
directory.
|
|
|
|
|
|
|
|
|
|
You can reset this "memory" of that directory by invoking the file
|
|
|
|
|
selection dialog with a different initial directory.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
"Windows" key is pressed.
|
2009-01-24 20:39:10 +00:00
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2015-09-26 07:25:58 +00:00
|
|
|
|
** Pasting from Windows clipboard into Emacs doesn't work.
|
|
|
|
|
|
|
|
|
|
This was reported to be the result of an anti-virus software blocking
|
|
|
|
|
the clipboard-related operations when a Web browser is open, for
|
|
|
|
|
security reasons. The solution is to close the Web browser while
|
|
|
|
|
working in Emacs, or to add emacs.exe to the list of applications that
|
|
|
|
|
are allowed to use the clipboard when the Web browser is open.
|
|
|
|
|
|
2015-10-30 10:28:00 +00:00
|
|
|
|
** "Pinning" Emacs to the taskbar doesn't work on Windows 10
|
|
|
|
|
|
|
|
|
|
"Doesn't work" here means that if you invoke Emacs by clicking on the
|
|
|
|
|
pinned icon, a separate button appears on the taskbar, instead of the
|
|
|
|
|
expected effect of the icon you clicked on being converted to that
|
|
|
|
|
button.
|
|
|
|
|
|
2015-11-20 09:08:40 +00:00
|
|
|
|
This is due to a bug in early versions of Windows 10, reportedly fixed
|
|
|
|
|
in build 1511 of Windows 10 (a.k.a. "Windows 10 SP1"). If you cannot
|
|
|
|
|
upgrade, read the work-around described below.
|
|
|
|
|
|
2015-10-30 10:28:00 +00:00
|
|
|
|
First, be sure to edit the Properties of the pinned icon to invoke
|
|
|
|
|
runemacs.exe, not emacs.exe. (The latter will cause an extra cmd
|
|
|
|
|
window to appear when you invoke Emacs from the pinned icon.)
|
|
|
|
|
|
|
|
|
|
But the real cause of the problem is the fact that the pinned icon
|
|
|
|
|
(which is really a shortcut in a special directory) lacks a unique
|
|
|
|
|
application-defined Application User Model ID (AppUserModelID) that
|
|
|
|
|
identifies the current process to the taskbar. This identifier allows
|
|
|
|
|
an application to group its associated processes and windows under a
|
|
|
|
|
single taskbar button. Emacs on Windows specifies a unique
|
|
|
|
|
AppUserModelID when it starts, but Windows 10, unlike previous
|
|
|
|
|
versions of MS-Windows, does not propagate that ID to the pinned icon.
|
|
|
|
|
|
|
|
|
|
To work around this, use some utility, such as 'win7appid', to set the
|
|
|
|
|
AppUserModelID of the pinned icon to the string "Gnu.Emacs". The
|
|
|
|
|
shortcut files corresponding to icons you pinned are stored by Windows
|
|
|
|
|
in the following subdirectory of your user's directory (by default
|
|
|
|
|
C:\Users\<UserName>\):
|
|
|
|
|
|
|
|
|
|
AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar
|
|
|
|
|
|
|
|
|
|
Look for the file 'emacs.lnk' there.
|
|
|
|
|
|
2006-07-14 15:03:52 +00:00
|
|
|
|
** Windows 95 and networking.
|
|
|
|
|
|
2014-02-21 09:02:19 +00:00
|
|
|
|
To support server sockets, Emacs loads ws2_32.dll. If this file is
|
|
|
|
|
missing, all Emacs networking features are disabled.
|
2006-07-14 15:03:52 +00:00
|
|
|
|
|
|
|
|
|
Old versions of Windows 95 may not have the required DLL. To use
|
2014-01-07 02:33:46 +00:00
|
|
|
|
Emacs's networking features on Windows 95, you must install the
|
2006-07-14 15:03:52 +00:00
|
|
|
|
"Windows Socket 2" update available from MicroSoft's support Web.
|
|
|
|
|
|
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
|
|
|
|
|
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.
|
2003-02-04 14:56:31 +00:00
|
|
|
|
|
2008-08-16 03:41:26 +00:00
|
|
|
|
** Emacs crashes when opening a file with a UNC path and rails-mode is loaded.
|
|
|
|
|
|
2014-01-23 02:11:13 +00:00
|
|
|
|
Loading rails-mode seems to interfere with UNC path handling. This has been
|
2008-08-16 03:41:26 +00:00
|
|
|
|
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.
|
|
|
|
|
|
2014-02-21 09:02:19 +00:00
|
|
|
|
** M-x term does not work on MS-Windows.
|
2005-10-25 21:28:54 +00:00
|
|
|
|
|
2014-02-21 09:02:19 +00:00
|
|
|
|
TTY emulation on Windows is undocumented, and programs such as stty
|
2015-04-07 17:42:28 +00:00
|
|
|
|
which are used on POSIX platforms to control tty emulation do not
|
2014-02-21 09:02:19 +00:00
|
|
|
|
exist for native windows terminals.
|
2008-03-17 23:34:55 +00:00
|
|
|
|
|
2014-02-21 09:02:19 +00:00
|
|
|
|
** Using create-fontset-from-ascii-font or the --font startup parameter
|
2005-10-25 21:28:54 +00:00
|
|
|
|
with a Chinese, Japanese or Korean font leads to display problems.
|
2014-01-23 02:11:13 +00:00
|
|
|
|
Use a Latin-only font as your default font. If you want control over
|
2005-10-25 21:28:54 +00:00
|
|
|
|
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
|
|
|
|
|
2014-02-21 09:02:19 +00:00
|
|
|
|
** Frames are not refreshed while dialogs or menus are displayed
|
|
|
|
|
|
|
|
|
|
This means no redisplay while the File or Font dialog or a pop-up menu
|
|
|
|
|
is displayed. This also means tooltips with help text for pop-up
|
2015-04-07 17:42:28 +00:00
|
|
|
|
menus are not displayed at all (except in a TTY session, where the help
|
2014-02-21 09:02:19 +00:00
|
|
|
|
text is shown in the echo area). This is because message handling
|
|
|
|
|
under Windows is synchronous, so we cannot handle repaint (or any
|
|
|
|
|
other) messages while waiting for a system function, which popped up
|
|
|
|
|
the menu/dialog, to return the result of the dialog or pop-up menu
|
|
|
|
|
interaction.
|
|
|
|
|
|
|
|
|
|
** Help text in tooltips does not work on old Windows versions
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2014-02-21 09:02:19 +00:00
|
|
|
|
** Display problems with ClearType method of smoothing
|
|
|
|
|
|
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
|
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.
|
2007-04-09 08:42:03 +00:00
|
|
|
|
|
2015-04-14 16:34:05 +00:00
|
|
|
|
** Cursor is displayed as a thin vertical bar and cannot be changed
|
|
|
|
|
|
|
|
|
|
This is known to happen if the Windows Magnifier is turned on before
|
|
|
|
|
the Emacs session starts. The Magnifier affects the cursor shape and
|
|
|
|
|
prevents any changes to it by setting the 'cursor-type' variable or
|
|
|
|
|
frame parameter.
|
|
|
|
|
|
|
|
|
|
The solution is to log off and on again, and then start the Emacs
|
|
|
|
|
session only after turning the Magnifier off.
|
|
|
|
|
|
|
|
|
|
To turn the Windows Magnifier off, click "Start->All Programs", or
|
|
|
|
|
"All Apps", depending on your Windows version, then select
|
|
|
|
|
"Accessibility" and click "Magnifier". In the Magnifier Settings
|
|
|
|
|
dialog that opens, click "Exit".
|
|
|
|
|
|
2014-02-21 09:02:19 +00:00
|
|
|
|
** Problems with mouse-tracking and focus management
|
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2014-02-21 09:02:19 +00:00
|
|
|
|
** Problems with Windows input methods
|
|
|
|
|
|
|
|
|
|
Some of the Windows input methods cause the keyboard to send
|
|
|
|
|
characters encoded in the appropriate coding system (e.g., ISO 8859-1
|
|
|
|
|
for Latin-1 characters, ISO 8859-8 for Hebrew characters, etc.). To
|
|
|
|
|
make these input methods work with Emacs on Windows 9X, you might need
|
|
|
|
|
to 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:
|
2007-04-08 08:59:32 +00:00
|
|
|
|
|
|
|
|
|
C-x RET k hebrew-iso-8bit RET
|
|
|
|
|
|
2014-02-21 09:02:19 +00:00
|
|
|
|
In addition, to use these Windows input methods, you might need to 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
|
|
|
|
|
2007-03-31 10:01:51 +00:00
|
|
|
|
To bind keys that produce non-ASCII characters with modifiers, you
|
2014-01-23 02:11:13 +00:00
|
|
|
|
must specify raw byte codes. For instance, if you want to bind
|
2015-08-26 21:05:43 +00:00
|
|
|
|
META-a-grave to a command, you need to specify this in your '~/.emacs':
|
2007-03-31 10:01:51 +00:00
|
|
|
|
|
|
|
|
|
(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
|
|
|
|
|
2014-02-21 09:02:19 +00:00
|
|
|
|
** Problems with the %b format specifier for format-time-string
|
|
|
|
|
|
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
|
2014-01-23 02:11:13 +00:00
|
|
|
|
of Windows. This is caused by a deficiency in the underlying system
|
2004-08-21 11:31:45 +00:00
|
|
|
|
library function.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2016-04-12 15:47:15 +00:00
|
|
|
|
** Non-US time zones.
|
2014-02-21 09:02:19 +00:00
|
|
|
|
|
2016-04-12 15:47:15 +00:00
|
|
|
|
Many non-US time zones are implemented incorrectly. This is due to
|
|
|
|
|
over-simplistic handling of daylight savings switchovers by the
|
|
|
|
|
Windows libraries.
|
2007-10-17 22:27:24 +00:00
|
|
|
|
|
2014-07-12 09:08:41 +00:00
|
|
|
|
** Files larger than 4GB report wrong size in a 32-bit Windows build
|
2014-02-21 09:02:19 +00:00
|
|
|
|
|
2007-04-27 13:37:31 +00:00
|
|
|
|
Files larger than 4GB cause overflow in the size (represented as a
|
2015-08-26 21:05:43 +00:00
|
|
|
|
32-bit integer) reported by 'file-attributes'. This affects Dired as
|
|
|
|
|
well, since the Windows port uses a Lisp emulation of 'ls', which relies
|
|
|
|
|
on 'file-attributes'.
|
2007-04-27 13:37:31 +00:00
|
|
|
|
|
2014-02-21 09:02:19 +00:00
|
|
|
|
** Playing sound doesn't support the :data method
|
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
Sound playing is not supported with the ':data DATA' key-value pair.
|
|
|
|
|
You _must_ use the ':file FILE' method.
|
2007-06-16 12:50:37 +00:00
|
|
|
|
|
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
|
|
|
|
|
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,
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
If the FTP client is the Cygwin port of GNU 'ftp', this appears to be
|
2004-09-04 12:25:43 +00:00
|
|
|
|
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
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
Windows FTP client, usually found in the 'C:\WINDOWS' or 'C:\WINNT'
|
2004-09-04 12:25:43 +00:00
|
|
|
|
directory. To force ange-ftp use the stock Windows client, set the
|
2015-08-26 21:05:43 +00:00
|
|
|
|
variable 'ange-ftp-ftp-program-name' to the absolute file name of the
|
2004-09-04 12:25:43 +00:00
|
|
|
|
client's executable. For example:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
If you want to stick with the Cygwin FTP client, you can work around
|
2015-08-26 21:05:43 +00:00
|
|
|
|
this problem by putting this in your '.emacs' file:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
2014-03-22 22:56:29 +00:00
|
|
|
|
printer drivers. A workaround on MS-Windows is to use Windows's basic
|
2004-08-21 11:31:45 +00:00
|
|
|
|
built in editor to print (this is possibly the only useful purpose it
|
|
|
|
|
has):
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
The solution is to switch the antivirus software to a less aggressive
|
2015-08-26 21:05:43 +00:00
|
|
|
|
mode (e.g., disable the "auto-protect" feature), or even uninstall
|
2004-08-21 11:31:45 +00:00
|
|
|
|
or disable it entirely.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2014-01-23 02:11:13 +00:00
|
|
|
|
This is usually a problem with the mouse driver. Because most Windows
|
2004-08-21 11:31:45 +00:00
|
|
|
|
programs do not do anything useful with the middle mouse button, many
|
|
|
|
|
mouse drivers allow you to define the wheel press to do something
|
2014-01-23 02:11:13 +00:00
|
|
|
|
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
|
2004-08-21 11:31:45 +00:00
|
|
|
|
generic mouse driver might help.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2017-05-19 12:37:58 +00:00
|
|
|
|
One particular situation where this happens is when you have
|
|
|
|
|
"Microsoft Intellipoint" installed, which runs the program
|
|
|
|
|
ipoint.exe. The fix is reportedly to uninstall this software.
|
|
|
|
|
|
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
|
|
|
|
|
2014-01-23 02:11:13 +00:00
|
|
|
|
This is another common problem with mouse drivers. Instead of
|
2004-08-21 11:31:45 +00:00
|
|
|
|
generating scroll events, some mouse drivers try to fake scroll bar
|
2014-01-23 02:11:13 +00:00
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
AltGr has been pressed. The variable 'w32-recognize-altgr' can be set
|
2004-08-21 11:31:45 +00:00
|
|
|
|
to nil to tell Emacs that AltGr is really Ctrl and Alt.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2014-01-07 02:33:46 +00:00
|
|
|
|
** Under some X-servers running on MS-Windows, Emacs's display is incorrect.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
There are reports that you can solve the problem with Exceed by
|
2015-08-26 21:05:43 +00:00
|
|
|
|
running 'Xconfig' from within NT, choosing "X selection", then
|
2004-08-21 11:31:45 +00:00
|
|
|
|
un-checking the boxes "auto-copy X selection" and "auto-paste to X
|
|
|
|
|
selection".
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2014-03-22 22:56:29 +00:00
|
|
|
|
If this does not work, please inform bug-gnu-emacs@gnu.org. Then
|
2004-08-21 11:31:45 +00:00
|
|
|
|
please call support for your X-server and see if you can get a fix.
|
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
|
|
|
|
|
2016-11-14 22:26:12 +00:00
|
|
|
|
|
2018-10-24 11:15:16 +00:00
|
|
|
|
* Runtime problems specific to macOS
|
|
|
|
|
|
2021-11-03 18:23:58 +00:00
|
|
|
|
** Error message when opening Emacs on macOS
|
2021-11-02 18:45:18 +00:00
|
|
|
|
|
2021-11-03 18:23:58 +00:00
|
|
|
|
When opening Emacs, you may see an error message saying something like
|
|
|
|
|
this:
|
2021-11-02 18:45:18 +00:00
|
|
|
|
|
|
|
|
|
"Emacs" can't be opened because Apple cannot check it for malicious
|
|
|
|
|
software. This software needs to be updated. Contact the developer
|
|
|
|
|
for more information.
|
|
|
|
|
|
2021-11-03 18:23:58 +00:00
|
|
|
|
The reason is that Apple incorrectly catalogs Emacs as potentially
|
|
|
|
|
malicious software and thus shows this error message.
|
|
|
|
|
|
2021-11-02 18:45:18 +00:00
|
|
|
|
To avoid this alert, open Finder, go to Applications, control-click
|
|
|
|
|
the Emacs app icon, and then choose Open. This adds a security
|
|
|
|
|
exception for Emacs and from now on you should be able to open it by
|
|
|
|
|
double-clicking on its icon, like any other app.
|
|
|
|
|
|
2018-10-24 11:15:16 +00:00
|
|
|
|
** macOS doesn't come with libxpm, so only XPM3 is supported.
|
|
|
|
|
|
|
|
|
|
Libxpm is available for macOS as part of the XQuartz project.
|
|
|
|
|
|
2021-08-21 13:03:21 +00:00
|
|
|
|
** Synthetic fonts on macOS
|
|
|
|
|
|
|
|
|
|
Synthetic bold looks thinner if the background is darker than the
|
|
|
|
|
foreground and font smoothing is turned on. In such cases, you can
|
|
|
|
|
turn off synthetic bold for particular fonts and use overstriking
|
|
|
|
|
instead by customizing the variable 'face-ignored-fonts'. For
|
|
|
|
|
instance, if the problem is with the Monaco font, you could put
|
|
|
|
|
something like the following in your init file:
|
|
|
|
|
|
|
|
|
|
(push "\\`-[^-]*-monaco-bold-" face-ignored-fonts)
|
2018-10-24 11:15:16 +00:00
|
|
|
|
|
2021-09-18 21:17:49 +00:00
|
|
|
|
** Native Compilation on macOS
|
|
|
|
|
|
|
|
|
|
Native complitation requires the libgccjit library to be installed and
|
|
|
|
|
its path available to Emacs. Errors such as:
|
|
|
|
|
|
|
|
|
|
libgccjit.so: error: error invoking gcc driver
|
|
|
|
|
Error: Internal native compiler error failed to compile
|
|
|
|
|
|
|
|
|
|
indicate Emacs can't find the library in running time. One can set
|
2021-11-12 12:50:55 +00:00
|
|
|
|
the "LIBRARY_PATH" environment variable in the early initialization
|
2021-09-18 21:17:49 +00:00
|
|
|
|
file; for example:
|
|
|
|
|
|
|
|
|
|
(setenv "LIBRARY_PATH"
|
|
|
|
|
(string-join
|
|
|
|
|
'("/usr/local/opt/gcc/lib/gcc/11"
|
|
|
|
|
"/usr/local/opt/libgccjit/lib/gcc/11"
|
|
|
|
|
"/usr/local/opt/gcc/lib/gcc/11/gcc/x86_64-apple-darwin20/11.2.0") ":"))
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
* Build-time problems
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Configuration
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
*** 'configure' warns "accepted by the compiler, rejected by the preprocessor".
|
2007-04-04 02:58:38 +00:00
|
|
|
|
|
|
|
|
|
This indicates a mismatch between the C compiler and preprocessor that
|
|
|
|
|
configure is using. For example, on Solaris 10 trying to use
|
2020-08-06 00:36:50 +00:00
|
|
|
|
CC=/opt/developerstudio12.6/bin/cc (the Oracle Developer Studio
|
|
|
|
|
compiler) together with CPP=/usr/lib/cpp can result in errors of
|
|
|
|
|
this form.
|
2007-04-04 02:58:38 +00:00
|
|
|
|
|
|
|
|
|
The solution is to tell configure to use the correct C preprocessor
|
2020-08-06 00:36:50 +00:00
|
|
|
|
for your C compiler (CPP="/opt/developerstudio12.6/bin/cc -E" in the
|
|
|
|
|
above example).
|
2007-04-04 02:58:38 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Compilation
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2021-11-06 12:23:02 +00:00
|
|
|
|
*** Link-time optimization with clang doesn't work on Fedora 20.
|
|
|
|
|
|
|
|
|
|
As of May 2014, Fedora 20 has broken LLVMgold.so plugin support in clang
|
|
|
|
|
(tested with clang-3.4-6.fc20) - 'clang --print-file-name=LLVMgold.so'
|
|
|
|
|
prints 'LLVMgold.so' instead of full path to plugin shared library, and
|
|
|
|
|
'clang -flto' is unable to find the plugin with the following error:
|
|
|
|
|
|
|
|
|
|
/bin/ld: error: /usr/bin/../lib/LLVMgold.so: could not load plugin library:
|
|
|
|
|
/usr/bin/../lib/LLVMgold.so: cannot open shared object file: No such file
|
|
|
|
|
or directory
|
|
|
|
|
|
|
|
|
|
The only way to avoid this is to build your own clang from source code
|
|
|
|
|
repositories, as described at http://clang.llvm.org/get_started.html.
|
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
*** Building Emacs over NFS fails with "Text file busy".
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
This was reported to happen when building Emacs on a GNU/Linux system
|
2007-04-12 04:16:47 +00:00
|
|
|
|
(Red Hat Linux 6.2) using a build directory automounted from Solaris
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
left "busy" for several seconds after Emacs has finished dumping
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'mount' command, or by adding ",rsize=1024,wsize=1024" to the mount
|
2004-08-21 11:31:45 +00:00
|
|
|
|
options in the appropriate system configuration file, such as
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'/etc/auto.home'.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Similar problems can happen if your machine NFS-mounts a directory
|
2015-08-26 21:05:43 +00:00
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
The solution is to remove this line from '/etc/fstab'.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
2014-01-23 02:11:13 +00:00
|
|
|
|
files are installed. Then use:
|
2007-01-13 02:25:58 +00:00
|
|
|
|
|
2014-03-22 22:56:29 +00:00
|
|
|
|
env CC="gcc -m32" ./configure --build=i386-linux-gnu --x-libraries=/usr/lib
|
2007-01-13 02:25:58 +00:00
|
|
|
|
|
|
|
|
|
(using the location of the 32-bit X libraries on your system).
|
|
|
|
|
|
2016-06-04 15:45:46 +00:00
|
|
|
|
*** Building on FreeBSD 11 fails at link time due to unresolved symbol
|
|
|
|
|
|
|
|
|
|
The symbol is sendmmsg@FBSD_1.4. This is due to a faulty libgio
|
|
|
|
|
library on these systems. The solution is to reconfigure Emacs while
|
|
|
|
|
disabling all the features that require libgio: rsvg, dbus, gconf, and
|
|
|
|
|
imagemagick.
|
|
|
|
|
|
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
|
|
|
|
|
|
2017-11-26 06:45:41 +00:00
|
|
|
|
https://lists.gnu.org/r/emacs-devel/2010-07/msg01266.html
|
2010-07-27 19:50:01 +00:00
|
|
|
|
|
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
|
|
|
|
|
|
2015-04-07 17:42:28 +00:00
|
|
|
|
This happens because GCC finds an incompatible regex.h header
|
2010-03-27 12:52:55 +00:00
|
|
|
|
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.
|
|
|
|
|
|
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
|
|
|
|
|
2008-02-04 11:26:17 +00:00
|
|
|
|
Emacs may not build using some Cygwin builds of GCC, such as Cygwin
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
configure --with-gcc --cflags -mwin32 --cflags -D__MSVCRT__
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Some versions of mingw32 make on some versions of Windows do not seem
|
2014-01-23 02:11:13 +00:00
|
|
|
|
to detect the shell correctly. Try "make SHELL=cmd.exe", or if that
|
2004-08-21 11:31:45 +00:00
|
|
|
|
fails, try running make from Cygwin bash instead.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
*** Building 'ctags' for MS-Windows with the MinGW port of GCC fails.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
This might happen due to a bug in the MinGW header assert.h, which
|
2015-08-26 21:05:43 +00:00
|
|
|
|
defines the 'assert' macro with a trailing semi-colon. The following
|
2004-08-21 11:31:45 +00:00
|
|
|
|
patch to assert.h should solve this:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
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
|
2007-03-03 11:03:50 +00:00
|
|
|
|
some functions that Microsoft have deemed non-threadsafe. The
|
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
|
|
|
|
|
2009-02-04 09:13:18 +00:00
|
|
|
|
We recommend the use of the MinGW port of GCC for compiling Emacs, as
|
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
|
|
|
|
|
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
|
2014-01-23 02:11:13 +00:00
|
|
|
|
not recognized by older versions of the resource compiler. There are
|
2009-02-04 09:13:18 +00:00
|
|
|
|
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.
|
|
|
|
|
|
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.
|
2017-11-26 06:45:41 +00:00
|
|
|
|
See https://lists.gnu.org/r/emacs-devel/2010-07/msg00995.html
|
2010-07-20 18:32:42 +00:00
|
|
|
|
|
|
|
|
|
The fix is to use forward slashes in all paths passed to the compiler.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Linking
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2008-08-26 20:02:17 +00:00
|
|
|
|
make CC=gcc
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
*** 'tparam' reported as a multiply-defined symbol when linking with ncurses.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2008-09-05 04:01:53 +00:00
|
|
|
|
** Bootstrapping
|
|
|
|
|
|
|
|
|
|
Bootstrapping (compiling the .el files) is normally only necessary
|
2010-05-28 03:23:08 +00:00
|
|
|
|
with development builds, since the .elc files are pre-compiled in releases.
|
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:
|
2015-08-26 21:05:43 +00:00
|
|
|
|
"No rule to make target '/path/to/some/lisp.elc'".
|
2008-09-05 04:01:53 +00:00
|
|
|
|
The causes of this problem are not understood. Using GNU make 3.81 compiled
|
2014-01-07 02:33:46 +00:00
|
|
|
|
from source, rather than the Ubuntu version, worked.
|
2017-09-13 22:52:52 +00:00
|
|
|
|
See <URL:https://debbugs.gnu.org/327>, <URL:https://debbugs.gnu.org/821>.
|
2008-09-05 04:01:53 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Dumping
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
*** Segfault during 'make'
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
If Emacs segfaults when 'make' executes one of these commands:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
LC_ALL=C ./temacs -batch -l loadup bootstrap
|
|
|
|
|
LC_ALL=C ./temacs -batch -l loadup dump
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
the problem may be due to inadequate workarounds for address space
|
|
|
|
|
layout randomization (ASLR), an operating system feature that
|
|
|
|
|
randomizes the virtual address space of a process. ASLR is commonly
|
|
|
|
|
enabled in Linux and NetBSD kernels, and is intended to deter exploits
|
|
|
|
|
of pointer-related bugs in applications. If ASLR is enabled, the
|
|
|
|
|
command:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
cat /proc/sys/kernel/randomize_va_space # GNU/Linux
|
|
|
|
|
sysctl security.pax.aslr.global # NetBSD
|
2004-09-25 20:39:13 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
outputs a nonzero value.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
These segfaults should not occur on most modern systems, because the
|
|
|
|
|
Emacs build procedure uses the command 'setfattr' or 'paxctl' to mark
|
|
|
|
|
the Emacs executable as requiring non-randomized address space, and
|
|
|
|
|
Emacs uses the 'personality' system call to disable address space
|
|
|
|
|
randomization when dumping. However, older kernels may not support
|
|
|
|
|
'setfattr', 'paxctl', or 'personality', and newer Linux kernels have a
|
|
|
|
|
secure computing mode (seccomp) that can be configured to disable the
|
|
|
|
|
'personality' call.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
It may be possible to work around the 'personality' problem in a newer
|
|
|
|
|
Linux kernel by configuring seccomp to allow the 'personality' call.
|
|
|
|
|
For example, if you are building Emacs under Docker, you can run the
|
|
|
|
|
Docker container with a security profile that allows 'personality' by
|
|
|
|
|
using Docker's --security-opt option with an appropriate profile; see
|
|
|
|
|
<https://docs.docker.com/engine/security/seccomp/>.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
To work around the ASLR problem in either an older or a newer kernel,
|
|
|
|
|
you can temporarily disable the feature while building Emacs. On
|
|
|
|
|
GNU/Linux you can do so using the following command (as root).
|
2004-09-25 20:39:13 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
echo 0 > /proc/sys/kernel/randomize_va_space
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
You can re-enable the feature when you are done, by echoing the
|
|
|
|
|
original value back to the file. NetBSD uses a different command,
|
|
|
|
|
e.g., 'sysctl -w security.pax.aslr.global=0'.
|
2006-07-14 15:03:52 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
Alternatively, you can try using the 'setarch' command when building
|
|
|
|
|
temacs like this, where -R disables address space randomization:
|
2005-06-28 18:52:26 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
setarch $(uname -m) -R make
|
2005-06-28 18:52:26 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
ASLR is not the only problem that can break Emacs dumping. Another
|
|
|
|
|
issue is that in Red Hat Linux kernels, Exec-shield is enabled by
|
|
|
|
|
default, and this creates a different memory layout. Emacs should
|
|
|
|
|
handle this at build time, but if this fails the following
|
|
|
|
|
instructions may be useful. Exec-shield is enabled on your system if
|
2005-06-28 18:52:26 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
cat /proc/sys/kernel/exec-shield
|
|
|
|
|
|
|
|
|
|
prints a nonzero value. You can temporarily disable it as follows:
|
2005-06-28 18:52:26 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
echo 0 > /proc/sys/kernel/exec-shield
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2016-05-18 08:05:00 +00:00
|
|
|
|
As with randomize_va_space, you can re-enable Exec-shield when you are
|
|
|
|
|
done, by echoing the original value back to the file.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** temacs prints "Pure Lisp storage exhausted".
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2014-03-22 22:56:29 +00:00
|
|
|
|
This means that the Lisp code loaded from the .elc and .el files during
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'temacs --batch --load loadup 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;
|
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.
|
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
|
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
|
|
|
|
|
2007-05-17 07:58:16 +00:00
|
|
|
|
*** OpenBSD 4.0 macppc: Segfault during dumping.
|
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
The build aborts with signal 11 when the command './temacs --batch
|
2007-05-18 07:43:29 +00:00
|
|
|
|
--load loadup bootstrap' tries to load files.el. A workaround seems
|
2007-05-17 08:02:52 +00:00
|
|
|
|
to be to reduce the level of compiler optimization used during the
|
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).
|
2007-05-17 07:58:16 +00:00
|
|
|
|
|
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.
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** First execution
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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.
|
2015-08-26 21:05:43 +00:00
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
emacs: ASCII text, with no line terminators
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2012-05-31 05:08:37 +00:00
|
|
|
|
On a system where getpagesize is not a system call, it is defined
|
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
|
2015-04-07 17:42:28 +00:00
|
|
|
|
value in the man page for a.out(5).
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2018-09-12 14:53:43 +00:00
|
|
|
|
* 'make check' failures
|
|
|
|
|
|
|
|
|
|
** emacs-module-tests fail on Ubuntu 16.04
|
|
|
|
|
|
|
|
|
|
This is due to a bug in GCC that was fixed in 2015; see
|
|
|
|
|
<https://lists.gnu.org/r/emacs-devel/2018-09/msg00548.html>.
|
|
|
|
|
You can work around the problem by using a later version of GCC or of
|
|
|
|
|
Ubuntu, or by configuring without modules.
|
|
|
|
|
|
2014-01-23 02:11:13 +00:00
|
|
|
|
* Problems on legacy systems
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2020-08-06 00:36:50 +00:00
|
|
|
|
** Solaris
|
|
|
|
|
|
|
|
|
|
*** Problem with remote X server on Suns.
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
*** Solaris 2.6: Emacs crashes with SIGBUS or SIGSEGV on Solaris after you delete a frame.
|
|
|
|
|
|
|
|
|
|
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:
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
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:
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
*** Solaris 7 or 8: Emacs reports a BadAtom error (from X)
|
|
|
|
|
|
|
|
|
|
This happens when Emacs was built on some other version of Solaris.
|
|
|
|
|
Rebuild it on Solaris 8.
|
|
|
|
|
|
|
|
|
|
*** When using M-x dbx with the SparcWorks debugger, the 'up' and 'down'
|
|
|
|
|
commands do not move the arrow in Emacs.
|
|
|
|
|
|
|
|
|
|
You can fix this by adding the following line to '~/.dbxinit':
|
|
|
|
|
|
|
|
|
|
dbxenv output_short_file_name off
|
|
|
|
|
|
|
|
|
|
*** On Solaris, CTRL-t is ignored by Emacs when you use
|
|
|
|
|
the fr.ISO-8859-15 locale (and maybe other related locales).
|
|
|
|
|
|
|
|
|
|
You can fix this by editing the file:
|
|
|
|
|
|
|
|
|
|
/usr/openwin/lib/locale/iso8859-15/Compose
|
|
|
|
|
|
|
|
|
|
Near the bottom there is a line that reads:
|
|
|
|
|
|
|
|
|
|
Ctrl<t> <quotedbl> <Y> : "\276" threequarters
|
|
|
|
|
|
|
|
|
|
while it should read:
|
|
|
|
|
|
|
|
|
|
Ctrl<T> <quotedbl> <Y> : "\276" threequarters
|
|
|
|
|
|
|
|
|
|
Note the lower case <t>. Changing this line should make C-t work.
|
|
|
|
|
|
|
|
|
|
*** 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.
|
|
|
|
|
|
|
|
|
|
*** Other legacy Solaris problems
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2014-01-23 02:11:13 +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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
pen@lysator.liu.se says (Feb 1998) that the Compose key does work
|
2010-05-28 03:23:08 +00:00
|
|
|
|
if you link with the MIT X11 libraries instead of the Solaris X11 libraries.
|
2004-09-04 12:25:43 +00:00
|
|
|
|
|
2010-05-28 03:23:08 +00:00
|
|
|
|
** MS-Windows 95, 98, ME, and NT
|
2004-09-04 12:25:43 +00:00
|
|
|
|
|
|
|
|
|
*** MS-Windows NT/95: Problems running Perl under Emacs
|
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'perl -de 0' just hangs when executed in an Emacs subshell.
|
2004-09-04 12:25:43 +00:00
|
|
|
|
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 ****
|
2008-08-26 20:02:17 +00:00
|
|
|
|
$rcfile=".perldb";
|
2004-09-04 12:25:43 +00:00
|
|
|
|
}
|
|
|
|
|
else {
|
|
|
|
|
! $console = "con";
|
2008-08-26 20:02:17 +00:00
|
|
|
|
$rcfile="perldb.ini";
|
2004-09-04 12:25:43 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
--- 68,74 ----
|
2008-08-26 20:02:17 +00:00
|
|
|
|
$rcfile=".perldb";
|
2004-09-04 12:25:43 +00:00
|
|
|
|
}
|
|
|
|
|
else {
|
|
|
|
|
! $console = "";
|
2008-08-26 20:02:17 +00:00
|
|
|
|
$rcfile="perldb.ini";
|
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 ****
|
2008-08-26 20:02:17 +00:00
|
|
|
|
$rcfile=".perldb";
|
2004-09-04 12:25:43 +00:00
|
|
|
|
}
|
|
|
|
|
elsif (-e "con") {
|
|
|
|
|
! $console = "con";
|
2008-08-26 20:02:17 +00:00
|
|
|
|
$rcfile="perldb.ini";
|
2004-09-04 12:25:43 +00:00
|
|
|
|
}
|
|
|
|
|
else {
|
|
|
|
|
--- 22,28 ----
|
2008-08-26 20:02:17 +00:00
|
|
|
|
$rcfile=".perldb";
|
2004-09-04 12:25:43 +00:00
|
|
|
|
}
|
|
|
|
|
elsif (-e "con") {
|
|
|
|
|
! $console = "";
|
2008-08-26 20:02:17 +00:00
|
|
|
|
$rcfile="perldb.ini";
|
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
|
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").
|
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
|
2010-05-28 03:23:08 +00:00
|
|
|
|
program in JDEE when javac.exe is installed, but not on the system PATH.
|
2004-09-04 12:25:43 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** MS-DOS
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
If the error message is "VDM has been already loaded", this is because
|
2015-08-26 21:05:43 +00:00
|
|
|
|
Windows has a program called 'redir.exe' that is incompatible with a
|
2004-08-21 11:31:45 +00:00
|
|
|
|
program by the same name supplied with DJGPP, which is used by
|
2015-08-26 21:05:43 +00:00
|
|
|
|
config.bat. To resolve this, move the DJGPP's 'bin' subdirectory to
|
2004-08-21 11:31:45 +00:00
|
|
|
|
the front of your PATH environment variable.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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.)
|
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
This happens when the functions 'user-login-name' and
|
|
|
|
|
'user-real-login-name' return different strings for your username as
|
2009-02-24 19:09:03 +00:00
|
|
|
|
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.
|
|
|
|
|
|
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").
|
|
|
|
|
|
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
|
|
|
|
|
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
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** Emacs compiled with DJGPP complains at startup:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2015-08-26 21:05:43 +00:00
|
|
|
|
This can happen if you define an environment variable 'TERM'. Emacs
|
2004-08-21 11:31:45 +00:00
|
|
|
|
on MSDOS uses an internal terminal emulator which is disabled if the
|
2015-08-26 21:05:43 +00:00
|
|
|
|
value of 'TERM' is anything but the string "internal". Emacs then
|
2004-08-21 11:31:45 +00:00
|
|
|
|
works as if its terminal were a dumb glass teletype that doesn't
|
2015-08-26 21:05:43 +00:00
|
|
|
|
support faces. To work around this, arrange for 'TERM' to be
|
2004-08-21 11:31:45 +00:00
|
|
|
|
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
|
2015-08-26 21:05:43 +00:00
|
|
|
|
'TERM'; this way, only Emacs gets the empty value, while the rest of
|
2004-08-21 11:31:45 +00:00
|
|
|
|
your system works as before.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** MS-DOS: Emacs crashes at startup.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Some users report that Emacs 19.29 requires dpmi memory management,
|
2010-05-28 03:23:08 +00:00
|
|
|
|
and crashes on startup if the system does not have it. We don't
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
*** Emacs compiled with DJGPP for MS-DOS/MS-Windows cannot access files
|
2015-08-26 21:05:43 +00:00
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
Another manifestation of this problem is that Emacs is unable to load
|
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
|
|
|
|
|
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
|
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
|
|
|
|
|
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
|
|
|
|
|
2018-05-18 16:24:04 +00:00
|
|
|
|
** Apple Macintosh operating systems
|
|
|
|
|
|
|
|
|
|
*** OS X 10.9 and earlier: symlinks autocomplete as directories
|
|
|
|
|
|
|
|
|
|
Autocompleting the name of a symbolic link incorrectly appends "/".
|
|
|
|
|
Building and running Emacs on OS X 10.10 (or later) fixes the problem.
|
|
|
|
|
Older operating systems are no longer supported by Apple.
|
|
|
|
|
https://bugs.gnu.org/31305
|
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Archaic window managers and toolkits
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2014-01-23 02:11:13 +00:00
|
|
|
|
*** Open Look: Under Open Look, the Emacs window disappears when you type M-q.
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
OpenWindows.WindowMenuAccelerators: False
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
twm normally ignores "program-specified" positions.
|
2015-08-26 21:05:43 +00:00
|
|
|
|
You can tell it to obey them with this command in your '.twmrc' file:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
UsePPosition "on" #allow clients to request a position
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
** Bugs related to old DEC hardware
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
This shell command should fix it:
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
2004-08-21 11:31:45 +00:00
|
|
|
|
xmodmap -e 'keycode 0xb1 = Meta_L'
|
1999-10-03 12:39:42 +00:00
|
|
|
|
|
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
|
|
|
|
|
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.
|
2001-12-06 09:26:21 +00:00
|
|
|
|
|
2007-02-11 01:18:25 +00:00
|
|
|
|
This file is part of GNU Emacs.
|
2002-11-06 05:11:59 +00:00
|
|
|
|
|
2008-05-15 07:32:14 +00:00
|
|
|
|
GNU Emacs is free software: you can redistribute it and/or modify
|
2007-02-11 01:18:25 +00:00
|
|
|
|
it under the terms of the GNU General Public License as published by
|
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.
|
2002-11-06 05:11:59 +00:00
|
|
|
|
|
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
|
2017-09-13 22:52:52 +00:00
|
|
|
|
along with GNU Emacs. If not, see <https://www.gnu.org/licenses/>.
|
2007-02-11 01:18:25 +00:00
|
|
|
|
|
|
|
|
|
|
2001-12-06 09:26:21 +00:00
|
|
|
|
Local variables:
|
|
|
|
|
mode: outline
|
2008-08-26 20:02:17 +00:00
|
|
|
|
paragraph-separate: "[ ]*$"
|
2001-12-06 09:26:21 +00:00
|
|
|
|
end:
|