aniani/vim
0
0
Fork 1
mirror of https://github.com/vim/vim.git synced 2025-09-26 04:04:07 -04:00
Code Activity

patch 9.0.0096: flag "new_value_alloced" is always true

Browse Source 
Problem:    Flag "new_value_alloced" is always true.
Solution:   Remove "new_value_alloced". (closes #10792)
This commit is contained in:
zeertzjq
2022-07-27 18:26:03 +01:00
committed by Bram Moolenaar
parent 122dea7007
commit f6782732ab
4 changed files with 14 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/option.c
View File

@@ -1716,8 +1716,6 @@ do_set(
#endif
unsigned newlen;
int comma;
int new_value_alloced; // new string option
// was allocated
// When using ":set opt=val" for a global option
// with a local value the local value will be
@@ -1785,13 +1783,11 @@ do_set(
s = newval;
newval = vim_strsave(s);
}
new_value_alloced = TRUE;
}
else if (nextchar == '<') // set to global val
{
newval = vim_strsave(*(char_u **)get_varp_scope(
&(options[opt_idx]), OPT_GLOBAL));
new_value_alloced = TRUE;
}
else
{
@@ -2060,7 +2056,6 @@ do_set(
if (save_arg != NULL) // number for 'whichwrap'
arg = save_arg;
new_value_alloced = TRUE;
}
/*
@@ -2109,8 +2104,7 @@ do_set(
// 'syntax' or 'filetype' autocommands may be
// triggered that can cause havoc.
errmsg = did_set_string_option(
opt_idx, (char_u **)varp,
new_value_alloced, oldval, errbuf,
opt_idx, (char_u **)varp, oldval, errbuf,
opt_flags, &value_checked);
secure = secure_saved;