From: "T.V Raman" <raman@google.com>
To: eliz@gnu.org
Cc: raman@google.com, emacs-devel@gnu.org
Subject: Re: Possibly add autoload cookie in iimage.el
Date: Sat, 30 Dec 2023 11:39:28 -0800 [thread overview]
Message-ID: <26000.29168.891991.646800@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <834jfz4ltz.fsf@gnu.org>
not sure as to what to say; it was triggering for me on the following
files:
1. https://github.com/tvraman/emacspeak/blob/master/lisp/emacspeak-eww.el#L1
2. https://github.com/tvraman/emacspeak/blob/master/lisp/emacspeak-url-template.el#L1
3. /usr/local/google/home/raman/emacs/lisp/emacspeak/wizards.el
I inferred eww since that was common to all 3; for now I've
just moved past it with an appropriate declare-function in
those modules.
I mostly reported it thinking it might help avoiding future
problems.
Eli Zaretskii writes:
> > From: "T.V Raman" <raman@google.com>
> > Date: Sat, 30 Dec 2023 09:43:05 -0800
> > Cc: raman@google.com,
> > emacs-devel@gnu.org
> >
> > As I said earlier, when compiling .el files that (require 'eww)
>
> Thanks. But I don't seem to be able to reproduce this. I created a
> file which has a single line:
>
> (require 'eww)
>
> and byte-compiled it, but didn't see any warnings. So would you mind
> showing a minimal Lisp file that does trigger a warning when
> byte-compiled? Then I could investigate why the warning is being
> emitted.
--
next prev parent reply other threads:[~2023-12-30 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 16:31 Possibly add autoload cookie in iimage.el T.V Raman
2023-12-29 18:59 ` Eli Zaretskii
2023-12-29 21:26 ` T.V Raman
2023-12-30 6:50 ` Eli Zaretskii
2023-12-30 17:43 ` T.V Raman
2023-12-30 17:55 ` Eli Zaretskii
2023-12-30 19:39 ` T.V Raman [this message]
2023-12-30 19:56 ` Eli Zaretskii
2023-12-31 3:13 ` T.V Raman
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=26000.29168.891991.646800@retriever.mtv.corp.google.com \
--to=raman@google.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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).