Nils Landt

I use a script for running tests in multiple languages. It duplicates some functionality of vim-test (to be editor agnostic) and includes custom logic for very specific projects I've had...

The biggest problem would be that I'm the only vim user on that project, and moving from "external script called via vim-test custom runner" to vim-test configuration would leave everyone...

I set `(setq org-caldav-debug-level 2)` and the issue occurred again, but `org-caldav-event-list` looks perfectly normal. Do I need to also not set `org-caldav-show-sync-results` to nil, or did I check in...

It took a while, but it happened now. I also have another idea of what might happen. I'm not calling `org-caldav-sync` manually, I'm using a function when emacs is idle,...

The error still happens, but infrequently, and I wasn't diligent about checking the messages before quitting Emacs. I have debug on error enabled globally, but the debugger did not open....

I added a save function to the timer as you suggested, and the issue did not occur in the 3 weeks since. So this seems fixed for me! > We...

I have updated to the newest version and removed my own save function. Thanks for the fix!

Unfortunately, 43fba8b59ff89903d1313c3343722160b7d5ff8b did not fix the issue. I removed my inbox file and org-caldav-bb for a fresh start. Below are some examples: org-caldav log: ``` UID: 026ce32d4298421764270505ead1d406@overture Title: Ostern (Stille...

Which option would you prefer?

I don't think #3210 is related, but this would fix it: `flatpak run --command='bottles-cli' com.usebottles.bottles run --args-replace -b MyBottle -e "$@"` That being said - `wine --version` results in `flatpak...