Re: [vim/vim] can't close a popup terminal window when its buffer has been replaced by "term_start()" (#5744)

2020-05-15 Fir de Conversatie M Kelly
Hi,

I noticed the fzf.vim issue is resolved.
Thank you for this!

-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/148b5d75-ed9b-46da-8d01-f924294e6827%40googlegroups.com.


Re: Since recent commit getting E863: Not allowed for a terminal in a popup window

2020-05-15 Fir de Conversatie M Kelly
Hi,

This issue is resolved in the latest fzf.vim 
commit d631c76e8d2dd18876a09d2c0919ece1a42a8721.
Thank you to those involved!

-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/5e3e146d-f19f-4525-a35d-71253320d2bb%40googlegroups.com.


Re: Since recent commit getting E863: Not allowed for a terminal in a popup window

2020-05-14 Fir de Conversatie M Kelly
Hi again,

I mean you said usage of a terminal in a popup has changed - and I can say 
this code calls term_start from a popup :-)
But I'm not yet clear on what is wrong with it.  I'll keep digging.

thx,
-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/93a80086-6204-4a48-afa3-9ba33f78760b%40googlegroups.com.


Re: Since recent commit getting E863: Not allowed for a terminal in a popup window

2020-05-14 Fir de Conversatie M Kelly
Hi,

I think it has to do with calling term_start from within a popup.
I'll keep digging.

-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/43e9b912-a238-4f38-8b3a-84dfcda6b827%40googlegroups.com.


Re: Since recent commit getting E863: Not allowed for a terminal in a popup window

2020-05-14 Fir de Conversatie M Kelly
Hi,

Someone else submitted an issue to fzf.vim for this 
https://github.com/junegunn/fzf.vim/issues/1028

I'll try to find the exact cmd that throws this later today.

thx!,
-m

On Wednesday, May 13, 2020 at 4:45:09 PM UTC-4, Bram Moolenaar wrote:
>
>
> > I think this is: 
> > 
> >   let fzf.buf = term_start([&shell, &shellcmdflag, command], 
> {'curwin': 
> > 1, 'exit_cb': function(fzf.on_exit)}) 
> > 
> > ... trying to see what is in fzf.on_exit that might matter ? 
>
> Please find out what the command is where the error is triggered. 
> The usage of a terminal in a popup window was made more strict to fix a 
> bug.  To see whether valid cases now run into this error we need to see 
> where exactly this happens. 
>
 

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/ae5a3831-07e0-46f1-b2dc-081d248f0a18%40googlegroups.com.


Re: [vim/vim] can't close a popup terminal window when its buffer has been replaced by "term_start()" (#5744)

2020-05-13 Fir de Conversatie M Kelly
Hi,

I raised a similar question in another thread.

>> All the examples raise E863, probably because of 5aed0cc.

Exactly, I find fzf+popup now has an issue since this commit.
Do we need to change fzf.vim to get around this ?

thx,
-m

>

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/317c0c3d-9031-48a5-844b-68a98de51e39%40googlegroups.com.


Re: Since recent commit getting E863: Not allowed for a terminal in a popup window

2020-05-13 Fir de Conversatie M Kelly
Hi,

Should I open a github issue for this ?
Seems there is similar info recently from lacygoill but not sure that is 
fully resolved ?

thx,
-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/4fe34376-27d5-4398-b77b-8897de2bcfce%40googlegroups.com.


Re: Since recent commit getting E863: Not allowed for a terminal in a popup window

2020-05-13 Fir de Conversatie M Kelly
Hi,

I think this is:

  let fzf.buf = term_start([&shell, &shellcmdflag, command], {'curwin': 
1, 'exit_cb': function(fzf.on_exit)})

... trying to see what is in fzf.on_exit that might matter ?

thx,
-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/616655cd-e501-4e23-985e-5bf0159fe522%40googlegroups.com.


Since recent commit getting E863: Not allowed for a terminal in a popup window

2020-05-13 Fir de Conversatie M Kelly
Hi,

Perhaps this was mentioned before ?

Since commit 5aed0ccb965dbad4b60f4c77c9c4455a9379e73c 
I am unable to use ag+fzf in a popup.  I get this error:

Error detected while processing function 
fzf#vim#grep[24]..86_fzf[18]..fzf#run[58]..66_execute_term:
line   70:
E863: Not allowed for a terminal in a popup window

before this commit it worked well.
I have the latest fzf and fzf.vim - do I need to submit a change to match 
latest vim api ?
Not sure yet what I need to change tho.

thx,
-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/89a68570-d0e1-43e7-a82e-ba0e1cc2b5a6%40googlegroups.com.


Re: Patch 8.2.0684

2020-05-03 Fir de Conversatie M Kelly
Hi,

No prob, just wanted to lyk.
Thank you always for your work and to all in the vim community

-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/7bbc0118-8b83-462f-824b-47280e4cc447%40googlegroups.com.


Re: Patch 8.2.0684

2020-05-03 Fir de Conversatie M Kelly
Hi,

Latest gives a compile error -

vim9compile.c: In function ‘delete_def_function_contents’:
vim9compile.c:6637:14: error: ‘dfunc_T’ {aka ‘struct dfunc_S’} has no 
member named ‘df_funcstack’
 6637 | if (dfunc->df_funcstack != NULL)

In on Linux 18.04 + hwe gcc 9.3
I'll start digging.

thx,
-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/c74a5788-4c87-4795-aa3c-1d468f6be013%40googlegroups.com.


Re: E216: No such group or event: filetypedetect *

2019-12-24 Fir de Conversatie M Kelly
Hi,

I apologize, I meant ftoff.vim, not ftopen.vim.

I found my error using v:throwpoint and effort.
I was not reading in all data from a command run from a job.
Once I corrected that I no longer see these errors.

thx and take care,
-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/a1549d61-7944-45cf-a3c5-1c9aa80d8abb%40googlegroups.com.


E216: No such group or event: filetypedetect *

2019-12-21 Fir de Conversatie M Kelly
Hi,

I sometimes get this -

E216: No such group or event: filetypedetect *

after an lopen from a plugin.  If I remove/comment out the -

silent! au! filetypedetect *

from /usr/local/share/vim/vim82/ftopen.vim

then after many attempts so far I do not see this exception.

Anyone know 1) how I can debug to see who is throwing this ? and 2). does 
this mean the silent! isn't working, or should it just have a try/catch 
around it ?
Or perhaps just add a bogus autogroup so the au! doesn't throw ?
Any suggestions ?

thx for everything vim,
-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/5d59d70e-459e-404a-ac20-336e91e602e8%40googlegroups.com.


Re: 1531 build error ? - unknown type name Clipboard_T

2019-06-14 Fir de Conversatie M Kelly
Hi,

ok, 1532 fixes it.

thanks!
-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/39071f01-b7ac-434f-a4e1-5979409bf76b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


1531 build error ? - unknown type name Clipboard_T

2019-06-14 Fir de Conversatie M Kelly
Hi,

When building commit 0554fa478 (1531) I now get:

In file included from proto.h:39:0,
 from vim.h:2084,
 from arabic.c:31:
proto/os_unix.pro:82:30: error: unknown type name ‘Clipboard_T’
 int clip_xterm_own_selection(Clipboard_T *cbd);

build worked ok just before this commit.

Any ideas ?  I will go dig and provide config info.

thx,
-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/7dfa91fe-629b-49e1-91f4-116b1d49f945%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: build error since today (invalid UTF-8)

2019-06-07 Fir de Conversatie M Kelly
Hi,

Thank you all so much.  8.1.1487 builds fine :-)

-mark

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/706fc908-98d9-416a-8da9-abffa2124b3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: build error since today (invalid UTF-8)

2019-06-06 Fir de Conversatie M Kelly
Hi,

I see someone else posted earlier about the same issue.
But those suggestions and also latest git rev do not resolve issue for me.

-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/e6ab3364-4955-4907-a5e2-bcc33a848c8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: build error since today (invalid UTF-8)

2019-06-06 Fir de Conversatie M Kelly
git rev is latest master since a few minutes ago:

  * 2019-06-06 773a97c25 (HEAD -> master, origin/master, origin/HEAD) Update 
runtime files - Add typescript syntax and indent. (Bram Moolenaar)

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/8bc0fb56-58be-4948-9bb3-14c80e85bb97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


build error since today (invalid UTF-8)

2019-06-06 Fir de Conversatie M Kelly
Hi,

I typically build daily and its been fine until today -

msgfmt --desktop -d . --template gvim.desktop.in -o tmp_gvim.desktop
rm -f LINGUAS
if command -v desktop-file-validate; then desktop-file-validate 
tmp_gvim.desktop; fi
/usr/bin/desktop-file-validate
tmp_gvim.desktop: warning: file contains lines that are not UTF-8 encoded. 
There is no guarantee the validator will correctly work.
[Invalid UTF-8] tmp_gvim.desktop: error: value 
"\xe0\xac\xaa\xe0\xac\xbe\xe0\xac\xa0\xe0\xad\x8d\xe0\xac\xaf 
\xe0\xac\xab\xe0\xac\xbe\xe0\xac\x87\xe0\xac\xb2\xe0\xac\x97\xe0\xad\x81\xe0\xac\xa1\xe0\xac\xbc\xe0\xac\xbf\xe0\xac\x95\xe0\xad\x81
 
\xe0\xac\xb8\xe0\xac\xae\xe0\xad\x8d\xe0\xac\xaa\xe0\xac\xbe\xe0\xac\xa6\xe0\xac\xa8
 \xe0\xac\x95\xe0\xac\xb0\xe0\xac\xa8\xe0\xad\x8d\xe0\xac\xa4\xe0\xad" for 
locale string key "Comment[or]" in group "Desktop Entry" contains y characters, 
locale string values should be encoded in UTF-8

I'm on 
linux 4.15.0-51-generic
gcc --version
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609
msgfmt (GNU gettext-tools) 0.19.7
GDM_LANG=en_US
LANG=en_US.UTF-8
LANGUAGE=en_US

Any ideas ?

thx,
-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/d85ac218-ad36-43a7-a2ed-f2c2f13bef8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: ex_docmd.c build error RESTRICT undeclared

2019-02-08 Fir de Conversatie M Kelly
OK, I see some others posted same issue in other threads.

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


ex_docmd.c build error RESTRICT undeclared

2019-02-08 Fir de Conversatie M Kelly
Hi,

Have a build problem this morning after latest pull:

ex_docmd.c: In function ‘do_one_cmd’:
ex_docmd.c:2015:36: error: ‘RESTRICT’ undeclared (first use in this function)
  if (restricted != 0 && (ea.argt & RESTRICT))
^
Any ideas ?

thx,
-mark

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How about a release?

2018-03-15 Fir de Conversatie M Kelly
Hi,

Thx.  Excited to try it out, I get this -

Error detected while processing function 17_StartDebug:
line   73:
Your gdb does not support the Machine Interface feature

But cannot seem to find info on the web about what this means/how to make 
progress.  Any quick suggestion ?
Do I need to build gdb with some non-standard configure options ?

GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
This GDB was configured as follows:
   configure --host=x86_64-linux-gnu --target=x86_64-linux-gnu
 --with-auto-load-dir=$debugdir:$datadir/auto-load
 --with-auto-load-safe-path=$debugdir:$datadir/auto-load
 --with-expat
 --with-gdb-datadir=/usr/share/gdb (relocatable)
 --with-jit-reader-dir=/usr/lib/gdb (relocatable)
 --without-libunwind-ia64
 --with-lzma
 --with-python=/usr (relocatable)
 --without-guile
 --with-separate-debug-dir=/usr/lib/debug (relocatable)
 --with-system-gdbinit=/etc/gdb/gdbinit
 --with-babeltrace

-m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How about a release?

2018-03-13 Fir de Conversatie M Kelly
Hi,

Where can I learn more about the debugger plugin ?

thx,
mark

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


jump list save ques

2018-01-02 Fir de Conversatie M Kelly
Hi,

How about adding a j# to the viminfo for how many jumps to save ?
Even if I clearjumps it seems the .viminfo file still has 100 everytime.
Q: is there a way to only save so many jumps to the jumplist ?
thx as always,
-mark

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: build error: unknown type name BalloonEval

2017-11-19 Fir de Conversatie M Kelly
On Sunday, November 19, 2017 at 10:07:51 AM UTC-5, M Kelly wrote:
> Hi,
> 
> Apologies if this was already posted -
> 
> I have a build error with latest master:
> 
> In file included from vim.h:1816:0,
>  from buffer.c:28:
> structs.h:3126:5: error: unknown type name ‘BalloonEval’
>  BalloonEval *tip;  /* tooltip for this menu item */
> 
> thx,
> mark

I will add this is building on Ubuntu 16.04 HWE with gcc

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


build error: unknown type name BalloonEval

2017-11-19 Fir de Conversatie M Kelly
Hi,

Apologies if this was already posted -

I have a build error with latest master:

In file included from vim.h:1816:0,
 from buffer.c:28:
structs.h:3126:5: error: unknown type name ‘BalloonEval’
 BalloonEval *tip;  /* tooltip for this menu item */

thx,
mark

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: No rule to make terminal.c

2017-09-19 Fir de Conversatie M Kelly
I think terminal.c was deleted in the latest version ??

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


rectangular (block) paste from clipboard ?

2017-08-02 Fir de Conversatie M Kelly
Hi,
Anyone know of a way to block paste from the external clipboard buffer ?
I can paste but its not block paste.
For example, I use tmux and block-copy selection to clipboard but cannot get 
this to block paste in vim.
thx,
m

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


v8.0.0765 build error

2017-07-25 Fir de Conversatie M Kelly
Hi,
Sorry if this is posted/solved already.
When building v8.0.0765 I get this error:

gui_x11.c: In function ‘gui_mch_get_color’:
gui_x11.c:2274:14: warning: unused variable ‘colormap’ [-Wunused-variable]
 Colormap colormap;
  ^
gui_x11.c:2273:17: warning: unused variable ‘available’ [-Wunused-variable]
 XColor  available;
 ^
gui_x11.c: In function ‘gui_mch_get_rgb_color’:
gui_x11.c:2300:5: error: ‘colormap’ undeclared (first use in this function)
 colormap = DefaultColormap(gui.dpy, DefaultScreen(gui.dpy));
 ^
gui_x11.c:2300:5: note: each undeclared identifier is reported only once for 
each function it appears in
gui_x11.c:2301:55: error: ‘available’ undeclared (first use in this function)
 if (XParseColor(gui.dpy, colormap, (char *)spec, &available) != 0

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Patch 8.0.0765

2017-07-25 Fir de Conversatie M Kelly
Hi,

I get a build error on ubuntu with gcc with v8.0.765:

gui_x11.c: In function ‘gui_mch_get_color’:
gui_x11.c:2274:14: warning: unused variable ‘colormap’ [-Wunused-variable]
 Colormap colormap;
  ^
gui_x11.c:2273:17: warning: unused variable ‘available’ [-Wunused-variable]
 XColor  available;
 ^
gui_x11.c: In function ‘gui_mch_get_rgb_color’:
gui_x11.c:2300:5: error: ‘colormap’ undeclared (first use in this function)
 colormap = DefaultColormap(gui.dpy, DefaultScreen(gui.dpy));
 ^
gui_x11.c:2300:5: note: each undeclared identifier is reported only once for 
each function it appears in
gui_x11.c:2301:55: error: ‘available’ undeclared (first use in this function)
 if (XParseColor(gui.dpy, colormap, (char *)spec, &available) != 0

-- 
-- 
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.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.