From: Juri Linkov <firstname.lastname@example.org> To: email@example.com Subject: S-RET Date: Sat, 14 Nov 2020 22:15:09 +0200 Message-ID: <firstname.lastname@example.org> (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://orgmode.org * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
Org-mode mailing list This inbox may be cloned and mirrored by anyone: git clone --mirror https://orgmode.org/list/0 list/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 list list/ https://orgmode.org/list \ firstname.lastname@example.org public-inbox-index list Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.emacs.orgmode nntp://news.gmane.io/gmane.emacs.orgmode AGPL code for this site: git clone https://public-inbox.org/public-inbox.git