换行/发送 的不同方式

[superzmy]

我平时不习惯 Enter 直接发送，而是更习惯用 Ctrl+Enter 发送、Enter 换行。
所以我把 deepseek-tui 改成了：Ctrl+Enter 发送，Shift+Enter / Ctrl+J / Enter 换行。
不过我发现，在 Git Bash / mintty 环境下，这些带修饰键的组合似乎无法被正确识别。

在我修改后的版本里：

Git Bash：Ctrl+Enter 不会发送，而是换行；Shift+Enter / Ctrl+J 会发送。
Windows Terminal（稳定版）：行为符合预期，Ctrl+Enter 发送，Shift+Enter / Ctrl+J / Enter 换行。
Windows Terminal Preview： 特殊按键都变成了可见的转义序列无法消费。
根据 deepseek 的分析：

问题不在代码，而在终端。Ctrl+Enter、Shift+Enter、Ctrl+J 在 mintty 中都会被转译成普通的 Enter，所以它们最终都会走到“换行”的分支。

原版之所以看起来像是 Ctrl+Enter 发送，是因为原版里 普通 Enter 就是发送。mintty 把 Ctrl+Enter 里的 Ctrl 吃掉后变成了普通 Enter，于是也进入了发送分支。
所以这并不是“Ctrl+Enter 发送”，而是“普通 Enter 发送，而 Ctrl 被终端吞掉了”。

新版本里之所以都不行，是因为现在 普通 Enter 是换行。所有被 mintty 去掉修饰键的按键（Ctrl+Enter、Shift+Enter、Ctrl+J）都会坍缩成普通 Enter，因此全部变成换行。

mintty 不能很好地区分这些键盘修饰键。这不是 deepseek-tui 在代码层面能够修复的——应用实际收到的只有普通的 KeyCode::Enter，Ctrl 和 Shift 根本没有传到 crossterm。

如果我坚持把 Ctrl+Enter 作为发送键，是否就意味着不同终端环境会出现不同的操作方式？
大家怎么看这个交互方案？

English version
I’m not used to Enter sending messages directly.
My preferred behavior is Ctrl+Enter to send and Enter to insert a newline.
So I modified deepseek-tui to use Ctrl+Enter to send, while Shift+Enter / Ctrl+J / Enter insert newlines.
However, I found that in the Git Bash / mintty environment, these modifier-based shortcuts do not seem to be recognized correctly.

In my modified version:

Git Bash: Ctrl+Enter does not send; it inserts a newline instead. Shift+Enter / Ctrl+J send.
Windows Terminal (stable): behaves as expected — Ctrl+Enter sends, Shift+Enter / Ctrl+J / Enter insert newlines.
Windows Terminal Preview: We could see “[13;133u” etc.
According to deepseek’s analysis:

The issue is not in the code, but in the terminal. Ctrl+Enter, Shift+Enter, and Ctrl+J are all translated by mintty into a plain Enter key — so they all end up taking the newline branch.

Why did Ctrl+Enter send in the original version? Because in the original version, plain Enter triggered send. mintty stripped Ctrl from Ctrl+Enter and turned it into a plain Enter, which also hit the send branch. So it was not really "Ctrl+Enter sends", but rather "plain Enter sends, and Ctrl was swallowed by the terminal."

Why do they all stop working in the new version? In the new version, plain Enter inserts a newline. All keys whose modifiers are stripped by mintty (Ctrl+Enter, Shift+Enter, Ctrl+J) collapse into plain Enter, so they all become newline actions.

mintty does not preserve these keyboard modifiers distinctly. This is not something deepseek-tui can fix — at the code level, what reaches the application is just a plain `KeyCode::Enter`, and the Ctrl/Shift information never makes it to `crossterm`.

If I insist on using Ctrl+Enter as the send shortcut, doesn’t that mean the behavior will differ across terminal environments?
What do you think about this interaction design?