edit search string and begin search from current location
up vote
5
down vote
favorite
I use C-s
to start an incremental search. Sometimes I want to change the search string and either restart the search entirely from the beginning of the document or (other times) just change the search string and proceed from current location. How does one do this?
search isearch
add a comment |
up vote
5
down vote
favorite
I use C-s
to start an incremental search. Sometimes I want to change the search string and either restart the search entirely from the beginning of the document or (other times) just change the search string and proceed from current location. How does one do this?
search isearch
add a comment |
up vote
5
down vote
favorite
up vote
5
down vote
favorite
I use C-s
to start an incremental search. Sometimes I want to change the search string and either restart the search entirely from the beginning of the document or (other times) just change the search string and proceed from current location. How does one do this?
search isearch
I use C-s
to start an incremental search. Sometimes I want to change the search string and either restart the search entirely from the beginning of the document or (other times) just change the search string and proceed from current location. How does one do this?
search isearch
search isearch
edited Nov 23 at 23:29
Drew
46.6k461104
46.6k461104
asked Nov 23 at 23:03
Alex
1283
1283
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
5
down vote
accepted
During Isearch
M-e
is bound toisearch-edit-string
. It pauses Isearch and puts the current search string in the minibuffer so you can edit it. Just useC-s
again to resume searching from the current position but with the new search string.
(I know it looks like your search string is already always in the minibuffer during Isearch, but it is not. I you use some kind of indicator of minibuffer depth then you can see the difference. For example, I use a standalone minibuffer frame, and its background changes when the minibuffer is active. And it changes to a different hue for each recursive edit (minibuffer depth). And it changes to yet another hue for Isearch.)
You can use
C-h C-h b
during Isearch to see a list of all of the Isearch key bindings (where you can findM-e
).
If you use Isearch+ then just
C-h
shows you detailed help, including bindings such asM-e
.
If you use library
help-fns+.el
thenC-h M-k isearch-mode-map
shows you all keys bound on that keymap, in human-readable form.
With Isearch+ you can also interrupt Isearch completely, do some editing or whatever, and then resume where you left off and with the same search state. (The latter is not the case if you stop Isearch and restart it at the location where you left off.)
To do that, use
C-x o
(isearchp-open-recursive-edit
). Resume searching withexit-recursive-edit
(bound toC-M-c
).
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
During Isearch
M-e
is bound toisearch-edit-string
. It pauses Isearch and puts the current search string in the minibuffer so you can edit it. Just useC-s
again to resume searching from the current position but with the new search string.
(I know it looks like your search string is already always in the minibuffer during Isearch, but it is not. I you use some kind of indicator of minibuffer depth then you can see the difference. For example, I use a standalone minibuffer frame, and its background changes when the minibuffer is active. And it changes to a different hue for each recursive edit (minibuffer depth). And it changes to yet another hue for Isearch.)
You can use
C-h C-h b
during Isearch to see a list of all of the Isearch key bindings (where you can findM-e
).
If you use Isearch+ then just
C-h
shows you detailed help, including bindings such asM-e
.
If you use library
help-fns+.el
thenC-h M-k isearch-mode-map
shows you all keys bound on that keymap, in human-readable form.
With Isearch+ you can also interrupt Isearch completely, do some editing or whatever, and then resume where you left off and with the same search state. (The latter is not the case if you stop Isearch and restart it at the location where you left off.)
To do that, use
C-x o
(isearchp-open-recursive-edit
). Resume searching withexit-recursive-edit
(bound toC-M-c
).
add a comment |
up vote
5
down vote
accepted
During Isearch
M-e
is bound toisearch-edit-string
. It pauses Isearch and puts the current search string in the minibuffer so you can edit it. Just useC-s
again to resume searching from the current position but with the new search string.
(I know it looks like your search string is already always in the minibuffer during Isearch, but it is not. I you use some kind of indicator of minibuffer depth then you can see the difference. For example, I use a standalone minibuffer frame, and its background changes when the minibuffer is active. And it changes to a different hue for each recursive edit (minibuffer depth). And it changes to yet another hue for Isearch.)
You can use
C-h C-h b
during Isearch to see a list of all of the Isearch key bindings (where you can findM-e
).
If you use Isearch+ then just
C-h
shows you detailed help, including bindings such asM-e
.
If you use library
help-fns+.el
thenC-h M-k isearch-mode-map
shows you all keys bound on that keymap, in human-readable form.
With Isearch+ you can also interrupt Isearch completely, do some editing or whatever, and then resume where you left off and with the same search state. (The latter is not the case if you stop Isearch and restart it at the location where you left off.)
To do that, use
C-x o
(isearchp-open-recursive-edit
). Resume searching withexit-recursive-edit
(bound toC-M-c
).
add a comment |
up vote
5
down vote
accepted
up vote
5
down vote
accepted
During Isearch
M-e
is bound toisearch-edit-string
. It pauses Isearch and puts the current search string in the minibuffer so you can edit it. Just useC-s
again to resume searching from the current position but with the new search string.
(I know it looks like your search string is already always in the minibuffer during Isearch, but it is not. I you use some kind of indicator of minibuffer depth then you can see the difference. For example, I use a standalone minibuffer frame, and its background changes when the minibuffer is active. And it changes to a different hue for each recursive edit (minibuffer depth). And it changes to yet another hue for Isearch.)
You can use
C-h C-h b
during Isearch to see a list of all of the Isearch key bindings (where you can findM-e
).
If you use Isearch+ then just
C-h
shows you detailed help, including bindings such asM-e
.
If you use library
help-fns+.el
thenC-h M-k isearch-mode-map
shows you all keys bound on that keymap, in human-readable form.
With Isearch+ you can also interrupt Isearch completely, do some editing or whatever, and then resume where you left off and with the same search state. (The latter is not the case if you stop Isearch and restart it at the location where you left off.)
To do that, use
C-x o
(isearchp-open-recursive-edit
). Resume searching withexit-recursive-edit
(bound toC-M-c
).
During Isearch
M-e
is bound toisearch-edit-string
. It pauses Isearch and puts the current search string in the minibuffer so you can edit it. Just useC-s
again to resume searching from the current position but with the new search string.
(I know it looks like your search string is already always in the minibuffer during Isearch, but it is not. I you use some kind of indicator of minibuffer depth then you can see the difference. For example, I use a standalone minibuffer frame, and its background changes when the minibuffer is active. And it changes to a different hue for each recursive edit (minibuffer depth). And it changes to yet another hue for Isearch.)
You can use
C-h C-h b
during Isearch to see a list of all of the Isearch key bindings (where you can findM-e
).
If you use Isearch+ then just
C-h
shows you detailed help, including bindings such asM-e
.
If you use library
help-fns+.el
thenC-h M-k isearch-mode-map
shows you all keys bound on that keymap, in human-readable form.
With Isearch+ you can also interrupt Isearch completely, do some editing or whatever, and then resume where you left off and with the same search state. (The latter is not the case if you stop Isearch and restart it at the location where you left off.)
To do that, use
C-x o
(isearchp-open-recursive-edit
). Resume searching withexit-recursive-edit
(bound toC-M-c
).
edited Nov 24 at 5:45
answered Nov 23 at 23:16
Drew
46.6k461104
46.6k461104
add a comment |
add a comment |
Thanks for contributing an answer to Emacs Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2femacs.stackexchange.com%2fquestions%2f46179%2fedit-search-string-and-begin-search-from-current-location%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown