https://gitlab.synchro.net/main/sbbs/-/issues/926#note_7213
I've traced this down to the addition of "clearabort()" to sbbs_t::getkey(): ```
+++ b/src/sbbs3/getkey.cpp
@@ -42,7 +42,7 @@ char sbbs_t::getkey(int mode)
YIELD(); // just in case someone is looping on getkey() when they shouldn't
return 0;
}
- clearabort();
+// clearabort();
if ((sys_status & SS_USERON || action == NODE_DFLT) && !(mode & (K_GETSTR | K_NOSPIN)))
mode |= (useron.misc & SPIN);
term->lncntr = 0;
```
By removing this call, hitting Ctrl-C during a scan for message text works *more* like it did in v3.20, but not exactly: the "Reading" prompt is redisplayed before the actual abortion of the scan. For example:
```
■ Main ■ 0:00:04 [2] DOVE-Net [1] General: F
find yo text son
Sub-board: General, Group: DOVE-Net, or All: A
[√] Display Subjects Only? No
Text to search for: ALSJKDF
Main Sysop Notices 111 Main General 500 ■ Reading ■ Main General (?=Menu) (348 of 500):
Message Scan aborted.
■ Main ■ 0:00:08 [2] DOVE-Net [1] General:
```
In v3.20, that "Reading" prompt would not be redisplayed.
I'm not sure why all the additions of clearabort() calls (in the Terminal Abstraction branch) to the input functions, but they appear to be causing issues with Ctrl-C behavior.
--- SBBSecho 3.25-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)