Path: utzoo!utgpu!watmath!uunet!tut.cis.ohio-state.edu!cs.utexas.edu!csd4.csd.uwm.edu!bbn!jr@bbn.com From: jr@bbn.com (John Robinson) Newsgroups: gnu.emacs Subject: Re: difficulties with lisp Message-ID: <45058@bbn.COM> Date: 31 Aug 89 14:28:22 GMT References: <8908172214.AA15126@dsys.ncsl.nist.gov> Sender: news@bbn.COM Reply-To: jr@bbn.com (John Robinson) Distribution: gnu Organization: BBN Systems and Technologies Corporation, Cambridge MA Lines: 38 In-reply-to: rbj@DSYS.NCSL.NIST.GOV (Root Boy Jim) In article <8908172214.AA15126@dsys.ncsl.nist.gov>, rbj@DSYS (Root Boy Jim) writes: >? From: Dr R M Damerell (RHBNC) > >? 1. When I try to load-file and the file has syntax errors, I cannot >? see any indication of where the error was detected. Is there any way >? to get this? > >Perhaps a combination of eval-defun and forward-sexp in the buffer to >be loaded will work. I don't know whether debug-on-error works when >loading or not. Use eval-region and binary-search the buffer. Also, debug-on-error ought to help some I think. To check for paren balancing, go to the end of the file and insert a ) . Emacs ought to complain if parens are unbalanced. Then delete that ) and the one before it. Emacs ought to show you a matching paren (check that it's the right one). This assume you are in some form of lisp mode. >? 3. Trying to debug a byte-compiled program, I get byte codes that >? fall off the right hand margin of the backtrace buffer's window. Is >? there a way to tell debug to wrap them onto the next line? > >Well, you can use scroll-left, but who wants to look at byte-code? Find the defun for the function and eval-defun or eval-last-sexp on it. Now it won't be in byte-code any longer. This is also one way to undo a debug-on-entry. Once the code is fixed and re-byte-compiled, load the compiled file to speed it up again. >? R.M.Damerell > > Root Boy Jim > Have GNU, Will Travel. -- /jr, nee John Robinson Life did not take over the globe by combat, jr@bbn.com or bbn!jr but by networking -- Lynn Margulis