aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
...
* | clipboard: Always copy as plain text in Wayland #9737Tim Morgan2019-03-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `wl-copy` by default tries to determine the mime type of a copied bit of text. From the [readme](https://github.com/bugaevc/wl-clipboard): > wl-copy automatically infers the type of the copied content by running > xdg-mime(1) on it. So copying a Ruby script from Nvim may store it in the Wayland clipboard as mime-type `application/x-ruby`. This is a small reproduction without Nvim: $ cat test.rb #!/usr/bin/env ruby puts 'hello world' $ cat test.rb | wl-copy $ wl-paste --list-types application/x-ruby This commit fixes that by telling wl-copy that all text copied from Nvim has the mime type `text/plain`. $ cat test.rb | wl-copy --type text/plain $ wl-paste --list-types text/plain;charset=utf-8
* | Allow using internal popupmenu or ext_popupmenu for wildmenuBjörn Linse2019-03-16
|/ | | | | Deprecate ext_wildmenu. ext_popupmenu already contains more state (anchor position), and will allow further expansion (info about items).
* Merge pull request #9616 from chemzqm/completechangeBjörn Linse2019-03-16
|\ | | | | add MenuPopupChanged autocmd
| * autocmd: add MenuPopupChanged autocmdchemzqm2019-03-15
| | | | | | | | | | | | Update src/nvim/auevents.lua Co-Authored-By: chemzqm <chemzqm@gmail.com>
* | Merge #9728 from justinmk/autocmd-onceJustin M. Keyes2019-03-15
|\ \
| * | autocmd: rename: "++nested", "++once"Justin M. Keyes2019-03-14
| | | | | | | | | | | | | | | Based on feedback from upstream: https://github.com/vim/vim/pull/4100
* | | vim-patch:8.1.0728: avoid breaking after single space #9733Jan Edmund Lazo2019-03-15
|/ / | | | | | | | | Problem: Cannot avoid breaking after a single space. Solution: Add the 'p' flag to 'formatoptions'. (Tom Ryder) https://github.com/vim/vim/commit/c3c3158756ae074052b0db2a3e3a7ba192df5330
* | TextYankPost: add v:event["inclusive"] #9717Justin M. Keyes2019-03-13
| |
* | docs: adjust the generated nvim_open_win docsBjörn Linse2019-03-12
| | | | | | | | | | The format here is not meant to be ideal, just a backstop until auto-generation has been fixed.
* | docs: update generated API docsBjörn Linse2019-03-12
| |
* | docs: floating windows introductionBjörn Linse2019-03-12
| |
* | floats: add NormalFloat highlight and 'nonumber' defaultBjörn Linse2019-03-12
| |
* | autocmd: rename "once" => "-once" #9713Justin M. Keyes2019-03-11
| | | | | | | | | | | | | | - Rename "nested" to "-nested", but continue to support "nested" for backwards-compatibility. - Allow any order: "-once -nested" or "-nested -once". ref https://github.com/neovim/neovim/pull/9706#issuecomment-471295747
* | Dist: make icon a proper square (#9716)Marco Hinz2019-03-11
| | | | | | | | | | | | The canvas was resized from 128x104 to 128x128 and centered via Gimp and further optimized via optipng. Fixes https://github.com/neovim/neovim/issues/9715
* | autocmd: introduce "once" featureJustin M. Keyes2019-03-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds a new feature to :autocmd which sets the handler to be executed at most one times. Before: augroup FooGroup autocmd! autocmd FileType foo call Foo() | autocmd! FooGroup * <buffer> augroup END After: autocmd FileType foo once call Foo()
* | vim-patch:8.1.0994: fix relative cursor position #9676Justin M. Keyes2019-03-09
|/ | | | | | Problem: Relative cursor position is not calculated correctly. Solution: Always set topline, also when window is one line only. (Robert Webb) Add more info to getwininfo() for testing. https://github.com/vim/vim/commit/8fcb60f961bdd134599fb016c6537fd496e800f5
* floats: implement floating windowsBjörn Linse2019-03-02
| | | | Co-Author: Dongdong Zhou <dzhou121@gmail.com>
* vim-patch:8.1.0225: mode() does not indicate using CTRL-O from Insert mode ↵Justin M. Keyes2019-02-24
| | | | | | | (#9644) Problem: Mode() does not indicate using CTRL-O from Insert mode. Solution: Add "niI", "niR" and "niV" to mode() result. (closes vim/vim#3000) https://github.com/vim/vim/commit/612cc3888b136e80485132d9f997ed457dbc5501
* man.vim: g:man_hardwrap #9633Curtis McEnroe2019-02-21
| | | | | | This option allows restoring the behaviour prior to #9023. Fixes #9583 Closes #9633
* vim-patch:8.1.0932: remove Farsi support (#9622)Justin M. Keyes2019-02-17
| | | | | Problem: Farsi support is outdated and unused. Solution: Delete the Farsi support. https://github.com/vim/vim/commit/14184a3133b9a6ee5f711d493c04e41ba4fa7c2f
* API: nvim_create_buf: add `scratch` parameterJustin M. Keyes2019-02-17
| | | | | Creating a scratch buffer is a chore/ritual, and would be more useful/common if formally exposed.
* UI: change implementation of hl_rgb2cterm_color()Justin M. Keyes2019-02-12
| | | | | Replace the implementation cargo-culted from Vim's source with something simpler which "seems to look better" with 'pumblend'.
* UI: 'pumblend' for cterm (256-color TUI)Justin M. Keyes2019-02-12
| | | | | | hl_rgb2cterm_color, hl_cterm2rgb_color were adapted from Vim 8.1 (color2index, cterm_color2rgb). ref: https://github.com/vim/vim/commit/c5cd88554f1e0b2e9ff08d9a0748238dd8340ce1
* ui: implement ext_messagesBjörn Linse2019-02-10
| | | | Co-Author: Dongdong Zhou <dzhou121@gmail.com>
* doc: 'fillchars' is local to windowMarco Hinz2019-02-09
| | | | | This was forgotten in 352811fe5 since the commit was originally meant to only change 'listchars'.
* UI: implement 'pumblend' option for semi-transparent popupmenuBjörn Linse2019-02-07
| | | | | | | | | | | | | Why? - Because we can. - Because the TUI is just another GUI™ - Because it looks kinda nice, and provides useful context like 1 out of 100 times Complies with "don't pay for what you don't use". Some crashes for resizing were unfolded, add tests for those.
* man.vim: set 'linebreak'Justin M. Keyes2019-02-06
| | | | closes #9583
* UI: always use contrete colors for default_colors_setBjörn Linse2019-02-05
| | | | | But add an escape hatch needed for external TUI, so it still can use terminal emulator defaults.
* options: set 'scrollback' to -1 by default #9563Marco Hinz2019-02-04
| | | | | | | | | Makes the 'scrollback' option more consistent (same default for all buffers) and future-proof. - Default to -1 for all buffers, but treat it as an implementation detail. - Document range of 1 - 100_000. - New terminal buffer by default sets scrollback=10_000 if the global default is -1. - Existing terminal buffer: On entering terminal-mode or on refresh, if the user explicitly did `:set[local] scbk=-1`, the local value goes to 100_000 (max). (This is undocumented on purpose. Users should work with explicit values in the range of 1-100_000.)
* events: add "Signal" event #9564Marco Hinz2019-02-04
| | | | | ..which gets triggered when SIGUSR1 is sent to the nvim process. Closes #9562
* vim-patch:8.0.1114: default for 'iminsert' is annoyingJan Edmund Lazo2019-02-03
| | | | | | Problem: Default for 'iminsert' is annoying. Solution: Make the default always zero. (Yasuhiro Matsumoto, closes vim/vim#2071) https://github.com/vim/vim/commit/4cf56bbc85f77846aeb378cfb071677336dfad6d
* vim-patch:8.0.1077: no debugger making use of the terminal windowJan Edmund Lazo2019-02-03
| | | | | | | Problem: No debugger making use of the terminal window. Solution: Add the term debugger plugin. So far only displays the current line when stopped. https://github.com/vim/vim/commit/fe386641b0c56c5de2bca8e1f4cd5e2a1f1aea7e
* Merge #9539 "options: make 'listchars' and 'fillchars' local to window"Marco Hinz2019-01-28
|\
| * vim-patch:8.1.0759: showing two characters for tab is limitedMarco Hinz2019-01-26
| | | | | | | | | | | | | | | | Problem: Showing two characters for tab is limited. Solution: Allow for a third character for "tab:" in 'listchars'. (Nathaniel Braun, Ken Takata, closes vim/vim#3810) https://github.com/vim/vim/commit/83a52171ba00b2b9fd2d1d22a07e38fc9fc69c1e
| * options: make 'fillchars'/'listchars' local to windowMarco Hinz2019-01-26
| | | | | | | | | | | | | | | | | | | | Using 'listchars' is a nice way to highlight tabs that were included by accident for buffers that set 'expandtab'. But maybe one does not want this for buffers that set 'noexpandtab', so now one can use: autocmd FileType go let &l:listchars .= ',tab: '
* | doc [ci skip] (#9553)Justin M. Keyes2019-01-27
| |
* | menu_get(): fix query behaviorJustin M. Keyes2019-01-27
| | | | | | | | | | | | - Return the menu properties, not only its children. - If the {path} param is given, return only the first node. The "next" nodes in the linked-list are irrelevant.
* | gen_api_vimdoc.py: Do not wrap on hyphens, long wordsJustin M. Keyes2019-01-26
| | | | | | | | | | | | - Any long symbol is intentional and should never be hardwrapped. - Vim help tags are often hyphenated, and hardwrapping on hyphens breaks the Vim help syntax parser.
* | doc [ci skip] #9478Justin M. Keyes2019-01-26
|/ | | | | | | | | | | | - Lua - developer guidelines - MAINTAIN.md - TUI: cleanup - TUI: mention Windows terminfo builtins - cleanup if_pyth, redirect python-bindeval tag Helped-by: Björn Linse <bjorn.linse@gmail.com> Helped-by: erw7 <erw7.github@gmail.com>
* checkhealth: validate locale (#9548)Justin M. Keyes2019-01-26
| | | | | | Test case: LANG= LC_ALL= LC_CTYPE= tmux nvim -u NORC +'checkhealth nvim'
* Fix api doc nvim_buf_lines_event exampleChen Mulong2019-01-22
| | | | when send_buffer=true, the first nvim_buf_lines_event will come with lastline=-1 instead of 0.
* ui: multigrid mouse supportBjörn Linse2019-01-20
|
* lua/stdlib: Load runtime modules on-demandJustin M. Keyes2019-01-14
| | | | | | | | | | Instead of eager-loading during plugin/* sourcing, define runtime modules such as `vim.inspect` as lazy builtins. Otherwise non-builtin Lua modules such as `vim.inspect` would not be available during startup (init.vim, `-c`, `--cmd`, …). ref #6580 ref #8677
* lua/stdlib: vim.inspect, string functionsKillTheMule2019-01-14
| | | | | ref #6580 ref #8677
* Merge #9468 'checkhealth: detect broken pip"'Justin M. Keyes2019-01-11
|\
| * health/pythonx: handle "pip upgrade failure"Marco Hinz2019-01-07
| | | | | | | | Reference: https://github.com/neovim/neovim/wiki/Following-HEAD#20181118
| * health/pythonx: refactor #Detect()Marco Hinz2019-01-07
| |
| * health/pythonx: refactor pyenv checkMarco Hinz2019-01-07
| |
* | clipboard/macOS: assume that pbcopy works #9480Marco Hinz2019-01-10
| | | | | | Avoids ~30-60 ms startup cost for users of clipboard=unnamed.
* | vim-patch:8.1.0648: custom operators can't act upon forced motionPedro L. Ramos2019-01-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Custom operators can't act upon a forced motion. (Christian Wellenbrock) Solution: Add the forced motion to the mode() result. (Christian Brabandt, closes vim/vim#3490) https://github.com/vim/vim/commit/5976f8ff00efcb3e155a89346e44f2ad43d2405a closes #8667 closes #9476 Christian Wellenbrock: > For (most) built in text objects it's possible to force operation on > them to be linewise, for example by using `dVab` (`:h o_V`, > `motion_force`). When using custom text objects (defined as mappings > by plugins for example), this doesn't currently work. > > Example: > > onoremap x viw > > Open a file with a few lines each containing some words. With the > cursor on any word, try: > > 1. `dw` (builtin) deletes some characters > 2. `dVw` (builtin) deletes linewise > 3. `dx` (from mapping) deletes some characters > 4. `dVx` (from mapping) deletes some characters, but should delete > linewise ref: https://github.com/wellle/targets.vim/issues/214 ref: https://gitter.im/neovim/neovim?at=5b379ff7f1664406610e7483
generated by cgit (git 2.34.1) at 2025-06-25 02:55:03 +0000