On Nov 14, 1:41 pm, Alexey Radkov <[email protected]> wrote: > Hi. > > I found a bug in buffer unloading algorithm due to kind of > misconception between how close_buffer() treats buffer unloading data > > [snip] > > I made a simple patch that just temporarily puts '\0' in b_p_bh[0] > before calling to close_buffer() from set_curbuf() and then revert the > first character back. It works fine but I think that a better way is > to add a parameter to close_buf() that will make this function aware > about aim it was called for. As i do not know how to attach files i > put it just here: >
This works, but the danger is that lines get mangled by wrapping. Probably you're using the Google Groups (or similar web-based) interface, which is why you cannot attach a file. If you instead send an email to [email protected] you can attach files as normal to your email, and it will hit the list. vim- [email protected] will go to the same place. > > I do not know if it is effective to report bugs in this maillist. But > I did not find other bug reports mechanism in vim. > This is a very good place to report bugs, especially if you have a patch attached to fix the bug. People report bugs here all the time, in fact it was only recently that a bug tracker was enabled on the Google code site for Vim: http://code.google.com/p/vim/issues/list Entering an issue on the Google code site automatically notifies this mailing list anyway. -- 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
