From: Maxime Devos <maximedevos@telenet.be>
To: Blake Shaw <blake@sweatshoppe.org>,
Luis Felipe <luis.felipe.la@protonmail.com>
Cc: guile-user@gnu.org, Guix Devel <guix-devel@gnu.org>
Subject: Re: Wiki && Re: [feature request] merge sxml->html from (haunt html) into guile?
Date: Tue, 28 Jun 2022 22:13:58 +0200 [thread overview]
Message-ID: <a9e203b96f504bed5e3ab99ad5173aedbb04ec95.camel@telenet.be> (raw)
In-Reply-To: <CAKjmbcDH8S90FW+xwo7XppU9G=qhTcYJUDPzU2Z9XHAHqLX87g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
Blake Shaw schreef op wo 29-06-2022 om 01:34 [+0700]:
> Which brings up another thing I've been considering working on thats
> been discussed in the Guix community: the need for click-to-edit
> wiki, written in Guile. [...]
I don't think ‘written in Guile’ has been discussed?
Also, I don't see the point in writing our own wiki software in Guile
when there's already plenty of Wiki software in existence with lots of
tools for moderation, version control, backups, lots of testing, etc.
Why not reuse pre-existing work instead of reinventing the wheel (likely
poorly, at least at first)?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-28 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKjmbcBO3YZSjD2zZvQ5Z21NGy78bO-d2FGBSPM=LD1nkwU1Kw@mail.gmail.com>
[not found] ` <skHXeytJhh-XZOWnqaD3Qi1z6uaXri9bDjPfcSBLVCZWzpsrNHqQ_aKLFiKN9Hhd4T2Ftu8Fqk_P6R7sHcZ5kqnfrr6L3Xk7SBDBYar09f8=@protonmail.com>
2022-06-28 18:34 ` Wiki && Re: [feature request] merge sxml->html from (haunt html) into guile? Blake Shaw
2022-06-28 20:13 ` Maxime Devos [this message]
2022-06-28 21:05 ` Maxime Devos
2022-06-29 3:26 ` bokr
2022-06-29 6:19 ` Dr. Arne Babenhauserheide
2022-06-28 19:57 dsmich
-- strict thread matches above, loose matches on Subject: below --
2022-06-29 22:19 Nathan Dehnel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a9e203b96f504bed5e3ab99ad5173aedbb04ec95.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=blake@sweatshoppe.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=luis.felipe.la@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.