On Wednesday 09 January 2008, Marc Haisenko wrote:
Hi folks,
a few weeks back I posted a patch that helps enabling cross-compiling by
adding the necessary stuff in configure.in to tell configure the necessary
values when cross-compiling. The patch also includes a README explaining
Hi all,
to reproduce:
vim -u NONE -U NONE
:set syntax
:set ft=mail
ithis newline is for readability
http://vim.org/(test)
The closing bracket will not be highlighted.
Richard
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For
On Jan 9, 6:06 pm, Andy Wokula [EMAIL PROTECTED] wrote:
I tried to write a function that collects all the matches for a given
pattern in the text.
For that purpose, it would be very nice if the following worked:
:%s/{pattern}/\=MyAddMatch(submatch(0))/gn
I agree, this could be
On Jan 10, 2008 4:20 PM, Ben Schmidt [EMAIL PROTECTED] wrote:
I suspect it is deliberate. URLs rarely contain parentheses, but are often
written
inside them in sentences, e.g.
There is interesting information on the web (for example, at http://vim.org/).
That is true. In case there is an
Richard Hartmann wrote:
On Jan 10, 2008 4:20 PM, Ben Schmidt [EMAIL PROTECTED] wrote:
I suspect it is deliberate. URLs rarely contain parentheses, but are often
written
inside them in sentences, e.g.
There is interesting information on the web (for example, at
http://vim.org/).
ap schrieb:
On Jan 9, 6:06 pm, Andy Wokula [EMAIL PROTECTED] wrote:
I tried to write a function that collects all the matches for a given
pattern in the text.
For that purpose, it would be very nice if the following worked:
:%s/{pattern}/\=MyAddMatch(submatch(0))/gn
I agree, this
On Fri, Jan 11, 2008 at 02:20:05AM +1100, Ben Schmidt wrote:
to reproduce:
vim -u NONE -U NONE
:set syntax
Presuming you mean :syntax enable.
:set ft=mail
ithis newline is for readability
http://vim.org/(test)
The closing bracket will not be highlighted.
I suspect
Richard Hartmann wrote:
On Jan 10, 2008 4:20 PM, Ben Schmidt [EMAIL PROTECTED] wrote:
I suspect it is deliberate. URLs rarely contain parentheses, but are often
written
inside them in sentences, e.g.
There is interesting information on the web (for example, at
http://vim.org/).
On Thu, Jan 10, 2008 at 08:28:14PM +0100, Tony Mechelynck wrote:
The parentheses should have been percent-escaped, i.e., replaced by a percent
sign and their hex value (00-FF) as in
http://www.vim.org/%28test%29
While it's true that the URL RFC dictates that such characters should be
On Jan 10, 2008 2:39 PM, James Vega [EMAIL PROTECTED] wrote:
On Thu, Jan 10, 2008 at 08:28:14PM +0100, Tony Mechelynck wrote:
The parentheses should have been percent-escaped, i.e., replaced by a
percent
sign and their hex value (00-FF) as in
http://www.vim.org/%28test%29
I was thinking of RFC 1738 (Uniform Resource Locators) but it also
mentions that parentheses are reserved characters and can be escaped
unless they're being used for a reserved purpose.
And whether they have a reserved purpose is dictated by the URL scheme, isn't
it,
not the
Philip Prindeville wrote:
This is simple enough: suppress the detecting of /usr/local and
putting it into the load path (etc) if we're cross-compiling.
Please review this and if it looks reasonable, signal to whomever to
commit it to the source tree (as a patch, obviously) or cast a
Marc Haisenko wrote:
On Wednesday 09 January 2008, Marc Haisenko wrote:
Hi folks,
a few weeks back I posted a patch that helps enabling cross-compiling by
adding the necessary stuff in configure.in to tell configure the necessary
values when cross-compiling. The patch also includes a
Patch 7.1.215
Problem:It is difficult to figure out what syntax items are nested at a
certain position.
Solution: Add the synstack() function.
Files: runtime/doc/eval.txt, src/eval.c, src/proto/syntax.pro,
src/syntax.c
*** ../vim-7.1.214/runtime/doc/eval.txt
Bram Moolenaar wrote:
A couple of problems were detected when the Unix shell is used to expand
file names containing characters such as a single quote. This applies
to completion on the command line and glob().
I made a patch that defines a function to echo each file name
separately. Inspired
Although according the Ben's earlier posting, we're both in the pipeline.
So I guess we just sit tight a little longer...
If you haven't seen Bram's post to you now (that should comt to you directly
and
via the vim_dev list), let me know and I will forward its text only to you.
Seems
he
On 10/01/2008, Ben Schmidt [EMAIL PROTECTED] wrote:
Andy Wokula wrote:
Bram Moolenaar schrieb:
Patch 7.1.215
Problem:It is difficult to figure out what syntax items are nested
at a
certain position.
Solution: Add the synstack() function.
Files:
Bram Moolenaar wrote:
Patch 7.1.215
Problem:It is difficult to figure out what syntax items are nested at a
certain position.
Solution: Add the synstack() function.
Files: runtime/doc/eval.txt, src/eval.c, src/proto/syntax.pro,
src/syntax.c
If you'd like to
Ted Pavlic mentioned on the vim-mac list that --remote-tab-silent is
not mentioned in the --help output and suggests to add it. I think
that's a good idea. What do you think?
There has been some positive feedback on this, so here's a patch to
implement it.
Bye,
Nico
Hi Bram,
There are already more than 200 patches. When will 7.2 come out? Any plans?
Regards,
Edward Leap Fox
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
20 matches
Mail list logo
