summaryrefslogtreecommitdiff
path: root/devdocs/elisp/inhibiting-interaction.html
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2025-08-14 22:58:58 -0500
committerCraig Jennings <c@cjennings.net>2025-08-14 22:58:58 -0500
commit82ba818ff456bcd6d56a06226e3f27e98fbb55c3 (patch)
tree158cfc17b2f644a10f063cb546752cfaae12c97f /devdocs/elisp/inhibiting-interaction.html
parent9278ddd4ea1a8b1a4c1edaa8894516e3f48d245b (diff)
downloaddotemacs-82ba818ff456bcd6d56a06226e3f27e98fbb55c3.tar.gz
dotemacs-82ba818ff456bcd6d56a06226e3f27e98fbb55c3.zip
removing all downloaded devdocs files
Diffstat (limited to 'devdocs/elisp/inhibiting-interaction.html')
-rw-r--r--devdocs/elisp/inhibiting-interaction.html12
1 files changed, 0 insertions, 12 deletions
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 @@
- <h3 class="section">Inhibiting Interaction</h3> <p>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. </p> <p>Binding the <code>inhibit-interaction</code> variable to something non-<code>nil</code> makes Emacs signal a <code>inhibited-interaction</code> error instead of prompting, which can then be used by the server process to handle these situations. </p> <p>Here’s a typical use case: </p> <div class="lisp"> <pre class="lisp">(let ((inhibit-interaction t))
- (respond-to-client
- (condition-case err
- (my-client-handling-function)
- (inhibited-interaction err))))
-</pre>
-</div> <p>If <code>my-client-handling-function</code> ends up calling something that asks the user for something (via <code>y-or-n-p</code> or <code>read-from-minibuffer</code> or the like), an <code>inhibited-interaction</code> error is signalled instead. The server code then catches that error and reports it to the client. </p><div class="_attribution">
- <p class="_attribution-p">
- Copyright &copy; 1990-1996, 1998-2022 Free Software Foundation, Inc. <br>Licensed under the GNU GPL license.<br>
- <a href="https://www.gnu.org/software/emacs/manual/html_node/elisp/Inhibiting-Interaction.html" class="_attribution-link">https://www.gnu.org/software/emacs/manual/html_node/elisp/Inhibiting-Interaction.html</a>
- </p>
-</div>