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

Markdown tags ** and __ are very often neglected #1497

Open
Silvan87 opened this issue May 17, 2017 · 9 comments
Open

Markdown tags ** and __ are very often neglected #1497

Silvan87 opened this issue May 17, 2017 · 9 comments
Labels

Comments

@Silvan87
Copy link

Silvan87 commented May 17, 2017

It would be very useful if markdown tag with bold (**) or italic (__) changed color text. It doesn't work while other text editors do it.

@elextr
Copy link
Member

elextr commented May 17, 2017

Seems whoever made the mappings for markdown mapped lots of syntax elements to the same style in the code instead of mapping each to a different style and left it up to the configuration files to do the mapping.

Pull requests fixing it are welcome.

@elextr elextr added the bug label May 17, 2017
@codebrainz
Copy link
Member

codebrainz commented May 18, 2017 via email

@Silvan87 Silvan87 changed the title Markdown tag with ** or __ doesn't work Markdown tags ** and __ are very often neglected May 18, 2017
@Silvan87
Copy link
Author

So, markdown tags ** and __ do work, but if you have to change colorscheme, this is uncomfortable. Maybe it's better other default choice for markdown colors.

@codebrainz
Copy link
Member

I agree, if someone were to create a pull request against Geany and Geany-Themes to improve it, it would be welcome.

@b4n
Copy link
Member

b4n commented May 20, 2017

The thing is that we don't yet have style that have the semantic of most markup languages, so there isn't something very sensible to map them to. Ideally I guess we'd have additional styles specific for that. I think we had a discussion started about that, but I can't seem to find it just now.
But yeah I guess it makes sense to have those styles, the only problem I know is that it'll break every theme that don't define those new names styles.

@elextr
Copy link
Member

elextr commented May 20, 2017

@b4n, it the new names are defined in filetypes.common won't that be used if the name isn't defined in the colour scheme? Sure it may be ugly, especially for a dark colour scheme, but that will make it obvious that the colour scheme needs updating :)

@codebrainz
Copy link
Member

There was geany/geany-themes#2, but I think it was also discussed somewhere else.

@b4n
Copy link
Member

b4n commented Sep 19, 2018

Since #1837 strong and emphasis styles have respectively the bold or italic property set on them, regardless of the colorscheme. Is that sufficient to close this issue, or some extra styles are indeed required?

@ralf3u
Copy link

ralf3u commented Nov 11, 2021

@codebrainz Excuse me, I have a question to your comment #1497 (comment): How do I make it, that for example **ha ha** is not shown bold in the editor? Thank you in advance for an answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants