emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Alexander Baier <lexi.baier@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Split source block at point
Date: Wed, 27 Nov 2013 12:48:46 +0530	[thread overview]
Message-ID: <87mwkqqpm1.fsf@gmail.com> (raw)
In-Reply-To: <87r4a2qpot.fsf@gmail.com> (Jambunathan K.'s message of "Wed, 27 Nov 2013 12:47:06 +0530")

Jambunathan K <kjambunathan@gmail.com> writes:

> C-h K C-c C-v C-d
      ^
      ^
      k

Looks like the keybindings are not indexed the canonical way in the Org
manual.
      
> Alexander Baier <lexi.baier@gmail.com> writes:
>
>> Hello together,
>>
>> is therer a command or a function that lets me split a source block at a
>> given position?  I think what I mean is best demonstrated by looking at
>> an example:
>>
>> Given this buffer:
>> ----------------------------------------------------------------
>> begin_src emacs-lisp
>>   (defun foo ()
>>     (bar))
>>
>>   (baz (foo))
>> end_src
>> ----------------------------------------------------------------
>>
>> With point somewhere at the free line I want to invoke the split
>> function and get this:
>> ----------------------------------------------------------------
>> begin_src emacs-lisp
>>   (defun foo ()
>>     (bar))
>> end_src
>>
>> begin_src emacs-lisp
>>   (baz (foo))
>> end_src
>> ----------------------------------------------------------------
>> This is similar to what M-RET does in message-mode.
>>
>> Do we already have something like this in org? And if not, do you think
>> this is useful? Personally I find myself quite frequently splitting up
>> soure blocks manually.
>>
>> Best regards,
>> --
>>  Alexander Baier

  reply	other threads:[~2013-11-27  7:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27  7:15 Split source block at point Alexander Baier
2013-11-27  7:17 ` Jambunathan K
2013-11-27  7:18   ` Jambunathan K [this message]
2013-11-27  7:39   ` Alexander Baier
2013-11-27  7:37 ` Christian Moe

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=87mwkqqpm1.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=lexi.baier@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).