Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

xkbgetkeymodifiermap(3) [x11r4 man page]

XkbGetKeyModifierMap(3) 					   XKB FUNCTIONS					   XkbGetKeyModifierMap(3)

NAME
XkbGetKeyModifierMap - Update the modifier map for one or more of the keys in a keyboard description SYNOPSIS
Status XkbGetKeyModifierMap ( dpy, first, num, xkb ) Display * dpy; unsigned int first; unsigned int num; XkbDescPtr xkb; ARGUMENTS
- dpy connection to X server - first keycode of first key to get - num number of keys for which information is desired - xkb keyboard description to update DESCRIPTION
The modmap entry of the client map is an array, indexed by keycode, specifying the real modifiers bound to a key. Each entry is a mask com- posed of a bitwise inclusive OR of the legal real modifiers: ShiftMask, LockMask, ControlMask, Mod1Mask, Mod2Mask, Mod3Mask, Mod4Mask, and Mod5Mask. If a bit is set in a modmap entry, the corresponding key is bound to that modifier. Pressing or releasing the key bound to a modifier changes the modifier set and unset state. The particular manner in which the modifier set and unset state changes is determined by the behavior and actions assigned to the key. XkbGetKeyModifierMap sends a request to the server for the modifier mappings for num keys starting with the key whose keycode is first. It waits for a reply and places the results in the xkb->map->modmap array. If successful, XkbGetKeyModifier returns Success. If the map component of the xkb parameter has not been allocated, XkbGetKeyModifierMap allocates and initializes it. If a compatible version of Xkb is not available in the server or the Xkb extension has not been properly initialized, XkbGetKeySyms returns BadAccess. If any allocation errors occur while obtaining the modifier map, XkbGetKeyModifierMap returns BadAlloc. DIAGNOSTICS
BadAccess The Xkb extension has not been properly initialized BadAlloc Unable to allocate storage X Version 11 libX11 1.2.1 XkbGetKeyModifierMap(3)

Check Out this Related Man Page

XkbGetKeySyms(3)						   XKB FUNCTIONS						  XkbGetKeySyms(3)

NAME
XkbGetKeySyms - Obtain the symbols for a subset of the keys in a keyboard description SYNOPSIS
Status XkbGetKeySyms (Display *dpy, unsigned int first, unsigned int num, XkbDescPtr xkb); ARGUMENTS
- dpy connection to X server - first keycode of first key to get - num number of keycodes for which syms desired - xkb Xkb description to be updated DESCRIPTION
XkbGetKeySyms sends a request to the server to obtain the set of keysyms bound to num keys starting with the key whose keycode is first. It waits for a reply and returns the keysyms in the map.syms field of xkb. If successful, XkbGetKeySyms returns Success. The xkb parameter must be a pointer to a valid Xkb keyboard description. If the client map in the xkb parameter has not been allocated, XkbGetKeySyms allocates and initializes it before obtaining the symbols. If a compatible version of Xkb is not available in the server or the Xkb extension has not been properly initialized, XkbGetKeySyms returns BadAccess. If num is less than 1 or greater than XkbMaxKeyCount, XkbGetKeySyms returns BadValue. If any allocation errors occur, XkbGetKeySyms returns BadAlloc. RETURN VALUES
Success The XkbGetKeySyms function returns Success if it gets a reply to a request to the server to obtain the set of keysyms bound to num keys starting with the key whose keycode is first. DIAGNOSTICS
BadAccess The Xkb extension has not been properly initialized BadAlloc Unable to allocate storage BadValue An argument is out of range X Version 11 libX11 1.6.0 XkbGetKeySyms(3)
Man Page

We Also Found This Discussion For You

1. UNIX for Advanced & Expert Users

Shopt -s histappend

What is the point of this? Whenever I close my shell it appends to the history file without adding this. I have never seen it overwrite my history file. # When the shell exits, append to the history file instead of overwriting it shopt -s histappend (3 Replies)
Discussion started by: cokedude
3 Replies