branch: elpa/isl
commit 74afa1a3d3f9a7cda68fcaedce7d8c37cd8af6e7
Author: Thierry Volpiatto <[email protected]>
Commit: Thierry Volpiatto <[email protected]>

    Update README
---
 README.org | 15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/README.org b/README.org
index 54155cfe2ba..bc0b1258a63 100644
--- a/README.org
+++ b/README.org
@@ -97,17 +97,19 @@ Here the commands available:
 | M-v    | isl-scroll-down                |
 | C-'    | isl-show-or-hide-context-lines |
 | C-l    | isl-recenter                   |
+| C-j    | isl-toggle-multi-search-in-line|
 
 Don't forget =C-h m= which will show you all these commands while
 running isearch-light.
 
 ** About multi matching
 
-By default =isl-search= uses multi matching like Helm, with limitation to
-symbol, not line like in Helm, that means "foo bar" matches "foo-bar"
-or "bar-foo" but not a line with "foo" and "bar" inside e.g. "foo some
-text bar", when you want to match something like this you have to use
-regexp e.g. "foo.*bar".
+By default =isl-search= uses multi matching like Helm, with limitation
+to symbol, not line like in Helm, that means "foo bar" matches
+"foo-bar" or "bar-foo" but not a line with "foo" and "bar" inside
+e.g. "foo some text bar", when you want to match something like this
+you have to use regexp e.g. "foo.*bar" or switch to multi line
+matching with C-j aka =isl-toggle-multi-search-in-line=.
 
 To use multi matching, separate text with one space, each pattern
 beginning by "!" will mean match everything but this, e.g. "foo !bar"
@@ -116,7 +118,8 @@ will not match "foo-bar" but will match "foo-baz".
 [[screen_shot1.png]]
 
 Note: You can jump to =helm-occur= for a line based search.
-You can also jump to [[https://github.com/victorhge/iedit][iedit-mode]] with 
multi match pattern.
+You can also jump to [[https://github.com/victorhge/iedit][iedit-mode]] with 
multi match pattern (you may have
+an error if all the matches do not refer to the same word or symbol).
 
 ** Isearch-light vs helm-occur
 

Reply via email to