aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/undo.c
Commit message (Collapse)AuthorAge
* refactor: saner options for uncrustify (#16204)dundargoc2021-11-19
| | | | | | | | | | | | | | | | | | | | | | | | * sp_enum_after_assign = force * sp_brace_typedef = force * nl_do_brace = remove * sp_do_brace_open = force * sp_brace_close_while = force * sp_before_semi = remove * sp_before_semi_for = remove * sp_before_semi_for_empty = remove * sp_between_semi_for_empty = remove * sp_after_semi_for_empty = remove * sp_before_square = remove * sp_before_squares = remove * sp_inside_square = remove * sp_inside_fparens = remove * sp_inside_fparen = remove * sp_inside_tparen = remove * sp_after_tparen_close = remove * sp_return_paren = force * pos_bool = lead * sp_pp_concat = remove * sp_pp_stringify = remove * fixup: disable formatting for the INIT section
* vim-patch:8.1.0779: argument for message functions is inconsistentJames McCoy2021-11-01
| | | | | | Problem: Argument for message functions is inconsistent. Solution: Make first argument to msg() "char *". https://github.com/vim/vim/commit/32526b3c1846025f0e655f41efd4e5428da16b6c
* vim-patch:8.1.0743: giving error messages is not flexibleJames McCoy2021-11-01
| | | | | | | | | Problem: Giving error messages is not flexible. Solution: Add semsg(). Change argument from "char_u *" to "char *", also for msg() and get rid of most MSG macros. (Ozaki Kiichi, closes vim/vim#3302) Also make emsg() accept a "char *" argument. Get rid of an enormous number of type casts. https://github.com/vim/vim/commit/f9e3e09fdc93be9f0d47afbc6c7df1188c2a5a0d
* refactor: saner options for uncrustify #16196dundargoc2021-10-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * refactor: general good option changes sp_deref = remove sp_not = remove sp_inv = remove sp_inside_paren_cast = remove mod_remove_duplicate_include = true sp_after_semi = add sp_after_semi_for = force sp_sizeof_paren = remove nl_return_expr = remove nl_else_brace = remove nl_else_if = remove * refactor: mod_remove_extra_semicolon = true * refactor: nl_max = 3 * refactor: sp_bool = force * refactor: sp_compare = force * refactor: sp_inside_paren = remove * refactor: sp_paren_paren = remove * refactor: sp_inside_sparen = remove * refactor: sp_before_sparen = force * refactor: sp_sign = remove * refactor: sp_addr = remove * refactor: sp_member = remove * refactor: nl_struct_brace = remove * refactor: nl_before_if_closing_paren = remove * refactor: nl_fdef_brace = force * refactor: sp_paren_comma = force * refactor: mod_full_brace_do = add
* vim-patch:8.1.2396: using old C style commentsDundar Göc2021-10-21
| | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/e38eab22c1fb950127f0307a9904de6d4561dc70
* refactor: remove space after starDundar Göc2021-10-19
|
* Merge pull request #15930 from dundargoc/vim-patch/old-style-c-commentsJan Edmund Lazo2021-10-17
|\ | | | | vim-patch:8.1.2396,8.1.2395,8.1.2394,8.1.2392,8.1.2368,8.1.2388,8.1.2379
| * vim-patch:8.1.2396: using old C style commentsDundar Göc2021-10-06
| | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/e38eab22c1fb950127f0307a9904de6d4561dc70
* | refactor: format all C files under nvim/ #15977dundargoc2021-10-12
| | | | | | | | | | | | | | | | * refactor: format all C files under nvim * refactor: disable formatting for Vim-owned files: * src/nvim/indent_c.c * src/nvim/regexp.c * src/nvim/regexp_nfa.c * src/nvim/testdir/samples/memfile_test.c
* | fix(extmarks): splice extmarks on nv_Undo #15920Tony Chen2021-10-06
|/
* refactor: remove redundant char casts #15888dundargoc2021-10-04
|
* refactor: format with uncrustify #15872dundargoc2021-10-02
| | | | * refactor: format with uncrustify * refactor: fix function parameter comments
* fix: remove trailing slashes before making directoryGregory Anders2021-08-27
| | | | | | Remove the trailing slashes from 'undofile' and 'backupdir' before creating directories. They cause problems on Windows which doesn't recognize these slashes as proper path separators.
* refactor: replace TRUE/FALSE with true/false #15425dundargoc2021-08-22
|
* refactor: replace TRUE/FALSE with true/falseDundar Göc2021-08-12
|
* fix: fix incorrect call sites of xcallocGregory Anders2021-07-24
| | | | The number of elements comes first and the size of each element second.
* refactor(undo): don't assume curbuf in u_compute_hashThomas Vigouroux2021-07-09
|
* refactor(undo): remove last occurence of save_curbufThomas Vigouroux2021-07-08
|
* style(undo): remove unnecessary commentThomas Vigouroux2021-07-06
|
* buffer: move BUFEMPTY to a functionThomas Vigouroux2021-07-06
|
* undo: reduce reliance on curbufThomas Vigouroux2021-07-06
|
* buffer: don't rely on curbuf in BUFEMPTYThomas Vigouroux2021-07-06
|
* undo: pvs/v547Jan Edmund Lazo2021-06-05
| | | | | | buf is nonnull when xfree(buf) is executed. free(NULL) is safe (for target compilers) so xfree(NULL) is also safe.
* Extmarks: Save extmark undo information to undofile.chentau2021-03-02
|
* buffer_updates: autoload episode III: revenge of the treesBjörn Linse2021-02-14
|
* fix: Include auto/config.h before HAVE_* preprocessor checksJames McCoy2020-12-15
| | | | Closes #13533
* vim-patch:8.1.2064: MS-Windows: compiler warnings for unused argumentsJan Edmund Lazo2020-12-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: MS-Windows: compiler warnings for unused arguments. Solution: Add UNUSED. (Yegappan Lakshmanan, closes vim/vim#4963) https://github.com/vim/vim/commit/bd67aac279adf3a1cfa11557229b44e4c2c3dcda N/A patches for version.c: vim-patch:8.1.0818: MS-Windows: cannot send large data with ch_sendraw() Problem: MS-Windows: cannot send large data with ch_sendraw(). Solution: Split write into several WriteFile() calls. (Yasuhiro Matsumoto, closes vim/vim#3823) https://github.com/vim/vim/commit/240583869ae477202494dd01ef1e8e2bac650f10 vim-patch:8.1.1131: getwinpos() does not work in the MS-Windows console Problem: getwinpos() does not work in the MS-Windows console. Solution: Implement getwinpos(). https://github.com/vim/vim/commit/16c34c37659e6afca74169969bdacb6b866548c9 vim-patch:8.2.0587: compiler warning for unused variable Problem: Compiler warning for unused variable. Solution: Add UNUSED. https://github.com/vim/vim/commit/21cfe500f322a0bea3367c677943ea6c57c282b9 vim-patch:8.2.0879: compiler warning for unused function argument Problem: Compiler warning for unused function argument. Solution: Add UNUSED. https://github.com/vim/vim/commit/f9ca08e95ff5b66a02c75334264dd86508b2a453 vim-patch:8.2.2104: build problem with Ruby 2.7 Problem: Build problem with Ruby 2.7. Solution: Adjust function declarations. (Ozaki Kiichi, closes vim/vim#7430) https://github.com/vim/vim/commit/d5a986f460019a924627d79350552f446505cffb
* api: add API for themesBjörn Linse2020-11-01
| | | | | | | | | | co-author: hlpr98 <hlpr98@gmail.com> (dict2hlattrs function) orange is sus?? NOVEMBER DAWN erase the lie that is redraw_later()
* vim-patch:8.1.1812: reading a truncted undo file hangs VimJan Edmund Lazo2020-10-05
| | | | | | Problem: Reading a truncted undo file hangs Vim. Solution: Check for reading EOF. (closes vim/vim#4769) https://github.com/vim/vim/commit/fb06d767a8d76eead5391302fc88115d6e3879d8
* undo: fix possibility of abortingerw72020-10-02
|
* 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
* vim-patch:8.1.0091: MS-Windows: Cannot interrupt gdb when program is runningerw72020-02-12
| | | | | | | Problem: MS-Windows: Cannot interrupt gdb when program is running. Solution: Add debugbreak() and use it in the terminal debugger. Respect 'modified' in a prompt buffer. https://github.com/vim/vim/commit/4551c0a9fcdbdef52836d4852686d54b5e47fdaf
* shed biking: it's always extmarks, never marks extendedBjörn Linse2020-01-20
|
* extmarks/bufhl: reimplement using new marktree data structureBjörn Linse2020-01-16
| | | | | | | | | | | | | | | | | | | | Add new "splice" interface for tracking buffer changes at the byte level. This will later be reused for byte-resolution buffer updates. (Implementation has been started, but using undocumented "_on_bytes" option now as interface hasn't been finalized). Use this interface to improve many edge cases of extmark adjustment. Changed tests indicate previously incorrect behavior. Adding tests for more edge cases will be follow-up work (overlaps on_bytes tests) Don't consider creation/deletion of marks an undoable event by itself. This behavior was never documented, and imposes complexity for little gain. Add nvim__buf_add_decoration temporary API for direct access to the new implementation. This should be refactored into a proper API for decorations, probably involving a huge dict. fixes #11598
* PVS/V618: fix emsgf format specifier #11643Husain Alshehhi2020-01-01
|
* extmark: don't crash in RO buffer.Björn Linse2019-11-16
|
* undo: delete undo_off global without effectBjörn Linse2019-11-16
|
* extmark: review changesBjörn Linse2019-11-11
|
* nsmarks: initial committimeyyy2019-11-11
|
* Remove excess <stdint.h>Jan Edmund Lazo2019-09-11
|
* vim-patch:8.1.1498: ":write" increments b:changedtick even though nothing ↵Justin M. Keyes2019-09-04
| | | | | | | | | changed Problem: ":write" increments b:changedtick even though nothing changed. (Daniel Hahler) Solution: Only increment b:changedtick if the modified flag is reset. https://github.com/vim/vim/commit/c024b4667875e5bc6fd0ed791530e33c3161bff7
* vim-patch:8.0.0858: check if job terminal is running #10908Jan Edmund Lazo2019-09-01
| | | | | Problem: Can exit while a terminal is still running a job. Solution: Consider a buffer with a running job like a changed file. https://github.com/vim/vim/commit/eb44a68b42eda207a5bc4def9ea8fc4d38acb650
* includesDaniel Hahler2019-08-07
|
* vim-patch:8.1.1049: when user tries to exit with CTRL-C message is confusingJan Edmund Lazo2019-07-28
| | | | | | | | | | | | | | | | | | Problem: When user tries to exit with CTRL-C message is confusing. Solution: Only mention ":qa!" when there is a changed buffer. (closes vim/vim#4163) https://github.com/vim/vim/commit/a84a3dd6635fcd2e07f510cba6a999585dcc381a vim-patch:8.1.1052: test for CTRL-C message sometimes fails Problem: test for CTRL-C message sometimes fails Solution: Make sure there are no changed buffers. https://github.com/vim/vim/commit/553e5a5c568e7d175b65b0472cd6d9843b25f4c8 vim-patch:8.1.1053: warning for missing return statement Problem: Warning for missing return statement. (Dominique Pelle) Solution: Add return statement. https://github.com/vim/vim/commit/d6c3f1fa2b5e1dd7dc87cf608d72b84ad696b58f
* cleanup: remove mch_fopen in favor of os_fopenJustin M. Keyes2019-07-25
|
* api: allow nvim_buf_attach from lua using callbacksBjörn Linse2019-06-04
|
* vim-patch:8.0.1496: VIM_CLEAR()Justin M. Keyes2019-05-25
| | | | | | | | Problem: Clearing a pointer takes two lines. Solution: Add VIM_CLEAR() and replace vim_clear(). (Hirohito Higashi, closes #2629) vim-patch:8.0.1481
* cleanup: remove HAVE_SELINUX #10040Justin M. Keyes2019-05-21
| | | | We never define HAVE_SELINUX, and no one has asked for it. So remove the dead code.
* lintJan Edmund Lazo2019-04-30
|
* lintJustin M. Keyes2019-04-29
|