Common Keyboard Shortcut. Mixes Up. Language Input Source

Sometimes using common OS X shortcuts invokes the "Select previous input source" command. For example, I'll try apple-H to hide an application but it will change the keyboard layout from Dvorak to Qwerty (and then rotate through them with more presses).
The input source option is set to "Use one input source in all documents" and some common shortcut becomes the shortcut to change the input source. I don't see any specific action that causes this -- I'll just wonder why my app isn't hiding, look up, and see the layout changing.
I'll even go far out of my way to change the keyboard shortcut (in the keyboard area) to something really convoluted like command-option-shift-D and then turn the "select previous input source" command off.
Has anyone else had this problem? Has anyone else found a solution?
iBook (Late 2001) Mac OS X (10.4.5) 600MHz G3, 640MB, 60GB

Similar Messages

Why is the keyboard shortcut for 'Select next input source' disabled when using Safari?

I'm using Safari 6.0.5 and am running 10.8.4 on a MacBook Pro 13" from last year.
I've been using Chrome and Firefox heavily recently, but switched to Safari to give it a chance. It's really nice and lightweight, which suits me.
However, for some reason unbeknownst to me, the keyboard shortcut 'Select next input source' is disabled in Safari, in all windows/input methods.
Since I constantly switch input methods, this is incredibly frustrating.
It persists after quit + restart.
Any ideas?

Yes, just Safari. In Chrome, Firefox and all other applications it works as expected.

No keyboard shortcuts in 2nd language keyboard after 10.5.6 update

I decided to take the plunge from 10.5.2 to 10.5.6. My only grievance for 10.5.2 was that Mail changed the extension of attached files if the filename contained non-latin characters (a known bug which was killed in 10.5.6). I took all necessary pre-update steps, namely:
SuperDuper! backup (SmartUpdate)
TimeMachine backup
Repaired permissions
Reboot from external USB drive; Repaired main system (internal) hard disk
Reboot off main drive in Safe Boot mode and install of OS X update, then finally,
Repaired permissions.
Now my Mac doesn't accept keyboard shortcuts of any kind in any application if the input language is Greek (it used to until this morning, in all incarnations of OS X from 10.2 to 10.5.2). Tried in two user accounts. I also created a new user account, same trouble.
If I add another language in the Input menu, e.g. Arabic, then the keyboard shortcuts work for that; still not for the Greek that used to work until now.
Gotta run, but I'll post back later with some further info on this issue (I really must dash out, and I haven't got time to elaborate right now...)
BTW, the Greek I'm using is not the one from the Apple install, but the one from here.

BTW, the Greek I'm using is not the one from the Apple install, but the one from here.
You probably need to ask vodkatini. I think that's a hack for using non-Unicode Greek with old apps. Do you really still need it? Apple won't make any effort to adjust OS X to accomodate such things.
Do the standard Apple Greek keyboards work OK?
You could also ask on Greek Mac boards where people might be using the vodkatini stuff. Or go back to your last OS where it worked.
http://www.macephemera.gr/news.php
http://www.helmug.gr/

Why am I unable to use Ctrl+Shift keyboard shortcuts in the Kotoeri input method on OS X 10.9?

For some reason I'm unable to switch from Hiragana to Katakana and vice versa using the Ctrl+Shift+K and Ctrl+Shift+H keyboard shortcuts when using the Kotoeri IME. The shortcuts appear in the IME menu in the menubar.
Have these shortcuts been changed in OS X Mavericks and the menu not updated, or does the menu not actively reflect the current keyboard shortcut settings? I'm using OS X 10.9.1 (if that helps at all).
Any help would be greatly appreciated!

Thanks for the hint! I hadn't realized that Xcode 5.1.1 was so huge (2.18Gb) and assumed after an hour that the installation had frozen.

What are the zoom keyboard shortcuts for the Italian Pro keyboard? How can I find any keyboard shortcuts for other language keyboards?

It's all in the title.

Perhaps you should post in the software forum for your OS -- it really has nothing to do with your hardware.
https://discussions.apple.com/community/mac_os
You could try setting up a new user account and see if the problem persists when you are logged into that.

Spotlight / Language Input Menu Keyboard Shortcuts

In the Mouse & Keyboard Preference Pane, I disable the keyboard shortcuts for the Language Input Menu.
In addition, I try to change the keyboard shortcut for Spotlight from CMD-Space to Option-Space.
The only problem is that these prefrences reset themselves upon logout.
Is there any way to fix this, or can someone point me to the .plist file for keyboard shortcuts?
Thanks in advance.

can someone explain in more detail on how to change the keyboard shortcut? on my old imac, i was able to switch languages by using cmd-spacebar.. but on my macbook, it seems to direct to another command.
how do i change that so i have a hotkey on my keyboard to change languages?? (i'm very tech. challenged, so baby steps would be goog >_<!!) thanks for the help!

Keyboard input source "randomly" changing???

Keyboard input source “randomly” changing???
Hi: I’m trying to learn the Dvorak keyboard as a touch typer, so I change my input source from “US” which is hunt and peck to “Dvorak”. But, weirdly (at least to me), I will have changed from one input source to the other, and yet 15’ later in a different program the input source is still on the other.
Is there some kind of auto sensing feature where the input source defaults to whatever was used with that document the last time or something like that? If so, is there a way to disable this feature so that what keyboard layout one chooses as an input source always stays that way until manually changed? Or is there another explanation for this behaviour?
Thank you very much!!!

In System Preferences -> Keyboard -> Input Sources is the option "Automatically Switch To A Document’s Input Source" selected perhaps?
Alternatively, in System Preferences -> Keyboard -> Shortcuts under Input Sources a shortcut for switching the input source might be selected. Perhaps you inadvertedly type that key combination sometimes.

Captivate 6 How to validate user input without using keyboard shortcuts

I've been using Adobe Captivate 6 for about 4 months now. Completely new to the program. The number one function of Captivate for me will to create many software simulations for verifiable training. This means that I will be utilizing the training and assessment modes A LOT. I have run into many hurdles throughout the process, but one of my biggies right now is this:
In the training and assessment modes, I have times where the user must input data such as an address or number. In the actual software they will be utilizing it is not always required to use TAB or ENTER in order to move to the next field. In some instances, it will be necessary to actually click into a field after entering data. My problem is that it seems as if Captivate will not allow this, as a keyboard shortcut is automatically entered even if a TAB or ENTER is not required after input. I assume this is so that the inputted information can be verified. If you decide you do not want to use a keyboard shortcut to validate the inputted information, you must have a submit button. Is there any way to change this?? All I want is for the user to enter information and then click into another field WITHOUT having to press ENTER, TAB, or hit a submit button. Is this even possible if you need user input to be validated?? Any ideas or suggestions would be much appreciated!!

Hello,
A while ago I explained the work flow I’m using often in that case, only for the last field you need to have either a shortcut or a submit button AND the sequence has to be imposed. The idea is that you make the Submit button for the first field transparent, delete the ‘Submit’ text and put it over the second field. So if the user clicks on the second field, he also submits the value of the first field.
Here is the blog post I’m referring to:
http://lilybiri.posterous.com/one-submit-button-for-multiple-text-entry-box
Although it was written for previous versions, the idea will still be functional.
Lilybiri

Keyboard input source change not being saved.

Since upgrading to 10.9 my original French spec Mac Mini reverts to French Keyboard input source when I close down, even after resetting keyboard input source to British PC on the login screen when booting up. Is there a more permanent setting option stored elsewhere?

Hi Brendan,
Thanks for the link. I did go into system preferences and checked that British was the default setting. In fact it was the only setting. Have subsequently done a bit more research. Up to now I have been changing input source at the initial login screen from French to British. I have just typed my username and password in using a French keyboard layout without changing the input source from French. It gets me in and the default input source is showing as British, which it is picking up from the system preferences. So there must be a setting somewhere that is specific to the login screen.
Done some more searching online and it looks like it may be a bug!
https://discussions.apple.com/message/23769843#23769843
There seem to be a few workarounds https://discussions.apple.com/thread/5485931
However, I have not worked at this level on a Mac before having a background in Windows support, Only recently getting a Mac. The last comment looks like some kind of Unix stuff, which I know OSX is based on. Is there an idiots step by step guide anywhere to carry out the plist edit etc?

Unable to unlock computer due to impossibility to switch between input sources

I cannot unlock my computer after wake up under the following circumstances.
- In System Preferences - Language and Text - Input Sources, I have the following input sources:
- US
- Bulgarian
- In System Preferences - Language and Text - Input Sources, I've chosen the "Allow a different one for each document" option
- My shortcut for "select previous input source" is Cmd-Space
- In System Preferences - Security and Privacy - General, I've chosen "Require password 5 seconds after sleep or screen saver begins"
- My password for login is using US layout characters only
- In System Preferences - Desktop & Screen Saver - Hot Corners, I've chosen "Put Display to Sleep" on the lower right corner, others are empty.
Steps to reproduce:
1. Open Safari and switch to Bulgarian keyboard layout with Cmd-Space
2. Use the trackpad to direct cursor in the lower right corner in order to activate screen sleep
3. Wait 5 seconds for the lock to be engaged
4. Wake up the computer with the trackpad or keyboard and enter your password to unlcok the computer
Result: The password dialog is shaking, suggesting the password is wrong. If I try to change the input source by pressing Cmd-Space, there is a sound heard from the OS X suggesting I am pressing a shortcut which isn't allowed. There's no visual menu to switch between keyboard layouts. I am most probably stuck with the last keyboard layout used on the last open application which is Bulgarian and since my password is in US, I cannot unlock the computer. I need to reset my computer by holding down the power button in order to be able to log in again.
This is the first time I felt my Mac is letting me down. To be honest, I can't understand how such a critical bug has managed to go unnoticed by the quality assurance team at Apple.

Similar probs here as those reported in initial mail of this thread.
OS X 10.9.2.
Two input sources installed.
Both are lattin based. No Cyryllic, nor far East, nor Judish, nor Arabic,....
Simply two lattin based input sources - keyboards.
Even under lattin keyboards there are different key layouts.
I know one possible difference: qwerty and qwertz.
Possibly there are more other layouts than these two.
Lets assume these two input sources, layouts: 1 and 2.
For certain user account the password was set while layout 1 was selected.
Then the user edits some texts, he selects for this keyboard layout/input source 2.
User makes Sleep OS X, or logs off.
Layout 2 keeps to be active.
User wants to unlock the mac.
It is not possible because password is konform with layout 1,
at the time of unlocking however layout 2 is selected.
It is not possible to select the another layout - user can not unlock os x.

Input source selector does not show when switching the input source

Hi,
I'm running OS X Mavericks on my late-2013 15" MacBook Pro with Retina Display. I set a key combinations in Keyboard section in System Preferences to "Select the previous input source" and "Select next source in Input menu".
In my previous MacBook, whenever I use the shortcut to switch my input source, there's a selector (as shown below) appear in the middle of the screen showing what input source I am selecting. Strangely, on this new MacBook, it just doesn't show it.
I thought that this is a change in Mavericks, but a few days ago, I install Mavericks on my old MacBook and the selector does appear when I am switching the input source using the shortcut. I have search throught all the setting in System Preferences, but there is no option to show or hide the Input source selector when switching the input source. Am I the only one? Am I missing something? Is there any fix?
Thanks in advance.

Try troubleshooting the adapter > Apple Portables: Troubleshooting MagSafe adapters

Toggle a specific input source with Applescript

Hello to all,
I am trying to write an Applescript to toggle a specific language input source. My main input sources are two, english and greek, but in many occasions i have to enable the "Greek polytonic" keyboard. So, after some search on the internet, I wrote this:
tell application "System Preferences"
activate
          reveal anchor "InputMenu" of pane id "com.apple.Localization"
end tell
tell application "System Events" to tell process "System Preferences"
click checkbox of row 76 of table 1 of scroll area 1 of tab group 1 of window 1
end tell
quit application "System Preferences"
It compiles OK, but when I run it what happens is that the selected checkbox (the "Greek Polytonic" one) gets checked and INSTANTLY unchecked.
Why does this happen?
Thanks in advance
Dimitris

Hello
I have confirmed the odd behaviour under 10.5.8. It seems to me the required accessibility is defective under 10.5.8. The GUI scripting code works fine under 10.6.8 but the row index of the enabled input source will change to some smaller number when you reopen the System Preferences.app.
Anyway, I've written a simple command line utility in C, which lets you manipulate the text input source. Here's the recipe for you.
# Recipe.
A) To compile and test the C programme.
A1) Copy the code listed below as main.c into new document of text editor (e.g. TextEdit) and save it as plain text named "main.c" on desktop.
A2) In Terminal.app, run the following (type each line followed by return) to create an executable file named "textinputsource" on desktop:
cd ~/Desktop
gcc -framework Carbon -o textinputsource main.c
A3) In Terminal.app, type the following and return to toggle the enabled/disabled state of the specified input source:
./textinputsource -t 'Greek Polytonic'
B) To create an AppleScript wrapper to call this utility.
B1) Create a new AppleScript script with the following contents and save it as a script bundle or an application bundle:
set p to (path to resource "textinputsource")'s POSIX path
do shell script p's quoted form & " -t 'Greek Polytonic'"
B2) Show package contents (via contextual menu) of the saved bundle and put the executable file "textinputsource" loose in its Contents/Resources directory. Now you can run the script bundle or the application bundle to toggle the input source.
# Notes.
• The utility programme has some other options. E.g., you can select the specified source by -s option. See comments in source code for details.
• You need to have Developer Tools installed to build the programme.
• Tested under 10.5.8 and 10.6.8 but no warranties of any kind.
• I noticed that System Preferences.app won't update the check box live when the enabled/disabled state is changed by this utility. You'd need to rerun the System Preferences to reflect the change in its GUI.
• This is freeware you may use and modify as you like.
# File
main.c
    file
        main.c
    function
        to manipulate text input source, i.e.,
            - print currently selected source,
            - select specified source (enable it as needed)
            - enable specified source,
            - disable specified source,
            - toggle enabled/disabled state of specified source.
    compile
        gcc -framework Carbon -o textinputsource main.c
    usage e.g.
        ./textinputsource [-s|e|d|t name]
        given no arguments, it will print the current source name.
        options:
            -s : select source name (enable it as needed)
            -e : enable source name
            -d : disable source name
            -t : toggle enabled/disabled on source name
#include <Carbon/Carbon.h>
#include <libgen.h>    // basename
TISInputSourceRef getInputSourceByName(char *);
int
main (int argc, char * argv[])
    int ret = -1;
    int c;
    TISInputSourceRef tis;
    CFStringRef name;
    OSStatus err = 0;
    while ((c = getopt(argc, argv, "s:e:d:t:h")) != -1)
        switch (c)
            case 's':
                tis = getInputSourceByName(optarg);
                if (tis)
                    CFBooleanRef enabled = TISGetInputSourceProperty(tis, kTISPropertyInputSourceIsEnabled);
                    if (enabled == kCFBooleanFalse)
                        TISEnableInputSource(tis);
                    err = TISSelectInputSource(tis);
                    CFRelease(tis);
                ret = tis ? (int) err : 1;
                break;
            case 'e':
                tis = getInputSourceByName(optarg);
                if (tis)
                    err = TISEnableInputSource(tis);
                    CFRelease(tis);
                ret = tis ? (int) err : 1;
                break;
            case 'd':
                tis = getInputSourceByName(optarg);
                if (tis)
                    err = TISDisableInputSource(tis);
                    CFRelease(tis);
                ret = tis ? (int) err : 1;
                break;
            case 't':
                tis = getInputSourceByName(optarg);
                if (tis)
                    CFBooleanRef enabled = TISGetInputSourceProperty(tis, kTISPropertyInputSourceIsEnabled);
                    if (enabled == kCFBooleanTrue)
                        err = TISDisableInputSource(tis);
                    else
                        err = TISEnableInputSource(tis);
                    CFRelease(tis);
                ret = tis ? (int) err : 1;
                break;
            case 'h':
            case '?':
            default:
                fprintf(stderr, "Usage: %s %s\n\t\%s\n\t%s\n\t%s\n\t%s\n\t%s\n",
                    basename(argv[0]),
                    "[-s|e|d|t name]",
                    "-s : select source name (enable it as needed)",
                    "-e : enable source name",
                    "-d : disable source name",
                    "-t : toggle enabled/disabled of source name",
                    "no arguments : print current source name"
                ret = 1;
                break;
    if (ret == -1) // no args: print current keyboard input source
        tis = TISCopyCurrentKeyboardInputSource();
        name = TISGetInputSourceProperty(tis, kTISPropertyLocalizedName);
        int len = CFStringGetLength(name) * 4 + 1;
        char cname[len];
        bool b = CFStringGetCString(name, cname, len, kCFStringEncodingUTF8);
        printf("%s\n", b ? cname : "");
        ret = b ? 0 : 1;
    if (err != noErr)
        fprintf(stderr, "Text Input Source Services error: %d\n", (int) err);
    return ret;
TISInputSourceRef
getInputSourceByName(char *cname)
    //     char *cname : input source name in UTF-8 terminated by null character
    //     return TISInputSourceRef or NULL : text input source reference (retained)
    CFStringRef name = CFStringCreateWithCString(kCFAllocatorDefault, cname, kCFStringEncodingUTF8);
    CFStringRef keys[] = { kTISPropertyLocalizedName };
    CFStringRef values[] = { name };
    CFDictionaryRef dict = CFDictionaryCreate(kCFAllocatorDefault, (const void **)keys, (const void **)values, 1, NULL, NULL);
    CFArrayRef array = TISCreateInputSourceList(dict, true);
    CFRelease(dict);
    CFRelease(name);
    if (!array)
        fprintf(stderr, "No such text input source: %s\n", optarg);
        return NULL;
    TISInputSourceRef tis = (TISInputSourceRef) CFArrayGetValueAtIndex(array, 0);
    CFRetain(tis);
    CFRelease(array);
    return tis;
Hope this may help,
H

How do I add an input source besides English in Gnome Shell? [SOLVED]

Hello.
I'm a bit confused as to how I should add additional languages/input sources in Gnome Shell. When I ran Gnome Shell in Ubuntu, I could add additional input sources via the Region & Language section of the Gnome control panel, but in Arch I've only got English (my locale is en_US.UTF-8). I'd like to be able to switch between English & Hebrew.
Do I need to install an underlying gnome package for handling additional input sources? Or do I need to manually add a locale? The wiki seems unclear on this. Also, should I use localectl? I'm also a bit unsure there.
Thanks!
Last edited by yochaigal (2015-02-21 16:38:25)

yochaigal wrote:Or do I need to manually add a locale?
I think so.
Edit the file at /etc/locale.gen and un-comment the desired locale then run:
# locale-gen
https://wiki.archlinux.org/index.php/Lo … ng_locales

Keyboard shortcut to duplicate seq-not intuitive

I find the keyboard shortcut for duplicating seqs in PPro very odd. On a Mac...most apps use the common shortcut of - cmd-"D". PPro use of shft-cmd- \ is a bit odd.
Yes I know I can remap but it seems common software global key commands would be the default. Isn't cmd-"D" true in AE?...not sure.
My last comment while in this mode...I feel keyboard shortcuts should be designed for one hand usage with out tremendous acrobatics. Thus allowing the other hand to be mostly on the mouse.
All Adobe products really should share more of the same common keyboard shortcuts.

I've already been told by a staffer for one of the other programs that unifying the gui & shorts are considered a worthwhile and not overly daunting part of the process; actually, a necessary set of steps. An iterative part, and yes partly fueled by internal wishes to have a sweet 'suite' and partly by comments from the base. Not a huge must-have-completely-and-forever-finalized by next release, but as part of the ongoing development of the programs. Plural. Manageable workload, and for a perceived worthwhile gain. How & what the changes are ... completely open-ended discussions.
You keep going to the AeFx side of things. That's the program I use the least currently. Which is of course subject to change as my skills and experience and (naturally) needs build. The length of the shorts pdf for that compared to say PrPro is almost laughable. Wow, that's ... a lot of shorts to even think of learning! But then, AeFx is an amazing program. Even for video software. Still, the total number of shorts that would be changed for a "unified set" option isn't that many, really.
For me, your objections are quite similar to say, two people looking at the same building. It's got ... shall we say, "character"? There are pipes hanging across hallways at varying heights, floors that shift up or down an inch or two or four randomly, halls that narrow around wider rooms then open back out, and lights and their accompanying switches placed in a totally random way.
One person says ... leave it as is, ANYONE can just look around and see they need to pay attention to moving around here ... let 'em do so and get on with life.
The other person says ... if we start working on some of this chaos, over time we'll have a building much easier to get around and work in. Fewer knocked noggins on the pipes, less time hunting for light-switches, fewer trips over sudden floor changes.
One chooses which person he/she will be in this scenario. And will probably switch viewpoints depending on the particular issue.
A last comment ... yea, I've noted I've not heard any complaints from any AeFx types other than you. Interesting, eh?
Neil

Lost input source?

I use the Hawaiian language input source on my MacBook pro and after installing Yosemite I lose it as an input source choice when I reboot. Previous versions of OS X never did this. Just wondering if anyone else is having issues with input sources

yes, i can see it changing in the system tray bar. but just there isn't any notificaiton in the middle display.
you know, when u use safari full screenmode, u will not see the tray bar, so you can't see what input you are using or changing to.

Common Keyboard Shortcut. Mixes Up. Language Input Source

Similar Messages

Maybe you are looking for