On Wednesday, October 4, 2023 at 8:02:42 PM UTC-5 M wrote:
> a consequence of having many poorly written syntax files. Main
distribution included
Your idea of a different override for syntax-include is the practical
solution. As you pointed out, syntax-include is dependent on the authors of
On Wednesday, October 4, 2023 at 1:55:55 PM UTC-5 Christian Brabandt wrote:
> Either nobody knows the answer or nobody understood the problem.
Thank you Christian, I'm glad to know it got out there anyway.
So maybe it will help for me to restate the problem, maybe not.
This has to do with
This question got no replies. Did it fail to be circulated? Does nobody
know the answer? Is it a stupid question? :)
On Thursday, September 14, 2023 at 1:22:07 PM UTC-5 Edward McGuire wrote:
> On Friday, July 21, 2023 at 3:18:39 PM UTC-5 Edward McGuire wrote:
> > how can I reliably ALW
On Friday, July 21, 2023 at 3:18:39 PM UTC-5 Edward McGuire wrote:
> how can I reliably ALWAYS limit embedded language highlighting to the
region that contains it, without the chance that the embedded language can
break out?
Still looking for a solution to this -- how to prevent pre-instal
I developed a syntax file for Noweb -- if you're unfamiliar, it's a
Literate Programming tool. Noweb source is LaTeX source, but with embedded
code blocks. The embedded code blocks are delimited, and I define a syntax
region that recognizes the delimiters. Inside a code block, I get
On Tuesday, May 30, 2023 at 12:38:34 PM UTC Christian Brabandt wrote:
> What is the script id? I might be able to check it on the server (no
promises however).
Originally "vim-noweb", and also when I ran into the problem I tried making
the ID the same as the filename "vim-noweb.tar.gz" and
This is my first time to try to contribute a Vim plugin to vim.org.
Where is this newbie going wrong?
I offered a tarball containing an ftdetect, a syntax, and a README and
LICENSE.
The site replied: "The package you uploaded (vim-noweb.tgz) is empty".
I have already extracted my own tarball to
