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

Add support for internal anchors #17

Open
satyagraha opened this issue Apr 11, 2013 · 6 comments
Open

Add support for internal anchors #17

satyagraha opened this issue Apr 11, 2013 · 6 comments
Milestone

Comments

@satyagraha
Copy link
Contributor

Markdown provides internal anchors for headings, e.g. on GitHub see https://gist.github.com/asabaylus/3071099 (and has finally fixed relative links so they work). Therefore, it would be very useful if this excellent Eclipse plugin provided equivalent functionality by generating such anchors.

You can see what GitHub does by looking at the generated page source for any .md file. I think there has been some debate about whether their implementation is exactly right (it uses the name rather than id attribute), but the principle seems pretty well-established though a bit difficult to track down in a "standard".

@winterstein
Copy link
Owner

Hello,

Thank you for the suggestion.

You can set a different markdown->html converter. The option is
Preferences -> Markdown: Command-line to run markdown.

I believe you can set pandoc to do what you want -- though I have not tested this.

It would be a good idea to integrate your idea into the plugin's normal behaviour. But I'm not sure when I'll have the time to do that.

@paulvi paulvi added this to the 1.2 milestone Jan 12, 2015
@paulvi
Copy link
Collaborator

paulvi commented Jan 12, 2015

Now there is GFMV #18

and the issue can be closed if README or Preference page has enough about how to use alternative markdown->html converter.

Currently it has frightening UNSTABLE in Preferences -> Markdown
(and no path selector)

@victorsegall
Copy link

and the issue can be closed if README or Preference page has enough about how to use alternative markdown->html converter.

Currently it has frightening UNSTABLE in Preferences -> Markdown

(and no path selector)

That separate issue is something I was looking for. When the UI text says "take in a file", and the case is passing the current editor view's markdown file to pandoc, I would need to know a variable which represents the file path to give to pandoc input.

I see that there is a "location" property (variable) in Eclipse, in context of the current file view, and must assume that this is probably available in the context where the command line would run.

@paulvi
Copy link
Collaborator

paulvi commented Mar 24, 2015

I can't tell, maybe @winterstein could, but he looks in seldom.

@victorsegall
Copy link

Answered my above off-topic in #38

@paulvi
Copy link
Collaborator

paulvi commented Mar 26, 2018

1.2 was released, but this is unclosed and planned for 1.2

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

No branches or pull requests

4 participants