From: Ihor Radchenko <email@example.com>
To: Dmitrii Korobeinikov <firstname.lastname@example.org>,
Subject: Re: [Proposal] Buffer Lenses and the Case of Org-Mode (also, Jupyter)
Date: Thu, 25 Apr 2019 11:25:31 +0800 [thread overview]
Message-ID: <email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1736 bytes --]
I strongly support the proposal.
Another use case for me is to speed up agenda creation.
I usually do not like to split my org files into too many. However, it
results in very large and slow org buffers later. If I can store some
parts of the org files externally and only show them if some condition
is met (say, for certain todo state of the parent entry), it would speed
up my agenda and the buffer navigation quite significantly.
*** TODO Project 1 :ORG:
# the project contents is stored in an external file
# beginning of a lense, which is linked to project1.org
**** Heading 1
**** Heading 2
And many headings below
# end of the lense
*** HOLD Project 2 :ORG:
# beginning of another lense
# nothing is included here because the project state is =HOLD=
# end of the lense
Let me put some historical context to this proposal.
There was a discussion of similar feature in emacs-dev last year.
The idea was to implement nested buffers:
There are also several projects, which implement part of the
functionality you described:
- mmm-mode: https://github.com/purcell/mmm-mode
- polymode: https://github.com/polymode/polymode
Dmitrii Korobeinikov <firstname.lastname@example.org> writes:
> I have written a proposal for buffer lenses which could prove useful in
> Org-mode, especially for interacting with code.
> If you are interested, please, see this link:
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-04-25 3:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 19:20 [Proposal] Buffer Lenses and the Case of Org-Mode (also, Jupyter) Dmitrii Korobeinikov
2019-04-25 3:25 ` Ihor Radchenko [this message]
[not found] ` <CA+Yh0SQ7yWQBjXhKbJPrCroriNpwhyFyQWAfHsUvxwmojsjKuw@mail.gmail.com>
2019-04-25 1:37 ` bug#35419: " Noam Postavsky
2019-04-25 7:11 ` bug#35419: Fwd: " 'Ihor Radchenko'
[not found] ` <email@example.com>
2019-04-25 8:40 ` bug#35419: " Dmitrii Korobeinikov
[not found] ` <CA+Yh0SSvQMucaC1EJR9GBxpKeP6haGiHN+Lf2QYo8csNoy0Waw@mail.gmail.com>
2019-04-25 17:52 ` Philipp Stephani
[not found] ` <CAArVCkQcwnjeMyRU6rpiuvGsOCUOsnQTQwQSGdDFKwQz_Sbi3g@mail.gmail.com>
2019-04-25 21:14 ` Dmitrii Korobeinikov
2019-04-26 12:05 ` Roland Everaert
2019-05-02 21:24 ` bug#35419: " Dmitrii Korobeinikov
2019-05-02 21:31 ` Dmitrii Korobeinikov
2019-04-25 21:00 ` Dmitrii Korobeinikov
[not found] ` <CA+Yh0ST+u0s6L-hR2=rs3O_46FqXn8utGotORx+FMDb7Jn0Rfw@mail.gmail.com>
2020-04-05 1:46 ` bug#35419: [O] " Dmitry Gutov
2020-04-05 10:05 ` Dmitrii Korobeinikov
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).