all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Hansen <rhansen@rhansen.org>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefankangas@gmail.com>
Cc: 59618@debbugs.gnu.org, yantar92@posteo.net, arsen@aarsen.me
Subject: bug#59618: 29.0.50; global-whitespace-mode + org-capture: "Marker does not point anywhere"
Date: Tue, 13 Dec 2022 01:25:22 -0500	[thread overview]
Message-ID: <b43da933-8f1e-c2ac-2af0-c9dd6348fb2e@rhansen.org> (raw)
In-Reply-To: <837czbib0k.fsf@gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 994 bytes --]

I believe this is caused by an interaction between indirect buffers and 
after-change-functions.  In the buffer with the error, 
whitespace--update-bob-eob is in after-change-functions even though 
whitespace-color-on (which is the only place that hook is registered) is 
never called on the buffer.  whitespace-color-on sets up state that 
whitespace--update-bob-eob depends on, which is why the error occurs.

I see no mention of after-change-functions in the documentation for 
indirect buffers, and no mention of indirect buffers in the 
documentation for after-change-functions.  I'm not sure how they're 
supposed to interact, so I'm not sure if this is a bug in whitespace, 
indirect buffers, or even org.  We could slap a bandaid on whitespace.el 
to work around this issue, but I'd rather fix this the right way.  I'm 
not sure what the right way is; if someone who understands indirect 
buffers could give me some tips I'd appreciate it.

bug#46982 might be related.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-12-13  6:25 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 [this message]
2022-12-13  6:34               ` Ihor Radchenko
2022-12-13  6:38                 ` Richard Hansen
2022-12-13  6:48                   ` Ihor Radchenko
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b43da933-8f1e-c2ac-2af0-c9dd6348fb2e@rhansen.org \
    --to=rhansen@rhansen.org \
    --cc=59618@debbugs.gnu.org \
    --cc=arsen@aarsen.me \
    --cc=eliz@gnu.org \
    --cc=stefankangas@gmail.com \
    --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.