I am using the Spyder which comes inside the Anaconda3 IDE. I found the Ipython Console here is very helpful in the sense that when I type in a function, the arguments and default values will come up automatically. When I used to use Jupyter notebook, there is no such functionality.
What I mean is like this:
When you just typed the function name and a left bracket, the Arguments help window just pop up.
However, my problem is that, sometimes, in the middle of this function completion, in this example, I finished typing bottom=a, but I forgot what should be passed to width, so let's say I pressed Alt+Tab in windows system to check it out in a PDF. Then I press Alt+Tab to switch back to Ipython console, but now the Arguments help window just dispeared.
My question is is there any shortcuts to make the it appear again? Typically, I just have to clear all my arguments, and go back to type the left bracket another time to make it appear to help me specify the arguments, but this is unkind.
Press shift+tab to get the argument window back.
Press ctrl+space to get the function window which appears after a dot (e.g. after "plt.").
Use the object inspector (renamed to the help window in later versions of Spyder). It gives the information you're looking for and much more!
In the main window, click on Tools -> Preferences -> Help -> Automatic connections -> check "IPython Console" and any others you'd like to use.
Go to the help tab which is defaulted to the top right of the main Spyder gui.
Click the gear on the top right of the help window and select "Rich Text"
Set the "Source" to "Console" on the upper left side of the "Help" tab.
In your IPython console, type plt.barh(.
Note the lock button next to the gear. This will lock the help window to the function while you continue to write code.
Related
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"
As you can see from the image above, every time I put my cursor to the end of curly brace, the related code (i.e. the one appeared on the left side of the image) pops up. This function is helpful when you want to see the beginning of the code snippet, but I don't want it to pop up all the time.
Does anyone know how to turn off this function in NetBeans IDE?
Go to Tools -> Options -> Editor and select General tab and uncheck Show tooltips. Click Apply and Ok.
The MATLAB GUI normally (for me) has 4 tabs in the upper left - Home, Plots, Apps and (I think) Editor. However the editor tab has disappeared and I cannot find documentation how to turn it back on. I tried the Layout->Default but that just arranges all the visible windows and doesn't re-enable to missing editor.
Does anyone know how to turn this back on?
Type edit in the command window.
Unfortunately you are right, there is no 'Editor' option in the Layout panel of Matlab's interface, and for obscure reasons it's not present in the default layout.
OK, I've checked Ratbert's answer as he got here before me but Mathworks tells me it disappears any time you're not actually editing any code. If that happens their answer was to just click on the New Script button. Doing that worked for me. Typing edit in the command window is (I think) doing the same thing.
Thanks!
For anyone that finds this thread at a later date I eventually debugged the root cause of this problem as a mouse that was failing. When attempting to close the open variables part of the GUI, when clicking the X in the upper left, the mouse was generating two clicks instead of one. The first closed the variables GUI, the second closed the editing GUI. Purchasing a new mouse resulted in no longer seeing the problem at all.
in matlab command window, go on top right triagle and click, a drop down list will appear, select undock editor
I use ctrl-backspace in MATLAB Editor (MATLAB 2015a) to remove the previous word, but it doesn't work in the command window. I tried changing it in Preferences -> Keyboard -> Shortcuts, but there doesn't seem to be the option to bind it to "Remove Previous Word" in the Command Window. In the attached image, you can see that it is set to work in the MATLAB Editor, but when clicking the down-arrow next to where it says MATLAB Editor, it does not show any other options.
This seems like a very common shortcut used by many Windows programs, and it's strange that it should only be allowed in the editor. If it's actually not allowed, why? Is there a workaround?
I tried to post an image of this but stack overflow says I'm not yet cool enough.
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).