On Wed Mar 19, 2025 at 11:08 AM CET, Quentin Carbonneaux wrote:
> PIC is not supported on any target.

Thank you for the clarification!

> It'd be good to look into it, but
> the design I have in mind will require frontends to change the IL they
> emit. Basically, each symbol reference would have to specify if it is
> expected to be in the same object file or if we need to look it up at
> runtime.

This sounds interesting. I hope this will come one day!

On Sat Feb 15, 2025 at 8:56 PM CET, Armin Preiml wrote:
> Signed-off-by: Armin Preiml <apreiml@strohwolke.at>
> ---
>
> v2: add nomem to the function signature of next
>
>  format/ini/scan.ha | 30 ++++++++++++++++++++++--------
>  1 file changed, 22 insertions(+), 8 deletions(-)
>
> diff --git a/format/ini/scan.ha b/format/ini/scan.ha
> index c4796cba..8bc629f9 100644
> --- a/format/ini/scan.ha
> +++ b/format/ini/scan.ha
> @@ -31,11 +31,16 @@ export fn finish(sc: *scanner) void = {

On Sat Mar 15, 2025 at 9:30 AM CET, Max Schillinger wrote:
> My server is a cheap VPS. But my new calendar is empty and I don't 
> know what could take so much time.

I think the password in .htpasswd is the problem!

I have created password as described in doc/tokidoki.8.scd:

  htpasswd -c -B -C 17 <filename> <user>

This already took a few seconds.

Now I have tried this command to verify my password:

On Sat Mar 15, 2025 at 9:30 AM CET, Max Schillinger wrote:
> Do you know what could be the reason for these slow response times?
>
> See a (redacted) log output below.

Sorry, I forgot to enable debug logs.

I assume this number after the IP address is the HTTP status code. It 
looks like responses are only slow for status codes 201, 204, 207, 308, 
and 400.

201 Created
204 No Content
207 Multi-Status (WebDAV; RFC 4918)

Hi all,

now I'm running tokidoki on my server. It works but response times are 
super slow (partially). Most of the times about 10 or 20 seconds.

My server is a cheap VPS. But my new calendar is empty and I don't know 
what could take so much time.

I'm wondering if tokidoki is running in a timeout of 10 seconds (once or 
twice per request). Because most of the response times in the log are 10 
or 20 seconds plus a little bit. But I also see 14.55s and 19.60s which 
doesn't match such a timeout.

Do you know what could be the reason for these slow response times?

On Fri Mar 14, 2025 at 10:31 PM CET, Conrad Hoffmann wrote:
> No, the names shouldn't matter. Keep them simple (in terms of special 
> characters), clients will have to be able to work with them.

Cool, thank you!

Hi Conrad,

On Fri Mar 14, 2025 at 3:40 PM CET, Conrad Hoffmann wrote:
> You cannot create a calendar from an .ics file. You can only create an 
> empty calendar (see below). I suppose you could pre-populate the 
> calendar with .ics files, but those should be individual events, not 
> calendars.
>
>> But this gives me an empty calendar (named "My calender"). When I create
>> a new entry in this calendar (in Thunderbird), this entry shows up in
>> this automatically created calendar file:
>> 
>> /tmp/tokidoki/bWF4/calendar/default/a2e9e1b4-2f4d-4c5a-b233-7f054b52b647.ics
>

Hi all,

I have tried tokidoki. But I'm doing something wrong.

I have built it with PAM:

go build -tags pam ./cmd/tokidoki/


Then I have created a folder for tokidoki and added a sample calendar:

mkdir /tmp/tokidoki
cd /tmp/tokidoki
wget https://gist.githubusercontent.com/DeMarko/6142417/raw/1cd301a5917141524b712f92c2e955e86a1add19/sample.ics

On Mon Mar 3, 2025 at 3:06 PM CET, Max Schillinger wrote:
> Btw, setting a subject with `aerc mailto:recipient... :header Subject 
> My Subject` fails as well. At least for this case, there is a 
> workaround:
>
>   aerc mailto:recipient...?subject='My Subject'
>
> As far as I know, I can't add an attachment this way.

Sorry, this is wrong. This command works:

  aerc 'mailto:recipient@example.org?subject=My Subject&attach=my_attachment'

On Sun Mar 2, 2025 at 4:47 PM CET, Ralph Seichter wrote:
> Possibly timing issues? Commands are executed asynchronously. Perhaps
> :attach is run before aerc is ready to process the command.

Same problem when aerc is already running.
I don't know how I could add a delay to the attach command.

Btw, setting a subject with `aerc mailto:recipient... :header Subject My 
Subject` fails as well. At least for this case, there is a workaround:

  aerc mailto:recipient...?subject='My Subject'

As far as I know, I can't add an attachment this way.