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
Configure width of output? #54
Comments
(If you'd like details of what I have tried, it's described here: https://clojurians.zulipchat.com/#narrow/stream/151924-data-science/topic/clerk.20questions .) |
You can control the width via the |
Excellent. Thank you!! I will play around with that. Might have a followup question or two. |
Great--thanks very much @mk. |
It seems as if clerk sets the width of the output in the browser to about 800 pixels for text, and about 700 pixels for Vega-Lite images. The images scroll, which is good, but I'd like to be able to make the displayed image width wider. I wouldn't mind being able to do the same with text, too, but I'm more concerned about Vega-Lite width.
i.e. it would be useful to be able to configure the output widths in the browser. Maybe there's a variable or function to do that already. I've looked for it in the docs and source, but haven't found it.
After working on this for a bit, I don't think the width constraint is coming from Vega-Lite or Hanami (which is what I'm using to generate Vega-Lite). I think the width constraint is either in some CSS used by clerk, or some of other code used to generate the output--either in clerk or a library it uses. I looked at the generated HTML in the browser, but it's not very informative. I think it comes from this function. There's a
"clerk"
div--maybe that's what the width constraint is attached to--but I don't know how to figure out how that's happening. I looked at the CSS files that that function uses, but nothing in them that I could recognize was the source of the width constraint. But I don't know CSS well, even for formatted code.Thanks. Not urgent, but it would be nice to be able to configure this.
The text was updated successfully, but these errors were encountered: