Skip to content
This repository has been archived by the owner on Aug 20, 2023. It is now read-only.

Implement sane defaults for compton-conf #43

Open
agaida opened this issue May 26, 2017 · 2 comments
Open

Implement sane defaults for compton-conf #43

agaida opened this issue May 26, 2017 · 2 comments
Assignees
Labels

Comments

@agaida
Copy link
Member

agaida commented May 26, 2017

The current defaults render the desktop nearly unusable - i would suggest to use the built in defaults of compton.

Unfortunately there is no way to export the buitin settings, so that means reading the conde (afaik).

@agaida agaida added the polish label May 26, 2017
@agaida agaida self-assigned this May 26, 2017
@ska67
Copy link
Contributor

ska67 commented Oct 22, 2017

What do you mean with nearly unusable? Do you mean, for example, transparent menus?
That is what I find unusable.

If you start compton without a configuration file, you get no effect at all.
Try it for yourself compton --dbus --config /dev/null
So I think built-in defaults come from the compton.sample.conf file in the root directory. This file is not significantly different from the compton.example.conf file from compton-conf.

IMO, if there is still interest, we should discuss sane defaults in public.
But I would be happy if at least my open pull requests were merged :-)

@agaida
Copy link
Member Author

agaida commented Feb 19, 2018

@ska67 - you are right, the default values in compton-conf seems to be from the sample file. And i would prefer the defaults equal to compton without a configuration file - thats all.

EDIT: compton lacks several things - one of these things is that it is not possible to dump the current configuration. Ok, i say nothing about bitrot and that the project is dead in the sense of dead*. The only activity for years is that some people say how great compton is and how they like it - but no one stand up, merge some things nor fix some of the bugs. If i could i would drop compton-conf - but as long compton live as a zombie in distributions there is no reason to do so.

*)
chjj/compton#432
chjj/compton#398 * not that ikey should be known :D
chjj/compton#352
chjj/compton#300
chjj/compton#267
chjj/compton#105 * really nice

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants