unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: michael.albinus@gmx.de, emacs-devel@gnu.org
Subject: Re: master 39e3fce0d5e0: 'read-passwd' can toggle the visibility of passwords
Date: Fri, 15 Mar 2024 20:37:41 +0200	[thread overview]
Message-ID: <86y1aj734a.fsf@gnu.org> (raw)
In-Reply-To: <jwvil1nfksn.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 15 Mar 2024 13:55:34 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: michael.albinus@gmx.de,  emacs-devel@gnu.org
> Date: Fri, 15 Mar 2024 13:55:34 -0400
> 
> >   In end of data:
> >   simple.el:10907:4: Warning: the function `define-icon' might not be defined at runtime.
> >   simple.el:10883:19: Warning: the function `icon-string' might not be defined at runtime.
> >   Makefile:289: recipe for target `../lisp/simple.elc' failed
> 
> Ah, right: the code as written only works if there's a warning earlier,
> because it uses `define-icon` inside a function and that macro is
> defined in `icons` and is not autoloaded, so the only reason it
> currently works is that `display-warning` loads `icons`: as soon as we
> fix the warning, the core problem shows up.
> 
> The hideous patch below should result in working code without warnings,
> but I hope we can find a better solution (e.g. one that lets us move
> the two `define-icon`s to the toplevel of some file rather than being
> inside a function).

Yes, the warnings are gone with this patch.

I do hope we can find a cleaner solution.

How about loading icons when compiling?  Or adding an autoload form
which states that the variable is in icons.el?



      parent reply	other threads:[~2024-03-15 18:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  8:07 master 39e3fce0d5e0: 'read-passwd' can toggle the visibility of passwords Eli Zaretskii
2024-03-15  8:23 ` Michael Albinus
2024-03-15  8:55   ` Eli Zaretskii
2024-03-15 11:55   ` Andreas Schwab
2024-03-15 12:19     ` Michael Albinus
2024-03-15 12:47       ` Andreas Schwab
2024-03-15 12:52         ` Eli Zaretskii
2024-03-15 18:20           ` Michael Albinus
2024-03-15 18:25             ` Stefan Monnier
2024-03-15 13:29 ` Stefan Monnier
2024-03-15 15:11   ` Eli Zaretskii
2024-03-15 17:55     ` Stefan Monnier
2024-03-15 18:23       ` Michael Albinus
2024-03-22 17:43         ` Michael Albinus
2024-04-04 15:24           ` Michael Albinus
2024-03-15 18:37       ` Eli Zaretskii [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:
  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=86y1aj734a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=monnier@iro.umontreal.ca \
    /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).