-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Newline does not work as expacted #117
Comments
I am away for a short holiday, but I can confirm this is an issue. Will fix asap. |
Fix newline insertion in multi-line widget. Closes #117
Shift enter is still submitting the message for me here on macOS with v0.6.4. I don't think it did this until I upgraded to 0.6 recently. |
@danyalaytekin Can you please let me know which terminal you use? It works fine for me on iTerm. |
Hi @ggozad, this was in the stock macOS 14.6.1 terminal. I've just tested in iTerm too. I should probably switch over entirely but it has never quite caught on... anyway, my results:
|
I found a similar issue. It works fine in Kitty with no multiplexer. Thanks |
Thank you all for reporting how this works across environments. |
#131 allows customizations to key bindings. See the README for how to do that. |
had to use ctrl+enter, on nixos tmux alacritty |
I opened a new windows terminal and made sure oterm is not running anywhere else before.
I am running oterm 0.5.2
Problems:
Clicking newline in multiline mode places newline in the wrong place (from second line onwards)
Pressing shift+enter sends data to ollama
newline position problems
a. Happens only on and after second line. Did not find what are the rules of placement of newline
b. Does not matter if ascii or unicode is used.
Uryvek.1.mp4
The text was updated successfully, but these errors were encountered: