home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: gnu.emacs.help
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!wupost!gumby!destroyer!ncar!sunny!southern
- From: southern@sunny.NoSubdomain.NoDomain (Lawrence Buja)
- Subject: Re: another .emacs problem
- Message-ID: <1992Sep2.185341.22805@ncar.ucar.edu>
- Sender: news@ncar.ucar.edu (USENET Maintenance)
- Reply-To: southern@ncar.ucar.edu
- Organization: National Center for Atmospheric Research
- References: <1992Sep1.182617.15356@engage.pko.dec.com> <1992Sep1.195517.18971@ncar.ucar.edu> <1992Sep2.154319.15711@den.mmc.com>
- Distribution: usa
- Date: Wed, 2 Sep 1992 18:53:41 GMT
- Lines: 29
-
- In article Kevin Rodgers writes:
- >In article southern@ncar.ucar.edu writes:
- >>I don't know what's biting you, but an invaluable emacs debugging
- >>function that might pinpoint it is available by setting:
- >>
- >>(setq stack-trace-on-error t) ; Trace errors in other window
- >
- >Set debug-on-error instead. From the (elisp)'Internals of Debugger'
- >info node:
- >
- >| * User Option: stack-trace-on-error
- >|
- >| ...
- >|
- >| We consider this feature to be obsolete and superseded by the
- >| debugger itself.
-
-
- I've looked at debug-on-error, but found it's tendency to get trapped
- in infinite loops when it tries to debug loading errors to be unacceptable.
-
- stack-trace-on-error gives me enough infothat I really haven't felt
- the need to revisit debug-on-error. I hope stack-trace-on-error doesn't
- get axed from future releases
-
- /\ Lawrence Buja Climate and Global Dynamics Division
- \_][ southern@ncar.ucar.edu National Center for Atmospheric Research
- \_________________________Boulder,_Colorado___80307-3000__________
-
-