cmhughes
commented
3 years ago Thanks for this. I'll take a proper look at this over the next few days.
In the meantime, how does the script behave on your big file without the m switch active?
The m switch is a known memory hog.
On Tue, 6 Jul 2021, 05:56 Peter Corke, @.***> wrote:
Please provide the following when posting an issue: original .tex code
It's a big file, a book manuscript that I can't post publicly but happy to share privately.
Here's a snippet, and the corresponding output is given further down. Even this snippet in a file by itself doesn't format right, so I'm guessing I'm doing something wrong.
\subsection{Images from Files}\label{sec:12.1.1}
We start with images stored in files since it is very likely that you already have lots of images stored on your computer. In this chapter we will work with some images provided with the Toolbox, but you can easily substitute your own images. We import an image into the MATLAB workspace using the Toolbox function \lstinline{iread}\FUNCTION{iread}\begin{lstlisting}
street = iread('street.png');\end{lstlisting} which returns a matrix\FUNCTION{about}\begin{lstlisting} about(street) street [uint8] : 851x1280 (1.1 MB)\end{lstlisting} that belongs to the class \FUNCTION{uint8}\lstinline{uint8} -- the elements of the matrix are unsigned 8-bit integers in the interval $[0,255]$. The elements are referred to as pixel values or \INDEX{grey value}grey values and are the gamma-encoded\SIDENOTE{Gamma encoding and decoding is discussed in \secref{sec:10.3.6}. Use the \lstinline{'gamma'} option for \lstinline{iread} to perform gamma decoding and obtain pixel values proportional to scene luminance.} luminance of that point in the original scene. For this 8-bit image the pixel values vary from 0 (darkest) to 255 (brightest). The image is shown in \figref{fig:12.1}{a}. \begin{figure}[t!]\includegraphics{M_4_012_001}\caption{The \lstinline{idisp} image browsing window. The top right shows the coordinate and value of the last pixel clicked on the image. The \textit{buttons} at the top left allow the pixel values along a line to be plotted, a \INDEX{histogram}histogram to be displayed, or the image to be zoomed. \textbf{a}~Greyscale image; \textbf{b}~color image}\label{fig:12.1}\end{figure}
yaml settings
modifyLineBreaks: preserveBlankLines: 1 condenseMultipleBlankLinesInto: 1 textWrapOptions: columns: 100
actual/given output
\subsection{Images from Files}\label{sec:12.1.1}
We start with images stored in files since it is very likely that you already have lots of images stored on your computer. In this chapter we will work with some images provided with the Toolbox, but you can easily substitute your own images. We import an image into the MATLAB workspace using the Toolbox function \lstinline{iread}\FUNCTION{iread} \begin{lstlisting}
street = iread('street.png'); \end{lstlisting} which returns a matrix\FUNCTION{about} \begin{lstlisting} about(street) street [uint8] : 851x1280 (1.1 MB) \end{lstlisting} that belongs to the class \FUNCTION{uint8}\lstinline{uint8} -- the elements of the matrix are unsigned 8-bit integers in the interval $[0,255]$. The elements are referred to as pixel values or \INDEX{grey value}grey values and are the gamma-encoded\SIDENOTE{Gamma encoding and decoding is discussed in \secref{sec:10.3.6}. Use the \lstinline{'gamma'} option for \lstinline{iread} to perform gamma decoding and obtain pixel values proportional to scene luminance.} luminance of that point in the original scene. For this 8-bit image the pixel values vary from 0 (darkest) to 255 (brightest). The image is shown in \figref{fig:12.1}{a}
the line after the second\end{ lstlisting} is very long in the input. On output it has been broken/formatted oddly. The first line is very long, the second ok, the third is indented.
A similar things happens with the caption. desired or expected output
- no lines longer than the requested 100 chars
- no indents in the middle of blocks
- no memory hogging
anything else
It's a big file, that is included into a main, so there is no preamble. I use custom commands/macros but they are pretty simple, just take a single argument.
The whole file is ~1900 lines long and it just hangs. After a couple of minutes its pushing 10GB of memory. Even with -tt nothing is written to the log file. If I take the first half of file it works quite quickly but the formatting is not what I was expecting, see above.
I had hoped that slicing/dicing the file would work but there's something in the file that is throwing it.
I have tried removing or translating unicode chars to ASCII but that didn't help.
% latexindent -v 3.9.3, 2021-05-07
% perl -v
This is perl 5, version 34, subversion 0 (v5.34.0) built for darwin-thread-multi-2level
Copyright 1987-2021, Larry Wall
running on macOS Catalina.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cmhughes/latexindent.pl/issues/279, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQ7CYGDZH4A7MTVDQLSQKDTWKEHNANCNFSM473ZE5UA .
petercorke
Please provide the following when posting an issue:
original .tex code
It's a big file, a book manuscript that I can't post publicly but happy to share privately.
Here's a snippet, and the corresponding output is given further down. Even this snippet in a file by itself doesn't format right, so I'm guessing I'm doing something wrong.
yaml settings
actual/given output
the line after the second
\end{ lstlisting}is very long in the input. On output it has been broken/formatted oddly. The first line is very long, the second ok, the third is indented.A similar things happens with the caption.
desired or expected output
anything else
It's a big file, that is included into a main, so there is no preamble. I use custom commands/macros but they are pretty simple, just take a single argument.
The whole file is ~1900 lines long and it just hangs. After a couple of minutes its pushing 10GB of memory. Even with -tt nothing is written to the log file. If I take the first half of file it works quite quickly but the formatting is not what I was expecting, see above.
I had hoped that slicing/dicing the file would work but there's something in the file that is throwing it.
I have tried removing or translating unicode chars to ASCII but that didn't help.
running on macOS Catalina.