Added a markdown file to keep track of overall ideas for led.
This commit is contained in:
parent
e6a7d26dbd
commit
1b32570b31
11
ideas.md
Normal file
11
ideas.md
Normal file
|
@ -0,0 +1,11 @@
|
|||
# General
|
||||
|
||||
- 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.
|
||||
- Persistent, infinite undo.
|
||||
- Auto-file saving by default, so you never have "dirty" buffers. The zed-app workflow.
|
||||
|
||||
# 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.
|
||||
- Only text-wrapped views, no horizontal scrolling. But the text wrapping needs to be good, e.g. preserving indent level etc.
|
23
todo.md
23
todo.md
|
@ -1,23 +0,0 @@
|
|||
- Syntax highlighting:
|
||||
- It's tempting to want to do syntax highlighting only on the bare
|
||||
minimum parts of the text after an edit, but realistically there
|
||||
are always cases where the entire text has to be scanned again to
|
||||
get correct results. So it must be something that can be done
|
||||
asynchronously.
|
||||
- Maybe a quick-n-dirty local update, followed by an async background
|
||||
update.
|
||||
- Should the syntax highlighting data be stored in the text buffer itself?
|
||||
Or should there be an accompanying structure on the side for that?
|
||||
- What do other editors do?
|
||||
|
||||
- Text encoding support:
|
||||
- Buffers need to know what encoding they represent.
|
||||
- Loading/saving code for different encodings.
|
||||
- Auto-detecting text encodings from file data (this one will be tricky).
|
||||
|
||||
- Word wrap.
|
||||
- Get non-wrapping text working again.
|
||||
- File opening by entering path
|
||||
- UI that wraps editors, for split view.
|
||||
- Persistent infinite undo
|
||||
- "Projects"
|
Loading…
Reference in New Issue
Block a user