-
Notifications
You must be signed in to change notification settings - Fork 16
Commands defined by \newtcbox
, \NewTCBox
, and friends
#300
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
Comments
The 10 arguments are more a side-effect than an intended feature. But, I see not reason why it should not be kept that way in future. I will add some remarks in that direction to the documentation. So, for I can confirm the subtle difference |
I should have looked to stackexchange first instead of searching the for the bug myself. Thank you very much! |
Done with version https://github.com/T-F-S/tcolorbox/releases/tag/v6.5.0 |
As documented, a new command
\⟨name⟩
defined by\newtcbox[⟨init options⟩]{\⟨name⟩}[⟨number⟩][⟨default⟩]{⟨options⟩}
or\newtcboxfit
takes⟨number⟩+1
arguments. With current implementation, the last mandatory argument is curried thus\⟨name⟩
can take at most 10 arguments.Will the behavior of "at most 10 arguments" be kept in future releases? If so maybe it's worth being documented, because when reading the docs I got the question, can
⟨number⟩
still be up to 9?`Similarly, a new command
\⟨name⟩
defined by\NewTCBox[⟨init options⟩]{\⟨name⟩}{⟨specification⟩}{⟨options⟩}
and\NewTCBoxFit
now can take at most 10 arguments, as if it was defined with arg-spec⟨specification⟩ m
. (The behavior of taking an extra mandatory argument beyond⟨specification⟩
, is not documented!)Also note a subtle difference: the trailing optional arguments in
⟨specification⟩
, if exist, can still be modified by!
. That is,\NewTCBox\mybox{!o}{}
works while\NewDocumentCommand\mycmd{!o m}{}
errors, because no mandatory arguments can appear after!
-modified opt-arg. Seetexdoc usrguide
, sec. 2.6 "Spacing and optional arguments" for more info.The text was updated successfully, but these errors were encountered: