-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unnecessary reverse indent of \item in nested enumerate environment #2670
Comments
Indentation is hard. So, before I agree this is a bug, let's first consider the example. Let's assume we use spaces and indent width of 2. Then the following should represent the example you provide: \begin{enumerate}
\item \begin{enumerate}
\item hello
world
\item hello
again
\end{enumerate}
\item hello
moon
\end{enumerate} I think my listing here also represents the correct indentation. And it seems that this does not work as expected now and so it may be a bug. But before I look closer, do you agree that this looks correctly indented to you? Notice, just to be clear: I am not trying to align |
Yes, I agree that the provided example represents the expected behaviour. There should be 3x indents before the inner |
I think this should be fixed now. |
I can confirm that the indentation works properly now. Thanks for fixing it! |
Great, glad to hear it works! |
Description
The indentation of
\item
seems to work improperly in a nestedenumerate
environment (enumerate
in anotherenumerate
). When I enter an\item
in a nestedenumerate
and type a space, the\item
gets indented backwards unnecessarily.Steps to reproduce
\item
in theenumerate
environment, after that start anotherenumerate
(where|
stands for the cursor position):\item
(which belongs to the innerenumerate
):Expected behavior
The inner
\item
should stay in place after the space is typed, like this:Actual behavior
The following recording shows the problematic actual behavior -
\item
gets falsely indented back:nested_enumerate.mov
Do you use a latexmkrc file?
No
VimtexInfo
The text was updated successfully, but these errors were encountered: