Guest User

Untitled

a guest
Oct 16th, 2018
68
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.36 KB | None | 0 0
  1. Current (unresolved) keymap file
  2. ================================
  3.  
  4. The following command prints one include statement for each component of the
  5. current keymap:
  6.  
  7. $ setxkbmap -print
  8.  
  9. Note that this is not a resolved keymap file!. Quite the opposite, it shows
  10. what will be passed to xkbcomp as components so that it resolves them to an
  11. actual keymap. A possible output could be:
  12.  
  13. xkb_keymap {
  14. xkb_keycodes { include "evdev+aliases(qwerty)" };
  15. xkb_types { include "complete" };
  16. xkb_compat { include "complete" };
  17. xkb_symbols { include "pc+latam+us:2+inet(evdev)" };
  18. xkb_geometry { include "pc(pc105)" };
  19. };
  20.  
  21. When passed into xkbcomp each include statement will be 'resolved'. This
  22. resolution process takes the string "pc+latam+us:2+inet(evdev)" and interprets
  23. it as follows: Merge files "pc" and "latam", then merge the "us" file
  24. into the 2nd group, finally merge the component named "evdev" inside the "inet"
  25. file. Because this include statement is inside a component of type xkb_symbols,
  26. the files "us", "latam", "pc" and "inet" will be looked for inside the
  27. <xkb data>/symbols/ directory.
  28.  
  29. NOTE: <xkb data> is usually /usr/share/X11/xkb/
  30.  
  31. Get current resolved file
  32. =========================
  33.  
  34. To print the current keymap but after resolution use:
  35.  
  36. $ xkbcomp -xkb $DISPLAY resolved_keymap.xkb
  37.  
  38. NOTE: It does not output to stdout but instead writes into resolved_keymap.xkb
Add Comment
Please, Sign In to add comment