| Commit message (Collapse) | Author | Age |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
before, RelWithDebInfo linking gave this warning:
src/mpack/conv.h:36:16: warning: type of ‘mpack_unpack_boolean’ does not match original declaration [-Wlto-type-mismatch]
36 | MPACK_API bool mpack_unpack_boolean(mpack_token_t t) FUNUSED FPURE;
| ^
src/mpack/conv.c:196:16: note: return value type mismatch
196 | MPACK_API bool mpack_unpack_boolean(mpack_token_t t)
| ^
|
| |
| |
| |
| |
| |
| | |
Problem: Quarto files are not recognized.
Solution: Recognize quarto files by the extension. (Jonas Strittmatter,
closes vim/vim#10880)
https://github.com/vim/vim/commit/3a9687fb2749cb3da6e3bbf60cb9eaa81f7889ae
|
| |
| |
| | |
Closes #19696
|
| |
| |
| | |
Note: This only applies to ambiguous-width characters.
|
| |
| |
| |
| |
| |
| |
| | |
(#19690)
Problem: Checking character options is duplicated and incomplete.
Solution: Move checking to check_chars_options(). (closes vim/vim#10863)
https://github.com/vim/vim/commit/8ca29b6a3599b82b8822b7697cad63d0244c2d59
|
| |
| |
| |
| |
| |
| | |
Problem: Command line history code is spread out.
Solution: Put the code in a new file. (Yegappan Lakshmanan, closes vim/vim#4779)
Also graduate the +cmdline_hist feature.
https://github.com/vim/vim/commit/d7663c22c6c1ff0f86b81371586fbc851d3a3e9e
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: setcellwidths() may make 'listchars' or 'fillchars' invalid.
Solution: Check the value and give an error. (closes vim/vim#9024)
https://github.com/vim/vim/commit/94358a1e6e640ca5ebeb295efdddd4e92b700673
Cherry-pick f_setcellwidths() change from patch 9.0.0036.
Cherry-pick 'ambiwidth' docs update from runtime update 079ba76ae7a7.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Problem: Memory acccess error when using setcellwidths().
Solution: Use array and pointers correctly.
https://github.com/vim/vim/commit/b06a6d59d12dbd67d55b3c46f6e5547e9103c931
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: It is not possible to specify cell widths of characters.
Solution: Add setcellwidths().
https://github.com/vim/vim/commit/08aac3c6192f0103cb87e280270a32b50e653be1
Co-Authored-By: delphinus <me@delphinus.dev>
|
| |
| |
| |
| |
| | |
This just avoids including mbyte.h in eval/typval.h, so that mbyte.h can
include eval/typval.h in Vim patch 8.2.1535.
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
defined by the user.
(Neo)vim has many different marks defined, but sometimes this may not be
completely adequate.
This change give the user the ability to define behavior for marks which
are not built in to (Neo)vim directly. This is accomplished through a
new option called the "usermarkfunc."
The usermarkfunc points to a vimscript function that takes an "action"
paramter (either "get" or "set") and a mark name.
a basic implementation that re-implements global mark behavior for user
marks would look something like:
let s:marks = {}
function UserMarkFunc(action, mark)
if a:action == "set"
let [n, lnum, col, off, curswant] = getcurpos()
let s:marks[a:mark] =
\ { "line": lnum, "col": col, "file": expand("%:p") }
else
return s:marks[a:mark]
endif
endfunction
set usermarkfunc=UserMarkFunc
of course the user could make the behavior be whatever.
It should also be noted that any valid unicode character can now be a
mark. It is not just limited to ASCII characters.
|
| |
|
|
|
|
|
|
|
|
| |
val" (#19670)
Problem: No error if an option is given an invalid value with
":let &opt = val".
Solution: Give the error. (closes vim/vim#9864)
https://github.com/vim/vim/commit/8ccbbeb620dcc73154de29c51100fe815cefe109
|
|
|
|
|
|
| |
Problem: The "trailing characters" error can be hard to understand.
Solution: Add the trailing characters to the message.
https://github.com/vim/vim/commit/2d06bfde29bd3a62fc85823d2aa719ef943bd319
|
|
|
|
|
|
|
|
|
| |
Problem: Ex command error cannot contain an argument.
Solution: Add ex_errmsg() and translate earlier. Use e_trailing_arg where
possible.
https://github.com/vim/vim/commit/8930caaa1a283092aca81fdbc3fcf15c7eadb197
Remove duplicate test file 062_tab_pages_spec.lua
|
|
|
|
|
|
| |
Problem: Vim9: line break after "->" only allowed in :def function.
Solution: Only allow line break after "->". (closes vim/vim#6492)
https://github.com/vim/vim/commit/dd1a9af00f6954b176c5875af0a91acde72572c8
|
|
|
| |
Fixes #19608
|
|
|
|
|
| |
Problem: Vim9: missing white space when using <f-args>.
Solution: Add spaces. (Christian J. Robinson)
https://github.com/vim/vim/commit/20d89e0ac65686481f97657008deede0b39ef5db
|
|
|
|
|
|
|
| |
confusing (#19656)
Problem: Vim9: error about using -complete without -nargs is confusing.
Solution: Change the wording.
https://github.com/vim/vim/commit/41a3485dd638a09e4c463b1a1da231f4290454f2
|
|
|
|
|
|
|
| |
Problem: Support for user commands is spread out. No good reason to make
user commands optional.
Solution: Move user command support to usercmd.c. Always enable the
user_commands feature.
https://github.com/vim/vim/commit/ac9fb18020d7e8bf16d02d45fbb02cf47328aaf7
|
|
|
|
| |
The line returned but ml_get_buf() may be freed by another call to
ml_get_buf(), so it is necessary to make a copy.
|
|
|
| |
Otherwise Test_menu_expand() fails when run alone.
|
|
|
|
|
|
|
| |
Problem: "delmenu" does not remove autocmmands. Running menu test function
alone fails.
Solution: Delete autocommands Make sure there is at least one menu.
(closes vim/vim#10848)
https://github.com/vim/vim/commit/206fce307b265f7f6c6290b623a80c1d846dd131
|
|
|
|
|
|
| |
Problem: Going past the end of a menu item with only modifier.
Solution: Check for NUL.
https://github.com/vim/vim/commit/083692d598139228e101b8c521aaef7bcf256e9a
|
|
|
|
|
|
| |
Problem: New buffers are not added to the Buffers menu.
Solution: Turn number into string. (Yee Cheng Chin, closes vim/vim#5864)
https://github.com/vim/vim/commit/5908fdf72fa1995735e38c46f254ddde81a87c1f
|
|
|
|
|
|
|
|
|
| |
Problem: Buffer menu does not handle special buffers properly.
Solution: Keep a dictionary with buffer names to reliably keep track of
entries.
Also trigger BufFilePre and BufFilePost for command-line and
terminal buffers when the name changes.
https://github.com/vim/vim/commit/5e94a29ebbde10dd973d58f1adba9a2fc83877d1
|
|
|
|
|
|
|
| |
Problem: Vim9: need more tests for empty string arguments.
Solution: Add more tests. Also use empty argument with menu_info() to get
the top-level menu names. (Yegappan Lakshmanan, closes vim/vim#8925)
https://github.com/vim/vim/commit/51491adfa86fd66a857cd7ec50d0b57dbdf3da59
|
|
|
|
|
|
| |
Problem: Coverity warns for using array index out of range.
Solution: Add extra "if" to avoid warning.
https://github.com/vim/vim/commit/56cb3378727783da2d246b9c5091784821666cfa
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: Menu functionality insufficiently tested.
Solution: Add tests. Add menu_info(). (Yegappan Lakshmanan, closes vim/vim#5760)
https://github.com/vim/vim/commit/0eabd4dc8ff50658f0ea0e92c7918a42242f6b80
Omit feedkeys() change: even if "L" flag is implemented it will likely
use input_enqueue(), which already checks for interrupts.
Omit Test_mouse_popup_menu(): already tested in Lua.
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
Replace its functionality by copying the entire directory where the
reports are instead.
|
| |
| |
| |
| |
| |
| |
| | |
- Use DIRECTORY instead of PATH in get_filename_component
- Use COMPILE_OPTIONS instead of COMPILE_FLAGS. COMPILE_FLAGS is treated
as a single string while COMPILE_OPTIONS is a list, meaning that cmake
will take care of any escaping and quoting automatically.
|
| | |
|
| |
| |
| | |
Co-authored-by: ii14 <ii14@users.noreply.github.com>
|
| | |
|
|\ \ |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
- Comment style
- Minimise scope of locals
|
| |/
|/|
| |
| | |
Co-authored-by: zeertzjq <zeertzjq@outlook.com>
Co-authored-by: notomo <notomo.motono@gmail.com>
|
| |
| |
| |
| |
| | |
Simplify variable declarations
Co-authored-by: zeertzjq <zeertzjq@outlook.com>
|
|\ \
| | |
| | | |
implement <c-\><c-o> key for terminal mode
|
| |/
| |
| |
| | |
this works similar to <c-o> or <c-\><c-o> in insert mode
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
N/A patches for version.c:
vim-patch:9.0.0135: comment about tabpage line above the wrong code
Problem: Comment about tabpage line above the wrong code.
Solution: Move the comment. (closes vim/vim#10836)
https://github.com/vim/vim/commit/0b0ccbbfb014e1c9682b86a7a41ff2837b0b8047
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The targets will only format files that have been changed in current
branch compared to the master branch. This includes unstaged, staged and
committed files.
Add following make and cmake targets:
formatc - format changed c files
formatlua - format changed lua files
format - run formatc and formatlua
Remove scripts/uncrustify.sh as this deprecates it.
|
|/
|
|
|
| |
The "cp" stands for codepoint.
Closes https://github.com/neovim/neovim/issues/7401
|