feat(treesitter): add styles.miscs to disable hardcoded italics

[GotaLoveFiraCode]

Set everything to O.styles.conditionals or { "italic" }, so, by default, the various settings are still italic. In other words, this is not a breaking change.

🎉 First off, thanks for taking the time to contribute! 🎉

Here are some guidelines:

• Format code using stylua.
• New plugin integration should be added in alphabetical order:
  • to the README (vimdoc is auto-generated).
  • to types.lua
• Create a topic branch on your fork for your specific PR.
• Use conventionalcommits.org's
  rules for explicit and meaningful commit messages.
• If it's your first time contributing to a project, then read
  About pull requests
  on Github's docs.

Here are some tips:

• Use vim.g.catppuccin_debug = true to get live config re-loading

[mrtnvgr]

Catppuccin compiles your configuration to simple colors, it helps to reduce start up time. no_italic (as well as other no_... options) removes all italic from highlight groups on compile time. If you still have italics, we should debug that code.

[lucario387]

This isn't a conditional though?. You can always just style = {} in userconfig or is it not

[GotaLoveFiraCode]

This precisely is the problem; the user’s config does not override this setting. That’s what I changed, by binding the setting for @module to the users setting for conditionals (which, by default, is also italic). This way the user can change if modules are italic or not, while the default of italic is still preserved.

[GotaLoveFiraCode]

Catppuccin compiles your configuration to simple colors, it helps to reduce start up time. no_italic (as well as other no_... options) removes all italic from highlight groups on compile time. If you still have italics, we should debug that code.

Hello! Sorry for taking so long to reply, I’ve been traveling.
When setting no_italic, everything works as expected.
What I am trying to fix with this PR is that it is impossible to control the italics that catppuccin’s treesitter integration sets. An example is anything treesitter thinks of as a module will become italic (e.g. in mod somemodule in rust, the somemodule would be italic), even if the user doesn’t want it to be italic. Currently, the only option is to have all modules (among other things) be italic, or turn italics off completely with no_italic—there is no way for the user to control modules specifically. Ideally, there should be a setting in styles in the setup call, so the user can control, independently of catppuccin’s treesitter integration, if modules should be italic or not. For now, though, setting modules to the users conditionals setting is easier and keeps the same default.

[rewhile]

You can now do

require("catppuccin").setup { styles = { miscs = {} } }

To disable the remaining hardcoded styles