Hi all!
I have the following ./configure invocation for building vim:
./configure --prefix=$HOME/apps/vim --with-features=huge \
--enable-perlinterp --enable-pythoninterp --enable-rubyinterp \
--enable-tclinterp --enable-luainterp
However, when the python run-time (or whatever) is
On 22/04/11 08:29, Shlomi Fish wrote:
Hi all!
I have the following ./configure invocation for building vim:
./configure --prefix=$HOME/apps/vim --with-features=huge \
--enable-perlinterp --enable-pythoninterp --enable-rubyinterp \
--enable-tclinterp --enable-luainterp
However, when
When 'encoding' is changed from default codepage, mkdir() doesn't work
for multi-byte name.
:set encoding=utf-8
:call mkdir(\u00a1)
:echo isdirectory(\u00a1)
0
(directory with broken name was created)
Please check the following patch. Changed to use _wmkdir().
diff -r 987cd9455925
Hello Bram,
hello list,
attached is a new syntax file for gnash(1) configuration files.
and a fix for a previous typo of mine.
--
bye Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Do not top-post! Type your
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
Nobody but Bram has commit access.
Interesting. So what's the protocol here? Can I try to get the patch
to him? Or does this patch have to sit in the ether for years until
someone is willing to be the maintainer of php.vim?
I'm hoping there's some kind of fallback mechanism for when a syntax
Dear [web] admins,
There is no A record for the domain name vim.org. That is,
this link shouldn't work:
http://vim.org/
Some browsers have a hack, where upon getting a failed DNS
response, will try adding www. to the beginning, but some won't.
And some of us use a DNS resolver (like opendns)
On 23/04/11 00:27, JasonWoof wrote:
Nobody but Bram has commit access.
Interesting. So what's the protocol here? Can I try to get the patch
to him? Or does this patch have to sit in the ether for years until
someone is willing to be the maintainer of php.vim?
I'm hoping there's some kind of
There have been lot's of discussion about this on the mailinglist.
That this topic is being written about again and again is a reason to
change it. IMHO.
Marc Weber
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For
Jason wrote:
There is no A record for the domain name vim.org. That is,
this link shouldn't work:
http://vim.org/
That's correct, actually. Not only doesn't it work, but it shouldn't
work. It is a shame people have abused DNS and expect it to work.
Marc wrote:
There have been lot's of
On Sat, 23 Apr 2011, Ben Schmidt wrote:
Marc wrote:
There have been lot's of discussion about this on the mailinglist. That
this topic is being written about again and again is a reason to change it.
IMHO.
To some extent, I agree. It'd be nice to 'fix' this, just to silence the
noise on
Perhaps the simplest thing is to get some cheap 'DNS hosting' that
offers a 'redirect' function. Basically the function just has a
server listen on port 80 for requests and return a 3xx (preferably
301 in our case) redirect (to http://www.vim.org/ in our case)
whenever it gets one.
I've taken
On 23/04/11 2:33 PM, Ben Schmidt wrote:
Perhaps the simplest thing is to get some cheap 'DNS hosting' that
offers a 'redirect' function. Basically the function just has a
server listen on port 80 for requests and return a 3xx (preferably
301 in our case) redirect (to http://www.vim.org/ in our
Ben Schmidt wrote:
Just to clarify, I don't mean that it's working for end
users; I just mean it looks to me like the server is
responding correctly, so if our DNS admin agrees to make the
change outlined above, things should go smoothly.
Here is a rehash from the August 2010 thread:
14 matches
Mail list logo
