Currently, the docs for the Printf standardlib simply mentions it uses "C printf style format specification", but does not specify what that is, nor provides a link to the C printf format.

It would be nice to explain it in the docs.

Currently you have to click on the devtools icon and then toggle errors button.

How do I:

• move a cell?
• delete a cell?
• see the cell's runtime?
• go to the main menu?
• etc

The last few weeks I have to switched to JuMP in order to perform my (optimization) analysis. Having a look at the documentation related to "Query Solutions" I found that you can extract very useful information regarding the optimizations results.

Thus, I was thinking that it would be a nice all of this information to be presented in a table. I understand that not everything is useful for every

Only relevant to pyplot with most recent matplotlib

plot(1:10)
sys:1: MatplotlibDeprecationWarning: Passing the fontdict parameter of _set_ticklabels() positionally is deprecated since Matplotlib 3.3; the parameter will become keyword-only two minor releases later.
sys:1: UserWarning: FixedFormatter should only be used together with FixedLocator
sys:1: MatplotlibDeprecationWarning: Case-i

I found that function mod2pi is not implemented yet, but mod works. Is there any list of implemented functions? Minimal working example is:

using Zygote

# This is working
gradient(x -> mod(x, 2pi), 1.)

# This is not
gradient(x -> mod2pi(x), 1.)

So that other people (like me) can help development of the interactive API. At the moment it is something alien that I Can just use through example. This is not the proper way forward...

(finally found Mouse in interaction/iodevices.jl...)

Hi there. It's my first day coding & I really appreciate this resource and I find it more or less easy to follow. However, I would recommend either providing a link to a glossary or simply having a glossary available for absolute beginners to explain terminology such as those referring to the various data types & examples given. Just to make the language a bit more accessible.

I'm enjoying

It would be handy for all edge operations to have both f(g, e) and f(g, src(e), dst(e)) defined by default on abstract graphs