From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Guile User <guile-user@gnu.org>
Subject: Starting a GNU Guile awesome list
Date: Mon, 13 Jul 2020 23:19:50 +0200 [thread overview]
Message-ID: <b9af8fee-cc10-9673-c230-10c0d1ffdb48@posteo.de> (raw)
Hello Guile Users,
I followed up on that idea I mentioned recently on the mailing list and
started creating an awesome list:
https://notabug.org/ZelphirKaltstahl/awesome-guile
I'd prefer to render only the org-mode file, as that is what I write and
feel most comfortable in, but I decided that the wrong / incomplete
rendering on notabug would seriously limit accessibility, so I exported
markdown and texinfo from org-mode.
If you know more things, which should be added to the list, please tell
me or create a PR or open an issue or … you get it.
Also links to usage examples would be very welcome.
I would like to keep the list informal and easily extendable. A few
questions though:
* Do you think license information should be written next to each item
in the list?
* Do you think each item should have a short description or not? Or
perhaps whenever one is readily available?
* Do you think the rendered readme.md should be handwritten instead of
exported from org-mode? (Perhaps I should not ask this question …
the amount of markdown typing … my fingers hurt.)
Best regards,
Zelphir
--
repositories: https://notabug.org/ZelphirKaltstahl
next reply other threads:[~2020-07-13 21:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 21:19 Zelphir Kaltstahl [this message]
2020-07-13 21:56 ` Starting a GNU Guile awesome list Jack Hill
2020-07-13 22:56 ` Aleix Conchillo Flaqué
2020-07-14 23:26 ` Zelphir Kaltstahl
2020-07-14 9:00 ` Dmitry Alexandrov
2020-07-14 21:23 ` Zelphir Kaltstahl
2020-07-15 6:32 ` Dr. Arne Babenhauserheide
2020-07-16 8:47 ` Dmitry Alexandrov
2020-07-16 19:01 ` Dr. Arne Babenhauserheide
2020-10-10 12:31 ` Zelphir Kaltstahl
2020-10-10 13:14 ` Matt Wette
2020-10-11 0:57 ` Zelphir Kaltstahl
2020-10-11 19:51 ` Ricardo Wurmus
2020-10-11 23:39 ` Zelphir Kaltstahl
2020-10-12 10:33 ` Ricardo Wurmus
2020-11-08 17:09 ` Zelphir Kaltstahl
2020-11-08 18:55 ` Paul Smith
2020-12-05 18:15 ` Zelphir Kaltstahl
2020-07-15 6:36 ` Dr. Arne Babenhauserheide
2020-07-15 21:14 ` Zelphir Kaltstahl
2020-07-15 22:40 ` Dr. Arne Babenhauserheide
2020-07-16 9:18 ` A licence for an ‘awesome list’ (was: Starting a GNU Guile awesome list) Dmitry Alexandrov
2020-07-16 18:56 ` Dr. Arne Babenhauserheide
2020-07-16 18:58 ` Dr. Arne Babenhauserheide
2020-07-16 20:47 ` Zelphir Kaltstahl
2020-07-16 22:55 ` Vladimir Zhbanov
2020-07-16 23:05 ` Vladimir Zhbanov
2020-07-17 0:20 ` John Cowan
2020-07-17 6:43 ` Dr. Arne Babenhauserheide
2020-07-14 14:14 ` Starting a GNU Guile awesome list Dr. Arne Babenhauserheide
2020-07-15 21:24 ` Zelphir Kaltstahl
2020-07-15 22:29 ` Dr. Arne Babenhauserheide
2020-07-14 16:37 ` Taylan Kammer
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=b9af8fee-cc10-9673-c230-10c0d1ffdb48@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=guile-user@gnu.org \
/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).