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 am trying to select a column in Excel such that the selected rows are all rows where data exists. I normally can do this by clicking on the first cell where data exists and then holding down Shift+Ctrl+Down arrow. This selects all the data in the column from the current cell to the last row of data.
However, when I try to do anything like this on my MAC it does something entirely different. Instead it zooms out on the MAC itself.
By default, Control + Down is assigned to Mission Control. Shift is a common modifier that slows down animations on Mac. If you're okay with removing the Mac shortcut, you can do that in System Preferences.
In System Preferences, click "Mission Control" and find the shortcut labeled "Application Windows". If you change or disable it, the problem should go away.
Command + Ctrl + (UP/Down/Left/Right) worked for me
I had the exact same problem. Try Ctrl + Command + Shift + Down.
I'm using Qt Creator 3.1.1 with FakeVim mode enabled.
When the completion popup appears with the desired function already as the first one, I have to press Enter twice in order to insert text. The same thing happens when I want to insert more letters before hitting Enter. I have to press first key twice, than everything goes as expected (following keys require single presses, Enter too).
ex. I entered avform and the popup appeared. If I want the first tooltip AVFormatContext i press Enter twice. If I want avformat_smthing I need to press aaform_ cause the first a will like change mode back to insert (but not really as I'm still in INSERT mode).
I wonder if anybody stumbled upon similar problem/inconvenience, and what can I do to change QtCreator behavior.
It seems like it's a known bug, and it hasn't been fixed yet. It only appears in newer versions of Qt-creator (>2.8.1). Partial fix is to disable autocompletion or unmark Pass keys in insert mode but both options have side effects (ex.Ctrl+N opens completion popup, but the text doesn't get inserted).
Link to: Issue on BugTracker for curious.
I understand that Mac has some Emacs keybindings enabled by default (e.g. Ctrl+A move to beginning of line etc.). If I open TextEdit for example I can navigate like in Emacs.
But when I try Alt+F or Alt+b for move to next word or last word it does not work. It prints out ƒ and ∫ instead.
Is there a way to jump words instead?
I think that I did not tinker with the keybindings and I use the US layout on a german keyboard.
If you want to re-enable them for the terminal
Terminal -> Preferences -> Keyboard
Check 'Use Option as Meta key'
my iTerm2 version is 3.1.6, profile -> keys -> set Esc+
Maybe one of these helps? (I don't use OSX myself, so I can't test anything).
http://blog.sensible.io/2012/10/19/mac-os-x-emacs-style-keybindings-everywhere.html
http://aufflick.com/blog/2006/01/10/emacs-keybindings-everywhere
Summary from first URL:
Create file ~/Library/Keybindings/DefaultKeyBinding.dict with the following content and restart all apps.
{
"~d" = "deleteWordForward:";
"^w" = "deleteWordBackward:";
"~f" = "moveWordForward:";
"~b" = "moveWordBackward:";
}
I'm a little confused if you're talking about the keys (within different apps on OS X) or specifically Emacs. On OS X the standard keys you would use to jump between words is:
option/alt + Left Arrow or Right Arrow
If it's specific to Emacs for OS X:
For Terminal.app, starting from Snow Leopard: Go to Preferences > Settings > Keyboard > Use option as meta key.
For iTerm: Go to Manage Profiles > Keyboard profiles > (your profile) > Option Key as…
If you want to use Option key for both international characters and
Meta key in Emacs, see info below for iTerm 0.10.x patch and/or binary.
Alt-b and Alt-f for navigating by word also works for your shell now.
UPDATE: The link the original website providing the patch is no longer online, however I was able to retrieve the cached information from the archive.org:
OSX + terminal + Meta key + national characters
Quite a mix, right? If you’re user of one of those keyboard layouts that have hidden some non-ISO1 characters under Option-key shortcuts and you use command line – read on, I might have a treat for you.
As it stands today, if you’re OSX user, and would like to use your Option (Alt) keys for both national characters and Meta-* shortcuts, you’re in for an unpleasant surprise – you can’t. It’s one or the other: both iTerm and Terminal.app allow you to flip between Option keys role, but neither of them allows you to use Option for both. Under Linux, it’s customary to use left Alt for Meta-* and right Alt for any national characters you might require. Same goes for Windows. Of course you can just train yourself in using ESC key in a prefix manner, but that’s avoiding the real problem.
Getting annoyed by this state of things, and faced with some Emacs usage, I decided to take advantage of the fact that iTerm is opensource software, and see if I can make a tiny change, to cater for my needs. Surely enough, after ~25 minutes I got a trivial patch: just changed the mask that iTerm uses for detecting that Option key is pressed down. It took few hours and 5 chapters of Cocoa book, to turn that into fully-fledged option in Keyboard Profiles section of iTerm. This was my first foray into lands of Objective C; while I came back victorious, I don’t see myself writing anything bigger in Objective C in nearest future.
Here’s the meat: ( https://sourceforge.net/p/iterm/patches/44/ )
“right Option is Normal” patch;
full patch allows you to pick which keys should be treated as Meta (both, only left, only right);
The patches were made against 0.10.x branch, at revision
1871.
Once you have the binary, launch it and go to Bookmarks > Manage profiles > Keyboard profiles. If you select a keyboard profile, you should see a new dropdown at the bottom of the keybindings list.
The options should be pretty much self-explanatory. The configuration shown above is the one I’m using — this way I get all Meta-* shortcuts with my left Option key, and all Polish characters with right Option key. Which is the way it Should Be™ :)
I haven’t heard from iTerm authors yet, so I have no idea whether this patch is going to merged upstream or not. I’ve been using my patched version for almost week and a half now, and nothing major exploded. Yes, iTerm is slower to redraw the screen on larger terminals (say, 130×80), but there are certain features (like 256 colors support) that make up for that.
more info: http://www.emacswiki.org/emacs/EmacsForMacOS
On iTerm2 3.0.15, go to:
Preferences -> Default -> Keys tab ->"Left option() key acts as:"
and change the value to:
+Esc
Solved this at the OS level as follows,
⟶ System preferences
⟶ Keyboard
⟶ Input Sources Tab
⟶ + at bottom left
⟶ Others in the left panel
⟶ add and select Unicode Hex Input from right panel
✓ Mac no longer prints anything on alt+letter|number
✓ enter unicode characters via alt+[code]
✅ the OS does not grab alt key shortcuts!
You should use KeyRemap4MacBook. In the Emacs Mode section, you will find numerous options to use the Option key as Meta including Option+BF to Option+Left/Right.
However, if you're a hardcore Dvorak user like myself who wants to use key bindings such as M-b and M-f using the original Dvorak layout, there's a problem. You can only "move backward/forward one word" in QWERTY layout. I use version 8.4.0 so I don't know about the latest version for Mavericks.
I use BetterTouchTool. Works like this:
Basically remaps Option-F and Option-B to Option-Right and Option Left, and I turned this on for any apps that I want the shortcut in, e.g., Firefox, Obsidian, Slack. Works great!
For Hyper you can fix the option key by setting the following configuration to your ~/.hyper.js file:
module.exports = {
config: {
modifierKeys: { altIsMeta: true }
}
}
source
In most multi-document editors for windowing environments, Control-TAB will utilize an MRU list to bring the user back to the last visible file. What is the appropriate command to accomplish this in Xcode 3.x?
I currently have Ctrl-TAB mapped to "View|Previous File", however this does not appear to be an MRU. Worse yet, if it hits the "beginning" of the list (should be a circular buffer), it falls back on inserting an actual TAB character into the text editor.
As of Xcode Version 3, there isn't anything that's exactly like the MRU you describe - however, check out the discussion on this page for some options that will get you closer to the behavior you want.
In recent XCode (10.3), when in a code editor press:
ctrl+1, right, right
Then use up and down keys and enter
to select from the MRU sorted list of recent files.
There is even an option to increase the size of the history.
In Xcode 3 (or any Mac application) you can use Command-Tilde (⌘~) to switch between open windows.
In Xcode 4 you use ⌘} for next tab and ⌘{ for previous tab - command shift bracket.
As a side note, for some reason Xcode 4 won't let me set the key binding for previous/next tab to the standard Control-Tab. When I try it puts in Command-Control-Tab.