On Thu, Jun 6, 2013 at 2:37 PM, Roland Eggner <[email protected]> wrote: > Hi Ben! > > On 2013-06-06 Thursday at 07:27 -0700 Ben Fritz wrote: >> On Thursday, June 6, 2013 3:08:24 AM UTC-5, Roland Eggner wrote: >> > … … >> > I reported not clearly enough, I am afraid. There are 2 probably related >> > bugs: >> > >> > (1) Commit “7.3.880 Problem: When writing viminfo, old history lines may >> > replace lines written more recently by another Vim instance. Solution: >> > Mark >> > history entries that were read from viminfo and overwrite them when >> > merging with >> > the current viminfo.” turned the viminfo feature effectively to a >> > “vimforget” >> > feature. The patch provided below reverts this. >> >> Certainly not the best solution. >> >> The patch may have broken :wviminfo, but the normal method of writing and >> reading viminfo (on Vim enter and exit) is much more useful after the patch. > > May I assume, your certainty is based on a test of my patch in a setup > following > the description I provided together with the patch? What particular > shortcomings did you encounter? >
I must have misunderstood your patch. You said your patch reverted the history-preserving change. I had the impression from your description that this is the only change you made. I did not apply and test the patch. I thought for some reason you were fixing :rviminfo and :wviminfo at the expense of the normal method, or were getting rid of the changes that allowed history to be merged instead of overwritten. These were the concerns I meant to raise. If this is not the case, then you may ignore my previous message. -- -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
