My apologies for skipping the maintainer. I will reach out to him directly.
--
--
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 messag
> Ok, it makes sense. But what about the first part of my post, before
> "But let us assume for a moment that this behaviour is correct"?
>
> There is neither buffer named '~/foobar/bar' nor '~/foobar/baz'. There
> are only 'bar' and 'baz' buffers. The results returned by either ':ls'
> or '' are
Aaron Peschel wrote:
> Fix is to runtime/syntax/apache.vim provided with vim. The current
> syntax file does not handle escaped quotes correctly.
Did you try contacting the maintainer, David Necas?
--
hundred-and-one symptoms of being an internet addict:
205. You're constantly yelling at your
On Thursday, September 12, 2013 1:59:51 AM UTC-7, ZyX wrote:
> On Sep 12, 2013 3:28 AM, "kans" wrote:
>
> >
>
> > On Wednesday, September 11, 2013 7:46:06 AM UTC-7, ZyX wrote:
>
> > > On Sep 11, 2013 1:27 PM, "Thomas" wrote:
>
> > >
>
> > > >
>
> > >
>
> > > > On 11 September 2013 00:18, N
Hirohito Higashi wrote:
> Hi Bram and Vim developers,
>
> How to reproduce. (on linux)
> - set terminal size to 80x20
> - make test
> - test92 and test93 fail.
> - test92.in and test93.in become empty.<--- unexpected!
>
> Expect behavior
> - test92.in and test93.in keep the contents of file
On Wednesday, September 11, 2013 6:36:28 PM UTC+2, ZyX wrote:
> > But let us assume for a moment that this behaviour is correct. Then:
>
> >
>
> > :buffer bar
>
> >
>
> > should display analogous results (because 'bar' is a substring in the
>
> > absolute path for all files). That is:
>
>
