-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace the tab key with 4 spaces in olstoy editor #1875
base: main
Are you sure you want to change the base?
Replace the tab key with 4 spaces in olstoy editor #1875
Conversation
|
Signed-off-by: Ryan Bottriell <[email protected]>
b266b55
to
7cc2a5e
Compare
Sounds like ILM is going to handle the dev days CLAs all together in the coming days, but I'm aware that it needs to be done here still |
auto replacement | ||
= QKeyEvent(QEvent::KeyPress, Qt::Key_Space, | ||
Qt::KeyboardModifiers(event->nativeModifiers()), | ||
" "); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm, in most editors, does TAB do the equivalent of hitting SPACE 4 times? Or does it do the number of spaces to take you to the next 4-space boundary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, I'm not sure why I didn't think of that. I'll take another look when I have a moment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ping just in case you're interested in fixing this up.
Description
Updates the osltoy application to use 4 spaces in the editor window instead of tab characters.
Tests
I'm not sure that this change warrants a test case, but I did launch the application and ensure that the tab key does indeed insert 4 spaces into the exitor.
Checklist:
already run clang-format v17 before submitting, I definitely will look at
the CI test that runs clang-format and fix anything that it highlights as
being nonconforming.