There's this one issue with Rstudio that has been bothering me for a long while now and I cannot find a solution.
I like to use a lot of shortcuts and move around the editor with arrow keys and also scroll the editor using Ctrl + arrow shorts. The issue is that if the script contains a user defined function and I press Ctrl+Up/Down the cursor jumps to that function even if it's nowhere near. Like sometimes hundreds of lines. EXTREMELY ANNOYING!!! And I have looked through shortcuts and this is the only thing I have found:
There are no more different Ctrl+Up/Down shorts. So it doesn't seem to be a multi mapping issue. Also if I change this mapping to something else the annoying jumping still continues. I just want it to stop! Can anybody help? Doesn't it annoy anyone else?
The behaviour of RStudio where Ctrl+Up and Ctrl+Down step the cursor between function definitions is not configurable and cannot be changed. Oddly, the same pair of keystrokes were chosen to move the scroll bar.
Your only option to avoid the conflict is to redefine the scroll up and scroll down keystrokes to something else (e.g. F8/F9 or something) so that they not longer conflict with this hardcoded option. You can then control the scroll bar using the keystrokes you have chosen without it conflicting with the behaviour where it steps between functions.
If you find you have accidentally navigated to a function you didn't want using Ctrl+Down, you can return the cursor to where it was using the "Source Navigate Back" keystroke which defaults to Ctrl+F9.
IMO this is clearly a bug in RStudio. I would report it to them and hope that it is fixed for a future version.
Related
I wonder if I'm doing something to make it not work, but simply put after tapping cmmd + shift + O or going to File >> Open quickly the option doesn't show up. It's like I did nothing.
Wondering if this is a known Xcode bug or if I'm doing something.
I'm using Xcode 10.1
You probably have more than one monitor connected.
This is something that confused me a lot of times as well; the quick search prompt will remember its position (you can drag it around) even on secondary monitors.
For what is worth, in my opinion, that field should always be presented on the current (in focus) editor.
In Visual Studio 2013, is it possible to change the keyboard shortcut for switching the overload on the Parameter Info popup to something other than up and down arrows?
For example, when you type:
System.Text.RegularExpressions.Regex.Matches(
A little box pops up telling you about overload 1 of 3 for that method. Pressing the down arrow will go to 2 of 3 etc. As a point of fact, the up and down arrows already serve the nifty function of moving the cursor. When that box is visible, you have to hit escape to get the up and down arrows back to their normal behavior.
My question is this, can you change the Parameter Info box up + down keyboard shortcuts to be something else, like control up or down?
I did notice that the left and right arrow keys might be a bit better than the escape key, but I'd still prefer to remap the up and down behavior so they can make the box go away.
I realized how much time (and hand movement) I spend hitting the escape and figured it'd be worth asking. I do not think this falls under the category of the keyboard shortcuts that you can remap from the Options screen.
Many thanks!
I worked with Resharper 5 before and when I have a problem in code (for example unsuitable space around a parentheses), I used Alt+Enter and Resharper fixed the problem. But in V6, this doesn't fix the problem, it generate a supress statement! What should I do?
Here is more detail:
1- I have this line in my code:
if (this.RequestClose!= null)
Resharper draw a blue line under it and warn that the space around != is not correct.
In Resharper 5, I could press Alt+Entyer two times to fix the spacing problem. In Resharper 6, if I press Alt + Enter two times on this line, nothing happens.
2- I have this line in my code:
var view = new AddressDetailView();
view.DataContext = viewModel;
Resharper suggests using object initializer, but pressing Alt+Enter twice doesn't fix it.
Resharper 6.1 solved this problem!
Did you actually look at the menu item you're selecting? (I'm guessing not, since your question includes no mention of what's in the menu.) Alt+Enter brings up a pop-up menu, you know. By pressing Alt+Enter twice, you're just selecting the first item in that menu.
ReSharper 6 has new features, therefore it has more options in the list, therefore the order is sometimes different. The quick fixes are almost certainly still working; it's just that the first quick-fix in the list isn't always the same one as in R#5.
The solution is simple: read what's on the screen before you select it. If the quick-fix you want isn't the first in the list, then cursor to the one you want before you hit Enter.
(There's never been a ReSharper version where it's safe to always accept the first item in the menu -- the options change depending on whether R#'s background scanning has completed yet or not. If you've been blindly accepting the first item every time, I'm surprised you haven't gotten bitten before now.)
I could not find any way to fix this problem and decided to use R# 5.1 with Style cope instead.
I'm in VS2010, on a breakpoint. How can I cause a datatip to be displayed for a given variable/expression w/o using my mouse to hover it?
That can't be done, exactly, but you can get the same result by selecting the variable you want to watch (using ReSharper's Ctrl + Alt + →/← can speed this up), and pressing Shift + F9, which will raise "QuickWatch" modal window with the datatip contained within.
If you prefer, you can also go into Options->Keyboard and bind the Debug.AddWatch to a different keyboard shortcut, and use that instead of Shift + F9, and then your variable data will persist in the Watch window so you can come back to it later (as suggested here)
You can also do this by opening the command window (Ctrl + Alt + A) and typing Debug.AddWatch variable_name.
While you can pin multiple windows in VS it will be a somewhat cumbersome experience and you will have to over it.
I personally use visual studio plugin called Oz Code, that automatically annotates all the local variables and intermediate results so I don't have to chose which variables to pinpoint.
The results looks something like this:
Will adding a watch not be suitable? When you hit your breakpoint the relevant details of the variable will be shown in the watch window.
Perhaps I have misunderstood what you're trying to achieve here!
You can click the 'pin' icon to force any datatip to stay open, and it will update to the current contents when you hit the breakpoint.
I don't know of a way to open a specified tip without pinning it, however.
The Locals and Autos windows might be helpful as they show all local variables, (they even show the return value of called functions!).
Note however that they show directly only variables in scope, so if you need a detail property that it is not yet menotioned in the code you can drilldown using the →/← keys, however if it is already mentioned in the code in the current scope then you should be able to see it directly in the Autos window.
The problem is exactly as asked in the question title.
When I'm typing in the text editor and referencing a public method that has a long signature (lots of parameters, usually 10 or more) the intellisense just stops working. It will sometimes flicker; other times it will not show at all.
Only seen this happen with C#, but I don't use anything else. It might happen in VB too. Don't know.
Anyone else seeing this?
I've Googled for an hour but can't seem to iron it out. I've restarted VS, rebooted the machine, enabled/disabled intellisense in Tools -> Options. NOTHING works.
You can hit CTRL Shift Spacebar to bring it back up.
Even better, Ctrl Shift Alt + C copies it to the clipboard.
Then Ctrl Shift Alt + P pastes it. Handy for templates.
I've discovered one cause for the problem.
If the method is at the top of the screen, it pops downwards.
If the method is at the bottom of the screen is pops upwards.
However in the middle of the screen if it's too big to go either way it gets confused - flickers or just won't open.
Unfortunately, no matter what I do I can't seem to get it to display more than 37 parameters...
Found a partial solution - change the font size
Was supposedly scheduled to be fixed in SP1...
http://social.msdn.microsoft.com/Forums/en/vseditor/thread/e2f06f24-0b68-48f3-a8b3-c31948f6e168