From: Eli Zaretskii <eliz@gnu.org>
To: Wolfgang Jenkner <wjenkner@inode.at>
Cc: spinuvit@gmail.com, 21368@debbugs.gnu.org
Subject: bug#21368: 25.0.50; Core navigation commands fail in a multi-line intangible text with fringe
Date: Sun, 30 Aug 2015 18:02:57 +0300 [thread overview]
Message-ID: <83lhcs250e.fsf@gnu.org> (raw)
In-Reply-To: <85twrhnddn.fsf@iznogoud.viz>
> From: Wolfgang Jenkner <wjenkner@inode.at>
> Date: Sun, 30 Aug 2015 14:55:45 +0200
> Cc: 21368@debbugs.gnu.org
>
> On Sun, Aug 30 2015, Vitalie Spinu wrote:
>
> > Prior to 1st of April 2015 the (backward-char 1) used to work with the above
> > example. Something changed between 1st of April and 1st of June and as a
> > consequence the point is now stuck even with the above example. I
>
> That's perhaps
>
> commit 84e0b7dad6f1a8e53261f9b96f5a9080fea681a4
> Author: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Mon Apr 13 15:51:15 2015 -0400
>
> Deprecate `intangible' and `point-entered' properties
I don't think so, because I have a build from May 1, and the problem
with backward-char is not there.
next prev parent reply other threads:[~2015-08-30 15:02 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
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 [this message]
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
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=83lhcs250e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21368@debbugs.gnu.org \
--cc=spinuvit@gmail.com \
--cc=wjenkner@inode.at \
/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).