Loading ...
Sorry, an error occurred while loading the content.
 

Re: added TextDeleted and TextYanked events

Expand Messages
  • Philippe Vaucher
    ... 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
    Message 1 of 34 , Mar 7 5:10 AM
      > 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.
      For more information, visit http://www.vim.org/maillist.php
    • Bram Moolenaar
      ... Yes, in a quite clumsy way. Especially the way arguments are passed to the commands being executed. And how state needs to be saved and restored. I have
      Message 34 of 34 , Mar 6 12:09 PM
        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/neovim/pull/4304
        > > >
        > > > Hehe, I just noticed that!
        > > >
        > > > Thanks :-)
        > > >
        > > > Sooooo 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 wink*
        > >
        > > I don't recall anyone asking for this feature in the past six years.
        > > If there was a discussion about how this is useful for more than one
        > > user, it would have been moved up in the todo list.
        > >
        > > Including just every patch available leads to a mess. Also,
        > > autocommands are a clumsy mechanism, thus I hesitate to add more of it.
        > >
        > > I had a brief look at the comments, and it appears the functionality
        > > would be better done with some kind of callback.
        > >
        >
        > Aren't autocmds basically Vim's way of doing callbacks?

        Yes, in a quite clumsy way. Especially the way arguments are passed to
        the commands being executed. And how state needs to be saved and
        restored. I have often wondered what would be a proper solution, but I
        don't have a concrete proposal.

        Another problem with autocommands is that the caller can do anything.
        Such as a BufReadPre could open a new window. Thus the Vim code
        triggering the autocommand has to be extremely careful about assuming
        the current state. And need to abort the command sometimes. Anyway,
        using a callback mechanism probably won't solve that. But the point
        where it is called could help.

        > 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.

        Each problem usually has several ways of dealing with it. Just taking
        the first solution that comes to mind is often wrong, it may lead to the
        need for another solution later, when it turns out that the first
        solution doesn't cover all use cases.

        --
        hundred-and-one symptoms of being an internet addict:
        71. You wonder how people walk

        /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
        /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
        \\\ an exciting new programming language -- http://www.Zimbu.org ///
        \\\ help me help AIDS victims -- http://ICCF-Holland.org ///

        --
        --
        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+unsubscribe@....
        For more options, visit https://groups.google.com/d/optout.
      Your message has been successfully submitted and would be delivered to recipients shortly.