On Sunday, May 29, 2016 at 4:44:12 PM UTC+3, Bram Moolenaar wrote:
> Ramel Eshed wrote:
>
> > In every Vim plugin that I've used (which are not too many though)
> > there was a protection on the general-purpose buffers (done by setting
> > and resetting 'modifiable').
> > The concern, I guess, is
On Monday, May 30, 2016 at 5:11:57 AM UTC+3, yega...@gmail.com wrote:
> Hi,
>
> On Sat, May 7, 2016 at 2:42 PM, Ramel Eshed wrote:
> > Hi All,
> >
> > Thanks to Bram and his recent work on channels, I have a preliminary
> > version of an asynchronous grep plugin which lets you work with the
> > a
On Sunday, May 29, 2016 at 4:44:12 PM UTC+3, Bram Moolenaar wrote:
> Ramel Eshed wrote:
>
> > I tried the patch from shougo's thread and it solved my problem. thanks!
>
> So the current Vim works for you?
Yes.
>
> > There is another (minor) issue I noticed; Because I had problems with
> > the cl
Hi,
On Sat, May 7, 2016 at 2:42 PM, Ramel Eshed wrote:
> Hi All,
>
> Thanks to Bram and his recent work on channels, I have a preliminary
> version of an asynchronous grep plugin which lets you work with the
> available results while grep is still running. I would like to take
> advantage of this
Hi,
On Sun, May 29, 2016 at 12:59 PM, 'Guyzmo' via vim_dev
wrote:
> Hi,
>
> I couldn’t resist, so please forgive the shameless self-promotion ☺
>
> I have recently coded a little tool I called git-repo, that you can find
> on pypi (pip install git-repo), that simplifies the process:
>
> On Sat, M
Benjamin Fritz wrote:
> I have a mapping that executes the :cnext command (or another command based
> on context):
>
> " map and to jump between locations in a quickfix list, or
> " differences if in window in diff mode
> if v:version >= 700
> nnoremap NextThingJump()
> nnoremapPre
Hi
I noticed an item in todo.txt which has been fixed already
months ago in Vim-7.4.1640:
=== BEGIN QUOTE ===
Using freed memory in quickfix code. (Dominique, 2016 Mar 21)
=== END QUOTE ===
Regards
Dominique
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type yo
Hi,
I could'nt resist, so please forgive the shameless self-promotion ☺
I have recently coded a little tool I called git-repo, that you can find
on pypi (pip install git-repo), that simplifies the process:
On Sat, May 28, 2016 at 12:19:21PM -0700, Yegappan Lakshmanan wrote:
> Fork the Vim reposi
Hi Bram,
On Sun, May 29, 2016 at 10:52 AM, Bram Moolenaar wrote:
>
> Yegappan Lakshmanan wrote:
>
>> >> To use a script local function as a job callback function, it looks like
>> >> you need to use function('s:') to generate a function
>> >> reference. Is it possible to simply use the 's:functio
Yegappan Lakshmanan wrote:
> >> To use a script local function as a job callback function, it looks like
> >> you need to use function('s:') to generate a function
> >> reference. Is it possible to simply use the 's:function_name' string?
> >
> > That doesn't work, because the string doesn't know
Hi Bram,
On Sun, May 29, 2016 at 9:52 AM, Bram Moolenaar wrote:
>
> Yegappan Lakshmanan wrote:
>
>> To use a script local function as a job callback function, it looks like
>> you need to use function('s:') to generate a function
>> reference. Is it possible to simply use the 's:function_name' st
Yegappan Lakshmanan wrote:
> To use a script local function as a job callback function, it looks like
> you need to use function('s:') to generate a function
> reference. Is it possible to simply use the 's:function_name' string?
That doesn't work, because the string doesn't know what script the
Hi,
To use a script local function as a job callback function, it looks like
you need to use function('s:') to generate a function
reference. Is it possible to simply use the 's:function_name' string?
Using the function name (as a string) as a callback is supported
for global functions.
- Yegapp
Patch 7.4.1859
Problem:Cannot use a function reference for "exit_cb".
Solution: Use get_callback(). (Yegappan Lakshmanan)
Files: src/channel.c, src/structs.h
*** ../vim-7.4.1858/src/channel.c 2016-05-29 16:24:45.949320300 +0200
--- src/channel.c 2016-05-29 16:39:22.6693082
Patch 7.4.1858
Problem:When a channel writes to a buffer it doesn't find a buffer by the
short name but re-uses it anyway.
Solution: Find buffer also by the short name.
Files: src/channel.c, src/buffer.c, src/vim.h
*** ../vim-7.4.1857/src/channel.c 2016-05-29 16:16:3
Patch 7.4.1857
Problem:When a channel appends to a buffer that is 'nomodifiable' there is
an error but appending is done anyway.
Solution: Add the 'modifiable' option. Refuse to write to a 'nomodifiable'
when the value is 1.
Files: src/structs.h, src/channel.c,
Ramel Eshed wrote:
> In every Vim plugin that I've used (which are not too many though)
> there was a protection on the general-purpose buffers (done by setting
> and resetting 'modifiable').
> The concern, I guess, is not to prevent the user from changing the
> buffer deliberately rather then to
Ramel Eshed wrote:
> I tried the patch from shougo's thread and it solved my problem. thanks!
So the current Vim works for you?
> There is another (minor) issue I noticed; Because I had problems with
> the close_cb (I got out-callbacks after it was called) I started a
> timer to 200ms so I'll b
18 matches
Mail list logo
