| Commit message (Collapse) | Author | Age |
... | |
|\ \
| | |
| | | |
Remove MiNT, NeXTSTEP, OS/2 References
|
| | |
| | |
| | |
| | |
| | | |
Paul Slootman was removed from the top of os_unix.c as OS/2 is no longer
supported, but is still credited in runtime/doc/intro.txt.
|
| | | |
|
| | |
| | |
| | |
| | | |
Remove trailing whitespace as well.
|
|\ \ \
| | | |
| | | | |
Fix newline substitution causing abort
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem : Command `s/\n//` is being translated into a call to do_join
with a count of 1. But do_join asserts its precondition count
>= 2, which is causing the program to abort.
Note : This in fact revealed bigger problems: generated join command
line count, as well as reported substitutions/lines were
wrong in several cases, since patch 7.4.232.
See:
[patch] http://markmail.org/message/vo7ruair5raccawp
[issue] https://code.google.com/p/vim/issues/detail?id=287
Solution : - Don't generate join command for single-line-range case.
- Make generated join command include:
* lines in range + 1, when range doesn't end at last line.
* lines in range, when range ends at last line.
- Make reported substitutions/lines always be
number-of-lines-joined - 1.
|
|\ \ \
| |/ /
|/| | |
Non-unix-specific os_unix function.
|
| | |
| | |
| | |
| | |
| | | |
Move general initialization functions to early_init, which simplifies
test/unit/helpers.lua, which requires all these functions.
|
| | |
| | |
| | |
| | |
| | | |
Use the portable uv_kill.
Don't bother with archaic BeOS.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Switch from POSIX's write() to fwrite(stdout,...) and disable buffering
since vim buffers output explicitly and flushes when needed, like when a
key is typed.
|
|\ \ \
| | | |
| | | | |
Fix some more -Wconversion warnings.
|
| | | |
| | | |
| | | |
| | | | |
Warnings were fixed in #1488.
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
eval: Fix coverity false positive.
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
** CID 74786: Resource leak (RESOURCE_LEAK)
/src/nvim/eval.c: 10614 in f_jobsend()
/src/nvim/eval.c: 10616 in f_jobsend()
save_tv_as_string() should return NULL and input_len <= 0 for an empty
string or error. Callers should check that input != NULL instead of
input_len > 0 and assert(input == NULL) when the length must be checked.
|
|\ \ \
| | | |
| | | | |
vim-patch:7.4.425,435,467,472,473,478
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
vim-patch:7.4.478
Problem: Using byte length instead of character length for
'showbreak'.
Solution: Compute the character length. (Marco Hinz)
https://code.google.com/p/vim/source/detail?r=v7-4-478
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
vim-patch:7.4.473
Problem: Cursor movement is incorrect when there is a number
column/sign/fold column and 'sbr' is displayed.
Solution: Adjust the column for 'sbr'. (Christian Brabandt)
https://code.google.com/p/vim/source/detail?r=v7-4-473
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
vim-patch:7.4.472
Problem: The "precedes" entry in 'listchar' will be drawn when
'showbreak is set and list is not.
Solution: Only draw this character when 'list' is on. (Christian
Brabandt)
https://code.google.com/p/vim/source/detail?r=af998690a8841d4df95cea0bed4246f2ba98e247
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
vim-patch:7.4.467
Avoid a problem with unwanted linebreaks in block mode
https://code.google.com/p/vim/source/detail?r=v7-4-467
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
vim-patch:7.4.435
Problem: Line formatting behaves differently when 'linebreak' is set.
(mvxxc)
Solution: Disable 'linebreak' temporarily. (Christian Brabandt)
https://code.google.com/p/vim/source/detail?r=v7-4-435
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
vim-patch:7.4.425
Problem: When 'showbreak' is used "gj" may move to the wrong
position. (Nazri Ramliy)
Solution: Adjust virtcol when 'showbreak' is set. (Christian Brabandt)
https://code.google.com/p/vim/source/detail?r=v7-4-425
|
| | | |
| | | |
| | | |
| | | |
| | | | |
These functions were only being used by mbyte.c, so move them and add the
"static" modifier.
|
| |/ /
|/| |
| | |
| | | |
This is not being used and should not be part of the core anyway.
|
| | |
| | |
| | |
| | | |
Also move read_error_exit to os/input.c
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
These functions only used to call another os_* function, so remove them and
replace all occurences in the project.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Also:
- Remove NO_CONSOLE_INPUT/NO_CONSULE preprocessor conditionals
- Remove ctrl_c_interrupts variable, check for mapped_ctrl_c directly in
process_interrupts()
- Move ui_inchar profiling to input_poll which is where Nvim blocks for input.
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| | |
- By default vim_feedkeys escaped all input for CSI/K_SPECIAL bytes
before using it. However since vim_replace_termcodes() also escapes
the input string chaining these functions together escapes input twice
- vim_feedkeys() now takes a third Boolean argument to enable/disable
escaping
- Breaks API compatibility
|
|\ \
| | |
| | | |
add missing refcount increment for systemlist()
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- get_system_output_as_rettv() was missing a refcount increment when
returning an empty list, i.e. when there was no output
- we now use rettv_list_aloc() instead of list_alloc()
- issue #1530
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
`try_malloc` was changed in 8bb2c2c0742c57150655e18cf8418a758cebdce8 to
avoid a warning when size is 0. Then, this improves some things on that:
- Use local vars instead of changing parameters.
- Homogenize style for other related functions.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Two new functions, `event_enable_deferred()`/`event_disable_deferred()` have to
be called by code that is capable of handling asynchronicity. User-dialog states
like "press ENTER to continue" or the swap file confirmation no longer will
generate K_EVENT.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|