On 2018-03-03 08:22, Renato Fabbri wrote:
> The major drawback I found is that vim session do no recover the
> terminal windows/buffers....
It depends on how you open your terminal windows. If you just use
:terminal
then if you use ":mksession", vim will only remember that you have a
terminal. But if you use
:terminal some_application --paremeter --other-parameter
then ":mksession" will remember what was running in that window and
re-spawn "some_application" with the appropriate arguments, not just
a blank shell when you reload the session.
For me, tmux (and GNU screen) provide additional benefits of
1) being able to monitor for silence/activity
2) the ability to re-connect to a session from a different connection
(start something on one machine, then ssh into the machine from
elsewhere and resume with everything where it was).
It doesn't detract from the functionality of :terminal as I do like
being able pause the :terminal and then interact by
yanking/moving/pasting with the full power of vim, not just a
vim-like approximation provided by tmux's copy-buffer mode.
-tim
--
--
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.
Saturday, March 3, 2018
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment