aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
| * | | strings.c: remove unused assignmentJente Hidskes2017-02-20
| | | | | | | | | | | | | | | | | | | | As reported by clang-scan, `length_modifier` is never read in any code path following this branch. It is safe to remove.
| * | | hardcopy.c: fix dead assignmentSander Bosma2017-02-20
| | | | | | | | | | | | | | | | | | | | | | | | `has_mbyte` is deprecated (globals.h), so `outputlen` is always assigned within the if statement. Therefore, the previous initialization is unnecessary.
| * | | message.c: fix dead assignment by removing dead codeSander Bosma2017-02-20
| | | | | | | | | | | | | | | | | | | | `enc_dbcs` and `enc_utf8` are deprecated (globals.h), so the second branch is always taken.
| * | | misc1.c: remove dead initializationSander Bosma2017-02-20
| | | |
| * | | screen.c: remove dead codeSander Bosma2017-02-20
| | | | | | | | | | | | | | | | | | | | | | | | As stated in globals.h, mbyte flags are deprecated, and code using it can be refractored to remove dead code. Since has_mbyte is defined to true, this refractoring correct.
| * | | screen.c: account for translated string lengthJente Hidskes2017-02-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `[RO]` is appended to the status line and `len` is increased with the length of this string (4). However, the string is marked for translation and may thus well be larger (or smaller) than 4. Therefore, we check the length at runtime. The resulting len is never actually used, and thus could be removed. However, by keeping this line, the body of this if-statement is kept consistent with surrounding code, and future changes can not forget to add this line when additional strings are added to p.
* | | | Merge pull request #6121 from lonerover/vim-7.4.2046James McCoy2017-02-27
|\ \ \ \ | | | | | | | | | | | | | | | vim-patch:7.4.2046
| * | | | vim-patch:7.4.2061lonerover2017-02-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: qf_init_ext() is too big. Solution: Move code to qf_parse_line() (Yegappan Lakshmanan) https://github.com/vim/vim/commit/e87e6dddc2b2a99572ec0db0833c052214c4fbd3
| * | | | vim-patch:7.4.2047lonerover2017-02-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Compiler warning for initializing a struct. Solution: Initialize in another way. (Anton Lindqvist) https://github.com/vim/vim/commit/bfafb4c4a01db3f8c508716daf689e0dfe92b649
| * | | | vim-patch:7.4.2046rover2017-02-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: The qf_init_ext() function is too big. Solution: Refactor it. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/e0d3797664c59afc9705808f86a7cf00fd6d874d
* | | | | lintJames McCoy2017-02-27
| | | | |
* | | | | vim-patch:7.4.2200James McCoy2017-02-27
| |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Cannot get all information about a quickfix list. Solution: Add an optional argument to get/set loc/qf list(). (Yegappan Lakshmanan) https://github.com/vim/vim/commit/d823fa910cca43fec3c31c030ee908a14c272640
* | | | Merge #6112 from ZyX-I/split-eval'/buf_get_changedtickJustin M. Keyes2017-02-27
|\ \ \ \ | | | | | | | | | | Better b:changedtick support
| * | | | *: Fix linter errorsZyX2017-02-25
| | | | |
| * | | | buffer: Hide one of the asserts from lua parserZyX2017-02-25
| | | | |
| * | | | buffer: Provide an initializer for di_keyZyX2017-02-24
| | | | |
| * | | | buffer: Remove b:changedtick from b: before freeing b:ZyX2017-02-24
| | | | | | | | | | | | | | | Avoids loosing b:changedtick value at `:bdelete`.
| * | | | memory: Free buffers after freeing variablesZyX2017-02-24
| | | | | | | | | | | | | | | Avoids use-after-free crashes when compiling with -DEXITFREE.
| * | | | eval: Do not allocate b:changedtick dictionary itemZyX2017-02-24
| | | | |
| * | | | *: Fix linter errorsZyX2017-02-23
| | | | |
| * | | | api: Make sure dict_set_var doesn’t edit read-only valuesZyX2017-02-23
| | | | | | | | | | | | | | | Fixes #6147
| * | | | api: Rename dict_set_value to dict_set_varZyX2017-02-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reasonings: 1. It is not used for anything, but scope dictionaries currenly. So there is no need to generalize and split it into dict_set_var (which will contain some scope-dictionary-specific checks) and dict_set_value (which will work for any dictionary). 2. Check for key size is no longer valid for non-scope dictionaries: you *can* use empty keys there. In scope dictionaries also, but you actually are not supposed to store there anything, but variables. Note that actually one may still do let b:[''] = 1 and “bypass” check for variable name. It won’t change what `echo b:` will show, but it may affect code which iterates over scope dictionary keys and sets them to something (if there is such code).
| * | | | eval: Remove incorrect workaroundZyX2017-02-23
| | | | | | | | | | | | | | | Was replaced by the previous patch. Also fixes legacy test 055.
| * | | | eval: Forbid (un)locking b:changedtickZyX2017-02-23
| | | | | | | | | | | | | | | Port of vim-patch:8.0.0343
| * | | | eval: Make sure `islocked('b:.changedtick')` does not error outZyX2017-02-23
| | | | | | | | | | | | | | | Port of vim-patch:8.0.0345
| * | | | eval: Specify more precise len for var_check_ro in get_lvalZyX2017-02-23
| | | | |
| * | | | eval: Refactor var_check_ro, tv_check_lock and var_check_fixedZyX2017-02-23
| | | | | | | | | | | | | | | | | | | | | | | | | - They are no longer responble for using gettext. - They now receive string length and use %.* format specifier in messages. - And one less global: one of the error messages is never repeated.
| * | | | eval: Fix memory leakZyX2017-02-23
| | | | | | | | | | | | | | | Ref vim/vim#1497
| * | | | buffer: Forbid unletting b:changedtickZyX2017-02-23
| | | | |
| * | | | eval: Refactor item_lockZyX2017-02-23
| | | | | | | | | | | | | | | If I am not mistaking, this commit should not change any functionality.
| * | | | eval: Make sure that b:changedtick may not be unlocked via :unlo b:varZyX2017-02-23
| | | | | | | | | | | | | | | It still may be unlocked by `:unlock b:.var`.
| * | | | buffer: Bind b:changedtick to b:['changedtick'], remove special casesZyX2017-02-23
| | | | |
| * | | | api/buffer: Add nvim_buf_get_changedtick methodZyX2017-02-23
| | | | |
* | | | | Merge #6111 from ZyX-I/split-eval'/os-fileioJustin M. Keyes2017-02-27
|\ \ \ \ \ | | | | | | | | | | | | Refactor writefile() and create more tests for it
| * | | | | eval: Flush buffer in write_listZyX2017-02-23
| | | | | | | | | | | | | | | | | | This way success/failure return from this function is more precise.
| * | | | | eval: Fix linter errorZyX2017-02-15
| | | | | |
| * | | | | eval: Fix error messages from writefileZyX2017-02-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. When calling writefile(list, fname, []) do not show error message twice. 2. Do not allow file name to be overwritten for writefile([1], 2). 3. Do not show “Can’t open file with an empty name” error after error like “using Float as a String” when type of the second argument is not correct. 4. Do not give multiple error messages and still continue for code like `writefile(["test", [], [], [], "tset"])`. Note that to fix 4. ideally I need tv_check_str_or_nr which is currently present in two PRs: #6114 and #5119. I would want to avoid copying this function into a yet another PR. Ref vim/vim#1476.
| * | | | | eval: Return immediately after an error in write_list()ZyX2017-02-14
| | | | | | | | | | | | | | | | | | Previously it could attempt to write trailing newline before returning.
| * | | | | eval: Remove outdated commentZyX2017-02-14
| | | | | |
| * | | | | eval: writefile: Give more adequate IO errors and do not call putc()ZyX2017-02-14
| | | | | |
| * | | | | os/fileio: Support appending to a fileZyX2017-02-14
| | | | | |
| * | | | | os/fileio: Allow certain failures during file_fsyncZyX2017-02-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | According to the documentation fsync() may fail with EROFS or EINVAL if “file descriptor is bound to a special file which does not support synchronization” (e.g. /dev/stderr). This condition is completely valid in this case since main point of `file_fsync()` is dumping buffered input.
* | | | | | Merge #6142 from justinmk/term-modifiableJustin M. Keyes2017-02-27
|\ \ \ \ \ \ | | | | | | | | | | | | | | terminal: 'modifiable'; 'scrollback'; follow output only if cursor is on last line
| * | | | | | terminal.c/redraw(): Remove cargo cult.Justin M. Keyes2017-02-26
| | | | | | |
| * | | | | | channel.c: loggingJustin M. Keyes2017-02-26
| | | | | | |
| * | | | | | terminal: Follow output only if cursor is at end.Justin M. Keyes2017-02-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Closes #2257 Closes #2636 References #2683
| * | | | | | terminal: 'scrollback'Justin M. Keyes2017-02-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Closes #2637
| * | | | | | options: 'scrollback'Justin M. Keyes2017-02-26
| | | | | | |
| * | | | | | terminal: Allow undo and 'modifiable'.Justin M. Keyes2017-02-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Partial step towards #2637. Will crash if *all* lines are deleted. Closes #2607 References #5431
* | | | | | | vim-patch:8.0.0379James McCoy2017-02-26
|/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: CTRL-Z and mouse click use CTRL-O unnecessary. Solution: Remove stuffing CTRL-O. (James McCoy, closes vim/vim#1453) https://github.com/vim/vim/commit/74a47162a07fddb532f4bead212f6c80ef474ae7
generated by cgit (git 2.34.1) at 2025-07-05 19:18:24 +0000