unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
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 21:06:15 +0200	[thread overview]
Message-ID: <87sj1u64ew.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <83ehdebut7.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 May 2013 20:37:08 +0300")

On Fri, 10 May 2013 20:37:08 +0300 Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Stephen Berman <stephen.berman@gmx.net>
[...]
>> (I wish I understood why this problem occurred and how your patch
>> fixes it...)
[...]
> I can give you a vague idea of why the problem occurred.
[...]

Thanks for the explanation.

>> Unless someone knows of another problem with allowing
>> overflow-newline-into-fringe in Visual Line mode, I would like to
>> request that both my patch and yours be committed to the trunk
>
> 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.

>                            If not, then I'm not prepared to believe
> that the above is the only problem with this change.  I'd like to see
> much more reports from users of those modes that this change doesn't
> cause any trouble, before I'd agree to installing it.  Just look how
> much time it took until this problem popped up.  Since I knew the only
> change was in a single macro that is used in a small number of places,
> fixing it was a 5-min job.  But imagine that the same would happen 3
> years after committing this change, with gazillions of unrelated
> changes in the display code since then.

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.  This bug report was initiated more than
four years ago by someone (not me) who noticed the odd display of a line
whose length is window-width when Visual Line mode is enabled.  Chong
Yidong pointed out that this was because fringe overflow was disabled in
Visual Line mode and he suspected "confusing results" if it were
enabled.  Then this past February, almost four years later, I posted
that I had enabled it in my local branch and had not observed any
problems.  I've been using it since then and only today hit the problem
that I reported and you quickly fixed.  Nobody using the vanilla trunk
can have run into the problem, because fringe overflow is still disabled
in Visual Line mode there.  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.  Does this make sense, or have I completely
misunderstood you?

Steve Berman





  reply	other threads:[~2013-05-10 19:06 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 [this message]
2013-05-10 19:31                 ` Eli Zaretskii
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=87sj1u64ew.fsf@rosalinde.fritz.box \
    --to=stephen.berman@gmx.net \
    --cc=2749@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=pent@aparamon.msk.ru \
    /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).