XMACTIVATEWMPROTOCOL(3)

📦
version 2.5.2 · 2 versions
, in alpine 3.24, arch rolling, centos-stream 9, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

💖 XmActivateWMProtocol — a library call bestie 💖

okay so welcome to the group chat, we're talking about XmActivateWMProtocol, and it's giving VendorShell convenience interface that activates a protocol. no cap, that's the whole vibe of the NAME section, so let's get into it 🫶

✨ SYNOPSIS ✨

#include <Xm/Protocols.h>
void XmActivateWMProtocol(
Widget shell,
Atom protocol);

yes bestie, that's it. two args. short, sweet, iconic 👑

🌸 DESCRIPTION 🌸

So XmActivateWMProtocol is what we call a convenience interface — like when your friend orders for the whole table so you don't have to 😌. Under the hood it calls XmActivateProtocol with the property value set to the atom returned by interning WM_PROTOCOLS. That's the whole thing. It's a little wrapper, and honestly? it ate.

Here's the deets on the args, one by one, no gatekeeping:

  • shell — Specifies the widget with which the protocol property is associated. So like, which widget is this protocol vibing with 💅
  • protocol — Specifies the protocol Atom. the literal atom, fr fr.
🎀 heads up: for a complete definition of VendorShell and its associated resources, go check out VendorShell(3). don't be out here guessing, bestie, the docs are right there 🦋

the squad. the mutuals. the ones you should also be reading, iykyk:

and that's the page, bestie 💜 this was XmActivateWMProtocol from the library call manual, and yes the footer says the exact same thing as the header, that's just the format, we don't question it, we respect it 😭💅

mwah, go activate a protocol, you're doing amazing 🌈⭐

📦 where this page comes from