1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
//! Terminal input events.
//!
//! [`Event`] is the typed output of [`Parser`], [`EventReader`], and the optional `EventStream`.
//! Termina reports ordinary input events such as keys, mouse input, focus changes, resize events,
//! and bracketed paste. It also keeps terminal responses such as CSI, OSC, and DCS in the same
//! public enum so callers can issue a query and read the response without a second internal event
//! model.
//!
//! Use [`EventReader::read`] or [`Terminal::read`] when reading from a process terminal. Use
//! [`Parser::pop`] when parsing bytes from a PTY, terminal multiplexer, or other caller-owned
//! input source. [`EventReader`] is the main place to look for event-reading examples and filter
//! behavior.
//!
//! # Implementation Notes
//!
//! Most event code is adapted from [crossterm events]. The main difference is intentional: Termina
//! includes escape sequences like [`Csi`] and [`Dcs`] in [`Event`] and does not split the model
//! into separate internal and public events. The key event types otherwise stay close to
//! crossterm's shape.
//!
//! [crossterm events]: https://docs.rs/crossterm/latest/crossterm/event/index.html
//! [`Csi`]: crate::escape::csi::Csi
//! [`Dcs`]: crate::escape::dcs::Dcs
//! [`EventReader`]: crate::EventReader
//! [`EventReader::read`]: crate::EventReader::read
//! [`Parser`]: crate::Parser
//! [`Parser::pop`]: crate::Parser::pop
//! [`Terminal::read`]: crate::Terminal::read
use crate::;
use crate;
use crate::;
pub
pub
pub
/// A parsed terminal input event or terminal protocol response.
///
/// Values of this type are returned by [`EventReader::read`], [`Terminal::read`], and
/// [`Parser::pop`]. See [`EventReader`] for the normal terminal-reading flow, including how
/// filters skip events without losing them.
/// A key event plus modifiers and protocol state.
///
/// `KeyEvent` appears inside [`Event::Key`], which is normally returned by [`EventReader::read`]
/// or [`Terminal::read`]. See [`EventReader`] for examples of filtering key events while leaving
/// other terminal events buffered.
///
/// `code` identifies the key, `kind` distinguishes press/release/repeat when the terminal reports
/// that detail, `modifiers` carries held modifier keys, and `state` carries protocol state such as
/// keypad-originated input.
///
/// Code that handles shortcuts should usually check `kind == KeyEventKind::Press` before acting.
/// Unix-style terminal input commonly reports only presses unless a keyboard enhancement protocol
/// requests event types, but the Windows legacy console API reports press and release records for
/// many keys. Ignoring `kind` can make a shortcut run twice on backends that expose releases.
///
/// Some key combinations also cannot be represented by some terminals at all. Crossterm's
/// [missing key combinations] issue is a useful catalogue of those terminal-level limitations;
/// report Termina bugs in Termina, not on that upstream issue.
///
/// # Implementation Notes
///
/// This mirrors the layout used by [crossterm key events].
///
/// [crossterm key events]: https://docs.rs/crossterm/latest/crossterm/event/struct.KeyEvent.html
/// [missing key combinations]: https://github.com/crossterm-rs/crossterm/issues/685
/// Whether a key was pressed, released, or repeated.
///
/// This controls whether a key event should trigger an action. Unix-style terminal input commonly
/// produces [`Self::Press`] only, while Windows legacy console input and enhanced keyboard
/// protocols can also produce [`Self::Release`] and [`Self::Repeat`]. Code that treats every
/// [`Event::Key`] as an action can therefore run twice for one physical key press. Shortcuts and
/// commands should usually act only on [`Self::Press`]. Some key combinations are also limited by
/// what the terminal can encode; Crossterm's [missing key combinations] issue is useful background
/// for those limitations, but Termina bugs should be reported to Termina.
///
/// [missing key combinations]: https://github.com/crossterm-rs/crossterm/issues/685
bitflags!
bitflags!
/// The key identity reported by the terminal.
/// Physical modifier keys reported as key events.
/// Media keys reported as key events.
/// Mouse input event with zero-based terminal cell coordinates.
///
/// Terminal mouse protocols encode cell positions as one-based coordinates, but Termina converts
/// them to zero-based `column` and `row` values for consistency with Rust indexing and the parser's
/// existing event model. SGR pixel mouse reports are represented separately as
/// [`crate::escape::csi::MouseReport::Sgr1016`].
/// The mouse action reported by the terminal.
/// Mouse buttons reported by terminal mouse tracking.