On Fri, Sep 08, 2006 at 08:53:33AM -0400, Brian Mathis wrote:
> According to the vtprint man page, it uses terminal escape sequences to
> activate the printer. When screen is running, it inserts a layer in
> between the program and your terminal program, which is what allows
> screen to perform
According to the vtprint man page, it uses terminal escape sequences to
activate the printer. When screen is running, it inserts a layer in
between the program and your terminal program, which is what allows
screen to perform its magic, and will also catch those sequences and
prevent vtprint f
Henry,I am not familiar with vtprint, but these sorts of problems sound like typical environment variable issues. If your vtprint environment gets set up in your .profile/.login or equivalent (you don't state what shell you use), but is not exported, then this can happen. From a quick Google sear
I use PuTTY to login to a shell account for reading/sending mail.
>From the shell without running Screen, I can print from Mutt
using "vtprint" (prints out on printer attached to local terminal).
When I evoke Mutt from a Screen session, nothing is sent to the
printer, even though I get a message o
