From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Greg Minshall <minshall@umich.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: babel/noweb concatenation of equally-named code blocks fails?
Date: Wed, 22 Apr 2020 19:09:09 +0200 [thread overview]
Message-ID: <87imhrmoqy.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <1279790.1587565360@apollo2.minshall.org> (Greg Minshall's message of "Wed, 22 Apr 2020 07:22:40 -0700")
Greg Minshall <minshall@umich.edu> writes:
> two minor edits i might make to the first paragraph, 1) to make clear
> that #+name: names only one block, and 2) to (maybe?) simplify the
> latter part of the same paragraph, while, at the same time, trying to
> keep a strong mention of the distinction between =NAME= and
> =noweb-ref= at the top of the article.
Your proposal is an improvement, indeed. Thank you.
> additionally, i did some wordsmithing. i've appended a diff, hopefully
> in a useful format (C-x C-v =); i'm not a git, git patch, expert.
Could you use "git format-patch" and use a proper commit message? You
may need to add TINYCHANGE at its end, if you haven't signed FSF papers
yet.
> i wonder if there might a place in this article to mention
> org-babel-expand-src-block (C-c C-v v)? it is mentioned, tangentially,
> later in the manual (but i only came across it recently).
You are right, this is a serious omission in this part of the manual.
Would you want to document it?
next prev parent reply other threads:[~2020-04-22 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 20:07 babel/noweb concatenation of equally-named code blocks fails? Greg Minshall
2020-04-19 21:11 ` Nicolas Goaziou
2020-04-19 21:18 ` Greg Minshall
2020-04-19 21:53 ` Nicolas Goaziou
2020-04-19 23:06 ` Greg Minshall
2020-04-20 9:23 ` Nicolas Goaziou
2020-04-22 4:45 ` Greg Minshall
2020-04-22 10:50 ` Nicolas Goaziou
2020-04-22 14:22 ` Greg Minshall
2020-04-22 17:09 ` Nicolas Goaziou [this message]
2020-04-22 21:51 ` Greg Minshall
2020-04-23 8:43 ` Nicolas Goaziou
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=87imhrmoqy.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=minshall@umich.edu \
/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).