vim forgets registers (*, +) after reattaching tmux session; E353: Nothing in register
I ssh into a remote system and use a vim+tmux workflow. I love it because I can detach my session at the end of the day, and when I fire it back up the next morning, it's exactly where I left off.
The problem is: when I reattach the tmux session, any open vim editor no longer recognizes the * or + registers. giving the error
E353: Nothing in register +
The only way I can get this to work again is if I quit out of all my vim tabs and restart it.
vim --version returns
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 24 2016 16:44:48)
+clipboard
+xterm_clipboard
se clipboard? returnsclipboard=unnamed,unnamedplus,autoselect,exclude:cons|linux
:echo has('clipboard') returns1
:echo has('xterm_clipboard') returns1
:echo $DISPLAY returnslocalhost:10.0 <-- this is consistant with the attached DISPLAY
Is there a way to get vim to reload the + and * registres?
ssh vim tmux
asked May 21 '18 at 22:05
BenBen
1064
add a comment |
I ssh into a remote system and use a vim+tmux workflow. I love it because I can detach my session at the end of the day, and when I fire it back up the next morning, it's exactly where I left off.
The problem is: when I reattach the tmux session, any open vim editor no longer recognizes the * or + registers. giving the error
E353: Nothing in register +
The only way I can get this to work again is if I quit out of all my vim tabs and restart it.
vim --version returns
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 24 2016 16:44:48)
+clipboard
+xterm_clipboard
se clipboard? returnsclipboard=unnamed,unnamedplus,autoselect,exclude:cons|linux
:echo has('clipboard') returns1
:echo has('xterm_clipboard') returns1
:echo $DISPLAY returnslocalhost:10.0 <-- this is consistant with the attached DISPLAY
Is there a way to get vim to reload the + and * registres?
ssh vim tmux
asked May 21 '18 at 22:05
BenBen
1064
There is currently some discussion on how to fix this issue github.com/vim/vim/issues/3649. If you can test a patch, please comment.
– Christian Brabandt
Dec 18 '18 at 11:28
add a comment |
I ssh into a remote system and use a vim+tmux workflow. I love it because I can detach my session at the end of the day, and when I fire it back up the next morning, it's exactly where I left off.
The problem is: when I reattach the tmux session, any open vim editor no longer recognizes the * or + registers. giving the error
E353: Nothing in register +
The only way I can get this to work again is if I quit out of all my vim tabs and restart it.
vim --version returns
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 24 2016 16:44:48)
+clipboard
+xterm_clipboard
se clipboard? returnsclipboard=unnamed,unnamedplus,autoselect,exclude:cons|linux
:echo has('clipboard') returns1
:echo has('xterm_clipboard') returns1
:echo $DISPLAY returnslocalhost:10.0 <-- this is consistant with the attached DISPLAY
Is there a way to get vim to reload the + and * registres?
ssh vim tmux
asked May 21 '18 at 22:05
BenBen
1064
I ssh into a remote system and use a vim+tmux workflow. I love it because I can detach my session at the end of the day, and when I fire it back up the next morning, it's exactly where I left off.
The problem is: when I reattach the tmux session, any open vim editor no longer recognizes the * or + registers. giving the error
E353: Nothing in register +
The only way I can get this to work again is if I quit out of all my vim tabs and restart it.
vim --version returns
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 24 2016 16:44:48)
+clipboard
+xterm_clipboard
se clipboard? returnsclipboard=unnamed,unnamedplus,autoselect,exclude:cons|linux
:echo has('clipboard') returns1
:echo has('xterm_clipboard') returns1
:echo $DISPLAY returnslocalhost:10.0 <-- this is consistant with the attached DISPLAY
Is there a way to get vim to reload the + and * registres?
ssh vim tmux
ssh vim tmux
asked May 21 '18 at 22:05
BenBen
1064
asked May 21 '18 at 22:05
BenBen
1064
edited Dec 17 '18 at 18:43
Ben
asked May 21 '18 at 22:05
BenBen
1064
asked May 21 '18 at 22:05
BenBen
1064
asked May 21 '18 at 22:05
BenBen
1064
1064
There is currently some discussion on how to fix this issue github.com/vim/vim/issues/3649. If you can test a patch, please comment.
– Christian Brabandt
Dec 18 '18 at 11:28
add a comment |
There is currently some discussion on how to fix this issue github.com/vim/vim/issues/3649. If you can test a patch, please comment.
– Christian Brabandt
Dec 18 '18 at 11:28
There is currently some discussion on how to fix this issue github.com/vim/vim/issues/3649. If you can test a patch, please comment.
– Christian Brabandt
Dec 18 '18 at 11:28
There is currently some discussion on how to fix this issue github.com/vim/vim/issues/3649. If you can test a patch, please comment.
– Christian Brabandt
Dec 18 '18 at 11:28
add a comment |
1 Answer
1
active
oldest
votes
This happens to me as well. I run Ubuntu 16.04 VirtualBox which is my remote VM. Everytime, I try to reconnect, I have lost the registers. I used to savestate on the VM and come to it.
These days, instead I use the tmux-resurrect and tmux-continuum extensions. These preserve the tmux-splits, and also the vim-states with vim-obsession. Next, instead of using savestate on the VM, I actually shut it off.
When I start it up, the registers work pretty reliably.
answered Jun 11 '18 at 1:31
alpha_989alpha_989
34726
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1324770%2fvim-forgets-registers-after-reattaching-tmux-session-e353-nothing-in-re%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This happens to me as well. I run Ubuntu 16.04 VirtualBox which is my remote VM. Everytime, I try to reconnect, I have lost the registers. I used to savestate on the VM and come to it.
These days, instead I use the tmux-resurrect and tmux-continuum extensions. These preserve the tmux-splits, and also the vim-states with vim-obsession. Next, instead of using savestate on the VM, I actually shut it off.
When I start it up, the registers work pretty reliably.
answered Jun 11 '18 at 1:31
alpha_989alpha_989
34726
add a comment |
This happens to me as well. I run Ubuntu 16.04 VirtualBox which is my remote VM. Everytime, I try to reconnect, I have lost the registers. I used to savestate on the VM and come to it.
These days, instead I use the tmux-resurrect and tmux-continuum extensions. These preserve the tmux-splits, and also the vim-states with vim-obsession. Next, instead of using savestate on the VM, I actually shut it off.
When I start it up, the registers work pretty reliably.
answered Jun 11 '18 at 1:31
alpha_989alpha_989
34726
add a comment |
This happens to me as well. I run Ubuntu 16.04 VirtualBox which is my remote VM. Everytime, I try to reconnect, I have lost the registers. I used to savestate on the VM and come to it.
These days, instead I use the tmux-resurrect and tmux-continuum extensions. These preserve the tmux-splits, and also the vim-states with vim-obsession. Next, instead of using savestate on the VM, I actually shut it off.
When I start it up, the registers work pretty reliably.
answered Jun 11 '18 at 1:31
alpha_989alpha_989
34726
This happens to me as well. I run Ubuntu 16.04 VirtualBox which is my remote VM. Everytime, I try to reconnect, I have lost the registers. I used to savestate on the VM and come to it.
These days, instead I use the tmux-resurrect and tmux-continuum extensions. These preserve the tmux-splits, and also the vim-states with vim-obsession. Next, instead of using savestate on the VM, I actually shut it off.
When I start it up, the registers work pretty reliably.
answered Jun 11 '18 at 1:31
alpha_989alpha_989
34726
answered Jun 11 '18 at 1:31
alpha_989alpha_989
34726
answered Jun 11 '18 at 1:31
alpha_989alpha_989
34726
answered Jun 11 '18 at 1:31
alpha_989alpha_989
34726
34726
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1324770%2fvim-forgets-registers-after-reattaching-tmux-session-e353-nothing-in-re%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
There is currently some discussion on how to fix this issue github.com/vim/vim/issues/3649. If you can test a patch, please comment.
– Christian Brabandt
Dec 18 '18 at 11:28