We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
cmd +/-
Normal:
Enlarge:
Zoom out:
/cc @mrnugget
No response
The text was updated successfully, but these errors were encountered:
Just my opinion: I think icons are optional, and I even feel a bit unnecessary(it is noise pollution)
What do you think about this? @iamnbutler I want to hear your thoughts
Sorry, something went wrong.
inline blame: Match icon size to font size in buffer (#11788)
ec65035
This fixes #11311. Release Notes: - Fixed icon in inline git blame entry not changing with the buffer font size. ([#11311](#11311)). Before: ![screenshot-2024-05-14-10 48 49@2x](https://github.com/zed-industries/zed/assets/1185253/4a288cae-a52b-4bee-8681-f1d9ba3b57f3) After: ![screenshot-2024-05-14-10 50 06@2x](https://github.com/zed-industries/zed/assets/1185253/f7a6a608-8ecc-4642-adbd-80858dea75e9)
inline blame: Match icon size to font size in buffer (zed-industries#…
95dd4cc
…11788) This fixes zed-industries#11311. Release Notes: - Fixed icon in inline git blame entry not changing with the buffer font size. ([zed-industries#11311](zed-industries#11311)). Before: ![screenshot-2024-05-14-10 48 49@2x](https://github.com/zed-industries/zed/assets/1185253/4a288cae-a52b-4bee-8681-f1d9ba3b57f3) After: ![screenshot-2024-05-14-10 50 06@2x](https://github.com/zed-industries/zed/assets/1185253/f7a6a608-8ecc-4642-adbd-80858dea75e9)
Successfully merging a pull request may close this issue.
Check for existing issues
Describe the feature
cmd +/-
Normal:
Enlarge:
Zoom out:
/cc @mrnugget
If applicable, add mockups / screenshots to help present your vision of the feature
No response
The text was updated successfully, but these errors were encountered: