aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
| * | | | eval: Fix PVS/V547: ufunc_T is actually an incomplete typeZyX2018-04-10
| | | | |
| * | | | edit: Fix PVS/V560: remove always true/false checksZyX2018-04-10
| | | | |
| * | | | diff: Fix PVS/V547: remove no longer needed OOM handlerZyX2018-04-10
| | | | |
| * | | | eval/decode: Silence PVS/V547: code written for 32-bit integersZyX2018-04-09
| | | | |
| * | | | charset: Fix PVS/V560: remove condition which was already checkedZyX2018-04-09
| | | | |
| * | | | charset: Silence PVS/V785: remove switch()ZyX2018-04-09
| | | | | | | | | | | | | | | | | | | | No idea why it thinks that pre is constant expression, but switch() may be removed.
| * | | | event/loop: Silence PVS/V547: condition is false in case of no timeoutZyX2018-04-09
| | | | |
| * | | | buffer: Fix PVS/V560: condition was checked three lines aboveZyX2018-04-09
| | | | |
| * | | | buffer: Fix PVS/V547: base is never set to octalZyX2018-04-09
| | | | |
| * | | | charset: Fix transchar() with multibyte charactersZyX2018-04-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It appears that transchar() was working under assumption that `transchar_nonprint()` may be used for multibyte characters while its documentation stated exact opposite. It was not actually untrue though, except that longer buffer would be needed then the one stated in documentation. But it is false now with assert().
| * | | | buffer: PVS/V557: Refactor maketitle()ZyX2018-04-09
| | | | |
| * | | | os/env: Refactor home_replace() to the new style and to return lengthZyX2018-04-09
| | | | |
| * | | | charset,*: Refactor transstr()ZyX2018-04-09
| | | | |
| * | | | memory: Fix documentation of some string copying functionsZyX2018-04-09
| | | | |
| * | | | buffer: Beautify code a bitZyX2018-04-09
| | | | |
| * | | | eval/typval_encode: Silence PVS/V501,V547,V779ZyX2018-04-02
| | | | | | | | | | | | | | | These kinds of warnings are inevitable for generic macros.
| * | | | api/buffer: Fix PVS/V547: use correct border for lnumZyX2018-04-02
| | | | | | | | | | | | | | | | | | | | | | | | | Should actually be silencing that for the sake of the case when `long` is actually not 64-bit. But it appears that Vim had already defined maximal line number. And even declared that exact value invalid, so no need in silencing.
| * | | | quickfix: Fix PVS/V560: remove duplicate conditionZyX2018-04-02
| | | | | | | | | | | | | | | Condition was checked in surrounding if().
* | | | | win: open child stdio handles in overlapped-mode (#8113)Björn Linse2018-04-25
| | | | | | | | | | | | | | | This will be used e.g. by the python client for native asyncio support
* | | | | Merge #8304 "default to 'nofsync'"Justin M. Keyes2018-04-24
|\ \ \ \ \
| * | | | | API: nvim__stats()Justin M. Keyes2018-04-24
| | | | | | | | | | | | | | | | | | | | | | | | Use it to verify fsync() behavior.
| * | | | | lintJustin M. Keyes2018-04-21
| | | | | |
| * | | | | defaults: disable 'fsync'Justin M. Keyes2018-04-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ref #6725 fsync() is very slow on some systems. And since the parent commit, Nvim is smarter about flushing files at certain times (e.g. CursorHold), regardless of whether 'fsync' is enabled. So it's less risky to disable 'fsync'. Profiling showed slow (2-4s) :write and :quit caused by fsync(): :quit shada_write_file(NULL, false); :write + fsync 0 0x00007f72da567b2d in fsync () at ../sysdeps/unix/syscall-template.S:84 1 0x0000000000638970 in uv__fs_fsync (req=<optimized out>) at /home/vagrant/neovim/.deps/build/src/libuv/src/unix/fs.c:150 2 uv__fs_work (w=<optimized out>) at /home/vagrant/neovim/.deps/build/src/libuv/src/unix/fs.c:953 3 0x0000000000639a70 in uv_fs_fsync (loop=<optimized out>, req=<optimized out>, file=41, cb=0x7f72da567b2d <fsync+45>) at /home/vagrant/neovim/.deps/build/src/libuv/src/unix/fs.c:1094 4 0x0000000000573694 in os_fsync (fd=41) at ../src/nvim/os/fs.c:631 5 0x00000000004ec9dc in buf_write (buf=<optimized out>, fname=<optimized out>, sfname=<optimized out>, start=1, end=1997, eap=0x7fffc864c570, append=<optimized out>, forceit=<optimized out>, reset_changed=<optimized out>, filtering=<optimized out>) at ../src/nvim/fileio.c:3387 6 0x00000000004b44ff in do_write (eap=0x7fffc864c570) at ../src/nvim/ex_cmds.c:1745 ... :write + nofsync 0 0x00007f72da567b2d in fsync () at ../sysdeps/unix/syscall-template.S:84 1 0x0000000000638970 in uv__fs_fsync (req=<optimized out>) at /home/vagrant/neovim/.deps/build/src/libuv/src/unix/fs.c:150 2 uv__fs_work (w=<optimized out>) at /home/vagrant/neovim/.deps/build/src/libuv/src/unix/fs.c:953 3 0x0000000000639a70 in uv_fs_fsync (loop=<optimized out>, req=<optimized out>, file=36, cb=0x7f72da567b2d <fsync+45>) at /home/vagrant/neovim/.deps/build/src/libuv/src/unix/fs.c:1094 4 0x0000000000573694 in os_fsync (fd=36) at ../src/nvim/os/fs.c:631 5 0x0000000000528f5a in mf_sync (mfp=0x7f72d8968d00, flags=5) at ../src/nvim/memfile.c:466 6 0x000000000052d569 in ml_preserve (buf=0x7f72d890f000, message=0) at ../src/nvim/memline.c:1659 7 0x00000000004ebadf in buf_write (buf=<optimized out>, fname=<optimized out>, sfname=<optimized out>, start=1, end=1997, eap=0x7fffc864c570, append=<optimized out>, forceit=<optimized out>, reset_changed=<optimized out>, filtering=<optimized out>) at ../src/nvim/fileio.c:3071 8 0x00000000004b44ff in do_write (eap=0x7fffc864c570) at ../src/nvim/ex_cmds.c:1745 ...
| * | | | | IO: let 'fsync' option control more casesJustin M. Keyes2018-04-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Vim has the 'swapsync' option which we removed in 62d137ce0969. Instead let 'fsync' control swapfile-fsync. These cases ALWAYS force fsync (ignoring 'fsync' option): - Idle (CursorHold). - Exit caused by deadly signal. - SIGPWR signal. - Explicit :preserve command.
| * | | | | IO: shada should respect 'fsync' optionJustin M. Keyes2018-04-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | shada_write_file() is called on exit (:quit and friends), this can be very slow. Note: AFAICT Vim (do_viminfo()) does not appear to fsync() viminfo.
* | | | | | tui/input.c: add support for mouse release events in urxvt (#8309)symphorien2018-04-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some terminals don't report which buttons are involved in some mouse events. For example, the urxvt protocol (http://www.huge-man-linux.net/man7/urxvt.html section "Mouse reporting") does not report which button has been released. In this case libtermkey reports button 0 (http://www.leonerd.org.uk/code/libtermkey/doc/termkey_interpret_mouse.3.html) Up to now, forward_mouse_event did not handle button==0. On press events there is not much we can do, and we keep the current behavior which is dropping the event. But on drag-and-release events we can compensate by remembering the last button pressed. fixes #3182 for urxvt fixes #5400
* | | | | | inccommand: pause :terminal redraws (#8307)Justin M. Keyes2018-04-22
| | | | | | | | | | | | | | | | | | fix #5584
* | | | | | inccommand: do not execute trailing commands #8256Nimit Bhardwaj2018-04-21
|/ / / / / | | | | | | | | | | | | | | | fix #7494
* | | | | terminal: do not call redraw_buf_later() (#8306)Justin M. Keyes2018-04-21
| | | | | | | | | | | | | | | fixes #8290
* | | | | ui_events: correct wrong argument orderBjörn Linse2018-04-17
| | | | |
* | | | | Merge #8276 'startup: Make -s - read from stdin'Justin M. Keyes2018-04-17
|\ \ \ \ \
| * | | | | win: Fix reading from stdinb-r-o-c-k2018-04-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Reading from stdin on Windows is fixed in the same way as it was in #8267. * The file_read function was returning without filling the destination buffer when it was called with a non-blocking file descriptor.
| * | | | | Merge branch 'master' into s-dash-stdinb-r-o-c-k2018-04-14
| |\ \ \ \ \
| * | | | | | getchar: Move REMAP_… values into a enumZyX2017-12-03
| | | | | | |
| * | | | | | Merge branch 'master' into s-dash-stdinZyX2017-12-03
| |\ \ \ \ \ \
| * | | | | | | main: Translate full -s error message, not part of itZyX2017-03-19
| | | | | | | |
| * | | | | | | os/fileio: Fix QB failureZyX2017-03-19
| | | | | | | |
| * | | | | | | *: Fix linter errorsZyX2017-03-19
| | | | | | | |
| * | | | | | | fileio,main: Do not restart syscall at EAGAIN when reading for -sZyX2017-03-19
| | | | | | | |
| * | | | | | | getchar: Use fileio instead of fdopenZyX2017-03-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: as fileio is cached and reads blocks this is going to wait until either EOF or reading enough characters to fill rbuffer. This is not good when reading user input from stdin as script.
| * | | | | | | main: Temporary fix assertion errorZyX2017-03-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This variant uses `fdopen()` which is not standard, but it fixes problem on my system. In next commit `scriptin` will use `FileDescriptor*` from os/fileio in place of `FILE*`.
| * | | | | | | main: Make `-s -` read from stdinZyX2017-03-19
| | | | | | | |
* | | | | | | | startup: ignore -XJustin M. Keyes2018-04-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | closes #8285
* | | | | | | | terminal: resize to the max dimensions (#8249)Andrew Pyatkov2018-04-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | closes #8096
* | | | | | | | job-control: children_kill_cb(): do not check elapsed timeJustin M. Keyes2018-04-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. Don't check elapsed time in children_kill_cb(), it's already implied by the start-time of the timer itself. 2. Restart timer from children_kill_cb() for PTY jobs, to send SIGKILL after SIGTERM. There is an edge case where SIGKILL might follow SIGTERM too quickly, if jobstop() is called near the 2-second timer window. But this edge case is not worth code complication.
* | | | | | | | job-control: one-shot timer instead of repeatingJustin M. Keyes2018-04-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before f31c26f1afb5 the timer was used to try SIGTERM *and* SIGKILL, so a repeating timer was needed. After f31c26f1afb5 process_stop() sends SIGTERM immediately, and the timer only sends SIGKILL. So we don't need a repeating timer. - Simplifies the logic: don't need to call uv_timer_stop() explicitly. - Avoids a problem: if process_stop() is called more than once in the 2-second window, the first on_process_exit() would call uv_timer_stop() which stops the timer for all stopped processes.
* | | | | | | | job-control: mitigate process-kill raceJustin M. Keyes2018-04-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | children_kill_cb() is racey. One obvious problem is that process_close_handles() is *queued* by on_process_exit(), so when children_kill_cb() is invoked, the dead process might still be in the `loop->children` list. If the OS already reclaimed the dead PID, Nvim may try to SIGKILL it. Avoid that by checking `proc->status`. Vim doesn't have this problem because it doesn't attempt to kill processes that ignored SIGTERM after a timeout. closes #8269
* | | | | | | | loop: remove `children_stop_requests`Justin M. Keyes2018-04-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It serves no purpose because process_stop() is already guarded by `proc->stopped_time`.
* | | | | | | | events: VimSuspend, VimResume #8280geekodour2018-04-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | closes #3648 ref #5959
* | | | | | | | Merge #6272 'stdpath()'Justin M. Keyes2018-04-15
|\ \ \ \ \ \ \ \
generated by cgit (git 2.34.1) at 2025-07-21 15:02:11 +0000