On Tue, Jun 10, 2008 at 3:17 AM, Can-Hua Chen <[EMAIL PROTECTED]> wrote:
> Today I find that my problem is probably related
> to the LC_CTYPE that I set as zh_CN.UTF-8.
> When I set it as "C", the aptitude and mutt doesn't
> show messed or corupted display any more.
>
> Now I am still wondering ho
Hi Greg
> I realize that screen expects to have an interactive user at one end
> of its connection, and therefore I'm in some sense misusing the
> program.
Well, not if you use 'screen -X'. Maybe the 'stuff' command helps:
stuff string
Stuff the string string in the input buffer
I have a long-running daemon process that I start with screen so that
I can occasionally connect to and converse with it. However, I'd also
occasionally like to converse with the server process via shell
scripts. I'd like to do something like this:
echo "some commands" | screen -r my_server_proc
Today I find that my problem is probably related
to the LC_CTYPE that I set as zh_CN.UTF-8.
When I set it as "C", the aptitude and mutt doesn't
show messed or corupted display any more.
Now I am still wondering how to have GNU Screen
work well with mutt and aptitude or any program
using termcap/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy Harrison wrote:
> After finding myself struggling to alter the MAXWIN value (without
> hard-coding it into any header files) and having it successfully
> change when I compiled screen, I made a small modification to the
> configure script to make
After finding myself struggling to alter the MAXWIN value (without
hard-coding it into any header files) and having it successfully
change when I compiled screen, I made a small modification to the
configure script to make it a little friendlier. This allows you to
specify --with-maxwin=50 or what
