Solved copy paste bug (Github code view beta)
-
@Pathduck yes.. that is it.
If it is disabled, the "bug" goes away.
I'm placing a bug now with github.
Because of you, I can directly point them to the problem.solved
-
@bksubhuti Good
Next time, please follow the troubleshooting steps completely.
Step #3 is testing in a new profile. You would then have realised where the problem was earlier
-
-
@bksubhuti Tip! To mark a topic as solved:
- Edit the first post
- Open the dropdown on the Submit button and click the option Ask As Question:
- Submit the post again
- Select the three dot vertical menu of the post that resolves the question:
- Select the option Mark This Post As The Correct Answer:
Thank you for making it easier for others to find a good solution
-
@Pathduck sorry.. i don't know how to do this.
Surely this interface is not a direct way to do this.
I tried several times.. I edited the first post and wrote solved.The moderator can mark this as solved. I can't figure it out.
-
PPathduck marked this topic as a question on
-
PPathduck has marked this topic as solved on
-
Ppafflick moved this topic from Vivaldi for Windows on
-
The clipboard in modern versions of Windows is only limited by the amount of memory installed in your computer. (The limit would be in bytes, and not lines of text anyway.) However, Windows 10 and 11 can struggle to copy more than 8 MB (roughly 2 million Latin characters) in one go with Clipboard history and Clipboard sync enabled.
Regarding your workflow, you can attach .patch to the end of GitHub code reviews to download a patch-file you can use to apply the proposed code changes. Manually copying code is error-prone, like youโve already experienced.