You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, for instance, the below example should have two matches on the same line, define-minor-mo and de ctrlf-local-mo. The shorter matches allow a more fine-grained movement, and greediness doesn't work well in files with long lines.
PS: Since this package is all about being sensible, couldn't the CRTLF prompt be replaced by something non-ugly, like Search? Also, I find that little arrow a bit gimmicky. I never forget what direction I was searching, unless I go for lunch in the middle of a search. I do sometimes loose track of whether I'm below or above the search starting point, though, which is what I initially thought the arrow was telling me.
The text was updated successfully, but these errors were encountered:
Yes, replacing .* with .*? in the greedy regexp builder should be safe and sensible, as you suggested.
I have no objection to making the prompt appearance customizable. I, in my personal configuration, would like to keep it as is, but there is no reason that everyone needs to see the same thing. Perhaps we could do something like mode-line-format, where it is a list of strings and/or symbols, like:
So, for instance, the below example should have two matches on the same line,
define-minor-mo
andde ctrlf-local-mo
. The shorter matches allow a more fine-grained movement, and greediness doesn't work well in files with long lines.PS: Since this package is all about being sensible, couldn't the
CRTLF
prompt be replaced by something non-ugly, likeSearch
? Also, I find that little arrow a bit gimmicky. I never forget what direction I was searching, unless I go for lunch in the middle of a search. I do sometimes loose track of whether I'm below or above the search starting point, though, which is what I initially thought the arrow was telling me.The text was updated successfully, but these errors were encountered: