On Thu, Oct 1, 2015 at 1:59 AM, h_east wrote:
> Hi,
>
> 2015-10-1 (Thu) 7:51:32 UTC+9 h_east:
>> Hi,
>>
>> 2015-10-1 (Thu) 7:11:19 UTC+9 Celes-Eternal:
>> > Hello,
>> >
>> >
>> > I have a problem with my vim since some times.
>> >
>> > I'm using compton + urxvt + vim with true transparency (that's
Hi,
2015-10-1 (Thu) 7:51:32 UTC+9 h_east:
> Hi,
>
> 2015-10-1 (Thu) 7:11:19 UTC+9 Celes-Eternal:
> > Hello,
> >
> >
> > I have a problem with my vim since some times.
> >
> > I'm using compton + urxvt + vim with true transparency (that's when the bug
> > occurs)
> >
> >
> > When i start vim
Hi,
2015-10-1 (Thu) 7:11:19 UTC+9 Celes-Eternal:
> Hello,
>
>
> I have a problem with my vim since some times.
>
> I'm using compton + urxvt + vim with true transparency (that's when the bug
> occurs)
>
>
> When i start vim (with file or not), i have this line which is added (buffer
> probl
Yasuhiro Matsumoto wrote:
> On Wednesday, September 30, 2015 at 9:25:54 AM UTC+9, Nobuhiro Takasaki wrote:
> > > Always using the position from g_cbNonTermcap seems strange.
> > > Should we not depend on the value of g_fTermcapMode?
> >
> > It was too simple. It is a failure.
> > I think that it
*bump*
--
--
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 message because you are subscribed to the Google Groups
"vim_dev" group.
T
tux. schrob am Freitag, 25. September 2015 um 01:20 Zeit:
> I tried to compile Vim with Racket (Make_mvc.mak) and Visual Studio
> 2010. However, it seems that somewhere the path is not properly
> escaped.
> Racket is installed to C:\Program Files (x86)\Racket, I set LIBRACKET
> to the correct ver
On Wed, 30 Sep 2015, Christian Brabandt wrote:
Can you reproduce it with the above command line I gave?
Oops, you're right, I should have tried that. And you're correct,
when invoked that way I don't get the message.
- Christian
--
"Help Microsoft stamp out Piracy. Give Linux to a F
On Mi, 30 Sep 2015, Christian J. Robinson wrote:
> On Wed, 30 Sep 2015, Christian Brabandt wrote:
> >On Mi, 30 Sep 2015, Christian Robinson wrote:
> >
> >>I get it immediately when the remote command is sent, before I
> >>actually switch to the gVim window.
> >>
> >>This is on Windows 7.
> >
> >Hm
On Wed, 30 Sep 2015, Christian Brabandt wrote:
Hi Christian!
On Mi, 30 Sep 2015, Christian Robinson wrote:
I get it immediately when the remote command is sent, before I
actually switch to the gVim window.
This is on Windows 7.
Hm, interesting. I don't see this with my usual vimrc setting,
Hi Christian!
On Mi, 30 Sep 2015, Christian Robinson wrote:
> > On Sep 30, 2015, at 2:01 AM, Christian Brabandt
> > wrote:
> >> On Fr, 04 Sep 2015, Christian J. Robinson wrote:
> >>
> >> If I set up the following autocmd:
> >>
> >>:autocmd FocusGained * :echomsg "here"
> >>
> >> Then from
> On Sep 30, 2015, at 2:01 AM, Christian Brabandt wrote:
>
> Hi Christian!
>
>> On Fr, 04 Sep 2015, Christian J. Robinson wrote:
>>
>>
>> If I set up the following autocmd:
>>
>>:autocmd FocusGained * :echomsg "here"
>>
>> Then from a command-line window do:
>>
>>vim --remote-send "
On Tuesday, September 29, 2015 at 4:18:00 PM UTC-5, Justin M. Keyes wrote:
> You can already do this with:
>
> echo filter(copy(v:oldfiles), 'v:val =~ "foo"')
>
>
>
> I wish that people focused on exposing general mechanisms in Vim instead of
> adding petty special cases to random features lik
Hi Christian!
On Fr, 04 Sep 2015, Christian J. Robinson wrote:
>
> If I set up the following autocmd:
>
> :autocmd FocusGained * :echomsg "here"
>
> Then from a command-line window do:
>
> vim --remote-send ":tabnew"
>
> I get the "here" message. This happens with a number of other
13 matches
Mail list logo
