From: Jay Iyer <jayiyer09@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Code block eval scope - subtree only option ignored
Date: Fri, 24 Feb 2017 11:56:19 -0800 [thread overview]
Message-ID: <CAGGEobXp0EkzuoBJ_25HPajmTUaQy9zCe02AnUmahPVRACvkeg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 253 bytes --]
Hi, evaluating a simple elisp code block in a subtree, called with C-c C-v
C-s or just C-c C-C, evaluates the entire Org buffer. Is this expected
behavior?
How can I force the eval on the visible portion (with narrowing) of the
tree only?
Thanks,
-jay
[-- Attachment #2: Type: text/html, Size: 564 bytes --]
next reply other threads:[~2017-02-24 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 19:56 Jay Iyer [this message]
2017-02-24 21:50 ` Code block eval scope - subtree only option ignored Charles C. Berry
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=CAGGEobXp0EkzuoBJ_25HPajmTUaQy9zCe02AnUmahPVRACvkeg@mail.gmail.com \
--to=jayiyer09@gmail.com \
--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).