Justin M. Keyes 8a2aec9974 fix(startup): server fails if $NVIM_APPNAME is relative dir #30310 ... Problem: If $NVIM_APPNAME is a relative dir path, Nvim fails to start its primary/default server, and `v:servername` is empty. Root cause is d34c64e342, but this wasn't noticed until 96128a5076 started reporting the error more loudly. Solution: - `server_address_new`: replace slashes "/" in the appname before using it as a servername. - `vim_mktempdir`: always prefer the system-wide top-level "nvim.user/" directory. That isn't intended to be specific to NVIM_APPNAME; rather, each *subdirectory* ("nvim.user/xxx") is owned by each Nvim instance. Nvim "apps" can be identified by the server socket(s) stored in those per-Nvim subdirs. fix #30256		2024-09-08 12:48:32 -07:00
..
autochdir_spec.lua	test: improve test conventions	2024-04-23 18:17:04 +02:00
chars_spec.lua	test: improve test conventions	2024-04-23 18:17:04 +02:00
cursorbind_spec.lua	test: improve test conventions	2024-04-23 18:17:04 +02:00
defaults_spec.lua	fix(startup): server fails if $NVIM_APPNAME is relative dir #30310	2024-09-08 12:48:32 -07:00
keymap_spec.lua	test: improve test conventions	2024-04-23 18:17:04 +02:00
modified_spec.lua	test: improve test conventions	2024-04-23 18:17:04 +02:00
mousescroll_spec.lua	test: improve test conventions	2024-04-23 18:17:04 +02:00
num_options_spec.lua	test: improve test conventions	2024-04-23 18:17:04 +02:00
shortmess_spec.lua	test: improve test conventions	2024-04-23 18:17:04 +02:00
tabstop_spec.lua	test: improve test conventions	2024-04-23 18:17:04 +02:00
winfixbuf_spec.lua	test: improve test conventions	2024-04-23 18:17:04 +02:00