Add logging to the live subcommand for easier debugging.

Metrohash is almost 3x faster than sha1. See file_hash bench.

Metrohash likely has a much higher collision rate than sha1, but the likelihood of collision is low for users due to the data being file contents. The performance win of this change is worth the increased probability of false negatives for detecting if the editor is "dirty".

The output pane height is currently set as the number of output lines. Cap this at some value (~40%) so that it doesn't take over the content area and provide a way to scroll the pane. Allow the user to drag the divider between the editor and output to change the cap %.

Always shrink the output pane to fit the output if that is easier to do.

For scripts that take a long time to run, the user may not want it to automatically re-run the script on every change to the code. Add the ability to disable auto-run. When auto-run is disabled, the user should have the new ability to run the script manually. Like there is currently, once a script is running there is no way to stop it.

Files opened in live mode show the dirty indicator when no changes have been made.

Ratatui does double buffering to efficiently update the terminal by only writing out what changed between draw calls. However, the UI is always redrawn every tick, and Ratatui is an immediate-mode framework meaning that the entire UI must be rebuilt in memory. Most of the time there will be no or few changes, meaning most of the just-created widgets will not be used.

Taking inspiration from the paradigms used in tui-realm, only call Terminal::draw if an event causes a state update. The main loop and event processing may need refactoring to make this easy.

Additionally, gather some metrics to see how this affects performance:

• Measure how long it takes to render per tick
• Monitor CPU usage before/after the change

Enable (full or partial) lint groups:

• clippy::pedantic
• clippy::nursery
• clippy::cargo

See the Clippy website for list of lints.

Currently, if the user presses ^C when any modal is visible it will close the modal. Sometimes users will spam ^C to force quit terminal applications. Support this expected behavior by exiting the app on ^C, but only when in the exit confirmation modal.

Implement with the ropey crate

The current list of commands and their aliases:

• run
• generate/gen
• live
• input-debug
• inline-scroll

Add more aliases:

• r
• g
• l/edit/e
• input/i

In live mode, when ASCII is enabled, it is impossible to tell whether a cell that contains a digit 0-9 is showing:

• its numerical value, or
• its ASCII value that is a digit, i.e. numerical value is 48..=57

The Save As modal should have an initial path that

Initialize the input of the Save As modal with the absolute path of the current file, with -copy appended to the stem of the basename.

e.g while editing the file examples/hello-world.bf, the Save As modal should be initialized with:

/absolute/path/to/examples/hello-world-copy.bf

If that filename exists, try appending -copy-2 to the original stem:

/absolute/path/to/examples/hello-world-copy-2.bf

Increment the number until the path does not exist.

Improve TUI widget rendering.

• Reduce allocations as much as possible
• Improve code clarity
• Separate app ("business") logic from rendering logic:
  • Move the following TUI widgets into crate::widgets:
    • CellWidget
    • ChunkedTapeDisplay (rename to ChunkedTapeWidget)
    • WindowDisplay (rename to TapeChunkWidget)
• Use ratatui for run subcommand

• Add unit tests for logic
• Add snapshot tests for UI widgets

Turn the project into a virtual workspace with crates:

• bf
  • move the module currently at bf::interpreter
  • extract and move the script gen strategies that are currently at bf::commands::generate
• bf_cli
  • rename the current crate to this
• bf_tui
  • move the module currently at bf::widgets
  • maybe the ones at bf::commands::live::widgets too ❓

That leaves bf::util which will get broken up and moved into the correct crate. Anything shared can be moved to bf::utils or a bf_utils crate can be created.

At some point the unsaved changes modal was disabled. This modal would appear when a user requests that the app exit while there are unsaved changes to the file. Re-enable this feature.

Add a warning to the modal that is shown then the textarea value is a filename that exists.

• Make them more ergonomic to use in code
• Improve UI & UX