From: Stefan Kangas <stefankangas@gmail.com>
To: Matt Armstrong <matt@rfc20.org>
Cc: 58801@debbugs.gnu.org
Subject: bug#58801: [PATCH] Autoload the `calc-eval-error' variable
Date: Thu, 24 Nov 2022 11:50:56 -0800 [thread overview]
Message-ID: <CADwFkm=C4Py912SUR+Uj_jKjjtFoGZBKovbG+LKOqjOpee6G4w@mail.gmail.com> (raw)
In-Reply-To: <8735ak6pq7.fsf@rfc20.org> (Matt Armstrong's message of "Tue, 15 Nov 2022 10:24:00 -0800")
Matt Armstrong <matt@rfc20.org> writes:
> Note that in my case I had (require 'calc) in the file that used the
> `calc-eval-error' symbol. The info docs for calc state that (require
> 'calc) loads nearly everything you need from calc. I may not understand
> something about the design constraints here, but it seems strange to
> refrain from autoloading this symbol, since (require 'calc) already
> (auto)loads a *lot* of stuff.
So you are saying that if you have a file foo.el, that requires calc,
and then tries to use calc-eval-error variable (documented as part of
the external API), you get a byte-compiler warning?
I agree that this doesn't sound very intuitive.
> My first impression is that adding `defvar' to squash bytecomp warnings
> for symbols in other packages is the wrong default action, and that the
> best idea is for
>
> (require 'foo)
>
> to provide all symbols 'foo-' that one might need when using the `foo'
> package in the normal way.
So I think we could install your patch.
next prev parent reply other threads:[~2022-11-24 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 17:02 bug#58801: [PATCH] Autoload the `calc-eval-error' variable Matt Armstrong
2022-11-11 13:16 ` Stefan Kangas
2022-11-15 18:24 ` Matt Armstrong
2022-11-15 18:42 ` Eli Zaretskii
2022-11-24 19:50 ` Stefan Kangas [this message]
2022-11-26 16:58 ` Matt Armstrong
2023-09-07 7:51 ` Stefan Kangas
2023-11-05 16:38 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=C4Py912SUR+Uj_jKjjtFoGZBKovbG+LKOqjOpee6G4w@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=58801@debbugs.gnu.org \
--cc=matt@rfc20.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.