aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* tests: Modernize migrated argument_count test.Lucas Hoffmann2015-06-16
|
* tests: Migrate legacy test argument_count.Lucas Hoffmann2015-06-16
|
* Merge #2819 'tests: Migrate legacy test argument_0count.'.Justin M. Keyes2015-06-16
|\
| * tests: Modernize migrated legacy test argument_0count.Lucas Hoffmann2015-06-16
| |
| * tests: Migrate legacy test argument_0count.Lucas Hoffmann2015-06-16
|/
* ex_docmd.c: :edit is a no-op in terminal buffers #2822Felipe Morales2015-06-14
| | | | Closes #2779
* vim-patch:7.4.719 #2817Andrea Cedraro2015-06-14
| | | | | | | Problem: Overflow when adding MAXCOL to a pointer. Solution: Subtract pointers instead. (James McCoy) https://github.com/vim/vim/commit/v7-4-719
* vim-patch:7.4.593 #2657David Bürgin2015-06-13
| | | | | | | | | | Problem: Crash when searching for "x\{0,90000}". (Dominique Pelle) Solution: Bail out from the NFA engine when the max limit is much higher than the min limit. https://github.com/vim/vim/commit/v7-4-593 See https://groups.google.com/d/msg/vim_dev/c7owwoseba8/ZETgSNZ6p10J
* tui: make termkey use utf-8 mode when &encoding=utf-8 #2469Björn Linse2015-06-13
|
* Merge #2832 'Mark NA patches; vim-patch:7.4.713'Justin M. Keyes2015-06-13
|\
| * vim-patch:7.4.713Felipe Morales2015-06-13
| | | | | | | | | | | | | | | | patch 7.4.713 Problem: Wrong condition for #ifdef. Solution: Change USR_EXRC_FILE2 to USR_VIMRC_FILE2. (Mikael Fourrier) https://code.google.com/p/vim/source/detail?r=v7-4-713
| * version.c: mark NA: 664, 703Justin M. Keyes2015-06-13
| |
| * version.c: Update patches listFelipe Morales2015-06-13
|/ | | | | | | | | | | | | | | | | These patches are not applicable (NA): .611 (if_python3.c) .627 (term.c) .666 (X on *nix) .678 (--remote) .683 (vimtutor) .687 (terminal) .691 (mzscheme) .692 (Solaris) .730 (crypto) .731 (GUI) .738 (compiling w/o syntax highlighting) .644 applied in an unsupported platform (Stratus VOS)
* Fix legacy tests makefile after 4873171f. #2826Lucas Hoffmann2015-06-12
|
* Merge #2585 'Migrate legacy test 74.'Justin M. Keyes2015-06-12
|\
| * tests: wviminfo_spec.lua: reworkJustin M. Keyes2015-06-12
| | | | | | | | 074_global_var_in_viminfo_spec: remove some redundant sanity checks.
| * tests: Add tests for the :wv command.Lucas Hoffmann2015-06-12
| |
| * tests: Migrate legacy test 74.Lucas Hoffmann2015-06-12
|/ | | | | Helped-By: David Bürgin <676c7473@gmail.com> Helped-By: Justin M. Keyes <justinkz@gmail.com>
* memline: Don't call memmove() with a NULL argument in ml_add_stack(). #2802oni-link2015-06-12
| | | | | | | | | When ml_add_stack() needs to increase the size of the empty stack, buf->b_ml.ml_stack is NULL and is used as argument in memmove(). This is undefined behaviour. Declaration of memmove() in string.h: extern void *memmove (void *__dest, const void *__src, size_t __n) __THROW __nonnull ((1, 2));
* Add complete() noinsert/noselect support #2792Shougo Matsushita2015-06-11
|
* Merge #2735 'provider: Only call system() once, don't use Python 3 ↵Florian Walch2015-06-09
|\ | | | | | | interpreter for +python, improve messages'.
| * provider/pythonx: Show absolute path to executable in error message.Florian Walch2015-06-09
| |
| * provider/pythonx: Merge s:check_version() and s:check_interpreter().Florian Walch2015-06-09
| |
| * provider/pythonx: Don't use Python 3 interpreter for +python.Florian Walch2015-06-09
| | | | | | | | | | | | | | | | | | The executable 'python' can refer to either Python 2 or Python 3. Add a check to only accept Python 2 interpreters as providers for +python. Also improve the error messages. Resolves #2734.
| * provider/pythonx: return error from DetectDaniel Hahler2015-06-09
| | | | | | | | Ref: https://github.com/blueyed/neovim/commit/9b653ce0#commitcomment-11195449
| * remote#host#RequirePythonHost: fix reference to logDaniel Hahler2015-06-09
| | | | | | | | | | | | | | | | I could not find a reference to NVIM_PYTHON_PYTHON_LOG anywhere, and python-client looks for NVIM_PYTHON_LOG_FILE. ~/.nvimlog appears to be hardcoded and enabled by default. This would need to be adjusted when this changes.
| * provider/python: Call: fix usage of 'finish' in functionDaniel Hahler2015-06-09
| | | | | | | | | | Do not call it again in case of an exception in `remote#host#Require` (ref: https://github.com/neovim/neovim/pull/2549#issuecomment-102674350).
| * provider/python: define Prog and Error functions alwaysDaniel Hahler2015-06-09
| | | | | | | | | | | | | | | | `provider#pythonX#Error` and `provider#pythonX#Prog` are currently meant for debugging only (the error message is not being used), and should therefore be defined always, especially in case of errors. Ref: https://github.com/neovim/neovim/pull/2549#issuecomment-98607580
| * provider/pythonx: Detect: only return valid versionsDaniel Hahler2015-06-09
| | | | | | | | | | The `check` return value of `s:check_version` was not being used, and it was returned always.
| * provider/pythonx: test python3/2 first, do not test python3.2Daniel Hahler2015-06-09
| | | | | | | | | | python3/python2 will typically point at the default / most recent interpreter.
| * provider/pythonx: add reference to ":help nvim-python" for errorDaniel Hahler2015-06-09
| |
| * provider/pythonx: fix grammar with errorDaniel Hahler2015-06-09
| |
| * provider/pythonx: only call system("python") onceDaniel Hahler2015-06-09
|/ | | | | `s:check_interpreter` will query/return the version also, so that `s:check_version` can just use that, without calling "python" again.
* Travis: Disable Valgrind in GCC build. #2806Florian Walch2015-06-09
| | | | | With Valgrind, the GCC build frequently passed the 50 min timeout on Travis.
* CMake: Fix helptags generation when prefix is not /usr. #2741Thomas Anderson2015-06-09
|
* CMake: Workaround for hanging helptags generation. #2801Florian Walch2015-06-06
| | | | | | | | | | | | | | | | | | | | | | | Piping input into nvim causes the helptags generation to hang. For example, the following does not work: yes | nvim -c "helptags ." The helptags are generated during installation with a command similar to the one above, using CMake's execute_process to call nvim. As execute_process does not use an intermediate shell, the following will cause the installation to hang: yes | make install pacaur, an Arch Linux package helper, uses a similar command to install packages [1], and thus can currently not be used to install Neovim. This commit adds a workaround to GenerateHelptags.cmake to circumvent this problem. [1] https://github.com/rmarquis/pacaur/blob/22c00a3d05f6504b44dfbc2f3cbd6ab1291e3c9c/pacaur#L825
* plugin: enable the matchit plugin by default #2723Felipe Morales2015-06-04
| | | | | Reviewed-by: Scott Prager <splinterofchaos@gmail.com> Reviewed-by: Michael Reed <m.reed@mykolab.com>
* Add noinsert and noselect features in completeopt #2564Shougo Matsushita2015-06-04
| | | | | | | | | | | | Backported from vim_dev: https://groups.google.com/forum/#!searchin/vim_dev/completeopt/vim_dev/tVsk0pdOGvs/fCzBbPkA4w0J Use case: https://github.com/Shougo/neocomplcache.vim/issues/426 Reviewed-by: Felipe Morales <hel.sheep@gmail.com> Reviewed-by: Scott Prager <splinterofchaos@gmail.com> Reviewed-by: Michael Reed <m.reed@mykolab.com>
* CMake: Fix _FORTIFY_SOURCE detection when using hardening-wrapper. #2788Florian Walch2015-06-04
| | | | | | | | | | | | When checking code with check_c_source_compiles, the "check variable" (for the _FORTIFY_SOURCE detection: previously _FORTIFY_SOURCE_ACCEPTABLE, now HAS_ACCEPTABLE_FORTIFY) is passed to the compiler like -D_FORTIFY_SOURCE_ACCEPTABLE. This throws off hardening-wrapper [1], which then NOT sets _FORTIFY_SOURCE=2 for the check, assuming it had already been set manually as it detected -D_FORTIFY_SOURCE*. Renaming the "check variable" to not match this pattern works around this problem. [1] https://github.com/thestinger/hardening-wrapper
* Merge pull request #2766 from Pyrohh/misc-cleanupMichael Reed2015-06-01
|\ | | | | | | | | [RDY] doc: Various removals/cleanups Reviewed-by: Felipe Morales <hel.sheep@gmail.com>
| * doc: Misc. X11-related cleanupsMichael Reed2015-06-01
| | | | | | | | | | | | | | These were all introduced by the previous commit, and spotted with with `make html` in `runtime/doc`. [ci skip]
| * doc: starting.txt cleanupMichael Reed2015-06-01
|/ | | | | | | - Removed mention of many options which don't exist anymore. - Add new tags for some new options (e.g., -v) While here, also remove a few X11 references.
* rplugin: Improve remote plugins detection messages #2769Shougo Matsushita2015-05-31
|
* Merge #2762 'terminal: don't set vterm size to 0'Justin M. Keyes2015-05-31
|\
| * fix for #2732 : win_new_width checks height before terminal_resizeFrederik Van Slycken2015-05-31
| | | | | | | | | | | | | | | | | | | | When splitting the window (win_split_ins), function win_new_width is already called before the height has been set. This calls terminal_resize, which passes a height of 0 on to libvterm, which doesn't handle a height of 0 properly. A fix is already in place in terminal.c for not passing on the height, but strictly speaking, it doesn't make sense for window to call terminal_resize when it isn't initialized completely yet.
| * terminal : don't set vterm size to 0 (workaround #2732)Frederik Van Slycken2015-05-31
|/
* Merge pull request #2767 from Pyrohh/mainerr-simplifyMichael Reed2015-05-30
|\ | | | | | | | | | | [RDY] main.c: Some refactoring / cleanups Reviewed-by: Scott Prager <splinterofchaos@gmail.com> Reviewed-by: oni-link <knil.ino@gmail.com>
| * Passing by: Remove X_LOCALE refsMichael Reed2015-05-30
| | | | | | | | We don't link to any X11 libs, so this is most likely unneeded.
| * main.c:mainerr(): Namespace messagesMichael Reed2015-05-30
| | | | | | | | | | | | | | | | | | | | Error messages in general should be namespaced, especially in the context of a shell. Given the possibility of a backgrounded job printing messages to standard output/error, namespacing these messages should avoid any confusion as to where the message came from. Helped-by: Scott Prager <splinterofchaos@gmail.com> Helped-by: oni-link <knil.ino@gmail.com>
| * main.c: Simplify error string managementMichael Reed2015-05-30
|/ | | | | | | | This removes the need for preprocessor defines as array indices, and brings error handling more in line with other files, which for the most most part to use constant strings (also, see `globals.h`). Helped-By: Nicolas Hillegeer <nicolas@hillegeer.com>