all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: visual-line-mode produces erratic behaviour with text properties
Date: Fri, 01 Jul 2016 10:55:00 +0300	[thread overview]
Message-ID: <831t3dvlm3.fsf@gnu.org> (raw)
In-Reply-To: <1467351025.3299202.653866593.5B4EE9EF@webmail.messagingengine.com> (message from Paul Rankin on Fri, 01 Jul 2016 15:30:25 +1000)

> From: Paul Rankin <hello@paulwrankin.com>
> Date: Fri, 01 Jul 2016 15:30:25 +1000
> 
> 1. $ emacs -Q
> 
> 2. insert a long paragraph of text
> M-: (url-insert-file-contents "https://gist.githubusercontent.com/rnkn/d5987c3495901e4950782f6648846e4e/raw/c22074e8f0940f6ec9c8b729f04567dc50664823/loren-ipsum.txt")
> 
> 3. turn on visual line mode
> M-: (visual-line-mode 1)
> 
> 4. add text properties
> M-: (add-text-properties (point-min) (point-max) '(line-prefix (space :align-to 10) wrap-prefix (space :align-to 10)))
> 
> 5. C-n past window length and up and around.
> 
> Expected results:
> 
> Navigation should continue by visual line.
> 
> Actual results:
> 
> Navigational behaviour becomes erratic. Point will no long move with visual lines, instead jumping to different columns. This is more pronounced with a window 80 columns or less.

Not quite accurate: the erratic behavior begins only when point
reaches the end of the first window-full.

Please report this as a bug, using "M-x report-emacs-bug RET".
Super-long lines such as this one slow down the display engine, and
there are various redisplay optimizations to try to countermand that,
so perhaps this is one of them.

In general, my recommendation is to stay away of such long lines in
Emacs.



  reply	other threads:[~2016-07-01  7:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-01  5:30 visual-line-mode produces erratic behaviour with text properties Paul Rankin
2016-07-01  7:55 ` Eli Zaretskii [this message]
2016-07-01  8:29   ` Paul Rankin
2016-07-01  9:29     ` 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=831t3dvlm3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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 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.