Re: VimTips - Google Wiki Usefulness
Yakov Lerner ([EMAIL PROTECTED]) wrote: On 2/26/07, A.J.Mechelynck [EMAIL PROTECTED] wrote: Paul Irofti wrote: Hello vimmers, I don't understand why Google Wiki is being discussed here as the main solution. As I see it there are a few _major_ disadvantages of using it: - it has software limitations that a large community, such as ours, can't cope with - it's managed and offered by a third party organization - we don't have controls of what features we want in and/or out or the way the layout/code/roadmap goes - it's a commercial product and Vim will be asociated with it in the long run - Google is as corporate as you can get, corporations and OpenSource don't mix well together (there are tons of examples) - from what I've read in this thread it doesn't even have all the features needed for a working Vim-tips wiki On the other hand mediawiki seems the best solution for something like this: - it's *OpenSource* - it offers an easy management environment - it can support high loads of traffic (see wikipedia) - it has multi-language support - it's easy to customize and improve - it's not chown()-ed by any corporation I know I'm not a regular here, but I read most of the mail I get from vim@ and don't quite get why you people are seriously considering this. So I thought I'd drop my two cents and hope that someone can shed some light. Thanks, Paul. Not a regular, maybe, yet your name isn't unfamiliar to me. Thanks for passing by. If we gan get hosting space somewhere for a mediawiki server, I'm all in favour. ElWiki.com Free MediaWiki hosting with fast setup. A free .com/net/org domain is offered for wikis which reach 10 pages of content. Google AdSense text-ads may be added to the right sidebar to cover hosting expenses. From: http://en.wikibooks.org/wiki/Wiki_Science:How_to_start_a_Wiki Yakov I just checked the ElWiki.com. It sound really nice in the sense that it's completely free. However, checking the terms, some made me think if it is what a Vim community should agree with (I quote from http://elwiki.com/register.php): Terms and Conditions Privacy # We won't spam you - your email address will only be used for notifications related to your account, and will not be disclosed to 3rd parties. Domain # Once your site reaches 10 pages of content, we will contact you via email and you will be offered a free .com/.net/.org address of your own choosing. # If you already own a domain which you would like to use, email domains[at]elwiki.com after you sign up and we will be happy to assist. # ElWiki will cover all costs associated with domain registration. Ownership # The site URL (domain or subdomain) will remain property of ElWiki. # Your site content will be licensed under the GNU Free Documentation License. Advertising # We reserve the right to display contextually-targeted text-based sponsored links in the right sidebar of your paes. # When using our free service, you may not add advertising to your Wiki without our prior consent. Obligations # The service is provided free-of-charge, as-is, and without any guarantees or obligations. # We reserve the right to cancel or alter the service at any time. Acceptable Use Policy # Use of this service for harrassing, obscene, or illegal activities is strictly prohibited. # Use of this service for hosting pornographic images is prohibited. Control and Approval # ElWiki reserves the right to reject creation of a Wiki, or delete a Wiki at it's sole discretion. # ElWiki may make ammendments to the site title, URL, or description. # You will be given non-exclusive administrative control over any site you choose to host with us. So this means that they can stop the wiki without further question or make it not free anymore, and therefore, what would become of the contents of the wiki? I also believe that mediawiki would be a good solution but I agree with Antoine when he says: the problem would be a free hosting. KR, Gregory
Re: VimTips - Google Wiki Usefulness
John Beckett ([EMAIL PROTECTED]) wrote: Bram Moolenaar wrote: I think this puts too much burdon the volunteers that become an admin. And it defeats the easy of use of a wiki. I was suggesting that people who have a tip, or a change, would email it to a Vim mailing list, where it would be massaged by the community, then posted to the wiki by an admin. Yes, that would burden the admins, and is against the spirit of a wiki. However, as I understand the Google wiki, a person wanting to post a tip would need to have a Google ID, and would have to mail an admin, and the admin would have to add the new person as an admin, then reply to the mail. That's also a pain for an admin, and is not really easy use of a wiki either. And which admin would be emailed? John Hello all, I just want to give you some ideas that you could maybe be useful for the Wiki (which I think is a great idea) or its administration. Concerning the registration, a reply mail for a confirmation of the activation of the membership is a great idea, and would prevent some bots to automatically post on the Wiki. Moreover, as an upper security level, the registering candidate could be asked to write down the numbers/letters that he/she would see on a picture representing those numbers/letters. That would prevent the registering candidate to be a bot or at least reduce it ever more (I've seen this in a couple of forums around). I believe that all the members, asking for a registration, should be able to post tips. In order to make it possible, I think that 3 levels of members should be there: 1. Admins : they manage the users and the wiki (they would have all the rights the reviewers have. See below) 2. Reviewers: the can review, edit and delete any post written in the wiki (it would facilitate the admins burden) and also manage the sections (create, move tips from a section to another, ...) 3. Members : they can post tips and modify their own post. They become sort of the owner of their post but where reviewers and admins can overlook it In this way, the responsability is a bit more spread and the admins are not only responsible for the Wiki contents. Regarding the type of wiki, I just checked out Mediawiki for work and it seems pretty nice but I don't know if it would meet what I proposed but if you think my ideas could be used, I could check it out. I hope it helped. Gregory SACRE
Re: ':Explore' higlight the results
Hello Chip, I followed your procedure, but unfortunately, the behaviour of netrw surprised me. The installation went fine, no error messages. I tried the following command: :Explore **//STRING to find all the file containing the string STRING. The command just hanged there, not doing anything, like freezing my gvim. I have to type CTRL-C to stop. Before the update, it was giving me the list of the files of the current directory and I could navigate through the results using SHIFTUP or DOWN. When I tried: :Explore */STRING it gave me a lot of error messages that disappeared too fast for me to read it. Is there a way to get that output to be able to debug it with your help? I'm running Vim 7.0 (compiled May 7 2006) on Windows XP (I didn't try it on my Linux box at home). Gregory On 11/3/06, Charles E Campbell Jr [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: Hello Vimmers, I've seen recently in the mailing list an interesting post/question about searching for a list of fies containing a pattern. The answer was that we could use :Explore or :vimgrep. For me, the first solution seems the best. I have a friend of mine that is using emacs, which has the same option as :Explore. However, the files matching the pattern are highlighted. Is it possible to do the same with :Explore? I checked the :help :Explore but couldn't find it. I've uploaded v107g of netrw.vim which supports this to my website: http://mysite.verizon.net/astronaut/vim/index.html#VimFuncs see Network Oriented Reading, Writing, and Browsing First, remove all previous versions of netrw from both your personal directories and from the system directory where netrw was installed (under Linux, that's often /usr/local/vim/share/vim/vim70/[plugin|autoload|doc]/netrw*). You'll also need to remove all previous versions of vimball. You can get the latest vimball from my website, too (see Vimball Archiver). Install it first: cd /usr/local/vim/share/vim/vim70 mv [wherever]/vimball.tar.gz . gunzip vimball.tar tar xvf vimball.tar Then you may install netrw: vim netrw.vba.gz :so % :q should do it. Regards, Chip Campbell
':Explore' higlight the results
Hello Vimmers, I've seen recently in the mailing list an interesting post/question about searching for a list of fies containing a pattern. The answer was that we could use :Explore or :vimgrep. For me, the first solution seems the best. I have a friend of mine that is using emacs, which has the same option as :Explore. However, the files matching the pattern are highlighted. Is it possible to do the same with :Explore? I checked the :help :Explore but couldn't find it. Thanks in advance! Gregory
How to check the difference with the origin file
Hello Vimmers, I was wondering if there is a way to see the differences between the file you are modifying and its original version. For example: Let's say I'm editing a text file. I finished editing it and I'd like to see all the changes I've performed on it since I opened it (to write down the changes and put them in a CVS or SVN log for example). I know there's the :undolist command but it doesn't give me the actual changes perfromed. Is there a way to do this? Should I use the .swp file in any way? Thanks, Gregory
Re: How to check the difference with the origin file
Thank you very much Yakov! It worked perfectly! On 10/2/06, Yakov Lerner [EMAIL PROTECTED] wrote: On 10/2/06, Gregory SACRE [EMAIL PROTECTED] wrote: I was wondering if there is a way to see the differences between the file you are modifying and its original version. The following nice thing comes from Donn Washburn: command! DiffOrig vert new | set bt=nofile | r # | 0d_ | diffthis | wincmd p | diffthis So (1) you puth the command above in your vimrc (2) When you want to see diffs with original (unsaved) file, you do :DiffOrig If you never used vim-diff-mode, you might need to read about it first, or try it in separate window (vimdiff oldfile newfile) Yakov