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
[RFC] Features/configurable log name #1
Conversation
This allows running more than one weechat at a time without awkwardly mv(1)'ing the log files out from under it, or somesuch.
EDIT: Also, how should I go about emitting a useful warning? Before this patch there was only one real error condition. Should I just refactor |
Running two different WeeChat with same home can lead to problems (the test is made on weechat.log, but this file is not really a problem). |
By the way, there's a task planned to have separate directories: https://savannah.nongnu.org/task/?10934 |
So this is a quick and dirty stab at enabling a workflow I need: Two weechats running. One for a work server that likes to do lots of force joining and generally messing with my client, and one for all the other clients.
Before this, I was doing something like;
but it's pretty awkward. With this patch I can just do
WEECHAT_LOG_NAME=work.log weechat and have it do the right thing. Thoughts?