Tom Purl * 3/1/2007 7:04 PM :
Okay, so now I am really an outsider to this whole issue as in that I
have just been following the whole thread with interest because i
regularly check vim tips/scripts at vim.org ...
For more information of where people are right now, check the mailing
list
On Fri, 2007-02-23 at 09:46 -0600, Tom Purl wrote:
Ok everyone, the project's created:
* http://code.google.com/p/vimtips/
I think there's a major disadvantage in using the code.google.com wiki
- it only allows people who have been added to the project to edit the
wiki via the web
Okay, so now I am really an outsider to this whole issue as in that I
have just been following the whole thread with interest because i
regularly check vim tips/scripts at vim.org ...
For more information of where people are right now, check the mailing list
archive for a thread titled VimTips
On Fri, 23 Feb 2007 06:32:28 +0200
Ali Polatel [EMAIL PROTECTED] wrote:
There is one thing to mention about parsing tips. Are we going to
put the additional comments to the wiki? There are many useful
comments but there are also many useless junk.
It would be _lots_ of work to look at
There is one thing to mention about parsing tips. Are we going to put
the additional comments to the wiki? There are many useful comments but
there are also many useless junk.
It would be _lots_ of work to look at every comment and see if they're
useful or not.
What are your ideas?
Ok everyone, the project's created:
* http://code.google.com/p/vimtips/
I think there's a major disadvantage in using the code.google.com wiki
- it only allows people who have been added to the project to edit the
wiki via the web interface (please correct me if I'm wrong). At least
if it
Tom Purl wrote:
There is one thing to mention about parsing tips. Are we going to put
the additional comments to the wiki? There are many useful comments but
there are also many useless junk.
It would be _lots_ of work to look at every comment and see if they're
useful or not.
What are your
Sorry for answering off list again, I can not post to the list.
That's unfortunate. I'm happy to post this to the list.
There is one thing to mention about parsing tips. Are we going to put
the additional comments to the wiki? There are many useful comments
but there are also many useless
Tom Purl wrote:
Ok everyone, the project's created:
* http://code.google.com/p/vimtips/
I think there's a major disadvantage in using the code.google.com wiki
- it only allows people who have been added to the project to edit the
wiki via the web interface (please correct me if I'm
* Swaroop C H ([EMAIL PROTECTED]) wrote:
could you please convert a few tips using your script and them
post them on the wiki? I would love to see the final output.
A heads up ... the script isn't working for other tips, I'll try to
polish the script in the morning (well, it's 2 am here).
Fantastic! I pasted this as-is into the wiki and here are the results:
* http://code.google.com/p/vimtips/wiki/1504_External_commands_on_Windows
We need to replace the code tags with triple braces as a start. Also,
we may want to add bullet points to the metadata fields.
Here's a reference
I added your script to the project's SVN repository:
* http://code.google.com/p/vimtips/source
We now have a total number of *three* scripts that could possibly convert
the tips. Thanks a ton to Dr. Chip, Swaroop, and Ali for contributing
scripts!
I really think that this should be enough
Tom Purl wrote:
I just checked the Google Code site (http://code.google.com/hosting/),
and couldn't find a Vim or VimTips project. I'd try creating it, but I
feel like someone more official to the project should do so. I think
someone should do it before someone else takes the name (like some
Tom Purl wrote:
I just checked the Google Code site (http://code.google.com/hosting/),
and couldn't find a Vim or VimTips project. I'd try creating it, but I
feel like someone more official to the project should do so. I think
someone should do it before someone else takes the name (like some
script could do the job.
Honestly, the only hard part here is step 2, and we can host our
script(s) on Google code if we would like.
If it's ok with you guys, I would be happy to set up a Vim Tips project
on the Google code site and create a section for the conversion scripts.
I know that Bram said
On 2/21/07, Tom Purl [EMAIL PROTECTED] wrote:
* We can host the scripts necessary to convert the tips there
* We can post examples of how the tips might look so we can gain
feedback
* We can take the name before some nefarious person decides to
Google-squat :)
So yeah, what do you guys
2. Convert said content into a the wiki markup language that Google
likes to use. We can do this a variety of ways. I'm partial to
python,
perl, and shell tools like sed and awk.
I know nothing about the tips format as they exist now, nor Goggle's
wiki markup language, but gimme a few docs pre-
Ok everyone, the project's created:
* http://code.google.com/p/vimtips/
Hooray!
The next step is to see some conversion script ideas. If you're the type
of person who can write a script like this in 15 minutes, then by all
means do so and send it to me. Otherwise, we can discuss it on the
On 2/21/07, Tom Purl [EMAIL PROTECTED] wrote:
The next step is to see some conversion script ideas. If you're the type
of person who can write a script like this in 15 minutes, then by all
means do so and send it to me. Otherwise, we can discuss it on the
mailing list unless people think its
On 2/21/07, Tom Purl [EMAIL PROTECTED] wrote:
The next step is to see some conversion script ideas. If you're the
type
of person who can write a script like this in 15 minutes, then by all
means do so and send it to me. Otherwise, we can discuss it on the
mailing list unless people think
Quick updates:
1. I posted all of the scripts that were sent to me today on the Google
site in the svn repository under the scripts directory.
2. I've added everyone who has sent me his or her google id as project
participants.
Thanks again!
Tom Purl
On 2/22/07, Tom Purl [EMAIL PROTECTED]
Tom Purl wrote:
Ok everyone, the project's created:
* http://code.google.com/p/vimtips/
Hooray!
The next step is to see some conversion script ideas. If you're the type
of person who can write a script like this in 15 minutes, then by all
means do so and send it to me. Otherwise,
On 2/18/07, Tom Purl [EMAIL PROTECTED] wrote:
I just checked the Google Code site (http://code.google.com/hosting/),
and couldn't find a Vim or VimTips project. I'd try creating it, but I
feel like someone more official to the project should do so. I think
someone should do it before someone
Tom Purl wrote:
I just checked the Google Code site (http://code.google.com/hosting/),
and couldn't find a Vim or VimTips project. I'd try creating it, but I
feel like someone more official to the project should do so. I think
someone should do it before someone else takes the name (like
On 2/17/07, Kim Schulz [EMAIL PROTECTED] wrote:
On Fri, 16 Feb 2007 02:37:28 +0100
Bram Moolenaar [EMAIL PROTECTED] wrote:
Hi all,
Google code has now added support for a wiki. This means open source
projects can have a wiki that's free, fast and reliable
(hopefully :-).
the existing structure of Vim Help could be used.
OTOH the perfect is the enemy of the good, so perhaps you just want to move
all tips as is, then have people slowly massage them into a coherent set of
useful tips.
The wiki tips project would only be helpful after some severe editing IMHO.
Some tips
slowly massage them into a coherent set of
useful tips.
We can do both. But we need to start somewhere. Moving all tips over
is the first step. We can simply keep the tip number at first. Making
some kind of index is something that anyone can do once the wiki exists.
The wiki tips project
On Fri, 16 Feb 2007 02:37:28 +0100
Bram Moolenaar [EMAIL PROTECTED] wrote:
Hi all,
Google code has now added support for a wiki. This means open source
projects can have a wiki that's free, fast and reliable
(hopefully :-).
http://code.google.com/hosting/
During my
On 2007-02-16, Bram Moolenaar [EMAIL PROTECTED] wrote:
Hi all,
Google code has now added support for a wiki. This means open source
projects can have a wiki that's free, fast and reliable (hopefully :-).
http://code.google.com/hosting/
During my presentation last Tuesday the idea
Bram Moolenaar wrote:
Hi all,
Google code has now added support for a wiki. This means open source
projects can have a wiki that's free, fast and reliable (hopefully :-).
http://code.google.com/hosting/
During my presentation last Tuesday the idea came up (again) to move the
Vim tips
30 matches
Mail list logo
