Am 09.02.2017 um 20:41 schrieb Achim Gratz:
Thomas Wolff writes:
The man page speaks about speculative local echo which sounds like
asking for trouble...
It is indispensable when you have a long-latency link.
Anyway, I could reproduce effects as you described with
mintty – tmux – mosh
Thomas Wolff writes:
> The man page speaks about speculative local echo which sounds like
> asking for trouble...
It is indispensable when you have a long-latency link.
> Anyway, I could reproduce effects as you described with
> mintty – tmux – mosh localhost (no additional screen needed)
> And,
Am 07.02.2017 um 22:00 schrieb Thomas Wolff:
Am 07.02.2017 um 08:30 schrieb Brian Inglis:
On 2017-02-06 12:46, Thomas Wolff wrote:
Am 05.02.2017 um 21:36 schrieb Brian Inglis:
It may also be useful if mintty had some character hex value box
display mode switch to display the actual codes at
Am 08.02.2017 um 23:51 schrieb Thomas Wolff:
Am 08.02.2017 um 19:34 schrieb Achim Gratz:
Thomas Wolff writes:
Further comments welcome, and it's Achim's turn to provide further
diagnostics input as requested in another mail. It could also be that
screen or tmux simply make invalid assumptions
Am 08.02.2017 um 19:34 schrieb Achim Gratz:
Thomas Wolff writes:
Further comments welcome, and it's Achim's turn to provide further
diagnostics input as requested in another mail. It could also be that
screen or tmux simply make invalid assumptions about the setting of
Wraparound modes.
That
Thomas Wolff writes:
> Further comments welcome, and it's Achim's turn to provide further
> diagnostics input as requested in another mail. It could also be that
> screen or tmux simply make invalid assumptions about the setting of
> Wraparound modes.
That will take a while. I'll have to set up
On 2017-02-07 13:52, Thomas Wolff wrote:
> Am 07.02.2017 um 08:30 schrieb Brian Inglis:
>> On 2017-02-06 12:46, Thomas Wolff wrote:
>>> Am 05.02.2017 um 21:36 schrieb Brian Inglis:
On 2017-02-05 11:35, Thomas Wolff wrote:
> Am 04.02.2017 um 17:13 schrieb Achim Gratz:
>> Thomas Wolff
Am 07.02.2017 um 08:30 schrieb Brian Inglis:
On 2017-02-06 12:46, Thomas Wolff wrote:
Am 05.02.2017 um 21:36 schrieb Brian Inglis:
It may also be useful if mintty had some character hex value box
display mode switch to display the actual codes at each visual
position, or maybe a font used to
Am 07.02.2017 um 08:30 schrieb Brian Inglis:
On 2017-02-06 12:46, Thomas Wolff wrote:
Am 05.02.2017 um 21:36 schrieb Brian Inglis:
On 2017-02-05 11:35, Thomas Wolff wrote:
Am 04.02.2017 um 17:13 schrieb Achim Gratz:
Thomas Wolff writes:
I have uploaded mintty 2.7.4 with the following
On 2017-02-06 12:46, Thomas Wolff wrote:
> Am 05.02.2017 um 21:36 schrieb Brian Inglis:
>> On 2017-02-05 11:35, Thomas Wolff wrote:
>>> Am 04.02.2017 um 17:13 schrieb Achim Gratz:
Thomas Wolff writes:
> I have uploaded mintty 2.7.4 with the following changes:
Since about
On 6 February 2017 at 12:46, Thomas Wolff wrote:
> Am 05.02.2017 um 21:36 schrieb Brian Inglis:
>>
>> On 2017-02-05 11:35, Thomas Wolff wrote:
>>>
>>> Hi Achim,
>>>
>>> Am 04.02.2017 um 17:13 schrieb Achim Gratz:
Thomas Wolff writes:
>
> I have uploaded mintty 2.7.4 with the
Am 05.02.2017 um 21:36 schrieb Brian Inglis:
On 2017-02-05 11:35, Thomas Wolff wrote:
Hi Achim,
Am 04.02.2017 um 17:13 schrieb Achim Gratz:
Thomas Wolff writes:
I have uploaded mintty 2.7.4 with the following changes:
Since about November/December last year I'm having problems with
screen
Am 06.02.2017 um 20:16 schrieb Achim Gratz:
Achim Gratz writes:
Thomas Wolff writes:
Is this within tmux or after leaving tmux (see comment below)? It
would be help to cross-test this; if it's mintty, which version would
show the behaviour first? What happens in xterm?
Within tmux or more
Achim Gratz writes:
> Thomas Wolff writes:
>> Is this within tmux or after leaving tmux (see comment below)? It
>> would be help to cross-test this; if it's mintty, which version would
>> show the behaviour first? What happens in xterm?
>
> Within tmux or more often screen within tmux. I'll have
On 2017-02-05 11:35, Thomas Wolff wrote:
> Hi Achim,
>
> Am 04.02.2017 um 17:13 schrieb Achim Gratz:
>> Thomas Wolff writes:
>>> I have uploaded mintty 2.7.4 with the following changes:
>> Since about November/December last year I'm having problems with
>> screen and tmux sessions in mintty not
Thomas Wolff writes:
> Is this within tmux or after leaving tmux (see comment below)? It
> would be help to cross-test this; if it's mintty, which version would
> show the behaviour first? What happens in xterm?
Within tmux or more often screen within tmux. I'll have to try what
happens in plain
Hi Achim,
Am 04.02.2017 um 17:13 schrieb Achim Gratz:
Thomas Wolff writes:
I have uploaded mintty 2.7.4 with the following changes:
Since about November/December last year I'm having problems with screen
and tmux sessions in mintty not correctly refreshing and leaving garbage
characters
Thomas Wolff writes:
> I have uploaded mintty 2.7.4 with the following changes:
Since about November/December last year I'm having problems with screen
and tmux sessions in mintty not correctly refreshing and leaving garbage
characters displayed in the terminal. It seems that the terminal size
I have uploaded mintty 2.7.4 with the following changes:
Localization details:
* Fixed localized Bell field contents.
* Adapting Bell list contents from system localization.
* Fixed unlocalized Colour chooser label "Basic colours:" and Font
chooser initial font sample.
* Fixed
19 matches
Mail list logo
