mirror of
https://github.com/Ark0N/Codeman.git
synced 2026-11-20 04:59:34 +01:00
fix(mobile): Send on Enter placeholder i18n, one-line field on desktop
- input-cjk.js translates its placeholder with CodemanI18n.t(), like the prompt composer, since i18n.js skips <textarea> subtrees; the zh-CN entries now show. - The field only grows on touch devices, where it is position: fixed. On a desktop it sits under the terminal, so growing would shrink the terminal box and resize the PTY on every line; it stays one line and scrolls there. - Input And Voice: a line break needs a hardware keyboard (no Shift+Enter on a phone keyboard, and the extended bar's newline key goes to the CLI). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
57fdb52f7c
commit
3c5b7e2199
3 files changed
+56
-15
No files matched your search
@@ -69,17 +69,19 @@ sequences, so word jumps and history keys keep working.
|
||||
|
||||
On a phone, **Input Field: Send on Enter** (beside CJK input) turns that field into a chat box:
|
||||
typed text stays in it until Enter, so you can scroll the terminal back to a question and edit
|
||||
your answer before sending. Shift+Enter adds a line, Esc clears the field, and autocorrect is on.
|
||||
Enter always goes out as its own write, a moment after the text, to the session the answer was
|
||||
typed for: a single character is typed, so CLI menus that take a digit still work, and anything
|
||||
longer goes like the prompt composer's Send, as one paste. The one exception is a lone digit while
|
||||
a permission or question dialog is waiting: the digit answers the dialog by itself, so no Enter
|
||||
follows it, which would otherwise confirm whatever the CLI shows next. The toolbar's Enter button
|
||||
sends the field too. With the keyboard bar's one-shot Ctrl armed, the next key you type goes out
|
||||
as a control key (Ctrl, then `c` is Ctrl+C) instead of being held. With a hardware keyboard, Ctrl
|
||||
shortcuts (undo, select all, copy) act on the field while it holds a draft and reach the CLI only
|
||||
when it is empty. With the keyboard down the field stays one line tall. A draft stays with its
|
||||
session: switching tabs and coming back brings it back.
|
||||
your answer before sending. With a hardware keyboard, Shift+Enter adds a line (a phone's on-screen
|
||||
keyboard has no Shift+Enter, and the extended bar's newline key goes to the CLI, not the field),
|
||||
Esc clears the field, and autocorrect is on. Enter always goes out as its own write, a moment
|
||||
after the text, to the session the answer was typed for: a single character is typed, so CLI menus
|
||||
that take a digit still work, and anything longer goes like the prompt composer's Send, as one
|
||||
paste. The one exception is a lone digit while a permission or question dialog is waiting: the
|
||||
digit answers the dialog by itself, so no Enter follows it, which would otherwise confirm whatever
|
||||
the CLI shows next. The toolbar's Enter button sends the field too. With the keyboard bar's
|
||||
one-shot Ctrl armed, the next key you type goes out as a control key (Ctrl, then `c` is Ctrl+C)
|
||||
instead of being held. With a hardware keyboard, Ctrl shortcuts (undo, select all, copy) act on
|
||||
the field while it holds a draft and reach the CLI only when it is empty. With the keyboard down
|
||||
the field stays one line tall. A draft stays with its session: switching tabs and coming back
|
||||
brings it back.
|
||||
|
||||
## Voice dictation
|
||||
|
||||
|
||||
Reference in new issue
Block a user