diff options
| author | Danilo M. <danix@danix.xyz> | 2026-08-20 12:26:51 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-08-20 12:26:51 +0200 |
| commit | 0496db64c34763c586ffad7d68ed9845a5395452 (patch) | |
| tree | 88d77364de8e704faffcdfbf5e4b4ac3b3fdcb28 /src/tagstrip.cpp | |
| parent | 2e1a6df8fd911ce933f24595be0299ffe3b90d70 (diff) | |
| download | qtmaildir-0496db64c34763c586ffad7d68ed9845a5395452.tar.gz qtmaildir-0496db64c34763c586ffad7d68ed9845a5395452.zip | |
docs: specify the composer's formatting toolbar, item 123
The spec said "the editor is plain text" and left it there, which reads
as "you are on your own with the syntax". Storage format and editing
affordances are separate decisions and only the first was stated.
The toolbar is text transformation over the markdown source, not
rich-text editing: bold, italic, code, strikethrough, link and quote,
selection-aware, with the cursor landing between the tokens when there
is no selection.
Its shortcuts belong to the composer window's own scope and do not
touch KeyMap, which matters for item 132: the two namespaces should not
be conflated when that rule is revisited.
Live syntax highlighting is a follow-up (item 133) rather than part of
this: agreeing with the grammar about nesting and about code spans is
the expensive half, and it is better judged after living with the
toolbar.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YDq53rMd3AQp7QmcZzpuBM
Diffstat (limited to 'src/tagstrip.cpp')
0 files changed, 0 insertions, 0 deletions