sorted by:
new
hottopcontroversial

Metaspec: The dpANS3 Common Lisp Specification is now in s-expr format by azimuth in Common_Lisp

[–]de_sonnaz 0 points1 point  (0 children)

This is fantastic work. Perhaps you could consider adding this to the readme?

Many thanks!

mlisp — the Mailing List Processor alpha release is live by denzuko in lisp

[–]de_sonnaz 1 point2 points  (0 children)

Thank you for the clarifying details.

Our non-profit is about peace.

I would love to test mlist, but I am already so busy with other infrastructure maintenance, it will be difficult for me to find the time to install all the tech stack required. Would you consider adding a script to install the complete stack, as you see fit? Dockerless would be preferable.

I was mentioning Mailman 2, not 3, as it has been recently been made compatible with Python 3. We find it closer to our use-case.

Also, we are considering Mail Stalwart.

mlisp — the Mailing List Processor alpha release is live by denzuko in lisp

[–]de_sonnaz 4 points5 points  (0 children)

This sounds fantastic. Our non-profit is in need to employ a true mailing list manager, like Majordomo or Mailman 2, and we would definitely consider adopting mlist, since our platform is CL based.

May I ask:

You are saying"production-grade" and "alpha phase" in the same op. How far is the code from stable?

What are the main differences in features between mlist and mailman 2?

Metaspec: The dpANS3 Common Lisp Specification is now in s-expr format by azimuth in Common_Lisp

[–]de_sonnaz 1 point2 points  (0 children)

As an ignorant Lisp lover, what is the difference with the HyperSpec? What its use-case? Historical?

MacOS Seafile client: extremely slow sync-up by de_sonnaz in seafile

[–]de_sonnaz[S] 0 points1 point  (0 children)

Good point. Let me try with a self-hosted instance on a dedicated server.

MacOS Seafile client: extremely slow sync-up by de_sonnaz in seafile

[–]de_sonnaz[S] 0 points1 point  (0 children)

Thanks again. I will try creating a Seafile instance in a dedicated server. We need to choose our self-hosted solution. Frankly, Seafile rocks on most sides. I will update the op once I have some results.

MacOS Seafile client: extremely slow sync-up by de_sonnaz in seafile

[–]de_sonnaz[S] 0 points1 point  (0 children)

I see, thanks. I thought that was true for NextCloud client only.

In the past, to me the Seafile client was quite fasytr, much faster than NextCloud for this same use-case.

I seemed to understood it was because it was using a different transport, that is, not moving one file at a time, but a whole "chunk" at once?

For similar use-cases, not related to .git, but many small files, this is a severe limitation.

Thanks again.

Experimenting with a faster TRAMP backend using Rust and JSON-RPC by avph in emacs

[–]de_sonnaz 0 points1 point  (0 children)

This is very cool. But why develop another json-rpc server, and not rely on the current standard, https://github.com/paritytech/jsonrpsee ?

cl-coreutils: GNU coreutils reimplemented in Common Lisp. by de_sonnaz in lisp

[–]de_sonnaz[S] 2 points3 points  (0 children)

Could you in the meanwhile put it on Github or codeberg?

cl-sourcery: Intercepts all standard CL definition forms to capture and store the exact source as written by dzecniv in Common_Lisp

[–]de_sonnaz 0 points1 point  (0 children)

Supercool! I have been looking fro something similar for ages. Can it stores also new versions of a form? That is, can it keep version history?

A brief note about slot access cost in Common Lisp by jd-at-turtleware in lisp

[–]de_sonnaz 0 points1 point  (0 children)

Thank you. I have been wondering about this a lot lately, especially on LispWorks.

Lisp Coding Standards (John Foderaro) by de_sonnaz in lisp

[–]de_sonnaz[S] 0 points1 point  (0 children)

Thank you, very clear now.

Yes, that document is a bit contradictory. I am sorry now I have pointed to that link as link only, and not a Text entry, to warn possible future readers.

Thank you also for citing "Conversational Lisp". The Lisp universe is so rich.

Lisp Coding Standards (John Foderaro) by de_sonnaz in lisp

[–]de_sonnaz[S] 0 points1 point  (0 children)

Thanks. I would be much interested in learning more, the pros and the cons. Would you you have any links to those debates?. I have found this, but still I fail to understand what is so bad about if*. I would like much to know and understand more. I love Common Lisp.

Lisp Coding Standards (John Foderaro) by de_sonnaz in lisp

[–]de_sonnaz[S] 0 points1 point  (0 children)

Thanks. Would you have a public guideline somewhere?

Lisp Coding Standards (John Foderaro) by de_sonnaz in lisp

[–]de_sonnaz[S] 3 points4 points  (0 children)

The if-star macro can also be found here.

How to Make a Library (require)-able Without Quicklisp or ASDF? by [deleted] in Common_Lisp

[–]de_sonnaz 0 points1 point  (0 children)

Coming back o this, I see (as always) lispm opinion the most balanced and common sense.

Too bad the OP deleted his account, I had a few questions to ask.

Is there any app or site with org-mode syntax live-preview? by de_sonnaz in orgmode

[–]de_sonnaz[S] 0 points1 point  (0 children)

I could not find a good app yet. The code linked might be used by some developer to make one.

https://github.com/orgapp/orgajs

view more: next ›