aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlexander Gramiak2017-11-12 18:06:32 -0600
committerAlexander Gramiak2017-11-14 00:00:18 -0600
commit0491de8dad7b3e25e643f4556375a82b7e6ac445 (patch)
tree8674df34e8948e3b98cea18c9fcfa7be4b08a6d5
parentcaa39f495c0783dac2d5701100db83ea10f126c0 (diff)
downloademacs-0491de8dad7b3e25e643f4556375a82b7e6ac445.tar.gz
emacs-0491de8dad7b3e25e643f4556375a82b7e6ac445.zip
* etc/PROBLEMS: Remove fixed xterm-mouse-mode problems
See: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29143#26
-rw-r--r--etc/PROBLEMS24
1 files changed, 0 insertions, 24 deletions
diff --git a/etc/PROBLEMS b/etc/PROBLEMS
index 3dd225302a7..ac76230f690 100644
--- a/etc/PROBLEMS
+++ b/etc/PROBLEMS
@@ -1117,14 +1117,6 @@ to happen in *.UTF-8 locales; zh_CN.GB2312 and zh_CN.GBK locales, for
1117example, work fine. A bug report has been filed in the Gnome 1117example, work fine. A bug report has been filed in the Gnome
1118bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=357032 1118bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=357032
1119 1119
1120*** Gnome: Emacs's xterm-mouse-mode doesn't work on the Gnome terminal.
1121
1122A symptom of this bug is that double-clicks insert a control sequence
1123into the buffer. The reason this happens is an apparent
1124incompatibility of the Gnome terminal with Xterm, which also affects
1125other programs using the Xterm mouse interface. A problem report has
1126been filed.
1127
1128*** Gnome: GPaste clipboard manager causes erratic behavior of 'yank' 1120*** Gnome: GPaste clipboard manager causes erratic behavior of 'yank'
1129 1121
1130The symptom is that 'kill-line' followed by 'yank' often (but not 1122The symptom is that 'kill-line' followed by 'yank' often (but not
@@ -1496,22 +1488,6 @@ this, you can remove the X resource or put this in your init file:
1496 1488
1497 (xterm-remove-modify-other-keys) 1489 (xterm-remove-modify-other-keys)
1498 1490
1499** Emacs's xterm-mouse doesn't work well in Evil mode.
1500
1501Specifically, clicking mouse-1 doesn't work as expected: instead of
1502moving point where you click, it highlights the region between the
1503line beginning and the click location, and displays error messages
1504about unbound keys in the echo area.
1505
1506To work around this, put this in your .emacs file:
1507
1508 (with-eval-after-load 'evil-maps
1509 (define-key evil-motion-state-map [down-mouse-1] nil))
1510
1511This appears to be a bug in Evil.
1512See discussions in https://github.com/emacs-evil/evil/issues/960
1513and https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29143
1514
1515** Emacs spontaneously displays "I-search: " at the bottom of the screen. 1491** Emacs spontaneously displays "I-search: " at the bottom of the screen.
1516 1492
1517This means that Control-S/Control-Q (XON/XOFF) "flow control" is being 1493This means that Control-S/Control-Q (XON/XOFF) "flow control" is being