On Fri, Jan 16, 2015 at 2:56 PM, Christian Brabandt <cblists@256bit.org> wrote:
Sorry I didn't get back to you sooner, but it took a while to narrow it down. It's this:
tabdo windo echo 'hi'
Basically, execute a command in all tabs and windows. The command doesn't matter (I tried a few different commands, including those that don't echo anything to eliminate :echo as the culprit). Everything works just fine until the first time this tabdo and windo combination is executed and then subsequent operations no longer affect the "* register. (Yes, 'clipboard' is set to unnamed both before and immediately after the command--didn't get modified and echoes my _vimrc as the last place from which it was set.)
Simply executing :windo echo 'hi' doesn't do it, nor does :tabdo echo 'hi'. It's got to be both tabdo and windo in the same operation.
(My previous diagnosis that it works the first time only was a misinterpretation of this symptom.)
The interesting thing is that I only have one buffer open, so all three of tabdo, windo and tabdo windo actually only execute once.
Thank you,
Salman
Hi Salman!
Can anybody else reproduce this? Salman, can you try to find out, which
On Fr, 16 Jan 2015, Salman Halim wrote:
> Hello, everybody. Bram asked me to forward this here in case anybody else could
> shed any light on this issue.
>
> Thank you. The issue:
>
> > Bram,
> >
> > I've tried this in several GVim distributions (on Windows 7, starting after
> about 7.4.3xx), but keep seeing the same behaviour with 'clilpboard' set to
> unnamed: the very first yank/delete/change operation sets the "* register
> (along with the usual "0, etc.), but subsequent operations only set the
> internal registers, not "*, so the operation's results aren't available outside
> GVim.
> >
> > If I do one of these, things work:
> >
> > 1. Explicitly prefix an operation with "*. This works, but is a departure
> from the usual behaviour. Or,
> > 2. Launch with vim -u NONE -U NONE and then set 'clipboard' to unnamed.
> >
> > Based on 2, you could argue that a plugin/autocommand must be doing
> something, but I didn't change any of those; I literally just dropped in
> another GVim build.
> >
> > It's interesting that the very first one works, but subsequent operations
> don't.
> >
> > Lastly, this doesn't work for simple operations such as yiw or y$, neither of
> which are mapped to anything. The only thing I can think of is that something
> changed in the code base in how this is handled.
> >
> > What do you think?
plugin does that?
Best,
Christian
Sorry I didn't get back to you sooner, but it took a while to narrow it down. It's this:
tabdo windo echo 'hi'
Basically, execute a command in all tabs and windows. The command doesn't matter (I tried a few different commands, including those that don't echo anything to eliminate :echo as the culprit). Everything works just fine until the first time this tabdo and windo combination is executed and then subsequent operations no longer affect the "* register. (Yes, 'clipboard' is set to unnamed both before and immediately after the command--didn't get modified and echoes my _vimrc as the last place from which it was set.)
Simply executing :windo echo 'hi' doesn't do it, nor does :tabdo echo 'hi'. It's got to be both tabdo and windo in the same operation.
(My previous diagnosis that it works the first time only was a misinterpretation of this symptom.)
The interesting thing is that I only have one buffer open, so all three of tabdo, windo and tabdo windo actually only execute once.
Thank you,
Salman
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment