Is there any way to reopen closed tabs on DataGrip? not recently closed :)
If you are about consoles: go to Files tool window, expand Scratches and Consoles -> Database Consoles -> Data source name -> you'll find here all consoles ever created and modified.
Ctrl+E or Cmd+E opens up a window with a list of recent files. Click on any to open it.
Related
Is it possible to close a Project without closing Xcode? if so, how?
The reason for this is that when I open another project, it leaves the old one open and then opens the new project in a different desktop on El Capitan 10.11
One option described in the comments is not the most convenient.
You have other appropriate options:
1. If you have playground opened in the Xcode you can click "File" from the left top -> select "Close <>". You will see that only you playground was closed but Xcode window not.
You can also close the whole Xcode windows. From "File" select "Close playground".
Last one is to close the Xcode, just select "File" -> "Close window"
The same is for projects: "Close project" should be clicked.
Please fin the information below:
https://developer.apple.com/library/ios/documentation/ToolsLanguages/Conceptual/Xcode_Overview/CreatingProjects.html
Hope this will somehow clarify
I am a long time Visual Studio and Eclipse user, and now that I'm developing iPhone applications, I've need to use XCode 6. Does anyone know how to do these two really (seemingly) easy things in XCode 6:
Close an open file: There's no apparent button to close a source file once you've opened it. So, now I have a ton of open files that I don't know how to close.
Use tabs: If I have a bunch of files open, I've only been able to successfully switch between them by using the little left and right arrows by the file's breadcrumb.
Sorry for asking such a simple question, but my brain is wired in a completely different direction than Apple thinks it should be.
Close an open file: File > Close Window or File > Close Tab
Use tabs: File > New > Tab
This question already has answers here:
Close all tabs in Visual Studio
(6 answers)
Closed 9 years ago.
If I have say for example 20 tabs open in VS 2010.
Is there a shortcut to closing all of them instead of manually click 'X' for each one?
Try using ALT + W + L. This would help you to close all the open documents at once.
Please vote if it worked.
Window → Close All Documents.
I always bind this to Ctrl+Shift+W
Right click on one of the tabs, select "Close all but this" the manually close the last one.
you can right click on a tab ->Close all but this. This will close all tabs except the one you clicked. Then you can click the "x" for the last tab remaining.
You can assign your own keyboard shortcut on Window.CloseAllDocuments action in VS options. By default there is none.
I'm using Visual Studio 2010 and when I do a "Find in Files" the results are returned to the "Find Results 1" window which is docked below my code editor window.
Before, I would double click on one of the results in the Find Results window and the file I clicked on would open in the code editor panel.
The problem is now when I click on one of the results, it opens in the same panel as the Find Results window which happens to be much smaller than the code editor window which is annoying.
Does anyone know how to make it so that when I double click on the search results they open up in the code editor window again?
Thanks!
Click Window → Reset Window Layout
Works for VS2013 Update 4 and all newer versions, including VS2019.
I thought I had this problem but it was easily fixed by docking the Find Results window using the very bottom of the window position selectors.
The files open in the same position as the Find Results when the window is docked in the positions immediately next to the centre position.
This is also being discussed here:
VS2010 docks code windows in the wrong place
Go the same... irritating... I realized that this unwanted behavior happened only while the app was running in debug. After I stopped debugging, a new panel was created with this file open in it. If I opened new files, they would open in this new panel. If I close all files in this new panel, opening new files from the "Find In Files" open in the standard code editor window (as long as the app is not running).
I had this problem also. I experienced the problem in VS2013. I did not want to do "Window -> Reset Window Layout" because it seemed like that was going to do other stuff that I did not want it to do.
Here was my solution:
I noticed the problem in VS2013 in which I had project "A" open.
I opened another copy of VS2013 and opened project "B".
I closed the copy of VS2013 that was exhibiting the annoying behavior: project A.
I closed the copy of VS2013 that had project B open.
This saved the settings from the "good" copy.
Opened project A in VS2013 and all was well.
Obviously, the caveat is that this requires you notice the problem before you close VS2013. But if you do notice it in time, this is a pretty easy solution.
For those who do not want to dock their "Find Results", "Error List", "Output",... windows to the right, and for those the above answer which is Window->Reset Window Layout doesn't work: may be you are trying to dock wrong place! You should dock these windows to very bottom. Refer here: https://stackoverflow.com/a/2735726/6176317
For me, this was happening with a Visual Studio window containing an SQL file with the Window Split option active. If the cursor was in the top pane of the window, both Ctrl + F (Find) and Ctrl + H (Find & Replace) would cause the find control to appear in the other (main) Visual Studio window. Moving the SQL window into the main window just caused Find and Find & Replace to display the "Find in Files" dialog instead until another tab was selected.
The workaround was to place the cursor in the bottom pane which caused both Find and Find & Replace to work correctly in that pane of that window. Unfortunately as long as the Window Split is there, the bug is still there in the top pane.
This question already has answers here:
Preventing console window from closing on Visual Studio C/C++ Console application
(24 answers)
Closed 8 years ago.
I'm using Visual Studio 2010 and Windows 7 x64
The command prompt closes after exit, even though I used "Start without debug". Is there a setting somewhere that I can use?
You can simply press Ctrl+F5 instead of F5 to run the built code. Then it will prompt you to press any key to continue. Or you can use this line -> system("pause"); at the end of the code to make it wait until you press any key.
However, if you use the above line, system("pause"); and press Ctrl+F5 to run, it will prompt you twice!
Yes, in VS2010 they changed this behavior somewhy.
Open your project and navigate to the following menu: Project -> YourProjectName Properties -> Configuration Properties -> Linker -> System. There in the field SubSystem use the drop-down to select Console (/SUBSYSTEM:CONSOLE) and apply the change.
"Start without debugging" should do the right thing now.
Or, if you write in C++ or in C, put
system("pause");
at the end of your program, then you'll get "Press any key to continue..." even when running in debug mode.
What about Console.Readline();?
Add a Console.ReadKey call to your program to force it to wait for you to press a key before exiting.
You could open a command prompt, CD to the Debug or Release folder, and type the name of your exe. When I suggest this to people they think it is a lot of work, but here are the bare minimum clicks and keystrokes for this:
in Visual Studio, right click your project in Solution Explorer or the tab with the file name if you have a file in the solution open, and choose Open Containing Folder or Open in Windows Explorer
in the resulting Windows Explorer window, double-click your way to the folder with the exe
Shift-right-click in the background of the explorer window and choose Open Commmand Window here
type the first letter of your executable and press tab until the full name appears
press enter
I think that's 14 keystrokes and clicks (counting shift-right-click as two for example) which really isn't much. Once you have the command prompt, of course, running it again is just up-arrow, enter.