Bug#886285: vim-runtime: tex syntax highlighting fails to enter math mode within align environment
jamessan at debian.org
Thu Feb 1 01:07:04 UTC 2018
On Wed, Jan 31, 2018 at 11:33:30PM +0100, Francesco Poli wrote:
> On Mon, 29 Jan 2018 21:12:01 -0500 James McCoy wrote:
> > On Mon, Jan 29, 2018 at 07:33:40PM +0100, Francesco Poli wrote:
> > > So I am puzzled: upstream dropped support for extended syntax provided
> > > by LaTeX packages (such as, for instance, amsmath), but, at the same
> > > time, suggest users to write extensions and contribute them upstream!
> > >
> > > Do you find this confusing?
> > No. There are lots of extensions to TeX, so he has decided to limit the
> > scope of what he supports in the main syntax file. He has also provided
> > a mechanism for other people to add support for extensions.
> Yes, but he also suggest those other people to contribute this enhanced
> Hence, I am not completely sure I understand the strategy.
The strategy is to focus on a specified scope and ask other people to
volunteer to develop/maintain support for extra packages.
> > As part of the package maintenance, neither are we going to develop the
> > syntax files for extensions nor solicit others to do so. Therefore I'm
> > closing this.
> I was not asking you to develop syntax files for extensions, or to
> solicit others to do so.
> I was just asking you to forward my feature request upstream.
That's just it, though. There is no upstream to forward the request to.
Someone has to volunteer to do the work to support the amsmath package
and that person would then be the upstream.
Charles isn't upstream because he's explicitly restricted the scope of
what syntax/tex.vim is going to cover. Bram isn't upstream because he
just aggregates runtime files from their maintainers when they request
to have them included with Vim.
That's why there's no action that I can take on this.
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
More information about the pkg-vim-maintainers