all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vitalie Spinu <spinuvit@gmail.com>
Cc: 21368@debbugs.gnu.org
Subject: bug#21368: 25.0.50; Core navigation commands fail in a multi-line intangible text with	fringe
Date: Sat, 29 Aug 2015 23:11:32 +0300	[thread overview]
Message-ID: <83zj1926tn.fsf@gnu.org> (raw)
In-Reply-To: <87a8t9kj51.fsf@gmail.com>

> From: Vitalie Spinu <spinuvit@gmail.com>
> Cc: 21368@debbugs.gnu.org
> Date: Sat, 29 Aug 2015 21:08:10 +0200
> 
> > What is a relatively recent change?  The C-b part or the M-x part?
> 
> The M-x part. Aka, invoking `backward-char` from programs.

I wonder what change that could be.

> > text around.  (Btw, yet another solution is to disable line-move-visual in
> > these cases -- would that be a good idea in those real-life examples?)
> 
> So the core of the issue is `line-move-visual`?

Yes.  Without it, previous-line just goes to the previous physical
line.  With it, Emacs needs to decide where to put point, and that's
not easy when invisible text is involved, because we can only put
point on some buffer position.





  parent reply	other threads:[~2015-08-29 20:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28 15:46 bug#21368: 25.0.50; Core navigation commands fail in a multi-line intangible text with fringe Vitalie Spinu
2015-08-28 19:45 ` Eli Zaretskii
2015-08-28 22:02   ` Vitalie Spinu
2015-08-29  7:25     ` Eli Zaretskii
2015-08-29 19:08       ` Vitalie Spinu
2015-08-29 19:17         ` Vitalie Spinu
2015-08-29 20:14           ` Eli Zaretskii
2015-08-29 20:11         ` Eli Zaretskii [this message]
2015-08-29 15:23     ` Wolfgang Jenkner
2015-08-29 19:11       ` Vitalie Spinu
2015-08-29 21:53         ` Wolfgang Jenkner
2015-08-30 11:46           ` Vitalie Spinu
2015-08-30 12:55             ` Wolfgang Jenkner
2015-08-30 15:02               ` Eli Zaretskii
2015-08-30 15:11                 ` Wolfgang Jenkner
2015-08-31 12:54                   ` Wolfgang Jenkner

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=83zj1926tn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21368@debbugs.gnu.org \
    --cc=spinuvit@gmail.com \
    /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.