When I click the 'Interactive SQL' button on my IBConsole, no window appears.
It is listed when I then click the 'active windows' button, but selecting it and clicking 'Switch to' does nothing.
Is there a known cause for this, or logging somewhere on my system?
It turns out the problem was caused by a corrupted IBConsole.xml settings file, located in C:\Users\myname\AppData\Roaming\Embarcadero\InterBase
The cause is unknown to me, but I replaced the file with a colleague's copy, and after that my Interactive SQL window functioned as normal.
Related
VSCode often suggests symbols as you type e.g. a variable or field name. When the correct variable name is suggested, usually I can press return to paste the suggestion.
This used to work all the time, now it only works often. And it's driving my crazy. Now, sometimes, when I press return, it actually enters a return character instead of the selected symbol.
Any ideas how to troubleshoot?
Relevant info:
I'm writing rust, with the popular rust-anayzer extension.
I'm on Ubuntu 22.04 LTS
Not sure what I should google for, or where to look for potential problems.
I had this issue before.
One possible reason why VSCode is occasionally inserting a return character instead of the selected symbol is due to conflicts with keyboard shortcuts. It's possible that another application or system function is also using the same keyboard shortcut as the "Enter" key, causing it to be triggered unexpectedly.
I solved it by resetting VSCode settings to their default values.
You can do this by going to the VSCode "Settings" page (File > Preferences > Settings) and clicking the "Open Settings (JSON)" button at the top right. Then, delete all the contents of the JSON file and save it. This will reset all your VSCode settings to their default values.
I specifically only want console out for Building my code, which is primarily C++. Every search for this leads me to configuring Run Configuration(s) to output the console. I'm not trying to RUN my program, just want the additional detail from console-out when I build and get warnings, some of which I'm not getting filepath info in the "Problems" window. Thanks!
This might already be set up by default. It was for me, once I found the solution I realized this. Check if the following filename exists:
<workspace_name>/.metadata/.plugins/org.eclipse.cdt.ui/global-build.log
If it's there, you might already be setup with build output saved to a file. It should be saved in this file. If you don't have this file, and/or you want to change the file location, do the following: click Window context menu->Preferences. Expand the triangle next to C/C++ on the left sidebar, then under that sub-menu, expand the triangle next to the Build menu, then click Logging. Inside the Logging window, ensure the checkbox next to Enable global build logging is checked, then click the Change... button next to the Log file location text box and select your log file. (In Linux, this part may not be so easy if you don't have a log file already touched. In this case, navigate to the directory in which you want to save your log file, then click the button in the top left that looks like a piece of paper with a pencil over it (when hovering over this button it says "Type a file name"), and then type the name of the log file you wish to use. Click Ok.) Then in the Preferences window, click Apply and/or Ok. Next time you build, this log file should be populated automatically with your Console output.
Sometimes when closing vscode, or a tab therein, I get a dialogue asking "Do you want to save the changes you made to filename?" However, the unsaved edits are actually from a previous session that was closed without such a query, probably when turning off the computer, so I can't remember if it was meaningful edits, or maybe just an accidental key-press, like a shortcut gone wrong; and doing undo to revisit the last edits doesn't work either.
My question: How can I see the diff between the saved version of a file, and the version in the editor window? I think it would be nicest just to have a "show diff" option in the dialogue, but for now I'm also happy with a command line diff command.
I'm using ubuntu 20.04.
I'm using VSCode version 1.52.1 on MacOS and I had a similar problem that may not be the same problem, but I'm guessing it will work for you as well.
When you're in the Explorer view, in the upper left part of Explorer you have your "Open Editors." If that shows a dot to the left indicating that the buffer has changes in it, you can right click the file name and select "Compare with Saved." This will open another buffer to the side that will show you any unsaved changes.
To get rid of that window (it took me a bit to figure this out I'm sorry to say!), you can click the 'X' to the left of the extra buffer in "Open Editors."
Hope this works for you!
A few bright notes for the keyboard players out there:
The command you are asking about has a default shortcut. Unless you've applied a keyboard map extension, the Ctrl+Kd arpeggio opens the very same diff view between the active and saved versions of the current file. The default shortcut to close an editor tab (be it the diff or a file or anything at all) is Ctrl+W.
The command, like any command in VSCode, is also accessible via the Ctrl+Shift+P command dropdown (on Linux, F1 opens it too). Start typing e.g. compa sav (it saves your keyboard wear and tear to shorten words to a prefix which is unambiguous enough), and the list will shrink dynamically to just a few commands. Yours is File: Compare Active File with Saved. When it's close to the top enough, navigate the list of commands with the down arrow and execute it with Enter. As a bonus, you may click on the little gear to the right of the command currently highlighted in the list and redefine its shortcut, if you use it very often and prefer a chord shortcut to the default arpeggio one. Sorry, there does not seem to be a shortcut in lieu of the gear click. If there is, please let me know!
But if you really, really want to right-click on the filename in the Open Editors view of the Explorer sidebar, you can open that view directly with, you guessed it, a shortcut: Ctrl+Ke. And if you change your mind on a dime right at this moment, or realize that you in fact never had a mouse to do the right-click in the first place, use Shift+F10 to drop down the "right-click menu", properly called the context menu, which you navigate with arrows and execute with Enter (that's kinda a common theme, as you probably noticed). This works mostly anywhere the right-click does.
While in the Open Editors view, to switch to an editor file tab, move the selection to the desired file. Press Space to bring the file into view but stay in the Open Editors view, or Enter to bring the file into view and shift the keyboard focus to it. Pressing Ctrl+Shift+E brings focus back to the editor from any view in the Explorer sidebar. The same shortcut moves focus to the Explorer sidebar from the editor.
Happy ♬ k'boarding ♬!
ctrl+shift+P (or command+shift+P on mac) and fuzzy search for "compare changes with saved files"
I want a save button that I can click with the mouse, but when I focus on a SQL editor page and file and do >Window >Customise Perspective >Edit actions, it's greyed out and says "Save (Ctrl+S' command cannot be made visible in this dialog.
DBeaver Community v6.0.5.2019... Windows 10 Enterprise 2016
It's just a simple thing so I don't have to keep switching between keyboard and mouse.
This is some months old so it may not be relevant for you, but this may help others (I was brought here as the lone google search result and had to keep poking around until I found it)
anyway, in DBeaver menu select Window>Preferences>DBeaver>Editors there should be a checkbox for 'Show Edit toolbar'. Check that and apply and close. Exit and restart DBeaver and it should have buttons for save/undo/etc. If it still does not, go to Window>Customize Perspective and the 'Edit actions' toolbar items should no longer be unselectable so you should be able to add them to the toolbar from there.
I am using eclipse on Ubuntu. When there is log being shown in console and I am moving cursor up or down in JAVA file to see the code, the cursor shifts itself to the console log and and I am having problem to investigate my code. My cursor shifts to console log even if I disable the console view from windows-> Show View. Is there any way that I am not forced to see the console.
I just got rid of this issue. Right click in console window, select preferences and then unchecked the checkBox "show when program writes to standard out" and also unchecked the checkBox "show when program writes to standard error".