From: Ihor Radchenko <yantar92@posteo.net>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org>,
eller.helmut@gmail.com
Subject: Re: MPS: dangling markers
Date: Sun, 30 Jun 2024 12:18:59 +0000 [thread overview]
Message-ID: <87plryk4i4.fsf@localhost> (raw)
In-Reply-To: <m234ouiq77.fsf@pro2.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>> Fixing should be just a matter of passing that extra int argument in
>> really all places.
>
> I've reverted it, so it should work now.
Or you can use the attached patch on top of the original commit.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Fix-all-the-calls-to-build_marker-after-dc3e5cbe5b6.patch --]
[-- Type: text/x-patch, Size: 2162 bytes --]
From 972c6c6652b49302ae6ea2fc77c59d998b547fd3 Mon Sep 17 00:00:00 2001
Message-ID: <972c6c6652b49302ae6ea2fc77c59d998b547fd3.1719749890.git.yantar92@posteo.net>
From: Ihor Radchenko <yantar92@posteo.net>
Date: Sun, 30 Jun 2024 14:17:50 +0200
Subject: [PATCH] Fix all the calls to `build_marker' after dc3e5cbe5b6
---
src/textconv.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/src/textconv.c b/src/textconv.c
index 0e43bd9d458..a601dcd6729 100644
--- a/src/textconv.c
+++ b/src/textconv.c
@@ -478,7 +478,7 @@ record_buffer_change (ptrdiff_t beg, ptrdiff_t end,
/* Make markers for both BEG and END. */
beg_marker = build_marker (current_buffer, beg,
- CHAR_TO_BYTE (beg));
+ CHAR_TO_BYTE (beg), 22);
/* If BEG and END are identical, make sure to keep the markers
eq. */
@@ -488,7 +488,7 @@ record_buffer_change (ptrdiff_t beg, ptrdiff_t end,
else
{
end_marker = build_marker (current_buffer, end,
- CHAR_TO_BYTE (end));
+ CHAR_TO_BYTE (end), 23);
/* Otherwise, make sure the marker extends past inserted
text. */
@@ -868,9 +868,9 @@ really_set_composing_text (struct frame *f, ptrdiff_t position,
/* Now set the markers which denote the composition region. */
f->conversion.compose_region_start
- = build_marker (current_buffer, PT, PT_BYTE);
+ = build_marker (current_buffer, PT, PT_BYTE, 24);
f->conversion.compose_region_end
- = build_marker (current_buffer, PT, PT_BYTE);
+ = build_marker (current_buffer, PT, PT_BYTE, 24);
Fset_marker_insertion_type (f->conversion.compose_region_end,
Qt);
@@ -1165,8 +1165,8 @@ locate_and_save_position_in_field (struct frame *f, struct window *w,
}
else
{
- c1 = build_marker (current_buffer, beg, CHAR_TO_BYTE (beg));
- c2 = build_marker (current_buffer, end, CHAR_TO_BYTE (end));
+ c1 = build_marker (current_buffer, beg, CHAR_TO_BYTE (beg), 25);
+ c2 = build_marker (current_buffer, end, CHAR_TO_BYTE (end), 25);
Fset_marker_insertion_type (c2, Qt);
f->conversion.field = Fcons (c1, Fcons (c2, window));
}
--
2.45.2
[-- Attachment #3: Type: text/plain, Size: 225 bytes --]
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-06-30 12:18 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 21:01 MPS: dangling markers Ihor Radchenko
2024-06-27 21:24 ` Stefan Monnier
2024-06-28 4:14 ` Gerd Möllmann
2024-06-28 16:37 ` Ihor Radchenko
2024-06-28 16:47 ` Gerd Möllmann
2024-06-28 16:52 ` Ihor Radchenko
2024-06-28 16:56 ` Gerd Möllmann
2024-06-28 17:18 ` Ihor Radchenko
2024-06-28 17:44 ` Gerd Möllmann
2024-06-29 3:57 ` Gerd Möllmann
2024-06-29 14:34 ` Ihor Radchenko
2024-06-29 14:56 ` Gerd Möllmann
2024-06-29 16:29 ` Eli Zaretskii
2024-06-29 17:09 ` Gerd Möllmann
2024-06-29 17:17 ` Gerd Möllmann
2024-06-29 17:23 ` Eli Zaretskii
2024-06-29 18:02 ` Gerd Möllmann
2024-06-29 18:11 ` Eli Zaretskii
2024-06-29 18:19 ` Gerd Möllmann
2024-06-29 19:51 ` Ihor Radchenko
2024-06-29 21:50 ` Gerd Möllmann
2024-06-29 22:33 ` Pip Cet
2024-06-30 4:41 ` Gerd Möllmann
2024-06-30 6:56 ` Gerd Möllmann
2024-06-30 9:51 ` Pip Cet
2024-06-30 11:02 ` Gerd Möllmann
2024-06-30 12:54 ` Pip Cet
2024-06-30 13:15 ` Gerd Möllmann
2024-06-30 19:02 ` Pip Cet
2024-06-30 19:22 ` Gerd Möllmann
2024-06-30 20:15 ` Pip Cet
2024-07-01 4:22 ` Gerd Möllmann
2024-07-01 17:14 ` Pip Cet
2024-07-01 18:20 ` Gerd Möllmann
2024-07-01 18:50 ` Eli Zaretskii
2024-07-01 19:04 ` Pip Cet
2024-07-01 19:07 ` Eli Zaretskii
2024-07-01 19:43 ` Gerd Möllmann
2024-07-01 18:56 ` Eli Zaretskii
2024-07-01 21:08 ` Pip Cet
2024-07-02 11:25 ` Eli Zaretskii
2024-07-03 18:46 ` Pip Cet
2024-07-03 19:20 ` Eli Zaretskii
2024-06-29 22:59 ` Stefan Monnier
2024-06-30 5:02 ` Gerd Möllmann
2024-06-30 5:29 ` Eli Zaretskii
2024-06-30 15:04 ` Stefan Monnier
2024-06-30 5:11 ` Eli Zaretskii
2024-06-30 4:57 ` Eli Zaretskii
2024-06-30 5:36 ` Gerd Möllmann
2024-06-30 12:25 ` Ihor Radchenko
2024-06-29 17:19 ` Ihor Radchenko
2024-06-29 18:05 ` Gerd Möllmann
2024-06-29 18:10 ` Eli Zaretskii
2024-06-29 18:17 ` Gerd Möllmann
2024-06-29 18:28 ` Ihor Radchenko
2024-06-29 17:20 ` Eli Zaretskii
2024-06-29 18:04 ` Gerd Möllmann
2024-06-29 17:16 ` Stefan Monnier
2024-06-29 18:12 ` Gerd Möllmann
2024-06-29 18:30 ` Stefan Monnier
2024-06-29 18:52 ` Gerd Möllmann
2024-06-29 21:20 ` Gerd Möllmann
2024-06-29 21:38 ` Gerd Möllmann
2024-06-30 7:11 ` Gerd Möllmann
2024-06-30 7:27 ` Gerd Möllmann
2024-06-30 7:45 ` Ihor Radchenko
2024-06-30 10:44 ` Gerd Möllmann
2024-06-30 11:23 ` Ihor Radchenko
2024-06-30 11:25 ` Gerd Möllmann
2024-06-30 11:31 ` Ihor Radchenko
2024-06-30 12:13 ` Gerd Möllmann
2024-06-30 12:18 ` Ihor Radchenko [this message]
2024-06-30 12:17 ` Ihor Radchenko
2024-06-30 12:28 ` Gerd Möllmann
2024-06-30 12:38 ` Ihor Radchenko
2024-06-30 12:48 ` Gerd Möllmann
2024-06-30 15:21 ` Ihor Radchenko
2024-06-30 15:32 ` Gerd Möllmann
2024-06-30 12:49 ` Eli Zaretskii
2024-06-29 15:17 ` Ihor Radchenko
2024-06-28 4:07 ` Gerd Möllmann
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=87plryk4i4.fsf@localhost \
--to=yantar92@posteo.net \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).