Next: , Previous: Search, Up: Commands

6.1.3 Ad-Hoc Commands

jabber.el supports a subset of XEP-0050, the standard for Ad-Hoc Commands. As the name implies, this can be used for just about anything. In particular, it is used not only by services, but also by clients (e.g. Psi, and jabber.el itself).

To find which commands are available, run “Request command list” (jabber-ahc-get-list).1

To run a command from the list, put point over it and run “Execute command” (jabber-ahc-execute-command), accepting the defaults for JID and node. (If you already know those, you could of course enter them yourself.)

What happens next depends on the command and the service. In some cases, the service just responds that the command has been run. You may also get a form to fill out. This form may have multiple stages, in which case there are “Next” and “Previous” buttons for navigating between stages. You may also see “Complete”, which runs the command skipping any remaining stages of the form, and “Cancel”, which cancels the command.

Currently, jabber.el uses ad-hoc commands for setting presence remotely. If you realize that you forgot to set your client to “away” with a low priority, you can do it remotely from any JID from jabber-account-list. So, you can add disabled JIDs in jabber-account-list to allow them control your presence.2


[1] This is the same thing as a disco items request to the node

[2] Most Jabber servers also support kicking a client off the net by logging in with another client with exactly the same resource.