Ben Fritz wrote:
> On Saturday, March 4, 2017 at 6:47:33 AM UTC-6, Bram Moolenaar wrote:
> > Philippe Vaucher wrote:
> >
> > > On Monday, February 29, 2016 at 4:13:31 PM UTC+1, Björn Linse wrote:
> > > > For the record, a version of this was merged into neovim:
> > > > https://github.com/neovim/
>
> ...
> I don't personally feel the need for one, but I know many people would
> like a "yank ring" style of plugin or other sort of clipboard management
> which this patch would enable.
>
>
FYI:
YankRing.vim : Maintains a history of previous yanks, changes and deletes
http://www.vim.org/scri
On Saturday, March 4, 2017 at 6:47:33 AM UTC-6, Bram Moolenaar wrote:
> Philippe Vaucher wrote:
>
> > On Monday, February 29, 2016 at 4:13:31 PM UTC+1, Björn Linse wrote:
> > > For the record, a version of this was merged into neovim:
> > > https://github.com/neovim/neovim/pull/4304
> >
> > Hehe,
Philippe Vaucher wrote:
> On Monday, February 29, 2016 at 4:13:31 PM UTC+1, Björn Linse wrote:
> > For the record, a version of this was merged into neovim:
> > https://github.com/neovim/neovim/pull/4304
>
> Hehe, I just noticed that!
>
> Thanks :-)
>
> So reguarding vim, 6 years ago this
Hi Philippe!
On Fr, 03 Mär 2017, Philippe Vaucher wrote:
> So reguarding vim, 6 years ago this was put in the TODO in the "As
> soon as possible" section. Today this patch still sits there...
> maybe... just maybe... is there some kind of problems with the patch
> submission process? *wink wi
On Monday, February 29, 2016 at 4:13:31 PM UTC+1, Björn Linse wrote:
> For the record, a version of this was merged into neovim:
> https://github.com/neovim/neovim/pull/4304
Hehe, I just noticed that!
Thanks :-)
So reguarding vim, 6 years ago this was put in the TODO in the "As soon as
poss
For the record, a version of this was merged into neovim:
https://github.com/neovim/neovim/pull/4304
--
--
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
---
Yawn... More than 2 years for a trivial patch like this.
https://github.com/Silex/vim/commit/de53ab72c89affa8ba77536ed8920751c037d127
Honestly, I'm disapointed. It's been a while I don't use vim anymore but I
think vim deserves a more reactive development model than the current one.
Bram: I thi
> It's in the todo list. That list is very long, and bug fixes have
> priority. Might take a while.
Bump :)
Philippe
--
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/ma
On Mar 18, 2012, at 6:16 PM, "Benjamin R. Haskell" wrote:
> On Sun, 18 Mar 2012, David Fishburn wrote:
>
>> I will also add this to the YankRing plugin (script #1234).
>>
>> I don't se the patch # to put a conditional check in for it.
>
> It hasn't been applied yet, but you shouldn't check
On Sun, 18 Mar 2012, David Fishburn wrote:
I will also add this to the YankRing plugin (script #1234).
I don't se the patch # to put a conditional check in for it.
It hasn't been applied yet, but you shouldn't check by patch # anyway.
exists() can detect whether an autocommand for a particul
I will also add this to the YankRing plugin (script #1234).
I don't se the patch # to put a conditional check in for it.
Could someone let me know.
Thanks.
--
David Fishburn
On Mar 16, 2012, at 1:28 AM, Philippe Vaucher
wrote:
>> Do you maybe have a yankring-like plugin that makes use
> Do you maybe have a yankring-like plugin that makes use of the feature?
> That could help people try it out in real-world scenarios.
Yes there is, see https://github.com/the-isz/MinYankRing.vim/tree/events
Philippe
--
You received this message from the "vim_dev" maillist.
Do not top-post! Typ
Hi,
Do you maybe have a yankring-like plugin that makes use of the feature?
That could help people try it out in real-world scenarios.
Jan
--
-[ OpenPGP key ID: 00A0FD5F ]-
Technological progress has merely provided us with more efficient means for
going backwards.
> Which might be out of date. The latest version is always available at:
> https://vim.googlecode.com/hg/runtime/doc/todo.txt
Thanks.
Philippe
--
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, visi
Hello
Excerpt from Jürgen Krämer:
-- --
>>> It's in the todo list. That list is very long, and bug fixes have
>>> priority. Might take a while.
>>
>> How long is that list? It's been more than 6 months now :/
>
> :help todo
Which might be out of date. The latest version is always availabl
Hi,
Philippe Vaucher wrote:
>> It's in the todo list. That list is very long, and bug fixes have
>> priority. Might take a while.
>
> How long is that list? It's been more than 6 months now :/
:help todo
Regards,
Jürgen
--
Sometimes I think the surest sign that intelligent life exists el
> It's in the todo list. That list is very long, and bug fixes have
> priority. Might take a while.
How long is that list? It's been more than 6 months now :/
Philippe
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to
Philippe Vaucher wrote:
> Bram: this is just a message to bump this issue, to avoid that you
> forget about it.
It's in the todo list. That list is very long, and bug fixes have
priority. Might take a while.
--
hundred-and-one symptoms of being an internet addict:
271. You collect hilarious
Bram: this is just a message to bump this issue, to avoid that you
forget about it.
Thanks,
Philippe
--
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
> I need to have a closer look. Bugs usually have a higher priority than
> new features.
Hum, it's been a while now... should I create a ticket on
http://code.google.com/p/vim/issues/list so it's not forgotten?
In the meantime, we did some tests about potential problems with this
new feature:
t
Philippe Vaucher wrote:
> So, Bram is that ok? Do you want the patch on another medium? Are
> there issues I didn't address?
I need to have a closer look. Bugs usually have a higher priority than
new features.
--
hundred-and-one symptoms of being an internet addict:
131. You challenge authori
So, Bram is that ok? Do you want the patch on another medium? Are
there issues I didn't address?
Thanks,
Philippe
--
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
Ok we did some tests and now everything works as it should.
For a better view of the patch, see
https://github.com/Silex/vim/commit/de0dd46e90fd7c6587492d3d7f8878d9f57f42f2
We tested with `vim -u NONE -U NONE --noplugin test.vim`, followed
by :so % and
test.vim being:
let s:count = 0
fu
Ah, the_isz found the first bug already :)
When yanking/deleting with a visual range, the autocmd is triggered
twice.
I'll fix it and report.
--
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, visi
> > > No because every delete/yank use the " register even if a register was
> > > explicitely specified. As a matter of completeness maybe it'd be nice
> > > to know which register was intended yes but it's the first time I
> > > fiddle with vim's source (with some pain) so I'm not too sure how mu
On May 24, 6:14 am, Bram Moolenaar wrote:
> Philippe Vaucher wrote:
> > > Don't you need to let the commands know what register text was yanked
> > > into?
>
> > No because every delete/yank use the " register even if a register was
> > explicitely specified. As a matter of completeness maybe it
Philippe Vaucher wrote:
> > I think they should be called TextDeletePost and TextYankPost to be
> > consistent.
>
> Ok, I can do that.
>
> > Try doing something weird in the autocommand, such as "help" and then
> > deleting something.
> > You probably need to disallow lots of things to avoid br
Philippe Vaucher wrote:
> > > No because every delete/yank use the " register even if a register was
> > > explicitely specified. As a matter of completeness maybe it'd be nice
> > > to know which register was intended yes but it's the first time I
> > > fiddle with vim's source (with some pain)
> > No because every delete/yank use the " register even if a register was
> > explicitely specified. As a matter of completeness maybe it'd be nice
> > to know which register was intended yes but it's the first time I
> > fiddle with vim's source (with some pain) so I'm not too sure how much
> > w
Reply to message «Re: added TextDeleted and TextYanked events»,
sent 01:00:50 24 May 2011, Tuesday
by Philippe Vaucher:
> No because every delete/yank use the " register even if a register was
> explicitely specified. As a matter of completeness maybe it'd be nice
> to know
> I think they should be called TextDeletePost and TextYankPost to be
> consistent.
Ok, I can do that.
> Try doing something weird in the autocommand, such as "help" and then
> deleting something.
> You probably need to disallow lots of things to avoid breaking stuff
> (and perhaps even crashing
Philippe Vaucher wrote:
> I added TextDelete and TextYank events.
>
> This necessity appeared because of the small delete register getting
> in our way in order to implement a proper killring. There exists a
> plugin that tries to address it (YankRing.vim) but then other things
> break down, lik
st it with:
autocmd TextDeleted * echom 'Deleted: ' . @"
autocmd TextYanked * echom 'Yanked: ' . @"
Tell me what you think.
Philippe
>From f82fa9037bf6bd2013742e9502ffcdea903e8401 Mon Sep 17 00:00:00 2001
From: Philippe Vaucher
Date: Mon, 23 May 2011 17:08:51 +0
34 matches
Mail list logo
