Logger should log to a file as well as displaying certain levels via the user interface.

Need to look into system-independent way to have parameter add/remove the flag

LspClient will be responsible for implementing all protocol functionality (such as knowing if the client should send a didOpen notification to the server or sending the Initialized notification after receiving an Initialize response).

https://crates.io/crates/cargo-make

Will make use of organization provided by lang-server.

Root selection is the entire file. Smallest child selection is a single character.

• h moves to parent selection
• j moves to next selection
• k moves to previous selection
• l moves to child selection

Will need to join with lsp input to get notifications

Note this quote from the LSP overview:

The tool notifies the language server that a document is open (‘textDocument/didOpen’). From now on, the truth about the contents of the document is no longer on the file system but kept by the tool in memory. The contents now has to be synchronized between the tool and the language server.

Probably be an Iterator of Changes?

Idea is that Terminal should know the best way to handle all of the requested changes

Need to review which commands are needed for each CI and which are handled by cache

https://github.com/Microsoft/vscode-languageserver-node/blob/c8ac910730a1f4499333a94f9e6cc25c0155818c/protocol/src/protocol.progress.proposed.md

Requires moving control panel to bottom so that window progress is shown as notifications on top

• --verbose/-v
• --starship_log=level

Maybe we can store the just binary in cache?

Will allow ability to mock file system functionality
blocks #12

Currently, this appears to require a chain() function on Consumer. The idea would be that the first Consumer is used until it returns None, the the second Consumer would be used

Instead of having each Processor return Edits, Processor should modify Pane's state and then Paper washes Pane at the end of the step

blocks #10
blocks #5

• Probably use templates
• No need for separate Modes

Ideal scenario is to use just, so that all scripts can be run locally as well as on github.

For now, waiting on just to become more cross-platform.

Since logging configuration is no longer dynamic, there's no longer a need to keep logging in io. It would be better placed in the root dir to give better visibility into when it is initialized.

Perhaps then it is a URL System or us?

Regarding size, UI should only be responsible for sharing size data with the app. App should be responsible for all appropriate modifications of data

Note that this means app will be responsible for knowing the exact location (row and column) of file contents and correct giving that info to the ui

Display mode

• . = change to command mode
• # = filter by line number
• / = filter by search item
• j = move window 1/4 window down
• k = move window 1/4 window up

Command mode

• <character> = add character to sketch
• BS = remove character from sketch
• Enter = execute command
• <C-C> = return to display mode

commands

• see file
• put
• end

Filter Mode

• Enter = change to action mode
• Tab = stack a new filter
• <C-C> = return to display mode

Line Number filter

• (digits) = line number
• (digits).(digits) range between 2 numbers
• (digits)+/-(digits) = range starting at first number and going 2nd number up or down

Action mode

• i = insert before filter
• I = insert after filter

Edit mode

It's not intuitive that -Index returns a IndexType.

For the negation functionality, it is most efficient to use - because Index ensures that self.0 >= 0 (thus no overflow checking is needed).

One option is to convert to IndexType then negate. However this would rely on the user knowing to use - with an allow(clippy::integer_arithmetic) feature.

Thus it might be better to use a function that returns the same as neg() that is better named. Ex: neg_as_index_type()?

This will allow changing test output of edits to {} instead of {:?}.

cwd is already stored in Terminal. Ideally we find a way to share it with Sheet

Automatic merging when there is only 1 person does not have a significant benefit

https://crates.io/crates/cargo-readme

Instead of retrieving value every time, store it and update when the size is changed.

Current system resets the entire screen to Default, then highlights all of the noise and then highlights the signal.

New system should map out the highlight of each block and then send the appropriate highlight commands such that no address is highlighted twice.