XkbAllocIndicatorMaps(3)

📦
version 1.8.14 · 8 versions
, in alpine 3.24, arch rolling, nixos 26.05, nixpkgs unstable

✨ XkbAllocIndicatorMaps ✨

okay so bestie, welcome to the XKB FUNCTIONS corner of the libX11 manual — this one is literally all about one tiny little helper that sets up the indicators part of your keyboard description record. she's small, she's focused, she slays one job only 💅

✨ NAME ✨

XkbAllocIndicatorMaps — allocates, directly, the indicators member of the keyboard description record 🎀

✨ SYNOPSIS ✨

Status XkbAllocIndicatorMaps (variable_type *xkb);

✨ ARGUMENTS ✨

  • xkb — the keyboard description structure 🦋 (yes, this is the main character of the whole page, pls be nice to her)

✨ DESCRIPTION ✨

so here's the vibe check: the xkb parameter must point to a valid keyboard description. like, that's non-negotiable. if it doesn't? XkbAllocIndicatorMaps hits you with a BadMatch error and honestly, fair 💀

but if it is valid, she allocates and initializes the indicators member of the keyboard description record, and returns Success. icon behavior, no notes ✨

and if she can't allocate the indicators record for whatever reason? she reports a BadAlloc error. that's it. that's the whole thing, lowkey 🫶

✨ RETURN VALUES ✨

  • Success — XkbAllocIndicatorMaps returns Success if it is successful in allocating and initializing the indicators member of the keyboard description record 🌸

✨ DIAGNOSTICS ✨

  • BadMatch — a compatible version of Xkb was not available in the server, or an argument has correct type and range but is otherwise invalid 🙈
  • BadAlloc — unable to allocate storage 😭
ngl bestie, if you see BadMatch it's either a version mismatch with the server or the argument is valid-looking but still wrong. go check your xkb pointer first, iykyk 💜

k that's the whole page, and truly it's giving "short but essential." this came to you straight from X Version 11, libX11 1.8.14 — catch you in the next manpage, bestie, mwah 💖🎀🦋

📦 where this page comes from