unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Richard Hansen <rhansen@rhansen.org>
Cc: 59618@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
	arsen@aarsen.me, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#59618: 29.0.50; global-whitespace-mode + org-capture: "Marker does not point anywhere"
Date: Tue, 13 Dec 2022 06:48:51 +0000	[thread overview]
Message-ID: <877cyvg5nw.fsf@localhost> (raw)
In-Reply-To: <d2b8abf6-e525-b580-9bbe-a896549f40aa@rhansen.org>

Richard Hansen <rhansen@rhansen.org> writes:

> On 12/13/22 01:34, Ihor Radchenko wrote:
>> Org's capture buffer is created by calling `make-indirect-buffer' with
>> CLONE argument.  This makes Emacs clone buffer local variables,
>> including `after-change-functions'.
>
> Sounds like setting CLONE to t does not clone markers.  That sounds like 
> a bug in `make-indirect-buffer', no?

AFAIK, it does clone markers. Also changing marker buffer appropriately.

-- 
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>





  reply	other threads:[~2022-12-13  6:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26 14:42 bug#59618: 29.0.50; global-whitespace-mode + org-capture: "Marker does not point anywhere" Arsen Arsenović via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-26 19:58 ` Eli Zaretskii
2022-11-26 20:11   ` Arsen Arsenović via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-27  0:27   ` Ihor Radchenko
2022-11-27  6:13     ` Stefan Kangas
2022-11-27  6:20       ` Ihor Radchenko
2022-11-27  6:54         ` Stefan Kangas
2022-12-01 12:06           ` Eli Zaretskii
2022-12-01 15:02             ` Stefan Kangas
2022-12-13  6:25             ` Richard Hansen
2022-12-13  6:34               ` Ihor Radchenko
2022-12-13  6:38                 ` Richard Hansen
2022-12-13  6:48                   ` Ihor Radchenko [this message]
2022-12-14  2:42                     ` Richard Hansen
2022-12-14 12:09                       ` Eli Zaretskii
2022-12-14 14:15                         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-14 15:08                           ` Ihor Radchenko
2022-12-14 17:40                             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-14 17:48                               ` Ihor Radchenko
2022-12-14 20:10                                 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-18  9:24                                   ` bug#59618: [PATCH] " Richard Hansen
2022-12-20  0:41                                     ` bug#59618: [PATCH] " Richard Hansen
2022-12-20 13:52                                       ` Eli Zaretskii
2022-12-21 13:34                                         ` Ihor Radchenko
2022-12-21 14:03                                           ` Eli Zaretskii
2022-11-27  0:28   ` 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

  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=877cyvg5nw.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=59618@debbugs.gnu.org \
    --cc=arsen@aarsen.me \
    --cc=eliz@gnu.org \
    --cc=rhansen@rhansen.org \
    --cc=stefankangas@gmail.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).