unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: larsi@gnus.org, 14547-done@debbugs.gnu.org, esabof@gmail.com
Subject: bug#14547: 24.3.1; line-break with pixel specification and word-wrap
Date: Mon, 31 Jan 2022 14:47:29 +0200	[thread overview]
Message-ID: <83o83s842m.fsf@gnu.org> (raw)
In-Reply-To: <877dagz33t.fsf@gmx.net> (message from Stephen Berman on Mon, 31 Jan 2022 10:06:14 +0100)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: Eli Zaretskii <eliz@gnu.org>,  14547@debbugs.gnu.org,  E Sabof
>  <esabof@gmail.com>
> Date: Mon, 31 Jan 2022 10:06:14 +0100
> 
> On Sun, 30 Jan 2022 22:43:14 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote:
> 
> > Stephen Berman <stephen.berman@gmx.net> writes:
> >
> >>>> If one executes the following in a graphical frame, the line will break:
> >>>>
> >>>> (insert (propertize
> >>>>            "\n"
> >>>>            'display `(space :align-to (- right))
> >>>>            'face '(:underline t))
> >>>>           "\n")
> >>>>
> >>>> (toggle-word-wrap 1)
> >
> > [...]
> >
> >> I think it's a manifestation of bug#2749, because I see no line break
> >> with this recipe in Emacs built with my patch enabling
> >> overflow-newline-into-fringe in visual-line-mode.
> >
> > (I'm going through old bug reports that unfortunately weren't resolved
> > at the time.)
> >
> > bug#2749 was fixed a few weeks later, so does that mean that the problem
> > discussed here also was fixed?
> 
> I think so.
> 
> >                                 (I must admit I didn't understand what
> > the reproducing code here is supposed to demonstrate.)
> 
> Based on the descriptions and discussion in bug#2749, I think the above
> code used to display an empty line between the parts of the line
> separated by the display property.  It doesn't now, presumably since the
> fix for bug#2749, which allows the newline to be in the fringe.

Yes, and I'm therefore closing this bug.





  reply	other threads:[~2022-01-31 12:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03 13:21 bug#14547: 24.3.1; line-break with pixel specification and word-wrap E Sabof
2013-06-03 16:07 ` Eli Zaretskii
2013-06-03 16:27   ` Stephen Berman
2022-01-30 21:43     ` Lars Ingebrigtsen
2022-01-31  9:06       ` Stephen Berman
2022-01-31 12:47         ` Eli Zaretskii [this message]
     [not found]   ` <CAEp6DyZSOfrjVpCn9O81E9vzPRuOWfzPjkFM+h9iTL1rNg0SXQ@mail.gmail.com>
2013-06-03 16:58     ` bug#14547: Fwd: " E Sabof
2013-06-03 17:10     ` Eli Zaretskii
2013-06-03 17:19       ` E Sabof
2013-06-03 17:51         ` 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

  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=83o83s842m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=14547-done@debbugs.gnu.org \
    --cc=esabof@gmail.com \
    --cc=larsi@gnus.org \
    --cc=stephen.berman@gmx.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 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).