Hi list and Bram. I got a report of strange behavior about vim's search history. And I have wrote an attached patch to fix it. Please check below description and the patch.
Thanks ==Description== Operations to reproduce: 1. Search backword: ?foobar/e<CR> 2. Search forward: /foobar/e<CR> 3. /<UP> Expected: Shows /foobar/e Actually: Shows /foobar\/e Problem: After OP1, "foobar/e" and '?' are stored into history as histstr (call this Hist#1). When OP2, it try to store "foobar/e" and '/' (Hist#2) but in_history() doesn't check separator character, so it matches with Hist#1 and in_history() returns true, and Hist#2 isn't stored into history. At OP3, search from history then match Hist#1, and it realize separator character is not match, then replace those escape characters. Solution: Make in_history() function sensible of separator character for search history, to store Hist#2. -- MURAOKA Taro <[email protected]> -- 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
search_history_direction.diff
Description: Binary data
