mirrors/neovim
1
0
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2025-10-07 18:36:30 +00:00
Code Issues Packages Projects Releases Wiki Activity
16,390 Commits 10 Branches 54 Tags
3566244d0e90d1efcf50d5136ab77d9a19aea9a1
Commit Graph

10532 Commits

Author SHA1 Message Date
Daniel Hahler
ac6671946a move changedOneline, changed_bytes 2019-08-07 14:21:23 +02:00
Daniel Hahler
53210c16d1 move changed_common 2019-08-07 14:21:23 +02:00
Daniel Hahler
0e5314f56e move changed_int/changed_internal 2019-08-07 14:21:23 +02:00
Daniel Hahler
a822b3e547 move changed 2019-08-07 14:21:23 +02:00
Daniel Hahler
2a421e52e4 move change_warning 2019-08-07 14:21:23 +02:00
Daniel Hahler
e8cd2bcf37 header 2019-08-07 14:21:23 +02:00
Daniel Hahler
4a8a87c3a9 orig src/nvim/change.c 2019-08-07 14:21:23 +02:00
Björn Linse
d75fc87dec Merge pull request #10703 from ngortheone/clang_dead2 
clang/"dead assignment": suppessed getchar.c

Possibly invalid, read on line 1972:
if (keylen >= 0 && keylen <= typebuf.tb_len) {
 2019-08-07 10:27:07 +02:00
Björn Linse
6fb0020df4 Merge pull request #10513 from bfredl/bytecount 
api/lua: add {byte_count} parameter to line region change event
 2019-08-06 20:25:46 +02:00
Björn Linse
c0993ed343 lua: support getting UTF-32 and UTF-16 sizes of replaced text 2019-08-06 20:24:36 +02:00
Daniel Hahler
dc1359bf8e Fix list_features to include space after first feature (#10711) 
Regressed in e134cc9d4a: the use of list_in_columns was not adding a
space after the first features, because we do not start on a new line:

> Features: -acl+iconv +tui

This moves all the related code to `list_features`, and just joins them
with spaces.
 2019-08-06 18:55:14 +02:00
Björn Linse
b0e26199ec lua: add {old_byte_size} to on_lines buffer change event 2019-08-06 17:01:47 +02:00
erw7
d6f15ccc3c remove DYNAMIC_ICONV 2019-08-06 12:44:22 +09:00
Jan Edmund Lazo
11a6dac8c9 vim-patch:8.1.1467: cscope test fails 
Problem:    Cscope test fails.
Solution:   Update expected text.
d6ec1730ba
 2019-08-05 22:41:51 -04:00
Jan Edmund Lazo
ce7bcdec23 vim-patch:8.1.1465: allocating wrong amount of memory 
Problem:    Allocating wrong amount of memory. (Yegappan Lakshmanan)
Solution:   Use sizeof() for right type of struct.
a37833dbd7
 2019-08-05 22:40:48 -04:00
Daniel Hahler
d55b12ea50 f_environ: cleanup/refactor 
- use os_getenvname_at_index / os_getenv
- f_getenv: empty (*p == NUL) is not null (undefined)
 2019-08-06 01:23:11 +02:00
Daniel Hahler
fd66ad2262 vim-patch:8.1.1305: there is no easy way to manipulate environment variables 
Problem:    There is no easy way to manipulate environment variables.
Solution:   Add environ(), getenv() and setenv(). (Yasuhiro Matsumoto,
            closes vim/vim#2875)
691ddeefb5
 2019-08-06 01:17:32 +02:00
Ihor Antonov
b09e03c64d clang/"dead assignment": screen.c #10702 
Suppress the warning.

mb_c and mb_l describe a char together, they are not independent variables. The
coupled assignments are good practice to avoid future confusion, even if the
current code doesn't use an assigned value.
 2019-08-06 00:53:54 +02:00
Ihor Antonov
512f24f71d clang/"dead assignment": suppessed 
To ensure consistency and avoid possible errors in the code
the assigment is considered to be legit.
 2019-08-05 18:40:31 -04:00
Jan Edmund Lazo
7086751c5e vim-patch:8.1.1439: ga_grow(): 1.5x growth rate #10699 
Problem:    Json_encode() is very slow for large results.
Solution:   In the growarray use a growth of at least 50%. (Ken Takata,
            closes vim/vim#4461)
c47ed44be7
 2019-08-05 23:42:41 +02:00
Björn Linse
f5d1e0e7b1 Merge pull request #10690 from bfredl/lua_print 
lua: laundry list (crashes and additions)
 2019-08-05 13:59:40 +02:00
Björn Linse
88938634e7 lua: add vim.in_fast_event() to check if we are in a luv callback 2019-08-05 13:57:24 +02:00
Björn Linse
e6d77993d1 lua: do not crash on syntax error in debug.debug() 2019-08-05 13:19:44 +02:00
Björn Linse
d3a7bdefb0 lua: immediate-callback safe print() 2019-08-05 13:19:44 +02:00
Jan Edmund Lazo
6871445dfe vim-patch:8.1.1383: warning for size_t/int mixup (#10694) 
Problem:    Warning for size_t/int mixup.
Solution:   Change type. (Mike Williams)
d33a764123
 2019-08-05 03:35:46 +02:00
Justin M. Keyes
45c34bd84a :doautocmd : Never show "No matching autocommands" #10689 
The message is useless, it doesn't even mention the event name.

vim_dev discussion:
https://groups.google.com/forum/#!msg/vim_dev/RTbq58TMq9w/Xr4rSoUTCgAJ

ref: https://github.com/vim/vim/issues/4300
 2019-08-05 03:33:45 +02:00
Jan Edmund Lazo
01ddb39699 vim-patch:8.1.1311: test: abort autocmd with exception #10692 
Problem:    Aborting an autocmd with an exception is not tested.
Solution:   Add a test.  Also shows how to abort a command by throwing an
            exception.
23b5139234
 2019-08-05 01:54:17 +02:00
Jan Edmund Lazo
a724209b5a vim-patch:8.1.1251: test completion of mapping keys #10691 
Problem:    No test for completion of mapping keys.
Solution:   Add a test.  Also clean up the code.
2cb9f02532
 2019-08-05 01:12:35 +02:00
Justin M. Keyes
2141dc2262 provider: check #Call() if g:loaded_xx_provider=2 2019-08-04 13:23:46 +02:00
Justin M. Keyes
5e6a08f2e6 provider: skip non-provider has() feature-names 
We don't want to retry autoload sourcing (slow) for every random has()
query that finds it way to eval_call_provider().
 2019-08-04 13:23:46 +02:00
Justin M. Keyes
241956720d provider: g:loaded_xx_provider=2 means "enabled and working" 
Value of 1 cannot be used, because users might set that in their vimrc
to _disable_ a provider, which would confuse :checkhealth and has().
 2019-08-04 13:23:46 +02:00
Justin M. Keyes
66938b928c provider: decide status by g:loaded_xx_provider 2019-08-04 13:23:46 +02:00
Rui Abreu Ferreira
2cfe4748e5 provider: let providers decide their status 
Instead of deciding provider status in eval_has_provider, move the
decision to the provider Vim scripts.

Previously, provider loading worked as follows:

1. eval_has_provider() verified provider availability by searching for
   the provider#providername#Call function and cached this verificaion as a static
   variable for some providers
2. providers short-circuited on loading to prevent the definition of the
   Call function (with the exception of the node provider that did not)

This commit changes the expected interface between nvim and its
providers to facilitate provider reloading, by splitting the
verification of the provider from the availability of the Call function.

eval_has_provider() now checks for a provider#providername#enabled
variable. It is up to the provider script to set this to 0 or 1
accordingly. eval_call_provider() remains unchanged.

All providers hosting a Call function were updated to respect this.

The clipboard provider now has a Reload function to reload the
provider.
 2019-08-04 13:23:46 +02:00
Jan Edmund Lazo
5dd860fd73 vim-patch:8.1.1237: error for using "compl", reserved word in C++ 
Problem:    Error for using "compl", reserved word in C++.
Solution:   Rename to "complp". (suggestion by Ken Takata)
52111f8231
 2019-08-03 12:38:50 -04:00
Jan Edmund Lazo
01b2dac727 vim-patch:8.1.1796: :argdo is not tested 
Problem:    :argdo is not tested
Solution:   Add a test.
72e1b39111
 2019-08-03 11:38:52 -04:00
Jan Edmund Lazo
620a906406 vim-patch:8.1.1775: error message may be empty in filetype test 
Problem:    Error message may be empty in filetype test.
Solution:   Use v:exception instead. (Daniel Hahler, closs vim/vim#4744)
eee9f65b2a
 2019-08-02 19:51:04 -04:00
Jan Edmund Lazo
12fe0cf5f9 vim-patch:8.1.1762: some filetype rules are in the wrong place 
Problem:    Some filetype rules are in the wrong place.
Solution:   Move to the right place.  Add a few more tests.
c273405188
 2019-08-02 19:48:32 -04:00
Jan Edmund Lazo
d827a750f7 vim-patch:8.1.1761: filetype "vuejs" causes problems for some users 
Problem:    Filetype "vuejs" causes problems for some users.
Solution:   Rename to "vue".
4248111497
 2019-08-02 19:46:34 -04:00
Jan Edmund Lazo
cdd8540a20 vim-patch:8.1.1187: cannot recognize Pipfile 
Problem:    Cannot recognize Pipfile.
Solution:   Use existing filetypes. (Charles Ross, closes vim/vim#4280)
3a4c53ba51
 2019-08-02 19:44:37 -04:00
Daniel Hahler
24fb7eefaa terminfo_start: use unibi_from_term, skip without TERM (#10670) 
This is clearer/more explicit and avoids potential mismatch between what unibilium thinks vs what Nvim thinks.

For reference: e3b16d6219/uniutil.c (L203-L211)
 2019-08-02 19:39:29 +02:00
Justin M. Keyes
b92a5bc3c4 Merge #10664 from janlazo/vim-8.1.1780 
vim-patch:8.1.{1374,1780}
 2019-08-02 06:01:46 +02:00
Justin M. Keyes
1f6c9fd822 stream: log unwritten bytes, if any #10663 2019-08-01 15:26:22 +02:00
Daniel Hahler
41bb68b8e8 process_stop: uv: do not close stdin first/explicitly #10584 
- process_stop: do not close stdin explicitly. The "close stdin" step was from
  aa9cb48, before we fixed/reworked the SIGTERM timing logic. So it's probably
  outdated / no longer needed.
- win: jobstop: exit_code 15
   GetExitCodeProcess appears to return the used signal.
   https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-getexitcodeprocess

ref #10573
 2019-08-01 13:55:06 +02:00
Jan Edmund Lazo
c708567262 fileio: port hotfix from patch 8.1.1379 
Patch 8.1.1379 includes a change to a test, added in Patch 8.1.0815.
Patch 8.1.0815 includes runtime doc changes to Blob.
Neovim does not support Blobs yet.
 2019-08-01 04:35:23 -04:00
Jan Edmund Lazo
7995a5e964 vim-patch:8.1.1374: check for file changed triggers too often 
Problem:    Check for file changed triggers too often.
Solution:   Don't use "b_p_ar" when it is negative.
c97582b029
 2019-08-01 04:29:39 -04:00
Jan Edmund Lazo
28946c285b lint 2019-08-01 04:20:35 -04:00
Jan Edmund Lazo
309296545c vim-patch:8.1.1780: warning for file no longer available is repeated 
Problem:    Warning for file no longer available is repeated every time Vim is
            focused. (Brian Armstrong)
Solution:   Only give the message once. (closes vim/vim#4748)
674e2bde6e
 2019-07-31 21:49:36 -04:00
Justin M. Keyes
65578693b2 Merge #10654 from ngortheone/clang/npd_helptags_one 
clang/"null pointer dereference": ex_cmds.c
 2019-07-31 07:22:12 +02:00
Ihor Antonov
6fc0a9f557 lint: helptags_one 2019-07-30 16:58:28 -04:00
Daniel Hahler
6e01ed6a4c vim-patch:8.1.0572: stopping a job does not work properly on OpenBSD 
Problem:    Stopping a job does not work properly on OpenBSD.
Solution:   Do not use getpgid() to check the process group of the job
            processs ID, always pass the negative process ID to kill().
            (George Koehler, closes vim/vim#3656)
76ab4fd619

Ref: https://github.com/neovim/neovim/issues/9704
Ref: https://github.com/neovim/neovim/issues/10182#issuecomment-514450069
Closes https://github.com/neovim/neovim/pull/10660
 2019-07-30 18:41:38 +02:00