From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 14547@debbugs.gnu.org, E Sabof <esabof@gmail.com>
Subject: bug#14547: 24.3.1; line-break with pixel specification and word-wrap
Date: Sun, 30 Jan 2022 22:43:14 +0100 [thread overview]
Message-ID: <877dag7vd9.fsf@gnus.org> (raw)
In-Reply-To: <87y5aryxaf.fsf@rosalinde.fritz.box> (Stephen Berman's message of "Mon, 03 Jun 2013 18:27:36 +0200")
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 must admit I didn't understand what
the reproducing code here is supposed to demonstrate.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-01-30 21:43 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 [this message]
2022-01-31 9:06 ` Stephen Berman
2022-01-31 12:47 ` Eli Zaretskii
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dag7vd9.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=14547@debbugs.gnu.org \
--cc=esabof@gmail.com \
--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 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.