[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#18727: 25.0.50; Paste to isearch-repeat-forward does not work
From: |
Juri Linkov |
Subject: |
bug#18727: 25.0.50; Paste to isearch-repeat-forward does not work |
Date: |
Sun, 04 Aug 2019 22:20:31 +0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu) |
>> 1) emacs -Q <file.txt>
>> 2) Copy some text to the Windows/Linux clipboard
>> e.g. if using Putty simply highlight some text
>> using the mouse
>> 3) C-s to invoke isearch-repeat-forward
>> 4) Pate text
>> e.g. using Putty use mouse to right-click
>>
>> Expected result: isearch is performed for pasted text
>>
>> Actual result: text is insterted into file buffer and
>> mini-buffer reports "Mark set"
>
> I'm unable to reproduce this bug in Emacs 27, so I'm guessing that it's
> been fixed in the intervening years, and I'm closing the bug report.
> If you're still seeing this bug, please reopen this bug report.
After trying to reproduce the bug report, I see a slightly different problem:
0. Run in a terminal: emacs -Q -nw
1. C-s
2.1. either from the MATE Terminal context menu select "Paste"
2.2. or in xterm click the middle mouse button
(both calls the same command)
3. Emacs hangs and typing 'C-g' produces the backtrace:
Debugger entered--Lisp error: (quit)
apply(debug error (quit))
edebug(error (quit))
signal(quit nil)
edebug-signal(quit nil)
xterm--pasted-text()
backtrace-eval((xterm--pasted-text) 0 edebug-after)
edebug-eval((xterm--pasted-text))
edebug-eval-expression((xterm--pasted-text))
edebug-eval-last-sexp()
funcall-interactively(edebug-eval-last-sexp)
call-interactively(edebug-eval-last-sexp nil nil)
command-execute(edebug-eval-last-sexp)
recursive-edit()
edebug--recursive-edit(error)
edebug--display-1((quit) 1 error)
edebug--display((quit) 1 error)
edebug(error (quit))
signal(quit nil)
edebug-signal(quit nil)
xterm--pasted-text()
(edebug-after (edebug-before 1) 2 (xterm--pasted-text))
(isearch-yank-string (edebug-after (edebug-before 1) 2 (xterm--pasted-text)))
(edebug-after (edebug-before 0) 3 (isearch-yank-string (edebug-after (edebug$
(closure (minibuffer-history-symbol t) nil (edebug-after (edebug-before 0) 3$
edebug-default-enter(isearch-xterm-paste nil (closure (minibuffer-history-sy$
edebug-default-enter(isearch-xterm-paste nil (closure (minibuffer-history-sy$
edebug-enter(isearch-xterm-paste nil (closure (minibuffer-history-symbol t) $
isearch-xterm-paste()
funcall-interactively(isearch-xterm-paste)
call-interactively(isearch-xterm-paste nil nil)
command-execute(isearch-xterm-paste)
I don't know why isearch uses an internal function 'xterm--pasted-text',
but not the same body as 'xterm-paste'. There is no such problem when
pasting outside of isearch using 'xterm-paste'.