emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: S-RET
Date: Sun, 15 Nov 2020 11:31:28 +0200	[thread overview]
Message-ID: <87y2j3ge4v.fsf@mail.linkov.net> (raw)
In-Reply-To: <CAJ51ETo6-p4uNndY42yCuy2eGWY3AwFm6s+FnDtnKRG-3a9reA@mail.gmail.com> (John Kitchin's message of "Sat, 14 Nov 2020 17:27:43 -0500")

> you can find a lot of functions like the ones in jupyter at
> https://github.com/jkitchin/scimax/blob/master/scimax-ob.el. I setup my
> ipython like this:
> https://github.com/jkitchin/scimax/blob/master/scimax-org-babel-ipython-upstream.el#L89
>
> although I will note there are several setups in that file, e.g. this
> hydra:
> https://github.com/jkitchin/scimax/blob/master/scimax-org-babel-ipython-upstream.el#L271
> …
> I don't use them all, but leave them to remind me sometimes.

Thanks, the number of supported features is impressive!

I see that the file name contains the word 'upstream'.  This implies a set
of patches to upstream modules.  Are there any plans to submit upstream
at least some of the most often used commands that correspond to
basic Jupyter shortcuts?

For example, it would make sense to bring scimax-execute-and-next-block
under the org-babel namespace as e.g. org-babel-execute-src-block-and-next-block
in the upstream ob-core.el.  Then S-RET will be available to other ob backends
(such as ob-ruby.el that I use often too.)


  reply	other threads:[~2020-11-15  9:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14 20:15 S-RET Juri Linkov
2020-11-14 22:27 ` S-RET John Kitchin
2020-11-15  9:31   ` Juri Linkov [this message]
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=87y2j3ge4v.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    /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).