Enter Key in Find dialog makes new line instead of jumping to the first result - visual-studio-code

After hitting CTRL+F (or CMD+F) my find-dialog opens in the top right corner with focus on the input.
Usually, after I enter the search term, I hit enter to jump to the first result. Unexpectedly, this creates a new line in the search input.
I tried looking in the settings, but no luck. I remember that it wasn't that way when I first installed VS Code.
How can I solve this, so that it jumps to the first found result?

Related

How to start the search process in Visual Studio Code

I can see the search form panel in left side, but, how can I start the search process? there is a field to put the text that I am looking for, but I don't find a button or icon to press and start the search process, I don't want to try pressing the enter button because I don't know if pressing enter will search or it will replace (since there is also a "replace" field)
Regards
Enter will start the search, don't worry. If I remember correctly
Ctrl+alt+enter does the replacement for all and you also have to
confirm before the replacement – FreshD
thanks, I also noticed a small triangle to hide the replace field

VS Code search inside the editor without rollover

If I search inside the actual editor of VS Code without an match below the current line, VS Code rollover the search from the top of the page.
How can I disable this?
One thing you can do instead of disabling this (which I don't thing this is configurable) is to use ctrl+U. It's soft undo, moves the cursor back to it's previous location. This is particularly useful when you need to move down in a long file to copy a variable or function name and then go back to your original position. So when vscode goes to the top of the page, put the cursor there, and then press ctrl+U to go back to the previous line you where editing.

Eclipse - How to disable "direction" on find/replace dialog

In eclipse, when using the CTRL+F dialog, it is a bit annoying to search for some word in a file and having to select the direction you want to search (forward or backward) or having to put the cursor focus at the top of the file to search forward.
Is it possible to disable this direction option and search for words just like Chrome does? (when searching in Chrome, if you reach the last coincidence and press next again, it will go back to the first one immediately).
In the Find/Replace dialog in the section Options there is the checkbox Wrap search for that.
The Wrap search option of the Find/Replace dialog is also applied to the Find Next (Ctrl+K) command.
Alternatively, you can use Incremental Find (Ctrl+J) which is a Find without a dialog: in the Incremental Find mode the entered search string is displayed in the status bar and by hitting Ctrl+J again you go to the next match. On the last match you have to hit Ctrl+J twice to go to the first match.

Visual Studio Code: How not to show suggestions on space?

So anytime I type space it brings up suggestions, which causes problems when I type space at the end of a line (just because i like having a little space there. This way cursor is at some distance from code when i click at the end of a line, it's easier to see code, it's less cluttered), and press enter. It brings up suggestions menu and insert the first thing from there, while i just want to insert a new line character.
I also need it to show suggestions when I'm typing, but only when I type a non whitespace character, so I can't set it to not bring up suggestions on typing.
I also want to accept suggestions on enter, so I can't turn this off either.
So I'm stuck with wanting suggestions on typing, but not on space, is there a way to somehow exclude space from suggestion triggers?
You can customize how you want to display it, this feature is called IntelliSense.
Go to File > Preferences > Keyboard Shortcuts (MacOs Code > Preferences > Keyboard Shortcuts)
and you can set the new key on:
list.toggleExpand
notification.toggle
if you want advance settings, go to keybindings.json
more info:
https://code.visualstudio.com/docs/editor/intellisense
https://code.visualstudio.com/docs/getstarted/keybindings
I think i've found a solution: turn off Suggest on Trigger Characters option.
This way it doesn't bring up IntelliSense on space or dot or anything else, but it still brings it up when i'm typing ordinary characters

How can I go to the next Eclipse marker (e.g. build error) using the keyboard?

Suppose I make a method signature change that breaks several callers, and I want to review the call sites manually to update them.
Once I change the signature, my "Problems" view shows, say, a dozen errors.
What keys can I hit to navigate through them while leaving the keyboard focus in the editor for fast fixups?
(It's been a while, but I think the Visual Studio equivalent is F8.)
Note that this question does not duplicate Eclipse: How to go to a error using only the keyboard (keyboard-shortcut)?, as that one seeks to navigate only between markers in the current file. In this case, I want to go to the next error regardless of which file it's in.
("Marker" is the general Eclipse term for errors, warnings, etc.)
The best I've come up with so far is Ctrl + F7 to flip to the Problems view, then ↓ to pick the topmost error, then Enter to go to it (which returns focus to the editor).
Here's a way to move to the next error, regardless of editor, in one keystroke. It's not perfect, but it works until it's fixed in Eclipse.
Open a "Markers" view. Click the down arrow at the top right, and choose "Configure Contents". Uncheck the show all box, and create the view to show only the problems you want to see. You'll probably want to deselect "warnings" and "errors" as well. Save it.
Click the same "Markers" down arrow, and choose "Group By". Select "None". This is important because you don't want the parent tree level nodes to show, otherwise some of your "next" actions will take you to those, which don't represent an error.
In Eclipse -> preferences -> keys, search for "Markers". If there is not a keystroke bound to the Markers view, create one. I use Ctrl + Shift + M
Get a keyboard hotkey tool like AutoHotKey (for PC's) or iKey for the Mac. I'm using iKey, but there are plenty of other Mac tools you can use. In your hotkey tool, define an action for the keystroke you want to use for "next error". I chose the standard CMD + .
For that keystroke/action in your hotkey tool, generate 3 keystrokes in the following order:
Ctrl + Shift + M
Down arrow
Enter
Of course, you'll want to change the first one to whatever you picked for yours. You'll probably want to restrict that action to be executed only when Eclipse is the current application.
Save that, create some compile errors, and test it.
Try Ctrl + 3 for Quick access popup window.
If the "Markers view" is not already visible, then type in "markers", in the searchbox on the popup window. Once you have selected it, it should stay available, when you press Ctrl + 3 the next time around.
I just had the same problem, after refactoring some parts of code. I had a lot of errors in different files and i had to go through all of those.
I used the following solution:
Mark all (relevant) entries in the Problems view.
To do this switch to the Problems view using Ctrl+F7 and select the entries with Shift+↓/↑
You can also select all entries using Ctrl+A
Open the marked errors by pressing ↵.
Every file containing at least one marked error will be opened.
The cursor will automatically select one error/file, as if you open only this specific entry
Fix the errors in the opened file.
Here you can use Ctrl+. to navigate to next error inside this file
Close the file using Ctrl+W when your done.
Eclipse will automatically focus the next file and you can go back to step 3
In my case this solution was much faster then switching to the Problems view each time.
There's an Eclipse bug entered for this that has an attachment that looks like it does what you want.
You could use AutoHotkey:
save the mouse position, send a mouse event to click on the arrow in CDT console and then return the mouse back to it's original location. Record the mouse coords with window spy or use autohotkey's search by image function (first capture the images of two arrows with printscreen into bitmaps).