unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Spaulding, Jeff" <jeff.spaulding@englobal.com>
Cc: 47240@debbugs.gnu.org
Subject: bug#47240: Images Treated as Whitespace and Removed from Buffer
Date: Fri, 19 Mar 2021 09:45:35 +0100	[thread overview]
Message-ID: <87lfajmt00.fsf@gnus.org> (raw)
In-Reply-To: <DM6PR14MB3498B65851DE6C02F38889B3EB699@DM6PR14MB3498.namprd14.prod.outlook.com> (Jeff Spaulding's message of "Thu, 18 Mar 2021 01:04:18 +0000")

"Spaulding, Jeff" <jeff.spaulding@englobal.com> writes:

> Press M-: to bring up an Eval: prompt in the minibuffer.  Enter the
> following elisp code:
>
> (insert-image (create-image "test.png"))
>
> The image will appear in the buffer.
>
> Press Enter.  The image will disappear.
>
> The image seems to always be deleted if the enter key is pressed (bound
> to the newline function), but not when C-j is pressed (bound to the
> electric-newline-and-maybe-indent function).  The image will not be
> deleted if there is any text following it on the line.  This suggests
> the image is being treated as trailing whitespace, as trailing
> whitespace is treated in the same way.

I think this is working basically as designed.  By default, images are
whitespace and handled as such, but if you don't want that, you have to
say

(insert-image (create-image "test.png") "*")

or something like that.

So I'm not sure whether there's anything to fix here.  Does anybody else
have an opinion here?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-03-19  8:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18  1:04 bug#47240: Images Treated as Whitespace and Removed from Buffer Spaulding, Jeff
2021-03-19  8:45 ` Lars Ingebrigtsen [this message]
2021-04-04  0:30   ` Stefan Kangas
2021-04-04  0:37     ` Spaulding, Jeff
2021-04-04 19:48     ` Lars Ingebrigtsen

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=87lfajmt00.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=47240@debbugs.gnu.org \
    --cc=jeff.spaulding@englobal.com \
    /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).