aboutsummaryrefslogtreecommitdiffstats
path: root/etc/PROBLEMS
diff options
context:
space:
mode:
authorIvan Shmakov2015-04-07 17:42:28 +0000
committerIvan Shmakov2015-04-07 17:42:28 +0000
commita137ff5025bbfe8aa3cd49814726c4b37ee3311d (patch)
tree9f615be99f54d9f95462e1af6f453b199429d245 /etc/PROBLEMS
parent29500239d3289803275ed6d4c774ab4488918564 (diff)
downloademacs-a137ff5025bbfe8aa3cd49814726c4b37ee3311d.tar.gz
emacs-a137ff5025bbfe8aa3cd49814726c4b37ee3311d.zip
Update etc/PROBLEMS.
* etc/PROBLEMS: Mention visible-cursor; a few more mentions of ~/.Xresources and xrdb(1); refer to 'GNU Coreutils' and 'X Window System' or 'X' (were: 'GNU Fileutils' and 'X Windows', respectively); other minor updates and tweaks. (Bug#20011)
Diffstat (limited to 'etc/PROBLEMS')
-rw-r--r--etc/PROBLEMS62
1 files changed, 37 insertions, 25 deletions
diff --git a/etc/PROBLEMS b/etc/PROBLEMS
index 87d3ec83700..c618309aca0 100644
--- a/etc/PROBLEMS
+++ b/etc/PROBLEMS
@@ -26,6 +26,9 @@ A typical error message might be something like
26This happens because some X resource specifies a bad font family for 26This happens because some X resource specifies a bad font family for
27Emacs to use. The possible places where this specification might be are: 27Emacs to use. The possible places where this specification might be are:
28 28
29 - in the X server resources database, often initialized from
30 ~/.Xresources (use $ xrdb -query to find out the current state)
31
29 - in your ~/.Xdefaults file 32 - in your ~/.Xdefaults file
30 33
31 - client-side X resource file, such as ~/Emacs or 34 - client-side X resource file, such as ~/Emacs or
@@ -35,6 +38,12 @@ One of these files might have bad or malformed specification of a
35fontset that Emacs should use. To fix the problem, you need to find 38fontset that Emacs should use. To fix the problem, you need to find
36the problematic line(s) and correct them. 39the problematic line(s) and correct them.
37 40
41After correcting ~/.Xresources, the new data has to be merged into the
42X server resources database. Depending on the circumstances, the
43following command may do the trick. See xrdb(1) for more information.
44
45 $ xrdb -merge ~/.Xresources
46
38** Emacs aborts while starting up, only when run without X. 47** Emacs aborts while starting up, only when run without X.
39 48
40This problem often results from compiling Emacs with GCC when GCC was 49This problem often results from compiling Emacs with GCC when GCC was
@@ -270,8 +279,7 @@ The error message might be something like this:
270 279
271This happens because epop3 redefines the function gethash, which is a 280This happens because epop3 redefines the function gethash, which is a
272built-in primitive beginning with Emacs 21.1. We don't have a patch 281built-in primitive beginning with Emacs 21.1. We don't have a patch
273for epop3 that fixes this, but perhaps a newer version of epop3 282for epop3 to fix it, but perhaps a newer version of epop3 corrects that.
274corrects that.
275 283
276*** Buffers from `with-output-to-temp-buffer' get set up in Help mode. 284*** Buffers from `with-output-to-temp-buffer' get set up in Help mode.
277 285
@@ -507,7 +515,7 @@ time. Possible reasons for this include:
507 515
508To work around the problem, you could either (a) set the variable 516To work around the problem, you could either (a) set the variable
509`directory-free-space-program' to nil, and thus prevent Emacs from 517`directory-free-space-program' to nil, and thus prevent Emacs from
510invoking `df'; (b) use `df' from the GNU Fileutils package; or 518invoking `df'; (b) use `df' from the GNU Coreutils package; or
511(c) use CVS, which is Free Software, instead of ClearCase. 519(c) use CVS, which is Free Software, instead of ClearCase.
512 520
513*** ps-print commands fail to find prologue files ps-prin*.ps. 521*** ps-print commands fail to find prologue files ps-prin*.ps.
@@ -600,7 +608,7 @@ For example, XFree86 4.3.0 has one version and Gnome usually comes
600with a newer version. Emacs compiled with Gtk+ will then use the 608with a newer version. Emacs compiled with Gtk+ will then use the
601newer version. In most cases the problem can be temporarily fixed by 609newer version. In most cases the problem can be temporarily fixed by
602stopping the application that has the error (it can be Emacs or any 610stopping the application that has the error (it can be Emacs or any
603other application), removing ~/.fonts.cache-1, and then start the 611other application), removing ~/.fonts.cache-1, and then starting the
604application again. If removing ~/.fonts.cache-1 and restarting 612application again. If removing ~/.fonts.cache-1 and restarting
605doesn't help, the application with problem must be recompiled with the 613doesn't help, the application with problem must be recompiled with the
606same version of FontConfig as the rest of the system uses. For KDE, 614same version of FontConfig as the rest of the system uses. For KDE,
@@ -700,7 +708,7 @@ frame's parameter list, like this:
700** Underlines appear at the wrong position. 708** Underlines appear at the wrong position.
701 709
702This is caused by fonts having a wrong UNDERLINE_POSITION property. 710This is caused by fonts having a wrong UNDERLINE_POSITION property.
703Examples are the font 7x13 on XFree prior to version 4.1, or the jmk 711Examples are the 7x13 font on XFree86 prior to version 4.1, or the jmk
704neep font from the Debian xfonts-jmk package prior to version 3.0.17. 712neep font from the Debian xfonts-jmk package prior to version 3.0.17.
705To circumvent this problem, set x-use-underline-position-properties 713To circumvent this problem, set x-use-underline-position-properties
706to nil in your `.emacs'. 714to nil in your `.emacs'.
@@ -823,7 +831,7 @@ If all users at your site of a particular keyboard prefer Meta to
823Compose, you can make the remapping happen automatically by adding the 831Compose, you can make the remapping happen automatically by adding the
824xmodmap command to the xdm setup script for that display. 832xmodmap command to the xdm setup script for that display.
825 833
826*** Using X Windows, control-shift-leftbutton makes Emacs hang. 834*** Using X Window System, control-shift-leftbutton makes Emacs hang.
827 835
828Use the shell command `xset bc' to make the old X Menu package work. 836Use the shell command `xset bc' to make the old X Menu package work.
829 837
@@ -987,8 +995,8 @@ while, Emacs may print a message:
987 995
988 Timed out waiting for property-notify event 996 Timed out waiting for property-notify event
989 997
990A workaround is to not use `klipper'. An upgrade to the `klipper' that 998A workaround is to not use `klipper'. Upgrading `klipper' to the one
991comes with KDE 3.3 or later also solves the problem. 999coming with KDE 3.3 or later also solves the problem.
992 1000
993*** CDE: Frames may cover dialogs they created when using CDE. 1001*** CDE: Frames may cover dialogs they created when using CDE.
994 1002
@@ -1113,8 +1121,8 @@ be carried out at the same time:
1113 (menu-bar-mode -1) 1121 (menu-bar-mode -1)
1114 (tool-bar-mode -1) 1122 (tool-bar-mode -1)
1115 1123
1116 For still quicker startup, put these X resources in your .Xdefaults 1124 For still quicker startup, put these X resources in your
1117 file: 1125 .Xresources or .Xdefaults file:
1118 1126
1119 Emacs.verticalScrollBars: off 1127 Emacs.verticalScrollBars: off
1120 Emacs.menuBar: off 1128 Emacs.menuBar: off
@@ -1133,7 +1141,7 @@ be carried out at the same time:
1133 -noatomsfile -nowinattr -cheaterrors -cheatevents 1141 -noatomsfile -nowinattr -cheaterrors -cheatevents
1134 Note that the -nograbcmap option is known to cause problems. 1142 Note that the -nograbcmap option is known to cause problems.
1135 For more about lbxproxy, see: 1143 For more about lbxproxy, see:
1136 http://www.xfree86.org/4.3.0/lbxproxy.1.html 1144 http://www.x.org/archive/X11R6.8.0/doc/lbxproxy.1.html
1137 1145
11385) If copying and killing is slow, try to disable the interaction with the 11465) If copying and killing is slow, try to disable the interaction with the
1139 native system's clipboard by adding these lines to your .emacs file: 1147 native system's clipboard by adding these lines to your .emacs file:
@@ -1201,17 +1209,17 @@ To check thoroughly for such resource specifications, use `xrdb
1201-query' to see what resources the X server records, and also look at 1209-query' to see what resources the X server records, and also look at
1202the user's ~/.Xdefaults and ~/.Xdefaults-* files. 1210the user's ~/.Xdefaults and ~/.Xdefaults-* files.
1203 1211
1204*** Emacs running under X Windows does not handle mouse clicks. 1212*** Emacs running under X Window System does not handle mouse clicks.
1205*** `emacs -geometry 80x20' finds a file named `80x20'. 1213*** `emacs -geometry 80x20' finds a file named `80x20'.
1206 1214
1207One cause of such problems is having (setq term-file-prefix nil) in 1215One cause of such problems is having (setq term-file-prefix nil) in
1208your .emacs file. Another cause is a bad value of EMACSLOADPATH in 1216your .emacs file. Another cause is a bad value of EMACSLOADPATH in
1209the environment. 1217the environment.
1210 1218
1211*** X Windows doesn't work if DISPLAY uses a hostname. 1219*** X doesn't work if DISPLAY uses a hostname.
1212 1220
1213People have reported kernel bugs in certain systems that cause Emacs 1221People have reported kernel bugs in certain systems that cause Emacs
1214not to work with X Windows if DISPLAY is set using a host name. But 1222not to work with X if DISPLAY is set using a host name. But
1215the problem does not occur if DISPLAY is set to `unix:0.0'. I think 1223the problem does not occur if DISPLAY is set to `unix:0.0'. I think
1216the bug has to do with SIGIO or FIONREAD. 1224the bug has to do with SIGIO or FIONREAD.
1217 1225
@@ -1393,7 +1401,7 @@ shows how to do this with C-^ and C-\.
1393** Screen is updated wrong, but only on one kind of terminal. 1401** Screen is updated wrong, but only on one kind of terminal.
1394 1402
1395This could mean that the termcap entry you are using for that 1403This could mean that the termcap entry you are using for that
1396terminal is wrong, or it could mean that Emacs has a bug handing 1404terminal is wrong, or it could mean that Emacs has a bug handling
1397the combination of features specified for that terminal. 1405the combination of features specified for that terminal.
1398 1406
1399The first step in tracking this down is to record what characters 1407The first step in tracking this down is to record what characters
@@ -1612,7 +1620,7 @@ http://debbugs.gnu.org/7791
1612The symptoms are: you are accessing a svn repository over SSH. 1620The symptoms are: you are accessing a svn repository over SSH.
1613You use vc-annotate on a large (several thousand line) file, and the 1621You use vc-annotate on a large (several thousand line) file, and the
1614result is truncated around the 1000 line mark. It works fine with 1622result is truncated around the 1000 line mark. It works fine with
1615other access methods (eg http), or from outside Emacs. 1623other access methods (e.g. http), or from outside Emacs.
1616 1624
1617This may be a similar libc/SSH issue to the one mentioned above for CVS. 1625This may be a similar libc/SSH issue to the one mentioned above for CVS.
1618A similar workaround seems to be effective: create a script with the 1626A similar workaround seems to be effective: create a script with the
@@ -1714,7 +1722,11 @@ the sequence "\E[?25h\E[?17;0;64c", and then run "tic linux-term" to
1714produce a modified terminfo entry. 1722produce a modified terminfo entry.
1715 1723
1716Alternatively, if you want a blinking underscore as your Emacs cursor, 1724Alternatively, if you want a blinking underscore as your Emacs cursor,
1717change the "cvvis" capability to send the "\E[?25h\E[?0c" command. 1725set the `visible-cursor' variable to nil in your ~/.emacs:
1726 (setq visible-cursor nil)
1727
1728Still other way is to change the "cvvis" capability to send the
1729"\E[?25h\E[?0c" command.
1718 1730
1719** FreeBSD 1731** FreeBSD
1720 1732
@@ -1906,7 +1918,7 @@ Near the bottom there is a line that reads:
1906 1918
1907 Ctrl<t> <quotedbl> <Y> : "\276" threequarters 1919 Ctrl<t> <quotedbl> <Y> : "\276" threequarters
1908 1920
1909that should read: 1921while it should read:
1910 1922
1911 Ctrl<T> <quotedbl> <Y> : "\276" threequarters 1923 Ctrl<T> <quotedbl> <Y> : "\276" threequarters
1912 1924
@@ -2049,7 +2061,7 @@ rails-mode.
2049** M-x term does not work on MS-Windows. 2061** M-x term does not work on MS-Windows.
2050 2062
2051TTY emulation on Windows is undocumented, and programs such as stty 2063TTY emulation on Windows is undocumented, and programs such as stty
2052which are used on posix platforms to control tty emulation do not 2064which are used on POSIX platforms to control tty emulation do not
2053exist for native windows terminals. 2065exist for native windows terminals.
2054 2066
2055** Using create-fontset-from-ascii-font or the --font startup parameter 2067** Using create-fontset-from-ascii-font or the --font startup parameter
@@ -2062,7 +2074,7 @@ use create-fontset-from-fontset-spec to define a fontset.
2062 2074
2063This means no redisplay while the File or Font dialog or a pop-up menu 2075This means no redisplay while the File or Font dialog or a pop-up menu
2064is displayed. This also means tooltips with help text for pop-up 2076is displayed. This also means tooltips with help text for pop-up
2065menus is not displayed at all (except in a TTY session, where the help 2077menus are not displayed at all (except in a TTY session, where the help
2066text is shown in the echo area). This is because message handling 2078text is shown in the echo area). This is because message handling
2067under Windows is synchronous, so we cannot handle repaint (or any 2079under Windows is synchronous, so we cannot handle repaint (or any
2068other) messages while waiting for a system function, which popped up 2080other) messages while waiting for a system function, which popped up
@@ -2144,7 +2156,7 @@ daylight savings switchovers by the Windows libraries.
2144 2156
2145Files larger than 4GB cause overflow in the size (represented as a 2157Files larger than 4GB cause overflow in the size (represented as a
214632-bit integer) reported by `file-attributes'. This affects Dired as 215832-bit integer) reported by `file-attributes'. This affects Dired as
2147well, since the Windows port uses a Lisp emulation of `ls' that relies 2159well, since the Windows port uses a Lisp emulation of `ls', which relies
2148on `file-attributes'. 2160on `file-attributes'.
2149 2161
2150** Playing sound doesn't support the :data method 2162** Playing sound doesn't support the :data method
@@ -2332,7 +2344,7 @@ you are working on the host called `marvin'. Then an entry in the
2332 2344
2333 marvin:/usr/local/src /usr/local/src ...options.omitted... 2345 marvin:/usr/local/src /usr/local/src ...options.omitted...
2334 2346
2335The solution is to remove this line from `etc/fstab'. 2347The solution is to remove this line from `/etc/fstab'.
2336 2348
2337*** Building a 32-bit executable on a 64-bit GNU/Linux architecture. 2349*** Building a 32-bit executable on a 64-bit GNU/Linux architecture.
2338 2350
@@ -2363,7 +2375,7 @@ The linker error messages look like this:
2363 oo-spd/i386/ctags.o:ctags.c:(.text+0x156e): undefined reference to `_imp__re_set_syntax' 2375 oo-spd/i386/ctags.o:ctags.c:(.text+0x156e): undefined reference to `_imp__re_set_syntax'
2364 collect2: ld returned 1 exit status 2376 collect2: ld returned 1 exit status
2365 2377
2366This happens because GCC finds an incompatible header regex.h 2378This happens because GCC finds an incompatible regex.h header
2367somewhere on the include path, before the version of regex.h supplied 2379somewhere on the include path, before the version of regex.h supplied
2368with Emacs. One such incompatible version of regex.h is part of the 2380with Emacs. One such incompatible version of regex.h is part of the
2369GnuWin32 Regex package. 2381GnuWin32 Regex package.
@@ -2510,7 +2522,7 @@ Compiling the lisp files fails at random places, complaining:
2510"No rule to make target `/path/to/some/lisp.elc'". 2522"No rule to make target `/path/to/some/lisp.elc'".
2511The causes of this problem are not understood. Using GNU make 3.81 compiled 2523The causes of this problem are not understood. Using GNU make 3.81 compiled
2512from source, rather than the Ubuntu version, worked. 2524from source, rather than the Ubuntu version, worked.
2513See <URL:http://debbugs.gnu.org/327, <URL:http://debbugs.gnu.org/821>. 2525See <URL:http://debbugs.gnu.org/327>, <URL:http://debbugs.gnu.org/821>.
2514 2526
2515** Dumping 2527** Dumping
2516 2528
@@ -2618,7 +2630,7 @@ build Emacs in a directory on a local disk.
2618On a system where getpagesize is not a system call, it is defined 2630On a system where getpagesize is not a system call, it is defined
2619as a macro. If the definition (in both unex*.c and malloc.c) is wrong, 2631as a macro. If the definition (in both unex*.c and malloc.c) is wrong,
2620it can cause problems like this. You might be able to find the correct 2632it can cause problems like this. You might be able to find the correct
2621value in the man page for a.out (5). 2633value in the man page for a.out(5).
2622 2634
2623* Problems on legacy systems 2635* Problems on legacy systems
2624 2636