From: Immanuel Litzroth <immanuel.litzroth@gmail.com>
To: sebastian.miele@gmail.com
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: noweb syntax clashing with shell here document syntax
Date: Mon, 22 Mar 2021 19:43:34 +0100 [thread overview]
Message-ID: <CAM1nAcx0Xym=WKZg8G3zJBZaCyE0zJgvZ=GzpYHf-Hr6zYXcXw@mail.gmail.com> (raw)
In-Reply-To: <87k0pzno39.fsf@gmail.com>
You can choose which delimiters signal noweb.
see the documentation of org-babel-noweb-wrap-start and
org-babel-noweb-wrap-end.
Immanuel
On Mon, Mar 22, 2021 at 5:35 PM Sebastian Miele
<sebastian.miele@gmail.com> wrote:
>
> Hello!
>
> The noweb syntax seems to clash with the syntax of here documents in
> shell scripts. In the block like
>
> #+BEGIN_SRC shell :noweb yes
> echo a
> <<A>>
> echo b
> #+END_SRC
>
> everything following the line with the the noweb reference does not
> get fontified properly. I suspect that the problem already is known
> for a long time. Is that true? If yes, what is the status of this
> issue? Is there a known workaround?
>
> At least in ZSH it may very well be the case that a line ending with
> '>>' never is valid, except in cases where something like an '<<A'
> before it is not an opening of a here document. So it possibly is
> something that could be fixed in sh-script.el. But I do not know
> exactly.
>
> Anybody who already knows more about this?
>
> Best wishes
> Sebastian
>
--
-- Researching the dual problem of finding the function that has a
given point as fixpoint.
next prev parent reply other threads:[~2021-03-22 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 16:35 noweb syntax clashing with shell here document syntax Sebastian Miele
2021-03-22 18:43 ` Immanuel Litzroth [this message]
2021-03-23 10:32 ` Sebastian Miele
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='CAM1nAcx0Xym=WKZg8G3zJBZaCyE0zJgvZ=GzpYHf-Hr6zYXcXw@mail.gmail.com' \
--to=immanuel.litzroth@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sebastian.miele@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).