Buffer directories design change
This commit is contained in:
@@ -1,8 +1,8 @@
|
||||
- What precise workflow do I need for me to be viable to use this?
|
||||
- From a user (novice) point of view, how does it look like?
|
||||
|
||||
|
||||
- build console window
|
||||
- Use WorkDir (raname to Workspace?) to shorten file names
|
||||
- Show what process/coroutines are running and allow to kill (active process buffer?)
|
||||
- Database idea: use special buffers to store information
|
||||
- Editing the buffer doesn't seem to be the slow part rather, accessing the data and putting it into the buffer (potentially hitting many different memory locations) I have a crazy idea to use buffers in order to store the names in a serialized format
|
||||
@@ -19,10 +19,11 @@ Commands TODO:
|
||||
|
||||
- CONSIDER AUTOMATING: CheckpointBeforeGoto
|
||||
- GotoBackward how to handle that in case we want to automate and create on every move?
|
||||
- Add jump checkpoints
|
||||
- Make sure the timing window works forward and backward in undo and jump
|
||||
|
||||
|
||||
backlog
|
||||
ISSUE Ctrl+Alt+Down (DuplicateLine) doesn't work on ubuntu
|
||||
FEATURE Search whole words, case sensitive etc.
|
||||
FEATURE Select all searched occurences
|
||||
FEATURE commands for scrolling: center, cursor_at_bottom_of_screen, cursor_at_top
|
||||
|
||||
Reference in New Issue
Block a user