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: pent@aparamon.msk.ru, 2749@debbugs.gnu.org
Subject: bug#2749: 23.0.91; Visual Line Mode: incorrect line wrapping in corner case
Date: Fri, 10 May 2013 22:31:53 +0300	[thread overview]
Message-ID: <83d2sybphy.fsf@gnu.org> (raw)
In-Reply-To: <87sj1u64ew.fsf@rosalinde.fritz.box>

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: monnier@iro.umontreal.ca,  pent@aparamon.msk.ru,  2749@debbugs.gnu.org
> Date: Fri, 10 May 2013 21:06:15 +0200
> 
> > Do you use Org mode or any other modes (e.g., magit) that are heavy
> > users of display strings?  
> 
> I don't use either of those modes, but I have been developing a new
> version of todo-mode.el for a very long time (which I plan to submit for
> possible inclusion in Emacs, hopefully before the next pretest begins)
> and it uses before-string overlays, on the order of hundreds per buffer
> (though most are not in the visible window at any time), as well as
> word-wrap and wrap-prefix.

Before- and after-strings are much easier on the display engine than
'display' text properties and overlays with 'display' properties.

> I may be misunderstanding you here, but it sounds like you think the
> patch to enable overflow-newline-into-fringe in Visual Line mode is
> already in the trunk; it isn't.

I know.  I said "imagine" because I understand this change is not in
the repository.

> But if it were now enabled (with my patch) and your patch were also
> added (to prevent the problem I reported today), then Org and magit
> users and others will be able to see if other problems do arise.

I suspect subtle issues will be triggered by this change in modes that
make heavy use of display properties.  But if Stefan is willing to
take that risk, let's install this and see what breaks.





  reply	other threads:[~2013-05-10 19:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 18:04 bug#2749: 23.0.91; Visual Line Mode: incorrect line wrapping in corner case Chong Yidong
2009-03-25  1:35 ` Stefan Monnier
2009-03-22 19:13   ` pent
2013-02-18 12:03     ` Stephen Berman
2013-05-10 14:01       ` Stephen Berman
2013-05-10 14:59         ` Eli Zaretskii
2013-05-10 15:49           ` Stephen Berman
2013-05-10 17:37             ` Eli Zaretskii
2013-05-10 19:06               ` Stephen Berman
2013-05-10 19:31                 ` Eli Zaretskii [this message]
2013-05-18 20:30                   ` Stephen Berman
2013-05-19 15:29                     ` Eli Zaretskii
2013-05-19 16:28                       ` Stephen Berman
2013-05-19 17:38                         ` Eli Zaretskii
2013-05-28 22:26                     ` Stefan Monnier
2013-07-02 15:54                       ` Eli Zaretskii
2013-07-03  9:15                         ` Stefan Monnier
2013-07-03  9:52                         ` Stephen Berman

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=83d2sybphy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=2749@debbugs.gnu.org \
    --cc=pent@aparamon.msk.ru \
    --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).