~whynothugo

The Netherlands

https://whynothugo.nl

Trackers

~whynothugo/vdirsyncer-rs

Last active 11 days ago

~whynothugo/lsp_lines.nvim

Last active 12 days ago

~whynothugo/shotman

Last active 25 days ago

~whynothugo/systemd-lock-handler

Last active 29 days ago

~whynothugo/whynothugo.nl

Last active a month ago

~whynothugo/dotfiles

Last active a month ago

~whynothugo/docker-makepkg

Last active a month ago

~whynothugo/clipmon

Last active 2 months ago

~whynothugo/wdisplays-ng

Last active 7 months ago

~whynothugo/himitsu-mutt

Last active 11 months ago
View more

#7 Require config only when really needed a day ago

Comment by ~whynothugo on ~bitfehler/vomit

An empty account:

> cat ~/.config/vomit/config.toml 
[accountname]

Doesn't seem to work either:

> vmt pick ~/drafts
10:17:29 [ERROR] failed to parse path '/home/hugo/drafts': path outside expected maildir: prefix not found

I'm not entirely sure what the error means; this directory contains cur, new and tmp.

#7 Require config only when really needed a day ago

Ticket created by ~whynothugo on ~bitfehler/vomit

I'm trying to use vmt pick ~/drafts to pick a single email from the maildir in $HOME/drafts (currently I run ag through these and honestly vmt pick would be a huge improvement).

However, it crashes right away indicating a missing configuration file:

13:31:33 [ERROR] Failed to load config file: error reading config file: No such file or directory (os error 2)

I tried creating an empty configuration file, but it still fails:

13:34:29 [ERROR] Failed to load config file: config error: no accounts found

At this point, I'm not sure what to do. I'm just trying to pick an email message form a given directory, there's no applicable host/username/password that makes sense for this operation.

I'm looking at how this works under the hood, and I think that the main issue is that main() tries to unconditionally read the configuration file, which makes it mandatory even in situations where it doesn't make sense. Perhaps lazy-reading the configuration when it is needed would help, but that sounds like a very non-trivial change.

#3 filter by severity 8 days ago

Comment by ~whynothugo on ~whynothugo/lsp_lines.nvim

This is likely best implemented in neovim itself before it hands over diagnostics to handlers. See https://github.com/neovim/neovim/pull/23751#issuecomment-1563498953

#34 Compatibility with lazy.nvim 8 days ago

Comment by ~whynothugo on ~whynothugo/lsp_lines.nvim

REPORTED RESOLVED NOT_OUR_BUG

#36 highlight entire line 8 days ago

Comment by ~whynothugo on ~whynothugo/lsp_lines.nvim

REPORTED RESOLVED IMPLEMENTED

#27 Docs for async_trait are a pain to read 11 days ago

Ticket created by ~whynothugo on ~whynothugo/vdirsyncer-rs

#17 Generate man page clap clap-mangen 25 days ago

Ticket created by ~whynothugo on ~whynothugo/shotman

Clap can generate most of the common sections, I only need to import some bits of text into this.

Some useful hints at: https://github.com/clap-rs/clap/issues/3354

#26 find_calendars query results in bloated responses 28 days ago

Ticket created by ~whynothugo on ~whynothugo/vdirsyncer-rs

When executing find_calendars, the response is huge since it contains a pretty large XML for each non-collection resource, but we only really care about the collections in the response.

This should be improved, although I'm not sure if that is even possible.

#25 Live test quirks with iCloud 29 days ago

Ticket created by ~whynothugo on ~whynothugo/vdirsyncer-rs

  • Deleting the calendar named /tasks/ is disallowed.

  • At least one additional calendar must exist (otherwise deletion is forbidden).

  • Everything else is super flaky. Creating a calendar works, but it is sometimes not available for a while (I've tested sleeping 10 seconds, but that's not enough).

  • Renaming a collection doesn't seem to have any effect.

  • Creating events in calendars doesn't seem to work; just an opaque 404.

#3 'Failed to grab sleep inhibitor lock'; remains unlocked & blocks sleep 29 days ago

Comment by ~whynothugo on ~whynothugo/systemd-lock-handler

I think this is the issue that was fixed in https://git.sr.ht/~whynothugo/systemd-lock-handler/commit/cb3f544ef4f2730a27adcfebe0df7556dfeb01bd

I've tagged a new release that includes that fix.