From: Eli Zaretskii <eliz@gnu.org>
To: Zack Weinberg <zackw@panix.com>
Cc: 45054@debbugs.gnu.org
Subject: bug#45054: 27.1; Can get point into the middle of a run of characters with a replacing display spec
Date: Wed, 09 Dec 2020 21:50:33 +0200 [thread overview]
Message-ID: <83zh2m4v3q.fsf@gnu.org> (raw)
In-Reply-To: <CAKCAbMhDYf94=xfViFsMWzy0V42on8esnHcmGpNi0x0A4_ezcQ@mail.gmail.com> (message from Zack Weinberg on Wed, 9 Dec 2020 14:20:15 -0500)
> From: Zack Weinberg <zackw@panix.com>
> Date: Wed, 9 Dec 2020 14:20:15 -0500
> Cc: 45054@debbugs.gnu.org
>
> On Wed, Dec 9, 2020 at 2:14 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > > From: Zack Weinberg <zackw@panix.com>
> > > Date: Wed, 9 Dec 2020 13:56:28 -0500
> > > Cc: 45054@debbugs.gnu.org
> > >
> > > Are you saying that this is not a bug?
> >
> > Did I say that?
>
> I don't know, that's why I ask. You said that "The adjustment of point
> to move it outside of the "forbidden" region is triggered by point
> movements, while your examples don't move point" and that could be
> read as "this is working as intended".
It could also be read as "that's why it doesn't work as intended".
prev parent reply other threads:[~2020-12-09 19:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 15:54 bug#45054: 27.1; Can get point into the middle of a run of characters with a replacing display spec Zack Weinberg
2020-12-05 15:59 ` Zack Weinberg
2020-12-05 16:18 ` Eli Zaretskii
2020-12-05 20:00 ` Zack Weinberg
2020-12-05 20:12 ` Eli Zaretskii
2020-12-05 20:30 ` Eli Zaretskii
[not found] ` <CAKCAbMipxyka3DNGYOswAewqN8PCGknMdnp3pkAVDi5V-Pcrxg@mail.gmail.com>
2020-12-05 22:12 ` Zack Weinberg
2020-12-06 5:41 ` Eli Zaretskii
2020-12-09 18:56 ` Zack Weinberg
2020-12-09 19:14 ` Eli Zaretskii
2020-12-09 19:20 ` Zack Weinberg
2020-12-09 19:50 ` Eli Zaretskii [this message]
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=83zh2m4v3q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45054@debbugs.gnu.org \
--cc=zackw@panix.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.