From: emacs18@gmail.com
To: 7757@debbugs.gnu.org
Subject: bug#7757: 24.0.50; list-load-path-shadows should be documented in lispref manual
Date: Wed, 29 Dec 2010 10:56:57 -0800 [thread overview]
Message-ID: <qtmlj38l85i.fsf@gmail.com> (raw)
I recently stumbled onto list-load-path-shadows command defined in
shadow.el. This is a very useful command, but it is not mentioned
in the lispref manual. I took a stab at adding it to the manual as
shown by the diff below which adds a few lines at the end of the
"Library Search" node in the manual just after the documentation
of locate-library.
=== modified file 'doc/lispref/loading.texi'
--- doc/lispref/loading.texi 2010-11-18 03:54:14 +0000
+++ doc/lispref/loading.texi 2010-12-29 18:50:23 +0000
@@ -363,6 +363,20 @@
tells @code{locate-library} to display the file name in the echo area.
@end deffn
+@deffn Command list-load-path-shadows &optional stringp
+Display a list of Emacs Lisp files that shadow other files.
+
+If @var{stringp} is non-@code{nil}, returns any shadows as a string.
+Otherwise, if interactive shows any shadows in a ``*Shadows*'' buffer;
+else prints messages listing any shadows.
+
+This function lists potential load path problems. Directories in
+the @var{load-path} variable are searched, in order, for Emacs Lisp
+files. When a previously encountered file name is found again, a
+message is displayed indicating that the later file is ``hidden'' by
+the earlier.
+@end deffn
+
@node Loading Non-ASCII
@section Loading Non-@acronym{ASCII} Characters
next reply other threads:[~2010-12-29 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 18:56 emacs18 [this message]
2011-01-23 20:34 ` bug#7757: 24.0.50; list-load-path-shadows should be documented in lispref manual Chong Yidong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=qtmlj38l85i.fsf@gmail.com \
--to=emacs18@gmail.com \
--cc=7757@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.