Comment #19 on issue 203 by [email protected]: Nothing in register *
problem (vim+tmux or vim+screen )
https://code.google.com/p/vim/issues/detail?id=203
Here is another way to show the same behavior with one machine.
1. Change runmode of Linux to multi-user text mode. (For RedHat, Edit
/etc/inittab. For Ubuntu, depends on version.)
2. Reboot machine.
3. Login
4. startx (For Ubuntu, depends on version. Might need to start service gdm
or lightdm.)
5. (In GUI terminal) tmux
6. (In GUI terminal) vim
7. Logout (This will return you to text mode)
8. startx (For Ubuntu, depends on version. Might need to start service gdm
or lightdm.)
9. (In GUI termianl) tmux attach
You will find that vim is frozen.
Yes. I also think that it might by a problem with the X11 libraries.
But for some reason, if you add
if (app_context != (XtAppContext)NULL){
XtDestroyApplicationContext(app_context);
app_context = (XtAppContext)NULL;
}
to the begining of resetup_term_clip() in os_unix.c, vim doesn't freeze.
So I naively thought that there might be way to work around the X11 library
problem(?).
If you have any trouble in reproducing the problem, please tell me what
Linux version you use.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
