On 27-5-2011 8:03, Taco Hoekwater wrote:
On 27 mei 2011, at 19:50, Aditya Mahajan wrote:
On Fri, 27 May 2011, Jesse Alama wrote:
Throwing an error would be one way to do this. If throwing an error is not possible, perhaps being
able to customize what gets printed when an undefined refe
On 27 mei 2011, at 19:50, Aditya Mahajan wrote:
> On Fri, 27 May 2011, Jesse Alama wrote:
>
>> Throwing an error would be one way to do this. If throwing an error is not
>> possible, perhaps being able to customize what gets printed when an
>> undefined reference is encountered. E.g., in
On Fri, 27 May 2011, Jesse Alama wrote:
Throwing an error would be one way to do this. If throwing an error is not
possible, perhaps being able to customize what gets printed when an undefined
reference is encountered. E.g., instead of "??", a big, annoying,
impossible-to-miss mark in the ma
On 2011-05-27 17:19:30 +0200, Andreas Schneider said:
On Friday, May 27, 2011 17:09 Wolfgang Schuster wrote:
Am 27.05.2011 um 17:04 schrieb Andreas Schneider:
Hello,
if I use \in, \about, \at or anything else that generates a
cross-reference, and that reference happens to be
On Friday, May 27, 2011 17:09 Wolfgang Schuster wrote:
> Am 27.05.2011 um 17:04 schrieb Andreas Schneider:
>> Hello,
>>
>> if I use \in, \about, \at or anything else that generates a
>> cross-reference, and that reference happens to be invalid (typo or
>> whatever), it just pri
Am 27.05.2011 um 17:04 schrieb Andreas Schneider:
> Hello,
>
> if I use \in, \about, \at or anything else that generates a
> cross-reference, and that reference happens to be invalid (typo or
> whatever), it just prints out "nothing". Is there a way to have
> context throw
Hello,
if I use \in, \about, \at or anything else that generates a
cross-reference, and that reference happens to be invalid (typo or
whatever), it just prints out "nothing". Is there a way to have
context throw an error if a reference is invalid? (That probably would
only m