| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |\ |
|
| | |
| |
| |
| | |
Allows eval/typval.h to #include message.h.
|
| |\ \
| |/
|/| |
|
| | | |
|
| |/
|
|
|
|
|
|
| |
Main points:
- Replace `char_u` with `char` in some cases.
- Remove `str[len] = NUL` hack in some cases when `str` may be considered
`const`.
|
| | |
|
| |
|
|
| |
Closes #5422
|
| | |
|
| |
|
|
|
|
|
| |
Problem: There is no way to get a list of the error lists.
Solution: Add ":chistory" and ":lhistory".
https://github.com/vim/vim/commit/f6acffbe83e622542d9fdf3066f51933e46e4954
|
| | |
|
| |
|
|
|
|
|
|
| |
Problem: evalcmd() has a confusing name.
Solution: Rename to execute(). Make silent optional. Support a list of
commands.
https://github.com/vim/vim/commit/79815f1ec77406f2f21a618c053e5793b597db7a
|
| |
|
|
|
|
|
| |
Problem: Typing "k" at the hit-enter prompt has no effect.
Solution: Don't assume recursive use of the prompt if a character was typed.
(Hirohito Higashi)
https://github.com/vim/vim/commit/a0055ad3a789b8eeb0c983d8a18d4bcaeaf456b8
|
| |
|
|
|
|
|
|
|
| |
Problem: It is not possible to only see part of the message history. It is
not possible to clear messages.
Solution: Add a count to ":messages" and a clear argument. (Yasuhiro
Matsumoto)
https://github.com/vim/vim/commit/451f849fd6282a4facd4f0f58af62837443fb5a6
|
| |
|
| |
Closes #5558
|
| |
|
|
|
|
|
|
|
|
| |
move `call_shell` to misc1.c
Move some fns to state.c
Move some fns to option.c
Move some fns to memline.c
Move `vim_chdir*` fns to file_search.c
Move some fns to new module, bytes.c
Move some fns to fileio.c
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
https://groups.google.com/forum/#!msg/vim_dev/H3Z3ChSUh_4/beZs6KzYdBsJ
|
| |/ |
|
| |
|
|
|
|
|
| |
vim-patch:7.4.1603
TODO(bfredl): if we allow events in HITRETURN and ASKMORE states,
we need to add the necessary redraws as well.
|
| | |
|
| |\
| |
| | |
vim-patch: 7.4.1347
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Problem: When there is any error Vim will use a non-zero exit code.
Solution: When using ":silent!" do not set the exit code. (Yasuhiro
Matsumoto)
https://github.com/vim/vim/commit/8b778d55993d951a65f8a59843cecd177c707676
|
| |/
|
|
| |
Originally there were 128 new errors, so I thought this is a good idea to fix
all of them. Of course, this commit also fixes many suppressed errors.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
1. Do not allow reading past buffer end when creating error messages.
2. Fix surrogate pairs range, avoid magic constants.
|
| |
|
|
|
|
|
| |
Problem: 0x202f is not recognized as a non-breaking space character.
Solution: Add 0x202f to the list. (Christian Brabandt)
https://github.com/vim/vim/commit/73284b973a013692dd1055cf210f3138a7f3c497
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Regarding the individual items in the header:
`Vim - Vi improved by Bram Moolenar`
Bram Moolenar is already mentioned throughout the documentation, as
well as the intro screen.
`:help uganda`
It's already shown to all users who don't use `shortmess+=I` upon
starting nvim, and is already placed prominently in help.txt, i.e.,
`:help` run with no arguments.
`:help credits`
Already mentioned near the top of help.txt.
`README.md`
Already mentioned in develop.txt.
|
| | |
|
| |
|
|
|
| |
The former no longer exists in this repo; see the top of
src/nvim/README.md.
|
| |
|
|
|
|
|
| |
Problem: Can't specify when not to ring the bell.
Solution: Add the 'belloff' option. (Christian Brabandt)
https://github.com/vim/vim/commit/165bc69d1b7f70ca9d5b657f35d0584ecb7b5183
|
| | |
|
| |
|
|
|
|
| |
Making an environment variable empty can be a way of unsetting it for
platforms that don't support unsetenv(). In most cases, we treat empty
variables as having been unset. For all others, use os_env_exists().
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Some style changes and minimal refactoring, to tidy up code.
No behavioural changes intended.
|
| |
|
|
|
|
|
| |
Problem: Missing change in another file.
Solution: Also change message.c
https://github.com/vim/vim/releases/tag/v7-4-712
|
| |
|
|
|
|
|
| |
Problem: Various small issues.
Solution: Fix those issues.
https://github.com/vim/vim/releases/tag/v7-4-553
|
| | |
|
| | |
|
| |
|
|
|
|
| |
We already use wrappers for allocation, the new `xfree` function is the
equivalent for deallocation and provides a way to fully replace the malloc
implementation used by Neovim.
|
| |
|
|
| |
Clean up said functions and some outdated comments while we're at it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Switching cursor off is only necessary in two occasions:
- When redrawing to avoid terminal flickering
- When the editor is busy
The first can now be handled by the TUI, so most calls to ui_cursor_off can be
removed from the core.
So, before this commit it was only necessary to switch the cursor off to notify
the user that nvim was running some long operation. Now the cursor_{on,off}
functions have been replaced by busy_{stop,start} which can be handled in a
UI-specific way(turning the cursor off or showing a busy indicator, for
example).
To make things even more simpler, nvim is always busy except when waiting for
user input or other asynchronous events: It automatically switches to a non-busy
state when the event loop is about to be entered for more than 100 milliseconds.
`ui_busy_start` can be called when its not desired to change the busy state in
the event loop (As its now done by functions that perform blocking shell
invocations).
|
| | |
|
