-
Notifications
You must be signed in to change notification settings - Fork 0
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
Bring inputter split from master into native-markdown-improvements branch #1
Bring inputter split from master into native-markdown-improvements branch #1
Conversation
With the latter allowing language selection, smallcaps and underlining
And also a huge refactor/clean-up
27d8ccd
to
ced1e7f
Compare
The GitHub UI is not doing us any favors here. This is literally just 1 commit ahead of your branch—a merge from master with the relevant conflicts fixed so everything moves to the expected places. |
ced1e7f
to
cd32002
Compare
I just added a start to some busted tests to see if we get the AST we expect for a given input. The AST coming out of these seems to be nested a little deeper than it needs to be, but I haven't looked into it in detail yet. |
cbe64e9
to
dd81035
Compare
dd81035
to
6e56fb2
Compare
6e56fb2
to
dbc6e55
Compare
dbc6e55
to
eaeabad
Compare
I think I have taken into account most of the things from this PR in my last rebase, regarding the inputter/package split, etc. Keeping this PR open for now, however, as a reminder to check the busted test logic. |
104adae
to
a154871
Compare
Main ideas from this PR used in the latest version => Closing. |
This is the work I did to merge the core layout changes (notably having inputters be first class pluggable modules) into your work on the markdown class. See sile-typesetter#1481 for further comments.
Note especially the current usage for this would work like so:
With the inputter automatically setting up the markdown document class as part of it's hard coded AST.