Reputation
696
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
3 13
Newest
 Yearling
Impact
~11k people reached

  • 0 posts edited
  • 0 helpful flags
  • 63 votes cast
Mar
29
comment Strange error message due to xparse and \newenvironment
@JosephWright: In the meantime, is there a way to revert to an older version of the package?
Mar
29
comment Strange error message due to xparse and \newenvironment
I don't think the externalization is causing the issue. Everything was working fine until I updated all packages to their latest version with tlmgr update --all. After that something broke and I started getting this error. I haven't been able to compile my document since.
Mar
29
comment Strange error message due to xparse and \newenvironment
Just updated my question with more code. I hope this is useful (some less important pieces are included from other files so they are missing).
Mar
29
revised Strange error message due to xparse and \newenvironment
more code - I hope this helps
Mar
29
comment Strange error message due to xparse and \newenvironment
When I use \DeclareExpandableDocumentCommand in my code, I get a completely non-informative error message: ! Undefined control sequence. \hyper@makecurrent ...activestrue \edef \Hy@param {#1}\ifx \Hy@param \Hy@cha... l.232 } ?
Mar
29
comment Strange error message due to xparse and \newenvironment
I just read up about the distinction between expandable and non-expandable (I wasn't familiar with this before). My \foo command is definitely not expandable since it involves variables and a counter.
Mar
29
comment Strange error message due to xparse and \newenvironment
I will try to distill the relevant part...
Mar
29
comment Strange error message due to xparse and \newenvironment
It calls something that generates a TikZ figure (which is later externalized).
Mar
29
comment Strange error message due to xparse and \newenvironment
\DeclareExpandableDocumentCommand indeed fixed the problem in the code snippet I posted, but it doesn't work in the original larger file which is much more complicated (among other things this code externalizes TikZ figures).
Mar
29
asked Strange error message due to xparse and \newenvironment
Aug
29
awarded  Yearling
Jul
30
accepted I redefined \- but it does not work in captions
Jul
30
asked I redefined \- but it does not work in captions
Jan
31
awarded  Autobiographer
Dec
3
awarded  Popular Question
Nov
20
awarded  Popular Question
Aug
29
awarded  Yearling
Jul
2
awarded  Curious
May
12
accepted Error using \newcommand within a beamer frame
May
8
comment Error using \newcommand within a beamer frame
That's what I did when I realized that this is what was causing my presentation not to compile. I just wonder why is it the case and whether it should be considered as a bug in beamer.