emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: John Foerch <jjfoerch@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: problem caused by eval-after-load "speedbar" [9.3 (release_9.3 @ c:/ProgramData/chocolatey/lib/Emacs/tools/emacs/share/emacs/27.1/lisp/org/)]
Date: Fri, 06 Nov 2020 00:59:08 -0500	[thread overview]
Message-ID: <87ft5nnhzn.fsf@kyleam.com> (raw)
In-Reply-To: <CAEeGWGKfrV7w9qtPRpAhFtiOCH-+8_ydEe11EoMAkUkbTq1fuA@mail.gmail.com>

John Foerch writes:

> Hello,
> I was getting the following error on emacs startup:
>     Symbol’s function definition is void: speedbar-add-supported-extension
> However, I noticed that 'eval-after-load can take either a filename or a
> feature symbol as its argument.  If the string "speedbar" were changed
> to the symbol 'speedbar, the eval form would be triggered by speedbar's
> 'provide form, not only loading a file that happened to be called
> "speedbar.el"

Thanks for the report and suggested fix.  I've switched this spot and
others over to using a symbol (51c4cc1a8).

      reply	other threads:[~2020-11-06  5:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30 14:07 Bug: problem caused by eval-after-load "speedbar" [9.3 (release_9.3 @ c:/ProgramData/chocolatey/lib/Emacs/tools/emacs/share/emacs/27.1/lisp/org/)] John Foerch
2020-11-06  5:59 ` Kyle Meyer [this message]

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ft5nnhzn.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jjfoerch@gmail.com \


* 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


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).