1 Known Problems with GNU Emacs
3 Copyright (C) 1987-1989, 1993-1999, 2001-2016 Free Software Foundation,
5 See the end of the file for license conditions.
8 This file describes various problems that have been encountered
9 in compiling, installing and running GNU Emacs. Try doing C-c C-t
10 and browsing through the outline headers. (See C-h m for help on
11 Outline mode.) Information about systems that are no longer supported,
12 and old Emacs releases, has been removed. Consult older versions of
13 this file if you are interested in that information.
15 * Mule-UCS doesn't work in Emacs 23 onwards
17 It's completely redundant now, as far as we know.
19 * Emacs startup failures
21 ** Emacs fails to start, complaining about missing fonts.
23 A typical error message might be something like
25 No fonts match ‘-*-fixed-medium-r-*--6-*-*-*-*-*-iso8859-1’
27 This happens because some X resource specifies a bad font family for
28 Emacs to use. The possible places where this specification might be are:
30 - in the X server resources database, often initialized from
31 ~/.Xresources (use $ xrdb -query to find out the current state)
33 - in your ~/.Xdefaults file
35 - client-side X resource file, such as ~/Emacs or
36 /usr/share/X11/app-defaults/Emacs
38 One of these files might have bad or malformed specification of a
39 fontset that Emacs should use. To fix the problem, you need to find
40 the problematic line(s) and correct them.
42 After correcting ~/.Xresources, the new data has to be merged into the
43 X server resources database. Depending on the circumstances, the
44 following command may do the trick. See xrdb(1) for more information.
46 $ xrdb -merge ~/.Xresources
48 ** Emacs aborts while starting up, only when run without X.
50 This problem often results from compiling Emacs with GCC when GCC was
51 installed incorrectly. The usual error in installing GCC is to
52 specify --includedir=/usr/include. Installation of GCC makes
53 corrected copies of the system header files. GCC is supposed to use
54 the corrected copies in preference to the original system headers.
55 Specifying --includedir=/usr/include causes the original system header
56 files to be used. On some systems, the definition of ioctl in the
57 original system header files is invalid for ANSI C and causes Emacs
60 The fix is to reinstall GCC, and this time do not specify --includedir
61 when you configure it. Then recompile Emacs. Specifying --includedir
62 is appropriate only in very special cases and it should *never* be the
63 same directory where system header files are kept.
65 ** Emacs does not start, complaining that it cannot open termcap database file.
67 If your system uses Terminfo rather than termcap (most modern
68 systems do), this could happen if the proper version of
69 ncurses is not visible to the Emacs configure script (i.e. it
70 cannot be found along the usual path the linker looks for
71 libraries). It can happen because your version of ncurses is
72 obsolete, or is available only in form of binaries.
74 The solution is to install an up-to-date version of ncurses in
75 the developer's form (header files, static libraries and
76 symbolic links); in some GNU/Linux distributions (e.g. Debian)
77 it constitutes a separate package.
79 ** Emacs 20 and later fails to load Lisp files at startup.
81 The typical error message might be like this:
83 "Cannot open load file: fontset"
85 This could happen if you compress the file lisp/subdirs.el. That file
86 tells Emacs what are the directories where it should look for Lisp
87 files. Emacs cannot work with subdirs.el compressed, since the
88 Auto-compress mode it needs for this will not be loaded until later,
89 when your .emacs file is processed. (The package 'fontset.el' is
90 required to set up fonts used to display text on window systems, and
91 it's loaded very early in the startup procedure.)
93 Similarly, any other .el file for which there's no corresponding .elc
94 file could fail to load if it is compressed.
96 The solution is to uncompress all .el files that don't have a .elc file.
98 Another possible reason for such failures is stale *.elc files
99 lurking somewhere on your load-path -- see the next section.
101 ** Emacs prints an error at startup after upgrading from an earlier version.
103 An example of such an error is:
105 x-complement-fontset-spec: "Wrong type argument: stringp, nil"
107 This can be another symptom of stale *.elc files in your load-path.
108 The following command will print any duplicate Lisp files that are
109 present in load-path:
111 emacs -batch -f list-load-path-shadows
113 If this command prints any file names, some of these files are stale,
114 and should be deleted or their directories removed from your
119 ** Emacs crashes when running in a terminal, if compiled with GCC 4.5.0
121 This version of GCC is buggy: see
123 http://debbugs.gnu.org/6031
124 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43904
126 You can work around this error in gcc-4.5 by omitting sibling call
127 optimization. To do this, configure Emacs with
129 CFLAGS="-g -O2 -fno-optimize-sibling-calls" ./configure
131 ** Emacs compiled with GCC 4.6.1 crashes on MS-Windows when C-g is pressed
133 This is known to happen when Emacs is compiled with MinGW GCC 4.6.1
134 with the -O2 option (which is the default in the Windows build). The
135 reason is a bug in MinGW GCC 4.6.1; to work around, either add the
136 '-fno-omit-frame-pointer' switch to GCC or compile without
137 optimizations ('--no-opt' switch to the configure.bat script).
139 ** Emacs crashes in x-popup-dialog.
141 This can happen if the dialog widget cannot find the font it wants to
142 use. You can work around the problem by specifying another font with
143 an X resource--for example, 'Emacs.dialog*.font: 9x15' (or any font that
144 happens to exist on your X server).
146 ** Emacs crashes when you use Bibtex mode.
148 This happens if your system puts a small limit on stack size. You can
149 prevent the problem by using a suitable shell command (often 'ulimit')
150 to raise the stack size limit before you run Emacs.
152 Patches to raise the stack size limit automatically in 'main'
153 (src/emacs.c) on various systems would be greatly appreciated.
155 ** Error message 'Symbol’s value as variable is void: x', followed by
156 a segmentation fault and core dump.
158 This has been tracked to a bug in tar! People report that tar erroneously
159 added a line like this at the beginning of files of Lisp code:
161 x FILENAME, N bytes, B tape blocks
163 If your tar has this problem, install GNU tar--if you can manage to
166 ** Emacs can crash when displaying PNG images with transparency.
168 This is due to a bug introduced in ImageMagick 6.8.2-3. The bug should
169 be fixed in ImageMagick 6.8.3-10. See <URL:http://debbugs.gnu.org/13867>.
171 ** Crashes when displaying GIF images in Emacs built with version
172 libungif-4.1.0 are resolved by using version libungif-4.1.0b1.
173 Configure checks for the correct version, but this problem could occur
174 if a binary built against a shared libungif is run on a system with an
177 ** Emacs aborts inside the function 'tparam1'.
179 This can happen if Emacs was built without terminfo support, but the
180 terminal's capabilities use format that is only supported by terminfo.
181 If your system has ncurses installed, this might happen if your
182 version of ncurses is broken; upgrading to a newer version of ncurses
183 and reconfiguring and rebuilding Emacs should solve this.
185 All modern systems support terminfo, so even if ncurses is not the
186 problem, you should look for a way to configure Emacs so that it uses
189 ** Emacs crashes when using some version of the Exceed X server.
191 Upgrading to a newer version of Exceed has been reported to prevent
192 these crashes. You should consider switching to a free X server, such
193 as Xming or Cygwin/X.
195 ** Emacs crashes with SIGSEGV in XtInitializeWidgetClass.
197 It crashes on X, but runs fine when called with option "-nw".
199 This has been observed when Emacs is linked with GNU ld but without passing
200 the -z nocombreloc flag. Emacs normally knows to pass the -z nocombreloc
201 flag when needed, so if you come across a situation where the flag is
202 necessary but missing, please report it via M-x report-emacs-bug.
204 On platforms such as Solaris, you can also work around this problem by
205 configuring your compiler to use the native linker instead of GNU ld.
207 ** When Emacs is compiled with Gtk+, closing a display kills Emacs.
209 There is a long-standing bug in GTK that prevents it from recovering
210 from disconnects: http://bugzilla.gnome.org/show_bug.cgi?id=85715.
212 Thus, for instance, when Emacs is run as a server on a text terminal,
213 and an X frame is created, and the X server for that frame crashes or
214 exits unexpectedly, Emacs must exit to prevent a GTK error that would
215 result in an endless loop.
217 If you need Emacs to be able to recover from closing displays, compile
218 it with the Lucid toolkit instead of GTK.
220 ** Emacs crashes when you try to view a file with complex characters.
222 For example, the etc/HELLO file (as shown by C-h h).
223 The message "symbol lookup error: /usr/bin/emacs: undefined symbol: OTF_open"
224 is shown in the terminal from which you launched Emacs.
225 This problem only happens when you use a graphical display (ie not
226 with -nw) and compiled Emacs with the "libotf" library for complex
229 This problem occurs because unfortunately there are two libraries
230 called "libotf". One is the library for handling OpenType fonts,
231 http://www.m17n.org/libotf/, which is the one that Emacs expects.
232 The other is a library for Open Trace Format, and is used by some
233 versions of the MPI message passing interface for parallel
236 For example, on RHEL6 GNU/Linux, the OpenMPI rpm provides a version
237 of "libotf.so" in /usr/lib/openmpi/lib. This directory is not
238 normally in the ld search path, but if you want to use OpenMPI,
239 you must issue the command "module load openmpi". This adds
240 /usr/lib/openmpi/lib to LD_LIBRARY_PATH. If you then start Emacs from
241 the same shell, you will encounter this crash.
242 Ref: <URL:https://bugzilla.redhat.com/show_bug.cgi?id=844776>
244 There is no good solution to this problem if you need to use both
245 OpenMPI and Emacs with libotf support. The best you can do is use a
246 wrapper shell script (or function) "emacs" that removes the offending
247 element from LD_LIBRARY_PATH before starting emacs proper.
248 Or you could recompile Emacs with an -Wl,-rpath option that
249 gives the location of the correct libotf.
251 * General runtime problems
255 *** Changes made to .el files do not take effect.
257 You may have forgotten to recompile them into .elc files.
258 Then the old .elc files will be loaded, and your changes
259 will not be seen. To fix this, do M-x byte-recompile-directory
260 and specify the directory that contains the Lisp files.
262 Emacs prints a warning when loading a .elc file which is older
263 than the corresponding .el file.
265 Alternatively, if you set the option 'load-prefer-newer' non-nil,
266 Emacs will load whichever version of a file is the newest.
268 *** Watch out for the EMACSLOADPATH environment variable
270 EMACSLOADPATH overrides which directories the function "load" will search.
272 If you observe strange problems, check for this variable in your
275 *** Using epop3.el package causes Emacs to signal an error.
277 The error message might be something like this:
279 "Lisp nesting exceeds max-lisp-eval-depth"
281 This happens because epop3 redefines the function gethash, which is a
282 built-in primitive beginning with Emacs 21.1. We don't have a patch
283 for epop3 to fix it, but perhaps a newer version of epop3 corrects that.
285 *** Buffers from 'with-output-to-temp-buffer' get set up in Help mode.
287 Changes in Emacs 20.4 to the hooks used by that function cause
288 problems for some packages, specifically BBDB. See the function's
289 documentation for the hooks involved. BBDB 2.00.06 fixes the problem.
291 *** The Hyperbole package causes *Help* buffers not to be displayed in
292 Help mode due to setting 'temp-buffer-show-hook' rather than using
293 'add-hook'. Using '(add-hook 'temp-buffer-show-hook 'help-mode-finish)'
294 after loading Hyperbole should fix this.
298 *** Unable to enter the M-| key on some German keyboards.
299 Some users have reported that M-| suffers from "keyboard ghosting".
300 This can't be fixed by Emacs, as the keypress never gets passed to it
301 at all (as can be verified using "xev"). You can work around this by
302 typing 'ESC |' instead.
304 *** "Compose Character" key does strange things when used as a Meta key.
306 If you define one key to serve as both Meta and Compose Character, you
307 will get strange results. In previous Emacs versions, this "worked"
308 in that the key acted as Meta--that's because the older Emacs versions
309 did not try to support Compose Character. Now Emacs tries to do
310 character composition in the standard X way. This means that you
311 must pick one meaning or the other for any given key.
313 You can use both functions (Meta, and Compose Character) if you assign
314 them to two different keys.
316 *** C-z just refreshes the screen instead of suspending Emacs.
318 You are probably using a shell that doesn't support job control, even
319 though the system itself is capable of it. Either use a different shell,
320 or set the variable 'cannot-suspend' to a non-nil value.
322 ** Mailers and other helper programs
324 *** movemail compiled with POP support can't connect to the POP server.
326 Make sure that the 'pop' entry in /etc/services, or in the services
327 NIS map if your machine uses NIS, has the same port number as the
328 entry on the POP server. A common error is for the POP server to be
329 listening on port 110, the assigned port for the POP3 protocol, while
330 the client is trying to connect on port 109, the assigned port for the
333 *** RMAIL gets error getting new mail.
335 RMAIL gets new mail from /usr/spool/mail/$USER using a program
336 called 'movemail'. This program interlocks with /bin/mail using
337 the protocol defined by /bin/mail.
339 There are two different protocols in general use. One of them uses
340 the 'flock' system call. The other involves creating a lock file;
341 'movemail' must be able to write in /usr/spool/mail in order to do
342 this. You control which one is used by defining, or not defining,
343 the macro MAIL_USE_FLOCK in config.h.
344 IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
345 SYSTEM, YOU CAN LOSE MAIL!
347 If your system uses the lock file protocol, and fascist restrictions
348 prevent ordinary users from writing the lock files in /usr/spool/mail,
349 you may need to make 'movemail' setgid to a suitable group such as
350 'mail'. To do this, use the following commands (as root) after doing the
356 Installation normally copies movemail from the build directory to an
357 installation directory which is usually under /usr/local/lib. The
358 installed copy of movemail is usually in the directory
359 /usr/local/lib/emacs/VERSION/TARGET. You must change the group and
360 mode of the installed copy; changing the group and mode of the build
361 directory copy is ineffective.
363 *** rcs2log gives you the awk error message "too many fields".
365 This is due to an arbitrary limit in certain versions of awk.
366 The solution is to use gawk (GNU awk).
368 ** Problems with hostname resolution
370 *** Emacs does not know your host's fully-qualified domain name.
372 For example, (system-name) returns some variation on
373 "localhost.localdomain", rather the name you were expecting.
375 You need to configure your machine with a fully qualified domain name,
376 (i.e., a name with at least one "."), either in /etc/hostname
377 or wherever your system calls for specifying this.
379 If you cannot fix the configuration, you can set the Lisp variable
380 mail-host-address to the value you want.
384 *** Emacs says it has saved a file, but the file does not actually
387 This can happen on certain systems when you are using NFS, if the
388 remote disk is full. It is due to a bug in NFS (or certain NFS
389 implementations), and there is apparently nothing Emacs can do to
390 detect the problem. Emacs checks the failure codes of all the system
391 calls involved in writing a file, including 'close'; but in the case
392 where the problem occurs, none of those system calls fails.
394 ** PSGML conflicts with sgml-mode.
396 PSGML package uses the same names of some variables (like keymap)
397 as built-in sgml-mode.el because it was created as a replacement
398 of that package. The conflict will be shown if you load
399 sgml-mode.el before psgml.el. E.g. this could happen if you edit
400 HTML page and then start to work with SGML or XML file. html-mode
401 (from sgml-mode.el) is used for HTML file and loading of psgml.el
402 (for sgml-mode or xml-mode) will cause an error.
406 *** Lines are not updated or new lines are added in the buffer upon commit.
408 When committing files located higher in the hierarchy than the examined
409 directory, some versions of the CVS program return an ambiguous message
410 from which PCL-CVS cannot extract the full location of the committed
411 files. As a result, the corresponding lines in the PCL-CVS buffer are
412 not updated with the new revision of these files, and new lines are
413 added to the top-level directory.
415 This can happen with CVS versions 1.12.8 and 1.12.9. Upgrade to CVS
416 1.12.10 or newer to fix this problem.
418 ** Miscellaneous problems
420 *** Editing files with very long lines is slow.
422 For example, simply moving through a file that contains hundreds of
423 thousands of characters per line is slow, and consumes a lot of CPU.
424 This is a known limitation of Emacs with no solution at this time.
426 *** Emacs uses 100% of CPU time
428 This was a known problem with some old versions of the Semantic package.
429 The solution was to upgrade Semantic to version 2.0pre4 (distributed
430 with CEDET 1.0pre4) or later. Note that Emacs includes Semantic since
431 23.2, and this issue does not apply to the included version.
433 *** Self-documentation messages are garbled.
435 This means that the file 'etc/DOC' doesn't properly correspond
436 with the Emacs executable. Redumping Emacs and then installing the
437 corresponding pair of files should fix the problem.
439 *** Programs running under terminal emulator do not recognize 'emacs'
442 The cause of this is a shell startup file that sets the TERMCAP
443 environment variable. The terminal emulator uses that variable to
444 provide the information on the special terminal type that Emacs emulates.
446 Rewrite your shell startup file so that it does not change TERMCAP
447 in such a case. You could use the following conditional which sets
448 it only if it is undefined.
450 if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file
452 Or you could set TERMCAP only when you set TERM--which should not
453 happen in a non-login shell.
455 *** In Shell mode, you get a ^M at the end of every line.
457 This happens to people who use tcsh, because it is trying to be too
458 smart. It sees that the Shell uses terminal type 'unknown' and turns
459 on the flag to output ^M at the end of each line. You can fix the
460 problem by adding this to your .cshrc file:
462 if ($?INSIDE_EMACS && $?tcsh)
464 stty -icrnl -onlcr -echo susp ^Z
467 *** Emacs startup on GNU/Linux systems (and possibly other systems) is slow.
469 This can happen if the system is misconfigured and Emacs can't get the
470 full qualified domain name, FQDN. You should have your FQDN in the
471 /etc/hosts file, something like this:
474 129.187.137.82 nuc04.t30.physik.tu-muenchen.de nuc04
476 The way to set this up may vary on non-GNU systems.
478 *** Visiting files in some auto-mounted directories causes Emacs to print
479 'Error reading dir-locals: (file-error "Read error" "is a directory" ...'
481 This can happen if the auto-mounter mistakenly reports that
482 .dir-locals.el exists and is a directory. There is nothing Emacs can
483 do about this, but you can avoid the issue by adding a suitable entry
484 to the variable 'locate-dominating-stop-dir-regexp'. For example, if
485 the problem relates to "/smb/.dir-locals.el", set that variable
486 to a new value where you replace "net\\|afs" with "net\\|afs\\|smb".
487 (The default value already matches common auto-mount prefixes.)
488 See http://lists.gnu.org/archive/html/help-gnu-emacs/2015-02/msg00461.html .
490 *** Attempting to visit remote files via ange-ftp fails.
492 If the error message is "ange-ftp-file-modtime: Specified time is not
493 representable", then this could happen when 'lukemftp' is used as the
494 ftp client. This was reported to happen on Debian GNU/Linux, kernel
495 version 2.4.3, with 'lukemftp' 1.5-5, but might happen on other
496 systems as well. To avoid this problem, switch to using the standard
497 ftp client. On a Debian system, type
499 update-alternatives --config ftp
501 and then choose /usr/bin/netkit-ftp.
503 *** Dired is very slow.
505 This could happen if invocation of the 'df' program takes a long
506 time. Possible reasons for this include:
508 - ClearCase mounted filesystems (VOBs) that sometimes make 'df'
509 response time extremely slow (dozens of seconds);
511 - slow automounters on some old versions of Unix;
513 - slow operation of some versions of 'df'.
515 To work around the problem, you could either (a) set the variable
516 'directory-free-space-program' to nil, and thus prevent Emacs from
517 invoking 'df'; (b) use 'df' from the GNU Coreutils package; or
518 (c) use CVS, which is Free Software, instead of ClearCase.
520 *** ps-print commands fail to find prologue files ps-prin*.ps.
522 This can happen if you use an old version of X-Symbol package: it
523 defines compatibility functions which trick ps-print into thinking it
524 runs in XEmacs, and look for the prologue files in a wrong directory.
526 The solution is to upgrade X-Symbol to a later version.
528 *** On systems with shared libraries you might encounter run-time errors
529 from the dynamic linker telling you that it is unable to find some
530 shared libraries, for instance those for Xaw3d or image support.
531 These errors mean Emacs has been linked with a library whose shared
532 library is not in the default search path of the dynamic linker.
534 Similar problems could prevent Emacs from building, since the build
535 process invokes Emacs several times.
537 On many systems, it is possible to set LD_LIBRARY_PATH in your
538 environment to specify additional directories where shared libraries
541 Other systems allow to set LD_RUN_PATH in a similar way, but before
542 Emacs is linked. With LD_RUN_PATH set, the linker will include a
543 specified run-time search path in the executable.
545 Please refer to the documentation of your dynamic linker for details.
547 *** When you run Ispell from Emacs, it reports a "misalignment" error.
549 This can happen if you compiled the Ispell program to use ASCII
550 characters only and then try to use it from Emacs with non-ASCII
551 characters, like Latin-1. The solution is to recompile Ispell with
552 support for 8-bit characters.
554 To see whether your Ispell program supports 8-bit characters, type
555 this at your shell's prompt:
559 and look in the output for the string "NO8BIT". If Ispell says
560 "!NO8BIT (8BIT)", your speller supports 8-bit characters; otherwise it
563 To rebuild Ispell with 8-bit character support, edit the local.h file
564 in the Ispell distribution and make sure it does _not_ define NO8BIT.
565 Then rebuild the speller.
567 Another possible cause for "misalignment" error messages is that the
568 version of Ispell installed on your machine is old. Upgrade.
570 Yet another possibility is that you are trying to spell-check a word
571 in a language that doesn't fit the dictionary you choose for use by
572 Ispell. (Ispell can only spell-check one language at a time, because
573 it uses a single dictionary.) Make sure that the text you are
574 spelling and the dictionary used by Ispell conform to each other.
576 If your spell-checking program is Aspell, it has been reported that if
577 you have a personal configuration file (normally ~/.aspell.conf), it
578 can cause this error. Remove that file, execute 'ispell-kill-ispell'
579 in Emacs, and then try spell-checking again.
581 *** Emacs eats all file descriptors when using kqueue file notifications.
582 See <http://debbugs.gnu.org/22814>.
584 When you have a large number of buffers running auto-revert-mode, and
585 Emacs is configured to use the kqueue file notification library, it
586 uses an own file descriptor for every watched file. On systems with a
587 small limit of file descriptors allowed per process, like OS X, you
588 could run out of file descriptors. You won't be able to open new files.
590 auto-revert-use-notify is set to nil in global-auto-revert-mode, therefore.
592 *** TLS problems, e.g., Gnus hangs when fetching via imaps
593 http://debbugs.gnu.org/24247
595 gnutls-cli 3.5.3 (2016-08-09) does not generate a "- Handshake was
596 completed" message that tls.el relies upon, causing affected Emacs
597 functions to hang. To work around the problem, use older or newer
598 versions of gnutls-cli, or use Emacs's built-in gnutls support.
600 * Runtime problems related to font handling
602 ** Characters are displayed as empty boxes or with wrong font under X.
604 *** This can occur when two different versions of FontConfig are used.
605 For example, XFree86 4.3.0 has one version and Gnome usually comes
606 with a newer version. Emacs compiled with Gtk+ will then use the
607 newer version. In most cases the problem can be temporarily fixed by
608 stopping the application that has the error (it can be Emacs or any
609 other application), removing ~/.fonts.cache-1, and then starting the
610 application again. If removing ~/.fonts.cache-1 and restarting
611 doesn't help, the application with problem must be recompiled with the
612 same version of FontConfig as the rest of the system uses. For KDE,
613 it is sufficient to recompile Qt.
615 *** Some fonts have a missing glyph and no default character. This is
616 known to occur for character number 160 (no-break space) in some
617 fonts, such as Lucida but Emacs sets the display table for the unibyte
618 and Latin-1 version of this character to display a space.
620 *** Some of the fonts called for in your fontset may not exist on your
623 Each X font covers just a fraction of the characters that Emacs
624 supports. To display the whole range of Emacs characters requires
625 many different fonts, collected into a fontset. You can remedy the
626 problem by installing additional fonts.
628 The intlfonts distribution includes a full spectrum of fonts that can
629 display all the characters Emacs supports. The etl-unicode collection
630 of fonts (available from <URL:ftp://ftp.x.org/contrib/fonts/>) includes
631 fonts that can display many Unicode characters; they can also be used
632 by ps-print and ps-mule to print Unicode characters.
634 ** Under X, some characters appear improperly aligned in their lines.
636 You may have bad fonts.
638 ** Under X, an unexpected monospace font is used as the default font.
640 When compiled with XFT, Emacs tries to use a default font named
641 "monospace". This is a "virtual font", which the operating system
642 (Fontconfig) redirects to a suitable font such as DejaVu Sans Mono.
643 On some systems, there exists a font that is actually named Monospace,
644 which takes over the virtual font. This is considered an operating
647 http://lists.gnu.org/archive/html/emacs-devel/2008-10/msg00696.html
649 If you encounter this problem, set the default font to a specific font
650 in your .Xresources or initialization file. For instance, you can put
651 the following in your .Xresources:
653 Emacs.font: DejaVu Sans Mono 12
655 ** Certain fonts make each line take one pixel more than it should.
657 This is because these fonts contain characters a little taller than
658 the font's nominal height. Emacs needs to make sure that lines do not
661 ** Font Lock displays portions of the buffer in incorrect faces.
663 By far the most frequent cause of this is a parenthesis '(' or a brace
664 '{' in column zero. Font Lock assumes that such a paren is outside of
665 any comment or string. This is of course not true in general, but the
666 vast majority of well-formatted program source files don't have such
667 parens, and therefore this assumption is used to allow optimizations
668 in Font Lock's syntactical analysis. These optimizations avoid some
669 pathological cases where jit-lock, the Just-in-Time fontification
670 introduced with Emacs 21.1, could significantly slow down scrolling
671 through the buffer, especially scrolling backwards, and also jumping
672 to the end of a very large buffer.
674 Beginning with version 22.1, a parenthesis or a brace in column zero
675 is highlighted in bold-red face if it is inside a string or a comment,
676 to indicate that it could interfere with Font Lock (and also with
677 indentation) and should be moved or escaped with a backslash.
679 If you don't use large buffers, or have a very fast machine which
680 makes the delays insignificant, you can avoid the incorrect
681 fontification by setting the variable
682 'font-lock-beginning-of-syntax-function' to a nil value. (This must
683 be done _after_ turning on Font Lock.)
685 Another alternative is to avoid a paren in column zero. For example,
686 in a Lisp string you could precede the paren with a backslash.
688 ** Emacs pauses for several seconds when changing the default font.
690 This has been reported for fvwm 2.2.5 and the window manager of KDE
691 2.1. The reason for the pause is Xt waiting for a ConfigureNotify
692 event from the window manager, which the window manager doesn't send.
693 Xt stops waiting after a default timeout of usually 5 seconds.
695 A workaround for this is to add something like
697 emacs.waitForWM: false
699 to your X resources. Alternatively, add '(wait-for-wm . nil)' to a
700 frame's parameter list, like this:
702 (modify-frame-parameters nil '((wait-for-wm . nil)))
704 (this should go into your '.emacs' file).
706 ** Underlines appear at the wrong position.
708 This is caused by fonts having a wrong UNDERLINE_POSITION property.
709 Examples are the 7x13 font on XFree86 prior to version 4.1, or the jmk
710 neep font from the Debian xfonts-jmk package prior to version 3.0.17.
711 To circumvent this problem, set x-use-underline-position-properties
712 to nil in your '.emacs'.
714 To see what is the value of UNDERLINE_POSITION defined by the font,
715 type 'xlsfonts -lll FONT' and look at the font's UNDERLINE_POSITION property.
717 ** When using Exceed, fonts sometimes appear too tall.
719 When the display is set to an Exceed X-server and fonts are specified
720 (either explicitly with the -fn option or implicitly with X resources)
721 then the fonts may appear "too tall". The actual character sizes are
722 correct but there is too much vertical spacing between rows, which
723 gives the appearance of "double spacing".
725 To prevent this, turn off the Exceed's "automatic font substitution"
726 feature (in the font part of the configuration window).
728 ** Subscript/superscript text in TeX is hard to read.
730 If 'tex-fontify-script' is non-nil, tex-mode displays
731 subscript/superscript text in the faces subscript/superscript, which
732 are smaller than the normal font and lowered/raised. With some fonts,
733 nested superscripts (say) can be hard to read. Switching to a
734 different font, or changing your antialiasing setting (on an LCD
735 screen), can both make the problem disappear. Alternatively, customize
736 the following variables: tex-font-script-display (how much to
737 lower/raise); tex-suscript-height-ratio (how much smaller than
738 normal); tex-suscript-height-minimum (minimum height).
740 ** Screen refresh is slow when there are special characters for which no suitable font is available
742 If the display is too slow in refreshing when you scroll to a new
743 region, or when you edit the buffer, it might be due to the fact that
744 some characters cannot be displayed in the default font, and Emacs is
745 spending too much time in looking for a suitable font to display them.
747 You can suspect this if you have several characters that are displayed
748 as small rectangles containing a hexadecimal code inside.
750 The solution is to install the appropriate fonts on your machine. For
751 instance if you are editing a text with a lot of math symbols, then
752 installing a font like 'Symbola' should solve this problem.
754 * Internationalization problems
756 ** M-{ does not work on a Spanish PC keyboard.
758 Many Spanish keyboards seem to ignore that combination. Emacs can't
759 do anything about it.
761 ** International characters aren't displayed under X.
765 XFree86 4 contains many fonts in iso10646-1 encoding which have
766 minimal character repertoires (whereas the encoding part of the font
767 name is meant to be a reasonable indication of the repertoire
768 according to the XLFD spec). Emacs may choose one of these to display
769 characters from the mule-unicode charsets and then typically won't be
770 able to find the glyphs to display many characters. (Check with C-u
771 C-x = .) To avoid this, you may need to use a fontset which sets the
772 font for the mule-unicode sets explicitly. E.g. to use GNU unifont,
773 include in the fontset spec:
775 mule-unicode-2500-33ff:-gnu-unifont-*-iso10646-1,\
776 mule-unicode-e000-ffff:-gnu-unifont-*-iso10646-1,\
777 mule-unicode-0100-24ff:-gnu-unifont-*-iso10646-1
779 ** The UTF-8/16/7 coding systems don't encode CJK (Far Eastern) characters.
781 Emacs directly supports the Unicode BMP whose code points are in the
782 ranges 0000-33ff and e000-ffff, and indirectly supports the parts of
783 CJK characters belonging to these legacy charsets:
785 GB2312, Big5, JISX0208, JISX0212, JISX0213-1, JISX0213-2, KSC5601
787 The latter support is done in Utf-Translate-Cjk mode (turned on by
788 default). Which Unicode CJK characters are decoded into which Emacs
789 charset is decided by the current language environment. For instance,
790 in Chinese-GB, most of them are decoded into chinese-gb2312.
792 If you read UTF-8 data with code points outside these ranges, the
793 characters appear in the buffer as raw bytes of the original UTF-8
794 (composed into a single quasi-character) and they will be written back
795 correctly as UTF-8, assuming you don't break the composed sequences.
796 If you read such characters from UTF-16 or UTF-7 data, they are
797 substituted with the Unicode 'replacement character', and you lose
800 ** Accented ISO-8859-1 characters are displayed as | or _.
802 Try other font set sizes (S-mouse-1). If the problem persists with
803 other sizes as well, your text is corrupted, probably through software
804 that is not 8-bit clean. If the problem goes away with another font
805 size, it's probably because some fonts pretend to be ISO-8859-1 fonts
806 when they are really ASCII fonts. In particular the schumacher-clean
807 fonts have this bug in some versions of X.
809 To see what glyphs are included in a font, use 'xfd', like this:
811 xfd -fn -schumacher-clean-medium-r-normal--12-120-75-75-c-60-iso8859-1
813 If this shows only ASCII glyphs, the font is indeed the source of the problem.
815 The solution is to remove the corresponding lines from the appropriate
816 'fonts.alias' file, then run 'mkfontdir' in that directory, and then run
819 ** The 'oc-unicode' package doesn't work with Emacs 21.
821 This package tries to define more private charsets than there are free
822 slots now. The current built-in Unicode support is actually more
823 flexible. (Use option 'utf-translate-cjk-mode' if you need CJK
824 support.) Files encoded as emacs-mule using oc-unicode aren't
825 generally read correctly by Emacs 21.
829 ** X keyboard problems
831 *** You "lose characters" after typing Compose Character key.
833 This is because the Compose Character key is defined as the keysym
834 Multi_key, and Emacs (seeing that) does the proper X
835 character-composition processing. If you don't want your Compose key
836 to do that, you can redefine it with xmodmap.
838 For example, here's one way to turn it into a Meta key:
840 xmodmap -e "keysym Multi_key = Meta_L"
842 If all users at your site of a particular keyboard prefer Meta to
843 Compose, you can make the remapping happen automatically by adding the
844 xmodmap command to the xdm setup script for that display.
846 *** Using X Window System, control-shift-leftbutton makes Emacs hang.
848 Use the shell command 'xset bc' to make the old X Menu package work.
850 *** C-SPC fails to work on Fedora GNU/Linux (or with fcitx input method).
852 Fedora Core 4 steals the C-SPC key by default for the 'iiimx' program
853 which is the input method for some languages. It blocks Emacs users
854 from using the C-SPC key for 'set-mark-command'.
856 One solutions is to remove the '<Ctrl>space' from the 'Iiimx' file
857 which can be found in the '/usr/lib/X11/app-defaults' directory.
858 However, that requires root access.
860 Another is to specify 'Emacs*useXIM: false' in your X resources.
862 Another is to build Emacs with the '--without-xim' configure option.
864 The same problem happens on any other system if you are using fcitx
865 (Chinese input method) which by default use C-SPC for toggling. If
866 you want to use fcitx with Emacs, you have two choices. Toggle fcitx
867 by another key (e.g. C-\) by modifying ~/.fcitx/config, or be
868 accustomed to use C-@ for 'set-mark-command'.
870 *** Link-time optimization with clang doesn't work on Fedora 20.
872 As of May 2014, Fedora 20 has broken LLVMgold.so plugin support in clang
873 (tested with clang-3.4-6.fc20) - 'clang --print-file-name=LLVMgold.so'
874 prints 'LLVMgold.so' instead of full path to plugin shared library, and
875 'clang -flto' is unable to find the plugin with the following error:
877 /bin/ld: error: /usr/bin/../lib/LLVMgold.so: could not load plugin library:
878 /usr/bin/../lib/LLVMgold.so: cannot open shared object file: No such file
881 The only way to avoid this is to build your own clang from source code
882 repositories, as described at http://clang.llvm.org/get_started.html.
884 *** M-SPC seems to be ignored as input.
886 See if your X server is set up to use this as a command
887 for character composition.
889 *** The S-C-t key combination doesn't get passed to Emacs on X.
891 This happens because some X configurations assign the Ctrl-Shift-t
892 combination the same meaning as the Multi_key. The offending
893 definition is in the file '...lib/X11/locale/iso8859-1/Compose'; there
894 might be other similar combinations which are grabbed by X for similar
897 We think that this can be countermanded with the 'xmodmap' utility, if
898 you want to be able to bind one of these key sequences within Emacs.
900 *** Under X, C-v and/or other keys don't work.
902 These may have been intercepted by your window manager.
903 See the WM's documentation for how to change this.
905 *** Clicking C-mouse-2 in the scroll bar doesn't split the window.
907 This currently doesn't work with scroll-bar widgets (and we don't know
908 a good way of implementing it with widgets). If Emacs is configured
909 --without-toolkit-scroll-bars, C-mouse-2 on the scroll bar does work.
911 *** Inability to send an Alt-modified key, when Emacs is communicating
912 directly with an X server.
914 If you have tried to bind an Alt-modified key as a command, and it
915 does not work to type the command, the first thing you should check is
916 whether the key is getting through to Emacs. To do this, type C-h c
917 followed by the Alt-modified key. C-h c should say what kind of event
918 it read. If it says it read an Alt-modified key, then make sure you
919 have made the key binding correctly.
921 If C-h c reports an event that doesn't have the Alt modifier, it may
922 be because your X server has no key for the Alt modifier. The X
923 server that comes from MIT does not set up the Alt modifier by default.
925 If your keyboard has keys named Alt, you can enable them as follows:
927 xmodmap -e 'add mod2 = Alt_L'
928 xmodmap -e 'add mod2 = Alt_R'
930 If the keyboard has just one key named Alt, then only one of those
931 commands is needed. The modifier 'mod2' is a reasonable choice if you
932 are using an unmodified MIT version of X. Otherwise, choose any
933 modifier bit not otherwise used.
935 If your keyboard does not have keys named Alt, you can use some other
936 keys. Use the keysym command in xmodmap to turn a function key (or
937 some other 'spare' key) into Alt_L or into Alt_R, and then use the
938 commands show above to make them modifier keys.
940 Note that if you have Alt keys but no Meta keys, Emacs translates Alt
941 into Meta. This is because of the great importance of Meta in Emacs.
943 ** Window-manager and toolkit-related problems
945 *** Emacs built with GTK+ toolkit produces corrupted display on HiDPI screen
947 This can happen if you set GDK_SCALE=2 in the environment or in your
948 '.xinitrc' file. (This setting is usually accompanied by
949 GDK_DPI_SCALE=0.5.) Emacs can not support these settings correctly,
950 as it doesn't use GTK+ exclusively. The result is that sometimes
951 widgets like the scroll bar are displayed incorrectly, and frames
952 could be displayed "cropped" to only part of the stuff that should be
955 The workaround is to explicitly disable these settings when invoking
956 Emacs, for example (from a Posix shell prompt):
958 $ GDK_SCALE=1 GDK_DPI_SCALE=1 emacs
960 *** Emacs built with GTK+ toolkit can unexpectedly widen frames
962 This resizing takes place when a frame is not wide enough to accommodate
963 its entire menu bar. Typically, it occurs when switching buffers or
964 changing a buffer's major mode and the new mode adds entries to the menu
965 bar. The frame is then widened by the window manager so that the menu
966 bar is fully shown. Subsequently switching to another buffer or
967 changing the buffer's mode will not shrink the frame back to its
968 previous width. The height of the frame remains unaltered. Apparently,
969 the failure is also dependent on the chosen font.
971 The resizing is usually accompanied by console output like
973 Gtk-CRITICAL **: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed
975 It's not clear whether the GTK version used has any impact on the
976 occurrence of the failure. So far, the failure has been observed with
977 GTK+ versions 3.4.2, 3.14.5 and 3.18.7. However, another 3.4.2 build
978 does not exhibit the bug.
980 Some window managers (Xfce) apparently work around this failure by
981 cropping the menu bar. With other windows managers, it's possible to
982 shrink the frame manually after the problem occurs, e.g. by dragging the
983 frame's border with the mouse. However, some window managers have been
984 reported to refuse such attempts and snap back to the width needed to
985 show the full menu bar (wmii) or at least cause the screen to flicker
986 during such resizing attempts (i3, IceWM).
988 See also http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15700,
989 http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22000,
990 http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22898 and
991 http://lists.gnu.org/archive/html/emacs-devel/2016-07/msg00154.html.
993 *** Metacity: Resizing Emacs or ALT-Tab causes X to be unresponsive.
995 This happens sometimes when using Metacity. Resizing Emacs or ALT-Tab:bing
996 makes the system unresponsive to the mouse or the keyboard. Killing Emacs
997 or shifting out from X and back again usually cures it (i.e. Ctrl-Alt-F1
998 and then Alt-F7). A bug for it is here:
999 https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/231034.
1000 Note that a permanent fix seems to be to disable "assistive technologies".
1002 *** Gnome: Emacs receives input directly from the keyboard, bypassing XIM.
1004 This seems to happen when gnome-settings-daemon version 2.12 or later
1005 is running. If gnome-settings-daemon is not running, Emacs receives
1006 input through XIM without any problem. Furthermore, this seems only
1007 to happen in *.UTF-8 locales; zh_CN.GB2312 and zh_CN.GBK locales, for
1008 example, work fine. A bug report has been filed in the Gnome
1009 bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=357032
1011 *** Gnome: Emacs's xterm-mouse-mode doesn't work on the Gnome terminal.
1013 A symptom of this bug is that double-clicks insert a control sequence
1014 into the buffer. The reason this happens is an apparent
1015 incompatibility of the Gnome terminal with Xterm, which also affects
1016 other programs using the Xterm mouse interface. A problem report has
1019 *** KDE: When running on KDE, colors or fonts are not as specified for Emacs,
1022 For example, you could see background you set for Emacs only in the
1023 empty portions of the Emacs display, while characters have some other
1026 This happens because KDE's defaults apply its color and font
1027 definitions even to applications that weren't compiled for KDE. The
1028 solution is to uncheck the "Apply fonts and colors to non-KDE apps"
1029 option in Preferences->Look&Feel->Style (KDE 2). In KDE 3, this option
1030 is in the "Colors" section, rather than "Style".
1032 Alternatively, if you do want the KDE defaults to apply to other
1033 applications, but not to Emacs, you could modify the file 'Emacs.ad'
1034 (should be in the '/usr/share/apps/kdisplay/app-defaults/' directory)
1035 so that it doesn't set the default background and foreground only for
1036 Emacs. For example, make sure the following resources are either not
1037 present or commented out:
1039 Emacs.default.attributeForeground
1040 Emacs.default.attributeBackground
1044 It is also reported that a bug in the gtk-engines-qt engine can cause this if
1045 Emacs is compiled with Gtk+.
1046 The bug is fixed in version 0.7 or newer of gtk-engines-qt.
1048 *** KDE: Emacs hangs on KDE when a large portion of text is killed.
1050 This is caused by a bug in the KDE applet 'klipper' which periodically
1051 requests the X clipboard contents from applications. Early versions
1052 of klipper don't implement the ICCCM protocol for large selections,
1053 which leads to Emacs being flooded with selection requests. After a
1054 while, Emacs may print a message:
1056 Timed out waiting for property-notify event
1058 A workaround is to not use 'klipper'. Upgrading 'klipper' to the one
1059 coming with KDE 3.3 or later also solves the problem.
1061 *** KDE / Plasma 5: Emacs exhausts memory and needs to be killed
1063 This problem occurs when large selections contain mixed line endings
1064 (i.e. the buffer has LF line endings, but in some parts CRLF is used).
1065 The source of the problem is currently under investigation, older
1066 versions of Emacs up to 24.5 just hang for a few seconds and then
1067 return with the message "Timed out waiting for property-notify event"
1068 as described in the previous note. As a workaround, go to the
1069 settings dialog for the Clipboard widget and select the option "Ignore
1072 Note: Plasma 5 has replaced the separate klipper process from earlier
1073 KDE versions with functionality directly integrated into plasmashell,
1074 so even if you've previously did not use klipper this will affect you.
1075 Also, all configuration you might have done to klipper is not used by
1076 the new Clipboard widget / plasmoid since it uses its own settings.
1077 You can hide the Clipboard widget by removing its entry from the
1078 system tray settings "Extra Items", but it's not clear if the
1079 underlying functionality in plasmashell gets fully disabled as well.
1080 At least a restart of plasmashell is required for the clipboard
1081 history to be cleared.
1083 *** CDE: Frames may cover dialogs they created when using CDE.
1085 This can happen if you have "Allow Primary Windows On Top" enabled which
1086 seems to be the default in the Common Desktop Environment.
1087 To change, go in to "Desktop Controls" -> "Window Style Manager"
1088 and uncheck "Allow Primary Windows On Top".
1090 *** Xaw3d : When using Xaw3d scroll bars without arrows, the very first mouse
1091 click in a scroll bar might be ignored by the scroll bar widget. This
1092 is probably a bug in Xaw3d; when Xaw3d is compiled with arrows, the
1095 *** Xaw: There are known binary incompatibilities between Xaw, Xaw3d, neXtaw,
1096 XawM and the few other derivatives of Xaw. So when you compile with
1097 one of these, it may not work to dynamically link with another one.
1098 For example, strange problems, such as Emacs exiting when you type
1099 "C-x 1", were reported when Emacs compiled with Xaw3d and libXaw was
1100 used with neXtaw at run time.
1102 The solution is to rebuild Emacs with the toolkit version you actually
1103 want to use, or set LD_PRELOAD to preload the same toolkit version you
1106 *** Open Motif: Problems with file dialogs in Emacs built with Open Motif.
1108 When Emacs 21 is built with Open Motif 2.1, it can happen that the
1109 graphical file dialog boxes do not work properly. The "OK", "Filter"
1110 and "Cancel" buttons do not respond to mouse clicks. Dragging the
1111 file dialog window usually causes the buttons to work again.
1113 As a workaround, you can try building Emacs using Motif or LessTif instead.
1115 Another workaround is not to use the mouse to trigger file prompts,
1116 but to use the keyboard. This way, you will be prompted for a file in
1117 the minibuffer instead of a graphical file dialog.
1119 *** LessTif: Problems in Emacs built with LessTif.
1121 The problems seem to depend on the version of LessTif and the Motif
1122 emulation for which it is set up.
1124 Only the Motif 1.2 emulation seems to be stable enough in LessTif.
1125 LessTif 0.92-17's Motif 1.2 emulation seems to work okay on FreeBSD.
1126 On GNU/Linux systems, lesstif-0.92.6 configured with "./configure
1127 --enable-build-12 --enable-default-12" is reported to be the most
1128 successful. The binary GNU/Linux package
1129 lesstif-devel-0.92.0-1.i386.rpm was reported to have problems with
1132 On some systems, Emacs occasionally locks up, grabbing all mouse and
1133 keyboard events. We don't know what causes these problems; they are
1134 not reproducible by Emacs developers.
1136 *** Motif: The Motif version of Emacs paints the screen a solid color.
1138 This has been observed to result from the following X resource:
1140 Emacs*default.attributeFont: -*-courier-medium-r-*-*-*-140-*-*-*-*-iso8859-*
1142 That the resource has this effect indicates a bug in something, but we
1143 do not know what. If it is an Emacs bug, we hope someone can
1144 explain what the bug is so we can fix it. In the mean time, removing
1145 the resource prevents the problem.
1147 ** General X problems
1149 *** Redisplay using X is much slower than previous Emacs versions.
1151 We've noticed that certain X servers draw the text much slower when
1152 scroll bars are on the left. We don't know why this happens. If this
1153 happens to you, you can work around it by putting the scroll bars
1154 on the right (as they were in Emacs 19).
1156 Here's how to do this:
1158 (set-scroll-bar-mode 'right)
1160 If you're not sure whether (or how much) this problem affects you,
1161 try that and see how much difference it makes. To set things back
1164 (set-scroll-bar-mode 'left)
1166 *** Error messages about undefined colors on X.
1168 The messages might say something like this:
1170 Unable to load color "grey95"
1172 (typically, in the '*Messages*' buffer), or something like this:
1174 Error while displaying tooltip: (error Undefined color lightyellow)
1176 These problems could happen if some other X program has used up too
1177 many colors of the X palette, leaving Emacs with insufficient system
1178 resources to load all the colors it needs.
1180 A solution is to exit the offending X programs before starting Emacs.
1182 "undefined color" messages can also occur if the RgbPath entry in the
1183 X configuration file is incorrect, or the rgb.txt file is not where
1184 X expects to find it.
1186 *** Improving performance with slow X connections.
1188 There are several ways to improve this performance, any subset of which can
1189 be carried out at the same time:
1191 1) If you don't need X Input Methods (XIM) for entering text in some
1192 language you use, you can improve performance on WAN links by using
1193 the X resource useXIM to turn off use of XIM. This does not affect
1194 the use of Emacs's own input methods, which are part of the Leim
1197 2) If the connection is very slow, you might also want to consider
1198 switching off scroll bars, menu bar, and tool bar. Adding the
1199 following forms to your .emacs file will accomplish that, but only
1200 after the initial frame is displayed:
1202 (scroll-bar-mode -1)
1206 For still quicker startup, put these X resources in your
1207 .Xresources or .Xdefaults file:
1209 Emacs.verticalScrollBars: off
1213 3) Use ssh to forward the X connection, and enable compression on this
1214 forwarded X connection (ssh -XC remotehostname emacs ...).
1216 4) Use lbxproxy on the remote end of the connection. This is an interface
1217 to the low bandwidth X extension in most modern X servers, which
1218 improves performance dramatically, at the slight expense of correctness
1219 of the X protocol. lbxproxy achieves the performance gain by grouping
1220 several X requests in one TCP packet and sending them off together,
1221 instead of requiring a round-trip for each X request in a separate
1222 packet. The switches that seem to work best for emacs are:
1223 -noatomsfile -nowinattr -cheaterrors -cheatevents
1224 Note that the -nograbcmap option is known to cause problems.
1225 For more about lbxproxy, see:
1226 http://www.x.org/archive/X11R6.8.0/doc/lbxproxy.1.html
1228 5) If copying and killing is slow, try to disable the interaction with the
1229 native system's clipboard by adding these lines to your .emacs file:
1230 (setq interprogram-cut-function nil)
1231 (setq interprogram-paste-function nil)
1233 *** Emacs gives the error, Couldn't find per display information.
1235 This can result if the X server runs out of memory because Emacs uses
1236 a large number of fonts. On systems where this happens, C-h h is
1239 We do not know of a way to prevent the problem.
1241 *** Emacs does not notice when you release the mouse.
1243 There are reports that this happened with (some) Microsoft mice and
1244 that replacing the mouse made it stop.
1246 *** You can't select from submenus (in the X toolkit version).
1248 On certain systems, mouse-tracking and selection in top-level menus
1249 works properly with the X toolkit, but neither of them works when you
1250 bring up a submenu (such as Bookmarks or Compare or Apply Patch, in
1253 This works on most systems. There is speculation that the failure is
1254 due to bugs in old versions of X toolkit libraries, but no one really
1255 knows. If someone debugs this and finds the precise cause, perhaps a
1256 workaround can be found.
1258 *** An error message such as 'X protocol error: BadMatch (invalid
1259 parameter attributes) on protocol request 93'.
1261 This comes from having an invalid X resource, such as
1263 (which is invalid because it specifies a color name for something
1264 that isn't a color.)
1266 The fix is to correct your X resources.
1268 *** Slow startup on X11R6 with X windows.
1270 If Emacs takes two minutes to start up on X11R6, see if your X
1271 resources specify any Adobe fonts. That causes the type-1 font
1272 renderer to start up, even if the font you asked for is not a type-1
1275 One way to avoid this problem is to eliminate the type-1 fonts from
1276 your font path, like this:
1278 xset -fp /usr/X11R6/lib/X11/fonts/Type1/
1280 *** Pull-down menus appear in the wrong place, in the toolkit version of Emacs.
1282 An X resource of this form can cause the problem:
1284 Emacs*geometry: 80x55+0+0
1286 This resource is supposed to apply, and does apply, to the menus
1287 individually as well as to Emacs frames. If that is not what you
1288 want, rewrite the resource.
1290 To check thoroughly for such resource specifications, use 'xrdb
1291 -query' to see what resources the X server records, and also look at
1292 the user's ~/.Xdefaults and ~/.Xdefaults-* files.
1294 *** Emacs running under X Window System does not handle mouse clicks.
1295 *** 'emacs -geometry 80x20' finds a file named '80x20'.
1297 One cause of such problems is having (setq term-file-prefix nil) in
1298 your .emacs file. Another cause is a bad value of EMACSLOADPATH in
1301 *** X doesn't work if DISPLAY uses a hostname.
1303 People have reported kernel bugs in certain systems that cause Emacs
1304 not to work with X if DISPLAY is set using a host name. But
1305 the problem does not occur if DISPLAY is set to 'unix:0.0'. I think
1306 the bug has to do with SIGIO or FIONREAD.
1308 You may be able to compensate for the bug by doing (set-input-mode nil nil).
1309 However, that has the disadvantage of turning off interrupts, so that
1310 you are unable to quit out of a Lisp program by typing C-g.
1312 *** Prevent double pastes in X
1314 The problem: a region, such as a command, is pasted twice when you copy
1315 it with your mouse from GNU Emacs to an xterm or an RXVT shell in X.
1316 The solution: try the following in your X configuration file,
1317 /etc/X11/xorg.conf This should enable both PS/2 and USB mice for
1318 single copies. You do not need any other drivers or options.
1320 Section "InputDevice"
1321 Identifier "Generic Mouse"
1323 Option "Device" "/dev/input/mice"
1326 *** Emacs is slow to exit in X
1328 After you use e.g. C-x C-c to exit, it takes many seconds before the
1329 Emacs window disappears. If Emacs was started from a terminal, you
1332 Error saving to X clipboard manager.
1333 If the problem persists, set 'x-select-enable-clipboard-manager' to nil.
1335 As the message suggests, this problem occurs when Emacs thinks you
1336 have a clipboard manager program running, but has trouble contacting it.
1337 If you don't want to use a clipboard manager, you can set the
1338 suggested variable. Or you can make Emacs not wait so long by
1339 reducing the value of 'x-selection-timeout', either in .emacs or with
1342 Sometimes this problem is due to a bug in your clipboard manager.
1343 Updating to the latest version of the manager can help.
1344 For example, in the Xfce 4.8 desktop environment, the clipboard
1345 manager in versions of xfce4-settings-helper before 4.8.2 is buggy;
1346 https://bugzilla.xfce.org/show_bug.cgi?id=7588 .
1348 *** Warning messages when running in Ubuntu
1350 When you start Emacs you may see something like this:
1352 (emacs:2286): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion
1353 'GTK_IS_MENU_SHELL(menu)' failed
1355 This happens if the Emacs binary has been renamed. The cause is the Ubuntu
1356 appmenu concept. It tries to track Emacs menus and show them in the top
1357 panel, instead of in each Emacs window. This is not properly implemented,
1358 so it fails for Emacs. The order of menus is wrong, and things like copy/paste
1359 that depend on what state Emacs is in are usually wrong (i.e. paste disabled
1360 even if you should be able to paste, and similar).
1362 You can get back menus on each frame by starting emacs like this:
1363 % env UBUNTU_MENUPROXY= emacs
1365 * Runtime problems on character terminals
1367 ** The meta key does not work on xterm.
1369 Typing M-x rings the terminal bell, and inserts a string like ";120~".
1370 For recent xterm versions (>= 216), Emacs uses xterm's modifyOtherKeys
1371 feature to generate strings for key combinations that are not
1372 otherwise usable. One circumstance in which this can cause problems
1373 is if you have specified the X resource
1375 xterm*VT100.Translations
1377 to contain translations that use the meta key. Then xterm will not
1378 use meta in modified function-keys, which confuses Emacs. To fix
1379 this, you can remove the X resource or put this in your init file:
1381 (xterm-remove-modify-other-keys)
1383 ** Emacs spontaneously displays "I-search: " at the bottom of the screen.
1385 This means that Control-S/Control-Q (XON/XOFF) "flow control" is being
1386 used. C-s/C-q flow control is bad for Emacs editors because it takes
1387 away C-s and C-q as user commands. Since editors do not output long
1388 streams of text without user commands, there is no need for a
1389 user-issuable "stop output" command in an editor; therefore, a
1390 properly designed flow control mechanism would transmit all possible
1391 input characters without interference. Designing such a mechanism is
1392 easy, for a person with at least half a brain.
1394 There are three possible reasons why flow control could be taking place:
1396 1) Terminal has not been told to disable flow control
1397 2) Insufficient padding for the terminal in use
1398 3) Some sort of terminal concentrator or line switch is responsible
1400 First of all, many terminals have a set-up mode which controls whether
1401 they generate XON/XOFF flow control characters. This must be set to
1402 "no XON/XOFF" in order for Emacs to work. (For example, on a VT220
1403 you may select "No XOFF" in the setup menu.) Sometimes there is an
1404 escape sequence that the computer can send to turn flow control off
1405 and on. If so, perhaps the termcap 'ti' string should turn flow
1406 control off, and the 'te' string should turn it on.
1408 Once the terminal has been told "no flow control", you may find it
1409 needs more padding. The amount of padding Emacs sends is controlled
1410 by the termcap entry for the terminal in use, and by the output baud
1411 rate as known by the kernel. The shell command 'stty' will print
1412 your output baud rate; 'stty' with suitable arguments will set it if
1413 it is wrong. Setting to a higher speed causes increased padding. If
1414 the results are wrong for the correct speed, there is probably a
1415 problem in the termcap entry. You must speak to a local Unix wizard
1416 to fix this. Perhaps you are just using the wrong terminal type.
1418 For terminals that lack a "no flow control" mode, sometimes just
1419 giving lots of padding will prevent actual generation of flow control
1420 codes. You might as well try it.
1422 If you are really unlucky, your terminal is connected to the computer
1423 through a concentrator which sends XON/XOFF flow control to the
1424 computer, or it insists on sending flow control itself no matter how
1425 much padding you give it. Unless you can figure out how to turn flow
1426 control off on this concentrator (again, refer to your local wizard),
1427 you are screwed! You should have the terminal or concentrator
1428 replaced with a properly designed one. In the mean time, some drastic
1429 measures can make Emacs semi-work.
1431 You can make Emacs ignore C-s and C-q and let the operating system
1432 handle them. To do this on a per-session basis, just type M-x
1433 enable-flow-control RET. You will see a message that C-\ and C-^ are
1434 now translated to C-s and C-q. (Use the same command M-x
1435 enable-flow-control to turn *off* this special mode. It toggles flow
1438 If C-\ and C-^ are inconvenient for you (for example, if one of them
1439 is the escape character of your terminal concentrator), you can choose
1440 other characters by setting the variables flow-control-c-s-replacement
1441 and flow-control-c-q-replacement. But choose carefully, since all
1442 other control characters are already used by emacs.
1444 IMPORTANT: if you type C-s by accident while flow control is enabled,
1445 Emacs output will freeze, and you will have to remember to type C-q in
1448 If you work in an environment where a majority of terminals of a
1449 certain type are flow control hobbled, you can use the function
1450 'enable-flow-control-on' to turn on this flow control avoidance scheme
1451 automatically. Here is an example:
1453 (enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
1455 If this isn't quite correct (e.g. you have a mixture of flow-control hobbled
1456 and good vt200 terminals), you can still run enable-flow-control
1459 I have no intention of ever redesigning the Emacs command set for the
1460 assumption that terminals use C-s/C-q flow control. XON/XOFF flow
1461 control technique is a bad design, and terminals that need it are bad
1462 merchandise and should not be purchased. Now that X is becoming
1463 widespread, XON/XOFF seems to be on the way out. If you can get some
1464 use out of GNU Emacs on inferior terminals, more power to you, but I
1465 will not make Emacs worse for properly designed systems for the sake
1466 of inferior systems.
1468 ** Control-S and Control-Q commands are ignored completely.
1470 For some reason, your system is using brain-damaged C-s/C-q flow
1471 control despite Emacs's attempts to turn it off. Perhaps your
1472 terminal is connected to the computer through a concentrator
1473 that wants to use flow control.
1475 You should first try to tell the concentrator not to use flow control.
1476 If you succeed in this, try making the terminal work without
1477 flow control, as described in the preceding section.
1479 If that line of approach is not successful, map some other characters
1480 into C-s and C-q using keyboard-translate-table. The example above
1481 shows how to do this with C-^ and C-\.
1483 ** Screen is updated wrong, but only on one kind of terminal.
1485 This could mean that the termcap entry you are using for that
1486 terminal is wrong, or it could mean that Emacs has a bug handling
1487 the combination of features specified for that terminal.
1489 The first step in tracking this down is to record what characters
1490 Emacs is sending to the terminal. Execute the Lisp expression
1491 (open-termscript "./emacs-script") to make Emacs write all
1492 terminal output into the file ~/emacs-script as well; then do
1493 what makes the screen update wrong, and look at the file
1494 and decode the characters using the manual for the terminal.
1495 There are several possibilities:
1497 1) The characters sent are correct, according to the terminal manual.
1499 In this case, there is no obvious bug in Emacs, and most likely you
1500 need more padding, or possibly the terminal manual is wrong.
1502 2) The characters sent are incorrect, due to an obscure aspect
1503 of the terminal behavior not described in an obvious way by termcap.
1505 This case is hard. It will be necessary to think of a way for
1506 Emacs to distinguish between terminals with this kind of behavior
1507 and other terminals that behave subtly differently but are
1508 classified the same by termcap; or else find an algorithm for
1509 Emacs to use that avoids the difference. Such changes must be
1510 tested on many kinds of terminals.
1512 3) The termcap entry is wrong.
1514 See the file etc/TERMS for information on changes
1515 that are known to be needed in commonly used termcap entries
1516 for certain terminals.
1518 4) The characters sent are incorrect, and clearly cannot be
1519 right for any terminal with the termcap entry you were using.
1521 This is unambiguously an Emacs bug, and can probably be fixed
1522 in termcap.c, tparam.c, term.c, scroll.c, cm.c or dispnew.c.
1524 ** Control-S and Control-Q commands are ignored completely on a net connection.
1526 Some versions of rlogin (and possibly telnet) do not pass flow
1527 control characters to the remote system to which they connect.
1528 On such systems, emacs on the remote system cannot disable flow
1529 control on the local system. Sometimes 'rlogin -8' will avoid this problem.
1531 One way to cure this is to disable flow control on the local host
1532 (the one running rlogin, not the one running rlogind) using the
1533 stty command, before starting the rlogin process. On many systems,
1534 "stty start u stop u" will do this. On some systems, use
1535 "stty -ixon" instead.
1537 Some versions of tcsh will prevent even this from working. One way
1538 around this is to start another shell before starting rlogin, and
1539 issue the stty command to disable flow control from that shell.
1541 If none of these methods work, the best solution is to type
1542 M-x enable-flow-control at the beginning of your emacs session, or
1543 if you expect the problem to continue, add a line such as the
1544 following to your .emacs (on the host running rlogind):
1546 (enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
1548 See the entry about spontaneous display of I-search (above) for more info.
1550 ** Output from Control-V is slow.
1552 On many bit-map terminals, scrolling operations are fairly slow.
1553 Often the termcap entry for the type of terminal in use fails
1554 to inform Emacs of this. The two lines at the bottom of the screen
1555 before a Control-V command are supposed to appear at the top after
1556 the Control-V command. If Emacs thinks scrolling the lines is fast,
1557 it will scroll them to the top of the screen.
1559 If scrolling is slow but Emacs thinks it is fast, the usual reason is
1560 that the termcap entry for the terminal you are using does not
1561 specify any padding time for the 'al' and 'dl' strings. Emacs
1562 concludes that these operations take only as much time as it takes to
1563 send the commands at whatever line speed you are using. You must
1564 fix the termcap entry to specify, for the 'al' and 'dl', as much
1565 time as the operations really take.
1567 Currently Emacs thinks in terms of serial lines which send characters
1568 at a fixed rate, so that any operation which takes time for the
1569 terminal to execute must also be padded. With bit-map terminals
1570 operated across networks, often the network provides some sort of
1571 flow control so that padding is never needed no matter how slow
1572 an operation is. You must still specify a padding time if you want
1573 Emacs to realize that the operation takes a long time. This will
1574 cause padding characters to be sent unnecessarily, but they do
1575 not really cost much. They will be transmitted while the scrolling
1576 is happening and then discarded quickly by the terminal.
1578 Most bit-map terminals provide commands for inserting or deleting
1579 multiple lines at once. Define the 'AL' and 'DL' strings in the
1580 termcap entry to say how to do these things, and you will have
1581 fast output without wasted padding characters. These strings should
1582 each contain a single %-spec saying how to send the number of lines
1583 to be scrolled. These %-specs are like those in the termcap
1586 You should also define the 'IC' and 'DC' strings if your terminal
1587 has a command to insert or delete multiple characters. These
1588 take the number of positions to insert or delete as an argument.
1590 A 'cs' string to set the scrolling region will reduce the amount
1591 of motion you see on the screen when part of the screen is scrolled.
1593 ** You type Control-H (Backspace) expecting to delete characters.
1595 Put 'stty dec' in your .login file and your problems will disappear
1598 The choice of Backspace for erasure was based on confusion, caused by
1599 the fact that backspacing causes erasure (later, when you type another
1600 character) on most display terminals. But it is a mistake. Deletion
1601 of text is not the same thing as backspacing followed by failure to
1602 overprint. I do not wish to propagate this confusion by conforming
1605 For this reason, I believe 'stty dec' is the right mode to use,
1606 and I have designed Emacs to go with that. If there were a thousand
1607 other control characters, I would define Control-h to delete as well;
1608 but there are not very many other control characters, and I think
1609 that providing the most mnemonic possible Help character is more
1610 important than adapting to people who don't use 'stty dec'.
1612 If you are obstinate about confusing buggy overprinting with deletion,
1613 you can redefine Backspace in your .emacs file:
1614 (global-set-key "\b" 'delete-backward-char)
1615 You can probably access help-command via f1.
1617 ** Colors are not available on a tty or in xterm.
1619 Emacs 21 supports colors on character terminals and terminal
1620 emulators, but this support relies on the terminfo or termcap database
1621 entry to specify that the display supports color. Emacs looks at the
1622 "Co" capability for the terminal to find out how many colors are
1623 supported; it should be non-zero to activate the color support within
1624 Emacs. (Most color terminals support 8 or 16 colors.) If your system
1625 uses terminfo, the name of the capability equivalent to "Co" is
1628 In addition to the "Co" capability, Emacs needs the "op" (for
1629 "original pair") capability, which tells how to switch the terminal
1630 back to the default foreground and background colors. Emacs will not
1631 use colors if this capability is not defined. If your terminal entry
1632 doesn't provide such a capability, try using the ANSI standard escape
1633 sequence \E[00m (that is, define a new termcap/terminfo entry and make
1634 it use your current terminal's entry plus \E[00m for the "op"
1637 Finally, the "NC" capability (terminfo name: "ncv") tells Emacs which
1638 attributes cannot be used with colors. Setting this capability
1639 incorrectly might have the effect of disabling colors; try setting
1640 this capability to '0' (zero) and see if that helps.
1642 Emacs uses the database entry for the terminal whose name is the value
1643 of the environment variable TERM. With 'xterm', a common terminal
1644 entry that supports color is 'xterm-color', so setting TERM's value to
1645 'xterm-color' might activate the color support on an xterm-compatible
1648 Beginning with version 22.1, Emacs supports the --color command-line
1649 option which may be used to force Emacs to use one of a few popular
1650 modes for getting colors on a tty. For example, --color=ansi8 sets up
1651 for using the ANSI-standard escape sequences that support 8 colors.
1653 Some modes do not use colors unless you turn on the Font-lock mode.
1654 Some people have long ago set their '~/.emacs' files to turn on
1655 Font-lock on X only, so they won't see colors on a tty. The
1656 recommended way of turning on Font-lock is by typing "M-x
1657 global-font-lock-mode RET" or by customizing the variable
1658 'global-font-lock-mode'.
1660 ** Unexpected characters inserted into the buffer when you start Emacs.
1661 See e.g. <URL:http://debbugs.gnu.org/11129>
1663 This can happen when you start Emacs in -nw mode in an Xterm.
1664 For example, in the *scratch* buffer, you might see something like:
1668 This is more likely to happen if you are using Emacs over a slow
1669 connection, and begin typing before Emacs is ready to respond.
1671 This occurs when Emacs tries to query the terminal to see what
1672 capabilities it supports, and gets confused by the answer.
1673 To avoid it, set xterm-extra-capabilities to a value other than
1674 'check' (the default). See that variable's documentation (in
1675 term/xterm.el) for more details.
1677 * Runtime problems specific to individual Unix variants
1681 *** GNU/Linux: Process output is corrupted.
1683 There is a bug in Linux kernel 2.6.10 PTYs that can cause emacs to
1684 read corrupted process output.
1686 *** GNU/Linux: Remote access to CVS with SSH causes file corruption.
1688 If you access a remote CVS repository via SSH, files may be corrupted
1689 due to bad interaction between CVS, SSH, and libc.
1691 To fix the problem, save the following script into a file, make it
1692 executable, and set CVS_RSH environment variable to the file name of
1696 exec 2> >(exec cat >&2 2>/dev/null)
1699 *** GNU/Linux: Truncated svn annotate output with SSH.
1700 http://debbugs.gnu.org/7791
1702 The symptoms are: you are accessing a svn repository over SSH.
1703 You use vc-annotate on a large (several thousand line) file, and the
1704 result is truncated around the 1000 line mark. It works fine with
1705 other access methods (e.g. http), or from outside Emacs.
1707 This may be a similar libc/SSH issue to the one mentioned above for CVS.
1708 A similar workaround seems to be effective: create a script with the
1709 same contents as the one used above for CVS_RSH, and set the SVN_SSH
1710 environment variable to point to it.
1712 *** GNU/Linux: After upgrading to a newer version of Emacs,
1713 the Meta key stops working.
1715 This was reported to happen on a GNU/Linux system distributed by
1716 Mandrake. The reason is that the previous version of Emacs was
1717 modified by Mandrake to make the Alt key act as the Meta key, on a
1718 keyboard where the Windows key is the one which produces the Meta
1719 modifier. A user who started using a newer version of Emacs, which
1720 was not hacked by Mandrake, expected the Alt key to continue to act as
1721 Meta, and was astonished when that didn't happen.
1723 The solution is to find out what key on your keyboard produces the Meta
1724 modifier, and use that key instead. Try all of the keys to the left
1725 and to the right of the space bar, together with the 'x' key, and see
1726 which combination produces "M-x" in the echo area. You can also use
1727 the 'xmodmap' utility to show all the keys which produce a Meta
1730 xmodmap -pk | grep -Ei "meta|alt"
1732 A more convenient way of finding out which keys produce a Meta modifier
1733 is to use the 'xkbprint' utility, if it's available on your system:
1735 xkbprint 0:0 /tmp/k.ps
1737 This produces a PostScript file '/tmp/k.ps' with a picture of your
1738 keyboard; printing that file on a PostScript printer will show what
1739 keys can serve as Meta.
1741 The 'xkeycaps' also shows a visual representation of the current
1742 keyboard settings. It also allows to modify them.
1744 *** GNU/Linux: slow startup on Linux-based GNU systems.
1746 People using systems based on the Linux kernel sometimes report that
1747 startup takes 10 to 15 seconds longer than 'usual'.
1749 This is because Emacs looks up the host name when it starts.
1750 Normally, this takes negligible time; the extra delay is due to
1751 improper system configuration. This problem can occur for both
1752 networked and non-networked machines.
1754 Here is how to fix the configuration. It requires being root.
1756 **** Networked Case.
1758 First, make sure the files '/etc/hosts' and '/etc/host.conf' both
1759 exist. The first line in the '/etc/hosts' file should look like this
1760 (replace HOSTNAME with your host name):
1764 Also make sure that the '/etc/host.conf' files contains the following
1770 Any changes, permanent and temporary, to the host name should be
1771 indicated in the '/etc/hosts' file, since it acts a limited local
1772 database of addresses and names (e.g., some SLIP connections
1773 dynamically allocate ip addresses).
1775 **** Non-Networked Case.
1777 The solution described in the networked case applies here as well.
1778 However, if you never intend to network your machine, you can use a
1779 simpler solution: create an empty '/etc/host.conf' file. The command
1780 'touch /etc/host.conf' suffices to create the file. The '/etc/hosts'
1781 file is not necessary with this approach.
1783 *** GNU/Linux: Emacs on a tty switches the cursor to large blinking block.
1785 This was reported to happen on some GNU/Linux systems which use
1786 ncurses version 5.0, but could be relevant for other versions as well.
1787 These versions of ncurses come with a 'linux' terminfo entry, where
1788 the "cvvis" capability (termcap "vs") is defined as "\E[?25h\E[?8c"
1789 (show cursor, change size). This escape sequence switches on a
1790 blinking hardware text-mode cursor whose size is a full character
1791 cell. This blinking cannot be stopped, since a hardware cursor
1794 A work-around is to redefine the "cvvis" capability so that it
1795 enables a *software* cursor. The software cursor works by inverting
1796 the colors of the character at point, so what you see is a block
1797 cursor that doesn't blink. For this to work, you need to redefine
1798 the "cnorm" capability as well, so that it operates on the software
1799 cursor instead of the hardware cursor.
1801 To this end, run "infocmp linux > linux-term", edit the file
1802 'linux-term' to make both the "cnorm" and "cvvis" capabilities send
1803 the sequence "\E[?25h\E[?17;0;64c", and then run "tic linux-term" to
1804 produce a modified terminfo entry.
1806 Alternatively, if you want a blinking underscore as your Emacs cursor,
1807 set the 'visible-cursor' variable to nil in your ~/.emacs:
1808 (setq visible-cursor nil)
1810 Still other way is to change the "cvvis" capability to send the
1811 "\E[?25h\E[?0c" command.
1815 *** FreeBSD: Getting a Meta key on the console.
1817 By default, neither Alt nor any other key acts as a Meta key on
1818 FreeBSD, but this can be changed using kbdcontrol(1). Dump the
1819 current keymap to a file with the command
1821 $ kbdcontrol -d >emacs.kbd
1823 Edit emacs.kbd, and give the key you want to be the Meta key the
1824 definition 'meta'. For instance, if your keyboard has a "Windows"
1825 key with scan code 105, change the line for scan code 105 in emacs.kbd
1828 105 meta meta meta meta meta meta meta meta O
1830 to make the Windows key the Meta key. Load the new keymap with
1832 $ kbdcontrol -l emacs.kbd
1836 *** HP/UX : Shell mode gives the message, "`tty`: Ambiguous".
1838 christos@theory.tn.cornell.edu says:
1840 The problem is that in your .cshrc you have something that tries to
1841 execute 'tty'. If you are not running the shell on a real tty then
1842 tty will print "not a tty". Csh expects one word in some places,
1843 but tty is giving it back 3.
1845 The solution is to add a pair of quotes around `tty` to make it a single
1848 if (`tty` == "/dev/console")
1850 should be changed to:
1852 if ("`tty`" == "/dev/console")
1854 Even better, move things that set up terminal sections out of .cshrc
1857 *** HP/UX: 'Pid xxx killed due to text modification or page I/O error'.
1859 On HP/UX, you can get that error when the Emacs executable is on an NFS
1860 file system. HP/UX responds this way if it tries to swap in a page and
1861 does not get a response from the server within a timeout whose default
1862 value is just ten seconds.
1864 If this happens to you, extend the timeout period.
1866 *** HP/UX: The right Alt key works wrong on German HP keyboards (and perhaps
1867 other non-English HP keyboards too).
1869 This is because HP-UX defines the modifiers wrong in X. Here is a
1870 shell script to fix the problem; be sure that it is run after VUE
1871 configures the X server.
1873 xmodmap 2> /dev/null - << EOF
1874 keysym Alt_L = Meta_L
1875 keysym Alt_R = Meta_R
1880 keysym Mode_switch = NoSymbol
1882 keysym Meta_R = Mode_switch
1883 add mod2 = Mode_switch
1886 *** HP/UX: Emacs does not recognize the AltGr key.
1888 To fix this, set up a file ~/.dt/sessions/sessionetc with executable
1889 rights, containing this text:
1891 --------------------------------
1892 xmodmap 2> /dev/null - << EOF
1893 keysym Alt_L = Meta_L
1894 keysym Alt_R = Meta_R
1899 keysym Mode_switch = NoSymbol
1901 keysym Meta_R = Mode_switch
1902 add mod2 = Mode_switch
1904 --------------------------------
1906 *** HP/UX 11.0: Emacs makes HP/UX 11.0 crash.
1908 This is a bug in HPUX; HPUX patch PHKL_16260 is said to fix it.
1912 *** AIX: Trouble using ptys.
1914 People often install the pty devices on AIX incorrectly.
1915 Use 'smit pty' to reinstall them properly.
1917 *** AIXterm: Your Delete key sends a Backspace to the terminal.
1919 The solution is to include in your .Xdefaults the lines:
1921 *aixterm.Translations: #override <Key>BackSpace: string(0x7f)
1922 aixterm*ttyModes: erase ^?
1924 This makes your Backspace key send DEL (ASCII 127).
1926 *** AIX: If linking fails because libXbsd isn't found, check if you
1927 are compiling with the system's 'cc' and CFLAGS containing '-O5'. If
1928 so, you have hit a compiler bug. Please make sure to re-configure
1929 Emacs so that it isn't compiled with '-O5'.
1931 *** AIX 4.3.x or 4.4: Compiling fails.
1933 This could happen if you use /bin/c89 as your compiler, instead of
1934 the default 'cc'. /bin/c89 treats certain warnings, such as benign
1935 redefinitions of macros, as errors, and fails the build. A solution
1936 is to use the default compiler 'cc'.
1938 *** AIX 4: Some programs fail when run in a Shell buffer
1939 with an error message like No terminfo entry for "unknown".
1941 On AIX, many terminal type definitions are not installed by default.
1942 'unknown' is one of them. Install the "Special Generic Terminal
1943 Definitions" to make them defined.
1947 We list bugs in current versions here. See also the section on legacy
1950 *** On Solaris, C-x doesn't get through to Emacs when you use the console.
1952 This is a Solaris feature (at least on Intel x86 cpus). Type C-r
1953 C-r C-t, to toggle whether C-x gets through to Emacs.
1955 *** Problem with remote X server on Suns.
1957 On a Sun, running Emacs on one machine with the X server on another
1958 may not work if you have used the unshared system libraries. This
1959 is because the unshared libraries fail to use YP for host name lookup.
1960 As a result, the host name you specify may not be recognized.
1962 *** Solaris 2.6: Emacs crashes with SIGBUS or SIGSEGV on Solaris after you delete a frame.
1964 We suspect that this is a bug in the X libraries provided by
1965 Sun. There is a report that one of these patches fixes the bug and
1966 makes the problem stop:
1968 105216-01 105393-01 105518-01 105621-01 105665-01 105615-02 105216-02
1969 105667-01 105401-08 105615-03 105621-02 105686-02 105736-01 105755-03
1970 106033-01 105379-01 105786-01 105181-04 105379-03 105786-04 105845-01
1971 105284-05 105669-02 105837-01 105837-02 105558-01 106125-02 105407-01
1973 Another person using a newer system (kernel patch level Generic_105181-06)
1974 suspects that the bug was fixed by one of these more recent patches:
1976 106040-07 SunOS 5.6: X Input & Output Method patch
1977 106222-01 OpenWindows 3.6: filemgr (ff.core) fixes
1978 105284-12 Motif 1.2.7: sparc Runtime library patch
1980 *** Solaris 7 or 8: Emacs reports a BadAtom error (from X)
1982 This happens when Emacs was built on some other version of Solaris.
1983 Rebuild it on Solaris 8.
1985 *** When using M-x dbx with the SparcWorks debugger, the 'up' and 'down'
1986 commands do not move the arrow in Emacs.
1988 You can fix this by adding the following line to '~/.dbxinit':
1990 dbxenv output_short_file_name off
1992 *** On Solaris, CTRL-t is ignored by Emacs when you use
1993 the fr.ISO-8859-15 locale (and maybe other related locales).
1995 You can fix this by editing the file:
1997 /usr/openwin/lib/locale/iso8859-15/Compose
1999 Near the bottom there is a line that reads:
2001 Ctrl<t> <quotedbl> <Y> : "\276" threequarters
2003 while it should read:
2005 Ctrl<T> <quotedbl> <Y> : "\276" threequarters
2007 Note the lower case <t>. Changing this line should make C-t work.
2009 *** On Solaris, Emacs fails to set menu-bar-update-hook on startup, with error
2010 "Error in menu-bar-update-hook: (error Point before start of properties)".
2011 This seems to be a GCC optimization bug that occurs for GCC 4.1.2 (-g
2012 and -g -O2) and GCC 4.2.3 (-g -O and -g -O2). You can fix this by
2013 compiling with GCC 4.2.3 or CC 5.7, with no optimizations.
2015 * Runtime problems specific to MS-Windows
2017 ** Emacs on Windows 9X requires UNICOWS.DLL
2019 If that DLL is not available, Emacs will display an error dialog
2020 stating its absence, and refuse to run.
2022 This is because Emacs 24.4 and later uses functions whose non-stub
2023 implementation is only available in UNICOWS.DLL, which implements the
2024 Microsoft Layer for Unicode on Windows 9X, or "MSLU". This article on
2027 http://msdn.microsoft.com/en-us/goglobal/bb688166.aspx
2029 includes a short description of MSLU and a link where it can be
2032 ** Emacs refuses to start on Windows 9X because ctime64 function is missing
2034 This is a sign that Emacs was compiled with MinGW runtime version
2035 4.0.x or later. These versions of runtime call in their startup code
2036 the ctime64 function, which does not exist in MSVCRT.DLL, the C
2037 runtime shared library, distributed with Windows 9X.
2039 A workaround is to build Emacs with MinGW runtime 3.x (the latest
2042 ** addpm fails to run on Windows NT4, complaining about Shell32.dll
2044 This is likely to happen because Shell32.dll shipped with NT4 lacks
2045 the updates required by Emacs. Installing Internet Explorer 4 solves
2046 the problem. Note that it is NOT enough to install IE6, because doing
2047 so will not install the Shell32.dll update.
2049 ** A few seconds delay is seen at startup and for many file operations
2051 This happens when the Net Logon service is enabled. During Emacs
2052 startup, this service issues many DNS requests looking up for the
2053 Windows Domain Controller. When Emacs accesses files on networked
2054 drives, it automatically logs on the user into those drives, which
2055 again causes delays when Net Logon is running.
2057 The solution seems to be to disable Net Logon with this command typed
2058 at the Windows shell prompt:
2062 To start the service again, type "net start netlogon". (You can also
2063 stop and start the service from the Computer Management application,
2064 accessible by right-clicking "My Computer" or "Computer", selecting
2065 "Manage", then clicking on "Services".)
2067 ** Emacs crashes when exiting the Emacs session
2069 This was reported to happen when some optional DLLs, such as those
2070 used for displaying images or the GnuTLS library or zlib compression
2071 library, which are loaded on-demand, have a runtime dependency on the
2072 libgcc DLL, libgcc_s_dw2-1.dll. The reason seems to be a bug in
2073 libgcc which rears its ugly head whenever the libgcc DLL is loaded
2074 after Emacs has started.
2076 One solution for this problem is to find an alternative build of the
2077 same optional library that does not depend on the libgcc DLL.
2079 Another possibility is to rebuild Emacs with the -shared-libgcc
2080 switch, which will force Emacs to load libgcc_s_dw2-1.dll on startup,
2081 ahead of any optional DLLs loaded on-demand later in the session.
2083 ** File selection dialog opens in incorrect directories
2085 Invoking the file selection dialog on Windows 7 or later shows a
2086 directory that is different from what was passed to 'read-file-name'
2087 or 'x-file-dialog' via their arguments.
2089 This is due to a deliberate change in behavior of the file selection
2090 dialogs introduced in Windows 7. It is explicitly described in the
2091 MSDN documentation of the GetOpenFileName API used by Emacs to pop up
2092 the file selection dialog. For the details, see
2094 http://msdn.microsoft.com/en-us/library/windows/desktop/ms646839%28v=vs.85%29.aspx
2096 The dialog shows the last directory in which the user selected a file
2097 in a previous invocation of the dialog with the same initial
2100 You can reset this "memory" of that directory by invoking the file
2101 selection dialog with a different initial directory.
2103 ** PATH can contain unexpanded environment variables
2105 Old releases of TCC (version 9) and 4NT (up to version 8) do not correctly
2106 expand App Paths entries of type REG_EXPAND_SZ. When Emacs is run from TCC
2107 and such an entry exists for emacs.exe, exec-path will contain the
2108 unexpanded entry. This has been fixed in TCC 10. For more information,
2111 ** Setting w32-pass-rwindow-to-system and w32-pass-lwindow-to-system to nil
2112 does not prevent the Start menu from popping up when the left or right
2113 "Windows" key is pressed.
2115 This was reported to happen when XKeymacs is installed. At least with
2116 XKeymacs Version 3.47, deactivating XKeymacs when Emacs is active is
2117 not enough to avoid its messing with the keyboard input. Exiting
2118 XKeymacs completely is reported to solve the problem.
2120 ** Pasting from Windows clipboard into Emacs doesn't work.
2122 This was reported to be the result of an anti-virus software blocking
2123 the clipboard-related operations when a Web browser is open, for
2124 security reasons. The solution is to close the Web browser while
2125 working in Emacs, or to add emacs.exe to the list of applications that
2126 are allowed to use the clipboard when the Web browser is open.
2128 ** "Pinning" Emacs to the taskbar doesn't work on Windows 10
2130 "Doesn't work" here means that if you invoke Emacs by clicking on the
2131 pinned icon, a separate button appears on the taskbar, instead of the
2132 expected effect of the icon you clicked on being converted to that
2135 This is due to a bug in early versions of Windows 10, reportedly fixed
2136 in build 1511 of Windows 10 (a.k.a. "Windows 10 SP1"). If you cannot
2137 upgrade, read the work-around described below.
2139 First, be sure to edit the Properties of the pinned icon to invoke
2140 runemacs.exe, not emacs.exe. (The latter will cause an extra cmd
2141 window to appear when you invoke Emacs from the pinned icon.)
2143 But the real cause of the problem is the fact that the pinned icon
2144 (which is really a shortcut in a special directory) lacks a unique
2145 application-defined Application User Model ID (AppUserModelID) that
2146 identifies the current process to the taskbar. This identifier allows
2147 an application to group its associated processes and windows under a
2148 single taskbar button. Emacs on Windows specifies a unique
2149 AppUserModelID when it starts, but Windows 10, unlike previous
2150 versions of MS-Windows, does not propagate that ID to the pinned icon.
2152 To work around this, use some utility, such as 'win7appid', to set the
2153 AppUserModelID of the pinned icon to the string "Gnu.Emacs". The
2154 shortcut files corresponding to icons you pinned are stored by Windows
2155 in the following subdirectory of your user's directory (by default
2156 C:\Users\<UserName>\):
2158 AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar
2160 Look for the file 'emacs.lnk' there.
2162 ** Windows 95 and networking.
2164 To support server sockets, Emacs loads ws2_32.dll. If this file is
2165 missing, all Emacs networking features are disabled.
2167 Old versions of Windows 95 may not have the required DLL. To use
2168 Emacs's networking features on Windows 95, you must install the
2169 "Windows Socket 2" update available from MicroSoft's support Web.
2171 ** Emacs exits with "X protocol error" when run with an X server for MS-Windows.
2173 A certain X server for Windows had a bug which caused this.
2174 Supposedly the newer 32-bit version of this server doesn't have the
2177 ** Emacs crashes when opening a file with a UNC path and rails-mode is loaded.
2179 Loading rails-mode seems to interfere with UNC path handling. This has been
2180 reported as a bug against both Emacs and rails-mode, so look for an updated
2181 rails-mode that avoids this crash, or avoid using UNC paths if using
2184 ** M-x term does not work on MS-Windows.
2186 TTY emulation on Windows is undocumented, and programs such as stty
2187 which are used on POSIX platforms to control tty emulation do not
2188 exist for native windows terminals.
2190 ** Using create-fontset-from-ascii-font or the --font startup parameter
2191 with a Chinese, Japanese or Korean font leads to display problems.
2192 Use a Latin-only font as your default font. If you want control over
2193 which font is used to display Chinese, Japanese or Korean character,
2194 use create-fontset-from-fontset-spec to define a fontset.
2196 ** Frames are not refreshed while dialogs or menus are displayed
2198 This means no redisplay while the File or Font dialog or a pop-up menu
2199 is displayed. This also means tooltips with help text for pop-up
2200 menus are not displayed at all (except in a TTY session, where the help
2201 text is shown in the echo area). This is because message handling
2202 under Windows is synchronous, so we cannot handle repaint (or any
2203 other) messages while waiting for a system function, which popped up
2204 the menu/dialog, to return the result of the dialog or pop-up menu
2207 ** Help text in tooltips does not work on old Windows versions
2209 Windows 95 and Windows NT up to version 4.0 do not support help text
2210 for menus. Help text is only available in later versions of Windows.
2212 ** Display problems with ClearType method of smoothing
2214 When "ClearType" method is selected as the "method to smooth edges of
2215 screen fonts" (in Display Properties, Appearance tab, under
2216 "Effects"), there are various problems related to display of
2217 characters: Bold fonts can be hard to read, small portions of some
2218 characters could appear chopped, etc. This happens because, under
2219 ClearType, characters are drawn outside their advertised bounding box.
2220 Emacs 21 disabled the use of ClearType, whereas Emacs 22 allows it and
2221 has some code to enlarge the width of the bounding box. Apparently,
2222 this display feature needs more changes to get it 100% right. A
2223 workaround is to disable ClearType.
2225 ** Cursor is displayed as a thin vertical bar and cannot be changed
2227 This is known to happen if the Windows Magnifier is turned on before
2228 the Emacs session starts. The Magnifier affects the cursor shape and
2229 prevents any changes to it by setting the 'cursor-type' variable or
2232 The solution is to log off and on again, and then start the Emacs
2233 session only after turning the Magnifier off.
2235 To turn the Windows Magnifier off, click "Start->All Programs", or
2236 "All Apps", depending on your Windows version, then select
2237 "Accessibility" and click "Magnifier". In the Magnifier Settings
2238 dialog that opens, click "Exit".
2240 ** Problems with mouse-tracking and focus management
2242 There are problems with display if mouse-tracking is enabled and the
2243 mouse is moved off a frame, over another frame then back over the first
2244 frame. A workaround is to click the left mouse button inside the frame
2245 after moving back into it.
2247 Some minor flickering still persists during mouse-tracking, although
2248 not as severely as in 21.1.
2250 An inactive cursor remains in an active window after the Windows
2251 Manager driven switch of the focus, until a key is pressed.
2253 ** Problems with Windows input methods
2255 Some of the Windows input methods cause the keyboard to send
2256 characters encoded in the appropriate coding system (e.g., ISO 8859-1
2257 for Latin-1 characters, ISO 8859-8 for Hebrew characters, etc.). To
2258 make these input methods work with Emacs on Windows 9X, you might need
2259 to set the keyboard coding system to the appropriate value after you
2260 activate the Windows input method. For example, if you activate the
2261 Hebrew input method, type this:
2263 C-x RET k hebrew-iso-8bit RET
2265 In addition, to use these Windows input methods, you might need to set
2266 your "Language for non-Unicode programs" (on Windows XP, this is on
2267 the Advanced tab of Regional Settings) to the language of the input
2270 To bind keys that produce non-ASCII characters with modifiers, you
2271 must specify raw byte codes. For instance, if you want to bind
2272 META-a-grave to a command, you need to specify this in your '~/.emacs':
2274 (global-set-key [?\M-\340] ...)
2276 The above example is for the Latin-1 environment where the byte code
2277 of the encoded a-grave is 340 octal. For other environments, use the
2278 encoding appropriate to that environment.
2280 ** Problems with the %b format specifier for format-time-string
2282 The %b specifier for format-time-string does not produce abbreviated
2283 month names with consistent widths for some locales on some versions
2284 of Windows. This is caused by a deficiency in the underlying system
2287 ** Non-US time zones.
2289 Many non-US time zones are implemented incorrectly. This is due to
2290 over-simplistic handling of daylight savings switchovers by the
2293 ** Files larger than 4GB report wrong size in a 32-bit Windows build
2295 Files larger than 4GB cause overflow in the size (represented as a
2296 32-bit integer) reported by 'file-attributes'. This affects Dired as
2297 well, since the Windows port uses a Lisp emulation of 'ls', which relies
2298 on 'file-attributes'.
2300 ** Playing sound doesn't support the :data method
2302 Sound playing is not supported with the ':data DATA' key-value pair.
2303 You _must_ use the ':file FILE' method.
2305 ** Typing Alt-Shift has strange effects on MS-Windows.
2307 This combination of keys is a command to change keyboard layout. If
2308 you proceed to type another non-modifier key before you let go of Alt
2309 and Shift, the Alt and Shift act as modifiers in the usual way. A
2310 more permanent work around is to change it to another key combination,
2311 or disable it in the "Regional and Language Options" applet of the
2312 Control Panel. (The exact sequence of mouse clicks in the "Regional
2313 and Language Options" applet needed to find the key combination that
2314 changes the keyboard layout depends on your Windows version; for XP,
2315 in the Languages tab, click "Details" and then "Key Settings".)
2317 ** Interrupting Cygwin port of Bash from Emacs doesn't work.
2319 Cygwin 1.x builds of the ported Bash cannot be interrupted from the
2320 MS-Windows version of Emacs. This is due to some change in the Bash
2321 port or in the Cygwin library which apparently make Bash ignore the
2322 keyboard interrupt event sent by Emacs to Bash. (Older Cygwin ports
2323 of Bash, up to b20.1, did receive SIGINT from Emacs.)
2325 ** Accessing remote files with ange-ftp hangs the MS-Windows version of Emacs.
2327 If the FTP client is the Cygwin port of GNU 'ftp', this appears to be
2328 due to some bug in the Cygwin DLL or some incompatibility between it
2329 and the implementation of asynchronous subprocesses in the Windows
2330 port of Emacs. Specifically, some parts of the FTP server responses
2331 are not flushed out, apparently due to buffering issues, which
2334 The solution is to downgrade to an older version of the Cygwin DLL
2335 (version 1.3.2 was reported to solve the problem), or use the stock
2336 Windows FTP client, usually found in the 'C:\WINDOWS' or 'C:\WINNT'
2337 directory. To force ange-ftp use the stock Windows client, set the
2338 variable 'ange-ftp-ftp-program-name' to the absolute file name of the
2339 client's executable. For example:
2341 (setq ange-ftp-ftp-program-name "c:/windows/ftp.exe")
2343 If you want to stick with the Cygwin FTP client, you can work around
2344 this problem by putting this in your '.emacs' file:
2346 (setq ange-ftp-ftp-program-args '("-i" "-n" "-g" "-v" "--prompt" "")
2348 ** lpr commands don't work on MS-Windows with some cheap printers.
2350 This problem may also strike other platforms, but the solution is
2351 likely to be a global one, and not Emacs specific.
2353 Many cheap inkjet, and even some cheap laser printers, do not
2354 print plain text anymore, they will only print through graphical
2355 printer drivers. A workaround on MS-Windows is to use Windows's basic
2356 built in editor to print (this is possibly the only useful purpose it
2359 (setq printer-name "") ; notepad takes the default
2360 (setq lpr-command "notepad") ; notepad
2361 (setq lpr-switches nil) ; not needed
2362 (setq lpr-printer-switch "/P") ; run notepad as batch printer
2364 ** Antivirus software interacts badly with the MS-Windows version of Emacs.
2366 The usual manifestation of these problems is that subprocesses don't
2367 work or even wedge the entire system. In particular, "M-x shell RET"
2368 was reported to fail to work. But other commands also sometimes don't
2369 work when an antivirus package is installed.
2371 The solution is to switch the antivirus software to a less aggressive
2372 mode (e.g., disable the "auto-protect" feature), or even uninstall
2373 or disable it entirely.
2375 ** Pressing the mouse button on MS-Windows does not give a mouse-2 event.
2377 This is usually a problem with the mouse driver. Because most Windows
2378 programs do not do anything useful with the middle mouse button, many
2379 mouse drivers allow you to define the wheel press to do something
2380 different. Some drivers do not even have the option to generate a
2381 middle button press. In such cases, setting the wheel press to
2382 "scroll" sometimes works if you press the button twice. Trying a
2383 generic mouse driver might help.
2385 ** Scrolling the mouse wheel on MS-Windows always scrolls the top window.
2387 This is another common problem with mouse drivers. Instead of
2388 generating scroll events, some mouse drivers try to fake scroll bar
2389 movement. But they are not intelligent enough to handle multiple
2390 scroll bars within a frame. Trying a generic mouse driver might help.
2392 ** Mail sent through Microsoft Exchange in some encodings appears to be
2393 mangled and is not seen correctly in Rmail or Gnus. We don't know
2394 exactly what happens, but it isn't an Emacs problem in cases we've
2397 ** On MS-Windows, you cannot use the right-hand ALT key and the left-hand
2398 CTRL key together to type a Control-Meta character.
2400 This is a consequence of a misfeature beyond Emacs's control.
2402 Under Windows, the AltGr key on international keyboards generates key
2403 events with the modifiers Right-Alt and Left-Ctrl. Since Emacs cannot
2404 distinguish AltGr from an explicit Right-Alt and Left-Ctrl
2405 combination, whenever it sees Right-Alt and Left-Ctrl it assumes that
2406 AltGr has been pressed. The variable 'w32-recognize-altgr' can be set
2407 to nil to tell Emacs that AltGr is really Ctrl and Alt.
2409 ** Under some X-servers running on MS-Windows, Emacs's display is incorrect.
2411 The symptoms are that Emacs does not completely erase blank areas of the
2412 screen during scrolling or some other screen operations (e.g., selective
2413 display or when killing a region). M-x recenter will cause the screen
2414 to be completely redisplayed and the "extra" characters will disappear.
2416 This is known to occur under Exceed 6, and possibly earlier versions
2417 as well; it is reportedly solved in version 6.2.0.16 and later. The
2418 problem lies in the X-server settings.
2420 There are reports that you can solve the problem with Exceed by
2421 running 'Xconfig' from within NT, choosing "X selection", then
2422 un-checking the boxes "auto-copy X selection" and "auto-paste to X
2425 If this does not work, please inform bug-gnu-emacs@gnu.org. Then
2426 please call support for your X-server and see if you can get a fix.
2427 If you do, please send it to bug-gnu-emacs@gnu.org so we can list it here.
2429 * Build-time problems
2433 *** 'configure' warns "accepted by the compiler, rejected by the preprocessor".
2435 This indicates a mismatch between the C compiler and preprocessor that
2436 configure is using. For example, on Solaris 10 trying to use
2437 CC=/opt/SUNWspro/bin/cc (the Sun Studio compiler) together with
2438 CPP=/usr/ccs/lib/cpp can result in errors of this form (you may also
2439 see the error '"/usr/include/sys/isa_defs.h", line 500: undefined control').
2441 The solution is to tell configure to use the correct C preprocessor
2442 for your C compiler (CPP="/opt/SUNWspro/bin/cc -E" in the above
2447 *** Building Emacs over NFS fails with "Text file busy".
2449 This was reported to happen when building Emacs on a GNU/Linux system
2450 (Red Hat Linux 6.2) using a build directory automounted from Solaris
2451 (SunOS 5.6) file server, but it might not be limited to that
2452 configuration alone. Presumably, the NFS server doesn't commit the
2453 files' data to disk quickly enough, and the Emacs executable file is
2454 left "busy" for several seconds after Emacs has finished dumping
2455 itself. This causes the subsequent commands which invoke the dumped
2456 Emacs executable to fail with the above message.
2458 In some of these cases, a time skew between the NFS server and the
2459 machine where Emacs is built is detected and reported by GNU Make
2460 (it says that some of the files have modification time in the future).
2461 This might be a symptom of NFS-related problems.
2463 If the NFS server runs on Solaris, apply the Solaris patch 105379-05
2464 (Sunos 5.6: /kernel/misc/nfssrv patch). If that doesn't work, or if
2465 you have a different version of the OS or the NFS server, you can
2466 force the NFS server to use 1KB blocks, which was reported to fix the
2467 problem albeit at a price of slowing down file I/O. You can force 1KB
2468 blocks by specifying the "-o rsize=1024,wsize=1024" options to the
2469 'mount' command, or by adding ",rsize=1024,wsize=1024" to the mount
2470 options in the appropriate system configuration file, such as
2473 Alternatively, when Make fails due to this problem, you could wait for
2474 a few seconds and then invoke Make again. In one particular case,
2475 waiting for 10 or more seconds between the two Make invocations seemed
2476 to work around the problem.
2478 Similar problems can happen if your machine NFS-mounts a directory
2479 onto itself. Suppose the Emacs sources live in '/usr/local/src' and
2480 you are working on the host called 'marvin'. Then an entry in the
2481 '/etc/fstab' file like the following is asking for trouble:
2483 marvin:/usr/local/src /usr/local/src ...options.omitted...
2485 The solution is to remove this line from '/etc/fstab'.
2487 *** Building a 32-bit executable on a 64-bit GNU/Linux architecture.
2489 First ensure that the necessary 32-bit system libraries and include
2490 files are installed. Then use:
2492 env CC="gcc -m32" ./configure --build=i386-linux-gnu --x-libraries=/usr/lib
2494 (using the location of the 32-bit X libraries on your system).
2496 *** Building on FreeBSD 11 fails at link time due to unresolved symbol
2498 The symbol is sendmmsg@FBSD_1.4. This is due to a faulty libgio
2499 library on these systems. The solution is to reconfigure Emacs while
2500 disabling all the features that require libgio: rsvg, dbus, gconf, and
2503 *** Building Emacs for Cygwin can fail with GCC 3
2505 As of Emacs 22.1, there have been stability problems with Cygwin
2506 builds of Emacs using GCC 3. Cygwin users are advised to use GCC 4.
2508 *** Building Emacs 23.3 and later will fail under Cygwin 1.5.19
2510 This is a consequence of a change to src/dired.c on 2010-07-27. The
2511 issue is that Cygwin 1.5.19 did not have d_ino in 'struct dirent'.
2514 http://lists.gnu.org/archive/html/emacs-devel/2010-07/msg01266.html
2516 *** Building the native MS-Windows port fails due to unresolved externals
2518 The linker error messages look like this:
2520 oo-spd/i386/ctags.o:ctags.c:(.text+0x156e): undefined reference to `_imp__re_set_syntax'
2521 collect2: ld returned 1 exit status
2523 This happens because GCC finds an incompatible regex.h header
2524 somewhere on the include path, before the version of regex.h supplied
2525 with Emacs. One such incompatible version of regex.h is part of the
2526 GnuWin32 Regex package.
2528 The solution is to remove the incompatible regex.h from the include
2529 path, when compiling Emacs. Alternatively, re-run the configure.bat
2530 script with the "-isystem C:/GnuWin32/include" switch (adapt for your
2531 system's place where you keep the GnuWin32 include files) -- this will
2532 cause the compiler to search headers in the directories specified by
2533 the Emacs Makefile _before_ it looks in the GnuWin32 include
2536 *** Building the native MS-Windows port with Cygwin GCC can fail.
2538 Emacs may not build using some Cygwin builds of GCC, such as Cygwin
2539 version 1.1.8, using the default configure settings. It appears to be
2540 necessary to specify the -mwin32 flag when compiling, and define
2541 __MSVCRT__, like so:
2543 configure --with-gcc --cflags -mwin32 --cflags -D__MSVCRT__
2545 *** Building the MS-Windows port fails with a CreateProcess failure.
2547 Some versions of mingw32 make on some versions of Windows do not seem
2548 to detect the shell correctly. Try "make SHELL=cmd.exe", or if that
2549 fails, try running make from Cygwin bash instead.
2551 *** Building 'ctags' for MS-Windows with the MinGW port of GCC fails.
2553 This might happen due to a bug in the MinGW header assert.h, which
2554 defines the 'assert' macro with a trailing semi-colon. The following
2555 patch to assert.h should solve this:
2557 *** include/assert.h.orig Sun Nov 7 02:41:36 1999
2558 --- include/assert.h Mon Jan 29 11:49:10 2001
2562 * If not debugging, assert does nothing.
2564 ! #define assert(x) ((void)0);
2566 #else /* debugging enabled */
2570 * If not debugging, assert does nothing.
2572 ! #define assert(x) ((void)0)
2574 #else /* debugging enabled */
2577 *** Building the MS-Windows port with Visual Studio 2005 fails.
2579 Microsoft no longer ships the single threaded version of the C library
2580 with their compiler, and the multithreaded static library is missing
2581 some functions that Microsoft have deemed non-threadsafe. The
2582 dynamically linked C library has all the functions, but there is a
2583 conflict between the versions of malloc in the DLL and in Emacs, which
2584 is not resolvable due to the way Windows does dynamic linking.
2586 We recommend the use of the MinGW port of GCC for compiling Emacs, as
2587 not only does it not suffer these problems, but it is also Free
2588 software like Emacs.
2590 *** Building the MS-Windows port with Visual Studio fails compiling emacs.rc
2592 If the build fails with the following message then the problem
2593 described here most likely applies:
2595 ../nt/emacs.rc(1) : error RC2176 : old DIB in icons\emacs.ico; pass it
2598 The Emacs icon contains a high resolution PNG icon for Vista, which is
2599 not recognized by older versions of the resource compiler. There are
2600 several workarounds for this problem:
2601 1. Use Free MinGW tools to compile, which do not have this problem.
2602 2. Install the latest Windows SDK.
2603 3. Replace emacs.ico with an older or edited icon.
2605 *** Building the MS-Windows port complains about unknown escape sequences.
2607 Errors and warnings can look like this:
2609 w32.c:1959:27: error: \x used with no following hex digits
2610 w32.c:1959:27: warning: unknown escape sequence '\i'
2612 This happens when paths using backslashes are passed to the compiler or
2613 linker (via -I and possibly other compiler flags); when these paths are
2614 included in source code, the backslashes are interpreted as escape sequences.
2615 See http://lists.gnu.org/archive/html/emacs-devel/2010-07/msg00995.html
2617 The fix is to use forward slashes in all paths passed to the compiler.
2621 *** Building Emacs with a system compiler fails to link because of an
2622 undefined symbol such as __eprintf which does not appear in Emacs.
2624 This can happen if some of the libraries linked into Emacs were built
2625 with GCC, but Emacs itself is being linked with a compiler other than
2626 GCC. Object files compiled with GCC might need some helper functions
2627 from libgcc.a, the library which comes with GCC, but the system
2628 compiler does not instruct the linker to search libgcc.a during the
2631 A solution is to link with GCC, like this:
2635 Since the .o object files already exist, this will not recompile Emacs
2636 with GCC, but just restart by trying again to link temacs.
2638 *** Sun with acc: Link failure when using acc on a Sun.
2640 To use acc, you need additional options just before the libraries, such as
2642 /usr/lang/SC2.0.1/values-Xt.o -L/usr/lang/SC2.0.1/cg87 -L/usr/lang/SC2.0.1
2644 and you need to add -lansi just before -lc.
2646 The precise file names depend on the compiler version, so we
2647 cannot easily arrange to supply them.
2649 *** 'tparam' reported as a multiply-defined symbol when linking with ncurses.
2651 This problem results from an incompatible change in ncurses, in
2652 version 1.9.9e approximately. This version is unable to provide a
2653 definition of tparm without also defining tparam. This is also
2654 incompatible with Terminfo; as a result, the Emacs Terminfo support
2655 does not work with this version of ncurses.
2657 The fix is to install a newer version of ncurses, such as version 4.2.
2661 Bootstrapping (compiling the .el files) is normally only necessary
2662 with development builds, since the .elc files are pre-compiled in releases.
2664 *** "No rule to make target" with Ubuntu 8.04 make 3.81-3build1
2666 Compiling the lisp files fails at random places, complaining:
2667 "No rule to make target '/path/to/some/lisp.elc'".
2668 The causes of this problem are not understood. Using GNU make 3.81 compiled
2669 from source, rather than the Ubuntu version, worked.
2670 See <URL:http://debbugs.gnu.org/327>, <URL:http://debbugs.gnu.org/821>.
2674 *** Segfault during 'make'
2676 If Emacs segfaults when 'make' executes one of these commands:
2678 LC_ALL=C ./temacs -batch -l loadup bootstrap
2679 LC_ALL=C ./temacs -batch -l loadup dump
2681 the problem may be due to inadequate workarounds for address space
2682 layout randomization (ASLR), an operating system feature that
2683 randomizes the virtual address space of a process. ASLR is commonly
2684 enabled in Linux and NetBSD kernels, and is intended to deter exploits
2685 of pointer-related bugs in applications. If ASLR is enabled, the
2688 cat /proc/sys/kernel/randomize_va_space # GNU/Linux
2689 sysctl security.pax.aslr.global # NetBSD
2691 outputs a nonzero value.
2693 These segfaults should not occur on most modern systems, because the
2694 Emacs build procedure uses the command 'setfattr' or 'paxctl' to mark
2695 the Emacs executable as requiring non-randomized address space, and
2696 Emacs uses the 'personality' system call to disable address space
2697 randomization when dumping. However, older kernels may not support
2698 'setfattr', 'paxctl', or 'personality', and newer Linux kernels have a
2699 secure computing mode (seccomp) that can be configured to disable the
2702 It may be possible to work around the 'personality' problem in a newer
2703 Linux kernel by configuring seccomp to allow the 'personality' call.
2704 For example, if you are building Emacs under Docker, you can run the
2705 Docker container with a security profile that allows 'personality' by
2706 using Docker's --security-opt option with an appropriate profile; see
2707 <https://docs.docker.com/engine/security/seccomp/>.
2709 To work around the ASLR problem in either an older or a newer kernel,
2710 you can temporarily disable the feature while building Emacs. On
2711 GNU/Linux you can do so using the following command (as root).
2713 echo 0 > /proc/sys/kernel/randomize_va_space
2715 You can re-enable the feature when you are done, by echoing the
2716 original value back to the file. NetBSD uses a different command,
2717 e.g., 'sysctl -w security.pax.aslr.global=0'.
2719 Alternatively, you can try using the 'setarch' command when building
2720 temacs like this, where -R disables address space randomization:
2722 setarch $(uname -m) -R make
2724 ASLR is not the only problem that can break Emacs dumping. Another
2725 issue is that in Red Hat Linux kernels, Exec-shield is enabled by
2726 default, and this creates a different memory layout. Emacs should
2727 handle this at build time, but if this fails the following
2728 instructions may be useful. Exec-shield is enabled on your system if
2730 cat /proc/sys/kernel/exec-shield
2732 prints a nonzero value. You can temporarily disable it as follows:
2734 echo 0 > /proc/sys/kernel/exec-shield
2736 As with randomize_va_space, you can re-enable Exec-shield when you are
2737 done, by echoing the original value back to the file.
2739 *** temacs prints "Pure Lisp storage exhausted".
2741 This means that the Lisp code loaded from the .elc and .el files during
2742 'temacs --batch --load loadup dump' took up more space than was allocated.
2744 This could be caused by
2745 1) adding code to the preloaded Lisp files
2746 2) adding more preloaded files in loadup.el
2747 3) having a site-init.el or site-load.el which loads files.
2748 Note that ANY site-init.el or site-load.el is nonstandard;
2749 if you have received Emacs from some other site and it contains a
2750 site-init.el or site-load.el file, consider deleting that file.
2751 4) getting the wrong .el or .elc files
2752 (not from the directory you expected).
2753 5) deleting some .elc files that are supposed to exist.
2754 This would cause the source files (.el files) to be
2755 loaded instead. They take up more room, so you lose.
2756 6) a bug in the Emacs distribution which underestimates the space required.
2758 If the need for more space is legitimate, change the definition
2759 of PURESIZE in puresize.h.
2761 But in some of the cases listed above, this problem is a consequence
2762 of something else that is wrong. Be sure to check and fix the real problem.
2764 *** OpenBSD 4.0 macppc: Segfault during dumping.
2766 The build aborts with signal 11 when the command './temacs --batch
2767 --load loadup bootstrap' tries to load files.el. A workaround seems
2768 to be to reduce the level of compiler optimization used during the
2769 build (from -O2 to -O1). It is possible this is an OpenBSD
2770 GCC problem specific to the macppc architecture, possibly only
2771 occurring with older versions of GCC (e.g. 3.3.5).
2773 *** openSUSE 10.3: Segfault in bcopy during dumping.
2775 This is due to a bug in the bcopy implementation in openSUSE 10.3.
2776 It is/will be fixed in an openSUSE update.
2780 *** Emacs binary is not in executable format, and cannot be run.
2782 This was reported to happen when Emacs is built in a directory mounted
2783 via NFS, for some combinations of NFS client and NFS server.
2784 Usually, the file 'emacs' produced in these cases is full of
2785 binary null characters, and the 'file' utility says:
2787 emacs: ASCII text, with no line terminators
2789 We don't know what exactly causes this failure. A work-around is to
2790 build Emacs in a directory on a local disk.
2792 *** The dumped Emacs crashes when run, trying to write pure data.
2794 On a system where getpagesize is not a system call, it is defined
2795 as a macro. If the definition (in both unex*.c and malloc.c) is wrong,
2796 it can cause problems like this. You might be able to find the correct
2797 value in the man page for a.out(5).
2799 * Problems on legacy systems
2801 This section covers bugs reported on very old hardware or software.
2802 If you are using hardware and an operating system shipped after 2000,
2803 it is unlikely you will see any of these.
2807 **** Strange results from format %d in a few cases, on a Sun.
2809 Sun compiler version SC3.0 has been found to miscompile part of editfns.c.
2810 The workaround is to compile with some other compiler such as GCC.
2812 **** On Solaris, Emacs dumps core if lisp-complete-symbol is called.
2814 If you compile Emacs with the -fast or -xO4 option with version 3.0.2
2815 of the Sun C compiler, Emacs dumps core when lisp-complete-symbol is
2816 called. The problem does not happen if you compile with GCC.
2818 **** On Solaris, Emacs crashes if you use (display-time).
2820 This can happen if you configure Emacs without specifying the precise
2821 version of Solaris that you are using.
2823 **** Solaris 2.x: GCC complains "64 bit integer types not supported".
2825 This suggests that GCC is not installed correctly. Most likely you
2826 are using GCC 2.7.2.3 (or earlier) on Solaris 2.6 (or later); this
2827 does not work without patching. To run GCC 2.7.2.3 on Solaris 2.6 or
2828 later, you must patch fixinc.svr4 and reinstall GCC from scratch as
2829 described in the Solaris FAQ
2830 <http://www.wins.uva.nl/pub/solaris/solaris2.html>. A better fix is
2831 to upgrade to GCC 2.8.1 or later.
2833 **** Solaris 2.7: Building Emacs with WorkShop Compilers 5.0 98/12/15
2834 C 5.0 failed, apparently with non-default CFLAGS, most probably due to
2835 compiler bugs. Using Sun Solaris 2.7 Sun WorkShop 6 update 1 C
2836 release was reported to work without problems. It worked OK on
2837 another system with Solaris 8 using apparently the same 5.0 compiler
2838 and the default CFLAGS.
2840 **** Solaris 2.x: Emacs dumps core when built with Motif.
2842 The Solaris Motif libraries are buggy, at least up through Solaris 2.5.1.
2843 Install the current Motif runtime library patch appropriate for your host.
2844 (Make sure the patch is current; some older patch versions still have the bug.)
2845 You should install the other patches recommended by Sun for your host, too.
2846 You can obtain Sun patches from ftp://sunsolve.sun.com/pub/patches/;
2847 look for files with names ending in '.PatchReport' to see which patches
2848 are currently recommended for your host.
2850 On Solaris 2.6, Emacs is said to work with Motif when Solaris patch
2851 105284-12 is installed, but fail when 105284-15 is installed.
2852 105284-18 might fix it again.
2854 **** Solaris 2.6 and 7: the Compose key does not work.
2856 This is a bug in Motif in Solaris. Supposedly it has been fixed for
2857 the next major release of Solaris. However, if someone with Sun
2858 support complains to Sun about the bug, they may release a patch.
2859 If you do this, mention Sun bug #4188711.
2861 One workaround is to use a locale that allows non-ASCII characters.
2862 For example, before invoking emacs, set the LC_ALL environment
2863 variable to "en_US" (American English). The directory /usr/lib/locale
2864 lists the supported locales; any locale other than "C" or "POSIX"
2867 pen@lysator.liu.se says (Feb 1998) that the Compose key does work
2868 if you link with the MIT X11 libraries instead of the Solaris X11 libraries.
2870 ** MS-Windows 95, 98, ME, and NT
2872 *** MS-Windows NT/95: Problems running Perl under Emacs
2874 'perl -de 0' just hangs when executed in an Emacs subshell.
2875 The fault lies with Perl (indirectly with Windows NT/95).
2877 The problem is that the Perl debugger explicitly opens a connection to
2878 "CON", which is the DOS/NT equivalent of "/dev/tty", for interacting
2881 On Unix, this is okay, because Emacs (or the shell?) creates a
2882 pseudo-tty so that /dev/tty is really the pipe Emacs is using to
2883 communicate with the subprocess.
2885 On NT, this fails because CON always refers to the handle for the
2886 relevant console (approximately equivalent to a tty), and cannot be
2887 redirected to refer to the pipe Emacs assigned to the subprocess as
2890 A workaround is to modify perldb.pl to use STDIN/STDOUT instead of CON.
2894 *** PERL/LIB/PERLDB.PL.orig Wed May 26 08:24:18 1993
2895 --- PERL/LIB/PERLDB.PL Mon Jul 01 15:28:16 1996
2902 $rcfile="perldb.ini";
2910 $rcfile="perldb.ini";
2915 *** perl/5.001/lib/perl5db.pl.orig Sun Jun 04 21:13:40 1995
2916 --- perl/5.001/lib/perl5db.pl Mon Jul 01 17:00:08 1996
2923 $rcfile="perldb.ini";
2931 $rcfile="perldb.ini";
2935 *** MS-Windows 95: Alt-f6 does not get through to Emacs.
2937 This character seems to be trapped by the kernel in Windows 95.
2938 You can enter M-f6 by typing ESC f6.
2940 *** MS-Windows 95/98/ME: subprocesses do not terminate properly.
2942 This is a limitation of the Operating System, and can cause problems
2943 when shutting down Windows. Ensure that all subprocesses are exited
2944 cleanly before exiting Emacs. For more details, see the Emacs on MS
2945 Windows FAQ (info manual "efaq-w32").
2947 *** MS-Windows 95/98/ME: crashes when Emacs invokes non-existent programs.
2949 When a program you are trying to run is not found on the PATH,
2950 Windows might respond by crashing or locking up your system. In
2951 particular, this has been reported when trying to compile a Java
2952 program in JDEE when javac.exe is installed, but not on the system PATH.
2956 *** When compiling with DJGPP on MS-Windows NT or later, "config msdos" fails.
2958 If the error message is "VDM has been already loaded", this is because
2959 Windows has a program called 'redir.exe' that is incompatible with a
2960 program by the same name supplied with DJGPP, which is used by
2961 config.bat. To resolve this, move the DJGPP's 'bin' subdirectory to
2962 the front of your PATH environment variable.
2964 *** When Emacs compiled with DJGPP runs on Windows 2000 and later, it cannot
2965 find your HOME directory.
2967 This was reported to happen when you click on "Save for future
2968 sessions" button in a Customize buffer. You might see an error
2969 message like this one:
2971 basic-save-buffer-2: c:/FOO/BAR/~dosuser/: no such directory
2973 (The telltale sign is the "~USER" part at the end of the directory
2974 Emacs complains about, where USER is your username or the literal
2975 string "dosuser", which is the default username set up by the DJGPP
2976 startup file DJGPP.ENV.)
2978 This happens when the functions 'user-login-name' and
2979 'user-real-login-name' return different strings for your username as
2980 Emacs sees it. To correct this, make sure both USER and USERNAME
2981 environment variables are set to the same value. Windows 2000 and
2982 later sets USERNAME, so if you want to keep that, make sure USER is
2983 set to the same value. If you don't want to set USER globally, you
2984 can do it in the [emacs] section of your DJGPP.ENV file.
2986 *** When Emacs compiled with DJGPP runs on Vista, it runs out of memory.
2988 If Emacs running on Vista displays "!MEM FULL!" in the mode line, you
2989 are hitting the memory allocation bugs in the Vista DPMI server. See
2990 msdos/INSTALL for how to work around these bugs (search for "Vista").
2992 *** When compiling with DJGPP on MS-Windows 95, Make fails for some targets
2995 This can happen if long file name support (the setting of environment
2996 variable LFN) when Emacs distribution was unpacked and during
2997 compilation are not the same. See msdos/INSTALL for the explanation
2998 of how to avoid this problem.
3000 *** Emacs compiled with DJGPP complains at startup:
3002 "Wrong type of argument: internal-facep, msdos-menu-active-face"
3004 This can happen if you define an environment variable 'TERM'. Emacs
3005 on MSDOS uses an internal terminal emulator which is disabled if the
3006 value of 'TERM' is anything but the string "internal". Emacs then
3007 works as if its terminal were a dumb glass teletype that doesn't
3008 support faces. To work around this, arrange for 'TERM' to be
3009 undefined when Emacs runs. The best way to do that is to add an
3010 [emacs] section to the DJGPP.ENV file which defines an empty value for
3011 'TERM'; this way, only Emacs gets the empty value, while the rest of
3012 your system works as before.
3014 *** MS-DOS: Emacs crashes at startup.
3016 Some users report that Emacs 19.29 requires dpmi memory management,
3017 and crashes on startup if the system does not have it. We don't
3018 know why this happens--perhaps these machines don't have enough real
3019 memory, or perhaps something is wrong in Emacs or the compiler.
3020 However, arranging to use dpmi support is a workaround.
3022 You can find out if you have a dpmi host by running go32 without
3023 arguments; it will tell you if it uses dpmi memory. For more
3024 information about dpmi memory, consult the djgpp FAQ. (djgpp
3025 is the GNU C compiler as packaged for MSDOS.)
3027 Compiling Emacs under MSDOS is extremely sensitive for proper memory
3028 configuration. If you experience problems during compilation, consider
3029 removing some or all memory resident programs (notably disk caches)
3030 and make sure that your memory managers are properly configured. See
3031 the djgpp faq for configuration hints.
3033 *** Emacs compiled with DJGPP for MS-DOS/MS-Windows cannot access files
3034 in the directory with the special name 'dev' under the root of any
3035 drive, e.g. 'c:/dev'.
3037 This is an unfortunate side-effect of the support for Unix-style
3038 device names such as /dev/null in the DJGPP runtime library. A
3039 work-around is to rename the problem directory to another name.
3041 *** MS-DOS: Emacs compiled for MSDOS cannot find some Lisp files, or other
3042 run-time support files, when long filename support is enabled.
3044 Usually, this problem will manifest itself when Emacs exits
3045 immediately after flashing the startup screen, because it cannot find
3046 the Lisp files it needs to load at startup. Redirect Emacs stdout
3047 and stderr to a file to see the error message printed by Emacs.
3049 Another manifestation of this problem is that Emacs is unable to load
3050 the support for editing program sources in languages such as C and Lisp.
3052 This can happen if the Emacs distribution was unzipped without LFN
3053 support, thus causing long filenames to be truncated to the first 6
3054 characters and a numeric tail that Windows 95 normally attaches to it.
3055 You should unzip the files again with a utility that supports long
3056 filenames (such as djtar from DJGPP or InfoZip's UnZip program
3057 compiled with DJGPP v2). The file msdos/INSTALL explains this issue
3060 Another possible reason for such failures is that Emacs compiled for
3061 MSDOS is used on Windows NT, where long file names are not supported
3062 by this version of Emacs, but the distribution was unpacked by an
3063 unzip program that preserved the long file names instead of truncating
3064 them to DOS 8+3 limits. To be useful on NT, the MSDOS port of Emacs
3065 must be unzipped by a DOS utility, so that long file names are
3068 ** Archaic window managers and toolkits
3070 *** Open Look: Under Open Look, the Emacs window disappears when you type M-q.
3072 Some versions of the Open Look window manager interpret M-q as a quit
3073 command for whatever window you are typing at. If you want to use
3074 Emacs with that window manager, you should try to configure the window
3075 manager to use some other command. You can disable the
3076 shortcut keys entirely by adding this line to ~/.OWdefaults:
3078 OpenWindows.WindowMenuAccelerators: False
3080 *** twm: A position you specified in .Xdefaults is ignored, using twm.
3082 twm normally ignores "program-specified" positions.
3083 You can tell it to obey them with this command in your '.twmrc' file:
3085 UsePPosition "on" #allow clients to request a position
3087 ** Bugs related to old DEC hardware
3089 *** The Compose key on a DEC keyboard does not work as Meta key.
3091 This shell command should fix it:
3093 xmodmap -e 'keycode 0xb1 = Meta_L'
3095 *** Keyboard input gets confused after a beep when using a DECserver
3098 This problem seems to be a matter of configuring the DECserver to use
3099 7 bit characters rather than 8 bit characters.
3101 This file is part of GNU Emacs.
3103 GNU Emacs is free software: you can redistribute it and/or modify
3104 it under the terms of the GNU General Public License as published by
3105 the Free Software Foundation, either version 3 of the License, or
3106 (at your option) any later version.
3108 GNU Emacs is distributed in the hope that it will be useful,
3109 but WITHOUT ANY WARRANTY; without even the implied warranty of
3110 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
3111 GNU General Public License for more details.
3113 You should have received a copy of the GNU General Public License
3114 along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
3119 paragraph-separate: "[
\f]*$"