From: Suhail Singh <suhailsingh247@gmail.com>
To: Vladimir Kazanov <vekazanov@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Suhail Singh <suhailsingh247@gmail.com>,
jimjoe@gmx.net, emacs-devel@gnu.org, adam@alphapapa.net
Subject: Re: Buffers with buffers (transclusion)
Date: Fri, 18 Oct 2024 20:25:45 -0400 [thread overview]
Message-ID: <871q0d2b1y.fsf@gmail.com> (raw)
In-Reply-To: <CAAs=0-0bctvYYNjSNWU7JW6E2cLUzvV-gW5ZFT13uy_t1ggurg@mail.gmail.com> (Vladimir Kazanov's message of "Fri, 18 Oct 2024 10:25:03 +0100")
Vladimir Kazanov <vekazanov@gmail.com> writes:
>> What bothers me in this entire discussion is that people are
>> discussing implementation without first describing the use cases,
>> requirements, and expectations in enough detail to think about both
>> the need/importance and possible implementations.
>
> 1. org-transclusion (https://github.com/nobiot/org-transclusion/) is a
> popular (1000 stars on Github) org-mode expansion that makes it
> possible to mix and match within a single org-mode file chunks of
> other org-mode files. It's like chunk-edit.el but focuses on org-mode
> only. It provides a live buffer sync feature.
Specifically, I make frequent use of org-transclusion . At any given
time I may be involved in one or more projects at $work. I need the
ability to summarize (for a given time period) my contributions towards
a specific project. Simultaneously, I also need the ability to
summarize my contributions (for a given time period) across all
projects. By having project-specific Org files where I maintain
project-specific summaries and having a joint Org file that links to the
project-specific summaries and "transcludes" them (i.e., inlines their
specific content) I am able to address both needs.
--
Suhail
next prev parent reply other threads:[~2024-10-19 0:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 13:53 Buffers with buffers (transclusion) Vladimir Kazanov
2024-10-15 14:45 ` Eli Zaretskii
2024-10-15 15:01 ` Vladimir Kazanov
2024-10-16 22:44 ` James Thomas
2024-10-17 6:27 ` Eli Zaretskii
2024-10-17 8:38 ` Vladimir Kazanov
2024-10-17 11:00 ` Eli Zaretskii
2024-10-17 11:38 ` Vladimir Kazanov
2024-10-17 12:59 ` Eli Zaretskii
2024-10-17 13:24 ` Vladimir Kazanov
2024-10-17 15:15 ` Eli Zaretskii
2024-10-17 14:36 ` Suhail Singh
2024-10-17 15:19 ` Eli Zaretskii
2024-10-17 16:28 ` Suhail Singh
2024-10-17 17:18 ` Eli Zaretskii
2024-10-18 9:25 ` Vladimir Kazanov
2024-10-19 0:25 ` Suhail Singh [this message]
2024-10-17 14:09 ` James Thomas
-- strict thread matches above, loose matches on Subject: below --
2024-10-15 17:57 Christopher Howard
2024-10-16 10:48 ` Vladimir Kazanov
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=871q0d2b1y.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=adam@alphapapa.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jimjoe@gmx.net \
--cc=vekazanov@gmail.com \
/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.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).