No fonts match `-*-fixed-medium-r-*--6-*-*-*-*-*-iso8859-1'
This happens because some X resource specifies a bad font family for
-Emacs to use. The possible places where this specification might be
-are:
+Emacs to use. The possible places where this specification might be are:
- in your ~/.Xdefaults file
- client-side X resource file, such as ~/Emacs or
- /usr/X11R6/lib/app-defaults/Emacs or
- /usr/X11R6/lib/X11/app-defaults/Emacs
+ /usr/share/X11/app-defaults/Emacs
One of these files might have bad or malformed specification of a
fontset that Emacs should use. To fix the problem, you need to find
systems do), this could happen if the proper version of
ncurses is not visible to the Emacs configure script (i.e. it
cannot be found along the usual path the linker looks for
-libraries). It can happen because your version of ncurses is
+libraries). It can happen because your version of ncurses is
obsolete, or is available only in form of binaries.
The solution is to install an up-to-date version of ncurses in
* Crash bugs
** Emacs crashes when running in a terminal, if compiled with GCC 4.5.0
+
This version of GCC is buggy: see
http://debbugs.gnu.org/6031
untar it :-).
** Emacs can crash when displaying PNG images with transparency.
+
This is due to a bug introduced in ImageMagick 6.8.2-3. The bug should
be fixed in ImageMagick 6.8.3-10. See <URL:http://debbugs.gnu.org/13867>.
it with the Lucid toolkit instead of GTK.
** Emacs crashes when you try to view a file with complex characters.
+
For example, the etc/HELLO file (as shown by C-h h).
The message "symbol lookup error: /usr/bin/emacs: undefined symbol: OTF_open"
is shown in the terminal from which you launched Emacs.
*** The Hyperbole package causes *Help* buffers not to be displayed in
Help mode due to setting `temp-buffer-show-hook' rather than using
-`add-hook'. Using `(add-hook 'temp-buffer-show-hook
-'help-mode-maybe)' after loading Hyperbole should fix this.
+`add-hook'. Using `(add-hook 'temp-buffer-show-hook 'help-mode-finish)'
+after loading Hyperbole should fix this.
** Keyboard problems
4 _rld_text_resolve(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
["/comp2/mtibuild/v73/workarea/v7.3/rld/rld_bridge.s":175, 0xfb6032c]
-(`rld' is the dynamic linker.) We don't know yet why this
+(`rld' is the dynamic linker.) We don't know why this
happens, but setting the environment variable LD_BIND_NOW to 1 (which
forces the dynamic linker to bind all shared objects early on) seems
to work around the problem.
*** Some of the fonts called for in your fontset may not exist on your
X server.
-Each X11 font covers just a fraction of the characters that Emacs
+Each X font covers just a fraction of the characters that Emacs
supports. To display the whole range of Emacs characters requires
many different fonts, collected into a fontset. You can remedy the
problem by installing additional fonts.
The intlfonts distribution includes a full spectrum of fonts that can
display all the characters Emacs supports. The etl-unicode collection
-of fonts (available from <URL:ftp://ftp.x.org/contrib/fonts/> and
-<URL:ftp://ftp.xfree86.org/pub/mirror/X.Org/contrib/fonts/>) includes
+of fonts (available from <URL:ftp://ftp.x.org/contrib/fonts/>) includes
fonts that can display many Unicode characters; they can also be used
by ps-print and ps-mule to print Unicode characters.
-** Under X11, some characters appear improperly aligned in their lines.
+** Under X, some characters appear improperly aligned in their lines.
-You may have bad X11 fonts; try installing the intlfonts distribution
-or the etl-unicode collection (see above).
+You may have bad fonts.
** Under X, an unexpected monospace font is used as the default font.
Another alternative is to avoid a paren in column zero. For example,
in a Lisp string you could precede the paren with a backslash.
-** With certain fonts, when the cursor appears on a character, the
-character doesn't appear--you get a solid box instead.
-
-One user on a Linux-based GNU system reported that this problem went
-away with installation of a new X server. The failing server was
-XFree86 3.1.1. XFree86 3.1.2 works.
-
** Emacs pauses for several seconds when changing the default font.
This has been reported for fvwm 2.2.5 and the window manager of KDE
other sizes as well, your text is corrupted, probably through software
that is not 8-bit clean. If the problem goes away with another font
size, it's probably because some fonts pretend to be ISO-8859-1 fonts
-when they are really ASCII fonts. In particular the schumacher-clean
+when they are really ASCII fonts. In particular the schumacher-clean
fonts have this bug in some versions of X.
To see what glyphs are included in a font, use `xfd', like this:
support.) Files encoded as emacs-mule using oc-unicode aren't
generally read correctly by Emacs 21.
-** After a while, Emacs slips into unibyte mode.
-
-The VM mail package, which is not part of Emacs, sometimes does
- (standard-display-european t)
-That should be changed to
- (standard-display-european 1 t)
-
* X runtime problems
** X keyboard problems
*** You "lose characters" after typing Compose Character key.
This is because the Compose Character key is defined as the keysym
-Multi_key, and Emacs (seeing that) does the proper X11
+Multi_key, and Emacs (seeing that) does the proper X
character-composition processing. If you don't want your Compose key
to do that, you can redefine it with xmodmap.
by another key (e.g. C-\) by modifying ~/.fcitx/config, or be
accustomed to use C-@ for `set-mark-command'.
+*** Link-time optimization with clang doesn't work on Fedora 20.
+
+As of May 2014, Fedora 20 has broken LLVMgold.so plugin support in clang
+(tested with clang-3.4-6.fc20) - `clang --print-file-name=LLVMgold.so'
+prints `LLVMgold.so' instead of full path to plugin shared library, and
+`clang -flto' is unable to find the plugin with the following error:
+
+/bin/ld: error: /usr/bin/../lib/LLVMgold.so: could not load plugin library:
+/usr/bin/../lib/LLVMgold.so: cannot open shared object file: No such file
+or directory
+
+The only way to avoid this is to build your own clang from source code
+repositories, as described at http://clang.llvm.org/get_started.html.
+
*** M-SPC seems to be ignored as input.
See if your X server is set up to use this as a command
*** Under X, C-v and/or other keys don't work.
-These may have been intercepted by your window manager. In
-particular, AfterStep 1.6 is reported to steal C-v in its default
-configuration. Various Meta keys are also likely to be taken by the
-configuration of the `feel'. See the WM's documentation for how to
-change this.
+These may have been intercepted by your window manager.
+See the WM's documentation for how to change this.
*** Clicking C-mouse-2 in the scroll bar doesn't split the window.
This happens sometimes when using Metacity. Resizing Emacs or ALT-Tab:bing
makes the system unresponsive to the mouse or the keyboard. Killing Emacs
-or shifting out from X11 and back again usually cures it (i.e. Ctrl-Alt-F1
+or shifting out from X and back again usually cures it (i.e. Ctrl-Alt-F1
and then Alt-F7). A bug for it is here:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/231034.
Note that a permanent fix seems to be to disable "assistive technologies".
and "Cancel" buttons do not respond to mouse clicks. Dragging the
file dialog window usually causes the buttons to work again.
-The solution is to use LessTif instead. LessTif is a free replacement
-for Motif. See the file INSTALL for information on how to do this.
+As a workaround, you can try building Emacs using Motif or LessTif instead.
Another workaround is not to use the mouse to trigger file prompts,
but to use the keyboard. This way, you will be prompted for a file in
lesstif-devel-0.92.0-1.i386.rpm was reported to have problems with
menu placement.
-On some systems, even with Motif 1.2 emulation, Emacs occasionally
-locks up, grabbing all mouse and keyboard events. We still don't know
-what causes these problems; they are not reproducible by Emacs developers.
+On some systems, Emacs occasionally locks up, grabbing all mouse and
+keyboard events. We don't know what causes these problems; they are
+not reproducible by Emacs developers.
*** Motif: The Motif version of Emacs paints the screen a solid color.
Emacs*default.attributeFont: -*-courier-medium-r-*-*-*-140-*-*-*-*-iso8859-*
That the resource has this effect indicates a bug in something, but we
-do not yet know what. If it is an Emacs bug, we hope someone can
+do not know what. If it is an Emacs bug, we hope someone can
explain what the bug is so we can fix it. In the mean time, removing
the resource prevents the problem.
** General X problems
-*** Redisplay using X11 is much slower than previous Emacs versions.
+*** Redisplay using X is much slower than previous Emacs versions.
We've noticed that certain X servers draw the text much slower when
scroll bars are on the left. We don't know why this happens. If this
When you start Emacs you may see something like this:
-(emacs:2286): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion
+(emacs:2286): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion
`GTK_IS_MENU_SHELL(menu)' failed
This happens if the Emacs binary has been renamed. The cause is the Ubuntu
* Runtime problems on character terminals
** The meta key does not work on xterm.
+
Typing M-x rings the terminal bell, and inserts a string like ";120~".
For recent xterm versions (>= 216), Emacs uses xterm's modifyOtherKeys
feature to generate strings for key combinations that are not
** FreeBSD
-*** FreeBSD 2.1.5: useless symbolic links remain in /tmp or other
-directories that have the +t bit.
-
-This is because of a kernel bug in FreeBSD 2.1.5 (fixed in 2.2).
-Emacs uses symbolic links to implement file locks. In a directory
-with +t bit, the directory owner becomes the owner of the symbolic
-link, so that it cannot be removed by anyone else.
-
-If you don't like those useless links, you can customize
-the option `create-lockfiles'.
-
*** FreeBSD: Getting a Meta key on the console.
By default, neither Alt nor any other key acts as a Meta key on
christos@theory.tn.cornell.edu says:
The problem is that in your .cshrc you have something that tries to
-execute `tty`. If you are not running the shell on a real tty then
-tty will print "not a tty". Csh expects one word in some places,
+execute `tty`. If you are not running the shell on a real tty then
+tty will print "not a tty". Csh expects one word in some places,
but tty is giving it back 3.
The solution is to add a pair of quotes around `tty` to make it a single
add mod2 = Mode_switch
EOF
-*** HP/UX: "Cannot find callback list" messages from dialog boxes in
-Emacs built with Motif.
-
-This problem resulted from a bug in GCC 2.4.5. Newer GCC versions
-such as 2.7.0 fix the problem.
-
*** HP/UX: Emacs does not recognize the AltGr key.
To fix this, set up a file ~/.dt/sessions/sessionetc with executable
** Irix
-*** Irix 6.5: Emacs crashes on the SGI R10K, when compiled with GCC.
-
-This seems to be fixed in GCC 2.95.
-
*** Irix: Trouble using ptys, or running out of ptys.
The program mkpts (which may be in `/usr/adm' or `/usr/sbin') needs to
* Runtime problems specific to MS-Windows
+** Emacs on Windows 9X requires UNICOWS.DLL
+
+If that DLL is not available, Emacs will display an error dialog
+stating its absence, and refuse to run.
+
+This is because Emacs 24.4 and later uses functions whose non-stub
+implementation is only available in UNICOWS.DLL, which implements the
+Microsoft Layer for Unicode on Windows 9X, or "MSLU". This article on
+MSDN:
+
+ http://msdn.microsoft.com/en-us/goglobal/bb688166.aspx
+
+includes a short description of MSLU and a link where it can be
+downloaded.
+
+** A few seconds delay is seen at startup and for many file operations
+
+This happens when the Net Logon service is enabled. During Emacs
+startup, this service issues many DNS requests looking up for the
+Windows Domain Controller. When Emacs accesses files on networked
+drives, it automatically logs on the user into those drives, which
+again causes delays when Net Logon is running.
+
+The solution seems to be to disable Net Logon with this command typed
+at the Windows shell prompt:
+
+ net stop netlogon
+
+To start the service again, type "net start netlogon". (You can also
+stop and start the service from the Computer Management application,
+accessible by right-clicking "My Computer" or "Computer", selecting
+"Manage", then clicking on "Services".)
+
+** Emacs crashes when exiting the Emacs session
+
+This was reported to happen when some optional DLLs, such as those
+used for displaying images or the GnuTLS library, which are loaded
+on-demand, have a runtime dependency on the libgcc DLL,
+libgcc_s_dw2-1.dll. The reason seems to be a bug in libgcc which
+rears its ugly head whenever the libgcc DLL is loaded after Emacs has
+started.
+
+One solution for this problem is to find an alternative build of the
+same optional library that does not depend on the libgcc DLL.
+
+Another possibility is to rebuild Emacs with the -shared-libgcc
+switch, which will force Emacs to load libgcc_s_dw2-1.dll on startup,
+ahead of any optional DLLs loaded on-demand later in the session.
+
** PATH can contain unexpanded environment variables
Old releases of TCC (version 9) and 4NT (up to version 8) do not correctly
** Windows 95 and networking.
-To support server sockets, Emacs 22.1 loads ws2_32.dll. If this file
-is missing, all Emacs networking features are disabled.
+To support server sockets, Emacs loads ws2_32.dll. If this file is
+missing, all Emacs networking features are disabled.
Old versions of Windows 95 may not have the required DLL. To use
Emacs's networking features on Windows 95, you must install the
** Emacs crashes when opening a file with a UNC path and rails-mode is loaded.
-Loading rails-mode seems to interfere with UNC path handling. This has been
+Loading rails-mode seems to interfere with UNC path handling. This has been
reported as a bug against both Emacs and rails-mode, so look for an updated
rails-mode that avoids this crash, or avoid using UNC paths if using
rails-mode.
-** Known problems with the MS-Windows port of Emacs 22.3
+** M-x term does not work on MS-Windows.
-M-x term does not work on MS-Windows. TTY emulation on Windows is
-undocumented, and programs such as stty which are used on posix platforms
-to control tty emulation do not exist for native windows terminals.
+TTY emulation on Windows is undocumented, and programs such as stty
+which are used on posix platforms to control tty emulation do not
+exist for native windows terminals.
-Using create-fontset-from-ascii-font or the --font startup parameter
+** Using create-fontset-from-ascii-font or the --font startup parameter
with a Chinese, Japanese or Korean font leads to display problems.
-Use a Latin-only font as your default font. If you want control over
+Use a Latin-only font as your default font. If you want control over
which font is used to display Chinese, Japanese or Korean character,
use create-fontset-from-fontset-spec to define a fontset.
-Frames are not refreshed while the File or Font dialog or a pop-up menu
-is displayed. This also means help text for pop-up menus is not
-displayed at all. This is because message handling under Windows is
-synchronous, so we cannot handle repaint (or any other) messages while
-waiting for a system function to return the result of the dialog or
-pop-up menu interaction.
+** Frames are not refreshed while dialogs or menus are displayed
+
+This means no redisplay while the File or Font dialog or a pop-up menu
+is displayed. This also means tooltips with help text for pop-up
+menus is not displayed at all (except in a TTY session, where the help
+text is shown in the echo area). This is because message handling
+under Windows is synchronous, so we cannot handle repaint (or any
+other) messages while waiting for a system function, which popped up
+the menu/dialog, to return the result of the dialog or pop-up menu
+interaction.
+
+** Help text in tooltips does not work on old Windows versions
Windows 95 and Windows NT up to version 4.0 do not support help text
for menus. Help text is only available in later versions of Windows.
+** Display problems with ClearType method of smoothing
+
When "ClearType" method is selected as the "method to smooth edges of
screen fonts" (in Display Properties, Appearance tab, under
"Effects"), there are various problems related to display of
this display feature needs more changes to get it 100% right. A
workaround is to disable ClearType.
+** Problems with mouse-tracking and focus management
+
There are problems with display if mouse-tracking is enabled and the
mouse is moved off a frame, over another frame then back over the first
frame. A workaround is to click the left mouse button inside the frame
An inactive cursor remains in an active window after the Windows
Manager driven switch of the focus, until a key is pressed.
-Windows input methods are not recognized by Emacs. However, some
-of these input methods cause the keyboard to send characters encoded
-in the appropriate coding system (e.g., ISO 8859-1 for Latin-1
-characters, ISO 8859-8 for Hebrew characters, etc.). To make these
-input methods work with Emacs, set the keyboard coding system to the
-appropriate value after you activate the Windows input method. For
-example, if you activate the Hebrew input method, type this:
+** Problems with Windows input methods
+
+Some of the Windows input methods cause the keyboard to send
+characters encoded in the appropriate coding system (e.g., ISO 8859-1
+for Latin-1 characters, ISO 8859-8 for Hebrew characters, etc.). To
+make these input methods work with Emacs on Windows 9X, you might need
+to set the keyboard coding system to the appropriate value after you
+activate the Windows input method. For example, if you activate the
+Hebrew input method, type this:
C-x RET k hebrew-iso-8bit RET
-(Emacs ought to recognize the Windows language-change event and set up
-the appropriate keyboard encoding automatically, but it doesn't do
-that yet.) In addition, to use these Windows input methods, you
-should set your "Language for non-Unicode programs" (on Windows XP,
-this is on the Advanced tab of Regional Settings) to the language of
-the input method.
+In addition, to use these Windows input methods, you might need to set
+your "Language for non-Unicode programs" (on Windows XP, this is on
+the Advanced tab of Regional Settings) to the language of the input
+method.
To bind keys that produce non-ASCII characters with modifiers, you
-must specify raw byte codes. For instance, if you want to bind
+must specify raw byte codes. For instance, if you want to bind
META-a-grave to a command, you need to specify this in your `~/.emacs':
(global-set-key [?\M-\340] ...)
of the encoded a-grave is 340 octal. For other environments, use the
encoding appropriate to that environment.
+** Problems with the %b format specifier for format-time-string
+
The %b specifier for format-time-string does not produce abbreviated
month names with consistent widths for some locales on some versions
-of Windows. This is caused by a deficiency in the underlying system
+of Windows. This is caused by a deficiency in the underlying system
library function.
+** Problems with set-time-zone-rule function
+
The function set-time-zone-rule gives incorrect results for many
non-US timezones. This is due to over-simplistic handling of
daylight savings switchovers by the Windows libraries.
+** Files larger than 4GB report wrong size
+
Files larger than 4GB cause overflow in the size (represented as a
32-bit integer) reported by `file-attributes'. This affects Dired as
well, since the Windows port uses a Lisp emulation of `ls' that relies
on `file-attributes'.
+** Playing sound doesn't support the :data method
+
Sound playing is not supported with the `:data DATA' key-value pair.
You _must_ use the `:file FILE' method.
Many cheap inkjet, and even some cheap laser printers, do not
print plain text anymore, they will only print through graphical
-printer drivers. A workaround on MS-Windows is to use Windows' basic
+printer drivers. A workaround on MS-Windows is to use Windows's basic
built in editor to print (this is possibly the only useful purpose it
has):
** Pressing the mouse button on MS-Windows does not give a mouse-2 event.
-This is usually a problem with the mouse driver. Because most Windows
+This is usually a problem with the mouse driver. Because most Windows
programs do not do anything useful with the middle mouse button, many
mouse drivers allow you to define the wheel press to do something
-different. Some drivers do not even have the option to generate a
-middle button press. In such cases, setting the wheel press to
-"scroll" sometimes works if you press the button twice. Trying a
+different. Some drivers do not even have the option to generate a
+middle button press. In such cases, setting the wheel press to
+"scroll" sometimes works if you press the button twice. Trying a
generic mouse driver might help.
** Scrolling the mouse wheel on MS-Windows always scrolls the top window.
-This is another common problem with mouse drivers. Instead of
+This is another common problem with mouse drivers. Instead of
generating scroll events, some mouse drivers try to fake scroll bar
-movement. But they are not intelligent enough to handle multiple
-scroll bars within a frame. Trying a generic mouse driver might help.
+movement. But they are not intelligent enough to handle multiple
+scroll bars within a frame. Trying a generic mouse driver might help.
** Mail sent through Microsoft Exchange in some encodings appears to be
mangled and is not seen correctly in Rmail or Gnus. We don't know
un-checking the boxes "auto-copy X selection" and "auto-paste to X
selection".
-Of this does not work, please inform bug-gnu-emacs@gnu.org. Then
+If this does not work, please inform bug-gnu-emacs@gnu.org. Then
please call support for your X-server and see if you can get a fix.
If you do, please send it to bug-gnu-emacs@gnu.org so we can list it here.
*** Building a 32-bit executable on a 64-bit GNU/Linux architecture.
First ensure that the necessary 32-bit system libraries and include
-files are installed. Then use:
+files are installed. Then use:
- env CC="gcc -m32" ./configure --build=i386-linux-gnu \
- --x-libraries=/usr/X11R6/lib
+ env CC="gcc -m32" ./configure --build=i386-linux-gnu --x-libraries=/usr/lib
(using the location of the 32-bit X libraries on your system).
*** Building the MS-Windows port fails with a CreateProcess failure.
Some versions of mingw32 make on some versions of Windows do not seem
-to detect the shell correctly. Try "make SHELL=cmd.exe", or if that
+to detect the shell correctly. Try "make SHELL=cmd.exe", or if that
fails, try running make from Cygwin bash instead.
*** Building `ctags' for MS-Windows with the MinGW port of GCC fails.
through SDKPAINT
The Emacs icon contains a high resolution PNG icon for Vista, which is
-not recognized by older versions of the resource compiler. There are
+not recognized by older versions of the resource compiler. There are
several workarounds for this problem:
1. Use Free MinGW tools to compile, which do not have this problem.
2. Install the latest Windows SDK.
** Dumping
-*** Linux: Segfault during `make bootstrap' under certain recent versions of the Linux kernel.
-
-With certain recent Linux kernels (like the one of Red Hat Fedora Core
-1 and newer), the new "Exec-shield" functionality is enabled by default, which
-creates a different memory layout that breaks the emacs dumper. Emacs tries
-to handle this at build time, but if the workaround used fails, these
-instructions can be useful.
-The work-around explained here is not enough on Fedora Core 4 (and possible
-newer). Read the next item.
+*** Segfault during `make bootstrap' under the Linux kernel.
-Configure can overcome the problem of exec-shield if the architecture is
-x86 and the program setarch is present. On other architectures no
-workaround is known.
+In Red Hat Linux kernels, "Exec-shield" functionality is enabled by
+default, which creates a different memory layout that can break the
+emacs dumper. Emacs tries to handle this at build time, but if this
+fails, the following instructions may be useful.
-You can check the Exec-shield state like this:
+Exec-shield is enabled on your system if
cat /proc/sys/kernel/exec-shield
-It returns non-zero when Exec-shield is enabled, 0 otherwise. Please
-read your system documentation for more details on Exec-shield and
-associated commands. Exec-shield can be turned off with this command:
+prints a value other than 0. (Please read your system documentation
+for more details on Exec-shield and associated commands.)
- echo "0" > /proc/sys/kernel/exec-shield
+Additionally, Linux kernel versions since 2.6.12 randomize the virtual
+address space of a process by default. If this feature is enabled on
+your system, then
-When Exec-shield is enabled, building Emacs will segfault during the
-execution of this command:
+ cat /proc/sys/kernel/randomize_va_space
- ./temacs --batch --load loadup [dump|bootstrap]
+prints a value other than 0.
-To work around this problem, it is necessary to temporarily disable
-Exec-shield while building Emacs, or, on x86, by using the `setarch'
-command when running temacs like this:
+When these features are enabled, building Emacs may segfault during
+the execution of this command:
- setarch i386 ./temacs --batch --load loadup [dump|bootstrap]
+ ./temacs --batch --load loadup [dump|bootstrap]
+To work around this problem, you can temporarily disable these
+features while building Emacs. You can do so using the following
+commands (as root). Remember to re-enable them when you are done,
+by echoing the original values back to the files.
-*** Fedora Core 4 GNU/Linux: Segfault during dumping.
+ echo 0 > /proc/sys/kernel/exec-shield
+ echo 0 > /proc/sys/kernel/randomize_va_space
-In addition to exec-shield explained above "Linux: Segfault during
-`make bootstrap' under certain recent versions of the Linux kernel"
-item, Linux kernel shipped with Fedora Core 4 randomizes the virtual
-address space of a process. As the result dumping may fail even if
-you turn off exec-shield. In this case, use the -R option to the setarch
-command:
+Or, on x86, you can try using the `setarch' command when running
+temacs, like this:
- setarch i386 -R ./temacs --batch --load loadup [dump|bootstrap]
+ setarch i386 -R ./temacs --batch --load loadup [dump|bootstrap]
or
- setarch i386 -R make bootstrap
-
-*** Fatal signal in the command temacs -l loadup inc dump.
-
-This command is the final stage of building Emacs. It is run by the
-Makefile in the src subdirectory.
-
-It has been known to get fatal errors due to insufficient swapping
-space available on the machine.
-
-On 68000s, it has also happened because of bugs in the
-subroutine `alloca'. Verify that `alloca' works right, even
-for large blocks (many pages).
-
-*** test-distrib says that the distribution has been clobbered.
-*** or, temacs prints "Command key out of range 0-127".
-*** or, temacs runs and dumps emacs, but emacs totally fails to work.
-*** or, temacs gets errors dumping emacs.
-
-This can be because the .elc files have been garbled. Do not be
-fooled by the fact that most of a .elc file is text: these are
-binary files and can contain all 256 byte values.
-
-In particular `shar' cannot be used for transmitting GNU Emacs.
-It typically truncates "lines". What appear to be "lines" in
-a binary file can of course be of any length. Even once `shar'
-itself is made to work correctly, `sh' discards null characters
-when unpacking the shell archive.
-
-I have also seen character \177 changed into \377. I do not know
-what transfer means caused this problem. Various network
-file transfer programs are suspected of clobbering the high bit.
-
-If you have a copy of Emacs that has been damaged in its
-nonprinting characters, you can fix them:
+ setarch i386 -R make
- 1) Record the names of all the .elc files.
- 2) Delete all the .elc files.
- 3) Recompile alloc.c with a value of PURESIZE twice as large.
- (See puresize.h.) You might as well save the old alloc.o.
- 4) Remake emacs. It should work now.
- 5) Running emacs, do Meta-x byte-compile-file repeatedly
- to recreate all the .elc files that used to exist.
- You may need to increase the value of the variable
- max-lisp-eval-depth to succeed in running the compiler interpreted
- on certain .el files. 400 was sufficient as of last report.
- 6) Reinstall the old alloc.o (undoing changes to alloc.c if any)
- and remake temacs.
- 7) Remake emacs. It should work now, with valid .elc files.
+(The -R option disables address space randomization.)
*** temacs prints "Pure Lisp storage exhausted".
-This means that the Lisp code loaded from the .elc and .el files
-during temacs -l loadup inc dump took up more space than was allocated.
+This means that the Lisp code loaded from the .elc and .el files during
+`temacs --batch --load loadup dump' took up more space than was allocated.
This could be caused by
1) adding code to the preloaded Lisp files
This is due to a bug in the bcopy implementation in openSUSE 10.3.
It is/will be fixed in an openSUSE update.
-** Installation
-
-*** On Solaris, use GNU Make when installing an out-of-tree build
-
-The Emacs configuration process allows you to configure the
-build environment so that you can build emacs in a directory
-outside of the distribution tree. When installing Emacs from an
-out-of-tree build directory on Solaris, you may need to use GNU
-make. The make programs bundled with Solaris support the VPATH
-macro but use it differently from the way the VPATH macro is
-used by GNU make. The differences will cause the "make install"
-step to fail, leaving you with an incomplete emacs
-installation. GNU make is available in /usr/sfw/bin on Solaris
-10 and can be installed as /opt/sfw/bin/gmake from the Solaris 9
-Software Companion CDROM.
-
-The problems due to the VPATH processing differences affect only
-out of tree builds so, if you are on a Solaris installation
-without GNU make, you can install Emacs completely by installing
-from a build environment using the original emacs distribution tree.
-
** First execution
*** Emacs binary is not in executable format, and cannot be run.
it can cause problems like this. You might be able to find the correct
value in the man page for a.out (5).
-* Runtime problems on legacy systems
+* Problems on legacy systems
This section covers bugs reported on very old hardware or software.
If you are using hardware and an operating system shipped after 2000,
it is unlikely you will see any of these.
-*** OPENSTEP 4.2: Compiling syntax.c with gcc 2.7.2.1 fails.
-
-The compiler was reported to crash while compiling syntax.c with the
-following message:
-
- cc: Internal compiler error: program cc1obj got fatal signal 11
-
-To work around this, replace the macros UPDATE_SYNTAX_TABLE_FORWARD,
-INC_BOTH, and INC_FROM with functions. To this end, first define 3
-functions, one each for every macro. Here's an example:
-
- static int update_syntax_table_forward(int from)
- {
- return(UPDATE_SYNTAX_TABLE_FORWARD(from));
- }/*update_syntax_table_forward*/
-
-Then replace all references to UPDATE_SYNTAX_TABLE_FORWARD in syntax.c
-with a call to the function update_syntax_table_forward.
-
*** Solaris 2.x
**** Strange results from format %d in a few cases, on a Sun.
-Sun compiler version SC3.0 has been found to miscompile part of
-editfns.c. The workaround is to compile with some other compiler such
-as GCC.
+Sun compiler version SC3.0 has been found to miscompile part of editfns.c.
+The workaround is to compile with some other compiler such as GCC.
**** On Solaris, Emacs dumps core if lisp-complete-symbol is called.
pen@lysator.liu.se says (Feb 1998) that the Compose key does work
if you link with the MIT X11 libraries instead of the Solaris X11 libraries.
-*** HP/UX: Emacs is slow using X11R5.
-
-This happens if you use the MIT versions of the X libraries--it
-doesn't run as fast as HP's version. People sometimes use the version
-because they see the HP version doesn't have the libraries libXaw.a,
-libXmu.a, libXext.a and others. HP/UX normally doesn't come with
-those libraries installed. To get good performance, you need to
-install them and rebuild Emacs.
-
-*** UnixWare 2.1: Error 12 (virtual memory exceeded) when dumping Emacs.
-
-Paul Abrahams (abrahams@acm.org) reports that with the installed
-virtual memory settings for UnixWare 2.1.2, an Error 12 occurs during
-the "make" that builds Emacs, when running temacs to dump emacs. That
-error indicates that the per-process virtual memory limit has been
-exceeded. The default limit is probably 32MB. Raising the virtual
-memory limit to 40MB should make it possible to finish building Emacs.
-
-You can do this with the command `ulimit' (sh) or `limit' (csh).
-But you have to be root to do it.
-
-According to Martin Sohnius, you can also retune this in the kernel:
-
- # /etc/conf/bin/idtune SDATLIM 33554432 ## soft data size limit
- # /etc/conf/bin/idtune HDATLIM 33554432 ## hard "
- # /etc/conf/bin/idtune SVMMSIZE unlimited ## soft process size limit
- # /etc/conf/bin/idtune HVMMSIZE unlimited ## hard "
- # /etc/conf/bin/idbuild -B
-
-(He recommends you not change the stack limit, though.)
-These changes take effect when you reboot.
-
** MS-Windows 95, 98, ME, and NT
*** MS-Windows NT/95: Problems running Perl under Emacs
** Archaic window managers and toolkits
-*** OpenLook: Under OpenLook, the Emacs window disappears when you type M-q.
+*** Open Look: Under Open Look, the Emacs window disappears when you type M-q.
Some versions of the Open Look window manager interpret M-q as a quit
command for whatever window you are typing at. If you want to use
HCoop / bpt / emacs.git / blobdiff