diff options
author | Norbert Preining <norbert@preining.info> | 2022-03-14 03:01:40 +0000 |
---|---|---|
committer | Norbert Preining <norbert@preining.info> | 2022-03-14 03:01:40 +0000 |
commit | 9754713ebfdd18985b356efe48892afe656e3d37 (patch) | |
tree | f8056e63e7d97caacbfcfee61a468bfc0137fe44 /support/latexindent/documentation/sec-conclusions-know-limitations.tex | |
parent | 830142c7beb66ea5baa91b009ecea1529eaa70b0 (diff) |
CTAN sync 202203140301
Diffstat (limited to 'support/latexindent/documentation/sec-conclusions-know-limitations.tex')
-rw-r--r-- | support/latexindent/documentation/sec-conclusions-know-limitations.tex | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/support/latexindent/documentation/sec-conclusions-know-limitations.tex b/support/latexindent/documentation/sec-conclusions-know-limitations.tex index fe31bde794..5afdddb6cc 100644 --- a/support/latexindent/documentation/sec-conclusions-know-limitations.tex +++ b/support/latexindent/documentation/sec-conclusions-know-limitations.tex @@ -14,13 +14,12 @@ will need to be stored in the `packing' phase, and that this will improve the efficiency of the script. - You can run \texttt{latexindent} on any file;% - \announce{2019-07-13}*{ability to call latexindent on any file} if you don't specify an - extension, then the extensions that you specify in - \lstinline[breaklines=true]!fileExtensionPreference! (see + You can run \texttt{latexindent} on any file; \announce{2019-07-13}*{ability to call + latexindent on any file} if you don't specify an extension, then the extensions that you + specify in \lstinline[breaklines=true]!fileExtensionPreference! (see \vref{lst:fileExtensionPreference}) will be consulted. If you find a case in which the script struggles, please feel free to report it at \cite{latexindent-home}, and in the - meantime, consider using a \texttt{noIndentBlock} (see \cpageref{lst:noIndentBlock}). + meantime, consider using a \texttt{noIndentBlock} (see \cpageref{lst:noIndentBlock}).% I hope that this script is useful to some; if you find an example where the script does not behave as you think it should, the best way to contact me is to report an issue on |