| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
| |
Problem: cannot get the text under the cursor like v:beval_text
Solution: Add <cexpr>.
https://github.com/vim/vim/commit/65f084749b260746d7f186af4f080298be2df55b
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
Problem: No completion for argument list commands.
Solution: Add arglist completion. (Yegappan Lakshmanan, closes vim/vim#2706)
https://github.com/vim/vim/commit/cd43effecab02c6c28b1c4a3a14f91b8c3f26c0d
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
Problem: No completion for :mapclear.
Solution: Add completion (Nobuhiro Takasaki et al. closes vim/vim#1943)
https://github.com/vim/vim/commit/cae92dc3d5bdd4009910671328cd01394bfbe2cf
|
|
|
|
| |
ref #1474
|
| |
|
|
|
|
|
|
|
| |
First step towards implemening issue #7401.
The same can be done for all deprecated mb_ functions in follow-up
patches.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
| |
Ref #8474
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| | |
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
|
|/
|
|
|
|
|
|
| |
(#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
|
|
|
|
|
| |
Problem: Building with gcc 7.1 yields new warnings.
Solution: Initialize result. (John Marriott)
https://github.com/vim/vim/commit/9e0f6ec0762575d229b86798b284ca4876bc3d73
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This changes Ex mode (Q, -e) to work like Vim's "improved Ex mode"
(gQ, -E). That brings some small behavior differences, but should not
impact most Ex scripts (unless, for example, they depend on mappings
being disabled--but that can be solved for -e by skipping user config).
Before this change:
* the screen test hangs.
After this change:
* Q acts like gQ.
* -e/-es differs from -E/-Es only in its treatment of stdin.
This moves towards potentially removing getexmodeline().
(HINT: That does NOT mean "removing Ex mode", it means removing the
Vi-compatible Ex mode, which differs from Vim's "improved Ex mode" only
in some minor details (e.g. mappings are disabled).)
ref #1089 :-)~
|
|
|
|
|
|
|
| |
Problem: Some macros are in lower case.
Solution: Make a few more macros upper case. Avoid lower case macros use an
argument twice.
https://github.com/vim/vim/commit/91acfffc1e6c0d8c2abfb186a0e79a5bf19c3f3f
|
|
|
|
|
| |
Problem: There are still a few macros that should be all-caps.
Solution: Make a few more macros all-caps.
https://github.com/vim/vim/commit/8820b48654b62472821d9b155fe03ab7ac13a05c
|
|
|
|
|
|
| |
Problem: ml_get errors in silent Ex mode. (Dominique Pelle)
Solution: Clear valid flags when setting the cursor. Set the topline when
not in full screen mode.
https://github.com/vim/vim/commit/d5d37537d1fa46fd468bd378af2006dd09840f38
|
| |
|
|
|
|
|
|
|
| |
Support more :command attributes:
-bang
-bar
-register
|
|
|
|
|
|
| |
- Always return all keys, with at least NIL value.
- Require `opts` param to be {"builtin":false}
- Validate `opts` param
|
| |
|
|\
| |
| | |
closes #4983
|
| | |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Vim has the 'swapsync' option which we removed in 62d137ce0969.
Instead let 'fsync' control swapfile-fsync.
These cases ALWAYS force fsync (ignoring 'fsync' option):
- Idle (CursorHold).
- Exit caused by deadly signal.
- SIGPWR signal.
- Explicit :preserve command.
|
|/ /
| |
| |
| | |
fix #7494
|
| |
| |
| |
| |
| | |
closes #3648
ref #5959
|
|/ |
|
|
|
| |
Removes obsolete did_throw after that.
|
|
|
|
| |
Fixes #7876
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
It's a micro-optimization; check path_is_absolute_path(autocmd_fname)
instead.
The main optimization (which is still in place) afforded by Vim 7.2.021
was to avoid resolving <afile> when it is not needed.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
During provider dispatch, eval_call_provider() saves global
state--including pointers, such as `autocmd_fname`--into
`provider_caller_scope` which is later restored by f_rpcrequest().
But `autocmd_fname` is special-cased in eval_vars(), for performance
(see Vim patch 7.2.021; this is also the singular purpose of the
`autocmd_fname_full` global. Yay!)
If eval_vars() frees `autocmd_fname` then its provider-RPC-scoped alias
becomes a problem.
Solution: Don't free autocmd_fname in eval_vars(), just copy into it.
closes #5245
closes #5617
Reference
------------------------------------------------------------------------
Vim patch 7.2.021
https://github.com/vim/vim/commit/f6dad43c98f47da1ff9d8c99b320fc3674f83c63
Problem: When executing autocommands getting the full file name may be
slow. (David Kotchan)
Solution: Postpone calling FullName_save() until autocmd_fname is used.
vim_dev discussion (2008): "Problem with CursorMoved AutoCommand when
Editing Files on a Remote WIndows Share"
https://groups.google.com/d/msg/vim_dev/kj95weZa_eE/GTgj4aq5sIgJ
|
| |
|
|
|
|
|
|
|
| |
Problem: Using "1q" it is possible to unload a changed buffer. (Rick Howe)
Solution: Check the right window for changes.
https://github.com/vim/vim/commit/ff930cad8a9100eeb04256aab1a14de993c1d7e9
|
|
|
|
|
|
|
| |
Problem: Can exit while a terminal is still running a job.
Solution: Consider a buffer with a running job like a changed file.
https://github.com/vim/vim/commit/eb44a68b42eda207a5bc4def9ea8fc4d38acb650
|
|
|
|
|
|
|
|
|
| |
Problem: The conf filetype detection is done before ftdetect scripts from
packages that are added later.
Solution: Add the FALLBACK argument to :setfiletype. (closes vim/vim#1679,
closes vim/vim#1693)
https://github.com/vim/vim/commit/3e54569b17683318e0cb6693ab0024c2ad1e3e8f
|
|
|
|
|
|
|
| |
Problem: A QuitPre autocommand may get the wrong file name.
Solution: Pass the buffer being closed to apply_autocmds(). (Rich Howe)
https://github.com/vim/vim/commit/87ffb5c1a3aa506a1be07af4e794b3753f839dc3
|
|
|
|
|
|
|
|
| |
Problem: Segfault with QuitPre autocommand closes the window. (Marek)
Solution: Check that the window pointer is still valid. (Christian Brabandt,
closes vim/vim#1817)
https://github.com/vim/vim/commit/0ea5070d79c8a13fb2403280a72f968495b0fab7
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Until now, the default `:filetype ...` setup was skipped if the user
config touched `:filetype` in any way (including implicitly via `:syntax
on`). No one needs that, and it's very confusing.
Instead, proceed with `:filetype ... on` unless the user explicitly
called `:filetype ... off`.
closes #7765
|