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
A new user here had its \use and \begin{document} inverted.
In that case, it turns out that the packages don't even seem to be instantiated. (Just quickly checked, with a print in one of the packages init methods, which didn't show up)
The error message is not too helpful. Well, the fix is obvious...
... yet I think that the weird behavior comes from accepting "fragments" (i.e. documents not starting with a \begin{document}), but it's not clear to me if the resulting behavior was really expected 🐱 -- and it's at best confusing. I understand why accepting fragments (i.e. documents not starting with a "document" or "sile" tag) may have an interest in some workflows, but I'd then question what the intended behavior is, when this occur on the very first input fragment. Packages not being loaded at any point without warning is certainly unexpected.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
A new user here had its
\use
and\begin{document}
inverted.In that case, it turns out that the packages don't even seem to be instantiated. (Just quickly checked, with a
print
in one of the packages init methods, which didn't show up)The error message is not too helpful. Well, the fix is obvious...
... yet I think that the weird behavior comes from accepting "fragments" (i.e. documents not starting with a
\begin{document}
), but it's not clear to me if the resulting behavior was really expected 🐱 -- and it's at best confusing. I understand why accepting fragments (i.e. documents not starting with a "document" or "sile" tag) may have an interest in some workflows, but I'd then question what the intended behavior is, when this occur on the very first input fragment. Packages not being loaded at any point without warning is certainly unexpected.The text was updated successfully, but these errors were encountered: