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 markdown highlighting #97

Merged
merged 1 commit into from
Aug 3, 2017
Merged

add markdown highlighting #97

merged 1 commit into from
Aug 3, 2017

Conversation

KristofferC
Copy link
Owner

Closes #96

@KristofferC KristofferC merged commit 7280583 into master Aug 3, 2017
@KristofferC KristofferC deleted the kc/markdown branch August 3, 2017 12:09
HIGHLIGHT_MARKDOWN = Ref(true)
enable_highlight_markdown(v::Bool) = HIGHLIGHT_MARKDOWN[] = v

function Base.Markdown.term(io::IO, md::Base.Markdown.Code, columns)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isn't this going to interfere with Documenter?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How and why?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

by shadowing base code on base types

@KristofferC
Copy link
Owner Author

I guess you are saying that Documenter calls into the terminal renderer for markdown? Does it?

@tkelman
Copy link
Contributor

tkelman commented Aug 3, 2017

Looks like it doesn't. The Atom or VS Code plugins might?

@KristofferC
Copy link
Owner Author

KristofferC commented Aug 3, 2017

Atom renders Markdown (in e.g. the help) using the HTML renderer and VS Code runs all their stuff in a sandboxed environment (not sure what they use).

@tkelman
Copy link
Contributor

tkelman commented Aug 4, 2017

Maker.jl and Lexicon.jl appear to use Markdown.term

@KristofferC
Copy link
Owner Author

Oh, the docpackage deprecated in 0.4 uses it, hmmm. As to maker, I guess it will be slightly better when used with OMR.

The whole point of this package is to experiment with new behaviour.if people don't love it they can disable the feature or uninstall the package.

@KristofferC
Copy link
Owner Author

By using this package the user says that he/she rather have the OMR defaults than the defaults in Julia. You might as well consider it a super lightweight fork of Julia but Julia is so flexible that instead of me having to ship the full Julia distribution, I can just ship the diff of my "fork" vs the Base Julia and Julia will monkey patch it in for me.

bad idea, awful hacks, ..., Hiding actual problems, ..., suppress legitimate warnings

You are using quite negative words about my package that I have spent a lot of time, effort and care to implement and I have tried my best to provide a good user experience and quickly fix any problems users have had. I have also been a good boy and upstreamed many of the changes that were first tried out here in this package to Base Julia, just like you are supposed to do (package -> Base).

I am tired of having these discussions every time I add a feature to this package. I know you don't like it, it has been noted but I won't be having this discussion again.

Repository owner locked and limited conversation to collaborators Aug 4, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants