Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!sdcsvax!ucsdhub!esosun!seismo!uunet!brunix!jak From: jak@brunix (Jak Kirman) Newsgroups: comp.emacs Subject: Error in init file [was Re: How to define VT2xx...] Message-ID: <1353@brunix.UUCP> Date: 5 Mar 89 18:41:22 GMT References: <36761@bbn.COM> <52705@yale-celray.yale.UUCP> Sender: news@brunix.UUCP Reply-To: jak@cs.brown.edu (Jak Kirman) Organization: Brown University Department of Computer Science Lines: 27 Speaking of Error in init file, I quite agree with Ashwin, this message should be a little more verbose. I think it would be sufficient if adding (setq debug-on-error t) to .emacs made it enter debug-mode when it encountered an error, but for some reason it does not (in Gnu Emacs 18.52). And loading the file after starting up emacs with the -q switch does not always have exactly the same behavior as starting emacs normally. Does anyone know why the setq... does not work, or better yet, how to fix it? While I am here, another point. In many of the elisp functions that I write, I use functions which print messages in the minibuffer. For example, replace-string prints a "Done", some search functions print "Mark set", and so on. Most of the time, I don't want these messages to appear. Is there a simple way of 'redirecting' messages, so that anything written to the minibuffer will not appear? At the moment I have a horrible kludge involving fsetting 'message to a wrapper around the old 'message. This is really not very elegant. I would be grateful for any ideas. Jak Kirman ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ARPA/BITNET : jak@cs.brown.edu Tel : (401) 863 7664 UUCP : ...!{decvax,allegra,ihnp4}!brunix!jak or 7695 Snail : 86 Benevolent St, Providence, 02906 RI. Tel : (401) 272 6149 It ain't what a man don't know that makes him a fool, but what he does know that ain't so. -- Josh Billings