screen-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [screen-devel] Move hosting to GitHub? (was: Re: Extend windows comm


From: Amadeusz Sławiński
Subject: Re: [screen-devel] Move hosting to GitHub? (was: Re: Extend windows command, introduce Xx string escape)
Date: Thu, 27 Mar 2014 15:08:39 +0100

On Thu, 27 Mar 2014 09:31:07 +0100
Axel Beckert <address@hidden> wrote:

> Hi,
> 
> On Wed, Mar 26, 2014 at 09:13:14PM +0100, Jostein Berntsen wrote:
> > Would it be an idea to move the savannah code to github instead
> > making it more visible and easy for more to contribute so we could
> > get a new release?
> 
> I think getting a new release out is no question of more people who
> contribute (code). It more a question of someone feeling responsible
> as a release manager (or similar) _and_ thinking it's time for a new
> release.

As I've wrote previously I've started keeping my own set of changes in
repository due to practically non existant development, while some
people send patches I've found use for. Which seems to be caused by lack
of dedicated maintainer, instead of people having access to repository.

> And IMHO it makes no difference where the code is primarily hosted for
> that.
> 
> From a political point of view, Savannah as GNU's own forge hosting is
> IMHO clearly the better choice as it runs with free software and is
> not run by a company.

As long as there is development I don't care where it's hosted ;)

---

On more pragmatic note, I've a lot of changes in my repository
(https://github.com/amade/screen - look at devel branch as it's more
recent) so I would like to avoid porting them back to "official" one.
Though I will understand if people are hesitant to use it.

Anyway some of changes include:
- hardstatus on top (that's where it all started ;)
- integrated a lot of patches which appeared over time on list
- more stability (I can still crash it when I try hard, but it seems a
  lot more stable to me)
- rewritten color handling, ie 256 and truecolor (where supported by
  terminal) escapes
- remove some escapes which can be replaced better by backticks
- removed a lot of cruft (though people trying to use it on some
  ancient machines may not apreciate), I use screen on linux, so it's
  the only place where I test, so making it work on some other systems
  may take a bit of patching again


Screenshot showing some of the mentioned stuff:
hardstatus on top, using backtick for loadavg with coloring depending
on load
(https://github.com/amade/scripts/blob/master/screen/loadavg.sh),
lower split showing off truecolor support
http://asmblr.net/scrot/2014-01-15-161848_1366x768_scrot.png

Amadeusz Sławiński



reply via email to

[Prev in Thread] Current Thread [Next in Thread]