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.

Sign up for GitHub

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

Jump to bottom

Disable profanity logging (not chatlogs) alltogeter or choosing where to write them #1442

Closed
mrkiko opened this issue Nov 27, 2020 · 5 comments · Fixed by #1455
Closed

Disable profanity logging (not chatlogs) alltogeter or choosing where to write them #1442

mrkiko opened this issue Nov 27, 2020 · 5 comments · Fixed by #1455
Assignees
@jubalh
Milestone
0.10.0

Comments

@mrkiko
Copy link

mrkiko commented Nov 27, 2020

Thus not having ~/.local/share/profanity/logs/profanity.log around.

Sorry if this is possible and I am missing the way to do it.
Thanks!!
@jubalh jubalh self-assigned this Nov 27, 2020
@jubalh jubalh added this to the 0.10.0 milestone Nov 27, 2020
@jubalh
Copy link
Member

jubalh commented Dec 3, 2020

You can use profanity -f logfile1 to use ~/.local/share/profanity/logs/logfile1.log instead. of default filename.

@mrkiko
Copy link
Author

mrkiko commented Dec 3, 2020 via email

@jubalh
Copy link
Member

jubalh commented Dec 3, 2020

I don't remember the reason why I made -f use a filename in the log dir and not let the user define the whole filename. I think there was one.. I'll look into it.
Then one could also do something like profanity -f /dev/null.

@wstrm
Copy link
Contributor

wstrm commented Dec 11, 2020

@jubalh did you find any reason? Doing stuff like profanity -f /dev/null that you noted would be nice :)

jubalh added a commit that referenced this issue Dec 11, 2020
@jubalh
Use whole path as logfile when defined via -f
a899001 
`profanity -f my` created ~/.local/share/profanity/logs/my.log`.

It would be nicer if one could define the actual path, so one can choose
another directory or even use /dev/null.

Fixes #1442
@jubalh jubalh mentioned this issue Dec 11, 2020
Merged
@jubalh
Copy link
Member

jubalh commented Dec 11, 2020

@mrkiko please test with the new -f behaviour. We will notify people in the changelog of the behaviour change.

@jubalh jubalh mentioned this issue Jan 11, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jubalh jubalh

Labels
None yet
Projects
None yet
Milestone
0.10.0
Development

Successfully merging a pull request may close this issue.

Use whole path as logfile when defined via -f profanity-im/profanity
3 participants
@jubalh @wstrm @mrkiko