pacien

Quoting 8go (2022-06-07 18:52:09) > I saw that many people add the `v` letter in front of the tag. Seems > common. Does it matter to you? Better with or...

Quoting 8go (2022-06-10 12:44:12) > Is there a community standard on the tag message? Should it be just > short as "release: v2.36.0" to ease bot-parsing, or can it be...

Quoting 8go (2022-06-07 18:52:09) > I saw that many people add the `v` letter in front of the tag. Seems > common. Does it matter to you? Better with or...

Quoting 8go (2022-10-11 10:23:38) > @pacien : Is there anything broken? Is it not working well as is? (Please ignore the previous message. GitHub suddenly decided to repost my old...

Maybe should the index be stored within each work directory instead of `~/.local/share/paperwork` as well. I currently switch between multiple work directories by using a symlink-based workaround for both the...

Good point regarding the separation of the index and the data. However I would really be against a lookup+timer approach for the index deletion: I store collections on my NAS...

The rebuild time for a >500 docs collection is really a big deal when all you want to do is insert a new document or simply search for "that invoice"...

taskwiki seems to behave strangely when blank line(s) are added between the viewport header and an existing task list: it inserts a second copy of the list instead of updating...

Same error with mautrix-telegram 0.8.2: ``` Aug 11 20:10:57 hp2 mautrix-telegram[16109]: [[email protected].[BRIDGE_PORTAL_USER]] Failed to handle Telegram update UpdateNewChannelMessage([MESSAGE REDACTED]), pts=36917, pts_count=1) Aug 11 20:10:57 hp2 mautrix-telegram[16109]: Traceback (most recent call...

An easy workaround could be to set this logger's level to WARNING by default instead. https://github.com/tulir/mautrix-telegram/blob/281f7203dc6eec8be9e6489a8bf29ad7e850f07d/example-config.yaml#L345-L346