"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "etc/PROBLEMS" between
emacs-27.1.tar.xz and emacs-27.2.tar.xz

About: GNU Emacs - the extensible, customizable, self-documenting real-time display editor.

PROBLEMS  (emacs-27.1.tar.xz):PROBLEMS  (emacs-27.2.tar.xz)
Known Problems with GNU Emacs Known Problems with GNU Emacs
Copyright (C) 1987-1989, 1993-1999, 2001-2020 Free Software Foundation, Copyright (C) 1987-1989, 1993-1999, 2001-2021 Free Software Foundation,
Inc. Inc.
See the end of the file for license conditions. See the end of the file for license conditions.
This file describes various problems that have been encountered This file describes various problems that have been encountered
in compiling, installing and running GNU Emacs. Try doing C-c C-t in compiling, installing and running GNU Emacs. Try doing C-c C-t
and browsing through the outline headers. (See C-h m for help on and browsing through the outline headers. (See C-h m for help on
Outline mode.) Information about systems that are no longer supported, Outline mode.) Information about systems that are no longer supported,
and old Emacs releases, has been removed. Consult older versions of and old Emacs releases, has been removed. Consult older versions of
this file if you are interested in that information. this file if you are interested in that information.
skipping to change at line 695 skipping to change at line 695
gnutls-cli 3.5.3 (2016-08-09) does not generate a "- Handshake was gnutls-cli 3.5.3 (2016-08-09) does not generate a "- Handshake was
completed" message that tls.el relies upon, causing affected Emacs completed" message that tls.el relies upon, causing affected Emacs
functions to hang. To work around the problem, use older or newer functions to hang. To work around the problem, use older or newer
versions of gnutls-cli, or use Emacs's built-in gnutls support. versions of gnutls-cli, or use Emacs's built-in gnutls support.
* Runtime problems related to font handling * Runtime problems related to font handling
** Characters are displayed as empty boxes or with wrong font under X. ** Characters are displayed as empty boxes or with wrong font under X.
*** This may be due to your local fontconfig customization.
Try removing or moving aside "$XDG_CONFIG_HOME/fontconfig/conf.d" and
"$XDG_CONFIG_HOME/fontconfig/fonts.conf"
($XDG_CONFIG_HOME is treated as "~/.config" if not set)
*** This can occur when two different versions of FontConfig are used. *** This can occur when two different versions of FontConfig are used.
For example, XFree86 4.3.0 has one version and Gnome usually comes For example, XFree86 4.3.0 has one version and Gnome usually comes
with a newer version. Emacs compiled with Gtk+ will then use the with a newer version. Emacs compiled with Gtk+ will then use the
newer version. In most cases the problem can be temporarily fixed by newer version. In most cases the problem can be temporarily fixed by
stopping the application that has the error (it can be Emacs or any stopping the application that has the error (it can be Emacs or any
other application), removing ~/.fonts.cache-1, and then starting the other application), removing ~/.fonts.cache-1, and then starting the
application again. If removing ~/.fonts.cache-1 and restarting application again. If removing ~/.fonts.cache-1 and restarting
doesn't help, the application with problem must be recompiled with the doesn't help, the application with problem must be recompiled with the
same version of FontConfig as the rest of the system uses. For KDE, same version of FontConfig as the rest of the system uses. For KDE,
it is sufficient to recompile Qt. it is sufficient to recompile Qt.
skipping to change at line 920 skipping to change at line 925
- (font (nil phetsarath\ ot unicode-bmp))) - (font (nil phetsarath\ ot unicode-bmp)))
+ (font (nil nil unicode-bmp :otf=lao\ ))) + (font (nil nil unicode-bmp :otf=lao\ )))
;;; <li> LAOO-OTF.flt ;;; <li> LAOO-OTF.flt
------------------------------------------------------------ ------------------------------------------------------------
If you can't modify that file directly, copy it to the directory If you can't modify that file directly, copy it to the directory
~/.m17n.d/ (create it if it doesn't exist), and apply the patch. ~/.m17n.d/ (create it if it doesn't exist), and apply the patch.
** On MS-Windows, some characters display as boxes with hex code.
Also, some characters could display with wrong fonts.
This can happen if Emacs was compiled without HarfBuzz support, and/or
if the HarfBuzz DLLs are not available at run time. Emacs will then
fall back to the Uniscribe as its shaping engine; Uniscribe was
deprecated by Microsoft, and sometimes fails to display correctly when
modern fonts are used, such as Noto Emoji or Ebrima.
The solution is to switch to a configuration that uses HarfBuzz as its
shaping engine, where these problems don't exist.
* Internationalization problems * Internationalization problems
** M-{ does not work on a Spanish PC keyboard. ** M-{ does not work on a Spanish PC keyboard.
Many Spanish keyboards seem to ignore that combination. Emacs can't Many Spanish keyboards seem to ignore that combination. Emacs can't
do anything about it. do anything about it.
** International characters aren't displayed under X. ** International characters aren't displayed under X.
*** Missing X fonts *** Missing X fonts
skipping to change at line 2865 skipping to change at line 2883
compiler does not instruct the linker to search libgcc.a during the compiler does not instruct the linker to search libgcc.a during the
link stage. link stage.
A solution is to link with GCC, like this: A solution is to link with GCC, like this:
make CC=gcc make CC=gcc
Since the .o object files already exist, this will not recompile Emacs Since the .o object files already exist, this will not recompile Emacs
with GCC, but just restart by trying again to link temacs. with GCC, but just restart by trying again to link temacs.
*** Building Emacs with -lcurses fails with undefined symbols like BC.
The 'configure' script attempts to use several terminal libraries,
including tinfo, ncurses, and terminfo, and curses (in that order).
If it happens to choose the long-obsolete curses library, Emacs will
not link correctly. Emacs 28 is expected to work around this problem;
in the meantime you can work around it by installing tinfo, ncurses or
terminfo instead.
This problem can happen on AIX 7.2 if you build with IBM's compiler XLC,
as AIX's ncurses library suffers from the libgcc problem mentioned above.
To work around this, configure and build with GCC.
*** Sun with acc: Link failure when using acc on a Sun. *** Sun with acc: Link failure when using acc on a Sun.
To use acc, you need additional options just before the libraries, such as To use acc, you need additional options just before the libraries, such as
/usr/lang/SC2.0.1/values-Xt.o -L/usr/lang/SC2.0.1/cg87 -L/usr/lang/SC2.0.1 /usr/lang/SC2.0.1/values-Xt.o -L/usr/lang/SC2.0.1/cg87 -L/usr/lang/SC2.0.1
and you need to add -lansi just before -lc. and you need to add -lansi just before -lc.
The precise file names depend on the compiler version, so we The precise file names depend on the compiler version, so we
cannot easily arrange to supply them. cannot easily arrange to supply them.
 End of changes. 4 change blocks. 
1 lines changed or deleted 32 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)