XkbGetNameChanges(3)

💖 XkbGetNameChanges — XKB FUNCTIONS 💖

okay bestie, welcome to the XkbGetNameChanges(3) page, part of the whole libX11 XKB situation ✨

---

🌸 NAME 🌸

XkbGetNameChanges — it updates your local copy of the keyboard description with the actual values of the results from one or more calls to XkbNoteNameChanges. like, you took notes, now you go get the real thing 🫶

---

🎀 SYNOPSIS 🎀

Status XkbGetNameChanges (Display *dpy, XkbDescPtr xkb,
       XkbNameChangesPtr changes);

---

✨ ARGUMENTS ✨

• dpy — your connection to the X server. the group chat line, basically 💅
• xkb — the keyboard description that the names get copied into. this is where the tea gets poured 🍓
• changes — the name components you want fetched from the server. your shopping list, no cap 🛍️

---

🦋 DESCRIPTION 🦋

so what it does is: it looks at the changes parameter 👀, pulls the necessary info off the server, and drops the results straight into the xkb keyboard description. iconic behavior fr fr.

⚠️ heads up: XkbGetNamesChanges can generate BadAlloc, BadImplementation, and BadMatch errors. (yes it's spelled like that on the page, that's just how the docs wrote it 😭)

---

💀 DIAGNOSTICS 💀

• BadAlloc — couldn't allocate storage. the mall run failed, literally 💀
• BadImplementation — invalid reply from the server. the server is giving nothing but red flags 🚩
• BadMatch — either a compatible version of Xkb wasn't available in the server, or an argument has the correct type and range but is otherwise invalid. it's giving "looks fine, is not fine" 🙈

---

👑 SEE ALSO 👑

• XkbNoteNameChanges(3) — the note-taking bestie this one depends on 🫶

---

okay that's the whole page, ty for coming to my ted talk 💜

sign-off time: this little masterpiece lives in X Version 11, shipped with libX11 1.8.4, and it's filed under XkbGetNameChanges(3) 💅✨ mwah, go forth and get those name changes bestie 🎀🦋