You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to have negative filters as well?
For example If I write some code, that I want to use in a Documenter.jl documentation, I could want to enhance keywords to be linked to the corresponding page, for example when speaking about my own Type MyType. In the code for Literate.jl. For both other cases (notebook and plain Julia) I don't want to clutter the notebook/example.
So for example I would write
#md # Now let's use [`MyType`](@ref)
#nb # Not let's use MyType
#jl # Now let's use MyType
but it would be shorter to write for example
#md # Now let's use [`MyType`](@ref)
#!md # Not let's use MyType
to say that the first line should be used in markdown and the second for all other types of renderings.
Of course for this example one could argue that the notebook might want to have just a marked up MyType so that we still need three versions, but then the example would just not fit my feature request ;)
Besides that: The idea of the package is quite nice, thanks for providing it :)
The text was updated successfully, but these errors were encountered:
Ah, I did not see, that they are removed for scripts, that's nice and avoids the double text I had for now;
but actually my main point was to illustrate an #!md
Would it be possible to have negative filters as well?
For example If I write some code, that I want to use in a
Documenter.jl
documentation, I could want to enhance keywords to be linked to the corresponding page, for example when speaking about my own TypeMyType
. In the code forLiterate.jl
. For both other cases (notebook and plain Julia) I don't want to clutter the notebook/example.So for example I would write
but it would be shorter to write for example
to say that the first line should be used in markdown and the second for all other types of renderings.
Of course for this example one could argue that the notebook might want to have just a marked up
MyType
so that we still need three versions, but then the example would just not fit my feature request ;)Besides that: The idea of the package is quite nice, thanks for providing it :)
The text was updated successfully, but these errors were encountered: