From 82ba818ff456bcd6d56a06226e3f27e98fbb55c3 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Thu, 14 Aug 2025 22:58:58 -0500 Subject: removing all downloaded devdocs files --- devdocs/elisp/inhibiting-interaction.html | 12 ------------ 1 file changed, 12 deletions(-) delete mode 100644 devdocs/elisp/inhibiting-interaction.html (limited to 'devdocs/elisp/inhibiting-interaction.html') diff --git a/devdocs/elisp/inhibiting-interaction.html b/devdocs/elisp/inhibiting-interaction.html deleted file mode 100644 index e5f23a15..00000000 --- a/devdocs/elisp/inhibiting-interaction.html +++ /dev/null @@ -1,12 +0,0 @@ -

Inhibiting Interaction

It’s sometimes useful to be able to run Emacs as a headless server process that responds to commands given over a network connection. However, Emacs is primarily a platform for interactive usage, so many commands prompt the user for feedback in certain anomalous situations. This makes this use case more difficult, since the server process will just hang waiting for user input.

Binding the inhibit-interaction variable to something non-nil makes Emacs signal a inhibited-interaction error instead of prompting, which can then be used by the server process to handle these situations.

Here’s a typical use case: 

(let ((inhibit-interaction t))
-  (respond-to-client
-   (condition-case err
-       (my-client-handling-function)
-     (inhibited-interaction err))))
-
-

If my-client-handling-function ends up calling something that asks the user for something (via y-or-n-p or read-from-minibuffer or the like), an inhibited-interaction error is signalled instead. The server code then catches that error and reports it to the client.

-

- Copyright © 1990-1996, 1998-2022 Free Software Foundation, Inc.
Licensed under the GNU GPL license.
- https://www.gnu.org/software/emacs/manual/html_node/elisp/Inhibiting-Interaction.html -

-
-- cgit v1.2.3