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

fix --write-pid-path is no effective #492

Closed
wants to merge 0 commits into from
Closed

Conversation

jialeens
Copy link
Contributor

fix --write-pid-path is no effective

the --write-pid-path is no effective,When picom is started, the configuration --write-pid-path is not read.
When picom exiting, remove the pid file.

@codecov
Copy link

codecov bot commented Sep 16, 2020

Codecov Report

Merging #492 into next will decrease coverage by 0.01%.
The diff coverage is 27.27%.

Impacted file tree graph

@@            Coverage Diff             @@
##             next     #492      +/-   ##
==========================================
- Coverage   36.85%   36.84%   -0.02%     
==========================================
  Files          45       45              
  Lines        8907     8918      +11     
==========================================
+ Hits         3283     3286       +3     
- Misses       5624     5632       +8     
Impacted Files Coverage Δ
src/options.c 21.53% <16.66%> (-0.10%) ⬇️
src/config_libconfig.c 57.95% <25.00%> (-0.41%) ⬇️
src/picom.c 68.97% <100.00%> (+0.30%) ⬆️
src/win.c 64.47% <0.00%> (-0.32%) ⬇️

src/picom.c Outdated Show resolved Hide resolved
@yshui
Copy link
Owner

yshui commented Sep 16, 2020

@jialeens Thanks for the PR!.

You also need to handle this option coming from command line.

@jialeens
Copy link
Contributor Author

@yshui
I handle command line argument checking

src/options.c Outdated
@@ -700,6 +700,11 @@ bool get_cfg(options_t *opt, int argc, char *const *argv, bool shadow_enable,
case 322:
// --logpath, --log-file
free(opt->logpath);
if (*optarg != '/') {
log_error("The --log-file in your configuration file is not"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is no requirement for --log-file to be an absolute path.

@yshui
Copy link
Owner

yshui commented Sep 16, 2020

Sorry, closed by mistake

@yshui
Copy link
Owner

yshui commented Sep 16, 2020

Pushed your changes to next, thanks.

@jialeens
Copy link
Contributor Author

OK, I see it.

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants