How about sharing vim tips every week as you are writing the book? If you write me one email 8 months from now, I'll probably forget who you are.
I did this with my book. 0 unsubscribes.
Edited to add: Might want to have a "just tell me when the book is ready, no more o' these" just in case. But really, if people aren't interested in content similar to what's in the book, why are they buying the book?
We need a vim installer that can do all those things which you will have to otherwise spend time and work endless hours customizing vim to do.
The reason why people move to modern GUI based editors is those editors do many things out of the box which you have to otherwise spend time learning and then do it.
Sure the initial set up is difficult. But once it's done, it's done.
And I think that right there is the reason such a tool will never truly catch on. (Nearly) everyone who currently uses Vim wouldn't use it. It is why things like Cream never caught on I think; there really is not as much demand as some people think.
Are you trying to argue that it could not be made quicker and easier, and that there'd be no benefit to making it quicker and easier?
I think Vim is great and if, as seems the case, a lot of people are put off it because of the large amounts of up-front effort it requires, then anything which helps lessen that initial effort is a good thing in my books.
I think it's a shame that there's often a kinda moralising attitude towards this issue - as if the present level of up-front effort is how things should be, and if, for whatever reason, you aren't prepared to put up with it, then they're not a "Vim person".
Switching from a modern GUI editor to another is easy because they are all more or less the same. Switching from a modern GUI editor to Vim is hard because they are fundamentally different. Why even trying to switch if one doesn't recognize the need to put some effort into it?
That's up to you.
I think Vim is more productive, and I'd like to see more people getting that benefit from it.
Myself and 2 other guys from #vim on Freenode tried doing this a few years ago, but it wound up failing because we couldn't decide on that perfect set of stuff to put in it. Perhaps the idea would be more successful if there was only one developer to make decisions, but...
In the end it made for a far better book, and I believe the author made as much money, possibly even more than if he had followed a more traditional process. In any case I don't suppose you were planning to retire on the proceeds of a book on Vim.
Best of luck, however you choose to write it. I look forward to reading it.
This is one that I bought and enjoy. He also set up a mailing list so readers had a place to discuss.
How about a promise on the page not to share our email with any third parties?