From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: failing creating multiple indirect org buffers .
Date: Sat, 02 Mar 2024 23:15:21 -0500 [thread overview]
Message-ID: <jwv5xy4eywe.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 878r30xgvr.fsf@web.de
> Using indirect clones is always an a bit fragile matter in
> my experience.
I recommend people stay away from them, indeed.
Using indirect buffers can make sense, but you need the clone to be
setup and controlled by a dedicated package which knows/understands
what is shared, what isn't, and how to accommodate its needs to
those realities.
Stefan
next prev parent reply other threads:[~2024-03-03 4:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 7:47 failing creating multiple indirect org buffers Alexandros Prekates
2024-03-01 8:23 ` Eli Zaretskii
2024-03-01 8:47 ` Alexandros Prekates
2024-03-02 7:47 ` Eli Zaretskii
2024-03-03 1:07 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-03-03 4:15 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
2024-03-04 8:37 ` Alexandros Prekates
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=jwv5xy4eywe.fsf-monnier+emacs@gnu.org \
--to=help-gnu-emacs@gnu.org \
--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.
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).