Quantcast

clipboard issue in global commands when set to unnamed

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

clipboard issue in global commands when set to unnamed

Bryce Orgill
I had previously mentioned that there was an issue with yanking in post title: "after vim 8 installation, yanking (yy) doesn't work in global command and macros".  The real issue I see with this is, when one sets clipboard to unnamed, any yanking done in global commands or macros does get yanked to the unnamed register ("") and the star register ("*).  However, it seems when I try to access the unnamed register (e.g.: let y1=@*), the contents change back to the original register's contents.  This is on windows.  See the two cases below where this setting is in place for both: set cb=unnamed.  When the clipboard setting is blank (i.e. set cb=), the commands work fine.  When set to unnamed the clipboard or something else doesn't work.  This to me is a bug.  It was working in version 7.4 just fine.  It was update 7.4.396 that broke this.  I understand the update was a performance fix, but with the unnamed setting it doesn't work for me.  It's the reason I haven't upgraded to version 8 yet.  When will this be fixed?

Cases below only differ in the macro setting (@q).

Case 1:
-------
Macro (@q): viw^C    "Ctrl C is mapped to "+y
Register "" before run: <empty or previous data>
Register "* before run: same as register ""
Buffer Contents before run:
55

Command executed with cursor on above buffer line: .g/^/normal @q

Register "" after run: 55
Register "* after run: 55

Case 2:
-------
Macro (@q): viw^C:let y1=@+^M    "Ctrl C is mapped to "+y
Register "" before run: <empty or previous data>
Register "* before run: same as register "" before run
Buffer Contents before run:
55

Command executed with cursor on above buffer line: .g/^/normal @q

Register "" after run: same as register "" before run
Register "* after run: same as register "* before run

--
--
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: clipboard issue in global commands when set to unnamed

Bram Moolenaar

Bryce Orgill wrote:

> I had previously mentioned that there was an issue with yanking in post
> title: "after vim 8 installation, yanking (yy) doesn't work in global
> command and macros".  The real issue I see with this is, when one sets
> clipboard to unnamed, any yanking done in global commands or macros does
> get yanked to the unnamed register ("") and the star register ("*).
> However, it seems when I try to access the unnamed register (e.g.: let
> y1=@*), the contents change back to the original register's contents.
> This is on windows.  See the two cases below where this setting is in
> place for both: set cb=unnamed.  When the clipboard setting is blank
> (i.e. set cb=), the commands work fine.  When set to unnamed the
> clipboard or something else doesn't work.  This to me is a bug.  It was
> working in version 7.4 just fine.  It was update 7.4.396 that broke
> this.  I understand the update was a performance fix, but with the
> unnamed setting it doesn't work for me.  It's the reason I haven't
> upgraded to version 8 yet.  When will this be fixed?
>
> Cases below only differ in the macro setting (@q).
>
> Case 1:
> -------
> Macro (@q): viw^C    "Ctrl C is mapped to "+y
> Register "" before run: <empty or previous data>
> Register "* before run: same as register ""
> Buffer Contents before run:
> 55
>
> Command executed with cursor on above buffer line: .g/^/normal @q
>
> Register "" after run: 55
> Register "* after run: 55
>
> Case 2:
> -------
> Macro (@q): viw^C:let y1=@+^M    "Ctrl C is mapped to "+y
> Register "" before run: <empty or previous data>
> Register "* before run: same as register "" before run
> Buffer Contents before run:
> 55
>
> Command executed with cursor on above buffer line: .g/^/normal @q
>
> Register "" after run: same as register "" before run
> Register "* after run: same as register "* before run

Thanks for the example. The extra :let command should not change the
register content.  Looks like a bug.

--
From "know your smileys":
 [:-) Frankenstein's monster

 /// Bram Moolenaar -- [hidden email] -- 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_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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Loading...