From: Eli Zaretskii <eliz@gnu.org>
To: "Mark A. Hershberger" <mah@everybody.org>
Cc: 72795@debbugs.gnu.org
Subject: bug#72795: 31.0.50; Make speedbar-add-supported-extension autoloaded
Date: Sun, 25 Aug 2024 07:47:20 +0300 [thread overview]
Message-ID: <86bk1hmco7.fsf@gnu.org> (raw)
In-Reply-To: <aaf91e399be5e811cb929ad29a36a9525923adb5.camel@everybody.org> (mah@everybody.org)
> From: "Mark A. Hershberger" <mah@everybody.org>
> Cc: 72795@debbugs.gnu.org
> Date: Sat, 24 Aug 2024 15:25:40 -0400
>
> On Sat, 2024-08-24 at 22:21 +0300, Eli Zaretskii wrote:
> >
> > Sorry, I don't understand: an autoloaded function is always fboundp,
> > so what do you mean by the above?
>
> My framing was wrong. See the PR I have against powershell.el for an
> example of what I'm trying to do.
>
> It is possible my PR is still wrong and require is the right thing in
> this case (not fboundp), but fboundp at least let's me get past the
> warnings about functions not known to be defined.
The need to (require PACKAGE) before calling functions from that
package is standard Emacs technique. To prevent warnings during byte
compilation you could simply (require 'speedbar). See the node
"Warning Tips" in the ELisp Reference manual for this and related
techniques.
I don't think speedbar or this function are special in any way, so I
don't think we need to do anything about this.
next prev parent reply other threads:[~2024-08-25 4:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 19:12 bug#72795: 31.0.50; Make speedbar-add-supported-extension autoloaded Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-24 19:20 ` Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-24 19:21 ` Eli Zaretskii
2024-08-24 19:25 ` Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-25 4:47 ` Eli Zaretskii [this message]
2024-09-30 0:48 ` Stefan Kangas
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=86bk1hmco7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72795@debbugs.gnu.org \
--cc=mah@everybody.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 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).