On Fri, Aug 1, 2008 at 12:13 PM, Will Robertson <wspr81(a)gmail.com> wrote:
On 02/08/2008, at 2:07 AM, Charilaos Skiadas wrote:
But does it happen often that you find the typing of "h" to be
helpful at all? I've never found TeX's
helpful suggestions all that
helpful personally. Either the error is obvious enough from the
message, or it is too complex for the message to be helpful. But I
guess your mileage may vary.
No, you're right that 'h' often does supply very much useful information :)
When writing macros and packages, however, I'd prefer it to stop at the
first instance of the error for three reasons:
1. Easier to see where it was! And no time waste with TeX trying to
recover from the error and continue typesetting.
2. Sometimes writing diagnostic information with the 'i' function is
3. In looping-like behaviour, I like to put in commands like
\show\somemacro to see what the value of something is. It's generally easier
to interpret this information in "real time" rather than have TeX run
through the whole document before working out what's going on.
Ideally, there'd be an option to have TextMate compile documents in a
similar way to TeXShop, stopping at errors and allowing input, but I can
understand that's either non-trivial or even impossible with the current
Well, now that you have thrown down the 'TeXShop does it' gauntlet I am
going to have to do some experimenting. :-) I think I might be able to get
what you want to work by detecting the error and the prompt and then using
dialog to get a response. I know I can create two way communication with
I didn't ever think to do it before because I never run in interactive mode.
I'll let you know what I figure out.
textmate mailing list