emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tom Gillespie <tgbugs@gmail.com>
To: Greg Minshall <minshall@umich.edu>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: <<noweb>> and ?font-lock? fly-check, ...
Date: Mon, 3 May 2021 13:55:44 -0700	[thread overview]
Message-ID: <CA+G3_PP+a5+=q2ycjZic9vKCH_OWxmYgUAUp99BxJeKorGoJZA@mail.gmail.com> (raw)
In-Reply-To: <1448608.1620015074@apollo2.minshall.org>

Hi Greg,
   I just checked and it induces a syntax error, which I did not know,
but turns out to be quite useful because it means that an untangled or
incorrectly tangled file will fail to run beyond that point. Best!

On Sun, May 2, 2021 at 9:11 PM Greg Minshall <minshall@umich.edu> wrote:
> Tom, that is quite devious, actually.  thank you very much!  do you
> know, by the way, what flycheck and/or the shell make the "<<&"
> construct out to be?  cheers, Greg

  reply	other threads:[~2021-05-03 20:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02 12:28 <<noweb>> and ?font-lock? fly-check, Greg Minshall
2021-05-02 14:05 ` Diego Zamboni
2021-05-02 15:48 ` Sébastien Miquel
2021-05-02 17:43   ` Greg Minshall
2021-05-02 18:17     ` Tom Gillespie
2021-05-03  4:11       ` Greg Minshall
2021-05-03 20:55         ` Tom Gillespie [this message]
2021-05-04  2:10           ` Greg Minshall

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:

  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='CA+G3_PP+a5+=q2ycjZic9vKCH_OWxmYgUAUp99BxJeKorGoJZA@mail.gmail.com' \
    --to=tgbugs@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=minshall@umich.edu \


* 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).