aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/option.c
Commit message (Collapse)AuthorAge
...
* vim-patch:8.2.0901: formatting CJK text isn't optimalJan Edmund Lazo2020-10-23
| | | | | | Problem: Formatting CJK text isn't optimal. Solution: Properly break CJK lines. (closes vim/vim#3875) https://github.com/vim/vim/commit/e52702f00322c8a8861efd0bd6a3775e685e5685
* vim-patch:8.2.0943: displaying ^M or ^J depends on current bufferJan Edmund Lazo2020-10-18
| | | | | | | | | | | | | | | Problem: Displaying ^M or ^J depends on current buffer. Solution: Pass the displayed buffer to transchar(). (closes vim/vim#6225) https://github.com/vim/vim/commit/32ee627750e8b7b3fa6516b893e72f6e6af54710 N/A patches for version.c: vim-patch:8.2.0862: ":term ++curwin" makes the current buffer hidden Problem: ":term ++curwin" makes the current buffer hidden. (Harm te Hennepe) Solution: Do not hide the current buffer. (closes vim/vim#6170) https://github.com/vim/vim/commit/b10090928cb5283f867e8457b7eea0985470d8d4
* vim-patch:8.1.1795: no syntax HL after splitting windows with :bufdoJan Edmund Lazo2020-10-17
| | | | | | | | Problem: No syntax HL after splitting windows with :bufdo. (Yasuhiro Matsumoto) Solution: Trigger Syntax autocommands in buffers that are active. (closes vim/vim#4761) https://github.com/vim/vim/commit/c7f1e4002184903f4e12e429dd5c6ab731932f86
* vim-patch:8.2.0953: spell checking doesn't work for CamelCased wordsThomas Vigouroux2020-09-24
| | | | | | | Problem: Spell checking doesn't work for CamelCased words. Solution: Add the "camel" value in the new option 'spelloptions'. (closes vim/vim#1235) https://github.com/vim/vim/commit/362b44bd4aa87a2aef0f8fd5a28d68dd09a7d909
* win/env: fix stdpath()/XDG_* initialization, parsing #12829erw72020-09-07
| | | | | | | | - Windows environment variables are semicolon-separated, but some logic was assuming colon (:). This broke initialization and parsing of XDG_CONFIG_DIRS, XDG_DATA_DIRS, 'runtimepath', stdpath(), etc. - test/defaults_spec: enable tests on Windows ref #12793
* vim-patch:8.2.1386: backslash not removed afer space with space in 'isfname'Jan Edmund Lazo2020-08-14
| | | | | | | | Problem: Backslash not removed afer space in option with space in 'isfname'. Solution: Do remove backslash before space, also when it is in 'isfname'. (Yasuhiro Matsumoto, closes vim/vim#6651) https://github.com/vim/vim/commit/994b89d28dc54c896e00eba66e247addb0540272
* fix: runtimepath always updates lua package.pathTJ DeVries2020-08-10
|
* vim-patch:8.1.1564: sign column takes up spaceShougo Matsushita2020-07-23
| | | | | | | Problem: Sign column takes up space. (Adam Stankiewicz) Solution: Optionally put signs in the number column. (Yegappan Lakshmanan, closes vim/vim#4555, closes vim/vim#4515) https://github.com/vim/vim/commit/394c5d8870b15150fc91a4c058dc571fd5eaa97e
* vim-patch:8.1.1623: display wrong with signs in narrow number columnerw72020-07-23
| | | | | | | Problem: Display wrong with signs in narrow number column. Solution: Increase the numbercolumn width if needed. (Yegappan Lakshmanan, closes vim/vim#4606) https://github.com/vim/vim/commit/e4b407f536ba8bd007152649a347a95320d80fce
* vim-patch:8.1.1564: sign column takes up spaceShougo Matsushita2020-07-23
| | | | | | | Problem: Sign column takes up space. (Adam Stankiewicz) Solution: Optionally put signs in the number column. (Yegappan Lakshmanan, closes vim/vim#4555, closes vim/vim#4515) https://github.com/vim/vim/commit/394c5d8870b15150fc91a4c058dc571fd5eaa97e
* option: fix pvs/v547Jan Edmund Lazo2020-06-18
|
* vim-patch:8.2.0932: missspelling spelllangJan Edmund Lazo2020-06-18
| | | | | | Problem: Missspelling spelllang. Solution: Add an "l". (Dominique Pelle) https://github.com/vim/vim/commit/f154f3ab2c1eea67afc20140c580ad003752dc72
* vim-patch:8.0.1554: custom plugins loaded with --cleanJan Edmund Lazo2020-06-18
| | | | | | Problem: Custom plugins loaded with --clean. Solution: Do not include the home directory in 'runtimepath'. https://github.com/vim/vim/commit/072687032683b1994d25a114893d9a6f8bc36612
* vim-patch:8.2.0309: window-local values have confusing nameJan Edmund Lazo2020-05-11
| | | | | | Problem: Window-local values have confusing name. Solution: Rename w_p_bri* to w_briopt_*. https://github.com/vim/vim/commit/b81f56fb57c87a7490dd79908c257437d1958447
* terminal: always return zero from get_scrolloff_value() #12230LawAbidingCactus2020-05-04
| | | | | | | Fixes flicker fix #11072 fix #11915
* vim-patch:8.1.0814: :mksession cannot handle a very long 'runtimepath'Billy Su2020-05-02
| | | | | | | | Problem: :mksession cannot handle a very long 'runtimepath'. (Timothy Madden) Solution: Expand each part separately, instead of the whole option at once. (Christian Brabandt, closes vim/vim#3466) https://github.com/vim/vim/commit/ed18f2c03ae4786b489943cb575bb781a70356e4
* Merge #12155 ':ls filter by terminal, lastused'Justin M. Keyes2020-04-26
|\
| * vim-patch:8.1.2225: the "last used" info of a buffer is under usedRob Pilling2020-04-21
| | | | | | | | | | | | | | Problem: The "last used" info of a buffer is under used. Solution: Add "lastused" to getbufinfo(). List buffers sorted by last-used field. (Andi Massimino, closes vim/vim#4722) https://github.com/vim/vim/commit/52410575be50d5c40bbe6380159df48cfc382ceb
* | lint: use docstring style #12187Billy SU2020-04-26
|/
* vim-patch:8.1.2147: crash when allocating memory failsJan Edmund Lazo2020-04-13
| | | | | | Problem: Crash when allocating memory fails. (Zu-Ming Jiang) Solution: Check that 'spellcapcheck' is not NULL. (closes vim/vim#5048) https://github.com/vim/vim/commit/53efb18530cc3940d7af2ea338947783ea5495ed
* pvs/v502: use explicit ternary in for-loopJan Edmund Lazo2020-04-13
|
* vim-patch:8.1.0864 Make 'scrolloff' and 'sidescrolloff' options window local ↵Will Eccles2020-03-17
| | | | | | | | | | (#11854) Problem: cannot have a local value for 'scrolloff' and 'sidescrolloff' Author: Bram Moolenar https://github.com/vim/vim/commit/375e3390078e740d3c83b0c118c50d9a920036c7
* vim-patch:8.1.1279: cannot set 'spellang' to "sr@latin"Jan Edmund Lazo2020-03-07
| | | | | | Problem: Cannot set 'spellang' to "sr@latin". (Bojan Stipic) Solution: Allow using '@' in 'spellang'. (closes vim/vim#4342) https://github.com/vim/vim/commit/9a061cb78ccbf78ec9ae454d37a49edccb4e94fc
* Merge pull request #11716 from teto/folds_auto_backupMatthieu Coudron2020-03-02
|\ | | | | [RFC] foldcolumn autowidth
| * addressing reviewsMatthieu Coudron2020-03-01
| |
| * foldcolumn: allow auto:XMatthieu Coudron2020-02-29
| | | | | | | | | | | | | | | | Similar to signcolumn, allow foldcolumn to adapt itself to the number of folds. Regression: vim supports a maximum fdc of 12, this limits it to 9.
* | vim-patch:8.1.0253: saving and restoring window title does not always workJan Edmund Lazo2020-03-01
|/ | | | | | | Problem: Saving and restoring window title does not always work. Solution: Use the stack push and pop commands. (Kouichi Iwamoto, closes vim/vim#3059) https://github.com/vim/vim/commit/40385dbcdfb44885f2e9b83e1e0285aeb8a0c2a8
* vim-patch:8.0.1660: the terminal API "drop" command doesn't support optionsJan Edmund Lazo2020-02-16
| | | | | | Problem: The terminal API "drop" command doesn't support options. Solution: Implement the options. https://github.com/vim/vim/commit/333b80acf3a44e462456e6d5730e47ffa449c83d
* vim-patch:8.1.0032: BS in prompt buffer starts new lineerw72020-02-12
| | | | | | | Problem: BS in prompt buffer starts new line. Solution: Do not allows BS over the prompt. Make term_sendkeys() handle special keys. Add a test. https://github.com/vim/vim/commit/6b810d92a9cd9378ab46ea0db07079cb789f9faa
* vim-patch:8.1.0027: difficult to make a plugin that feeds a line to a joberw72020-02-12
| | | | | | Problem: Difficult to make a plugin that feeds a line to a job. Solution: Add the nitial code for the "prompt" buftype. https://github.com/vim/vim/commit/f273245f6433d5d43a5671306b520a3230c35787
* env: try find library dir (like /usr[/local]/lib/nvim) and add it to &rtpBjörn Linse2020-02-07
|
* options: winhighlight: fix incorrect string equality testBjörn Linse2020-01-28
|
* refactor: move session functions to ex_session.cJustin M. Keyes2020-01-28
|
* vim-patch:8.1.1144: too strict checking of the 'spellfile' optionJan Edmund Lazo2020-01-26
| | | | | | Problem: Too strict checking of the 'spellfile' option. Solution: Allow for a path. https://github.com/vim/vim/commit/862f1e17eaf2b9c6617dfba31d8487cde462658d
* vim-patch:8.1.1143: may pass weird strings to file name expansionJan Edmund Lazo2020-01-26
| | | | | | Problem: May pass weird strings to file name expansion. Solution: Check for matching characters. Disallow control characters. https://github.com/vim/vim/commit/8f130eda4747e4a4d68353cdb650f359fd01469b
* vim-patch:8.1.0061: fix resetting, setting 'title' #11733Billy SU2020-01-21
| | | | | Problem: Window title is wrong after resetting and setting 'title'. Solution: Move resetting the title into maketitle(). (Jason Franklin) https://github.com/vim/vim/commit/84a9308511871d9ff94c91a1c6badb92300ded98
* restore old 'termencoding' behaviorBjörn Linse2020-01-19
| | | | | | | | | | | | | | | | | | | | | | Partially reverts #11647. Replaces #11662 The old implementation was removed without clear motivation. The "term option" hackaround added in its place is neither shorter nor simpler. The new behavior breaks even init.vim that expliticly check against it: if exists('&termencoding') set termencoding=utf-8 endif There was nothing wrong with the 0.4.x behavior. Empty &tenc has indicated that the &enc value should be used for all the history of Nvim. Ignoring setting the option is the expected behavior for Vim versions that does not support the option (and Nvim is such a version) 'tenc' was also irrelevant to the Test_unicode python3 test. The reason this has to be disabled is that neovim can't change internal 'encoding'
* Remove termtype optionerw72020-01-17
|
* Change option name from termwintype to termtypeerw72020-01-17
|
* Rename from os_win_conpty.{c,h} to pty_conpty_win.{c,h}erw72020-01-17
|
* Change to use ConPTY, if availableerw72020-01-17
|
* defaults: set fillchars "foldsep" to box line #11702Matthieu Coudron2020-01-11
| | | | | "│" U+2502 BOX DRAWINGS LIGHT VERTICAL Fallback to old default | if 'ambiwidth' is set.
* option: restore termencoding (readonly) #11662Jan Edmund Lazo2020-01-02
| | | | 'termencoding' option was removed in abaabd1d03fd723630f6addeadee9928faa4cdde but some plugins check its value.
* fillchars: adding foldopen, foldsep, foldcloseMatthieu Coudron2019-12-25
| | | | | You can try it with set fillchars+=foldopen:▾,foldsep:│,foldclose:▸
* jumplist: browser-style (or 'tagstack') navigation #11530butwerenotthereyet2019-12-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Traditionally, when navigating to a specific location from the middle of the jumplist results in shifting the current location to the bottom of the list and adding the new location after it. This behavior is not desireable to all users--see, for example https://vi.stackexchange.com/questions/18344/how-to-change-jumplist-behavior. Here, another jumplist behavior is introduced. When jumpoptions (a new option set added here) includes stack, the jumplist behaves like the tagstack or like history in a web browser. That is, when navigating to a location from the middle of the jumplist 2 first 1 second 0 third <-- current location 1 fourth 2 fifth to a new location the locations after the current location in the jump list are discarded 2 first 1 second 0 third <-- current location The result is that when moving forward from that location, the new location will be appended to the jumplist: 3 first 2 second 1 third 0 new If the new location is the same new == second as some previous (but not immediately prior) entry in the jumplist, 2 first 1 second 0 third <-- current location 1 fourth 2 fifth both occurrences preserved 3 first 2 second 1 third 0 second (new) when moving forward from that location. It would be desireable to go farther and, when the new location is the same as the location that is currently next in the jumplist, new == fourth make the result of navigating to the new location by jumping (e.g. 50gg) be the same as moving forward in the jumplist 2 first 1 second 0 third 1 new <-- current location 2 fifth and simply increment the jumplist index. That change is NOT part of this patch because it would require passing the new cursor location to the function (setpcmark) from all of its callees. That in turn would require those callees to know *before* calling what the new cursor location is, which do they do not currently.
* Merge pull request #11445 from bfredl/fcslcsBjörn Linse2019-11-26
|\ | | | | options: make 'fillchars' and 'listchars' global-local instead of local-only
| * options: make 'fillchars' and 'listchars' global-localBjörn Linse2019-11-26
| | | | | | | | | | | | | | | | | | These options were previously global. A global-local window option behaves closer to a global option "per default" (i e with :set), but still supports local behavior via :setl Also this restores back-compat for nvim_set_option("fcs", ...) which are currently broken on 0.4.x but worked in earlier versions
* | UI: emit mouse_on/mouse_off on attach #11455Justin M. Keyes2019-11-25
|/ | | closes #11372
* vim-patch:8.1.1228: not possible to process tags with a functionRob Pilling2019-10-22
| | | | | | Problem: Not possible to process tags with a function. Solution: Add tagfunc() (Christian Brabandt, Andy Massimino, closes vim/vim#4010) https://github.com/vim/vim/commit/45e18cbdc40afd8144d20dcc07ad2d981636f4c9
* win_line: update `w_last_cursorline` alwaysDaniel Hahler2019-10-04
| | | | | | | | | | | | Vim patch 8.1.0856 (54d9ea6) caused a performance regression in Neovim, when `set conceallevel=1 nocursorline` was used, since then due to refactoring in 23c71d5 `w_last_cursorline` would never get updated anymore. Adds/uses `redrawdebug+=nodelta` for testing this. Fixes https://github.com/neovim/neovim/issues/11100. Closes https://github.com/neovim/neovim/pull/11101.
generated by cgit (git 2.34.1) at 2025-09-24 07:22:17 +0000