feat: ctrl + o to insert a line break
#62
Merged
Conversation
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
|
Ah this is a nice addition, thanks! Yes the issue is around tui-textarea which doesn't support nice multi line inputs yet. It's being tracked in #16 and rhysd/tui-textarea#5. |
dustinblackman
approved these changes
Mar 16, 2024
|
Thank you for reviewing and accepting my suggestion! |
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.
I’v been using oatmeal for the past several days and have found it to be quite beneficial. However, I believe that the chat functionality could be improved by allowing the insertion of line breaks.
My intention was to configure a key binding using Shift + Enter to insert a line break, but unfortunately, the application does not seem to recognize this.
Additionally, I've tried setting Ctrl + M and Ctrl + Enter as potential key bindings, but these too aren't detected as intended. Instead, the application appeared to recognize them as a simple Enter key press, which results in the message being sent.(Possibly, this could be due to the specifications of tui-textarea...?)
Thank you for considering this enhancement.