-
Notifications
You must be signed in to change notification settings - Fork 101
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
How do we use these extensions? #35
Comments
Hi @andreabedini there's a blog post explanining how to load extensions from the CLI: http://asciidoctor.org/release-notes/asciidoctor-1-5-0/#spotlight-load-extensions Let me know if this is working for you, |
And to bring everything together, here's an example of how you would load the emoji inline macro extension:
Note that the Btw, we need a README for this repository that covers (at least) the following information:
We should also cover how these extensions are organized to help people create new ones. ...and eventually, we need to graduate some extension out of the lab once we determine that they are stable and popular. But we'll cross that bridge when we get to it. |
Are you able to load the extensions now @andreabedini? If so, perhaps we can open a new issue to add a proper README. |
hi @mojavelinux @Mogztter sorry for leaving you hanging. I think I did manage to get them working at some point (and in some way). Mine was perhaps a little complaint on the lack of documentation! :) thanks for all your work. I love asciidoc(or) and I want to see it succeed! especially in academia (my industry) where markdown has already some momentum behind (scholarly markdown). |
Nice.
A justified compliant indeed. I'm going to close this and replace it with an issue to create a proper README. |
Closed in favor of #44. |
Asciidoctor version 1.5.2 mentions, in the help, an option to require ruby modules before running
I guess this can be used to load these extensions from the command line but I can't find any documentation about this. Especially it's not mentioned either here or here.
The text was updated successfully, but these errors were encountered: