On Mon, May 16, 2016 at 2:01 AM, Gary Johnson wrote:
> On 2016-05-15, Dun Peal wrote:
>> Any ideas? Is this a bug? Should I post this somewhere else?
>
> This is the right place. I can reproduce the behavior. It looks
> like a bug to me. I was hoping for a response from someone more
> knowled
> On 13 May 2016, at 3:45 pm, Nikolay Aleksandrovich Pavlov
> wrote:
>
> I guess the answer is buried in the source code only. I know that
>
> a) Current window’s statusline is updated on
>
> 1. typing something
> 2. changing mode
> 3. changing some options, but I can’t give you a list
> 4. ru
Christian Brabandt wrote:
> On Sa, 14 Mai 2016, Bram Moolenaar wrote:
>
> >
> > Christian Brabandt wrote;
> >
> > > On Fr, 13 Mai 2016, Ken Takata wrote:
> > >
> > > > Hi,
> > > >
> > > > 2016/5/13 Fri 4:59:07 UTC+9 Bram Moolenaar wrote:
> > > > > Gabriele Fava wrote;
> > > > >
> > > > > >
> As a workaround (without forcing term=builtin_ansi), do you have any
> success if you hit backspace a bunch of times at the password prompt,
> before you start typing the password?
Yes: this works. If I remove forcing the term and I hit backspace a few times,
then I can edit the file properly.
Reading the link Justin posted, seems like this is a limitation resulting from
the design of Vim.
Given this limitation, is there another way to run post-creation setup on *all*
matching buffers, including those created for files specified on the CLI?
I need to set the filetype and run a bunch
On Mo, 16 Mai 2016, Bram Moolenaar wrote:
> 99% of users will never use the file, there is not much point in
> including it in the installer. It can be made available separately, so
> that when someone wants to debug the executable that is possible.
Well, it is 16.5 MB vs. 13 MB (that is the 64b
On Thu, May 12, 2016, Frosty Frosty wrote:
> Combinations like Ctrl + [ , Ctrl + W (work with windows) or Ctrl + U, Сtrl +
> D e.t.c. don't work for El Capitan and MacVim 7.4. Do you have the same
> problem or this is only my system bug?
It's not true on mine. Do you have Ctrl remapped to someth
On 5/15/2016 8:10 PM, Eric Christopherson wrote:
On Sun, May 15, 2016, Tim Chase wrote:
On 2016-05-15 19:08, 'Suresh Govindachar' via vim_use wrote:
I exported the entire Windows registry -- resulting text file is
about 500 MBytes. I can open this text file in Notepad++ -- but
opening it in Vi
