This forum is a read-only archive of the Gammon Software forum (2000–2026). No new posts can be made. Search the archive.

Copy and paste issue

Posted by Xandler on Sun 06 Feb 2022 06:12 PM — 5 posts, 17,460 views.

Xandler #0
So, I have come across an issue while using copy and paste when mushclient is open. Basically what happens is, I copy something, then go to paste it elsewhere and the copy gets over ridden by a blank entry. How do I know it's a blank entry? I open up the clipboard history and it's basically a blank entry on top of what I want to paste. I posted in the Microsoft forums about this thinking is was a computer issue with my operating system but it's an application issue (the tech posted something along the lines of: It seems the operating system has been corrupted or one of the system files has been corrupted that made the system acts wired). Has anyone ran across this issue and is there a fix for it? I'm running the latest version of mushclient (5.06) if that helps (I've even tried a fresh install and going back to a previous version) and the problem persists.
Nick Gammon Australia Forum Administrator #1
I do occasionally get reports about this sort of thing:

http://www.gammon.com.au/forum/?id=14349

http://www.gammon.com.au/forum/?id=80

http://www.gammon.com.au/forum/?id=2036

http://www.gammon.com.au/forum/?id=1452

There may be others.

To be honest, if copy/paste didn't work, in general, it would be a huge issue. However this only seems to crop up every couple of years, which suggest that it is an operating system issue, rather than a client issue.
Xandler #2
I see, it's weird though, if I close out mushclient, copy and paste works as intended, but having it open seems to cause that issue. After further investigation it appears to be a trigger I have enabled that's causing it. I know it's a long shot without posting the exact trigger, but do you know of any kind of trigger setting that would cause this?
Nick Gammon Australia Forum Administrator #3
It is possible in the scripting interface to change the clipboard, so perhaps that is it.
Xandler #4
I found the error that was causing it to act like that. On one of the triggers I made I must have mistakenly set the copy wildcards to clipboard from none to 1, I honestly don't know how other than a random misclick while editing. Either way, issue resolved.