aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* vim-patch:7.4.1486James McCoy2016-07-08
| | | | | | | Problem: ":loadplugin" is not optimal, some people find it confusing. Solution: Only use ":packadd" with an optional "!". https://github.com/vim/vim/commit/f3654827368e6204608036353a0360e9e7c21e02
* vim-patch:7.4.1480James McCoy2016-07-08
| | | | | | | Problem: Cannot add a pack direcory without loading a plugin. Solution: Add the :packadd command. https://github.com/vim/vim/commit/91715873d19a1859c08eeded7848113596e2f2bd
* vim-patch:7.4.1479James McCoy2016-07-08
| | | | | | | Problem: No testfor ":loadplugin". Solution: Add a test. Fix how option is being set. https://github.com/vim/vim/commit/863c1a9079fa340d663ccafb011729a29186d73e
* vim-patch:7.4.1478James McCoy2016-07-08
| | | | | | | Problem: ":loadplugin" doesn't take care of ftdetect files. Solution: Also load ftdetect scripts when appropriate. https://github.com/vim/vim/commit/1bdd42627d619258d0e847f217cfc1c2795f1ac5
* vim-patch:7.4.1396James McCoy2016-07-08
| | | | | | | Problem: Compiler warnings for conversions. Solution: Add type cast. https://github.com/vim/vim/commit/1daae446e58fd90f98c51ff3af8f54bfa5197751
* vim-patch:7.4.1388James McCoy2016-07-08
| | | | | | | Problem: Compiler warning. (Cesar Romani) Solution: Initialize variable. https://github.com/vim/vim/commit/bdcd75275002c3b74015bb9bc0a01b13bb6107d4
* vim-patch:7.4.1384James McCoy2016-07-08
| | | | | | | Problem: It is not easy to use a set of plugins and their dependencies. Solution: Add packages, ":loadopt", 'packpath'. https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
* vim-patch:7.4.1111 (#5004)prollings2016-07-06
| | | | | | Problem: test_expand fails on MS-Windows. Solution: Always use forward slashes. Remove references to test27. https://github.com/vim/vim/commit/f60b796fa9870bdfc4cdeb91653bac041916077d
* os/fs: Rename os_file_exists to os_path_exists (#4973)Daniel Xu2016-07-06
| | | | Because the old name did not indicate that the function would return true on directories as well.
* tui: Assume 256 colors in most cases.Justin M. Keyes2016-07-03
| | | | | | | | Assume 256 colors if: - $TERM contains "xterm" or "256" - $COLORTERM contains "256" Closes #2912
* options: Default t_Co to 256.Justin M. Keyes2016-07-02
| | | | | | | | This commit doesn't change any behavior, only moves the init out of main.c We _could_ move some initialization from tui.c:terminfo_start to an earlier phase, in order to avoid mis-reporting 't_Co' during startup. But this will be messy, and gains very little: TERM=linux works "good enough" as long as we correct t_Co in tui.c:terminfo_start (c5b02d5a7).
* options: Set 't_Co' from unibilium + fix_terminfo.Mateusz Czaplinski2016-07-02
| | | | | | | | | | | | | | | | | Closes #3428 References #4999 The Linux "virtual consoles" available on Alt-F1...Alt-F7 (i.e. tty1-tty7) support only 8 colors (actually, it's 16 colors when counted together with "bold/bright" attribute) and 8 background colors (those in some cases can be upped to 16 too, by using "blink" attribute - but this might be more risky, in case some legacy consoles really show it as blinking? I'm not sure about that.) This limit is buried deep in kernel sources for default tty drivers. Trying to use the Neovim's default 256 colors in this case gives totally bad colors, breaking all color schemes and sometimes rendering parts of the text invisible. A simple change enables code paths for handling 8/16 colors, which are still present in Neovim codebase.
* vim-patch:7.4.1121 (#4989)prollings2016-07-02
| | | | | | | Problem: test_expand leaves files behind. Solution: Edit another file before deleting, otherwise the swap file remains. https://github.com/vim/vim/commit/08b270a8a4544be9a7fecce311834fde2b457634
* vim-patch:7.4.1716Marco Hinz2016-07-01
| | | | | | | Problem: 'autochdir' doesn't work for the first file. (Rob Hoelz) Solution: Call DO_AUTOCHDIR after startup. (Christian Brabandt) https://github.com/vim/vim/commit/baec5c1768098f9dd867b465aaabfdfb294f10c2
* Merge pull request #4880 from bfredl/zerotimerBjörn Linse2016-07-01
|\ | | | | make timers work correctly when timeout or repeat is zero
| * timers: make repeat=0 work one-shot (consistent with vim)Björn Linse2016-06-29
| |
| * timers: make timers work with zero timeoutBjörn Linse2016-06-29
| |
* | Fix regression of :drop introduced in 1a91000Michael Budde2016-07-01
| | | | | | | | | | | | | | | | A single line was deleted from `ex_drop()` in 1a91000 when fixing clint warnings causing the `:drop` command to not work correctly if the buffer is not already open in a window. Fixes #4981
* | vim-patch:7.4.1136Patrick2016-06-30
|/ | | | | | | | Problem: Wrong argument to assert_exception() causes a crash. (reported by Coverity) Solution: Check for NULL pointer. Add a test. https://github.com/vim/vim/commit/da5dcd936656f524dd0ae7cb2685245f07f5720f
* [RFC] Fix #4979: Trigger TabNewEntered also with <CTRL-W>TDimitri Merejkowsky2016-06-28
| | | | Original patch by @fmoralesc
* Update version.c (#4974)KillTheMule2016-06-27
| | | | | | | | | Only update some entries that are already in `version.c`. Mercilessly stolen from https://github.com/neovim/neovim/pull/4634. At least one possible contributor got confused by it not being as-up-do-date-as-it-coul-be(tm). We shouldn't have that. 1005, 1010: :smile 1039: small Build 1058, 1073, 1079, 1097: alloc 1555, 1556, 1573: Makefile 1560, 1579: channel
* Merge #4646 from oni-link/fix.issue.4569.3Justin M. Keyes2016-06-26
|\ | | | | Fix for missing output (#4569, ...)
| * fixup2: process.c: Prevent data loss for process output streamsoni-link2016-05-15
| | | | | | | | | | | | | | | | The only data loss should be, if a process forked a child that keeps sending data after the parent terminated. While not in teardown mode we could keep reading child data, but then `:!cmd` would block after `cmd` exited. In teardown mode we want to exit nvim so we cannot keep reading child data.
| * fixup: process.c: Prevent data loss for process output streamsoni-link2016-05-15
| | | | | | | | | | | | * Get system buffer size for upper data limit. Otherwise data loss if this buffer is too big. * Test whether teardown needs special handling.
| * shell.c: Fix missing outputoni-link2016-05-15
| | | | | | | | | | | | | | | | | | | | | | | | The whole stream buffer is now put on screen at once instead of only data up to the last newline. This has some advantages: * RBuffer cannot wrap around, so we never forget to output second half of the buffer. * Stream data is not delayed anymore, because we don't have to wait for a newline. This works by remembering the last used screen column.
| * process.c: Prevent data loss for process output streamsoni-link2016-05-15
| | | | | | | | | | For a terminating process, it's output streams could be closed, before all data is read.
* | version: State that 1960 was includedZyX2016-06-26
| |
* | Merge #4965 from justinmk/fixup4453Justin M. Keyes2016-06-25
|\ \ | | | | | | ex_cmds2.c: lint
| * | ex_cmds2.c: cleanupJustin M. Keyes2016-06-25
| | |
| * | ex_cmds2.c:style: Silence all clint warningsJ Phani Mahesh2016-06-24
| | |
* | | option: Make all pointers in set_string_option constantZyX2016-06-24
| | |
* | | *: Fix linter errorsZyX2016-06-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | Also adds one exception to linter rules: typedef struct { kvec_t(Object) stack; } EncodedData; is completely valid (from the style guide point of view) code.
* | | kvec: Do not bother with making capacity a power of 2ZyX2016-06-24
| | | | | | | | | This avoids gcc warnings about undefined behaviour.
* | | msgpack_rpc: Fix crash in log_server_msgZyX2016-06-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It appears that used msgpack library is not able to parse back message created by msgpack_rpc_from_object() if nesting level is too high, so log_server_msg now cares about msgpack_unpack_next() return value. Also error message from server_notifications_spec.lua is not readable if something is wrong (though at least now it does not crash when parsing deeply nested structures). log_server_msg() in the test reports [msgpack-rpc] nvim -> client(1) [error] "parse error"
* | | option: Handle NULL string in set_option_valueZyX2016-06-24
| | |
* | | eval: Also make clear_tv non-recursiveZyX2016-06-24
| | |
* | | kvec,typval_encode: Add new vector: the one with preallocated arrayZyX2016-06-24
| | |
* | | msgpack_rpc: Also make msgpack_from_*/msgpack_to_* functions not recurZyX2016-06-24
| | | | | | | | | | | | | | | | | | This removes some stack overflows in new test regarding deeply nested variables. Now in place of crashing vim_to_object/msgpack_rpc_from_object/etc it crashes clear_tv with stack overflow.
* | | api/helpers: Use typval_encode.h for vim_to_objectZyX2016-06-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This ought to prevent stack overflow, but I do not see this actually working: *lua* code crashes with stack overflow when trying to deserialize msgpack from Neovim, Neovim is fine even if nesting level is increased 100x (though test becomes very slow); not sure how recursive function may survive this. So it looks like there are currently only two positive effects: 1. NULL lists are returned as empty (#4596). 2. Functional tests are slightly more fast. Very slightly. Checked for Release build for test/functional/eval tests because benchmarking of debug mode is not very useful.
* | | os/fileio: Use readv oftenZyX2016-06-24
| | |
* | | *: Satisfy linter (newest type casts rule)ZyX2016-06-24
| | |
* | | file: Move src/nvim/file.* to src/nvim/os/fileio.*ZyX2016-06-24
| | |
* | | unittests: Add tests for file.cZyX2016-06-24
| | | | | | | | | | | | Also fixes some errors found.
* | | shada: Do not forget to close ShaDa readerZyX2016-06-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | Previously there was file descriptor leak, not detected by sanitizers. Now it is file descriptor leak with a small memory leak which is detected by ASAN what fails one of the tests (actually, “ShaDa support code leaves .tmp.z in-place when there is error in original ShaDa and it has .tmp.a … .tmp.x”, but error is reported at the next test because leaks are not detected until Neovim exit and Neovim exit happens when clear()/reset() is called which happens in before_each only).
* | | file: Use own constants, do not rely on fcntl.hZyX2016-06-23
| | | | | | | | | | | | | | | | | | | | | One of the reasons is that O_RDONLY is zero, which makes checking whether file is opened read- or write-only harder. It is not guaranteed that on other system O_WRONLY will not be zero (e.g. because file can only be opened in read-write mode).
* | | file: Add buffered reading and writingZyX2016-06-23
| | | | | | | | | | | | Still no busted tests. Not tested without HAVE_PREADV.
* | | file,os/fs,shada: Separate opening, closing, writing and reading filesZyX2016-06-23
|/ / | | | | | | | | | | | | | | Moves low-level functions handling to os/fs.c. Adds file.c with a proxy interface. Target: while leaving syscalls handling is os.c (partially handled by libuv), add buffering for reading and writing to file.c.
* | cmake: remove unused includes (#4947)Nicolai Skogheim2016-06-22
| |
* | lintJames McCoy2016-06-22
| |
* | vim-patch:7.4.1592James McCoy2016-06-22
| | | | | | | | | | | | | | Problem: Quickfix code using memory after being freed. (Dominique Pelle) Solution: Detect that the window was closed. (Hirohito Higashi) https://github.com/vim/vim/commit/0899d698030ec076eb26352cda1ea334ab0819d9
generated by cgit (git 2.34.1) at 2025-06-06 12:58:20 +0000