You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I am very much interested in the tmux integration feature that you have
implemented. This would really be an awesome feature if it has deep integration
with the tmux panes (just like iterm2). That way, my tmux panes will be
displayed as qutty tabs and navigation becomes very easy. Not sure if the tmux
integration is complete or not, but right now, I am facing some issues with it.
BTW, I am forced to run QuTTY 0.5-beta.exe because all the future versions have
some issue or the other on Windows 7.
I downloaded and compiled tmux from the link you have provided in the wiki and
started tmux on my Linux server. On my W7 machine, I launch Qutty and then type
"tmux -CC attach". I get an error msg on my Qutty console (pic attached) and
then qutty crashes.
What steps will reproduce the problem?
1. compile and run tmux on linux server
2. run qutty on W7
3. run tmux -CC attach to attach
What is the expected output? What do you see instead?
qutty should display the tmux panes
What version of the product are you using? On what operating system?
0.5, windows 7
Please provide any additional information below.
Original issue reported on code.google.com by [email protected] on 10 Aug 2013 at 1:52
hi
Tmux integration used to work fine(except with a few inconveniences) for
https://github.com/gnachman/tmux2.git codebase.
May be something has changed there causing these issues.
This commandmode has been integrated in official tmux 1.8.
We are working on integrating qutty with that.
It will be a few weeks for basic integration to start working.
In the meantime, we will be happy to help with why latest versions are not
working for you.
You shall open a separate bug for that.
Does it crash (any files in %USERPROFILE%\qutty\dumps\) ? Or something is not
working as expected ?
Thanks
Rajendran
Original issue reported on code.google.com by
[email protected]
on 10 Aug 2013 at 1:52Attachments:
The text was updated successfully, but these errors were encountered: