From eca81082a142e86dac1e9d18321d577a2390805a Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Fri, 27 Feb 2026 18:17:36 +0000 Subject: [PATCH] ; Fix some comments. --- src/blockinput.h | 14 +++++++------- src/keyboard.h | 6 +++--- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/src/blockinput.h b/src/blockinput.h index 3d394a8b554..b34ce2cc55f 100644 --- a/src/blockinput.h +++ b/src/blockinput.h @@ -28,21 +28,21 @@ INLINE_HEADER_BEGIN To avoid this, we make the following requirements: - * Everyone must evaluate BLOCK_INPUT before performing actions that - might conflict with a signal handler, and then call UNBLOCK_INPUT - after performing them. Calls BLOCK_INPUT and UNBLOCK_INPUT may be - nested. + * Everyone must call block_input before performing actions that + might conflict with a signal handler, and then call unblock_input + after performing them. Calls to block_input and unblock_input + may be nested. * Any complicated interrupt handling code should test - INPUT_BLOCKED_P, and put off its work until later. + input_blocked_p, and put off its work until later. * If the interrupt handling code wishes, it may set pending_signals to a non-zero value. If that flag is set - when input becomes unblocked, UNBLOCK_INPUT will then read + when input becomes unblocked, unblock_input will then read input and process timers. Historically, Emacs signal handlers did much more than they do now, - and this caused many BLOCK_INPUT calls to be sprinkled around the code. + and this caused many block_input calls to be sprinkled around the code. FIXME: Remove calls that aren't needed now. */ extern volatile int interrupt_input_blocked; diff --git a/src/keyboard.h b/src/keyboard.h index 67eff7678e8..b88752dcb86 100644 --- a/src/keyboard.h +++ b/src/keyboard.h @@ -242,7 +242,7 @@ extern KBOARD *initial_kboard; In the any-kboard state, this is the kboard from which we are right now considering input. We can consider input from another - kboard, but doing so requires throwing to wrong_kboard_jmpbuf. */ + kboard, but doing so requires returning -2 (wrong_kboard_jmpbuf). */ extern KBOARD *current_kboard; @@ -258,12 +258,12 @@ extern uintmax_t num_input_events; /* The location of point immediately before the last command was executed, or the last time the undo-boundary command added a - boundary.*/ + boundary. */ extern ptrdiff_t point_before_last_command_or_undo; /* The value of current_buffer immediately before the last command was executed, or the last time the undo-boundary command added a - boundary.*/ + boundary. */ extern struct buffer *buffer_before_last_command_or_undo; extern struct buffer *prev_buffer;