emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tom Gillespie <tgbugs@gmail.com>
To: Greg Minshall <minshall@umich.edu>
Cc: sebastien.miquel@posteo.eu, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: <<noweb>> and ?font-lock? fly-check, ...
Date: Sun, 2 May 2021 11:17:10 -0700	[thread overview]
Message-ID: <CA+G3_PO-jYwphaco6vn3q20-2vNMf+ZB9UuQA_+NCA__LrCGKA@mail.gmail.com> (raw)
In-Reply-To: <1437519.1619977385@apollo2.minshall.org>

Hi Greg,
    A slightly different suggestion that doesn't break other org
processors (which might not allow users to change
org-babel-noweb-wrap- values) is to prefix the names of the blocks
with & (e.g. <<&block-to-noweb-in>>) as I do in multiple places in
I found this solution while fighting with the font-locking behavior in
shell blocks. Best!

  reply	other threads:[~2021-05-02 18:19 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 [this message]
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: 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_PO-jYwphaco6vn3q20-2vNMf+ZB9UuQA_+NCA__LrCGKA@mail.gmail.com \
    --to=tgbugs@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=minshall@umich.edu \
    --cc=sebastien.miquel@posteo.eu \


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