Hirohito Higashi wrote:
> Contents of fixes.
>
> runtime/doc/diff.txt
> 1. :diffupdate abbreviation is :dif. not :diffs
>
> runtime/doc/options.txt
> - boolean option neet no~ index. ('breakindent', 'fsync', 'langnoremap')
> I checked all boolean option. above three options is missing no~.
>
>
David wrote:
> On Tuesday, October 20, 2015 at 8:47:27 PM UTC+2, ZyX wrote:
> > 2015-10-20 21:11 GMT+03:00 glts <676c7...@gmail.com>:
> > > In a plain Vim installation, if I have a personal ftplugin
> > > ~/.vim/ftplugin/text.vim that contains the line
> > >
> > > setlocal expandtab
> >
On Wednesday, October 21, 2015 at 11:51:04 PM UTC+2, Gary Johnson wrote:
> On 2015-10-21, glts wrote:
> > On Wednesday, October 21, 2015 at 8:32:32 PM UTC+2, Gary Johnson wrote:
> > > On 2015-10-21, glts wrote:
> > > > On Tuesday, October 20, 2015 at 8:47:27 PM UTC+2, ZyX wrote:
> > > > > 2015-10-2
Hi Bram and list,
Contents of fixes.
runtime/doc/diff.txt
1. :diffupdate abbreviation is :dif. not :diffs
runtime/doc/options.txt
- boolean option neet no~ index. ('breakindent', 'fsync', 'langnoremap')
I checked all boolean option. above three options is missing no~.
runtime/doc/syntax.txt
- t
On Thursday, October 22, 2015 at 10:32:59 AM UTC-5, Matthew Horan wrote:
> To reproduce this issue:
>
> mkdir with\ spaces
> ln -s $(which sh) with\ spaces/
> SHELL=$(pwd)/with\ spaces/sh vim
>
>
>
> In the launched Vim, trying to execute anything through a shell, ie :! ls,
> will fail with th
2015-10-22 2:29 GMT+03:00 Radoslaw Burny :
> To reply to the previous question about my measurements: I took one of the
> bigger files from my team's C++ codebase, and copied it 5 times. The result
> was 1.1 MB, 30 kLOC C++ file. Only the first search time was measured;
> vim-searchindex caches th
Am 2015-10-21 15:55, schrieb Martin Florian:
can someone maybe help me out? I'm looking for the current maintainer
of
ftplugin/changelog.vim (see forwarded mail for context).
Well if no one answers, let me try.
Would you be willing to maintain that file yourself?
For a smaller file, this shou
Hi,
As I said, you should post this direct to vim-dev yourself (maybe copy
to Bram), and it'll get considered for inclusion.
For what it's worth, I've checked through the changes and they look
fine to me (although I'd defer to Bram on whether it's OK to take out
support for ancient Vim versions -
