-*diff.txt* For Vim version 9.1. Last change: 2025 Aug 06
+*diff.txt* For Vim version 9.1. Last change: 2025 Sep 15
VIM REFERENCE MANUAL by Bram Moolenaar
that function so the diff algorithm will align based on it.
To use it, set anchors using 'diffanchors' which is a comma-separated list of
-{address} in each file, and then add "anchor" to 'diffopt'. Internaly, Vim
+{address} in each file, and then add "anchor" to 'diffopt'. Internally, Vim
splits each file up into sections split by the anchors. It performs the diff
on each pair of sections separately before merging the results back.
-*helphelp.txt* For Vim version 9.1. Last change: 2025 Aug 06
+*helphelp.txt* For Vim version 9.1. Last change: 2025 Sep 15
VIM REFERENCE MANUAL by Bram Moolenaar
template.
Vim help files generally use 2 spaces after a sentence (since they are written
-using a fixed-width font and that was the prefered style in the 70s/80s), like
-what is described here: https://english.stackexchange.com/a/2602
+using a fixed-width font and that was the preferred style in the 70s/80s),
+like what is described here: https://english.stackexchange.com/a/2602
The first line in a help file should have the following format:
Each anchor line splits the buffer (the split happens above the
anchor), with each part being diff'ed separately before the final
result is joined. When more than one {address} are provided, the
- anchors will be sorted interally by line number. If using buffer
+ anchors will be sorted internally by line number. If using buffer
local options, each buffer should have the same number of anchors
(extra anchors will be ignored). This option is only used when
'diffopt' has "anchor" set. See |diff-anchors| for more details and
-*terminal.txt* For Vim version 9.1. Last change: 2025 Sep 14
+*terminal.txt* For Vim version 9.1. Last change: 2025 Sep 15
VIM REFERENCE MANUAL by Bram Moolenaar
set a temporary breakpoint at the specified position
*:Clear* delete the breakpoint at the cursor position
*:ToggleBreak* set a breakpoint at the cursor position or delete all
- breakpoints at the cursor positoin
+ breakpoints at the cursor position
*:Step* execute the gdb "step" command
*:Over* execute the gdb "next" command (`:Next` is a Vim command)
-*wayland.txt* For Vim version 9.1. Last change: 2025 Sep 02
+*wayland.txt* For Vim version 9.1. Last change: 2025 Sep 15
VIM REFERENCE MANUAL by Bram Moolenaar
case scenario protocols, see |wayland-focus-steal|. Selection in this case
essentially means the "clipboard." You can check if your Wayland compositor
supports either of these protocols by running the wayland-info command, which
-should be bunded with libwayland on your system: >
+should be bundled with libwayland on your system: >
wayland-info | grep -E '(ext_data_control|zwlr_data_control)'
<If grep finds a match, then you have either or both protocols on your system.
If you don't get any match, then please see |wayland-focus-steal| for more
}
}
- if (!local) // ':set' used insted of ':setlocal'
+ if (!local) // ':set' used instead of ':setlocal'
// Cache the callback array
if (copy_cpt_callbacks(&cpt_cb, &cpt_cb_count, curbuf->b_p_cpt_cb,
curbuf->b_p_cpt_count) != OK)
char_u *str, // What to send
char_u **result, // Set to result of expr
char_u **receiver, // Full path of "name"
- int is_expr, // Is it an expresison or keystrokes?
+ int is_expr, // Is it an expression or keystrokes?
int timeout, // In milliseconds
int silent) // Don't complain if socket doesn't exist
{
else
vim_free(path);
- // Exit, we aren't waiting for a reponse
+ // Exit, we aren't waiting for a response
return 0;
}
/*
* Append a message to a command. Note that "len" is the length of contents.
- * Returns OK on sucess and FAIL on failure
+ * Returns OK on success and FAIL on failure
*/
static int
socket_server_append_msg(ss_cmd_T *cmd, char_u type, char_u *contents, int len)
STRLEN(result) + 1); // We add +1 in case "result"
// is an empty string.
else
- // An error occured, return an error msg instead
+ // An error occurred, return an error msg instead
socket_server_append_msg(&rcmd, SS_MSG_TYPE_STRING,
(char_u *)_(e_invalid_expression_received),
STRLEN(e_invalid_expression_received));
}
/*
- * Check if socket "name" is reponsive by sending an ALIVE command. This does
+ * Check if socket "name" is responsive by sending an ALIVE command. This does
* not require the socket server to be active.
*/
static int
if (maxwidth == 0)
return;
- // Reset got_int to avoid build_stl_str_hl() isn't evaluted.
+ // Reset got_int to avoid build_stl_str_hl() isn't evaluated.
got_int = FALSE;
if (tpl_is_vert)
LOG_TRN("Received OSC response: %s", (char*)tp);
// Check if it is a valid OSC sequence, and consume it. OSC format
// consists of:
- // <idenfitifer><data><terminator>
+ // <identifier><data><terminator>
// <identifier> is either <Esc>] or an OSC character
// <terminator> can be '\007', <Esc>\ or STERM.
cur = 1 + (tp[0] == ESC);
call assert_equal('a#', getline('.'))
set completeopt&
- " Test 2: Filter nonkeyword and keyword matches with differet startpos
+ " Test 2: Filter nonkeyword and keyword matches with different startpos
set completeopt+=menuone,noselect
call feedkeys("S#a\<C-N>b\<F2>\<F3>\<Esc>0", 'tx!')
call assert_equal(['abc', 'abcd', '#abar'], b:matches->mapnew('v:val.word'))
call assert_equal(2, g:CallCount)
call assert_equal('a#', getline('.'))
- " Test 2: Filter nonkeyword and keyword matches with differet startpos
+ " Test 2: Filter nonkeyword and keyword matches with different startpos
for fuzzy in range(2)
if fuzzy
set completeopt+=fuzzy
END
v9.CheckSourceFailure(lines, 'E1326: Variable "foo" not found in object "B"')
- # Using super to access an overriden method in the parent class
+ # Using super to access an overridden method in the parent class
lines =<< trim END
vim9script
call assert_equal('2', getreg('+'))
- " Check if wlrestore doesn't disconnect the display if not nessecary by seeing
+ " Check if wlrestore doesn't disconnect the display if not necessary by seeing
" if Vim doesn't lose the selection
call setreg('+', 'testing', 'c')
bw!
- " Check behaviour when selecton is cleared (empty)
+ " Check behaviour when selection is cleared (empty)
call system('wl-copy --clear')
call assert_fails('put +', 'E353:')
endfunc
bw!
endfunc
-" this caused a NULL derefence
+" this caused a NULL dereference
func Test_xxd_null_dereference()
CheckUnix
CheckExecutable /bin/true
struct wl_seat *proxy;
char *label; // Name of seat as text (e.g. seat0,
// seat1...).
- uint32_t capabilities; // Bitmask of the capabilites of the seat
+ uint32_t capabilities; // Bitmask of the capabilities of the seat
// (pointer, keyboard, touch).
} vwl_seat_T;
/*
* Connect to the display with name; passing NULL will use libwayland's way of
* getting the display. Additionally get the registry object but will not
- * starting listening. Returns OK on sucess and FAIL on failure.
+ * starting listening. Returns OK on success and FAIL on failure.
*/
static int
vwl_connect_display(const char *display)
// better to do it this way. Additionally other Wayland applications
// seem to set the selection every time.
//
- // There should be no noticable performance change since its not
+ // There should be no noticeable performance change since its not
// like this is running in the background constantly in Vim, only
// runs once when the user yanks text to the system clipboard.
vwl_data_source_destroy(&clip_sel->source, FALSE);