On Sun, Aug 10, 2008 at 09:18:21PM -0400, Andy Harrison wrote:
> On Wed, Aug 6, 2008 at 10:44 AM, Ken Steen <[EMAIL PROTECTED]> wrote:
> > I have a small file manager that uses screen to open programs in new
> > screen windows. It works correctly except when using screen on a
> > directory mounted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micah Cowan wrote:
> My question is: is screen even right to issue the initialization string,
> at all? And particularly _after_ issuing smkx.
(Sorry, here and elsewhere, I mean smcup (termcap "ti"), not smkx.)
- --
Micah J. Cowan
Programmer, musicia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So, the other day, I suddenly found that screen was no longer using the
alternate screen buffer as it usually does. Worse, screen _thought_ it
was operating under the alternate screen buffer, so left a dirty screen
upon exit. Thinking it was a recently
On Sun, Aug 10, 2008 at 09:18:21PM -0400, Andy Harrison wrote:
> Although completely unrelated to screen, I had similar permission
> problems with one of my sshfs mounts. I finally solved it with the
> following sshfs params: [... -o allow_root]
Hmm -- perhaps this is related to screen being set-
On Wed, Aug 6, 2008 at 10:44 AM, Ken Steen <[EMAIL PROTECTED]> wrote:
> I have a small file manager that uses screen to open programs in new
> screen windows. It works correctly except when using screen on a
> directory mounted with sshfs or when using screen on a directory that is
> a symbolic li
* Jean-Yves Levesque had this to say on [05 Aug 2008, 11:40:03 -0400]:
> I do not know if this is an issue with my config
> but when I run the vertical split with layouts and
> I try to use the windowlist command (Ctrl-a ") I
> get the following message:
>
> Window size too small for window list p
