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 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/).
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