copy issue [4]
copy issue
Friday, December 16, 2011 12:56 AM - jophy cui
Hi,
After I used the left button select the content, the terminal will start a new line which is bother me. Let's say, i wanna run the "vi" something,i will input the vi first then i used the left buttton to select the file, it will start a new line. Do me have any configuration to avoid this ?
Program Ver. : Xshell 4
After I used the left button select the content, the terminal will start a new line which is bother me. Let's say, i wanna run the "vi" something,i will input the vi first then i used the left buttton to select the file, it will start a new line. Do me have any configuration to avoid this ?
Program Ver. : Xshell 4
Re: copy issue
Sunday, December 18, 2011 10:36 PM - John
Some windows programs use CTRL+C to copy mouse selected area.
Ctrl+C is used for interrupt signal in the terminal.
Please check your ms windows program like Yahoo dictionary.
Ctrl+C is used for interrupt signal in the terminal.
Please check your ms windows program like Yahoo dictionary.
Re: copy issue
Monday, December 19, 2011 11:02 PM - jophy cui
Hi john,
I don't think it is Ctrl + C this, because when you double click the left button in the ternimal, it also start a new line. Anyway thx for your advice.
I don't think it is Ctrl + C this, because when you double click the left button in the ternimal, it also start a new line. Anyway thx for your advice.
Re: copy issue
Monday, December 19, 2011 11:55 PM - Support
John was right about pointing out the 3rd party application. We have received a few reports that the dictionary applications cause this issue.
Do you have any applications that automatically initialize some actions when you double click on a word?
---
Technical Support
Do you have any applications that automatically initialize some actions when you double click on a word?
---
Technical Support
Re: copy issue
Tuesday, December 20, 2011 5:43 PM - jophy cui
Hi ,
I checked again. John was right, it was the 3rd party dictionary application cause this. problem solved, thank you very much!
I checked again. John was right, it was the 3rd party dictionary application cause this. problem solved, thank you very much!
Previous views: 282