<div dir="ltr">Yep, I'm using the TTY interface. I cannot reproduce it in the LKB interface either. <div><br></div><div>While I do dabble in lisp from time to time -- thanks to your successful proselytizing :-) -- I mainly use the TTY interface because it's faster than using the LKB, thanks to all the emacs bindings I've set up for loading specific grammars and reparsing the last string etc.<div> <br></div><div style>And yes, :reset did the trick. Thanks a lot for the tip. Much nicer than having to restart LOGON.</div><div style><br></div><div style>Ned</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote"> On Fri, May 10, 2013 at 3:15 PM, Stephan Oepen <span dir="ltr"><<a href="mailto:oe@ifi.uio.no" target="_blank">oe@ifi.uio.no</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> great, thanks, ned!<br> <br> i can reproduce the issue, though only when parsing from<br> the Lisp prompt, i.e.<br> <br> (lkb::do-parse-tty "der man leyen-t dos bukh")<br> <br> as someone who programs in lisp, i suspect that is what<br> you usually do? if so, the error goes away when i leave<br> the error context, i.e. type ‘:reset’ to the lisp prompt.<br> <br> when going through ‘Parse|Parse input ...’, i cannot get<br> nested unification contexts using your grammar; is there<br> more to the recipe? or are actually those students who<br> have run into this problem all using the TTY interface?<br> <br> best, oe<br> <div class="HOEnZb"><div class="h5"><br> <br> On Fri, May 10, 2013 at 11:42 PM, Ned Letcher <<a href="mailto:nletcher@gmail.com">nletcher@gmail.com</a>> wrote:<br> > I've been able to reliably reproduce this -- at least on my machine. This<br> > error seems to occur following a parse that was aborted due to running out<br> > of edges. ie:<br> ><br> > "Probable runaway rule: parse/generate aborted (see documentation for<br> > *maximum-number-of-edges*)"<br> ><br> > Once this has occurred it seems that anything that then involves unification<br> > results in the nested unification error, such as parsing, or loading a<br> > grammar.<br> ><br> > I've attached a grammar that will give the max edges error if you try to<br> > parse "der man leyen-t dos bukh". Then you can reload the grammar or try to<br> > parse the string again to get the nested unification error.<br> ><br> > Ned<br> ><br> ><br> ><br> > On Fri, May 10, 2013 at 6:04 AM, Ann Copestake <<a href="mailto:Ann.Copestake@cl.cam.ac.uk">Ann.Copestake@cl.cam.ac.uk</a>><br> > wrote:<br> >><br> >><br> >> in case it helps - I recollect that error message as turning up in highly<br> >> misleading contexts. The ones I remember were code bugs - feature<br> >> structure<br> >> creation not being called correctly. These could potentially turn up in<br> >> lkb/user-fns.lsp as well as in the main code, so if that's been modified,<br> >> I'd<br> >> be suspicious.<br> >><br> >> Best,<br> >><br> >> Ann<br> >><br> >><br> >><br> >><br> ><br> ><br> ><br> > --<br> > <a href="http://nedned.net" target="_blank">nedned.net</a><br> </div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><a href="http://nedned.net" target="_blank">nedned.net</a> </div>