![](https://secure.gravatar.com/avatar/c037e51c81ff40b910e63b6f9dab5230.jpg?s=120&d=mm&r=g)
I suppose because
(1) The word 'breakpoint' didn't come to mind
(2) I'm used to consulting documentation rather than source code in the
first instance
(3) I've never worked in Turing tarpits before
(4) Grepping 'breakpoint' as suggested doesn't turn up anything obvious in
any case -- about 100 instances any of which could be a lead.
I'm getting the impression that there's no real-world distinction between
ConTeXt users and ConTeXt developers.
James
On Wed, Mar 3, 2010 at 8:44 PM, luigi scarso
On Wed, Mar 3, 2010 at 9:41 PM, James Fisher
wrote: Certainly works -- thanks Wolfgang.
Stymies me how people on this mailing list know this stuff -- even a Google search for "setbreakpoints", assuming I knew the command in advance, returns nada. So why don't you grep in base/* ?
-- luigi
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net
___________________________________________________________________________________