Re: vim.org is down
http://groups.google.com/group/vim_dev/browse_thread/thread/36b81acf60548c20 I pointed out that it is a simple DNS issue, and gave some examples of Sourceforge sites that have chosen to add an A record for the domain (vim.org for us) in their DNS. ... 216.34.181.97 vim.org Turns out you're right, John, though I couldn't find any actual evidence in your mail or the thread you cited to prove it. :-) However, this page does prove it: http://sourceforge.net/apps/trac/sourceforge/wiki/Custom%20VHOSTs Since SF recommend it, putting an A record for the bare domain must be OK and not mess up their load balancing or anything (though without checking their docs, we couldn't have known that; another project's doing it doesn't make it right). IMHO, it would be wise to update our config so that it matches SF's recommendation. I agree with the DNS admin that people *should* use www. I don't really think people should use Chrome either, which is where the problem rears its head because Chrome doesn't automatically add the www for you if it has a failure. But that doesn't necessarily mean we shouldn't support it. In fact, IMHO, I have an opinion is a pretty poor reason not to do something, and other good reasons not to do this seem to be vanishing. Might as well take a few seconds to update the config and help these guys out. Ben. -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
RE: vim.org is down
Ben Schmidt wrote: Turns out you're right, John, though I couldn't find any actual evidence in your mail or the thread you cited to prove it. :-) However, this page does prove it: http://sourceforge.net/apps/trac/sourceforge/wiki/Custom%20VHOSTs Interesting docs, thanks. BTW while in general defining an A record for vim.org would not be sufficient when several websites are hosted at the one IP address, the fact that putting the entry that I showed in your hosts file works does prove that adding the DNS A record would work (although of course it is ideal to know that Sourceforge support that, and it will work in the future). I suggest you try Bram, and see if he wants to ask for the change. I'm still in let sleeping dogs lie camp. John -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: vim.org is down
On 23/04/11 6:29 PM, John Beckett wrote: Ben Schmidt wrote: Turns out you're right, John, though I couldn't find any actual evidence in your mail or the thread you cited to prove it. :-) However, this page does prove it: http://sourceforge.net/apps/trac/sourceforge/wiki/Custom%20VHOSTs Interesting docs, thanks. BTW while in general defining an A record for vim.org would not be sufficient when several websites are hosted at the one IP address, the fact that putting the entry that I showed in your hosts file works does prove that adding the DNS A record would work (although of course it is ideal to know that Sourceforge support that, and it will work in the future). O, I never said it wouldn't *work*. It just might not be reliable or responsible. If SF changed things, it would break, and if they were doing load balancing or geotargetting with DNS, we'd be bypassing it by hard-coding in a static IP, so could screw things up for them. I suggest you try Bram, and see if he wants to ask for the change. I'm still in let sleeping dogs lie camp. Well, I've given my opinion: I think it would be a nice thing to do for those who want it, it is technically feasible, wouldn't hurt anything, and I can see no good reason not to do it. But I don't actually care about it, and it doesn't affect me. So, if anyone's going to actually push for it, or put in extra work to convince Bram/our DNS admin (sorry I don't know his name!)/anyone else relevant to make the change, it won't be me. Smiles, Ben. -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
Re: vim.org is down
On 23/04/11 10:29, John Beckett wrote: Ben Schmidt wrote: Turns out you're right, John, though I couldn't find any actual evidence in your mail or the thread you cited to prove it. :-) However, this page does prove it: http://sourceforge.net/apps/trac/sourceforge/wiki/Custom%20VHOSTs Interesting docs, thanks. BTW while in general defining an A record for vim.org would not be sufficient when several websites are hosted at the one IP address, the fact that putting the entry that I showed in your hosts file works does prove that adding the DNS A record would work (although of course it is ideal to know that Sourceforge support that, and it will work in the future). I suggest you try Bram, and see if he wants to ask for the change. I'm still in let sleeping dogs lie camp. John Me too. If you want to be able to address vim.org without the www., then either use a browser which adds it, or put in your hosts file the line mentioned a couple of posts earlier, and you'll never see that there is no A record that your DNS server can find. Though if the nluug.nl admin (or someone) were to add a vim.org A record (for that domain which I don't use anyway) with a redirect to www.vim.org, I would certainly raise no hue and cry against it. Best regards, Tony. -- We are going to give a little something, a few little years more, to socialism, because socialism is defunct. It dies all by itself. The bad thing is that socialism, being a victim of its ... Did I say socialism? -- Fidel Castro -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
[PATCH] Fix tab completion for :find
The attached patch fixes this issue from todo.txt: :find completion does not escape space in directory name. (Isz, 2010 Nov 2) Carlo -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php vim-find-fix.patch Description: Binary data
Re: C comment indentation bug in to-do list
On 22-Apr-2011 Graeme McCutcheon graememcc_fire...@graeme-online.co.uk wrote: The to-do list includes the following bug: When entering a C /* comment, after typing Enter for 70 times the indent disappears. (Vincent Beffara, 2008 Jul 3) However, from the help for C indenting, the documentation for cinoptions syntax includes: *NVim searches for unclosed comments at most N lines away. This limits the time needed to search for the start of a comment. (default 70 lines). and something like set cinoptions=*100 does indeed change the behavior. Looks like a feature, not a bug! In fairness to the reporter, the documentation about the default was incorrect until changeset b9e314fe473f. Regards, Graeme Hi, thanks for your effort! I fixed the same bug some time ago the same way you did now (well, instead of digging through the docs I looked at the source code). I brought up the topic on the list and the response was that while the limit of 70 lines is a feature, the problem here is that the indent is for some reason decreased after the 70 lines while it would be better if it was copied from the previous line. -- Cheers, Lech -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
