-
Notifications
You must be signed in to change notification settings - Fork 91
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
Don't include full file path in log files #445
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. To help make it easier for us to investigate your issue, please follow the contributing instructions. |
Hi, If you don't want to have the full path included in the log have you tried using the following option when ripping?
Example:
|
Interesting thought - I just tested with the below command and found the full file path is still captured in the log.
Output snippet:
|
@the-confessor Have you tried specifying just the |
I did try that also, though I didn't capture it at the time. Result was the same. |
Hi, don't know if something has changed in the meantime but I've just tested this and it seems to work as expected:
|
The default log file format includes the full file path to a ripped file, e.g.
The full path to the file is really not relevant, especially given that the log file is contained in the same folder as the files.
I know that logger plugins are available but that seems like overkill for this case.
Suggestion is to just include the basename of the file:
The text was updated successfully, but these errors were encountered: