From: TEC <email@example.com>
To: Kyle Meyer <firstname.lastname@example.org>
Cc: Jarmo Hurri <email@example.com>, firstname.lastname@example.org
Subject: Re: PATCH: Display point of code block point when confirming evaluation
Date: Wed, 30 Sep 2020 12:57:58 +0800 [thread overview]
Message-ID: <email@example.com> (raw)
Kyle Meyer <firstname.lastname@example.org> writes:
> That sounds reasonable to me, and the change looks fine to me.
> My only
> thought is that perhaps the line number would be friendlier to
> but I don't feel strongly about that.
+1 for line numbers
Assuming the current format is something like:
"Do you want to eval <lang> block at <pos> y/n:"
I'd be in favour of:
"Do you want to eval <lang> block at <pos> (line <line>) y/n:"
All the best,
next prev parent reply other threads:[~2020-09-30 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 7:26 PATCH: Display point of code block point when confirming evaluation Jarmo Hurri
2020-09-30 4:04 ` Kyle Meyer
2020-09-30 4:57 ` TEC [this message]
2020-09-30 16:46 ` Eric S Fraga
2020-10-07 3:37 ` Kyle Meyer
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).