| Commit message (Collapse) | Author | Age |
| |\ |
|
| | |
| |
| |
| | |
Problem: Unknown key mappings listed in substitute confirm message.
Solution: Include hints as to what the key mappings do.
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| | |
Problem:
The message E325 displays “vim -r” to recover the file.
Solution:
Change the message to display “nvim -r” instead of “vim -r”.
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Farewell to Bram and dedicate upcoming Vim 9.1 to him (vim/vim#12749)
https://github.com/vim/vim/commit/e978b4534a5e10471108259118c0ef791106fd92
Also update the header for the following files that were converted to Vim9
script upstream:
- autoload/ccomplete.lua (vim9jitted)
- ftplugin.vim
- ftplugof.vim
- indent.vim
- indent/vim.vim
- makemenu.vim
This also updates the "Last Change" dates, even if some changes (due to rewrites
to Vim9 script) were not ported.
There's still a few other places where Bram is still mentioned as a maintainer
in the files we and Vim have:
- ftplugin/bash.vim
- indent/bash.vim
- indent/html.vim
- indent/mail.vim
- macros/accents.vim
- macros/editexisting.vim
- syntax/bash.vim
- syntax/shared/typescriptcommon.vim
- syntax/tar.vim
- syntax/typescript.vim
- syntax/typescriptreact.vim
- syntax/zimbu.vim
Maybe future patches will address that.
Also exclude changes to .po files that didn't apply automatically (the
`:messages` maintainer string isn't used in Nvim anyway).
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
| |\| |
|
| | |
| |
| | |
Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously if a highlight group with a name outside the regexp
[a-zA-Z0-9_] was defined, Nvim would emit an "invalid character"
warning message. This was annoying for Lua scripts, as it was very hard
to debug what line of code was triggering this message since it didn't
produce a stack trace.
This has now been promoted to an error with the code E5248.
Additionally the ASCII character period ('.') and at-sign ('@') have
been added to the allowed list of characters of a highlight group name
to support the application of defining hierarchical highlight groups,
e.g. 'TS.keyword'.
Co-authored-by: Christian Clason <christian.clason@uni-due.de>
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change unlocks additional registers for Neovim by allowing a user
to define their own behavior for non-builtin registers.
This is accopmlished through a new option 'userregfunc'
The 'userregfunc' defines the function to call when handling a register
for which there is no builtin functionality.
The 'userregfunc' function should take 3 arguments:
action - Either "yank" or "put"
register - The character corresponding to the register
content - In the case of action == "yank", the dictionary describing
the yanked content, with the following keys:
{type} - Either "char", "line" or "block"
{lines} - The lines being yanked as a list
{width} - The width in case of "block" mode.
{additional_data} - Additional data (can be returned in
"put" mode)
In case of "put" this function should return the content to put. This
content can be either:
* A dictionary in the same template as content above.
* A list of strings. This will be assumed to be "line" mode.
* A string. This will be assumed to be "char" mode.
An example of a "null" 'userregfunc' that provides an implementation
identical to traditional vim registers would be:
let s:contents = {}
function! MyUserregFunction(action, register, content) abort
if a:action == "put"
return get(s:contents, a:register, "")
else
let s:contents[a:register] = a:content
endif
endfunction
set userregfun=MyUserregFunction
It is important to note that any valid unicode character can now be a
register, including something like @☺.
This change also addresses the multibyte parsing issues surrounding
let @a = 'xyz'
let @🔨 = 'hammer'
|
| | |
|
| |
|
|
|
| |
Update runtime files
https://github.com/vim/vim/commit/130cbfc31235c6cb52ffe718ea0a5bb50fbbc9fd
|
| |
|
|
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/7e6a515ed14e204fafb3dd6e98f2fb543e64aedd
Omit vim9.
|
| |
|
|
|
|
|
|
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/cb80aa2d53e56d3aba3b3c439fb467f29a750c5e
Omit runtime/doc/tabpage.txt.
Patch v8.2.1401 is not ported yet.
Port optwin.vim changes without gettext().
Patch v8.2.1544 is not ported yet.
|
| |
|
|
|
|
|
|
| |
Update runtime files
https://github.com/vim/vim/commit/47e13953ffdbb9f163b901196dec8c2100b72edd
Ignore *.rej files, generated by vim-patch.sh.
Source of mistakes for 1st-time contributors.
|
| |
|
|
|
|
|
|
| |
Neovim runs "src/nvim/po/check.vim" to validate all translations.
Build fails if any translation file has a duplicate.
Remove these duplicates via "msguniq --unique".
https://manpage.me/?q=msguniq
|
| |
|
|
|
| |
Runtime file updates.
https://github.com/vim/vim/commit/664f3cf3f21d3699bfd179c318ef5c869c085648
|
| | |
|
| | |
|
| |
|
|
| |
Closes https://github.com/neovim/neovim/issues/10031
|
| |
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/20aac6c1126988339611576d425965a25a777658
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/675e8d6adb88d5b38087870dfda51c0205070741
---
NA:
vim-patch:ffd112edc6a8
Fix missing patch number.
https://github.com/vim/vim/commit/ffd112edc6a8f72b66c06207bff4431f6aec7b6f
|
| |
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/d2f3a8b8787333abf2300d38836b196955f10c00
|
| |
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/7db25fed5de1be922b8cbb0328149469606a0424
|
| |
|
|
|
| |
Update runtime files and translations
https://github.com/vim/vim/commit/15142e27aaafa15b72d1042c25fbb5e4f12b6736
|
| |
|
|
|
|
| |
Long overdue runtime update.
https://github.com/vim/vim/commit/01164a6546b4c635daf96a1f17d1cb2d07f32a66
|
| |
|
|
|
|
| |
Updated runtime files and translations.
https://github.com/vim/vim/commit/74675a666b51edd61e0210132658d81a86c5102c
|
| |
|
|
|
|
| |
Updated runtime files. Remove HiLink commands.
https://github.com/vim/vim/commit/f37506f60f87d52a9e8850e30067645e2b13783c
|
| |
|
|
|
|
| |
Updated runtime files and translations.
https://github.com/vim/vim/commit/818078ddfbb8cc2546f697c5675a251d095722ec
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Updated runtime files.
https://github.com/vim/vim/commit/e18dbe865d190e74fb5d43ac8bc6ac22507d0223
|
| | |
|
| |\ |
|
| |/
|
|
|
|
| |
Updated runtime files.
https://github.com/vim/vim/commit/939a1abe935a539f2d4c90a56cb0682cbaf3bbb0
|
| | |
|
| |
|
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/fc39ecf8ded5466d7e9cbde8db75517718b023d8
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Sync po files to code at 3a68a4861adcc950cdbde709d4841f8ea0c52b12.
|
| |
|
|
|
|
|
|
| |
Problem: Build fails because of some messages being repeated.
Curiously, all repeated messages have this comment:
"Explicit typecast avoids warning on Mac OS X 10.6".
No idea why.
Solution: Remove repeated messages.
|
|
|
Move files from src/ to src/nvim/.
- src/nvim/ becomes the new root dir for nvim executable sources.
- src/libnvim/ is planned to become root dir of the neovim library.
|