emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

* Mark and Tangle
@ 2010-09-04 13:19 Jambunathan K
  2010-09-07 23:40 ` Eric Schulte
  0 siblings, 1 reply; 4+ messages in thread
From: Jambunathan K @ 2010-09-04 13:19 UTC (permalink / raw)
  To: emacs-orgmode


If there is support for marking (unmarking) headlines in org file it
could be quite useful.

For example, selective tangling.

Jambunathan K.

^ permalink raw reply	[flat|nested] 4+ messages in thread

• * Re: Mark and Tangle
    2010-09-04 13:19 Mark and Tangle Jambunathan K
  @ 2010-09-07 23:40 ` Eric Schulte
    2010-09-08  3:00   ` Jambunathan K
    0 siblings, 1 reply; 4+ messages in thread
  From: Eric Schulte @ 2010-09-07 23:40 UTC (permalink / raw)
    To: Jambunathan K; +Cc: emacs-orgmode
  
  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
  
  ^ permalink raw reply	[flat|nested] 4+ messages in thread

• • * Re: Mark and Tangle
      2010-09-07 23:40 ` Eric Schulte
    @ 2010-09-08  3:00   ` Jambunathan K
      2010-09-08 13:57     ` Dan Davison
      0 siblings, 1 reply; 4+ messages in thread
    From: Jambunathan K @ 2010-09-08  3:00 UTC (permalink / raw)
      To: Eric Schulte; +Cc: emacs-orgmode
    
    
    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
    
    ^ permalink raw reply	[flat|nested] 4+ messages in thread

  • • * Re: Mark and Tangle
        2010-09-08  3:00   ` Jambunathan K
      @ 2010-09-08 13:57     ` Dan Davison
        0 siblings, 0 replies; 4+ messages in thread
      From: Dan Davison @ 2010-09-08 13:57 UTC (permalink / raw)
        To: Jambunathan K; +Cc: emacs-orgmode
      
      Jambunathan K <kjambunathan@gmail.com> writes:
      
      > 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.
      
      Hi Jambunathan,
      
      Org-mode has an established mechanism for selective export, which uses
      tags
      
      http://orgmode.org/manual/Selective-export.html#Selective-export
      
      I think this could be viewed as an Org version of "marking
      subtrees". Perhaps selective tangling should be implemented in an
      analogous fashion?  (so that it happens automatically, without requiring
      obscure lisp forms in babel header args).
      
      Dan
      
      
      >
      > 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.
      >>
      >> this >>
      >> 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
      >
      > _______________________________________________
      > 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
      
      ^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2010-09-08 13:57 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-09-04 13:19 Mark and Tangle Jambunathan K
2010-09-07 23:40 ` Eric Schulte
2010-09-08  3:00   ` Jambunathan K
2010-09-08 13:57     ` Dan Davison

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).