Implemented a gutter with line numbers for multi-line editing

README.md

@@ -1,18 +1,18 @@
 # shed
 
-A Unix shell written in Rust. The name is a nod to the two oldest Unix utilities — `sh` and `ed` — reflecting the shell's emphasis on a capable built-in line editor alongside standard shell functionality.
+A Unix shell written in Rust. The name is a nod to both `sh` and `ed`. It's a shell with a heavy emphasis on smooth line editing.
 
 ## Features
 
 ### Line Editor
 
-`shed` includes a built-in `vim` emulator as its line editor, written from scratch — not a readline wrapper or external library. It aims to provide a more precise vim-like editing experience at the shell prompt.
+`shed` includes a built-in `vim` emulator as its line editor, written from scratch. It aims to provide a more precise vim-like editing experience at the shell prompt.
 
-- **Normal mode** — motions (`w`, `b`, `e`, `f`, `t`, `%`, `0`, `$`, etc.), verbs (`d`, `c`, `y`, `p`, `r`, `x`, `~`, etc.), text objects (`iw`, `aw`, `i"`, `a{`, `is`, etc.), registers, `.` repeat, `;`/`,` repeat, and counts
-- **Insert mode** — insert, append, replace, with Ctrl+W word deletion and undo/redo
-- **Visual mode** — character-wise selection with operator support
-- **Real-time syntax highlighting** — commands, keywords, strings, variables, redirections, and operators are colored as you type
-- **Tab completion** — context-aware completion for commands, file paths, and variables
+- **Normal mode** - motions (`w`, `b`, `e`, `f`, `t`, `%`, `0`, `$`, etc.), verbs (`d`, `c`, `y`, `p`, `r`, `x`, `~`, etc.), text objects (`iw`, `aw`, `i"`, `a{`, `is`, etc.), registers, `.` repeat, `;`/`,` repeat, and counts
+- **Insert mode** - insert, append, replace, with Ctrl+W word deletion and undo/redo
+- **Visual mode** - character-wise selection with operator support
+- **Real-time syntax highlighting** - commands, keywords, strings, variables, redirections, and operators are colored as you type
+- **Tab completion** - context-aware completion for commands, file paths, and variables
 
 ### Prompt
 
@@ -29,7 +29,7 @@ The prompt string supports escape sequences for dynamic content:
 | `\e[...` | ANSI escape sequences for colors and styling |
 | `\!name` | Execute a shell function and embed its output |
 
-The `\!` escape is particularly useful — it lets you embed the output of any shell function directly in your prompt. Define a function that prints something, then reference it in your prompt string:
+The `\!` escape is particularly useful. It lets you embed the output of any shell function directly in your prompt. Define a function that prints something, then reference it in your prompt string:
 
 ```sh
 gitbranch() { git branch --show-current 2>/dev/null; }
@@ -42,20 +42,20 @@ Additionally, `echo` now has a `-p` flag that expands prompt escape sequences, s
 
 shed's scripting language contains all of the essentials.
 
-- **Control flow** — `if`/`elif`/`else`, `for`, `while`, `until`, `case` with pattern matching and fallthrough
-- **Functions** — user-defined with local variable scoping, recursion depth limits, and `return`
-- **Pipes and redirections** — `|`, `|&` (pipe stderr), `<`, `>`, `>>`, `<<` (heredoc), `<<<` (herestring), fd duplication (`2>&1`)
-- **Process substitution** — `<(...)` and `>(...)`
-- **Command substitution** — `$(...)` and backticks
-- **Arithmetic expansion** — `$((...))` with `+`, `-`, `*`, `/`, `%`, `**`
-- **Parameter expansion** — `${var}`, `${var:-default}`, `${var:=default}`, `${var:+alt}`, `${var:?err}`, `${#var}`, `${var#pattern}`, `${var%pattern}`, `${var/pat/rep}`
-- **Brace expansion** — `{a,b,c}`, `{1..10}`, `{1..10..2}`
-- **Glob expansion** — `*`, `?`, `[...]` with optional dotglob
-- **Tilde expansion** — `~` and `~user`
-- **Logical operators** — `&&`, `||`, `&` (background)
-- **Test expressions** — `[[ ... ]]` with file tests, string comparison, arithmetic comparison, and regex matching
-- **Subshells** — `(...)` for isolated execution
-- **Variable attributes** — `export`, `local`, `readonly`
+- **Control flow** - `if`/`elif`/`else`, `for`, `while`, `until`, `case` with pattern matching and fallthrough
+- **Functions** - user-defined with local variable scoping, recursion depth limits, and `return`
+- **Pipes and redirections** - `|`, `|&` (pipe stderr), `<`, `>`, `>>`, `<<` (heredoc), `<<<` (herestring), fd duplication (`2>&1`)
+- **Process substitution** - `<(...)` and `>(...)`
+- **Command substitution** - `$(...)` and backticks
+- **Arithmetic expansion** - `$((...))` with `+`, `-`, `*`, `/`, `%`, `**`
+- **Parameter expansion** - `${var}`, `${var:-default}`, `${var:=default}`, `${var:+alt}`, `${var:?err}`, `${#var}`, `${var#pattern}`, `${var%pattern}`, `${var/pat/rep}`
+- **Brace expansion** - `{a,b,c}`, `{1..10}`, `{1..10..2}`
+- **Glob expansion** - `*`, `?`, `[...]` with optional dotglob
+- **Tilde expansion** - `~` and `~user`
+- **Logical operators** - `&&`, `||`, `&` (background)
+- **Test expressions** - `[[ ... ]]` with file tests, string comparison, arithmetic comparison, and regex matching
+- **Subshells** - `(...)` for isolated execution
+- **Variable attributes** - `export`, `local`, `readonly`
 
 ### Job Control
 
@@ -126,8 +126,8 @@ imports = [ shed.homeModules.shed ];
 
 ## Status
 
-`shed` is experimental software and is currently under active development. It covers most day-to-day interactive shell usage and a good portion of POSIX shell scripting, but it is not yet fully POSIX-compliant.
+`shed` is experimental software and is currently under active development. It covers most day-to-day interactive shell usage and a good portion of POSIX shell scripting, but it is not yet fully POSIX-compliant. There is no guarantee that your computer will not explode when you run this. Use it at your own risk, the software is provided as-is.
 
 ## Why shed?
 
-This originally started as an educational hobby project, but over the course of about a year or so it's taken the form of an actual daily-drivable shell. I mainly wanted to create a shell where line editing is more frictionless than standard choices. I use vim a lot so I've built up a lot of muscle memory, and a fair amount of that muscle memory does not apply to vi modes in `bash`/`zsh`. For instance, the standard vi mode in `zsh` does not support selection via text objects. I wanted to create a line editor that includes even the obscure stuff like 'g?'.
+This originally started as an educational hobby project, but over the course of about a year or so it's taken the form of an actual daily-drivable shell. I mainly wanted to create a shell where line editing is more frictionless than standard choices. I use vim a lot so I've built up a lot of muscle memory, and a fair amount of that muscle memory does not apply to vi modes in `bash`/`zsh`. For instance, the standard vi mode in `zsh` does not support selection via text objects. I wanted to create a line editor that actually feels like you're in an editor.