Closed jaydixit closed 10 years ago
I'm not sure what you intend to.
I guess:
A. Just invoke isearch-repeat-forward
while doing helm-swoop
.
B. When helm-swoop
called, it starts with selecting the next match using last used words.
Could you tell me more specifically?
For me, when I do helm-swoop RET foo RET
, then invoke isearch-repeat-forward
from within helm-swoop
, it hangs. Same thing with helm-multi-swoop-all
followed by search string followed by isearch-repeat-forward
. If I do C-g
then look at Messages, I see this:
goto-history-element: Wrong type argument: numberp, nil
Quit
goto-history-element: Wrong type argument: numberp, nil
byte-code: Beginning of bufferError during redisplay: (eval (format "L%d" (helm-candidate-number-at-point))) signaled (error "No buffer named *helm*")
Error during redisplay: (eval (format "L%d" (helm-candidate-number-at-point))) signaled (error "No buffer named *helm*") [32 times]
Invalid face reference: t [6 times]
ad-Orig-call-interactively: End of buffer
(Shell command succeeded with no output)
I'm afraid I couldn't reproduce the error. I guess those error belong to helm.
Perhaps you can fix this problem by setting the keybind assigning to isearch-repeat-forward
If you assigned C-s
to isearch-repeat-forward
(define-key helm-swoop-map (kbd "C-s") 'helm-next-line)
(define-key helm-multi-swoop-map (kbd "C-s") 'helm-next-line)
I'm used to using
isearch-forward
for finding strings in my buffer. I am in the process of switching to helm-swoop, which seems much more powerful since it shows me all matches first and allows me to then choose which instance to visit.However, I am in the habit of, having found one match, hitting
isearch-repeat-forward
to jump to the next match. Is there a way to invoke this from within helm-swoop?