Open thomasboyt opened 10 years ago
Thanks for documenting this.
On Sunday, December 8, 2013, Thomas Boyt wrote:
I discussed this with @eventualbuddha https://github.com/eventualbuddhaa few weeks ago and it seems that this is a known bug, but I don't see an issue for it here.
For some reason, the very first shell opened in tmux doesn't attach to the system clipboard. When I try to yank & paste in VIM, I get the dreaded Nothing in register * error.
All subsequent shells opened in tmux - whether in a new pane, window, or even a new session - will have the clipboard attached correctly. Of course, if you close down all tmux sessions (and thus close tmux) and then create a new session, you'll once again be detached from the system clipboard.
The workaround is easy enough - just create a new pane and close the first one - but it's rather annoying. I have no idea what's actually broken - tmux, reattach-to-system-clipboard, or the config itself - but it'd be great to see a fix :)
— Reply to this email directly or view it on GitHubhttps://github.com/square/maximum-awesome/issues/124 .
This happens for me since messing with my system over the weekend. No idea what caused it though, did not update maximum-awesome until now (which didn´t fix the issue).
I also have this issue
I discussed this with @eventualbuddha a few weeks ago and it seems that this is a known bug, but I don't see an issue for it here.
For some reason, the very first shell opened in tmux doesn't attach to the system clipboard. When I try to yank & paste in VIM, I get the dreaded
Nothing in register *
error.All subsequent shells opened in tmux - whether in a new pane, window, or even a new session - will have the clipboard attached correctly. Of course, if you close down all tmux sessions (and thus close tmux) and then create a new session, you'll once again be detached from the system clipboard.
The workaround is easy enough - just create a new pane and close the first one - but it's rather annoying. I have no idea what's actually broken - tmux, reattach-to-user-namespace, or the config itself - but it'd be great to see a fix :)