From: Ihor Radchenko <yantar92@posteo.net>
To: pareto optimal <pareto.optimal@mailfence.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org babel noweb expansion includes extra newline
Date: Sun, 23 Oct 2022 05:29:36 +0000 [thread overview]
Message-ID: <87sfjfp0ov.fsf@localhost> (raw)
In-Reply-To: <1988480151.334881.1643853809467@ichabod.co-bxl>
pareto optimal <pareto.optimal@mailfence.com> writes:
> #+RESULTS:
> #+begin_example
> "git ls-files ~/system/users/profiles/emacs/default.nix
> git ls-files ~/system/users/profiles/emacs/emacs-packages.nix
> git ls-files ~/system/users/profiles/chat/default.nix
> git ls-files ~/system/profiles/misc/default.nix
> git ls-files "
> #+end_example
> *** here's what hapepns if we just run =all-tangled-filepaths=
>
> ...
> #+name: files-to-remove-from-git
> #+begin_src sh :noweb yes :dir ~/system
> git ls-files <<all-tangled-filepaths()>>
> #+end_src
This is because noweb automatically appends text before <<...>> to each
line of multi-line noweb expansions.
See https://orgmode.org/manual/Noweb-Reference-Syntax.html
On the latest Org, this behaviour can be disabled using :noweb-prefix no
header argument.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2022-10-24 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 2:03 Org babel noweb expansion includes extra newline pareto optimal
2022-10-23 5:29 ` Ihor Radchenko [this message]
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=87sfjfp0ov.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=pareto.optimal@mailfence.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).