emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BABEL] Seemless editing of Babel Blocks
Date: Mon, 16 Aug 2010 14:08:21 +0530	[thread overview]
Message-ID: <81hbivx88y.fsf@gmail.com> (raw)
In-Reply-To: <87k4opu5fk.fsf@gmail.com> (Eric Schulte's message of "Tue, 20 Jul 2010 15:58:07 -0700")


Eric
Apologize for duplicate post. Ccing the mailing list this time.

    Eric> Hi Jambunathan, I like the idea of displaying the
    Eric> begin/end_src lines as commented sections in the
    Eric> org-edit-special code buffer, and then potentially using them
    Eric> to change the values of the begin/end_src lines in the
    Eric> original org-mode buffer after exiting the src-edit buffer.
    Eric> It would be very cool to be able to edit header arguments
    Eric> while editing source code.  It may be hard to implement, but
    Eric> could be worth the effort.


Based on my experimentation, offering of #+begin_src and #+end_src
lines (or for that matter 'surrounding context' - leading and
trailing) is not problematic as such.

What really gets in the way (in the sense of being irksome to implement)
is the preserving and restoring of indentations while moving between the
org and org-src buffers.

I am giving up my efforts on this proposal.

1 Original Proposal 
~~~~~~~~~~~~~~~~~~~~

What is this in org-buffer


  (defun hello () 
    ""
    (message "Hello World")
    )

gets offered as 

;; #+begin_src emacs-lisp
(defun hello () 
  ""
  (message "Hello World")
  )
;; #+end_src

in org-src buffer.

All that babel has to do is to run 'comment-region' and
'uncomment-region' on leading and trailing contexts before moving into
and out-of org-src buffers. 

(un)comment-region makes sure that this could be done in a target
language agnostic way. 

Furthermore, the way emacs fills out comment blocks (while editing
them) would retain the org-like structure of the surrounding context.

Jambunathan K.

  reply	other threads:[~2010-08-16  8:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 12:10 [BABEL] Seemless editing of Babel Blocks Jambunathan K
2010-07-20 22:58 ` Eric Schulte
2010-08-16  8:38   ` Jambunathan K [this message]
2010-08-16  9:20     ` [BABEL] [PROPOSAL] " Jambunathan K
2010-09-02 23:41       ` Dan Davison
2010-09-02 23:50         ` Erik Iverson
2010-09-03 19:08         ` Tom Short
2010-09-03 20:45           ` Dan Davison
2010-09-04  8:58         ` Jambunathan K
2010-09-04 15:04           ` Eric Schulte
2010-09-05  9:55             ` Jambunathan K
2010-09-05 15:58               ` Dan Davison
2010-09-05 19:12                 ` Eric Schulte
2010-09-05 20:22               ` Eric Schulte

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=81hbivx88y.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).