Re: [Expectperl-discuss] Windows interaction

[Austin S. <te...@of...>]

On Wed, Jun 19, 2002 at 02:34:49PM -0700, Wim Verhaert wrote:
> Thanks for the replies,...
> It seems that the problem I have is related to the folowing command
> 
> print $session "$argument\n";
> 
> The problem now in the windows environement is the '\n'. When I replace this
> with '\r' it works.
> I never had this problem in a unix environement. Any comments?
> 

	This is an excellent question. I have had trouble with different
unix applications expecting \r, so it's not windows specific.
	I suspect preference for \r vs \n is application specific, though
there are terminal parameters to specify whether \n gets translated to \r
or vice-versa. Then, a beauty of arcane history, when it gets echoed back
to you it is again filtered by the tty output settings (which is also
configurable via stty or IO::Stty, etc).
	I don't have any good answer for why an application would prefer one
vs. the other. Probably also arcane historical reasons. Most apps seem to
like \n. IIRC when I used cu to talk to modems they liked \r.

	Short answer: do whatever works.

	Austin