> * The other two both suffer from a rather poor visual impression
> unless we get into custom parsers/converters and essentially re-invent
> the wheel.
Could be changed. Now that Vim has the conceal feature ... we could
extend the Vim help syntax ..
Creating parsers is not that hard using the right tools.
> * Having said that, having a way of converting Vim help file syntax
> into something pretty would be really nice, especially if it could be
> automatically presented for scripts that contain doc/*
Strong argument :)
So what does vim help file syntax miss?
- it has links
- headlines ? :-(
(everything after long = or - separators?)
- links
- anchors
- code blocks
What else would be required? (maybe some standardization)
Eg if_lua also contains such headlines:
Properties
----------
o "w()" sets "w" as the current window.
o "w.buffer" contains the buffer of window "w" (read-only).
IMHO something editor friendly should be used.
> * This is a personal opinion and I fully understand that others will
> disagree fervently, but my experiences with Git have generally
> involved things going wrong and stuff being lost so for the
> git-inexperienced among us, it might be worth either (in order of my
> preference) using Mercurial (like the vim source itself), offering
> both Mercurial and Git access depending on what the user prefers or
> giving instructions on how to use hg-git to give people another
> alternative.
git can always be accessed by mercurial bridge.
Also when using github there is a SVN protocol implementation for git
AFAIK.
Also for contributing something like "git diff > file" send file would
be enough. We could provide a Vim command.
I'll shut up and wait for another days - waiting for comments and
thoughts.
> "Keep what is Vim?" at start page?
Agreed.
Marc Weber
--
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
No comments:
Post a Comment