| Commit message (Collapse) | Author | Age |
... | |
|
|
| |
Band-aid workaround to file collision when using `tempname` for temporary batchfiles.
|
|
|
|
|
| |
Problem: Quickfix code uses too many /* */ comments.
Solution: Change to // comments. (Yegappan Lakshmanan)
https://github.com/vim/vim/commit/00bf8cd2115be7c14258aee48c0a7568147c9cd7
|
|
|
|
|
|
|
| |
Problem: Using a full path is supported for 'directory' but not for
'backupdir'. (Mikolaj Machowski)
Solution: Support 'backupdir' as well. (Christian Brabandt, closes vim/vim#179)
https://github.com/vim/vim/commit/b782ba475a3f8f2b0be99dda164ba4545347f60f
|
|
|
|
|
|
| |
Problem: In :let-heredoc line continuation is recognized.
Solution: Do not consume line continuation. (Ozaki Kiichi, closes vim/vim#4580)
https://github.com/vim/vim/commit/e96a2498f9a2d3e93ac07431f6d4afd77f30afdf
|
|
|
|
|
|
| |
Problem: Directly checking 'buftype' value.
Solution: Add the bt_normal() function. (Yegappan Lakshmanan)
https://github.com/vim/vim/commit/91335e5a67aaa9937e65f1e779b9f3f10fd33ee4
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Cannot get the script line number when executing a function.
Solution: Store the line number besides the script ID. (Ozaki Kiichi,
closes vim/vim#3362) Also display the line number with ":verbose set".
https://github.com/vim/vim/commit/f29c1c6aa3f365c025890fab5fb9efbe88eb1761
|
|/
|
|
|
|
|
|
|
| |
changed
Problem: ":write" increments b:changedtick even though nothing changed.
(Daniel Hahler)
Solution: Only increment b:changedtick if the modified flag is reset.
https://github.com/vim/vim/commit/c024b4667875e5bc6fd0ed791530e33c3161bff7
|
|
|
|
|
| |
Problem: Might be freeing memory that was not allocated.
Solution: Have next_fenc() set the fenc_alloced flag. (closes vim/vim#4804)
https://github.com/vim/vim/commit/f077db24230d10ef9a66ae14da34b639464d8fa2
|
|\
| |
| | |
vim-patch:8.1.1318: code for text changes is in a "misc" file
|
| | |
|
|\ \
| |/
|/|
| | |
closes #3457
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Problem: Check for file changed triggers too often.
Solution: Don't use "b_p_ar" when it is negative.
https://github.com/vim/vim/commit/c97582b0296cb6f63f3c2e5a0eb954f5920a8e42
|
| |
|
|
|
|
|
|
|
| |
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)
https://github.com/vim/vim/commit/674e2bde6e7b0c468f304713aa8f97a45e1fcc89
|
|
|
| |
* shorten_buf_name: condition inside outer if-branch with inverse condition
|
|
|
|
|
|
| |
* pvs/V1026: possible overflow in a loop
* refactor: char_u -> uint8_t
* lint
* remove unused if branch: enc_utf8 is always true
|
|
|
| |
Introduce os_file_settime(), remove cruft.
|
|
|
|
|
| |
Problem: Writefile() never calls fsync().
Solution: Follow the 'fsync' option with override to enable or disable.
https://github.com/vim/vim/commit/7567d0b115e332f61a9f390aaccdf7825b891227
|
|
|
|
|
|
|
|
|
| |
Problem: Cannot tell whether a register is being used for executing or
recording.
Solution: Add reg_executing() and reg_recording(). (Hirohito Higashi,
closes vim/vim#2745) Rename the global variables for consistency. Store
the register name in reg_executing.
https://github.com/vim/vim/commit/0b6d911e5de1a1c10a23d4c2ee1b0275c474a2dd
|
| |
|
|
|
|
|
|
|
|
| |
Problem: Clearing a pointer takes two lines.
Solution: Add VIM_CLEAR() and replace vim_clear(). (Hirohito Higashi,
closes #2629)
vim-patch:8.0.1481
|
|
|
|
| |
We never define HAVE_SELINUX, and no one has asked for it.
So remove the dead code.
|
|
|
|
|
|
|
|
|
|
| |
Restores code removed in #9709.
uv_fs_copyfile() copies the perm bits but not the group name.
https://github.com/libuv/libuv/pull/1547
ref #9709
ref #8288
|
|\
| |
| |
| | |
ref #8288
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: If writing runs into a conversion error the backup file is
deleted. (Arseny Nasokin)
Solution: Don't delete the backup file is the file was overwritten and a
conversion error occurred. (Christian Brabandt, closes vim/vim#4387)
https://github.com/vim/vim/commit/cf0bfd9ade5173bcc12563bfc90c21a4db10535d
|
| |
| |
| |
| |
| |
| | |
- redraw! in an invisible buffer rendered the screen unusable.
- storing the autocmd window handle and using it in API function could lead
to crashes. Unregister the handle when the window is not active.
|
| |
| |
| |
| |
| |
| |
| | |
Problem: A BufReadPre autocommand may cause the cursor to move.
Solution: Restore the cursor position after executing the autocommand,
unless the autocommand moved it. (Christian Brabandt,
closes vim/vim#4302, closes vim/vim#4294)
https://github.com/vim/vim/commit/a68e59590905da9b4448ff1fcac929ad1a18da9e
|
|\ \ |
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Others can read the swap file if a user is careless with his
primary group.
Solution: If the group permission allows for reading but the world
permissions doesn't, make sure the group is right.
https://github.com/vim/vim/commit/5a73e0ca54c77e067c3b12ea6f35e3e8681e8cf8
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Asking about existing swap file unnecessarily.
Solution: When it is safe, delete the swap file. Remove
HAS_SWAP_EXISTS_ACTION, it is always defined. (closes vim/vim#1237)
https://github.com/vim/vim/commit/67cf86bfff5fd5224d557d81cb146f46e33b831c
N/A:
vim-patch:8.1.1232
vim-patch:8.1.1233
vim-patch:8.1.1236
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Making an autocommand trigger once is not so easy.
Solution: Add the ++once argument. Also add ++nested as an alias for
"nested". (Justin M. Keyes, closes vim/vim#4100)
https://github.com/vim/vim/commit/eb93f3f0e2b2ae65c5c3f55be3e62d64e3066f35
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
bisected to f5d5da391715
Other test steps:
nvim -u NORC
:terminal tree / " Produces lots of output
:edit somefile.txt
:vsplit
:vsplit
<c-w>l
<c-w>l
<c-w>h
<c-w>p
|
| |
| |
| |
| |
| |
| |
| | |
Problem: If autocmd pattern only contained `++once` handlers, and
all of them completed, then there would be an empty group
displayed by `:autocmd Foo`.
Solution: Delete the pattern if all of its commands were deleted.
|
| |
| |
| |
| |
| | |
Based on feedback from upstream:
https://github.com/vim/vim/pull/4100
|
|/
|
|
|
|
|
| |
- Rename "nested" to "-nested", but continue to support "nested" for
backwards-compatibility.
- Allow any order: "-once -nested" or "-nested -once".
ref https://github.com/neovim/neovim/pull/9706#issuecomment-471295747
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds a new feature to :autocmd which sets the handler to be executed at
most one times.
Before:
augroup FooGroup
autocmd!
autocmd FileType foo call Foo() | autocmd! FooGroup * <buffer>
augroup END
After:
autocmd FileType foo once call Foo()
|
| |
|
|
|
|
|
|
|
|
|
| |
Suggested by ZyX in https://github.com/neovim/neovim/issues/6725#issuecomment-312197691 :
> There already is an exception if writing to a “device” (e.g. FIFO).
> It makes sense to ignore certain errors like ENOTSUP or EOPNOTSUPP
> since it is not something we or user can do anything about.
ref #6725
|