From: Greg Minshall <minshall@umich.edu>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: sebastien.miquel@posteo.eu, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [FR] Make :var foo=name-of-src-block assign the source block code instead of currently assigned result of evaluation (was: [PATCH] Add :noweb-prefix and :noweb-trans babel header arguments)
Date: Sat, 16 Jul 2022 17:31:13 +0300 [thread overview]
Message-ID: <2307233.1657981873@apollo2.minshall.org> (raw)
In-Reply-To: <87k08dxrnc.fsf@localhost>
Ihor,
> Alternative ideas are welcome though. I'd prefer to avoid breaking
> change if we can find an equally simple syntax alternative to assign
> source block code to a variable.
my two cents would be to avoid the breaking change. (i notice, for
example, that i use this construct in some of my .org files.)
cheers, Greg
next prev parent reply other threads:[~2022-07-16 14:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 10:42 [PATCH] Add :noweb-prefix and :noweb-trans babel header arguments Sébastien Miquel
2022-04-28 13:45 ` Ihor Radchenko
2022-04-29 14:27 ` Sébastien Miquel
2022-04-30 6:05 ` Ihor Radchenko
2022-04-30 7:35 ` Sébastien Miquel
2022-04-30 8:41 ` Ihor Radchenko
2022-05-30 19:51 ` Sébastien Miquel
2022-05-31 5:14 ` Ihor Radchenko
2022-05-31 6:48 ` Sébastien Miquel
2022-07-16 8:57 ` [FR] Make :var foo=name-of-src-block assign the source block code instead of currently assigned result of evaluation (was: [PATCH] Add :noweb-prefix and :noweb-trans babel header arguments) Ihor Radchenko
2022-07-16 10:17 ` Greg Minshall
2022-07-16 10:45 ` Ihor Radchenko
2022-07-16 14:31 ` Greg Minshall [this message]
2022-07-17 17:39 ` Sébastien Miquel
2022-07-23 4:52 ` Ihor Radchenko
2022-08-29 17:39 ` [PATCH] " Sébastien Miquel
2022-08-31 4:04 ` Ihor Radchenko
2022-07-21 11:13 ` [PATCH] org-babel: Do not echo output of resolved noweb references Ihor Radchenko
2022-07-21 13:41 ` Sébastien Miquel
2022-08-22 12:01 ` Ihor Radchenko
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=2307233.1657981873@apollo2.minshall.org \
--to=minshall@umich.edu \
--cc=emacs-orgmode@gnu.org \
--cc=sebastien.miquel@posteo.eu \
--cc=yantar92@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).