feat: add app-specific line break handling for o and +o in insert mode - #130
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
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.
Some applications, such as ChatGPT, use Enter to send a message and require Shift+Enter or Ctrl+Enter to insert a line break.
In Normal mode, vim_ahk currently sends Enter when executing
oorO. In these applications, this may send the current message instead of opening a new line.This PR adds the
VimShiftEnterandVimCtrlEnterapplication groups and uses the appropriate key combination when handlingoandO.For now, these groups are hard-coded, so users need to edit the vim_ahk script directly to add or change applications.
Current list:
Making these groups configurable from the settings window would be useful. However, adding more application-specific options there would make the window increasingly complex, while several other settings also remain hard-coded. A separate configuration mechanism may eventually be needed to manage these settings (#129).
Partially addresses #128.