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 23:05:14 +0200 [thread overview]
Message-ID: <386fe4579a196e29e042fcd44c14eb141dbe14c5.camel@telenet.be> (raw)
In-Reply-To: <a9e203b96f504bed5e3ab99ad5173aedbb04ec95.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
Maxime Devos schreef op di 28-06-2022 om 22:13 [+0200]:
> 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)?
>
(TBC: you can, if you want)
[-- 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 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 6:57 [feature request] merge sxml->html from (haunt html) into guile? Blake Shaw
2022-06-28 13:26 ` Luis Felipe
2022-06-28 18:34 ` Wiki && " Blake Shaw
2022-06-28 20:13 ` Maxime Devos
2022-06-28 21:05 ` Maxime Devos [this message]
2022-06-29 3:26 ` bokr
2022-06-29 6:19 ` Dr. Arne Babenhauserheide
-- strict thread matches above, loose matches on Subject: below --
2022-06-28 19:57 dsmich
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=386fe4579a196e29e042fcd44c14eb141dbe14c5.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).