From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: Any easy way to use multiple indirect buffers based on subtrees?
Date: Thu, 13 Sep 2018 05:02:58 -0500 [thread overview]
Message-ID: <8736udogtp.fsf@alphapapa.net> (raw)
In-Reply-To: CADq_+R1J3DygFTpOVrp5dfZLdo_pnh9YTyNikyjO50fCUS2iSg@mail.gmail.com
In addition to Kyle's suggestion, you may find Helm useful, as commands
like helm-org-in-buffer-headings have an "Open in indirect buffer"
action, which makes it easy to open subtrees in indirect buffers.
helm-org-rifle can also do this.
If there are certain subtrees you often work with together, you could
write a function to open certain entries by UUID in indirect buffers,
then arrange the buffers into frames/windows accordingly.
prev parent reply other threads:[~2018-09-13 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 17:26 Any easy way to use multiple indirect buffers based on subtrees? Cody Goodman
2018-09-05 0:11 ` Kyle Meyer
2018-09-13 10:02 ` Adam Porter [this message]
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=8736udogtp.fsf@alphapapa.net \
--to=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
/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).