Mercurial > emacs
comparison etc/PROBLEMS @ 90796:4ef881a120fe
Merge from emacs--devo--0
Patches applied:
* emacs--devo--0 (patch 675-697)
- Update from CVS
- Merge from gnus--rel--5.10
- Release ERC 5.2.
* gnus--rel--5.10 (patch 211-215)
- Update from CVS
- Merge from emacs--devo--0
Revision: emacs@sv.gnu.org/emacs--unicode--0--patch-189
author | Miles Bader <miles@gnu.org> |
---|---|
date | Wed, 11 Apr 2007 00:17:47 +0000 |
parents | c0409ee15cee 9bc027540c27 |
children | e6fdae9180d4 |
comparison
equal
deleted
inserted
replaced
90795:b9182b6a90c9 | 90796:4ef881a120fe |
---|---|
218 http://bugzilla.gnome.org/show_bug.cgi?id=85715. | 218 http://bugzilla.gnome.org/show_bug.cgi?id=85715. |
219 | 219 |
220 ** Emacs compiled with Gtk+ crashes on startup on cygwin. | 220 ** Emacs compiled with Gtk+ crashes on startup on cygwin. |
221 | 221 |
222 A typical error message is | 222 A typical error message is |
223 ***MEMORY-ERROR***: emacs[5172]: GSlice: failed to allocate 504 bytes | 223 ***MEMORY-ERROR***: emacs[5172]: GSlice: failed to allocate 504 bytes |
224 (alignment: 512): Function not implemented | 224 (alignment: 512): Function not implemented |
225 | 225 |
226 Emacs supplies its own malloc, but glib (part of Gtk+) calls memalign and on | 226 Emacs supplies its own malloc, but glib (part of Gtk+) calls memalign and on |
227 cygwin that becomes the cygwin supplied memalign. As malloc is not the | 227 cygwin that becomes the cygwin supplied memalign. As malloc is not the |
228 cygwin malloc, the cygwin memalign always returns ENOSYS. A fix for this | 228 cygwin malloc, the cygwin memalign always returns ENOSYS. A fix for this |
2104 pop-up menu interaction. | 2104 pop-up menu interaction. |
2105 | 2105 |
2106 Windows 95 and Windows NT up to version 4.0 do not support help text | 2106 Windows 95 and Windows NT up to version 4.0 do not support help text |
2107 for menus. Help text is only available in later versions of Windows. | 2107 for menus. Help text is only available in later versions of Windows. |
2108 | 2108 |
2109 When "ClearType" method is selected as the "method to smooth edges of | |
2110 screen fonts" (in Display Properties, Appearance tab, under | |
2111 "Effects"), there are various problems related to display of | |
2112 characters: 2-pixel trace is left behind when moving overlays, bold | |
2113 fonts can be hard to read, small portions of some characters could | |
2114 appear chopped, etc. This happens because, under ClearType, | |
2115 characters are drawn outside their advertised bounding box. Emacs 21 | |
2116 disabled the use of ClearType, whereas Emacs 22 allows it and has some | |
2117 code to enlarge the width of the bounding box. Apparently, this | |
2118 display feature needs more changes to get it 100% right. A workaround | |
2119 is to disable ClearType. | |
2120 | |
2109 There are problems with display if mouse-tracking is enabled and the | 2121 There are problems with display if mouse-tracking is enabled and the |
2110 mouse is moved off a frame, over another frame then back over the first | 2122 mouse is moved off a frame, over another frame then back over the first |
2111 frame. A workaround is to click the left mouse button inside the frame | 2123 frame. A workaround is to click the left mouse button inside the frame |
2112 after moving back into it. | 2124 after moving back into it. |
2113 | 2125 |
2115 not as severely as in 21.1. | 2127 not as severely as in 21.1. |
2116 | 2128 |
2117 An inactive cursor remains in an active window after the Windows | 2129 An inactive cursor remains in an active window after the Windows |
2118 Manager driven switch of the focus, until a key is pressed. | 2130 Manager driven switch of the focus, until a key is pressed. |
2119 | 2131 |
2120 Windows input methods are not recognized by Emacs. Some | 2132 Windows input methods are not recognized by Emacs. However, some |
2121 of these input methods cause the keyboard to send characters encoded | 2133 of these input methods cause the keyboard to send characters encoded |
2122 in the appropriate coding system (e.g., ISO 8859-1 for Latin-1 | 2134 in the appropriate coding system (e.g., ISO 8859-1 for Latin-1 |
2123 characters, ISO 8859-8 for Hebrew characters, etc.). To make this | 2135 characters, ISO 8859-8 for Hebrew characters, etc.). To make these |
2124 work, set the keyboard coding system to the appropriate value after | 2136 input methods work with Emacs, set the keyboard coding system to the |
2125 you activate the Windows input method. For example, if you activate | 2137 appropriate value after you activate the Windows input method. For |
2126 the Hebrew input method, type "C-x RET k iso-8859-8 RET". (Emacs | 2138 example, if you activate the Hebrew input method, type this: |
2127 ought to recognize the Windows language-change event and set up the | 2139 |
2128 appropriate keyboard encoding automatically, but it doesn't do that | 2140 C-x RET k hebrew-iso-8bit RET |
2129 yet.) | 2141 |
2142 (Emacs ought to recognize the Windows language-change event and set up | |
2143 the appropriate keyboard encoding automatically, but it doesn't do | |
2144 that yet.) In addition, to use these Windows input methods, you | |
2145 should set your "Language for non-Unicode programs" (on Windows XP, | |
2146 this is on the Advanced tab of Regional Settings) to the language of | |
2147 the input method. | |
2148 | |
2149 To bind keys that produce non-ASCII characters with modifiers, you | |
2150 must specify raw byte codes. For instance, if you want to bind | |
2151 META-a-grave to a command, you need to specify this in your `~/.emacs': | |
2152 | |
2153 (global-set-key [?\M-\340] ...) | |
2154 | |
2155 The above example is for the Latin-1 environment where the byte code | |
2156 of the encoded a-grave is 340 octal. For other environments, use the | |
2157 encoding appropriate to that environment. | |
2130 | 2158 |
2131 The %b specifier for format-time-string does not produce abbreviated | 2159 The %b specifier for format-time-string does not produce abbreviated |
2132 month names with consistent widths for some locales on some versions | 2160 month names with consistent widths for some locales on some versions |
2133 of Windows. This is caused by a deficiency in the underlying system | 2161 of Windows. This is caused by a deficiency in the underlying system |
2134 library function. | 2162 library function. |
2296 `--enable-shared' option and then rebuild libjpeg. This produces a | 2324 `--enable-shared' option and then rebuild libjpeg. This produces a |
2297 shared version of libjpeg, which you need to install. Finally, rerun | 2325 shared version of libjpeg, which you need to install. Finally, rerun |
2298 the Emacs configure script, which should now find the jpeg library. | 2326 the Emacs configure script, which should now find the jpeg library. |
2299 Alternatively, modify the generated src/Makefile to link the .a file | 2327 Alternatively, modify the generated src/Makefile to link the .a file |
2300 explicitly, and edit src/config.h to define HAVE_JPEG. | 2328 explicitly, and edit src/config.h to define HAVE_JPEG. |
2329 | |
2330 *** `configure' warns ``accepted by the compiler, rejected by the preprocessor''. | |
2331 | |
2332 This indicates a mismatch between the C compiler and preprocessor that | |
2333 configure is using. For example, on Solaris 10 trying to use | |
2334 CC=/opt/SUNWspro/bin/cc (the Sun Studio compiler) together with | |
2335 CPP=/usr/ccs/lib/cpp can result in errors of this form (you may also | |
2336 see the error ``"/usr/include/sys/isa_defs.h", line 500: undefined control''). | |
2337 | |
2338 The solution is to tell configure to use the correct C preprocessor | |
2339 for your C compiler (CPP="/opt/SUNWspro/bin/cc -E" in the above | |
2340 example). | |
2341 | |
2342 *** `configure' fails with ``"junk.c", line 660: invalid input token: 8.elc'' | |
2343 | |
2344 The final stage of the Emacs configure process uses the C preprocessor | |
2345 to generate the Makefiles. Errors of this form can occur if the C | |
2346 preprocessor inserts extra whitespace into its output. The solution | |
2347 is to find the switches that stop your preprocessor from inserting extra | |
2348 whitespace, add them to CPPFLAGS, and re-run configure. For example, | |
2349 this error can occur on Solaris 10 when using the Sun Studio compiler | |
2350 ``Sun C 5.8'' with its preprocessor CPP="/opt/SUNWspro/bin/cc -E". | |
2351 The relevant switch in this case is "-Xs" (``compile assuming | |
2352 (pre-ANSI) K & R C style code''). | |
2301 | 2353 |
2302 ** Compilation | 2354 ** Compilation |
2303 | 2355 |
2304 *** Building Emacs over NFS fails with ``Text file busy''. | 2356 *** Building Emacs over NFS fails with ``Text file busy''. |
2305 | 2357 |
2719 | 2771 |
2720 *** Installing Emacs gets an error running `install-info'. | 2772 *** Installing Emacs gets an error running `install-info'. |
2721 | 2773 |
2722 You need to install a recent version of Texinfo; that package | 2774 You need to install a recent version of Texinfo; that package |
2723 supplies the `install-info' command. | 2775 supplies the `install-info' command. |
2776 | |
2777 *** Installing to a directory with spaces in the name fails. | |
2778 | |
2779 For example, if you call configure with a directory-related option | |
2780 with spaces in the value, eg --enable-locallisppath='/path/with\ spaces'. | |
2781 Using directory paths with spaces is not supported at this time: you | |
2782 must re-configure without using spaces. | |
2724 | 2783 |
2725 ** First execution | 2784 ** First execution |
2726 | 2785 |
2727 *** Emacs binary is not in executable format, and cannot be run. | 2786 *** Emacs binary is not in executable format, and cannot be run. |
2728 | 2787 |