Mercurial > hg > xemacs-beta

comparison PROBLEMS @ 367:a4f53d9b3154 r21-1-13

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-1-13
author cvs
date Mon, 13 Aug 2007 11:01:07 +0200
parents 30d2cfa1092a
children 1d62742628b6
comparison
equal deleted inserted replaced
366:83d76f480a59 367:a4f53d9b3154
1024 if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file 1024 if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file
1025 1025
1026 Or you could set TERMCAP only when you set TERM--which should not 1026 Or you could set TERMCAP only when you set TERM--which should not
1027 happen in a non-login shell. 1027 happen in a non-login shell.
1028 1028
1029 *** The popup menu appears at the buttom/right of my screen. 1029 *** The popup menu appears at the bottom/right of my screen.
1030 1030
1031 You probably have something like the following in your ~/.Xdefaults 1031 You probably have something like the following in your ~/.Xdefaults
1032 1032
1033 Emacs.geometry: 81x56--9--1 1033 Emacs.geometry: 81x56--9--1
1034 1034
1237 compatible include files into the compilation. In particular this 1237 compatible include files into the compilation. In particular this
1238 affected virtually all ioctl() calls. 1238 affected virtually all ioctl() calls.
1239 1239
1240 1240
1241 ** Linux 1241 ** Linux
1242 *** Mandrake
1243
1244 The Mandrake Linux distribution is attempting to comprehensively
1245 update the user interface, and make it consistent across
1246 applications. This is very difficult, and will occasionally cause
1247 conflicts with applications like Emacs with their own long-established
1248 interfaces. Known issues specific to Mandrake or especially common:
1249
1250 Some versions of XEmacs distributed with Mandrake were patched to make
1251 the Meta and Alt keysyms synonymous. These normally work as expected
1252 in the Mandrake environment. However, custom-built XEmacsen will seem
1253 to "inexplicably" not respect the "Alt-invokes-Meta-commands" convention.
1254 See "I want XEmacs to use the Alt key" below.
1255
1256 The color-gcc wrapper (see below) is in common use on the Mandrake
1257 platform.
1258
1259 *** I want XEmacs to use the Alt key, not the XXX key, for Meta commands
1260
1261 For historical reasons, XEmacs looks for a Meta key, then an Alt key.
1262 It binds Meta commands to the X11 modifier bit attached to the first
1263 of these it finds. On PCs, the Windows key is often assigned the Meta
1264 bit, but many desktop environments go to great lengths to get all apps
1265 to use the Alt key, and reserve the Windows key to (sensibly enough)
1266 the window manager.
1267
1268 One correct way to implement this was suggested on comp.emacs.xemacs
1269 (by Kilian Foth and in more detail by Michael Piotrowski): unmap the
1270 Meta modifier using xmodmap or xkb, and then map the Meta/Windows key
1271 to the Super or Hyper keysym and an appropriate mod bit. XEmacs will
1272 not find the Meta keysym, and default to using the Alt key for Meta
1273 keybindings. Typically few applications use the (X11) Meta modifier;
1274 it is tedious but not too much so to teach the ones you need to use
1275 Super instead of Meta. There may be further useful hints in the
1276 discussion of keymapping on non-Linux platforms.
1277
1278 *** The color-gcc wrapper
1279
1280 This wrapper colorizes the error messages from gcc. By default XEmacs
1281 does not interpret the escape sequences used to generate colors,
1282 resulting in a cluttered, hard-to-read buffer. You can remove or
1283 defeat the wrapper, or you may get good results from the ansi-color.el
1284 library:
1285
1286 http://www.geocities.com/kensanata/color-emacs.html#ansicolors
1287
1242 *** `C-z', or `M-x suspend-emacs' hangs instead of suspending. 1288 *** `C-z', or `M-x suspend-emacs' hangs instead of suspending.
1243 1289
1244 If you build with `gpm' support on Linux, you cannot suspend XEmacs 1290 If you build with `gpm' support on Linux, you cannot suspend XEmacs
1245 because gpm installs a buggy SIGTSTP handler. Either compile with 1291 because gpm installs a buggy SIGTSTP handler. Either compile with
1246 `--with-gpm=no', or don't suspend XEmacs on the Linux console until 1292 `--with-gpm=no', or don't suspend XEmacs on the Linux console until
1396 event (mouse, keyboard, expose...) results in a "poll: Interrupted 1442 event (mouse, keyboard, expose...) results in a "poll: Interrupted
1397 system call" message in the window where XEmacs was 1443 system call" message in the window where XEmacs was
1398 launched. Forcing a static link of libc.a alone by adding 1444 launched. Forcing a static link of libc.a alone by adding
1399 /usr/lib/libc.a at the end of the link line solves this. Note that 1445 /usr/lib/libc.a at the end of the link line solves this. Note that
1400 my 9.07 build of 19.14b17 and my (old) build of 19.13 both exhibit 1446 my 9.07 build of 19.14b17 and my (old) build of 19.13 both exhibit
1401 the same behaviour. I've tried various hpux patches to no avail. If 1447 the same behavior. I've tried various hpux patches to no avail. If
1402 this problem cannot be solved before the release date, binary kits 1448 this problem cannot be solved before the release date, binary kits
1403 for HP *must* be linked statically against libc, otherwise this 1449 for HP *must* be linked statically against libc, otherwise this
1404 problem will show up. (This is directed at whoever will volunteer 1450 problem will show up. (This is directed at whoever will volunteer
1405 for this kit, as I won't be available to do it, unless 19.14 gets 1451 for this kit, as I won't be available to do it, unless 19.14 gets
1406 delayed until mid-june ;-). I think this problem will be an FAQ soon 1452 delayed until mid-june ;-). I think this problem will be an FAQ soon