aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* man.vim: avoid duplicate buffers, E95Justin M. Keyes2018-10-25
| | | | | | | | | | | | | | | | | | | | Before this commit, man#init_pager() always tries to scrape the manpage name and set the buffer name. That's much less important than avoiding duplicate buffers and E95. And it doesn't seem to be necessary, usually. Steps to reproduce: $ export MANPAGER="nvim -c 'set ft=man' -" $ man sleep :Man sleep Error detected while processing function man#init_pager: line 15: E95: Buffer with this name already exists :ls! 1 h- "man://SLEEP(1)" line 4 2 %a- "man://sleep(1)" line 1
* CI/Travis/macOS: use default Travis-provided python/pipJustin M. Keyes2018-10-23
| | | | | | | Despite #9095, `brew upgrade python` broke again, somehow. We should not bother attempting to force a python version. Instead use whatever python Travis provides on the macOS image.
* Merge #9145 'CI, nodejs fixes'Justin M. Keyes2018-10-22
|\
| * auevents.lua: keep events in alphabetical orderJustin M. Keyes2018-10-22
| |
| * provider/nodejs: fix npm,yarn detectionJan Edmund Lazo2018-10-22
| | | | | | | | | | | | | | | | | | | | For each package manager, 1. Check if they are executable before starting a job. 2. Check if the job opts are set before checking the job status TODO: Validate the job id. Prioritize npm because it's faster than yarn. Reindent the code to 2-space indent.
| * test: fix/speedup scrollback_specJan Edmund Lazo2018-10-22
| | | | | | | | | | - fix: Use "set PROMPT=$" trick to satisfy screen:expect{any='%$'} - speedup: Use cmd.exe instead of powershell.
| * CI/AppVeyor: invalidate .deps if build.ps1 changesJan Edmund Lazo2018-10-22
| |
| * CI/AppVeyor: fix MSBuild hack for functional testsJan Edmund Lazo2018-10-22
| | | | | | | | | | | | PR #9087 changed the error string by removing 'Running', breaking the MSBuild hack detecting failure for functional tests. If stdout or stderr has a line with 'functional tests failed with error', fail the build.
* | Merge pull request #9143 from bfredl/nuclearBjörn Linse2018-10-22
|\ \ | |/ |/| disable clearing almost everywhere, cleanup screen.c dead code
| * ui: disable clearing almost everywhereBjörn Linse2018-10-22
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Avoid clearing the screen in most situations. NOT_VALID should be equivalent to CLEAR unless some external force messed up the terminal, for these situations <c-l> and :mode will still clear the screen. Also eliminate some obsolete code in screen.c, that dealt with that in vim drawing window 1 can mess up window 2, but this never happens in nvim. But what about slow terminals? There is two common meanings in which a terminal is said to be "slow": Most commonly (and in the sense of vim:s nottyfast) it means low bandwidth for sending bytes from nvim to the terminal. If the screen is very similar before and after the update_screen(CLEAR) this change should reduce bandwidth. If the screen is quite different, but there is no new regions of contiguous whitespace, clearing doesn't reduce bandwidth significantly. If the new screen contains a lot of whitespace, it will depend of if vsplits are used or not: as long as there is no vsplits, ce is used to cheaply clear the rest of the line, so full-screen clear is not needed to reduce bandwith. However a left vsplit currently needs to be padded with whitespace all the way to the separator. It is possible ec (clear N chars) can be used to reduce bandwidth here if this is a problem. (All of this assumes that one doesn't set Normal guibg=... on a non-BCE terminal, if you do you are doomed regardless of this change). Slow can also mean that drawing pixels on the screen is slow. E-ink screens is a recent example. Avoiding clearing and redrawing the unchanged part of the screen will always improve performance in these cases.
* Merge #9146 from justinmk/fix-warningsJustin M. Keyes2018-10-21
|\
| * fix warning: null arg passed to 'nonnull' paramJustin M. Keyes2018-10-21
| | | | | | | | Found by clang scan-build 5.0
| * fix warning: null arg passed to 'nonnull' paramJustin M. Keyes2018-10-21
| | | | | | | | Found by clang scan-build 5.0
| * fix warning: "Assigned value is garbage"Justin M. Keyes2018-10-21
| | | | | | | | | | | | | | clang scan-build noticed that find_command() may bitmask `eap->flags`. cmd_can_preview() only uses `ea.cmdidx`, but let's fix the warning... Found by clang scan-build 5.0
| * fix warning: "Dead assignment"Justin M. Keyes2018-10-21
| | | | | | | | | | | | | | `tv` is passed to the TYPVAL_ENCODE_CONV_FUNC_BEFORE_* macros, which don't appear to actually use that parameter. Found by clang scan-build 5.0
| * fix warning: null pointer dereferenceJustin M. Keyes2018-10-21
| | | | | | | | Found by clang scan-build 5.0
| * fix warning: garbage/uninitialized valueJustin M. Keyes2018-10-21
| | | | | | | | | | | | | | According to clang scan-build, `fromcol` could be uninitialized at line 2645. Found by clang scan-build 5.0
| * fix warning: "Uninitialized argument"Justin M. Keyes2018-10-21
|/ | | | | | clang scan-build thinks os_system() could set `do_profiling` flag. Found by clang scan-build 5.0
* Merge pull request #9144 from bfredl/ui_event_compatBjörn Linse2018-10-21
|\ | | | | api/ui: verify compatibility of UI events
| * api/ui: verify compatibility of UI eventsBjörn Linse2018-10-21
| |
* | man.vim: :Man! operates on buffer contents (#9139)Justin M. Keyes2018-10-21
| | | | | | | | | | | | | | | | | | mandoc may not handle quoted MANPAGER arguments correctly. E.g. with export MANPAGER='nvim -u NORC -c "set ft=man"' mandoc treats `"set` and `ft=man"'` as separate tokens. To workaround that, provide :Man! so that MANPAGER can avoid quoting. closes #9120
* | Merge #9141 from justinmk/pvsJustin M. Keyes2018-10-21
|\ \ | |/ |/|
| * tui.c: Fix ext.set_underline_color for !has_colon_rgbJustin M. Keyes2018-10-20
| | | | | | | | PVS/V523: The 'then' statement is equivalent to the 'else' statement.
| * screen.c: Fix PVS/V560: condition is always falseJustin M. Keyes2018-10-20
|/
* provider/nodejs: Simultaneously query npm and yarn #9054Mahmoud Al-Qudsi2018-10-18
| | | | | | ref #9001 Instead of serially querying npm and yarn for neovim, start both as a job and then wait for a successful result from either.
* Merge #9130 'build: Fix for macOS 10.14/mojave'Justin M. Keyes2018-10-18
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fix #9050 Q: (from From #7891) > It turns out there's a difference between executing > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang > and /usr/bin/clang. CMake was picking up the former and with that it left off > a key include path. Why? A: /usr/bin/clang is a shim that uses libxcselect/libxcrun under the hood. $ otool -L /usr/bin/clang /usr/bin/clang: /usr/lib/libxcselect.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.200.5) From https://macops.ca/developer-binaries-on-os-x-xcode-select-and-xcrun/ : > this shim binary loads functions in libxcselect.dylib that can locate the > path to the real binary, depending on how the system has been configured. One > part of this process is to check whether this path contains > usr/lib/libxcrun.dylib, and the xcrun tool, in which case it will invoke > xcrun to run the binary. > ... > (If all of this isn’t yet enough indirection for you, /usr/bin/xcrun itself > is a shim, and so libxcselect.dylib contains code to detect whether the > executed xcrun is a shim. Look for the __xcrun_shim segment in the __DATA > section output by the command: pagestuff /usr/bin/xcrun -a.)
| * build/macOS: provide SDK path to deps compilerdm1try2018-10-17
| | | | | | | | | | otherwise, system headers cannot be found on Mojave they were moved from /usr/include to SDK path
| * build/macOS: fix luajit install stepdm1try2018-10-17
| | | | | | | | | | prevent luajit to assigning default value to MACOSX_DEPLOYMENT_TARGET ref #9050
* | Merge #9086 'vim-patch:8.1.0448'Justin M. Keyes2018-10-18
|\ \
| * | test/old: stub CanRunVimInTerminal()Justin M. Keyes2018-10-16
| | |
| * | vim-patch:8.1.0448: cursorline not removed when using 'cursorbind'Justin M. Keyes2018-10-16
| |/ | | | | | | | | | | Problem: Cursorline not removed when using 'cursorbind'. (Justin Keyes) Solution: Store the last cursor line per window. (closes vim/vim#3488) https://github.com/vim/vim/commit/4a5abbd6138240d109278fe1f0b45489d22f712d
* | Merge #9124 'vim-patch:8.0.1672'Justin M. Keyes2018-10-17
|\ \
| * | functionaltest: map error does not cancel promptJan Edmund Lazo2018-10-14
| | |
| * | vim-patch:8.0.1672: error during completion causes command to be cancelledJan Edmund Lazo2018-10-13
| | | | | | | | | | | | | | | | | | Problem: Error during completion causes command to be cancelled. Solution: Reset did_emsg before waiting for another character. (Tom M.) https://github.com/vim/vim/commit/72532d354e699f1cceec34c0b08e1de4d3ea9641
* | | test: Improve 008_autocommands_spec reliability (#9129)Justin M. Keyes2018-10-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Sometimes 008_autocommands_spec fails like this: [ RUN ] autocommands that delete and unload buffers: BufUnload, VimLeave: -- Output to stderr: CMake Error at /home/travis/build/neovim/neovim/cmake/RunTests.cmake:53 (message): functional tests failed with error: 1 The final :quit + wait() is a race. Use command() instead, which is synchronous. Use command('silent! ...') everywhere else too, because it's clearer instead of feeding input and clearing the expected errors with CTRL-L.
* | | Merge #9131 from janlazo/vim-8.0.0670Justin M. Keyes2018-10-17
|\ \ \
| * | | vim-patch:8.0.1067: try/catch in timer does not prevent it from being stoppedJan Edmund Lazo2018-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Using try/catch in timer does not prevent it from being stopped. Solution: Reset the exception context and use did_emsg instead of called_emsg. https://github.com/vim/vim/commit/e723c42836d971180d1bf9f98916966c5543fff1
| * | | vim-patch:8.0.0670: can't use input() in a timer callbackJan Edmund Lazo2018-10-15
| | |/ | |/| | | | | | | | | | | | | | | | Problem: Can't use input() in a timer callback. (Cosmin Popescu) Solution: Reset vgetc_busy and set timer_busy. (Ozaki Kiichi, closes vim/vim#1790, closes vim/vim#1129) https://github.com/vim/vim/commit/1e8e14552e0cc8881411eb8fbe39a654dae42554
* | | Merge pull request #6930 from bfredl/expectfixBjörn Linse2018-10-16
|\ \ \ | |/ / |/| | tests: detect and fix fragile sceen tests, and mark intentional unchanged expect():s
| * | tests: improve robustness of immediate successes in screen testsBjörn Linse2018-10-15
|/ /
* | vim-patch:8.1.0476: memory leaks in test_escaped_glob (#9127)Jan Edmund Lazo2018-10-14
| | | | | | | | | | Problem: Memory leaks in test_escaped_glob. Solution: Avoid failure when running the shell, use the sandbox. https://github.com/vim/vim/commit/a2aad028305c306ecf33e0fd720fe1ed98596371
* | Merge pull request #9123 from jamessan/unibilium-parsing-fixJames McCoy2018-10-13
|\ \ | |/ |/| third-party/unibilium: Fix parsing of extended capability entries
| * third-party/unibilium: Fix parsing of extended capability entriesJames McCoy2018-10-13
|/ | | | | | | | | | | | | In the 20180331 release, the format was slightly changed: > 20180331 > + improve terminfo write/read by modifying the fourth item of the > extended header to denote the number of valid strings in the extended > string table (prompted by a comment in unibilium's sources). Since the number of valid string capabilities is not necessarily the same as extstrslen, it's not possible to sanity check the total number of items up front anymore.
* Merge #9095 'CI/travis/macOS: fix missing pip3'Justin M. Keyes2018-10-13
|\
| * CI/travis/macOS: silence non-error messages from homebrewJustin M. Keyes2018-10-13
| | | | | | | | Reduces the log size by 11% (1100/9670 lines).
| * CI/travis/macOS: use "sudo rm" to remove coresJustin M. Keyes2018-10-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After bumping Travis macOS to 10.13, it now hangs at: + check_core_dumps --delete quiet + local del= + test --delete = --delete + del=1 + shift + local app=quiet + test osx = osx ++ find /cores/ -type f -print + local 'cores=/cores//core.554 /cores//core.641 /cores//core.801' + test -z '/cores//core.554 /cores//core.641 /cores//core.801' + local core + for core in '$cores' + test 1 = 1 + print_core quiet /cores//core.554 + local app=quiet + local core=/cores//core.554 + test quiet = quiet + echo 'Found core /cores//core.554' Found core /cores//core.554 + return 0 + rm /cores//core.554 override r-------- root/admin for /cores//core.554? The cores are always present on the Travis macOS 10.13 image! Hilarious.
| * test: adjust timer testsJustin M. Keyes2018-10-13
| | | | | | | | | | Timer tests are less reliable on Travis CI macOS 10.12 (most egregious). Also somewhat on 10.13.
| * CI/travis/macOS: fix missing pip3Justin M. Keyes2018-10-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | homebrew or Travis changed something, now `pip3` isn't in $PATH. `ls /usr/local/opt/python/libexec/bin` confirmed this, no matter what brew reinstall/relink/upgrade are used. Bumping the macOS image to 10.12 or 10.13 makes the problem go away. ==> Processing gcc49 formula rename to gcc@4.9 ==> Unlinking gcc49 ==> Moving gcc49 versions to /usr/local/Cellar/gcc@4.9 ==> Relinking gcc@4.9 Warning: gcc@4.9 is outdated! To avoid broken installations, as soon as possible please run: brew upgrade Or, if you're OK with a less reliable fix: brew upgrade gcc@4.9 python info: Python 2.7.12 Python 2.7.12 ci/before_install.sh: line 18: python3: command not found pip 8.1.2 from /usr/local/lib/python2.7/site-packages (python 2.7) pip 8.1.2 from /usr/local/lib/python2.7/site-packages (python 2.7) ci/before_install.sh: line 21: pip3: command not found pyenv versions: * system (set by /Users/travis/.pyenv/version) Upgrade Python 3. To restore the stashed changes to /usr/local/Homebrew run: 'cd /usr/local/Homebrew && git stash pop' ==> Caveats Python has been installed as /usr/local/bin/python3 Unversioned symlinks `python`, `python-config`, `pip` etc. pointing to `python3`, `python3-config`, `pip3` etc., respectively, have been installed into /usr/local/opt/python/libexec/bin If you need Homebrew's Python 2.7 run brew install python@2 Pip, setuptools, and wheel have been installed. To update them run pip3 install --upgrade pip setuptools wheel You can install Python packages with pip3 install <package> They will install into the site-package directory /usr/local/lib/python3.7/site-packages See: https://docs.brew.sh/Homebrew-and-Python ==> Summary º /usr/local/Cellar/python/3.7.0: 8,864 files, 153.8MB, built in 6 minutes 32 seconds ... Upgrade Python 3 pip. ci/before_install.sh: line 30: pip3: command not found travis_time:end:0d23f522:start=1538818824750644000,finish=1538819451424021000,duration=626673377000 The command "ci/before_install.sh" failed and exited with 127 during . Your build has been stopped. /Users/travis/.travis/job_stages: line 373: shell_session_update: command not found ==> Processing gcc49 formula rename to gcc@4.9 ==> Unlinking gcc49 ==> Moving gcc49 versions to /usr/local/Cellar/gcc@4.9 ==> Relinking gcc@4.9 Warning: gcc@4.9 is outdated! To avoid broken installations, as soon as possible please run: brew upgrade Or, if you're OK with a less reliable fix: brew upgrade gcc@4.9 python info: Python 2.7.12 Python 2.7.12 ci/before_install.sh: line 18: python3: command not found pip 8.1.2 from /usr/local/lib/python2.7/site-packages (python 2.7) pip 8.1.2 from /usr/local/lib/python2.7/site-packages (python 2.7) ci/before_install.sh: line 21: pip3: command not found pyenv versions: * system (set by /Users/travis/.pyenv/version) Upgrade Python 3. To restore the stashed changes to /usr/local/Homebrew run: 'cd /usr/local/Homebrew && git stash pop' ==> Caveats Python has been installed as /usr/local/bin/python3 Unversioned symlinks `python`, `python-config`, `pip` etc. pointing to `python3`, `python3-config`, `pip3` etc., respectively, have been installed into /usr/local/opt/python/libexec/bin If you need Homebrew's Python 2.7 run brew install python@2 Pip, setuptools, and wheel have been installed. To update them run pip3 install --upgrade pip setuptools wheel You can install Python packages with pip3 install <package> They will install into the site-package directory /usr/local/lib/python3.7/site-packages See: https://docs.brew.sh/Homebrew-and-Python ==> Summary º /usr/local/Cellar/python/3.7.0: 8,864 files, 153.8MB, built in 6 minutes 32 seconds ... Upgrade Python 3 pip. ci/before_install.sh: line 30: pip3: command not found travis_time:end:0d23f522:start=1538818824750644000,finish=1538819451424021000,duration=626673377000 The command "ci/before_install.sh" failed and exited with 127 during . Your build has been stopped. /Users/travis/.travis/job_stages: line 373: shell_session_update: command not found
* | Merge #9122 from janlazo/vim-8.1.0473Justin M. Keyes2018-10-13
|\ \ | |/ |/|
| * memline: process_still_running is boolJan Edmund Lazo2018-10-13
| |
generated by cgit (git 2.34.1) at 2025-06-26 02:04:28 +0000