[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: <<noweb>> and ?font-lock? fly-check, ...
From: |
Tom Gillespie |
Subject: |
Re: <<noweb>> and ?font-lock? fly-check, ... |
Date: |
Mon, 3 May 2021 13:55:44 -0700 |
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!
Tom
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
>
- <<noweb>> and ?font-lock? fly-check, ..., Greg Minshall, 2021/05/02
- Re: <<noweb>> and ?font-lock? fly-check, ..., Diego Zamboni, 2021/05/02
- Re: <<noweb>> and ?font-lock? fly-check, ..., Sébastien Miquel, 2021/05/02
- Re: <<noweb>> and ?font-lock? fly-check, ..., Greg Minshall, 2021/05/02
- Re: <<noweb>> and ?font-lock? fly-check, ..., Tom Gillespie, 2021/05/02
- Re: <<noweb>> and ?font-lock? fly-check, ..., Greg Minshall, 2021/05/03
- Re: <<noweb>> and ?font-lock? fly-check, ...,
Tom Gillespie <=
- Re: <<noweb>> and ?font-lock? fly-check, ..., Greg Minshall, 2021/05/03