> I use archlinux + awesome tiling WM. The bug is not 100% reproducible but it
> does happen most of the time (e.g. 90%). The steps to reproduce are:
>
> 1. Open gvim in full screen mode.
> 2. Create two buffers
> 3. Move to a different workspace (e.g. on the browswer)
> 4. return to the gvim work
On Thu, Mar 16, 2017 at 11:23:20PM +0900, Kazunobu Kuriyama wrote:
> 2017-03-16 8:40 GMT+09:00 Michal Grochmal <[1]groch...@member.fsf.org>:
>
> On Wed, Mar 15, 2017 at 11:16:49PM +0100, Bram Moolenaar wrote:
> >
> > Kazunobu Kuriyama wrote:
>> >
>>
On Wed, Mar 15, 2017 at 11:16:49PM +0100, Bram Moolenaar wrote:
>
> Kazunobu Kuriyama wrote:
>
> > > But it seems strange that we need to restrict [:cntrl:] and [:graph:] to
> > > ASCII only.
> >
> > Quite understandable. But otherwise, we will have to either rely
> > entirely on the is*() fun
I may be doing a horrible misinterpretation of the subject, but here goes
nothing.
> > > > This just uses the existing logic in mch_can_exe to populate a buffer
> > > > with the
> > > > absolute path to the binary. The Windows code was already walking
> > > > $PATH, so it seems pointless not to
> It can be resolved with bracketed paste, if both terminal and Vim
> support bracketed paste. I do not remember the current state of
> bracketed paste support in Vim, but AFAIR there were some patches
> somewhere.
That's true, bracketed paste should be available on most terminals
today. xfree86.
Hi guys,
I went through the list of emails about this topic and am a little
confused why it is being such a fuss. Apologies in advance if i'm
talking out of my ass but, at least according to my understanding, there
is no way for Vim to be immune to content pasted into it.
Vim is as much a script
Hi Bram,
> Vim has always been conservative about the default option values.
> Without any .vimrc the default is 'compatible'. That's nice for people
> who rely on the old Vi. But how many of these still exist? I expect
> nearly all Vim users to want 'nocompatible', thus create a .vimrc ASAP.
>
Hi,
On Mon, Jul 18, 2016 at 06:02:10AM +0200, Tony Mechelynck wrote:
> Right.
>
> >
> > The issue happens when I open Vim with the following configuration
> > (.vimrc):
> >
> > " 3 is tree listing
> > let g:netrw_liststyle=3
> > let g:netrw_chgwin=2
> > let g:netrw_winsize=22
> >
Hello,
Apologies if this email bounces several times, it is my first time using
googlegroups. And I am struggling with their we interface.
I believe I found a bug in the runtime/autoload/netrw.vim script (the
path is based on the repository structure). Since `netrw` is a script
originally by Dr
