| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2018-05-21 | Gather options in a vector when running Buffer::on_option_changed | Maxime Coste | |
| on_option_changed might trigger hooks that will mutate the option managers, invalidating the iterators we use. | |||
| 2018-05-14 | Rename Context::Flags::Transient to Context::Flags::Draft | Maxime Coste | |
| Draft is well establish and all draft context are transient. | |||
| 2018-05-02 | Refactor buffer undo tree | Maxime Coste | |
| Store the undo tree as an array of undo nodes, instead of as a pointer based tree. | |||
| 2018-04-06 | Make error messages more consistent | Delapouite | |
| 2018-03-13 | Do not jump to buffer start on `g.` with no previous modifications | Maxime Coste | |
| 2018-03-09 | Detect no-op replaces and do not act on them | Maxime Coste | |
| This avoids recording no-op undo groups. | |||
| 2018-02-24 | Allow l/h to cross line boundaries | Maxime Coste | |
| l and h are now respectively "next character" and "previous character" | |||
| 2018-02-18 | Buffer: avoid expensive option flattening in on_registred with NoHooks | Maxime Coste | |
| 2018-02-11 | Refuse modification of ReadOnly buffers and make Debug buffer readonly | Maxime Coste | |
| The debug buffer is a bit special as lots of events might mutate it, permitting it to be modified leads to some buggy behaviour: For example, `pipe` uses a ForwardChangeTracker to track buffer changes, but when applied on a debug buffer with the profile flag on, each shell execution will trigger an additional modification of the buffer while applying the changes, leading to an assertion failing as changes might not be happening in a forward way anymore. Trying to modify a debug buffer will now raise an error immediatly. | |||
| 2018-01-18 | Use the _str and _sv string literals more often | Maxime Coste | |
| 2017-11-07 | Buffer: change clamp logic to preserve ordering | Maxime Coste | |
| clamp could change ordering between a coordinate past the end. Say in a buffer with 1 line of 2 char: {0, 1} was clamped to {0, 1} {1, 0} was clamped to {0, 0} That was reversing their ordering, and might be the root cause of the bug lurking in undo range computation. | |||
| 2017-09-01 | Make Buffer::Modification an aggregate | Maxime Coste | |
| 2017-08-29 | Rename containers.hh to ranges.hh (and Container to Range) | Maxime Coste | |
| 2017-08-04 | Purge history on buffer reload when NoUndo flag is on | Maxime Coste | |
| We were preserving the history in that case, so on fifo buffers (that set the NoUndo flag until the fifo is closed), we still had the history from the "previous life" of the buffer, leading crashes when trying to apply it. Fixes #1518 | |||
| 2017-08-01 | Slight formatting tweak | Maxime Coste | |
| 2017-06-28 | Consider non-files buffers as never modified | Maxime Coste | |
| 2017-06-26 | Fix replacing last eol with a single eol | Maxime Coste | |
| 2017-06-15 | Move tolerance for one past end of line coordinates to highlighter code | Maxime Coste | |
| The rest of Kakoune's code now requires coord passed to Buffer::iterator_at to be valid. | |||
| 2017-06-15 | Go back to window lines ending at one past the end of the buffer line | Maxime Coste | |
| Change Buffer::iterator_at so that this case is tolerated, and fixes the coord to next line start instead of clamping to last line char. | |||
| 2017-06-12 | Simplify a bit buffer iteration functions | Maxime Coste | |
| Dont try to ensure the returned value is valid, incrementing past the end/decrementing before begin is the caller's error. | |||
| 2017-06-11 | Fix the Buffer::end() madness | Maxime Coste | |
| Until now, buffer had multiple recognized end coordinates, either { line_count, 0 } or { line_count - 1, line[line_count - 1].length }. Now the only correct end coord is { line_count, 0 }, removing the need for various special cases. | |||
| 2017-06-07 | Run BufCreate hook *before* Buf{Open,New}File | Maxime Coste | |
| 2017-06-07 | Small style tweak | Maxime Coste | |
| 2017-05-26 | Remove unneeded explicit conversion | Maxime Coste | |
| 2017-05-22 | Do not avoid eol in insert mode vertical movement | Maxime Coste | |
| 2017-05-21 | Fix vertical movement with tabstops | Maxime Coste | |
| Fixes #1388 | |||
| 2017-05-07 | Respect tabstop in Buffer::offset_coord | Maxime Coste | |
| 2017-04-20 | Fix generation of empty erase changes | Maxime Coste | |
| Fixes #1308 | |||
| 2017-03-22 | Try to fix clang 3.5 compilation | Maxime Coste | |
| 2017-03-16 | Fixes some clang-tidy warning and add a few missing meta.hh include | Maxime Coste | |
| 2017-03-15 | Small code tweaks regarding flags handling | Maxime Coste | |
| 2017-02-19 | Rename BufNew and BufOpen hooks to BufNewFile and BufOpenFile | Maxime Coste | |
| Fixes #1225 | |||
| 2017-02-07 | Fix Buffer::offset_coord that was dropping the target coordinate | Maxime Coste | |
| 2017-01-31 | Formatting fix | Maxime Coste | |
| 2017-01-30 | Make SharedString::create take a list of StringViews | Maxime Coste | |
| 2017-01-28 | Remove hash from StringData | Maxime Coste | |
| Maintaining the hash value of strings is not worth it as we only use it for buffer reload, but pay for it on any buffer modifications. | |||
| 2017-01-01 | When inserting at the end, store the next line as end pos in the change | Maxime Coste | |
| 2016-11-24 | Forward client name to contexts created for write-all | Maxime Coste | |
| Fixes #937 | |||
| 2016-11-14 | Propagate the hooks disabled state through prompt, menu, and command execution | Maxime Coste | |
| Maintain it as well during buffer creation even if the hooks are not executed in client context. Fixes #818 | |||
| 2016-10-01 | Support codepoints of variable width | Maxime Coste | |
| Add a ColumnCount type and use it in place of CharCount whenever more appropriate, take column size of codepoints into account for vertical movements and docstring wrapping. Fixes #811 | |||
| 2016-09-21 | Tweak Buffer::offset_coord implementation | Maxime Coste | |
| 2016-08-14 | Fix comment missing a closing parenthesis | Maxime Coste | |
| 2016-07-26 | Use explicit initialization of the `timespec` object to fix compilation on ↵ | Frank LENORMAND | |
| older compilers | |||
| 2016-07-24 | Support for going backward/forward in buffer history with <a-u>/<a-U> | Maxime Coste | |
| 2016-07-24 | Support counts for undo/redo | Maxime Coste | |
| 2016-07-24 | Support moving between arbitrary history nodes | Maxime Coste | |
| 2016-07-24 | Store creation timepoint in HistoryNode | Maxime Coste | |
| 2016-07-24 | Store buffer undo/redo information in a tree instead of a vector | Maxime Coste | |
| 2016-07-24 | Merge remote-tracking branch 'lenormf/readonly-mode' | Maxime Coste | |
| 2016-07-23 | Implement a `readonly` mode | Frank LENORMAND | |
| This commit introduces the `readonly` variable as well as the `-ro` command line option which prevent buffers from being overwritten on disk when the `write` command is used without arguments. Some buffers can selectively be put in readonly mode by setting the `readonly` variable on the `buffer` scope, the `global` mode will affect all buffers (even those who will be open subsequently), using the `window` scope will have no effect. Closes #685 | |||
