summaryrefslogtreecommitdiff
path: root/devdocs/elisp/recording-input.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/recording-input.html
parent9278ddd4ea1a8b1a4c1edaa8894516e3f48d245b (diff)
downloaddotemacs-82ba818ff456bcd6d56a06226e3f27e98fbb55c3.tar.gz
dotemacs-82ba818ff456bcd6d56a06226e3f27e98fbb55c3.zip
removing all downloaded devdocs files
Diffstat (limited to 'devdocs/elisp/recording-input.html')
-rw-r--r--devdocs/elisp/recording-input.html14
1 files changed, 0 insertions, 14 deletions
diff --git a/devdocs/elisp/recording-input.html b/devdocs/elisp/recording-input.html
deleted file mode 100644
index ffd2688c..00000000
--- a/devdocs/elisp/recording-input.html
+++ /dev/null
@@ -1,14 +0,0 @@
- <h4 class="subsection">Recording Input</h4> <dl> <dt id="recent-keys">Function: <strong>recent-keys</strong> <em>&amp;optional include-cmds</em>
-</dt> <dd>
-<p>This function returns a vector containing the last 300 input events from the keyboard or mouse. All input events are included, whether or not they were used as parts of key sequences. Thus, you always get the last 300 input events, not counting events generated by keyboard macros. (These are excluded because they are less interesting for debugging; it should be enough to see the events that invoked the macros.) </p> <p>If <var>include-cmds</var> is non-<code>nil</code>, complete key sequences in the result vector are interleaved with pseudo-events of the form <code>(nil . <var>COMMAND</var>)</code>, where <var>COMMAND</var> is the binding of the key sequence (see <a href="command-overview">Command Overview</a>). </p> <p>A call to <code>clear-this-command-keys</code> (see <a href="command-loop-info">Command Loop Info</a>) causes this function to return an empty vector immediately afterward. </p>
-</dd>
-</dl> <dl> <dt id="open-dribble-file">Command: <strong>open-dribble-file</strong> <em>filename</em>
-</dt> <dd>
- <p>This function opens a <em>dribble file</em> named <var>filename</var>. When a dribble file is open, each input event from the keyboard or mouse (but not those from keyboard macros) is written in that file. A non-character event is expressed using its printed representation surrounded by ‘<samp>&lt;…&gt;</samp>’. Be aware that sensitive information (such as passwords) may end up recorded in the dribble file. </p> <p>You close the dribble file by calling this function with an argument of <code>nil</code>. </p>
-</dd>
-</dl> <p>See also the <code>open-termscript</code> function (see <a href="terminal-output">Terminal Output</a>). </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/Recording-Input.html" class="_attribution-link">https://www.gnu.org/software/emacs/manual/html_node/elisp/Recording-Input.html</a>
- </p>
-</div>