From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Drew Adams <drew.adams@oracle.com>
Cc: 17832@debbugs.gnu.org
Subject: bug#17832: 24.4.50; `apropos-library' behavior for a top-level library file
Date: Mon, 23 Jun 2014 09:00:33 -0400 [thread overview]
Message-ID: <jwv38eviy4b.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <b137d4d2-e543-4527-ab52-4c6c115be49a@default> (Drew Adams's message of "Sun, 22 Jun 2014 09:15:52 -0700 (PDT)")
> Rather than just saying that the command is misnamed, or the name is
> misleading, the first part of this bug report is to request that the
> command live up to its name: give you a report of the functions and
> variables defined in the _whole library_, recursively including those
> of its required component libraries.
Many libraries will then appear to define all the CL macros&functions.
To do a better job, we'd need to distinguish the case where it
"requires" some other library for internal use compared to the case
where it requires a file which is conceptually part of the same library
(just split over several files).
The most common case, AFAICT, is the first, so I think in doubt it's
better to assume "requires" aren't really part of the library.
> As a first and partial bug fix then, I propose that `apropos-library'
> always print TEXT (which it does when there are defined symbols in the
> file).
Sounds good.
Stefan
next prev parent reply other threads:[~2014-06-23 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 16:15 bug#17832: 24.4.50; `apropos-library' behavior for a top-level library file Drew Adams
2014-06-23 13:00 ` Stefan Monnier [this message]
2014-06-23 14:39 ` Drew Adams
2021-07-14 10:13 ` Lars Ingebrigtsen
2021-07-14 14:31 ` bug#17832: [External] : " Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv38eviy4b.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=17832@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).