unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 21468@debbugs.gnu.org
Subject: bug#21468: 24.5; When next-line (visual) crosses overlay with before-string="\n" point goes to column 0
Date: Sun, 11 Oct 2015 05:38:17 +0300	[thread overview]
Message-ID: <83k2quqgdi.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-8JONcizaXwMK+QYaodwy1yp_h+UcMto=RvW__+_30_fw@mail.gmail.com>

> Date: Sat, 10 Oct 2015 17:06:59 -0400
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Cc: 21468@debbugs.gnu.org
> 
> On Sat, Oct 10, 2015 at 1:09 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> Date: Sat, 10 Oct 2015 12:51:06 -0400
> >> From: Noam Postavsky <npostavs@users.sourceforge.net>
> >>
> >> Okay, that makes sense, but it means this approach is worse than
> >> overlayed newlines for magit.
> >
> > I don't think so.  I think a casual mismatch in a column while moving
> > through a buffer, and in marginal cases at that, is not a big deal.
> 
> It's not a *big* deal, but with Emacs 25 using overlayed newlines
> gives no problems at all.

I'm quite sure problems will surface sooner or later.  Overlays with
newlines hit on fragile parts of the display engine code, which was
never really designed for that kind of stuff.





  reply	other threads:[~2015-10-11  2:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-13  5:17 bug#21468: 24.5; When next-line (visual) crosses overlay with before-string="\n" point goes to column 0 Noam Postavsky
2015-09-13 10:30 ` Eli Zaretskii
2015-09-13 17:20   ` Noam Postavsky
2015-09-13 19:50     ` Eli Zaretskii
2015-09-13 20:22       ` Noam Postavsky
2015-09-14  6:17         ` Eli Zaretskii
2015-09-14 12:46           ` Noam Postavsky
2015-09-14 13:22             ` Stefan Monnier
2015-09-14 13:33             ` Eli Zaretskii
2015-09-14 13:55               ` Noam Postavsky
2015-09-14 15:14                 ` Eli Zaretskii
2015-09-14 20:50                   ` Noam Postavsky
2015-09-15  6:53                     ` Eli Zaretskii
2015-10-01 20:43                       ` Noam Postavsky
2015-10-02 10:01                         ` Eli Zaretskii
2015-10-02 19:58                           ` Noam Postavsky
2015-10-02 21:00                             ` Eli Zaretskii
2015-10-09 23:34                               ` Noam Postavsky
2015-10-10  7:14                                 ` Eli Zaretskii
2015-10-10 13:37                                   ` Noam Postavsky
2015-10-10 14:20                                     ` Eli Zaretskii
2015-10-10 16:51                                       ` Noam Postavsky
2015-10-10 17:09                                         ` Eli Zaretskii
2015-10-10 21:06                                           ` Noam Postavsky
2015-10-11  2:38                                             ` Eli Zaretskii [this message]
2015-10-10 17:03                                     ` 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=83k2quqgdi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21468@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.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).