Thibaut Lienart
Thibaut Lienart
@rmsrosa pointed out that if you do something like ```` \textoutput{blah} ```julia:blah println("hello") ``` ```` Then there will need to be a "double pass" so that everything is appropriately rendered....
Eg: ```` ```julia:extable #hideall using PrettyTables io = IOBuffer() pretty_table(io, [1 5.0; 2 4.0], ["degree" "bound"], backend=:html); println("~~~", String(take!(io)), "~~~") ``` \textoutput{extable} ````` This can make for a nice demo...
Brought to you by @lucaferranti looks like: https://juliaintervals.github.io/pages/apiDocs/apiIntervalArithmetic/ code: https://github.com/JuliaIntervals/juliaintervals.github.io/blob/fa7f24bc11f988e0ed5812267da1973663005471/utils.jl#L54-L100 could just add a demo point with a screenshot and just link to the code.
The prerendering assumes that `Julia>` highlighting works as well as `Julia-repl>` ; the first one might not be true anymore and the second one was probably never true. There probably...
Kindly suggested by Tim Holy: https://github.com/timholy/SnoopCompile.jl/issues/197#issuecomment-754916697
There's a few things that are problematic: * if the file is not in assets it doesn't quite seem to work * the docstring for `\textinput` should be improved in...
```julia-repl julia> s = """ > hello """ "> hello\n" julia> h = Markdown.parse(s) │ hello julia> Markdown.html(h) "\nhello\n\n" ``` in some cases (e.g. if user wants to use Bootstrap),...
* [x] auto generated site maps (issue #491, PR #631 with docs) -- 0.10.2 * [x] auto generated robots.txt (creds to @remi-garcia, PR #653 ) * [x] improvements to RSS...
Usually only require a bunch of meta tags. Maybe this process could be streamlined by adding one dictionary per standard social media thing with fields corresponding to the key values...
When working on circuitscape.org ; I realised that the geometry wasn't applied properly by Safari and Chromium but was by Firefox. Both Safari and Chrom(e/ium) are affected by `-webkit-*` directives...