-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add more test cases #13
Comments
Hi, I noticed that the current version doesn't look at sectioning commands. For example, the following snippet: \section{Introduction}
If a sectioning command is on the first line, it should remain there.
\subsection{Related Works}
However, a sectioning command in the middle of the file should have an empty line before it.
Also, these commands should be on their own line.\subsection{Our Contributions}And another.\subsection{Outline}
\section{Preliminaries}
However a well-formatted sectioning command should not move.
only gets line-wrapped into: \section{Introduction}
If a sectioning command is on the first line, it should remain there.
\subsection{Related Works}
However, a sectioning command in the middle of the file should have
an empty line before it.
Also, these commands should be on their own line.\subsection{Our
Contributions}And another.\subsection{Outline}
\section{Preliminaries}
However a well-formatted sectioning command should not move.
Whereas it should perhaps be formatted to: \section{Introduction}
If a sectioning command is on the first line, it should remain there.
\subsection{Related Works}
However, a sectioning command in the middle of the file should have
an empty line before it.
Also, these commands should be on their own line.
\subsection{Our Contributions}
And another.
\subsection{Outline}
\section{Preliminaries}
However a well-formatted sectioning command should not move.
If this would be a useful test to include, I could make a PR into |
Thanks for this! I agree that commands such as |
More test cases are always appreciated, to ensure that tex-fmt is behaving correctly, to understand the performance on different documents, and to prevent regressions.
The text was updated successfully, but these errors were encountered: