From: Kyle Meyer <kyle@kyleam.com>
To: "Julian M. Burgos" <julian.burgos@hafogvatn.is>
Cc: "Juan Manuel Macías" <maciaschain@posteo.net>,
orgmode <emacs-orgmode@gnu.org>
Subject: Re: [tip for EXWM users] An alternative method for isolate trees
Date: Tue, 02 Mar 2021 00:44:21 -0500 [thread overview]
Message-ID: <871rcynm8a.fsf@kyleam.com> (raw)
In-Reply-To: <xgz5z2aubpr.fsf@hafogvatn.is>
Julian M. Burgos writes:
> I have not noticed that org-tree-to-indirect-buffer
> reuses the indirect buffer when you call it for a second time.
> According to the manual, "with a C-u prefix, do not remove the
> previously used indirect buffer", but that does not seem to work.
> When you do Cu-Cc-Cx-b from a buffer that already has an indirect
> buffer you get a "cannot modify an area being edited in a dedicated
> buffer". If you try it from a different buffer, the prefix is ignored
> and the indirect buffer is assigned to the tree from the last buffer.
Hmm, could you provide a reproducer for the problem? Here's what I
tried with the current master (afd75d05a), Emacs 27.1, and no custom
configuration.
--8<---------------cut here---------------start------------->8---
* a
a content
* b
b content
--8<---------------cut here---------------end--------------->8---
- on "a", C-c C-x b ;; org-tree-to-indirect-buffer
Displays <file>-a-1 buffer.
- move to "b", C-u C-c C-x b
Displays <file>-b-1 buffer, a-1 buffer still exists.
next prev parent reply other threads:[~2021-03-02 5:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 12:55 [tip for EXWM users] An alternative method for isolate trees Juan Manuel Macías
2021-03-01 13:37 ` Julian M. Burgos
2021-03-01 14:10 ` Juan Manuel Macías
2021-03-01 15:37 ` Julian M. Burgos
2021-03-01 16:42 ` Juan Manuel Macías
2021-03-02 5:44 ` Kyle Meyer [this message]
2021-03-02 9:29 ` Julian M. Burgos
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rcynm8a.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=julian.burgos@hafogvatn.is \
--cc=maciaschain@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).