[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
flow-control
From: |
Nikolai Weibull |
Subject: |
flow-control |
Date: |
Wed, 1 Dec 2004 02:19:38 +0100 |
User-agent: |
Mutt/1.5.6i |
OK, an often revisited subject, but it just struck me that it's not
working as I thought it would. Why doesn't 'defflow off' disable
flow-control in my terminals? For most of my windows created by a new
screen (with a $SHELL in them), I get something like
(1,79)/(132,79)+8192 -(-)flow -c1 UTF-8 1(zsh)
in my info output, but for
screen -t 'mua' 9 mutt -n
I get
(6,19)/(132,79)+8192 -(+)flow app -c1 UTF-8 9(mua)
What gives? Without the 'defflow off' in my screenrc, I get -flow for
most and +flow for the one with mutt in it.
In mutt, flow-control will be enabled. In a terminal, [-(-)],
flow-control is also still enabled, so the defflow off doesn't seem to
have any real effect. Is this due to xterm? I thought I understood
flow-control (finally), but it seems I don't.
Should I understand this as, even though screen passes on ^S, the shell
will interpret ^S unless stty -ixon has been run and that in the case of
mutt, there's really no chance for stty -ixon to be run?
nikolai
--
::: name: Nikolai Weibull :: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA :: loc atm: Gothenburg, Sweden :::
::: page: www.pcppopper.org :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- flow-control,
Nikolai Weibull <=