aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* | ui: Only call ui_flush when the busy state changesThiago de Arruda2015-03-16
| | | | | | | | | | Also add back the `ui_flush` call to `get_keystroke`. Its necessary to display prompt messages correctly.
* | ui: Replace cursor_{on,off} by busy_{stop,start}Thiago de Arruda2015-03-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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).
* | vim-patch: mark 7.4.660 as includedoni-link2015-03-13
| | | | | | | | | | | | refs #2138 vim-patch: https://code.google.com/p/vim/source/detail?r=476a12a96bb1e5ccc71b1c1010d529deca271617
* | syntax.c: Prevent use after free for variable g:colors_name.oni-link2015-03-13
| | | | | | | | | | | | | | | | | | | | | | ASan spotted a problem when using 'set background={light,dark}' with color scheme solarized. While loading the colors for color scheme 'g:colors_name', the pointer on the value for this variable can become invalid, because of an 'unlet colors_name' (part of an :highlight clear, syntax.c:6173). To prevent the use of the freed value, decouple the value from 'g:colors_name' before calling load_colors() with it.
* | vim-patch:7.4.637 #2126Lech Lorens2015-03-13
|/ | | | | | | | Problem: Incorrectly read the number of buffer for which an autocommand should be registered. Solution: Reverse check for "<buffer=abuf>". (Lech Lorens) https://code.google.com/p/vim/source/detail?r=v7-4-637
* Merge pull request #2118 from rev112/fix_redundant_castJohn Szakmeister2015-03-13
|\ | | | | Remove redundant casts
| * Remove redundant castsAnton Ovchinnikov2015-03-09
| |
* | Interface cleanup: Symlink handling & docsMichael Reed2015-03-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This removes the ability to start nvim via the following aliases in favor of just using their command line arguments: ex vim -e exim vim -E view vim -R gvim vim -g gex vim -eg gview vim -Rg rvim vim -Z rview vim -RZ rgvim vim -gZ rgview vim -RgZ This also removes Vi mode (-v) for consistency. From ':help -v': -v Start Ex in Vi mode. Only makes a difference when the executable is called "ex" or "gvim". For gvim the GUI is not started if possible.
* | vim-patch: mark 7.4.615 as included #2109Michael Reed2015-03-12
| | | | | | | | | | | | refs #1761 Original vim patch: http://ftp.vim.org/vim/patches/7.4/7.4.615
* | Merge pull request #2114 from oni-link/remove.assertJohn Szakmeister2015-03-12
|\ \ | | | | | | Fixes for two compiler warnings
| * | Compiler warns about uninitialized object in vim_eval().oni-link2015-03-08
| | | | | | | | | | | | | | | In case of an evaluation error the returned Object is not initialized, so initialize it with OBJECT_INIT.
| * | Remove unnecessary assert() in os_dirname().oni-link2015-03-08
| |/ | | | | | | | | | | | | | | | | Compiler warns about buf always being nonnull. buf is per function attribute always nonnull, so buf can be removed from the assert(). But a buffer length of zero is also no problem, because it makes uv_cwd() return a failure without writing into buf. So the remaining length check can also be removed.
* | os_unix_defs && os/unix_defs: Consistently use '~' over '$HOME' #2009Michael Reed2015-03-11
| | | | | | | | | | | | these path names are ridiculous... Based on #889, but also remove some unused #defines
* | legacy tests: migrate test84Rainer Borene2015-03-11
| |
* | legacy tests: migrate test91Rainer Borene2015-03-11
| |
* | legacy tests: migrate test90Rainer Borene2015-03-11
| |
* | legacy tests: migrate test95Rainer Borene2015-03-11
| |
* | legacy tests: migrate test15Rainer Borene2015-03-11
| |
* | legacy tests: migrate test_listlbr_utf8Rainer Borene2015-03-11
| |
* | legacy tests: migrate test98Rainer Borene2015-03-11
| |
* | legacy tests: migrate test103Rainer Borene2015-03-11
| |
* | legacy tests: migrate test_qf_titleRainer Borene2015-03-11
| |
* | legacy tests: migrate test100Rainer Borene2015-03-11
| |
* | test: migrate legacy test 77 #2046Gustaf Lindstedt2015-03-08
| | | | | | | | Migrate legacy test 77 which tests mf_hash_grow() to lua/busted.
* | version: don't use NVIM_VERSION_* directly outside version.cBjörn Linse2015-03-08
| | | | | | | | This avoids recompiles after commiting.
* | config: split out versiondef.h from config.hBjörn Linse2015-03-08
|/ | | | This avoids recompiling every c file after comitting.
* tui: fall back to underline for undercurl. #2099Chase Geigle2015-03-07
| | | | closes #2098
* set_init_1: mb_init() on fallback encoding (utf8) #2106Floris van Liere2015-03-07
| | | | | | | | | | | | Explanation: Running `:set encoding=utf-8` _after_ startup correctly initializes multibyte; but mb_init() was _not_ called during startup if locale detection (enc_locale()) failed. This wasn't a problem in Vim because the Vim default encoding (latin1) does not require mb_init(). But Nvim defaults to utf8, so mb_init() is required. closes #1271 closes #1672
* Macro cleanup: USE_UNIXFILENAMEMichael Reed2015-03-05
|
* Macro cleanup: USE_ON_FLY_SCROLLMichael Reed2015-03-05
|
* Macro cleanup: USER_HIGHLIGHTMichael Reed2015-03-05
|
* Macro cleanup: USE_EXE_NAMEMichael Reed2015-03-05
|
* Macro cleanup: ONE_CLIPBOARDMichael Reed2015-03-05
|
* Macro cleanup: UNICODE16Michael Reed2015-03-05
| | | | Fix clint warnings as well.
* Macro cleanup: SPACE_IN_FILENAMEMichael Reed2015-03-05
|
* Macro cleanup: HAVE_SANDBOXMichael Reed2015-03-05
|
* vim-patch:7.4.578oni-link2015-03-04
| | | | | | | | Problem: Using getcurpos() after "$" in an empty line returns a negative number. Solution: Don't add one when this would overflow. (Hirohito Higashi) https://code.google.com/p/vim/source/detail?r=v7-4-578
* remote_ui: Fix error messages #2045Carlos Castillo2015-03-04
| | | | Make the error messages more precise and uniform.
* jobsend: Don't append extra newline after last itemBjörn Linse2015-03-03
| | | | This allows sending binary data that is not newline terminated
* deps: Add libvterm to the project dependenciesThiago de Arruda2015-02-28
| | | | | libvterm is a terminal emulation library with abstract display. It will be used to implement builtin terminal emulation into Nvim.
* illumos requires the use of limits.h for things like INT_MAX #2049Mike Zeller2015-02-26
|
* Fix warnings: message.c: copy_hotkeys_and_msg: Garbage value: FP. #2062Eliseo Martínez2015-02-26
| | | | | | | | | | | | | | Problem : Branch condition evaluates to a garbage value @ 2868. Diagnostic : False positive. Rationale : Array has_hotkey, declared at 2812, is initialized by console_dialog_alloc (only the needed number of elements). That same number of elements is used by copy_hotkeys_and_msg. Suggested path error is impossible, because it involves a different number of elements in those functions. Resolution : Above condition is cumbersome to prove through assertions. Thus, we prefer to just initialize the array to all-false at declaration point before calling console_dialog_alloc.
* job: Allow spawning jobs connected to pseudo terminalsThiago de Arruda2015-02-23
|
* job: Refactor process spawning and startup argumentsThiago de Arruda2015-02-23
| | | | | | | | - process spawning was decoupled from the rest of the job control logic. The goal is reusing it for spawning processes connected to pseudo terminal file descriptors. - job_start now receives a JobOptions structure containing all the startup options.
* job: Send SIGTERM before calling job_stop in job_teardownThiago de Arruda2015-02-23
| | | | | Send sigterm immediately since it can be caught by processes. If they don't respond and are still alive after a while, SIGKILL will be sent.
* eval: Fix buffering of data in job autocommandsThiago de Arruda2015-02-23
| | | | | Job autocommands will no longer buffer data chunks that don't end in newlines characters.
* Simpler handling for "always-on"/"always-off" options. #2002Florian Walch2015-02-22
| | | | | 'compatible' and 'edcompatible' are forced to be off. 'ttyfast' is forced to be on.
* tui: Also use xterm-256color when TERM=screen and COLORTERM != NULLThiago de Arruda2015-02-21
| | | | | When COLORTERM != null force xterm-256color capabilities when TERM equals xterm or screen.
* Fix warnings: window.c: close_last_window_tabpage(): Use after free: RI.Eliseo Martínez2015-02-21
| | | | | | | | | | | | | Problem : Use after free @ 1795. Diagnostic : Real issue. Rationale : prev_curtab can in fact be freed as a result of call `win_close_othertab(win, free_buf, prev_curtab);`, but it's later used at `sprintf(..., tabpage_index(prev_curtab));`. This was introduced at 3ffc5d81c34cfdd535573a50790690c88e4324bb. Resolution : Move prev_idx calculation before the call freeing prev_curtab.
* Fix warnings: screen.c: screen_puts_len(): Various (4): FP/MI.Eliseo Martínez2015-02-21
| | | | | | | | | | | | | | | | Problems : Assigned value is garbage or undefined @ 5363. Result of operation is garbage or undefined @ 5356. Result of operation is garbage or undefined @ 5320. Result of operation is garbage or undefined @ 5192. Diagnostic : False positives / Multithreading issues. Rationale : Suggested error paths contain incoherent values for has_mbyte, enc_utf8, and enc_dbcs, which should always hold the relationship has_mbyte = enc_utf8 || enc_dbcs, with enc_utf8 and enc_dbcs being mutually exclusive. Asserting on the globals, though, fails, because checker believes they could be modified by other threads in between. Resolution : Make local copy of globals and assert relationship on them.