unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
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: Fri, 9 Oct 2015 19:34:43 -0400	[thread overview]
Message-ID: <CAM-tV--84Dzcx5B2istjU7p+LSqYpmSj_zCZAcjZGrjHtzafpg@mail.gmail.com> (raw)
In-Reply-To: <83zj013s0h.fsf@gnu.org>

On 10/2/15, Eli Zaretskii <eliz@gnu.org> wrote:
>
> If you want to put the cursor there, you need an overlay with a
> 'cursor' property.

This works nicely. But there are some other glitches.

- On a truncated line with the overlay, move-end-of-line skips to the
next line. (I tried to avoid this by only adding the stretched space
when it's going to be visible. But that just made things worse
(looping in the display engine))

- When at the end of line, next-line goes to the end-of-line instead
of staying on the same column.

> Or we could have a new feature whereby the stretch of white space
> would allow positioning the cursor on it.  Right now, the flag that
> disallows positioning the cursor is hard-coded in the display engine.

Could be interesting, but I don't know of any need for it at present.





  reply	other threads:[~2015-10-09 23:34 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 [this message]
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
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=CAM-tV--84Dzcx5B2istjU7p+LSqYpmSj_zCZAcjZGrjHtzafpg@mail.gmail.com \
    --to=npostavs@users.sourceforge.net \
    --cc=21468@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).