Hi folks,
With the recent deprecation of [shortcuts], I had to go fishing for information to figure out what had changed. The manual for dunst does not mention the words “shortcut” or “bind” anymore, and the closest we get to informing the user is with the deprecation message.
https://github.com/dunst-project/dunst/blob/master/src/utils.c#L357-L360
https://github.com/dunst-project/dunst/blob/master/src/option_parser.c#L435-L438
Could we turn the elements in deprecated_sections into { name, info } arrays where info points you to a relevant manual, and modify save_settings accordingly?
I'm not sure how much energy we want to put into making informative deprecation; but if I run into it, others are likely to do the same, and it'd be a shame to get them started on the wrong foot with dunstctl.
Thanks for your work on the recent iterations!
Hi folks,
With the recent deprecation of
[shortcuts], I had to go fishing for information to figure out what had changed. The manual fordunstdoes not mention the words “shortcut” or “bind” anymore, and the closest we get to informing the user is with the deprecation message.https://github.com/dunst-project/dunst/blob/master/src/utils.c#L357-L360
https://github.com/dunst-project/dunst/blob/master/src/option_parser.c#L435-L438
Could we turn the elements in
deprecated_sectionsinto{ name, info }arrays whereinfopoints you to a relevant manual, and modifysave_settingsaccordingly?I'm not sure how much energy we want to put into making informative deprecation; but if I run into it, others are likely to do the same, and it'd be a shame to get them started on the wrong foot with
dunstctl.Thanks for your work on the recent iterations!