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

#124: Convert much compiletime configuration to runtime flags #125

Merged
merged 7 commits into from
Jul 13, 2015

Conversation

binki
Copy link
Contributor

@binki binki commented Jul 13, 2015

See issue #124.

I generated a lot of changesets because I converted each configurable item independently to avoid confusing myself.

I also added .gitignore and .dir-locals.el to make working with the code easier for me. I hope you don’t mind—you’re actually using sccs instead of git yourself? :-p

The change I’m most concerned about is the code fencing one as that didn’t translate directly from #if into if (), if you see what I mean regarding the switch () in markdown.c. I think I got the logic right, though maybe you have a better way to lay it out or want to simplify it somehow with a macro.

@Orc
Copy link
Owner

Orc commented Jul 13, 2015

I like all of your changes except for the .gitignore and .dir-locals.el -- I hate cluttering up my baseline with miscellaneous files. Could you split those two out into a separate changeset?

binki added 7 commits July 13, 2015 03:24
Instead of specifying `./configure.sh --with-dl=both`, specify
`-fdlextra` or `MKD_DLEXTRA` at runtime.
This change is more invasive and difficult for me as not all existing
preprocessor directives directly translate to `if () {}`.

Instead of passing `--with-fenced-code` to `configure.sh`, now use
`MKD_FENCEDCODE` or `-ffencedcode`.

The output of `markdown -VV` will now display `FENCEDCODE` if the
feature is enabled and `!FENCEDCODE` if it is disabled rather than
displaying `FENCED-CODE` if the feature is enabled.
Now specify flag `-fidanchor` or `MKD_IDANCHOR` instead of
`./configure.sh --with-id-anchor`. In `markdown -VV` displays as
`IDANCHOR` or `!IDANCHOR` rather than `ID-ANCHOR`.
Instead of `./configure.sh --with-github-tags`, specify `-fgithubtags`
or `MKD_GITHUBTAGS`. Shows up in `markdown -VV` as `GITHUBTAGS`
instead of `GITHUB-TAGS` now.
Instead of `./configure.sh --with-urlencoded-anchor`, now use
`-furlencodedanchor` or `MKD_URLENCODEDANCHOR`.
@binki
Copy link
Contributor Author

binki commented Jul 13, 2015

OK, I pulled those commits out.

Orc pushed a commit that referenced this pull request Jul 13, 2015
#124: Convert much compiletime configuration to runtime flags
@Orc Orc merged commit bde87f6 into Orc:master Jul 13, 2015
@Orc
Copy link
Owner

Orc commented Jul 13, 2015

Danka, and merged!

@binki
Copy link
Contributor Author

binki commented Jul 13, 2015

Thanks!

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.

2 participants