Re: Any plans for a new release?

2016-06-14 Thread Simon Ruderich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Mon, Jun 13, 2016 at 08:24:45PM +0200, Amadeusz Sławiński wrote: > Hi, > > right it was quite a while, I will do release this weekend. > If anyone has any other patches they want to get in before release > please send them. > I'll backport mentio

Re: Any plans for a new release?

2016-06-14 Thread Антон Кочков
Hello! Can you please include also a 'truecolor' option support in this release too? I see it's in the 'master' branch, which you said is development branch for v5. Since tmux-2.2 was released with support for this feature it would be nice to see it in the latest screen release too. See also the b

Re: Any plans for a new release?

2016-06-14 Thread Carsten Mattner
On Mon, Jun 13, 2016 at 8:24 PM, Amadeusz Sławiński wrote: > On Mon, 13 Jun 2016 14:07:17 +0200 > Carsten Mattner wrote: > >> On Sun, Jun 12, 2016 at 10:44 PM, Andrew Savchenko >> wrote: >> > Hello, >> > >> > it looks like git head contains many important fixes: code >> > hardening (e.g. strcpy

Re: Any plans for a new release?

2016-06-13 Thread Amadeusz Sławiński
On Mon, 13 Jun 2016 14:07:17 +0200 Carsten Mattner wrote: > On Sun, Jun 12, 2016 at 10:44 PM, Andrew Savchenko > wrote: > > Hello, > > > > it looks like git head contains many important fixes: code > > hardening (e.g. strcpy -> strncpy) and fix for hardoded screenterm > > value (commit 37ca949e4

Re: Any plans for a new release?

2016-06-13 Thread Carsten Mattner
On Sun, Jun 12, 2016 at 10:44 PM, Andrew Savchenko wrote: > Hello, > > it looks like git head contains many important fixes: code > hardening (e.g. strcpy -> strncpy) and fix for hardoded screenterm > value (commit 37ca949e462a7608572f653848b5a7554964fd53). The latter > is very important, since it

Any plans for a new release?

2016-06-12 Thread Andrew Savchenko
Hello, it looks like git head contains many important fixes: code hardening (e.g. strcpy -> strncpy) and fix for hardoded screenterm value (commit 37ca949e462a7608572f653848b5a7554964fd53). The latter is very important, since it fixes segfault which happens when $TERM is longer than 20 chars, e.g.

Re: plans

2005-12-19 Thread Juergen Weigert
On Dec 18, 05 16:46:50 +0100, Michael Schroeder wrote: > On Sat, Dec 17, 2005 at 01:26:46PM -0800, John Davidorff Pell wrote: > > A long ago discussion resulted in the following being supplied to me. > > I have used when building screen ever since, but it is not in 4.0.2. > > Please include is

Re: plans

2005-12-18 Thread Michael Schroeder
On Sat, Dec 17, 2005 at 01:26:46PM -0800, John Davidorff Pell wrote: > A long ago discussion resulted in the following being supplied to me. > I have used when building screen ever since, but it is not in 4.0.2. > Please include is in HEAD? :-) Don't worry, it's already in "HEAD". Micha. --

Re: plans

2005-12-18 Thread Matto Fransen
Hi, On Sat, Dec 17, 2005 at 12:45:38PM +0100, Rafal Maszkowski wrote: > What I plan to do is: > - include my sockdr/status patch - I use it successfully since some 2 years > - probably include Bill's patch > - applying some Linux and GNU software distributions patches > - think about more consiste

Re: plans

2005-12-17 Thread John Davidorff Pell
A long ago discussion resulted in the following being supplied to me. I have used when building screen ever since, but it is not in 4.0.2. Please include is in HEAD? :-) Basically the last "if else" is new. Its only a few lines, and I love it. Thanks! JP Begin forwarded message: From:

plans

2005-12-17 Thread Rafal Maszkowski
What I plan to do is: - include my sockdr/status patch - I use it successfully since some 2 years - probably include Bill's patch - applying some Linux and GNU software distributions patches - think about more consistent vi movement in the scroll buffer - work on optimizing resize if time allows (m