Skip to content
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

Expand documentation clarifying the use of -c switch that moves cruft files to another directory #180

Closed
ashirwad opened this issue Dec 4, 2019 · 3 comments

Comments

@ashirwad
Copy link

@ashirwad ashirwad commented Dec 4, 2019

Hello,

Thanks for this excellent tool! I have started using latexindent recently and found it to be really useful in beautifying latex documents.

I am creating this issue to bring to your attention the peculiar behavior of the -c switch that's supposed to move latexindent-generated files to a specified directory. When I use -c=build, latexindent does the following:

  • moves only the backup files, and
  • renames the indent.log file to buildindent.log and keeps it in the main directory.

However, -c=build/ (notice the trailing slash) gives the desired behavior. In your SO answer you have not included the trailing slash (the cause of the unexpected behavior), however, in your documentation you have used a trailing slash when defining the path for the cruft directory. So, you may want to add some clarifying remarks in your documentation emphasizing the use of a trailing slash.

Thanks!

@cmhughes

This comment has been minimized.

Copy link
Owner

@cmhughes cmhughes commented Dec 4, 2019

@ashirwad

This comment has been minimized.

Copy link
Author

@ashirwad ashirwad commented Dec 4, 2019

No problem, take your time. :)

jlelong added a commit to James-Yu/LaTeX-Workshop that referenced this issue Dec 27, 2019
@cmhughes

This comment has been minimized.

Copy link
Owner

@cmhughes cmhughes commented Mar 9, 2020

Thanks again for this, as of b84e9dc this is resolved. It'll be part of the next release, thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.