| 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”.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(#29566)
Problem: spell completion message still wrong in translations
(after 9.1.0512)
Solution: Update translation files with the new message
(Kyle Kovacs)
closes: vim/vim#15113
https://github.com/vim/vim/commit/68f5ceddca2ec2d591b9180020c95bb86bf6d3d2
Co-authored-by: Kyle Kovacs <kkovacs@diconfiberoptics.com>
|
| |\| |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| | |
* optwin
* synchronize with Vim
|
| |\| |
|
| | |
| |
| |
| |
| | |
Include version number in the translated message so that the word order
can be changed.
Also do not translate URL.
|
| | |
| |
| | |
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/d2f3a8b8787333abf2300d38836b196955f10c00
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Update translations.
https://github.com/vim/vim/commit/bf92e3a3719f255dbb30102ceb618e0eac7c9497
|
| |
|
|
|
|
| |
Updated runtime files and translations.
https://github.com/vim/vim/commit/74675a666b51edd61e0210132658d81a86c5102c
|
| |
|
|
|
|
|
|
|
|
| |
Also re-word some error messages:
- "Key does not exist: %s"
- "Invalid channel: %<PRIu64>"
- "Request array size must be 4 (request) or 3 (notification)"
- "String cannot contain newlines"
References #6150
|
| |
|
|
|
|
|
| |
Problem: Viminfo does not merge file marks properly.
Solution: Use a timestamp. Add the :clearjumps command.
https://github.com/vim/vim/commit/2d35899721da0e9359a9fe1059554f8c4ea7f0c1
|
| |
|
|
|
|
|
|
| |
Problem: Arguments of setqflist() are not checked properly.
Solution: Add better checks, add a test. (Nikolai Pavlov, Hirohito Higashi,
closes vim/vim#661)
https://github.com/vim/vim/commit/d106e5ba7f10f0d2a14eaefe5d78405044416cb9
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix translation of the term 'tag'
Prefer native word instead of transliteration
* Update uk.po automatically
Run make update-po-uk in src/nvim/po
* Update fuzzy translations in uk.po
* Translate missing msgstr
* Fix layout of the front page
* Apply cleanup.vim
Additionally, remove irrelevant and confusing comments
* Copy uk.po into uk.cp1251.po
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
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.
|
