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: Sat, 05 Dec 2020 22:12:48 +0200 [thread overview]
Message-ID: <83o8j8au67.fsf@gnu.org> (raw)
In-Reply-To: <CAKCAbMjuZkCssHYvq_JcAek2M_3TgQQ9i6pVS=QcJffKa_ksuQ@mail.gmail.com> (message from Zack Weinberg on Sat, 5 Dec 2020 15:00:30 -0500)
> From: Zack Weinberg <zackw@panix.com>
> Date: Sat, 5 Dec 2020 15:00:30 -0500
> Cc: 45054@debbugs.gnu.org
>
> On Sat, Dec 5, 2020 at 11:18 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > > 1. Is this indeed a bug in Emacs?
> >
> > Probably a bug in adjust_point_for_property. Try your recipe after
> > setting global-disable-point-adjustment non-nil.
>
> No change, but set-variable doesn't recognize that variable (so I used
> setq instead) Is this variable possibly only available in development
> trunk and/or in an Emacs compiled with internal debugging enabled?
No, it just isn't a user option, just a variable.
> > A workaround in Lisp? Try making the affected text, or some of it,
> > invisible, i.e. give it the 'invisible' text property as well. (I
> > didn't try to test this solution, so I cannot promise it will work.)
>
> That makes the situation worse: with the mode enabled, I can separate
> point from the visible cursor just by attempting to move the visible
> cursor over the displayed ¶.
Then I guess your method of putting the display property really freaks
out the mechanism of adjusting point to move it out of this and other
similar properties.
> > > 3. I think it would be better UI if the C-d in the recipe deleted the
> > > entire run of text that’s getting hidden (more generally, deletion
> > > commands should behave as if the ¶ is really what’s in the buffer).
> > > I can’t figure out how to implement that, can you suggest anything?
> >
> > Why can't you delete every character around point that has this
> > special property?
>
> I don't know how to do that.
What part is missing? Implement a command that uses
next-property-change and previous-property-change to find where the
property starts and ends, then delete all those characters. Am I
missing something?
next prev parent reply other threads:[~2020-12-05 20:12 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 [this message]
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
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=83o8j8au67.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 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).