feat: implement backslash multiline input feature#102
Open
nicoovh wants to merge 1 commit into
Open
Conversation
- Added support for \+Enter to insert newlines instead of submitting - Updated help text to document multiline support - Implemented proper newline handling in input processing - Added cleanup of backslash markers when submitting input
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR will add the possibility to use +enter to go to next line, for terminal+OS combination that fails into typing ALT+Enter, such as MacOS + iterm2 with FR keyboard.
I propose to use the claude's method, +enter
see attached gif
this may fix #7