all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Michael Kleehammer <michael@kleehammer.com>
Cc: 59068@debbugs.gnu.org
Subject: bug#59068: 29.0.50; noverlay causing indirect append issues
Date: Mon, 07 Nov 2022 07:59:57 +0100	[thread overview]
Message-ID: <m2h6zbw8pe.fsf@Mini.fritz.box> (raw)
In-Reply-To: <87tu3bs4lz.fsf@pop-os.mail-host-address-is-not-set> (Michael Kleehammer's message of "Sun, 06 Nov 2022 23:42:00 -0600")

Michael Kleehammer <michael@kleehammer.com> writes:

> Michael Kleehammer <michael@kleehammer.com> writes:
>
> I've extracted enough from edit-indirect to reproduce the problem and attached
> it.  Eval the file and follow the instructions at the bottom.
>
> With the noverlay builds of Emacs, each commit is inserted above the original
> text.  With previous builds it is not.
>
> Let me know if I can help or if the example is not clear enough.  I'm still
> working on my elisp skills, so making it a unit-test style function would take
> me quite a while.

Thanks, Michael.

I'm afraid, I can't yet reproduce this.  This is with an Emacs from
23dd27a97953bab3ffab86dcc83b4e3b139657aa.  Here is what I did:

emacs -Q
C-x C-f test.el RET
M-x eval-buffer RET
M-: (test-create-indirect)
C-x b *test* RET
;; Add "- 1" to line 2
M-: (test-commit-indirect) RET
C-x b test.el RET

The lines at the top of the file are as expected

;; one
;; two - 1
;; three

(setq test-beg 1
...

Did I miss something?





  reply	other threads:[~2022-11-07  6:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06  5:09 bug#59068: 29.0.50; noverlay causing indirect append issues Michael Kleehammer
2022-11-06  5:25 ` Gerd Möllmann
2022-11-06  6:37   ` Eli Zaretskii
2022-11-07  5:42 ` Michael Kleehammer
2022-11-07  6:59   ` Gerd Möllmann [this message]
2022-11-07 23:25 ` Matt Armstrong
2022-11-16 22:04   ` Michael Kleehammer
2022-11-17  0:28     ` Matt Armstrong

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=m2h6zbw8pe.fsf@Mini.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=59068@debbugs.gnu.org \
    --cc=michael@kleehammer.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.