On Wed, Mar 7, 2012 at 3:03 PM, Erik Falor <[email protected]> wrote: >> By the way, I notice in my default font in IE8, that the line number >> column has 1px gaps between some of the lines. I am trying to fix this >> in the current version, but it is being a pain in the ass to figure >> out. If you happen upon a fix, do let me know. > > Isn't IE always a PITA? I think my blog looks like garbage on that > browser. >
It is, but actually I noticed the problem first in Firefox with my "unselectable areas" changes. Further investigation shows all browsers seem to be affected with at least some fonts. My current workaround I'm playing with is to add a 1px padding to the elements which have background. I first tried experimenting with lineheight, but that just makes wrapped lines look stupid and sometimes causes other problems (I don't remember what precisely). >> Also, I mostly do >> development on a branch on a clone listed on Vim's google code site. >> Let me know if you want commit access instead of just mailing patches >> around, I'll probably be pretty liberal about it as long as nobody >> tries to update/establish tagged versions. > > I'd like access. I saw mentions in the comments about looking at Hg > logs and history, but never found the URL or name of the clone. I'll > look closer at the google code site. Let me know if you need me to > send my SSH pubkey or other credentials. After some web searching it looks like sadly you cannot add committers to server-side clones of a project. You could create a server-side clone of my clone and we could pull back and forth as needed, or I can create a new full-blown project, but I'd rather go for the former option rather than creating a new project on google code or BitBucket. The revision numbers listed in the change log comments refer to Vim's "default" branch, they are the revision where Bram actually incorporates the version. I do development on the 2html-dev branch in my clone, and add a tag for each release I send to Bram. There's significant work in the server-side clone for the unselectable regions feature, but it's not yet quite ready. The regions rely on using readonly <input> blocks, which sadly don't have well-defined width, causing problems in Chrome and Safari for the foldcolumn. You should be able to apply your patch to the tag for 2html_v7.3.10. -- You received this message from the "vim_use" 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
