#1
|
|||
|
|||
Copy & Past multi-line text
I am using SecureCRT 7.1.3
When I copy multi-line text from some editor and past it to the active serial session screen I am expecting to receive exactly the same content on the serial interface connected to. Unfortunately, SecureCRT eats some of Line Feed (0x0A) characters and replaces them with Carriage Return (0x0D). For example, the text (shown here in the hex): 09 0A 0D 0A 0A 0D 20 21 22 23 24 25 26 27 28 29 transmitted as: 09 0D 0D 0D 0D 20 21 22 23 24 25 26 27 28 Is there ability to send multi-line text as is without any changes by paste operation? P.S. It's not a Windows copy paste issue, because the other terminal app sends pasted text properly. |
#2
|
|||
|
|||
Hi azazello,
Version 7.1.3 is pretty old but if you enable New line mode in the Terminal / Emulation / Modes category of Session Options, what are the results?
__________________
Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
#3
|
|||
|
|||
Thank you for the fast response.
It's quite clear from the help file that this option is used for generating new line by CR LF substitution, but not to keep the text unchanged. Code:
09 0A 0D 0A 0A 0D 20 : original text 09 0D 0A 0D 0A 0D 0A 0D 0A 20 : New Line option checked 09 0D 0D 0D 0D 20 : New Line option unchecked |
#4
|
|||
|
|||
Hi azazello,
Quote:
__________________
Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
#6
|
|||
|
|||
Hi azazello,
Would you copy the data you wish to paste into SecureCRT into the clipboard and then run the attached script and let me know the resulting output? Probably posting a screenshot of the resulting dialog box would be best. See this guide for attaching/embedding graphics in your post.
__________________
Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
#7
|
|||
|
|||
Quote:
Here's the content of the test file (7 bytes in the attachment "Port_.txt"): [HT][LF][CR][LF][LF][CR][SP] I added [SP] to your script for the clarity of space symbol. Here's the result: |
#8
|
|||
|
|||
Hi azazello,
Now please configure your session for level 9 trace options output and paste the same data in the terminal window for a test:
__________________
Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
#9
|
|||
|
|||
Sending from COM7 session log:
SecureCRT - Version 8.7.3 (x64 build 2279) [SERIAL-TRACE 23:39:54.068] : COMM-EVENT [dsr,rlsd] [SERIAL-TRACE 23:39:54.068] : Comm State Change [DSR-ON] [SERIAL-TRACE 23:39:54.068] : Comm State Change [RLSD-ON] [SERIAL-TRACE 23:39:54.068] : COMM-EVENT [cts] [SERIAL-TRACE 23:39:54.068] : Comm State Change [CTS-ON] [SERIAL-TRACE 23:40:42.620] : [SEND] : 00000000 | 09 0d .. [SERIAL-TRACE 23:40:42.620] : COMM-EVENT [tx] [SERIAL-TRACE 23:40:42.635] : [SEND] : 00000000 | 0d . [SERIAL-TRACE 23:40:42.635] : COMM-EVENT [tx] [SERIAL-TRACE 23:40:42.651] : [SEND] : 00000000 | 0d . [SERIAL-TRACE 23:40:42.651] : COMM-EVENT [tx] [SERIAL-TRACE 23:40:42.667] : [SEND] : 00000000 | 0d . [SERIAL-TRACE 23:40:42.667] : COMM-EVENT [tx] [SERIAL-TRACE 23:40:42.682] : [SEND] : 00000000 | 20 [SERIAL-TRACE 23:40:42.682] : COMM-EVENT [tx] [SERIAL-TRACE 23:42:37.771] : Waiting 10 seconds for I/O thread 10404 to exit. [SERIAL-TRACE 23:42:37.786] : I/O thread 10404 has exited cleanly. [SERIAL-TRACE 23:42:37.786] : Close Handle[2728] Receiving to COM107 session log: SecureCRT - Version 8.7.3 (x64 build 2279) [SERIAL-TRACE 23:40:42.720] : [RECV] : 00000000 | 09 0d 0d 0d 0d 20 ..... [SERIAL-TRACE 23:42:37.802] : COMM-EVENT [dsr,rlsd] [SERIAL-TRACE 23:42:37.802] : Comm State Change [DSR-OFF] [SERIAL-TRACE 23:42:37.802] : Comm State Change [RLSD-OFF] [SERIAL-TRACE 23:42:37.802] : COMM-EVENT [cts] [SERIAL-TRACE 23:42:37.802] : Comm State Change [CTS-OFF] [SERIAL-TRACE 23:42:40.748] : Waiting 10 seconds for I/O thread 7124 to exit. [SERIAL-TRACE 23:42:40.748] : I/O thread 7124 has exited cleanly. [SERIAL-TRACE 23:42:40.748] : Close Handle[2796] |
#10
|
|||
|
|||
Hi azazello,
That's odd. For me, the CR and LFs all were retained when sending/pasting. Please attach the INI for your serial session and Global.ini file. (General / Configuration Paths category in Global Options will show the path to the config where you will find Global.ini, session INI files are in the Sessions subfolder.) Or send it to support@vandyke.com and reference Attn Brenda - Forum Thread #14337 in the subject line.
__________________
Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
#11
|
|||
|
|||
Global.ini and serial session INI files are attached.
|
#12
|
|||
|
|||
Hi azazello,
We have found if you use Send Binary (Transfer menu) with your test file, the line endings are sent as-is. What are your results?
__________________
Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
#13
|
|||
|
|||
Quote:
When I use send binary operation, the file transferred as is - it's the main purpose of this feature (I hope ![]() But my question is about the paste operation the previously copied text data into the active session screen. The problem is when the text pasted into the terminal window, the same logic works as when the buttons pressed on the keyboard. Thus, the checkbox "New Line Mode" (Terminal/Emulation/Modes) is analyzed when the pasted text is parsed, which should be verified only when the ENTER key is physically pressed. Last edited by azazello; 11-18-2020 at 06:08 AM. |
#14
|
|||
|
|||
Hi azazello,
Yes, I understand that. We just wanted confirmation there was a workaround you can use. ![]() I will update this thread when I have further news. If you want direct contact, send an email to support@vandyke.com and reference Attn Brenda - Forum Thread #14337 in the subject line.
__________________
Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
#15
|
|||
|
|||
Hi azazello,
Our investigation has revealed that when SecureCRT pastes the contents of the clipboard, conversions of EOL characters are performed such that the data is entered as if it were typed. Meaning that since the Enter key typically generates a CR (not LF, not CRLF, not LFCR), all LF's are typically dropped from a paste operation. The only way to avoid such conversion currently is to use the Send Binary functionality that was referenced earlier. I've created a feature request on your behalf for a Paste Without EOL conversion (Raw Paste) feature. While we don't have any ETA as to if/when such a feature would become available, we will post here with news should something become available. If you prefer direct email notification, send an email to support@vandyke.com and include "Feature Request - Forum Thread #14337" in the subject line or use this form from the support page of our website.
__________________
Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | |
|
|