From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 10578@debbugs.gnu.org
Subject: bug#10578: 24.0.92; No png images on OpenSUSE 12.1
Date: Thu, 26 Jan 2012 15:59:20 +0100 [thread overview]
Message-ID: <CAAeL0SQQ+MRGgAY0MCXXGVJX9+c=vV1P0wUexh1Moa_5hKcHDQ@mail.gmail.com> (raw)
In-Reply-To: <E1RqPe4-0005gp-6O@fencepost.gnu.org>
On Thu, Jan 26, 2012 at 14:45, Eli Zaretskii <eliz@gnu.org> wrote:
> To tell the truth, I don't like such vague warning, since the
> reference to *Messages* is not specific enough to be useful, IMO. It
> is better to show some more specific text in the delayed warning
> itself.
That goes back to what I said in a previous message (that you didn't answer):
"If we want to warn with the real message for image_error, either we
duplicate the Fformat call in add_to_log, which seems a waste, or we
add some function xdisp.c:add_to_log_and_warn. Alternatively,
repurposing add_to_log to also (optionally) warn wouldn't be
difficult, as it is used only nine times in the sources."
Juanma
next prev parent reply other threads:[~2012-01-26 14:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 16:12 bug#10578: 24.0.92; No png images on OpenSUSE 12.1 Lars Ingebrigtsen
2012-01-22 16:30 ` Eli Zaretskii
2012-01-22 16:50 ` Lars Magne Ingebrigtsen
2012-01-22 16:59 ` Achim Gratz
2012-01-22 17:02 ` Andreas Schwab
2012-01-25 19:25 ` Lars Ingebrigtsen
2012-01-22 17:51 ` Eli Zaretskii
2012-01-22 18:12 ` Eli Zaretskii
2012-01-22 19:32 ` Juanma Barranquero
2012-01-22 20:41 ` Eli Zaretskii
2012-01-22 21:25 ` Juanma Barranquero
2012-01-22 21:38 ` Juanma Barranquero
2012-01-23 1:11 ` Juanma Barranquero
2012-01-25 19:31 ` Lars Ingebrigtsen
2012-01-26 4:26 ` Juanma Barranquero
2012-01-26 5:43 ` Eli Zaretskii
2012-01-26 12:27 ` Juanma Barranquero
2012-01-26 13:45 ` Eli Zaretskii
2012-01-26 14:59 ` Juanma Barranquero [this message]
2012-01-26 17:22 ` Juanma Barranquero
2012-01-26 17:26 ` Juanma Barranquero
2016-02-08 6:18 ` Lars Ingebrigtsen
2016-02-08 18:17 ` Eli Zaretskii
2016-02-09 0:13 ` Lars Ingebrigtsen
2016-02-09 0:17 ` Lars Ingebrigtsen
2016-02-09 0:23 ` Lars Ingebrigtsen
2016-02-09 3:41 ` Eli Zaretskii
2012-01-25 19:28 ` Lars Ingebrigtsen
2012-01-26 1:49 ` Stefan Monnier
2012-01-26 17:21 ` Achim Gratz
2012-01-22 16:46 ` Achim Gratz
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='CAAeL0SQQ+MRGgAY0MCXXGVJX9+c=vV1P0wUexh1Moa_5hKcHDQ@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=10578@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).