From: Eli Zaretskii <eliz@gnu.org>
To: Alcor <alcor@tilde.club>, Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 69920@debbugs.gnu.org
Subject: bug#69920: Proposed fix - Toggling MIME inline attachment previews adds superfluous newlines
Date: Sat, 23 Mar 2024 08:52:56 +0200 [thread overview]
Message-ID: <86ttkxzbg7.fsf@gnu.org> (raw)
In-Reply-To: <87wmpuouay.fsf@tilde.club> (bug-gnu-emacs@gnu.org)
> Date: Fri, 22 Mar 2024 22:01:09 +0100
> From: Alcor via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> After some investigation, I noticed that `mm-inline-image' adds a
> newline via (insert "\n") directly after `insert-image' for unclear
> reasons.
I'm guessing this is to make sure text following the image starts on a
new line, rather than after the image.
Why is the current code a problem? IOW, when does the extra newline
cause any harm? You talk about "the issue", but I didn't see any
explanation what that issue is.
Eric, any comments?
prev parent reply other threads:[~2024-03-23 6:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 17:59 bug#69920: 29.2; gnus: article-mode: Toggling MIME inline attachment previews adds superfluous newlines Alcor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-22 21:01 ` bug#69920: Proposed fix - " Alcor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-22 22:25 ` Alcor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-23 6:59 ` Eli Zaretskii
2024-03-23 9:53 ` Alcor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-23 10:20 ` Eli Zaretskii
2024-04-06 8:59 ` Eli Zaretskii
2024-04-18 9:00 ` Eli Zaretskii
2024-04-22 2:48 ` Eric Abrahamsen
2024-04-22 12:42 ` Alcor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-22 14:58 ` bug#69920: 29.2; gnus: article-mode: " Eric Abrahamsen
2024-03-23 6:52 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ttkxzbg7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69920@debbugs.gnu.org \
--cc=alcor@tilde.club \
--cc=eric@ericabrahamsen.net \
/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.