Well, I second this. Indeed, modifying the obsidian.css does the trick, but you have to do this everytime you select a new theme, since
obsidian.css get overwritten. So if you switch themes often, or want to try new ones, then every single time you need to re-append the CSS lines to
obsidian.css, and it is painful (especially if you rely on more than one single vault and want to set a new theme for each of your vaults, for instance).
I personnally can’t edit markdown in a non-monospaced font, so I need to do this for every single theme I use
Which solutions would we have?
One would be to have a separate user-only CSS file (say
custom.css) that would not be overwritten when you change theme (only
obsidian.css would be). I believe at least one well-known code editor does this, might be VS Code or Atom, not sure. This would not break the way the theme plugin currently works, and still allow users to customize their CSS without having all their changes overwritten each time they switch theme.
Another one would be to have a dedicated setting for this, but I think it would imply more development work, and I believe that depending on the way the themes are written, this might be more difficult to handle (maybe user would love to use a specific font, but still keep monospace fonts for code blocks for instance, I don’t know… so this seems more complicated).
What do you think?