[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#16546: C-s vs. whitespace highlighting
From: |
Juri Linkov |
Subject: |
bug#16546: C-s vs. whitespace highlighting |
Date: |
Tue, 28 Jan 2014 09:30:07 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (x86_64-pc-linux-gnu) |
> IMO, Emacs should refrain from making permanent changes to the search
> string, as given by the user. IOW, the search string should be kept
> untouched, and any transformations of it should be done "on the fly"
> to achieve the intended behavior, based on both the _current_ search
> string and the _current_ user options that govern the search behavior.
I agree that we have to keep the original string, and interpret it
differently according to the current search options.
And to distinguish the case when the search string was entered manually
and the case when the search string was yanked with `C-s C-y' I think
we should inspect the stack of `isearch-cmds'. If it contains two or more
manually entered space characters then preserve them while matching whitespace.
- bug#16546: C-s vs. whitespace highlighting, (continued)
- bug#16546: C-s vs. whitespace highlighting, Dani Moncayo, 2014/01/25
- bug#16546: C-s vs. whitespace highlighting, Nicolas Richard, 2014/01/26
- bug#16546: C-s vs. whitespace highlighting, Dani Moncayo, 2014/01/27
- bug#16546: C-s vs. whitespace highlighting, martin rudalics, 2014/01/27
- bug#16546: C-s vs. whitespace highlighting, Dani Moncayo, 2014/01/27
- bug#16546: C-s vs. whitespace highlighting, Juri Linkov, 2014/01/27
- bug#16546: C-s vs. whitespace highlighting, Dani Moncayo, 2014/01/27
- bug#16546: C-s vs. whitespace highlighting,
Juri Linkov <=
bug#16546: C-s vs. whitespace highlighting, jidanni, 2014/01/25