all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Al Haji-Ali <abdo.haji.ali@gmail.com>
Cc: larsi@gnus.org, 62637@debbugs.gnu.org
Subject: bug#62637: 29.0.60; Issues when displaying images
Date: Mon, 03 Apr 2023 21:42:20 +0300	[thread overview]
Message-ID: <838rf8vmcz.fsf@gnu.org> (raw)
In-Reply-To: <m2sfdglsxd.fsf@gmail.com> (message from Al Haji-Ali on Mon, 03 Apr 2023 19:30:38 +0100)

> From: Al Haji-Ali <abdo.haji.ali@gmail.com>
> Cc: larsi@gnus.org, 62637@debbugs.gnu.org
> Date: Mon, 03 Apr 2023 19:30:38 +0100
> 
> This code tests overlay visibility for images with three cases:
> - using insert-image: as you explained this does not work as expected.
> - using put-image: Since put-images uses an overlay, I guess the same logic applies.
> - put-image with a newline: Seems to work for some reason. This is what `mml-inline-image` was using before and why notmuch was working.

I think the invisible overlay will work if its span is different from
exactly the same text as the one on which image is defined.  I think
notmuch could simply copy the old definition of mml-inline-image, and
use that.

> Sorry for the noise. I am not sure there's a bug in this case, only unjustified expectations as you put it.

No sweat.

I'd still like to hear from Lars about the string he used in the
insert-image call: should we replace it with a non-whitespace string?





  reply	other threads:[~2023-04-03 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-02 13:31 bug#62637: 29.0.60; Issues when displaying images Abdul-Lateef Haji-Ali via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-03 13:35 ` Eli Zaretskii
2023-04-03 16:32   ` Eli Zaretskii
2023-04-03 18:30     ` Al Haji-Ali
2023-04-03 18:42       ` Eli Zaretskii [this message]
2023-04-08 13:03   ` Eli Zaretskii

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=838rf8vmcz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62637@debbugs.gnu.org \
    --cc=abdo.haji.ali@gmail.com \
    --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 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.