unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: PENG Kevin <kevin.remegame@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	73663@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#73663: 29.4; indirect-buffer behaviour is not correct
Date: Tue, 08 Oct 2024 00:49:50 +0200	[thread overview]
Message-ID: <877cajbka9.fsf@web.de> (raw)
In-Reply-To: <87zfng2cdt.fsf@gmail.com> (PENG Kevin's message of "Mon, 07 Oct 2024 22:34:27 +0800")

PENG Kevin <kevin.remegame@gmail.com> writes:

> The text of the indirect buffer is always identical to the text of its
> base buffer; changes made by editing either one are visible
> immediately in the other. “Text” here includes both the characters and
> their text properties.

`image-mode' uses text properties to display the image!  Most major
modes use text properties to font-lock the buffer and change the way how
its contents are displayed.

Use cases of indirect buffers are limited, maybe we need to warn more
explicitly that their usefulness is very restricted.  IIRC, having
indirect and base buffer using different major modes is something that
was never supported.

From the past discussions about the matter I also recall that the
limitations are lying in the concept and we can't do much here without a
reimplementation of the idea.

So I would suggest to rather think about how to get what you want
without using indirect buffers.


Michael.





  reply	other threads:[~2024-10-07 22:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-06 15:42 bug#73663: 29.4; indirect-buffer behaviour is not correct PENG Kevin
2024-10-06 16:22 ` Eli Zaretskii
2024-10-07 14:34   ` PENG Kevin
2024-10-07 22:49     ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-10-09  5:23       ` PENG Kevin
2024-10-09 12:46         ` Eli Zaretskii
2024-10-12 12:56           ` PENG Kevin
2024-10-12 14:26             ` Eli Zaretskii
2024-10-09 12:46         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-12 13:05           ` PENG Kevin

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=877cajbka9.fsf@web.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=73663@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=kevin.remegame@gmail.com \
    --cc=michael_heerdegen@web.de \
    --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).