From: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-user@gnu.org
Subject: Re: Guile Hacker Handbook - Character sets
Date: Fri, 19 Feb 2021 12:15:53 +0100 [thread overview]
Message-ID: <47212862c48080378509b721d2874a27f86de519.camel@korwin-zmijowski.fr> (raw)
In-Reply-To: <87y2flm49a.fsf@elephly.net>
Le jeudi 18 février 2021 à 22:53 +0100, Ricardo Wurmus a écrit :
> Hi Jérémy,
>
> > For those who missed it, I am also starting a work towards a guile-
> > ide.el for Emacs.
> >
> > https://framagit.org/Jeko/guile-ide
>
> Interesting. Do you think there is some overlap with guile-
> studio[1]?
> (It’s available in Guix.)
>
> [1]: https://git.elephly.net/software/guile-studio.git
>
Hi Ricardo !
Firstly, I am convinced Guile Studio can help in Guile onboarding ! I
did come from Spacemacs and moved to Emacs (because of Paredit) when I
felt ready. I have to say the way Spacemacs configuration is made also
helped me to apprehend the jump to Emacs.
I think there could be overlaps actually even if we seem to serve
different purposes. In my perspective, Guile Studio could activate a
Guile mode instead of the Scheme mode ! This Guile mode would come from
guile-ide.el. So it can benefit to newcomers thanks to Guile Studio as
well as advanced (bare)Emacs users.
The guile-ide.el I try to build is focused on the code edition
(specially "refactoring" features like extracting or renaming
variables/procedures, adding/removing procedure parameters, generating
test/implemetation code/file, highlighting syntax errors/unused
variables/not defined variables, providing auto-completion, jumping to
definition/usage/documentation, and so on… all accross all files of a
project).
There is more, but I have to start somewhere haha.
Those are features I am used to when I edit code with editors at work.
Jérémy
next prev parent reply other threads:[~2021-02-19 11:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 19:54 Guile Hacker Handbook - Character sets Jérémy Korwin-Zmijowski
2021-02-18 21:53 ` Ricardo Wurmus
2021-02-19 11:15 ` Jérémy Korwin-Zmijowski [this message]
2021-02-18 21:54 ` Ricardo Wurmus
2021-02-19 8:10 ` Eli Zaretskii
2021-02-19 10:20 ` Jérémy Korwin-Zmijowski
2021-02-19 12:16 ` Eli Zaretskii
2021-02-18 21:56 ` Zelphir Kaltstahl
2021-02-19 11:23 ` Jérémy Korwin-Zmijowski
2021-02-19 17:26 ` Dr. Arne Babenhauserheide
2021-02-18 23:15 ` divoplade
2021-02-19 0:10 ` John Cowan
2021-02-19 12:59 ` Jérémy Korwin-Zmijowski
2021-02-19 7:09 ` Dr. Arne Babenhauserheide
2021-02-19 21:31 ` Jérémy Korwin-Zmijowski
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=47212862c48080378509b721d2874a27f86de519.camel@korwin-zmijowski.fr \
--to=jeremy@korwin-zmijowski.fr \
--cc=guile-user@gnu.org \
--cc=rekado@elephly.net \
/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).