Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!sdd.hp.com!hplabs!hpl-opus!hpnmdla!darrylo
From: darrylo@hpnmdla.hp.com (Darryl Okahata)
Newsgroups: comp.emacs
Subject: Re: Re: info needed on "message" function
Message-ID: <390004@hpnmdla.hp.com>
Date: 7 May 91 03:14:52 GMT
References: <71902@eerie.acsu.Buffalo.EDU>
Organization: HP Network Measurements Div, Santa Rosa, CA
Lines: 34

In comp.emacs, triantos@acsu.buffalo.edu (Nick B Triantos) writes:

> Hello.  I am trying to make a new function to replace "message",
> which will put the message on the bottom line, but also append it to
> a *message* buffer if a variable is set.  Maybe there's already
> someone else who's done that, but I'd like to try to do it myself.

     Well, just for your information, it's already been done.

-------------------------------------------------------------------------------
;;; log-messages.el - facility to log the output of the "message" function.
;;; 
;;; Have you ever been frustrated by not being able to read an emacs message
;;; because it gets overwritten by another message?  Then this package is for
;;; you.  By setting the user variable "log-messages" to non-nil, you can have
;;; the messages logged for you in the buffer "*Message Log*".
;;; 
;;; The variable "non-logged-message-regexps" lets you filter out messages you
;;; know you don't want logged.  I'm not sure how useful this really is, but
;;; it's there if you want it.
;;; 
;;; Unfortunately, some messages you see in the minibuffer are not produced
;;; using the "message" function, so they will not be logged.
-------------------------------------------------------------------------------

It was posted to gnu.emacs.sources on October 18, 1990.

     -- Darryl Okahata
	UUCP: {hplabs!, hpcea!, hpfcla!} hpnmd!darrylo
	Internet: darrylo%sr@relay.hp.com

DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion or policy of Hewlett-Packard or of the
little green men that have been following him all day.