Often times I want to delete a highlighted code or lines, the habit comes from other languages like Java, C++: I would high light the code that I want to delete, then hit the delete key. But in Xcode when I high light, let us say "Dictionary", it would pop up a new frame which tells me the API or something else, and Xcode would switch focus onto the new frame and don't respond to the delete key like in the link above.
What do I do to get this fixed, so that I can highlight something and hit delete key to delete it, or is there a better way to delete stuffs in Xcode?
That's Quick Help. The problem is that you held down the Option key when clicking on the word. Don't do that.
If you have a recent mac or an external Apple trackpad, try just tapping twice instead of pressing.
It seems to me like you're pressing too hard, which the trackpad can detect since it has "force touch", and it shows information about what you are pressing.
Related
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.
I have no idea what happened but when I woke up this morning to start working, my selection + middle mouse button no longer pastes the selection.
This has always worked prior to today and the only thing I changed was added a time stamp in my C/Program Files/Git/etc/profile.d/git-prompt.sh. Unfortunately I did not check if the paste was working prior to this change, but I've since reverted it, thinking it might be the cause. Still nothing.
If I enable paste on the right mouse button from the options window, it works. Still, middle mouse click does nothing even though it is enabled and selected. See the screenshot
Any idea what may have happened or what I need to change to get the behavior to return? I can deal with the right click pasting, but muscle memory and working in Linux has me conditioned to use the middle mouse wheel click, so I will begrudgingly.
There are lots of "How to enable selection paste in Git Bash" I've found, but they all point to updating the options like shown in the screenshot and are not one bit helpful. Please do not mark this as a duplicate.
Thank you.
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.
I have to use Atmel Studio for a project and I'm using
the memory window very often, to look on specific data Segments of the microcontroller.
Unfortunately It's very hard to keep track of specific lines in this window, looking like this:
especially switching between multiple locations. Is there a way to mark specific lines, maybe with a background color, or anything like that? I couldn't find a feature like that.
If I understand you correctly, I can try to give you my decision. When you move the cursor over a segment of memory, a cell with the segment value pops up. If you click on the pin button, you fix the cell, and you will can add your comments to the cell.
P.S.: Sorry for my English.
Screen
You can also Hexplorer. This is specifical comfortable .hex editor.
I ask if there is any way to scroll beyond the last line in xcode, because I always end up pressing a lot of enters to the end of my files, so that I don't have to always type my code at the bottom of my window.
I have skimmed through the properties panel of XCode, and had a look at this forum. So far the answer looks negative, but I kept my hopes up. :)
Any ideas for tricking XCode to scroll beyond the last line? (I have XCode 4.5.2)
There is now a plugin for that !
Have a look at SCXcodeEditorInset !
Dont think there is a way to do this but if you are trying to edit the buttom of the code while having it near the top of your display, you can click the middle view button in xcode to bring up the console/watcher and then drag that up to the desirable spot. This does decrease the overall space of your editor but can sometimes be useful if you prefer this or just need to do that temporarily
What I do is, When you finished typing at the bottom, before you go to top, type some unnecessary code "asdf" as error then go where you want. you can come back clicking on top right red error panel.