HyperTerminal, which I despise, has a feature that I unfortunately need. When doing simple terminal emulation (not telnet), and connected to a COM port, under the File/Properties/Settings/ASCII Setup menu there is an "Append Line Feeds to Incoming Line Ends" check box, and the strange application I am communicating to needs that. Is there anyway to make AbsoluteTelnet do this too? In other words, when the application I'm talking to sends a carriage return, I want a line feed added.
[size=1][ December 14, 2005, 05:12 PM: Message edited by: Brian T. Pence ][/size]
Nick,
I'll look into it. Shouldn't be hard.
Brian
Nick, Give this a try:
<p><a href="/beta-testing" target="_blank" rel="noopener">Beta Testing</a></p>
Your option is at the top right on the Options->Properties->VTOptions page. Let me know how it goes.
This doesn't work exactly right. When I set CR->CR/LF (and LF->LF), I get what looks like two CR/LFs. I can't find any permutation that changes the incoming CR to just a LF/CR, if I understand it correctly. Is it possible that when the original CR is translated to a CR/LF, the "new" CR gets translated a second time into CR/LF?
I don't think the system I'm communicating to ever sends a LF itself.
Thanks for working on this.
-- Nick
I should make this a bit clearer -- when the system I'm communicating to sends a CR on its own your software correctly replaces it with CR/LF, which is great. When I send a CR via completing a command on the keyboard when talking to the system (i.e. >foo CR) and it is echoed back, the CR is echoed twice, as it were. This isn't the end of the world, however, and if it's hard to fix that's not really a problem.
What you're probably seeing is a result of a CR/LF being sent from the host. The first CR is changed to a CR/LF, then the LF linefeeds again.
Perhaps a better behavior would be to only add a LF after the CR if one does not already exist.
In your situation, you may have different behaviors inside of your application and at the command line.
I'll see what I can do.
Brian
Brian,
Without your change, a CR from the command prompt (i.e., sent to the system) would be echoed back as a CR only -- no LF attached. It appears now the I get two CR/LF's, as the command prompt is echoed twice. That is:
Prompt> foo
comes back with
Prompt>
Prompt>
on the next two lines. Ideally there would be just one 'Prompt>' afterwards. But as I said this isn't a very big deal, and your change fixes my largest problem.
What is the value of your setting of
Options->Properties->VTOptions->Enter Sends?
If you get two prompts, it seems unlikely to be related to the new feature, which would only interpret data on the way in. If you got two prompts, it must be something else.
Brian
Nick,
Just wanted to ping you on whether you've been able to research this further. Before I can release this feature into the mainstream release, we need to clear up the remaining issues to ensure that is implemented correctly. Can you send me a logfile of your session (File->Open Log/File->Close LOG)
Brian
Brian,
Thanks, I emailed you an annotated log file.
-- Nick
