-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 28/02/14 18:05, Marco Hunsicker wrote: > IMHO this would be too much of a hassle for little gain as it would > require all users to adjust their configuration. That's not necessary -- no overriding could just be inferred to mean "the old style".
> I've forwarded a patch for code review that allows a bit more > freedom as my initial proposal. > > It allows one to configure the separator string that should be > used. An empty string disables the insertion of a default > separator altogether. > > This way it's possible to allow customization for all output > formats, but only with i3bar one is required to resort to the > module format string for the actual definition, while with the > other formats you can conveniently define it just once and avoid > the otherwise probably necessary duplication in the module > definitions. > > This should support your use case as well. Disable the default > separator. Then add any necessary separation as part of a module's > format string. Sounds good. - -- Alexander alexan...@plaimi.net https://secure.plaimi.net/~alexander -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlMQw3kACgkQRtClrXBQc7U5iQEAnheXwdSfAdQa68HFjnSv4Mks QdCOqCxPujibe4oe2D8A/RDswOYrdROic8W0VEAiLgKiqrgQisSTNx2zkaE07fls =wsUC -----END PGP SIGNATURE-----
