do so you may have
to fix it manually.
Original message
From: "Vadim A. Misbakh-Soloviov"
Date: 26/09/2013 14:51 (GMT+00:00)
To: tmux-users@lists.sourceforge.net
Subject: Fwd: Re: Corrupting the terminal with /dev/urandom
Actually, not always.
Once upo
Actually, not always.
Once upon a time I corrupted tmux session by /dev/urandom in that way,
that even status-bar and tabbar was broken. And reset has no effect on
them. The only way to 100% fix is a restart session :/
26.09.2013 19:56, Paulo Ferreira пишет:
>
> On 23/09/2013, at 23:26, Jack O'C
> I've had this problem before. Sometimes 'reset' doesn't fix it because
> the binary data includes the magic tmux escape code to set the window
> name. I have to go in and explicitly change the window name back, and
> then it works fine.
Splitting the window, breaking off the f0obared pane and kil
I've had this problem before. Sometimes 'reset' doesn't fix it because
the binary data includes the magic tmux escape code to set the window
name. I have to go in and explicitly change the window name back, and
then it works fine.
On Thu, Sep 26, 2013 at 11:27 AM, Saad Malik wrote:
> Paulo,
> Hmm
Paulo,
Hmm there is no 'reset' for Cygwin users. Any one know of a method of
resetting mintty terminal when it's in a 'non-normal' state? I've been bit
by this issue a couple times--mostly by careless catting of binary files.
The only workaround was to completely kill the tmux session and then star
On 23/09/2013, at 23:26, Jack O'Connor wrote:
> Let me preface this by saying this is a stupid question. Please feel free to
> tell me "don't do that".
>
> When I run `cat /dev/urandom` inside of tmux, it usually corrupts my
> terminal, and I end up with something like this:
>
>
>
> Gnome-
