Closed pbrisbin closed 13 years ago
Hey
Thanks for submitting this. Would you like to generate a patch for this so that it when I apply it it correctly attributes you as the author?
Cool, as long as you approve the approach I can fork/pull req soon. I'll add a note about the new option in the helptext, but feel free to reword when you pull in.
Sounds good. I'm happy with it as I don't see it adversely affecting anyone. I'm not sure that I'd be able to get it upstreamed though, but that's a separate issue :)
Just out of interest, what version of Vim are you using, and on what platform?
I'm using 7.3 on 64bit Arch linux. I can provide vim --version if you'd like (it's long). I installed gvim for the xclipboard support but only ever use the cli executable (and launch chrome there from).
Also, doh. I didn't realize this wasn't the "official" repo for the script. I probably wouldn't have submitted either of these issues had I known this was just a periodically updated mirror... Feel free to just close the other one. I also wouldn't worry about applying my changes if you don't want to manage the possible conflicts next time you update from upstream.
I merged the pull request you sent as I think it will likely be useful to others who face the same issue.
Hello,
I've had one nagging issue with this plugin, when I launch my browser via the *Doc commands, the vim window becomes corrupt. All the text disappears and only reappears as I move the cursor over each line. I found that this could be avoided by not launching the browser
silent
ly. I'm not sure the source of the problem (likely not you), but I like this workaround for now.In case you're interested, here is a small patch which allows another option to choose if the browser should be launched as is currently or without the
silent
. I just putg:haddock_browser_nosilent = 1
in my vimrc.I'm no expert in vim so there's likely a more elegant solution out there.
Thanks!