From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: "Julian M. Burgos" <julian.burgos@hafogvatn.is>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: [tip for EXWM users] An alternative method for isolate trees
Date: Mon, 01 Mar 2021 17:42:23 +0100 [thread overview]
Message-ID: <871rcyu8pc.fsf@posteo.net> (raw)
In-Reply-To: <xgz5z2aubpr.fsf@hafogvatn.is> (Julian M. Burgos's message of "Mon, 01 Mar 2021 15:37:20 +0000")
Hi Julian,
"Julian M. Burgos" <julian.burgos@hafogvatn.is> writes:
> This does not seem to be a limitation from emacs, as it is possible to
> open multiple indirect buffers from a base buffer, using for example
> clone-indirect-buffer. So it should be possible to make a function
> combining "clone-indirect-buffer" and "org-narrow-to-subtree" perhaps?
> I am thinking so this option is available not only to EXWM users.
I think that combining clone-indirect-buffer and org-narrow-to-subtree
would work well. Another way to isolate several trees at once is by
using the excellent package org-sidebar
(https://github.com/alphapapa/org-sidebar). In fact, I borrowed from
this package the idea of renaming the new buffers with the string :: (if
I open helm and start typing ::, it shows me the list of isolated trees,
so it's very useful to have a dedicated string). Although my method for
isolating each tree is more pedestrian :-). And it only makes sense in
EXWM...
Best regards,
Juan Manuel
next prev parent reply other threads:[~2021-03-01 16:44 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 [this message]
2021-03-02 5:44 ` Kyle Meyer
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=871rcyu8pc.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=julian.burgos@hafogvatn.is \
/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).