From: Emanuel Berg via "Emacs development discussions." <emacs-devel@gnu.org>
To: emacs-devel@gnu.org
Cc: help-gnu-emacs@gnu.org
Subject: Re: urandom number in Emacs
Date: Sun, 07 Nov 2021 09:58:00 +0100 [thread overview]
Message-ID: <878ry0mjfr.fsf@zoho.eu> (raw)
In-Reply-To: 87czncmju0.fsf@zoho.eu
I've heard "Emacs don't need Elispers, Emacs needs
C programmers".
OK, so you have a list of things Emacs needs in C?
Or maybe a linked list I should say ...
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-11-07 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 16:35 urandom number in Emacs Emanuel Berg via Emacs development discussions.
2021-11-07 0:13 ` Emanuel Berg via Emacs development discussions.
2021-11-07 8:22 ` Omar Polo
2021-11-07 8:49 ` Emanuel Berg via Emacs development discussions.
2021-11-07 8:53 ` Omar Polo
2021-11-07 9:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-07 8:58 ` Emanuel Berg via Emacs development discussions. [this message]
2021-11-07 19:47 ` Emanuel Berg via Emacs development discussions.
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ry0mjfr.fsf@zoho.eu \
--to=emacs-devel@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).