Why Ctrl+C randomly goes to another piece of the code? - eclipse

My first question here.
As I'm writing code normaly, sometimes I need to copy. And like every 50-100 Ctrl+C copys, the mouse pointer goes to another part of the code and it doesn't copy what was selected (I mainly use eclipse IDE, but I believe this happened in other editors). It's like I was pressing Ctrl+LMB.
This kinda happens randomly and I can't seem to replicate it. I believe I'm misclicking a key but I never do realize what I just did.
This can really piss me off and I can't find anything online related.
Is it just me? Does anyone have an ideia what could be happening?

Related

VS code cursor unresponsive

I am having a hard time on VS code due to issues with the cursor. It keeps jumping around while I am typing and makes a mess of my codes. I have tried reloading the window and even restarting my system multiple times but its no help at all. I have also disabled my extensions to no avail.
Secondly, when I copy and paste my codes from one file to another, it all gets jumbled up and almost impossible to rectify as my cursor wont even let me type.
I would appreciate any help with this as I have struggled for months now with no success and this is my last resort. I look forward to your kind help. Thanks

VSCode annoying problem focus behavior, keeps jumping to a problem

Last Edit:
It appears I've had an F8 key being pressed non-stop, and it seems to be a shortcut for "Go to Next Error or Warning".
I've wrote a piece of code, it has an error which I'm aware of. Specifically, I'm trying to run a function which doesn't exist yet:
All good, I'm glad it is telling me there's a problem, but... I wish to keep writing stuff in the same file and I simply can't. Every so often the GUI keeps sending the caret (the place where my next piece of text will be written) to the beginning of the problematic piece of code. Simply speaking, I can't keep doing anything until I resolve the problem, since it forcefully intrudes my every action. Even more than that! When I go to a different file, with means of fixing the problem and adding the missing function, it once again interrupts me and forcefully takes me back to the problematic file to show me that there's a problem (??!?!?!). Closing it with "Esc" only closes it once, but it keeps on returning every several seconds.
I don't think it was like that just a week ago, and I didn't install any new plugin since then. I'm currently using the last version, 1.58.2.
How do I stop this work-flow-intruding behavior?
Edit:
I've kept on working for some time and it turns out the issue is much bigger than that. Whenever I type a name of some property, half way through some wild problem would jump and tell me "Cannot find name 'quar'. Did you mean 'quarter'?". The issue is basically the time delay of the problem checks, it's non-existent. It's also too intrusive, moving the caret and jumping between files to show me the existing problems. It's very recent, it didn't happen earlier this week. I've tried disabling different plugins I have and they're not the cause.
This is not exactly your issue, but could be related to what you are experiencing: https://github.com/microsoft/vscode/issues/68776
Try disabling the Outline Explorer and see what happens then.
Furthermore, see if disabling autosave improves anything.

output of Dr. Racket algebraic stepper to file

During debugging the stepper breaks down after reaching the bug. And stepping towards the bug every time takes at least a hundred clicks. So doing that every time seems senseless. Is there a way to save all the evaluation steps that you see in the stepper to a file?
Stepper's author here (yes, you can stick pins in a wax doll of me): Okay, before I answer your actual question, I want to let you know: you can jump to the end of the stepping sequence in about one click by clicking the "jump to end" button, available in Racket 7.6 and later. Or maybe 7.5. Your question suggests you aren't familiar with this operation, possibly because you're running an older version.
To answer your actual question: there is code in place to allow dumping the stepper's output to a file. I strongly suspect that it's not in a shape that would make it terribly useful for you, but it probably wouldn't be hard to add this as a menu option for the stepper's operation.
Before doing that, though: does "jump to end" not solve your problem?
EDIT: Ah! it sounds like jumping to the end makes the stepper non-functional. I'd love to be able to reproduce that, if you can tell me how.

Anyway to get rid of this view in VSCode IDE?

There's a little column to the right of your code window which shows all of your code at a huge glance. It's kinda handy to click to jump to a certain portion if you have a large file....ultimately, especially when I have 2 windows side by side, it takes up a lot of useful space. Anyways I can remove this? (Having a hard time researching it because I don't even know what it's called)
Okay...I tried some different search terms and found this article.
https://stackoverflow.com/a/44774811/8887398
It's called "minimap".

How to hide the VSCode update dialog

I get the VSCode update dialog a bit too often and do not want to click it away anymore. Is there a way to make sure that it is never displayed anymore?
Press ESC.
VS Code is all about high-speed workflow and not having to interact with anything except your code via keyboard. Everything has key chords, e.g. CTRL-P and CTRL-SHIFT-P. So having to stop what I'm doing, go to the mouse, and dismiss this popup, whenever a background task feels like completing (and not even really then, because the popup actually appears some short time later) just so I can get visual confirmation of which file I'm currently coding in, to refocus my work after being distracted by the same popup, is really awkward. They are in a stupid location and don't even fade away after time like well-behaved toasts.
That said, I think that's really two parts; the distraction, and relatively high workflow cost to dismiss.
It helped me a lot to learn that it can be dismissed quickly and easily with the ESC key. The other half the problem I still haven't solved, but hope that helps you.