aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/ex_docmd.c
Commit message (Collapse)AuthorAge
...
* | cleanup: remove legacy `enc_dbcs` global #9660Justin M. Keyes2019-03-02
|/
* vim-patch:8.1.0803: session restore: handle single quotes #9620Marco Hinz2019-02-17
| | | | | | | | | Problem: Session file has problem with single quote in file name. (Jon Crowe) Solution: Use a double quoted string. Add a test. https://github.com/vim/vim/commit/ad36a3588d32985ee27bd11aa97e5195ef623158 Fixes https://github.com/neovim/neovim/issues/9618
* window/ui: reorganize size variables, fix terminal window size with multigrid.Björn Linse2019-01-27
| | | | | | | wp->w_height_inner now contains the "inner" size, regardless if the window has been drawn yet or not. It should be used instead of wp->w_grid.Rows, for stuff that is not directly related to accessing the allocated grid memory, such like cursor movement and terminal size
* PVS/V1028: cast operands, not the resultJustin M. Keyes2019-01-18
|
* clang/"Dead assignment"Justin M. Keyes2019-01-13
|
* vim-patch:8.0.0251: not easy to select Python 2 or 3 (#9173)David Jimenez2019-01-02
| | | | | | Problem: It is not so easy to write a script that works with both Python 2 and Python 3, even when the Python code works with both. Solution: Add 'pyxversion', :pyx, etc. (Marc Weber, Ken Takata) https://github.com/vim/vim/commit/f42dd3c3901ea0ba38e67a616aea9953cae81b8d
* multigrid: Fix lint errorsUtkarsh Maheshwari2018-12-31
|
* multigrid: Allow UIs to set grid size different from window sizeUtkarsh Maheshwari2018-12-31
|
* ex_docmd: '/' is not a path for Cmdline* eventsJan Edmund Lazo2018-12-12
| | | | | | | | | Code from https://github.com/neovim/neovim/pull/9348#issuecomment-446416118 autocmd_fname_full was removed in https://github.com/neovim/neovim/commit/82cd0be2eaf71c0476e15c66ba3e83c76896d407 but Vim uses this hack for <afile> on CmdlineEnter and related events in vim-patch:8.0.1748. Port the hack by not treating "/" as a path for <afile> on these events.
* vim-patch:8.1.0337: :file fails in quickfix command (#9215)Jan Edmund Lazo2018-11-09
| | | | | | Problem: :file fails in quickfix command. Solution: Allow :file without argument when curbuf_lock is set. (Jason Franklin) https://github.com/vim/vim/commit/379fb76b080521f7c09265ec3264b9e698923518
* ui: disable clearing almost everywhereBjörn Linse2018-10-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Avoid clearing the screen in most situations. NOT_VALID should be equivalent to CLEAR unless some external force messed up the terminal, for these situations <c-l> and :mode will still clear the screen. Also eliminate some obsolete code in screen.c, that dealt with that in vim drawing window 1 can mess up window 2, but this never happens in nvim. But what about slow terminals? There is two common meanings in which a terminal is said to be "slow": Most commonly (and in the sense of vim:s nottyfast) it means low bandwidth for sending bytes from nvim to the terminal. If the screen is very similar before and after the update_screen(CLEAR) this change should reduce bandwidth. If the screen is quite different, but there is no new regions of contiguous whitespace, clearing doesn't reduce bandwidth significantly. If the new screen contains a lot of whitespace, it will depend of if vsplits are used or not: as long as there is no vsplits, ce is used to cheaply clear the rest of the line, so full-screen clear is not needed to reduce bandwith. However a left vsplit currently needs to be padded with whitespace all the way to the separator. It is possible ec (clear N chars) can be used to reduce bandwidth here if this is a problem. (All of this assumes that one doesn't set Normal guibg=... on a non-BCE terminal, if you do you are doomed regardless of this change). Slow can also mean that drawing pixels on the screen is slow. E-ink screens is a recent example. Avoiding clearing and redrawing the unchanged part of the screen will always improve performance in these cases.
* fix warning: "Assigned value is garbage"Justin M. Keyes2018-10-21
| | | | | | | clang scan-build noticed that find_command() may bitmask `eap->flags`. cmd_can_preview() only uses `ea.cmdidx`, but let's fix the warning... Found by clang scan-build 5.0
* vim-patch:8.1.0047: no completion for :unlet $VARJan Edmund Lazo2018-10-02
| | | | | | Problem: No completion for :unlet $VAR. Solution: Add completion. (Jason Franklin) https://github.com/vim/vim/commit/19834010889fc5bfa0f88b3ba83133dae6c0a35d
* lintJan Edmund Lazo2018-09-29
|
* globals: arg_had_last is boolJan Edmund Lazo2018-09-29
|
* vim-patch:8.0.1485: weird autocmd may cause arglist to be changed recursivelyJan Edmund Lazo2018-09-29
| | | | | | | Problem: Weird autocmd may cause arglist to be changed recursively. Solution: Prevent recursively changing the argument list. (Christian Brabandt, closes vim/vim#2472) https://github.com/vim/vim/commit/9e33efd1523b85a70533930dd43a26925a2b648c
* vim-patch:8.0.1215: newer gcc warns for implicit fallthroughJan Edmund Lazo2018-09-20
| | | | | | Problem: Newer gcc warns for implicit fallthrough. Solution: Consistently use a FALLTHROUGH comment. (Christian Brabandt) https://github.com/vim/vim/commit/2f40d129bf45cd35976e4120336ae6d504f5a5dd
* lintJan Edmund Lazo2018-09-16
|
* vim-patch:8.0.1416: crash when searching for a sentenceJan Edmund Lazo2018-09-16
| | | | | | Problem: Crash when searching for a sentence. Solution: Return NUL when getting character at MAXCOL. (closes vim/vim#2468) https://github.com/vim/vim/commit/8ada6aa9298b4764d9ca0024dd21b17e815595ce
* lintJan Edmund Lazo2018-09-14
|
* globals: KeyTyped is boolJan Edmund Lazo2018-09-14
|
* vim-patch:8.0.1089: range count in user commandKwon-Young2018-09-13
| | | | | | | | Problem: Cannot get range count in user command. Solution: Add <range> argument. https://github.com/vim/vim/commit/c168bd4bd3a9b856fc410fc4515dcca1d10d7461 close #8946
* UI/cleanup: Remove most redraw_later_clear() callsJustin M. Keyes2018-09-12
| | | | | | Vim :! may "mess up the screen" because of e.g. switching between cooked mode, but Nvim just uses pipes. So maybe we can avoid these redraw_later_clear() CYA calls.
* vim-patch:8.1.0219: expanding ## fails to escape backtickJan Edmund Lazo2018-09-11
| | | | | | Problem: Expanding ## fails to escape backtick. Solution: Escape a backtick in a file name. (closes vim/vim#3257) https://github.com/vim/vim/commit/2c8c681bfcd5138a0ec8ce018216dc2dc69a11a0
* Merge #8953 from janlazo/vim-8.0.1190Justin M. Keyes2018-09-05
|\
| * vim-patch:8.0.1595: no autocommand triggered before exitingJan Edmund Lazo2018-09-04
| | | | | | | | | | | | Problem: No autocommand triggered before exiting. Solution: Add the ExitPre autocommand event. https://github.com/vim/vim/commit/12a96de430779b88795fac87a2be666d9f661d1e
| * vim-patch:8.0.1190: unusable after opening new window in BufWritePre eventJan Edmund Lazo2018-09-04
| | | | | | | | | | | | | | | | Problem: Vim becomes unusable after opening new window in BufWritePre event. Solution: Call not_exiting(). (Martin Tournoij, closes vim/vim#2205) Also for "2q" when a help window is open. Add a test. https://github.com/vim/vim/commit/2c33d7bb69c4c2c5b0e39b03cc4b0c04cfdfbb0b
* | vim-patch:8.1.0333: :mkview does not restore cursor properly after "$"Jan Edmund Lazo2018-09-02
|/ | | | | | | Problem: :mkview does not restore cursor properly after "$". (Dominique Pelle) Solution: Position the cursor with "normal! $". https://github.com/vim/vim/commit/92c1b696413bf0e28f2fec22090d42e8a825eff2
* vim-patch:8.0.1151: "vim -c startinsert!" doesn't append (#8886)Jan Edmund Lazo2018-08-22
| | | | | Problem: "vim -c startinsert!" doesn't append. Solution: Correct line number on startup. (Christian Brabandt, closes vim/vim#2117) https://github.com/vim/vim/commit/09ca932f8e7d63a83b39baa7c03d4c6145e3baab
* lintJan Edmund Lazo2018-08-20
|
* undo: update undo_time() function signatureJan Edmund Lazo2018-08-20
| | | | | sec,file,absolute (params) are bool. Fix callers and local variables of undo_time().
* lintJan Edmund Lazo2018-08-17
|
* vim-patch:8.0.1090: cannot get the text under the cursor like v:beval_textJan Edmund Lazo2018-08-17
| | | | | | Problem: cannot get the text under the cursor like v:beval_text Solution: Add <cexpr>. https://github.com/vim/vim/commit/65f084749b260746d7f186af4f080298be2df55b
* vim-patch:8.1.0159: completion for user names does not work for a prefix.Jan Edmund Lazo2018-08-17
| | | | | | | Problem: Completion for user names does not work if a prefix is also a full matching name. (Nazri Ramliy) Solution: Accept both full and partial matches. (Dominique Pelle) https://github.com/vim/vim/commit/6c5d1043022520512ee36aa1a29662b60af33c95
* ex_docmd: forceit,usefilter are boolJan Edmund Lazo2018-08-17
|
* vim-patch:8.0.1649: no completion for argument list commandsJan Edmund Lazo2018-08-16
| | | | | | Problem: No completion for argument list commands. Solution: Add arglist completion. (Yegappan Lakshmanan, closes vim/vim#2706) https://github.com/vim/vim/commit/cd43effecab02c6c28b1c4a3a14f91b8c3f26c0d
* vim-patch:8.0.1231: expanding file name drops dashJan Edmund Lazo2018-08-16
| | | | | | Problem: Expanding file name drops dash. (stucki) Solution: Use the right position. (Christian Brabandt, closes vim/vim#2184) https://github.com/vim/vim/commit/c312b8b87a589ed8452dbf0f555f05ff86d04692
* vim-patch:8.0.0878: no completion for :mapclearJan Edmund Lazo2018-08-16
| | | | | | Problem: No completion for :mapclear. Solution: Add completion (Nobuhiro Takasaki et al. closes vim/vim#1943) https://github.com/vim/vim/commit/cae92dc3d5bdd4009910671328cd01394bfbe2cf
* refactor: Replace vim_strrchr() with strrchar() (#8718)ZviRackover2018-08-11
| | | | ref #1474
* style: fixing minor issues noted in code review.ZviRackover2018-08-06
|
* Remove all occurences of the mb_ptr2char macroZviRackover2018-08-06
| | | | | | | First step towards implemening issue #7401. The same can be done for all deprecated mb_ functions in follow-up patches.
* globals: virtual_op is TriStateJan Edmund Lazo2018-08-01
|
* Merge #8589 'VimL: Remove legacy v:xx aliases'Justin M. Keyes2018-07-23
|
* ui: use line-based rather than char-based updates in screen.cBjörn Linse2018-07-21
| | | | | | | | | | | | | Add ext_newgrid and ext_hlstate extensions. These use predefined highlights and line-segment based updates, for efficiency and simplicity.. The ext_hlstate extension in addition allows semantic identification of builtin and syntax highlights. Reimplement the old char-based updates in the remote UI layer, for compatibility. For the moment, this is still the default. The bulitin TUI uses the new line-based protocol. cmdline uses curwin cursor position when ext_cmdline is active.
* *: Replace b_changedtick with new always-inline functionsZyX2018-06-22
| | | Ref #8474
* Merge #8596 from janlazo/vim-8.0.0615Justin M. Keyes2018-06-20
|\
| * lintJan Edmund Lazo2018-06-19
| |
| * vim-patch:8.0.0615: using % with :hardcopy wrongly escapes spacesJan Edmund Lazo2018-06-19
| | | | | | | | | | | | Problem: Using % with :hardcopy wrongly escapes spaces. (Alexey Muranov) Solution: Expand % differently. (Christian Brabandt, closes vim/vim#1682) https://github.com/vim/vim/commit/bf15b8d78b22661db8b19d662b62bb9a061cdd37
* | vim-patch:8.0.0546: swap file exists briefly when opening the command window ↵Jan Edmund Lazo2018-06-19
|/ | | | | | | | (#8588) Problem: Swap file exists briefly when opening the command window. Solution: Set the noswapfile command modifier before splitting the window. (James McCoy, closes vim/vim#1620) https://github.com/vim/vim/commit/3bab93998d01a01b7f2a071fa3b8054bb0094625
* vim-patch:8.0.0598: building with gcc 7.1 yields new warnings (#8585)Jan Edmund Lazo2018-06-19
| | | | | Problem: Building with gcc 7.1 yields new warnings. Solution: Initialize result. (John Marriott) https://github.com/vim/vim/commit/9e0f6ec0762575d229b86798b284ca4876bc3d73
generated by cgit (git 2.34.1) at 2025-06-08 07:34:04 +0000