Formatting non-standard Latex-Environments

[Alken0]

Hi,

first of all: thanks for your work. The plugin is amazing.

Currently not all environments from packages are fromatted correclty (like the \begin{xltabular} environment).
I wonder if it is possible to tell the plugin to format the environment like a normal tabular-environment with the help of a comment or the settings.

[PHPirates]

We have a hardcoded list of known tabular environments and we detect user-defined environments I think. I mean, we cannot really detect this from the environment definition (I think?) so we need to hardcode something. Though maybe we could assume every environment name with 'tabular' in it is a table environment.

I don't think we have this in settings yet, but sounds like a good idea.

Do you have a specific list of environments? From which package is xltabular?

[frankbits]

Maybe it would also be possible to, for example manually configure TeXiFy this way, to handle for example \begin{minted}{<language>} the same as \begin{lstlisting}[language=<language>], with LanguageInjections...

[PHPirates]

Yes, that's why I said it sounds like a good idea to add to the settings.
The \begin{minted}{language} should be hardcoded in TeXiFy, looks like we missed that one (\newminted environments are supported), thanks for pointing that out.

[frankbits]

\begin{minted}{language} is handled as verbatim, without Syntax-Check, but not with language injections

[frankbits]

\newminted works for most cases

> \newminted environments are supported

This really helped me.

%! language = JSON
\begin{minted}{json}
{
    "key": "value"
}
\end{minted}

Using the above code shows the following errors in the IDE:

• JSON standard does not allow such tokens
• ':' expected, got '}'
• JSON standard allows only one top-level value

%! language = JSON Lines
\begin{minted}{json}
{
    "key": "value"
}
\end{minted}

With JSON Lines it gets reduces to one error:

• ':' expected, got '}'
  but does not catch errors like JSON standard does not allow trailing comma .

\begin{jsoncode}
{
    "key": "value"
}
\end{jsoncode}

Replacing %! language = JSON Lines and \begin{minted}{json} with an \newminted-environment allows fixes this problem.

%! language = InjectablePHP
\begin{minted}{php}
interface Foo {}
\end{minted}

For PHP-Code, that is started inline (works in minted with startinline-option), I have to use %! language = InjectablePHP.
This activates highlighting for php code without <?php.
The {php} still gets treated as part of the PHPCode. (no Error, as PHPStorm does not treat it as an error)

\begin{phpcode}
<?php interface Foo {}
\end{phpcode}

But when using \newminted{php}{startinline} for a php-listing it injects standard PHP, that needs a opening php-tag <?php, like %! language = PHP.
This makes sense, if startinline is not set, but maybe it could detect this option, and use the InjectablePHP-context.

%! language = InjectablePHP
\begin{phpcode}
interface Foo {}
\end{phpcode}

Currently I still need to add %! language = InjectablePHP to get PHP-support in listings without <?php.

[PHPirates]

Continued in #3544