On Sunday, 23 February 2014 23:51:48 UTC+1, MarcWeber wrote:
> Excerpts from Diego Viola's message of Sun Feb 23 09:29:16 + 2014:
>
> > I would like to start by saying that I admire your work on Vim, I've
>
> > been using it for quite some time now and I really enjoy using Vim
>
> > every d
> So many years of usage experience went into vim. This means the existing code
> addresses a vast number of corner cases which crept up during the years.
that's why Bram wants a test for every patch ;)
I don't have the expertise to say which path would be the best for neovim, but
at least test
Michel Albert :
> Partial refactoring is harder (depending on the case, a *lot* harder)
> and will take longer but is not risking as much. And not to forget,
> has a chance to get merged into the mainline code.
The problem with this approach is that everything would still have to go
through Bram,
Vundle vs Vam vs .. issues showed that users don't need 100%
satisfaction in all cases - projects can still be successful.
Eg I mean: Vundle depends on vim-scripts.org - and vim-scripts org maps
scripts from www.vim.org to urls by title - and some title occur more
than once. Thus there is a chance
I don't understand, Bram says "It's much better to improve what we have." which
is good and reasonable to me. I agree with this.
But then we have people like Thiago de Arruda (aka tarruda)
> Currently the 'lispwords' setting is global, yet three filetypes attempt
> to change it on filetype/indent load: scheme, clojure, and art.
>
> Scheme and Clojure, in particular, are two very different Lisp variants,
> but both modify 'lispwords' to influence their indenting. Both filetypes
> also
On Mon Feb 02/24/14 at 8:01, Diego Viola wrote:
> But then we have people like Thiago de Arruda (aka tarruda) who have
> worked very hard on multithreading support for Vim, and his patches
> didn't make it into mainline Vim.
>
> So how can we "improve what we have" when 99% of the patches are igno
OK I'm sorry about that, that was an exaggeration.
Sorry.
--
--
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
---
You received this message because you are
On Monday, February 24, 2014 10:29:38 AM UTC+1, Jan Larres wrote:
> So in
> addition to the refactoring I think that a more flexible development
> model that is not dependent on just one person and an antiquated
> 'patches' system could definitely improve things.
That, however, is something that
Hi,
Apache's ProxyPassMatch directive
(http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypassmatch) is not
recognised as a keyword in vim.
I've added the directive to apache's syntax file and attached the diff. It is
my first contribution to vim, so please let me know if the diff format
Hello,
I have created an updated version of the gnuplot syntax highlighting file for
vim. It is available at http://www.vim.org/scripts/script.php?script_id=4873.
The version of gnuplot.vim by John Hoelzel that ships with vim is 11 years out
of date, and the only other one I found was by Jim E
On 24 February 2014, Diego Viola wrote:
> I don't understand, Bram says "It's much better to improve what we
> have." which is good and reasonable to me. I agree with this.
>
> But then we have people like Thiago de Arruda (aka tarruda) who have
> worked very hard on multithreading support for Vim
> In my opinion the way forward is for enough people to start reading
> the code, patiently and diligently, in their own rhythm. Once there is
> a critical mass of developers who actually understand the code,
Which will never happen because those people today who want to code
might no longer choos
LCD 47 :
> In my opinion the way forward is for enough people to start reading
> the code, patiently and diligently, in their own rhythm. Once there is
> a critical mass of developers who actually understand the code, and see
> it as just old, rather than terrible or evil, we might see progres
On 24 February 2014, Marc Weber wrote:
[...]
> Thus its even more important that we try to turn Vim into kind of
> "business" model - because "specialization" is the engine of todays
> world - even more for complex software like Vim.
What I'm saying is, it takes _knowledge_ to move forward.
On 25 February 2014, Jan Larres wrote:
> LCD 47 :
> > In my opinion the way forward is for enough people to start
> > reading the code, patiently and diligently, in their own rhythm.
> > Once there is a critical mass of developers who actually understand
> > the code, and see it as just old, r
LCD 47 :
> On 25 February 2014, Jan Larres wrote:
>> LCD 47 :
>>> In my opinion the way forward is for enough people to start
>>> reading the code, patiently and diligently, in their own rhythm.
>>> Once there is a critical mass of developers who actually understand
>>> the code, and see it as
When lex/yacc are used to generate C++ compatible sources, these extensions are
used. However, vim syntax highlighter doesn't currently recognize them. I think
these extensions should be added.
As a reference, GNU automake recognizes them:
http://ftp.gnu.org/old-gnu/Manuals/automake-1.6.1/html_n
+1 to this.
On Tuesday, December 31, 2013 1:01:55 PM UTC+1, Shougo wrote:
> Hi, Bram.
>
>
>
> I created the patch for adding option to disable insert completion message in
>
> shortmess.
>
> Because, the completion message is not useful for powered users.
>
> But it clears previous command
Adam Matan wrote:
> Apache's ProxyPassMatch directive
> (http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypassmatch)
> is not recognised as a keyword in vim.
> I've added the directive to apache's syntax file and attached the
> diff. It is my first contribution to vim, so please let me kn
CSS defines words which contain '-'. This change lets syntax files for CSS
highlight such words correctly.
--
Masanori Ogino
http://twitter.com/omasanori
http://gplus.to/omasanori
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you
reported to python bug tracker http://bugs.python.org/issue20763
--
Yukihiro Nakadaira - yukihiro.nakada...@gmail.com
--
--
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
When -Dusethreads is specified for building perl, build stops with error.
Below is a patch.
https://gist.github.com/mattn/9202034
I tested this on:
linux perl 5.14 & --enable-perlinterp=yes (OK)
linux perl 5.14 & --enable-perlinterp=dynamic (OK)
linux perl 5.16 & --enable-perlinterp=yes (OK)
lin
perl 5.19.9 include signatures feature, and it will be released on 5.20 .
The feature break syntax of sub-routine prototype. For example, signatures
allow to write like follow.
sub foo($class, $a, $b = sub(){ warn "foo" }) {
# ...
}
Below is a patch.
https://gist.github.com/mattn/9185175
Tha
Yuri Vic wrote:
> When lex/yacc are used to generate C++ compatible sources, these
> extensions are used. However, vim syntax highlighter doesn't currently
> recognize them. I think these extensions should be added.
> As a reference, GNU automake recognizes them:
> http://ftp.gnu.org/old-gnu/Manu
Masanori Ogino wrote:
> CSS defines words which contain '-'. This change lets syntax files for CSS
> highlight such words correctly.
If the problem is in the syntax file, then fix it in the syntax file.
Changing 'iskeyword' has lots of side effects, better avoid that.
--
ARTHUR:A scrat
Sorry typo.
On Tuesday, February 25, 2014 12:46:53 PM UTC+9, mattn wrote:
> When -Dusethreads is specified for building perl, build stops with error.
> Below is a patch.
When -Dusethreads is NOT specified for building perl, And building with
--enable-perlinterp=dynamic, build stops with error. B
Yasuhiro Matsumoto wrote:
> When -Dusethreads is specified for building perl, build stops with error.
> Below is a patch.
>
> https://gist.github.com/mattn/9202034
>
> I tested this on:
>
> linux perl 5.14 & --enable-perlinterp=yes (OK)
> linux perl 5.14 & --enable-perlinterp=dynamic (OK)
> li
On Mon, Feb 24, 2014 at 07:52:47PM -0800, mattn wrote:
> perl 5.19.9 include signatures feature, and it will be released on 5.20 .
> The feature break syntax of sub-routine prototype. For example, signatures
> allow to write like follow.
>
> sub foo($class, $a, $b = sub(){ warn "foo" }) {
> # .
On Tuesday, February 25, 2014 1:34:30 PM UTC+9, Bram Moolenaar wrote:
> Yasuhiro Matsumoto wrote:
>
> > When -Dusethreads is specified for building perl, build stops with error.
> > Below is a patch.
> >
> > https://gist.github.com/mattn/9202034
> >
> > I tested this on:
> >
> > linux perl 5.14
I need to add small fix about this patch. Please wait.
--
--
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
---
You received this message because you are sub
On Tuesday, February 25, 2014 1:46:18 PM UTC+9, mattn wrote:
> I need to add small fix about this patch. Please wait.
Done. Updated https://gist.github.com/mattn/9202034
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying
Thank you.
I'll post again if I find that the problem can't be fixed without changing
'iskeyword'. Until that, please ignore the patch.
2014-02-25 13:15 GMT+09:00 Bram Moolenaar :
>
> Masanori Ogino wrote:
>
> > CSS defines words which contain '-'. This change lets syntax files for
> CSS
> > hi
James McCoy wrote:
> In Ruby 2.x, there exists RbConfig::CONFIG['rubyarchhdrdir'] which
> should be used instead of constructing the path from
> RbConfig::CONFIG['rubyhdrdir'] and RbConfig::CONFIG['arch']. The
> attached patch does this.
Thanks, I'll put it on the todo list.
--
BLACK KNIGHT:
On 25 February 2014, Jan Larres wrote:
> LCD 47 :
> > On 25 February 2014, Jan Larres wrote:
> >> LCD 47 :
> >>> In my opinion the way forward is for enough people to
> >>> start reading the code, patiently and diligently, in their own
> >>> rhythm. Once there is a critical mass of developer
> So can you suggest a patch?
Sure, attaching patch.
--
--
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
---
You received this message because you are subs
36 matches
Mail list logo
