emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dmitrii Korobeinikov <dim1212k@gmail.com>
To: Roland Everaert <reveatwork@gmail.com>
Cc: 35419@debbugs.gnu.org
Subject: bug#35419: bug#35419: [Proposal] Buffer Lenses and the Case of Org-Mode (also, Jupyter)
Date: Fri, 3 May 2019 18:06:57 +0600	[thread overview]
Message-ID: <CA+Yh0SQAD3ut0-opoBP8aUfhJEapSRhn8Y3YdOV_1cEtMLxqVQ@mail.gmail.com> (raw)
In-Reply-To: <87lfzn4x61.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

Understood, thank you!

пт, 3 мая 2019 г. в 17:03, Roland Everaert <reveatwork@gmail.com>:

> For what I understand of eev (which I discover following this thread),
> the idea is to create "notebooks" (à la Jupyter) of commands that can be
> executed in
> any orders the user want. So, lenses could be useful to apply the
> correct mode the block of code at point.
>
> Dmitrii Korobeinikov writes:
>
> >> I see lens to be useful for the eev mode, too.
> >
> > Never heard of eev, but judging by some demos, it's a way to execute
> elisp
> > commands interactively.
> > Something like stitching blocks of commands together, or the data to
> > operate on, or embedding a target such as a shell in the same buffer is
> the
> > use-case idea then?
>
>
> --
> Luke, use the FOSS
>
> Sent from Emacs
>

[-- Attachment #2: Type: text/html, Size: 1180 bytes --]

  reply	other threads:[~2019-05-03 12:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+Yh0STecZHv_dxGEMOuy9F7X_dnxbCfNX5KnekwfZW_hQXYsg@mail.gmail.com>
2019-05-03 11:03 ` bug#35419: bug#35419: [Proposal] Buffer Lenses and the Case of Org-Mode (also, Jupyter) Roland Everaert
2019-05-03 12:06   ` Dmitrii Korobeinikov [this message]
     [not found] <CA+Yh0SQ7yWQBjXhKbJPrCroriNpwhyFyQWAfHsUvxwmojsjKuw@mail.gmail.com>
2019-05-02 21:24 ` Dmitrii Korobeinikov

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=CA+Yh0SQAD3ut0-opoBP8aUfhJEapSRhn8Y3YdOV_1cEtMLxqVQ@mail.gmail.com \
    --to=dim1212k@gmail.com \
    --cc=35419@debbugs.gnu.org \
    --cc=reveatwork@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).