Repository navigation
Markdown styling setting, lists that carry on, and Cmd+C that just works - #32
Merged
Merged
Conversation
- Settings has a new "Markdown styling" setting: full (as before), minimal (the markdown symbols faded, the text plain: no bold or italics), or off (plain text). Enter or a click switches between them. - Every setting now says, under it in faded text, what its current value does, and lines separate the settings. - Enter in a list item starts the next one: the same bullet, the next number, an empty task box. Enter on an empty item ends the list. Quotes carry on too. Shift+Enter is a plain new line. - Tab at the start of a list item nests it under the item above; Shift+Tab brings it back out. - On a Mac, Cmd+C copies in any terminal with no setup: selected text goes on the clipboard as soon as it's selected. Typing or pasting over a selection leaves what you'd copied before on the clipboard, and Cmd+V over a selection pastes that. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Minimal now fades the markdown symbols and keeps code green; everything else stays plain (no bold, italics or underlines). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
Author
🚀 Deploying Preview to Cloudflare 🚀Preview Deployments by commit
|
- The selected setting is marked by a bar on its left, instead of a highlighted block. - Settings with a few options show them all, like "on | off" or "full | minimal | off", with the current one highlighted. Pick one with ←/→ or a click; Enter goes to the next. - The minimal markdown styling keeps italics, as well as green code. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
Author
|
Updated:
161 tests pass; clippy and fmt are clean. Checked in the real app: → picks the next option, and a click on "on" switches Nerd Font. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.




Four changes you asked for, plus closing #31 in favour of the three-way styling setting.
What changed
Markdown styling setting. Settings → Markdown styling: full (default, same as before), minimal (the markdown symbols are faded, italics and green code stay; no bold), or off (plain text). Shown as
full | minimal | off. Links still open with Ctrl+click in every mode, and History uses the same styling.Settings explain themselves. Each setting now has a faded line under it saying what the current value does (it changes when the value does), with a line between settings. A bar on the left marks the selected setting (no highlighted block). Settings with a few options show them all (
on | off,full | minimal | off), with the current one highlighted: ←/→ or a click picks one, and Enter goes to the next.Lists carry on. Enter in a list item starts the next one with the same bullet, the next number, or an empty
[ ]task box. Quotes (>) carry on too.3.as a list. Brought back out, it continues the numbering above it.Cmd+C just works. Why nano is different: nano leaves the mouse to the terminal, so the terminal does the selecting, and its Cmd+C copies that. writui handles the mouse itself (that's what makes everything clickable), so the terminal has no selection to copy, and it never passes Cmd+C on. Now anything you select in writui goes on the clipboard right away, so Cmd+C has nothing left to do. To protect what you'd copied before:
Cmd+V already worked: it's the terminal's paste, which writui reads. It only seemed broken because Cmd+C hadn't copied anything. The README's terminal config for passing Cmd+C on to writui is gone, since nothing needs setting up now.
One trade-off: "select, Cmd+C, then type over the selection" leaves the clipboard as it was before you selected. Cmd+X is the way to cut. Also, if the clipboard held an image, selecting text replaces it.
Evidence
cargo test: 160 pass, including new tests for list continuation, nesting and renumbering, the styling levels, the Settings layout and clicks, and the clipboard rules (tests use a fake clipboard).cargo clippy --all-targetsandcargo fmt --check: clean.site/demo.tape) typed-before every bullet, which would now give- - …. I updated it to type the first bullet only and re-recorded it.Try it
gh pr checkout 32 && cargo run(Debug builds use
.dev-data/, passwordwritui-dev.) Try a list with Enter, Tab and Shift+Tab. Presssfor Settings and switch Markdown styling. Then double-click a word in a post and press Cmd+C in Alacritty, and paste somewhere else.Version:
0.19.0.🤖 Generated with Claude Code