aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* clipboard: remove start_batch_changes() in redir_write()Justin M. Keyes2017-08-20
| | | | | | | | | | | | | | | | | | | | | | | | start_batch_changes() doesn't avoid invoking the clipboard once-per-line, because the loop is actually in ex_echo(), which calls redir_write() for each message. But we've already entered start_batch_changes() by then, so that was never the problem. redir_write at /home/vagrant/old.neovim/build/../src/nvim/message.c:2523 msg_puts_attr_len at /home/vagrant/old.neovim/build/../src/nvim/message.c:1600 msg_outtrans_len_attr at /home/vagrant/old.neovim/build/../src/nvim/message.c:1221 ex_echo at /home/vagrant/old.neovim/build/../src/nvim/eval.c:19433 do_one_cmd at /home/vagrant/old.neovim/build/../src/nvim/ex_docmd.c:2242 Trying to defer _explicit_ clipboard updates is difficult. :redir @+ | silent echo system('cat foo') | redir END is essentially equivalent to: for l in readfile('foo') let @+ .= l endfor We cannot make judgements about when to ignore a script's bad decisions. start_batch_changes() only works around the case of clipboard=unnamed, i.e. _implicit_ clipboard updates (`:g/foo/d`). Not explicit assignment.
* clipboard: avoid error flood during :redirJustin M. Keyes2017-08-20
| | | | | | | | | | | | | | | | | | redir_write(): - This is a "batch" operation which was not yet covered by start_batch_changes() adjust_clipboard_name(): - msg() and friends during :redir will, of course, cause redir_write() to try to capture that message, which causes recursion. - EMSG() here is trouble: if it interrupts :redir it is a mess. Rather than deal with the mess, show a non-error message. closes #7182 closes #7184 closes #7183 ref #6048 ref #7032
* doc/api: nvim_out_write() and friendsJustin M. Keyes2017-08-18
| | | | References #7178
* version: tweak layout, docJustin M. Keyes2017-08-18
|
* intro: remove byline #6984Justin M. Keyes2017-08-18
|
* nvim -h: omit special-case optionsJustin M. Keyes2017-08-18
| | | | | | Group some options, and sort them alphabetically. `nvim -h` should fit on one (smallish) screen. Uncommon options don't need to be here, they live in the :help.
* Merge #7007 'Windows :terminal'Justin M. Keyes2017-08-16
|\ | | | | | | References #6383 Closes #4748
| * single-includes: ignore os/pty_process_win.hJustin M. Keyes2017-08-16
| |
| * pty_process_win: avoid quoting for cmd.exeerw72017-08-16
| |
| * win/pty: log errorserw72017-08-16
| |
| * win/pyt: cleanuperw72017-08-16
| |
| * win/pty: quote_cmd_arg(): check boundserw72017-08-16
| |
| * win/pty: jobstart, jobstop: fix null-pointer dereferenceerw72017-08-16
| | | | | | | | | | | | | | - Make sure that proc->in is not NULL, because nvim crashed when starting a job with pty. - Make sure that proc->out is not NULL, because nvim crashed when stopping a job opened with pty.
| * win: support :terminalerw72017-08-16
| |
| * win/install: winpty-agent.exeRui Abreu Ferreira2017-08-16
| |
| * win: integrate winpty (WIP)Ryan Prichard2017-08-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Handling of process exit is still broken. It detects the moment when the child process exits, then quickly stops polling for process output. It should continue polling for output until the agent has scraped all of the process' output. This problem is easy to notice by running a command like "dir && exit", but even typing "exit<ENTER>" can manifest the problem -- the "t" might not appear. winpty's Cygwin adapter handles shutdown by waiting for the agent to close the CONOUT pipe, which it does after it has scraped the child's last output. AFAIK, neovim doesn't do anything interesting when winpty closes the CONOUT pipe.
* | Merge pull request #7052 from ckelsel/vim-8.0.0044James McCoy2017-08-16
|\ \ | | | | | | vim-patch:8.0.0044
| * | vim-patch:8.0.0044ckelsel2017-08-16
| |/ | | | | | | | | | | | | | | Problem: In diff mode the cursor may end up below the last line, resulting in an ml_get error. Solution: Check the line to be valid. https://github.com/vim/vim/commit/025e3e0bafbc85cc4e365145af711edf99d0a90d
* | Merge pull request #7145 from ckelsel/vim-8.0.0174James McCoy2017-08-16
|\ \ | | | | | | vim-patch:8.0.0174
| * | vim-patch:8.0.0174ckelsel2017-08-10
| | | | | | | | | | | | | | | | | | | | | | | | Problem: For completion "locale -a" is executed on MS-Windows, even though it most likely won't work. Solution: Skip executing "locale -a" on MS-Windows. (Ken Takata) https://github.com/vim/vim/commit/b8f7bd68f6fdff51ca4db5b145dcde42ee7b804b
* | | vim-patch:8.0.0679Justin M. Keyes2017-08-16
| | | | | | | | | | | | | | | | | | | | | Problem: Using freed memory. Solution: Get the parent frame pointer earlier. https://github.com/vim/vim/commit/41cc038ff83498c589c7d25b3d2984145528eb92
* | | vim-patch:8.0.0678 closing a window does not trigger resizingJustin M. Keyes2017-08-16
| |/ |/| | | | | | | | | | | | | | | | | | | Closes #6748 Problem: When 'equalalways' is set and closing a window in a separate frame, not all window sizes are adjusted. (Glacambre) Solution: Resize all windows if the new current window is not in the same frame as the closed window. (closes vim/vim#1707) https://github.com/vim/vim/commit/8eeeba8c025ff844e6514c4a60cec11bf1fc1b35
* | Merge pull request #7168 from teto/fix_covertyJames McCoy2017-08-15
|\ \ | | | | | | Closes #7149
| * | coverty: solve  #7149Matthieu Coudron2017-08-15
| | |
* | | Merge #6364 'command-line color hook'Justin M. Keyes2017-08-16
|\ \ \ | |/ / |/| |
| * | ex_getln: Make error messages look betterZyX2017-08-14
| | |
| * | Merge branch 'master' into colored-cmdlineZyX2017-08-06
| |\ \
| * | | api/helpers: Fix typoZyX2017-08-06
| | | |
| * | | api/helpers: Clarify try_start() usageZyX2017-08-06
| | | |
| * | | Merge branch 'master' into colored-cmdlineZyX2017-07-31
| |\ \ \
| * \ \ \ Merge branch 'master' into colored-cmdlineZyX2017-07-31
| |\ \ \ \
| * | | | | ex_getln: Cache highlight callback calling resultsZyX2017-07-26
| | | | | |
| * | | | | message: Only require second (format) argument to be not NULLZyX2017-07-26
| | | | | |
| * | | | | ex_getln: Avoid GCC “unused variable” warning from QBZyX2017-07-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 17:25:45,363 WARN - /home/quickbuild/buildagent/workspace/root/neovim/pull-requests-automated/src/nvim/ex_getln.c: In function ‘color_cmdline’: 17:25:45,363 WARN - /home/quickbuild/buildagent/workspace/root/neovim/pull-requests-automated/src/nvim/ex_getln.c:2335:8: error: variable ‘printed_errmsg’ set but not used [-Werror=unused-but-set-variable] 17:25:45,363 WARN - bool printed_errmsg = false; 17:25:45,363 WARN - ^ 17:25:45,399 WARN - cc1: all warnings being treated as errors
| * | | | | *: Fix clint errorsZyX2017-07-18
| | | | | |
| * | | | | ex_getln: Check prev_prompt_errors before running redrawcmdlineZyX2017-07-18
| | | | | | | | | | | | | | | | | | | | | | | | Otherwise there will be infinite recursion and shortly a crash. Running redrawcmdline recursively occurs under color_cmdline_error label.
| * | | | | api helpers: Also save and restore did_emsgZyX2017-07-18
| | | | | |
| * | | | | ex_getln: Replace global with entry in save_cclineZyX2017-07-17
| | | | | |
| * | | | | ex_getln: Do not do useless try_enter/try_leave callsZyX2017-07-17
| | | | | | | | | | | | | | | | | | | | | | | | These are actually needed for two modes only. And even for these modes they should eventually go away.
| * | | | | ex_getln: Do not goto color_cmdline_end without first cleaning upZyX2017-07-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The issue with debug mode was actually not cleaning up after `try_enter`: location `&tstate` was pointing to got invalidated and received some “garbage” (actually, values that got stored on the stack afterwards). But pointer to that garbage was still stored in `msg_list`, so next attempt to check it resulted in a crash.
| * | | | | api helpers: Save/restore more values in try_enter/try_leaveZyX2017-07-16
| | | | | | | | | | | | | | | | | | | | | | | | This fixes memory leak reported by ASAN. This also somehow fixes test40, though I have no idea why except that that test yields memory leak report.
| * | | | | oldtests: Use $(TOOL) in place of $(VALGRIND)ZyX2017-07-16
| | | | | |
| * | | | | Merge branch 'master' into colored-cmdlineZyX2017-07-15
| |\ \ \ \ \
| * | | | | | ex_getln: Save and restore try stateZyX2017-07-01
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: when processing cycle such as :for pat in [' \ze*', ' \zs*'] : try : let l = matchlist('x x', pat) : $put ='E888 NOT detected for ' . pat : catch : $put ='E888 detected for ' . pat : endtry :endfor `:let l = …` throwing an error causes this error to be caught after color_cmdline attempts to get callback for highlighting next line (the one with `$put = 'E888 NOT…`). Saving/restoring state prevents this from happening.
| * | | | | | ex_getln: Do not make <C-c> interrupt input() after interrupting hl cbZyX2017-06-28
| | | | | | |
| * | | | | | ex_getln: Fix indentZyX2017-06-28
| | | | | | |
| * | | | | | ex_getln: Make sure standard error reporting facility is not usedZyX2017-06-28
| | | | | | |
| * | | | | | ex_getln: Fix “echoerr msg not shown” problemZyX2017-06-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This also attempted to fix problem with cancelling input() on error by avoiding standard error printing facilities (assumed thrown error message is the problem), but with no luck so far.
| * | | | | | ex_getln: Call highlight callback inside :tryZyX2017-06-28
| | | | | | |
| * | | | | | ex_getln: Enable coloring for expression modeZyX2017-06-27
| | | | | | |
generated by cgit (git 2.34.1) at 2025-08-04 12:15:12 +0000