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

create tokens for encountered link definitions #500

Closed
wants to merge 2 commits into from
Closed

create tokens for encountered link definitions #500

wants to merge 2 commits into from

Conversation

grant-g
Copy link

@grant-g grant-g commented Oct 15, 2014

The Eclipse project's Orion [1] markdown editor uses marked both to generate HTML content and to identify the regions in the .md source for syntax styling. Marked's current lack of generated tokens for encountered link definitions makes it impossible for Orion's editor to reliably identify the regions following a link definition.

This pull request creates tokens for encountered link definitions. These tokens do not affect the generated output in any way, but enable a client of marked's lexer to know the link definition's character range, which is the only missing piece to complete mapping from the .md source to the generated .html.

[1] https://orionhub.org/

@KrishnaPG
Copy link

Wondering if this PR resolves this problem: #664 ? or is this something different?

@grant-g
Copy link
Author

grant-g commented Sep 28, 2015

No, #664 is different.

@Feder1co5oave
Copy link
Contributor

+1, I like the idea. Although I would have used link_def instead of def as the type of the items, since it sounds more clear.

@joshbruce
Copy link
Member

Closing as stale, missing tests (??), and merge conflicts. Created issue and flagged as milestone 0.5.0: #1025

@joshbruce joshbruce closed this Jan 21, 2018
@Feder1co5oave
Copy link
Contributor

I could take a look at this, but I'm wondering if it makes sense to have and call a def renderer, since link definitions don't produce any output per se, by spec

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

Successfully merging this pull request may close these issues.

4 participants