I found what I consider a bug in startcombination processing. context version used: version: 2013.09.03 16:23 Examples: 1.) Good compilable source and 2.) source that fails The bad thing about this is that one, at least checks and checks syntax for errors and the error in fact is simply a blank line, which doesn't stand out as a syntax error in my mind, expecially when white space is supposed to be ignored by tex/context in usual modes. Has this been noticed before? ---------------- The below works successfully \starttext \placefigure [here,none] [fig: reference tag] {citation text} { \startcombination[1*2] {\externalfigure[test-image.png][width=34mm]}{} {\externalfigure[test-image.png][width=34mm]}{} \stopcombination } \stoptext ---------------- The below fails \starttext \placefigure [here,none] [fig: reference tag] {citation text} { \startcombination[1*2] {\externalfigure[test-image.png][width=34mm]}{} {\externalfigure[test-image.png][width=34mm]}{} \stopcombination } \stoptext ------------------this failure prints out the following in the log file. system > tex > error on line 8 in file /tmp/minexp.mkiv: Missing { inserted ... system > tex > error on line 1 in file /tmp/minexp.mkiv: You can't use ` ... system > tex > error on line 2 in file /tmp/minexp.mkiv: Undefined control sequence ... The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. )) ! Emergency stop. system > tex > error on line 0 in file : Emergency stop ... % END