Christian Brabandt wrote:
> On Mi, 24 Mai 2017, fREW Schmidt wrote:
>
> > Yes. "If I replace the contents of /usr/share/vim/vim80/syntax/vb.vim with
> > `let
> > b:current_syntax = "vb"` everything is fast and, as I would hope, the
> > support
> > files are not loaded N times per buffer but
Frew Schmidt wrote:
> I'm glad you were able to come up with a solution! So I guess `vim *` goes
> through a different codepath than `:args *`? Note that this also affects the
> quickfix, the location list, and the local args list. Initially I discovered
> this issue with `:cexpr` and
Is there a way for vim's autocomplete (ctrl+n, ctrl+p) to show case
sensitive matches?
For example, if I have fooBar and foobar in the current file, I start
type foo, then hit ctrl+n, I would like to be able to chooose between
fooBar and foobar, but vim thinks there is only one match (foobar)
I
Le jeudi 25 mai 2017 16:25:06 UTC+2, Ben Fritz a écrit :
> On Thursday, May 25, 2017 at 4:58:48 AM UTC-5, Ni Va wrote:
> > Hi,
> >
> > Attempting to profile my _vimrc i've launched this command :
> >
> > .\vim80\gvim.exe --cmd 'profile start _vimrc.profile" --cmd "profile! file
> > _vimrc"
> >
On Thursday, May 25, 2017 at 4:58:48 AM UTC-5, Ni Va wrote:
> Hi,
>
> Attempting to profile my _vimrc i've launched this command :
>
> .\vim80\gvim.exe --cmd 'profile start _vimrc.profile" --cmd "profile! file
> _vimrc"
>
>
> but this error happens :
>
> Error detected while processing
On Thu, May 25, 2017 at 09:14:06AM +0200, Christian Brabandt wrote:
> So perhaps we need a similar change here as well. Can you provide a
> reproducible example for the :cexpr case please)?
Sure; same setup as before, and in vim:
:cexpr system('ls * \| xargs -n1 -I{} echo {}:1:{}')
--
fREW
Hi,
Attempting to profile my _vimrc i've launched this command :
.\vim80\gvim.exe --cmd 'profile start _vimrc.profile" --cmd "profile! file
_vimrc"
but this error happens :
Error detected while processing pre-vimrc command line:
E20: Mark not set
And the _vimrc.profile is not feed.
Thank
On May 25, Christian Brabandt wrote:
> [...]
>
> I am not sure, if this behaviour is a bug. However after
> thinking some more about it, I am wondering, whether the
> fact that the BufNew autocommand triggers a FileType
> autocommand is a bug itself, since autocommands shouldn't
> nest
On Mi, 24 Mai 2017, Frew Schmidt wrote:
> I'm glad you were able to come up with a solution!
So much for the unwillingness of the vim maintainers to fix this issue.
> So I guess `vim *` goes through a different codepath than `:args *`?
Don't think so. Perhaps the autocommand wasn't set up
Fullquote, because I am CC'ing Bram for comment
On Mi, 24 Mai 2017, Christian Brabandt wrote:
>
> On Mi, 24 Mai 2017, fREW Schmidt wrote:
>
> > Yes. "If I replace the contents of /usr/share/vim/vim80/syntax/vb.vim with
> > `let
> > b:current_syntax = "vb"` everything is fast and, as I would
10 matches
Mail list logo