cessen/led
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

More notes about how I want undo to work.

Browse Source
This commit is contained in:
Nathan Vegdahl 2020-01-31 20:18:12 +09:00
parent 1b32570b31
commit af71aea299
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ideas.md
View File

@ -2,9 +2,13 @@
- Persistent editing state, so you can close and open a file (or the entire editor) and still keep your unsaved edits. - Persistent editing state, so you can close and open a file (or the entire editor) and still keep your unsaved edits.
- No concept of tabs or open-but-invisible buffers. The only open files are the ones you see. - No concept of tabs or open-but-invisible buffers. The only open files are the ones you see.
- Persistent, infinite undo.
- Auto-file saving by default, so you never have "dirty" buffers. The zed-app workflow. - Auto-file saving by default, so you never have "dirty" buffers. The zed-app workflow.
# Undo
- Persistent, infinite undo.
- The undo command doesn't pop anything off the undo stack, rather it walks back until the user is happy and then pushes that state onto the top of the undo stack. The idea is that you never lose any undo state, even when undoing. This will definitely feel weird to people used to more standard undo systems, but it unlocks the possibility of e.g. only undoing within a selected area, among other things.
# UI # UI
- Split view, but only auto-layout. The user just specifies how many views they want, and the editor figures out how to lay them out. Probably the user can tweak knobs for how the auto-layout works. - Split view, but only auto-layout. The user just specifies how many views they want, and the editor figures out how to lay them out. Probably the user can tweak knobs for how the auto-layout works.