> 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 m
> 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 "Vi
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
> > wik
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 c
> 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
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 i
>> 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 leas
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 allow
> 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
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
* Tom Purl ([EMAIL PROTECTED]) wrote:
> 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
> scrip
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 scrip
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 tags with triple braces as a start. Also,
we may want to add bullet points to the metadata fields.
Here's a reference to the
* 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 he
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. Othe
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]>
> On 2/22/07, Tom Purl <[EMAIL PROTECTED]> wrote:
>> Swaroop, 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.
>
> Looks like I can't add anything to the wiki until the admin adds me as
> part of the project :)
Wow, tha
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).
Thanks,
Swaroop
On 2/22/07, Tom Purl <[EMAIL PROTECTED]> wrote:
Swaroop, 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.
Looks like I can't add anything to the wiki until the admin adds me as
part of the project :)
Here's the output
> 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 pe
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
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
mail
>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
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 thi
> 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
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
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 (l
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 someon
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
malicious Emacs u
John Beckett wrote:
> Bram Moolenaar wrote:
> > Using the project name VimTips would be good.
>
> Everyone here is used to the name "Vim Tips" so VimTips sounds good, but on
> a wiki I suggest that the name should be just "Vim".
I'm sure we will use the wiki for other things than tips some day
Bram Moolenaar wrote:
Using the project name VimTips would be good.
Everyone here is used to the name "Vim Tips" so VimTips sounds good, but on
a wiki I suggest that the name should be just "Vim".
It seems logical to me that a Vim Tips wiki would start with a (brief) page
outlining what Vim
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 :-).
>
>
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
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
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
36 matches
Mail list logo
