Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with isearch
Search options answers only
not deleted
user 5253
is the incremental search facility that highlights matching text as characters are typed. isearch-forward and isearch-backward support searching characters, strings, and regexp.
2
votes
When searching, how to always ensure that a few lines after the highlighted word are visible?
M-x apropos-variable RET isearch.*\(hook\|function\) RET leads you to isearch-update-post-hook, which seems to be what you're looking for. So ... … (add-hook 'isearch-update-post-hook
(lambda ()
(when (> (length isearch-string) 0)
;;or whatever
(recenter)))
nil t) …
- 3,386
3
votes
Accepted
Is there any way to configure isearch-forward-regexp invert backslashes usage?
Just adapt isearch-search-fun-function:
(defun isearch-extended-regexp-forward ()
(interactive)
(let ((regexp-chars "[|{}()`=<>]")
(isearch-message-prefix-add "Extended ")
(isearch-search-fun-function … t)
other-args)))))
(isearch-forward t))) …
- 3,386