polybar/include/modules/meta
patrick96 3f60561ae3 logger: Downgrade some warning messages
A warning implies something went wrong and (possibly) the user should do
something about it. However, warnings are not always used this way.

For example:

* When a fallback value for a `${..}` reference is used, this shouldn't
  produce a warning (or notice) since using fallbacks is not something
  bad.
* pulse telling you that it uses the default sink because no sink was
  specified also does not warrant a warning (even notice may be too
  high).
* Whenever polybar shuts down it produces a "Termination signal
  received..." warning. Since there isn't a more proper way to shut down
  polybar, it should not produce a warning. Same argument for a
  `screenchange-reload`
2020-04-22 00:38:31 +02:00
..
base.hpp bar: Make module separator a label 2019-10-27 16:02:33 +01:00
base.inl logger: Downgrade some warning messages 2020-04-22 00:38:31 +02:00
event_handler.hpp refactor(event_handler): Abstract sink attaching 2016-12-23 05:08:19 +01:00
event_module.hpp fix(modules): Warmup in runner thread to avoid block 2017-01-27 13:29:10 +01:00
factory.hpp fix(alsa): use correct module_name 2018-02-11 17:04:08 +01:00
inotify_module.hpp fix(modules): Warmup in runner thread to avoid block 2017-01-27 13:29:10 +01:00
input_handler.hpp refactor(modules): Input handling 2016-12-23 20:43:52 +01:00
static_module.hpp fix(xwindow): Lock mutexes on update #416 2017-02-05 13:37:16 +01:00
timer_module.hpp fix(timer_module): Catch warmup exceptions 2017-01-31 12:38:38 +01:00