Skip to content

Permit CTRL+A #char-specific behavior anywhere, not just at line start.#65

Open
kristomu wants to merge 2 commits intocknave:mainfrom
kristomu:char-editing
Open

Permit CTRL+A #char-specific behavior anywhere, not just at line start.#65
kristomu wants to merge 2 commits intocknave:mainfrom
kristomu:char-editing

Conversation

@kristomu
Copy link
Copy Markdown
Contributor

This fixes #62 and is also reasonably robust. E.g. editing a different part of a commented-out line that also contains #char won't trigger the #char behavior unless the cursor is in the right spot.

kristomu added 2 commits May 21, 2025 19:03
…ent.

For instance, first using CTRL+A to set the character number after
a #char comand to 99, then using CTRL+A again to set it to 100 would
leave the cursor at the last digit, which would cause it to be cut off
if one were to press enter. This change always places it after the last
digit so that pressing enter minimizes one's surprise.
@kristomu
Copy link
Copy Markdown
Contributor Author

I'm not sure what the camelcase/snake case convention is because textedit has both of them, so I just made a guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Char Select (Ctrl+A) doesn't work within #if clause

1 participant