Markus Triska

@jeshan: Yes, I would greatly appreciate your help with porting newer developments from Scryer Prolog to the SICStus version! I think a good way to do this would be a series...

No PR is being filed here, this issue is the discussion about how to best synchronize the versions. A PR could be a result of this discussion.

I have one general comment for porting changes: The focus should be on the **commits** that went into Scryer Prolog, *not the PRs*! That is: To port a commit that...

(It is OK to reference multiple commits in a single commit, if it makes sense to port the commits as a unit!)

I have added instructions to **LetSWICrypt** that describe how to renew the certificate *without root permissions*, please have a look. Simply set up a cron job (as a regular user)...

The new `ssl_add_certificate_key/3` predicate proposed in https://github.com/SWI-Prolog/packages-ssl/pull/86 lets you update the certificate of an already created context. Pending comments from OpenSSL developers whether this is an officially supported way to update...

All of this is solved in https://github.com/SWI-Prolog/packages-ssl/pull/87, please try it out!

This is possible as of SWI-Prolog 7.3.34, and documented in the new section: [**Exchanging certificates**](https://github.com/triska/letswicrypt#exchanging-certificates) You can use the predicates of `library(ssl)` to detect when it is time to renew...

This now works, thank you a lot!

@peschue: To write each character literally, you can also use `put_char/1`: ?- maplist(put_char, "b\"ar"). b"ar true. Using `format/2` is much more efficient: ?- format("~s", ["b\"ar"]). b"ar true.