Hi!
* Ana Guerrero <[email protected]> [2009-02-03 08:26:04 CET]:
> On Sun, Feb 01, 2009 at 11:03:23PM +0100, Gerfried Fuchs wrote:
> > When one is in #split mode, tt++ regularly switches back to have the
> > input above the ------ line and not below it anymore, making the upper
> > part behave just like in nonsplit mode. Not sure what might cause this
> > but it happens extremely regularly to me. Only thing I did switch from
> > default is #config {echo command} {off} additional to the #split (with
> > no options).
>
> Before I forward this to upstream could you confirm if you have the problem
> with current unstable's tintin? I am not myself an user of the #split mode,
> and in the trying I have done I did not get this problem. A 2-3 lines
> config-file with a test case would help too.
Still happens for me, I'm connected to discworld.atuin.net port 23, I
don't use any config-file (because tintin doesn't seem to support any
dot file?), I just do a "#session {DW} {discworld.atuin.net} {23}",
"#split", "#config {echo command} {off}".
What also bothers me a bit about the echo command is that it
neverteless _does_ echo the linebreak, no matter of that setting.
Thanks. :)
Rhonda
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
