all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Matt Armstrong <matt@rfc20.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
	"Ihor Radchenko" <yantar92@posteo.net>
Cc: 58928@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Eli Qian <eli.q.qian@gmail.com>
Subject: bug#58928: 29.0.50; overlays in org-mode are disrupted after call `org-capture`
Date: Tue, 01 Nov 2022 16:25:22 -0700	[thread overview]
Message-ID: <87tu3i9s0t.fsf@rfc20.org> (raw)
In-Reply-To: <87y1su9uaj.fsf@rfc20.org>

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

I've created a simpler repro that demonstrates how inserts/deletes in an
indirect buffer does not update positions for overlays its base buffer.

This function creates a temp buffer with some text and one overlay, then
an indirect buffer against it.  Editing text in the indirect buffer
fails to update overlay positions in the base buffer.

(defun repro58928 ()
  (interactive)
  (with-current-buffer (get-buffer-create "*b58928*")
    (erase-buffer)
    (delete-all-overlays)
    (insert "My dog has fleas,\nlots and lots of fleas!\n")
    (let ((overlay (make-overlay 18 (point-max))))
      (overlay-put overlay 'face 'match))
    (pop-to-buffer (current-buffer))
    (ignore-errors
      (kill-buffer "*INDIRECT-b58928*"))
    (let ((indirect (make-indirect-buffer (current-buffer)
					  "*INDIRECT-b58928*")))
      (with-current-buffer indirect
	(goto-char (point-min)))
      (pop-to-buffer indirect))))

I'm not sure where the bug is, but the good news is that the regression
test will be easy to express in lisp.


[-- Attachment #2: before typing in the indirect buffer --]
[-- Type: image/png, Size: 34718 bytes --]

[-- Attachment #3: after typing in the indirect buffer --]
[-- Type: image/png, Size: 40692 bytes --]

  reply	other threads:[~2022-11-01 23:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 13:58 bug#58928: 29.0.50; overlays in org-mode are disrupted after call `org-capture` Eli Qian
2022-11-01  6:14 ` Eli Zaretskii
2022-11-01  7:01   ` Gerd Möllmann
     [not found]     ` <87sfj3gmsx.fsf@gmail.com>
2022-11-01  7:50       ` Gerd Möllmann
2022-11-01  8:08         ` Gerd Möllmann
2022-11-01  9:07         ` Ihor Radchenko
2022-11-01  9:20           ` Gerd Möllmann
2022-11-01 22:36             ` Matt Armstrong
2022-11-01 23:25               ` Matt Armstrong [this message]
2022-11-02  1:39             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-02  2:49               ` Matt Armstrong
2022-11-02  4:53               ` Gerd Möllmann
2022-11-03 13:10               ` Eason Huang
2022-11-03 14:25                 ` Gerd Möllmann
2022-11-03 14:57                   ` Eason Huang
2022-11-03 15:18                     ` Gerd Möllmann
2022-11-03 15:41                       ` Eason Huang
2022-11-03 15:02                   ` Eason Huang
2022-11-03 15:45                     ` Eason Huang
2022-11-03 16:12                       ` Gerd Möllmann
2022-11-03 22:51                     ` Matt Armstrong
2022-11-04  2:49                       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-04  4:33                       ` Matt Armstrong
2022-11-04 16:05                         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-04 22:47                           ` Matt Armstrong
2022-11-04 22:58                             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-05  6:28                             ` Eli Zaretskii
2022-11-04  3:47                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-04 18:06                       ` Matt Armstrong
2022-11-05  2:45                         ` Ihor Radchenko

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=87tu3i9s0t.fsf@rfc20.org \
    --to=matt@rfc20.org \
    --cc=58928@debbugs.gnu.org \
    --cc=eli.q.qian@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=yantar92@posteo.net \
    /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.