aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* | doc/api.txt: Merge with api-funcs.txtJustin M. Keyes2017-03-01
| | | | | | | | | | | | | | | | | | | | It's important that users have a single, easy-to-remember place for reading about the API. So this commit changes gen_api_vimdoc.py so that the generated section is appended to api.txt instead of creating a separate document. Also remove the section numbering and ToC: it's a maintenance cost, and it will be unnecessary when #5169 is integrated.
* | terminal: Avoid unnecessary redraws.Justin M. Keyes2017-03-01
| |
* | terminal: Disable some options in terminal-mode.Justin M. Keyes2017-03-01
| | | | | | | | | | | | | | In terminal-mode these options are nonsense because cursor is placed at end of buffer to "follow" output. Closes #2259
* | terminal: Keep cursor position.Justin M. Keyes2017-03-01
| | | | | | | | | | | | Let the terminal dictate the normal-mode cursor position. This will be disorienting sometimes, but it is closer to what users expect vs always going to the last line.
* | Merge #6139 from justinmk/win32-runtimeJustin M. Keyes2017-03-01
|\ \ | | | | | | win/package: runtime files
| * | win/package: runtime filesJustin M. Keyes2017-03-01
| | | | | | | | | | | | | | | | | | | | | runtime/plugin/gui_shim.vim is from Neovim-Qt. This is a temporary measure, we will add real UI events which obviate gui_shim.vim. Closes #6145
| * | win/package: cat.exeJustin M. Keyes2017-03-01
| | |
* | | vim-patch:8.0.0390 (#6197)Tommy Allen2017-03-01
|/ / | | | | | | | | | | | | Problem: When the window scrolls horizontally when the popup menu is displayed part of it may not be cleared. (Neovim issue #6184) Solution: Remove the menu when the windows scrolled. (closes vim/vim#1524) Fixes #6184
* | vim-patch:7.4.2095James McCoy2017-02-27
| | | | | | | | | | | | | | | | | | | | Problem: Man test fails when run with the GUI. Solution: Adjust for different behavior of GUI. Add assert_inrange(). https://github.com/vim/vim/commit/61c04493b00f85d0b97436260a9ef9ab82143b78 Only changes related to assert_inrange() were included, since we have a distinct man plugin.
* | vim-patch:7.4.2098James McCoy2017-02-27
| | | | | | | | | | | | | | Problem: Text object tests are old style. Solution: Turn them into new style tests. (James McCoy, closes vim/vim#941) https://github.com/vim/vim/commit/00b24be454800f544676aa8850fb4378a568901e
* | Merge pull request #6190 from jamessan/vim-7.4.1991James McCoy2017-02-27
|\ \ | | | | | | vim-patch:7.4.1991,7.4.1992,7.4.1993,7.4.1994
| * | vim-patch:7.4.1994James McCoy2017-02-27
| | | | | | | | | | | | | | | | | | | | | Problem: True-false test fails. Solution: Filter the dict to only keep the value that matters. https://github.com/vim/vim/commit/05e418d436410cd8bbf5a29ff81e8ad68408b1e8
| * | vim-patch:7.4.1993James McCoy2017-02-27
| | | | | | | | | | | | | | | | | | | | | Problem: Not all TRUE and FALSE arguments are tested. Solution: Add a few more tests. https://github.com/vim/vim/commit/6bb450145e96d7b182769fd9502a267da72667ec
| * | vim-patch:7.4.1992James McCoy2017-02-27
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Values for true and false can be confusing. Solution: Update the documentation. Add a test. Make v:true evaluate to TRUE for a non-zero-arg. https://github.com/vim/vim/commit/e381d3d5e098546854b008e01ca1d28ba1a4a057
| * | vim-patch:7.4.1991James McCoy2017-02-27
| | | | | | | | | | | | | | | | | | | | | Problem: glob() does not add a symbolic link when there are no wildcards. Solution: Remove the call to mch_getperm(). https://github.com/vim/vim/commit/00efded1064427ab3f84e4d57af62e0aab876fc6
* | | edit.c: CTRL-SPC: Insert previously-inserted text. #6090Matthew Malcomson2017-02-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Default Vim behavior of i_CTRL-<Space> is to insert the last-inserted text and exit insert mode. :help i_CTRL-@ Before this commit that did not happen because insert_handle_key() checks for NUL instead of checking for ' ' with a CTRL `mod_mask`. I'm leaving the check for NUL despite the fact that at the moment that key is never seen when using the terminal UI (not for C-Space, nor C-@). This is because I assume it's still allowed for other front-ends to pass NUL, but at the moment the terminal UI isn't.
* | | Merge #6148 from delftswa2017/clang-scan-fix-dead-storesJustin M. Keyes2017-02-28
|\ \ \ | | | | | | | | vim-patch:8.0.0353
| * | | strings.c: remove unused assignmentJente Hidskes2017-02-20
| | | | | | | | | | | | | | | | | | | | As reported by clang-scan, `length_modifier` is never read in any code path following this branch. It is safe to remove.
| * | | hardcopy.c: fix dead assignmentSander Bosma2017-02-20
| | | | | | | | | | | | | | | | | | | | | | | | `has_mbyte` is deprecated (globals.h), so `outputlen` is always assigned within the if statement. Therefore, the previous initialization is unnecessary.
| * | | message.c: fix dead assignment by removing dead codeSander Bosma2017-02-20
| | | | | | | | | | | | | | | | | | | | `enc_dbcs` and `enc_utf8` are deprecated (globals.h), so the second branch is always taken.
| * | | misc1.c: remove dead initializationSander Bosma2017-02-20
| | | |
| * | | screen.c: remove dead codeSander Bosma2017-02-20
| | | | | | | | | | | | | | | | | | | | | | | | As stated in globals.h, mbyte flags are deprecated, and code using it can be refractored to remove dead code. Since has_mbyte is defined to true, this refractoring correct.
| * | | screen.c: account for translated string lengthJente Hidskes2017-02-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `[RO]` is appended to the status line and `len` is increased with the length of this string (4). However, the string is marked for translation and may thus well be larger (or smaller) than 4. Therefore, we check the length at runtime. The resulting len is never actually used, and thus could be removed. However, by keeping this line, the body of this if-statement is kept consistent with surrounding code, and future changes can not forget to add this line when additional strings are added to p.
* | | | Merge pull request #6121 from lonerover/vim-7.4.2046James McCoy2017-02-27
|\ \ \ \ | | | | | | | | | | | | | | | vim-patch:7.4.2046
| * | | | vim-patch:7.4.2061lonerover2017-02-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: qf_init_ext() is too big. Solution: Move code to qf_parse_line() (Yegappan Lakshmanan) https://github.com/vim/vim/commit/e87e6dddc2b2a99572ec0db0833c052214c4fbd3
| * | | | vim-patch:7.4.2047lonerover2017-02-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Compiler warning for initializing a struct. Solution: Initialize in another way. (Anton Lindqvist) https://github.com/vim/vim/commit/bfafb4c4a01db3f8c508716daf689e0dfe92b649
| * | | | vim-patch:7.4.2046rover2017-02-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: The qf_init_ext() function is too big. Solution: Refactor it. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/e0d3797664c59afc9705808f86a7cf00fd6d874d
* | | | | lintJames McCoy2017-02-27
| | | | |
* | | | | vim-patch:7.4.2200James McCoy2017-02-27
| |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Cannot get all information about a quickfix list. Solution: Add an optional argument to get/set loc/qf list(). (Yegappan Lakshmanan) https://github.com/vim/vim/commit/d823fa910cca43fec3c31c030ee908a14c272640
* | | | Merge #6112 from ZyX-I/split-eval'/buf_get_changedtickJustin M. Keyes2017-02-27
|\ \ \ \ | | | | | | | | | | Better b:changedtick support
| * | | | *: Fix linter errorsZyX2017-02-25
| | | | |
| * | | | buffer: Hide one of the asserts from lua parserZyX2017-02-25
| | | | |
| * | | | buffer: Provide an initializer for di_keyZyX2017-02-24
| | | | |
| * | | | buffer: Remove b:changedtick from b: before freeing b:ZyX2017-02-24
| | | | | | | | | | | | | | | Avoids loosing b:changedtick value at `:bdelete`.
| * | | | memory: Free buffers after freeing variablesZyX2017-02-24
| | | | | | | | | | | | | | | Avoids use-after-free crashes when compiling with -DEXITFREE.
| * | | | eval: Do not allocate b:changedtick dictionary itemZyX2017-02-24
| | | | |
| * | | | *: Fix linter errorsZyX2017-02-23
| | | | |
| * | | | api: Make sure dict_set_var doesn’t edit read-only valuesZyX2017-02-23
| | | | | | | | | | | | | | | Fixes #6147
| * | | | api: Rename dict_set_value to dict_set_varZyX2017-02-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reasonings: 1. It is not used for anything, but scope dictionaries currenly. So there is no need to generalize and split it into dict_set_var (which will contain some scope-dictionary-specific checks) and dict_set_value (which will work for any dictionary). 2. Check for key size is no longer valid for non-scope dictionaries: you *can* use empty keys there. In scope dictionaries also, but you actually are not supposed to store there anything, but variables. Note that actually one may still do let b:[''] = 1 and “bypass” check for variable name. It won’t change what `echo b:` will show, but it may affect code which iterates over scope dictionary keys and sets them to something (if there is such code).
| * | | | eval: Remove incorrect workaroundZyX2017-02-23
| | | | | | | | | | | | | | | Was replaced by the previous patch. Also fixes legacy test 055.
| * | | | eval: Forbid (un)locking b:changedtickZyX2017-02-23
| | | | | | | | | | | | | | | Port of vim-patch:8.0.0343
| * | | | eval: Make sure `islocked('b:.changedtick')` does not error outZyX2017-02-23
| | | | | | | | | | | | | | | Port of vim-patch:8.0.0345
| * | | | eval: Specify more precise len for var_check_ro in get_lvalZyX2017-02-23
| | | | |
| * | | | eval: Refactor var_check_ro, tv_check_lock and var_check_fixedZyX2017-02-23
| | | | | | | | | | | | | | | | | | | | | | | | | - They are no longer responble for using gettext. - They now receive string length and use %.* format specifier in messages. - And one less global: one of the error messages is never repeated.
| * | | | eval: Fix memory leakZyX2017-02-23
| | | | | | | | | | | | | | | Ref vim/vim#1497
| * | | | buffer: Forbid unletting b:changedtickZyX2017-02-23
| | | | |
| * | | | eval: Refactor item_lockZyX2017-02-23
| | | | | | | | | | | | | | | If I am not mistaking, this commit should not change any functionality.
| * | | | eval: Make sure that b:changedtick may not be unlocked via :unlo b:varZyX2017-02-23
| | | | | | | | | | | | | | | It still may be unlocked by `:unlock b:.var`.
| * | | | buffer: Bind b:changedtick to b:['changedtick'], remove special casesZyX2017-02-23
| | | | |
| * | | | api/buffer: Add nvim_buf_get_changedtick methodZyX2017-02-23
| | | | |
generated by cgit (git 2.34.1) at 2025-07-21 06:58:28 +0000