From: Juri Linkov <juri@linkov.net>
To: emacs-orgmode@gnu.org
Subject: S-RET
Date: Sat, 14 Nov 2020 22:15:09 +0200 [thread overview]
Message-ID: <87sg9bn19u.fsf@mail.linkov.net> (raw)
I've switched to Org Babel as a replacement of Jupyter Notebook since I already
tired copying Julia program texts back and forth between Jupyter pages
in web browsers and Emacs. Fortunately, Org Babel can do everything that
Jupyter Notebook does. Except that there is a small usability feature
that I miss in Org Babel. Typing 'C-RET' in Jupyter evaluates the current
code block. In Org Babel 'C-RET' inserts a new heading at the end of
the current subtree. To evaluate the code block there is 'C-c C-c'
(org-ctrl-c-ctrl-c). Thus the equivalent of 'C-RET' is 'C-c C-c'.
So far, so good.
What I miss in Org Babel is an equivalent of 'S-RET' that in Jupyter
creates a new code block relative to the current code block.
Actually, in Org Babel such a command already exists and is bound to
the needed key 'S-RET', but currently it works only on tables:
the command is 'org-table-copy-down' and it copies the current field
down to the next row and moves point along with it. This is exactly
what is needed also in context of code blocks.
Maybe like there is already the command named 'org-ctrl-c-ctrl-c',
a new general command bound to e.g. 'org-s-ret' could do this
depending on context.
PS: another similarity is how typing RET in shell buffers
inserts a new prompt where the user can type a new command.
'S-RET' in code blocks could work the same way: type 'S-RET'
and write code in the next code block, and type 'S-RET' again.
next reply other threads:[~2020-11-14 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 20:15 Juri Linkov [this message]
2020-11-14 22:27 ` S-RET John Kitchin
2020-11-15 9:31 ` S-RET Juri Linkov
2020-11-16 18:37 ` S-RET John Kitchin
2020-11-16 8:37 ` S-RET Leo
2020-11-16 9:49 ` S-RET Juri Linkov
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=87sg9bn19u.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=emacs-orgmode@gnu.org \
/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).