Org-mode mailing list
 help / color / mirror / Atom feed
From: Diego Zamboni <>
To: Greg Minshall <>
Cc: Org-mode <>
Subject: Re: <<noweb>> and ?font-lock? fly-check, ...
Date: Sun, 2 May 2021 16:05:41 +0200
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]

I don't think there's an easy way to fix this - since src blocks are
fontified using the mode for the corresponding language. Particularly in
shell script, since << has a meaning in the language ("here" input), I
assume this is why the rest of the block gets fontified differently.


On Sun, May 2, 2021 at 2:29 PM Greg Minshall <> wrote:

> hi, all.
> using a <<noweb>> reference in a bash source block, the buffer's font
> lock colors go south on lines folowing the <<noweb>> reference.  (in my
> case, all remaining lines in the buffer are colored bright yellow).  the
> major and minor modes are as listed below.
> is there an obvious thing to do to either get whatever syntax checker is
> running to ignore the <<noweb>> reference, or some such?
> thanks in advance, Greg
> major mode: Shell-script[bash]
> Enabled minor modes: Async-Bytecomp-Package Auto-Composition
> Auto-Compression Auto-Encryption Blink-Cursor Electric-Indent
> File-Name-Shadow Flycheck Font-Lock Global-Eldoc Global-Flycheck
> Global-Font-Lock Line-Number Marginalia Menu-Bar Mouse-Wheel
> My-Global-Subword Org-Src Override-Global Selectrum
> Sh-Electric-Here-Document Shell-Dirtrack Straight-Package-Neutering
> Straight-Use-Package Subword Tooltip Transient-Mark Yas Yas-Global

[-- Attachment #2: Type: text/html, Size: 1769 bytes --]

  reply	other threads:[~2021-05-02 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02 12:28 Greg Minshall
2021-05-02 14:05 ` Diego Zamboni [this message]
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
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Org-mode mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror list/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 list list/ \
	public-inbox-index list

Example config snippet for mirrors.
Newsgroups are available over NNTP:

AGPL code for this site: git clone