I should have waited to see it several times before reporting. Maybe my network systemd service restarted at that moment. Feel free to close.

I got pimsync working and I am really glad not to deal with vdirsyncer breaking on every nixpkgs update (because of the python ecosystem). Ideally I would use pimsync to sync with google. I've read your blog and I dont mind setting up a proxy for auth. Would that work with master ?

I just ran pimsync check I got an almost instant error discovering context url: error resolving DNS SRV records: error executing query all timed out

I reran it and it worked fine. Is the timeout set to a very low value ?

ha yeah I feared something like that though I had not checked. I will try to fix the nix derivation. Sees like I can't close this ticket ? but feel free to do so

sinve you've fixed some of the issues I had on the master branch, I tried to run the master branch (compiled via nix https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/pi/pimsync/package.nix, with the source changed to a 17 march revision) and printing pimsync version returns 0.3.0. Would be nice to see it's not a proper tagged release, like maybe 0.4.0-unstable-a543b4 or like neovim does

nvim --version
NVIM v0.11.0-nightly+d6653e1

thank you

I see this in my logs

mars 16 23:42:58 tatooine systemd[2729]: Starting pimsync calendar&contacts synchronization...
mars 16 23:42:58 tatooine pimsync[2995214]: Error: Could not parse configuration file at /home/teto/.config/pimsync/pimsync.conf
mars 16 23:42:58 tatooine pimsync[2995214]: Caused by:
mars 16 23:42:58 tatooine pimsync[2995214]:     0: resolving password for storage
mars 16 23:42:58 tatooine pimsync[2995214]:     1: Command exited with status 127.

If I run the command in a shell I get

pimsync sync                              
Error: initialising application
Caused by:
    0: initialising storage calendar_nova_gmail_remote
    1: input/output error: error performing webdav request: http request returned 401 Unauthorized
    2: error performing webdav request: http request returned 401 Unauthorized
    3: http request returned 401 Unauthorized

so I believe the message "Could not parse configuration file" is faulty. In the first excerpt, pimsync is just not able to fetch my password. The 2nd example gives another error but it shows that pimsync can parse the config.

With pimsync 0.3.0

Running this in nixos, a linux distribution with readonly package directories, I get:

$ pimsync sync       
ERROR [pimsync] Error in sync task: creating plan
Caused by:
    0: Error querying status database: Error interacting with sqlite backend: attempt to write a readonly database (code 8)
    1: Error interacting with sqlite backend: attempt to write a readonly database (code 8)
    2: attempt to write a readonly database (code 8).

I had a quick look at strace to see where pimsync tried to write but could not find the path. I have

➜ cat /home/teto/.config/pimsync/pimsync.conf
[general]
status_path "/home/teto/.local/share/pimsync/status"

➜ ls -l /home/teto/.local/share/pimsync/status
.rw-r--r-- 135k teto 16 mars  17:00  calendar_fastmail.status
.rw-r--r--  17k teto 16 mars  17:00  calendar_fastmail.status-journal

➜  file /home/teto/.local/share/pimsync/status/calendar_fastmail.status
/home/teto/.local/share/pimsync/status/calendar_fastmail.status: SQLite 3.x database, last written using SQLite version 3048000, file counter 133, database pages 33, cookie 0xd, schema 4, UTF-8, version-valid-for 133

It would be nice to have the faulty path in the error message. In this case, it looks read-write for my user so I dont get the error yet.

I just had the error: bail!("Invalid value for colletions: {params}"); should be "collections"

I love lsp_lines but the way it displaces the content of the text can be annoying which is why if the diagnostic fits on the line as virtual text, I would prefer it to be used and ONLY when the diagnostic is too big, resort to virtual lines.

it's already set to false (the default), my remark works regardless of insert mode. if you delete a word, quickly alternate between insert and normal modes, keeping one's eyes on the current row can be tiring (cursorline helps a bit but even better if the eyes don't have to move). It's not easy to implement, just a suggestion. Very cool plugin btw, I love it.