Skip to content
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

Bug: Header Language icons don't appear even when the option "Always" is selected #271

Open
HusseinBaraja opened this issue Jun 28, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@HusseinBaraja
Copy link

Describe the bug

In a test vault where there are no plugins other than Code Styler, the Header Language Icon doesn't appear.

Bear in mind that the language icon appears in the codeblock preview but not in the note file itself

Steps to reproduce

1- Create a new vault.
2- Install the plugin
3- Change the header settings based on the image above
4- paste the markdown codeblock in a new note

Default Theme, No CSS snippets were loaded

``` python title:Circle
circle = Circle()  # create a circle
circle.set_fill(PINK, opacity=0.5)  # set the color and transparency
```

Expected behaviour

The python language Icon should appear in the header.

Current behaviour

Only the title is displayed in the header.

Environment

Obsidian Version: v1.6.5
Code Styler Version:

  • Plugin Version: v1.1.7
  • Obsidian Version: v1.6.5
  • Platform: Desktop
  • OS: Windows 11
  • Theme: Default
  • CSS Snippets: No

Screenshots

LanguageIcon

PreviewBlock

Here are the Header settings for this example:
Settings

Additional context

@HusseinBaraja HusseinBaraja added the bug Something isn't working label Jun 28, 2024
@HusseinBaraja
Copy link
Author

Nevermind I'm just dumb, I didn't connect the language name to the (```) at the beggining, I assumed it will still work because the code got colored correctly after I put the language name.
Sorry about the issue

@loris-intergalactique
Copy link

Thanks for the resolution nonetheless because it also helped me, I do not think it was dumb because it could be expected Markdown behavior

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants