On 4 Oct, 14:34, Ben Fritz <[email protected]> wrote: > On Oct 3, 12:06 pm, Carlo <[email protected]> wrote: > > > Sorry, I sent that off too early. To elaborate: > > > * It's built on Google App Engine > > * It regularly retrieves the latest doc files > > fromhttp://vim.googlecode.com/hg/runtime/doc/andprocesses them > > * The Google custom search it uses doesn't work, presumably since > > Google hasn't indexed the contents yet > > > Please let me know any feedback. I'm going to hold off advertising its > > existence more widely (i.e. vim_use list) for now. > > > Bram, let me know if you approve of this or would like any changes to > > it. Everyone else, hope you like it. > > Compare the main page of vimhelp.appspot.com to the main page of > vimdoc.sourceforge.net/htmldoc/ > > I notice that on vimhelp.appspot.com, the CTRL-D, CTRL-T, CTRL-O, etc. > are all nicely colored, indicating that something is recognized as > special about them, but that is all. On sourceforge, these are all > links. Although the sourceforge docs are not colored, I find them more > useful in this specific case. Is this something that can be fixed?
Fixed now for CTRL-sequences and some other miscellaneous cases. Although it's true that the way that vimdoc.sf.net links absolutely everything that is linkable has its advantages. Perhaps I will experiment later on with making more things links, without making them stand out too much from the other text. Regarding Bram's comment, I've also added some quick links to the top and bottom of each page. > You have a good idea of an automatic update mechanism, certainly. I > find that out-of-data help files online can be very annoying. Thanks. To respond to Bram's query on this: I've got an hourly cronjob that downloads http://vim.googlecode.com/hg/runtime/doc/ and all .txt files listed there. (It uses the HTTP "ETag" cacheing mechanism to minimise traffic, and to notice when files haven't changed.) It then generates the HTML-ified versions. By the way, the site search works now. Carlo -- 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
