From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: PATCH: Display point of code block point when confirming evaluation
Date: Sat, 07 Dec 2019 09:26:57 +0200 [thread overview]
Message-ID: <87sglwoata.fsf@iki.fi> (raw)
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
Greetings.
Please find attached a patch that adds the point of the source code
block to the message shown to user when confirming the evaluation of the
block.
In large org-files, I have often trouble figuring out which code block
Org is confirming me to evaluate when exporting. This is especially true
when I have set 'cache: yes'. When something changes in code, these
blocks need to be re-evaluated during export, but the '#results:' of
these blocks are not changed. Therefore, on the next export I will be
asked again, unless I find the block and evaluate it by hand myself.
This patch adds the 'start' element of source block info at the end of
the confirmation message.
Jarmo
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: point in confirm --]
[-- Type: text/x-patch, Size: 1649 bytes --]
From aaa68af8a7710ffe2c61fc45edf2ff377438cd32 Mon Sep 17 00:00:00 2001
From: Jarmo Hurri <jarmo.hurri@iki.fi>
Date: Sat, 7 Dec 2019 09:14:34 +0200
Subject: [PATCH] ob-core.el: Display block point during evaluation
confirmation
* lisp/ob-core.el (org-babel-confirm-evaluate): Display code block
point when querying confirmation of evaluation.
This addresses the problem of finding the block currently evaluated.
---
lisp/ob-core.el | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/lisp/ob-core.el b/lisp/ob-core.el
index f877ff51b..7ba9894e6 100644
--- a/lisp/ob-core.el
+++ b/lisp/ob-core.el
@@ -277,7 +277,8 @@ environment, to override this check."
(let* ((evalp (org-babel-check-confirm-evaluate info))
(lang (nth 0 info))
(name (nth 4 info))
- (name-string (if name (format " (%s) " name) " ")))
+ (name-string (if name (format " (%s) " name) " "))
+ (start (nth 5 info)))
(pcase evalp
(`nil nil)
(`t t)
@@ -285,11 +286,11 @@ environment, to override this check."
(and (not (bound-and-true-p
org-babel-confirm-evaluate-answer-no))
(yes-or-no-p
- (format "Evaluate this %s code block%son your system? "
- lang name-string)))
+ (format "Evaluate this %s code block%son your system (point %d)? "
+ lang name-string start)))
(progn
- (message "Evaluation of this %s code block%sis aborted."
- lang name-string)
+ (message "Evaluation of this %s code block%sis aborted (point %d)."
+ lang name-string start)
nil)))
(x (error "Unexpected value `%s' from `org-babel-check-confirm-evaluate'" x)))))
--
2.21.0
next reply other threads:[~2019-12-07 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 7:26 Jarmo Hurri [this message]
2020-09-30 4:04 ` PATCH: Display point of code block point when confirming evaluation Kyle Meyer
2020-09-30 4:57 ` TEC
2020-09-30 16:46 ` Eric S Fraga
2020-10-07 3:37 ` Kyle Meyer
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=87sglwoata.fsf@iki.fi \
--to=jarmo.hurri@iki.fi \
--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).