Problem: Misspelled mkspellmem as makespellmem.
Solution: Drop duplicate help entry, fix test. (Naruhiko Nishino, Ken
Takata, closesvim/vim#4437)
076073950c
Problem: Using expressions in a modeline is unsafe.
Solution: Disallow using expressions in a modeline, unless the
'modelineexpr' option is set. Update help, add more tests.
110289e781
Problem: Modeline test fails when run by root.
Solution: Set 'modeline' for the test. (James McCoy, closesvim/vim#3592)
9691f82f86
N/A patches:
vim-patch:8.1.0208: file left behind after running individual test
Problem: When executing an insecure function the secure flag is stuck.
(Gabriel Barta)
Solution: Restore "secure" instead of decrementing it. (closesvim/vim#3705)
48f377a476
Problem: Setting 'filetype' in a modeline causes an error (Hirohito
Higashi).
Solution: Don't add the P_INSECURE flag when setting 'filetype' from a
modeline. Also for 'syntax'.
916a818cea
Problem: May evaluate insecure value when appending to option.
Solution: Set the secure flag when changing an option that was previously
set insecurely. Also allow numbers for the characters from
'spelllang' that are used for LANG.vim.
247bb7e43b
Problem: Cannot build without the sandbox.
Solution: Set the secure option instead of using the sandbox. Also restrict
the characters from 'spelllang' that are used for LANG.vim.
(suggested by Yasuhiro Matsumoto)
82e8c92ebe
Problem: Evaluating a modeline might invoke using a shell command. (Paul
Huber)
Solution: Set the sandbox flag when setting options from a modeline.
5958f95a40
Problem: Defining function in sandbox is inconsistent, cannot use :function
but can define a lambda.
Solution: Allow defining a function in the sandbox, but also use the sandbox
when executing it. (closesvim/vim#3182)
93343725b5
fix appimage failure:
-- Deploying icons --
Deploying icon /home/travis/build/neovim/bot-ci/build/neovim/runtime/nvim.png
WARNING: x and y resolution of icon are not equal: /home/travis/build/neovim/bot-ci/build/neovim/runtime/nvim.png
ERROR: Icon /home/travis/build/neovim/bot-ci/build/neovim/runtime/nvim.png has invalid x resolution: 104
ERROR: Valid resolutions for icons are: 8x8, 16x16, ...
Failed to deploy icon: /home/travis/build/neovim/bot-ci/build/neovim/runtime/nvim.png
mv: cannot stat '/home/travis/build/neovim/bot-ci/build/neovim/build/nvim.appimage*': No such file or directory
ref https://github.com/neovim/bot-ci/issues/144
Maintenance release to fix issues found in v0.3.4.
FIXES:
f891131c6b#9894 options: properly reset directories on 'autochdir'
9a5488c2a6 Remove MSVC optimization workaround for SHM_ALL
1793ba8176 Make SHM_ALL to a variable instead of a compound literal #define
947069ba14 doc: mention "pynvim" module rename
46c7e12f27#9629 screen: don't crash when drawing popupmenu with 'rightleft' option
f1843c0035 vim-patch:8.1.0677: look-behind match may use the wrong line number
1204421888#8325 :terminal : set topline based on window height
aaa8c3d711#9504 :recover : Fix crash on non-existent *.swp
gcc-9 has [improved compliance] with the C spec for lifetime of compound
literals, tying their lifetime to block scope instead of function scope.
This makes the behavior comparable to all other automatic variables.
Using the SHM_ALL #define instantiated a compound literal local to an if
clause and assigned the address to a "char_u *". Since the pointer was
then being used outside of the if clause, it was using an invalid
address.
[improved compliance]: https://gcc.gnu.org/gcc-9/porting_to.html#complitCloses#9855
crash reported in #9584
Problem: Look-behind match may use the wrong line number. (Dominique Pelle)
Solution: Use the line number in regsave instead of the one in behind_pos,
we may be looking at the previous line. (closesvim/vim#3749)
866f355814
This maintenance release fixes some issues found in v0.3.3.
FIXES:
8a7b6200fb#9487 provider: improve error message if provider is missing
44ea903ca5#9468 checkhealth: detect broken pip
b4028056fa Windows: nvim-qt v0.2.12 (fix potential "blank screen" at startup)
Move `has_eval_provider()` check to `eval_call_provider()` to make sure that
every code path calls it first.
Previously we would, when pynvim was missing, get a nice error message for
`:python3 1`, but not for `:py3file blah`.
Fixes https://github.com/neovim/neovim/issues/9485
