Mercurial > hg > xemacs-beta

comparison PROBLEMS @ 223:2c611d1463a6 r20-4b10

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r20-4b10
author cvs
date Mon, 13 Aug 2007 10:10:54 +0200
parents 1f0dabaa0855
children 0e522484dd2a
comparison
equal deleted inserted replaced
222:aae4c8b01452 223:2c611d1463a6
11 - Problems with running XEmacs 11 - Problems with running XEmacs
12 - Compatibility problems 12 - Compatibility problems
13 - Mule issues 13 - Mule issues
14 14
15 Use `C-c C-f' to move to the next equal level of outline, and 15 Use `C-c C-f' to move to the next equal level of outline, and
16 `C-c C-f' to move to previous equal level. `C-h m' will give more 16 `C-c C-b' to move to previous equal level. `C-h m' will give more
17 advice about the Outline mode. 17 info about the Outline mode.
18 18
19 Also, Try finding the things you need using one of the search commands 19 Also, Try finding the things you need using one of the search commands
20 XEmacs provides (e.g. `C-s'). 20 XEmacs provides (e.g. `C-s').
21 21
22 A general advice: 22 A general advice:
27 27
28 * Problems with building XEmacs 28 * Problems with building XEmacs
29 =============================== 29 ===============================
30 30
31 ** Don't use -O2 with gcc 2.7.2 under Linux without also using 31 ** Don't use -O2 with gcc 2.7.2 under Linux without also using
32 `-fno-strength-reduce'. 32 `-fno-strength-reduce'.
33 33
34 gcc will generate incorrect code otherwise. This bug is present in at 34 gcc will generate incorrect code otherwise. This bug is present in at
35 least 2.6.x and 2.7.[0-2]. This bug has been fixed in GCC 2.7.2.1 and 35 least 2.6.x and 2.7.[0-2]. This bug has been fixed in GCC 2.7.2.1 and
36 later. 36 later.
37 37
1279 Make sure that your load-path and your $EMACSLOADPATH environment 1279 Make sure that your load-path and your $EMACSLOADPATH environment
1280 variable are not pointing at an Emacs18 lisp directory. This will 1280 variable are not pointing at an Emacs18 lisp directory. This will
1281 cripple emacs. 1281 cripple emacs.
1282 1282
1283 ** Some packages that worked before now cause the error 1283 ** Some packages that worked before now cause the error
1284 Wrong type argument: arrayp, #<face ... > 1284 Wrong type argument: arrayp, #<face ... >
1285 1285
1286 Code which uses the `face' accessor functions must be recompiled with 1286 Code which uses the `face' accessor functions must be recompiled with
1287 xemacs 19.9 or later. The functions whose callers must be recompiled 1287 xemacs 19.9 or later. The functions whose callers must be recompiled
1288 are: face-font, face-foreground, face-background, 1288 are: face-font, face-foreground, face-background,
1289 face-background-pixmap, and face-underline-p. The .elc files 1289 face-background-pixmap, and face-underline-p. The .elc files
1304 1304
1305 1305
1306 * MULE issues 1306 * MULE issues
1307 ============= 1307 =============
1308 1308
1309 ** A reminder: XEmacs/Mule work does not currently receive *any*
1310 funding, and all work is done by volunteers. If you think you can
1311 help, please contact the XEmacs maintainers.
1312
1313 ** XEmacs/Mule doesn't work on a tty.
1314
1315 This is a major problem, which we plan to address in a future release
1316 of XEmacs. Basically, XEmacs should have primitives to be told
1317 whether the terminal can handle international output, and which
1318 locale. Also, it should be able to do approximations of characters to
1319 the nearest supported by the locale.
1320
1309 ** Internationalized (Asian) Isearch doesn't work. 1321 ** Internationalized (Asian) Isearch doesn't work.
1310 1322
1311 Currently, Isearch doesn't directly support any of the input methods 1323 Currently, Isearch doesn't directly support any of the input methods
1312 that are not XIM based (like egg, canna and quail) (and there are 1324 that are not XIM based (like egg, canna and quail) (and there are
1313 potential problems with XIM version too...). This is something 1325 potential problems with XIM version too...). If you're using egg
1314 we are working on, but for the moment, if you're using egg there is a 1326 there is a workaround. Hitting <RET> right after C-s to invoke
1315 workaround. Hitting <RET> right after C-s to invoke Isearch will put 1327 Isearch will put Isearch in string mode, where a complete string can
1316 Isearch in string mode, where a complete string can be typed into the 1328 be typed into the minibuffer and then processed by Isearch afterwards.
1317 minibuffer and then processed by Isearch afterwards. Since egg is now 1329 Since egg is now supported in the minibuffer using string mode you can
1318 supported in the minibuffer using string mode you can now use egg to 1330 now use egg to input your Japanese, Korean or Chinese string, then hit
1319 input your Japanese, Korean or Chinese string, then hit return to send 1331 return to send that to Isearch and then use standard Isearch commands
1320 that to Isearch and then use standard Isearch commands from there. 1332 from there.
1321 1333
1322 ** Using egg or canna and mousing around while in 'fence' mode screws 1334 ** Using egg and mousing around while in 'fence' mode screws up my
1323 up my buffer. 1335 buffer.
1324 1336
1325 Don't do this. The fence modes of egg and canna are currently very 1337 Don't do this. The fence modes of egg and canna are currently very
1326 modal, and messing with where they expect point to be and what they 1338 modal, and messing with where they expect point to be and what they
1327 think is the current buffer is just asking for trouble. If you're 1339 think is the current buffer is just asking for trouble. If you're
1328 lucky they will realize that something is awry, and simply delete the 1340 lucky they will realize that something is awry, and simply delete the
1329 fence, but worst case can trash other buffers too. We've tried to 1341 fence, but worst case can trash other buffers too. We've tried to
1330 protect against this where we can, but there still are many ways to 1342 protect against this where we can, but there still are many ways to
1331 shoot yourself in the foot. So just finish what you are typing into 1343 shoot yourself in the foot. So just finish what you are typing into
1332 the fence before reaching for the mouse. 1344 the fence before reaching for the mouse.
1345
1346 ** Not all languages in Quail are supported like Devanagari and Indian
1347 languages, Lao and Tibetan.
1348
1349 Quail requires more work and testing. Although it has been ported to
1350 XEmacs, it works really well for Japanese and for the European
1351 languages.
1352
1353 ** Right-to-left mode is not yet implemented, so languages like
1354 Arabic, Hebrew and Thai don't work.
1355
1356 Getting this right requires more work. It may be implemented in a
1357 future XEmacs version, but don't hold your breath. If you know
1358 someone who is ready to implement this, please let us know.
1359
1360 ** We need more developers and native language testers. It's extremely
1361 difficult (and not particularly productive) to address languages that
1362 nobody is using and testing.
1363
1364 ** The kWnn and cWnn support for Chinese and Korean needs developers
1365 and testers. It probably doesn't work.
1366
1367 ** There are no `native XEmacs' TUTORIALs for any Asian languages,
1368 including Japanese. FSF Emacs and XEmacs tutorials are quite similar,
1369 so it should be sufficient to skim through the differences and apply
1370 them to the Japanese version.
1371
1372 ** We only have localized menus translated for Japanese, and the
1373 Japanese menus are developing bitrot (the Mule menu appears in
1374 English).
1375
1376 ** XIM is untested for any language other than Japanese.