On Sat, Jun 18, 2011 at 11:37:07PM +0300, Kostik Belousov wrote:
> On Sat, Jun 18, 2011 at 10:14:32PM +0200, Stefan `Sec` Zehl wrote:
> > Hi,
> >
> > On Thu, Jun 16, 2011 at 13:15 -0700, Jeremy Chadwick wrote:
> > > Example: run mutt from within GNU screen while connected to
> > > the sy
On Sat, Jun 18, 2011 at 10:14:32PM +0200, Stefan `Sec` Zehl wrote:
> Hi,
>
> On Thu, Jun 16, 2011 at 13:15 -0700, Jeremy Chadwick wrote:
> > Example: run mutt from within GNU screen while connected to
> > the system with PuTTY, then copy some of the terminal content and paste
> > it some
On Sat, Jun 18, 2011 at 10:14:32PM +0200, Stefan `Sec` Zehl wrote:
> Hi,
>
> On Thu, Jun 16, 2011 at 13:15 -0700, Jeremy Chadwick wrote:
> > Example: run mutt from within GNU screen while connected to
> > the system with PuTTY, then copy some of the terminal content and paste
> > it some
Hi,
On Thu, Jun 16, 2011 at 13:15 -0700, Jeremy Chadwick wrote:
> Example: run mutt from within GNU screen while connected to
> the system with PuTTY, then copy some of the terminal content and paste
> it somewhere. Wow, look at all those extraneous spaces at the end of
> lines, which y
On Thu, Jun 16, 2011 at 08:59:51PM +0200, Hans Ottevanger wrote:
> On Thu, Jun 16, 2011 at 07:18:37PM +0200, Ivan Voras wrote:
> > Hello,
> >
> > This *looks* like it should be a trivial problem (or at least
> > often-encountered one) but short of debugging both screen and tcsh, I
> > have no id
On Thu, Jun 16, 2011 at 07:18:37PM +0200, Ivan Voras wrote:
> Hello,
>
> This *looks* like it should be a trivial problem (or at least
> often-encountered one) but short of debugging both screen and tcsh, I
> have no ideas what to do next...
>
> On several machines (seemingly random, some are r
Hello,
This *looks* like it should be a trivial problem (or at least
often-encountered one) but short of debugging both screen and tcsh, I
have no ideas what to do next...
On several machines (seemingly random, some are running 7-stable, others
8-stable), I get this message after starting "s
