Supposed we have the following contents in current buffer:
line 1. (defun ...
line 2. ...
....many lines here...
line 500. (define-package ...
....many lines here...
....
line 999. (define-key ...
Now the cursor position in current buffer is 0(line 1, col 1). Then I call vc/query-replace, in mini buffer we input "define-key", the screen will scroll down to line 999, then do nothing, delete "ine-key", the screen stays in line 999. I think a better behavior is that now the screen should scroll up to line 1("def" of "defun" is matched there). Even now we input "ine-package", the screen stays in line 999, a better behavior is that now the screen should scroll to line 500, since the first match pattern is there. That's exactly what isearch and other editors like sublime text 2 do.
I hope you can understand what I mean. It's a bit hard to explain or you can diff that using isearch and vr following the above workflow.
Supposed we have the following contents in current buffer:
line 1. (defun ... line 2. ... ....many lines here... line 500. (define-package ... ....many lines here... .... line 999. (define-key ...
Now the cursor position in current buffer is 0(line 1, col 1). Then I call
vc/query-replace
, in mini buffer we input "define-key", the screen will scroll down to line 999, then do nothing, delete "ine-key", the screen stays in line 999. I think a better behavior is that now the screen should scroll up to line 1("def" of "defun" is matched there). Even now we input "ine-package", the screen stays in line 999, a better behavior is that now the screen should scroll to line 500, since the first match pattern is there. That's exactly what isearch and other editors like sublime text 2 do.I hope you can understand what I mean. It's a bit hard to explain or you can diff that using isearch and vr following the above workflow.
Not a really important issue. :)