Re: VimWiki - released finally
On Tue, June 5, 2007 6:51 am, Sebastian Menge wrote: Am Dienstag, den 05.06.2007, 13:38 +0200 schrieb misi e: all what is missing now (as long as I know) an interface to access this wiki from vim itself .) Easy with http://wikipediafs.sf.net :-) Also, don't forget about the ItsAllText plugin for Firefox. Tom Purl
Re: VimWiki - released finally
On Tue, June 5, 2007 5:41 am, Sebastian Menge wrote: [cross-posted to vim, vim-dev, vim-announce, wikia-l] Hi all Finally I have imported all the vim tips from http://vim.org/tips to http://vim.wikia.com and set up a minimal infrastructure to keep things going. Not everything is perfect, but I think it is usable now. Wow! This really looks excellent Sebastian. Also, it look very robust and complete. I really think that this implementation of the tips wiki is sufficient and complete. Does anyone disagree? If so, what do you suggest? Thanks again! Tom Purl
Re: VimWiki - released finally
How do you update the categories? I can't seem to find that text when I edit the full page. Thanks! Tom Purl On Tue, June 5, 2007 6:51 am, Sebastian Menge wrote: Am Dienstag, den 05.06.2007, 13:38 +0200 schrieb misi e: all what is missing now (as long as I know) an interface to access this wiki from vim itself .) Easy with http://wikipediafs.sf.net :-) Cool would be a vim-plugin that detects [[WikiPage]] and produces a link that opens WikiPage.mw from the wikipediafs. Seb.
Re: VimWiki - released finally
On Tue, June 5, 2007 12:36 pm, [EMAIL PROTECTED] wrote: Hello, Tom Purl [EMAIL PROTECTED] wrtoe: How do you update the categories? I can't seem to find that text when I edit the full page. We need to edit the tips to add them one, or several category tags. e.g.: [[Category:Integration]] But I am editing a tip, and I don't see any reference to a [[Category:Foo]] link. Thanks! Tom Purl
Re: VimWiki - released finally
On Tue, June 5, 2007 11:34 am, Brian McKee wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5-Jun-07, at 12:00 PM, Tom Purl wrote: On Tue, June 5, 2007 5:41 am, Sebastian Menge wrote: [cross-posted to vim, vim-dev, vim-announce, wikia-l] Finally I have imported all the vim tips from http://vim.org/tips to http://vim.wikia.com and set up a minimal infrastructure to keep things going. Not everything is perfect, but I think it is usable now. Wow! This really looks excellent Sebastian. Also, it look very robust and complete. I really think that this implementation of the tips wiki is sufficient and complete. Does anyone disagree? If so, what do you suggest? Indeed - looks good! Can someone point out how I can get an RSS feed of the recent changes? The page is here http://vim.wikia.com/wiki/Special:Recentchanges Perhaps it's a feature we need to enable? I see some other wikia sites seem to append feed=rss to the url, but that doesn't work for the vim wiki... Brian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) Comment: Verify this email or encrypt your email for free - see gnupg.org iD8DBQFGZZB6GnOmb9xIQHQRAiKaAKDdpaAT2+ABJxXbqTUMNz+B4m6Q7ACfX8sj 2xm2SBX9KwsY+Zw0y8T+D1w= =5Eug -END PGP SIGNATURE- The recent changes page has links for both rss and atom feeds. HTH! Tom Purl
Re: VimWiki - released finally
On Tue, June 5, 2007 1:14 pm, Brian McKee wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5-Jun-07, at 1:59 PM, Tom Purl wrote: On Tue, June 5, 2007 11:34 am, Brian McKee wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5-Jun-07, at 12:00 PM, Tom Purl wrote: On Tue, June 5, 2007 5:41 am, Sebastian Menge wrote: [cross-posted to vim, vim-dev, vim-announce, wikia-l] Finally I have imported all the vim tips from http://vim.org/ tips to http://vim.wikia.com I really think that this implementation of the tips wiki is sufficient and complete. Does anyone disagree? If so, what do you suggest? Can someone point out how I can get an RSS feed of the recent changes? The page is here http://vim.wikia.com/wiki/Special:Recentchanges The recent changes page has links for both rss and atom feeds. Oh - I guess it's in the headers only - I was looking for a clickable link rather than just the indicator in the url bar. If there's a clickable link supposed to be there - I'm not seeing it and a quick /atom/ of the source only shows the link in the headers. Here's what I'm seeing: URL: http://vim.wikia.com/wiki/Special:Recentchanges Using both IE and Firefox, I'm am seeing both RSS and Atom links in the toolbox box. This is true whether I am logged in or not. Here's exactly what I see in the toolbox box: Toolbox * RSS Atom * Upload file * Special pages What are you seeing? Thanks, Tom Purl
Re: VimWiki - released finally
On Tue, June 5, 2007 2:29 pm, [EMAIL PROTECTED] wrote: Selon Tom Purl [EMAIL PROTECTED]: On Tue, June 5, 2007 12:36 pm, [EMAIL PROTECTED] wrote: Hello, Tom Purl [EMAIL PROTECTED] wrtoe: How do you update the categories? I can't seem to find that text when I edit the full page. We need to edit the tips to add them one, or several category tags. e.g.: [[Category:Integration]] But I am editing a tip, and I don't see any reference to a [[Category:Foo]] link. IIRC, the category won't appear in the general categories list until it has a page associated (edit the description of the category). However, if you have several pages for a given undocumented category (i.e. having [[Category:Foo]]) and then open the default page for the category (i.e. click on the red link) you will see all the related pages of that category. From my very little experience regarding the organisation of a wiki from scratch, I'll say that everytime we put a page into a new category, we have to define right away the page of that new category. Otherwise, another similar, but different) category may emerge. I don't think that I'm describing my problem very clearly. I'm trying to edit the following page: * http://vim.wikia.com/wiki/Indenting_%22throws%22_in_java When I click on the edit link, I should see something similar to this: some text some more text [[Category:Foo]] Instead, all I see is this: some text some more text One would assume that if the raw version of the page didn't include a [[Category:Foo]] link, then the published version also wouldn't include any category information. The weird thing is that the published version of this particular page includes two categories; Review and VimTip. So what I don't understand is, why can't I change these categories? I've been editing Mediawiki pages for 4 years, and I've never seen anything like this. Thanks in advance for any help! Tom Purl
Re: VimWiki - First Beta
At first blush, it looks really good. I'm making a httrack copy of it
right now since I know that it won't be up much longer. Later I can
give you a better review :)
Great work!
Tom Purl
On Tue, May 29, 2007 7:04 am, Sebastian Menge wrote:
Hi all
Access the first beta here: http://tinyurl.com/34kfj5
I did a lot of experiments over the weekend. I mostly used a local
mediawiki-installation and even from localhost to localhost a full
import takes about an hour. Im excited to learn how long it will take to
import to a remote mediawiki ...
Some notes about it:
1) references to other tips get automatically replaced like in
http://tinyurl.com/34kfj5/VimTip123
2) references to the vim help get replaced by links to the
vim-doc.sf.net as in http://tinyurl.com/34kfj5/VimTip26
3) the following chars are forbidden in titles : [] {} # | +
These get replaced by __HASH__ __PLUS__ and the like. This is ugly but i
dont want to do any editorial work on the articles now.
4) The formatting of the tips and comments gets broken fairly often.
This is because original tips are verbatim and could contain wiki-markup
(eg. one space indent is interpreted as verbatim by the wiki or the vim
command '[[' starts a wiki tag)
5) we definitely need to edit the tips later on. I wont tweak the script
up to infinity. Some things are easier repaired by Hand (e.g.
http://tinyurl.com/34kfj5/VimTip7 )
My host is only accessible until 17h MESZ (thats 3h from now on). Then
i'll be offline.
Please give feedback!
Sebastian.
Re: VimWiki - First Beta
On Tue, May 29, 2007 9:53 am, Tom Purl wrote: On Tue, May 29, 2007 8:45 am, Yakov Lerner wrote: On 5/29/07, Sebastian Menge [EMAIL PROTECTED] wrote: Hi all Access the first beta here: http://tinyurl.com/34kfj5 Where can I see the recently posted/by recency view ? In other words, what's used for RSS ? I don't think that Mediawiki has this feature by default. Traditionally, I think you're supposed to explicitly watch a page and then you need to manually check your watched pages list. It's not the most efficient process in the world I know, but that's the way it's done most of the time. Wait, here's a better answer. It looks like both wikia and wikibooks offers an rss feed of the recent changes page. Since we have our own wiki instance on wikia, the recent changes page on has vim-related changes. On the wikibooks page, it appears that every single change to en.wikibooks.org is recorded on that page. This may be something to think about when we eventually choose our wiki host.
Re: VimWiki - First Beta
On Tue, May 29, 2007 8:45 am, Yakov Lerner wrote: On 5/29/07, Sebastian Menge [EMAIL PROTECTED] wrote: Hi all Access the first beta here: http://tinyurl.com/34kfj5 Where can I see the recently posted/by recency view ? In other words, what's used for RSS ? I don't think that Mediawiki has this feature by default. Traditionally, I think you're supposed to explicitly watch a page and then you need to manually check your watched pages list. It's not the most efficient process in the world I know, but that's the way it's done most of the time. HTH, Tom Purl
Re: VimWiki - Poll on wiki hosting
On Wed, May 23, 2007 3:03 am, Sebastian Menge wrote: Since John asked for wikibooks again, I've setup a poll to bring this discussion to an end. But before some last words: Wikibooks does not ask you to create structure in chapters,sections up front. It is not even suggested! Suggested is Content first and structure in chapters,sections later. But I don't see any structure in the 1500 tips. Neither now nor later. That's the reason why tips are separated from the manual! I agree with this. The tips are basically just a bucket of information, with very little structure. Also, some day it might be nice to add other content to the wiki that doesn't fit very well into a book format. One of the things I really like about Wikia is that it's run by the founds of the Mediawiki project. Here's some more information: * http://www.wikia.com/wiki/Why_use_Wikia%3F Of course, we could make it work on wikibooks, and it is a very nice site. Just my two cents, Tom Purl
Transparent Encryption and Decryption On Windows
I like to use OpenSSL to encrypt some files on my hard drive. I cobbled together the following script that allows me to transparently view and updated OpenSSL-encrypted docs using vim on Linux: augroup encrypted au! First make sure nothing is written to ~/.viminfo while editing an encrypted file. autocmd BufReadPre,FileReadPre *.des3 set viminfo= We don't want a swap file, as it write unencrypted data to disk autocmd BufReadPre,FileReadPre *.des3 set noswapfile Switch to binary mode to read the encrypted file autocmd BufReadPre,FileReadPre *.des3 set bin autocmd BufReadPre,FileReadPre *.des3 let ch_save = ch|set ch=2 autocmd BufReadPre,FileReadPre *.des3 let shsave=sh autocmd BufReadPre,FileReadPre *.des3 let sh='sh' autocmd BufReadPre,FileReadPre *.des3 let ch_save = ch|set ch=2 autocmd BufReadPost,FileReadPost*.des3 '[,']!openssl enc -d -des3 2 /dev/null autocmd BufReadPost,FileReadPost*.des3 let sh=shsave Switch to normal mode for editing autocmd BufReadPost,FileReadPost*.des3 set nobin autocmd BufReadPost,FileReadPost*.des3 let ch = ch_save|unlet ch_save autocmd BufReadPost,FileReadPost*.des3 execute :doautocmd BufReadPost . expand(%:r) Convert all text to encrypted text before writing autocmd BufWritePre,FileWritePre*.des3 set bin autocmd BufWritePre,FileWritePre*.des3 let shsave=sh autocmd BufWritePre,FileWritePre*.des3 let sh='sh' autocmd BufWritePre,FileWritePre*.des3 '[,']!openssl enc -e -des3 -salt 2/dev/null autocmd BufWritePre,FileWritePre*.des3 let sh=shsave Undo the encryption so we are back in the normal text, directly after the file has been written. autocmd BufWritePost,FileWritePost *.des3 silent u autocmd BufWritePost,FileWritePost *.des3 set nobin augroup END Basically, when I try to open a file with a des3 file extension, this chunk of code is executed. To get this to work on Windows, I changed the openssl lines to the following: autocmd BufReadPost,FileReadPost*.des3 '[,']!C:\OpenSSL\bin\openssl.exe enc -d -des3 2 /dev/null ... autocmd BufWritePre,FileWritePre*.des3 '[,']!C:\OpenSSL\bin\openssl.exe enc -e -des3 -salt 2/dev/null Also, I commented out the let sh='sh' lines, since I get the following value when I execute the :echo sh command: C:\WINDOWS\system32\cmd.exe However, when I try to open an encrypted file using this function, I get the following error: c: gvim .\secret.txt.des3 .\secret.txt.des3 [noeol][unix] 10L, 1304C shell returned 1 10 lines filtered Press ENTER or type command to continue ... 'sh' is not recognized as an internal or external command, operable program or batch file. The weird part is that I commented out all of the lines that explicitly reference 'sh'. What am I doing wrong? Is there anyone else who's usuing gpg or openssl with Vim? Thanks in advance! Tom Purl
Re: Transparent Encryption and Decryption On Windows
On Wed, May 23, 2007 11:05 am, Allan Wind wrote: On 2007-05-23T09:59:22-0500, Tom Purl wrote: Is there anyone else who's usuing gpg or openssl with Vim? I use one of the gpg plugins all the time: http://www.vim.org/scripts/script.php?script_id=1751 Problem solved. Thanks Allan. I was hoping to find an openssl solution since I'm so familiar with it and prefer symmetric to asymmetric encryption. However, since the gpg.vim plugin is so robust, and since it works with Windows, I decided to take a closer look at gpg. It turns out that I can use symmetric (password-only) encryption with gpg, and that the gpg.vim plugin supports it very well. I therefore converted my old encrypted file to use gpg encryption using the following commands on Windows: c:\foo dir 05/23/2007 10:42 AM 312 secret.txt.des3 c:\foo openssl enc -d -des3 -in .\secret.txt.des3 -out .\secret.txt (entered password) c:\foo dir 05/23/2007 10:45 AM 312 secret.txt 05/23/2007 10:42 AM 312 secret.txt.des3 c:\foo gpg --symmetric --output .\secret.txt.gpg .\secret.txt (entered password twice) c:\foo dir 05/23/2007 10:45 AM 312 secret.txt 05/23/2007 10:42 AM 312 secret.txt.des3 05/23/2007 10:46 AM 312 secret.txt.gpg c:\foo sdelete .\secret.txt c:\foo dir 05/23/2007 10:42 AM 312 secret.txt.des3 05/23/2007 10:46 AM 312 secret.txt.gpg I could then transparently edit the file using vim once I had installed the gpg.vim plugin. Thanks to everyone for their help, especially Markus Braun for writing such an excellent plugin. Tom Purl
Re: Vim Wiki - Tip Page Formatting Deadline
On Mon, May 21, 2007 10:16 am, Sebastian Menge wrote: A problem are tips that contain URLs to external sites (e.g. other tips) This is regarded as spam by mediawiki (captcha). Though the URLs are clean (since someone edited them before) we have to either import these tips by hand or convert all a hrefs in the script. I am able to add links to external web sites to a page without going through a captcha on the wikia site. If we do end up using the wikia site, I can run the conversion script and avoid a lot of the obstacles that are affecting the rest of you. Thanks, Tom Purl
RE: Vim Wiki - Wiki Template Proposal
On Tue, May 15, 2007 7:46 am, Sebastian Menge wrote: Am Dienstag, den 15.05.2007, 13:51 +0200 schrieb Zdenek Sekera: http://scratchpad.wikia.com/wiki/VimTest Since I'm the *only* person who has so far voted against using wiki templates, I will accept the fact that I'm in the minority and get out of the way :) Having said that, I really like the idea of using templates in this way if we're going to use macros. Also, check out the wikia site (vim.wiki.com). I uploaded Sebastian's logo. Thanks, Tom Purl
Re: Vim Wiki - Wiki Template Proposal
On Tue, May 15, 2007 9:51 am, fREW wrote: On 5/15/07, Sebastian Menge [EMAIL PROTECTED] wrote: Am Dienstag, den 15.05.2007, 10:03 +0200 schrieb Sebastian Menge: Now I have. There is a sample on http://scratchpad.wikia.com/wiki/VimTest But it leads to another problem: In a wiki we have no means to autoincrement the id. Thus the convention VimTipID for page names is not feasible. A good prefix is a must in my opinion, but what suffix? Howto assure that it is unique, not cryptic etc? Or what about complete freedom, and revising it afterwards? Perhaps we can even drop the prefix and use simply a category. Seb. That's a hard question. Would it be worth it to have a cron job or something that ran every night and moved/linked the newest tips to chronologically ordered tip numbers? I don't think doing that would be a problem, I just think it might be surprising when you make a tip, and it's gone the next day. But a redirect like wikipedia has might make that more reasonable. This sounds like an excellent idea to me, and not too terribly difficult to implement. Thanks, Tom Purl
Vim Wiki - Tip Page Formatting Deadline
Task: Wiki Format Sign-Off Deadline: Monday, May 21st (arbitrary, I know) Overview We've had some great, constructive discussions lately regarding how we will be creating and editing tips in the future. Before we can finally decide how this is going to work, however, we need to decide upon a page format for tips. The most recently-updated wiki tip examples can be found at the following URL: * http://scratchpad.wikia.com/wiki/VimTest The following tips should stand out: * http://scratchpad.wikia.com/wiki/VimTip1 * http://scratchpad.wikia.com/wiki/VimTip1_v2 This first tip uses the Template:Tip template (http://scratchpad.wikia.com/wiki/Template:Tip), and the second tip uses the Template:Tip2 template (http://scratchpad.wikia.com/wiki/Template:Tip2). Requested Actions = Please take a look at these tips, decide which one you prefer, and then provide constructive criticism for that tip's format. There's no such thing as a dumb comment. My Two Cents I really like VimTip1_v2, which uses the Tip2 template. Here's what I like: * No special formatting for commands or any other preformatted text. I think that this is an essential requirement for the initial conversion effort. * Easy to read * Succinct How do you want to handle comments? Typically on a Mediawiki site, you sign you comments like so: This is so cool! Which is then saved to the page like this: This is so cool! Tpurl 15:17, 15 May 2007 (UTC) It's a little ugly, but it's the norm in the wiki world. What do you guys think? Tom Purl
Re: Vim Wiki - Wiki Template Proposal
On Tue, May 15, 2007 10:13 am, fREW wrote: Also, check out the wikia site (vim.wiki.com). I uploaded Sebastian's logo. Thanks, Tom Purl I dig the page! That logo is great :-) I think you dropped off an a when you sent out the link though. http://vim.wikia.com/wiki/Main_Page Yikes! Thanks for fixing that typo. Tom Purl
Re: Vim Wiki - Wiki Template Proposal
On Tue, May 15, 2007 10:39 am, Sebastian Menge wrote: I attach the three scripts (without any warranty ;-) ). But it would be better to use a svn repository when we work on it together... Can we get commit access to http://vimtips.googlecode.com/svn/trunk/scripts/ ? Sure, I can handle that. First, you need a gmail/google account, however. Then I can add you as an SVN committer for the scripts repository. Thanks, Tom Purl
Re: VimWiki - again - but with a brand new option
Sorry it took me so long to respond to this Sebastian. On Thu, May 10, 2007 11:57 am, Sebastian Menge wrote: Am Donnerstag, den 10.05.2007, 10:44 -0500 schrieb Tom Purl: ... The proposal was not about the layout directly but about separating formatting from content! So feel free to change the formatting of the Template, but with this approach noone has ever to edit the tips directly to change the design ... Please dont mix content and markup at import time! Ohhh..., ok. Sorry for being so dense about this in the past. So your proposal is that we use Mediawiki template to do the actual formatting, and put the actual content into some sort of macro/function. From a conversion and sysadmin point of view, this is a great idea in my opinion. The problem is that it adds another barrier to entry for potential tip authors in my opinion. We are assuming that the tip authors have or are willing to gain an intermediate knowledge of Mediawiki authoring, just so they can post a tip. In my opinion, this is probably a bad idea. This will keep people from posting tips, and will make it more difficult to edit tips. I'd love to hear other opinions of course. ... Lets just go ahead on the Wikia. I think it's a great option, and am anxious to see which wiki works best for us. Thanks again! Tom Purl
Re: Wiki: structure, template and logo
On Mon, May 14, 2007 2:51 am, Sebastian Menge wrote: Hi The discussion about http://vim.wikia.com seems to die. I doubt we can hold the schedule if we don't do something. I agree! Using the scripts you posted it is very easy to publish all the tips in the template-format. So it's a matter of an hour to publish all the tips to the wikia. If there are at least some people on the list who like that proposal, I would do that this week. The layout can be changed at any time. More important is the real data: At the moment the template looks like this: http://scratchpad.wikia.com/wiki/Template:Tip Did i forget something important? I think that we should get more feedback about the template idea. I, for one, don't think that it's a good idea, and no one else has commented on it. I think I will start a new thread to encourage more input. I'll try to make it sounds exciting and controversial :) Further I have created a vim logo for the wikia (simply exported vim.svg to png and the right resolution), but it seems I am not allowed to upload it as Wiki.png which is protected and used as default logo. I have no idea about rights management in mediawiki, perhaps Tom as the admin knows more about that? Yeah, this sounds great! Email it to me and I'll be happy to upload it. Last point: Should the wiki be only for tips? Or should the tips be one part of the wiki? I would prefer the last: Setup a nice frontpage for the wiki that links to another page VimTips which is in turn a frontpage to the tips VimTipID. This is a great question. I think we should just focus on tips for now, and then worry about the taxonomy of the site later. BTW Is there someone around who knows the wikipedia standards well? Should it be [[VimTip], [[Vim Tip]] or [[Vim_Tip]] !? Would be nice if there were someone who could review the pages for things like that ... This is another great question. In my opinion, Mediawiki does a very good job of handling spaces and special characters in file names. I therefore think that we should err on the side of readability, and try to make the titles as readable (including spaces and such) as possible. Thanks again! Tom Purl
Vim Wiki - Wiki Template Proposal
Sebastian Menge has graciously created a Mediawiki template that could
be used with the proposed Vim wiki. Here's a link to the template:
* http://scratchpad.wikia.com/wiki/Template:Tip
This is the wrapper for the actual tip content. Here's an example of
some plain-text content:
{{Tip
|id=1
|title=Tip #1 - the super star
|created=February 24, 2001 14:47
|complexity=basic
|author=scott at kintana.com
|version=5.7
|text=
When a discussion started about learning vim on the vim list Juergen
Salk mentioned the quot;*quot; key as something that he wished he had
know earlier. When I read the mail I had to go help on what the heck the
quot;*quot; did. I also wish I had known earlier...brbrUsing the
quot;*quot; key while in normal mode searches for the word under the
cursor.brbrIf that doesn't save you a lot of typing, I don't know
what will.
}}
When you combine this content with the template on the wiki, you get the
following:
* http://scratchpad.wikia.com/wiki/VimTip1
The big benefit of using a wiki template is that it separates the
content from the presentation, which can be very nice from the
perspective of a sysadmin or tip converter.
The disadvantage, in my eyes, of using wiki templates is that it adds
another barrier to entry for potential tip authors/editors. Not only
would they have to know how to do basic Mediawiki editing, but they
would also have to know how to use templates. Also, in my opinion, it
is more difficult to edit the content when it's squished into a
template.
So far, we know about the opinions of me and Sebastian. What does
everyone else think? Is the template thing a good idea for our wiki?
Thanks again!
Tom Purl
Re: VimWiki - again - but with a brand new option
On Thu, May 10, 2007 3:40 am, John Beckett wrote: Tom Purl wrote: Here's what I propose we do: 1. Finalize a tip formatting standard. 2. Use the best available script that supports this standard. 3. Update the best available script if necessary. 4. Revise the standard if necessary. 5. Convert a tips sample. 6. Review the sample and revise the script if necessary. Good. But to keep our discussion focussed, please do what you did last time: Put a sample tip on a wiki page so we can agree on its features. We already have a tip on the page that people have been working on. You can see the link to it on the following page: * http://en.wikibooks.org/wiki/Learning_the_vi_editor/Vim/TipsSandbox Please take Gene's advice and manually edit the page to how you think it should look. Once the format is agreed, we can ask for a script. I recommend: - Propose a format for the URL of each tip, as well as the format of the page. - Omit the info box with author, date, tip rating, Vim version. It's too hard to maintain, and too intrusive. - Keep the comments on the tip page, with a very simple comment heading in front of each, something like: -By UserName on March 8, 2001 14:51- To make it easy to edit the page, the comment heading should be a single line in the wiki source. I agree that we should keep things as simple as possible, at least for the initial conversion. After that, when all updates are manual, we can be more fancy :) This not only saves time, but I just don't think that it is possible to create a conversion script that can convert plain text that doesn't use a single markup style to a consistent format. -Or- Put all the comments on the talk page, with the format as above. However, that seems unnecessarily tricky to do in practice (it doubles the number of pages we have to work with). I favour putting the comments in the main page to make it easier to clean up the tip. When we see a tip with old-style comments, we would know that it needed an overhaul. So do I. 1. Let's use this mailing list to coordinate the project. All comments regarding wiki page format, however, should be written to the talk section of the affected wiki page. Please be more explicit. Will we use the vim or the vim-dev list? I was referring to the user mailing list. How can we comment on the wiki page format on the talk section? Each page has a talk tab, and you can use it to comment on a wiki page. I think we should use the vim mailing list for all discussions until a decision (your decision!) is made to finalise the wiki site, format, and script. Ok, what does everyone else think? I'm open to this, especially since it's easier to keep up with the mailing list than it is to keep up with a Wikibooks watchlist page. Final suggestion: Please start a new thread (new subject) which we will follow until everything is finalised, rather than replying to this. I agree. I'm a big fan of proper mailing list thread etiquette, even though I completely ignored it for this discussion :) I plan on starting a new thread for each deadline, and I think we should be fairly granular when it comes to thread creation. It makes things easier to follow. If in doubt, create a new thread! It would be great if you would consider what I and others have written, then make a proposal with what you think. Thanks for the feedback! My proposal is basically what I said yesterday - that we follow some sort of schedule and make some decisions. I like your suggestions. What does everyone else think? Tom Purl
RE: VimWiki - again - but with a brand new option
On Thu, May 10, 2007 10:52 am, Zdenek Sekera wrote: It would be great if you would consider what I and others have written, then make a proposal with what you think. Thanks for the feedback! My proposal is basically what I said yesterday - that we follow some sort of schedule and make some decisions. I like your suggestions. What does everyone else think? Sounds very good, go for it as per Gene's suggestion. Nothing will get done otherwise, unless somebody knowledgable really starts. Good luck! For the record, a couple of very knowledgeable people have already done most of the hard work. For examples, we have a collection of conversion scripts already: * http://vimtips.googlecode.com/svn/trunk/scripts/ The only part that really remains is the part that requires some sort of consensus, albeit small. So yes, a lot of work by very talented people has been done already. The remaining work is actually pretty small; it just requires a small amount of agreement. Also, I really don't think that this project suffers from bureaucratic overkill or the lack of talented individuals who can do a lot of great work in a very short amount of time. The reason why everything's been moving so slowly so far is due to a lack of organization in my opinion. I'll try and do my part, and if a few other people can pitch in a few minutes every couple of days or so, I think we'll be done soon. Thanks! Tom Purl
Re: VimWiki - again - but with a brand new option
On Tue, May 8, 2007 3:32 pm, Bram Moolenaar wrote: The main goal now is to get the Vim tips collection back to live. It has been dead for three months now! I wasn't aware of this, and it's definitely a problem. Here's what I propose we do: 1. Finalize a tip formatting standard. 2. Use the best available script that supports this standard. 3. Update the best available script if necessary. 4. Revise the standard if necessary. 5. Convert a tips sample. 6. Review the sample and revise the script if necessary. Once we're done with all of that, we can revisit the question of which wiki we'll use and then convert all of the tips. Since this project is lagging, let's also use the following standards: 1. Let's use this mailing list to coordinate the project. All comments regarding wiki page format, however, should be written to the talk section of the affected wiki page. If you're unsure as to where to post your comment, then just post it to this mailing list. 2. Let's set a deadline for signing off of the wiki formatting standard of 5/21. 2. Let's set a deadline for determining the best conversion script of standard of 6/4. This is just a start, and I'm open to all opinions/criticism. I just want to give this project a shot in the arm so that we can resurrect one of the best features of the Vim editor. What do yo guys think? Perhaps we can figure out some clever way to also make the help files available with links between the tips and the help files. Thus in the help file you would see some link that takes you to a tip associated with the text at that position. But without that the tips are still very useful. -- From know your smileys: O:-) Saint /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org /// \\\help me help AIDS victims -- http://ICCF-Holland.org ///
Re: VimWiki - again - but with a brand new option
On Wed, May 9, 2007 11:37 am, Sebastian Menge wrote: First, im not sure about what you mean by a) formatting standard and b) a script that supports the standard is a) something like a template in mediawiki-speak? see: http://home.comcast.net/~gerisch/MediaWikiTemplates.html http://www.mediawiki.org/wiki/Help:Templates By formatting standard, I mean that we need to agree on how we want the tips to look once they're converted and posted to the wiki. Basically, what do we want the tips to look like so we can tweak the conversion script (if necessary). is b) something that reads the tips-db on vim.org and posts it to the wiki? Here, I'm referring to the script that will convert the scripts from their current format to their future, wiki-fied format. We already have 3 or 4 scripts that could do this. Everything else is agreed and appreciated :-) Thanks! Seb. PS: When writing this mail I got my hands dirty on the scratchpad of wikia.com: http://scratchpad.wikia.com/wiki/VimTest http://scratchpad.wikia.com/wiki/Template:Tip PPS: There are extensions for mediawiki that could be useful: To supply a HTML-Form to submit a tip: http://meta.wikimedia.org/wiki/Help:Inputbox To order a list of pages by popularity http://semeb.com/dpldemo/index.php/Manual Both are installed on wikia.org We do have a Wikia site available if we want it (http://vim.wikia.com/wiki/Main_Page). I agree with you; it has a lot of nice features, and may give us a bit more flexibility than the wikibooks option. I think we should revisit this topic once we're ready to start the real conversion.
Re: VimWiki - again - but with a brand new option
On Tue, May 8, 2007 3:32 pm, Bram Moolenaar wrote: The main goal now is to get the Vim tips collection back to live. It has been dead for three months now! I wasn't aware of this, and it's definitely a problem. Here's what I propose we do: 1. Finalize a tip formatting standard. 2. Use the best available script that supports this standard. 3. Update the best available script if necessary. 4. Revise the standard if necessary. 5. Convert a tips sample. 6. Review the sample and revise the script if necessary. Once we're done with all of that, we can revisit the question of which wiki we'll use and then convert all of the tips. Since this project is lagging, let's also use the following standards: 1. Let's use this mailing list to coordinate the project. All comments regarding wiki page format, however, should be written to the talk section of the affected wiki page. If you're unsure as to where to post your comment, then just post it to this mailing list. 2. Let's set a deadline for signing off of the wiki formatting standard of 5/21. 2. Let's set a deadline for determining the best conversion script of standard of 6/4. This is just a start, and I'm open to all opinions/criticism. I just want to give this project a shot in the arm so that we can resurrect one of the best features of the Vim editor. What do yo guys think? Perhaps we can figure out some clever way to also make the help files available with links between the tips and the help files. Thus in the help file you would see some link that takes you to a tip associated with the text at that position. But without that the tips are still very useful. -- From know your smileys: O:-) Saint /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org /// \\\help me help AIDS victims -- http://ICCF-Holland.org ///
Re: VimWiki - again - but with a brand new option
On Wed, May 9, 2007 11:37 am, Sebastian Menge wrote: First, im not sure about what you mean by a) formatting standard and b) a script that supports the standard is a) something like a template in mediawiki-speak? see: http://home.comcast.net/~gerisch/MediaWikiTemplates.html http://www.mediawiki.org/wiki/Help:Templates By formatting standard, I mean that we need to agree on how we want the tips to look once they're converted and posted to the wiki. Basically, what do we want the tips to look like so we can tweak the conversion script (if necessary). is b) something that reads the tips-db on vim.org and posts it to the wiki? Here, I'm referring to the script that will convert the scripts from their current format to their future, wiki-fied format. We already have 3 or 4 scripts that could do this. Everything else is agreed and appreciated :-) Thanks! Seb. PS: When writing this mail I got my hands dirty on the scratchpad of wikia.com: http://scratchpad.wikia.com/wiki/VimTest http://scratchpad.wikia.com/wiki/Template:Tip PPS: There are extensions for mediawiki that could be useful: To supply a HTML-Form to submit a tip: http://meta.wikimedia.org/wiki/Help:Inputbox To order a list of pages by popularity http://semeb.com/dpldemo/index.php/Manual Both are installed on wikia.org We do have a Wikia site available if we want it (http://vim.wikia.com/wiki/Main_Page). I agree with you; it has a lot of nice features, and may give us a bit more flexibility than the wikibooks option. I think we should revisit this topic once we're ready to start the real conversion.
Re: Two different versions of Vim...
Please see the following archived message: * http://www.mail-archive.com/vim@vim.org/msg06747.html HTH! Tom Purl On Fri, April 20, 2007 10:09 am, Marv Boyes wrote: Hello, all. This is going to be painfully basic, I'm sure, but I can't find my way around it. I've just clean-installed Ubuntu 7.04 and am busily setting things up the way I want them. Naturally, Vim comes first. :) Ubuntu installed vim as a default package, without GUI enabled. I installed the GUI-related packages, but then decided that I'd rather have all patches up to date and installed Vim via AAP (which I really like, by the way). I ended up with Vim 7.0.224 in text-mode, but version 7.0.164 in GUI mode. Apparently, the Ubuntu-packaged versions install to one place, and the AAP version in another. I removed all Vim-related Ubuntu packages and re-ran the AAP install with --enable-gui=gtk2 in my config.arg file. That's evidently not the correct syntax, since I ended up with no GUI available. Basically, what I'm trying to do is have Vim, with GUI, always patched-up-to-date. Is AAP the best way to do this on Ubuntu? If so, I can't seem to find a clear answer as to how to do so (i.e., it installs fine, patches fine, but I can't get a GUI to save my life). I'm content to use the Ubuntu packages, as long as subsequent uses of aap update give me the same version of Vim in both text and GUI modes. Any and all guidance would be greatly appreciated; many thanks in advance.
Re: Two different versions of Vim...
Also, I forgot to mention that AAP is a perfectly fine way to have a cutting-edge version of Vim on your Ubuntu computer. On Fri, April 20, 2007 10:09 am, Marv Boyes wrote: Hello, all. This is going to be painfully basic, I'm sure, but I can't find my way around it. I've just clean-installed Ubuntu 7.04 and am busily setting things up the way I want them. Naturally, Vim comes first. :) Ubuntu installed vim as a default package, without GUI enabled. I installed the GUI-related packages, but then decided that I'd rather have all patches up to date and installed Vim via AAP (which I really like, by the way). I ended up with Vim 7.0.224 in text-mode, but version 7.0.164 in GUI mode. Apparently, the Ubuntu-packaged versions install to one place, and the AAP version in another. I removed all Vim-related Ubuntu packages and re-ran the AAP install with --enable-gui=gtk2 in my config.arg file. That's evidently not the correct syntax, since I ended up with no GUI available. Basically, what I'm trying to do is have Vim, with GUI, always patched-up-to-date. Is AAP the best way to do this on Ubuntu? If so, I can't seem to find a clear answer as to how to do so (i.e., it installs fine, patches fine, but I can't get a GUI to save my life). I'm content to use the Ubuntu packages, as long as subsequent uses of aap update give me the same version of Vim in both text and GUI modes. Any and all guidance would be greatly appreciated; many thanks in advance.
Re: Two different versions of Vim...
On Fri, April 20, 2007 11:29 am, Marv Boyes wrote: 1- After removing every trace of Ubuntu's default-installed vim, I installed the following from repositories: vim-common vim-full vim-gui-common That gave me vim with the GNOME2 interface. The command 'gvim' runs Vim 7.0.164 with a GUI. The command 'vim' returns the error /usr/local/bin/vim: No such file or directory. So, apparently, text-mode vim vanished for some reason, or my paths got screwed up. (Please pardon the undoubtedly inaccurate terminology.) Check your ~/.bashrc and ~/.bash_profile files to see if you have a vim alias pointing at that location. Also, your EDITOR system variable might be pointing at that explicit location. You can check that variable using the following command: $ echo $EDITOR If your editor is pointing at /usr/local/bin/vim, then you may want to just change it to vim. 2- After removing every trace of Vim as installed above, I ran AAP with --enable-gui=gnome2 in my config.arg. I got Vim 7.0.224 in text-mode, but the GUI is reported as having _not_ been enabled at compile time. Ok, first, did you run the build-dep commands that I referenced in my previous e-mail message? Please note that I didn't ask you to run apt-get install; you should be running apt-get build-dep in order to install all of the gui dependencies that Vim requires. Next, you don't have to uninstall the Ubuntu version of Vim in order to install the AAP version. It's my understanding that AAP installs the vim folder tree under /usr/local, not /usr (like the Ubuntu package). Not uninstalling the Ubuntu packages if they're already there will probably save you time and make troubleshooting easier. Now, if you installed the gui dependencies and are still having problems, then we need to find someone who's more familiar with AAP. If I were install vim from source the old fashioned-way, I would do the following: $ cd /arbitrary/vim/build/dir $ ./configure --enable-gui=gnome2 21 | tee ./config.custom (the previous command configures vim and sends STDOUT and STDERR to the config.custom file. Tee is used to also send all output to the terminal) (lots of output) $ grep -i error ./config.custom $ grep -i exception ./config.custom $ grep -i gui ./config.custom $ grep -i gnome ./config.custom (the previous three commands tell you if there were any problems with the config. The gui search is especially important) I'm assuming you can do some similar troubleshooting using AAP, but I'm not familiar with that process. Does anyone else know how you can do this with AAP? Again, I'm sorry if I'm missing something extremely basic; it's just that nothing I'm trying is working. No reason to apologize, a lot of people have had problems compiling vim with gui support in the past. Also, there aren't really any trolls on this list, so you don't have to walk on egg shells :) HTH! Tom Purl
Re: How to open a BIG file quickly?
On Thu, April 5, 2007 2:38 am, ³Â·½ÈÙ wrote: Dear all, If I want to open one 1G bytes size file,it's really slow. Thank you in advance. Just out of curiosity, why are you trying to edit a 1 GB file with any text editor? I'm assuming that these files are flat file databases. If that's true, then why don't you just read and write to them using some sort of ODBC driver + database front end? That will give you far superior performance to a text editor. If you can't edit the file like it's a database, then I would seriously think about creating some sort of Perl or shell script to handle reading and writing. HTH! Tom Purl
Re: how to replace ESC to some other key?
On Wed, April 4, 2007 10:55 am, wangxu wrote: ESC is so far from the center of the keyboard. Can I replace this key to Caps Lock,for example? I don't know how you would do it with the Caps Lock key, but here's what I put in my vimrc to do it with the command key: let mapleader = , HTH! Tom Purl
Re: startup extremely slow
On Thu, March 29, 2007 7:01 am, Jagpreet wrote: Hi There, I use putty to connect to remote server with telnet. Not using the graphics version because of high speed with consol version. In the recent time I have started working some other remote server and I copied all my vim data(.vimrc, .vim) to this server as well. When I use vim command to open a file it is extremely slow in opening the files. Sometimes the time to open the file is almost 90 seconds. Please suggest where the problem can be. I've had this issue before when I couldn't connect to the x server. I know that you're not using Gvim, but I've even had this issue when trying to use the terminal version. Here's two things you can try: 1. Export your display variable so that it matches the IP of your client. For example, if your client's IP is 1.2.3.4, run the following command on the server: export DISPLAY=1.2.3.4:0.0 Also, you may need to have some sort of xserver running on your client, like exceed. 2. Pass some switch to vim that forces it to ignore any display settings. I don't know if this setting exists. In the end, I'm think you're having display issues. Are there any xserver experts out there who could give Jagpreet a less half-baked solution? HTH! Tom Purl
RE: startup extremely slow
OK, so you tried passing the -X flag when opening the file? If so, and it's still slow, maybe you use use the -V[N] option to see what's going on? On Thu, March 29, 2007 9:48 am, Jagpreet wrote: Thanks for your quick reply. Well I'm not using any X-server nor do I intend to. I just find that I logon to server with SSH instead of telnet(as server doesn't support this). All I want to use vim in consol mode because it works very fast, and is working on other server with the same settings. After the file gets open it works as expected but its very long time it takes to open the file. So far as display settings are concerned I have that in .bashrc file and I'm exporting DISPLAY variable anyways. I tried the same with without setting that as well but result is the same. Not sure whats happening. -Original Message- From: Tom Purl [mailto:[EMAIL PROTECTED] Sent: Thursday, March 29, 2007 7:51 PM To: A.J.Mechelynck Cc: Jagpreet; vim@vim.org Subject: Re: startup extremely slow On Thu, March 29, 2007 9:16 am, A.J.Mechelynck wrote: To avoid trying to connect with an X server in an X-enabled console Vim (which could be a console version with clipboard support, or a GUI version being run in console mode), use -X on the shell command line for Vim, thus: vim -X foobar.txt Thanks a ton Richard and Tony! This is a much easier solution to my problem than what I'm doing today (setting the DISPLAY var). Does this help you Jagpreet? Tom Purl
Re: building gvim on debian
I would try the following command first: apt-get build-dep vim-gtk This will install all of the dependencies for compiling vim (with gtk2 presumably). See if that gets rid of your problems. HTH! Tom Purl On Sun, March 25, 2007 12:22 pm, Yakov Lerner wrote: When on FedoraCore, I can build gvim whenever I want and I can install needed dependencies (*-devel). But debian-derived distros are not nice to me ... on the debian-derived distro (mepis), trying to install libgtk for building gvim I got into trouble that I don't know how to solve: 'apt-get install libgtk2.0-dev' gives me errors [1]. Is libgtk2.0-dev is the correct package name that I need to build gvim ? Trying to install lesstif results in apt-get error, too. (I do 'apt-get update' often, but it results in errors [2]) What am I doing wrong ? Thanks Yakov one man's bug is another man's feature, -- Below [1] errors from 'apt-install libgtk2.0-dev' [2] errors from 'apt-get update' [3] contents of the sources.list -- [1] $ apt-install libgtk2.0-dev Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: libgtk2.0-dev: Depends: libgtk2.0-0 (= 2.8.17-1ubuntu5) but 2.8.20-0ubuntu1.1 is to be installed Depends: libglib2.0-dev (= 2.8.5) but it is not going to be installed Depends: libpango1.0-dev (= 1.10.0-2) but it is not going to be installed Depends: libatk1.0-dev (= 1.6.1-2) but it is not going to be installed Depends: libcairo2-dev but it is not going to be installed E: Broken packages --- [2] 'apt-get update' also produces errors: Get:1 http://apt.mepis.org mepis Release.gpg [191B] Hit http://apt.mepis.org mepis Release Hit http://apt.mepis.org mepis/main Packages Get:2 http://security.ubuntu.com dapper-security Release.gpg [191B] Get:3 http://archive.ubuntu.com breezy Release.gpg [189B] Get:4 http://archive.ubuntu.com dapper Release.gpg [189B] Get:5 http://archive.ubuntu.com dapper-updates Release.gpg [191B] Get:6 http://archive.ubuntu.com dapper-backports Release.gpg [191B] Hit http://archive.ubuntu.com breezy Release Hit http://archive.ubuntu.com dapper Release Hit http://archive.ubuntu.com dapper-updates Release Hit http://archive.ubuntu.com dapper-backports Release Hit http://archive.ubuntu.com breezy/main Packages Hit http://archive.ubuntu.com breezy/restricted Packages Hit http://archive.ubuntu.com dapper/main Packages Get:7 http://security.ubuntu.com dapper-security Release [50.9kB] Hit http://archive.ubuntu.com dapper/restricted Packages Get:8 http://security.ubuntu.com dapper-security/main Packages 99% [8 Packages bzip2 0] [Waiting for headers] [Waiting for headers] 25.6kB/s 0sbzip2: (stdin) is not a bzip2 file. Err http://security.ubuntu.com dapper-security/main Packages Sub-process bzip2 returned an error code (2) Hit http://archive.ubuntu.com dapper/universe Packages Get:9 http://security.ubuntu.com dapper-security/restricted Packages 99% [Waiting for headers] 25.6kB/s 0sbzip2: (stdin) is not a bzip2 file. Err http://security.ubuntu.com dapper-security/restricted Packages Sub-process bzip2 returned an error code (2) Hit http://archive.ubuntu.com dapper/multiverse Packages Get:10 http://archive.ubuntu.com dapper-updates/main Packages 99% [10 Packages bzip2 0] [Waiting for headers] 25.6kB/s 0sbzip2: (stdin) is not a bzip2 file. Err http://archive.ubuntu.com dapper-updates/main Packages Sub-process bzip2 returned an error code (2) Get:11 http://archive.ubuntu.com dapper-updates/restricted Packages 99% [11 Packages bzip2 0] [Waiting for headers] 25.6kB/s 0sbzip2: (stdin) is not a bzip2 file. Err http://archive.ubuntu.com dapper-updates/restricted Packages Sub-process bzip2 returned an error code (2) Hit http://archive.ubuntu.com dapper-backports/main Packages Hit http://archive.ubuntu.com dapper-backports/restricted Packages Hit http://archive.ubuntu.com dapper-backports/universe Packages Hit http://archive.ubuntu.com dapper-backports/multiverse Packages Fetched 59.9kB in 8s (7326B/s) Failed to fetch http://archive.ubuntu.com/ubuntu/dists/dapper-updates/main/binary-i386/Packages.bz2 Sub-process bzip2 returned an error code (2) Failed to fetch http://archive.ubuntu.com/ubuntu/dists/dapper-updates/restricted/binary-i386/Packages.bz2 Sub-process
Re: hosting wiki tips
On Fri, March 23, 2007 11:42 pm, Hari Krishna Dara wrote: I know this came up during the recent discussions on using wiki for tips and it was ruled out. ... I came across this free hosting website called 110mb.com which has like 2gb of free space with no advertisements and no catches on hosting, and many people were successful in hosting mediawiki (search their forums) and other wikis on their space. Why shoudn't this be an option that we should consider? My understanding was that we were going to try and make Wikibooks work for the following reasons: 1. We had people on the list who were already using Wikibooks and liked it quite a bit. 2. It uses the Mediawiki wiki engine, which is probably the most ubiquitous wike engine available. 3. It has proven spam-fighting capabilities 4. The majority of people who had an opinion on the topic seemed to favor using a Wikibook site. In the end, I guess you could say that it was the lowest-risk choice. HTH! Tom Purl
Re: rss feed for vim plugins
On Wed, March 7, 2007 3:51 am, Thomas wrote: Hi, Since http://plasmasturm.org/feeds/vimscripts/ seems to be still out of order, I was looking for another way to keep track of updates of vim plugins and breathtaking new submissions. I came across this service http://feed43.com/ which appears to be able to create a nice rss feed using these setting: ... I just finished creating this feed, so I don't know how this works reliably and over a longer period but it looks quite good. Is there a way that we can subscribe to this feed, or do we have to create our own personal instance at free43? Do you guys gals (mostly guys here, it seems) know similar maybe better services? I tried doing something similar to this with Yahoo Pipes, but it doesn't seem to support HTML (which is the only way to get tips today), only XML. Thanks again! Tom Purl
RE: VimTips Wiki: New Direction
On Tue, March 6, 2007 2:34 pm, Denis Perelyubskiy wrote: Finally, on the subject of converting the comments - it is entirely a manual process, that can not be automated. Comments need to be integrated into the body of the main tip (maybe the tip needs to be adjusted, reworded, etc). We should just push out the existing pages, and then set to work on reworking the tips by hand. Eventually we'll be done. I agree mostly. The process of moving the tips from vim.org to the wiki host can be automated. Ideally, I also think that it would be a good idea to refactor some comments into the body of some tips, but I certainly don't think that it's necessary for every tip. For example, I wrote tip number 1280 which, in hindsight, is pretty lame. My tip has one comment from someone who agrees that my tip is lame :) Also, I imagine that about 5 people a year read this tip, and those people probably were looking for something else anyways. In that situation, do we *really* need to merge the comment with the tip? No one uses the tip, and the comment's pretty pointless. Why don't we just ignore it? On the other hand, there are some tips that are used hundreds of times a week. These tips will probably be refactored and updated very quickly due to the sheer number of eyeballs reading it. So I guess what I'm saying is, what's wrong with waiting for the community to refactor these tips using guidelines from the wikibook admins? Thanks! Tom Purl
VimTips Wiki: New Direction
Here's my view of where we are regarding the Vim Tips wiki conversion project: 1. The Google wiki seems to be a poor option due to the difficulty involved in registering. 2. Multiple other wiki engines have been discussed, and the clear favorite seems to be a site built on top of the Mediawiki application. 3. Of all of the sites that offer free wiki hosting using Mediawiki, Wikibooks seems to be the most favored. Note: These are all my opinions based on what I've read. I hope to hear from everyone that has a different perspective :) Ok, so based on my version of reality, I think that we should proceed with the following actions: 0. I'll create the following page on the Vim Tips chapter of the Vim book on Wikibooks (whew!): * http://en.wikibooks.org/wiki/Learning_the_vi_editor/Vim/TipsSandbox 1. All of the people who wrote tip conversion scripts before should update them so that the output format is Wikipedia markup, not Google markup * I apologize to the script writers for making them do more work. Hopefully, the necessary changes to your scripts will be small. * Also, please note that I _don't_ think that anyone should contribute a new script to this effort. We already have three very capable scripts that can probably get the job done very well, so I don't think that the effort would be worthwhile for anyone else. 2. Convert one tip and post the output on the TipsSandbox page listed above. 3. The vim community will come to a consensus on the best format for the tips, and we will use the best script for the job. 4. Consensus achieved!!! 5. We will automate the task of converting all of the tips. 6. A group of wiki superusers will inspect 50 random tips and make sure that they look good. 7. The invisible hand of The Wiki will then gradually make our wonderful collection of Vim tips even more awesome than they've ever been before! ;D So, what do you guys think? Tom Purl
Re: VimTips Wiki: New Direction
Would you please give me an url or something so I may learn the Wikipedia markup? :) Easier said than done. I've actually had problems finding a complete list in the past. Here's the best resource I could find: * http://meta.wikimedia.org/wiki/MediaWiki_Markup Also, please note that there are Python and Perl libraries for converting HTML to mediawiki markup and vice-versa, if that's of any help. Thanks! Tom Purl
Re: VimTips Wiki: New Direction
Bram Mooleanaar summarized: I'm still a bit worried about spammers, since that is what broke down the current tip collection. Perhaps someone can look into this, so that the scripts we use for conversion do the right thing? I looked into the anti-spam features of Wikibooks, and they basically do the basics: blacklists for abusers and easy rollbacks. So the top 2% of spammers/vandalizers will be blocked, and it will be easy for the admins to roll back the problems created by the outher 98%. So will that be effective? Eh, maybe. It seems to be effective enough for a lot of Wikibooks, and we *do* have experts on this mailing list (*cough* Martin Krischik *cough*) so I would love to hear their perspectives :) I don't think that the conversion effort will be wasted, even if we don't end up using Wikibooks as our wiki host. The two top hosts in my eyes are Wikibooks and Wikia, and they both use the Mediawiki wiki engine. Also, many other wiki engines support the Mediawiki markup language, so I think we're future-proofing our content by using this markup language. From my experience, it's definitely the de facto standard. Thanks! Tom Purl
Re: VimTips Wiki: New Direction
Ali Polatel said: 2. Convert one tip and post the output on the TipsSandbox page listed above. I converted vimtips.py , you can find it at google svn: http://vimtips.googlecode.com/svn/trunk/scripts/vimtips.py (at least we can still use svn right ;) And check out http://en.wikibooks.org/wiki/Learning_the_vi_editor/Vim/TipsSandbox to see how it parsed tip #1. Looks like a great start Ali! I wanted to use that page as the center of the project for now, so I refactored tip number one into its own page: * http://en.wikibooks.org/wiki/Learning_the_vi_editor/Vim/TipsSandbox/Tip_1:_the_super_star Also, I left comments on the output of your script on the talk page for that page. Well I think it's a great decision. Thanks! I would take more credit but I'm just repeating what almost everyone else said. Thanks again! Tom Purl
Re: VimTips - Google Wiki Usefulness
1. Email-address verification of the user automatically adds the user to the project 2. First few contributions by the user are modified by the admin, once they prove themselves genuine and worthy, they can be moved to non-moderated status and their future contributions are automatically committed which speeds up the process (I've seen this work for many mailing lists too). If Google Code wiki provides these features, I think it would be ideal. If not, can we configure Wikia to do this? Sorry for not responding sooner. I've been having e-mail problems all weekend. I think the answers are no and no. I do however think that both sites have pretty decent spam-fighting features that may work for us. Thanks! Tom Purl
Re: VimTips Wiki: New Direction
Bram Mooleanaar summarized: I'm still a bit worried about spammers, since that is what broke down the current tip collection. Perhaps someone can look into this, so that the scripts we use for conversion do the right thing? I looked into the anti-spam features of Wikibooks, and they basically do the basics: blacklists for abusers and easy rollbacks. So the top 2% of spammers/vandalizers will be blocked, and it will be easy for the admins to roll back the problems created by the outher 98%. I also just noticed that the site forces you to enter a captcha if you enter add a link to a wiki page. I know that captchas aren't the perfect solution, but this probably helps a little bit with spam. Tom Purl
Re: tips project
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 archive for a thread titled VimTips - Google Wiki Usefulness. Actually, I followed that other thread you mention - VimTips - Google Wiki Usefulness, and unless I missed something, people seem to agree that requiring to register will not be a good idea, and will decrease a number of useful tips. At least I haven't seen anyone argue the opposite. I don't think that anyone has a problem with requiring wiki users to log in. The problem is that we don't want to set the bar too high, and the Google wiki requires potential editors to jump through far too many hoops just to register. I thought there was talk about wikimedia and wikibooks, but then i saw these messages about google's wiki again. How come? Because we don't want to rush the decision, and are considering all possibilities. Since the tips are probably going to be hosted on this wiki for quite a while, we all want to be happy with the decision that we make. I'd argue that we should not even do the wiki and add more people to administer the tips (to get rid of spam) if need be, as opposed to doing the wiki which might discourage others from updating. Bram seems to be in favor of a wiki for the tips (or at least in favor of trying it out, I may be mistaken), and a lot of other Vim community members seems to think that it's a good idea. Of course, that doesn't mean that they're right, but that does mean that it's highly likely that the tips will be converted to a wiki sometime soon. Thanks! Tom Purl
Re: tips project
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 - Google Wiki Usefulness. HTH! Tom Purl
Re: VimTips - Google Wiki Usefulness
I imagine these sites work from the frantic effort of very large numbers of contributors (much larger than we should expect). Twenty-four hours per day, there is someone monitoring edits to their favourite wikipedia page. From complaints I've seen from burnt-out contributors, the spam and junk is removed by shear physical effort (with clever tools). I agree that it will be a decent amount of work to keep the proposed vim tips wiki somewhat spam-free. On the plus side, I imagine that the tip authors will be very willing to help keep their tips free of spam and vandalism. Also, we should expect spam to get much worse. I agree here too somewhat, but we can also expect anti-spam tools to improve, especially in the Wikipedia community. So, I think that requiring vimtip admins to suffer a bit of pain in managing the entry of tips and changes would probably be less effort than what would be required to clean up vandalism. The people who don't want to use the Google Wiki (or some other equally cumbersome solution) aren't trying to avoid work. We're not worried about the work load; we're worried about usability for tip editors. I'm sure that if we all put our head together, we could come up with a iron-clad tips site that is very easy to administer and virtually spam-free. The only problem is that it would be so cumbersome to use that very few people would actually add any tips. This seems counter-productive to me since easier access is one of the main reasons that so many people want to move the tips to a wiki. How often are tips added or changed? Look at the effort that people put into this mailing list ... I would have thought that manually tweaking tips would be manageable. Yes, we could just manage everything via the mailing list, and it wouldn't be much work for the admins. I just don't think that 80% of potential tip editors would go through the hassle, and that's saying a lot when you consider how technically proficient most Vim users are. Would someone please check how the Google wiki would work if a malicious admin were accidentally added. Is there a super-admin? There are two types of users in a Google project, members and owners. Members have access to *everything* except the project administration tab. If a malicious user were added as a member, he/she could very easily wreck the wiki because it's stored in an SVN repository, to which he/she has full write access.
Re: VimTips - Google Wiki Usefulness
Tom Purl wrote: However, there are still people, including Bram, who seem to feel pretty strongly about using the Google wiki. Bram, are we going down the wrong track by planning for a non-Google wiki? For this site, I think it's very important that we get as close to a consensus as possible regarding who will do the hosting. No, I don't feel strongly about using the Google wiki. It was just an idea that came up. Being able to use the large server base and cleverness of Google would be an advanage. But there are also disadvantages, mainly that it's not simple to let everybody edit the wiki. Ok, thanks for clearing that up. Using wikibooks.org sounds attractive, but I don't see any protection against spamming. And that is exactly what happens to the Vim tips. It's just a matter of time before this happens on wikibooks.org too. I agree that spam protection should be our top priority. Besides that, transferring all existing tips to the wiki needs to be tried out. I don't understand what you mean here. Are you saying that we should move forward with a Google wiki conversion, irrespective of whether or not we end up using the Google wiki? Converting all of the files getting sign-off from the Vim community would probably takes more than a couple of weeks. This seems like a lot of time to spend for on a solution that looks like it may not pan out. I too am in favor of making steady progress with the conversion, but converting the tips before we pick a wiki seems to be the wrong order of operations to me. Thanks! Tom Purl
Re: VimTips - Google Wiki Usefulness
Using wikibooks.org sounds attractive, but I don't see any protection against spamming. And that is exactly what happens to the Vim tips. It's just a matter of time before this happens on wikibooks.org too. I agree that spam protection should be our top priority. Why ? We already have the spam problem and while annoying it doesn't negate the value of the tips themselves. Sure it's important, but the quality and quantity of content should be top priority shouldn't it? I guess I should have said the following: I agree that we should balance accessibility with good spam protection. That aside - if wikibooks doesn't seem to have the spam problem now I don't think it's appropriate to dismiss them just because we don't _think_ it will work. Proof is in the pudding - wikipedia and wikibooks seem to prove it _does_ work. I don't think that anyone is rejecting Wikibooks outright. I think that they should be on our non-Google top 5 list personally. I just think that people are cautious because very few people have experience with it. No one for sure knows whether it will actually work for our needs. It therefore pays to be cautious and deliberative.
Re: VimTips spam protection - ideal case ? free hosting vs vim community driven own solution
I've followed some of the emails of the thread Google Wiki Usefulness. . .. One big point was: How to protect against spammers? = === Actually, I found a really good reference on this today: * http://www.wikia.com/wiki/Help:Spam It echoes a lot of what you said. They combine blacklists, captchas, and simple iq tests to help block edits that are most likely to contain spam. It seems like a pretty good strategy to me if you're going to let anonymous users contribute to your wiki. Vim community driven own system ? = === Has anyone elaborated the pro cons of a) using a dedicated server* and our own or adjusted system, funded by vim community (* or something like that) Yes, and it wasn't well-received. b) a free hosting like Google Wiki Problems with this wiki are the reason that we're looking for other possible solutions. c) extend the already existing vim.org to support wiki like features? This hasn't gained much traction. Do we already know what we really want/ need? = === a) I've read about some people fearing loosing initial authorship of tips causing those authors to not mantain their tips any longer? I don't think that this will be a problem. b) On the other hand we need some pages gathering all the important nice peaces of code shaping a a kind of cookbook having headlines... ... All I want to say is: I think there can be more benefits than copying tips. Does my imagination match yours? I'm all in favor of refactoring the tips some day if we find a better design that the Vim community prefers. But in the mean time, let's move the stuff over and strive to achieve 100% data fidelity in the process.
Re: VimTips - Google Wiki Usefulness
Ok, so the majority of people seem to be saying that the Google wiki isn't very well-suited for our needs. Most notably, it's very likely that it will severely inhibit contributions. I agree with this whole-heartedly. Also, a lot of people are discussing third-party wiki hosting sites and the possibility of running our wiki on donated server space. I think this is a useful exercise in case we do end up not using the Google wiki. However, there are still people, including Bram, who seem to feel pretty strongly about using the Google wiki. Bram, are we going down the wrong track by planning for a non-Google wiki? For this site, I think it's very important that we get as close to a consensus as possible regarding who will do the hosting. Thanks again to everyone! Tom Purl
Re: VimTips - Google Wiki Usefulness
I do think that we can do the addition of new people who want to be able to edit the wiki manually. That should also filter out the spammers. There is only a delay between wanting to edit the wiki and being able to do it the first time. Not perfect, but it's something that we can setup right now and try out. Ok, so here's the proposed workflow: 1. Potential tip editer/adder (Veronica Vimlover) visits the Google vimtips project. On the front page, she sees a message that tells her to post a message to 'vimtips-general' Google group if she wants to post or edit a tip. * Please note that if Veronica visits the wiki page first instead of the Project Home page, she won't know how to gain the proper access to edit wiki pages since for the following reasons: 1. The wiki page itself doesn't tell you how to gain the necessary access to edit pages. 2. I don's see how you can define a default FrontPage for the wiki, so we can't specify how to gain edit access on any sort of wiki front page. 2. Veronica joins the vimtips Google group and posts a message asking someone to please give her the necessary access to edit the wiki page. * Please note that if she doesn't have a Google id at this point, she'll need to acquire one. 3. The admins will monitor the Google group. When Veronica requests access, one of us will take ownership of the request by responding to the Google group message. 4. When the project admin has the time, he/she will add give Veronica a Project Member user status, and notify her via the group that she has the proper access. * Please note that if Veronica only obtained a Google id so that she could post to the wiki (like I did), she probably won't check either the vimtips group or her Gmail very often. It is therefore possible that Veronica will not know in a timely fashion that she has be given the proper access to update the wiki. * One probable solution to this problem is that we could have Veronica post her wiki access request the vim mailing list. This certainly has its advantages, but it might clutter the vim mailing list, and it would make it more difficult for the admins to spot access requests. * Another option would be to have Veronica directly e-mail one of the project admins listed on the Project Home page, but I think that the disadvantages of this solution are pretty obvious (problems with admins checking Gmail, vacations, etc). Ok, I know that was long, but I just wanted everyone to know what was necessary to implement the process of manually adding wiki editors to the vimtips project. This is definitely more labor-intensive and error-proned than any web app registration process that I've ever seen. I still think that the process listed sets the registration bar too high, and it is not conducive to a vibrant, robust wiki. Also, I know that spam is an issue, but there are tradeoffs. The process listed above may eliminate 98% of all spam, but what percentage of possible wiki editors will it also deter? Also, we need to compare the amount of work we would put into deleting spam from a different member-only wiki each week with the amount of time it takes to add dozens of wiki users to the Google wiki using the process above. What do you guys think? Should we still move ahead with the Google wiki? Thanks! Tom Purl
Re: tips project
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? This is a really good question. Here's my opinion. The comments *are* a necessary part of the tip, and should be included with the import. In general, I would like to move 100% of the content from the tips on the vim.org web site to the wiki, even if some of the data doesn't fit very well into the wiki. After that, the tips information can be refactored as necessary by the community.
Re: tips project
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 junk. It would be _lots_ of work to look at every comment and see if they're useful or not. What are your ideas? The comments *are* a necessary part of the tip, and should be included with the import. In general, I would like to move 100% of the content from the tips on the vim.org web site to the wiki, even if some of the data doesn't fit very well into the wiki. After that, the tips information can be refactored as necessary by the community. What I thought was that maybe it's possible to use SpamAssassin (or some of its modules) while converting the tips, to at least get some score that will make it easier to filter this later. I don't know if spam assassin can be used in this way, at least part of the filters are email specific, but maybe some are general. Moshe I think we should focus on a non-automated solution for filtering comments. Basically, I think that we'll convert all of the old tips to the new wiki with all of the content, metadata, and comments. 90 % of those tips will stay that way forever since they're fine just the way they are and require no comments or updates. The commonly-used tips, however, will be refactored according to community's preferences where comments (along with metadata) will be merged or deleted.
VimTips - Google Wiki Usefulness
I've done a bit of work on the vimtips wiki at Google the last few days, and it's come to my attention that it isn't really designed to do what we want it to do. The Google wiki is designed to be used by a small number of people working on a particular open source project. It is not designed to be editable by hundreds (or possibly thousands) of users to exchange tips on using an application. The basic bottleneck is that only project members can edit the wiki, meaning that these will be the only people who can add or edit tips. The only way to become a project member is to have a project admin (so far, me) visit the project's admin interface and add him or her. There is no web interface or other functionality in place to do this in a more automated way. This awkward user-registration process will most certainly keep people from contributing or updating tips. It will also create a lot of tedious and error-proned work for the project's admins, even if I were to add a dozen more. So as I see it, we have two things we need to do if we want to keep the wiki conversion project moving: 1. Define our wiki requirements * Do we want anonymous users to be able to contribute at all like they can on vim.org/tips today? * Does the wiki have to be hosted by Google, or is it ok if we move to another wiki host if they match all of our requirements? * This question is probably mostly for Bram, since he first suggested the Google wiki. * I personally really like Google in general. They just don't have the apps that we need today. * Cost? * I'm assuming that the ideal number if free :) * Embedded WYSIWYG editor, etc. 2. Choose the wiki host that best suits our needs * I see two options: * Wait for Google to meet all of our requirements? * Google recently acquired JotSpot, so maybe that wiki will be functional enough to meet all of our requirements some day. * Find a different wiki host that does meet all of our requirements, and should be able to do so for at least 3 years or so. So what do you guys think? Tom Purl
Re: tips project
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 scripts. If anyone else is thinking about contributing, I encourage you to take a look at the existing scripts and try to improve one of them based on feedback from the community. Thanks again! Tom Purl * 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). I wrote a script to parse vim tips which seems to work ok , here it is: http://hawking.nonlogic.org/code/python/vimtips.py I'll be happy if you guys can test it , then we can add some code to put the parsed tips to the wiki. Ali -- Ali Polatel (hawking) [EMAIL PROTECTED] http://hawking.nonlogic.org/ gpg: F0186CA2 fp: 7110 01E2 F8B6 83A2 AC52 1D9F 986B 76E1 F018 6CA2 () ascii ribbon campaign - against html mail /\
Re: tips project
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 malicious Emacs user :), even if the tips conversion script isn't done yet. Otherwise, I'd be happy to do it and brag to my dorky friends about how integral my efforts are to the Vim project ;) Tom: Were you thinking of creating the conversion script? And copying the web site tips into the wiki? I haven't started something like that, but I would be happy to help with such an effort. I've written a few wiki conversion scripts before coincidentally. Does anyone know of some docs that might assist in this process? Does a wiki have a bulk import, or is it a matter of emulating what a person would type? Here's the basic process as I see it: 1. Scrape the tips from vim.org. We can either scrape the HTML itself, or pipe it through a tool like elinks to get formatted content (if that ends up being easier to parse). * I know that we can download a plain-text version of the tips as some sort of tarball, but I don't think that version includes comments. 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. * We probably will want to create one text file for each tip. 3. Post a sample of some converted tips on the wiki and get community sign-off (more or less). 4. Upload marked-up content to the Google wiki * Google usually provides some sort of RPC api for this sort of thing, but lacking that, a simple Perl 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 that he didn't want to set up the VimTips project until we were ready convert content, but I think that it would be nice to set it up very soon for the following reasons: * 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 think? Thanks! Tom Purl
RE: tips project
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 mailing list unless people think its too OT. So if you're interested in helping, start scraping vim.org/tips and let us know what works for you. Thanks! Tom Purl
Re: tips project
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 too OT. So if you're interested in helping, start scraping vim.org/tips and let us know what works for you. I've thrown a quick script together, it's not perfect but it gets all the basic details such as the tip number, author, version and content : http://pastebin.com/886040 We could enhance it to fetch additional notes as well and then just loop it from 1 to 1504 I guess :) Fantastic. I can't look at this script until tonight, but I'll be sure to do so. 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. Also, I just wanted to say that it looks like we won't have to write any sort of upload script. The Google wiki is built on top of an svn repository, so we'll just have to check in our converted files to publish them. I think that this feature will be especially nice if we find ourselves doing the conversion multiple times. Thanks again Swaroop! Tom Purl
Re: tips project
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] 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 of the script for tip 1504 : --- Tip 1504 Authored by Tim Keating Created on February 6, 2007 9:16 Complexity is basic Version of Vim required is '' codeIf you want to execute an external command on Windows, you need to know one trick. Let's say you're building a command to check out the file you're working on (using Perforce as an example): br / br /map lt;f6gt;:!p4 edit % br / br /However, that will just populate the command line. To force the command to execute without having to hit Enter, you need to embed a CR/LF. On Linux, you do this with CTRL+V CTRL+M. On Windows (as of version 7; not sure how far back this goes), CTRL+V is mapped to quot;Paste from Windows Clipboardquot;. You have to use CTRL+Q instead: br / br /map lt;f6gt;:!p4 edit %CTRL+Q CTRL+M br / br /Which will look like: br / br /map lt;f6gt;:!p4 edit %^M/code --- -- Swaroop
Re: ant plugin recomendation
Place the following into your .vimrc/_vimrc: autocmd BufRead *.java compiler ant Now when you edit .java files and want to compile them using the default ant target, you simply type the following command from the editor: :mak If you want to invoke a non-default target, simply execute it using the following command: :!ant othertarget This command simply interacts with the shell. If your $PWD isn't where your build.xml file is located, then you'll have to pass that file to ant as a parameter. This is how I use ant with Vim, and it doesn't require any plugins. Also, it's very effective and easy to use. Also, you might want to try the following command: :h quickfix Please note that this works on both Windows and Linux. HTH! Tom Purl P.S. I control my $PWD variable using the Project plugin, which is something that you might want to look into if you're doing a lot of Java development using Vim. Hi, I need some plugin to be able to compile using ant and parse it's output from vim. I've seen there are some, but I want something small and simple i have not found yet. Any recomendation will be appreciated. Thanks.
Re: how to read the file created in PC in Linux correctly?
You can use a third-party tool called dos2unix to convert the files. Also, vim has functionality that can do this, but I don't remember it right now. HTH! Tom Purl Hi, I have a lot of text files created in PC. When I open them in Linux using gvim, I get a lot of ^M and no line breaking. It is messy. How can I read the file correctly in Linux? Thanks Frank
Re: How to diff in gvim
Hi, I'm trying to diff two files in (portable) gvim I have two files opened in two vertical windows. (Kind of Winmerge screen setup) When I type :diff I get the error E97: Can not create diffs I don't think that you're supposed to diff files this way, but I could be wrong. If I have a buffer that I want to diff with another, I usually do the following: 1. Un-split all of your windows, leaving only one, and then load file #1 in that window. 2. Type the following command: * :vert diffsplit path_to_file2 This should give you the results that you want. HTH! Tom Purl
Re: External command with arguments (WinXP)
C:C:\Programme\Microsoft Office\Office10\OUTLOOK.EXE /a c:\vimtemp\trigger.sql How can I run this inside of vim to attach the current buffer? Have you tried putting a ! in front of it? For example, at the bottom of the vim window: :!C:\Programme\Microsoft Office\Office10\OUTLOOK.EXE /a c:\vimtemp\trigger.sql I would have tried this command myself, but I don't have outlook on my machine. Hopefully it works. HTH! Tom Purl
Re: Workspace concept ala TextPad
Is it possible to load a set of files when you start gvim? (Like in Textpad, for those who know this editor) For example: I have a project containing 20 files. I frequently uses 5 of them to modify and debug them. Can you give a command to vim like: Load workspace projectX, which then load the 5 defined files? And when needed add or delete files from this workspace? Two more options: Project plugin -- * http://www.vim.org/scripts/script.php?script_id=69 I don't know how I used to live without this plugin. It allows you to create an Eclipse-style layout of a group of files using arbitrary criteria. Plain-Old-Buffers - You could also just open all of the files in Gvim and then use a tool like selectbuf (http://www.vim.org/scripts/script.php?script_id=107) to navigate between them. HTH! Tom Purl
Using Tags In A Markdown Doc
I use the potwiki plugin to document all types of things, and often some of the files can get pretty large. I use the Markdown markup language to author my potwiki pages, and organize the larger ones with headings and sub-headings and such. I would like to create an table of contents (TOC) on some of my large pages so I can jump around to different headings easily, like I do with Vim help files. However, I don't know how I could accomplish this in my potwiki pages. I took a look at the tag documentation, and it looks like I'll need to find some type of tag processor for my headings, but I don't know where to start. Is the help tag processor for vim available as a separate script, or would I have to register my wiki pages as help pages in order to use it? Am I even going about this correctly? Also, I don't have to use the Markdown markup in my pages. If I can use a different format and easily create tag files, then I'm happy with that too. Thanks in advance! Tom Purl
Loading Vimfiles On WIndows With GVimPortable
I'm trying to use Gvim on Windows from a USB thumbdrive. I found and installed the GvimPortable project (http://portablegvim.sourceforge.net/), and it works pretty well. The only problem is that I would like to use a non-standard location for my vimfiles directory. Here's the basic directory layout that I would like to use: USB_ROOT | |__/Apps | |__/conf | | | |__/vim | | | |__vimrc | | | |__/vimfiles (my custom vimfiles dir) | |__/GVimPortable | |__GVimPortable.exe (which launches gvim) |__GVimPortable.ini (which has some config options) Using this custom directory structure, I hope to protect my custom vimfiles directory when I upgrade GvimPortable (or any other app on my thumbdrive). I'm currently able to set the location of the vimrc file using the GVimPortable.ini file, but I'm unable to specify the location of my custom vimfiles directory. Since my vimfiles directory is usually placed in my $HOME directory, I tried putting both of the following commands into my vimrc: let $HOME = . let $HOME = E:/Apps/_conf/vim Both commands seems to change the value of the $HOME dir, but it does nothing to load the plugins and such in my custom vimfiles directory. Does anyone know how to fix this? Thanks in advance! Tom Purl
Loading Vimfiles On WIndows With GVimPortable
Forgive me if this is double-posted. I'm having e-mail problems this morning. I'm trying to use Gvim on Windows from a USB thumbdrive. I found and installed the GvimPortable project (http://portablegvim.sourceforge.net/), and it works pretty well. The only problem is that I would like to use a non-standard location for my vimfiles directory. Here's the basic directory layout that I would like to use: USB_ROOT | |__/Apps | |__/conf | | | |__/vim | | | |__vimrc | | | |__/vimfiles (my custom vimfiles dir) | |__/GVimPortable | |__GVimPortable.exe (which launches gvim) |__GVimPortable.ini (which has some config options) Using this custom directory structure, I hope to protect my custom vimfiles directory when I upgrade GvimPortable (or any other app on my thumbdrive). I'm currently able to set the location of the vimrc file using the GVimPortable.ini file, but I'm unable to specify the location of my custom vimfiles directory. Since my vimfiles directory is usually placed in my $HOME directory, I tried putting both of the following commands into my vimrc: let $HOME = . let $HOME = E:/Apps/_conf/vim Both commands seems to change the value of the $HOME dir, but it does nothing to load the plugins and such in my custom vimfiles directory. Does anyone know how to fix this? Thanks in advance! Tom Purl
Re: Loading Vimfiles On WIndows With GVimPortable
Thanks for the advice Al! On 30/11/06, Tom Purl [EMAIL PROTECTED] wrote: I'm trying to use Gvim on Windows from a USB thumbdrive. I found and installed the GvimPortable project (http://portablegvim.sourceforge.net/), and it works pretty well. [snip] Using this custom directory structure, I hope to protect my custom vimfiles directory when I upgrade GvimPortable (or any other app on my thumbdrive). [snip] Does anyone know how to fix this? [snip] On my USB stick is a directory structure thus: /vim - /vim70 - /vimfiles - _gvimrc - _vimrc vim70 is the standard vim directory, vimfiles is my vimfiles directory. Running U:/vim/vim70/gvim70 automatically finds the vimrc/gvimrc files and the vimfiles directory and upgrading is simply a case of changing the vim70 directory. In practice, I have _vimrc and _gvimrc in the format shown below and the real vimrc file in the vimfiles directory. This allows me to have the entirety of vimfiles in a subversion repository to keep my USB stick, windows machine (C:\vim\vimfiles) and Linux PC (~/.vim) synchronised. I guess I could just merge my personal vimfiles dir with the $VIM/vimfiles dir, but then wouldn't I have to re-merge it every time I upgrade VIM? If so, then how difficult is that for you? What does GvimPortable offer over this sort of arrangement? Not much really I guess. I think some of its exe's are compressed somehow, and it's a simpler installation process, but that's about it. Regards, Al P.S. If you are interested, I can zip up my U:\vim directory and send you a copy... That's a very generous offer , but I don't think I need that yet. Thanks again! Tom Purl
Re: Loading Vimfiles On WIndows With GVimPortable
Thanks a ton for all of the help AJ, Al, and Gary. I basically took did what AJ and Al suggested, including replacing the GVimPortable runtime with the official one. I forgot that the vimfiles directory under $VIM doesn't contain any files, so I simply placed my vimfiles dir there and also placed my _vimrc in the same directory. Now everythign works exactly like I want it to. Thanks again! Tom Purl
Re: tar all files in buffer preserving path
This seems like a pretty sweet tip. It would be much appreciated if you
could post a fleshed-out version of this tip, along with some possible
use cases on the vim.org tips page.
Thanks!
Tom Purl
Yeah, thanks it works like this too:
bufdo !tar -vrf /path/to/archive.tar %:p
How do I avoid the
Press ENTER or type command to continue
prompt after each file is processed?
On 22/11/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Eric Smith wrote:
I want to make a tar file that includes the full pathname.
When I go
:bufdo ! tar -vrf archive_with_full_path.tar %
The `%' does not expand the full path so I do not get the path
information into the tar file.
How could I best achieve what I want?
Try (untested)
bufdo exe '!tar -vrf /path/to/archive.tar' expand('%:p')
see :help expand()
Best regards,
Tony.
--
Eric Smith
Re: Calendar ?
Check out the source, which should be in one of your plugin directories. For me, it's in $HOME/vimfiles/plugin/calendar.vim on my Win XP computer. The header of the file has a ton of commments, including usage statements nad Additional notes. HTH! Tom Purl Hi, where can I find instructions on how to use Calendar.vim and its keybindings ? I visited vim.org's script pages about Calendar.vim but didn't found, what I was searching for. Google also gave me nothing... But may be all this is my fault ?! Regards, mcc
Re: Setting Up Debugging
I suggest using the Dfunc/Decho/Dret debugging system already part of netrw. Once you have the plugin installed, vim netrw.vim :DechoOn :wq The latest version of netrw uses DechoTabOn, which means that debugging output will go to a separate tab. You can save the resulting output to a file whenever you wish, and the display won't be affected (other than seeing the presence of two tabs). You can get the Decho plugin from: http://vim.sourceforge.net/scripts/script.php?script_id=120 -or- http://mysite.verizon.net/astronaut/vim/index.html#DECHO (this latter one is always the most up-to-date) You'll need an up-to-date version of vimball to extract plugins that I've generated since August 1, 2006: http://vim.sourceforge.net/scripts/script.php?script_id=1502 -or- http://mysite.verizon.net/astronaut/vim/index.html#VimFuncs see Vimball Archiver (the most up-to-date version is here) Thanks for the quick reply Dr. Chip! I tried installing both the latest version of netrw and Decho, but I'm seeing a weird problem. Here's the process that I used to install these plugins: vim plugin.vba.gz so % And here's what the plugins look like on the file system (Linux) after running said process: [EMAIL PROTECTED] ~/.vim $ find . -type f -name *Decho* ./doc/Decho.txt?[[[1 ./plugin/Decho.vim?[[[1 ./syntax/Decho.vim?[[[1 [EMAIL PROTECTED] ~/.vim $ find . -type f -name *netrw* ./doc/pi_netrw.txt?[[[1 ./plugin/netrwPlugin.vim?[[[1 ./syntax/netrw.vim?[[[1 ./autoload/netrw.vim?[[[1 ./autoload/netrwFileHandlers.vim?[[[1 ./autoload/netrwSettings.vim?[[[1 Has anyone ever seen anything like this before? Thanks again! Tom Purl
Re: Setting Up Debugging
Thanks for the quick reply Dr. Chip! I tried installing both the latest version of netrw and Decho, but I'm seeing a weird problem. Here's the process that I used to install these plugins: vim plugin.vba.gz so % And here's what the plugins look like on the file system (Linux) after running said process: [EMAIL PROTECTED] ~/.vim $ find . -type f -name *Decho* ./doc/Decho.txt?[[[1 ./plugin/Decho.vim?[[[1 ./syntax/Decho.vim?[[[1 [EMAIL PROTECTED] ~/.vim $ find . -type f -name *netrw* ./doc/pi_netrw.txt?[[[1 ./plugin/netrwPlugin.vim?[[[1 ./syntax/netrw.vim?[[[1 ./autoload/netrw.vim?[[[1 ./autoload/netrwFileHandlers.vim?[[[1 ./autoload/netrwSettings.vim?[[[1 Has anyone ever seen anything like this before? Yes -- its due to an out-of-date vimball plugin. You need to get an up-to-date version of vimball (v18 or later), and to remove any previous vimball remnants. Ok, I just wanted to make sure. My computer has been doing some weird things lately, and I wanted to narrow it down. Also, it's impossible to search for the term [[[1 in Google, so it was hard for me troubleshoot *that* problem. Thanks again! Tom Purl
Auto-refresh When Edited By Outside Application
I use pyGTD, a text file-based todo list from within Vim. Here's the basic workflow: 1. I edit task lines in a file called todo.txt, updating properties such as percentage completed, and save my changes. 2. I execute the gtd.py script from within Vim using the following command: * :silent !./gtd.py 3. The gtd.py script then updates the text in todo.txt if necessary. For example, if I say that a task is 100% completed, it will delete the task from todo.txt. 4. todo.txt is then updated automatically to reflect its newly-updated content (thanks to the shortmess command). The problem is that sometimes todo.txt is automatiaclly updated after running gtd.py and sometimes it isn't. Does anyone know why this might be the case? I done a Vim help search for the term refresh, but didn't find anything. Thanks in advance for the help! Tom Purl
Re: Vim7: Spell checking not working with ft=mail
Anthony Campbell wrote: I know, I have subscribed, but my posts never appear. (This is not new; it's been like that for many months.) I've tried unsubscribing and resubscribing, but no luck. Did you receive the confirmation email which was sent to you as an auto-reply when you sent a mail to vim-subscribe -at- vim.org ? And did you do what it said? (If you did, you should receive two copies of the present email.) Is the From: line of your messages to the list identical to that on your two subscribe emails? (Messages From non-subscribed email addresses are silently discarded by the mail robot for the list). Is the list address present in the To: or Cc: (not Bcc:) line? (Reply to Sender on a post will never send to the list; Reply to All ought to). Are your messages in plaintext only, with no HTML? (HTML messages are silently discarded as an anti-spam measure; they never make it to the list.) Another possibility is that the Vim listserver is bouncing your messages and your mail provider isn't telling you that this happens. I had a problem for a while when my mail provider was recognized as a spammer by the listserver, and all of the messages that I sent to the list were bounced. Luckily, my mail provider sent an error e-mail to me that gave me a decent amount of troubleshooting information. HTH! Tom Purl
Re: Vim7: Spell checking not working with ft=mail
I'm using Vim with a filetype of mail right now, and it's able to do on-the-fly spell-checking :) A lot of filetypes have special provisions where they turn spell-checking off in certain areas that you don't want to spell-check. I think that the mail filetype turns off spell checking if what you're text is after an arrow (, , etc.). Is that what you're doing? HTH! Tom Purl Hi, I'm using Vim 7.0.10 and wanted to try out the new on-the-fly spell checking. It works great, but as soon as I set ft=mail, it stops working (no highlighting anymore). Any clues why? Leslie -- gpg --keyserver pgp.mit.edu --recv-keys DD4EBF83 http://nic-nac-project.de/~skypher/
Re: Planet Vim
Are there enough people out there users/developers that blog about Vim? I'm sure that you could find a critical mass. If so, it would be great to have a planet vim to aggregate these blog posts. I don't see why planet web sites still exist. I can basically recreate this functionality using an rss-aggregating web site such as Bloglines. You can search for Vim-related blogs using their blog search engine, and then track your favorite Vim-related sites in a Vim folder. I'm not trying to be negative - I just wanted to save you some time if the functionality that I described is what you require. HTH! Tom Purl
Re: Vim7: Spell checking not working with ft=mail
I'm using Vim with a filetype of mail right now, and it's able to do on-the-fly spell-checking :) A lot of filetypes have special provisions where they turn spell-checking off in certain areas that you don't want to spell-check. I think that the mail filetype turns off spell checking if what you're text is after an arrow (, , etc.). Is that what you're doing? Whoops, it's too bad that Vim doesn't yet come with on-the-fly grammar checking :) here's what I meant to say in the second-to-last sentence in the above paragraph: I think that the mail filetype turns off spell checking if what you're typing is after an arrow (, , etc.). HTH! Tom Purl Hi, I'm using Vim 7.0.10 and wanted to try out the new on-the-fly spell checking. It works great, but as soon as I set ft=mail, it stops working (no highlighting anymore). Any clues why? Leslie -- gpg --keyserver pgp.mit.edu --recv-keys DD4EBF83 http://nic-nac-project.de/~skypher/
Re: Vim7: Spell checking not working with ft=mail
On Thu, Oct 12, 2006 at 02:40:48PM -0500, Tom Purl wrote: A lot of filetypes have special provisions where they turn spell-checking off in certain areas that you don't want to spell-check. I read about that; however, mail.vim doesn't seem to do that (I could be wrong here). I think I've checked this before and I'm pretty sure that mail.vim does pick and choose where it spell-checks. I know that on my version of Vim (Windows 7.0), new text is spell-checked while text after an arrow is not. I think that the mail filetype turns off spell checking if what you're text is after an arrow (, , etc.). Is that what you're doing? No, I wasn't quoting anything... Could you post an example of the text that isn't being spell-checked?
Re: Vim7: Spell checking not working with ft=mail
What part of the email message are you referring to? Basically, mail.vim does spell checking only in the letter portion, not the headers (or Subject: ...), etc. I'm talking about the body, i.e. I'm just starting to write stuff at the top without any headers. Leslie Ah, there's your problem. In an email, everything until the first empty line is headers. Add the following 4 lines at the top of your email: From: To: Subject: (i.e., 3 nonempty lines and one empty line). You may add more headers, and/or fill them in. Then your body text will be after the first empty line, and it will not be regaded as headers. That's weird. I use Gvim to edit web mail via the Mozex extension. I can place this is a tset at line one in my message after executing the `set filetype=mail` command, and it will be spell-checked. I don't have to include any headers or empty lines or anything else like that.
Re: @ macro history
I appreciate the recommendations, but my workflow is pretty much set in stone for complex reasons. Thanks again! Tom Purl On Tue, Oct 03, 2006 at 11:23:38AM +0200, A.J.Mechelynck wrote: Tom Purl wrote: I'm trying to execute a series of Vim commands on multiple files. Here's the workflow: 1. Open a file using gvim 2. Execute a named macro (that was recorded using the `q + a` command) 3. Save and close my file (which forces me to close gvim in this example). 4. Repeat on the next file without having to re-record my macro. This works for me with vim, but for some reason, when I re-open gvim, it forgets my @ macro. What setting can I change to fix this? Thanks in advance! Tom Purl 3. You don't have to close Vim for that. Save your file with :w then edit the next file with :e file2, which implicitly closes your first file; or replace your file buffer by a [NoFile] buffer by means of :enew. If you started Vim with several files as an argument list (e.g., vim *.[ch] to edit all .c and .h files) or if you set the argument list afterwards (:args *.htm *.html) you can simply go from one file to the next using :next. What you registered using qa and replay using xa is in register a. The :registers command should show it to you even after closing and restarting Vim. Best regards, Tony.
Re: I cannot install gvim7.0
Please reply to the list so that others can learn from our mistakes :) I think it works. But it's really surprising. I run apt-get build-dep vim-gnome, then run ./configure the same result:checking --enable-gui argument... no GUI support. You can also try the `apt-get build-dep` command with the following Debian packages: vim-gtk vim-gui-common I removed the original source codes, and get a new one from vim-7.0-extra.tar.gz, vim-7.0-lang.tar.gz, vim-7.0.tar.bz2. You should only require the last file in that list to compile gvim. Then I can compile vim with GUI. By the way, I run ./configure without any arguments. This is probably a *big* part of the reason why you can't compile gvim. In order to compile GVIM, it was my understanding that you needed to use some sort of GUI flag when executing the ./configuration step. Try running the following command in the future when compiling vim: ./configure --help | grep GUI This will show you all of the GUI-related flags that you need to consider when compiling gvim. HTH! Tom Purl On 10/2/06, Tom Purl [EMAIL PROTECTED] wrote: On Mon, Oct 02, 2006 at 12:42:52AM +0800, Zheng Da wrote: Hello. I try to install vim7.0 But I can't install vim with GUI. It seems that configure automatically looks for a GUI, but it always tells no in my system. checking --enable-gui argument... no GUI support And I'm sure there isn't gvim in my system. I read src/INSTALL. It tells me that I need glib and gtk+ at least version 1.1.16, but below 2.0. I use Debian, and in my system, there are libgtk1.2, libgtk1.2-common, libgtk1.2-dev, libglib1.2, libglib1.2-dev. So what else do I need? -- With regards Zheng Da I had this same problem, and I think that it was fixed by installing the xwindows dev libraries. The output of ./configure told me what was missing from an X11 dev perspective. You might also want to try the following to install all of the compilation dependencies: sudo apt-get build-dep vim-gnome HTH! Tom Purl -- With regards Zheng Da
@ macro history
I'm trying to execute a series of Vim commands on multiple files. Here's the workflow: 1. Open a file using gvim 2. Execute a named macro (that was recorded using the `q + a` command) 3. Save and close my file (which forces me to close gvim in this example). 4. Repeat on the next file without having to re-record my macro. This works for me with vim, but for some reason, when I re-open gvim, it forgets my @ macro. What setting can I change to fix this? Thanks in advance! Tom Purl
Re: @ macro history
Thanks for the quick reply Tim! I did a little more research based on your help, and I found the options.txt help file. From what I understand, to do what I want to do, I should put the following line in my ~/.vimrc: set viminfo='50,1000,s100 However, this still doesn't cause vim to remember registers across sessions. I'll save an @ macro in one instance of gvim, close gvim, and then when I re-open it, I can't use that macro. Does anyone else know if there's something I'm missing? Thanks again! Tom Purl I'm trying to execute a series of Vim commands on multiple files. Here's the workflow: 1. Open a file using gvim 2. Execute a named macro (that was recorded using the `q + a` command) 3. Save and close my file (which forces me to close gvim in this example). 4. Repeat on the next file without having to re-record my macro. This works for me with vim, but for some reason, when I re-open gvim, it forgets my @ macro. What setting can I change to fix this? The 'viminfo' setting controls whether registers get saved...particularly a combination of the s and options. Since you're recording to register a, you'll want to preserve your registers, so that they get restored when vim restarts. -tim
Re: @ macro history
Thanks again for all of the great tips Tim! set viminfo='50,1000,s100 Strange. You are correct that the viminfo setting you list *should* do the trick. To evidence this, I started up vim, recorded a macro to the q register, ran it a couple times, and quit, then restarted vim, and tried @a again to execute the macro. Worked like a charm. I looked in my .viminfo file under the #Registers: section, and I didn't see a q register. I saw 0-9, and a few other letters, but no q. So I guess it's not being written, but I can't imagine why not. My first suspicion would be that something is impolitely tromping on your viminfo setting. You might try :verbose set viminfo? to see if it's been changed elsewhere. Then, grab a baseball bat and your cousins Guido, Fat Tony Vinny and go remedy the problem. ;) I added this to my .vimrc file, and when I close vim, my viminfo settings are sent to stdout. But that's the only time that I see my settings. My assumption is therefore that no other file is changing my viminfo setting. Also, I found these other files on my system that may be affecting my viminfo settings (I use Debian Linux): $ locate vimrc | xargs grep viminfo /etc/vim/vimrc:set viminfo='20,\50 /usr/share/vim/vimrc:set viminfo='20,\50 Thanks again! Tom Purl
Email Text Formatter Plugin
Forgive me if this is a terribly simple question, but I searched for a while and couldn't find the solution to this problem. I'm looking for a simple function that will reformat a selected block of text for e-mail messages (80 columns long, preserving characters, etc). Vim Cream can do this very well, but the functionality doesn't easily translate to vanilla Vim from what I can see, and I prefer using Vim instead of Cream. Is there a function that allows me to do this for Vim? Thanks in advance! Tom Purl
Re: Email Text Formatter Plugin
Thanks a ton! This works very well. On Tue, Aug 22, 2006 at 12:08:50PM +1000, Pete Johns wrote: On Mon, 2006-08-21 at 20:54:21 -0500, Tom Purl sent: I'm looking for a simple function that will reformat a selected block of text for e-mail messages (80 columns long, preserving characters, etc). Vim Cream can do this very well, but the functionality doesn't easily translate to vanilla Vim from what I can see, and I prefer using Vim instead of Cream. Is there a function that allows me to do this for Vim? Have you tried 'gq'? This works perfectly for me with visual blocks. See: :help gq Hope this helps; --paj -- Pete Johns http://johnsy.com/ Contact Information http://johnsy.com/contact/ Taking Stock http://johnsy.com/20060821101816 dsc00220 http://johnsy.com/albums/flickr/210370644
[EMAIL PROTECTED]: failure notice]
When I send e-mail using my mail hosting company as my SMTP host, it gets bounced by the list. I'm using a different SMTP host now, which is why I can send this message to the list. The problem is that I don't have the option of using an alternate SMTP host most of the day, so it would be really nice if I could use my mail hosting company (Zettai.net'). The error message below says that my mail hosting company's mail servers are blocked by Sorbs. I forwarded this on to their tech support, and they said that Sorbs forces you to pay to get your name removed from their black list, which my mail hosting company believes is unethical. Is there anything that can be done by someone on this list to re-allow e-mail from my mail hosting company? Any help at all would be greatly appreciated! Tom Purl - Forwarded message from [EMAIL PROTECTED] - X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on theta.zettai.net X-Spam-Report: * 1.0 NO_REAL_NAME From: does not include a real name * -0.0 NO_RELAYS Informational: message was not relayed via SMTP * 2.0 BIZ_TLD URI: Contains an URL in the BIZ top-level domain * -1.1 BAYES_05 BODY: Bayesian spam probability is 1 to 5% * [score: 0.0206] * 3.4 AWL AWL: From: address is in the auto white-list X-Spam-Status: Yes, score=5.2 required=5.0 tests=AWL,BAYES_05,BIZ_TLD, NO_REAL_NAME,NO_RELAYS autolearn=no version=3.1.0 X-Spam-Level: * From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: failure notice Hi. This is the qmail-send program at a.mx.zettai.net. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. vim@vim.org: 217.73.17.21 does not like recipient. Remote host said: 554 5.7.1 Service unavailable; Client host [205.234.172.66] blocked using dnsbl.sorbs.net; Spam Received See: http://www.sorbs.net/lookup.shtml?205.234.172.66 Giving up on 217.73.17.21. --- Below this line is a copy of the message. Return-Path: [EMAIL PROTECTED] Received: (qmail 20923 invoked by uid 80); 16 Aug 2006 16:00:02 - Received: from 159.53.46.143 (SquirrelMail authenticated user [EMAIL PROTECTED]) by mail.zoper.com with HTTP; Wed, 16 Aug 2006 11:00:01 -0500 (CDT) Message-ID: [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Wed, 16 Aug 2006 11:00:01 -0500 (CDT) Subject: Re: netrw Uses Single Quotes On Windows From: Tom Purl [EMAIL PROTECTED] To: Charles E Campbell Jr [EMAIL PROTECTED] Cc: vim@vim.org User-Agent: SquirrelMail/1.4.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Oh duh. Thanks for the help! Tom Purl wrote: I'm trying to use the netrw plugin with Vim 7 on Windows to edit files using the scp protocol. My scp client of choice is pscp. ..snip.. Please use a more up-to-date version of netrw. There's one on vim.sf.net, and there's an even more up-to-date one at my website. http://vim.sourceforge.net/scripts/script.php?script_id=1075 http://mysite.verizon.net/astronaut/vim/index.html#VimFuncs , see Network Oriented Reading, Writing, and Browsing. Regards, Chip Campbell - End forwarded message -
Re: [EMAIL PROTECTED]: failure notice]
On Thu, Aug 17, 2006 at 11:00:01PM +0200, Bram Moolenaar wrote: Paying money to be removed from a blacklist? If this is correct then this blacklist system must immediately be removed from spam checkers. It's like blackmail. I actually think this would be illegal. Here's the offcial response from my mail hosting service: * http://www.zettai.net/Weblog/sorbs Thanks a ton for the help! Tom Purl
netrw Uses Single Quotes On Windows
I'm trying to use the netrw plugin with Vim 7 on Windows to edit files using the scp protocol. My scp client of choice is pscp. The netrw help includes instructions for using pscp, but it's broken on Windows because the netrw plugin tries to surround your hostname with single quotes. Here's what is sent to the command line when I try and open a file using scp: C:\WINDOWS\system32\cmd.exe /c C:\WINDOWS\system32\pscp.exe -q 'foo.domain.com:/some/dir/file.txt' VIG3E.tmp.profile When this command string is executed, the following error is returned: ssh_init: Host does not exist shell returned 1 When I execute this same command outside of Vim without the single quotes, it works. I found the following link related to this problem: * http://www.vim.org/tips/tip.php?tip_id=1181 It states that this problem was introduced by Vim 7 didn't exist in version 6. Would this be considered a bug then? If not, is there anything I can do to replace the single quotes with either a) nothing at all or b) double quotes? Thanks in advance! Tom Purl
RE: Tips for advance use of Vim
From: Charles E Campbell Jr, Fri, August 11, 2006 11:31 am Tom Purl wrote: The big downside of a wiki is administrative costs. It would probably be slightly more difficult to fight spam, and you would need a heck of a lot more moderators. No more than we currently have. A lot of issues are self-regulated because users are capable of fixing pages. And the spam problem has already afflicted the tips, at the cost of using moderators to elide them. I can just see the (insert favorite descriptive adjectival phrase here) spammers wiping out existing tips' contents and inserting their garbage. Of course, I'm not a wiki expert, and perhaps this problem isn't a problem? Wikis are extremely durable, especially since anyone can fix them. Abuse tends to be over-advertised, especially for wikis requiring login to edit (like the current site). MediaWiki (Wikipedia) in particular is very strong in this area, since it is possible to see diffs between any two versions of a page. Of course it helps to have a few moderators that can lock down a page prone to abuse, but any user can revert a change simply by going back to a previous non-spammed version and pasting it to the current. The current Tips is terribly burdened by typos and obsolete pages, I think a Wiki would be a good way to fix the current problems. It appears as though lots of people like the idea of using a wiki as an interface to the tips on vim.org. Should there be a next step? If so, then what should it be? One possibility would be to set up a test wiki on vim.org that wouldn't be visited by normal vim.org users. We could test out some of the ideas in this thread and see if there are any advantages. Also, someone could set up a test wiki in a separate domain and we could test things out (if we don't want to mess with the main site). Of course, I would say that this type of decision should be made by a site admin or someone like that. Have any of those people been following this thread? Tom Purl
Re: verbose -V
how can I redirect the call gvim -V to a file? ? [Windows XP] Joachim ### gvim -V c:/temp/ausgabe see :help -V two paragraphs :help 'verbosefile' Here's how I'm using the verbosefile setting in my _vimrc file: let verbosefile = expand($TEMP) . /vim_debug.out HTH! Tom Purl
The Project Plugin, netrw, And Remote File Access On WIndows
I'm using Vim on a single Windows workstation to edit multiple files
hosted on remote Windows servers. Here's my usual use case:
1. Map a drive to server foo by entering the following into the run
window:
* \\foo.domain.com\c$\somedir
2. After an Explorer window opens to that directory, I right-click on
the file that I want to edit and choose to open it in Vim.
When I open the file in Windows and press Ctrl+g, it displays the
following path:
* \\foo.domain.com\c$\some_proj\some_file.xml
This works pretty well, but I would really like to be able to do the
same thing using the Project plugin to save time when I need to view or
edit multiple files across multiple servers. The problem is that I
can't get this to work. Here's what I've tried:
some_proj=$HOME/some_proj CD=. {
server_foo {
file://foo.domain.com/c$/some_proj/some_file.xml # Ex 1
\\foo.domain.com\c$\some_proj\some_file.xml # Ex 2
}
}
Neither of the paths in that example work. Has anyone else found a way
to do this?
Thanks in advance for any help!
Tom Purl
Re: Can't find terminal library when compiling Vim7.0
On Sun, Jul 30, 2006 at 10:53:01AM +1200, Johnathan wrote: no terminal library found checking for tgetent()... configure: error: NOT FOUND! You need to install a terminal library; for example ncurses. Or specify the name of the library with --with-tlib. Can someone please tell me what library I'm suppose to point to with --with-tlib. Did you install the ncurses-dev package? I also use Kubuntu 6.06, but didn't use the --with-tlib config option. HTH! Tom Purl
Re: Running python scripts from Vim
On Fri, Jul 28, 2006 at 01:46:46PM +0200, Preben Randhol wrote: I have now tried several vim scripts for python to set up vim as a good python IDE. It has taken some time due to that not all scripts are well documented and there are some old buggy scripts that makes other scripts not work. But now it really starts to shape up :-) If you have some time, could you please share this recipe with the list? Thanks! Tom Purl
Re: I lost gvim on a Debian/testing
* http://www.debian.org/doc/FAQ/ch-pkgtools.en.html Check out the part about the `dpkg --purge foo` command. I've found that this is the only command on Debian that truly uninstalls a package. HTH! Tom Purl Hi, I am an user of gvim on a Debian/testing. I mistakenly deleted some vim, gvim related directories like /etc/vim, /etc/gvim. After that, I was unable to run gvim. Whenever I run it , I always get the vim without gui. I tried reinstall vim-gnome by giving a command apt-get install --reinstall vim-gnome on a console. But no success. It still runs the vim without gui. and I also did: apt-get remove --purge vim-gnome vim-gtk apt-get install vim-gtk dpkg-reconfigure vim-gtk I tried vim-gtk and other variants but no success again. When I look inside the directory /usr/bin I see that the vim.gtk and vim.gnome is already there without any symbolic link. When I run them inside that directory, It still runs vim without gui. It is most likely that I deleted some files related to vim as mentioned above. I think the apt-get was confused after that. The only choice left is to compile it from the source. Goodbye to apt-get for gvim. Can somebody help to me? Without gvim, I feel myself as an orphan. Thanks, Ahmet __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
[Fwd: Re: Sharing vimproject file between WinXP and cygwin]
Whoops, forgot to cc the list.
Original Message
Subject: Re: Sharing vimproject file between WinXP and cygwin
From:Tom Purl [EMAIL PROTECTED]
Date:Wed, July 19, 2006 3:03 pm
To: Jean-Rene David [EMAIL PROTECTED]
--
The following path works well for me on both XP and Linux:
some_project=$HOME/some_project filter=*.txt CD=. {
I just have to set a %home% environment variable on my XP machine. I
can then synchronize my $HOME/some_project project between my Linux and
XP computers using unison and work on it using Vim without making any
modifications to anything.
HTH!
Tom Purl
I've been using the Project plugin for many years
now and I like it a lot. However one problem keeps
bugging me.
I would like to share my ~/.vimprojects file
between my cygwin and windows version of vim.
The problem is the paths for the project. When I
enter a posix path, the windows version doesn't
recognize it and vice-versa. I could run the file
through a small script which converts the paths
with cygpath but keeping them synchronized would
be cumbersome.
Any ideas?
--
JR
Re: Firefox and VIM?
Mozex is still supported for Firefox. Here's where you can download it: * https://nic-nac-project.de/~kaosmos/mozex107-en.html ...and here's how you can configure it with gnome-terminal: * http://blogs.sun.com/roller/page/alanbur/20041007#making_those_long_weblog_posts ...and here's what's in my Textareas field on Windows XP: * C:\PROGRA~1\vim\vim70\gvim.exe %t HTH! Tom Purl On Wed, Jul 19, 2006 at 01:39:07AM +0300, Yakov Lerner wrote: Right, mozex for firefox is at https://addons.mozilla.org/firefox/40/ But it seems not maintained for a long time Yakov On 7/19/06, Max Dyckhoff [EMAIL PROTECTED] wrote: From that very page: Mozex works with both Mozilla and Firebird. Interesting, I might try that out! Max -Original Message- From: Yakov Lerner [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 18, 2006 3:28 PM To: Noah Spurrier Cc: vim@vim.org Subject: Re: Firefox and VIM? On 7/19/06, Noah Spurrier [EMAIL PROTECTED] wrote: When is someone going to write a VIM plugin for Mozilla Firefox? For Mozilla Mozilla browser, such thing exists -- http://mozex.mozdev.org (i say mozilla mozilla to distinguish it from mozilla firefox :-) For Firefox, I'm not sure. Yakov
