From: "Ludovic Courtès" <ludo@gnu.org>
To: Aniket Patil <aniket112.patil@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Outreachy contribution & guidance with guile.
Date: Wed, 28 Oct 2020 15:37:31 +0100 [thread overview]
Message-ID: <87361y2z84.fsf@gnu.org> (raw)
In-Reply-To: <CAF-xJgvYYMa6dzATMazszfdVG6v=W8kmjbehDnnc=oBesKx0Cg@mail.gmail.com> (Aniket Patil's message of "Wed, 28 Oct 2020 18:27:42 +0530")
Hello Aniket,
Aniket Patil <aniket112.patil@gmail.com> skribis:
> I sent patches for gnu/packages/cran.scm. I am planning to add more
> variables to cran.scm file. Meanwhile, I am writing my final outreachy
> application.
Great!
> I am thinking about translating guix or gnu docs in Indian languages,
> which I know.
Translation work is happening via the Translation Project. See
<https://translationproject.org/domain/guix-manual.html> for the Guix
manual (I think few GNU manuals are available for translations apart
from this one).
Several people on this list are involved in translation, and Arun Isaac
took care of the Tamil translation of the Shepherd, so surely you can
get guidance on this from people here.
> Also, as an emacs user, who is trying to understand lisp to get
> comfortable around emacs, I was a bit confused about whether shall I
> learn lisp first or guile first? What do you suggest?
Guix itself is written in Guile Scheme. Scheme is a member of the “Lisp
family” of programming languages, and so is Emacs Lisp (the language
used in Emacs).
There are “dialectic” differences, such as different function names, but
also deeper changes, such as a single name space for both “normal”
variables and procedures in Scheme as well as a focus on “functional
programming” in Scheme whereas Emacs Lisp is more biased towards
imperative programming.
I’m very much biased :-), but I think that Scheme is a bit easier to
learn.
If you’re going to write code for Emacs, Emacs Lisp is what you should
learn; if you’re going to write code for Guix, learn Scheme. Either
way, despite their differences, you’ll find it rather easy to learn one
once you know the other.
Ludo’.
next prev parent reply other threads:[~2020-10-28 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 12:57 Outreachy contribution & guidance with guile Aniket Patil
2020-10-28 14:27 ` zimoun
2020-10-28 14:37 ` Ludovic Courtès [this message]
2020-10-28 15:01 ` Aniket Patil
2020-10-29 4:33 ` Arun Isaac
2020-10-29 16:37 ` Aniket Patil
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87361y2z84.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=aniket112.patil@gmail.com \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).