From: Wolfgang Jenkner <wjenkner@inode.at>
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:53:49 +0200 [thread overview]
Message-ID: <85613xn4lu.fsf@iznogoud.viz> (raw)
In-Reply-To: <87613xkiz5.fsf@gmail.com> (Vitalie Spinu's message of "Sat, 29 Aug 2015 21:11:42 +0200")
On Sat, Aug 29 2015, Vitalie Spinu wrote:
>> However, I tried your test case with emacs trunk fd93edb built on 2015-03-27
>
>> In particular, the first backward-char (however invoked) brings point (which
>> does not visually move) 6 positions back (from the "d" of "dummy" to the "f"
>> of "fringe"); the next backward-char moves point by one position back to the
>> last space character before "fringe".
>
> This doesn't happen in current trunk, M-: (backward-char 1) doesn't move the
> pointer.
I guess you tested this in the *scratch* buffer, whereas I tested it in
a fundamental-mode buffer.
In *scratch* point seems indeed to be stuck on the "d" of "dummy" while
in fundamental-mode the behaviour is like I described it above.
However, fd93edb from 2015-03-27 behaves in the same way as trunk does,
in *scratch*, too.
next prev parent reply other threads:[~2015-08-29 21:53 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 [this message]
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=85613xn4lu.fsf@iznogoud.viz \
--to=wjenkner@inode.at \
--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.