Hi, On Fri, Feb 19, 2021 at 6:12 PM obcat <[email protected]> wrote:
> I believe you only intend to ignore case in the command argument. ":edit" > and ":Edit" would still be different. > > I intend to ignore case in the whole keyword rather than only the command > argument. For example, suppose that the output of :history :is as follows: > > # cmd history > 1 edit foo.txt > 2 Edit bar.txt > 3 edit baz.txt > 4 Edit qux.txt > > 5 history : > > I want to be able to type :edit b and press Up to complete :edit baz and > press Up again to complete :Edit bar.txt. > > I actually would like this to be more clever. E.g. when typing ":e file" > and pressing it would also find ":edit filemore". Also ignoring extra > colons or white space, which cause no semantic difference. > > That sounds good! It would be interesting to add a new option like > histsearchopt to change the behavior of Up / Down in the cmdline-mode so > that we can specify something like set histsearchopt=ignorecase or set > histsearchopt=clever. > > > Based on the description, it looks like you are looking for fuzzy search. We should add 'fuzzymatch' to 'wildoptions' and enable fuzzy completion for all the commands. Regards, Yegappan -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7nS2N4mjYAc4YHp4dU1-toVFqQ_MLVKs%2BAvhRnODoUH_w%40mail.gmail.com.
