Re: log full path of magically loaded files?

[Barry Margolin <barmar@alum.mit.edu>]

In article <5315d3ad-be2e-4ec9-9acb-87aa7d92bd71@googlegroups.com>,
 danmbox@gmail.com wrote:

> > It's not all that strange.  *Messages* records the stream of predominantly
> > 1-line messages which appear in the echo area.  It's not intended as a
> > general system log.  Too much uninteresting stuff in the echo area could
> > be distracting and a nuisance.  Usually the exact path of a loaded library
> > is uninteresting.
> 
> I'm not going to argue with "it is the way it is"; but the argument that an 
> automagically triggered action is "uninteresting" and thus not to be logged 
> (while a command explicitly issued by the user somehow deserves to be logged) 
> isn't very convincing. Thanks anyway!

One of the documented differences between load and require is that 
require doesn't display a message saying what it's doing. If it doesn't 
display anything, it won't go in *Messages*.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***