From: Jambunathan K <kjambunathan@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Mark and Tangle
Date: Wed, 08 Sep 2010 08:30:47 +0530 [thread overview]
Message-ID: <81sk1kykv0.fsf@gmail.com> (raw)
In-Reply-To: 87occ9unq8.fsf@gmail.com
Let me explain what I mean by selective tangling (or any one of the
other babel operations)
I mark subtrees [1]. The nearest Org equivalent would be to create a
sparse tree with say a tag match and consider the visible portions as
selected or marked.
Then babel could choose to act on just the visible portion [2] as
opposed to the whole buffer (both visible and invisible).
It would be the responsibility of the user to make sure that visible
portions of the buffer form a coherent whole and babel's results
pipeline is not entirely broken.
Needless to say, selective 'babeling' is more expressive than 'babeling'
based on language or a set of languages or just a subtree. This is
because it could capture a user's complete workflow and editing
environment.
I believe the above request is consistent with org's way of doing
things [3].
As for the thread that you reference, I believe the solution is a bit
'nerdy' (if I may use the word) and relies on advanced knowledge (for
example, org's tagging apis, programming in elisp and fact that babel
plists could indeed be lisp forms)
Footnotes:
[1] Marking as in emacs sense of the word. Think marking buffers,
marking gnus articles etc for later bulk action.
[2] That is, org-babel-do would hence forward take an additional
visibility-ok arguments.
- Visibility need not be just that of a subtree but of any structural
element.
- Modification of buffer due to insertion of #+results elements and
their visibility could slightly complicate the implementation.
[3] As of today, I do consider babel's workflow (as a literate
programming environment) is orthogonal to Org's world view. Now that
babel is a first class entity within org-mode and emacs there is a
strong reason why this orthogonality should continue to be exist.
Just my few cents here.
Jambunathan K.
"Eric Schulte" <schulte.eric@gmail.com> writes:
> I'm not sure if this exactly fits your needs, but see this recent
> related thread.
>
> http://thread.gmane.org/gmane.emacs.orgmode/29401/focus=29482
>
> Best -- Eric
>
> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> If there is support for marking (unmarking) headlines in org file it
>> could be quite useful.
>>
>> For example, selective tangling.
>>
>> Jambunathan K.
>>
>>
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-09-08 3:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 13:19 Mark and Tangle Jambunathan K
2010-09-07 23:40 ` Eric Schulte
2010-09-08 3:00 ` Jambunathan K [this message]
2010-09-08 13:57 ` Dan Davison
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=81sk1kykv0.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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/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).