[SOLVED] Vi and international keyboards dead keys

Hello all,
I'm learning Vi from the excellent documentation by the author himself and Mary Ann Horton at FreeBSD Documentation. However I'm facing a wall that I can't seem to get around.
Under the portuguese keyboard layout as defined by pt-latin1, the following diacritics are dead-keys:
~ (tilde)
^ (circumflex) (above the tilde, requires also the use of the SHIFT key)
` (gave accent, aka back tick) (above acute accent, requires the use of the SHIFT key)
Because they are dead keys, these diacritics aren't compatible with Vi command mode and certain CTRL combinations. They are however very useful. How can I handle this problem in Vi without remmaping these symbols to different keys (it is very important I don't remap them)? Is there a way to temporarily disable dead-keys functionality and have them function as regular one-hit keys?
My search for pt keymaps without dead keys produced 0 results. So, I don't think that is an option.
Last edited by marfig (2010-08-09 00:22:23)

Well, I took a closer look at man keymaps and found a way to deal with this; I can create single modifier definitions and load them with loadkeys.
So, if I look at dumpkeys I may find the following two lines
keycode 27 = dead_acute dead_grave apostrophe
keycode 43 = dead_tilde dead_circumflex asciitilde Control_backslash
I now know the keycodes. So I can create a new file (say, pt-latin1-undead), and write this this:
plain keycode 27 = acute
shift keycode 27 = grave
plain keycode 43 = asciitilde
shift keycode 43 = circumflex
Then all I need to do is load it with:
sudo loadkeys pt-latin1-undead
This will load it on top of my current keymap, replacing only those modifiers I defined and leaving the rest intact. When I'm done and want to get back to dead_keys mode, I simply load pt-latin1 again. Tested it already and works flawlessly!
The only disadvantage I can see is that loadkeys requires root access.
Note: The actual code for circumflex is 'asciicircum'. I didn't know this and my first try with 'asciicircumflex' was giving me a syntax error on loadkeys. So I just tried 'circumflex' and it worked. Seems to be a synonym.
Flagging as SOLVED.
Last edited by marfig (2010-08-09 00:38:14)

Similar Messages

  • Terminal.app, Window-switching, and International Keyboard

    Hi. I have a MBP running Mountain Lion (10.8.3), and I frequently work with Terminal.app. The following minor issue has been irritating me more and more recently: I can't use <Cmd>+<`> to switch Terminal windows using the "U.S. + International" keyboard.
    The shortcut works for other applications I use, like Firefox (and other browsers), Outlook and other MS Office components, MacVim, etc. But Terminal.app ignores it. It appears under Terminal's own Windows menu, as "Cycle Through Windows" .
    Thinking there might be some connection with my decision a few months ago to switch to the "U. S. International - PC" keyboard (for easier insertion of accents etc.), I went and switched that off ... Voila! Window-switching works again. But why is this necessary? Why can other applications deal with <Cmd>+<`> in U.S. International - PC mode, but Terminal.app can't?
    I'd like both options to be available at the same time, so suggestions welcome.

    AnonyMouse,
    If not for what Cornelius suggests....you may wish to
    have a look at the Apple Knowledge Base Article found
    http://docs.info.apple.com/article.html?artnum=25730
    Hope that helps some,
    littleshoulders [:-)
    ++++++++
    Hey there, littleshoulders, I owe ya a couple of beers! After reading the article that you referred me to, I checked my Font Book and sure enough, the Monaco font was missing, so I extracted the font from my installation disk using Pacifist once again, and installed it in HD/Library/Fonts. It then appeared in Font Book, so I launched Terminal and presto!, the full Terminal window appeared in all its glory. A big hug from me to you!
    By the way, Pacifist has saved my sanity at least a half dozen times....it's one app that I can truly say is worth its weight in gold. As far as I'm concerned, it's a must have.
    17" Powerbook - 1.5GHz - 1.5GB RAM Mac OS X (10.3.9)

  • [SOLVED] Zynaddsubfx and qwerty keyboard

    Hello guys and girls!
    I have a little trouble with zynaddsubfx   For a long time I was having fun with Zynaddsubfx and his awesome synths. I don't have any real musical (midi or usb, no matter) keyboard  and i played sounds with general qwerty keyboard. Zynaddsubfx previously worked on windows port and some other linux-based distros on my computer (for years never modified). But now here on Arch I can't play sounds with pc keyboard . Zynaddsubfx doesn't respond on almost all keys, except "6" and "7". But it is catastrophically small amount of keys to play with
    I have installed Archlinux x64 and here the list of installed packages:
    zynaddsubfx 2.4.1-1
    alsa-firmware 1.0.23-1
    alsa-lib 1.0.23-1
    alsa-oss 1.0.17-1
    alsa-utils 1.0.23-2
    gnome-alsamixer 0.9.6-3
    alsa-plugins 1.0.23-1
    lib32-alsa-lib 1.0.23-2 (lib32)
    lib32-alsa-plugins 1.0.23-2 (lib32)
    jack 0.118.0-3
    timidity++ 2.13.2-9
    fluidsynth 1.1.1-2
    I think the problem is wrong keymap(?) But i don't know where to fix it
    And, please, don't tell me things like "go and buy some serious stuff (midi keyboard, real synthesizer etc etc)" bcause I am not a musician and I am just having fun with Zynaddsubfx.
    Thanks in advance
    Last edited by Salamatiqus (2010-08-22 04:00:42)

    Haha, I found a solution
    It is simple as Arch must to be
    Launch [System -> Settings -> Keyboard], then move english keymap to up until english keymap will be first in the keymap's list. And wow, now zynaddsubfx works like in good old days
    Thanks to all, problem officially solved
    P.S yes, of course when i click piano keys with mouse sound appears
    Last edited by Salamatiqus (2010-07-04 10:17:05)

  • ITunes 10.5 and Microsoft keyboard media keys with IntelliType Installed

    Hi. I just updated to iTunes 10.5 and the media keys (play/pause, back, and forward buttons -- the latter two of which have been mapped to previous and next track respectively) on my Microsoft Ergonomic 4000 keyboard no longer work when iTunes in minimized. It works fine if iTunes is the active window. I tried installing the latest version of IntelliType (v8.2) and the installation notified me that I already have the latest version. I had no problems with the older version of iTunes (10.4).
    Is anyone else having this problem? Any solutions? Thanks in advance!

    I managed a different FIX. This is just for Microsoft Multimedia keyboard (I have Microsoft 8000)
    I uninstalled Microsoft Intellitype 8.1 that I had and then installed the newer 8.2 Version.
    Before I did that I Downgraded to Itunes 10.3 64x like someone else said, but it did not help.
    If this fix don't work with Itunes 10.5 then Downgrade like I did, It easier..No copying of files needed.
    After you uninstall Itunes 10.5 and Install 10.3, it give you an error for your library.
    So you press "SHIFT" and then open ITUNES.
    then you go to "My Music\iTunes" folder inside your genereal music folder, it should be there. (WIN 7)
    then to "Previous iTunes Libraries" folder and you should have a backup or and some kind of old "itunes Library folder" files...you choose one of them and Itunes opens fine with all playlist and everything.
    Now everything workd find.
    Good luck!
    P.S
    I after all this this does not work, might be because I installed Itune 10.3 before the new Intellitype 8.2.
    So try Uninstalling Intellitype 8.2 again.
    Then reinstall it...maybe it does things when Installing...I don't know.

  • No dead keys in Qt applications

    Hallo everyone.
    I use KDE 4.7.4-1 (latest stable) and have enabled two keyboard layouts, English US international with dead keys and Greek polytonic. Dead keys work perfectly in Greek in all applications, but not in English in Qt applications. For example, I can press “^" and "o" in Chromium and produce "ô" but if I try that in Kopete the whole sequence will be ignored.
    Does anybody know if this is a known bug or a problem with my system?
    Thanks in advance.

    Yes, I've seen, but as in blno's case, my locales as are correctly set:
    nikos@Russell:~$ locale
    LANG=el_GR.UTF-8
    LC_CTYPE="el_GR.UTF-8"
    LC_NUMERIC="el_GR.UTF-8"
    LC_TIME="el_GR.UTF-8"
    LC_COLLATE="el_GR.UTF-8"
    LC_MONETARY="el_GR.UTF-8"
    LC_MESSAGES="el_GR.UTF-8"
    LC_PAPER="el_GR.UTF-8"
    LC_NAME="el_GR.UTF-8"
    LC_ADDRESS="el_GR.UTF-8"
    LC_TELEPHONE="el_GR.UTF-8"
    LC_MEASUREMENT="el_GR.UTF-8"
    LC_IDENTIFICATION="el_GR.UTF-8"
    LC_ALL=el_GR.UTF-8
    Edit: Typo
    Last edited by GordonGR (2012-02-01 21:42:26)

  • [Solved] BEPO keyboard and dead keys

    Hello!
    So, I'm using a French BEPO keyboard, and it works pretty well, till today.
    Indeed, today, I wanted to write a greek letter, µ, but I couldn't. This letter is mapped to Alt-Gr+g.
    However, when loading the bepo in the console, it's working well (in a TTY). This only affects QT or GTK applications so far (X).
    This is the only one not working: my other dead keys just works like a charm (-> ´+i=í…)
    My final purpose is to be able to type any simple greek letter as explained here (http://bepo.fr/wiki/Lettre_grecque_sous_Linux). But I need the mu lettre to work first…
    I've tried GTK_IM_MODULE=xim, but then my normal deadkeys don't work anymore nor this alt-gr+g.
    By default, I use:
    export GTK_IM_MODULE=ibus
    export XMODIFIERS=@im=ibus
    export QT_IM_MODULE=ibus
    I also found out that alt-gr+/(L) is not working as a dead key (in order to type ø for example). (http://bepo.fr/wiki/Barre_inscrite)
    I should, lastly, say that I use a typematrix keyboard which is build with BEPO on it.
    Last edited by jiehong (2012-06-13 12:53:18)

    Hi,
    I aslo use the BÉPO layout.
    The Alt-Gr + G key changed in xorg with the last update of the xkeyboard-config package (happened on June 02 for me): this combination was the 'μ' greek letter, now it is the 'dead_greek' dead character. It is now what it should be so that is fine.
    To type the 'μ' letter, you now type Alt-Gr+G, followed by M.
    Note that this dead key works for me only if I use the xim input method. With other input method, some dead keys work, some others don't.
    I don't use some variables to set the input method, I use dconf-editor (package dconf),
    I set the key org/gnome/desktop/interface/gtk-im-module to xim (you don't have to restart for this change to take effect).
    When I was trying to configure greek letters before the xkeyboard-config update, I also found out that when I have a ~/.Xcompose file, it kills all the dead keys of my layout, I don't know if this is a bug or if I'm doing something wrong. Try to remove yours.

  • [SOLVED] No internal keyboard on LG R400 while and after installing

    Hi,
    I just tried to install Arch 64bit on this machine and everything works as expected - besides the internal keyboard, I had to use an external USB-keyboard to do the install and after install and playing with different HOOKS in the mkcpinitio.conf I still can't get it working.
    This is strange because I did install Arch on that machine about 2 years ago and the internal keyboard was working. I did try an old backup and the keyboard is working with an Arch from 2011.
    Since there is also no mention about such problems on the R400-wiki I'm running out of ideas. The keyboard controller seems to be i8042 and according to /dev/input/by-path/ seems to be loaded ok and linked to event0.
    platform-i8042-serio-0-event-kbd -> ../event0
    I already tried to append the options
    i8042.nomux=1 i8042.reset
    at boot time but keyboard remains dead.
    Any pointers where to look or what to try? Maybe an older kernel?
    TIA,
    Heinz
    Last edited by HeinB777 (2013-06-07 01:12:37)

    After trying various things this seems to be related to the 3.9.x kernel.
    The only solutions I found for now is to install a 3.8.x kernel and IgnorePkg linux and linux-headers. With this internal keyboard is ok.
    Since this seems to be an upstream bug introduced with 3.9 kernel I mark this thread as solved.
    See also here for more information: https://bugzilla.redhat.com/show_bug.cgi?id=969550
    Last edited by HeinB777 (2013-06-13 01:22:44)

  • [SOLVED] Dead keys on console in UTF-8 locale

    Hello,
    I want to share something interesting I found out about dead keys support on the Linux console (i.e., without X).
    I live in Canada and use the "Canadian French" keyboard, which uses dead keys for several diacritical marks (e.g., to type ê I push and release the ^ key, then type the e key). It works perfectly under X, but I was unable to type any character using dead keys on the console. On the other hand, non-ASCII characters like "é" that do not use dead keys worked perfectly.
    After some googling, I found many posts claiming the kernel did not support dead keys when the console was in Unicode mode. So I changed the locale to a non-UTF-8 setting in /etc/rc.conf, and indeed dead keys started working. But this was not useful to me, since editing UTF-8 files resulted in gibberish, and I did not want to regress back to Latin1 encoding or have to support both encodings. I tried many combinations of settings, but none worked. For a few days, I thought there was no way to have dead keys and Unicode working on the Console.
    But then I started to install Arch Linux on another computer and noticed that when I set the keyboard to Canadian French with the "km" utility before installing (the keymap is called "cf"), dead keys worked, even though the locale was Unicode! So there was a way to do it.
    I started digging and trying new things, and found out that after the following incantations, I was able to enable dead keys for Unicode on the console:
    kbd_mode -a
    sudo loadkeys cf
    kbd_mode -u
    This sets the console to ASCII mode, loads the "cf" keymap, and sets the console back to Unicode. I found it by trial and error, and I have no idea why it works or whether it breaks anything. I'm posting here to ask if there are easier ways to have a functional Canadian French keyboard on the console, and to document what I did in case someone has a similar problem.
    Last edited by pguertin (2010-01-23 21:44:33)

    I have the exact same issue.
    The weird thing for me is that before I was using gentoo and never had a problem with dead keys and unicode. Also, I confirm that dead keys is working when booting from the archlinux installation cd. Either run 'loadkeys cf' rigth after login or pass 'keymap=cf' as a boot parameter to the kernel line by editing it in grub before booting.
    Your solution is interesting, however the cf.map.gz file is the same on the installation cd (and on my gentoo system) so it should works without editing it.
    In my quest to solve this issue, I found something interesting. I added the 'keymap' hook in /etc/mkinitcpio.conf and regenerated the image by issuing
    mkinitcpio -g /boot/kernel26.img
    This alone didn't solved the issue, but then I REMOVED the keymap assignation in /etc/rc.conf (i.e. leaving it as
    KEYMAP=
    ), rebooted... and voilà, it now works.
    Furthermore, now if I run
    sudo loadkeys cf
    after login it stops working (well of course because it's the same as defining KEYMAP="cf" in /etc/rc.conf). Issuing the 3 commands of your first post make it works again. OK so I did one more test: boot from the archlinux installation cd by adding the 'keymap=cf' boot parameter to the kernel line and then run 'loadkeys cf' after login to see if it breaks dead keys. But no, it still works.
    So is this issue comes from a newer version of the kernel/loadkeys/mkinitcpio/...? How different is the kernel and initramfs images of the installation cd compared to the installed system ?

  • [xorg7] international keyboard issues [SOLVED]

    note that i've read the wiki as well as most of the related posts here in the bbs
    thereafter i edited :etc:x11:xorg;conf (sorry, keyboard is lost)
    got xf86-input-keyboard and xf86-input-mouse and xf86-video-nv installed, as well as xorg-fonts-100dpi;
    since it didn't do what i wanted, killed x and launched xorgcfg -textmode to reconfigure it, with no difference; shoud i try hwd -x ,
    xorg7 starts in this location, but have issues left :
    - keyboard configuration is lost in x  : capital, accentuated are lost; i'm on a international (105) fr keyboard
    - mouse scroll is gone
    - the shift keys do not allow me to select any string (but the middle mouse button does)
    cannot find yet a related topic that would give me some hint on how to solve this;
    can someone give a hand on this issue please ,
    /etc/X11/xorg;conf :
    Section "ServerLayout"
            Identifier     "XFree86 Configured"
            Screen      0  "Screen0" 0 0
    Section "Files"
            RgbPath      "/usr/share/X11/rgb"
            ModulePath   "/usr/lib/xorg/modules"
            FontPath     "/usr/share/fonts/misc:unscaled"
            FontPath     "/usr/share/fonts/misc"
            FontPath     "/usr/share/fonts/100dpi:unscaled"
    Section "Module"
        #Load           "glx" Unsupported with Composite extension
            Load  "ddc"  # ddc probing of monitor
            Load  "dbe"
            Load  "extmod"
            Load  "bitmap" # bitmap-fonts
            Load  "type1"
            Load  "freetype"
            Load  "record"
    EndSection
    Section "InputDevice"
            Identifier  "Keyboard0"
            Driver      "keyboard"
            Option      "CoreKeyboard"
            Option      "XkbRules" "xfree86"
            Option      "XkbModel" "pc105"
            Option      "XkbLayout" "fr"
            Option      "XkbOptions" "compose:rwin"
        #Option         "XkbVariant" "nodeadkeys" ## accents ds les consoles, mais empeche les accents circonflexes dans les applis X
    EndSection
    Section "InputDevice"
            Identifier  "PS/2 Mouse"
            Driver      "mouse"
            Option      "Protocol" "auto"
            Option      "ZAxisMapping" "4 5"
            Option      "Device" "/dev/psaux"
            Option      "Emulate3Buttons" "false"
            Option      "Emulate3Timeout" "70"
            Option      "SendCoreEvents" "true"
    EndSection
    Section "Monitor"
            Identifier   "Monitor0"
    ### Comment all HorizSync and VertSync values to use DDC:
            HorizSync    30.0 - 97.0
            VertRefresh  50.0 - 180.0
    Section "Device"
        #Driver      "vesa"
        #Driver         "nvidia"
            Identifier  "Card0"
            Driver      "nv"
            VendorName  "All"
            BoardName   "All"
            Card        "NVIDIA GeForce"
    EndSection
    Section "Screen"
            Identifier "Screen0"
            Device     "Card0"
            Monitor    "Monitor0"
            DefaultDepth     24
            Option      "DPMS"
            Option      "nvagp" "1"
        # should be switched off *if* the system crash:
            Option      "RenderAccel" "true"
        #Option "AllowGLXWithComposite"
            SubSection "Display"
                    Depth     1
                    Modes    "1280x1024" "1024x768" "800x600" "640x480"
            EndSubSection

    Trying out ...
    is this writen somewhere and i missed it ?
    It seems to solve all of my keyboard & mouse issues.
    Only is the cursor quite bizarre ; when i go left with the [left arrow],the cursor shows in every position  it goes (dunno if one can visualize this!), and doesn't blink anymore. Anyway that's just a detail that I'l cope with later.
    Thanks a lot Cerebral

  • Satellite P10, internal keyboard: The pipe key doesn't work anymore

    Hello everybody!
    I have a Satellite P10 with WinXP(SP1) for ca. 1 year.
    Symptoms: It's about the internal keyboard. I've used the pipe key <|> indeed not everyday, but it worked. And suddenly I see that it's not doing anymore: it's "dead", whereas all other keys are working properly...
    My following steps:
    1) I've deinstalled the standard keyboard driver (101/102 keys) or Microsoft Natural Keyboard (PS/2), and it was successfully found after Windows starting up. There is no hardware conflict according to the Device Manager or System Information, the driver is running properly...
    2) The keyboard layout is German. But I've tested already the English (US) one too: the result is the same.
    Questions:
    1) Is the key physically damaged?
    2) If not, what can I do to fix the problem? Where can I get maybe a newer driver?
    Thanks in advance!
    Message was edited by: MischaG

    Hello Mischa
    If you can not use the button at all I assume that the button is defective. It is not known to me that driver update can has influence on just several buttons.
    If the unit is about 1 year old the warranty is still valid. You can contact service partner and let them exchange the keyboard.
    Bye

  • Dead keys in keyboard no longer working

    I use "us-acentos"  keymap and since 2014-09-24 upgrade the dead keys are no longer working: typing apostrophe  followed by "e" should print "é" but instead it just prints the apostrophe.
    This under X both in bash and in a graphical editor such as leafpad, geany, netbeans. In a non-X session the dead keys do not work either, an apostrophe followed by "e"  will just display a space.
    Would anyone have any suggestion as to why this happened and how to correct it? Thank you.
    Output of locale-ctl status:
    System locale: LANG=fr_CA.UTF-8;
    VC Keymap: us-acentos;
    X11 Layout: n/a.
    Output of pacman.log:
    [2014-09-24 16:59] [PACMAN] starting full system upgrade
    [2014-09-24 17:03] [PACMAN] upgraded bash (4.3.024-1 -> 4.3.024-2)
    [2014-09-24 17:03] [PACMAN] installed ca-certificates-utils (20140325-2)
    [2014-09-24 17:03] [PACMAN] installed ca-certificates-mozilla (3.17-3)
    [2014-09-24 17:03] [PACMAN] installed ca-certificates-cacert (20140824-1)
    [2014-09-24 17:03] [PACMAN] upgraded ca-certificates (20140325-1 -> 20140325-2)
    [2014-09-24 17:03] [PACMAN] upgraded efivar (0.10.8.g81d0146-1 -> 0.11-1)
    [2014-09-24 17:03] [PACMAN] upgraded efibootmgr (0.7.0.16.g099e110-1 -> 0.8.0-1)
    [2014-09-24 17:03] [PACMAN] upgraded rtmpdump (20131205-1 -> 20140918-2)
    [2014-09-24 17:03] [PACMAN] upgraded libx264 (1:142.20140826-1 -> 1:142.20140826-2)
    [2014-09-24 17:03] [PACMAN] upgraded ffmpeg (1:2.3.3-2 -> 1:2.4.1-1)
    [2014-09-24 17:03] [PACMAN] upgraded nspr (4.10.6-1 -> 4.10.7-1)
    [2014-09-24 17:03] [PACMAN] upgraded nss (3.16.3-1 -> 3.17-3)
    [2014-09-24 17:03] [PACMAN] upgraded firefox (32.0.1-1 -> 32.0.2-1)
    [2014-09-24 17:03] [PACMAN] upgraded firefox-i18n-fr (32.0.1-1 -> 32.0.2-1)
    [2014-09-24 17:03] [PACMAN] upgraded gegl (0.2.0-11 -> 0.2.0-12)
    [2014-09-24 17:03] [PACMAN] upgraded gstreamer (1.4.1-1 -> 1.4.2-1)
    [2014-09-24 17:03] [PACMAN] upgraded gst-plugins-base-libs (1.4.1-1 -> 1.4.2-1)
    [2014-09-24 17:03] [PACMAN] upgraded gst-plugins-base (1.4.1-1 -> 1.4.2-1)
    [2014-09-24 17:03] [PACMAN] upgraded k3b (2.0.2-9 -> 2.0.2-10)
    [2014-09-24 17:03] [PACMAN] upgraded libgpg-error (1.14-1 -> 1.16-1)
    [2014-09-24 17:03] [PACMAN] upgraded libtirpc (0.2.4-1 -> 0.2.5-1)
    [2014-09-24 17:03] [PACMAN] upgraded xine-lib (1.2.6-1 -> 1.2.6-2)
    [2014-09-24 17:03] [PACMAN] upgraded opencv (2.4.9-4 -> 2.4.9-5)
    [2014-09-24 17:03] [PACMAN] upgraded openresolv (3.5.7-1 -> 3.5.7-2)
    [2014-09-24 17:03] [PACMAN] upgraded openscenegraph (3.2.1-1 -> 3.2.1-2)
    [2014-09-24 17:03] [PACMAN] upgraded perl (5.20.0-5 -> 5.20.1-1)
    [2014-09-24 17:03] [PACMAN] upgraded python2 (2.7.8-1 -> 2.7.8-2)
    [2014-09-24 17:03] [PACMAN] upgraded x264 (1:142.20140826-1 -> 1:142.20140826-2)
    [2014-09-24 17:03] [PACMAN] upgraded xorg-server-common (1.16.0-6 -> 1.16.1-1)
    [2014-09-24 17:03] [PACMAN] upgraded xorg-server (1.16.0-6 -> 1.16.1-1)
    [2014-09-24 17:03] [PACMAN] upgraded xz (5.0.6-1 -> 5.0.7-1)

    Follow-up:
    1) I could restore the keyboard in X with this command:
    $ localectl set-x11-keymap us pc104 alt-intl
    which creates /etc/X11/xorg.conf.d/00-keyboard.conf:
    Section "InputClass"
    Identifier "system-keyboard"
    MatchIsKeyboard "on"
    Option "XkbLayout" "us"
    Option "XkbModel" "pc105"
    Option "XkbVariant" "intl"
    Option "XkbOptions" "terminate:ctrl_alt_bksp"
    EndSection
    another option that worked was to rename /etc/X11/xorg.conf.d/10-evdev.conf.pacsave to /etc/X11/xorg.conf.d/10-evdev.conf, which also contained the "XkbLayout" and "XkbVariant" lines under "InputClass" (the original file had been renamed to .pacsave in February 2013). See wiki:
    https://wiki.archlinux.org/index.php/Ke … on_in_Xorg
    The output from localectl status now reads:
    System Locale: LANG=fr_CA.UTF-8
    VC Keymap: us-acentos
    X11 Layout: us
    X11 Model: pc105
    X11 Variant: intl
    X11 Options: terminate:ctrl_alt_bksp
    So it seems that the result of an earlier upgrade was to "unset" the keyboard for X (compare with output from localectl status in original post). Why?
    2) the keyboard in console (out of X) is still not working. If I try to set it to "us-alt-intl" in /etc/vconsole.conf, it works as "us" should (no dead keys); it I use "us-acentos" some keys do not work. locale-ctl shows that "us-acentos" does exist (but not "us-alt-intl").
    Mystery.

  • Dead Keys on Lenovo W520 built-in keyboard after Windows 7 (64bit) Update

    After my Windows 7 update, I have several dead keys.  Left Alt, Up Arrow, Print Screen, F5, F6, and the ThinkVantage Keys are all dead.  Orginally I thought it was just Windows, but after booting into my Linux OS, I run into the same issues.  I have tried reflashing my bios, but that did not fix the problem.  Can anyone help?
    Hardware: Lenovo W520 (Referbished)
    OS: Windows 7 (64bit), Debian Linux (64bit)
    Age: 2 months after refurbished
    Update 1: Chrome and Firefox would crash if I tried to download something.  Did a system restore which fixed the problems with that, but there are still dead keys.  I am now downloading a bootable cd from Lenovo.  If that fails, I will attempt to reflash one last time before I send this thing to get fixed by the pros.
    Update 2: Just remember, why would the lights in the keyboard stop working?  They keys still work, but the mike key and the caps key are not lighting up their LEDs when I'm using them.

    After my Windows 7 update, I have several dead keys.  Left Alt, Up Arrow, Print Screen, F5, F6, and the ThinkVantage Keys are all dead.  Orginally I thought it was just Windows, but after booting into my Linux OS, I run into the same issues.  I have tried reflashing my bios, but that did not fix the problem.  Can anyone help?
    Hardware: Lenovo W520 (Referbished)
    OS: Windows 7 (64bit), Debian Linux (64bit)
    Age: 2 months after refurbished
    Update 1: Chrome and Firefox would crash if I tried to download something.  Did a system restore which fixed the problems with that, but there are still dead keys.  I am now downloading a bootable cd from Lenovo.  If that fails, I will attempt to reflash one last time before I send this thing to get fixed by the pros.
    Update 2: Just remember, why would the lights in the keyboard stop working?  They keys still work, but the mike key and the caps key are not lighting up their LEDs when I'm using them.

  • International keyboard with Norwegian layout - possible to remap some keys?

    Hey, I have a MBP OS X 10.6.8 with international keyboard that I have selected a Norwegian layout on, since I need the special characters we have in our language (æ, ø and å).
    My question is - is it possible to remap just SOME keys/characters while in this configuration?
    The keys I need to remap are:
    < to ` (so I can do Command-` in programs to change windows)
    ´ to ' (because I use the standard apostrophe)
    Any way to do this in OS X, or maybe with other software? Thanks for any help!

    Some possible options:
    +Use system preferences/language & text/text/symbol and text substitution to create shortcuts
    +Use Ukelele to create a custom keyboard layout
    http://scripts.sil.org/ukelele
    +Use the US layout and type your special characters using the built-in alt key shortcuts
    http://homepage.mac.com/thgewecke/diacritics.html
    Note:  Standard apostrophe is alt + @ on the Norwegian layout (alt + \ if keys are printed for US layout).

  • My logitech external keyboard started typing strange figures and takes a photo each time I press delete. Ipad internal keyboard works fine. Btooth etc all connected. Hapened suddenly.

    My logitech external keyboard started typing strange figures and takes a photo each time I press delete. Ipad internal keyboard works fine. Btooth etc all connected. Happened suddenly.Did I press a strange key somehow??

    Thank you but - Are there batteries?? Is it not wireless? Very thin and I would have no ideas where batteries were?

  • Macbook pro 15" mid 2010 i spilled water on keyboard now it wont power on if the battery is connected and the keys on keyboard doesnt work it works fine with no battery and external keyboard if i order a battery and new keyboard will every else work again

    macbook pro 15" mid 2010 i spilled water on keyboard now it wont power on if the battery is connected and the keys on keyboard doesnt work it works fine with no battery and external keyboard if i order a battery and new keyboard will every else work again lik it did before

    If you have records that show that you've taken your MacBook Pro in for a year to fix the machine, I would escalate the problem to Apple Customer Relations - unfortunately I don't have a number for Spain.
    It would only seem logical to me that if you've been trying to have the machine repaired during the time that the 'recall' was in effect that you should be eligible for a new logic board. But only customer relations will be able to make that call.
    Good luck - take the issue as high up the food chain as you can and see what happens.
    Clinton

Maybe you are looking for