lasers

Here's an idea... For starters, users could manually specify which placeholders to escape html. ```diff diff --git a/py3status/formatter.py b/py3status/formatter.py index 9b8659a..e37ea0f 100644 --- a/py3status/formatter.py +++ b/py3status/formatter.py @@ -2,6 +2,7 @@...

>I think you're right. The problem is that I was looking at... Solved by https://github.com/ultrabug/py3status/pull/2202.... Probably.

@ultrabug IIRC this looks 99% fine. Can address them later if necessary.

Not very recently. I looked at this weeks after this came out. LGTM. I have a diff after this that makes py3status act more like i3status in terminal. You can...

>that's the one above about the output_format parameter being overwritten on the module level IIRC that's for i3status modules only. AFAIK no i3status module have this config and only one...

@oaken-source This does it? ```diff diff --git a/py3status/i3status.py b/py3status/i3status.py index 8fc97e5..c3f6de4 100644 --- a/py3status/i3status.py +++ b/py3status/i3status.py @@ -330,10 +330,10 @@ class I3status(Thread): value = TZTIME_FORMAT if key == "format_time": continue...

I'd like this feature too... Change default name so `Saved 6/13/2023` could be replaced with `Stashed 6/13/2023`.... or really, to just add brackets `[Saved MM/DD/YYYY]` to default name so the...

2 years 3 months passed. Can you determine if you're still having this problem today on `1.10.8` or `1.10.9_pre`? The older versions are not trustworthy. Thank you.

@NoXPhasma How about now on current git? We had a couple of xinerama PRs merged recently.

>official way This is probably it. Obviously we have a bug somewhere. Did you try numbers outside of total number of monitors too? How are you autostarting it? See if...