emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Aaron Ecay <aaronecay@gmail.com>
To: "Charles C. Berry" <ccberry@ucsd.edu>,
	Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [PATCH][BUG] org-babel-confirm-evaluate
Date: Sat, 07 Nov 2015 10:48:30 +0000	[thread overview]
Message-ID: <87twoyt79d.fsf@gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1511061604510.2161@charles-berrys-macbook.local>

Hi Chuck,

The patch is fundamentally correct, please push it.  A couple minor
comments:

2015ko azaroak 7an, "Charles C. Berry"-ek idatzi zuen:

[...]

> +      (`query (or
> +	       (and (not (org-bound-and-true-p
> +			  org-babel-confirm-evaluate-answer-no))
> +		    (yes-or-no-p
> +		     (format "Evaluate this %s code block%s on your system? "
                                                          ^^^
Rather than inserting that space, you should make the no-name value of
name-string a single space.  Otherwise there will be two spaces if the
block does have a name.

> +			     lang name-string)))
> +	       (and
> +		(message "Evaluation of this %s code-block%s is aborted."
> +			 lang name-string)
> +		nil)))

I think ‘progn’ would be better than ‘and’ here, just as a matter of
style.  Same comment as above applies about the extra space.

Thanks very much for the patch, and sorry for the breakage,
Aaron

PS Git gave me some strange errors about trailing whitespace when trying
to apply your patch, until I converted it from DOS to Unix line
endings.  I’ve never seen git do that before – I think it usually copes
very well with different line ending styles.  Does anyone know what to
do in this scenario?  Manually changing the line endings of the patch
file seems hackish.

-- 
Aaron Ecay

  reply	other threads:[~2015-11-07 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07  0:11 [PATCH][BUG] org-babel-confirm-evaluate Charles C. Berry
2015-11-07 10:48 ` Aaron Ecay [this message]
2015-11-07 18:13   ` Charles C. Berry
2015-11-07 21:36     ` Aaron Ecay

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=87twoyt79d.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=ccberry@ucsd.edu \
    --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).