Fix some spelling mistakes

This commit is contained in:
Craig Barnes 2020-08-15 19:39:00 +01:00
parent ef1bab6559
commit 104fe2fa55
9 changed files with 12 additions and 12 deletions

View file

@ -325,7 +325,7 @@ The tertiary DA response is always `\EP!|464f4f54\E\\`. The `\EP!|` is
the standard tertiary DA response prefix, `DCS ! |`. The trailing
`\E\\` is of course the standard string terminator, `ST`.
In the response above, the interresting part is `464f4f54`; this is
In the response above, the interesting part is `464f4f54`; this is
the string _FOOT_ in hex.
The secondary DA response is `\E[>1;XXYYZZ;0c`, where XXYYZZ is foot's

View file

@ -37,7 +37,7 @@ cmd_scrollback_up(struct terminal *term, int rows)
/*
* This happens when scrolling up in a newly opened terminal;
* every single line (except those already visible) are
* uninitalized, and the loop above will bring us back to
* uninitialized, and the loop above will bring us back to
* where we started.
*/
return;

6
csi.c
View file

@ -334,7 +334,7 @@ csi_dispatch(struct terminal *term, uint8_t final)
/*
* Note: we never reset 'last-printed'. According to
* ECMA-48, the behaviour is undefined if REP was
* _not_ preceeded by a graphical character.
* _not_ preceded by a graphical character.
*/
int count = vt_param_get(term, 0, 1);
LOG_DBG("REP: '%lc' %d times", (wint_t)term->vt.last_printed, count);
@ -377,7 +377,7 @@ csi_dispatch(struct terminal *term, uint8_t final)
* - 29 ANSI text locator (i.e., DEC Locator mode).
*
* Note: we report ourselves as a VT220, mainly to be able
* to pass parameters, to indiciate we support sixel, and
* to pass parameters, to indicate we support sixel, and
* ANSI colors.
*
* The VT level must be synchronized with the secondary DA
@ -1416,7 +1416,7 @@ csi_dispatch(struct terminal *term, uint8_t final)
* determine level of support.
*
* We report ourselves as a VT220. This must be
* synchronized with the primary DA respons.
* synchronized with the primary DA response.
*
* Note: tertiary DA replies with "FOOT".
*/

View file

@ -58,7 +58,7 @@ CPU: i5-8250U
RAM: 8GB
Graphics: Intel UHD Graphcis 620
Graphics: Intel UHD Graphics 620
### Terminal configuration

View file

@ -733,7 +733,7 @@ keyboard_key(void *data, struct wl_keyboard *wl_keyboard, uint32_t serial,
xkb_keysym_t sym = xkb_state_key_get_one_sym(seat->kbd.xkb_state, key);
if (state == XKB_KEY_DOWN && term->conf->mouse.hide_when_typing &&
/* TODO: better way to detect modifers */
/* TODO: better way to detect modifiers */
sym != XKB_KEY_Shift_L && sym != XKB_KEY_Shift_R &&
sym != XKB_KEY_Control_L && sym != XKB_KEY_Control_R &&
sym != XKB_KEY_Alt_L && sym != XKB_KEY_Alt_R &&
@ -959,7 +959,7 @@ keyboard_modifiers(void *data, struct wl_keyboard *wl_keyboard, uint32_t serial,
xkb_state_update_mask(
seat->kbd.xkb_state, mods_depressed, mods_latched, mods_locked, 0, 0, group);
/* Update state of modifiers we're interrested in for e.g mouse events */
/* Update state of modifiers we're interested in for e.g mouse events */
seat->kbd.shift = xkb_state_mod_index_is_active(
seat->kbd.xkb_state, seat->kbd.mod_shift, XKB_STATE_MODS_DEPRESSED);
seat->kbd.alt = xkb_state_mod_index_is_active(

2
osc.c
View file

@ -512,7 +512,7 @@ osc_dispatch(struct terminal *term)
* Update color of already rendered cells.
*
* Note that we do *not* store the original palette
* index. Therefor, the best we can do is compare
* index. Therefore, the best we can do is compare
* colors - if they match, assume "our" palette index
* was the one used to render the cell.
*

View file

@ -119,7 +119,7 @@ fdm_reap(struct fdm *fdm, int fd, int events, void *data)
}
tll_foreach(reaper->children, it) {
/* Don't use wait() since we don't want to accidentaly reap
/* Don't use wait() since we don't want to accidentally reap
* the PTS slave */
pid_t pid = it->item;

View file

@ -610,7 +610,7 @@ grid_render_scroll(struct terminal *term, struct buffer *buf,
* So, we need to figure out when to SHM scroll, and when to
* memmove.
*
* For now, assume that the both methods perform rougly the same,
* For now, assume that the both methods perform roughly the same,
* given an equal number of bytes to move/allocate, and use the
* method that results in the least amount of bytes to touch.
*

View file

@ -421,7 +421,7 @@ struct terminal {
bool autosize;
} image;
unsigned params[5]; /* Collected parmaeters, for RASTER, COLOR_SPEC */
unsigned params[5]; /* Collected parameters, for RASTER, COLOR_SPEC */
unsigned param; /* Currently collecting parameter, for RASTER, COLOR_SPEC and REPEAT */
unsigned param_idx; /* Parameters seen */