inner environment text-object fails on { being the first char after \begin{}

[habamax]

Description

No way to visually select or delete inner environment with vie, die for the code block of the json source.

Steps to reproduce

1. vim -u minimal.vim minimal.tex
2. position cursor on "contacts"
3. vie

minimal.tex

\documentclass{minimal}
\begin{document}
\begin{minted}
    {
        "contacts": [
          {
            "source_id": "mandatory"
          }
        ]
    }
\end{minted}
\end{document}

Expected behavior

Contents of the minted environment is visually selected:

Actual behavior

A single char is selected at the end of the environment:

Do you use a latexmkrc file?

No

VimtexInfo

System info
  OS: Microsoft Windows 10 Pro (10.0.19041 N/A Build 19041)
  Vim version: VIM 8.2 (1-3399)
  Has clientserver: true
  Servername: GVIM

VimTeX project: minimal
  base: minimal.tex
  root: C:\Users\maksim.kim
  tex: C:\Users\maksim.kim\minimal.tex
  main parser: current file
  document class: 
  compiler: latexmk
    engine: -lualatex
    options:
      -shell-escape
      -verbose
      -file-line-error
      -synctex=1
      -interaction=nonstopmode
    build_dir: minimal
    callback: 1
    continuous: 1
    executable: latexmk
  viewer: General
  qf method: LaTeX logfile

[habamax]

It didn't work for me with crowded minted environment:

And only if I add non { char (not space) before { it starts recognizing inner environment:

[habamax]

And vae, dae works no matter what.

[lervag]

vae and dae are simple. The problem here is that the initial { is very confusing. There is no "generic" manner to parse TeX reliably, so how do we know it is not part of the \begin{...}[..]{..} command?

[lervag]

I think we need to make some heuristic, but I'm not sure if it is safe to do so.

[lervag]

You would get the same problem with

\begin{minted}
    [
        "contacts": [
          {
            "source_id": "mandatory"
          }
        ]
    ]
\end{minted}

The point, as hinted, is that VimTeX parses \begin{minted}{...} as the beginning of the environment. The parser allows separating white space, including newlines. And this really is allowed LaTeX. Notice that the following will compile perfectly fine:

\documentclass{article}
\usepackage{minted}
\begin{document}

\begin{minted}
  [
    numbersep=5mm,
    linenos=true,
    fontsize=\footnotesize,
    breaklines
  ]
  {
    json
  }
  {
    "contacts": [
      {
        "source_id": "mandatory"
      }
    ]
  }
\end{minted}
\end{document}

My point is only to show that it really is hard to properly parse this stuff. And I don't know if I'm able to really find a good way to make it work reliably.

[lervag]

In my last example: I think we can both agree that the inner part of the environment starts at {\n "contacts" (\n indicates newline). But the current parser is greedy and "gobbles" up the last { ... } also as an argument for \begin{minted}, and so it puts the start of the inner area at the final } before \end{minted}.

So, at least the issue is now fully understood and explained. It remains to see if it is possible to suggest any solution. I'm afraid it is going to be hard.. :\

[lervag]

Perhaps a workaround is to add an empty line first? Or a json comment?

[habamax]

I can totally understand it is not a trivial thing to do, indeed.

1. Empty line doesn't make any difference
2. json comment might be a workaround but for now I just vaekoj :)

[habamax]

I am thinking of non-greedy {}[]{} detection, could you point me to the place where it is defined?

[habamax]

One additional thing: cac on \begin deletes all the way up to \end :)

[lervag]

Yes; for the exact same reason.

[lervag]

It is more or less impossible to write a perfect parser here, I believe. To do so, we need to know the exact signature of each command. But we don't. :\

[lervag]

I am thinking of non-greedy {}[]{} detection, could you point me to the place where it is defined?

In some cases, non-greedy would be perfect. In others, it would not be good and you would have to adjust.