Sometimes, after I search something (or accidentally click "search for definition), mostly in PHP files, the VS starts never-ending (running blue line) search (and I hear CPU loading during that time). However, I can't cancel that, with neither Esc and Ctrl+Shift+F > Stop. What I should do?
I even hear how my CPU is loaded during that period and doesn't stop...
Well, I haven't found other workaround till date, than :
Right Click on any $variable name and select Peek to definition and VS stops loading.
Related
I am using Eclipse and I am coding java. I really like the "Smart Caret" option for the Home and End buttons since it allows you to go the start and end of a line but not past any whitespaces. Also the Home key will take you to the start of a comment, rather than the start of the line. And you can cycle through different positions with these keys. And this is how the editor was by default, from installation.
However one thing that has happened a few times now is that when I am writing code in the editor, this functionality just vanishes. It is seemingly random when it happens and the weirdest part, I think, is that it is file specific. So all of a sudden when I am writing, the Home and End keys start taking me to the very start and end of the line I am on. It is as if I am accidentally pressing some hotkey to disable these Smart Carets for the specific file.
It does not help to disable and re-enable the Smart Caret option in Preferences. And beyond that I do not really know what to do. Is this a bug? It is incredibly annoying when it happens. Being used to things working one way, then having them spontaneously change and then again having them back to the default when I am editing a different file.
See further below for the original question.
I've used gdb for over a couple of decades, and after an update gdb started defeating c-x-b and preventing windows from being used to view things I wanted to see, while forcing bindings to buffers I didn't care to see. The fix seems to have broken tab completion for shells.
Ah, so how can I to stop gdb from taking control of the buffers/windows/frames layout without breaking something else?
;; fix 'feature' of broken gdb where it takes control of an
;; emacs window, and locks the user out from switching from it
;;
(defun set-window-undedicated-p (window flag)
"Never set window dedicated."
flag)
(advice-add 'set-window-dedicated-p :override #'set-window-undedicated-p)
--- problem in the original post --->
about a year back, after an update, file name completion windows in the shell stopped closing after the completion. I figured this behavior would go away on the next release .. but it never has.
hitting tab -- all good
after completion, then another ls with tab
I can repeat this process until my shell panel is all but crowded out, and emacs fills with completion panels that all contain additional views of the shell.
Is this some kind of new feature that can be turned off? Or is it, as seems more likely, a bug? (How can it have lived for so long!?). Is there a simple way without taking one's hands off the keyboard to, in general, close the completion window so that the screen looks like it did before hitting tab?
[I had to take out the more detailed descriptions of the images because with them, stack exchange complained of unformatted code and wouldn't take the post... there was not even a hint of code in them. Anyway, this should be good enough.]
When editing an expression in a Watch window, the delete key wipes the expression and leaves the VSCode in an unstable state.
Is it an issue or I'm missing something? If it's an issue it is unbelievable that nobody has noticed it so far (as if nobody uses the debugger).
This is so annoying that I'm considering switching back to Webstorm/Sublime.
More detailed steps to reproduce:
1. Start debugging session in any (backend or frontend) javascript app and set a breakpoint
After execution stops, add anything to the Watch window
Try editing the expression in the Watch window; use the 'delete' key while editing
Result: instead of a single letter being deleted, the whole expression is deleted from the Watch window, and the VSCode is left in a bad state which is reflected in all other expressions being greyed out, i.e. almost invisible
After launching with code --disable-extensions the same thing happens (while using a node.js application)
The expected behavior is that when pressed, the cursor jumps to the end of the word it's on.
From time to time, the combination will do absolutely nothing when pressed.
I tried checking if I have any shortcut set to this combination but there's none.
Anybody get this too? It doesn't happen too often, but when it happens once, it will not work again until I restart the computer.
I am developing using the PyDev plugin in Eclipse. My program uses several classes in several files. I usually run the program using the green "play" icon or using Control+F11. The only problem is that it will run the file, which is currently in "focus". Usually this is not the one containing the starting point of my application. As I run my program something like 200 times a day, this means that I need 200 extra click on the mouse and often forget about this.
Is there any way of setting the default file to launch?
Yes, change the launching to rerun the last launched, so Ctrl+F11 will launch the last one -- and use F9 to launch the one with focus -- See instructions and details at: http://pydev.org/manual_101_run.html
For me, the shortcut is Ctrl+Shift+F9. I don't think I've changed any keybindings, so its strange that it would be different from the official documentation.
Go to Run->Run History, and select the run that is your 'main' run. Now you should be able to use Ctrl-Shift+F9 from any other file to rerun your main. If it isn't Ctrl+Shift+F9 for you, look on the console window that should be at the bottom of your screen showing the stdout after every run. There is an icon on the top of it that has the green start arrow with a yellow arrow underneath it pointing to the right. That is the command to relaunch with the same configuration. If you hover over that, it should tell you the keyboard shortcut you need.