Hi Vimmers,

Have some patches. 1 and 2 are trivial fixes.

With 4, I've tried to hack my way through getting scrollbind to work  
when scrolling unfocussed windows (the one not containing the cursor).  
This was annoying me, because when I had a vert split diff open, my  
mouse wheel wouldn't scroll both windows in sync half the time (when  
my mouse cursor was over the inactive pane). This patch contains  
changes exclusively from the Vim tree. This being my first venture  
into that code, someone more familiar with the codebase should  
definitely review it before it gets accepted. I just did some  
superficial testing, and it seemed to work, but I don't know the  
nuances of scrollbind.

Should this go into the Vim tree, or MacVim? It's a bigger issue on  
Mac OS X than on other platforms, since on Windows, the scroll wheel  
scrolls the focussed window, not the one under the cursor. (I didn't  
try any Linux WMs.)


Patch 3 is a one-liner that I'm not completely comfortable with. It  
makes a call to read the viminfo when a preloaded Vim instance is  
taken and run. I'll give some background for why I did it: I was doing  
some stuff where I opened a few files in a Vim instance, made some  
changes, then closed the instance. I was repeating this several times.  
Quickstart was on, and I noticed that my registers were oscillating  
between two sets. After working in one instance, changing some  
registers, and closing it, those registers were written to my viminfo.  
When I opened another instance, it was already preloaded with an old  
viminfo, so the changes weren't there. But opening this instance  
caused another to preload in the background, getting the new viminfo  
with the changed registers again. Closing the second instance  
overwrites the viminfo again, and so it continues.

The reason I'm unhappy about this patch is because it raises two  
issues. First, should this be folded into a more general hook that's  
called when an instance is about to be used? And second, should we  
attempt to unify the viminfo across instances? I could imagine that  
when an instance is deactivated (i.e. when it's no longer the active  
window), it writes its viminfo, and the next instance to be activated  
reads it. (This could be tricky, because the newly-activated instance  
would have to wait until the previous one had finished writing.)


And finally, I'm working on some changes to drag and drop (getting my  
beloved "replace dropped buffer" feature back). It's not done yet, and  
the discussion from 2008-07 ("Open files in ...?") are scaring me.


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Attachment: 0001-Fixed-typo-in-debug-message-strings.patch
Description: Binary data


Attachment: 0002-Fixed-opening-with-search-text-to-do-an-inclusive-se.patch
Description: Binary data


Attachment: 0003-Reload-viminfo-when-using-a-cached-Vim-process.patch
Description: Binary data


Attachment: 0004-Keep-scrollbind-bound-windows-in-sync-when-unfocusse.patch
Description: Binary data




Jonathon Mah
[email protected]





Jonathon Mah
[email protected]


Reply via email to