Hi, this topic has been dead for ages already but I ended up finding it by
accident due to a related discussion happening elsewhere.
So, I'd just like to share NeoVim as a pretty good solution for this, since it
was born with embedding in mind, and has been used with success in GUI
implementati
s/an special case/restriction/
2016-01-15 13:52 GMT-02:00 Francisco Lopes :
> This relaxing of rules would mean adding an special case to that bullet.
> Like:
>
>- Enter completion, that *actually* adds text.
>
> —
> Reply to this email directly or view it on GitHub
>
Hi,
2016-01-15 7:14 GMT-02:00 h_east :
> Hi,
>
> 2016-1-15(Fri) 18:10:10 UTC+9 h_east:
> > Hi Francisco, Chris.B and list,
> >
> > 2016-1-15(Fri) 6:39:07 UTC+9 Francisco Lopes:
> > > @chrisbra I've just checked that it reproduces like I described. Will
&g
Em sexta-feira, 27 de março de 2015 11:16:17 UTC-3, Francisco Lopes escreveu:
> Em sexta-feira, 27 de março de 2015 10:52:22 UTC-3, Kazunobu Kuriyama
> escreveu:
> > On Mar 27, 2015, at 13:53, Francisco Lopes
> > wrote:
> >
> > > Em sexta-feira, 27 de março
Em sexta-feira, 27 de março de 2015 10:52:22 UTC-3, Kazunobu Kuriyama escreveu:
> On Mar 27, 2015, at 13:53, Francisco Lopes
> wrote:
>
> > Em sexta-feira, 27 de março de 2015 01:51:05 UTC-3, Francisco Lopes
> > escreveu:
> >> Em sexta-feira, 27 de março de
Em sexta-feira, 27 de março de 2015 01:51:05 UTC-3, Francisco Lopes escreveu:
> Em sexta-feira, 27 de março de 2015 01:44:37 UTC-3, Francisco Lopes escreveu:
> > Em quinta-feira, 26 de março de 2015 00:10:51 UTC-3, Kazunobu Kuriyama
> > escreveu:
> > > On Mar 26, 2015,
Em sexta-feira, 27 de março de 2015 01:44:37 UTC-3, Francisco Lopes escreveu:
> Em quinta-feira, 26 de março de 2015 00:10:51 UTC-3, Kazunobu Kuriyama
> escreveu:
> > On Mar 26, 2015, at 1:36, Francisco Lopes
> > wrote:
> >
> > > Em segunda-feira, 23 de março
Em quinta-feira, 26 de março de 2015 00:10:51 UTC-3, Kazunobu Kuriyama
escreveu:
> On Mar 26, 2015, at 1:36, Francisco Lopes
> wrote:
>
> > Em segunda-feira, 23 de março de 2015 04:19:30 UTC-3, Kazunobu Kuriyama
> > escreveu:
> >> Hi list,
> >>
>
Em segunda-feira, 23 de março de 2015 04:19:30 UTC-3, Kazunobu Kuriyama
escreveu:
> Hi list,
>
>
> The attached patch was written to address two issues on Vim build on Mac OS X
> with privately installed Python.
>
>
> (1) The current configure script uses the responses of the Python executab
se) is being considered as success by the test and
the first part of the if statement is always being executed, even if my python
version is 2.7.
I'm on OS X with zsh.
Regards,
Francisco Lopes
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type
Em quarta-feira, 12 de março de 2014 11h22min22s UTC-3, Francisco Lopes
escreveu:
> Em quarta-feira, 12 de março de 2014 11h14min04s UTC-3, Christ van Willegen
> escreveu:
>
> > On Wed, Mar 12, 2014 at 2:46 PM, Francisco Lopes
>
> >
>
> > wrote:
>
>
Em quarta-feira, 12 de março de 2014 11h14min04s UTC-3, Christ van Willegen
escreveu:
> On Wed, Mar 12, 2014 at 2:46 PM, Francisco Lopes
>
> wrote:
>
> > Does Vim do that trying to be smart? because it doesn't seem a behavior of
> > the plugin
>
>
&
hi guys I need some help, I'm tweaking a completion plugin and I don't know
whether the behavior I'm seeing is from Vim or from the plugin. Let's say I
have the cursor at
foo(|)
and I type bar which give the options
bar()
barvar
When I select bar() from the menu with , what I end up with is
fo
Em sexta-feira, 10 de janeiro de 2014 18h31min23s UTC-2, Francisco Lopes
escreveu:
> ^^^
erm, any comments?
--
--
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:
^^^
--
--
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 u
The problem: Vim flickers (in my case subtly) while typing on buffer A when
there's a hidden edited and unsaved buffer B.
Cause: Have plugin that access the buffer options (e.g. in python:
.options[ ]) triggered by changing the
buffer (typing, etc).
Debugging I found the root cause:
"About the
Bram Moolenaar wrote:
>
> It appears the problem is that pum_first and pum_height are out of sync.
>
> pum_first is corrected only after the code that causes a redraw for the
>
> preview window.
>
>
>
> Please verify the patch below also fixes the crash. It's better in the
>
> sense that it
some more info originally from
https://github.com/Valloric/YouCompleteMe/issues/618#issuecomment-27265698:
@Valloric my real advice is that, they should run it,
as soon as this get fixed upstream,
this is a plain bug as can be checked in the vim thread.
I've debugged it a bit more and got more
Bram Moolenaar wrote:
> Francisco Lopes wrote:
>
>
>
> > I've applied the following patch to pum_redraw function to avoid rare
> > segfaults I was suffering.
>
> >
>
> > diff -r 92c9748e0ccb src/popupmnu.c
>
> > --- a/src/popupmnu.
specifically while debugging, pum_first was 1 making idx beyond arrays bounds.
--
--
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 mes
I've applied the following patch to pum_redraw function to avoid rare segfaults
I was suffering.
diff -r 92c9748e0ccb src/popupmnu.c
--- a/src/popupmnu.cSun Oct 06 17:46:56 2013 +0200
+++ b/src/popupmnu.cMon Oct 21 12:29:31 2013 -0200
@@ -295,6 +295,8 @@
for (i = 0; i < pum_height; +
On 14/09/2012, at 01:54, ZyX wrote:
> If I were doing this thing I would change function references to have type
>
>typedef struct funcref_S funcref_T;
>struct funcref_S {
>void *fv_data;
>funcdef_T *fv_func_def;
>intfv_refcount;
>intfv
https://groups.google.com/d/msg/vim_dev/F2z5I9tayKY/UNGZ1-kSvq4J
Regards
---
Francisco Lopes
--
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
For continued discussion see
https://groups.google.com/d/topic/vim_dev/kS8BkiqqwyY/discussion.
This topic is closed.
--
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/mail
mplementing the functions, the hard
part will be to define and implement
what the vim_get callback will return.
Any comments please?
Regards
---
Francisco Lopes
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are
gt;
> Conversion between VIM types and libffi types is necessary.
>
>
> In this embryonary stage (I know nothing about VIM internals),
> any suggestions? criticisms?
>
> Regards
> ---
> Francisco Lopes
Changed my mind a bit after some looking around at VIM sources.
Hi, this topic has already been discussed in 2008, and became dead.
Time to make it born again.
I was talking with Bram about the limitations of libcall: the load/unload
of a library at every invocation and the arguments limitations.
I talked about a small change on it to avoid the load/unload pr
eclare prototypes for
native functions.
Conversion between VIM types and libffi types is necessary.
libffi is MIT licensed and is adopted in several projects.
In this embryonary stage (I know nothing about VIM internals),
any suggestions? criticisms?
Regards
---
Francisco Lopes
--
You re
28 matches
Mail list logo
