Micah Cowan writes:
> Yeah, screen doesn't allow split lines (or lines whose lengths are
> greater than 2048 bytes).
Don't the GNU Coding Conventions have something to say about arbitrary
limits? ;-)
PS: Sadrul, I'm eagerly awaiting the power of a ~/.screenrc.lua!
___
On Wed, Jan 07, 2009 at 11:44:51AM EST, Micah Cowan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Chris Jones wrote:
> > Couldn't find anything in the usual repositories.
> >
> > Here's my current hardstatus line (length=190):
> >
> > hardstatus alwayslastline "%{+r wk}%H %{+b yk}
On (08:27 07/01/09), Micah Cowan put forth the proposition:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Wood wrote:
I have a flashing block cursor set up because I find it very hard to see
the normal _ underline cursor - expecially when searching through man
pages etc.
The problem come
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Grant wrote:
> On Sun, Jan 4, 2009 at 12:16 PM, Michael Grant wrote:
>> I have both a linux box and a freebsd box. I have just started using
>> screen on the linux box. There seems to be some very definite
>> differences in behavior between
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Jones wrote:
> Couldn't find anything in the usual repositories.
>
> Here's my current hardstatus line (length=190):
>
> hardstatus alwayslastline "%{+r wk}%H %{+b yk}%0` %{+b wk} %1` | %2` %3` |%4`
> %{+b wk}| %{+b wk}%l%{+b wk} |%{+b gk} %n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Wood wrote:
> On (16:32 19/12/08), Dave Wood put forth the
> proposition:
>> On (18:54 18/12/08), Dave Wood put forth the
>> proposition:
>>> I find after switching screens a few times that I get either
>>> ';screen' or
>>> ';xterm-xf86-v40' pri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Wood wrote:
> I have a flashing block cursor set up because I find it very hard to see
> the normal _ underline cursor - expecially when searching through man
> pages etc.
>
> The problem comes when I run ncurses programs in screen. The cursor ge
